19.

Simulation
User Manual

Rock Flow Dynamics

March 2019
 19.1

Copyright Notice
Rock Flow Dynamics r (RFD), 2004–2019. All rights reserved. This document is the intel-
lectual property of RFD. It is not allowed to copy this document, to store it in an information
retrieval system, distribute, translate and retransmit in any form or by any means, electronic
or mechanical, in whole or in part, without the prior written consent of RFD.

Trade Mark
RFD, the RFD logotype and tNavigator r product, and other words or symbols used to identify
the products and services described herein are trademarks, trade names or service marks of
RFD. It is not allowed to imitate, use, copy trademarks, in whole or in part, without the prior
written consent of the RFD. A graphical design, icons and other elements of design may be
trademarks and/or trade dress of RFD and are not allowed to use, copy or imitate, in whole
or in part, without the prior written consent of the RFD. Other company, product, and service
names are the properties of their respective owners.

Security Notice
The software’s specifications suggested by RFD are recommendations and do not limit the
configurations that may be used to operate the software. It is recommended to operate the
software in a secure environment whether such software is operated on a single system or
across a network. A software’s user is responsible for configuring and maintaining networks
and/or system(s) in a secure manner. If you have any questions about security requirements
for the software, please contact your local RFD representative.

Disclaimer
The information contained in this document is subject to change without notice and should
not be construed as a commitment by RFD. RFD assumes no responsibility for 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.
Since the software, which is described in the present document is constantly improved, you
may find descriptions based on previous versions of the software.

2
 19.1

Contents
1. Introduction 50

2. Physical model 54
2.1. Differential equations for black-oil model . . . . . . . . . . . . . . . . . . 54
2.2. Boundary conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
2.3. Initial conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
2.3.1. Equilibrium initialization . . . . . . . . . . . . . . . . . . . . . . . . 56
2.3.2. Non-equilibrium initialization . . . . . . . . . . . . . . . . . . . . . 56
2.3.3. Mixed initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
2.4. Permeability tensor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
2.5. Porosity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
2.6. Phase relative permeability . . . . . . . . . . . . . . . . . . . . . . . . . . 59
2.6.1. Keywords to set relative permeability . . . . . . . . . . . . . . . . . 60
2.6.2. Corey correlation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
2.6.3. LET correlation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
2.6.4. Linear Baker model . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
2.6.5. First Stone’s model . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
2.6.6. Second Stone’s model . . . . . . . . . . . . . . . . . . . . . . . . . . 73
2.6.7. End point scaling, two-point method . . . . . . . . . . . . . . . . . . 73
2.6.8. End point scaling, three-point method . . . . . . . . . . . . . . . . . 77
2.6.9. Directional and irreversible RP . . . . . . . . . . . . . . . . . . . . . 79
2.6.10. RP at dual porosity runs. . . . . . . . . . . . . . . . . . . . . . . . . 79
2.6.11. User-defined relative permeability of the injected phase . . . . . . . 80
2.6.12. Surface tension effects . . . . . . . . . . . . . . . . . . . . . . . . . 81
2.6.13. Miscible flood modeling . . . . . . . . . . . . . . . . . . . . . . . . 83
2.6.14. Velocity-dependent relative permeabilities . . . . . . . . . . . . . . . 84
2.7. Hysteresis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
2.7.1. Implementing the hysteresis option . . . . . . . . . . . . . . . . . . . 87
2.7.2. Relative permeability hysteresis in the non-wetting phase . . . . . . . 92
2.7.3. Relative permeability hysteresis in the wetting phase . . . . . . . . . 96
2.7.4. Capillary pressure hysteresis . . . . . . . . . . . . . . . . . . . . . . 98
2.7.5. Hysteresis in three-phase system . . . . . . . . . . . . . . . . . . . . 100
2.7.6. Hysteresis definition in IM/GE/ST format . . . . . . . . . . . . . . . 101
2.8. PVT properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
2.8.1. Phase viscosity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
2.8.2. Phase formation volume factor . . . . . . . . . . . . . . . . . . . . . 103
2.8.3. Phase molar density . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
2.8.4. Phase mass density . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
2.8.5. Solubility of gas component into oil phase . . . . . . . . . . . . . . . 104
2.8.6. Vaporisation of oil component into gas phase . . . . . . . . . . . . . 106
2.8.7. Keywords to set PVT . . . . . . . . . . . . . . . . . . . . . . . . . . 106
2.8.8. API tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

CONTENTS 3
 19.1

2.9. Oil Standing’s correlations . . . . . . . . . . . . . . . . . . . . . . . . . . 108

2.9.1. 2-phase water-oil model. Dead Oil . . . . . . . . . . . . . . . . . . . 109
2.9.2. 3-phase model. Live Oil . . . . . . . . . . . . . . . . . . . . . . . . 109
2.10. Gas Standing’s correlations . . . . . . . . . . . . . . . . . . . . . . . . . . 111
2.10.1. Gas Formation Volume Factor . . . . . . . . . . . . . . . . . . . . . 111
2.10.2. Gas Viscosity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
2.11. Capillary pressures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
2.11.1. Oil-gas capillary pressure . . . . . . . . . . . . . . . . . . . . . . . . 112
2.11.2. Oil-water capillary pressure . . . . . . . . . . . . . . . . . . . . . . 112
2.11.3. Gas-water capillary pressure . . . . . . . . . . . . . . . . . . . . . . 112
2.11.4. Capillary pressure end point scaling . . . . . . . . . . . . . . . . . . 112
2.11.5. Capillary pressure calculation according to Leverett J-function . . . . 114
2.12. Fluid velocities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
2.13. Inflow from aquifer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
2.14. Well . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
2.14.1. Well approximation . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
2.14.2. Group control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
2.14.3. Economic control . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
2.14.4. Separators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
2.14.5. Gas plants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
2.14.6. MULTI-phase injection . . . . . . . . . . . . . . . . . . . . . . . . . 125
2.14.7. WAG injection mode . . . . . . . . . . . . . . . . . . . . . . . . . . 125
2.14.8. DCQ. Gas Field Model . . . . . . . . . . . . . . . . . . . . . . . . . 126
2.14.9. Gas Lift Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . 126
2.14.10. Standard network option . . . . . . . . . . . . . . . . . . . . . . . . 128
2.14.11. NETWORK option. Automatic chokes. Compressors . . . . . . . . . 128
2.14.12. Pipe and networks equipment. Chokes . . . . . . . . . . . . . . . . . 130
2.14.13. Well prioritization option . . . . . . . . . . . . . . . . . . . . . . . . 132
2.14.14. Prioritized drilling queue. Sequential drilling queue . . . . . . . . . . 133
2.15. Multisegment well . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
2.15.1. Multisegment well model . . . . . . . . . . . . . . . . . . . . . . . . 135
2.15.2. Inflow performance . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
2.15.3. The pressure loss calculation . . . . . . . . . . . . . . . . . . . . . . 138
2.15.4. Top segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
2.15.5. External sources and sinks . . . . . . . . . . . . . . . . . . . . . . . 139
2.15.6. Looped flow paths . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
2.15.7. Pressure drops based on VFP tables . . . . . . . . . . . . . . . . . . 142
2.15.8. Reverse flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
2.15.9. Chokes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
2.15.10. Injection wells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
2.15.11. Model for gas-liquid slip . . . . . . . . . . . . . . . . . . . . . . . . 144
2.15.12. Three-phase flow and oil-water slip . . . . . . . . . . . . . . . . . . 147
2.15.13. Friction pressure loss . . . . . . . . . . . . . . . . . . . . . . . . . . 149

CONTENTS 4
 19.1

2.15.14. Acceleration pressure loss . . . . . . . . . . . . . . . . . . . . . . . 149

2.15.15. Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
2.16. Polymer Flood . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
2.16.1. Polymer Flood option POLYMER . . . . . . . . . . . . . . . . . . . 151
2.16.2. Polymer flooding based on BrightWater technology . . . . . . . . . . 153
2.16.3. Polymer flood in IM format . . . . . . . . . . . . . . . . . . . . . . 154
2.17. Tracer modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
2.17.1. Tracer modeling keywords . . . . . . . . . . . . . . . . . . . . . . . 157
2.17.2. Decay of tracer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
2.17.3. Tracer adsorption . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
2.17.4. Adsorption and decay of tracer . . . . . . . . . . . . . . . . . . . . . 158
2.18. Foam modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
2.19. Residual oil modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
2.20. The division of hydrocarbons tracking . . . . . . . . . . . . . . . . . . . . 162
2.21. Asphaltene modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
2.22. Alkaline flooding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
2.23. Surfactant injection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
2.23.1. Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
2.24. Waters with different salinities . . . . . . . . . . . . . . . . . . . . . . . . 168
2.24.1. Fresh water injection into the saline reservoir . . . . . . . . . . . . . 168
2.24.2. Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
2.24.3. Low salinity option . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
2.25. Scale deposition model . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
2.26. Temperature option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
2.27. Dual porosity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
2.27.1. RP at dual porosity runs. . . . . . . . . . . . . . . . . . . . . . . . . 177
2.27.2. Gravity drainage option . . . . . . . . . . . . . . . . . . . . . . . . . 178
2.28. Coal Bed Methane Model . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
2.28.1. Coal Bed Methane Model in IM/GE/ST format . . . . . . . . . . . . 182
2.29. Geomechanical model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
2.29.1. Fully coupled method . . . . . . . . . . . . . . . . . . . . . . . . . . 182
2.29.2. Successive method . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
2.29.3. Calculation of azimuth angle of hydraulic fracture . . . . . . . . . . 186
2.29.4. Mohr-Coulomb failure criterion . . . . . . . . . . . . . . . . . . . . 186
2.29.5. Keywords for the fully coupled method . . . . . . . . . . . . . . . . 186
2.29.6. Keywords for the successive method . . . . . . . . . . . . . . . . . . 187

3. Compositional model 188

3.1. Vapor-liquid equilibrium . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
3.2. Phase stability test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
3.3. Vapor-liquid-water equilibrium . . . . . . . . . . . . . . . . . . . . . . . . 190
3.3.1. CO2/H2S solution in the aqueous phase . . . . . . . . . . . . . . . . 192
3.4. Hydrocarbon-water phase equilibrium . . . . . . . . . . . . . . . . . . . . 192
3.5. Equations of state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

CONTENTS 5
 19.1

3.5.1. EOS in reservoir and surface conditions . . . . . . . . . . . . . . . . 195

3.6. Empirical correlations for EOS parameters . . . . . . . . . . . . . . . . . . 195
3.6.1. Riazi and Daubert . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
3.6.2. Kesler and Lee . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
3.6.3. Cavett . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
3.6.4. Twu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
3.7. Density . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
3.8. Viscosity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
3.8.1. Lohrenz-Bray-Clark Correlation . . . . . . . . . . . . . . . . . . . . 200
3.8.2. Modified Lohrenz-Bray-Clark Correlation . . . . . . . . . . . . . . . 201
3.8.3. Pedersen Correlation . . . . . . . . . . . . . . . . . . . . . . . . . . 201
3.9. Lumping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
3.10. Multiple water component model . . . . . . . . . . . . . . . . . . . . . . . 202
3.11. Diffusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
3.11.1. The cross phase diffusion . . . . . . . . . . . . . . . . . . . . . . . . 204
3.12. Solid phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
3.12.1. Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
3.13. Simulation of nonequilibrium thermodynamics . . . . . . . . . . . . . . . . 206
3.13.1. Methods 1 and 2 for simulation of nonequilibrium processes . . . . . 206
3.13.2. DKDT method for simulation of nonequilibrium . . . . . . . . . . . 207

4. Compositional thermal model with chemical reactions 210

4.1. Basic volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
4.2. Saturations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
4.3. Phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
4.4. Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
4.5. Mass and molar water density . . . . . . . . . . . . . . . . . . . . . . . . . 213
4.6. Mass and molar liquid density . . . . . . . . . . . . . . . . . . . . . . . . 215
4.7. Molar and mass gas density . . . . . . . . . . . . . . . . . . . . . . . . . . 216
4.8. Molar solid density . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
4.9. Thermodynamic equilibrium condition . . . . . . . . . . . . . . . . . . . . 219
4.10. Phase saturations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
4.11. Water viscosity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
4.12. Oil viscosity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
4.13. Gas viscosity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
4.14. Enthalpy and heat capacity of the components . . . . . . . . . . . . . . . . 223
4.15. Enthalpy and internal energy of the phases . . . . . . . . . . . . . . . . . . 224
4.16. Water enthalpy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
4.17. Liquid enthalpy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
4.18. Vaporization enthalpy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
4.19. Gas phase enthalpy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
4.20. Solid phase enthalpy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
4.21. Rock enthalpy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
4.22. Default enthalpy values for ST format models . . . . . . . . . . . . . . . . 228

CONTENTS 6
 19.1

4.23. Block internal energy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

4.24. Porosity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
4.25. Pore volume of grid block . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
4.26. Bulk volume of grid block . . . . . . . . . . . . . . . . . . . . . . . . . . 233
4.27. Bulk volume of rock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
4.28. Thermal conductivity of the grid block . . . . . . . . . . . . . . . . . . . . 234
4.29. Chemical reactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
4.30. The heat loss between the reservoir and surroundings . . . . . . . . . . . . 238
4.31. Heater simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
4.31.1. Heater with constant energy injection rate . . . . . . . . . . . . . . . 240
4.31.2. Heater with energy density dependent injection rate . . . . . . . . . . 240
4.31.3. Selecting of the heater operating mode depending on the defined
properties E3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
4.31.4. Temperature difference dependent injection rate . . . . . . . . . . . . 241
4.31.5. Flags of automatic heating or cooling ST . . . . . . . . . . . . . . . 241
4.32. Phase flow rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
4.33. Mass conservation equation . . . . . . . . . . . . . . . . . . . . . . . . . . 242
4.34. Energy conservation equation . . . . . . . . . . . . . . . . . . . . . . . . . 242
4.35. Phase relative permeabilities . . . . . . . . . . . . . . . . . . . . . . . . . 244
4.35.1. Phase relative permeability for two-phase systems . . . . . . . . . . 244
4.35.2. Phase relative permeabilities scaling . . . . . . . . . . . . . . . . . . 245
4.35.3. Phase relative permeabilities for three-phase systems . . . . . . . . . 252
4.36. Calculation of the phase composition . . . . . . . . . . . . . . . . . . . . . 256
4.36.1. Statement of the problem . . . . . . . . . . . . . . . . . . . . . . . . 256
4.37. Initial conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
4.37.1. Explicit specification of initial conditions . . . . . . . . . . . . . . . 257
4.37.2. Calculations of initial conditions from hydrostatic and thermody-
namic equilibrium conditions . . . . . . . . . . . . . . . . . . . . . . 259

5. Mathematical model 261

5.1. Space approximation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
5.2. Solution algorithm for time step problem . . . . . . . . . . . . . . . . . . . 261
5.3. Time approximation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
5.4. Transition from physical model to system of equations . . . . . . . . . . . 262
5.5. Model geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
5.5.1. Defining active/inactive blocks . . . . . . . . . . . . . . . . . . . . . 265
5.5.2. Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
5.5.3. Multireservoir option . . . . . . . . . . . . . . . . . . . . . . . . . . 266
5.5.4. Coordinate transformation . . . . . . . . . . . . . . . . . . . . . . . 266
5.5.5. Connections between blocks . . . . . . . . . . . . . . . . . . . . . . 266
5.5.6. Transmissibility calculation . . . . . . . . . . . . . . . . . . . . . . . 267
5.5.7. Grid coarsening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
5.5.8. LGR – Local Grid Refinement . . . . . . . . . . . . . . . . . . . . . 270
5.6. Well Approximation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

CONTENTS 7
 19.1

5.6.1. Well Inflow Performance . . . . . . . . . . . . . . . . . . . . . . . . 272

5.6.2. Connection transmissibility calculation (CF and Kh) . . . . . . . . . 273
5.6.3. Average permeability calculation . . . . . . . . . . . . . . . . . . . . 274
5.6.4. Pressure equivalent radius calculation . . . . . . . . . . . . . . . . . 274
5.6.5. Mobility calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
5.6.6. Average well bore density and connection pressure calculation . . . . 275
5.6.7. Well potential calculations . . . . . . . . . . . . . . . . . . . . . . . 276
5.7. Modified well model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
5.7.1. Well model with generalized connections . . . . . . . . . . . . . . . 278
5.7.2. Hydraulic fracture data . . . . . . . . . . . . . . . . . . . . . . . . . 279
5.7.3. Hydraulic fractures via virtual connections . . . . . . . . . . . . . . 281
5.7.4. Flow rate along the fracture . . . . . . . . . . . . . . . . . . . . . . 281
5.7.5. Calculation of the inflow to the fracture from the grid block . . . . . 282
5.7.6. Total inflow from the hydraulic fracture to the well connection . . . 283
5.7.7. Description of simulation of large amount of hydraulic fractures . . . 283
5.7.8. Fracture keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
5.7.9. Simulation of plugging of well bottom zone . . . . . . . . . . . . . . 286
5.7.10. Simulation of well bottom zone dynamics: processing acids, surfactants287
5.7.11. Well bottom zone keywords . . . . . . . . . . . . . . . . . . . . . . 288
5.8. Hydraulic Fractures modeling via LGR . . . . . . . . . . . . . . . . . . . . 288
5.8.1. Fracture Modeling Workflow . . . . . . . . . . . . . . . . . . . . . . 288
5.8.2. Fracture Zone (FZ) and Non-Fracture Zone (NFZ) . . . . . . . . . . 291
5.8.3. Local Grid Refinement and Unstructured Grids . . . . . . . . . . . . 296
5.8.4. Fractures Intersection . . . . . . . . . . . . . . . . . . . . . . . . . . 299
5.8.5. Permeability Adjustment in Fracture Zone . . . . . . . . . . . . . . . 300
5.8.6. Fracture Rotation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
5.8.7. Properties of inactive coarse blocks, penetrated by the fracture . . . . 301
5.9. ASP model description . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
5.9.1. Water relative permeability calculations . . . . . . . . . . . . . . . . 304
5.9.2. Water viscosity calculations . . . . . . . . . . . . . . . . . . . . . . 305
5.9.3. Water viscosity calculations without salt . . . . . . . . . . . . . . . . 305
5.9.4. Capillary pressure in water-oil system . . . . . . . . . . . . . . . . . 306
5.9.5. Water mass density calculations . . . . . . . . . . . . . . . . . . . . 306
5.10. Oil and gas in-place . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
5.10.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
5.10.2. Fluid-in-place tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
5.10.3. Log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
5.10.4. Fluid-in-place density and concentration . . . . . . . . . . . . . . . . 312
5.10.5. Oil and gas in-place via separators . . . . . . . . . . . . . . . . . . . 313
5.11. Phase potentials calculations . . . . . . . . . . . . . . . . . . . . . . . . . 313
5.12. Split and merge (sector modeling) . . . . . . . . . . . . . . . . . . . . . . 314
5.12.1. Split in console version . . . . . . . . . . . . . . . . . . . . . . . . . 315
5.12.2. Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316

CONTENTS 8
 19.1

5.12.3. Special features for wells . . . . . . . . . . . . . . . . . . . . . . . . 316

5.13. Reservoir Coupling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
5.13.1. Master and subordinate groups . . . . . . . . . . . . . . . . . . . . . 318
5.13.2. Surface network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
5.13.3. Features of the implementation . . . . . . . . . . . . . . . . . . . . . 320

6. VFP tables generation 321

6.1. Single Phase Flow Theory . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
6.1.1. Friction pressure loss . . . . . . . . . . . . . . . . . . . . . . . . . . 322
6.1.2. Single-Phase Friction Factor (f) . . . . . . . . . . . . . . . . . . . . 323
6.1.3. The Single Phase hydrostatic pressure drop . . . . . . . . . . . . . . 323
6.2. Multiphase Flow Theory . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
6.2.1. Nomenclature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
6.2.2. Griffith Correlation . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
6.2.3. Petalas & Aziz correlation . . . . . . . . . . . . . . . . . . . . . . . 331
6.2.4. Beggs & Brill correlation . . . . . . . . . . . . . . . . . . . . . . . . 342
6.2.5. Beggs & Brill revised correlation . . . . . . . . . . . . . . . . . . . 346
6.2.6. Orkiszewski method . . . . . . . . . . . . . . . . . . . . . . . . . . 348
6.2.7. Gray correlation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
6.2.8. Aziz, Govier and Fogarasi correlation . . . . . . . . . . . . . . . . . 353
6.2.9. Mukherjee & Brill correlation . . . . . . . . . . . . . . . . . . . . . 357

7. FAQ 361
7.1. Various questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
7.1.1. What does the message mean "Warning: BOM ignored" . . . . . . . 361
7.1.2. What minimum amount of memory is required for model’s calculation 361
7.1.3. What causes the warnings of negative compressibility and/or viscosity 361
7.2. Reasons for the difference in calculation results . . . . . . . . . . . . . . . 363
7.3. ”The correct answer” in dynamic modelling . . . . . . . . . . . . . . . . . 366
7.3.1. Problem discretization and solution . . . . . . . . . . . . . . . . . . 366
7.3.2. Influence of the number of cores . . . . . . . . . . . . . . . . . . . . 368
7.3.3. Influence of timestep . . . . . . . . . . . . . . . . . . . . . . . . . . 369
7.3.4. What can we do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
7.4. How to speed-up model calculation without its simplification . . . . . . . . 374
7.4.1. Problem statement . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
7.4.2. Flow through the block . . . . . . . . . . . . . . . . . . . . . . . . . 375
7.4.3. Grid connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
7.4.4. Grid stratification factor . . . . . . . . . . . . . . . . . . . . . . . . 378
7.4.5. Influence of smoothness of the data . . . . . . . . . . . . . . . . . . 380
7.4.6. Influence of end points match . . . . . . . . . . . . . . . . . . . . . 383
7.4.7. Conservation equation . . . . . . . . . . . . . . . . . . . . . . . . . 384
7.4.8. VFP tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385

CONTENTS 9
 19.1

8. tNavigator console version 386

8.1. Command line options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
8.1.1. Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
8.1.2. Input data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
8.1.3. Client-server options . . . . . . . . . . . . . . . . . . . . . . . . . . 388
8.1.4. Simulation process . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
8.1.5. Parallel computation . . . . . . . . . . . . . . . . . . . . . . . . . . 389
8.1.6. Group: thread to CPU bind logic model . . . . . . . . . . . . . . . . 389
8.1.7. Debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
8.1.8. Result files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
8.1.9. Boundary conditions . . . . . . . . . . . . . . . . . . . . . . . . . . 391
8.1.10. UNRST/UNSMRY compatibility output . . . . . . . . . . . . . . . . 391
8.1.11. MO options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
8.1.12. GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
8.1.13. Remote GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
8.1.14. Model save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394

9. Data files 395

9.1. Results of tNavigator calculation . . . . . . . . . . . . . . . . . . . . . . . 395
9.2. USER folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
9.3. Log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
9.3.1. Load Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
9.3.2. Blocks with convergence problems . . . . . . . . . . . . . . . . . . . 400
9.3.3. The reason of each Newton iteration . . . . . . . . . . . . . . . . . . 400

10. Units 402

11. Input data format 404

11.1. Input formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
11.2. tNavigator format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
11.3. Keywords’ syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405

12. Keywords for formats tN, E1, E3 407

12.1. Definition section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
12.1.1. RUNSPEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
12.1.2. TITLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
12.1.3. REPORTFILE / REPORTSCREEN . . . . . . . . . . . . . . . . . . 411
12.1.4. TNAVCTRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
12.1.5. AIMCTRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
12.1.6. FLASHCTRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
12.1.7. NEFLASH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
12.1.8. VELDEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
12.1.9. PHASEID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
12.1.10. TFORM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436

CONTENTS 10
 19.1

12.1.11. IMPORT_WELL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437

12.1.12. IMPORT_NETWORK . . . . . . . . . . . . . . . . . . . . . . . . . 438
12.1.13. IMPORT_PROJECT . . . . . . . . . . . . . . . . . . . . . . . . . . 439
12.1.14. UNIFOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
12.1.15. UNIFOUTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
12.1.16. MULTOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
12.1.17. MULTOUTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
12.1.18. START . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
12.1.19. METRIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
12.1.20. FIELD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
12.1.21. LAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
12.1.22. LANGUAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
12.1.23. BLACKOIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
12.1.24. DEFINES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
12.1.25. VDEF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
12.1.26. PREDEFINES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
12.1.27. OPEN_BASE_MODEL . . . . . . . . . . . . . . . . . . . . . . . . . 460
12.1.28. DIMENS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
12.1.29. TABDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
12.1.30. EQLDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
12.1.31. ACTDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
12.1.32. REGDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
12.1.33. VFPIDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
12.1.34. VFPPDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
12.1.35. GPTDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
12.1.36. PIMTDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
12.1.37. ROCKCOMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
12.1.38. ROCKDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
12.1.39. WELLDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
12.1.40. FAULTDIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
12.1.41. WSEGDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
12.1.42. HEATDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
12.1.43. UDQDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
12.1.44. UDQPARAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
12.1.45. UDADIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
12.1.46. UDTDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
12.1.47. TCBDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
12.1.48. TRACERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
12.1.49. SURFACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
12.1.50. SURFACTW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
12.1.51. POLYMER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
12.1.52. ALKALINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
12.1.53. NONNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491

CONTENTS 11
 19.1

12.1.54. THERMAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492

12.1.55. REACTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
12.1.56. OIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
12.1.57. GAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
12.1.58. WATER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
12.1.59. VAPOIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
12.1.60. DISGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
12.1.61. SOLID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
12.1.62. BRINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
12.1.63. LOWSALT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
12.1.64. TEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502
12.1.65. TEMPR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
12.1.66. API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
12.1.67. ASPHALTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
12.1.68. FOAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
12.1.69. MISCIBLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
12.1.70. DIFFUSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
12.1.71. DIFFX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
12.1.72. DIFFY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
12.1.73. DIFFZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
12.1.74. CART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
12.1.75. SATOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
12.1.76. NUMRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
12.1.77. KVALUES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
12.1.78. ISGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
12.1.79. NOMIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
12.1.80. INCLUDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
12.1.81. PATHS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
12.1.82. IMPLICIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
12.1.83. DUALPORO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523
12.1.84. DUALPERM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
12.1.85. COAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
12.1.86. GRAVDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
12.1.87. GRAVDRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
12.1.88. LGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
12.1.89. VISCD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
12.1.90. NODPPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
12.1.91. NETWORK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
12.1.92. CO2SOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
12.1.93. H2SSOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
12.1.94. EQLOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
12.1.95. GRIDOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
12.1.96. FORMOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536

CONTENTS 12
 19.1

12.1.97. NOSIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538

12.1.98. GASFIELD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
12.1.99. GEOMECH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
12.1.100. GEODIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
12.1.101. RFD_WFRAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
12.1.102. AIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
12.1.103. AIMFRAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
12.1.104. ECHO / NOECHO . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
12.1.105. IMPES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
12.1.106. FULLIMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
12.1.107. HWELLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
12.1.108. PETOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
12.1.109. PARALLEL / PARAOPTS . . . . . . . . . . . . . . . . . . . . . . . 550
12.1.110. NPROCX / NPROCKY . . . . . . . . . . . . . . . . . . . . . . . . . 551
12.1.111. MESSAGE / MESSAGES / MSGFILE . . . . . . . . . . . . . . . . 552
12.1.112. WARN / NOWARN / NOWARNEP . . . . . . . . . . . . . . . . . . 553
12.1.113. END . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
12.1.114. ECINIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
12.1.115. ECDATES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
12.1.116. ECVAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
12.1.117. SCDPDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
12.1.118. LGRCOPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
12.1.119. BIGMODEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
12.1.120. JALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
12.1.121. SKIPSTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
12.1.122. LICENSES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
12.1.123. MEMORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
12.1.124. FMTIN/ FMTSAVE . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
12.1.125. MULTIN/ MULTSAVE . . . . . . . . . . . . . . . . . . . . . . . . . 568
12.1.126. MONITOR/ NOMONITO . . . . . . . . . . . . . . . . . . . . . . . 569
12.1.127. PSPLITX/ PSPLITY/ PSPLITZ . . . . . . . . . . . . . . . . . . . . 570
12.1.128. RPTHMD/ RPTHMG/ RPTHMW . . . . . . . . . . . . . . . . . . . 571
12.1.129. RPTISOL/ RPTPROPS/ RPTREGS/ RPTRUNSP/ RPTSCHED/
RPTSMRY/ RPTSOL . . . . . . . . . . . . . . . . . . . . . . . . . . 572
12.1.130. UNIFIN/ UNIFSAVE . . . . . . . . . . . . . . . . . . . . . . . . . . 573
12.1.131. PVTGEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
12.1.132. CBMOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
12.1.133. DPCDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
12.1.134. NODPCDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
12.1.135. TRACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
12.1.136. ENDSCALE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
12.2. Grid section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
12.2.1. GRID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583

CONTENTS 13
 19.1

12.2.2. DX / DY / DZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
12.2.3. DXV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
12.2.4. DYV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
12.2.5. DZV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
12.2.6. TOPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
12.2.7. MIDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590
12.2.8. COORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
12.2.9. ZCORN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
12.2.10. ADDZCORN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
12.2.11. OLDTRAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
12.2.12. NEWTRAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
12.2.13. PERMX / PERMY / PERMZ . . . . . . . . . . . . . . . . . . . . . . 597
12.2.14. PERMMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
12.2.15. MULTX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
12.2.16. MULTX- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
12.2.17. MULTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
12.2.18. MULTY- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
12.2.19. MULTZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
12.2.20. MULTZ- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
12.2.21. HMMLTPX / HMMLTPY / HMMLTPZ / HMMLTPXY . . . . . . . 611
12.2.22. HMMULTX / HMMULTY / HMMULTZ / HMMLTXY / HMMULTPV612
12.2.23. HMMULTX- / HMMULTY- / HMMULTZ- . . . . . . . . . . . . . . 614
12.2.24. PORO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616
12.2.25. NTG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
12.2.26. DZNET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
12.2.27. PORV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
12.2.28. MULTPV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621
12.2.29. ACTNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
12.2.30. MINPV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
12.2.31. MINPORV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626
12.2.32. MINPVV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627
12.2.33. MINDZNET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628
12.2.34. MINPVR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629
12.2.35. MINROCKV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 630
12.2.36. MINRV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
12.2.37. PERMAVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
12.2.38. FAULTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
12.2.39. MULTFLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
12.2.40. THPRESFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
12.2.41. USEFLUX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638
12.2.42. DUMPFLUX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639
12.2.43. FLUXREG / FLUXTYPE . . . . . . . . . . . . . . . . . . . . . . . 640
12.2.44. DOMAINS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641

CONTENTS 14
 19.1

12.2.45. ISOLNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642

12.2.46. SOLVDIRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
12.2.47. RESVNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
12.2.48. COORDSYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
12.2.49. GDFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
12.2.50. TRANX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
12.2.51. TRANY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
12.2.52. TRANZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
12.2.53. MAXTRANZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
12.2.54. NNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
12.2.55. EDITNNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
12.2.56. EDITNNCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656
12.2.57. NNCGEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
12.2.58. PINCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
12.2.59. PINCHXY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662
12.2.60. PINCHOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
12.2.61. PINCHREG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664
12.2.62. PINCHNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666
12.2.63. JFUNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667
12.2.64. JFUNCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
12.2.65. JFPERM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671
12.2.66. GRIDUNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672
12.2.67. MAPAXES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
12.2.68. MAPUNITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674
12.2.69. LX / LY / LZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675
12.2.70. DPNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676
12.2.71. DPGRID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677
12.2.72. SIGMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
12.2.73. SIGMAV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
12.2.74. LTOSIGMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680
12.2.75. SIGMAGD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681
12.2.76. SIGMAGDV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
12.2.77. THCONMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
12.2.78. SIGMATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686
12.2.79. MULTMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687
12.2.80. DZMTRX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688
12.2.81. DZMATRIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689
12.2.82. DZMTRXV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
12.2.83. MULTREGT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691
12.2.84. ROCKPROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693
12.2.85. ROCKCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694
12.2.86. ROCKCONT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696
12.2.87. THCGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 698

CONTENTS 15
 19.1

12.2.88. THCOIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700

12.2.89. THCWATER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702
12.2.90. THCSOLID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704
12.2.91. THCROCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
12.2.92. HEATTX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 708
12.2.93. HEATTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709
12.2.94. HEATTZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710
12.2.95. SPECGRID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711
12.2.96. BG_xxx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712
12.2.97. CARFIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713
12.2.98. CARFINBG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
12.2.99. REFINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716
12.2.100. INNERWIDTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719
12.2.101. ENDFIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
12.2.102. NXFIN / NYFIN / NZFIN . . . . . . . . . . . . . . . . . . . . . . . 722
12.2.103. HXFIN / HYFIN / HZFIN . . . . . . . . . . . . . . . . . . . . . . . 723
12.2.104. AMALGAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724
12.2.105. COARSEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725
12.2.106. GRIDFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727
12.2.107. PLMIXNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 728
12.2.108. ROCKDEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729
12.2.109. IMPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
12.2.110. VISGRID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
12.2.111. DIFFMMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733
12.2.112. DIFFMX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
12.2.113. DIFFMX- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
12.2.114. DIFFMY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
12.2.115. DIFFMY- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
12.2.116. DIFFMZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
12.2.117. DIFFMZ- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
12.2.118. INIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
12.2.119. RPTGRID/ RPTGRIDL . . . . . . . . . . . . . . . . . . . . . . . . . 741
12.2.120. YOUNGMOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
12.2.121. POISSONR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
12.2.122. BIOTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
12.2.123. CORNERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
12.2.124. DEACDEPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
12.2.125. FRACTURE_PATH . . . . . . . . . . . . . . . . . . . . . . . . . . . 749
12.2.126. FRACTURE_PLANE . . . . . . . . . . . . . . . . . . . . . . . . . . 751
12.2.127. FRACTURE_TEMPLATE . . . . . . . . . . . . . . . . . . . . . . . 752
12.2.128. FRACTURE_WELL . . . . . . . . . . . . . . . . . . . . . . . . . . 762
12.2.129. FRACTURE_ARITHMETIC . . . . . . . . . . . . . . . . . . . . . . 764
12.3. Arithmetic section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 769

CONTENTS 16
 19.1

12.3.1. EDIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 770

12.3.2. ARITHMETIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771
12.3.3. BOX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 778
12.3.4. ENDBOX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779
12.3.5. ARR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 780
12.3.6. WORK/IWORK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783
12.3.7. IF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784
12.3.8. IF-THEN-ELSE-ENDIF . . . . . . . . . . . . . . . . . . . . . . . . 785
12.3.9. BLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787
12.3.10. CYLINDER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 789
12.3.11. STORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 790
12.3.12. SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 791
12.3.13. INTERPOLATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 792
12.3.14. MULTIPLY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 801
12.3.15. MULTIREG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802
12.3.16. MULTREGP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803
12.3.17. COPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
12.3.18. COPYBOX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808
12.3.19. COPYREG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809
12.3.20. EQUALREG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810
12.3.21. ADD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
12.3.22. ADDREG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812
12.3.23. EQUALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813
12.3.24. MAXVALUE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814
12.3.25. MINVALUE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815
12.3.26. OPERATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 816
12.3.27. OPERATER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818
12.3.28. DEPTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820
12.4. Region section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821
12.4.1. REGIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822
12.4.2. PVTNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823
12.4.3. SATNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 824
12.4.4. SURFNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825
12.4.5. SURFWNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826
12.4.6. LWSLTNUM / LSNUM . . . . . . . . . . . . . . . . . . . . . . . . 827
12.4.7. IMBNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828
12.4.8. MISCNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830
12.4.9. EQLNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831
12.4.10. FIPNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832
12.4.11. FIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833
12.4.12. FIPOWG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835
12.4.13. FIPPATT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836
12.4.14. ROCKNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837

CONTENTS 17
 19.1

12.4.15. COALNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 838

12.4.16. PMANUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
12.4.17. ENDNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840
12.4.18. FLUXNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 841
12.4.19. VISCNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 842
12.4.20. EOSNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843
12.4.21. OPERNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844
12.4.22. MULTNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845
12.4.23. KRNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
12.4.24. KRNUMMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847
12.4.25. IMBNUMMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 848
12.4.26. WH2NUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
12.4.27. WH3NUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850
12.4.28. ZONES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851
12.4.29. TRACKREG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853
12.5. PVT Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854
12.5.1. PROPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854
12.5.2. PVDO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
12.5.3. PVCDO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
12.5.4. PVTO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859
12.5.5. PVTW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 862
12.5.6. PVCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 864
12.5.7. PVDG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
12.5.8. PVTG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 868
12.5.9. PVZG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 870
12.5.10. OVPG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 872
12.5.11. STANDO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 874
12.5.12. STANDG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
12.5.13. RSCONST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876
12.5.14. RSCONSTT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877
12.5.15. RVCONST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 879
12.5.16. RVCONSTT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 880
12.5.17. ROCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 882
12.5.18. RKTRMDIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 884
12.5.19. ROCKTSIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 885
12.5.20. ROCKPAMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887
12.5.21. ROCKTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 889
12.5.22. ROCKTABH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 891
12.5.23. HMMROCKT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895
12.5.24. HMRREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 896
12.5.25. PERMSTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897
12.5.26. TRROCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 898
12.5.27. ROCKAXES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 900

CONTENTS 18
 19.1

12.5.28. ROCKSTRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 901

12.5.29. COHESION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 902
12.5.30. THETA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903
12.5.31. ROCKOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 904
12.5.32. OVERBURD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 906
12.5.33. DENSITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 907
12.5.34. GRAVITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 908
12.5.35. APIGROUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 909
12.5.36. PVTOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 910
12.5.37. DIFFC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 912
12.6. Relative permeabilities and capillary pressures . . . . . . . . . . . . . . . . 913
12.6.1. SWOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914
12.6.2. SGOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 917
12.6.3. COREYWO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
12.6.4. COREYGO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 921
12.6.5. COREYWG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923
12.6.6. COREYWOMOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . 925
12.6.7. COREYGOMOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . 926
12.6.8. LETWO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 927
12.6.9. LETGO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 930
12.6.10. LETWG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933
12.6.11. SLGOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 936
12.6.12. SOF2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938
12.6.13. SWFN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 940
12.6.14. SGFN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 942
12.6.15. SOF3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 944
12.6.16. SGWFN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 946
12.6.17. SOMWAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 948
12.6.18. SOMGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 950
12.6.19. TOLCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 952
12.6.20. STONE1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 953
12.6.21. STONE2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 954
12.6.22. STONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 955
12.6.23. STONEPAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 956
12.6.24. TZONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 957
12.6.25. SCALECRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 958
12.6.26. SWL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 959
12.6.27. SWLPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 960
12.6.28. SGL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 961
12.6.29. SWCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 962
12.6.30. SGCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963
12.6.31. SOWCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 964
12.6.32. SOGCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 965

CONTENTS 19
 19.1

12.6.33. SWU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 966

12.6.34. SGU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 967
12.6.35. ISGL, ISGCR, ISGU, ISWL, ISWLPC, ISWCR, ISWU, ISOGCR,
ISOWCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 968
12.6.36. SCALELIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 969
12.6.37. ENPTVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 970
12.6.38. ENKRVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 972
12.6.39. ENPCVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
12.6.40. ENPTRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974
12.6.41. ENPKTRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 976
12.6.42. ENPCTRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977
12.6.43. ENPTRCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978
12.6.44. ENPKTRCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979
12.6.45. ENPCTRCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 980
12.6.46. LSWL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 981
12.6.47. LSWLPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 982
12.6.48. LSWU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983
12.6.49. LPCW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 984
12.6.50. LSOGCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 985
12.6.51. LSOWCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 986
12.6.52. LSWCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 987
12.6.53. LKRW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988
12.6.54. LKRWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989
12.6.55. LKRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 990
12.6.56. LKRORW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991
12.6.57. LKRORG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 992
12.6.58. KRO, KRORW, KRORG . . . . . . . . . . . . . . . . . . . . . . . . 993
12.6.59. KRW, KRWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 994
12.6.60. KRG, KRGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995
12.6.61. IKRG, IKRGR, IKRW, IKRWR, IKRO, IKRORW, IKRORG . . . . 996
12.6.62. PCW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997
12.6.63. PCG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998
12.6.64. IPCW, IPCG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 999
12.6.65. SWATINIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1000
12.6.66. PPCWMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1002
12.6.67. EHYSTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003
12.6.68. EHYSTRR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1006
12.6.69. DRAINAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1008
12.6.70. HYSTKRW / HYSTKROW / HYSTKRG / HYSTKROG . . . . . . 1009
12.6.71. HYSTKRWR / HYSTKROWR / HYSTKRGR / HYSTKROGR . . . 1012
12.6.72. HYSTPCW / HYSTPCG . . . . . . . . . . . . . . . . . . . . . . . . 1015
12.6.73. HYSTPCWR / HYSTPCGR . . . . . . . . . . . . . . . . . . . . . . 1017
12.6.74. HYSTOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1019

CONTENTS 20
 19.1

12.6.75. HYSTOPTSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021

12.6.76. MISCSTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1022
12.6.77. MISCSTRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1023
12.6.78. MISCSTRR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024
12.6.79. MISCEXP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025
12.6.80. PARACHOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1026
12.6.81. PMISC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1027
12.6.82. MSFN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1028
12.6.83. SDENSITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1030
12.6.84. SGCWMIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1031
12.6.85. SORWMIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1032
12.6.86. TLMIXPAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1033
12.6.87. STOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1034
12.6.88. STOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035
12.6.89. KRSMOOTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1036
12.6.90. LINEAR_ISOPERM . . . . . . . . . . . . . . . . . . . . . . . . . . 1037
12.7. Salts and tracers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1038
12.7.1. SALTPROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1039
12.7.2. SALTTRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1040
12.7.3. SALTNODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041
12.7.4. ADSALNOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1042
12.7.5. ESSNODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1043
12.7.6. PLYVISCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044
12.7.7. BDENSITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1046
12.7.8. PVTWSALT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1047
12.7.9. LSALTFNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048
12.7.10. TRACER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1050
12.7.11. TRACERM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1051
12.7.12. TRACEROPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1052
12.7.13. TRMMULTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1054
12.7.14. TRMMULTT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1056
12.7.15. TRMTEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1057
12.7.16. TRDCY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1058
12.7.17. TRADS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1059
12.8. EOR: Enhanced Oil Recovery . . . . . . . . . . . . . . . . . . . . . . . . . 1060
12.8.1. NPROPANTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1061
12.8.2. PROPANTNAMES . . . . . . . . . . . . . . . . . . . . . . . . . . . 1062
12.8.3. PROPANTTABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . 1063
12.8.4. FLOWFUNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1065
12.8.5. NFLOWFTB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1067
12.8.6. FLOWFNAMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1068
12.8.7. FLOWFTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1069
12.8.8. SOCRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1071

CONTENTS 21
 19.1

12.8.9. SURFADS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1072

12.8.10. SURFST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1073
12.8.11. SURFVISC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1074
12.8.12. SURFCAPD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1075
12.8.13. SURFROCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1076
12.8.14. SURFADDW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1077
12.8.15. SURFDW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1078
12.8.16. SURFSTES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1079
12.8.17. SSWL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1081
12.8.18. SSWCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1082
12.8.19. SSWU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1083
12.8.20. SSOWCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1084
12.8.21. SKRW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1085
12.8.22. SKRWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1086
12.8.23. SKRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1087
12.8.24. SKRORW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1088
12.8.25. PLYVISC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1089
12.8.26. PLYADS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1090
12.8.27. PLYADSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1091
12.8.28. PLYMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1093
12.8.29. PLMIXPAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1094
12.8.30. PLYROCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1095
12.8.31. PLYKRRF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1096
12.8.32. PLYSHEAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1097
12.8.33. PLYSHLOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1099
12.8.34. SHRATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1101
12.8.35. PLYVISCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1102
12.8.36. PLYVSCST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1104
12.8.37. TEMPNODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1106
12.8.38. ALSURFST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1107
12.8.39. ALSURFAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1108
12.8.40. ALPOLADS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1109
12.8.41. ALKADS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1110
12.8.42. ALKROCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1111
12.8.43. STVP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1112
12.8.44. WAGHYSTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1113
12.8.45. WAGHALT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1115
12.9. Coal Bed Methane properties . . . . . . . . . . . . . . . . . . . . . . . . . 1116
12.9.1. DIFFCOAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1116
12.9.2. LANGMUIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1117
12.9.3. LANGMPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1118
12.9.4. LANGMULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1119
12.9.5. MLANG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1120

CONTENTS 22
 19.1

12.9.6. LANGMEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1121

12.9.7. DIFFCBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1123
12.9.8. RESORB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124
12.10. Asphaltene properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1125
12.10.1. ASPP1P . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1125
12.10.2. ASPREWG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1126
12.10.3. ASPP2P . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1127
12.10.4. ASPPW2D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1128
12.10.5. ASPFLRT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1129
12.10.6. ASPLCRT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1130
12.10.7. ASPVISO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1131
12.10.8. ASPDEPO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1132
12.10.9. CATYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1133
12.11. Foam properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1134
12.11.1. FOAMADS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1134
12.11.2. FOAMOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1135
12.11.3. FOAMROCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1136
12.11.4. FOAMDCYW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1137
12.11.5. FOAMDCYO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1138
12.11.6. FOAMMOB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1139
12.11.7. FOAMMOBP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1140
12.11.8. FOAMMOBS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1141
12.12. Residual oil properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1142
12.12.1. SOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1142
12.12.2. SOROPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1143
12.13. Solid phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1144
12.13.1. SOLIDMMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1144
12.13.2. SOLIDMMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1145
12.13.3. SOLIDADS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1146
12.14. Compositional properties . . . . . . . . . . . . . . . . . . . . . . . . . . . 1147
12.14.1. COMPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1148
12.14.2. COMPW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1149
12.14.3. CNAMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1150
12.14.4. DETAILMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1151
12.14.5. DETAILVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1153
12.14.6. EOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1155
12.14.7. EOSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1156
12.14.8. LUMPDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1157
12.14.9. LUMPING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1158
12.14.10. RTEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1159
12.14.11. STCOND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1160
12.14.12. WATERTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1161
12.14.13. ZI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1162

CONTENTS 23
 19.1

12.14.14. COMPVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1163

12.14.15. XMFVP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1165
12.14.16. YMFVP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1166
12.14.17. ZMFVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1167
12.14.18. NEI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1169
12.14.19. KVTABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1170
12.14.20. TCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1171
12.14.21. TCRITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1173
12.14.22. PCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1174
12.14.23. PCRITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1176
12.14.24. VCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1177
12.14.25. VCRITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1179
12.14.26. VCRITVIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1180
12.14.27. ZCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1181
12.14.28. ZCRITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1182
12.14.29. ZCRITVIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1183
12.14.30. MW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1184
12.14.31. MWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1186
12.14.32. MWW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1187
12.14.33. MWWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1188
12.14.34. PREFW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1189
12.14.35. PREFWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1190
12.14.36. DREFW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1191
12.14.37. DREFWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1192
12.14.38. ACF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1193
12.14.39. ACFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1195
12.14.40. BIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1196
12.14.41. BICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1198
12.14.42. OMEGAA / OMEGAB . . . . . . . . . . . . . . . . . . . . . . . . . 1199
12.14.43. OMEGAAS / OMEGABS . . . . . . . . . . . . . . . . . . . . . . . 1200
12.14.44. LBCCOEF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1201
12.14.45. LBCCOEFR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1202
12.14.46. VCOMPACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1203
12.14.47. FACTLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1204
12.14.48. LILIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1205
12.14.49. PRCORR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1206
12.14.50. SSHIFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1207
12.14.51. SSHIFTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1208
12.14.52. VSHIF1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1209
12.14.53. TREFVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1210
12.14.54. EPSCOMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1211
12.14.55. ENKRVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1212
12.14.56. ENPCVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1214

CONTENTS 24
 19.1

12.14.57. ENPTVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1215

12.14.58. DIFFCGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1217
12.14.59. DIFFCOIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1218
12.14.60. DIFFCGO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1219
12.14.61. DIFFCOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1220
12.14.62. VDKRG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1221
12.14.63. VDKRGC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1223
12.14.64. VDKRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1224
12.14.65. PEDERSEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1226
12.14.66. PEDTUNE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1227
12.14.67. PEDTUNER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1229
12.14.68. NCOMPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1230
12.14.69. DNGL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1231
12.14.70. SOLUBILI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1232
12.14.71. RSWVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1233
12.15. Thermal properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1234
12.15.1. CGDTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1235
12.15.2. CGVTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1236
12.15.3. CODTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1237
12.15.4. COVTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1238
12.15.5. CVTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1239
12.15.6. CVTYPES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1240
12.15.7. CCTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1241
12.15.8. CCTYPES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1242
12.15.9. WATDENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1243
12.15.10. THANALB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1244
12.15.11. KVCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1245
12.15.12. KVCRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1247
12.15.13. KVTEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1248
12.15.14. KVTABTn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1249
12.15.15. KVTABLIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1250
12.15.16. KVWI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1252
12.15.17. HEATCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1253
12.15.18. HEATCRT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1254
12.15.19. HEATTCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1255
12.15.20. HEATVAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1257
12.15.21. HEATVAPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1258
12.15.22. THCONR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1259
12.15.23. THCONSF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1260
12.15.24. ROCKT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1261
12.15.25. THCONMIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1263
12.15.26. STHERMX1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1264
12.15.27. STHERMX2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1265

CONTENTS 25
 19.1

12.15.28. SDREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1266

12.15.29. SPREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1267
12.15.30. SCREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1268
12.15.31. STREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1269
12.15.32. THERMEX1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1270
12.15.33. THERMEX2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1271
12.15.34. THERMEX3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1272
12.15.35. PREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1273
12.15.36. PREFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1274
12.15.37. PREFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1275
12.15.38. TREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1276
12.15.39. TREFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1277
12.15.40. TREFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1278
12.15.41. DREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1279
12.15.42. DREFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1280
12.15.43. DREFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1281
12.15.44. VREFW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1282
12.15.45. CREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1283
12.15.46. CREFW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1284
12.15.47. WI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1285
12.15.48. WMFVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1286
12.15.49. WNAMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1287
12.15.50. ZFACTOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1288
12.15.51. ZFACT1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1289
12.15.52. VISCREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1290
12.15.53. WATVISCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1291
12.15.54. OILVISCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1292
12.15.55. OILVISCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1294
12.15.56. OILVINDX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1297
12.15.57. OILVINDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1298
12.15.58. GASVISCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1300
12.15.59. GASVISCF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1301
12.15.60. REACRATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1302
12.15.61. REACACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1303
12.15.62. REACCORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1304
12.15.63. REACLIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1305
12.15.64. REACCONC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1307
12.15.65. REACPORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1308
12.15.66. STOPROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1309
12.15.67. STOREAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1310
12.15.68. REACPHA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1311
12.15.69. REACSORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1313
12.15.70. REACENTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1314

CONTENTS 26
 19.1

12.15.71. EQLDREAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1315

12.15.72. EQLDKVCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1317
12.15.73. SPECHA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1318
12.15.74. SPECHB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1319
12.15.75. SPECHC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1320
12.15.76. SPECHD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1321
12.15.77. SPECHG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1322
12.15.78. SPECHH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1323
12.15.79. SPECHI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1324
12.15.80. SPECHJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1325
12.15.81. HEATVAPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1326
12.15.82. SPECHS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1327
12.15.83. SPECHT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1328
12.15.84. TEMPVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1329
12.15.85. ENPTVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1330
12.15.86. ENKRVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1332
12.15.87. ENPCVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1333
12.15.88. ROCKV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1334
12.15.89. THSVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1335
12.15.90. THWVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1336
12.15.91. SPECROCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1337
12.15.92. SPECHEAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1338
12.15.93. CALVAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1339
12.15.94. CALVALR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1340
12.16. Initialization section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1341
12.16.1. SOLUTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1342
12.16.2. EQUIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1343
12.16.3. RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1346
12.16.4. RESTARTDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1349
12.16.5. RPTRST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1351
12.16.6. OUTSOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1356
12.16.7. RSVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1357
12.16.8. PBVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1358
12.16.9. RVVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1359
12.16.10. PDVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1360
12.16.11. THPRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1361
12.16.12. PRESSURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1363
12.16.13. PRVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1365
12.16.14. SWAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1366
12.16.15. SGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1368
12.16.16. SOIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1370
12.16.17. SSOLID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1372
12.16.18. APIVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1373

CONTENTS 27
 19.1

12.16.19. OILAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1374

12.16.20. SMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1375
12.16.21. XMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1376
12.16.22. YMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1377
12.16.23. ZMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1378
12.16.24. FIELDSEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1380
12.16.25. FIPSEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1382
12.16.26. GPTABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1384
12.16.27. GPTABLEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1386
12.16.28. GPTABLE3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1388
12.16.29. RECOVERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1390
12.16.30. DENSTRMIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1391
12.16.31. SEPDEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1392
12.16.32. TEMPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1394
12.16.33. RTEMPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1395
12.16.34. RTEMPVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1396
12.16.35. WTEMPDEF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1397
12.16.36. PBUB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1398
12.16.37. RS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1400
12.16.38. RV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1402
12.16.39. PDEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1404
12.16.40. DATUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1405
12.16.41. DATUMR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1406
12.16.42. DATUMRX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1407
12.16.43. TBLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1408
12.16.44. TNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1410
12.16.45. TVDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1412
12.16.46. ROCKSALT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1414
12.16.47. SALT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1415
12.16.48. SALTVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1416
12.16.49. SRSALT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1417
12.16.50. SURF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1418
12.16.51. SPOLY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1419
12.16.52. GASCONC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1420
12.16.53. GASSATC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1421
12.16.54. GASCCMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1422
12.16.55. RPTMAPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1423
12.16.56. RSW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1425
12.16.57. SFOAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1426
12.16.58. SOILR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1427
12.16.59. ROMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1428
12.16.60. WMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1429
12.16.61. RPTRSTD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1430

CONTENTS 28
 19.1

12.16.62. RPTRSTT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1431

12.16.63. RPTRSTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1432
12.16.64. RPTMAPD/RPTGRAPHD . . . . . . . . . . . . . . . . . . . . . . . 1433
12.16.65. RPTMAPT/RPTGRAPHT . . . . . . . . . . . . . . . . . . . . . . . 1435
12.16.66. RPTMAPL/RPTGRAPHL . . . . . . . . . . . . . . . . . . . . . . . 1437
12.17. Inflow from aquifer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1438
12.17.1. AQUDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1439
12.17.2. AQUFLUX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1441
12.17.3. AQUCHWAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1442
12.17.4. AQUFET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1444
12.17.5. AQUOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1446
12.17.6. AQUFETP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1448
12.17.7. AQSTREAW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1450
12.17.8. AQANTRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1451
12.17.9. AQUCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1452
12.17.10. AQUTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1454
12.17.11. AQUANCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1455
12.17.12. AQANCONL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1457
12.17.13. AQUNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1459
12.17.14. AQUCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1461
12.17.15. AQUGP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1464
12.17.16. HMMLCTAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1467
12.17.17. HMMLFTAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1468
12.18. Data output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1469
12.18.1. SUMMARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1469
12.18.2. RPTONLY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1485
12.18.3. RPTONLYO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1486
12.18.4. SEPARATE / RUNSUM . . . . . . . . . . . . . . . . . . . . . . . . 1487
12.19. Schedule section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1488
12.19.1. SCHEDULE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1490
12.19.2. WELSOMIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1491
12.19.3. WELSPECS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1492
12.19.4. WELSPECL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1495
12.19.5. WELLSPEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1498
12.19.6. COMPDAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1499
12.19.7. COMPDATL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1502
12.19.8. COMPDATM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1505
12.19.9. WELLTRACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1506
12.19.10. COMPDATMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1508
12.19.11. WELSEGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1513
12.19.12. WSEGINIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1517
12.19.13. WSEGLINK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1518
12.19.14. WSEGTABL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1520

CONTENTS 29
 19.1

12.19.15. WSEGVALV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1522

12.19.16. WSEGAICD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1524
12.19.17. WSEGSICD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1528
12.19.18. WSEGEXSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1534
12.19.19. WSEGFLIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1536
12.19.20. WSEGFMOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1538
12.19.21. WSEGDFPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1541
12.19.22. WSEGSEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1544
12.19.23. WSEGPULL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1546
12.19.24. WFRICTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1549
12.19.25. WFRICTNL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1552
12.19.26. WFRICSEG / WFRICSGL . . . . . . . . . . . . . . . . . . . . . . . 1554
12.19.27. COMPSEGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1556
12.19.28. COMPSEGL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1559
12.19.29. COMPLUMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1560
12.19.30. COMPLMPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1562
12.19.31. COMPORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1564
12.19.32. COMPINJK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1566
12.19.33. WLIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1568
12.19.34. WLISTDYN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1570
12.19.35. WPIMULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1572
12.19.36. WPIMULTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1575
12.19.37. WPITAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1578
12.19.38. PIMULTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1579
12.19.39. COMPRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1580
12.19.40. FBHPDEF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1582
12.19.41. WINJMULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1583
12.19.42. WCONPROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1585
12.19.43. WCONHIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1589
12.19.44. WCONINJE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1592
12.19.45. WCONINJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1596
12.19.46. WCONINJP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1598
12.19.47. WCONINJH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1600
12.19.48. WELLINJE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1603
12.19.49. GRUPINJE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1607
12.19.50. WCYCLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1610
12.19.51. WELLWAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1612
12.19.52. WWAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1614
12.19.53. WHISTCTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1619
12.19.54. WCUTBACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1620
12.19.55. WCUTBACKX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1623
12.19.56. GCUTBACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1625
12.19.57. WBHGLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1627

CONTENTS 30
 19.1

12.19.58. WTMULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1629

12.19.59. WTADD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1631
12.19.60. WELTARG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1632
12.19.61. WELLTARG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1635
12.19.62. WELCNTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1636
12.19.63. GRUPTARG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1638
12.19.64. WELPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1639
12.19.65. VFPINJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1640
12.19.66. VFPPROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1643
12.19.67. VFPCHK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1647
12.19.68. VFPCHECK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1648
12.19.69. VFPTABL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1649
12.19.70. WVFPEXP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1650
12.19.71. VFPCORR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1652
12.19.72. WELLTCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1655
12.19.73. WELLTCBT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1656
12.19.74. WECON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1657
12.19.75. WECONX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1661
12.19.76. GECONX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1663
12.19.77. WECONCMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1665
12.19.78. WGORPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1666
12.19.79. WELLLIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1667
12.19.80. CECON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1668
12.19.81. WECONINJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1670
12.19.82. WECONINJX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1671
12.19.83. WEFAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1673
12.19.84. GEFAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1674
12.19.85. WORKTHP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1675
12.19.86. GCONPROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1676
12.19.87. GUIDERAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1680
12.19.88. WREGROUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1683
12.19.89. GCONPRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1685
12.19.90. GPMAINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1688
12.19.91. GPMAINT3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1691
12.19.92. PRIORITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1695
12.19.93. WELPRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1697
12.19.94. WGRUPCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1699
12.19.95. GCONINJE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1701
12.19.96. GCONSUMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1704
12.19.97. GSATPROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1705
12.19.98. GSATINJE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1707
12.19.99. GSATCOMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1709
12.19.100. GRUPTREE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1710

CONTENTS 31
 19.1

12.19.101. DGRDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1711

12.19.102. BRANPROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1712
12.19.103. NODEPROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1714
12.19.104. NETCHOKE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1717
12.19.105. NCONSUMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1719
12.19.106. GNETDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1720
12.19.107. GNETINJE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1722
12.19.108. NETCOMPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1724
12.19.109. COMPOFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1727
12.19.110. NWATREM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1728
12.19.111. NGASREM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1729
12.19.112. NOILREM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1731
12.19.113. GNETPUMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1732
12.19.114. GRUPNET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1733
12.19.115. DRSDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1735
12.19.116. VAPPARS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1736
12.19.117. DRSDTVP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1738
12.19.118. DRSDTVPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1739
12.19.119. DRVDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1740
12.19.120. COMPENSATION . . . . . . . . . . . . . . . . . . . . . . . . . . . 1741
12.19.121. GECON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1742
12.19.122. GRUPLIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1744
12.19.123. WELDRAW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1745
12.19.124. DATES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1748
12.19.125. TSTEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1751
12.19.126. NEXTSTEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1752
12.19.127. WELLSHUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1753
12.19.128. WELOPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1754
12.19.129. WELOPENL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1756
12.19.130. WELLOPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1758
12.19.131. MATCORR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1759
12.19.132. NETBALAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1760
12.19.133. WSEGITER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1761
12.19.134. TUNING / TUNINGDP / TUNINGL / TUNINGS . . . . . . . . . . 1762
12.19.135. TIGHTENP / TSCRIT . . . . . . . . . . . . . . . . . . . . . . . . . 1763
12.19.136. ZIPPY2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1764
12.19.137. NSTACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1765
12.19.138. LGRLOCK / LGRFREE . . . . . . . . . . . . . . . . . . . . . . . . 1766
12.19.139. CVCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1767
12.19.140. RUNCTRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1768
12.19.141. MULTSIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1780
12.19.142. MULTSIGV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1781
12.19.143. WFRAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1782

CONTENTS 32
 19.1

12.19.144. WFRACL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1785

12.19.145. WFRACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1788
12.19.146. WFRACPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1797
12.19.147. FRACTURE_STAGE . . . . . . . . . . . . . . . . . . . . . . . . . . 1801
12.19.148. COMPFRAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1802
12.19.149. COMPFRACL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1805
12.19.150. WPIFUNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1808
12.19.151. WSKFUNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1810
12.19.152. WBHZONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1812
12.19.153. WLIMTOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1814
12.19.154. SEPVALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1815
12.19.155. GSEPCOND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1817
12.19.156. SEPCOND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1818
12.19.157. WSEPCOND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1820
12.19.158. ACTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1821
12.19.159. ACTIONG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1823
12.19.160. ACTIONR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1826
12.19.161. ACTIONW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1828
12.19.162. ACTIONX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1831
12.19.163. DELAYACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1837
12.19.164. ENDACTIO / ENDACTION . . . . . . . . . . . . . . . . . . . . . . 1839
12.19.165. UDQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1840
12.19.166. UDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1846
12.19.167. ACTIONC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1849
12.19.168. WDFAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1854
12.19.169. WDFACCOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1855
12.19.170. WDFACCORL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1857
12.19.171. WTRACER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1858
12.19.172. WSURFACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1859
12.19.173. WALKALIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1860
12.19.174. WPOLYMER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1861
12.19.175. WSALT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1862
12.19.176. WTEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1863
12.19.177. WHTEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1864
12.19.178. WINJTEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1865
12.19.179. WINJWAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1866
12.19.180. WINJW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1867
12.19.181. HEATER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1868
12.19.182. HEATERL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1869
12.19.183. WTEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1870
12.19.184. WELLSTRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1872
12.19.185. WELLSTRW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1873
12.19.186. COMPMOBI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1874

CONTENTS 33
 19.1

12.19.187. COMPMBIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1875

12.19.188. WINJMIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1876
12.19.189. WINJORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1878
12.19.190. WINJGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1880
12.19.191. GINJGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1882
12.19.192. GADVANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1884
12.19.193. GRUPSALE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1885
12.19.194. GCONSALE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1886
12.19.195. GRUPFUEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1888
12.19.196. WTAKEGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1889
12.19.197. WAVAILIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1890
12.19.198. SWINGFAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1891
12.19.199. GSWINGF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1893
12.19.200. GDCQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1895
12.19.201. GASYEAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1897
12.19.202. GASPERIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1900
12.19.203. DCQDEFN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1903
12.19.204. GDCQECON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1904
12.19.205. GASBEGIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1905
12.19.206. GASEND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1907
12.19.207. GASMONTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1908
12.19.208. WGASPROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1909
12.19.209. GASFTARG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1910
12.19.210. GASFDECR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1911
12.19.211. GASFCOMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1912
12.19.212. WVFPDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1913
12.19.213. PICOND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1914
12.19.214. WPAVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1916
12.19.215. WPAVEDEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1921
12.19.216. WRFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1922
12.19.217. WRFTPLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1923
12.19.218. SKIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1925
12.19.219. SKIPREST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1926
12.19.220. SKIP100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1927
12.19.221. SKIP300 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1928
12.19.222. SKIPTNAV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1929
12.19.223. SKIPOFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1930
12.19.224. SKIPON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1932
12.19.225. ENDSKIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1933
12.19.226. DRILPRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1934
12.19.227. WDRILPRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1936
12.19.228. WDRILTIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1938
12.19.229. QDRILL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1939

CONTENTS 34
 19.1

12.19.230. GDRILPOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1940

12.19.231. WDRILRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1941
12.19.232. WORKLIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1942
12.19.233. GRUPRIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1943
12.19.234. NUPCOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1945
12.19.235. WELLOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1946
12.19.236. GCONTOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1947
12.19.237. WLIFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1948
12.19.238. PRORDER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1951
12.19.239. LIFTOPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1953
12.19.240. GLIFTLIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1954
12.19.241. GLIFTOPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1955
12.19.242. WLIFTOPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1956
12.19.243. OPTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1958
12.19.244. OPTIONS3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1961
12.19.245. COMPVAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1962
12.19.246. COMPVALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1963
12.19.247. WNETDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1964
12.19.248. WELLPROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1965
12.19.249. GRUPPROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1968
12.19.250. WELLCOMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1970
12.19.251. TRANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1972
12.19.252. SCDPTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1973
12.19.253. SCDPTRAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1974
12.19.254. SCDATAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1975
12.19.255. WSCTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1976
12.19.256. WSEGCNTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1977
12.19.257. PSEUPRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1978
12.19.258. GWRATMUL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1979
12.19.259. APILIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1980
12.19.260. AUTOSAVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1981
12.19.261. WELLGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1982
12.19.262. SLAVES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1984
12.19.263. GRUPMAST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1985
12.19.264. GRUPSLAV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1987
12.19.265. CSKIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1989
12.19.266. WFOAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1990
12.19.267. WELLINCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1991
12.19.268. WELLDATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1992
12.19.269. WELLBRANCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1994
12.19.270. AIMPVI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1996
12.19.271. CALTRAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1997
12.19.272. LGRON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1998

CONTENTS 35
 19.1

12.19.273. LGROFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1999

12.19.274. GMDISBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2000
12.19.275. GMPSTBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2002
12.19.276. WLOGCALC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2004

13. Keywords for formats tN, IM, ST, GE 2005

13.1. Data entry system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2006
13.1.1. MATRIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2006
13.1.2. FRACTURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2007
13.1.3. CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2008
13.1.4. IVAR / JVAR / KVAR . . . . . . . . . . . . . . . . . . . . . . . . . 2009
13.1.5. IJK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2010
13.1.6. BG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2011
13.1.7. FZ / NFZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2012
13.1.8. EQUALSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2013
13.2. Input/Output Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2014
13.2.1. TITLE1 / TITLE2 / TITLE3 . . . . . . . . . . . . . . . . . . . . . . 2014
13.2.2. INUNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2015
13.2.3. RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2016
13.2.4. RESDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2017
13.2.5. FILENAMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2018
13.2.6. INCLUDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2019
13.3. Reservoir description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2020
13.3.1. GRID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2020
13.3.2. DI / DJ / DK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2021
13.3.3. ZCORN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2022
13.3.4. COORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2023
13.3.5. BLOCKGROUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2024
13.3.6. DUALPOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2025
13.3.7. SHAPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2026
13.3.8. DIFRAC / DJFRAC / DKFRAC . . . . . . . . . . . . . . . . . . . . 2027
13.3.9. NULL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2028
13.3.10. POR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2029
13.3.11. PERMI / PERMJ / PERMK . . . . . . . . . . . . . . . . . . . . . . 2030
13.3.12. NETGROSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2031
13.3.13. PINCHOUTARRAY . . . . . . . . . . . . . . . . . . . . . . . . . . 2032
13.3.14. VOLMOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2033
13.3.15. NETPAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2034
13.3.16. AQLEAK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2035
13.3.17. AQMETHOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2036
13.3.18. AQVISC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2037
13.3.19. AQPROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2038
13.3.20. AQUIFER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2039
13.3.21. AQFUNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2040

CONTENTS 36
 19.1

13.3.22. DUALPERM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2041

13.3.23. CORNERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2042
13.3.24. CTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2044
13.3.25. CROCKTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2045
13.3.26. CPRPOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2046
13.3.27. CCPOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2048
13.3.28. CROCKTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2049
13.3.29. CROCKTABH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2050
13.3.30. DEPLETION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2054
13.3.31. TRANSI / TRANSJ / TRANSK . . . . . . . . . . . . . . . . . . . . 2055
13.3.32. TRANLI / TRANLJ / TRANLK . . . . . . . . . . . . . . . . . . . . 2056
13.3.33. TRANSMULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2057
13.3.34. TRANSF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2058
13.3.35. FRFRAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2059
13.3.36. FORMINFRAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2060
13.3.37. SECTORARRAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2061
13.3.38. ISECTOR / SECTORNAMES . . . . . . . . . . . . . . . . . . . . . 2062
13.3.39. DEPTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2063
13.3.40. DTOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2064
13.3.41. PVCUTOFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2065
13.3.42. REFINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2066
13.3.43. SCONNECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2068
13.3.44. PLNRFRAC_TEMPLATE . . . . . . . . . . . . . . . . . . . . . . . 2069
13.3.45. PLNRFRAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2072
13.3.46. VAMOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2073
13.3.47. VATYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2075
13.4. Other Reservoir Properties . . . . . . . . . . . . . . . . . . . . . . . . . . 2076
13.4.1. ROCKTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2076
13.4.2. THTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2078
13.4.3. ROCKCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2079
13.4.4. PRPOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2080
13.4.5. CPOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2082
13.4.6. CTPOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2084
13.4.7. CPTPOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2085
13.4.8. THCONR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2086
13.4.9. THCONW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2087
13.4.10. THCONO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2088
13.4.11. THCONG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2089
13.4.12. THCONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2090
13.4.13. THCONMIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2091
13.4.14. RXEQFOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2092
13.4.15. RXEQBAK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2094
13.4.16. RXEQBASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2096

CONTENTS 37
 19.1

13.4.17. HLOSST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2097

13.4.18. HLOSSTDIFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2098
13.4.19. HLOSSPROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2099
13.4.20. CPORPD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2100
13.4.21. PORMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2101
13.4.22. PORFORM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2102
13.4.23. DILATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2103
13.5. Component properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2105
13.5.1. K_SURF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2105
13.5.2. SURFLASH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2106
13.5.3. MOLVOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2107
13.5.4. MODEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2108
13.5.5. NC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2110
13.5.6. HCFLAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2111
13.5.7. PVC3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2112
13.5.8. CRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2113
13.5.9. PVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2114
13.5.10. PVTCOND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2116
13.5.11. DIFLIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2118
13.5.12. EGUST / BGUST / ZGUST . . . . . . . . . . . . . . . . . . . . . . 2120
13.5.13. DENSITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2121
13.5.14. AQUEOUS-DENSITY . . . . . . . . . . . . . . . . . . . . . . . . . 2122
13.5.15. SALINITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2123
13.5.16. GRAVITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2124
13.5.17. PVTAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2125
13.5.18. APIGRAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2126
13.5.19. BOTAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2128
13.5.20. VOTAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2130
13.5.21. BWI / CW / REFPW / CVW / VWI . . . . . . . . . . . . . . . . . . 2132
13.5.22. RHOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2133
13.5.23. PTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2134
13.5.24. COMPNAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2135
13.5.25. PRSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2136
13.5.26. TEMR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2137
13.5.27. PSURF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2138
13.5.28. TSURF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2139
13.5.29. MOLDEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2140
13.5.30. MASSDEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2141
13.5.31. CP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2142
13.5.32. CT1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2143
13.5.33. CT2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2144
13.5.34. CPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2145
13.5.35. PCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2146

CONTENTS 38
 19.1

13.5.36. TCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2147

13.5.37. SOLID_DEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2148
13.5.38. SOLID_CP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2149
13.5.39. KVTABLIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2150
13.5.40. KVTABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2151
13.5.41. KV1 / KV2 / KV3 / KV4 / KV5 . . . . . . . . . . . . . . . . . . . . 2152
13.5.42. CPL1 / CPL2 / CPL3 / CPL4 . . . . . . . . . . . . . . . . . . . . . . 2153
13.5.43. CPG1 / CPG2 / CPG3 / CPG4 . . . . . . . . . . . . . . . . . . . . . 2154
13.5.44. HVAPR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2155
13.5.45. HVR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2156
13.5.46. EV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2157
13.5.47. STOREAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2158
13.5.48. STOPROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2159
13.5.49. FREQFAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2160
13.5.50. FREQFACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2161
13.5.51. EACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2162
13.5.52. EACT_TAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2163
13.5.53. RENTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2164
13.5.54. RORDER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2165
13.5.55. RPHASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2166
13.5.56. RTEMUPR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2167
13.5.57. RTEMLOWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2168
13.5.58. RXCRITCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2169
13.5.59. O2PP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2170
13.5.60. VSTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2171
13.5.61. VISCTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2172
13.5.62. VISCOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2173
13.5.63. VISVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2174
13.5.64. VISCOEFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2175
13.5.65. MIXVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2176
13.5.66. AVISC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2177
13.5.67. BVISC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2178
13.5.68. VISCTABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2179
13.5.69. VSMIXCOMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2181
13.5.70. VSMIXENDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2182
13.5.71. VSMIXFUNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2183
13.5.72. AVG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2184
13.5.73. BVG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2185
13.5.74. CMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2186
13.5.75. GASD-ZCOEF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2187
13.5.76. GASLIQKV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2188
13.5.77. COT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2189
13.5.78. CO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2190

CONTENTS 39
 19.1

13.5.79. BOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2191

13.5.80. CVO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2192
13.5.81. VOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2193
13.5.82. IDEALGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2194
13.5.83. EOSSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2195
13.5.84. EOSTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2196
13.5.85. BIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2197
13.5.86. PCHOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2198
13.5.87. AC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2199
13.5.88. OMEGA / OMEGB . . . . . . . . . . . . . . . . . . . . . . . . . . . 2200
13.5.89. VSHIFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2201
13.5.90. VSHIF1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2202
13.5.91. TREFVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2203
13.5.92. VGUST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2204
13.5.93. PADSORP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2205
13.5.94. PPERM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2206
13.5.95. PMIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2207
13.5.96. PREFCONC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2208
13.5.97. PVISC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2209
13.5.98. INCOMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2210
13.5.99. DIFFUSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2211
13.6. Rock-Fluid data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2213
13.6.1. ROCKFLUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2213
13.6.2. RPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2214
13.6.3. KROIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2215
13.6.4. KROGCG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2216
13.6.5. SWT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2217
13.6.6. SLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2219
13.6.7. SGT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2221
13.6.8. JFUNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2223
13.6.9. SRFTNW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2224
13.6.10. SRFTNG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2225
13.6.11. RTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2226
13.6.12. KRTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2227
13.6.13. KRTEMTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2228
13.6.14. SWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2230
13.6.15. BSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2231
13.6.16. SWCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2232
13.6.17. BSWCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2233
13.6.18. SOIRW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2234
13.6.19. BSOIRW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2235
13.6.20. SGCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2236
13.6.21. BSGCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2237

CONTENTS 40
 19.1

13.6.22. SGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2238

13.6.23. BSGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2239
13.6.24. SOIRG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2240
13.6.25. BSOIRG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2241
13.6.26. SORW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2242
13.6.27. BSORW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2243
13.6.28. SORG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2244
13.6.29. BSORG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2245
13.6.30. KRWIRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2246
13.6.31. BKRWIRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2247
13.6.32. KRGCW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2248
13.6.33. BKRGCW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2249
13.6.34. KROCW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2250
13.6.35. BKROCW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2251
13.6.36. PCGEND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2252
13.6.37. BPCGMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2253
13.6.38. PCWEND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2254
13.6.39. BPCWMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2255
13.6.40. EPSPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2256
13.6.41. EPSPCG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2257
13.6.42. SWTI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2258
13.6.43. HYSKRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2260
13.6.44. SORMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2262
13.6.45. HYSKRW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2263
13.6.46. HYSKRG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2265
13.6.47. HYSKROW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2266
13.6.48. HYSKROG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2268
13.6.49. HYS_KRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2269
13.6.50. HYS_KRG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2272
13.6.51. HYS_PCOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2274
13.6.52. HYS_PCOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2275
13.6.53. HYS_LEVEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2276
13.6.54. SORM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2277
13.6.55. DAMP-PCOW-TROIL . . . . . . . . . . . . . . . . . . . . . . . . . 2279
13.6.56. PTHRESHI / PTHRESHJ / PTHRESHK . . . . . . . . . . . . . . . 2280
13.6.57. ADGMAXC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2281
13.6.58. ADGCSTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2282
13.6.59. COAL-DIF-COMP . . . . . . . . . . . . . . . . . . . . . . . . . . . 2283
13.6.60. COAL-DIF-TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2284
13.7. Initial conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2285
13.7.1. INITIAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2285
13.7.2. VERTICAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2286
13.7.3. USER_INPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2287

CONTENTS 41
 19.1

13.7.4. SWINIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2288

13.7.5. SWNEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2289
13.7.6. SONEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2290
13.7.7. PB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2291
13.7.8. DATUMDEPTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2292
13.7.9. GASZONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2293
13.7.10. INITREGION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2294
13.7.11. INTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2295
13.7.12. REFPRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2296
13.7.13. REFDEPTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2297
13.7.14. DWOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2298
13.7.15. DGOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2299
13.7.16. WOC_SW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2300
13.7.17. SO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2301
13.7.18. SG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2302
13.7.19. SW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2303
13.7.20. SAT_ADJUST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2304
13.7.21. API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2305
13.7.22. APIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2306
13.7.23. PRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2307
13.7.24. TEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2308
13.7.25. CONC_SLD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2309
13.7.26. MFRAC_OIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2310
13.7.27. MFRAC_GAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2311
13.7.28. PBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2312
13.7.29. SEPARATOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2313
13.8. Numerical methods control . . . . . . . . . . . . . . . . . . . . . . . . . . 2316
13.8.1. NUMERICAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2316
13.8.2. TFORM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2317
13.8.3. ISOTHERMAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2318
13.8.4. MINTEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2319
13.8.5. MAXTEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2320
13.8.6. RELAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2321
13.8.7. SOLVER / PNTHRDS . . . . . . . . . . . . . . . . . . . . . . . . . 2322
13.9. Well and recurrent data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2323
13.9.1. RUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2323
13.9.2. STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2324
13.9.3. DATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2325
13.9.4. TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2326
13.9.5. GROUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2327
13.9.6. WELL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2330
13.9.7. PRODUCER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2331
13.9.8. INJECTOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2332

CONTENTS 42
 19.1

13.9.9. BHPDEPTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2333

13.9.10. GEOMETRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2334
13.9.11. PERF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2336
13.9.12. PERFV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2340
13.9.13. LAYERXYZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2343
13.9.14. KRPERF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2345
13.9.15. SETPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2347
13.9.16. WELGEO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2349
13.9.17. SHUTIN / OPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2350
13.9.18. WLISTSHUT / WELISTOPEN . . . . . . . . . . . . . . . . . . . . 2351
13.9.19. DRILLQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2352
13.9.20. MODELSHUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2353
13.9.21. XFLOW-MODEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2354
13.9.22. ON-TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2355
13.9.23. OPERATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2356
13.9.24. OPERATE-HIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2359
13.9.25. ALTER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2361
13.9.26. ALTER-HIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2362
13.9.27. MONITOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2364
13.9.28. TARGET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2366
13.9.29. WTINCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2368
13.9.30. WTMULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2370
13.9.31. GCONP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2372
13.9.32. GCONI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2374
13.9.33. GPRODGROUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2376
13.9.34. GCONM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2377
13.9.35. WELSEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2379
13.9.36. DENSTR-MIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2380
13.9.37. PLANT-TABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2382
13.9.38. PTUBE1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2384
13.9.39. PWELLBORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2387
13.9.40. PHWELLBORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2388
13.9.41. GLIFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2390
13.9.42. GLOPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2391
13.9.43. GLCONTROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2392
13.9.44. LAYER-CTRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2393
13.9.45. TMPSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2395
13.9.46. HEATR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2396
13.9.47. UHTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2397
13.9.48. TINJW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2398
13.9.49. QUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2399
13.9.50. PINJW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2400
13.9.51. HTWELL / HTWRATE / HTWRATEPL / HTWTEMP / HTWI . . . 2401

CONTENTS 43
 19.1

13.9.52. ALTERCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2402

13.9.53. TRIGGER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2403

14. Keywords for formats tN, MO 2408

14.1. INPUt Data Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2409
14.1.1. INPUt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2409
14.1.2. TITLe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2410
14.1.3. PRINt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2411
14.1.4. UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2412
14.1.5. IDATe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2413
14.1.6. SDATe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2414
14.1.7. CNAMe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2415
14.1.8. IMPLicit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2416
14.1.9. INCLude . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2417
14.1.10. SCMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2418
14.1.11. DPORo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2419
14.1.12. EPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2420
14.1.13. EPSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2421
14.1.14. DWPW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2422
14.1.15. OPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2423
14.1.16. ETUNe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2424
14.1.17. GPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2425
14.1.18. MPGP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2426
14.1.19. RG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2427
14.1.20. THER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2428
14.2. FLUId Data Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2429
14.2.1. FLUId . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2429
14.2.2. WATR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2430
14.2.3. BASIc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2431
14.2.4. TEMPerature (FLUI) . . . . . . . . . . . . . . . . . . . . . . . . . . 2432
14.2.5. OPVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2433
14.2.6. GPVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2434
14.2.7. OPVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2435
14.2.8. OMGA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2436
14.2.9. OMGB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2437
14.2.10. VOLU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2438
14.2.11. KVSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2439
14.2.12. KVPX / KVPY / KVPZ . . . . . . . . . . . . . . . . . . . . . . . . 2440
14.2.13. SDEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2441
14.2.14. EQUA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2442
14.2.15. VCOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2443
14.2.16. F(DE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2444
14.2.17. INTE (FLUID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2445
14.2.18. PROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2446

CONTENTS 44
 19.1

14.2.19. TRAC (FLUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2447

14.2.20. UOIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2448
14.2.21. UGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2449
14.2.22. UWAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2450
14.2.23. UROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2451
14.2.24. THCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2452
14.2.25. THCG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2453
14.2.26. THCW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2454
14.2.27. THCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2455
14.2.28. OVVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2456
14.2.29. GVVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2457
14.2.30. WVVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2458
14.2.31. OVPG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2459
14.2.32. SOLU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2460
14.2.33. VCVI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2461
14.2.34. ZCOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2462
14.3. RELAtive Permeability Data Section . . . . . . . . . . . . . . . . . . . . . 2463
14.3.1. RELA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2463
14.3.2. WETT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2464
14.3.3. KRWO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2465
14.3.4. KRGO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2466
14.3.5. TFUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2467
14.4. GRID Data Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2468
14.4.1. GRID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2468
14.4.2. VERT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2469
14.4.3. HORI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2470
14.4.4. SIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2471
14.4.5. DATUm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2472
14.4.6. X-DIrection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2473
14.4.7. Y-DIrection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2474
14.4.8. DEPTh / ZGRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2475
14.4.9. THICkness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2476
14.4.10. POROsity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2477
14.4.11. MINPv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2478
14.4.12. K_X / K_Y / K_Z (KX / KY / KZ, PERMX / PERMY / PERMZ) . . 2480
14.4.13. CROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2481
14.4.14. REFE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2482
14.4.15. ACTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2483
14.4.16. COORd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2484
14.4.17. FIPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2485
14.4.18. SATNum / ROCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2486
14.4.19. AQCD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2487
14.4.20. CONS (GRID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2488

CONTENTS 45
 19.1

14.4.21. DEFI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2489

14.4.22. DPSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2490
14.4.23. FSAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2491
14.4.24. FSWA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2492
14.4.25. FSWL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2493
14.4.26. FKPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2494
14.4.27. FPVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2495
14.4.28. PVTNum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2496
14.4.29. DZMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2497
14.4.30. EQUI / EQLN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2498
14.4.31. F(PO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2499
14.4.32. FAUL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2500
14.4.33. FMUL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2501
14.4.34. FCRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2502
14.4.35. FKX / FKY / FKZ . . . . . . . . . . . . . . . . . . . . . . . . . . . 2503
14.4.36. FMLX / FMLY / FMLZ . . . . . . . . . . . . . . . . . . . . . . . . 2504
14.4.37. FEQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2505
14.4.38. FPOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2506
14.4.39. FREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2507
14.4.40. IEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2508
14.4.41. INTE (GRID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2509
14.4.42. KPTA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2511
14.4.43. LAYE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2512
14.4.44. LEVJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2513
14.4.45. LGRD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2514
14.4.46. MINDznet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2515
14.4.47. MODI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2516
14.4.48. MULX / MULY / MULZ (MX / MY / MZ, M_X / M_Y / M_Z, M-X
/ M-Y / M-Z, MULTX / MULTY / MULTZ) . . . . . . . . . . . . . 2518
14.4.49. PINCh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2519
14.4.50. PORV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2520
14.4.51. PVOL / RVOL / PVR . . . . . . . . . . . . . . . . . . . . . . . . . . 2521
14.4.52. T_X / T_Y / T_Z (TX / TY / TZ, T-X / T-Y / T-Z) . . . . . . . . . . 2523
14.4.53. VARI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2525
14.4.54. NNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2526
14.4.55. NTG / NTOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2527
14.4.56. REPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2528
14.4.57. SGCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2529
14.4.58. SGL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2530
14.4.59. SGU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2531
14.4.60. SOGCr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2532
14.4.61. SOWCr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2533
14.4.62. SWU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2534

CONTENTS 46
 19.1

14.4.63. SWL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2535

14.4.64. SWCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2536
14.4.65. XKRG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2537
14.4.66. XKRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2538
14.4.67. XKRW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2539
14.4.68. XPCG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2540
14.4.69. XPCW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2541
14.4.70. YKRW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2542
14.4.71. ZCORn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2543
14.4.72. ZVAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2544
14.4.73. TSUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2545
14.5. INIT Data Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2546
14.5.1. INIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2546
14.5.2. EQUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2547
14.5.3. CONS (INIT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2548
14.5.4. GOCX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2550
14.5.5. GOCY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2551
14.5.6. PBVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2552
14.5.7. RSVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2553
14.5.8. RVVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2554
14.5.9. PCSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2555
14.5.10. SEPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2556
14.5.11. AQCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2557
14.5.12. AQCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2558
14.5.13. AQUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2560
14.5.14. AQFE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2561
14.5.15. AQUW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2562
14.5.16. AQWO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2563
14.5.17. RHAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2564
14.6. RECUrrent Data Section . . . . . . . . . . . . . . . . . . . . . . . . . . . 2565
14.6.1. RECU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2565
14.6.2. RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2566
14.6.3. EFILe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2567
14.6.4. TFIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2569
14.6.5. ETAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2571
14.6.6. TTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2576
14.6.7. ENDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2577
14.6.8. ENDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2578
14.6.9. HFILe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2579
14.6.10. HTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2581
14.6.11. ENDH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2582
14.6.12. EFORm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2583
14.6.13. HFORm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2585

CONTENTS 47
 19.1

14.6.14. EUNIts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2587

14.6.15. HUNIts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2588
14.6.16. PERF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2589
14.6.17. SQUEeze . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2591
14.6.18. PROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2593
14.6.19. INJE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2594
14.6.20. LTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2595
14.6.21. PREX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2596
14.6.22. P-RE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2597
14.6.23. WELL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2598
14.6.24. LIFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2600
14.6.25. WCOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2601
14.6.26. WWAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2602
14.6.27. WFRA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2603
14.6.28. WFRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2605
14.6.29. SHUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2609
14.6.30. STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2610
14.6.31. HOIL / HGAS / HWAT / HLIQ / HBHP / HTHP / HWEF . . . . . . 2611
14.6.32. TUBI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2612
14.6.33. FLOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2615
14.6.34. THP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2616
14.6.35. RATI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2617
14.6.36. BHP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2618
14.6.37. ALQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2619
14.6.38. OPEN (RECU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2620
14.6.39. DREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2621
14.6.40. XFLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2622
14.6.41. BHPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2623
14.6.42. THPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2624
14.6.43. OPT / WPT / GPT / LPT / VPT . . . . . . . . . . . . . . . . . . . . 2625
14.6.44. OIT / GIT / WIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2626
14.6.45. LIFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2627
14.6.46. WALQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2628
14.6.47. WEF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2629
14.6.48. STRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2630
14.6.49. GOPT / GGPT / GWPT / GLPT . . . . . . . . . . . . . . . . . . . . 2631
14.6.50. GGIT / GWIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2632
14.6.51. HOURS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2633
14.6.52. DATE / READ / TIME . . . . . . . . . . . . . . . . . . . . . . . . . 2634
14.6.53. GROU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2635
14.6.54. DRAW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2636
14.6.55. VREP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2637
14.6.56. RECY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2638

CONTENTS 48
 19.1

14.6.57. MAKE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2639

14.6.58. SALE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2640
14.6.59. GGRT / GWRT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2641
14.6.60. CWAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2642
14.6.61. KMOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2643
14.6.62. PARE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2644
14.6.63. GVRT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2645
14.6.64. PLIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2646
14.6.65. ILIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2648
14.6.66. GLIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2649
14.6.67. CIJK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2651
14.6.68. ARRAy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2653
14.6.69. FREQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2654
14.6.70. DELTa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2655
14.6.71. COMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2656
14.6.72. BRANch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2657
14.6.73. TRAC (RECU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2658
14.6.74. WGPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2659
14.6.75. WMPG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2660
14.6.76. WRG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2661
14.6.77. TEMP (RECU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2662
14.6.78. TEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2663
14.6.79. STMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2664

15. Keyword definitions index formats E1, E3 2665

16. Keyword definitions index formats IM, ST, GE 2677

17. Keyword definitions index format tN 2682

18. Keyword definitions index format MO 2685

19. References 2689

CONTENTS 49
 19.1

1. Introduction
tNavigator is a software package, offered as a single executable, which allows to build static
and dynamic reservoir models, run dynamic simulations, perform extended uncertainty anal-
ysis and build surface network as a part of one integrated workflow. All the parts of the
workflow share common proprietary internal data storage system, super-scalable parallel nu-
merical engine, data input/output mechanism and graphical user interface. tNavigator supports
METRIC, LAB, FIELD units systems.
tNavigator is a multi-platform software application written in C++ and can be installed on
Linux, Windows 64-bit OS and run on systems with shared and distributed memory layout
as a console or GUI (local or remote) based application. tNavigator runs on workstations and
clusters. Cloud based solution with full GUI capabilities via remote desktop is also available.
tNavigator contains the following 8 functional modules licensed separately:

• Geology Designer (includes PVT Designer and VFP Designer);

• Model Designer (includes PVT Designer and VFP Designer);

• Network Designer (includes PVT Designer and VFP Designer);

• Black Oil simulator;

• Compositional simulator;

• Thermal simulator;

• Assisted History Matching (AHM, optimization and uncertainty analysis);

• Graphical User Interface.

The list of tNavigator documentation is available in tNavigator Library.

In this document there is a description of physical model, mathematical model and

the keywords that can be used in dynamic model in the following tNavigator modules:

• Black Oil simulator;

• Compositional simulator;

• Thermal simulator.

These modules are fully integrated with Graphical User Interface. The description of
graphical interface is available in the User Guide.

tNavigator can be used for the following cases:

• Isothermic systems (black-oil or compositional) – section 2;

1. Introduction 50
 19.1

• Temperature option, to allow the modeling of the temperature effects of cold/hot water
injection – section 2.26;

• Compositional model – section 3;

• Thermal compositional model with chemical reactions – section 4.

List of supported operating systems: Windows (only Windows 7 (SP1) or newer), Linux
(64-bit versions).
CPU+GPU calculation. tNavigator use CPU+GPU simulation engine: calculation speed-
up can be obtained due to solving systems of linear equations using graphics accelerators
NVidia. Only GPUs starting Pascal architecture are supported (and latest CUDA drivers) to
utilize GPU functionality.
tNavigator has one executable file for CPU and GPU calculations. If there are GPU’s available
then they will be used in simulation combined with CPU. If there are no GPU’s available the
calculation will go on CPUs.
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=8 million 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).

Equations of fluid flow in porous media. Molar densities and pressure are set to the state
variables that allow a general compositional model formulation, where the black oil model is
a special case.

The model takes into account the following physical aspects:

• Darcy’s law for fluid flow;

• PVT, EOS, hysteresis;

• Dual porosity, dual permeability;

1. Introduction 51
 19.1

• Streamline, aquifers, tracers;

• Vertical, horizontal, multisegment wells, drilling queue;

• Networks and gas gathering systems;

• Coal bed methane model (CBM);

• Molecular diffusion, adsorption, desorption;

• Enhanced oil recovery (surfactants, polymers, alkaline, foam, CO2 injection);

• Steam injection, Steam Assisted Gravity Drainage technology (SAGD);

• and other.

Model grid. The following aspects are supported:

• Block-centered geometry, corner-point geometry, grid specification via blocks tops;

• Unstructured grids;

• Local grid refinement and coarsening;

• Non-neighbor connections, faults, pinchouts;

• Multireservoir option;

• Reservoir coupling, master-slave;

• Sector modeling (automatic split and merge, boundary conditions).

Time approximations.
The following schemes are available to solve systems of differential equations: fully implicit
time scheme or AIM (adaptive implicit).

Space approximations.
Finite-volume method with finite-difference approximation of the differential operators is uti-
lized. It assumes upstream approximation.

Non-linear system of equations.

We use the Newton method with full Jacobian with analytic derivatives for solving the non-
linear system of equations.

Linear systems with Jacobian and matrix operations.

We use BCGS (BiConjugate Gradient Stabilized) algorithm to solve the system of linear
equations. This is a novel method that gets automatically adjusted to the problem at hand. We
employ ILU(0) as a preconditioner for the linear system solver. This method is a variation
of LU-decomposition that is designed specially for the tNavigator package. When solving a

1. Introduction 52
 19.1

linear system with Jacobian one has to store both the sparse matrix and the preconditioner.
tNavigator contains a block-oriented modification of the widely used MSR (Modified Sparse
Row) method yielding improvement both in memory volume and speed.

For best usage of user experience the keyword notations are chosen to be close as much
as possible to the most common simulators.
tNavigator reads keyword in different formats and converts them into its own inner data
format.

This User Manual describes all keywords which can be used in tNavigator:

• tN keywords;

• E1 keywords;

• E3 keywords;

• IM keywords;

• ST keywords;

• GE keywords;

• MO 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.

E1, E3 format keywords are red. For example: TABDIMS (see 12.1.29). Index of E1, E3
keywords is in 15.

IM, ST, GE format keywords are pink. For example: TEMR (see 13.5.26). Index of these
keywords is in 16.

MO format keywords are green. For example: IDATe (see 14.1.5). Index of MO keywords
is in 18.

The keywords that can be used only in tN are blue. For example: REACCONC
(see 12.15.64). Index of tN keywords is in 17.

The description points out whether there are parameters of the keyword which are used by
some formats and ignored in others, or have different meanings in different formats.
tNavigator simulator is subject to future development. Any feedback is appreciated.

1. Introduction 53
 19.1

2. Physical model
Simulator uses standard three phase three component isothermal black-oil model and compo-
sitional model.

The description of compositional model is in the section 3.

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.8.5),

• RO,G = RO,G (pO ) – vaporisation of oil component into gas phase (known function)
(see 2.8.6),

• BP = BP (pP ) – phase formation volume factor (known function) (see 2.8.2),

• ϕ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.8.3,

2. Physical model 54
 19.1

• k = k(pW , pO , pG , x, y, z) – permeability tensor (known function) (see 2.4),

• krP = krP (SW , SG ) – phase relative permeability (known function) (see 2.6),

• µP = µP (pP ) – phase viscosity (known function) (see 2.8.1),

• γ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.8.4),

• PcOG = PcOG (SG ) – oil-gas capillary pressure (known function) (see 2.11.1),

• PcOW = PcOW (SW ) – oil-water capillary pressure (known function) (see 2.11.2),

• qc = qc (p, N,t, x, y, z) – source of component (known function) (see 2.14.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 5. Mathematical model.
The keyword RUNCTRL (see 12.19.140) controls the solution algorithms and the parame-
ters 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 55

 19.1

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.

2.3.1. Equilibrium initialization

The initial equilibrium is defined by keyword EQUIL (see 12.16.2) and (for 3-phase models)
either PBVD (see 12.16.8) or RSVD (see 12.16.7). It is mandatory to specify one of these
two keywords unless GOC depth coincides with reference depth in all equilibrium regions
(DGOc = Ddat ). The data must be defined for each Equilibrium region.

Additionally, the keyword SWATINIT (see 12.6.65) can be used in this option to set the
initial water saturation that will be used to scale capillary pressure. Thus, when SWATINIT
is used, the capillary pressures are selected in such a way that the given water saturation
is obtained. The PCW scaling array is calculated and created so that the specified capillary
pressures are scaled to obtain SWATINIT.

2.3.2. Non-equilibrium initialization

The initial equilibrium is defined by explicit input of initial pressure and saturation properties
for each grid block by the following keywords:

• SWAT (see 12.16.14), SOIL (see 12.16.16), SGAS (see 12.16.15) – initial saturations
of each phase.

• PRESSURE (see 12.16.12) or PRVD (see 12.16.13) – initial reservoir pressure.

• PBUB (see 12.16.36) or RS (see 12.16.37) – dew point pressure and initial gas solution
in oil. These keywords are used to describe the properties of live oil.

• RV (see 12.16.38) or PDEW (see 12.16.39) – bubble point pressure and initial oil vapor-
ization. These keywords are used to describe the properties of wet gas.

2.3. Initial conditions 56

 19.1

2.3.3. Mixed initialization

By default, EQUIL (see 12.16.2) keyword cannot be used simultaneously with SWAT
(see 12.16.14) and SGAS (see 12.16.15). If both Equilibrium and Non-Equilibrium initial-
Equil Equil Equil
izations are indicated, then equilibrium phase saturations SW , SO , SG be prioritized
and all explicit definitions will be ignored.

The default behavior can be altered by NONEQSAT option of EQLOPTS (see 12.1.94)
Equil Equil Equil
keyword. If this option is set, then SW , SO , SG will be overwritten by SWAT
(see 12.16.14) and/or SGAS (see 12.16.15).

The recalculation algorithm for NONEQSAT option is described below:

1. For 3-phase models (Gas, Oil, and Water are presented in the model):

• EQUIL (see 12.16.2) and SWAT (see 12.16.14) are defined in the same Equilibrium
region:
– SW = SWAT
Equil Equil Equil
– If (1 − SWAT ) > SG then SG = SG and SO = (1 − SWAT − SG )
– Otherwise SG = (1 − SWAT ) and SO = 0
• EQUIL (see 12.16.2) and SGAS (see 12.16.15) are defined in the same Equilibrium
region:
– SG = SGAS
Equil Equil Equil
– If (1 − SGAS) > SW then SW = SW and SO = (1 − SGAS − SW )
– Otherwise SW = (1 − SGAS) and SO = 0
• EQUIL (see 12.16.2) and both SWAT (see 12.16.14) and SGAS (see 12.16.15) are
defined in the same Equillibrium region:
– SG = SGAS
– If (SWAT + SGAS) ≤ 1 then SW = SWAT and SO = (1 − SWAT − SGAS)
– Otherwise SW = (1 − SGAS) and SO = 0

2. For 2-phase models:

• EQUIL (see 12.16.2) and SWAT (see 12.16.14) are defined in the same Equilibrium
region in Oil-Water model.
– SW = SWAT
– SO = (1 − SWAT )
• EQUIL (see 12.16.2) and SWAT (see 12.16.14) are defined in the same Equilibrium
region in Gas-Water model or in 3-phase model with Gas-Water contact (i.e.
Gas-Oil and Water-Oil contacts are set on the same depth).
– SW = SWAT

2.3.3. Mixed initialization 57

 19.1

– SG = (1 − SWAT )
• EQUIL (see 12.16.2) and SGAS (see 12.16.15) are defined in the same Equilibrium
region in Gas-Water model or in 3-phase model with Gas-Water contact (i.e.
Gas-Oil and Water-Oil contacts are set on the same depth).
– SG = SGAS
– SW = (1 − SGAS)

2.4. Permeability tensor

Absolute permeability tensor k = k(pW , pO , pG , x, y, z) is user input data array function de-
fined in all reservoir points. PERMX / PERMY / PERMZ (see 12.2.13) On default de-
pendence of k on pressure is omitted. One can specify this dependence using keywords
ROCKTAB (see 12.5.21) and ROCKTABH (see 12.5.22) (ROCKTABH is used for hysteretic
rock compaction).

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) (2.11)

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 defined via ROCK (see 12.5.17) keyword)

• pref – reference pressure (user input data defined via ROCK (see 12.5.17) keyword)
Also, porosity dependence on reservoir pressure can be defined via Rock Compaction
Tables (ROCKTAB (see 12.5.21), or ROCKTABH (see 12.5.22) (ROCKTABH is used for hys-
teretic rock compaction)).

In this case the pore volume will be modified with a use of porosity multipliers:

ϕ(p) = ϕinit × ϕmult (p) (2.12)

where
• ϕinit – Initial porosity.

• ϕmult (p) – Porosity multiplier.

2.4. Permeability tensor 58

 19.1

Additionally, the modifiers can be applied to porosity multipliers with respect to pressure
gradient:

(p − pre f )
 
ϕ(p) = ϕinit × ϕmult (p) λ1 + λ1 (2.13)
Pscale
where

• λ1 and λ2 – dimensionless modification parameters defined by HMMROCKT

(see 12.5.23) keyword.

• pre f – pivot reference pressure defined by HMRREF (see 12.5.24) keyword.

• pscale – reference scale pressure defined by HMRREF (see 12.5.24) keyword. This pa-
rameter is applied to make λ2 dimensionless.

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 water-oil and
gas-oil.

2. Relative permeabilities (and capillary pressure) scaling for two-phase systems.

3. Oil relative permeability krO is calculated using the first or the second Stone’s model
(STONE1 (see 12.6.20), section 2.6.5, STONE2 (see 12.6.21), section 2.6.6) or linear
Baker’s model (section 2.6.4). Linear Baker’s model is used for default.

Phase relative permeability krP = krP (SW , SG ) are defined by experimental data. The usual
assumptions are:

krW = krW (SW ) (2.14)

krG = krG (SG ) (2.15)
krO = krO (SW , SG ) (2.16)

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

(Can be set for example via SWOF (see 12.6.1) for first pair, SGOF (see 12.6.2), SLGOF
(see 12.6.11) for second pair. The full list of supported keywords is in the section 2.6.1).
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

2.6. Phase relative permeability 59

 19.1

• 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

Then we can define analytical approximations for the listed above functions:

nW if SW ≤ SWC
 0

krWO (SW ) =

SW − SWC
 krW rO
 otherwise
1 − SWC − SOrW

nOW if 1 − SW − SOrW < 0
 0

krOW (SW ) =

1 − SW − SOrW
 krOcW
 otherwise
1 − SWC − SOrW

nG if SG < SGr
 0

krGO (SG ) =

S G − SGr
 krGcW
 otherwise
1 − SGr − Swr

nOG if 1 − SG − SW c − SOrG < 0
 0

krOG (SG ) =

1 − SG − SW c − SOrG
 krOcW
 otherwise
1 − SW c − SOrG

Then we define:

krW (SW ) = krWO (SW ), (2.17)

krG (SG ) = krGO (SG ). (2.18)

2.6.1. Keywords to set relative permeability

• 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);

2.6.1. Keywords to set relative permeability 60

 19.1

• 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 mod-
els, when oil isn’t present);

• COREYWO (see 12.6.3), COREYGO (see 12.6.4), COREYWG (see 12.6.5) — calculation
of relative permeabilities and capillary pressure via Corey correlation;

• LETWO (see 12.6.8), LETGO (see 12.6.9), LETWG (see 12.6.10) — calculation of rela-
tive permeabilities and capillary pressure via LET correlation.

The are two keyword groups; one shouldn’t 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 12.5. PVT Properties (PVT properties,
permeabilities, initial pressures and saturations).
The following keyword combinations are allowed (from keywords PVTO, PVCO, PVCDO,
PVDO, PVDG, PVZG, PVTG, PVTW, RSCONST, RSCONSTT, RVCONST, RVCONSTT,
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)
Live oil, PVTO (see 12.5.4) (or PVCO, see 12.5.6),
dry gas, PVDG (see 12.5.7) (or PVZG, see 12.5.9),
water PVTW (see 12.5.5),
SGOF (see 12.6.2), SLGOF (see 12.6.11), SWOF (see 12.6.1)

2.6.1. Keywords to set relative permeability 61

 19.1

Live oil, PVTO (see 12.5.4) (or PVCO, see 12.5.6),

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.13) (or RSCONSTT, see 12.5.14),
water PVTW (see 12.5.5),
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.15) (or RVCONSTT, see 12.5.16),
water PVTW (see 12.5.5),
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),
water PVTW (see 12.5.5),
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),
water PVTW (see 12.5.5),
SGOF (see 12.6.2), SLGOF (see 12.6.11), SWOF (see 12.6.1)

2.6.2. 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 formulae below.

2.6.2. Corey correlation 62

 19.1

In tNavigator there is a possibility to use Corey (LET) correlation only for

RP and define capillary pressure via a table. In this case one should enter 0
i in parameter 12 (power) of the keyword COREYWO, COREYGO (LETWO,
LETGO) and define tables SWOF, SGOF or other. Values for capillary pres-
sure will be taken from tables and RP will be calculated using Corey (LET)
correlation.
Keyword COREYWO (see 12.6.3) (see the picture 1 for relative permeabilities for water-
oil system):

Figure 1. Relative permeabilities for water-oil system

Denote:
SW − SWCR
SW n = SW n (SW ) =
1 − SWCR − SOWCR − SGL

2.6.2. Corey correlation 63

 19.1


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.19)





0, 1 − SOWCR − SGL < SW ≤ SWU





 0, SW L ≤ SW < SWCR


 k (S )nW , S

rW R W n WCR ≤ SW ≤ 1 − SOWCR − SGL
krW (SW ) = (2.20)
WU −SW
krWU − (krWU − krW R ) SOWCRS+S




 GL +SWU −1
,

1 − SOWCR − SGL < SW ≤ SWU

 h in p
 pcOW (SWCR ) S pcO −SW

, SW L ≤ SW ≤ S pcO
S pcO −SWCR
pcOW (SW ) = (2.21)

0, S pcO < SW ≤ SWU


Modified formulae for RP approximation (the keyword COREYWOMOD, see 12.6.6):

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
krORW + (krOLW − krORW ) SSWCR SW L ≤ SW < SWCR




 −SW L

krOW (SW ) = krORW (1 − SW n )nOW SWCR ≤ SW ≤ 1 − SOWCR − SGL (2.22)





0 1 − SOWCR − SGL < SW ≤ SWU



0 SW L ≤ SW < SWCR






krW (SW ) = krW R (SW n )nW SWCR ≤ SW ≤ 1 − SGL (2.23)




 SWU −SW
krWU − (krWU − krW R ) SGL 1 − SGL < SW ≤ SWU

+SWU −1

2.6.2. Corey correlation 64

 19.1


S pcO −SW n p
h i
 pcOW (SWCR ) SW L ≤ SW ≤ S pcO

S pcO −SWCR
pcOW (SW ) = (2.24)

0 S pcO < SW ≤ SWU


Keyword COREYGO (see 12.6.4) (see the picture 2 for relative permeabilities for gas-oil
system):

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 ≤ SG < SGCR




 −SGL

krOG (SG ) = krORG (1 − SGn )nOG SGCR ≤ SG ≤ 1 − SOGCR − SW L (2.25)





0 1 − SOGCR − SW L < SG ≤ SGU


2.6.2. Corey correlation 65

 19.1


0 SGL ≤ SG < SGCR






krG (SG ) = krGR (SGn )nG SGCR ≤ SG ≤ 1 − SOGCR − SW L (2.26)




GU −SG
krGU − (krGU − krGR ) SOGCR S+S

1 − SOGCR − SW L < SG ≤ SGU

W L +SGU −1


0 SGL ≤ SG < S pcG


pcOG (SG ) = h in pG (2.27)
S −S pcG
 pcOG (1 − SOGCR − SW L ) 1−S pcGG−SOGCR S pcG ≤ SG ≤ SGU


−SW L

Modified formulae 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
krORG + (krOLG − krORG ) SSGCR SGL ≤ SG < SGCR




 −SGL

krOG (SG ) = krORG (1 − SGn )nOG SGCR ≤ SG ≤ 1 − SOGCR − SW L (2.28)





0 1 − SOGCR − SW L < SG ≤ SGU


0 SGL ≤ SG < SGCR






krG (SG ) = krGR (SGn )nG SGCR ≤ SG ≤ 1 − SW L (2.29)




−SG
krGU − (krGU − krGR ) SWSLGU

+SGU −1 1 − SW L < SG ≤ SGU



0 SGL ≤ SG < S pcG


pcOG (SG ) = h in pG (2.30)
S −S pcG
 pcOG (1 − SOGCR − SW L ) 1−S pcGG−SOGCR S pcG ≤ SG ≤ SGU


−SW L

Keyword COREYWG (see 12.6.5) (see the picture 3 for relative permeabilities for water-
gas system):

2.6.2. Corey correlation 66

 19.1

Figure 3. Relative permeabilities for water-gas system

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.31)




 SWU −SW
krWU − (krWU − krW R ) SGCR 1 − SGCR < SW ≤ SWU

+SWU −1

2.6.2. Corey correlation 67

 19.1


0 SGL ≤ SG < SGCR





krG (SG ) = krGR (SGn )nG SGCR ≤ SG ≤ 1 − SWCR (2.32)




 SGU −SG
krGU − (krGU − krGR ) SWCR 1 − SWCR < SG ≤ SGU

+SGU −1

S pcO −SW n p
h i
 pcW G (SWCR ) SW L ≤ SW ≤ S pcO

S pcO −SWCR
pcW G (SW ) = (2.33)

0 S pcO < SW ≤ SWU


2.6.3. LET correlation

The keywords LETWO (see 12.6.8), LETGO (see 12.6.9) and LETWG (see 12.6.10) approx-
imates relative permeability for water-oil, gas-oil and water-gas systems using formulae below.

In tNavigator there is a possibility to use Corey (LET) correlation only for

RP and define capillary pressure via a table. In this case one should enter 0
i in parameter 12 (power) of the keyword COREYWO, COREYGO (LETWO,
LETGO) and define tables SWOF, SGOF or other. Values for capillary pres-
sure will be taken from tables and RP will be calculated using Corey (LET)
correlation.
For water-oil system (keyword LETWO (see 12.6.8), see the picture 4):

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
nOW +E STO
, SWCR ≤ SW ≤ 1 − SOWCR − SGL (2.34)


 (1−S W n ) O W n


0, 1 − SOWCR − SGL < SW ≤ SWU





 0, SW L ≤ SW < SWCR
 n
krW R SWWn



nW , SWCR ≤ SW ≤ 1 − SOWCR − SGL
krW (SW ) = SW n +EW (1−SW n )TW (2.35)
WU −SW
krWU − (krWU − krW R ) SOWCRS+S




 GL +SWU −1
,

1 − SOWCR − SGL < SW ≤ SWU


2.6.3. LET correlation 68

 19.1

Figure 4. LET correlation for water-oil system

formulae for capillary pressure are the same as in section Corey correlation 2.6.2.

Description of parameters:

• N describes the lower part of the curve (the same way as N in Corey correlation).

• 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), see the picture 5):

Denote:
SG − SGCR
SGn = SGn (SG ) =
1 − SGCR − SOGCR − SW L

2.6.3. LET correlation 69

 19.1

Figure 5. LET correlation for gas-oil system


GCR −SG
krORG + (krOLG − krORG ) SSGCR SGL ≤ SG < SGCR




 −SGL

krOG (SG ) = krORG (1−SGn )nOG (2.36)
TG SGCR ≤ SG ≤ 1 − SOGCR − SW L


 (1−SGn )nOG +EG SGn


0 1 − SOGCR − SW L < SG ≤ SGU



0 SGL ≤ SG < SGCR





 n G
krG (SG ) = krGR SGn
nG SGCR ≤ SG ≤ 1 − SOGCR − SW L (2.37)
 SGn +EG (1−SGn )TG



GU −SG
krGU − (krGU − krGR ) SOGCR S+S

1 − SOGCR − SW L < SG ≤ SGU

W L +SGU −1

For the water-gas systems (keyword LETWG, see 12.6.10) (picture – 6):

Denote:

2.6.3. LET correlation 70

 19.1

Figure 6. LET correlation for water-gas system

SW − SWCR
SW n = SW n (SW ) =
1 − SWCR − SGCR
SG − SGCR
SGn = SGn (SG ) =
1 − SGCR − SWCR
Then:


0 SGL ≤ SG < SGCR





 nG
krG (SG ) = krGR SGn (2.38)
nG SGCR ≤ SG ≤ 1 − SWCR

 SGn +EG (1−SGn )TG


 SGU −SG
krGU − (krGU − krGR ) SWCR 1 − SWCR < SG ≤ SGU

+SGU −1

2.6.3. LET correlation 71

 19.1


0 SW L ≤ SW < SWCR




 n
krW (SW ) = krW R SWWn (2.39)
nW SWCR ≤ SW ≤ 1 − SGCR
 SW n +EW (1−SW n )TW



 SWU −SW
krWU − (krWU − krW R ) SGCR 1 − SGCR < SW ≤ SWU

+SWU −1

Formulae for capillary pressure are the same as in 2.6.2. Corey correlation.

2.6.4. 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 < ε










krOW (SG + SW ) SG < ε


krO (SW , SG ) = (2.40)
 SG · krOG (SG + SW − SW c )
+


SG + (SW − SW c )





 + (SW − SW c ) · krOW (SG + SW )



 else
SG + (SW − SW c )

2.6.5. First Stone’s model

The keyword STONE1 (see 12.6.20) is used to specify this model.

Let us define the following constants:

• 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.

2.6.4. Linear Baker model 72

 19.1

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), SOM-
GAS (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.41)
1 − SW c − Som (SG )
and ∗ (S , S )
SO O G krOW (SW ) krOG (SG )
krO = krO (SO , SW , SG ) = ∗ ∗ (S ) . (2.42)
krOcW 1 − SW (SW , SG ) 1 − SG G

2.6.6. Second Stone’s 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
• 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 ) −
krOcW krOcW
− krOcW (krW (SW ) + krG (SG )) (2.43)

2.6.7. End point scaling, two-point method

Phase permeability scaling. Specification of critical saturation end points can be done using
one of the following ways (not compatible by default):

2.6.6. Second Stone’s model 73

 19.1

• Specification of critical saturation end points for each grid block (keywords SWL
(see 12.6.26), SWCR (see 12.6.29), ..., KRW (see 12.6.59), ...).

• Specification of critical saturation end points as depth function (keywords ENPTVD

(see 12.6.37), ENKRVD, see 12.6.38).

• Specification of critical saturation end points as a function of temperature (keywords

ENPTVT (see 12.15.85), ENKRVT, see 12.15.86) – only for thermo-compositional
model.

• Specification of critical saturation end points as a function of composition (ENPTVC

(see 12.14.57), ENKRVC, see 12.14.55) – only for compositional model.

• Specification of critical saturation end points as a function of tracer (salt, surfactant) con-
centration (tNavigator-only keywords ENPTRC (see 12.6.40), ENPTRCM, see 12.6.43).

Possible combinations can be specified using 5-th parameter of the keyword ENDSCALE
(see 12.1.136).

The keyword ENDSCALE (see 12.1.136) indicates that end point scaling of relative per-
meabilities and capillary pressures will be used. Table end points can then be entered cell
by cell (SWL (see 12.6.26), SWCR (see 12.6.29), SWU (see 12.6.33), KRW (see 12.6.59),
PCW, see 12.6.62) or with respect to depth (ENPTVD (see 12.6.37), ENKRVD (see 12.6.38),
ENPCVD, see 12.6.39).

If end point scaling option is selected (ENDSCALE, see 12.1.136), saturations and relative
permeabilities are renormalized according to formulae below.
Saturations scaling
First introduce notations

• SW , SG are block water and gas saturations,

• 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) isn’t 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 ∗ 10−6 – in E1 models (krW ≤ 1.0 ∗ 10−20 – in E3 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),

2.6.7. End point scaling, two-point method 74

 19.1

• SWCR (see 12.6.29), SGCR (see 12.6.30) are user defined values of critical water (and
gas) saturation in current block,

• SWU (see 12.6.33), SGU (see 12.6.34) are user defined values of maximal water (and
gas) saturation in current block,

• S̃W , S̃G 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 )

S̃W = SW cr +
SWU − SWCR (2.44)
(SG − SGCR)(SGmax − SGcr )
S̃G = SGcr +
SGU − SGCR
The keyword TZONE (see 12.6.24) 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.31) will be modified for oil-
water runs or oil-water-miscible gas runs, SOGCR (see 12.6.32) will be modified only
for oil-gas runs;

2. the parameter is set true to water phase, SWCR (see 12.6.29) will be modified;

3. the parameter is set true to gas phase, SGCR (see 12.6.30) will be modified for gas-water
runs and oil-gas runs.

Appropriate relative permeabilities are calculated as


 0

 SW ≤ SWCR
krW (SW ) = krWO (S̃W ) SWCR < SW < SWU (2.45)


krW max (table) SW ≥ SWU


 0

 SG ≤ SGCR
krG (SG ) = krGO (S̃G ) SGCR < SG < SGU (2.46)


krG max (table) SG ≥ SGU


Oil relative permeabilities are calculated in analogous way.

2.6.7. End point scaling, two-point method 75

 19.1

Relative permeabilities scaling

If at least one of the following arrays KRO (see 12.6.58), KRW (see 12.6.59), KRG
(see 12.6.60), KRORW (see 12.6.58), KRORG (see 12.6.58), KRWR (see 12.6.59), KRGR
(see 12.6.60) is set, relative permeabilities are additionally scaled according to following
formulae.

• Water:

◦ If only KRW is set

scaled KRW
krW (SW ) = krW (SW ) · (2.47)
krW max (table)

◦ If both KRW and KRWR are set

scaled KRW R
SW 6 SR krW (SW ) = krW (SW ) · (2.48)
krW (SR)
scaled
SW > SR krW (SW ) = KRW R + (2.49)
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.50)

SR(table) = 1.0 − SGCR(table) gas-water case (2.51)

• Gas:

◦ If only KRG is set

scaled KRG
krG (SG ) = krG (SG ) · (2.52)
krG max (table)

◦ If both KRG and KRGR are set

scaled KRGR
SG 6 SR krG (SG ) = krG (SG ) · (2.53)
krG (SR)
scaled
SG > SR krG (SG ) = KRGR + (2.54)
KRG − KRGR
+ · (krG (SG ) − krG (SR))
krG max (table) − krG (SR)

2.6.7. End point scaling, two-point method 76

 19.1

• Oil:
here “P” stands for water or gas phase

◦ If only KRO is set

scaled KRO
krOP (SP ) = krOP (SP ) · (2.55)
krOP max (table)

◦ If both KRO and KRORP are set

scaled KRORP
SP 6 SPCR krOP (SP ) = krOP (SP ) · (2.56)
krOP (SPCR)
scaled
SP > SPCR krOP (SP ) = KRORP +
KRO − KRORP
+ · (krOP (SP ) − krOP (SPCR))
krOP max (table) − krOP (SPCR)

2.6.8. End point scaling, three-point method

If in addition to ENDSCALE (see 12.1.136) three point scaling method for relative perme-
abilities is selected (SCALECRS, see 12.6.25), phase permeabilities are recalculated in the
following manner.
Saturations scaling
As for two-point case, first introduce notations

• SW , SG are block water and gas saturations,

• 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),

• SW max , SGmax are maximal values of water (and gas) saturation in SWOF (see 12.6.1)
(SGOF, see 12.6.2),

• SWL (see 12.6.26), SGL (see 12.6.28) are user defined values of connate water (and
gas) saturation in current block,

• SWCR (see 12.6.29), SGCR (see 12.6.30) are user defined values of critical water (and
gas) saturation in current block,

2.6.8. End point scaling, three-point method 77

 19.1

• SOWCR (see 12.6.31), SOGCR (see 12.6.32) are user defined values of critical oil-to-
water (and oil-to-gas) saturation in current block,
• SWU (see 12.6.33), SGU (see 12.6.34) are user defined values of maximal water (and
gas) saturation in current block,
• S̃W , S̃G 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 −SWCR)(Sr −SW cr )
W cr + SWCR < SW < SR
 S
S̃W = SR−SWCR (2.57)
 S + W (S −SR)(SW max −Sr )
r SWU−SR SR < SW < SWU

Relative permeability is calculated as in (2.45).

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

 S + (SG −SGCR)(Sr −SGcr ) SGCR < S < SR
Gcr SR−SGCR G
S̃G = (2.58)
 S + (SG −SR)(SGmax −Sr ) SR < S < SGU
r SGU−SR G

Relative permeability is calculated as in (2.46).

The keyword TZONE (see 12.6.24) 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.31) will be modified for oil-
water runs or oil-water-miscible gas runs, SOGCR (see 12.6.32) will be modified only
for oil-gas runs;
2. the parameter is set true to water phase, SWCR (see 12.6.29) will be modified;
3. the parameter is set true to gas phase, SGCR (see 12.6.30) will be modified for gas-water
runs and oil-gas runs.

2.6.8. End point scaling, three-point method 78

 19.1

Relative permeabilities scaling

If at least one of the following arrays KRO (see 12.6.58), KRW (see 12.6.59), KRG
(see 12.6.60), KRORW (see 12.6.58), KRORG (see 12.6.58), KRWR (see 12.6.59), KRGR
(see 12.6.60) is set, relative permeabilities are additionally scaled according to formulae, the
same as for two-point scaling case, see (2.47) – (2.56). The only difference is that now SR
and SPCR are defined properly.

2.6.9. Directional and irreversible RP

Directional and irreversible relative permeabilities can be used if the corresponding options
are specified in SATOPTS (see 12.1.75):
• 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.23), KRNUMY (see 12.4.23), KRNUMZ, see 12.4.23). 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.23),
KRNUMX- (see 12.4.23), KRNUMY (see 12.4.23), KRNUMY- (see 12.4.23), KRNUMZ
(see 12.4.23) and KRNUMZ- (see 12.4.23).
If hysteresis is used (option HYSTER in SATOPTS, see 12.1.75) 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.75):
• 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 IMBNUMX (see 12.4.7), IMBNUMY (see 12.4.7), IMBNUMZ, see 12.4.7). 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 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.10. RP at dual porosity runs.

KRNUMMF (see 12.4.24) – 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.83) and dual permeability DUALPERM (see 12.1.84).
In accordance with the grid specification for dual porosity models (upper part – the matrix,

2.6.9. Directional and irreversible RP 79

 19.1

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.25) – 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.83) and dual permeability DUALPERM (see 12.1.84) in case when hysteresis option
is used (parameter HYSTER of the keyword SATOPTS, see 12.1.75).
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 an imbibition table for matrix,
the flow from the fracture to the matrix uses an imbibition table for fracture.

2.6.11. 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.19.32) 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:

• kr (P, ∗) – relative permeability of the injected phase (a constant value specified via the
keyword COMPINJK, see 12.19.32) (relative permeability in the region that is full of
injected phase);

• relative permeabilities of other phases are zero.

2.6.11. User-defined relative permeability of the injected phase 80

 19.1

2.6.12. Surface tension effects

The surface tension between the oil and gas phases can be used to evaluate miscibility of two
fluids. For models in E3 format the approach [28], in which parameters that are functions
of surface tension are applied for interpolation of relative permeability and pressure between
immiscible and miscible values:

immiscibile miscibile
KrO = Fk KrO + (1 − Fk )KrO
immiscibile miscibile
KrG = Fk KrG + (1 − Fk )KrG
immiscibile
PcOG = Fp PcOG
where KrO , KrG are the relative permeability of oil and gas, respectively, PcOG is a capillary
pressure in the oil-gas system, Fk and Fp are interpolation parameters that are functions of
the surface tension σ between oil and gas phases. If surface tension is high then parameters
Fk and Fp tend to 1 and the flow becomes immiscible. If surface tension is weak parameters
tend to 0 and the flow becomes miscible.
Immiscible parameters, such as KrO immiscibile , K immiscibile and Pimmiscibile , can be obtained
rG cOG
from the user-defined rock curves (e.g., using the keyword SGFN, see 12.6.14). Miscible
relative permeabilities for oil and gas are assumed to be straight lines by default, for example
miscibile = S , however, rock curves defined by user can be specified using the keyword
KrO O
MISCNUM (see 12.4.8). The miscible capillary pressure is assumed to be zero. Furthermore,
miscibile , Smiscibile for miscible flow are scaled in such way that end
the critical saturations SOcr Gcr
points for miscible and immiscible relative permeabilities coincide:

immiscibile miscibile
SOcr = Fk SOcr + (1 − Fk )SOcr
immiscibile miscibile
SGcr = Fk SGcr + (1 − Fk )SGcr
immiscibile , Simmiscibile are the critical immiscible saturations for oil and gas, respectively,
SOcr Gcr
generally obtained from user-defined rock curves, however, in the case of hysteresis they may
be the critical point of a scanning curve (see section 2.7).
By default (unless the keyword MISCNUM (see 12.4.8) is not defined) SOcr miscibile and
miscibile are equal to zero, then above written equations are simplified:
SGcr

miscibile
SOcr = Fk SOcr
miscibile
SGcr = Fk SGcr
The interpolation parameter for relative permeability Fk is computed by the Coats’s formula:
 N
σ
Fk =
σ0

where σ0 is the reference surface tension (dynes/cm) (defined by MISCSTR (see 12.6.76) or
MISCSTRR, see 12.6.78), N is the exponent set by keyword MISCEXP, see 12.6.79). σ0 can
be also calculated using the Macleod-Sugden correlation (see the formula below) at a reference

2.6.12. Surface tension effects 81

 19.1

pressure, specified by keyword MISCSTRP (see 12.6.77) or MISCSTRR (see 12.6.78).

Thus, relative permeabilities approach to miscible values if surface tension σ (dynes/cm)
tend to zero and immiscible values if surface tension σ is larger than or equal to the reference
surface tension σ0 . For blocks, where the flow is single-phase, Fk is equal to 1.
The interpolation parameter for capillary pressure Fp is a linear function of the surface
tension:  
σ1 σ
Fp = min ,
σ0 σ0
where σ1 is the maximum surface tension for capillary pressure calculation (by default σ1 =
σ0 ), but it can be defined larger then σ0 using the 3-rd parameter of keyword MISCSTR
(see 12.6.76) or MISCSTRR (see 12.6.78).
If surface tension tend to zero, the capillary pressure PcOG is equal to miscible capillary
pressure, i.e. is equal to zero. If surface tension is equal to the reference one σ0 then the
immiscibile . If surface tension
capillary pressure PcOG is equal to immiscible capillary pressure PcOG
is larger than σ0 the capillary pressure can be extrapolated beyond the immiscible values. In
this case Fp can exceed 1:
σ1
Fp ≤
σ0
For blocks, where the flow is single-phase, Fk is set equal to 1.
The surface tension σ can be defined as a pressure function using the keyword STVP
(see 12.8.43) or using the Macleod-Sugden correlation:
" #4
Nc
σ= ∑ [P]i(bmLxi − bVmyi)
i=1

where xi , yi are the liquid and vapor mole fractions, bm m

L , bV are the liquid and vapor phase
molar densities converted into gm-M/cc, [P]i are parachors defined by keywords PARACHOR
(see 12.6.80). For blocks, where the flow is single-phase, the surface tension is equal to zero.
The value of surface tension drops to zero when phase compositions and phase molar densities
become equal. Such condition occurs near the critical point.
To take into account a surface tension effect the following keywords can be used:

• MISCIBLE (see 12.1.69) – for models in E3 format turns on dependence of relative

permeability and capillary pressure on surface tensions;

• MISCNUM (see 12.4.8) – specifies miscibility region number for each grid block;

• MISCSTR (see 12.6.76) – specifies reference surface tension (one should use the key-
word MISCSTRR (see 12.6.78) to set the miscibility reference surface tension for each
saturation region);

• MISCSTRP (see 12.6.77) – specifies miscibility surface tension reference pressure (al-
ternative to the keyword MISCSTR, see 12.6.76);

2.6.12. Surface tension effects 82

 19.1

• MISCEXP (see 12.6.79) – specifies miscibility exponent (exponent of the surface tension
ratio);

• STVP (see 12.8.43) – specifies surface tension variation with pressure;

• PARACHOR (see 12.6.80) – specifies parachors.

2.6.13. Miscible flood modeling

The simulation of miscible flood for models in E1 format is based on an implementation of
the empirical approach developed by M. Todd and W. Longstaff [27]. An alternative approach
for models in E3 format is used for miscible flood modeling, which is based on the use of
surface tensions calculated using the Macleod–Sugden correlation (see section 2.6.12. Surface
tension effects).
The miscible displacement of oil by miscible gas injection is modeled in three-component
system consisting of reservoir oil, injection gas (solvent) and water. It is assumed that reservoir
fluids consits of three components: oil (stock tank oil together with the associated solution
gas), injection gas (solvent) and water. The solvent and reservoir oil components are miscible
in all proportions, i.e. one hydrocarbon phase exists in the reservoir. Thus, the relative perme-
ability requirements of the model are similar to a two-phase system (water–hydrocarbon). The
viscosity and density are recalculated taken into account the Todd-Longstaff mixing parameter.
The empirical Todd–Longstaff approach allows to simulate a physical dispersion between
the miscible components in the hydrocarbon phase. An empirical mixing parameter ω is in-
troduced varing from 0 to 1 and defining the size of the dispersed area in each block of the
grid. Thus, the value of mixing parameter ω defines the degree of fluid mixing in each block.
If ω =1 the size of the dispersed area is much larger than the typical size of block, therefore,
the hydrocarbon components are considered to be fully mixed. In this case the miscible com-
ponents have the same values of viscosity and density as defined by the appropriate formulas.
If ω =0 the dispersed area between oil and gas is negligibly thin then density and viscosity
of miscible components are equal to values of density and viscosity of pure components.
Intermediate value of ω is used to simulate incomplete mixing of components.
In miscible flood modeling the injected gas is a solvent with the oil. The flow equations
are a special case of the standard three-phase, three-component flow (water, oil and gas),
where the gas-oil capillary pressure is set to zero (i.e. PcOG =0).
It is possible to define a capillary pressure between water and hydrocarbon phases
PctW (SW ) not equal to zero as a function of water saturation. The pressures of components
are:
PG = PO
PW = PO − PctW (SW )
In miscible flood modeling the following keywords are used:

• MISCIBLE (see 12.1.69) – for models in E1 format activates the miscible flood model
based on the Todd–Longstaff approach;

2.6.13. Miscible flood modeling 83

 19.1

• PMISC (see 12.6.81) – defines tables that model the transition between immiscible and
miscible displacement as a function of oil pressure;

• MSFN (see 12.6.82) – allows to use a relative permeability curve for the miscible dis-
placement model;

• SDENSITY (see 12.6.83) – specifies the surface density of miscible injection gas for the
miscible displacement model;

• SGCWMIS (see 12.6.84) – defines tables of miscible critical gas saturation versus water
saturation;

• SORWMIS (see 12.6.85) – defines tables of miscible residual oil saturation versus water
saturation;

• TLMIXPAR (see 12.6.86) – defines the Todd-Longstaff mixing parameter.

2.6.14. Velocity-dependent relative permeabilities

In case of high gas velocities, in addition to the Forchheimer models, this model takes into
account complex effects by defining a dependence between velocity and relative permeability.
The oil and gas relative permeabilities are functions of Capillary Number in accordance with
switches specified by user via the VELDEP (see 12.1.8) keyword in the RUNSPEC section.
The properties of the oil and gas velocity-dependent relative permeabilities are specified by
the keywords VDKRO (see 12.14.64), VDKRG (see 12.14.62) and VDKRGC (see 12.14.63).
These models are implemented for gas condensate systems in case of the expected re-
duction in Productivity Index (PI) are not observed when a well bottom hole pressure drops
below the fluid dew point pressure. There are several theories explaining why the gas rela-
tive permeability in particular remains relatively high. Nowdays, the widely accepted theory
assumes that a combination of low Interfacial Tensions (IFT) at reservoir conditions and high
velocities are the main driving forces.
In practice IFT is combined with velocity through the capillary number. The available
definitions of the capillary number are described below. If flow velocities are high, turbulence
effects as indicated by the Forchheimer model become significant and a model for velocity-
dependent relative permeabilities has been developed as part of this global scheme. These
models are intended for gas condensate systems and do not work with black oil models.
Capillary number models
The capillary number model affects the gas and oil relative permeabilities. The increase in
the capillary number leads to:
• decrease in residual saturations;

• change of the relative permeability from the user-specified (immiscible) saturation

curves towards an miscible curve generated by simulator.
There are two model of capillary number:

2.6.14. Velocity-dependent relative permeabilities 84

 19.1

• 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 ith phase in
flow direction at previous time step;
– ∆Pi - pressure drop of ith phase;
– L - length of block along flow direction.

Forchheimer models
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

• 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

2.6.14. Velocity-dependent relative permeabilities 85

 19.1

Calculation of D-factor based on the Forchheimer parameter

If for gas phase Forchheimer parameter is calculated based on the model specified by key-
word VELDEP (see 12.1.8), a D-factor for all production well connections is also calculated.
For models in E3 formats D-factors defined by keywords COMPDAT (see 12.19.6) or
WDFAC (see 12.19.168) are replaced by D-factors calculated using VELDEP (see 12.1.8).
However, if D-factors calculated using keyword WDFACCOR (see 12.19.169) overwrite the
D-factor values calculated based on Forchheimer parameter (see formula below). Calculated
D-factors for well connections can be written to the summary file via the mnemonic CDFAC.
D-factor is calculated based on the Forchheimer parameter as:
Ke 1 γg
D = α · βg · · ·
h rw µg
where
• α is a constant (METRIC: 2.2446×10−10 day/sm3 , FIELD: 6.83352×10−8 day/Msc f );

• βg is the Forchheimer parameter for gas;

• Ke is the effective permeability of the connected grid block;

• h is the length of the connection;

• rw is the wellbore radius;

• γg is the relative density of produced or injected gas at surface conditions with respect
to air at standard temperature and pressure;

• µg is the gas viscosity in the connection grid block.

This formula is based on the assumption that effective radius r0 is much larger than the
wellbore radius rw .

2.7. Hysteresis
Relative permeabilities and capillary pressure depend not only the saturation, but also on the
direction of variation. Hysteresis allows to simulate dependence of saturation functions on
prehistory. In two-phase system (water-oil or gas-oil) let’s denote the wetting relationship as
P1 > P2 if a phase P1 wets P2 . This means that the phase P1 is a wetting phase and P2 is
a non-wetting one. A process of decreasing wetting phase saturation is called drainage and
a process of increasing wetting phase saturation is called imbibition. Relative permeabilities
curves corresponding to these processes are denoted kdrain and kimbib , respectively.
In case of the drainage or imbibition process is reversed at some point, the used data does
not pass back over its previous values but instead start follows a scanning curve generated by
the implemented hysteresis model (e.g., Carlson’s, Killough’s, Jargon’s models).
Hysteresis is applied during calculation of relative permeabilities and capillary pressure in
the two-phase system and can be taken into account in the three-phase system.

2.7. Hysteresis 86
 19.1

Therefore, for water-oil system we should specified the wetting relationship between oil
and water, while for gas-oil system the wetting relationship between gas and oil.
The general description of avaliable hysteresis options and calculation algorithms in E1/E3
format are provided in sections 2.7.1 – 2.7.5.
The list of avaliable options for realtive permeability and capillary pressure hysteresis in
IM/GE/ST format is provided in section 2.7.6.

2.7.1. Implementing the hysteresis option

Hysteresis option allows to use relative permeabilities and capillary pressure curves for
drainage (decreasing wetting phase saturation) and imbibition (increasing wetting phase satu-
ration) processes in the model. Hysteresis option can be enabled via the keyword SATOPTS
(see 12.1.75) (parameter HYSTER).

The main hysteresis parameters are specified via keyword EHYSTR (see 12.6.67) or via
HYSTKRW / HYSTKROW / HYSTKRG / HYSTKROG (see 12.6.70) keywords (for relative
permeability hysteresis) and HYSTPCW / HYSTPCG (see 12.6.72) keywords (for capillary
pressure hysteresis).

If there are several saturation regions in the model, different hysteresis models can be
assigned for each region via HYSTKRWR / HYSTKROWR / HYSTKRGR / HYSTKROGR
(see 12.6.71) keywords (for relative permeability hysteresis) and HYSTPCWR / HYSTPCGR
(see 12.6.73) keywords (for capillary pressure hysteresis).

EHYSTR (see 12.6.67) will be ignored if at least one of HYSTKRW(R) (see 12.6.71),
HYSTKROW(R) (see 12.6.71), HYSTKRG(R) (see 12.6.71), HYSTKROG(R) (see 12.6.71),
HYSTPCW(R) (see 12.6.73), HYSTPCG(R) (see 12.6.73) keywords is indicated, as they have
higher priority.

Additional hysteresis parameters can be specified via keyword HYSTOPTS (see 12.6.74)
or HYSTOPTSR (see 12.6.75) .

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.

The following models of relative permeability hysteresis can be implemented by EHYSTR

(see 12.6.67) keyword:

• 0 – Carlson’s hysteresis model used for the non-wetting phase(s), drainage (SATNUM,
see 12.4.3) curve used for the wetting phase.

2.7.1. Implementing the hysteresis option 87

 19.1

• 1 – Carlson’s hysteresis model used for the non-wetting phase(s), imbibition (IMBNUM,
see 12.4.7) curve used for the wetting phase.

• 2 – Killough’s hysteresis model used for the non-wetting phase(s), drainage (SATNUM,
see 12.4.3) curve used for the wetting phase.

• 3 – Killough’s hysteresis model used for the non-wetting phase(s), imbibition (IMBNUM,
see 12.4.7) curve used for the wetting phase.

• 4 – Killough’s hysteresis model used for both wetting and non-wetting phases.

• 5 – Carlson’s non-wetting model for gas and water phases, drainage (SATNUM,
see 12.4.3) curve used for the wetting phase.

• 6 – Killough’s non-wetting model for the gas and water phases, drainage (SATNUM,
see 12.4.3) curve used for the wetting phase.

• 7 – Killough’s hysteresis model used for the non-wetting gas and water phases and the
wetting oil phase.

• 8 – Jargon’s hysteresis model used for the non-wetting phase, drainage (SATNUM,
see 12.4.3) curve used for the wetting phase.

• 9 – Jargon’s hysteresis model used for the non-wetting phase, imbibition (IMBNUM,
see 12.4.7) curve used for the wetting phase.

• -1 – Only equilibration option. The model is equilibrated using the drainage curve
(SATNUM, see 12.4.3). The simulation uses the imbibition curve (IMBNUM, see 12.4.7).

The relationship W > O (water–wet system) is used if second parameters of keyword

EHYSTR (see 12.6.67) is equal to 0, 1, 2, 3, 4, 8 and 9. If it is set equal to 5, 6 and 7 the
relationship O > W (oil–wet system) is used.

For calculation of relative permeability krG it is always supposed that oil wets gas (i.e.,
O > G). For three-phase model krOG can be calculated specifying the relationship between gas
and oil using the 8-th parameter of keyword EHYSTR (see 12.6.67). If OIL is selected (i.e., oil
is treated as wetting to gas) then the relationship O > G is used, otherwise G > O is applied.
However, if O > W is specified then 8-th parameter of keyword EHYSTR (see 12.6.67) is
ignored and it is assumed that O > G.

Generally, initial value of relative permeability is taken from the drainage curve. Except
the case when O > W in water-oil system, in this case initial value of relative permeability is
taken from the imbibition curve. For equilibrating it is always used the drainage curve (SAT-
NUM, see 12.4.3).

The following models of relative permeability hysteresis can be implemented by HYS-

TKRW(R) / HYSTKROW(R) / HYSTKRG(R) / HYSTKROG(R) (see 12.6.71) keywords:

2.7.1. Implementing the hysteresis option 88

 19.1

• Killough’s hysteresis model – parameter KILLOUGH.

• Modified Killough’s hysteresis model – parameter KILLOUGH_MOD.

• Carlson’s hysteresis model – parameter CARLSON.

• Analytical Carlson’s hysteresis model – parameter CARLSON_A.

• Jargon’s hysteresis model – parameter JARGON.

If hysteresis is used (option HYSTER in SATOPTS, see 12.1.75) 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.75):
• 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 IMBNUMX (see 12.4.7), IMBNUMY (see 12.4.7), IMBNUMZ, see 12.4.7). 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 ot from I to I+1. (in this case DIRECT must also 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).
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.60);

• 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.60);

• IKRW – maximal water relative permeability (for drainage process this value is specified
via the keyword KRW, see 12.6.59);

• IKRWR – water relative permeability at the residual oil (of residual gas in gas-water sys-
tem) (for drainage process this value is specified via the keyword KRWR, see 12.6.59);

• IKRO – maximal oil relative permeability (for drainage process this value is specified
via the keyword KRO, see 12.6.58);

• IKRORG – oil relative permeability at the critical gas saturation (for drainage process
this value is specified via the keyword KRORG, see 12.6.58);

2.7.1. Implementing the hysteresis option 89

 19.1

• IKRORW – oil relative permeability at the critical water saturation (for drainage process
this value is specified via the keyword KRORW, see 12.6.58).

For imbibition process the saturation end points are:

• ISGL (see 12.6.35) – minimal (connate) gas saturation (for drainage process this value
is specified via the keyword SGL, see 12.6.28);

• ISGCR (see 12.6.35) – critical gas saturation (for drainage process this value is specified
via the keyword SGCR, see 12.6.30);

• ISGU (see 12.6.35) – maximal gas saturation (for drainage process this value is specified
via the keyword SGU, see 12.6.34);

• ISWL (see 12.6.35) – minimal (connate) water saturation (for drainage process this value
is specified via the keyword SWL, see 12.6.26);

• ISWLPC (see 12.6.35) – 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.27);

• ISWCR (see 12.6.35) – critical water saturation (for drainage process this value is spec-
ified via the keyword SWCR, see 12.6.29);

• ISWU (see 12.6.35) – maximal water saturation (for drainage process this value is
specified via the keyword SWU, see 12.6.33);

• ISOGCR (see 12.6.35) – critical oil saturation in oil-gas system (for drainage process
this value is specified via the keyword SOGCR, see 12.6.32);

• ISOWCR (see 12.6.35) – critical oil saturation in oil-water system (for drainage process
this value is specified via the keyword SOWCR, see 12.6.31).

For the simplicity we suppose that in all formulas the argument of relative permeabilities
is the saturation of non-wetting phase. Arguments can be recalculated in terms of wetting
phase, for example, in the water-oil system (W > O) the saturation of non-wetting phase SO
corresponds to SW = 1 − SO − SGl .
For the correct construction of scanning curve the drainage and imbibition curves should
coincide at maximum saturation point of non-wetting phase Snmax . One of the curves should lie
below another one, i.e. drainage and imbibition curves can not intersect each other. Moreover,
the following condition should be fulfilled:

Sncrd ≤ Sncri ≤ Snmax

where

• Snmax is the maximum saturation point of non-wetting phase;

2.7.1. Implementing the hysteresis option 90

 19.1

• Sncrd is the maximum saturation of non-wetting phase at which the relative permeability
of drainage curve is equal to zero;

• Sncri is the maximum saturation of non-wetting phase at which the relative permeability
of imbibition curve is equal to zero;

• Sncrt is the critical saturation of non-wetting phase for scanning curve. It depends on
saturation Shy at which the drainage process switches to imbibition one. The way of its
calculation depends on the selected hysteresis model (e.g., Carlson’s model, Killough’s
model, Jargon’s model).

Drainage option (DRAINAGE, see 12.6.69) can be used in hysteresis. In this case k r values
obtained in the hysteresis option should lie on or below drainage curve.

2.7.1. Implementing the hysteresis option 91

 19.1

2.7.2. Relative permeability hysteresis in the non-wetting phase

Examples of hysteresis of relative permeabilities krOW (W > O) and krG (O > G) in the
non-wetting phase are shown in figures 7 and 8 respectively.
If the saturation of non-wetting phase Sn monotonically increases from Sncrd (point A)
to the maximum saturation Snmax (point B) then the relative premiability follows the curve
AB (drainage curve). If after that Sn starts do decrease then the permeability varies along the
curve BC (imbibition curve).
If a drainage switches to imbibition at some intermediate point D of curve AB then
the saturation Shy at point D is saved and an scanning curve DE is constructed, thus the
permeability follows this curve.
If an imbibition switches to the drainage process at some intermediate point of curve DE
then the permeability varies along the curve DE (scanning curve) until reaches the saturation
value Shy (point D). If after that the drainage process continues then the permeability will run
along the curve DB. If the saturation Sn decreases at point E then the permeability will run
along the curve EA.

Figure 7. Hysteresis of relative permeability krOW (W > O) in the non-wetting phase

2.7.2. Relative permeability hysteresis in the non-wetting phase 92

 19.1

Figure 8. Hysteresis of relative permeability krG (O > G) in the non-wetting phase

For non-wetting phase there are several hysteresis models implemented for the scanning
curve construction:
• Killough’s model.
To construct a scanning curve the saturation at end–point of scanning curve (trapped
saturation) is calculated as:
Shy − Sncrd
Sncrt (Shy ) = Sncrd + , (2.59)
1 +C(Shy − Sncrd )
where
1 1
C= − . (2.60)
Sncri − Sncrd Snmax − Sncrd
In order to avoid unphysical behaviour at low values of Shy the modified Killough’s
model (KILLOUGH_MOD) is implemented:
Shy − Sncrd
Sncrt (Shy ) = Sncrd + , (2.61)
A +C(Shy − Sncrd )

2.7.2. Relative permeability hysteresis in the non-wetting phase 93

 19.1

where

A = 1 + α Snmax − Shy , (2.62)
α can be specified by 4-th parameter of keyword EHYSTR (see 12.6.67) or by
TRAP_PARAM parameter of HYSTKRW(R) / HYSTKROW(R) / HYSTKRG(R) /
HYSTKROG(R) (see 12.6.71) keywords.
If α = 0 non-modified Killough’s model will be applied.

To calculate the relative permeability along the scanning curve the following formula is
used:
scan drain kimbib (Snorm (Sn , Shy ))
k (Sn , Shy ) = k (Shy ) ,
kdrain (Snmax )
where
(Sn − Sncrt )(Snmax − Sncri )
Snorm (Sn , Shy ) = + Sncri , (2.63)
(Shy − Sncrt )
The curvature of the scanning curve can be modified with a use of Killough’s saturation-
interpolation:
 βn
scan drain Sn − Sncrt
k (Sn ) = k (Shy ) (2.64)
Shy − Sncrt

– βn is the exponent for non-wetting phase. Its value can be specified via the pa-
rameter NONWET_POW of HYSTKRW(R) / HYSTKROW(R) / HYSTKRG(R) /
HYSTKROG(R) (see 12.6.71) keywords.

Notice that Sncrt is always located between Sncrd and Sncri (i.e., Sncrd ≤ Sncri ). But if
the drainage and imbibition curves coincides, it is required the scanning curve coincide
with them only at its end points (i.e., at Shy and Sncrd = Sncri ).
• Carlson’s model.
To construct a scanning curve an imbibition curve is used. The imbibition curve is
shifted in parallel untill crossing the drainage curve at point Shy .
• Analytical Carlson’s model.
This model can be defined only via HYSTKRW(R) / HYSTKROW(R) / HYSTKRG(R)
/ HYSTKROG(R) (see 12.6.71) keywords.
To construct a scanning curve a drainage curve and critical imbibition saturation are
used. The scanning curve is constructed with the following assumption:

K scan (Sn ) = K drain (Sn f ) (2.65)

In order to define the value of Sn f , the trapped saturation Sncrt (Shy ) is calculated via
equation 2.59.
Then, the Sn f value is calculated via the following equations:

2.7.2. Relative permeability hysteresis in the non-wetting phase 94

 19.1

– If α > 0 in equation 2.62:

 
  s 2
1−A 1−A 4A
Sn f (Sn ) = Sncrd +0.5  Sn − Sncrt + + Sn − Sncrt + + (Sn − Sncrt )
C C C

– If α = 0 in equation 2.62:
" r #
4
Sn f (Sn ) = Sncrd + 0.5 (Sn − Sncrt ) + (Sn − Sncrt )2 + (Sn − Sncrt )
C

All scanning curves conctructed via Analytical Carlson’s method will be paralell to each
other.

• Jargon’s model.
The relative permeability along the scanning curve is calculated using the following
formula:
scan kimbib (Snorm (Sn , Shy ))
k (Sn , Shy ) = drain × kdrain (Sn ),
k (Snorm (Sn , Shy ))
where
(Snmax − Sncrd )
Snorm (Sn , Shy ) = Sncrd + (Sn − Sncrd ) × .
(Shy − Sncrd )
Notice that the critical point of scanning curve is calculated using the formula:

(Sncri − Sncrd ) · (Shy − Sncrd )

Sncrt (Shy ) = Sncrd + .
(Snmax − Sncrd )

2.7.2. Relative permeability hysteresis in the non-wetting phase 95

 19.1

2.7.3. Relative permeability hysteresis in the wetting phase

Examples of hysteresis of relative permeabilities krW (W > O) and krOG (O > G) in the
wetting phase are shown in figures 9 and 10, respectively.

Figure 9. Hysteresis of relative permeability krW (W > O) in the wetting phase

To construct a scanning curve the Killough’s model is used. Saturations Sncrt (Shy ) and
Snorm (Sn , Shy ) are calculated using the formulas (2.59) and (2.63), respectively. The relative
permeability at end–point of scanning curve is calculated as:
 
scan drain imbib drain
k (Sncrt (Shy )) = k (Sncrt (Shy )) + k (Sncri ) − k (Sncri ) ×

Sncrt (Shy ) − Sncrd βwet

 
× (2.66)
Sncri − Sncrd
Where
• βwet is the exponent for wetting phase. Its value can be specified via the parameter
WET_POW of HYSTKRW(R) / HYSTKROW(R) / HYSTKRG(R) / HYSTKROG(R)
(see 12.6.71).

2.7.3. Relative permeability hysteresis in the wetting phase 96

 19.1

Figure 10. Hysteresis of relative permeability krOG (O > G) in the wetting phase

The relative permeability in the wetting phase is calculated as:

!
k imbib (S (S , S ))  
norm n hy
kscan (Sn , Shy ) = kdrain (Shy ) + × k scan
(S ncrt (Shy )) − k drain
(S hy ) .
kimbib (Sncri )

2.7.3. Relative permeability hysteresis in the wetting phase 97

 19.1

2.7.4. Capillary pressure hysteresis

The primary drainage and imbibition curves should be available. To construct a scanning curve
the Killough’s hysteresis model is used [29].
Water capillary pressure
The distribution of capillary pressure as function of water saturation in water-oil system is
shown in figure 11.

Figure 11. Water capillary pressure hysteresis

As can be seen in figure 11 when a water saturation decreases from Swcrd to the minimum
water saturation Swl the capillary pressure varies along a drainage curve (curve AB). If a water
saturation increases starting from point B to Swcri then the capillary pressure will follow the
imbibition curve (curve BC ). If the drainage process switches to the imbibition process at
some intermediate point D of curve AB then the saturation value Shy at this switching point

2.7.4. Capillary pressure hysteresis 98

 19.1

is saved and Swcrt is calculated, then a scanning curve is constructed. If the process goes back
to a drainage one at some intermediate point of scanning curve DE then the capillary pressure
follows the curve DE untill the saturation reches Shy (point D).
A scanning curve is weighted average of drainage and imbibition curves and calculated
as:
scan drain imbib drain
Pcow (Sw , Shy ) = Pcow (Sw ) + F(Sw , Shy ) · (Pcow (Sw ) − Pcow (Sw )),
   
1 1 1 1
F(Sw , Shy ) = − / − ,
Sw − Shy + E E Swma − Shy + E E
where

• E is the curvature, which can be specified by the 1-st parameter of keyword EHYSTR
(see 12.6.67) or by the EPS parameter of HYSTPCW(R) / HYSTPCG(R) (see 12.6.73)
keywords.
By default E = 0.1.

• Shy is the water saturation. A drainage process switches to imbibition process at this
value.

• Swma = 1 − Sowcrt (Shy = 1 − Somax ) is the maximum possible water saturation. Notice
that calculation of Sowcrt depends on the selected relative permeabilities hysteresis
model used for construction of scanning curve (e.g., Carlson’s model, Killough’s model,
Jargon’s model).

Gas capillary pressure

The distribution of capillary pressure as function of gas saturation in oil-gas system is shown
in figure 11.
A scanning curve is weighted average of drainage and imbibition curves and calculated
as:

scan drain imbib drain

Pcog (Sg , Shy ) = Pcog (Sg ) + F(Sg , Shy ) · (Pcog (Sg ) − Pcog (Sg )),
   
1 1 1 1
F(Sg , Shy ) = − / − ,
Shy − Sg + E E Shy − Sgcrt + E E
where

• E is the curvature, which can be specified by the 1-st parameter of keyword EHYSTR
(see 12.6.67) or by the EPS parameter of HYSTPCW(R) / HYSTPCG(R) (see 12.6.73)
keywords.
By default E = 0.1.

• Shy is the gas saturation. A drainage process switches to imbibition process at this value.

• Sgcrt (Shy = Sghy ) is the minimum possible gas saturation. Notice that calculation of Sgcrt
depends on the selected relative permeabilities hysteresis model used for construction
of scanning curve (e.g., Carlson’s model, Killough’s model, Jargon’s model).

2.7.4. Capillary pressure hysteresis 99

 19.1

Figure 12. Gas capillary pressure hysteresis

2.7.5. Hysteresis in three-phase system

If the first Stone’s model is used then in case of hysteresis the saturation SOm is calculated as:
imbib drain imbib
SOm = SOm + F · (SOm − SOm ), (2.67)

where SOmdrain is the saturation calculated using the drainage curve and Simbib is the saturation
Om
calculated using the imbibition curve.

F = Fsw · Fw + (1 − Fsw ) · Fg , (2.68)

Sw − Swl
Fsw = scan
, (2.69)
1 − Swl − Sowcr

2.7.5. Hysteresis in three-phase system 100

 19.1

imbib − Sscan
Sowcr owcr
Fw = imbib − Sdrain
, (2.70)
Sowcr owcr
imbib − Sscan
Sogcr ogcr
Fg = imbib drain
, (2.71)
Sogcr − Sogcr
where

• Sowcr
scan is the critical point of oil scanning curve in the water-oil system. The way of
scan depends on the selected hysteresis model (e.g., Carlson’s model,
calculation of Sowcr
Killough’s model, Jargon’s model).

• Sogcr
scan is the critical point of oil scanning curve in the oil-gas system. The way of
scan depends on the selected hysteresis model (e.g., Carlson’s model,
calculation of Sogcr
Killough’s model, Jargon’s model).

2.7.6. Hysteresis definition in IM/GE/ST format

There are several avaliable hysteresis models in IM/GE/ST format:

• Analytical Carlson’s model.

• Killough’s model.

• Modified Killough’s model.

The detailed description of these options is provided in the previous sections.

The hysteresis option utilizes the same calculation algorithms as in the E1/E1 format.
However, unlike E1/E1 formulation, in IM/GE/ST format it is possible to assign different
hysteresis models for separate saturation regions (defined by RPT (see 13.6.2) keyword).
The algorithms for relative permeability hysteresis calculations are described in Relative
permeability hysteresis in the non-wetting phase and Relative permeability hysteresis in the
non-wetting phase sections.

The algorithms for capillary pressure hysteresis calculations are described in Capillary
pressure hysteresis section.

In order to implement Killough’s or modified Killough’s correlation correlations in Oil-

Water systems, Oil-Water Imbibition table must be provided via SWTI (see 13.6.42) keyword.

In order to implement Capillary Pressure hysteresis option, the Imbibition Capillary Pres-
sure table must be provided in the 5th column of SWT (see 13.6.5), SLT (see 13.6.6), SGT
(see 13.6.7) keywords.

The hysteresis option can be defined IM/GE/ST formats via the following keywords:

2.7.6. Hysteresis definition in IM/GE/ST format 101

 19.1

I. Black Oil cases (IM format):

1. Keywords defining Relative Permeability Hysteresis:

• HYSKRO (see 13.6.43) – Oil Relative Permeability Hysteresis in Oil-Water sys-

tems.
– If Killough’s or modified Killough’s correlation is used, Oil-Water Imbibition
table must be provided via SWTI (see 13.6.42) keyword.
– Additionally, the maximum residual oil saturation in Imbibition process can
de specified via SORMAX (see 13.6.44) keyword.
• HYSKRW (see 13.6.45) – Water Relative Permeability Hysteresis in Oil-Water
systems.
– If Killough’s or modified Killough’s correlation is used, Oil-Water Imbibition
table must be provided via SWTI (see 13.6.42) keyword.
• HYSKRG (see 13.6.46) – Gas Relative Permeability Hysteresis.

2. Keywords defining Capillary Pressure Hysteresis:

• EPSPC (see 13.6.40) – Oil-Water Capillary Pressure Hysteresis.

– If this option is used, the 5th column in SWT (see 13.6.5) table must be
specified.
• EPSPCG (see 13.6.41) – Gas-Oil Capillary Pressure Hysteresis.
– If this option is used, the 5th column in SLT (see 13.6.6) or SGT (see 13.6.7)
table must be specified.

II. Compositionall cases (GE format):

1. Keywords defining Relative Permeability Hysteresis:

• HYSKROW (see 13.6.47) – Oil Relative Permeability Hysteresis in Oil-Water sys-

tems.
• HYSKROG (see 13.6.48) – Oil Relative Permeability Hysteresis in Gas-Oil sys-
tems.
• HYSKRG (see 13.6.46) – Gas Relative Permeability Hysteresis in Gas-Oil systems.

2. Keywords defining Capillary Pressure Hysteresis:

• EPSPC (see 13.6.40) – Oil-Water Capillary Pressure Hysteresis.

– If this option is used, the 5th column in SWT (see 13.6.5) table must be
specified.

2.7.6. Hysteresis definition in IM/GE/ST format 102

 19.1

III. Thermal cases (ST format):

1. Keywords defining Relative Permeability Hysteresis:

• HYS_KRO (see 13.6.49) – Oil Relative Permeability Hysteresis and optionally,
Water Relative Permeability Hysteresis in water-wet systems.
• HYS_KRG (see 13.6.50) – Gas Relative Permeability Hysteresis.
2. Keywords defining Capillary Pressure Hysteresis:
• HYS_PCOW (see 13.6.51) – Oil-Water Capillary Pressure Hysteresis.
• HYS_PCOG (see 13.6.52) – Gas-Oil Capillary Pressure Hysteresis.
• HYS_LEVEL (see 13.6.53) – The rebound path of scanning curves in Capillary
Pressure Hysteresis.

2.8. PVT properties

2.8.1. Phase viscosity
For black oil model phase viscosity µP = µP (pP ) is a 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).
Also the approximations obtained from PVT properties by correlation analysis may be used
(2.9. Oil Standing’s correlations, 2.10. Gas Standing’s correlations). Keywords STANDO
(see 12.5.11), STANDG (see 12.5.12).

2.8.2. Phase formation volume factor

Phase formation volume factor BP = BP (pP ) is a 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 (2.9. Oil Standing’s correlations, 2.10. Gas Standing’s
correlations).

2.8.3. Phase molar density

for black oil model phase molar density is always function of BP - formation volume factor.
For water component it is calculated as
ξW,SC
ξW = (2.72)
BW

2.8. PVT properties 103

 19.1

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.73)
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.74)
BO BG

Here ξP,SC is molar density of phase P in standard conditions.

2.8.4. Phase mass density

For black oil model 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.33), GRAV-
ITY, see 12.5.34):

• ρO,SC is the oil density at surface condition

• ρG,SC is the gas density at surface condition

• ρW,SC is the 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 =
BW
RG,O ρG,SC + ρO,SC
ρO = (2.75)
BO
RO,G ρO,SC + ρG,SC
ρG =
BG

2.8.5. 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.19.115) sets maximum rate of increase of solution gas-oil
ratio (sm3 /sm3 /day).

2.8.4. Phase mass density 104

 19.1

The keyword VAPPARS (see 12.19.116) controls oil vaporization by reducing the maxi-
mum allowed values of RG,O in a block.

For black-oil models the following extanesions of the keyword DRSDT (see 12.19.115)
can be used:

1. Set maximum rate of increase of solution gas-oil ratio as a function of pressure

(keyword DRSDTVP, see 12.19.117).
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.

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 na-
ture of the system relaxation (keyword DRSDTVPE, see 12.19.118).
The relaxation process of the physical value f in the first approximation can be de-
scribed 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 dynamics.
Analogously for Rs relaxation equation is:
dRs
= −D(∆p)(Rs − R∗s (p))
dt
• D – parameter characterizing the relaxation rate of the gas-oil ratio in relative
units,
• R∗s – equilibrium value of gas-oil ratio.

2.8.5. Solubility of gas component into oil phase 105

 19.1

2.8.6. 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.19.119) sets maximum rate of increase of vapor oil-gas ratio.

The keyword VAPPARS (see 12.19.116) controls oil vaporization by reducing the maxi-
mum allowed values of RO,G in a block.

2.8.7. Keywords to set PVT

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 compress-
ibility 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.13) — if dead oil is used to model oil with a constant dissolved gas
concentration;

• RSCONSTT (see 12.5.14) — if dead oil is used to model oil with a constant dissolved 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.15) — if dry gas is used to model gas with a constant vaporized oil
concentration;

• RVCONSTT (see 12.5.16) — if dry gas is used to model gas with a constant vaporized oil
concentration (vaporized oil concentration may be different in different PVT regions);

• PVTW (see 12.5.5) — water;

• PVTOPTS (see 12.5.36) — sets the method of PVT properties interpolation.

The keywords specifying initial pressures and saturations (see 12.16. Initialization section):

2.8.6. Vaporisation of oil component into gas phase 106

 19.1

• RV (see 12.16.38) — initial oil vaporization with wet gas (wet gas);

• PDEW (see 12.16.39) — initial dew point pressure (wet gas);

• RS (see 12.16.37) — initial gas solution in oil (live oil);

• PBUB (see 12.16.36) — 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.16.38), PDEW (see 12.16.39)

• group 2:
RS (see 12.16.37), PBUB (see 12.16.36)

2.8.8. 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 the PVT tables that specify oil properties
are defined for multiple values of API density over a particular range. Then at every time step
for every grid block, based on the local oil API density value, two tables with the closest API
values are found. Oil properties (Pbub , Bo , µo ) are determined via the known Rs and pressure
for both these tables and linearly interpolated for the intermediate API values.
Supported keywords are listed below.
E1 format
• Option is enabled by the keyword API (see 12.1.66).

• PVT properties are specified via ordinary keywords (PVTO (see 12.5.4), PVCO
(see 12.5.6), etc).

• The values of oil API gravity are specified via the keyword GRAVITY (see 12.5.34) (or
is calculated from the density specified in DENSITY, see 12.5.33).

• Maximum number of oil PVT tables groups if the API tracking option is enabled –
APIGROUP (see 12.5.35).

• APIVD (see 12.16.18) specifies tables of oil API density versus depth for each equilib-
rium region.

• OILAPI (see 12.16.19) specifies initial oil API values in each grid block (when initial
conditions are set via enumeration via the keywords SWAT (see 12.16.14), PRESSURE
(see 12.16.12) etc.);

• 3-rd parameter of VISCREF (see 12.15.52) specifies reference API gravity.

IM format

2.8.8. API tracking 107

 19.1

• Option is enabled by the API-INT option of the keyword MODEL (see 13.5.4).

• Gas PVT properties are specified via the keyword PVTAPI (see 13.5.17).

• PVT properties of saturated oil are specified via the keyword APIGRAD (see 13.5.18).

• PVT properties of undersaturated oil are specified via the keywords BOTAPI
(see 13.5.19) and VOTAPI (see 13.5.20).

• API values as a function of depth are specified via the keyword APIT (see 13.7.22).

• API values per each grid block are specified via the keyword API (see 13.7.21).

Fully implicit method is used for API calculation by default. It can be changed to explicit
via the keyword TRACEROPTS (see 12.7.12).

2.9. Oil Standing’s correlations

Bubble-Point Pressure (1981, [7, p. 87], [8, p. 8-9]):
 0.83 !
Rsb
pb = 1.2548 · 100.00091T(F) −0.0125API − 1.4 (2.76)
0.1781 · γG

Solution Gas-Oil-Ratio (GOR) (1981, [7, p. 78-79], [8, p. 8-9]):

 1.2048
Rs = 0.1781 · γG (0.7971 · p + 1.4) · 100.0125API−0.00091T(F) (2.77)

where
141.5
API = − 131.5
γO
Parameters:

• pb is the bubble-point pressure (barsa);

• p is the system pressure (barsa);

• Rs is the gas solubility (sm3 /sm3 );

• Rsb is the gas solubility at bubble point (sm3 /sm3 );

• T(F) is the system temperature ( ◦ F);

• γG is the specific gravity of the gas (taken from the keyword GRAVITY (see 12.5.34) or
calculated from the keyword DENSITY, see 12.5.33);

• γO is the specific gravity of the stock-tank oil (taken from the keyword GRAVITY
(see 12.5.34) or calculated from the keyword DENSITY, see 12.5.33).

2.9. Oil Standing’s correlations 108

 19.1

Standing’s correlation should be used with caution if non-hydrocarbon components are

known to be present in the system.

It should be noted that Standing’s equation is valid for applications at and below the
bubble-point pressure of the crude oil.

2.9.1. 2-phase water-oil model. Dead Oil

The case where options WATER (see 12.1.58) and OIL (see 12.1.56) 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.78)
API4.53 T(R) − 260

where

• a = 10(0.43+8.33/API)

• T(R) is the system temperature ( ◦ R);

2.9.2. 3-phase model. Live Oil

The case where options WATER (see 12.1.58), OIL (see 12.1.56), GAS (see 12.1.57), DISGAS
(see 12.1.60) are used.
There is no Standing’s correlations for VAPOIL (see 12.1.59) case.
Gas saturated (below bubble point pressure)
The keyword STANDO (see 12.5.11) specifies 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
BOb = 0.9759 + 0.000120 · 5.614583 · Rs + 1.25 · T(F) (2.79)
γO

Viscosity: [7, p. 117-118]

µOb = 10a (µOd )b (2.80)
where

a = 5.614583 · Rs · [2.2 × 10−7 · 5.614583 · Rs − 7.4 × 10−4 ]

2.9.1. 2-phase water-oil model. Dead Oil 109

 19.1

0.68 0.25 0.062

b= + d +
10c 10 10e
c = 8.62 × 10−5 · 5.614583 · Rs
d = 1.1 × 10−3 · 5.614583 · Rs
e = 3.74 × 10−3 · 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.11) specifies the following parameters: Rsb or pb , T ,
[cO ] – isothermal compressibility coefficient.
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.81)

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.79);
• 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.82)

where

A = 4.1646 · 10−7 (5.614583 · Rsb )0.69357 γG0.1885 · (API)0.3272 T(F)

0.6729

Viscosity: [9, p. 241]

1.6 0.56
µOu = µOb + 0.001 · 14.50377 · (p − pb ) · [0.024µOb + 0.038µOb ] (2.83)

where

2.9.2. 3-phase model. Live Oil 110

 19.1

• µOu – undersaturated oil viscosity (cp);

• µOb – viscosity of the oil at the bubble-point pressure (cp) (is calculated according to
the formula 2.80).

2.10. Gas Standing’s correlations

The keyword STANDG (see 12.5.12) 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.10.1. Gas Formation Volume Factor

[7, p. 65-66]
z · T(R)
BG = 0.02827 (2.84)
14.50377 · p
where

• T(R) is the system temperature ( ◦ R);

• p is the initial reservoir pressure (Barsa).

2.10.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:
"   #
−4 0.06243745ρG Y
µG = 10 K exp X (2.85)
62.43
with
1.5
(9.379 + 0.0160Ma ) T(R)
K=
209.2 + 19.26Ma + T(R)
986.4
X = 3.448 + + 0.01009 Ma
T(R)

Y = 2.4 − 0.2 X

2.10. Gas Standing’s correlations 111

 19.1

where
ρG is the gas density at reservoir pressure and temperature (kg/m3 );
Ma is the apparent molecular weight of the gas mixture;

and
1 0.0689 · p · Ma
ρG =
0.06243745 10.73z · T(R)

Ma = 28.96γG
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.11. Capillary pressures

2.11.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.

It can be set in the table form (SGOF (see 12.6.2) or SGFN, see 12.6.14) or calculated via
correlations (COREYGO (see 12.6.4), LETGO, see 12.6.9).

2.11.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.

It can be set in the table form (SWOF (see 12.6.1) or SWFN, see 12.6.13) or calculated
via correlations (COREYWO (see 12.6.3), LETWO, see 12.6.8).

2.11.3. Gas-water capillary pressure

Gas-water capillary pressure PcGW = PcGW (SW ) is user input data array defined in a number
of SW points and interpolated for other points.

It can be set in the table form (SWFN, see 12.6.13) or calculated via correlations
(COREYWG (see 12.6.5), LETWG, see 12.6.10).

2.11.4. 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):

2.11. Capillary pressures 112

 19.1

• Specification of critical saturation end points for each grid block (keywords PCW
(see 12.6.62), PCG, see 12.6.63).

• Specification of initial water saturation for each grid block (keyword SWATINIT,
see 12.6.65). When SWATINIT (see 12.6.65) is used, the maximum capillary pressure
array PCW is generated. Hence, if the keyword SWATINIT (see 12.6.65) is specified
then values specified by PCW (see 12.6.62) will be ignored.

• Specification of critical saturation end points as depth function (keywords ENPCVD,

see 12.6.39).

• Specification of critical saturation end points as temperature function (keywords EN-

PCVT (see 12.15.87) - only for thermo-compositional model.

• Specification of critical saturation end points as composition function (ENPCVC

(see 12.14.56) - only for compositional model.

Possible combinations can be specified using 5-th parameter of the keyword ENDSCALE
(see 12.1.136).

If end point scaling is selected by ENDSCALE (see 12.1.136), 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 formulae
below.
Let’s first introduce notations

• SW , SG are block water and gas saturations,

• 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 max , SGmax are maximal values of water (and gas) saturation in SWOF (see 12.6.1)
(SGOF, see 12.6.2),

• SWL (see 12.6.26), SGL (see 12.6.28) are user defined values of connate water (and
gas) saturation in current block,

• SWU (see 12.6.33), SGU (see 12.6.34) are user defined values of maximal water (and
gas) saturation in current block,

• PCW (see 12.6.62), PCG (see 12.6.63) are user defined arrays of maximum capillary
pressures,

• 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)

• S̃W , S̃G are scaled block water and gas saturations.

2.11.4. Capillary pressure end point scaling 113

 19.1

Saturations are scaled as

(SW − SW L)(SW max − SW co )
S̃W = SW co +
SWU − SW L (2.86)
(SG − SGL)(SGmax − SG co )
S̃G = SG co +
SGU − SGL
Appropriate capillary pressures are calculated as
PCW
PcOW (SW ) = PcOW (S̃W )(table) ∗
PcOW max (table)
(2.87)
PCG
PcOG (SG ) = PcOG (S̃G )(table) ∗
PcOG max (table)

2.11.5. Capillary pressure calculation according to Leverett J-function

If end point scaling is selected by ENDSCALE (see 12.1.136), capillary pressures may be
calculated according to Leverett J-function model. Phase capillary pressures are scaled if first
argument of JFUNC (see 12.2.63) indicates scaling is to be performed. (This keyword defines
parameters for whole reservoir. The keyword JFUNCR (see 12.2.64) can be used to specify
data separetely for each saturation region.)

Scaling formulae are the following:

PcOW (SW ) = JW (SW )(table) ∗ Jmult W

(2.88)
PcOG (SG ) = JG (SG )(table) ∗ Jmult G

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 )β ∗CONST
(2.89)
Jmult G = STG ∗ (ϕ i, j,k )α /(K i, j,k )β ∗CONST
where

• STW – oil-water surface tension, second argument of keyword JFUNC (see 12.2.63);

• STG – oil-gas surface tension, third argument of keyword JFUNC (see 12.2.63);

• ϕ i, j,k – porosity in grid block;

• K i, j,k – permeability, calculated according to one of the following methods

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

2.11.5. Capillary pressure calculation according to Leverett J-function 114

 19.1

i, j,k
– Z: K i, j,k = kzz ;

the method is selected by 6-th parameter of keyword JFUNC (see 12.2.63).

Or instead of this parameter one can specify the special permeability value used for
J-function computation (JFPERM, see 12.2.65). If this keyword is specified then perme-
ability direction (the 6-th parameter of JFUNC, see 12.2.63) is ignored.

• α – exponent for porosity, fourth argument of keyword JFUNC (see 12.2.63);

• β – exponent for permeability, fifth argument of keyword JFUNC (see 12.2.63);

• CONST – constant depending of units system:

– 0.318316 (METRIC: pressure barsa, permeability mD);

– 4.61678 (FIELD: pressure psia, permeability mD);
– 0.314153 (LAB: pressure atma, permeability mD).

2.12. Fluid velocities

In general, fluid velocities in the porous media are not calculated explicitly for use in the
physical model except in certain limited contexts, including:

• Velocity-dependent relative permeabilities;

• Output of velocities as a grid property (required by VELOCITY and the related mnemon-
ics of the keyword RPTRST, see 12.16.5).

The fluid velocities between two blocks are calculated as follows:

Fo
Uo =
A · ϕ · (So − SoWCR )
Fg
Ug = (2.90)
A · ϕ · (Sg − SgCR )
Fw
Uw =
A · ϕ · (Sw − SwCR )
where

• Fo,g,w are the flow rates of phase (oil, gas, water) measured at reservoir conditions;

• A is the flow area between the two blocks;

• ϕ is the porosity;

• So,g,w are the phase saturations for oil, gas, and water;

• SgCR and SwCR are the critical gas and water saturations;

• SoWCR is the critical oil-to-water saturation.

2.12. Fluid velocities 115

 19.1

All grid parameters refer to the upstream of the two blocks.

The velocities of fluids in the wellbore and pipes are an entirely different matter. Their
derivation and usage is covered in VFP tables generation.

2.13. Inflow from aquifer

tNavigator supports the following types of aquifers:
• numerical aquifer.
Is set via the keywords AQUCON (see 12.17.14), AQUNUM (see 12.17.13);

• constant-flux aquifer (analytic aquifer).

Is set via the keywords AQUFLUX (see 12.17.2), AQUANCON (see 12.17.11), AQAN-
CONL (see 12.17.12);
A water flow rate from aquifer is calculating the following way:

Qai = Fa · Ai · m (2.91)

where:

– Qai – inflow rate from the aquifer to block i;

– Fa – the aquifer constant flux, entered by the user (parameter 2 of AQUFLUX,
see 12.17.2);
– Ai – the area of the connection of block i;
– m – influx multiplier (parameter 10 of the keyword AQUANCON (see 12.17.11)
or parameter 11 of AQANCONL, see 12.17.12).

• Fetkovich aquifer (analytic aquifer).

Is set via the keywords AQUFETP (see 12.17.6), AQUFET (see 12.17.4), AQUANCON
(see 12.17.11), AQANCONL (see 12.17.12). The keyword HMMLFTAQ (see 12.17.17)
defines multipliers for Fetkovich aquifer parameters. These multipliers can be used for
history matching;
A water flow rate from aquifer is calculating the following way:
d
Qai = (Wai ) = Jαi (pa + pc − pi + ρg(di − da )) (2.92)
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;

2.13. Inflow from aquifer 116

 19.1

– pc - water pressure in block i;

– pi - capillary pressure;
– ρ - water density in the aquifer;
– di - depth of block i;
– da - aquifer datum depth.
mi A i
α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.17.10), AQUANCON (see 12.17.11), AQAN-
CONL (see 12.17.12), AQUCT (see 12.17.9). The keyword HMMLCTAQ (see 12.17.16)
defines multipliers for Carter-Tracy aquifer parameters. These multipliers can be used
for history matching;
The average inflow rate from the aquifer to a grid block i for timestep ∆t is calculated
by the following formula:
Qai = αi (a − b∆p) (2.93)
where:

– ∆p - change of pressure p for timestep ∆p: p(t + ∆t) − p(t);

– αi - is the area fraction for each connection block;
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.94)
Tc PID (t + ∆t)D − tD PID0 (t + ∆t)D

The number b is calculated by the following formula:

β
b= (2.95)
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 .

2.13. Inflow from aquifer 117

 19.1

Time constant Tc is defined by the following way:

µW ϕCt ro2
Tc = (2.96)
ka c1

where:

– ka - aquifer permeability;
– ϕ - aquifer porosity;
– µW - water viscosity in the aquifer;
– Ct - total Aquifer 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 hΘϕCt ro2 (2.97)

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.98)
β

where:

– pa0 - initial pressure of water in the aquifer;

– p - average water pressure on the aquifer boundary;
– Qa - aquifer inflow rate.

• Bottom-Drive option for Carter-Tracy aquifer.

This option is an extension of the standard Carter-Tracy aquifer model that enables con-
sideration of gravitational effects in Aquifer zone. It can be activated by BD parameter
of AQUOPTS (see 12.17.5) keyword.

2.13. Inflow from aquifer 118

 19.1

In this case the β coefficient in equations 2.94 and 2.95 will be calculated as follows:
r
Kv 3
β = c3 ΘϕCt r (2.99)
Kh o
where:

– c2 – constant which is equal to 3,1415 (METRIC) or 0,55955 (FIELD);

– Θ – angle subtended by the aquifer boundary from the center of the reservoir,
divided by 360 ◦ ;
– ϕ – Aquifer Porosity;
– Ct – total Aquifer compressibility (rock + water);
– Kv – Aquifer Permeability in vertical direction;
– Kh – Aquifer Permeability in horizontal direction;
– ro - aquifer inner radius;

• constant head/pressure water aquifer.

Is set via the keywords AQUCHWAT (see 12.17.3), AQUANCON (see 12.17.11),
AQANCONL (see 12.17.12).

The water flow rate into a grid block from aquifer is calculated using the formula:
d
Qai = (Gai ) = Jαi [pa + pc − pi + ρg(di − da )] (2.100)
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.

2.13. Inflow from aquifer 119

 19.1

• Semi-Analytical Aquifer.
This aquifer model can be used only in thermal runs for the models in ST format.
The Semi-Analytical Aquifer model can be defined via the keyword AQMETHOD
(see 13.3.17) (parameter *SEMI-ANALYTICAL). The water flow rate into a grid block
from aquifer is calculated using the following correlation:
λ
Qai = ·J (2.101)
α
where:

– Qai – water flow rate into a grid block i from aquifer or vice versa (when the
backflow option is enabled);
– J – aquifer productivity index;
– αi is calculated as follows:
ka
Qai = (2.102)
ϕ µWa Ct
∗ ka – aquifer permeability;
∗ ϕ – aquifer porosity;
∗ µWa – water viscosity in aquifer;
∗ Ct – total aquifer compressibility.
– λ is calculated as follows:
ka
∗ – for water inflow from aquifer to reservoir;
µWa
kkrW
∗ – for water inflow from reservoir to aquifer;
µW
• dimensions for aquifers should be specified via AQUDIMS (see 12.17.1).
Connection of the analytic and semy-analytical aquifers to the reservoir:
• AQUANCON (see 12.17.11), AQANCONL (see 12.17.12) – defines the connection of
the analytic aquifer to the reservoir;
• AQUGP (see 12.17.15) – defines geometry of aquifer connection to reservoir (connect
at the specified depth value, connect to reservoir bottom, to reservoir boundary, different
type of productivity indexes calculation).
The keyword can be used in combination with the keyword DEACDEPT (see 12.2.124)
to deactivate all blocks below the specified depth.
Calculation options for analytic aquifers are set via the keyword AQUOPTS (see 12.17.5).

Brine option is supported for aquifers (BRINE, see 12.1.62) (salt concentration is set via
keywords AQUFETP (see 12.17.6), AQUFET (see 12.17.4), AQUCT, see 12.17.9).

2.13. Inflow from aquifer 120

 19.1

AQANTRC (see 12.17.8) – the keyword specifies initial tracer concentrations for analytic
aquifers (keywords AQUFET (see 12.17.4), AQUFETP (see 12.17.6), AQUCT (see 12.17.9),
AQUFLUX, see 12.17.2).

2.14. Well
2.14.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.103)

where
• MP (pP , SW , SG ) – phase mobility, known, will be defined below, see section 5.6.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.6.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,

2πKmult (t)βc Kh
see 12.19.6), otherwise calculated according to T = , see section 5.6.2.
(ln(r0 /rw ) + s)
Here

– Kmult (t) – multiplier (known defined by WPIMULT (see 12.19.35) or by WPI-

MULTL (see 12.19.36) within local grids)
– βc = const – units conversion factor (known)
– Kh (known) – may be defined by user (COMPDAT, see 12.19.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.6.3
(known)
– r0 is pressure equivalent radius, may be defined by user, COMPDAT (see 12.19.6),
otherwise its approximation depends on the discrete approximation chosen for the
equations (2.1)–(2.4), and will be defined below, see section 5.6.4.
– rw = dw /2 = const – well radius (known, COMPDAT, see 12.19.6)

2.14. Well 121

 19.1

– s = s(x, y, z,t) – skin effect term (known, COMPDAT, see 12.19.6)

In this case source of component c will be equal to

qc = ∑ xc,P ξP QP (p, N) (2.104)

P

where

• xc,P = xc,P (p, N) – moles of component c per mole of phase P,

• ξP = ξP (p, N) – phase molar density, see 2.8.3,

• QP (p, N) – phase rate in reservoir conditions, calculated in (2.103).

The keyword WRFT (see 12.19.216) 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.6. Well Approxi-
mation.

2.14.2. Group control

tNavigator supports the following possibilities to specify group control:

• GRUPTREE (see 12.19.100) – 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.19.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.19.86) – group control for producers.

• GCONINJE (see 12.19.95) – group control for injectors.

• GCONSUMP (see 12.19.96) – gas consumption and import rates for groups.

• GUIDERAT (see 12.19.87) – The keyword specifies a general formula for calculating
production guide rates (for group control, keyword – GCONPROD, see 12.19.86).
Group flow rate targets are distributed among the wells in proportion to their guide
rates.
Default: well’s guide rate is equal to its potential flow rate at the beginning of each time
step (description of well’s potential flow rate is in the section 5.6.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.

2.14.2. Group control 122

 19.1

• WGRUPCON (see 12.19.94) – specifies well guide rates for group control.

• GSATPROD (see 12.19.97) – specifies production rate for satellite groups.

• GSATINJE (see 12.19.98) – specifies injection rate for satellite groups.

• keywords GRUPSALE (see 12.19.193) and GCONSALE (see 12.19.194) – specify the
group gas sales rate.

• GRUPFUEL (see 12.19.195) – specifies the group gas fuel rate.

2.14.3. Economic control

tNavigator supports the following possibilities to specify economic control:

• WECON (see 12.19.74) defines economic limits for production wells via production
rates, water cut, GOR, etc;

• WECONX (see 12.19.75) defines economic limits for production wells in a more general
way, using arbitrary parameters;

• WECONINJ (see 12.19.81) defines economic limits for injection wells via injection rates;

• WECONINJX (see 12.19.82) defines economic limits for injection wells in a more gen-
eral way, using arbitrary parameters;

• WECONCMF (see 12.19.77) defines economic limits for production wells via component
mole fractions;

• CECON (see 12.19.80) defines economic limit by connection for production well;

• GECON (see 12.19.121) defines economic limit for groups via production rates;

• GECONX (see 12.19.76) allows to specify economical limits of arbitrary type for groups
of wells;

• GDCQECON (see 12.19.204) defines economic limit for groups via DCQ.

2.14.4. Separators
For black oil model (E1 data type):
SEPVALS (see 12.19.154) – 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.19.155), which allocates
well groups to separators. If the separator corresponds to a group, all wells of this group use
this separator.

2.14.3. Economic control 123

 19.1

For compositional models (E3 data type):

FIELDSEP (see 12.16.24) – This keyword specifies field separator. All the wells use this sep-
arator for default. To specify different separator for one well or for well group one should use
the keywords SEPCOND (see 12.19.156), WSEPCOND (see 12.19.157).

SEPCOND (see 12.19.156) – This keyword specifies separator conditions (the first usage of
this keyword) or re-specifies separator conditions (the nest usages of this keyword). The sep-
arator conditions are associated with the well via the keyword WSEPCOND (see 12.19.157).

2.14.5. Gas plants

For separator stage (see parameter 9 of keyword SEPCOND, see 12.19.156) a gas plant table
can be used instead of a flash calculation. Gas plant tables can be defined by GPTABLE
(see 12.16.26), GPTABLE3 (see 12.16.28), GPTABLEN (see 12.16.27) keywords.
For each component the oil recovery fraction (the number of moles of liquid output per
mole of feed) is specified as a function of the ”heavy” mole fraction of the feed by keyword
GPTABLE (see 12.16.26). The components consisting of the heavy fraction are also specified
in the table.
If NGL (natural gas liquid) output exists GPTABLEN (see 12.16.27) keyword should be
used instead GPTABLE (see 12.16.26). GPTABLEN specifies the table of both the oil recovery
fractions and the NGL recovery fractions for each component as a function of the ”heavy”
mole fraction of the feed. The keyword DNGL (see 12.14.69) specifies partial densities in the
NGL stream.
The keyword GPTABLE3 (see 12.16.28) specifies a table with recovery fractions for oil,
NGL and gas for each component as a function of the ”heavy” mole fraction of the feed.
This keyword can be used instead of GPTABLE (see 12.16.26), GPTABLEN (see 12.16.27) in
case of for one or more components, the sum of the oil, NGL and gas recovery fractions is
not equal to one. To exclude one or more components in the post separator oil, NGL or gas
streams GPTABLE3 can be used. The partial densities in the NGL stream is specified using
the keyword DNGL (see 12.14.69).
The way to compute the oil, NGL and gas recovery fractions is decribed below.
The oil, NGL and gas compositions are calculated as follows:

RiO zi
xi = ,
∑ RiO zi
RiG zi
yi = , (2.105)
∑ RiG zi
RiN zi
ni = ,
∑ RiN zi
where:

• zi is the input mixture composition to the gas plant,

2.14.5. Gas plants 124

 19.1

• RiO is the oil recovery factor,

• RiG is the gas recovery factor,

• RiN is the NGL recovery factor (NGL – natural gas liquid).

The mole fraction of NGL, oil and gas are:

RN = ∑ RiN zi ,
R̃O
R0 = ,
R̃O + R̃G (2.106)
R̃G
RG = ,
R̃O + R̃G
where:
R̃O = ∑ RiO zi ,
(2.107)
R̃G = ∑ RiG zi .
Oil and gas properties are calculated in accordance with their compositions xi and yi .

2.14.6. MULTI-phase injection

The keywords that can be used for multi-phase injection:

• 2-nd parameter of the keyword WCONINJE (see 12.19.44) should be set to MULTI
(multi-phase injection). The preferred phase of the well will be injected (specified via
WELSPECS, see 12.19.3);

• 5-th parameter of WCONINJE (see 12.19.44) specifies the surface flow rate of the pre-
ferred phase;

• parameters 12-14 of WCONINJE (see 12.19.44) 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.19.47), WCONINJP (see 12.19.46), WWAG (see 12.19.52).

2.14.7. WAG injection mode

The keywords to simulate water-gas injection mode: WCYCLE (see 12.19.50), WELLWAG
(see 12.19.51), WWAG (see 12.19.52).

2.14.6. MULTI-phase injection 125

 19.1

2.14.8. DCQ. Gas Field Model

tNavigator support the following operations in Gas Field Model:

• Specification of swing and profile factors for FIELD – SWINGFAC (see 12.19.198).
The required rate of gas production has a seasonality profile. One should specify an an-
nual 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 month’s profile factor.

• Seasonality profile for groups – GSWINGF (see 12.19.199). The keyword GASFIELD
(see 12.1.98) 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.19.209). Decrement values for these rates – the keyword GASFDECR
(see 12.19.210).

• The keywords GASYEAR (see 12.19.201) and GASPERIO (see 12.19.202) sets contract
periods. These keywords should be used instead of DATES (see 12.19.124), TSTEP
(see 12.19.125). GASPERIO (see 12.19.202) should be used if the length of the contract
period is less than a year.

• Well operations and reports during the contract period should be entered between the
keywords GASBEGIN (see 12.19.205) and GASEND (see 12.19.206). Time in the con-
tract period (when the operation should take place) should be specified via GASMONTH
(see 12.19.207).

• Initial DCQ (Daily Contracted Quantity) for each well should be specified via GDCQ
(see 12.19.200).

• GDCQECON (see 12.19.204) – 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.19.211) – the using of compressors in models with standard net-
work option (see section 2.14.10).

• DCQDEFN (see 12.19.203) defines whether the DCQ targets set in keywords GASYEAR
(see 12.19.201), GASPERIO (see 12.19.202) or GDCQ (see 12.19.200) correspond to
energy or gas production rate.

2.14.9. Gas Lift Optimization

The keywords that can be used in Gas Lift Optimization option: LIFTOPT (see 12.19.239),
GLIFTOPT (see 12.19.241), WLIFTOPT (see 12.19.242), GLIFTLIM (see 12.19.240).

2.14.8. DCQ. Gas Field Model 126

 19.1

This option is used to allocate the lift gas to each well to meet well, group or field produc-
tion 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.19.66), VFPCORR,
see 12.19.71).

• An increment size for lift gas injection rate is specified (METRIC: sm3 /day, FIELD:
Msc f /day) (1-st parameter of LIFTOPT, see 12.19.239). The lift gas resources are
divided in discrete increments of uniform size.

• The minimum economic gradient (2-nd parameter of LIFTOPT, see 12.19.239) 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 in-
cremental gradient) is calculated – the increment of field oil production rate (due to
increment in the gas lift at one increment value) multiplied by well’s 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 :
fw ∗ ∆TO
Winc =
GLinc
where:
fw – well’s weighting factor (4-th parameter of WLIFTOPT, see 12.19.242);
∆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.19.242)
is specified):
fw ∗ ∆TO
Winc =
GLinc + fG ∗ ∆TG
where:
fG – gas production rate weighting factor (6-th parameter of WLIFTOPT, see 12.19.242);
∆TG – increment (or decrement) in field gas production rate.

2.14.9. Gas Lift Optimization 127

 19.1

• 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.19.241),
GLIFTLIM (see 12.19.240).

2.14.10. Standard network option

Standard network structure is the same as the hierarchy specified in GRUPTREE
(see 12.19.100). If the network should have a structure different from standard group hier-
archy then one should use an extended network option – 2.14.11 (the keyword NETWORK,
see 12.1.91).

Production network is specified via GRUPNET (see 12.19.114). Pumps and compressors –
GNETPUMP (see 12.19.113), GASFCOMP (see 12.19.211). Automatic compressors are also
supported.

2.14.11. NETWORK option. Automatic chokes. Compressors

NETWORK option is specified via the keyword NETWORK (see 12.1.91). The keyword sets
dimensions for extended network model. The extended network model is specified via key-
words NODEPROP (see 12.19.103), BRANPROP (see 12.19.102).
Injection network could be specified via the keyword GNETINJE (see 12.19.107).

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.

GNETDP (see 12.19.106) contains parameters for the dynamic changing of fixed pressures.
The keyword 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.

NETBALAN (see 12.19.132) 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.19.100) – 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.19.3). Thus a group either contains wells (that is a wellgroup)
or has other groups as children (that is a node-group).

2.14.10. Standard network option 128

 19.1

In case of extended network model group structure can be different from the struc-
ture specified by GRUPTREE (see 12.19.100) (the bottom nodes in the tree should be the
same (i.e. well groups)). BRANPROP (see 12.19.102) specifies branch properties. NODE-
PROP (see 12.19.103) specifies node properties. The top node should have a fixed pressure.
WNETDP (see 12.19.247) sets fixed pressure drop value between a well’s tubing head pressure
and its group’s 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.19.110) – removes water from a node in the extended network.

NGASREM (see 12.19.111) – removes gas from a node in the extended network.

NOILREM (see 12.19.112) – removes oil from a node in the extended network.

NCONSUMP (see 12.19.105) – 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 group’s production rate target.

A branch is set as a choke via a flag YES in parameter 3 of the keyword NODEPROP
(see 12.19.103) 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.19.102).

Automatic compressors (pumps).

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

2.14.11. NETWORK option. Automatic chokes. Compressors 129

 19.1

2.14.12. Pipe and networks equipment. Chokes

upstream pipe diameter

bean diameter

Figure 13. Model of choke.

Choke is a tool which limits flow in pipe due to local decreasing of the pipe section area.
The main functions of choke are:
• control of flow in pipe;

• additional pressure drop, namely its decreasing. It is needed to decrease pressure to

allowable values in the following network constructions.
The keyword NETCHOKE (see 12.19.104) sets choke properties in tNavigator.
There are two regimes of choke workflow – critical and subcritical. ”Critical” means
that velocity of fluid flow in choke’s bean achieves acoustical velocity; ”subcritical” means
that the velocity is less than acoustical one. These regimes are radically different. Effect
of acoustical velocity achieving is called choked flow. It means that flow volume doesn’t
depend on downstream pressure. This effect is used in field development and networks to
hold on initially set constant flow volume and get rid of influence of network parts on well
workflow and entire reservoir.
To determine whether flow is critical or subcritical, it is often used ratio of upstream
pressure to downstream one as an approximation. If the value of the ratio is less than defined
critical value Ccrit it is considered that flow is critical, otherwise – subcritical.
There is a correlation between choke pressure drop and mass fluid flow through it. Corre-
lation type MECHANISTIC is supported in tNavigator. Pressure drop for mixture is calculated
as a linear combination of partial pressure drop of liquid and gas phases:

∆P = αL ∆PL + αG ∆PG , (2.108)

where αL and αG are liquid and gas fractures in flow correspondingly. Equations for
pressure drop in gas and liquid phases are calculated via Bernoulli’s law:
 2
ρm V
∆PG = (2.109)
2 CvG ZG

ρm V 2
 
∆PL = (2.110)
2 CvL

2.14.12. Pipe and networks equipment. Chokes 130

 19.1

There:

• ρm – mixture density;

• CvL – liquid flow coefficient;

• CvG – gas flow coefficient;

• ZG – gas expansibility coefficient;

• V – mixture velocity.

CvL and CvG are coefficients which account all irreversible processes in choke – friction,
heat loss, etc. These coefficients may be set explicitly or calculated via common discharge
coefficient, Cd : p
Cv = Cd / 1 − δ 4 , (2.111)
where Cv is one of the coefficients CvL and CvG .
Gas expansibility coefficient is got from [26]:

0.41 + 0.35δ 4 ∆P
ZG = 1 − · , (2.112)
γ Pup
where:

• δ = dbean /dup – diameters ratio;

• γ – heat capacity ratio;

• ∆P – choke pressure drop;

• Pup – upstream pressure.

Mixture velocity, V , is expressed via mass fluid flow:

Q
V= , (2.113)
Abean · ρm
where:

• Q – mixture mass rate;

• Abean – bean cross-section area.

2.14.12. Pipe and networks equipment. Chokes 131

 19.1

2.14.13. Well prioritization option

Keywords PRIORITY (see 12.19.92), GCONPRI (see 12.19.89) 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.19.86).

Well prioritization option description.

• Wells priorities are calculated according to formula specified in PRIORITY (see 12.19.92).

• Wells are turned on in decreasing order of their priority (well with the highest priority
is the first).

• Wells are turned on until group’s production rate limit is exceeded.

• A rate of well, which exceeds the group’s limit, is cut to meet the limit (in spite of its
own limits WCONPROD, see 12.19.42).

• Wells with low priority are closed until they are selected to produce.

• Wells, which violate economic limits, and are closed manually can’t be selected to
produce.

• 2 priority formulae can be specified and they can be used as PRI and PR2 in GCONPRI,
see 12.19.89).

• If 2 limits that have different priority formulae 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 NUP-
COL (see 12.19.234) iterations via the formula (coefficients are specified in PRIORITY,
see 12.19.92):
A + BPO +CPW + DPG
PRIORITY =
E + FPO + GPW + HPG
where:

– Pp – potential well rate for the phase p (description of well’s potential flow rate
is in the section 5.6.7);
– A, B, C , D, E , F , G, H – coefficient from PRIORITY (see 12.19.92).

• Wells’ priorities calculated via formulae PRIORITY (see 12.19.92) can be overriden via
numbers specified directly in the keyword WELPRI (see 12.19.93);

2.14.13. Well prioritization option 132

 19.1

• In group hierarchy both methods of potential guide rates GCONPROD (see 12.19.86)
and well prioritization GCONPRI (see 12.19.89) 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.14.14. 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.19.86), GCONINJE, see 12.19.95).
If a group cannot provide its production volume, the producer with the highest drilling priority
(that belongs to that group, and doesn’t belong to any other group under the same production
control) will be opened automatically. If a group cannot provide its injection volume, the in-
jector with the highest drilling priority (that belongs to that group, and doesn’t 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.19.229). 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.19.227). Wells
from prioritized queue are opened in decreasing order of their drilling priority. The key-
word DRILPRI (see 12.19.226) specifies the default priority formula for the prioritized
drilling queue.

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.19.228).

The keyword WDRILRES (see 12.19.231) prevents from drilling two wells in one grid
block.

2.15. Multisegment well

Multisegment well model allows to describe in detail fluid flow in a wellbore. This tool is
specially designed for horizontal and multilateral wells, however, it can be implemented for
analysis of fluid flow in standard vertical and deviated wells.
In the multisegment well model a wellbore (or any its branches) is divided into one-
dimensional segments. For each segment a set of independent variables describing local fluid
conditions is specified. For models in E1 format 4 variables are specified: the fluid pressure,

2.14.14. Prioritized drilling queue. Sequential drilling queue 133

 19.1

the total flow rate and the flowing fractions of water and gas. For models in E3 format the
following variables are specified for each segment: nc +3 variables (where nc is the number of
hydrocarbon components), the fluid pressure, the total molar flow rate and the flowing molar
densities of water and each hydrocarbon component. Each segment may have completions
in one or more grid blocks, or none at all if there are no perforations in this region. In
each segment variables are calculated using the material balance equations for each phases or
component and the pressure drop equation taking into account local hydrostatic, friction and
acceleration pressure gradients. A pressure drop can be calculateded using the homogeneous
flow model where all phases flow with the same velocity, or a ”drift flux” model, in which it
is assumed that there is slip between phases. Furthermore, the pressure drop can be obtained
from precalculated VFP tables providing high accuracy of calculations and allows to model
chokes.
In general case the multisegment well model allows:

• To improve modelling of multilateral wells. Design of data input allows easily to use
multilateral wells. There are two separate keywords specifying a segment structure and
perforation intervals. Branches are identified by their numbers. If it is required branches
can have sub-branches;

• To improve modelling of multiphase flow. The use of the ”drift flux” model or precal-
culated tables of pressure drop allows to obtain more accurate pressure gradients than
in the homogeneous flow model implemented in other well models. A pressure gradient
can vary from segment to segment along a wellbore and is calculated implicitly in each
segment using local flow conditions;

• More flexible modeling of well. The number of grid block completions can be different
for different segments. For more accurate modelling it is required to specify the large
number of segments, while for faster computation the number of segments should be
small;

• In the multisegment well model there are special tools for well modelling. Some of well
segments can be treated as flow control devices such as chokes by providing a pressure
drop table that describes pressure losses in chokes as a function of flow. Moreover the
following flow control devices are available:

– Pressure loss multipliers can be used for modelling of ”smart” devices that isolates
regions with high GOR or WOR;
– Flow limiting valves can be used for modelling of ”smart” devices that limits the
flow of oil, water or gas through a segment;
– Other well components can be modeled, for example: sub-critical valves,
”labyrinth” devices and downhole separators.

• More realistically modelling of crossflow due to varying fluid mixture throughout the
well. Complex crossflow regimes can occur in multilateral wells, including branch-
to-branch crossflow and crossflow within a branch. In other well models if crossflow

2.15. Multisegment well 134

 19.1

occurs then the mixture flowing back into the reservoir will affect well bore contents,
whatever where in the well crossflow occured;

• Wellbore storage effects can be modeled more accurately by dividing a well bore into
several segments. In the ”drift flux” model phases can flow in opposite directions at low
flow rates, so that redistribution of phases can occur in the wellbore during shut–in well
tests.

2.15.1. Multisegment well model

A multisegment well consists of a series of segments forming a tree topology. Thus a single
bore well consists of a series of segments located in sequence along the wellbore. A mul-
tilateral well consists of a series of segments located along a main stem and one or several
segments located along each of its branches connected with the segment of main stem (see
figure 14). If it is required any branch of multilateral well can have sub-branches. This can be
useful when modeling inflow control devices as a part of network of segments. Thus for each
network of segments it is possible to create an arbitrary number of branches and sub-branches,
but the created network should form a tree topology. Segments within topology can be con-
nected in order to form a loop (see section Looped flow paths). Each segment consists of a
node and a flow path to its parent node. A segment’s node is located at the end of segment
that is furthest away form the wellhead (see figure 15).
Each segment is located at specific depth and has a pressure determined by the well model
calculation. For each segment a length, diameter, roughness, area and volume are specified.
The volume is used for wellbore storage calculations, other parameters are specified segment’s
flow path and used for calculation of friction and acceleration pressure losses. In addition for
each segment (its flow path) oil, water and gas rates determined by the well model calculation
are specified.
The top segment is a special case. It does not connect with parent segment therefore,
it is not possible to calculate a pressure drop along the segment. Hence for the top segment
pressure, roughness and area are not required to specify. The pressure drop equation is replaced
by a boundary condition corresponding to the well’s control mode (see section Top segment).
A segment node should be located at each branch junction. Flow from the formation
through grid block connections enters into the well at segment nodes. A segment (i.e. its node)
can accept flow from any number of grid block connections (see figure 15). To increase an
accuracy of calculation for each connection a segment should be created with its node located
at the center of corresponding grid block. It is possible to decrease a number of segments by
assigning two or more grid block connections to each segment. In this case it is required to
locate the segment’s node at the center of corresponding interval of perforations. At the same
time it is not possible to assign a single grid block connection to more than one segment.
Generally each grid block connection allocates to the segment whose node lies nearest to it. If
necessary it is possible to explicitly specify a segment to which connection should be assigned
using the keywords COMPSEGS (see 12.19.27) or COMPSEGL (see 12.19.28).
Segment’s nodes can be located at intermediate points along the wellbore, for example,
where tubing properties or inclination angle vary. Furthermore, segments representing chokes

2.15.1. Multisegment well model 135

 19.1

Figure 14. Multilateral, multisegment well.

or inflow control devices can be additionally specified. In general the optimum number of
segments required to model a well is a compromise between desired speed of calculations and
accuracy.

2.15.2. Inflow performance

The fluid flow between a grid block and corresponding segment’s node is defined by the
inflow performance relationship:


qP j = Tw j MP j p j + Hc j − pn − Hnc

where
• qP j is the volumetric flow rate of phase P in jth connection at stock tank conditions
for models in E1 format and at reservoir conditions for models in E3 format. Flow from
a formation into a well has positive sign and negative sign from well into the formation;
• Tw j is the jth connection transmissibility factor;

2.15.2. Inflow performance 136

 19.1

Figure 15. Segment structure.

• MP j is the phase mobility at jth connection. If the node injects fluid into the formation,
the ratio of the phase mobilities represents the phase mixture in the segment;
• p j is the pressure in the grid block containing jth connection;
• Hc j is the hydrostatic pressure head between the connection’s depth and the center depth
of the grid block;
• pn is the pressure at the corresponding segment’s node n;
• Hnc is the hydrostatic pressure head between the segment’s node n and the depth of
connection.
In contrast to standard wells in multisegment wells the connection depth can not be equal
to the grid block center depth. Depths can be set independently using keywords COMPSEGS
(see 12.19.27) (or COMPSEGL, see 12.19.28) or calculated by default using segment depths
and their position within the segment. The hydrostatic head Hnc between a connection and
associated segment node is calculated implicitly from the density of mixture in the segment.
The hydrostatic head Hc j between a connection and the grid block center is calculated by
averaging the fluid densities in the grid block.
For models in E1 format the average is weighted according to corresponding fluid relative
permeabilities in order to obtain the smooth variation of value when fluid in the block is
displaced by another phase. This averaged density is calculated explicitly at each time step.

2.15.2. Inflow performance 137

 19.1

For models in E3 format the average is weighted according to corresponding implicit fluid
saturations in order to obtain the smooth variation of value when fluid in the block is displaced
by another phase.

2.15.3. The pressure loss calculation

Pressure losses can be calculated as follows:
• Using a homogeneous flow model.
In this model it is assumed that there is no slip between phases. Hydrostatic term
depends on the density of the fluid mixture in the segment and is a flow-weighted av-
erage of phase densities. The frictional pressure drop is calculated in the similar way
as used for the wellbore (see section 6.1.1). The accelerated pressure drop along seg-
ment is calculated as difference between velocity heads of the inflowing and outflowing
mixture.
• Interpolating the pressure drop from precalculated VFP tables.
The created VFP table describes a pressure drop along a tubing of a certain length at
the specified inclination angle. A pressure drop along segment is interpolated using the
associated VFP table and can be scaled according to the segment’s length or depth span.
Optionally, the table containing only the frictional pressure drop can be created, while
the hydrostatic pressure drop is calculated based on fluid properties in the segment. VFP
tables can be used to describe pressure losses in a choke.
• Using a ”drift flux” slip model.
This model is a simple correlation that is continuous in the whole range of flow con-
ditions. The model includes slip effects as follows: a local vertical slip velocity super-
imposed on a velocity ratio resulting from profiles of holdup fraction and flow velocity
across the tubing cross section. In case of the mixture velocity is small enough the
local vertical slip velocity generates countercurrent flow (i.e., phases flow in opposite
directions).
• Using a model for a specific flow control device.

– Model defining sub-critical flow through a valve with a specified throat cross-
section area (see the keyword WSEGVALV, see 12.19.15).
– ”Flow limiting valve” model. This model represents a hypothetical device dynami-
cally limiting oil, water or gas flow rates (at surface conditions) through a segment
to the defined maximum value by sharply increasing the frictional pressure drop
across segment when the specified limit is exceeded (see the keyword WSEGFLIM,
see 12.19.19);
– Model used to calculate the pressure drop across inflow control device. This device
is located around a tubing section and diverts the inflowing fluid from the adjacent
part of the formation through a sand screen and then into a spiral constriction
before fluid enters into the tubing (see the keyword WSEGSICD, see 12.19.17);

2.15.3. The pressure loss calculation 138

 19.1

– Model represents an autonomous inflow control device (see the keyword

WSEGAICD, see 12.19.16).

The homogeneous flow model (specified by default) is the most simple model providing
results close to ones in the wellbore friction option (when there is no crossflow). VFP tables
provide flexible and potentially more accurate method for the calculation of pressure losses.
Tables can be created by selecting an appropriate correlation of multiphase flow. The ”drift
flux” model is less accurate than the correctly calculated VFP table because of the need for
simplicity and continuity in the used correlation. The ”drift flux” model allows to model a
phase separation and countercurrent flow occurring at low flow velocities (e.g., in shut-in
well tests). Parameters in the ”drift flux” model, defining a slip velocity, are specified by the
keyword WSEGFMOD (see 12.19.20).

2.15.4. Top segment

A top segment is a special segment of the well. Its node corresponds to the well’s bottom hole
reference depth, i.e. the pressure in the top segment is equal to the bottom whole pressure
(BHP). Since there is no parent segment located above top segment it is not possible to
calculate a pressure drop across segment. The pressure loss equation in the top segment is
replaced by a boundary condition corresponding to the well’s mode of control. The volume
of the top segment can be set in order to calculate wellbore storage. It is worth to estimate
whether there is an advantage in modelling the whole wellbore via segments up to the tubing
head. In such case the well’s reported BHP is really its THP. The best position of the top
segment is above perforations and all lateral branch junctions. The pressure loss between this
point and the tubing head is modeled using VFP tables.
It is reasonable to model the whole well bore with segments if a well test is being simulated
and it is necessary to model wellbore storage effects in detail. The ”drift flux” model can be
used to model a separation of phases in the wellbore during a shut-in test.

2.15.5. External sources and sinks

It is possible to import well or gas into a segment from a source located outside the reservoir
grid. The import rate can be specified as a constant value or as a function of pressure in
segment (see the keyword WSEGEXSS, see 12.19.18). Imported fluid will be added to fluid
flowing through a segment.
Gas import can be used to model the effect of lift gas injection in order to examine the
kickoff process. Water import can be used to take into account water used to power a downhole
hydraulic pump if this is injected into the wellbore.
It is possible to remove fluid from a segment into an external source with a rate that is a
function of pressure in the segment. This option should be used to model recirculating wells
along with thermal option (specified by keyword THERMAL, see 12.1.54).

2.15.4. Top segment 139

 19.1

2.15.6. Looped flow paths

The gathering tree topology formed by multisegment wells in general does not allow to create
looped flow paths within the well. However, it is possible to add looped flow paths as follows:
• The basic well topology should be specified using the keyword WELSEGS
(see 12.19.11). One or more pairs of nodes of different segments have to coincide.
This means that segment’s nodes should be specified at the same true vertical depth
given in the keyword WELSEGS (see 12.19.11). However, it is not sufficient to create
looped flow path and this pair of nodes will work as they are unconnected;

• Each pair of nodes should be ”linked” using the keyword WSEGLINK (see 12.19.13).
Using this step each pair of nodes starts to communicate and looped flow path forms.
At least on of these segments should be located at the end of a branch.
The looped flow path is shown in figure 16. Linked nodes forms the looped flow path
between top and bottom well branches of the multisegment well. Flow from the bottom branch
can pass into the main stem directly or through the top branch, while flow form the top branch
can pass into the main stem directly or through the bottom branch. The pressure variations in
the top and bottom branches determine the direction of the flow.
The pressure drop equations in segments, whose nodes are linked, do not change, but the
material balance equations for one of segments are replaced by equations of equality of the
pressure, flowing fraction of water and flowing fraction of gas at the linked segment nodes.
This option will work if the following conditions are satisfied:
• One of the linked with the keyword WSEGLINK (see 12.19.13) segments should be
located at the end of a branch;

• The second segment of the pair should have non zero roughness, i.e. 8 parameter of the
keyword WELSEGS (see 12.19.11) should not be equal to zero;

• Top segment of well can not be the part of looped flow path, i.e. it can not be specified
in the keyword WSEGLINK (see 12.19.13).

Linked segment nodes

In the keyword WSEGLINK (see 12.19.13) the first segment of the pair is assumed to be the
primary linked segment, while the second segment of the pair is the secondary linked segment.
If the first segment of the pair of linked segments is located at the end of the branch, while
the second segment is not, then the first segment will be treated as the secondary segment of
this pair. For the secondary segment of the pair the material balance equations are replaced by
the solution equality equations.
If flows in connections or external sources/sinks are specified for both linked segments
(COMPSEGS (see 12.19.27) or COMPSEGL, see 12.19.28) then these flows will be assigned
to the primary segment of the pair (since only this segment of the pair has the material balance
equations including these terms). Any volume corresponding to the secondary segment of

2.15.6. Looped flow paths 140

 19.1

Figure 16. Schematic looped flow path in multisegment well .

the pair of linked segments will be assigned as an additional volume in the primary linked
segment.
Besides the replacement of the material balance equations by solution equality equations
in the secondary linked segment, these segments are not different from standard segments of
multisegment well. Hence the pressure drop equation for any segment of the pair of linked
segments can be changed by any of the ways described in the section The pressure loss
calculation.

Modeling an unpacked annulus

An example of looped flow paths in multisegment wells is flow in an unpacked annulus.
One branch of well can be used to model a tubing and consists of a series of segments, each
segment directly connected with its immediate neighbors (see figure 17). Another well branch
can be used to model an unpacked annulus. Each segment along this branch is connected with
its neighbors as well (see figure 17).
Flow can pass into a well only through connections in annulus segments. Flow can move
along annulus and entrance into the tubing via control valves located at intervals along well.
Without possibility to model looped flow paths flow from the annulus segment would have
been limited so that it would have to flow into the tubing through the specific valve. Because
of the looped flow paths option flow in an annulus segment can pass through any of the valves
into the tubing.

2.15.6. Looped flow paths 141

 19.1

Figure 17. Multisegment well with an unpacked annulus.

2.15.7. Pressure drops based on VFP tables

VFP tables allows more flexibly and more accurately to define a pressure drop across each
segment. Interpolating the pressure drop based on the table is more faster than calculating the
pressure drop using the multiphase flow correlation. It is required to specify a separate table
for each segment. Segments having the same diameter, inclination and roughness can use the
same VFP table. A pressure drop is scaled according to the length and depth span of each
segment.
VFP tables should be constructed for a tubing of representative length and having appro-
priate inclination angle, using the corresponding multiphase flow correlation. The table should
be in the form of production VFP table and specified by the keyword VFPPROD (see 12.19.66)
in the section SCHEDULE. The standard VFP table specifies BHP as a function of flow rate,
THP, the water and gas fractions, and ALQ (optionally). When implemented to a well segment
BHP is assumed to be as the segment’s nodal pressure (i.e., its inlet pressure), while THP is
the pressure at the node of its neighboring segment towards the wellhead (i.e., the segment
outlet pressure). The similar approach is used to create VFP tables for modeling pressure
drops in branches in the Network option.

Pressure drop scaling

The second parameter of the first record of a VFP table (see keyword VFPPROD, see 12.19.66)
usually contains the bottom hole datum depth of the table. However, when the table is used to
obtain a pressure drop across segment the table should contain either length or the depth span
of the tubing of the representative length, for which this table is calculated.
When interpolating a pressure drop across a segment based on the VFP table the pressure
drop is scaled proportionally to the segment’s length or depth span. 7–th parameter of the
keyword WSEGTABL (see 12.19.14) specifies the pressure drop scaling (using length or

2.15.7. Pressure drops based on VFP tables 142

 19.1

depth span). The choice of the scaling value should be consistent with the value given in the
second parameter of the first record of the VFP table.
The choice of scaling value is important when the same table is used for segments having
a different inclination angle. The friction pressure drop is proportional to the length and
the hydrostatic pressure drop is proportional to the septh span. The choice of scaling value
should depend on size of contribution of process (friction or hydrostatic) into pressure losses.
Obviously, horizontal segments should be scaled according to length.
The pressure drop can not be scaled at all, for example, if a segment is a choke, since a
pressure drop across choke does not change proportional to the length of the device.

Pressure drop components

Usually, VFP tables describe the combined effect of friction and hydrostatic pressure losses
along the tubing of the representative length. The table does not contain enough information
to evaluate the effect from each component on the pressure drop. Thus, the pressure drop
obtained from the VFP table is the pressure drop caused by friction, while the hydrostatic
pressure loss is assumed to be zero. In addition, the table includes an acceleration pressure
loss caused by expansion of the gas phase in its passage down the pressure gradient. Pressure
losses due to additional fluid entering into the segment (e.g., through perforations).
An acceleration pressure loss is calculated and added to the total pressure loss interpo-
lated from the table if this is indicated in 6-th parameter of the first record of the keyword
WELSEGS (see 12.19.11). In this case the VFP table should be created without including
any acceleration pressure loss otherwise the component due to gas expansion will be included
twice. The acceleration pressure loss component is normally small in comparison with the
total pressure drop and in most cases can be neglected.
Furthermore, it is possible to create the VFP table containing only the friction pressure
loss and calculate a hydrostatic pressure loss across segment and then add it to the interpolated
(from a VFP table) pressure drop. The VFP table containing only the friction pressure loss can
be created if for the calculation of the VFP table the horizontal tubing of the representative
length was used. Such approach can be used for gently undulating sections of tubing in order
to avoid the creation of separate tables for each inclination angle. The hydrostatic pressure
loss is calculated based on the homogeneous flow model and slip effects are neglected.

2.15.8. Reverse flow

When fluid flows through the segment of production well in opposite direction problems may
appear. This flow can occur away from the well head. The sign of this flow is negative. In
production well the reverse flow occurs when the flow velocity is small and crossflow occurs.
If revers flow is likely to occur, it is possible to extend the VFP table into the negative flow
region.
To handle reverse flow, when the flow value is less (or negative) than the first flow
value in the VFP table, the option specified by 6-th parameter of the keyword WSEGTABL
(see 12.19.14) is available:

2.15.8. Reverse flow 143

 19.1

• reverse flow and a pressure drop in VFP tables. This option is recommended for hori-
zontal segments or segments modeling chokes, or VFP tables in which only the friction
pressure loss is given (see the section Pressure drop components), i.e. the hydrostatic
pressure loss does not take into account. In this case a pressure drop can be reversed
when the flow reverses. The first flow value in the VFP table should be positive. For
negative flows the VFP table ”mirror image” is implemented. For flows between posi-
tive and negative first value, the pressure loss is linearly interpolated between this two
points.

2.15.9. Chokes
VFP tables can be created to model a pressure drop across flow control devices, for example
chokes. The effect of varying the choke diameter can be included into the table by using
the ALQ variable. For a segment representing a choke a pressure loss is not scaled. The
reverse flow in these segments is taken into account via the reverse of the pressure drop (6–th
parameter of the keyword WSEGTABL, see 12.19.14).

2.15.10. Injection wells

In injection wells single phase water or gas flow through segments, therefore, there is no a
big need to use VFP tables for modeling pressure losses. The multiphase flow can occur if
there is crossflow with reservoir fluid entering at one or more perforated intervals. If a VFP
table should be used to model a pressure loss across segment of injection well, the possibility
of occurrence of multiphase flow requires that created VFP tables have the production format
(see keyword VFPPROD, see 12.19.66), but with negative flow values.

2.15.11. Model for gas-liquid slip

A slip model allows the phases to flow with different velocities. Generally, gas phase flows
with higher velocity in comparison to the liquid phase. Thus, slip increases the liquid holdup
fraction for a given flowing gas-liquid ratio, therefore increasing the hydrostatic head compo-
nent.
In drift flux models a slip between gas and liquid phases is a combination of two mecha-
nisms. The first mechanism results from the non-uniform distribution of gas across the cross-
section of the pipe, and the velocity profile across the pipe. The concentration of gas in the
gas-liquid mixture is the highest along the centerline of the pipe and lowest near the pipe wall.
The local flow velocity of the mixture is the highest along the centerline of the pipe. Thus,
integrating across the pipe area, the average gas velocity is higher than the liquid one. The
second mechanism is based on the tendency of gas to rise vertically through the liquid due to
buoyancy.
The gas velocity takes into account both mechanisms:

vg = C0 j + vd

where

2.15.9. Chokes 144

 19.1

• vg is the gas phase velocity, averaged across the pipe area;

• C0 is the profile parameter (or distribution coefficient) resulting from the velocity and
gas concentration profiles;

• j is the volumetric flux of the mixture;

• vd is the drift velocity of the gas.

The behavior of volumetric mixture flux is similar to the average mixture velocity, and is
the sum of the gas and liquid superficial velocities:

j = vsg + vsl = αg vg + (1 − αg )vl

where αg is the gas volume fraction, averaged across the pipe area. The average liquid flow
velocity is calculated as:
1 − αgC0 αg
vl = j− vd
1 − αg 1 − αg
The profile parameter
Ref. [31] shows that the value of profile parameter C0 can vary from 1 to 1.5. In the
bubble and slug flow regimes, see for example [1], C0 is set equal to 1.2. For low values of
αg and j C0 is equal to 1.2.
However, at high velocities, the profiles become flat and C0 tends to 1.0. Moreover, C0
should approach to 1 if αg tends to 1. In other words, the product C0 αg should be less than
1.
The profile parameter C0 is calculated as:
A
C0 =
(1 + (A − 1)β ∗2 )

By default the coefficient A is 1.2. A can be specified by user but its value should be higher
than 1. The parameter β ∗ is used to reduce C0 up to 1 at high values of αg and j .The
parameter β ∗ is calculated as:

β −B
β∗ = , 0 ≤ β∗ ≤ 1
1−B
The parameter β tends to 1 when αg approaches to 1, and mixture velocity approaches
to particular value. The velocity of the onset of the annular flow regime is supposed to be
the velocity at which profile slip vanishes. The transition to annular flow occurs when the
gas superficial velocity vsg reaches the ”flooding” value that is sufficient to prevent the liquid
from falling back against the gas flow, vsg f (see the next section).
Thus, β is calculated using the formula:
 
αg | j|
β = max αg , Fv
vsg f

2.15.11. Model for gas-liquid slip 145

 19.1

Parameters B and Fv are specified by user. B defines the value of the gas holdup fraction
or the flooding velocity fraction above which the profile parameter C0 starts to decrease from
the value A. Fv is a multiplier on the flooding velocity fraction. Its default value is 1.0, but the
profile flattening can be made more or less sensitive to the velocity by respectively increasing
or decreasing Fv value.
Maximum value of the parameter B is limited. It is supposed that the gas superficial
velocity vsg = vg αg increases with increase in both αg and j . Thus, the following relation
should be valid:

B ≤ (2 − A)/A
for coefficients A and B. If A = 1.2 B should be less than 0.6667.
The drift velocity
The rise velocity of gas through a stationary liquid can be expressed via vd :
vd
vg (vl = 0) =
1 − αgC0

If αg tends to 0, the gas velocity tends to the rise velocity of a single bubble, the value of
which is 1.53vc . Here vc is the characteristic velocity, which is calculated as:
1/4
σgl g(ρl − ρg )

vc =
ρl2

where

• σgl is the gas-liquid interfacial tension;

• g is the acceleration due to gravity;

• ρl and ρg are the liquid and gas phase densities.

At high values of αg the gas velocity tends to the ”flooding velocity”, which is high
enough to support a thin annular film of liquid and prevent it from falling back against the
gas flow. Wallis and Makkenchery obtained the following relation:
 1/2
ρl
vg (vl = 0) = Ku vc
ρg

where Ku is the critical Kutateladze number related to the dimensionless pipe diameter:
 1/2
∗ ρl
D =
ρg

via the shown below table.

2.15.11. Model for gas-liquid slip 146

 19.1

D∗ Ku
≤2 0
4 1.0
10 2.1
14 2.5
20 2.8
28 3.0
≥ 50 3.2
To calculate the drift velocity of the gas vd the following formula is used:
(1 − αgC0 )C0 K(αg )vc
vd = q
ρl
ρg αgC0 + 1 − αgC0

where
K(αg ) = 1.53/C0 αg ≤ a1
K(αg ) = Ku αg ≥ a2
Defaulted values of a1 and a2 are 0.2 and 0.4, respectively. All formulas described above are
derived supposing that a gas-liquid mixture flows in a vertical pipe. To scale the drift velocity
for flow in inclined segments vd is multiplied by an inclination factor:
vd (θ ) = m(θ )vd |θ =0
m(θ ) = (cosθ )0.5 (1 + sinθ )2
where θ is the angle of inclination from the vertical.

2.15.12. Three-phase flow and oil-water slip

The described above drift flux model was formulated for two-phase gas-liquid mixtures. If
three-phase mixtures flows in the wellbore, and oil-water mixtures are considered, a different
model should be applied.
When considering three-phase mixtures, we can use the above formulation to model the
total slip between the gas phase and the combined liquid phase. The properties of the combined
liquid phase (density, viscosity) are calculated as an average of the oil and water properties,
weighted according to the volume fraction α of each phase. In this case we do not take into
account the possibility of occurrence of emulsions. However, an application of two-phase flow
correlations to oil-water-gas mixtures is a standard approach. The gas-liquid interfacial tension
is calculated as:
αo σgo + αw σwg
σgl =
αo + αw
where σgo and σgw are the gas-oil and water-gas interfacial tensions, respectively. The inter-
facial tension σgo can be specified in tabular form as a function of pressure using the keyword
STOG (see 12.6.87).

2.15.12. Three-phase flow and oil-water slip 147

 19.1

To model the slip between oil and water in the liquid phase the following formula is used
[32]:
vo = C00 vl + v0d
In this model the profile parameter C00 is equal to 1.2, which becomes unity when oil is the
continuous phase at αo > 0.7.
The continuous function of the holdup fraction of oil in the liquid phase can be written as:

C00 = A αol ≤ B1

C00 = 1 αol ≤ B2
 
0 αol − B1
C0 = A − (A − 1) B1 < αol < B2
B2 − B1
where αol = αo /(αo + αw ). The defaulted values of coefficients are A = 1.2, B1 = 0.4 and
B2 = 0.7. A condition of increase in the oil superficial velocity with the oil holdup fraction
requires:
B ≤ (2 − A)/A
The oil-liquid drift velocity v0d is calculated as:
0
v0d = 1.53v0c (1 − αol )n

where  1/4
σow g(ρw − ρo )
v0c =
ρw2
where σow is the oil-water interfacial tension. The tension can either be specified in tabular
form as a function of pressure using the keyword STOW (see 12.6.88) or calculated as the
difference between the values of σgo and σwg obtained from the above correlations.
The oil-water drift velocity in inclined segments is scaled in a similar way as described
earlier for the gas-liquid drift velocity, using an inclination factor m(θ ).

The effect of gas on oil-water slip

The presence of free gas in liquid can prevent the slip between oil and water phases. It is
assumed that the inclination factor m(θ ) for oil-water slip should be multiplied by a factor
mg (θ , αg ), which describes this effect as a function of the pipe inclination and the gas volume
fraction:
αg
mg (θ , αg ) = 1 − , αg < a3
a3 (θ )
mg (θ , αg ) = 0, αg > a3
The oil-water drift velocity decreases up to zero if the gas volume fraction increases from
zero to a3 and is equal to zero if αg is larger than a3 . The limit value a3 is the function
of pipe inclination. If the pipe inclination angle from the vertical varies from 0 to 70 degrees
a small amount of gas is required in order to remove the drift between oil and water. For

2.15.12. Three-phase flow and oil-water slip 148

 19.1

almost horizontal flows the gas effect is much weaker (due to segregation from the liquid). To
calculate a3 the following formula is used:
3
a3 (θ ) = 0.017eθr .28

where θr is the inclination angle from the vertical in radians (=πθ /180).

2.15.13. Friction pressure loss

The friction pressure loss is calculated based on the approach used in the Hagedorn & Brown
correlation [14].
C f f Lw2
∆p f = 2
A Dρ
where
• f – the Fanning friction factor;

• L – the length of the segment;

• w – the mass flow rate of the fluid mixture through the segment;

• A – the area of cross-section of segment;

• D – the segment’s diameter;

• ρ – the density of the fluid mixture;

• C f – the units conversion constant (METRIC: 2.679e−15 , FIELD: 5.784e−14 ).

The Fanning friction factor is calculated using the same method as in the wellbore friction
option (see section 6.1.1), but the Reynolds number is calculated as:
Cr Dw
Re =
Aµ
• Cr – the units conversion constant (METRIC: 0.01158, FIELD: 0.01722).
The viscosity µ is calculated as an average of the phase viscosities weighted according to
their volume fraction. The above written formula is equivalent to the homogeneous model
used in the Wellbore Friction option if there is no slip between the phases.

2.15.14. Acceleration pressure loss

The acceleration pressure loss across segment is the difference between the velocity head
of the mixture flowing across the outlet junction of segment and the velocity heads of the
mixture flowing through all its inlet junctions (the segment main inlet and any side branches
connecting with the segment).
∆pa = Hvout − ∑ Hvin
inlets

2.15.13. Friction pressure loss 149

 19.1

The velocity head of the mixture flowing through a junction is calculated as:

0.5C f w2
Hv =
A2 ρ

A is the area of cross-section of segment for the outlet junction flow and A is the maximum
of the cross-section areas for the inlet junction flow. Thus the acceleration pressure loss will
give the Bernoulli effect at restrictions but no pressure recovery at expansions. Since all
velocity heads from all flows entering into a segment from side branches are included into a
full velocity head it is assumed that flow is entering into the segment with no momentum loss.
Reservoir flow into the segment (through grid block connections) is not included in the
inflow velocity head. Thus, the acceleration pressure loss is the loss required to accelerate
fluid from zero velocity to the segment’s outflow velocity.

2.15.15. Keywords
The structure of multisegment well is specified via the keyword WELSEGS (see 12.19.11).
WSEGDIMS (see 12.1.41) – dimensions of data for multisegment well (not necessarily key-
word, tNavigator allocates memory dynamically). WSEGTABL (see 12.19.14) – specifies cal-
culation of segment pressure drops from VFP tables.
WSEGVALV (see 12.19.15) – specifies calculation of segment pressure drops for sub-critical
valve.

Keywords WSEGAICD (see 12.19.16) and WSEGSICD (see 12.19.17) are used to control
the inflow profile along a horizontal well.
Definition of location of completions in a multisegment well – COMPSEGS (see 12.19.27)
(COMPSEGL (see 12.19.28) for LGR case).

Adding or removing fluids to or from a segment in a multisegment well – WSEGEXSS

(see 12.19.18). Adding or removing fluid depends on a specified rate or segment’s pressure.
The source or sink for this fluid is external.

WFRICSEG (see 12.19.26) (WFRICSGL (see 12.19.26) 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.19.24) (WFRICTN (see 12.19.24) in LGR case).
WFRICSEG (WFRICSGL, see 12.19.26) provides an easy way of transformating a friction well
into a multisegment well by changing the keyword name to WFRICSEG.

WSEGFLIM (see 12.19.19) defines segment of multisegment well as a flow limiting valve.

WSEGAICD (see 12.19.16) designates a segment of multisegment well as an autonomous

inflow control device.

2.15.15. Keywords 150

 19.1

WSEGSICD (see 12.19.17) designates a segment of multisegment well as an spiral inflow

control device.

WSEGLINK (see 12.19.13) defines chord segment links required to occur looped flow
paths in multisegment wells.

WSEGSEP (see 12.19.22) designates a segment of multisegment well as a down-hole sep-

arator.

WSEGPULL (see 12.19.23) defines segment of multisegment well as a pullthrough pump

for a down-hole separator.

WSEGFMOD (see 12.19.20) specifies the multiphase flow model used to calculate the
pressure losses within segments of a multisegment well.

WSEGDFPA (see 12.19.21) used to modify the parameters that control the Drift Flux slip
model in multisegment wells.

2.16. Polymer Flood

In tNavigator the following options are supported to model polymer flood:
• Polymer flood option POLYMER (see 12.1.51) (formats E1, E3).
• To enhance the polymer action it may be injected together with the alkaline (see
2.22. Alkaline flooding) and surfactant (see 2.23. Surfactant injection).
• ASP (Alkaline-Surfactant-Polymer flooding) model. For the full description, see the
section 5.9. ASP model description.
• Special option of Polymer flooding based on BrightWater technology – section
2.16.2. Polymer flooding based on BrightWater technology).
• If mixing of waters with different salinities is used (BRINE, see 12.1.62), then polymer
solution viscosity can be set as function of salt concentration. The keywords SALTNODE
(see 12.7.3) and PLYVISCS (see 12.7.6) should be specified.
Also polymer adsorption functions varying with salinity can be specified: use keywords
PLYADSS (see 12.8.27) and ADSALNOD (see 12.7.4).
• Polymer flood in IM format – see the section 2.16.3. Polymer flood in IM format.

2.16.1. Polymer Flood option POLYMER

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

2.16. Polymer Flood 151

 19.1

Keyword Section Description

POLYMER (see 12.1.51) RUNSPEC Indicates that Polymer Food model is used
PLYADS (see 12.8.26) PROPS Polymer adsorption function
PLYADSS (see 12.8.27) PROPS Polymer adsorption function varying with
salinity
PLYMAX (see 12.8.28) PROPS Polymer and salt concentration for mixing cal-
culations
PLMIXPAR (see 12.8.29) PROPS Specifies Polymer Todd-Longstaff mixing pa-
rameter
PLMIXNUM (see 12.2.107) GRID Specifies regions with different polymer char-
acteristics for each grid blocks
PLYROCK (see 12.8.30) PROPS Specifies the rock properties for Polymer flood
PLYKRRF (see 12.8.31) PROPS Specifies the rock permeability (blockwise) for
Polymer flood
PLYVISC (see 12.8.25) PROPS Specifies solution viscosity multiplier as a
function of polymer concentration
PLYSHEAR (see 12.8.32) PROPS Polymer solution viscosity multiplier in the
case of shear thinning
PLYSHLOG (see 12.8.33) PROPS Polymer solution shear multiplier (logarithmic
formula)
SHRATE (see 12.8.34) PROPS Shear rate form and constant for the polymer
shear thinning/thickening logarithmic model
SALTNODE (see 12.7.3) PROPS Sets the data to calculate polymer solution vis-
cosity as a function of salt concentration
PLYVISCS (see 12.7.6) PROPS Sets the data to calculate polymer solution vis-
cosity as a function of salt concentration
WPOLYMER (see 12.19.174) SCHEDULE Specifies polymer concentration in the well’s
injection stream
PLYVISCT (see 12.8.35) PROPS Specifies polymer viscosity multiplier func-
tions of polymer concentration and tempera-
ture. It used only with the activated tempera-
ture option (TEMP, see 12.1.64)
PLYVSCST (see 12.8.36) PROPS Specifies full polymer/salt solution/tempera-
ture viscosity function. It can be used only
with the activated temperature option (TEMP,
see 12.1.64) and activated salt-sensitivity op-
tion (BRINE, see 12.1.62)

2.16.1. Polymer Flood option POLYMER 152

 19.1

2.16.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.11) (the tracer for which
the holding time in the reservoir will be calculated). Polymer injection can be defined using
the keyword WTRACER (see 12.19.171).
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.13), TRM-
MULTT (see 12.7.14).

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.64). 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.13), TRMMULTT (see 12.7.14). ktemp (Tpol ) - the function depending on the

2.16.2. Polymer flooding based on BrightWater technology 153

 19.1

factor of absolute permeability on the temperature, defined via table TRMTEMP (see 12.7.15).
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

Keyword Section Description

TEMP (see 12.1.64)
TRACERM (see 12.7.11)
TRMMULTC (see 12.7.13)
TRMMULTT (see 12.7.14)
TRMTEMP (see 12.7.15)
WTRACER (see 12.19.171)
RUNSPEC Specifies temperature option
PROPS Specifies tracer list for which the holding time
in the reservoir will be calculated
PROPS Specifies the dependence between absolute
permeability multiplier and tracer concentra-
tion
PROPS Specifies the dependence between absolute
permeability multiplier and holding time in the
reservoir
PROPS Specifies the dependence between absolute
permeability multiplier and temperature
SCHEDULE Specifies the value of tracer concentration in
the injection stream

2.16.3. Polymer flood in IM format

Polymer flood models: differences in E1 and IM formulation
• ”Dead pore space” (not invaded by polymer) depends on absolute permeability, not on
saturation region as in E1 format;

• Polymer speed is the same as water speed (no Bvisc

poly );

• Several polymer models available.

Polymer flood model in IM format is specified 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.98).

2.16.3. Polymer flood in IM format 154

 19.1

System of maintenance equations:

 asp 
krW
UW = −βc k asp (∇p + ∇PcW − ρW g∇d)
µ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 )
• ρW
sc – mass water density in surface conditions (kg/sm3 )

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.93),
• 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.94) as a function of absolute permeability
Polymer adsorption modelling.
Adsorption parameters are set via the keywords PADSORP (see 13.5.93) and PPERM
(see 13.5.94).
PADSORP (see 13.5.93) 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 max-
imal value in PADSORP (see 13.5.93) to use it in maintenance equation.
Keyword PPERM (see 13.5.94) 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.94).
Let’s denote Ad = Aads 3
poly Ad,max , (kg/sm ). For Ad,max interpolation we use maximal
permeability in one of the directions (i.e. max(PERMI (see 13.3.11), PERMJ (see 13.3.11),
PERMK, see 13.3.11)).
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).

2.16.3. Polymer flood in IM format 155

 19.1

Water viscosity calculation.

Let’s denote µW (p) ”usual” viscosity, which is calculated via VWI (see 13.5.21), CVW
(see 13.5.21).
Also denote:
re f
• C poly – reference polymer concentration (kg/sm3 ) which is set in PREFCONC
(see 13.5.96);
re f
• µ poly – reference polymer viscosity which is set in PVISC (see 13.5.97);

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.95) and one of its options:

• LINEAR – linear model.

asp re f
µW = α µ poly + (1 − α)µW (p) (2.114)

where α is a relative polymer concentration:

C poly
α= re f
(2.115)
C poly

• NONLINEAR – non-linear model.

asp re f
µW = (µ poly )α (µW (p))(1−α) (2.116)

• 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.117)
Rk
where Rk is given by:
Ad
Rk = 1 + (Krr f − 1) (2.118)
Ad,max
So, for polymer solution mobility λwasp is:
asp
krW krW
λwasp = asp =   . (2.119)
µW Ad asp
1 + (Krr f − 1) Ad,max µW

2.16.3. Polymer flood in IM format 156

 19.1

2.17. Tracer modeling

tNavigator allows to simulate flow of tracers in water, oil or gas phase. This option can
be used for models in E1 format and compositional isothermal models with one–component
water in E3 format, while a tracer can be only connected to water. In order to activate the
environmental tracers option 4-th parameter of keywords TRACERS (see 12.1.48) (section
RUNSPEC ) should be larger than 0. This parameter specifies maximum number of tracers. It
is possible to set up to 50 tracers for a model. A tracer is connected to a component.
Furthermore, the tracer adsorption on a rock and decay of the tracer with time can be taken
into account. It is possible to simulate both adsorption and decay for a tracer.
The tracer adsorption on the rock is defined as a function using the keyword TRADS
(see 12.7.17). A tracer half-life period is specified by keyword TRDCY (see 12.7.16) in the
section PROPS for each PVT region. Using these keyword it is necessary to add a tracer name
to the keyword’s name in order to indicate the tracer corresponding to data.
For adsorption model a mass rock density is specified by keyword TRROCK (see 12.5.26).
Furthermore, this keyword is used to set the adsorption model and adsorption initialization
model.
System of equations of mass conservation of tracer connected to component c in phase P
can be written as:
∂ ∂  
(ϕNc ·Ctr ) + (1 − ϕ)ρrock ·Ctrads ξP,sc = − div (ξPUP ·Ctr ) + Qtr (2.120)
∂t ∂t
where

• Ctr is the tracer concentration (METRIC: sm3 /sm3 ; FIELD: stb/stb for liquids,
Msc f /Msc f for gas);

• Ctrads is the consentation of adsorbed part of tracer (METRIC: sm3 /kg; FIELD: stb/lb
for liquids, Msc f /lb for gas), defined as a function of Ctr using the keyword TRADS
(see 12.7.17);

• Qtr is the source/sink for tracer (wells);

• ρrock is the mass rock density (METRIC: kg/rm3 , FIELD: lb/rb) at pre f specified by
keyword TRROCK (see 12.5.26).

The list of passive tracers and their calculation method are given by first and second
parameters of keyword TRACEROPTS (see 12.7.12), respectively.

2.17.1. Tracer modeling keywords

Keyword Section Description

TRACER (see 12.7.10) PROPS Specifies passive tracers settings
TRACERS (see 12.1.48) RUNSPEC Specifies dimensions for tracers

2.17. Tracer modeling 157

 19.1

Keyword Section Description

WTRACER (see 12.19.171)
TNUM (see 12.16.44)
TBLK (see 12.16.43)
TVDP (see 12.16.45)
SCHEDULE Specifies the value of concentration of a
tracer in the injection streams of its asso-
ciated phase for flooding
REGIONS Specifies tracer concentration region num-
bers for each grid block
SOLUTION Specifies the initial concentration of a
tracer in each grid block
SOLUTION Specifies tables of initial tracer concentra-
tion with respect to depth for each tracer

2.17.2. Decay of tracer

Decay of tracers is simulated as half decay process, i.e. the process results in decrease of tracer
mass by a factor of two. The half-life period is specified by keyword TRDCY (see 12.7.16) in
the section PROPS for each tracer. Decay of tracer starts immediately after its injection into a
reservoir.

2.17.3. Tracer adsorption

Model of tracer adsorption can be also used for compositional isothermal models with one–
component water in E3 format. It is assumed that tracer adsorption is the instantaneous effect.
The adsorption model can take into account desorption effect. Presence of desorption is de-
fined by the 1-st parameter of keyword TRROCK (see 12.5.26). Desorption appears when
tracer concentration decreases in grid block.
The adsorption initialization model can be specified by 3-rd parameter of keyword TR-
ROCK (see 12.5.26). There are two models of adsorption initialization. In the first model the
input tracer concentration is defined from equilibration condition (the total mass of tracer is
conserved and distributed between the fluid and rock). In the second model, it is assumed that
the input fluid concentration is equal to the input tracer concentration, and adsorbed on the
rock tracer concentration is defined from adsorption function.
The tracer adsorption function (adsorption isotherm) is tabulated for each SAT region
using keyword TRADS (see 12.7.17). This table contains dependence of rock adsorbed tracer
concentration on the tracer concentration in solution.

2.17.4. Adsorption and decay of tracer

The following models combining adsorption and decay of tracer are implemented:

1. Parameter DCY1 of keyword TRACEROPTS (see 12.7.12).

Decay of tracer is modeled by defining a half-life period λ (days). After this period a
tracer mass decreases by a factor of two (tracer adsorbed on the rock does not participate
in decay process). The half-life period is specified by keyword TRDCY (see 12.7.16)

2.17.2. Decay of tracer 158

 19.1

in the section PROPS for each PVT region. The tracer concentration obtained from

∆t
conservative equation (2.120) is multiplied by 12 λ . However, in this approach a tracer
concentration in fluid is not in equilibrium with concentration of tracer adsorbed on the
rock.

2. Parameter DCY2 of keyword TRACEROPTS (see 12.7.12).

It is assumed that decay of tracer appears instantaneously at the end of time step. Since
tracer concentration decreased (there has been a decay of tracer) desorption process
starts and the desorbed tracer participates in decay. Desorption continues until achieving
equilibrium between concentration of tracer in fluid and in rock. An equilibrium tracer
concentration after decay C˜tr can be found from the following equation:
 
Mtr C˜tr − ΛCtr = ΛMrock Cads (Ctr ) −Cads (C˜tr ) ,


(2.121)

where

• Ctr is the tracer concentration (METRIC: sm3 /sm3 ; FIELD: stb/stb for liquids,
Msc f /Msc f for gas);
• Ctrads is the consentation of adsorbed part of tracer (METRIC: sm3 /kg; FIELD:
stb/lb for liquids, Msc f /lb for gas), defined as a function of Ctr using the key-
word TRADS (see 12.7.17);
• Qtr is the source/sink for tracer (wells);
• ρrock is the mass rock density (METRIC: kg/rm3 , FIELD: lb/rb) at pre f specified
by keyword TRROCK (see 12.5.26);

∆t
• Λ = 12 λ , λ is the half-life period (day) defined for each PVT region using
keyword TRDCY (see 12.7.16).

3. Parameter DCY3 of keyword TRACEROPTS (see 12.7.12).

Decay of tracer occurs along with adsorption process. In this case adsorbed part of tracer
and dissolved part of tracer decay. An equilibrium tracer concentration after decay C˜tr
can be found from the following equation:
 
Λ MtrCtr + MrockCads (Ctr ) = MtrC˜tr +Cads (C˜tr )Mrock , (2.122)

where

• Ctr is the tracer concentration (METRIC: sm3 /sm3 ; FIELD: stb/stb for liquids,
Msc f /Msc f for gas);
• Ctrads is the consentation of adsorbed part of tracer (METRIC: sm3 /kg; FIELD:
stb/lb for liquids, Msc f /lb for gas), defined as a function of Ctr using the key-
word TRADS (see 12.7.17);
• Qtr is the source/sink for tracer (wells);

2.17.4. Adsorption and decay of tracer 159

 19.1

• ρrock is the mass rock density (METRIC: kg/rm3 , FIELD: lb/rb) at pre f specified
by keyword TRROCK (see 12.5.26);

∆t
• Λ = 12 λ , λ is the half-life period (day) defined for each PVT region using
keyword TRDCY (see 12.7.16).

4. Parameter DCY4 of keyword TRACEROPTS (see 12.7.12).

In this case the equation of tracer mass conservation takes into account decay of tracer.
Ctr can be obtained from the equation:

∂ ∂  
(ϕNc ·Ctr ) + (1 − ϕ)ρrock ·Ctrads ξP,sc = − div (ξPUP ·Ctr ) + Qtr −
∂t ∂t  
− Λ (ϕNc ) − Λ (1 − ϕ)ρrock ·Ctrads ξP,sc (2.123)

where

• Nc = Nc (t, x, y, z) – c = 1, . . . , nc is the molar density of component (kg-mol/m3 );

• Ctr is the tracer concentration (METRIC: sm3 /sm3 ; FIELD: stb/stb for liquids,
Msc f /Msc f for gas);
• Ctrads is the consentation of adsorbed part of tracer (METRIC: sm3 /kg; FIELD:
stb/lb for liquids, Msc f /lb for gas), defined as a function of Ctr using the key-
word TRADS (see 12.7.17);
• Qtr is the source/sink for tracer (wells);
• ρrock is the mass rock density (METRIC: kg/rm3 , FIELD: lb/rb) at pre f specified
by keyword TRROCK (see 12.5.26);
• Λ = ln2
λ is the decay coefficient (1/day), where λ is the half-life period (day)
defined for each PVT region using keyword TRDCY (see 12.7.16).

2.18. Foam modeling

i Foam option is only available in E1 models.

Foam is modeled as a tracer with special properties. Its use is initiated by the keyword
FOAM (see 12.1.68). Foam may be associated either with gas component or with water com-
ponent; this is specified by the keyword FOAMOPTS (see 12.11.2).
The initial concentration of foam in grid blocks is given by SFOAM (see 12.16.57). Also,
foam may come with the injected streams (WFOAM, see 12.19.266). Over time, the amount of
foam may gradually change due to adsorption and/or decay. The function of foam adsorption
by the rock formation is specified by FOAMADS (see 12.11.1). The possibility of desorption
is specified by FOAMROCK (see 12.11.3). The decay is modeled via the half-life period which
may depend on water saturation (FOAMDCYW, see 12.11.4) and/or oil saturation (FOAMD-
CYO, see 12.11.5). The details of interplay between decay and adsorption are controlled by the

2.18. Foam modeling 160

 19.1

options of the keyword TRACEROPTS (see 12.7.12), the same way it is done with ordinary
tracers.
Amount of gas-bound foam in a block is subject to the following conservation law:
!  
∂ V NgC f ∂ a1−ϕ
+ V ρrC f = ∑ FgC f + QgC f − λ (Sw , So )VC f (2.124)
∂t ρg(sc) ∂t ϕ neighb. cells | {z } | {z }
| {z } | {z } | {z } prod./ decay
free foam adsorbed foam inflow/outflow inj.

For the water-bound foam there is a similar expression:

!  
∂ V NwC f ∂ a1−ϕ
+ V ρr C f = ∑ FwC f + QwC f − λ (Sw , So )VC f (2.125)
∂t ρw(sc) ∂t ϕ

where

• C f is the foam concentration,

• ρw,g(sc) are the gas and water densities at standard conditions, respectively,

• ρr is the rock density,

• V is the block pore volume,

• Ng,w are the molar densities of gas and water, respectively,

• Caf is the adsorbed foam concentration,

• ϕ is the porosity,

• Fg,w are the gas and water flow values to or from neighboring blocks,

• Qg,w are the gas and water net production rates, respectively (with injection counted as
negative),

• λ (Sw , So ) is the decay rate coefficient, depending on oil and water saturations.

The influence of foam on the dynamics of fluids in the reservoir is specified via the
gas mobility reduction mutiplier dependent on foam concentration (FOAMMOB, see 12.11.6).
It may also depend on pressure (FOAMMOBP, see 12.11.7) and on shear (FOAMMOBS,
see 12.11.8).
The gas mobility reduction mutiplier Mr f is calculated as follows:

Mr f = (1 − Mrcpf )Mv (Vg ) + Mrcpf

Mrcpf = (1 − Mc (C f ))M p (P) + Mc (C f )

where

2.18. Foam modeling 161

 19.1

• Mv (Vg ) is the coefficient dependent on gas velocity and defined via FOAMMOBS
(see 12.11.8).

• Mc (C f ) is the coefficient dependent on foam concentration and defined via FOAMMOB

(see 12.11.6).

• M p (P) is the coefficient dependent on pressure and defined via FOAMMOBP

(see 12.11.7).

• P is the oil phase pressure.

• Vg is the gas velocity which is calculated as:

Bg · Fg
Vg =
ϕ ·A
Here

– Fg is the gas flow rate measured in surface conditions,

– Bg is the gas formation volume factor,
– ϕ is the average porosity of the two cells,
– A is the flow area between the two cells.

2.19. Residual oil modeling

Supported keywords:

• SOR (see 12.12.1) – activates residual oil modeling option and sets residual oil saturation
values in each SATNUM (see 12.4.3) region;

• SOILR (see 12.16.58) – initial residual oil saturation values in each grid block;

• ROMF (see 12.16.59) – initial composition of residual oil in each grid block;

• SOROPTS (see 12.12.2) – compressibility model of residual oil.

2.20. The division of hydrocarbons tracking

Keywords:

• TRACK (see 12.1.135) – enables the option and sets properties of the tracking;

• TRACKREG (see 12.4.29) – sets tracking regions in the model.

2.19. Residual oil modeling 162

 19.1

2.21. Asphaltene modeling

Supported keywords:
• ASPHALTE (see 12.1.67) – activates option of asphaltene precipitation modeling and
sets oil viscosity change model type;
• ASPDEPO (see 12.10.8) – sets properties of asphaltene deposition process;
• ASPFLRT (see 12.10.5) – sets the kinetic reaction rates for the flocculation and disso-
ciation processes for each component;
• ASPLCRT (see 12.10.6) – sets properties of asphaltene plugging;
• ASPVISO (see 12.10.7) – sets parameters of oil viscosity change model;
• CATYPE (see 12.10.9) – sets asphaltene components;
• 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 keyword
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);
• ASPPW2D (see 12.10.4) – defines two-variable asphaltene precipitation function.

2.22. Alkaline flooding

Alkaline flooding is performed via alkaline chemicals injection (high pH). Alkaline flooding
can be done simultaneously with surfactant (see 2.23. Surfactant injection) and polymer (see
2.16. Polymer Flood).

For the full description of ASP (Alkaline-Surfactant-Polymer) mathematical model, see

the section 5.9. ASP model description.
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.52). Alkaline concentra-
tion in the well injection steam is set via WALKALIN (see 12.19.173).

All the supported features are described below.

2.21. Asphaltene modeling 163

 19.1

Alkaline adsorption.
Alkaline adsorption is calculated at each time step. The table of alkaline adsorption as a func-
tion of its concentration is specified via the keyword ALKADS (see 12.8.41).
Desorption can be prevented (1-st parameter of ALKROCK, see 12.8.42), then the concentra-
tion 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.10);
• Ast (Calkl ) – surface tension multiplier dependent on alkaline concentration (specified
via the keyword ALSURFST, see 12.8.38).
Effect on surfactant and polymer adsorption.
Alkaline reduces surfactant and polymer adsorption on the rock and enhance their effectiveness
this way. Mass of adsorbed surfactant and polymer is calculated via the formula:
1−ϕ
Porv ∗ Mrock ∗Cads ∗ ∗ Aad (Calkl )
ϕ
where:
• Porv – block pore volume;
• Mrock – rock mass density (specified via SURFROCK (see 12.8.13), PLYROCK,
see 12.8.30);
• Cads – concentration of adsorbed surfactant and polymer (from the keywords SURFADS
(see 12.8.9), PLYADS (see 12.8.26);
• ϕ – porosity;
• Aad (Calkl ) – adsorption multiplier that depends on the alkaline concentration (specified
via ALSURFAD (see 12.8.39), ALPOLADS, see 12.8.40).
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:
• Calkl
max – maximum alkaline concentration reached in the block during the calculated

period.

2.22. Alkaline flooding 164

 19.1

2.23. Surfactant injection

tNavigator has an option of Surfactant injection simulation (and solvents injection). This
option is based on tracers simulation technology.
For the full description of ASP (Alkaline-Surfactant-Polymer) mathematical model, see
the section 5.9. ASP model description.
The keyword SURFACT (see 12.1.49) indicates the Surfactant option. Surfactants are
chemical agents which are injected to the formation as an admixture to the phase (water in
case of surfactants, or oil in case of solvents), and change the oil-water surface tension.
In tNavigator the effect of admixture (surfactants, salts, any other tracers) on fluid per-
meation behavior is simulated by altering saturation end points (ENPTRC (see 12.6.40),
ENPTRCM, see 12.6.43), relative phase permeabilities (ENPKTRC (see 12.6.41), ENPKTRCM,
see 12.6.44), and capillary pressures (ENPCTRC (see 12.6.42), ENPCTRCM, see 12.6.45).
For each block it is possible to define scaled critical oil-in-water saturations at miscible
conditions using the keyword SOCRS (see 12.8.8).
Surfactant adsorption.
Surfactant adsorption is a function of surfactant concentration and is specified via the keyword
SURFADS (see 12.8.9). Mass of adsorbed surfactant (MadsSURF ) is calculated by the formula:
1−ϕ
MadsSURF = Porv ∗ ∗ Mrock ∗ FA(CadsSURF )
ϕ

where:

• Porv – block pore volume;

• ϕ – porosity;

• Mrock – mass density of the rock (specified via the keyword SURFROCK, see 12.8.13);

• FA(CadsSURF ) – surfactant adsorption function from a local surfactant concentration

(specified via the keyword SURFADS, see 12.8.9).

The following adsorption model is supported: each grid block retraces the adsorption func-
tion 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 func-
tions 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.

2.23. Surfactant injection 165

 19.1

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.14) (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.15) can be used instead of the keyword SURFADDW
(see 12.8.14). In the keyword SURFDW (see 12.8.15): F – function of the concentration of
dissolved (in the water) surfactant in grid block.
In SURFADDW (see 12.8.14): F – function of adsorbed surfactant concentration in grid block.
In case of table SURFDW (see 12.8.15) 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 SUR-
FADDW (see 12.8.14) adsorbed surfactant affects all three phases RP.

2.23.1. Keywords

Keyword Section Description

SOCRS (see 12.8.8)
SURFACT (see 12.1.49)
SURFACTW (see 12.1.50)
SURFADS (see 12.8.9)
SURFADDW (see 12.8.14)
SURFDW (see 12.8.15)
PROPS Defines the scaled critical oil-in-water satura-
tions at miscible conditions
RUNSPEC Defines that surfactants will be used in the
model
RUNSPEC Defines that surfactants will be used in the
model, the change of wettability will be sim-
ulated
PROPS Specifies surfactant adsorption functions
PROPS Coefficient is used to simulate the change to
wettability due to adsorbed surfactant concen-
tration
PROPS Coefficient is used to simulate the change to
wettability due to dissolved surfactant concen-
tration in grid block

2.23.1. Keywords 166

 19.1

Keyword Section Description

SURFCAPD (see 12.8.12) PROPS Surfactant capillary de-saturation functions
SURFST (see 12.8.10) PROPS Water-oil surface tension as a function of sur-
factant concentration
SURFSTES (see 12.8.16) PROPS Water-oil surface tension as a function of sur-
factant and salt concentrations
SURFVISC (see 12.8.11) PROPS Viscosity of water solution as a function of sur-
factant concentration
SURFROCK (see 12.8.13) PROPS Specifies surfactant-rock properties
ENPTRC (see 12.6.40) PROPS Specifies the saturation end points as a function
of surfactant concentration
ENPTRCM (see 12.6.43) PROPS Specifies the scaling of saturation end points as
a function of surfactant concentration
ENPKTRC (see 12.6.41) PROPS Specifies the relative phase permeabilities as a
function of surfactant concentration
ENPKTRCM (see 12.6.44) PROPS Specifies the scaling of relative phase perme-
abilities as a function of surfactant concentra-
tion
ENPCTRC (see 12.6.42) PROPS Specifies the capillary pressures as a function
of surfactant concentration
ENPCTRCM (see 12.6.45) PROPS Specifies the scaling of capillary pressures as a
function of surfactant concentration
SSWL (see 12.8.17) PROPS Specifies the connate water saturation for mis-
cible conditions, which can be used for scaling
the oil relative permeability to water and gas
SSWCR (see 12.8.18) PROPS Specifies the critical water saturation for mis-
cible conditions, which can be used for scaling
the surfactant water relative permeability
SSWU (see 12.8.19) PROPS Specifies the maximum water saturation for
miscible conditions, which can be used for
scaling the surfactant water relative permeabil-
ity
SSOWCR (see 12.8.20) PROPS Specifies the critical oil in water saturation
for miscible conditions, which can be used for
scaling the oil relative permeability to water

2.23.1. Keywords 167

 19.1

Keyword Section Description

SKRW (see 12.8.21)
SKRWR (see 12.8.22)
SKRO (see 12.8.23)
SKRORW (see 12.8.24)
SURFNUM (see 12.4.4)
SURFWNUM (see 12.4.5)
WSURFACT (see 12.19.172)
PROPS Specifies the value of water relative permeabil-
ity at the maximum water saturation for misci-
ble conditions, which can be used for scaling
the surfactant water relative permeability
PROPS Specifies the value of water relative perme-
ability at the critical oil saturation for miscible
conditions, which can be used for scaling the
surfactant water relative permeability
PROPS Specifies the value of oil relative permeabil-
ity at the maximum oil saturation for miscible
conditions, which can be used for scaling the
surfactant oil relative permeability
PROPS Specifies the value of oil relative permeabil-
ity at the critical water saturation for miscible
conditions, which can be used for scaling the
surfactant oil relative permeability
REGIONS Surfactant miscible region number
REGIONS Saturation function region number in water-
wettability case
SCHEDULE Specifies the concentration of surfactant in the
injection stream

2.24. Waters with different salinities

tNavigator supports the following options to simulate waters with different salinities:
• BRINE (see 12.1.62) option – this keywords sets that mixing of waters with different
salinities will be used.
• Additional option to BRINE (see 12.1.62) – 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.24.1.
• Low salinity water simulation – LOWSALT (see 12.1.63). 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.24.3.

2.24.1. Fresh water injection into the saline reservoir

Salination of reservoir production layers is the way to localize residual reserves of hydrocar-
bons, determine the efficiency of reservoir development, determine oil flooding efficiency in
dependence on pore filling of salt and on salt solubility in fresh water.

2.24. Waters with different salinities 168

 19.1

tNavigator has an option of simulation of fresh water injection into a saline reservoir.
Keyword BRINE (see 12.1.62) indicates that the Brine Tracking option is enabled, which
allows the modeling of waters with different salinities.
Salt washing-out with fresh water is simulated the following way:

• ROCKSALT (see 12.16.46) (mass of reservoir salt that can be dissolved kg);
• initial reservoir salt concentration can be specified through its saturation SRSALT
(see 12.16.49);
• spreading of injected water is calculated (water salinity is specified via WSALT,
see 12.19.175);
• 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.8) (The keyword BDENSITY (see 12.7.7) specifies the brine sur-
face 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.1);
• reservoir salt dissolution rate is directly proportional to difference of salt solution (cur-
rent and saturated).

The keyword SALTTRM (see 12.7.2) sets the dependence between permeability and
amount of dissolved reservoir salt. SALTTRM (see 12.7.2) and SALTPROP (see 12.7.1) can
be specified for different PVT regions.

In tNavigator the effect of admixture (salts, surfactants, any other tracers) on fluid per-
meation behavior is simulated by altering saturation end points (ENPTRC (see 12.6.40),
ENPTRCM, see 12.6.43), relative phase permeabilities (ENPKTRC (see 12.6.41), ENPKTRCM,
see 12.6.44), and capillary pressures (ENPCTRC (see 12.6.42), ENPCTRCM, see 12.6.45).
The initial salt concentration (kg/m3 ) can be specify via the keyword SALT (see 12.16.47).
The keyword should be used when the initial state has been set by enumeration (keywords
PRESSURE (see 12.16.12), RS (see 12.16.37), RV (see 12.16.38), SGAS (see 12.16.15) and
SWAT, see 12.16.14). For a run initialized by equilibration EQUIL (see 12.16.2), the keyword
SALTVD (see 12.16.48) should be used instead of SALT (see 12.16.47) (salt concentration
versus depth for equilibration).

Brine option is supported for aquifers (BRINE, see 12.1.62) (salt concentration is set via
keywords AQUFETP (see 12.17.6), AQUFET (see 12.17.4), AQUCT, see 12.17.9).

2.24.2. Keywords

2.24.2. Keywords 169

 19.1

Keyword Section Description

BRINE (see 12.1.62) RUNSPEC This keyword indicates that the Brine Track-
ing option is enabled, to allow the modeling of
waters with different salinities
PVTWSALT (see 12.7.8) PROPS Specifies water PVT data for runs in which the
Brine option is active
BDENSITY (see 12.7.7) PROPS Specifies the brine surface density variation
with the salt concentration
SALTPROP (see 12.7.1) 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.2) PROPS Specifies the dependence between permeability
and amount of dissolved reservoir salt
ENPTRC (see 12.6.40) PROPS Specifies the saturation end points as a function
of salt concentration
ENPTRCM (see 12.6.43) PROPS Specifies the scaling of saturation end points as
a function of salt concentration
ENPKTRC (see 12.6.41) PROPS Specifies the relative phase permeabilities as a
function of salt concentration
ENPKTRCM (see 12.6.44) PROPS Specifies the scaling of relative phase perme-
abilities as a function of salt concentration
ENPCTRC (see 12.6.42) PROPS Specifies the capillary pressures as a function
of salt concentration
ENPCTRCM (see 12.6.45) PROPS Specifies the scaling of capillary pressures as a
function of salt concentration
SALT (see 12.16.47) SOLUTION Specifies initial salt concentration for each grid
block
SALTVD (see 12.16.48) SOLUTION Specifies initial salt concentration versus depth
for equilibration
ROCKSALT (see 12.16.46) SOLUTION Specifies initial mass of reservoir salt for each
grid block
SRSALT (see 12.16.49) SOLUTION Specifies initial reservoir salt concentration
through its saturation
WSALT (see 12.19.175) SCHEDULE Specifies the concentration of salt in the well
injection stream

2.24.2. Keywords 170

 19.1

2.24.3. Low salinity option

This option is activated via the keyword – LOWSALT (see 12.1.63). (this keyword automati-
cally turns on the option BRINE (see 12.1.62) – simulation of waters with different salinities
– section 2.24.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 formulae
using high (index h) and low (index l ) salinity tables saturation end points:

• SW
i = F Sl + (1 − F )Sh (minimum water saturation (connate))
c 1 Wc 1 Wc

• SW
i l h
cr = F1 SW cr + (1 − F1 )SW cr (critical water saturation)

• SW
i l h
max = F1 SW max + (1 − F1 )SW max (maximum water saturation)

• SOW
i l h
cr = F1 SOW cr + (1 − F1 )SOW cr (residual oil saturation in water-oil system)

• SOGcr
i 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.9).

Then RP and capillary pressures are calculated the following way:

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

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

• krOG
i 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.9).

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.

• krW
h = f (S , Si i h
W W cr ), SW max , krW max

• krW
l = f (S , Si i l
W W cr ), SW max , krW max

analogously for krOW , krOG , pcOW .

In modelling water with low salinity for end–point scaling the following keywords are
used:

2.24.3. Low salinity option 171

 19.1

• LSWL (see 12.6.46) – specifies the connate water saturation, which can be used for
scaling the (oil-wet) oil-water capillary pressure and oil relative permeability to water
tables;
• LSWLPC (see 12.6.47) – specifies the connate water saturation, which can be used for
scaling the (oil-wet) oil-water capillary pressure tables;
• LSWU (see 12.6.48) – specifies the maximum water saturation, which can be used
for scaling the (oil-wet) oil-water capillary pressure and water relative permeability
saturation tables;
• LPCW (see 12.6.49) – specifies the maximum value of oil-water capillary pressure,
which can be used for scaling the (oil-wet) water-oil capillary pressure saturation tables;
• LSOGCR (see 12.6.50) – specifies the critical oil in gas saturation, which can be used
for scaling the (oil-wet) oil relative permeability to gas saturation tables;
• LSOWCR (see 12.6.51) – specifies the critical oil in water saturation, which can be used
for scaling the (oil-wet) oil relative permeability to water saturation tables;
• LSWCR (see 12.6.52) – specifies the critical water saturation, which can be used for
scaling the (oil-wet) water relative permeability saturation tables;
• LKRW (see 12.6.53) – specifies the value of water relative permeability at the maximum
water saturation in each grid block, which can be used for scaling the (oil-wet) water
relative permeability saturation tables;
• LKRWR (see 12.6.54) – specifies the value of water relative permeability at the critical
oil saturation in each grid block, which can be used for scaling the (oil-wet) water
relative permeability saturation tables;
• LKRO (see 12.6.55) – specifies the value of oil relative permeability at the maximum oil
saturation, which can be used for scaling the (oil-wet) oil relative permeability saturation
tables in modelling water with low salinity;
• LKRORW (see 12.6.56) – specifies the value of oil relative permeability at the critical
water saturation, which can be used for scaling the (oil-wet) oil relative permeability
saturation tables;
• LKRORG (see 12.6.57) – specifies the value of oil relative permeability at the critical
gas saturation, which can be used for scaling the (oil-wet) oil relative permeability
saturation tables.

2.25. Scale deposition model

The cumulative effects of scale deposited around the well connections and the resulting degra-
dation of the productivity index due to sea water injection are supported in tNavigator via the
following keywords:

2.25. Scale deposition model 172

 19.1

• SCDATAB (see 12.19.254) – 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.19.252) – 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.117) – set the dependences number;
• WSCTAB (see 12.19.255) – assign tables to individual wells;
• SCDPTRAC (see 12.19.253) – note tracer name, which concentration represents the
fraction of sea water present in the water flowing into a well.

2.26. Temperature option

For temperature option tNavigator supports the following keywords:
• TEMP (see 12.1.64) – indicates that the temperature option is enabled, to allow the
modeling of the temperature effects of cold water injection;
• TEMPR (see 12.1.65) – indicates that the temperature option is enabled. This keyword
is different from the keyword TEMP (see 12.1.64) 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.15.91) – specifies the volume specific heat of rock as a function of
temperature;
• SPECHEAT (see 12.15.92) – specifies the volume specific heat of oil, gas, water as a
function of temperature;
• OILVISCT (see 12.15.54) – sets the table of oil viscosity as a function of temperature
for each PVT region;
• WATVISCT (see 12.15.53) – sets the table of water viscosity as a function of temperature
for each PVT region;
• VISCREF (see 12.15.52) – sets reference pressure and reference dissolved gas concen-
tration for each PVT region;
• THCONR (see 12.15.22) – sets the rock thermal conductivity;
• RTEMPA (see 12.16.33) – specifies initial reservoir temperature;
• RTEMPVD (see 12.16.34) – specifies the dependence between initial reservoir tempera-
ture and depth;

2.26. Temperature option 173

 19.1

• WTEMP (see 12.19.176) – specifies the temperature of injected water;

• WTEMPDEF (see 12.16.35) – default water temperature for injectors is case if the key-
word WTEMP (see 12.19.176) is not defined;

• TRMTEMP (see 12.7.15) – the function depending on the factor of absolute permeability
on the temperature (for polymer flooding models 2.16.2);

• ROCKCONT (see 12.2.86) – 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;

• TEMPNODE (see 12.8.37) – specifies temperature values to calculate polymer solution

viscosity.

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.15.53)
(depends on temperature);

• µW
0 (p) – water viscosity as a function of pressure (specified using PVTW, see 12.5.5);

• pre f – reference pressure (specified using VISCREF, see 12.15.52).

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.15.54) (assumed to be at the refer-
ence pressure and Rs , specified via VISCREF, see 12.15.52);

• µ p – viscosity from PVCO (see 12.5.6) (or PVDO, see 12.5.2);

• pre f – reference pressure, specified via VISCREF (see 12.15.52);

• Rsre f – reference Rs , specified via VISCREF (see 12.15.52).

2.26. Temperature option 174

 19.1

Thermal conduction modeling

In general case the effect of thermal conduction of heat in the rock is negligeable in com-
parison to the convection of heat with the injected water. Thermal conduction can be modelled
by using either the keyword THCONR (see 12.15.22) or keywords THCROCK (see 12.2.91),
THCOIL (see 12.2.88), THCWATER (see 12.2.89), THCGAS (see 12.2.87) and THCSOLID
(see 12.2.90) in the GRID section. These keywords specify the block rock and fluid thermal
conductivity.

2.27. Dual porosity

Dual porosity is specified by the keyword DUALPORO (see 12.1.83) (or DUALPOR
(see 13.3.6) for IM/ST models).
Dual permeability — DUALPERM (see 12.1.84).

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 using
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.83) or DUALPERM (see 12.1.84) is used, the num-
ber of layers in the Z-direction should be even (this number is entered by the third parameter
of the keyword DIMENS (see 12.1.28) (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.90) cancels a multiplication of permeability (for the
fracture blocks) by porosity (fracture blocks) during the dual porosity run. Since this multipli-
cation is used to obtain a net bulk fracture permeability one have to enter this value manually
if NODPPM is enabled.

DPNUM (see 12.2.70) – specifies reservoir fields that should be considered as single poros-
ity fields.

DPGRID (see 12.2.71) – if the keyword is enabled, 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.

2.27. Dual porosity 175

 19.1

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.28). This operation is applied only
for fracture blocks which don’t have manually input grid data.

THCONMF (see 12.2.77) – specifies the matrix to fracture thermal conductivity value for
each matrix block in dual porosity run (2.27) with THERMAL (see 12.1.54) option.

SIGMATH (see 12.2.78) – specifies the multiplier used in calculating the matrix–fracture
thermal transmissibilities.

DIFFMMF (see 12.2.111) – specifies multipliers of diffusivities (see keywords DIFFUSE

(see 12.1.70) and COAL, see 12.1.85) calculated for non-neighbour connections (see the key-
word NNC, see 12.2.54).
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.72) or different
values for different grid blocks can be entered – SIGMAV (see 12.2.73). Sigma factor is related
to the distances between fractures (matrix block sizes) in X, Y and Z directions:
 
1 1 1
σ =4 + + ,
lx2 ly2 lz2

where lx , ly and lz are the characteristic 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).) The keyword ROCKTSIG (see 12.5.19) allows to specify a multiplier for
a sigma-factor σ as a function of pressure in tabulated form in order to take into account a
modification of the matrix-fracture coupling caused by rock compaction.
Default. If neither of the keywords SIGMA (see 12.2.72), SIGMAV (see 12.2.73),
LTOSIGMA (see 12.2.74) is specified, sigma factor will be considered zero.

Viscous Displacement.
VISCD (see 12.1.89) – 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.69), LY (see 12.2.69), LZ (see 12.2.69).
Viscous displacement – fluid flow under the influence of pressure gradient. One can ob-
serve a pressure gradient in the dual porosity system. This gradient moves the fluid in the

2.27. Dual porosity 176

 19.1

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 isn’t
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.69), LY (see 12.2.69), LZ
(see 12.2.69) and LTOSIGMA (see 12.2.74). If tNavigator compute σ , any manually input of
this parameter (SIGMA, see 12.2.72) in data file will be ignored.

LTOSIGMA (see 12.2.74) – this keyword can be used in dual porosity run, if the op-
tion Viscous displacement is enabled (VISCD, see 12.1.89). Using the keyword LTOSIGMA
(see 12.2.74) sigma factor multiplier can be obtained from the distances between fractures
(matrix block sizes).
Sigma factor is related to the distances between fractures (matrix block sizes) in X, Y and
Z directions:
fx fy fz
σ = 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).)
The values of lx , ly, lz that aren’t specified or are equal to zero will not be used in calcula-
tions.
LTOSIGMA (see 12.2.74) defines f x , f y, f z.

Multipliers for sigma factor.

Sigma factor (defined via SIGMA (see 12.2.72), SIGMAV, see 12.2.73) is multiplied by
the multiplier MULTSIG (see 12.19.141) (the same multiplier for whole reservoir) or different
multipliers for grid blocks can be entered using the keyword MULTSIGV (see 12.19.142).

MULTMF (see 12.2.79) – the keyword specifies multiplier which is used to calculate the
matrix-fracture flows.

2.27.1. RP at dual porosity runs.

KRNUMMF (see 12.4.24) – 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.83) and dual permeability DUALPERM (see 12.1.84).
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.25) – 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.83) and dual permeability DUALPERM (see 12.1.84) in case when hysteresis option
is used (parameter HYSTER of the keyword SATOPTS, see 12.1.75).

2.27.1. RP at dual porosity runs. 177

 19.1

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 an imbibition table for matrix,
the flow from the fracture to the matrix uses an imbibition table for fracture.

2.27.2. Gravity drainage option

The following keywords are supported:

• GRAVDR (see 12.1.86) – This keyword switches on an option of gravity drainage be-
tween matrix and fracture cells for dual porosity models;

• GRAVDRM (see 12.1.87) – This keyword switches on an option of alternative gravity

drainage between matrix and fracture cells for dual porosity models;

• DZMTRX (see 12.2.80) – 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.82) – 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.81) – analogue to DZMTRX (see 12.2.80);

• SIGMAGD (see 12.2.75) – 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.76) – 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.28. Coal Bed Methane Model

Coal Bed Methane (CBM) Model in E1/E3 can be activated using COAL (see 12.1.85). For
similar functionality in IM/GE/ST models, see 2.28.1. Coal Bed Methane Model in IM/GE/ST
format.
Coal Bed Methane Model is simulated via dual porosity model (2.27, DUALPORO,
see 12.1.83): coal matrix and the permeable rock fractures.

Adsorption model is set by the keyword CBMOPTS (see 12.1.132).

2.27.2. Gravity drainage option 178

 19.1

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;

• 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.4);

• DIFFMF – diffusivity: DIFFMF = DIFFMMF ∗Vol ∗ σ ;

• DIFFMMF – multiplier specified via the keyword DIFFMMF (see 12.2.111);

• Vol – block coal volume;

• σ – multiplier that can be specified for the whole field (SIGMA, see 12.2.72) or for
each grid block (SIGMAV, see 12.2.73).

The diffusivities can be modified by multiplying the calculated value by an input multipli-
ers defined by DIFFMX (see 12.2.112), DIFFMY (see 12.2.114), DIFFMZ (see 12.2.116).
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.

Maximum coal surface gas concentration can be set via MLANG (see 12.9.5).
Initial coal surface gas concentration can be set via GASCONC (see 12.16.52).
Initial saturated coal surface gas concentration can be set via GASSATC (see 12.16.53).

2.28. Coal Bed Methane Model 179

 19.1

Note 1
MLANG:for compositional model in E3 format the keyword MLANG (see 12.9.5) is used for
the Langmuir isotherm scaling LANGMUIR (see 12.9.2) at the at the maximum fracture pres-
sure.

Note 2
GASCONC: for compositional model in E3 format the keyword GASCONC (see 12.16.52) can
set the initial coal gas concentration for one component defined via GASCCMP (see 12.16.54).

Note 3
GASSATC: for the model in the format E1 the keyword GASSATC (see 12.16.53) is used for
the Langmuir isotherm scaling LANGMUIR (see 12.9.2) at the initial reservoir pressure.
Note 4
GASSATC: for compositional model in E3 format the keyword GASSATC (see 12.16.53) is
used for the Langmuir isotherm scaling (LANGMUIR (see 12.9.2) or LANGMEXT, see 12.9.6)
at the initial reservoir pressure and composition in the reservoir for one component. The com-
ponent is defined via the keyword GASCCMP (see 12.16.54). 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.6).
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 βp·pi
L(p, y1 , y2 , ...)i = ϕ ·Vi ·
RTs 1 + ∑nc y j β ·p
j=1 pj

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.6);

• pi – Langmuir pressure constant for component i (specified via LANGMEXT,

see 12.9.6);

2.28. Coal Bed Methane Model 180

 19.1

• yi – hydro carbon mole fraction in gas phase for component i;

• p – pressure;

• β – pressure scaling factor (specified by LANGMPL, see 12.9.3).

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.7);

• ρc – coal density (ROCKDEN, see 12.2.108);

• RFi – readsorption factor for component i (RESORB, see 12.9.8);

• 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.72) or for
each grid block (SIGMAV, see 12.2.73).

Palmer–Mansoori rock compaction model.

According to the Palmer–Mansoori model the pore volumes V (p) at the current pressure p is
calculated using the following formula:
   
cm 1 K βp β p0
V (p) = V (p0 ) 1 + (p − p0 ) + −1 −
ϕ0 ϕ0 M 1 + β p 1 + β p0
where
• K is the bulk modulus (METRIC: barsa, FIELD: psia);

• M is the constrained axial modulus (METRIC: barsa, FIELD: psia);

• γ is the grain compressibility (METRIC: 1/barsa, FIELD: 1/psia);

• β is the Langmuir curve parameter (METRIC: 1/barsa, FIELD: 1/psia);

• εl is the Langmuir curve parameter;

• f is the fraction varying from 0 to 1;

2.28. Coal Bed Methane Model 181

 19.1

• n is the exponent in permeability-porosity relationship;

• g is the geometric factor (from 0 to 1) related to the orientation of the fracture system;

• ϕ0 is the initial porosity;

• V (p0 ) is the pore volume at the initial pressure, p0 ;

• cm = Mg − M
K 
+ f −1 γ

Suggesting that permeability varies with porosity as

k ϕ
=
k0 ϕ0

then the transmissibility multiplier is calculated as:

   n
cm 1 K βp β p0
1 + (p − p0 ) + −1 −
ϕ0 ϕ0 M 1 + β p 1 + β p0

Palmer–Mansoori model parameters are specified using the keyword ROCKPAMA

(see 12.5.20).

2.28.1. Coal Bed Methane Model in IM/GE/ST format

Models in the IM/GE/ST formats can consider the desorption of the gas (in black oil models)
or a particular gas component (in compositional models).
Maximum adsorption capacity is specified by ADGMAXC (see 13.6.57).
Adsorption coefficient is specified by ADGCSTC (see 13.6.58).
Diffusion of the gas is characterized in one of the two ways: by the diffusion coefficient
(COAL-DIF-COMP, see 13.6.59) or by the characteristic time of diffusion (COAL-DIF-TIME,
see 13.6.60).

2.29. Geomechanical model

Hydrocarbon simulation in reservoir requires to take into account rock deformation. The ge-
omechanical model is described elastic rock stresses. In this case in addition to the viscous
compressible fluid filtration problem in a porous medium the system of elasticity equations
should be solved.

2.29.1. Fully coupled method

If option FE of the keyword GEOMECH (see 12.1.99) is specified then the fully coupled
approach will be used. In this case the joint system of coupled equations describing filtration
processes in reservoir and geomechanical effects is solved on the unified grid [35].

2.28.1. Coal Bed Methane Model in IM/GE/ST format 182

 19.1

Steady state rock momentum balance equations in the X, Y, Z directions can be written as:
σx τyx τzx
+ + =0
x y z
σy τyx τzy
+ + =0 (2.126)
y x z
σz τxz τzy
+ + + ρg = 0
z x y
where ρ is the the rock density (or a combination of rock and fluid reservoir density) specified
with keyword ROCKDEN (see 12.2.108), g is the acceleration due to gravity constant. The
elastic normal stresses σ and shear stresses τ can be expressed as:

σx = 2Gεx + λ (εx + εy + εz ) − αP
σy = 2Gεy + λ (εx + εy + εz ) − αP
σx = 2Gεz + λ (εx + εy + εz ) − αP
(2.127)
τxy = Gγxy
τxy = Gγxy
τxy = Gγxy

where P is the pore pressure, α is the Biot constant (BIOTC, see 12.2.122). In this case
stresses are total ones since they include pressure P and α . G is the shear modulus, λ are
Lame’s constants, which are functions of Young’s modulus E (YOUNGMOD, see 12.2.120)
and Poisson’s ratio ν (POISSONR, see 12.2.121):
E Eν
G= λ=
2(1 + ν) (1 − 2ν)(1 + ν)

Strains ε and γ are defined in terms of displacements in X, Y, Z directions:

u
εx =
x
v
εy =
y
w
εz =
z
u v
γxy = +
x y
v w
γyz = +
z y
w u
γzx = +
x z
On each side of the grid, i.e., X-, X+, Y-, Y+ and Z-, Z+, either stress or dis-
placement boundary conditions can be chosen. + means the outward normal direction of
this boundary face coincides with the axis direction. - means the outward normal is in

2.29.1. Fully coupled method 183

 19.1

opposite direction. Displacement boundary conditions can be specified via the keyword
GMDISBC (see 12.19.274). Principal stress boundary conditions can be specified via the
keyword GMPSTBC (see 12.19.275). If keywords GMDISBC (see 12.19.274) and/or GMP-
STBC (see 12.19.275) are not set then displacements and/or stresses are assumed to be zero
at boundaries.

!
When using the fully coupled method it is not recommended to specify
keywords ROCK (see 12.5.17), ROCKTAB (see 12.5.21) and ROCKTABH
(see 12.5.22) in a model otherwise compressibility data can be inconsistent.

2.29.2. Successive method

If option EX of the keyword GEOMECH (see 12.1.99) is specified then the successive approach
will be used. In this case the fluid filtration problem and elastic deformation of the rock
problem are solved independently and successively.
At each time step the fluid filtration equation is solved first, then diagonal elements of the
tensor of mechanical stresses are recalculated based on obtained data at the next step:
 
n+1 n Kbulk 1 1
σii = σii + ∆ϕ − ∆p 1 − + , i = 1, 2, 3. (2.128)
α C pp KS C pp K f

where porosity ϕ is a function of pressure and temperature, i.e. ϕ = ϕ(p, T ). Kbulk ,C pp

etc. values used for the calculation are described in the following sections. Initial values of
diagonal elements of the tensor are specified by the keyword ROCKSTRE (see 12.5.28). To
transform a stress tensor into diagonal form we need to rotate the coordinate system axes using
the keyword ROCKAXES (see 12.5.27) such that the rotated axes coincide with principal stress
directions.
Feedback from the elastic deformation of the rock problem occurs if azimuth angle of
fracture is calculated according to the elastic state of the cells (see 2.29.3). In this case the
obtained value of azimuth angle will be taken into account when solving the fluid filtration
equation at the next step.
Calculation of compressibility of the rock matrix and block compressibility

The keyword ROCK (see 12.5.17) specifies the following elastic properties of rocks:

1. pre f – reference pressure;

2. C pp – rock compressibility;
1
3. CR = – compressibility of the rock matrix;
KS
1
4. Cbc = – block compressibility (block that contains mixture);
Kbulk
5. porosity value ϕ0 at reference pressure pre f , if CR is not specified or Cbc ;

2.29.2. Successive method 184

 19.1

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.129)

2. if compressibility of the rock matrix CR is not specified, but ϕ0 , C = C pp are specified:

Cbc
CR = (2.130)
3(1 − ν0 )ϕ0
1+
2(1 − 2ν0 )(1 − ϕ0 )

3. if the value of Poisson coefficient is not specified ν0 :

Cbc
CR = (2.131)
3ϕ0
1+
2(1 − ϕ0 )

4. if C pp is not specified, the default value will be used C pp = 0.00005bars−1

5. if ϕ0 is not specified, the default value will be used ϕ0 = 0.33;

The following relation is used for calculating the Biot constant in each block based on rock
properties, specified in the keyword ROCK (see 12.5.17):
Kbulk CR
α = 1− = 1− . (2.132)
KS Cbc
Mixture K f

The following relationship for K f estimation is used

1 So Sw Sg
= + + , (2.133)
Kf Ko Kw Kg

• SP is the phase concentration, P = W, O, G,

• KP is the coefficient of uniform phase compression, P = W, O, G.

1 ∂ BP
1/KP = CP = − , (2.134)
BP ∂ p
• CP is the phase compressibility (P = W, O, G);

• BP is the Formation Volume Factor (P = W, O, G).

2.29.2. Successive method 185

 19.1

2.29.3. 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.19.145) and GEOMECH (see 12.1.99) 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.19.145), zenith angle is
0◦ .

2.29.4. Mohr-Coulomb failure criterion

In reservoir exploitation modelling it is important to take into account an occurrence of frac-
tures. To take into account reservoir fractures the Mohr–Coulomb failure criterion [36] is used.
It represents the relationship between the shear strength of a rock versus the applied normal
stress:
τ = σ · tan θ + c
where

• τ is the shear stress;

• σ is the normal stress;

• c is the intercept of the failure envelope with the τ axis (specified by keyword COHE-
SION, see 12.5.29);

• θ is the slope of the failure envelope (specified by keyword THETA, see 12.5.30);

According to this theory the failure of strength happens when the unfavourable combina-
tion of normal and shear stresses occurs in some region.

2.29.5. Keywords for the fully coupled method

Keyword Section Description

GEOMECH (see 12.1.99)
GEODIMS (see 12.1.100)
GMDISBC (see 12.19.274)
GMPSTBC (see 12.19.275)
YOUNGMOD (see 12.2.120)
POISSONR (see 12.2.121)
RUNSPEC Specifies geomechanical model describing the
elastic deformation of the rock (mandatory)
RUNSPEC Specifies dimensions of geomechanics data to
be used in calculations
SCHEDULE Specifies displacement boundary conditions
SCHEDULE Specifies principal stress boundary conditions
GRID Specifies Young’s modulus for rock stress bal-
ance (mandatory)
GRID Specifies Poisson’s ratio for rock stress balance
(mandatory)

2.29.3. Calculation of azimuth angle of hydraulic fracture 186

 19.1

BIOTC (see 12.2.122)
ROCKDEN (see 12.2.108)
PERMSTAB (see 12.5.25)
ROCKAXES (see 12.5.27)
COHESION (see 12.5.29)
THETA (see 12.5.30)
GRID Specifies the Biot’s constant for interaction be-
tween rock and fluid
GRID Specifies the rock density
PROPS Specifies permeability multiplier as function of
rock stress in a tabular form
PROPS Specifies the azimuth and zenith angle of the
regional stress
PROPS Specifies the intercept of the failure envelope
with the τ axis
PROPS Specifies the slope of the failure envelope

2.29.6. Keywords for the successive method

All keywords are mandatory.

Keyword Section Description

GEOMECH (see 12.1.99) RUNSPEC Specifies geomechanical model describing the
elastic deformation of the rock (mandatory)
ROCK (see 12.5.17) PROPS Specifies elastic properties of rocks (manda-
tory)
ROCKSTRE (see 12.5.28) PROPS Specifies the diagonal elements of the stress
tensor (the regional stress) (mandatory)
ROCKAXES (see 12.5.27) PROPS Specifies the azimuth and zenith angle of the
regional stress (mandatory)

2.29.6. Keywords for the successive method 187

 19.1

3. Compositional model
The number of components should be set via the keyword COMPS (see 12.14.1).
For every component (CNAMES, see 12.14.3) user defines:
• Tci – critical temperature of ith component, TCRIT (see 12.14.20),
• pci – critical pressure of ith component, PCRIT (see 12.14.22),
• ωi – acentric factor of ith component, ACF (see 12.14.38),
• ci j – binary interaction coefficients, BIC (see 12.14.40).
For some components default values of parameters may be used (TCRIT (see 12.14.20),
PCRIT (see 12.14.22), VCRIT (see 12.14.24), MW (see 12.14.30), BIC, see 12.14.40). In this
case component properties will be taken from the internal database (see [24]) in compliance
with their names indicated in CNAMES (see 12.14.3).

For water and rock property the same keywords can be used as for black oil model
(PVTW (see 12.5.5), ROCK (see 12.5.17), DENSITY (see 12.5.33), SWOF (see 12.6.1), SGOF
(see 12.6.2) and other).
To change convergence settings for compositional flash (calculation of processes with
vapor/liquid–equilibrium) the keyword FLASHCTRL (see 12.1.6) should be used.

3.1. Vapor-liquid equilibrium

When solving fluid filtration equations, it is required to define phase mole fractions FP and
moles of component i per mole of phase P xi P . In oder to obtain FP and xi P flash calculations
at specified pressure and temperature are used [38].
Let water phase be inert due to poor solubility of hydrocarbons in water. Then the two-
phase vapor-liquid system consisting of N = nc − 1 components can be considered. Let us
suppose that a hydrocarbon mixture splits into two phases, which are in thermodynamic equi-
librium at fixed pressure p, temperature T and composition zi = Ni / ∑Nj=1 N j . The distribution
coefficients (K-values) Ki of component i between equilibrium phases are calculated as:

Ki = xiV /xi L , i = 1, . . . , N (3.1)

Thus, a flash calculation (calculation of two-phase vapor-liquid equilibrium) is equivalent

to solving a system of nonlinear algebraic equations for N + 1 unknown variables Ki , FV
[39]:

lnϕi L − lnϕiV − lnKi = 0, i = 1, . . . , N

N (3.2)
(Ki − 1)zi
 ∑
 =0
i=1 1 + (Ki − 1)FV
Here ϕi P = ϕi P (p, T, N) is a fugacity coefficient of component i in phase P. In the system (3.2)
N first equations are conditions of equality of component chemical potentials in equilibrium

3. Compositional model 188

 19.1

phases [38], the last equation is the continuity condition, the so–called Rachford–Rice equation
[41].
Logarithms of fugacity coefficients are calculated as:
 m
2 ∑ j=1 Ai j x j,P Bi

C A ZP + m2 B Bi (ZP −C)
ln ϕi P = ln + − ln + (3.3)
ZP − B (m1 − m2 )B A B ZP + m1 B B

where

• ZP , P = V, L are Z-factors for vapor (P = V ) and liquid (P = L ) phases;

• constant coefficients of equation of state A, B, Ai j and etc. are indicated in the section
3.5.

At initial step the pressure p, temperature T , molar mixture composition zi different

from critical (Ki 6= 1), and the constant coefficients of equation of state (see section 3.5) are
specified.
If there is no initial approximation of K-values then the Wilson correlation [38] is used:


0 exp 5.373(1 + ωi )(1 − 1/Tr i )
Ki = , i = 1, . . . , N (3.4)
pr i
where pr i and Tr i are calculated using formulas from the section 3.5 and ωi is acentric factor
of ith component.

3.2. Phase stability test

The main complication of a flash calculation is that a mixture splits into unknown number of
equilibrium phases. A non trivial solution of the system (3.2) exists only if it is supposed that
the mixture is in a two-phase equilibrium state.
Therefore, it is required an effective method to test a stability of single-phase state [40]
in oder to optimize a flash calculation. If a phase stability test shows that the hydrocarbon
mixture is in a stable single-phase state then a flash calculation (3.2) is not required, otherwise
results of this approach is used as an initial approximation for the flash calculation (3.2).
The stability test is based on the stability criterion of thermodynamic system. According
to this criterion a system is in a stable state at fixed pressure p and temperature T if there is
no another stable state with lower Gibbs energy [38].
Let’s consider a hydrocarbon mixture with a molar composition ni (i = 1, . . . , N ). If the
mixture is in single-phase state then its Gibbs energy is G0 = G(n1 , . . , nN ). Let’s suppose
that the mixture splits into two phases (I and II) with compositions (n1 − ε1 , . . , nN − εN ) and
(ε1 , . . , εN ), respectively. Then the initial mixture is in a stable single-phase state if for any
small value ε > 0 and any composition of II phase with mole fractions yi = εi /ε the following
condition is satisfied:
GI + GII − G0 ≥ 0 (3.5)

3.2. Phase stability test 189

 19.1

3.3. Vapor-liquid-water equilibrium

Let’s consider a hydrocarbon mixture consisting of nc components at specified pressure p,
temperature T and composition zi (i = 1, . . . , nc ). Let’s assume that one of mixture compo-
nents is water (i = w) and hydrocarbon components are highly soluble in water. Therefore, a
water phase can not be treated as inert one and can not be excluded from a consideration.
Let’s suppose that from hydrocarbon components only CO2 (i = co2) (or H2 S ) is soluble
in water, other components can be only in oil and gas phases, while a water component can
be only in water phase. Formulas shown below are obtained for modeling of CO2 solution.
Formulas are similar for modeling of H2 S solution.
Under thermobaric conditions the hydrocarbon mixture splits into vapor, liquid and water
phases that are in thermodynamic equilibrium. Distribution coefficients of ith component
between equilibrium phases are calculated via K-values KiV , KiW :

KiV = xiV /xi L , i = 1, . . . , nc (3.6)

Kco2W = xco2W /xco2 L (3.7)

Mole fractions of components in phases (vapor, liquid and water) xiV , xi L , xiW are calcu-
lated via K-values KiV , KiW and mole fractions of phases FV , FL , FW are calculated similar
to the two-phase case:
KiV zi
xiV = , i = 1, . . , w,
b dco2, . . , nc (3.8)
FL + KiV FV
zi
xi L = , i = 1, . . , w,
b dco2, . . , nc (3.9)
FL + KiV FV

Kco2V zco2
xco2V = , (3.10)
FL + Kco2V FV + Kco2W FW
zco2
xco2 L = , (3.11)
FL + Kco2V FV + Kco2W FW

Kco2W zco2 zw
xco2W = , xwW = (3.12)
FL + Kco2V FV + Kco2W FW FW

Taking into account a formula ∑ni=1

c
xi P = 1 for phases P = W, V, L and formulas (3.8 –
3.12) the system of equations of material balance can be obtained. This system is similar to

3.3. Vapor-liquid-water equilibrium 190

 19.1

the Rachford-Rice equation [41] for the three-phase case:



 (Kco2V − 1)zco2




 1 + (Kco2V − 1)FV + (Kco2W − 1)FW

(KiV − 1)zi


+ ∑ = 0,


i6={w,co2} (1 − FW ) + (KiV − 1)FV




(3.13)
(Kco2W − 1)zco2





 1 + (Kco2V − 1)FV + (Kco2W − 1)FW




(−1)zi zw


+ ∑ + =0


i6={w,co2} (1 − FW ) + (KiV − 1)FV

 FW

Thus, the three-phase flash calculation (calculation of three-phase vapor-liquid-water equi-

librium) [40, 42] is to solving a system of nonlinear algebraic equations for nc +2 independent
variables KiV (i 6= w), Kco2W , FV , FW :

lnKco2W + ln ϕco2W − ln ϕco2 L = 0,










 lnKiV + ln ϕiV − ln ϕi L = 0, i = 1, . . , w,b . . , nc



(Kco2V − 1)zco2








 1 + (Kco2V − 1)FV + (Kco2W − 1)FW

(KiV − 1)zi (3.14)
+ ∑ = 0,



 i6={w,co2} (1 − FW ) + (K iV − 1)FV




(Kco2W − 1)zco2








 1 + (Kco2V − 1)FV + (Kco2W − 1)FW

(−1)zi zw


+ ∑ + =0




i6={w,co2} (1 − F ) + (K − 1)F
W iV V W F

Here the first nc equations describe the condition of thermodynamic equilibrium (equality
of fugacities of components in equilibrium phases), the last 2 equations describe a material
balance of components in phases.
W is supposed to calculate from the condition of phase equilib-
A fugacity coefficient ϕco2
rium of binary saturated system CO2 /water [37]:

xW,sat V,sat V,sat W,sat

co2 /xco2 = ϕco2 /ϕco2 . (3.15)

Let’s suppose that mole fraction of water in the vapor phase is low, then an estimation
xV,sat
co2 ≈ 1 is correct, and the fugacity coefficient of CO2 in water phase can be approximaty
calculated as:

W V,sat W,sat
ϕco2 ≈ ϕco2 /xco2 . (3.16)

3.3. Vapor-liquid-water equilibrium 191

 19.1

V,sat
Here the fugacity coefficient of CO2 in the vapor phase ϕco2 (p, T ) is calculated using
the equation of state by the formula (3.3), the mole fraction of CO2 in the water phase xW,satco2
can be calculated as a function of pressure and temperature:
sol
Nco2 Rsat
s,co2 (p, T )
xW,sat
co2 = = sc , (3.17)
sol
Nw + Nco2 Rsat sc
s,co2 (p, T ) + ξco2 /ξW

sol is the mole fraction of CO dissolved in water, ξ sc and ξ sc are molar densities of
where Nco2 2 co2 W
CO2 and water, respectively, specified in the fluid filtration model, Rsat
s,co2 (p, T ) is solubility
of CO2 in water, it can be calculated using the correlation from [37]. Thus, CO2 in the
water phase does not depend on composition of hydrocarbon mixture and is a function of
temperature and pressure.
For the solution of system (3.14) using a method of successive approximation the initial
0
approximation Kco2W can be specified by the formula [44]:
 b
0 10 T − 273.15
Kco2W = , (3.18)
p a

where a = 180.89, b = 0.2350 are constant coefficients.

3.3.1. CO2/H2S solution in the aqueous phase

CO2 or H2 S solution in the aqueous phase option is activated using the keywords CO2SOL
(see 12.1.92) and H2SSOL (see 12.1.93), respectively, in the section RUNSPEC.
If option VLW_FLASH of the keyword FLASHCTRL (see 12.1.6) is set equal to 1 then a
three-phase flash calculation for a system vapor-liquid-water is used. A fugacity function of
dissolved gas (CO2 or H2 S ) for water phase is a function of pressure and temperature and
calculated using the phase equilibrium between dissolved gas and water (see section 3.4).
Properties of water-gas (CO2 or H2 S ) system are specified in tabular form by SOLUBILI
(see 12.14.70). It is not required to specify SOLUBILI (see 12.14.70) since for CO2 a default
set of data is provided. In this set of data CO2 solubility is calculated from the correlations
[37], water compressibility and viscosity are taken from the PVTW (see 12.5.5) data. For H2 S
there is no default data.
Initial concentration of dissolved gas (CO2 or H2 S ) are specified by RSW (see 12.16.56)
in tabular form. RSWVD (see 12.14.71) specifies a table of gas (CO2 or H2 S ) concentration
in water phase versus depth.
If the option VLW_FLASH of the keyword FLASHCTRL (see 12.1.6) turns off (set equal to
0), then the distribution of (CO2 or H2 S ) component between water and hydrocarbon phases
is set via data table as a function of pressure.

3.4. Hydrocarbon-water phase equilibrium

Modeling of dissolution of CO2 (or H2 S ) in the vapor-liquid-water system it is required to
calculate dissolved gas-water phase equilibrium. Let’s assume that a hydrocarbon phase is gas.

3.3.1. CO2/H2S solution in the aqueous phase 192

 19.1

Formulas shown below are obtained for modeling of CO2 solution. Formulas are similar for
modeling of H2 S solution.
If CO2 is a single hydrocarbon component in the system it is possible that it can totally
dissolve in water under certain thermobaric conditions. This can happen if Nco2 ξWsc /(Nw ξco2
sc ) ≤

Rsat sat
s, co2 (p, T ), where Rs, co2 (p, T ) is the solubility limit of CO2 in water (3.17).
Let’s a hydrocarbon mixture containing at least two hydrocarbon components, including
CO2 , splits into equilibrium phases then formulas (3.8-3.12) can be rewritten as:

xiV = zi /FV , i = 1, . . , w,
b dco2, . . , nc
xco2V = zco2 / (FV + Kco2W FW ) , xwW = zw /FW ,
xco2W = Kco2W zco2 / (FV + Kco2W FW ) FW

The problem of two-phase liquid-water equilibrium is described by the system of 2 alge-

W , F :
braic equation for 2 independent variables Kco2 W

Φ1 = lnKco2W + lnϕco2W − lnϕco2V = 0,



nc (3.19)
zw (Kco2W − 1)zco2 (−1)zi
= + + ∑ 1 − FW = 0


Φ
 2 FW 1 + (Kco2W − 1)FW
i6={w,co2}

The system of (3.19) is a special case of the system (3.2) and can be calculated by the
method of successive approximation [39]. To obtain the initial approximation Kco2W 0 the
formula (3.18) is used, the fugacity coefficient of CO2 in a hydrocarbon phase is calculated
using the formula (3.3), and the fugacity coefficient of CO2 in a water phase using the formula
(3.16).

3.5. Equations of state

The following equations of state are considered
RT a
p= − . (3.20)
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 type of equation of state for each EoS region is
specified by EOS (see 12.14.6). 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 overridden via the keywords OMEGAA
(see 12.14.42) and OMEGAB (see 12.14.42).

3.5. Equations of state 193

 19.1

The equation (3.20) divided by p is:

1 A
− = 1, (3.21)
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.22)
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.14.22), TCRIT,
see 12.14.20), βi j — pair interaction coefficients of components (BIC, see 12.14.40), Ωa and
Ωb depends on the Equation of state:

RK : Ωa (T, i) = Ωa0 Tri−0.5 ,

Ωb (T, i) = Ωb0 ,
 2
SRK : Ωa (T, i) = Ωa0 1 + (0.48 + 1.574ωi − 0.176ωi2 )(1 − Tri0.5 ) ,
Ωb (T, i) = Ωb0 ,
 2
PR : Ωa (T, i) = Ωa0 1 + (0.37464 + 1.54226ωi − 0.26992ωi2 )(1 − Tri0.5 ) ,
Ωb (T, i) = Ωb0 ,
 2
PR∗ : 2 3 0.5
Ωa (T, i) = Ωa0 1 + (0.379642 + 1.48503ωi − 0.164423ωi + 0.016666ωi )(1 − Tri ) ,
if ωi > 0.49.

Where ωi — acentric factor of the component (ACF, see 12.14.38), Modification of Peng-
Robinson equation PR∗ is used if the keyword PRCORR (see 12.14.49) is specified. Tem-
perature T is fixed and it is specified via the keywords RTEMP (see 12.14.10) or TEMPVD
(see 12.15.84).

3.5. Equations of state 194

 19.1

3.5.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.14.39),
BICS (see 12.14.41), OMEGAAS (see 12.14.43), OMEGABS (see 12.14.43), MWS
(see 12.14.31), PCRITS (see 12.14.23), SSHIFTS (see 12.14.51), TCRITS (see 12.14.21),
VCRITS (see 12.14.25), ZCRITS (see 12.14.28).

The following keywors are used for EOS in reservoir conditions: ACF (see 12.14.38),
BIC (see 12.14.40), OMEGAA (see 12.14.42), OMEGAB (see 12.14.42), MW (see 12.14.30),
MWW (see 12.14.32), PCRIT (see 12.14.22), TCRIT (see 12.14.20), VCRIT (see 12.14.24),
ZCRIT (see 12.14.27), SSHIFT (see 12.14.50), VSHIF1 (see 12.14.52), TREFVS (see 12.14.53).

If any (or all) keywords for surface EOS are not specified then these parameters are taken
from reservoir condition keywords by default.

A different EOS to use in surface conditions can be specified using the keyword EOSS
(see 12.14.7).

3.6. Empirical correlations for EOS parameters

In case if EOS parameters of a compound are not known, it is possible to reconstruct them
from empirical correlations. This can be done on the preparation stage in PVT Designer, or
(for models in GE format) during the calculaion.
The following correlations are available in PVT Designer:
• Riazi and Daubert;
• Kesler and Lee;
• Cavett;
• Twu.
All correlations are based on specific gravity and molecular weight. If the specific gravity
is not available, it is also calculated by correlation [10]:
ρ = 0.86715 + 3.41434 · 10−3 n − 2.8396 · 10−5 n2 + 2.49433 · 10−8 n3 − 1.1628/n,
where n is the number of carbon atoms in molecule calculated from molecular weight (con-
sidering the compound a saturated alkane). At n > 45, another correlation takes over:
ρ = 0.1129 ln(n) + 0.5203
Correlations of Riazi and Daubert, Kesler and Lee, and Twu can be applied during the
calculation using the keyword CRIT (see 13.5.8).

3.5.1. EOS in reservoir and surface conditions 195

 19.1

3.6.1. Riazi and Daubert

Riazi and Daubert (1987) developed a set of equations to calculate properties of components
using specific gravity γ and molecular weight M . Boiling point Tb is used for calculations
and is not recorded. Tb calculation depends on the M value.
If M < 300:

Tb = 3.76587 exp(3.7741 × 10−3 M + 2.98404γ − 4.25288 × 10−3 Mγ)M 0.40167 γ −1.58262 ,

if M ≥ 300:

Tb = 9.3369 exp(1.6514 × 10−4 M + 1.4103γ − 7.5152 × 10−4 Mγ)M 0.5369 γ −0.7276 .

Other properties are calculated using Tb and specific gravity γ .

• Critical temperature

Tc = 9.5233Tb0.81067 γ 0.53691 exp(−9.314 × 10−4 Tb − 0.544442γ + 6.4791 × 10−4 Tb γ).

• Critical pressure

pc = 3.1958 × 105 Tb−0.4844 γ 4.0846 exp(−8.505 × 10−3 Tb − 4.8014γ + 5.749 × 10−3 Tb γ).

• Critical volume

Vc = 6.2 × 107 Tb1.20493 γ 17.2074 exp(−7.58 × 10−3 Tb − 28.5524γ + 1.172 × 10−2 Tb γ).

• Acentric factor (Edmister’s correlation)

   
3 pc Tc
ω = ln − 1 − 1.
7 1.01325 Tb

3.6.2. Kesler and Lee

Kesler and Lee (1976) developed a set of equations to calculate properties of components
using specific gravity γ and molecular weight M .
A boiling point Tb is used in internal calculations and is not recorded. Tb is calculated as:

Tb = 1071.28−94170M −0.03522 γ 3.266 exp(−4.922×10−3 M −4.7685γ +3.462×10−3 Mγ).

Other properties are calculated using Tb and specific gravity γ .

• Critical temperature

(0.1441 − 1.0069γ)105
Tc = 189.8 + 450.6γ + (0.4244 + 0.1174γ)Tb + .
Tb

3.6.1. Riazi and Daubert 196

 19.1

• Critical pressure
  
0.0566 4.1216 0.21343 Tb
pc = exp 5.689 − γ − 0.43639 + γ + γ 2 103
+

1.182 0.15302 Tb2 9.9099 Tb3

   
+ (0.47579 + + − 2.4505 + .
γ γ2 106 γ2 1010

• Acentric factor

−7.904 + 0.1352K − 0.007465K 2 + 8.359Tbr + (1.408−0.01063K) ,
 Tbr > 0.8
Tbr
ω = − ln( pc )−5.92714+ 6.09648 +1.28862 ln(Tbr )−0.169347T 6
14.696 Tbr br

 15.6875 6 , Tbr ≤ 0.8
15.2518− Tb r −13.4721 ln(Tbr )+0.43577Tbr

Tb 1/3
where Tbr = Tc and K = Tb /γ .
• Critical volume
RTc Zc
Vc =
,
M pc
where Zc = 0.2905 − 0.0850ω is a critical compressibility factor.

3.6.3. Cavett
Cavett (1962) developed a set of equations to calculate properties of components using specific
gravity γ and molecular weight M . Boiling point Tb is used in internal calculations and is
not recorded. Tb is calculated as:

Tb = 1071.28−9.417×104 M −0.03522 γ 3.266 exp(−4.922×10−3 M −4.7685γ +3.462×10−3 Mγ).

Denoting API = 141.5/γ − 131.5 and F = 1.8Tb − 459.67. Then:
• Critical temperature

Tc = 426.7062278 + 0.95187183F − 6.01889 × 10−4 F 2

− 4.95625 × 10−3 (API)F + 2.160588 × 10−7 F 3
+ 2.949718 × 10−6 (API)F 2 + 1.817311 × 10−8 (API 2 )F 2 .

• Critical pressure
pc = 10k ,
where

k = 1.6675956 + 9.412011 × 10−4 F − 3.047475 × 10−6 F 2

− 2.087611 × 10−5 (API)F + 1.5184103 × 10−9 F 3
+ 1.1047899 × 10−8 (API)F 2 − 4.8271599 × 10−8 (API 2 )F.
+ 1.3949619 × 10−10 (API 2 )F 2 .

3.6.3. Cavett 197

 19.1

• Acentric factor (Edmister’s correlation)

   
3 pc Tc
ω = ln − 1 − 1.
7 1.01325 Tb

• Critical volume (Reidel’s correlation)

10.732Tc
Vc = .
M pc (3.72 + 0.26(5.811 + 4.919ω − 7))

3.6.4. Twu
Twu (1984) initially calculates critical properties (Tc0 , Pc0 ,Vc0 ), specific gravity γ0 and molecu-
lar weight of n-alkanes to the boiling point Tb . The obtained data are then used as parameters
to correlate undefined critical properties of component with defined specific gravity γ and
molecular weight M .
Boiling point Tb is used in internal calculations and is not recorded.

Tb = 1071.28 − 9.417 × 104 M −0.03522 γ 3.266 exp(−4.922 × 10−3 M

− 4.7685γ + 3.462 × 10−3 Mγ).

• Critical temperature
 2
(1 + 2 fT )
Tc = Tc0 ,
(1 − 2 fT )
where

Tc0 = Tb /(0.533272 + 0.34383 × 10−3 Tb + 2.52617 × 10−7 Tb2 − 1.658481 × 10−10 Tb3
+ 4.60773 × 1024 Tb−13 ),

fT = ∆γT (−0.27016/Tb0.5 + (0.0398285 − 0.706691/Tb0.5 )∆γT ),

∆γT = exp(5(γ0 − γ)) − 1,
γ0 = 0.843593 − 0.128624α − 3.36159α 3 − 13749.5α 12 ,
α = 1 − Tb /Tc0 .

• Critical volume  2
(1 + 2 fV )
Vc = Vc0 ,
(1 − 2 fV )
where
∆γV = exp(4(γ02 − γ 2 )) − 1,
fV = ∆γV (0.347776/Tb0.5 + (−0.182421 + 2.248896/Tb0.5 )∆γV ).

3.6.4. Twu 198

 19.1

• Critical pressure
 2
(1 + 2 f p )
pc = p0c (Tc /Tc0 )(Vc /Vc0 ) ,
(1 − 2 f p )
where

p0c = (1.00661 + 0.31412α 0.5 + 9.16106α + 9.5041α 2 + 27.35886α 4 )2 ,

fP = ∆γP ((2.53262−34.4321/Tb0.5 −2.30193Tb ×10−3 )+(−11.4277+187.934Tb−0.5

+ 4.11963Tb × 10−3 )∆γP ),

∆γP = exp(0.5(γ0 − γ)) − 1.

• Acentric factor (Edmister’s correlation)

   
3 pc Tc
ω = ln − 1 − 1.
7 1.01325 Tb

3.7. Density
For equation of state RK, SRK and non-shifted PR EOS (EOS, see 12.14.6) phase molar
density of each phase P is defined by formula:
p
ξP = . (3.23)
ZRT
Equation of state with shifts (shifted PR EOS):
, !
n
ZRT 

ξP = 1 − ∑ zi bi si + sti · Tres − Tre f vs , (3.24)
p i=1

Where:

• zi — molar concentration of component i in phase P;

• si — shift parameter of the component i, specified via the keyword SSHIFT

(see 12.14.50);

• sti — temperature gradient for volume shift of the component i, specified via the key-
word VSHIF1 (see 12.14.52);

• Tres — reservoir tempearture;

• Tre f vs — reference tempearture for linear temperature-dependent volume shift model

specified via TREFVS (see 12.14.53);

• bi = Ωb RT ci
pci .

3.7. Density 199

 19.1

Phase mass density is calculated by the formula

ρP = ξP MwP , (3.25)

where MwP average molecular weight of phase P,

N
MwP = ∑ Mwi ci , (3.26)
i=1

N N
MwO = ∑ Mwi xiO , MwG = ∑ Mwi xiG (3.27)
i=1 i=1

Mwi are component molecular weights, MW (see 12.14.30), MWW (see 12.14.32) and xiP are
concentrations of component i in phase P.

3.8. Viscosity
For water phase viscosity is constant (PVTW, see 12.5.5). For hydrocarbons by default the
method Lohrenz-Bray-Clark Correlation is used (see section 3.8.1).
PEDERSEN (see 12.14.65) keyword specifies that viscosities will be calculated via Pedersen’s
method (see section Pedersen Correlation).

3.8.1. Lohrenz-Bray-Clark Correlation

In viscosity calculation of µP the correlation Lohrenz-Bray-Clark is used

1/4
(µP − µP∗ )χ + 10−4 2
= a1 + a2 ξrP + a3 ξrP 3
+ a4 ξrP 4
+ a5 ξrP . (3.28)

Where:

• ξrP = ξP /ξc .

• a1 = 0.1023000, a2 = 0.0233640, a3 = 0.0585330, a4 = −0.0407580, a5 = 0.0093324.

These coefficients can be overridden via the keyword LBCCOEF (see 12.14.44). One
should use the keyword LBCCOEFR (see 12.14.45) to set different coefficients for each
equation of state region.

• χ - function of molecular weights, critical temperature and critical pressure.

!1/6 !−1/2 !−2/3

N N N
χ= ∑ ziTci ∑ ziMwi ∑ zi pci . (3.29)
i=1 i=1 i=1

3.8. Viscosity 200

 19.1

Critical temperatures Tci (TCRIT, see 12.14.20), critical pressures pci (PCRIT, see 12.14.22)
and molecular weights Mwi (MW (see 12.14.30), MWW, see 12.14.32) are user defined.

Phase molar density ξP is defined in the section 3.7.

Critical molar density ξc is calculated via the following formula
!−1
N
ξc = ∑ ciVci , (3.30)
i=1
where Vci – critical molar volume of the component i, specified by user (keywords VCRIT
(see 12.14.24), VCRITVIS, see 12.14.26) or calculated from critical Z-factors (keyword ZCRIT
(see 12.14.27), ZCRITVIS, see 12.14.29).
Dilute gas mixture viscosity µ ∗ is calculated from
! !−1
N N
1/2 1/2
µ∗ = ∑ zi µi∗Mwi ∑ ziMwi . (3.31)
i=1 i=1
where dilute gas viscosities for individual component i, µi∗ , are defined as

∗
 34 × 10−5 Tri0.94 /χi , Tri ≤ 1.5
µi = (3.32)
17.78 × 10−5 (4.58Tri − 1.67)0.625 /χi , Tri > 1.5


and
1/6 −1/2 −2/3
χi = Tci Mwi pci . (3.33)

3.8.2. Modified Lohrenz-Bray-Clark Correlation

This correlation can be obtained by modifiying the equation 3.28:
 
ξrP
 
max
ξrP − ξrP
∗ −4 1/4 2 3 4


(µP − µP )χ + 10 = a1 + a2 ξrP + a3 ξrP + a4 ξrP + a5 ξrP × e (3.34)
!−1
N
max
ξrP = ∑ ciVmini (3.35)
i=1
Where Vmini – minimum molar volume of the component i. It can be specified via keyword
VCOMPACT (see 12.14.46).

3.8.3. Pedersen Correlation

Detailed description of Pedersen correlation is in [25]. It sets via the keyword PEDERSEN
(see 12.14.65).

User parameters for Pedersen correlation can be set via the keywords PEDTUNE
(see 12.14.66), PEDTUNER (see 12.14.67).

3.8.2. Modified Lohrenz-Bray-Clark Correlation 201

 19.1

3.9. Lumping
Lumping is a creation of a pseudocomponent with calculated effective properties based on
multiple actual components. It serves to decrease the number of variables during the calcula-
tion. Lumping may be performed in PVT Designer prior to calculations of the model.
The hydrodynamic calculations engine treats the lumped pseudocomponent as a single
user-defined component with specified properties. The addition of keywords LUMPDIMS
(see 12.14.8), LUMPING (see 12.14.9), DETAILMF (see 12.14.4), and DETAILVD (see 12.14.5)
make it possible to derive the contents of the original components in the fluid after the calcu-
lation. In this case the original components are interpreted as tracers, and their concentrations
become available in the GUI:

• as grids on the tab Grid Properties in the node Calculated → ASP Flood and Tracers;

• as graphs on the tab Graphs in the node Tracers.

3.10. Multiple water component model

For isothermal compositional models option of multiple component water is supported via the
following keywords:

• COMPW (see 12.14.2) – activation of multiple water component option in a model and
setting the number of water components;

• WNAMES (see 12.15.49) – associating a synonymous string with each component for
reporting purposes;

• PREFW (see 12.14.34) – setting of reference pressure values for water components;

• PREFWS (see 12.14.35) – setting of reference pressure values for water components
that will be used in surface calculations;

• DREFW (see 12.14.36) – setting of water components’ densities at reference pressure;

• DREFWS (see 12.14.37) – setting of water component densities values that will be used
in surface calculations;

• MWW (see 12.14.32) – setting of water components’ molecular weights;

• MWWS (see 12.14.33) – setting of water components’ molecular weights that will be
used in surface calculations;

• VREFW (see 12.15.44) – setting of reference viscosity and viscosibility values for water
components;

• CREFW (see 12.15.46) – setting of compressibility values for water components;

• WI (see 12.15.47) – setting of water composition;

3.9. Lumping 202

 19.1

• WMF (see 12.16.60) – setting of initial molar concentration of water components in each
grid block;

• WMFVD (see 12.15.48) – setting of initial molar concentration of water components in

each grid block;

• AQSTREAW (see 12.17.7) – setting of aquifer’s molar concentration of water compo-

nents;

• WELLSTRW (see 12.19.185) – specifying the composition of injected water stream;

• WINJW (see 12.19.180) – specifying the nature of injected water.

The water component density values, at pressure P, are calculated from:

ρW = ρre fW · (1 + X + X 2 /2),
where:

• X = −cPW · (P − Pre fW );

• ρre fW is the reference density values, specified with keyword DREFW (see 12.14.36);

• CPW is the water component compressibility values, specified with keyword CREFW
(see 12.15.46);

• Pre fW is the reference pressure values, specified with keyword PREFW (see 12.14.34).

The water component viscosity values, at pressure P, are calculated from:

µW = µre fW · (1 +Y +Y 2 /2)
where:

• Y = −cVW · (P − Pre fW );

• µre fW is the reference viscosity values, specified with keyword VREFW (see 12.15.44);

• cVW is the viscosibility values, specified with keyword VREFW (see 12.15.44);

• Pre fW is the reference pressure values, specified with keyword PREFW (see 12.14.34).

3.10. Multiple water component model 203

 19.1

3.11. Diffusion
A diffusion is a penetration of particles of one substance between particles of another sub-
stance from a region of high concentration to a region of low concentration, i.e. the movement
of a substance caused by a concentration gradient leading to a aligning concentration.
In tNavigator the model of molecular diffusion caused by a concentration gradient is
implemented. In this model the molar flux of component i per unit area per unit time is
calculated as:
Qi = −c · Di · ∇xi
where

• c – is the total molar concentration given by c = 1/vm (METRIC: kg-mol/rm3 ; FIELD:

lb-mol/rb);

• vm – is the molar volume of the mixture;

• Di – is the diffusion coefficient of component i (METRIC: m2 /day, FIELD: f t 2 /day),

given by keywords DIFFCOIL (see 12.14.59) and DIFFCGAS (see 12.14.58);

• ∇ = ∂ /∂ d – is the gradient in the direction of flow;

• xi – is the mole fraction of component i.

3.11.1. The cross phase diffusion

Along with diffusion of oil and gas components within oil and gas phases, respectively, the
diffusion of components between the phases should be taken into account. In tNavigator the
cross phase diffusion option is implemented (only for compositional models in E3 format).
The cross phase oil – gas and gas – oil diffusion coefficients are specified by DIFFCGO
(see 12.14.60) and DIFFCOG (see 12.14.61) keywords.
In tNavigator the cross phase diffusion problem is simplified to the problem of diffusion
of components within one phase. On the border between neighboring blocks an artificial
buffer zone is created as shown schematically in the figure 18. It is assumed that in this
region the fluids are mixed and the mixture composition is a result of mixing compositions of
these blocks. The resulting composition is used to define the potential for molecular diffusion
of each component. A molar flux of component between phases is a diffusive flow of this
component cross the buffer zone within one phase. If a component concentration in a block is
higher than its concentration in the buffer zone it is supposed that a component incoming in
the buffer zone with one phase is diffused to another phase.
Let’s consider two blocks I and J , containing oil and gas, respectively. The buffer zone
composition is calculated as:
ei = (ξo · xi )I + (ξg · yi )J ,
m
where

• ξo – is the oil molar density;

3.11. Diffusion 204

 19.1

Figure 18. Sketch of the cross phase diffusion

• xi – is the oil mole fraction of component i;

• ξg – is the gas molar density;

• yi – is the gas mole fraction of component i.

The buffer zone pressure and temperature are equal to half–sum of pressure and tempera-
ture specified in neighbouring blocks:
PI + PJ TI + TJ
Pe = , Te =
2 2

Let’s denote oil and gas molar density in buffer zone as xei and yei , respectively, and ξeo
and ξeg as their molar density, respectively. As an example, assuming xi > xei and yi > yei two
diffusive flows of component i occur: from oil phase to gas phase FXog and from gas phase
to oil phase FYgo (see figure 18). FXog is flow of component i from block I to the buffer
zone within oil phase. FYgo is flow of component i from block J to the buffer zone within
gas phase.
The cross phase diffusive flow between the oil in cell I and the gas in cell J for component
i is calculated as:

F = FXog + FYgo ,
FXog = Di f f × Dogi × min(SoI , SgJ ) × ξO × (xi − xei , 0),
FYgo = Di f f × Dgoi × min(SoI , SgJ ) × ξG × (xi − xei , 0),

where

• SI and SJ are the oil and gas saturations in cell I and J , respectively;

• Di f f is the diffusivity;

3.11.1. The cross phase diffusion 205

 19.1

• Dogi and Dgoi are the cross phase oil – gas (specified by keyword DIFFCOG,
see 12.14.61) and gas – oil (specified by keyword DIFFCGO, see 12.14.60) diffusion
coefficients, respectively.

3.12. Solid phase

Solid components can be suspended in the oil phase or can be deposited on to the formation.
Suspended solids are transfered with the flow. Deposition of solids leads to reduction in the
pore volume available for flow.

3.12.1. Keywords

Keyword Section Description

SOLID (see 12.1.61) RUNSPEC Indicates that there is a solid phase in the mode
SOLIDMMC (see 12.13.1) PROPS Specifies tables of mobility multiplier as a
function of adsorbed solid concentration
SOLIDMMS (see 12.13.2) PROPS Specifies tables of mobility multiplier as a
function of adsorbed solid saturation
SOLIDADS (see 12.13.3) PROPS Specifies tables of solid adsorption function
ROCKDEN (see 12.2.108) GRID Specifies the rock density

3.13. Simulation of nonequilibrium thermodynamics

In real systems, forward and reverse physical processes may go at widely different rates.
For example, gas dissolution is much slower than gas liberation from oil. A nonequilibrium
process is one with duration comparable to or exceeding the characteristic time of variation
of external conditions.
It is assumed that thermodynamical processes run at equilibrium conditions. However,
when the grid block size in a model is large and time step is small, the deviations from
equilibrium can significantly affect the simulation results.
In tNavigator several approaches are implemented to simulate nonequilibrium processes.
For black oil models, gas solubility in oil is simulated using the following keywords: DRSDT
(see 12.19.115), DRSDTVP (see 12.19.117), DRSDTVPE (see 12.19.118). For compositional
models three methods are available in tNavigator: methods 1 and 2 based on the approach
from [45] and method 3 is referred to as DKDT method.

3.13.1. Methods 1 and 2 for simulation of nonequilibrium processes

In [45] the condition of equality of components’ chemical potentials in different phases is
suggested to be replaced by the condition of relaxation of chemical potentials difference to
zero when a system tends to the equilibrium state after a modification of external parameters

3.12. Solid phase 206

 19.1

(pressure and mixture composition). The system of equations describing vapor-liquid state
(3.2) can be rewritten as: 
ln ϕi L − ln ϕiV − ln Ki = ωi

(Ki − 1)zi (3.36)
∑N

i=1 = 0.
1 + (Ki − 1)FV
where

• ωi = (ln(ϕiV
∗ ) − ln(ϕ ∗ ) − ln(K ∗ ))e−αdt ;
iL i
Equation terms having a symbol * are calculated using Ki from the previous time step,
while composition zi and pressure are taken from the current time step.

The main complication of methods for simulation of nonequilibrium thermodynamics in

compositional models is to identify a nonequilibrium state. Let’s consider thermodynamical
processes of phase transitions. The formation of a new phase takes place in all volume of
the mixture, hence this process can be considered as equilibrium. A reverse transition into a
single-phase state takes place at the limited surface, hence it is a nonequilibrium process.
A phase is supposed to be stable if the result of a flash calculation for a mixture with
composition corresponding to this phase is a single-phase state.
The following criteria of nonequilibrium state are used [45]:

1. For 1-st method:

When varying system parameters (pressure and mixture composition) at least one phase
is stable then a process is nonequilibrium and ωi coefficients should be calculated. In
this case a mass transfer between phases occurs through interphase border. In other cases
the process is supposed to be equilibrium and ωi = 0;

2. For 2-nd method:

In addition to the previous criterion mass transfer of component is analysed. If compo-
nent mass transfer occurs from a stable phase into an unstable one then such process is
assumed to be nonequilibrium and ωi coefficients are calculated. If the component mass
transfer occurs from an unstable phase to a stable one then the process is equilibrium
and ωi = 0.

The keyword NEFLASH (see 12.1.7) allows to specify method 1 or 2 for simulation of
nonequilibrium thermodynamics. The value of α for calculation of coefficients ωi in the
formula (3.36) is set using the keyword NEFLASH (see 12.1.7) as well.

3.13.2. DKDT method for simulation of nonequilibrium

In tNavigator DKDT method can be used for simulation of nonequilibrium thermodynamics
in compositional models. This method is based on the limitation of variation of K-values Ki .
DKDT method is the third method specified by the keyword NEFLASH (see 12.1.7).
Let’s consider a two-phase mixture consisting of N components and assume that in a two-
phase state each component is in both phases. In compositional models solubility of gas in a

3.13.2. DKDT method for simulation of nonequilibrium 207

 19.1

liquid phase leads to decrease of a vapor phase fraction FV . The Rachford–Rice equation [41]
describes dependence of the vapor phase fraction FV on K-values Ki and composition zi :
N
(Ki − 1)zi
h(FV ) = ∑ = 0. (3.37)
i=1 1 + (Ki − 1)FV
The effect of nonequilibrium state can be noticed via variation of coefficients Ki . Moreover,
coefficients Ki depend on pressure. This approach allows to control the rate of reduction of the
vapor phase fraction in the nonequilibrium state due to a limitation of variation of K-values.
Negative flash method
In case if the considered system is in a steady single-phase state, the K-values are not
defined. The physically acceptable solution of system of equations describing vapor-liquid
equilibrium is in the range FV ∈ [0, 1] corresponding to a two-phase state. Generally, a solution
of the system exists in a wider range. In [46] the negative flash is suggested, which allows to
correctly extrapolate K-values to the single-phase region.
The function h(FV ) monotonically decreases with FV and has asymptotes at values
1
of FV = 1−K . Mole fractions of components xi,P are non negative in the range FV ∈
i 

1 1
1−Kmax , 1−Kmin [46]. Here Kmax and Kmin are maximum and minimum K-values, re-
spectively. In the negative flash calculation the system
 of equations
 describing vapor-liquid
1 1
equilibrium is solved in the extended range FV ∈ 1−Kmax , 1−Kmin .

DKDT method details

Method DKDT for simulation of nonequilibrium effects includes the following steps:
1. Calculation of equilibrium K-values Ki∗ using the negative flash. The negative flash
allows to obtain correct K-values Ki∗ not only for a two-phase state, but in a wider
region (of pressure and temperature) for single-phase state. The correctness of K-values
means that component mole fractions calculated based on these values are non negative.
2. The problem of relaxation of Ki to its equilibrium value is considered:
∂ Ki
= −α(Ki − Ki∗ )
∂t
Discretizing the differential equation the limitation on Ki can be obtained. The pa-
rameter α limits the increase of K-values and is specified by the keyword NEFLASH
(see 12.1.7) for the 3-rd method.
The state is considered to be equilibrium if for all K-values the below condition is
satisfied:
|Kin+1 − Kin | ≤ α|Ki∗ − Kin |∆t.
If for any K-value this condition is not satisfied then this state is assumed to be nonequi-
librium and values Kin+1 are adjusted as follows:

Kin+1 = Kin + α(Ki∗ − Kin )∆t.

3.13.2. DKDT method for simulation of nonequilibrium 208

 19.1

When α = 0 a two-phase state is always considered as nonequilibrium and K-values do

not change. When α is large enough the nonequilibrium condition is not always satisfied
and any two-phase state will be considered as equilibrium. Any nonequilibrium process
can become equilibrium one during a long time period. This can happen when α > 0.

3. Calculation of a gas fraction FV in the system oil-gas using the Rachford-Rice equation
(3.37) with new K-values Kin+1 .

3.13.2. DKDT method for simulation of nonequilibrium 209

 19.1

4. Compositional thermal model with chemical reactions

In this section compositional thermal model with chemical reactions is described. Furthermore,
models in E3 can be compositional (see section 3. Compositional model) or thermal (see
section 12.15. Thermal properties). The thermal simulation is activated by keyword THERMAL
(see 12.1.54).
Let’s 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)— doesn’t 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 cer-
tain 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 — dissolution
oil ⇒ gas — oil evaporation
oil ⇒ coke — carbonization
oil, gas ⇒ gas, water — burning
coke, gas ⇒ gas, water — burning
The solid phase is specified in E3 data format using the keyword SOLID (see 12.1.61) and in
ST data format by the keyword MODEL (see 13.5.4).
Component volatility type is specified in E3 using CVTYPE (see 12.15.5) (note also
its counterpart for surface conditions CVTYPES, see 12.15.6) and in ST using 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

4. Compositional thermal model with chemical reactions 210

 19.1

• 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.

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)

 
SP = 1 − SS SP , P = W, O, G
b b

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);

4.2. Saturations 211

 19.1

• 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.

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 (wa-
ter, 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,PξPSP = 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.14.1) in E3 data format.
Total number of components and the number of components in water, oil and gas phases are

4.4. Components 212

 19.1

set using the keyword MODEL (see 13.5.4) in ST 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 },

hence (SS = SbS ):

nP
∑ xc,PξPSP = 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.15.5) (MODEL, see 13.5.4) specifies that c-component
can’t 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

For models in E3 format the mass density and the molar water density on default (or if the
keyword THANALB (see 12.15.10) is present) are calculated

A0 + A1 T + A2 T 2 + A3 T 3 + A4 T 4 + A5 T 5 cw,p (p−A7 ) 1
ρW = e , ξW = · ρW , (4.5)
1 + A6 T MWW
where
A0 = 999.83952 A1 = 16.955176
A2 = −7.987 × 10−3 A3 = −46.170461 × 10−6
A4 = 105.56302 × 10−9 A5 = −280.54353 × 10−12
A6 = 16.87985 × 10−3 A7 = 102
If the keyword WATDENT (see 12.15.9) is enabled, then
ρw,re f
ρW = ,
(1 − cw,p (p − pw,re f ))(1 + cw,1,T (T − Tw,re f ) + cw,2,T (T − Tw,re f )2 )
1 (4.6)
ξW = · ρW
MWW
where

• ρw,re f = ρW,SC /BW (pre f ) (kg/m3 )

4.5. Mass and molar water density 213

 19.1

• ρW,SC – is set via DENSITY (see 12.5.33)

• cw,p , pw,re f , BW (pre f ) – are set via PVTW (see 12.5.5), cw,p can be calculated using
WATERTAB (see 12.14.12) data
• cw,1,T , cw,2,T , Tw,re f – are set via WATDENT (see 12.15.9)
• MWW – water molar weight
For models in ST format the mass density and the molar water density are calculated as
follows: 
ξW = ρw,re f exp cw,p (p − pre f ) − cw,1,T (T − Tre f )−
T 2 − Tre2 f 
(4.7)
−cw,2,T + cw,pT (p − pre f )(T − Tre f ) ,
2
ρW = ξW · MWW
where
• pre f – reference pressure PRSR (see 13.5.25)
• Tre f – reference temperature TEMR (see 13.5.26)
• ρw,re f – component density w from MOLDEN (see 13.5.29) (mol/m3 )
• ck,p , ck,1,T , ck,2,T , ck,pT – the properties of component w specified via CP
(see 13.5.31), CT1 (see 13.5.32), CT2 (see 13.5.33), CPT (see 13.5.34).
If for the component w CP (see 13.5.31) = 0,CT1 (see 13.5.32) = 0,CT2 (see 13.5.33) =
0,CPT (see 13.5.34) = 0 and MOLDEN (see 13.5.29) = 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.88888 kg-mol/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 × 10−5 − 1.076823 × 10−8 (pre f − 1.01325) 1/bar ,
– cw,1,T = −1.9095 × 10−3 1/K ,
– cw,2,T = 7.296 × 10−6 1/K 2 .

4.5. Mass and molar water density 214

 19.1

4.6. Mass and molar liquid density

The molar density and mass liquid density are calculated as
, !
MWk
ξO = 1 ∑ xk,O ρk,O , ρO = ξO∑ xk,OMWk (in E3);
, k ! k
(4.10)
1
ξO = 1 ∑ xk,O ρk,O , ρO = ξO∑ xk,OMWk (in ST).
k k

In E3 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.11)
where

1. pk,re f – reference pressure for component k (PREF (see 12.15.35) for reservoir condi-
tions, PREFS (see 12.15.37) for surface conditions),

2. Tk,re f – reference temperature for component k (TREF (see 12.15.38) for reservoir
conditions, TREFS (see 12.15.40) for surface conditions),

3. ρk,re f – density of component k at reference pressure and reference temperature (DREF

(see 12.15.41) for reservoir conditions, DREFS (see 12.15.43) for surface conditions),

4. ck,p – component k compressibility (CREF, see 12.15.45),

5. ck,T – thermal expansion coefficient for component k (THERMEX1, see 12.15.32).

Alternatively, gas-like compressibility may be specified for some components in the liq-
uid state. This approach might be preferable for trapped gases when modeling foamy oil. In
this case the component’s volume is calculated as V = ZRT /P, with Z defined by ZFAC-
TOR (see 12.15.50). The type of compressibility used for components is specified by the
keyword CCTYPE (see 12.15.7); note also its counterpart for surface conditions CCTYPES
(see 12.15.8).
In ST data format component liquid density ρk,O (p, T ) (kg-mol/m3 ) is calculated as

ρk,O = ρk,re f · exp ck,p (p − pre f ) − ck,1,T (T − Tre f )−
T 2 − Tre2 f 
− ck,2,T + ck,pT (p − pre f )(T − Tre f ) (4.12)
2
where

1. pre f – reference pressure (PRSR, see 13.5.25)

2. Tre f – reference temperature (TEMR, see 13.5.26)

4.6. Mass and molar liquid density 215

 19.1

3. ρk,re f – density of component k at reference pressure and reference temperature

(MOLDEN, see 13.5.29)
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.15.32),
• ck,2,T (CT2) – the second thermal expansion coefficient for component k (for this
parameter tNavigator uses the keyword THERMEX2, see 12.15.33); 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.15.34)
Oil phase density using an EoS
To calculate the specific molar volume for the oil phase an equation of state (EoS) can be
used. The keyword CODTYPE (see 12.15.3) defines the components for the mixture that can
be used in the EoS calculation.
Let’s define moles of component c per mole of phase Oil (O), where c = 1, ..., n0c , specified
by the keyword CODTYPE (see 12.15.3) as xc,O E and not specified by this keyword as xno .
c,O
If component including in subset of components defined by CODTYPE (see 12.15.3) is used
E
for calculation of EoS then xc,O no is set to be zero if
is equal to xc,O and 0 otherwise. xc,O
component is used in calculation of EoS and be equal to xc,O otherwise.
Then the oil specific molar volume is calculated:
n0c
no
VO = ∑ xc,OVc,O + XE VEoS (p, T, x1,O
emix
, ..., xnemix
0 ,O )
c
c=1
where
n0c E
xc,O
E E emix
X = ∑ xc,O xc,O =
c=1 XE
If type EMIX is specified in the keyword CODTYPE (see 12.15.3) then the lowest root
(Liquid root) of the cubic equation of state is selected. In case a mixture cannot exist as an oil
under the given pressure and composition, the obtained volume could be unphysical.
Notice that if smaller subset of the components are selected from available components
for the EoS, all heavy components should be included in this subset.

4.7. Molar and mass gas density

In E3 data format the molar and the gas mass density are calculated as
,  !
MWw Zk,0 RT
ξG = 1 xw,G + ∑ xk,G − Zk,1
ρw k p (4.13)
ρG = ξG ∑ xk,G MWk
k

4.7. Molar and mass gas density 216

 19.1

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 is the boiling temperature ( ◦ C), TbK = Tb + 273.15 is 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 · 10−6 C4 = −6.93747 · 10−9 C5 = 2.97203 · 10−12

The coefficients Zk,0 , Zk,1 are specified using the keywords ZFACTOR (see 12.15.50),
ZFACT1 (see 12.15.51).
Zk,0 default value is 0.96.
J m3 · bar
Gas constant R in (4.13) is equal to 8.3143 = 0.083143 , i.e. R =
K · mol K · kg-mol
0.083143 for the unit of pressure bar , and the unit amount of fluid kg-mol .
In ST 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. Let’s specify i = 1, . . . , n0c
pri pri pT
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.36), the critical pressure pci is
set using PCRIT (see 13.5.35). 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].
Gas phase density using an EoS To calculate the specific molar volume for the gas
phase an equation of state (EoS) can be used. The keyword CGDTYPE (see 12.15.1) defines
the components for the mixture that can be used in the EoS calculation. Gas (G), where
c = 1, ..., n0c , specified by the keyword CGDTYPE (see 12.15.1) as xc,G
E and not specified by

4.7. Molar and mass gas density 217

 19.1

this keyword as xc,Gno . If component including in subset of components defined by CGDTYPE

E is equal to x
(see 12.15.1) is used for calculation of EoS then xc,G no
c,G and 0 otherwise. xc,G
is set to be zero if component is used in calculation of EoS and be equal to xc,G otherwise.
Then the gas specific molar volume is calculated:
n0c
no
VG = ∑ xc,GVc,G + XE VEoS (p, T, x1,G
emix
, ..., xnemix
0 ,G ) + xw,GVw,G
c
c=1

where
n0c E
xc,G
E E emix
X = ∑ xc,G xc,G =
c=1 XE
If type EMIX is specified in the keyword CGDTYPE (see 12.15.1) then the highest root (Vapor
root) of the cubic equation of state is selected. In case a mixture cannot exist as a gas under
the given pressure and composition, the obtained volume could be unphysical.
Notice that if smaller subset of the components are selected from available components
for the EoS, all light components should be included in this subset.

4.8. Molar solid density

Molar solid density (coke) is calculated as
, !
nc
1
ξS = 1 ∑0 xk,S ρk (4.19)
k=n +1c

In E3 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.14.30) (CMM,

see 13.5.74)

2. pk,re f – reference pressure for component k (SPREF, see 12.15.29)

3. Tk,re f – reference temperature for component k (STREF, see 12.15.31)

4. ρk,re f – density of component k at reference pressure and reference temperature

(SDREF, see 12.15.28)

5. ck,p – component k compressibility (SCREF, see 12.15.30)

6. ck,T – thermal expansion coefficient for component k (is specified using the keyword
STHERMX1, see 12.15.26)

4.8. Molar solid density 218

 19.1

In ST 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

1. pre f – reference pressure (PRSR, see 13.5.25)

2. Tre f – reference temperature (TEMR, see 13.5.26)

3. ρk,re f – density of component k at reference pressure and reference temperature

(SOLID_DEN, see 13.5.37)

4. ck,p , ck,T , ck,pT – properties of component k in the solid phase (SOLID_DEN,

see 13.5.37):

• ck,p – component k compressibility,

• ck,T – thermal expansion coefficient for component k (for this parameter tNavi-
gator uses the keyword STHERMX1, see 12.15.26),
• ck,pT – the coefficient of density dependence on temperature and pressure (for this
parameter tNavigator uses the keyword STHERMX2, see 12.15.27)

Mass solid density isn’t used in the calculations.

4.9. Thermodynamic equilibrium condition

MP - the number of moles in the "mobile" phase P, P = W, O, G, in the unit volume. Obvi-
ously
n0P n0c
∑ MP = Ntot = ∑ Nc.
P=1 c=1
MP
Let RP = — the part of "mobile" component mixture in the phase P, concerning the total
Ntot
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

4.9. Thermodynamic equilibrium condition 219

 19.1

Since water component isn’t 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 partition coefficients 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
Thermal equilibrium conditions are the following:
n0P n0c n0c
∑ RP = 1, ∑ xc,O = 1(RO > 0), ∑ xc,G = 1(RG > 0).
P=1 c=2 c=1

The values Ki = Ki (p, T ) can be specified via the tables KVTEMP (see 12.15.13),
KVTABTn (see 12.15.14), KVTABLIM (see 12.15.15) in E3 (KVTABLIM (see 13.5.39),
KVTABLE (see 13.5.40) in ST), or via the correlation formula:
Ki (p, T ) = (Ai + Bi /p +Ci p) · e−Di /(T −Ei ) (4.22)
where the coefficients Ai , Bi , Ci , Di , Ei are set using the keywords KVCR (see 12.15.11) in
E3 (KV1 / KV2 / KV3 / KV4 / KV5 (see 13.5.41) in ST).
In ST 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.23)
p psi a
In E3 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.24)
p a
It is very difficult to choose many parameters in (4.22) (Ki (p, T ) should be positive and
increasing in conjunction with T ). In E3 data format the correlation (Wilson) for hydrocarbon
components can be used – KVWI (see 12.15.16):
pci 5.372697·(1+Ai )·(1−Tci /T )
Ki (p, T ) = ·e (4.25)
p
where

4.9. Thermodynamic equilibrium condition 220

 19.1

• Tci – component critical temperature TCRIT (see 12.14.20);

• pci – component critical pressure PCRIT (see 12.14.22);

• Ai – component acentric factor ACF (see 12.14.38).

4.10. Phase saturations

Following (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.26)
ξP
The description of calculations of the solid phase saturation is in the section (4.4).

4.11. Water viscosity

Water viscosity can be specified as a function of temperature using the tables – WATVISCT
(see 12.15.53) (E3 data format), VISCTABLE (see 13.5.68) (ST data format), or via correla-
tions. In E3 the following correlation is used (Grabovski):

µW (T ) = 1 AW + BW TC +CW TC2 , AW = 0.1323, BW = 0.03333, CW = 7.643 · 10−6



(4.27)
◦
where TC is the temperature ( C). In ST the following correlation is used:
 
µW (T ) = AW exp BW /T (4.28)

where T is the temperature (K), the coefficients AW , BW are set via the keywords AVISC
(see 13.5.66), BVISC (see 13.5.67).

Multiple viscosity regions can be specified via VSTYPE (see 13.5.60), VISCTYPE
(see 13.5.61) (ST). tNavigator also uses the keyword (VISCNUM, see 12.4.19).

In E3 data format the viscosity dependence on pressure can be specified:

µW0 (p)
µW (p, T ) = µW (T ) 0 (p ) (4.29)
µW re f

where

• µW (T ) – water viscosity (depends on temperature) is calculated above;

• µW
0 (p) – water viscosity as a function of pressure (specified using PVTW, see 12.5.5);

• pre f – reference pressure (specified using VISCREF, see 12.15.52).

4.10. Phase saturations 221

 19.1

4.12. Oil viscosity

Oil viscosity is calculated using the formula

µO (T ) = ∏(µk,O ) fk (xk,O ) (4.30)

k

where oil component viscosity µk,O (T ) can be specified as a function of temperature us-
ing the tables of this keyword OILVISCT (see 12.15.54) (in E3 data format), VISCTABLE
(see 13.5.68) (ST), or using correlation (OILVISCC, see 12.15.55). Component viscosities for
the oil phase can be compute using Lorentz-Bray-Clark correlation (COVTYPE, see 12.15.4).
fk (x) (default: fk (x) = x ) are specified using OILVINDX (see 12.15.56) (in E3 data format)
or VSMIXCOMP (see 13.5.69), VSMIXENDP (see 13.5.70), VSMIXFUNC (see 13.5.71) (ST).
tNavigator also uses the keyword OILVINDT (see 12.15.57).
In E3 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 ST 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.66), BVISC (see 13.5.67).

Multiple viscosity regions can be specified via VSTYPE (see 13.5.60), VISCTYPE
(see 13.5.61) (ST). tNavigator also uses the keyword (VISCNUM, see 12.4.19).

In E3 data format pressure dependence can be set:

µO0 (p)
µO (p, T ) = µO (T ) (4.31)
µ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);

• pre f – reference pressure (specified using VISCREF, see 12.15.52).

4.13. Gas viscosity

In E3 data format gas viscosity is calculated

µG (p, T ) = ∑ xk,G µk,G (4.32)

k

4.12. Oil viscosity 222

 19.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 · 10−3 , Bg = 5.0956 · 10−5 , Cg = 2.9223 · 10−6 , 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.15.58), or using the
correlation formula with the coefficients GASVISCF (see 12.15.59):

µk,G (T ) = Ak · T Bk (4.33)

Moreover, the gas phase viscosities can be computed by the Lorentz-Bray-Clark (LBC) corre-
lation using the keyword CGVTYPE (see 12.15.2).
In ST data format gas viscosity is calculated as
n0c
!, 0 !
p nc p
µG (T ) = ∑ µk,G · xk,G MWk ∑ xk,G MWk (4.34)
k=1 k=1

where MWk – molecular weight of the component k (specified using CMM, see 13.5.74),
component viscosities are set via correlation (4.33) with the coefficients AVG (see 13.5.72),
BVG (see 13.5.73). If gas viscosity isn’t specified by user then in ST data format it is calculated
as
µG (T ) = 0.0136 + 3.8 · 10−5 · TC , TC = T − 273.15
Multiple viscosity regions can be specified via VSTYPE (see 13.5.60), VISCTYPE
(see 13.5.61) (ST). tNavigator also uses the keyword (VISCNUM, see 12.4.19).

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.35)

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 isn’t 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 E3 data format: CPc,P (kJ/kg/◦ C). In ST data format: CPc,P (J/mol/◦ C).

4.14. Enthalpy and heat capacity of the components 223

 19.1

4.15. Enthalpy and internal energy of the phases

Enthalpy of the phase HP (T ) (for one mole, kJ/mol ):
nc
HP (p, T ) = ∑ xc,P (p, T ) · Hc,P · MWc (in E3)
c=1 (4.36)
nc
HP (p, T ) = ∑ xc,P (p, T ) · Hc,P (in ST)
c=1

where MWc – molecular weight given by the keyword MW (see 12.14.30) (kg/mol ). In E3
data format the gas phase component enthalpies include both a temperature dependent term
and a pressure dependent term (Joule-Thomson) (see 4.46, 4.47).
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.37)
P=1

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.38)

4.16. Water enthalpy

In E3 data format the enthalpy, the water vaporization enthalpy are taken from the internal
tables (see [20]). These enthalpies are the functions of pressure and temperature. In ST data
format the enthalpy, the water vaporization enthalpy are also taken from the internal tables.
In [21] there is a following formula for water enthalpy:

h f = hc 1 + (1 − Tr ) A + BTr +CTr2 + DTr3 + ETr4 + F(1 − Tr )α ,

(4.39)

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.15. Enthalpy and internal energy of the phases 224

 19.1

4.17. Liquid enthalpy

In E3 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.40)
2
where the coefficients CP1,c (kJ/kg/◦ C), CP2,c are specified using the keywords SPECHA
(see 12.15.73), SPECHB (see 12.15.74) (default: 0), Tre f is specified using STCOND
(see 12.14.11).
In ST data format the component liquid enthalpy is calculated as
4
1
Hc,O (T ) = ∑ CPi,c (T − Tre f )i (4.41)
i=1 i!

where the coefficients CPi,c , i = 1, . . . , 4 are specified using the keywords CPL1 / CPL2 /
CPL3 / CPL4 (see 13.5.42).
tNavigator also uses the keywords CP3,c = SPECHC (see 12.15.75), CP4,c = SPECHD
(see 12.15.76).
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 specified using TEMR (see 13.5.26).
Then the liquid phase enthalpy is calculated according to (4.36).

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.42)

where:
For models in E3 format Ac is specified using the keyword HEATVAP (see 12.15.20) (default:
0 kJ/kg).
For models in ST format A0c is specified using the keyword HVR (see 13.5.45) (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.15.21) (E3), EV
(see 13.5.46) (ST).
Critical temperature of the component Tc,crit is specified using the keyword TCRIT
(see 12.14.20) (E3), TCRIT (see 13.5.36) (ST).
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.35).
If the component enthalpy in the gas phase and vaporization enthalpy is specified then the
oil phase enthalpy is calculated from the equation (4.35).

4.17. Liquid enthalpy 225

 19.1

4.19. Gas phase enthalpy

In E3 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.43)

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.44)
2
where the coefficients hc,G (kJ/kg), CP1,c (kJ/kg/◦ C), CP2,c (kJ/kg/◦C2 ), are speci-
fied using the keywords HEATVAPS (see 12.15.81), SPECHG (see 12.15.77), SPECHH
(see 12.15.78) (default: 0), Tre f is specified using STCOND (see 12.14.11).
In ST data format the component gas phase enthalpy is calculated as
4
1
Hc,G (T ) = hc,G + ∑ CPi,c (T − Tre f )i (4.45)
i=1 i!

where the coefficients hc,G , CPi,c , i = 1, . . . , 4 are specified using the keywords HVAPR
(see 13.5.44), CPG1 / CPG2 / CPG3 / CPG4 (see 13.5.43).
tNavigator also uses the keywords CP3,c = SPECHI (see 12.15.79), CP4,c = SPECHJ
(see 12.15.80). Default values: hc,G = 0.25Btu/lb/F = 0.25∗1.05506/0.453592∗1.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.26).

Then the gas phase enthalpy is calculated according to (4.36).

If the vaporization enthalpy isn’t specified, then during E3 data format instead of (4.36) is
used:
nc

HG (p, T ) = ∑ xc,G (p, T ) · Hc,G (T ) · MWc + HJT,c (p) (4.46)
c=1
where (Joule-Thomson)
HJT,c (p) = −102 · Zc,1 · (p − pre f ) (4.47)
The coefficient Zc,1 is set via ZFACT1 (see 12.15.51), pre f – STCOND (see 12.14.11). Mul-
tiplier 102 (4.47) results from units transformation: Zc,1 – m3 /kg-mol , so Zc,1 · (p − pre f ) –
m3 /kg-mol · bar = 105 · m3 · Pa/kg-mol = 102 · kJ/kg-mol .

4.19. Gas phase enthalpy 226

 19.1

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 (E3) or
2 (4.48)
1
Hc,S (T ) = CP1,c (T − Tre f ) + CP2,c (T − Tre f )2 (ST)
2
where
• in E3 data format the coefficients CP1,c (kJ/kg/◦ C), CP2,c are specified using the
keywords SPECHS (see 12.15.82), SPECHT (see 12.15.83) (default: 0), Tre f is specified
using the keyword STCOND (see 12.14.11).

• in ST data format the coefficients CP1,c , CP2,c are specified using the keywords
SOLID_CP (see 13.5.38) (default: CP1,c = 17kJ/mol/C , CP2,c = 0), Tre f is specified
using the keyword TEMR (see 13.5.26).
Then the solid phase enthalpy is calculated according to (4.36).

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.49)
2
where
• CP1 is the rock volumetric heat capacity (does not depend on temperature) (MET-
RIC: kJ/m3 /K , FIELD: Btu/ f t 3 /F ). For models in E3 it is specified by HEATCR
(see 12.15.17) (default: 0). For models in ST it is specified by ROCKCP (see 13.4.3)
(default: 2347kJ/m3 );

• CP2 is the temperature (T ) dependence of the rock volumetric heat capacity for each
grid block (METRIC: kJ/m3 /K 2 , FIELD: Btu/ f t 3 /F 2 ). For models in E3 it is specified
by HEATCRT (see 12.15.18) (default: 0). For models in ST it is specified by ROCKCP
(see 13.4.3) (default: 0);

• Tre f is the reference temperature specified by STCOND (see 12.14.11) for models in E3
format and by TEMR (see 13.5.26) for models in ST format.
In tNavigator the coefficients CP1 , CP2 can be specified via the keyword HEATTCR
(see 12.15.19).
Internal rock energy (for unit volume, kJ/m3 ):

UR (T ) = HR (T ) (4.50)

4.20. Solid phase enthalpy 227

 19.1

4.22. Default enthalpy values for ST format models

For ST format models there are 3 types of enthalpy specification:

1) Oil enthalpy (CPL1 / CPL2 / CPL3 / CPL4, see 13.5.42) and vaporization enthalpy
(HVR (see 13.5.45), EV, see 13.5.46) are entered.

2) Gas enthalpy (CPG1 / CPG2 / CPG3 / CPG4, see 13.5.43) and vaporization enthalpy
(HVR (see 13.5.45), EV, see 13.5.46) are entered.

3) Oil enthalpy (CPL1 / CPL2 / CPL3 / CPL4, see 13.5.42), gas enthalpy (CPG1 /
CPG2 / CPG3 / CPG4, see 13.5.43) and the value of vaporization enthalpy at the
point Tre f (HVAPR, see 13.5.44) 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.42) = 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 vapor-
ization 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 vapor-
ization 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.42) = 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.37),
solid phase (4.38) and rock (4.50), (in the unit volume) are multiplied by the volume (see 4.1
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.51)

4.24. Porosity
In E3 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.52)

where

4.22. Default enthalpy values for ST format models 228

 19.1

• ψ(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.17) (default: in E1 = 0, in E3 = 4.934·10−5 /Bar );

• pref – reference pressure for ϕ(x, y, z) (ROCK, see 12.5.17) (default 1.0132Bar ).
In ST data format the porosity ϕ = ϕ(p, T, x, y, z) is calculated in one of the two ways
depending on the PORFORM (see 13.4.22) parameter:
Value of PORFORM (see 13.4.22) Porosity


LINEAR ϕ(p, T, x, y, z) = ϕre f (x, y, z) · 1 + c(p,t)


EXP ϕ(p, T, x, y, z) = ϕre f (x, y, z) · exp c(p,t)
Here ϕre f (x, y, z) is the porosity at the reference pressure pre f (POR, see 13.3.10) and
c(p,t) is a dimensionless parameter calculated according to one of the following models:

1. Linear Elastic Model

 
c(p,t) = min pormax, c p (p − pre f ) − cT (T − Tre f ) (4.53)

where

• 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), ROCKT (see 12.15.24); 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.26).
• pormax – maximal fractional increase in porosity due to pressure (PORMAX,
see 13.4.21). The value pormax should be in the range from 0 to 1. If the keyword
PORMAX (see 13.4.21) is not defined, then the value of pormax is considered as
infinite.

2. Nonlinear Elastic Model

 
c(p,t) = min pormax, c p (p − pre f ) + cporpd − cT (T − Tre f ) (4.54)

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)

4.24. Porosity 229

 19.1

– 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.20)
• c p , cT , pref , Tre f , pormax - are defined analogously to Linear Elastic model.
3. P-T Cross-Term Model
 
c(p,t) = min pormax, c p (p − pre f ) + c pT (p − pre f )(T − Tre f ) − cT (T − Tre f ) (4.55)
where
• c pT – pressure-temperature cross-term coefficient of the formation effective poros-
ity (1/Bar/◦C) (CPTPOR (see 13.4.7), ROCKT (see 12.15.24); default – 0);
• 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.23).

The dependence between porosity and pressure is calculated via the formula
c(p,t) = c p (p − pre f ) (4.56)
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. 19), consists of 4 phases:
• I. Elastic: reversible elastic expansion with a reference pressure pbase (DILATION
(see 13.4.23), parameter PBASE, by default is equal to the value of PRPOR,
see 13.4.4), reference porosity ϕbase (POR, see 13.3.10) and with the pore vol-
ume compressibility value cpepac (1/Bar ) (DILATION (see 13.4.23), parameter
CPEPAC, by default is equal to the value of CPOR, see 13.4.5).
• II. Dilation: when the pressure exceeds the value pdila (DILATION (see 13.4.23),
parameter PDILA, by default 0). Rock compressibility coefficient at dilation crd
(1/Bar ) is set using DILATION (see 13.4.23), parameter CRD (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 de-
fined using reference porosity and the coefficient PORRATMAX from DILATION
(see 13.4.23), (by default 1) that sets the coefficient of maximal porosity increasing
over reference porosity.

4.24. Porosity 230

 19.1

Figure 19. Dilation-Recompaction Model

• III. Elastic Compaction: with the initial pore volume compressibility value cpepac,
no recovery after dilation. In this case tNavigator takes maximum values that were
reached in dilation as ϕre f and pre f .
• IV. Recompaction: when the pressure falls below the value p pact (DILATION
(see 13.4.23), parameter PPACT, 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 com-
pression, is defined using the parameter f r (DILATION (see 13.4.23), parameter
FR, 0 ≤ f r ≤ 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.57)
After the calculation of ϕmin it is possible to calculate compressibility factor cpact

4.24. Porosity 231

 19.1

via the formula (4.56):

1 ϕmin
ϕmin = ϕ(p pact ) exp (−cpact · p pact ) ⇒ cpact = − · ln (4.58)
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. Fur-
ther 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 pro-
cess 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.

Figure 20. Dilation-Recompaction. Porosity variation during 3 cycles

Temperature effect can be taken into account for Dilation-Recompaction model. the
formula (4.56) is corrected the following way


c(p,t) = c p (p − pre f ) − cT T − Tre f (4.59)

4.24. Porosity 232

 19.1

where cT – effective thermal expansion coefficient of the formation (1/◦C), set by

CTPOR (see 13.4.6) for elastic curves (I) and (III), parameter CTD from DILATION
(see 13.4.23), for dilation curve (II) and parameter CTPPAC 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 compressibil-
ity.

4.25. Pore volume of grid block

In E3 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)

• Else
Vp,re f (x, y, z) = γ(x, y, z)ψ(x, y, z)ϕ(x, y, z)Vgeom (4.60)
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.61)

see 4.24.
In ST data format pore volume Vp,re f at reference pressure pref and temperature Tre f
(see 4.24) is calculated via formula (4.60), where multiplier γ(x, y, z) (default: 1) is set via
VOLMOD (see 13.3.14). 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.62)

see 4.24.

4.26. Bulk volume of grid block

In E3 data format bulk volume of grid block Vb :
• If ROCKV (see 12.15.88) is specified, then Vb = Vp,re f + ROCKV (see 12.15.88).

• Else Vb = max{Vgeom ,Vp,re f }.

In ST 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.14).

4.27. Bulk volume of rock

Bulk volume of rock VR :
VR = max{Vb −Vp , 0}.

4.25. Pore volume of grid block 233

 19.1

4.28. Thermal conductivity of the grid block

For models in E3 format thermal conductivity of the grid block is

Kb = Λ · T HCaver (4.63)

where
• T HCaver – is the average of the phase and rock conductivities (kJ/m/day/◦ C). This
value depends on rock and phases properties, therefore, it does not change during com-
putation. T HCaver is used to calculate thermal transmissibilities;

• Λ – is the thermal conductivity multiplier varying as a function of saturation in compu-

tation.
Thermal transmissibilities in X, Y and Z directions can be directly specified by keywords
HEATTX (see 12.2.92), HEATTY (see 12.2.93) and HEATTZ (see 12.2.94), respectively.
If the keyword THCONR (see 12.15.22) is used in the model then T HCaver is equal to
conductivity specified by the keyword THCONR (see 12.15.22). The thermal conductivity
multiplier Λ depending on saturation is calculated as:

Λ = 1 − αSG

where
• α – is set via THCONSF (see 12.15.23), α ∈ [0, 1] (default: 0);

• SG – is the gas upstream saturation (i.e., taken in the block from which thermal energy
flow outcomes).
If the keyword THCROCK (see 12.2.91) is specified in a model then T HCaver is calculated
as a porosity weighted average of the phase and rock conductivities using the formula:
T HCO + T HCG + T HCW + T HCS
T HCaverage = ϕ + (1 − ϕ)T HCR
NP
where:

• ϕ – porosity of the grid block;

• NP – the number of phases P in the model;

• T HCG – gas phase thermal conductivity, specified via THCGAS (see 12.2.87);

• T HCO – oil phase thermal conductivity, specified via THCOIL (see 12.2.88);

• T HCW – water phase thermal conductivity, specified via THCWATER (see 12.2.89);

• T HCS – solid phase thermal conductivity, specified via THCSOLID (see 12.2.90);

4.28. Thermal conductivity of the grid block 234

 19.1

• T HCR – rock thermal conductivity, specified via THCROCK (see 12.2.91).

If some phases do not exist in the model, then the correspondent phase thermal conductivity
will be ignored. The thermal conductivity multiplier Λ is a function of all phases saturation
and calculated as:

Λ = (ϕ(∑ SP T HCP ) + (1 − ϕ)T HCR )/T HCaverage

P

where SP are upstream saturations for phases P = O, G,W, S .

In ST data format thermal conductivity of the grid block can be specified via the key-
word THCONMIX (see 13.4.13). The correlations described below are also avaliable for usage
in E3 format and can be specified via the keyword THCONMIX (see 12.15.25).

There are four methods of conductivity calculations that can be defined by THCONMIX
(see 13.4.13) or THCONMIX (see 12.15.25):

1. SIMPLE – volume-weighted mixing rule for thermal conductivity:

 
Kb = ϕ 1 − SbS · (kW SW + kO SO + kG SG ) + ϕ · kS · SbS + (1 − ϕ) · kR (4.64)

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.

2. LOG – volume-weighted mixing rule written in logarithmic form:

 
ln(Kb ) = ϕ 1 − SbS · (ln(kW ) · SW + ln(kO ) · SO + ln(kG ) · SG )+
(4.65)
+ϕ · ln(kS ) · SbS + (1 − ϕ) · ln(kR )

3. COMPLEX – mixing rule that takes special actions for small values of block’s porosity:
   
  kR kR
Kb0
p p
= 1 − SW + SO · kG · F + SW + SO · kL · F (4.66)
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

4.28. Thermal conductivity of the grid block 235

 19.1

• ϕ f – "mobile" porosity.

4. TEMPER – mixing rule that applies additional temperature correction: The dependence
between the block thermal conductivity and the temperature

Kb = Kb0 − 1.7524 · 10−5 (T 0

 − Tre f ) · (Kb − 119616)×
(4.67)

0

−0.64 0 −3

(−3.6784·10−6 Kb0 )
× Kb · Kb · 1.8 · 10 · T + 110644.8

where Tre f is given by the keyword TEMR (see 13.5.26).

4.29. Chemical reactions

Let’s consider nr chemical reactions. The number of chemical reactions nr can be defined by
keyword REACTION (see 12.1.55). 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.15.67) in E3; STOREAC (see 13.5.47) in ST;

• SPr = (SPri )i=1,...,nc – stoichiometric coefficients for products of the reaction number
r , are specified using STOPROD (see 12.15.66) in E3; STOPROD (see 13.5.48) in ST;

• Ar – reaction rate constant of the reaction number r , are specified using REACRATE
(see 12.15.60) in E3; FREQFAC (see 13.5.49) in ST;

• Er – activation energy in chemical reaction rates of the reaction number r , are

specified using REACACT (see 12.15.61) in E3; EACT (see 13.5.51) in ST;

• Hr – reaction enthalpy of the reaction number r , are specified using REACENTH

(see 12.15.70) in E3; RENTH (see 13.5.53) in ST;

• Nr = (nri )i=1,...,nc – order of component in chemical reaction r (for non-reactants can

be > 0 for catalyst, < 0 for inhibitor), are specified using REACCORD (see 12.15.62),
REACSORD (see 12.15.69) in E3; RORDER (see 13.5.54) in ST.

For example, for nc = 5, components C12 H26 , C3 H8 , O2 , CO2 , H2 O and nr = 2 reactions:

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

4.29. Chemical reactions 236

 19.1

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
−Er /(RT 0 )
Rr = Vb · Ar · e · ∏(c0ri )nri (4.68)
i=1

m3 · bar
where R = 0.083143 , component concentration (since 4.4):
K · kg-mol
 
1 − SS · ξO · SO xiO if the reactant i is in the oil phase

 b



 

1 − SbS · ξG · SG xiG if the reactant i is in the gas phase




 
cri = − (4.69)
1 SS · ξW · SW xiW if the reactant i is in the water phase
 b



b



SS · ξS · xiS = Ni if the reactant i is in the solid phase


Ni if the reactant i is in all phases


ϕ · cri



 if it isn’t gas and not REACPHA (see 12.15.68) with GPP

0
cri = (there is no O2PP, see 13.5.59) (4.70)



 p0 · x

i,G else (for gas)

where temperature, pressure and order are:

 
 
 T if T > Tu  p if p > pu 
 u  u
 
if c0ri > Cri
  n
0 0 0 ri
T = Tl if T < Tl p = pl if p < pl nri = (4.71)
1 else

 
 

 

T else  p else

where

• Tu is specified using RTEMUPR (see 13.5.56) (REACLIMS (see 12.15.63) in E3 data

format),

• Tl – RTEMLOWR (see 13.5.57) (REACLIMS (see 12.15.63) in E3 data format),

• Cri – RXCRITCON (see 13.5.58) (there is no analogue in E3 (n0ri = nri ); tNavigator uses
the keyword Cri = REACCONC, see 12.15.64),

4.29. Chemical reactions 237

 19.1

• pu , pl is specified using REACLIMS (see 12.15.63) (there is no analogue in ST ( p0 =

p)).

O2PP (see 13.5.59) 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.15.68) in E3, RPHASE (see 13.5.55) in ST. In E3 data format
the "mobile" component can be specified in all phases, then cri = ϕ · Ni . This is a default
value. In ST data format the default value is calculated using the data of the keyword MODEL
(see 13.5.4).

As the reaction nears equilibrium, its rate might need a correction specified by the key-
word EQLDREAC (see 12.15.71). The equilibrium parameters used in this correction are spec-
ified via the keyword EQLDKVCR (see 12.15.72) in E3 format or via keywords RXEQFOR
(see 13.4.14) and RXEQBAK (see 13.4.15) in ST format.
The reaction rate (4.68) can depend on pore volume Vp = ϕ ·Vb :
0
Rr = Vp · ϕ nr,p · Ar · e−Er /(RT ) · ∏ (cri )nri · ∏ (p0 · xi,G )nri (4.72)
i∈Fr i6∈Fr

where nr,p = ∑ nri − 1, indices Fr :

i∈Fr

Fr = i ∈ {1, . . . , nc : if i is not a gas and there is no REACPHA (see 12.15.68) with GPP
(no O2PP, see 13.5.59) }

In E3 data format another value nr,p can be specified for each reaction using REACPORD
(see 12.15.65). 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.73)
r=1

The additional energy flow, appears via the chemical reactions:

nr
QRe = ∑ Hr Rr . (4.74)
r=1

4.30. The heat loss between the reservoir and surroundings

In E3 and ST 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 238
 19.1

• The connection between the reservoir and cap and base rocks. In E3 data format
the complicated form of connection can be specified via the keyword ROCKCON
(see 12.2.85), in ST – 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.19). tNavigator also uses the keyword ROCKCONT
(see 12.2.86), 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 E3 is set via
ROCKDIMS (see 12.1.38), in ST – is specified at the same time with the description of
the geometry.

• Volumetric heat capacity (kJ/m3 /C ) – ROCKPROP (see 12.2.84) (E3), HLOSSPROP

(see 13.4.19) (ST), ROCKCONT (see 12.2.86).

• Rock conductivity (kJ/m/day/C ) – ROCKPROP (see 12.2.84) (E3), HLOSSPROP

(see 13.4.19) (ST), ROCKCONT (see 12.2.86).

• Initial temperature (C ) – ROCKPROP (see 12.2.84) (E3), HLOSST (see 13.4.17) (ST),
ROCKCONT (see 12.2.86).

• Temperature-dependent coefficient of the volumetric heat capacity of the rock

(kJ/m3 /C2 ) – ROCKPROP (see 12.2.84) in E3 (is not defined in ST).

• Minimal difference between temperatures when the calculations of the heat loss should
start (C ) – HLOSSTDIFF (see 13.4.18) in ST, ROCKCONT (see 12.2.86) (default 0) (is
missing in E3).

• Gas phase thermal conductivity using the keyword THCGAS (see 12.2.87).

• Oil phase thermal conductivity using the keyword THCOIL (see 12.2.88).

• Water phase thermal conductivity using the keyword THCWATER (see 12.2.89).

• Solid phase thermal conductivity using the keyword THCSOLID (see 12.2.90).

• Rock thermal conductivity using the keyword THCROCK (see 12.2.91).

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 isn’t
situated on the the reservoir boundary).

4.31. Heater simulation

Let’s consider 3 heater models:

I constant energy injection rate;

4.31. Heater simulation 239

 19.1

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 maximum number of heater connections is defined by keyword HEATDIMS
(see 12.1.42).
The following parameters should be specified via the keywords:
1. heater name (for E3 format models);
2. I,J,K-coordinates of the heater connection;
3. maximum heat injection rate, Hmax ;
in E3 data format Hmax has units METRIC: kJ/day, FIELD: Btu/day;
units in ST 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 between
heat rate and the difference between current block temperature and maximum tempera-
ture), R;
in E3 format R has units METRIC: kJ/day/K , FIELD: Btu/day/R◦ ;
units in ST 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 ST format
parameter 1 shouldn’t be specified). In E3 format parameters 1-3 are specified via the keyword
HEATER (see 12.19.181) (or HEATERL (see 12.19.182) in a local grid refinement (LGR)). In
ST format parameters 2-3 are specified via the keyword HEATR (see 13.9.46).
For this heater model the heat will be injected at a constant rate to the grid block:
H = Hmax . (4.75)

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 ST
format parameter 1 shouldn’t be specified). In E3 format parameters 1-5 are specified via the
keyword HEATER (see 12.19.181) (or HEATERL (see 12.19.182) in a local grid refinement
(LGR)). In ST format parameters 2-3 are specified via the keyword HEATR (see 13.9.46),
parameter 4 – via the keyword TMPSET (see 13.9.45), parameter 5 – UHTR (see 13.9.47).
In E3 for this heater model the heat rate to the grid block is:
H = min((Tmax − T )R, Hmax ), (4.76)

4.31.1. Heater with constant energy injection rate 240

 19.1

where T – current temperature in the grid block. In ST the heat rate to the grid block (for the
linear model) depends on R sign:

min((T − T )R, 0), R > 0,
max
H= (4.77)
min((T − Tmax )|R|, 0), R < 0.


4.31.3. Selecting of the heater operating mode depending on the defined properties E3

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 E3, 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:
!
i−1
Etot (Tmax ) − Etot
H = min V , Hmax , (4.78)
dt

where V - block volume, Etot (Tmax ) - density of the full energy in the block at maximum
i−1
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 ST

In ST for the block to which the heater is connected, one could specify an option of automatic
switching of heater operation mode (R > 0):

min((T − T )R, H ), T < T ,
max max max
H= (4.79)
0, T ≥ Tmax .


The same way the operation mode of cooling element can be switched automatically
(R < 0):

min((T − T )R, H ), T > T ,
max max max
H= (4.80)
0, T ≤ Tmax .


4.31.3. Selecting of the heater operating mode depending on the defined properties E3 241
 19.1

4.32. Phase flow rate

 k 
rP
up = −βc k (∇p + ∇PcP − ρP g∇d) (4.81)
µ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.33. Mass conservation equation

Mass conservation equation (moles) for each component:
nP 0
∂  
ϕ(1 − SbS )Nc = div ∑ xc,P ξPUP + Qc + QRc , c = 1, . . . , n0c (4.82)
∂t P=1
∂
(ϕNc ) = QRc , c = n0c + 1, . . . , nc (4.83)
∂t
where
• UP = UP (p, N) – velocity vector (4.81) of phase flow P, P = 1, . . . , n0P ;

• Qc = ∑nβw=1 δβ qc — total rate of all sources and flows; δβ – Dirac δ function localized
β

β
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.73);

• SbS – solid phase saturation (4.4);

• n0P , n0c – see 4.4.

Sources and flows — injectors and producers and aquifers.

4.34. Energy conservation equation

Energy conservation equation:
∂
(Ub ) = Fe +Ce + QRe + Qwell
e − QL (4.84)
∂t
where
• internal block energy (kJ ) Ub specified via (4.51);

4.32. Phase flow rate 242

 19.1

• convection enthalpy flow from (in) neighbouring surrounding points

n0P
Fe = div ∑ HPξPUP
P=1

where phase enthalpy HP specified via (4.36), UP = UP (p, N) – velocity vector (4.81)
of phase flow;

• energy flow due to conductivity

Ce = div(Kb ∇T ),

where Kb — block thermal conductivity (kJ/m/day/◦ C), see 4.28;

• energy flow due to chemical reactions QRe see 4.74;

• energy flow from the well

n0P
Qwell
e = ∑ HP · ξP · QP, (4.85)
P=1

where QP – rate of phase P for connection in the grid block, phase enthalpy HP
specified via 4.36;

• QL — energy flow due to heat loss with surrounding, see 4.30.

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
= ∑ HPξPUP 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 13.8.2). In case if the primary variables are p, Nc and Etot – system fluid enthalpy (pa-
rameter ZH in the keyword TFORM, see 13.8.2).

In this case the form of mass conservation equation doesn’t change (4.82) but the energy
conservation equation will be the following:
n0P
! Z
! Z
∂
∂t
Vb Etot = − ∑ HPξPUP ds + Kb∇T ds + QRe + Qwell e − QL .
P=1
∂Vb ∂Vb

4.34. Energy conservation equation 243

 19.1

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 water-oil and
gas-oil (see the table 3).

2. Relative permeabilities (and capillary pressure) scaling for two-phase systems

(see 4.35.2, see the table 5).

3. Oil relative permeability krO is calculated using the first or the second Stone’s model.

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.26),
SWCR (see 12.6.29), ..., KRW (see 12.6.59), etc).

• Specification of critical saturations as depth function (keywords ENPTVD (see 12.6.37),

ENKRVD, see 12.6.38).

• Specification of critical saturations as a function of temperature (keywords ENPTVT

(see 12.15.85), ENKRVT, see 12.15.86) – only for thermo-compositional model.

• Specification of critical saturations as a function of tracer (salt, surfactant) concentration

(tNavigator-only keywords ENPTRC (see 12.6.40), ENPTRCM, see 12.6.43).

• Specification of critical saturations as composition function (keywords ENKRVC

(see 12.14.55), ENPCVC (see 12.14.56) and ENPTVC, see 12.14.57).

4.35.1. Phase relative permeability for two-phase systems

Specification of phase relative permeabilities is in the table 3.

Table 3. Phase relative permeabilities

Value E3 data format CMG data format Value description

krW (SW ), SWOF (see 12.6.1) SWT (see 13.6.5) relative permeability for
krOW (SW ) two-phase system water-oil
krG (SG ), krOG (SG ) SGOF (see 12.6.2) SLT (see 13.6.6) relative permeability for
two-phase system gas-oil
PcOW (SW ) SWOF (see 12.6.1) SWT (see 13.6.5) capillary pressure
two-phase system water-oil
PcOG (SG ) SGOF (see 12.6.2) SLT (see 13.6.6) capillary pressure
two-phase system gas-oil

4.35. Phase relative permeabilities 244

 19.1

Phase relative permeabilities can be specified for different saturation regions (Saturation
regions are specified via SATNUM (see 12.4.3) (E3), KRTYPE (see 13.6.12) (CMG)). I -
saturation region number for current block i. From the table 3 we take functions for I and
enter for them constants from the table 4. We suppose that at initialization stage the following
condition is checked
max krOW = max krOG
SW SG

Table 4. Phase relative permeability constants

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 = 1 − SW − 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 )

4.35.2. Phase relative permeabilities scaling

Each constant in the table 4 can be changed,

• via phase permeabilities scaling;

• these constants can be specified as temperature dependent constants;

see the table 5.

Phase relative permeability scaling is switched on using the keyword ENDSCALE
(see 12.1.136) (E3 data format run).

4.35.2. Phase relative permeabilities scaling 245

 19.1

In CMG data format initial conditions can be specified as constants in saturation regions
(for example – SWR (see 13.6.14) etc.) and as constants in each grid block (for example –
BSWR (see 13.6.15) etc.), in E3 data format – constant should be specified for each grid
block. tNavigator supports all keyword from the table 5.

Table 5. Phase relative permeability scaling

Value Number E3 (replace "Number") CMG (replace "Number")

0
SW L SW L •SWL (see 12.6.26) •BSWR (see 13.6.15)
•ENPTVT (see 12.15.85), parameter 2 •SWR (see 13.6.14)
•KRTEMTAB (see 13.6.13)
0
SWCR SWCR •SWCR (see 12.6.29) •BSWCRIT (see 13.6.17)
•ENPTVT (see 12.15.85), parameter 3 •SWCRIT (see 13.6.16)
•KRTEMTAB (see 13.6.13)
0
SWU SWU •SWU (see 12.6.33) •1 − BSOIRW (see 13.6.19)
•ENPTVT (see 12.15.85), parameter 4 •1 − SOIRW (see 13.6.18)
•1 − KRTEMTAB (see 13.6.13)
0
SGL SGL •SGL (see 12.6.28) •BSGCON (see 13.6.21)
•ENPTVT (see 12.15.85), parameter 5 •SGCON (see 13.6.20)
•KRTEMTAB (see 13.6.13)
0
SGCR SGCR •SGCR (see 12.6.30) •BSGR (see 13.6.23)
•ENPTVT (see 12.15.85), parameter 6 •SGR (see 13.6.22)
•KRTEMTAB (see 13.6.13)
0
SGU SGU •SGU (see 12.6.34) •1 − BSOIRG (see 13.6.25)
•ENPTVT (see 12.15.85), parameter 7 •1 − SOIRG (see 13.6.24)
•1 − KRTEMTAB (see 13.6.13)
0
SOWCR SOWCR •SOWCR (see 12.6.31) •BSORW (see 13.6.27)
•ENPTVT (see 12.15.85), parameter 8 •SORW (see 13.6.26)
•KRTEMTAB (see 13.6.13)
0
SOGCR SOGCR •SOGCR (see 12.6.32) •BSORG (see 13.6.29)
•ENPTVT (see 12.15.85), parameter 9 •SORG (see 13.6.28)
•KRTEMTAB (see 13.6.13)
0
krW max krW max •KRW (see 12.6.59) •BKRWIRO (see 13.6.31)
•ENKRVT (see 12.15.86), parameter 2 •KRWIRO (see 13.6.30)
•KRTEMTAB (see 13.6.13)
0
krGmax krGmax •KRG (see 12.6.60) •BKRGCW (see 13.6.33)
•ENKRVT (see 12.15.86), parameter 3 •KRGCW (see 13.6.32)
•KRTEMTAB (see 13.6.13)
0
krOmax krOmax •KRO (see 12.6.58) •KROGCG (see 13.6.4)
•ENKRVT (see 12.15.86), parameter 4 •BKROCW (see 13.6.35)
•KROCW (see 13.6.34)
•KRTEMTAB (see 13.6.13)
0
krW R krW R •KRWR (see 12.6.59) —
•ENKRVT (see 12.15.86), parameter 5

4.35.2. Phase relative permeabilities scaling 246

 19.1

Value Number E3 (replace "Number") CMG (replace "Number")

0
krGR krGR •KRGR (see 12.6.60) —
•ENKRVT (see 12.15.86), parameter 6
0
krORG krORG •KRORG (see 12.6.58) —
•ENKRVT (see 12.15.86), parameter 7
0
krORW krORW •KRORW (see 12.6.58) —
•ENKRVT (see 12.15.86), parameter 8
0
PCGmax PCGmax •PCG (see 12.6.63) •BPCGMAX (see 13.6.37)
•ENPCVT (see 12.15.87), parameter 2 •PCGEND (see 13.6.36)
•KRTEMTAB (see 13.6.13)
0
PCW max PCW max •PCW (see 12.6.62) •BPCWMAX (see 13.6.39)
•ENPCVT (see 12.15.87), parameter 3 •PCWEND (see 13.6.38)
•KRTEMTAB (see 13.6.13)

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 0
+ SGCR 0
+ SW
4. SOGCR 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
1 − SOGCR 0
− SW L

For the given SW , T :



SW 0
SWCR 0 (T )
(T ) > SWU





0

SWCR
 SW < SWCR (T )
0
SW (SW , T ) = (4.86)
0 (T )




SWU SW > SWU
SWU − SWCR



 0
SWCR + (SW − SWCR (T )) else
0 (T ) − S0
SWU WCR (T )
0
0 krW max (T ) 0
krW (SW , T ) = krW (SW (SW , T )) (4.87)
krW max

4.35.2. Phase relative permeabilities scaling 247

 19.1

If there is an oil phase in the model, the following parameters are calculated

0 (T ) > 1 − S0 0
SW , SW OWCR (T ) − SGL (T )



 L

0 (T )

S , SW < SW

 WL


 L
0
SOW (SW , T ) = 1 − SOWCR − SGL , 0
SW > 1 − SOWCR 0 (T )
(T ) − SGL (4.88)



 SW L + (SW − SW 0 (T ))×

 L

 1 − S OWCR − SGL − SW L
 × 0 (T ) − S0 (T ) , else


0
1 − SOWCR (T ) − SGL WL
k 0 (T )
0 0
krOW (SW , T ) = rOmax krOW (SOW (SW , T )) (4.89)
krOmax



SW , 0 (T ) > S0 (T )
SW

 L WU



0 (T )

SW L ,
 SW < SW L
0
ScOW (SW , T ) = (4.90)
0 (T )




SWU , SW > SWU
SWU − SW L


0 (T ))
SW L + (SW − SW 0 (T ) , else


L 0
SWU (T ) − SW L
0
0 PCW max (T ) 0
PcOW (SW , T ) = PcOW (ScOW (SW , T )) (4.91)
PCW max
If there is gas phase in the model, for the given SG , T :


 SG , 0
SGCR 0 (T )
(T ) > SGU





0

SGCR ,
 SG < SGCR (T )
0
SG (SG , T ) = (4.92)
0 (T )




 SGU , SG > SGU
SGU − SGCR


SGCR + (SG − SGCR

 0 (T )) 0 , else
0
SGU (T ) − SGCR (T )
0
krGmax (T )
0 0
krG (SG , T ) = krG (SG (SG , T )) (4.93)
krGmax

4.35.2. Phase relative permeabilities scaling 248

 19.1

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 )

S , SG < SGL

 GL



0
SOG (SG , T ) = 1 − SOGCR − SW L , 0
SG > 1 − SOGCR 0 (T )
(T ) − SW (4.94)
 L



 0
SGL + (SG − SGL (T ))×


 1 − SOGCR − SW L − SGL
 × 0 (T ) − S0 (T ) , else


0
1 − SOGCR (T ) − SW L GL
k 0 (T )
0 0
krOG (SG , T ) = rOmax krOG (SOG (SG , T )) (4.95)
krOmax



SG , 0 (T ) > S0 (T )
SGL

 GU



0 (T )

SGL ,
 SG < SGL
0
ScOG (SG , T ) = (4.96)
0 (T )




SGU , SG > SGU
SGU − SGL


0 (T ))
SGL + (SG − SGL 0 (T ) , else


0
SGU (T ) − SGL
0
PCGmax (T )
0 0
PcOG (SG , T ) = PcOG (ScOG (SG , T )) (4.97)
PCGmax
Phase relative permeabilities three-point scaling is enabled in E3 data format (see the
keyword SCALECRS, see 12.6.25). This method keeps permeability values in three 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
1 − SOGCR 0
− SW 0
SGU
L
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:


1 − S0 0
0 OWCR (T ) − SGL (T ) if oil phase is enabled
SW r (T ) =
 0
1 − SGCR (T ) else

1 − S
OWCR − SGL if oil phase is enabled
SW r =
1 − SGCR else


4.35.2. Phase relative permeabilities scaling 249

 19.1

0 (T ) is not in the interval [S0 0 0 0

If calculated value SW r WCR (T ), SWU (T )] or SWCR (T ) > SWU (T ),
then SW0 (S , T ) is calculated via formula (4.86), else:
W


 SWCR , SW < SWCR 0 (T )







 SWCR + (SW − SWCR 0 (T ))×



 SW r − SWCR 0 0 (T )
 × 0 , SWCR (T ) 6 SW < SW


0
SW r (T ) − SWCR (T ) r
0
SW (SW , T ) = (4.98)



 0
SW r + (SW − SW r (T ))×



 SWU − SW r 0 (T ) 6 S < S0 (T )
 × 0 0 (T ) , SW

W

r WU


 SWU (T ) − S Wr



SWU , SW > SWU 0 (T )

0 (S0 (T ), T ) = S
Note that SW Wr Wr .
If the keyword KRWR (see 12.6.59) is not specified or krW (SW r ) > krW max , then
0 (S , T ) is calculated via formula (4.87), else:
krW W
 0
krW R (T ) 0 0 (T )

 krW (SW (SW , T )), SW < SW r
k (S )

 rW W r


0 0
0
krW (SW , T ) = k0 (T ) + krW max (T ) − krW R (T ) × (4.99)
rW R


 k rW max − krW (SW r )



×(krW (SW 0 (S , T )) − k (S )) 0 (T )
, SW > SW
W rW W r 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 (T ), 1 − S0 0
If calculated value SOW r (T ) is not in the interval [SW L OWCR (T ) − SGL (T )] or
SW0 (T ) > 1 − S0 (T ) − 0 (T ), then
SGL 0 (S , T ) is calculated via formula (4.88), else
SOW
L OWCR W
0
SOW (SW , T ) =


SW L 0 (T )
SW < SW L







 0 (T )) SOW r − SW L 0 (T ) 6 S < S0
SW L + (SW − SW SW OW r (T )

W


 L 0 0 (T )
SOW r (T ) − SW L

 L
= 0

SOW r + (SW − SOW r (T ))×


 1 − SOWCR − SGL − SOW r 0 0 0
× SOW r (T ) 6 SW < 1 − SOWCR (T ) − SGL (T )


0
1 − SOWCR (T ) − SGL 0 (T ) − S0
OW r (T )







1 − S

−S 0
SW > 1 − SOWCR 0 (T )
(T ) − SGL
OWCR GL
(4.100)

4.35.2. Phase relative permeabilities scaling 250

 19.1

0 (S0
Note that SOW OW r (T ), T ) = SOW r .
If the keyword KRORW (see 12.6.58) is not specified or krOW (SOW r ) > krOmax , then
0
krOW (SW , T ) is calculated via formula (4.89), else
 0
krOmax 0
(T ) − krORW (T )

 k 0 (T ) + ×
rORW
krOmax − krOW (SOW r )




0
krOW (SW , T ) = 0 (S , T )) − k
×(krOW (SOW W
0
rOW (SOW r )) SW < SOW r (T )
(4.101)

k0 (T )


 rORW
 0 0
 krOW (SOW (SW , T )) SW > SOW r (T )
krOW (SOW r )
0 0
(SOW 0
Note that krOW r (T ), T ) = krORW (T ).
If gas phase is present then for the given SG , T the following parameters are calculated:

1 − S0 0
0 OGCR (T ) − SW L (T ) if oil phase is present
SGr (T ) =
 0
1 − SWCR (T ) else

1 − S
OGCR − SW L if oil phase is present
SGr =
1 − SWCR else


0 (T ) is not in the interval [S0 0 0 0

If the calculated value SGr GCR (T ), SGU (T )] or SGCR (T ) > SGU (T ),
0
then SG (SG , T ) is calculated via formula (4.92), else



 SGCR , 0
SG < SGCR (T )





SGCR + (SG − SGCR

 0 (T ))×



 SGr − SGCR 0 0 (T )
 × 0 , SGCR (T ) 6 SG < SGr


0
SGr (T ) − SGCR (T )
0
SG (SG , T ) = (4.102)



 SGr + (SG − SGr0 (T ))×



 SGU − SGr 0 (T ) 6 S < S0 (T )
× 0 0 (T ) , SGr

G

GU
(T ) −



 S GU S Gr



S , 0 (T )
SG > SGU
GU

Note that SG 0 (S0 (T ), T ) = S .

Gr Gr
0 (S , T )
If the keyword KRGR (see 12.6.60) is not specified or krG (SGr ) > krGmax , then krG G
is calculated via formula (4.93), else
 0
krGR (T ) 0 0 (T )

 krG (SG (SG , T )), SG < SGr
k (S )

 rG Gr


0 0
0
krG (SG , T ) = k0 (T ) + krGmax (T ) − krGR (T ) × (4.103)
rGR


 krGmax − k (S
rG Gr )



×(krG (SG 0 (S , T )) − k (S )), S > S0 (T )
G rG Gr G Gr

4.35.2. Phase relative permeabilities scaling 251

 19.1

0 (S0 (T ), T ) = k0
Note that krG Gr rGR (T ).
0 (S , T ), k0
If oil phase is present then SOG 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 0 0 0
SGL (T ) > 1 − SOGCR (T ) − SW L (T ), then SOG (SG , T ) is calculated via formula (4.94), else

0
SOG (SG , T ) =



 SGL 0 (T )
SG < SGL






 0 (T )) SOGr − SGL 0 (T ) 6 S < S0
SGL + (SG − SGL SGL OGr (T )

G



 0 0 (T )
SOGr (T ) − SGL

= 0

 SOGr + (SG − SOGr (T ))×


 1 − S OGCR − SW L − SOGr 0 0 0 (T )
× SOGr (T ) 6 SG < 1 − SOGCR (T ) − SW


0
1 − SOGCR 0 (T ) − S0
(T ) − SW L
OGr (T )




 L


1 − S

−S 0
SG > 1 − SOGCR 0 (T )
(T ) − SW
OGCR WL L
(4.104)
0 (S0
Note that SOG OGr (T ), T ) = SOGr .
If the keyword KRORG (see 12.6.58) is not specified or krOG (SOGr ) > krOmax , then
0
krOG (SG , T ) is calculated via formula (4.95), else
 0
krOmax 0
(T ) − krORG (T )

k 0 (T ) + ×
rORG
krOmax − krOG (SOGr )




0
krOG (SG , T ) = 0 (S , T )) − k
×(krOG (SOG G
0
rOG (SOGr )) SG < SOGr (T )
(4.105)

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 three-phase systems

If oil phase is present in the model, then oil relative permeability krO should be calculated.
Let’s consider models from the table 6.

4.35.3. Phase relative permeabilities for three-phase systems 252

 19.1

Table 6. Phase relative permeabilities for three-phase systems

Name E1/E3 data format IM/GE data format ST data format

Linear model (see default KROIL (see 13.6.3) is not available
[22]) (SEGREGATED)
Stone I model (stan- STONE1 (see 12.6.20) is not available is not available
dard)
Stone I model (modi- is not available KROIL (see 13.6.3) RPT (see 13.6.2)
fied) (see [23]) (STONE1) (STONE1)
Stone II model (modi- STONE2 (see 12.6.21) default, KROIL default, RPT
fied) (see 13.6.3) (see 13.6.2)
(STONE2) (STONE2)
Linear Isoperm model LINEAR_ISOPERM KROIL (see 13.6.3) RPT (see 13.6.2)
(see 12.6.90) (LINEAR_ISOPERM) (LININTERP)

Linear Baker’s model

Let (ε – small parameter):


 0
krOG (SG + SW − SW 0 (T ), T ) 0 (T ) < ε
SW − SW

 L L





0
krOW (SG + SW , T ) SG < ε



0
krO (SW , SG , T ) = 0 0 (T ), T ) (4.106)
 SG · krOG (SG + SW − SW L


0 (T )) +
S + (S − S

G W


 W L
0 (T )) · k0

(SW − SW rOW (SG + SW , T )


L
 + else


SG + (SW − SW 0 (T ))
L

First Stone’s model

Let’s consider SOm (SG , T ):

• for standard first Stone’s model:

0 0
SOm (T ) = min(SOWCR (T ), SOGCR (T ))

• for modified first Stone’s 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 )

4.35.3. Phase relative permeabilities for three-phase systems 253

 19.1

Let
0 0
SW (SW , T ) = max(SW , SW L (T )).
∗ (S , S , T ), S∗ (S , S , T ), S∗ (S , T ) the following values:
Let’s denote as SO W G W W G G G
 0 (S , T ) − S − S (S , T )
1 − SW W G Om G 0 (S , T ) − S > S (S , T )


0 if 1 − SW W G Om G
∗
SO (SW , SG , T ) = 1 − SW L (T ) − SOm (SG , T )

0 else

0 (S , T ) − S0 (T )
SW
∗ W WL
SW (SW , SG , T ) = 0 (T ) − S (S , T )
1 − SW L Om G
∗ SG
SG (SG , T ) = 0
1 − SW L (T ) − SOm (SG , T )

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 , S , T ))(1 − S∗ (S , T )) (4.107)
(1 − SW W G G 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 ).
Second Stone’s model
Let’s consider the following functions:
 0
krGmax (T )

 0 if KRG (see 12.6.60) and KRW (see 12.6.59) are specified
k (T )



 rW max
 krW max


if only KRW (see 12.6.59) is specified

0
α(T ) = krW max (T ) (4.108)
 0
krGmax (T )


 if only KRG (see 12.6.60) is specified



 krW max

else

1
 0
krW max (T )

 0 if KRG (see 12.6.60) and KRW (see 12.6.59) are specified
krGmax (T )



0

 krW max (T )

if only KRW (see 12.6.59) is specified


β (T ) = krGmax (4.109)
k
 rGmax

if only KRG (see 12.6.60) is specified



 0
krGmax (T )




1 else

4.35.3. Phase relative permeabilities for three-phase systems 254

 19.1

Then
 0
krOW (SW , T )

0 0 0 0
krO (SW , SG , T ) = krOW (SW L (T ), T ) 0 0 (T ), T ) + α(T )krW (SW , T )
krOW (SW L
 0
krOG (SG , T )
 
0 0 0
· 0 0 + β (T )krG (SG , T ) − (α(T )krW (SW , T ) + β (T )krG (SG , T )) (4.110)
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 ).
Linear Isoperm model
In this model the oil relative permeability krO (SG , SW ) is defined using curves (isoperms)
along which krO is assumed to be a constant value in the following region:

(1 − SOrG − SW c )
SW cr < SW < 1 − SOrW , 0 < SG < (1 − SOrW − SW )
(1 − SOrW − SW c )
where SW c is the connate water saturation, SOrW is the residual oil to water saturation.
Moreover, isoperms are assumed to be straight lines. Let’s:

krO (SG = 0, SW ) = krOW (SW )

krO (SG , SW = SW l ) = krOG (SG )

∗ )=k
If krOW (SW ∗ ∗ ∗
rOG (SG ) for some values SW , SG , then

∗ ∗
krO (SG , SW ) = krOW (SW ) = krOG (SG )
∗ , 0), (S , S∗ )].
for any point (SG , SW ) in the region [(SW Wl G

Segregated model
In this model the a segregated assumption for the gas and water is used. Gas and water
are constant in a block. Water in the gas zone is assumed to be equal to the connate water
saturation SW c . Then the oil relative permeability krO is calculated as

SG krOG + (SW − SW c )krOW

krO =
SG + SW − SW c
where krOG is the oil relative permeability for a system with oil, gas and connate water, krOW
is the oil relative permeability for a system with oil and water only.

4.35.3. Phase relative permeabilities for three-phase systems 255

 19.1

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
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



 xc,L = Kc (p, T ) ωc,G > 0, ωc,L > 0, where L ∈ {O,W }

 0
 nc
∑ xc,P = 1 P = O,W, G (4.111)

 c=1 !


 nc
ϕe f f (1 − SbS ) Ntot ∑ RP HP − 102 p + ϕe f f ∑ , Nc Hc,S +



c=nc


 P=O,W,G


+(1 − ϕe f f )HR = Etot ,


0
nc
where ϕe f f = Vp /Vb – effective porosity, Ntot = ∑ Nc .
c=1
Note, then the number of equations and the number of variables in (4.111) are equal (and
0 00 00
equal to 4 + nc + nc , here nc – the number of components, for which ωc,G > 0, ωc,L > 0,
where as in 4.111 L ∈ {O,W }).

4.37. Initial conditions

For the equations 4.82, 4.84 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.36. Calculation of the phase composition 256

 19.1

4.37.1. Explicit specification of initial conditions

In this case the following parameters are always specified explicitly:

• pressure p – via PRESSURE (see 12.16.12) (PRES, see 13.7.23);

• temperature T – via TEMPI (see 12.16.32) (TEMP, see 13.7.24).

For solid phase always

• in E3 data format one should specify explicitly solid phase saturation SbS and com-
ponent distribution xc,S (see 4.4) via SSOLID (see 12.16.17) and SMF (see 12.16.20);
then molar density of solid phase is calculated (4.19) and molar densities Nc , c =
n0c + 1, . . . , nc ;

• in ST 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.25).

Phase and component composition of ’mobile’ phases and components can be specified
several ways.

• tNavigator (this option is missing in ST and E3 data formats) allows to specify ex-
n0c
plicitly values zc = Nc /Ntot , c = 1, . . . , n0c , Ntot = ∑ Nc via ZMF (see 12.16.23). So
c=1
initialization algorithm is the following:

– calculation of Ki = Ki (p, T ) using pressure and temperature from 4.22, 4.24, 4.25
– 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 E3 data format (this option is missing in ST) value of z0c = Nc /Ntot

0 , c = 2, . . . , n0 ,
c
n0c
0
Ntot = ∑ Nc is specified explicitly via ZMF (see 12.16.23), water saturation SW is set
c=2
via SWAT (see 12.16.14). Free gas is not defined: SG = 0, SO = 1 − SW , two keywords
SOIL (see 12.16.16) and SGAS (see 12.16.15) 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 ;

4.37.1. Explicit specification of initial conditions 257

 19.1

– 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.16.14)

(SW, see 13.7.19), SOIL (see 12.16.16) (SO, see 13.7.17), SGAS (see 12.16.15) (SG,
see 13.7.18). Concentration matrix xc,P c = 1, . . . , n0c , P = O, G (for P = W ) – using
XMF (see 12.16.21) (MFRAC_OIL, see 13.7.26), YMF (see 12.16.22) (MFRAC_GAS,
see 13.7.27). 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.

N SW SO SG E3 format ST 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

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 .

In E3 and ST data formats initial conditions are specified in each grid block.

• Pressure – PRESSURE (see 12.16.12), PRES (see 13.7.23).

• Temperature – TEMPI (see 12.16.32), TEMP (see 13.7.24).

• Solid phase – SSOLID (see 12.16.17), SMF (see 12.16.20), CONC_SLD (see 13.7.25).

• ’Mobile’ phases – ZMF (see 12.16.23), SWAT (see 12.16.14), SOIL (see 12.16.16),
SGAS (see 12.16.15), XMF (see 12.16.21), YMF (see 12.16.22), SW (see 13.7.19),
SO (see 13.7.17), SG (see 13.7.18), MFRAC_OIL (see 13.7.26), MFRAC_GAS
(see 13.7.27).

4.37.1. Explicit specification of initial conditions 258

 19.1

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 E3 data format depends on depth – TEMPVD (see 12.15.84);

• in ST data format – is specified implicitly via TEMP (see 13.7.24).

In black oil case the pressure p and saturation of ’mobile’ phases are calculated from
hydrostatic equilibrium conditions – EQUIL (see 12.16.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. ST supports only explicit specification of concentration ma-
trix xc,P c = 1, . . . , n0c , P = O, G in each block via MFRAC_OIL (see 13.7.26), MFRAC_GAS
(see 13.7.27), see 4.37.1.
In E3 data format there are several ways to specify component composition of mixture
versus depth.
n0c
• Distribution of values zc = Nc /Ntot , c = 1, . . . , n0c , Ntot = ∑ Nc versus depth is speci-
c=1
fied via either ZMFVD (see 12.14.17) or COMPVD (see 12.14.14), or ZI (see 12.14.13).
Then mass density is calculated via the following algorithm:

– values Ki = Ki (p, T ) are calculated from pressure and temperature at selected depth
(4.22, 4.24, 4.25);
– 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.16.23);
– 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.14.15), YMFVP (see 12.14.16).
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 ;

4.37.2. Calculations of initial conditions from hydrostatic and thermodynamic equilibrium conditions259
 19.1

– 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.16.21), YMF
(see 12.16.22);
– 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 conditions260
 19.1

5. Mathematical model
Simulator uses usual finite volume 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 in the section 5.4.

The keyword RUNCTRL (see 12.19.140) controls the solution algorithms and the parame-
ters of iteration process.

5.1. Space approximation

Simulator uses standard finite volume approximation with respect to space variables on block
centered mesh. The standard upstream approximation is used for computation 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.19.140) or specify the keyword AIM
(see 12.1.102).

Settings of AIM can be changed in the keyword AIMCTRL (see 12.1.5).

5. Mathematical model 261

 19.1

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 g∇D) + ∑ 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.19.140).
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.19.140).

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 elements
– 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 equa-
tions with modified incomplete LU factorization (MILU(0)) as preconditioner.

5.4. Transition from physical model to system of equations 262

 19.1

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.19.140).

The keyword RUNCTRL (see 12.19.140) controls the solution algorithms and the parame-
ters of iteration process.

5.5. Model geometry

tNavigator supports three types of grid cell geometry (see figure 21):

Block-centered Corner-point Via block corners

Figure 21. Grid types

• Block-centered geometry is intended for simple grids. More complex geological structures
like faults and pinchouts are better modeled by other grid types.

• Defined with 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).
• Grid blocks are rectangular with horizontal top and bottom faces and vertical side
faces.
Differences in DX, DY, DZ, and TOPS for neighboring blocks may
lead to a grid of complicated topology. In such cases the simulator
GUI resorts to displaying non-rectangular blocks which correctly
! reproduce the interblock connectivity, but not the block sizes (see
figure 22). Also, in the displayed properties of a block, its Z coordi-
nate may differ from its depth (the hydrodynamic calculations rely
on the latter).

5.5. Model geometry 263

 19.1

Defined in the model Displayed in GUI

Figure 22. Block-centered grid in complicated cases

• Transmissibilities are calculated by default using OLDTRAN (see 12.2.11) method.

• Corner-point geometry

• Defined with keywords COORD (see 12.2.8) and ZCORN (see 12.2.9).
• Blocks can have various shapes. Corners of all blocks in one column are located
on the same set of guide lines, which are not necessarily vertical and not neces-
sarily parallel to each other. The positions of block corners on the guide lines are
specified for each block independently and do not necessarily coincide with those
of the neighboring blocks.
• Transmissibilities are calculated by default using NEWTRAN (see 12.2.12) method.

• Grid specified via blocks corners

• Defined with keyword CORNERS (see 12.2.123).

• Blocks can have arbitrary shapes. All corners of each block are specified separately
and independently of each other.
• Transmissibilities are calculated by default using NEWTRAN (see 12.2.12) method.

Additional options.
Grid can be included to the model using the following keywords:

• IMPORT (see 12.2.109) – This keyword imports cubes into a model. Cubes should be
specified in binary format.

• VISGRID (see 12.2.110) – This 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.123). The example of Y-pillar grid
format is available in the description of the keyword CORNERS (see 12.2.123).

• GDFILE (see 12.2.49) – This keyword defines a model grid using the special format file
(*.GRID – E1/E3 format).

5.5. Model geometry 264

 19.1

5.5.1. Defining active/inactive blocks

Grid blocks can be active or inactive. Calculations run only in active blocks, while inactive
blocks are excluded from calculations. It is possible to identify grid blocks as active or inactive
using the following keywords:

• ACTNUM (see 12.2.29) – This keyword is used to identify active/inactive blocks.

• MINPV (see 12.2.30) – This keyword switches a grid block into inactive state if its pore
volume (METRIC: rm3 , FIELD: rb) is smaller than specified in this keyword.

• MINPVV (see 12.2.32) – This keyword switches a grid block into inactive state if its pore
volume (METRIC: rm3 , FIELD: rb) is smaller than value specified in this keyword and
associated with that block.

• MINDZNET (see 12.2.33) – This keyword switches a grid block into inactive state if its
net thickness (DZ, see 12.2.2) (METRIC: m, FIELD: f t ) is smaller than specified in
this keyword.

• MINPVR (see 12.2.34) – This keyword switches grid blocks into inactive state if their
pore volume is less than a specified fraction of an average pore volume.

5.5.2. Faults
To define complex geological structures – faults and their parameters the following keywords
can be used:

• FAULTS (see 12.2.38) – This keyword specifies parameters of fault (set of faults): name,
coordinates of segments, faces.

• MULTFLT (see 12.2.39) – This keyword specifies transmissibility multipliers for all
fault’s cells, in direction corresponding to face of fault.

• THPRESFT (see 12.2.40) – This keyword sets 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.

• THPRES (see 12.16.11) – This keyword sets threshold pressure value for flow between
equilibration regions. If pressure difference between cells of specified regions is less
than threshold value, there will be no flow between those cells.

• FAULTDIM (see 12.1.40) – This keyword specifies the maximum number of faults de-
fined by keyword FAULTS (see 12.2.38).

5.5.1. Defining active/inactive blocks 265

 19.1

5.5.3. Multireservoir option

If several reservoirs are defined in the model the following keywords can be used:
• COORDSYS (see 12.2.48) – This keyword specifies a coordinate system for each reser-
voir in the model.

• NUMRES (see 12.1.76) – This keyword sets a number of reservoirs in the model.

5.5.4. Coordinate transformation

To transform coordinate system the following keywords can be used:
• MAPAXES (see 12.2.67) – This keyword is used to transform grid coordinates to coor-
dinate system associated with the map.

• MAPUNITS (see 12.2.68) – This keyword is used to specify MAPAXES (see 12.2.67)
data units.

5.5.5. Connections between blocks

The figure 23 shows different types of blocks’ connections that may be presented in the model.
Transmissibility is calculated for connections as described in the section 5.5.6.
Connections are reported in the *.log file as follows:
Log entry
Mesh connections statistics: total= <number>, geometrical=
<number>, pinched= <number>, NNC= <number> (including matrix-
fracture= <number>), geometrical NNC= <number>, numerical
aquifer= <number>
Below the list of all non-neighboring connections is printed with their types (AQUIFER,
PINCHX etc).

Here the geometrical connections include:

• Normal connections between blocks whose numbers differ by one (the number of these
connections is not listed separately);

• Connections between blocks which are non-neighboring by number, but neighboring by

geometry, usually due to a fault (listed as "geometrical NNC").
Total connections count is the sum of:
• Geometrical connections;

• Pinched-out connections created by PINCH (see 12.2.58) and related keywords

(PINCH (see 12.2.58), PINCHXY (see 12.2.59), PINCHOUT (see 12.2.60), PINCHNUM
(see 12.2.62), PINCHREG (see 12.2.61) – create connections across pinched-out layers);

5.5.3. Multireservoir option 266

 19.1

Ordinary geometrical connections Geometrical NNC’s

PINCHXY

PINCH
Pinch-out connections Non-neighboring connection

Figure 23. Connection types

• Non-neighboring connections created by NNC (see 12.2.54) and related keywords (NNC
(see 12.2.54), EDITNNC (see 12.2.55), EDITNNCR (see 12.2.56), NNCGEN (see 12.2.57),
NONNC (see 12.1.53) – create, edit or disallow non-neighbor connections), including
matrix-fracture NNC’s for dual porosity models (listed separately);

• Connections to numeric aquifers created by AQUCON (see 12.17.14) and related key-
words.

Connections and translmissibilities for them are visualized in Graphical interface under
Grid properties → Interblock flows, see the section Interblock Flows in the tNavigator
User Guide.

5.5.6. Transmissibility calculation

Transmissibility can be specified via the keywords TRANX (see 12.2.50), TRANY
(see 12.2.51), TRANZ (see 12.2.52).

If these keywords are not specified, transmissibility will be calculated via the formula
below.

5.5.6. Transmissibility calculation 267

 19.1

1. If OLDTRAN (see 12.2.11) is active, transmissibility value is calculated as follows:

CDARCY · T MULT Xi · A · DIPC
T RANXi = ,
B
where:

• CDARCY – Darcy’s constant (METRIC: 0.00852702, FIELD: 0.00112712);

• T MULT Xi – transmissibility multiplier for ith 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
• DIPC = DHS
– dip correction.
DHS+DV S
DXi +DX j 2

– DHS = 2 ;
– DV S = (DEPT Hi − DEPT H j )2 ;
DXi +DX j
• B= 2·PERMXav ;
– Wi = DXi ;
– W j = DX j ;
The expression for the Y -transmissibility value is analogous to the above, with the ap-
propriate permutations of X , Y and Z . For Z -transmissibility NT Gi , NT G j and DIPC
are equal to 1.

2. If NEWTRAN (see 12.2.12) is active, transmissibility value is calculated as follows:

CDARCY · T MULT Xi
T RANXi = 1 1
,
Ti + T j

where:
(A·Di )
• Ti = PERMXi · RNT Gi · (D i ·Di )
;
(A·Di )
• 1
Wi = RNT Gi · (D i ·Di )
;
(A·D )
• 1
Wj = RNT G j · (D j ·Dj j ) .

(A · Di ) is a scalar product. For Z -transmissibility RNT Gi is equal to 1.

The following keywords can also be used:

• MULTX (see 12.2.15) specifies transmissibility multipliers in X-direction for plane be-
tween blocks [I, J, K] and [I + 1, J, K].

• MULTX- (see 12.2.16) specifies transmissibility multipliers in X-direction for plane

between blocks [I − 1, J, K] and [I, J, K].

5.5.6. Transmissibility calculation 268

 19.1

• MULTY (see 12.2.17) specifies transmissibility multipliers in Y-direction for plane be-
tween blocks [I, J, K] and [I, J + 1, K].

• MULTY- (see 12.2.18) specifies transmissibility multipliers in Y-direction for plane be-
tween blocks [I, J − 1, K] and [I, J, K].

• MULTZ (see 12.2.19) specifies transmissibility multipliers in Z-direction for plane be-
tween blocks [I, J, K] and [I, J, K + 1].

• MULTZ- (see 12.2.20) specifies transmissibility multipliers in Z-direction for plane be-
tween blocks [I, J, K − 1] and [I, J, K].

• HMMULTX / HMMULTY / HMMULTZ / HMMLTXY / HMMULTPV (see 12.2.22)

specify cumulative additional pore volume and transmissibility multipliers in positive
direction of axis X (i.e. between blocks [I, J, K] and [I + 1, J, K]), axis Y and axis Z,
respectively. HMMULTPV is the cumulative pore volume multiplier which acts as a
multiplier if MULTPV (see 12.2.28) has been previously specified.

• HMMULTX- / HMMULTY- / HMMULTZ- (see 12.2.23) specify cumulative additional

transmissibility multipliers in negative direction of axis X (i.e. between blocks [I −
1, J, K] and [I, J, K]), axis Y and axis Z, respectively.

• MAXTRANZ (see 12.2.53) specifies the upper threshold for calculated transmissibilities
in Z direction.

• PERMAVE (see 12.2.37) sets value of parameter p in formula for calculation perme-
ability averages for transmissibility:
!1
Wi · PERMXip +W j · PERMX jp p

PERMXav = .
Wi +W j

• NNC (see 12.2.54), EDITNNC (see 12.2.55), EDITNNCR (see 12.2.56), NNCGEN
(see 12.2.57), NONNC (see 12.1.53) create, edit or disallow non-neighbor connections.

• PINCH (see 12.2.58), PINCHXY (see 12.2.59), PINCHOUT (see 12.2.60), PINCHNUM
(see 12.2.62), PINCHREG (see 12.2.61) create connections across pinched-out layers.

The following data cubes are accessible to user arithmetic:

• MULTXGRD — transmissibility multiplier in X direction specified by MULTX (see 12.2.15)

in the sections GRID and/or EDIT.

• MULTYGRD — transmissibility multiplier in Y direction specified by MULTY (see 12.2.17)

in the sections GRID and/or EDIT.

• MULTZGRD — transmissibility multiplier in Z direction specified by MULTZ (see 12.2.19)

in the sections GRID and/or EDIT.

5.5.6. Transmissibility calculation 269

 19.1

• MULTX, MULTXM — transmissibility multiplier in X direction specified by MULTX

(see 12.2.15)/MULTX- (see 12.2.16) in the SCHEDULE section.

• MULTY, MULTYM — transmissibility multiplier in Y direction specified by MULTY

(see 12.2.17)/MULTY- (see 12.2.18) in the SCHEDULE section.

• MULTZ, MULTZM — transmissibility multiplier in Z direction specified by MULTZ

(see 12.2.19)/MULTZ- (see 12.2.20) in the SCHEDULE section.

5.5.7. Grid coarsening

The local grid coarsening can be applied in tNavigator. This option is opposite to the local grid
refinement (LGR) option (see section 5.5.8). In order to decrease the number of active grid
blocks selected bocks are merged and replaced by coarsened blocks. The following keywords
are supported:

• COARSEN (see 12.2.105) – This keyword sets blocks coarsening.

5.5.8. LGR – Local Grid Refinement

In tNavigator local grid refinements can be specified.
The following keywords are supported:

• LGR (see 12.1.88) (RUNSPEC section) – set options and dimensions for local grid
refinement.

• LGRCOPY (see 12.1.118) (RUNSPEC section) – this option allows blocks of refined
grid to inherit formation properties from parent grid host blocks.

• CARFIN (see 12.2.97) (GRID section)– specifies a Cartesian local grid refinement
(LGR). CARFIN (see 12.2.97) 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.97) 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.101), which terminates data for a local grid refinement.

• REFINE (see 12.2.99) – 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.101), 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.101) – terminates data for a local grid refinement.

• LGRON (see 12.19.272) (SCHEDULE section) – activates a local grid refinement at any
time step.

5.5.7. Grid coarsening 270

 19.1

• LGROFF (see 12.19.273) (SCHEDULE section) – switches a local grid refinement off at
any time step.

• NXFIN / NYFIN / NZFIN (see 12.2.102) (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.103) (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.19.4) (SCHEDULE section) – introduces a new well, defining in-
formation on its name and coordinates in local grids (LGR). WELSPECL must be used
in place of WELSPECS (see 12.19.3) to set the general specification data for wells in
local refined grids.

• COMPDATL (see 12.19.7) (SCHEDULE section) – defines well completions in local

grids (LGR).
COMPDATL (see 12.19.7) must be used in place of COMPDAT (see 12.19.6) to specify
the connection data for wells in local refined grids.

• COMPLMPL (see 12.19.30) (SCHEDULE section) – lumps connections together into

completions to provide realization of simultaneous actions for wells in local grids
(LGR).
COMPLMPL (see 12.19.30) must be used in place of COMPLUMP (see 12.19.29) to
lump connections together into completions to provide realization of simultaneous ac-
tions for wells in local refined grids.

• WPIMULTL (see 12.19.36) (SCHEDULE section) – multiplies well connection transmis-

sibility factors by specified value for wells in local grids (LGR).
WPIMULTL (see 12.19.36) must be used in place of WPIMULT (see 12.19.35) to multi-
ply well connection transmissibility factors by specified value for wells in local refined
grids.

• WELOPENL (see 12.19.129) (SCHEDULE section) – shuts or reopens wells and well
connections in Local Grid Refinement (LGR - 5.5.8).

• WFRACL (see 12.19.144) (SCHEDULE section) – specifies the hydraulic fracture for
wells in local refined grids (LGR). WFRACL (see 12.19.144) must be used in place of
WFRAC (see 12.19.143) to specify the hydraulic fracture for wells in local refined grids.

• WFRACPL (see 12.19.146) (SCHEDULE section) – specifies the hydraulic fracture for
wells in local refined grids (LGR) in graphical interface. WFRACPL (see 12.19.146)
must be used in place of WFRACP (see 12.19.145) to specify the hydraulic fracture for
wells in local refined grids in graphical interface.

5.5.8. LGR – Local Grid Refinement 271

 19.1

• COMPFRACL (see 12.19.149) (SCHEDULE section) – specifies the hydraulic fracture

for connection in the grid layer for wells in local refined grids (LGR). COMPFRACL
(see 12.19.149) must be used in place of COMPFRAC (see 12.19.148) to specify the
hydraulic fracture for connection in the grid layer for wells in local refined grids.

5.6. Well Approximation

After discretization of equations for each grid block penetrated by the well the relationship be-
tween 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.19.42), WCONINJE, see 12.19.44).

5.6.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.103) the inflow performance relationship for each well
connection l with coordinates (i, j, k), defined by keyword COMPDAT (see 12.19.6), can be
written in terms of the volumetric phase flow rate (P = {W, O, G}, i.e. Water, Oil, Gas) as:

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.6.2;

• MP = MP (pl , SW
l , Sl ) – the total phase mobility at connection l , defined below, see
G
section 5.6.5;

• pl , SW
l , Sl – nodal pressure and saturations in the grid block, containing connection;
G

5.6. Well Approximation 272

 19.1

• Nc – component molar densities in block l ;

• plcon (t) – the connection l pressure, see section 5.6.6;

To specify connections and trajectories of wells for locally refined grids instead of COM-
PDAT (see 12.19.6) the keyword COMPDATL (see 12.19.7) or COMPDATM (see 12.19.8)
should be used.
An interval of well perforations in measured depth (between upper measured depth MDU
and lower measured depth MDL) is defined using the keyword COMPDATMD (see 12.19.10).
tNavigator automatically defines intersections of the well bore with grid and opens connections
in the depth interval between MDU and MDL values.
Locations and properties of one or several connections of specified well can be specified
by WELLCOMP (see 12.19.250). This keyword is obsolete, therefore it is recommended to
use the keyword COMPDATMD (see 12.19.10).

5.6.2. Connection transmissibility calculation (CF and Kh)

Connection productivity index T l (t) may be defined by user, COMPDAT (see 12.19.6). Oth-
erwise it is calculated according to formula
l
2πKmult (t)βc (Kh)l
l
T (t) = . (5.3)
(ln(rol /rwl ) + sl )
Here
• Kmult
l (t) – KH multiplier for connection l , COMPDAT, see 12.19.6);

• βc – the unit conversion factor, see section 10;

• (Kh)l may be explicitly defined by user, COMPDAT (see 12.19.6); otherwise it is cal-
culated as product of K l – average permeability in plane perpendicular to well axis,
see section 5.6.3, and hl , the size of the grid block in the direction of perforation
penetration;

• rol – pressure equivalent radius, defined below, see section 5.6.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 [19].

5.6.2. Connection transmissibility calculation (CF and Kh) 273

 19.1

First, these parameters are calculated along directions (Khx , Khy , Khz ; CFx , CFy , CFz ).
Then, depending on model type (E1, E3, MO) the resulting value will be equal either to the
sum or the square root of sum of squares.

In models with MO format:

Kh = Khx + Khy + Khz
CF = CFx +CFy +CFz
This logic is also used in Load well data from graphical interface.

In models with E1, E3 format models (where the main part of the model is in E1
format):
p
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 MO models, to set up CF calculation like in E1, E3 format. It should be used after
trajectories.

5.6.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

• 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.6.4. Pressure equivalent radius calculation

The pressure equivalent radius rol is defined as the distance from the well at which the pres-
sure, calculated using (5.2) is equal to the pressure of the block, containing the connection. In
a Cartesian grid the Peaceman’s 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
kl
+ kl
1 2

where

5.6.3. Average permeability calculation 274

 19.1

• 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 dimen-
sions 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.6.5. Mobility calculation

Mobility calculations are different for production well connections and injection well connec-
tions. 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 )
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
• krP = krP (SW
l , Sl ) is phase relative permeability evaluated at grid block saturations;
G

• µP = µP (pl ) is phase viscosity evaluated at grid block conditions;

5.6.6. Average well bore density and connection pressure calculation

In tNavigator two models can be used to calculate density in the wellbore (specified via 12-th
parameter of the keyword WELSPECS, see 12.19.3):
• AVG – averaged density calculation model. All formulae in this section below are for
this case.
• SEG – segmented model of density calculations. In this case to calculate pressure in
the formula 5.8 density is not taken from the formula 5.7, but it is calculated for each
connection independently.

5.6.5. Mobility calculation 275

 19.1

AVG – averaged density calculation model.

Friction effects are usually small within the well bore at formation level, and they are ne-
glected. We assume Darcy flow. The average well bore density is assumed to be constant at
each calculation time step and equal to:
l +ρ
∑ ρO,SC q̃lO + ρW,SC q̃W l l l
G,SC (q̃G + RG,O (p )q̃O )
l
ρ̄av = l l
(5.7)
∑ BO (pav )q̃O + Bw (pav )q̃W + BG (pav )(q̃lG + (RG,O (pl ) − RG,O (pav ))q̃lO )
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;

• q̃lP = q̃lP (pl , SW

l , Sl ,t) is the well phase volumetric flow rate into connection l at stan-
G
dard 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.103),
WCONPROD (see 12.19.42), WCONINJE (see 12.19.44);

• 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.6.7. Well potential calculations

Well potential is well flow rate (production or injection rate) in the absence of any rate con-
straints 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.19.123).

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:

5.6.7. Well potential calculations 276

 19.1

• Group control. Wells potentials values are used as guide rates for wells, if their guide
rates are not specified via WGRUPCON (see 12.19.94). Well (and group) guide rates
can be specified according to their potentials (GUIDERAT, see 12.19.87).

• PRIORITY (see 12.19.92) – prioritization group control, one can set well priorities ac-
cording to their potentials;

• DRILPRI (see 12.19.226) – prioritized drilling queue, one can set well drilling priorities
according to their potentials.

5.6.7. Well potential calculations 277

 19.1

5.7. Modified well model

Let’s consider modified well model. Modifications help to describe hydraulic fracture simu-
lation. In this section there is a description of fracture modeling via virtual connections. Also
another possibility can be used fo define hydraulic fractures – Hydraulic Fractures modeling
via LGR.

5.7.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 w,li
b w,li = γil ϒ 2πKmult βc K h = γil Θw,li ,
Θ (5.9)
log(r0w,li /rww,li )

• 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.7. Modified well model 278

 19.1

• 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.7.2. Hydraulic fracture data

In this section there is a description of fracture modeling via virtual connections. Also another
possibility can be used fo define hydraulic fractures – Hydraulic Fractures modeling via LGR.

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 permeabil-
ity – 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.7.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 – FLOWF-
NAMES (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.19.143),
WFRACP (see 12.19.145), COMPFRAC (see 12.19.148) (LGR case – WFRACL
(see 12.19.144), WFRACPL (see 12.19.146), COMPFRACL, see 12.19.149).
For MO format models the keywords WFRA (see 14.6.27) and WFRP (see 14.6.28) can

5.7.2. Hydraulic fracture data 279

 19.1

be used (WFRP (see 14.6.28) is an analogue of WFRACP, see 12.19.145).

Fracture passes through the inactive blocks until it reaches its half-length. Thus, the
flow through inactive blocks is possible.

• 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.19.167).

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.19.145) (or 26-th parameter of WFRACPL, see 12.19.146)).

In case if injected proppant volume is specified, tNavigator calculates fracture geometry

(the formula is taken based on the article [11]):
s
k
w = C f DV (5.10)
hk f

kf w
CfD = (5.11)
kx f
where:
C f D – equals 1.6 in tNavigator (at this value optimal configuration of fracture is specified
based on the article [11]),
V – injected proppant volume,
h – fracture height (from first to last specified connection (12 and 13 parameters of the
keyword WFRACP (see 12.19.145) 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 proppant
– 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 permeabil-
ity (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;

5.7.2. Hydraulic fracture data 280

 19.1

• 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.7.3. Hydraulic fractures via virtual connections

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.7.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 ana-
logues 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.7.3. Hydraulic fractures via virtual connections 281

 19.1

-
X PERMZ
Z
? ?

PERMX
'$
#
?
PERMX PERMX
-
=⇒ 
"!
&%
 d -

h
w

Figure 24. Calculation of equivalent inflow to the fracture

5.7.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 24 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

2πβc K w, j hw, j
Θ̃w, 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.7.5. Calculation of the inflow to the fracture from the grid block 282
 19.1

5.7.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
!
q̃lc = − ∑ γ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.7.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 sec-
tion 5.7.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 con-
nection 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 – it’s 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.7.2, 5.7.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. 24.
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.7.5:
2πβc · 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 function
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.7.6. Total inflow from the hydraulic fracture to the well connection 283
 19.1

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 speci-
fied 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 proppant (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 = ∞.
Let’s 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 doesn’t 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
!
q̃lc =− ∑ w,li
γli Θ̃ li
Ψ(p − p , pb ) w w
∑ 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.7.7. Description of simulation of large amount of hydraulic fractures 284

 19.1

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.7.8. Fracture keywords

Keyword Section Description

FLOWFUNC (see 12.8.4)
FLOWFTAB (see 12.8.7)
FLOWFNAMES (see 12.8.6)
NFLOWFTB (see 12.8.5)
NPROPANTS (see 12.8.1)
PROPANTNAMES (see 12.8.2)
PROPANTTABLE (see 12.8.3)
WFRAC (see 12.19.143)
WFRACL (see 12.19.144)
COMPFRAC (see 12.19.148)
COMPFRACL (see 12.19.149)
WFRACP (see 12.19.145)
PROPS Specifies coefficients of linear or expo-
nential flow function (the dependence be-
tween permeability and flow (or time)).
I.e. this function sets the duration of the
effect of hydraulic fracture
PROPS Specifies tabular flow functions
PROPS Specifies tabular flow functions names
PROPS Specifies number of tabular flow functions
PROPS Specifies number of proppant types
PROPS Specifies proppant names
PROPS Specifies the table of relation between
pressure and proppant permeability
SCHEDULE Specifies the hydraulic fracture
SCHEDULE Specifies the hydraulic fracture in LGR-
case
SCHEDULE Specifies the hydraulic fracture for one
layer (fracture height is equal to the block
height, in which fracture goes in this layer)
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
SCHEDULE Specifies the hydraulic fracture; using this
keyword fracture geometry can be calcu-
lated by tNavigator from injected proppant
volume

5.7.8. Fracture keywords 285

 19.1

Keyword Section Description

WFRACPL (see 12.19.146)
ACTIONC (see 12.19.167)
WFRP (see 14.6.28)
WFRA (see 14.6.27)
SCHEDULE Specifies the hydraulic fracture; using this
keyword fracture geometry can be calcu-
lated by tNavigator from injected proppant
volume; LGR case
SCHEDULE Sets the automatic opening of fractures at
an event in a block (for example, the cre-
ation of fractures on the injection wells
at excess pressure in the block a certain
value)
RECU Specifies the hydraulic fracture for MO
format models.
RECU Specifies the hydraulic fracture for MO
format models.

Keywords to specify hydraulic fractures: WFRAC (see 12.19.143), WFRACP (see 12.19.145),
COMPFRAC (see 12.19.148). An in local grid refinements LGR: WFRACL (see 12.19.144),
WFRACPL (see 12.19.146), COMPFRACL (see 12.19.149). 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.19.145) (WFRACPL,
see 12.19.146).
WFRAC (see 12.19.143) and COMPFRAC (see 12.19.148) are its reductions. The differences
between COMPFRAC (see 12.19.148) and WFRAC (see 12.19.143) are:

• 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.7.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.19.35). We add the function which depends of dimensionless flow s (see
the description in the section 5.7.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

5.7.9. Simulation of plugging of well bottom zone 286

 19.1

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.19.150), which is analogous to WPIMULT (see 12.19.35).
After an operation of cleaning of well bottom zone one should specify WPIMULT
(see 12.19.35) again, this will set to zero value accumulated dimensionless flow. Specifi-
cation 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.7.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.19.151), analogous to WPIFUNC (see 12.19.150).
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.19.6) again. This will set to zero
value accumulated dimensionless flow. Specification of other parameters of the function
fsw,l (s) or specification of new type of function will also set to zero accumulated dimen-
sionless flow.

5.7.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.19.152).

5.7.10. Simulation of well bottom zone dynamics: processing acids, surfactants 287
 19.1

5.7.11. Well bottom zone keywords

Keyword Section Description

FLOWFUNC (see 12.8.4)
FLOWFTAB (see 12.8.7)
FLOWFNAMES (see 12.8.6)
NFLOWFTB (see 12.8.5)
WBHZONE (see 12.19.152)
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
PROPS Specifies tabular flow functions
PROPS Specifies tabular flow functions names
PROPS Specifies number of tabular flow functions
SCHEDULE Specifies the well bottomhole zone treatment

5.8. Hydraulic Fractures modeling via LGR

The fracture model is based on the local grid refinement (LGR) in the fracture zone and a
change of reservoir properties in the Stimulated Rock Volume (SRV). Notice that if the block
centered geometry grid (see section 5.5) is used a fracture model based on the LGR approach
can not be constructed. Figure 25 schematically shows a fracture zone (cylinder) and a fracture
stimulated zone (ellipsoid).

5.8.1. Fracture Modeling Workflow

To create a fracture follow the steps:

1. Specify a polyline (a set of points x, y, z) to construct a fracture using the keyword

FRACTURE_PATH (see 12.2.125). From the specified set of points select an anchor
point, which will be located on a well trajectory. In figure 25 the polyline FRAC-
TURE_PATH is specified by 3 points, the polyline 2–nd point (ANCHOR POINT) is a
point, in which the polyline is linked to the well bore (WELL).
As an example figure 26 shows XY and XZ projections of a polyline consisting of
5 points. 3-rd point is a polyline anchor point to the well trajectory (WELL) and is
denoted as ANCHOR POINT in figure 26. A fracture zone (FRACTURE_ZONE) and
a fracture stimulated zone (NONFRACTURE_ZONE) are shown in XY plane (top
view). In this example the option STIMULATED_DELTA is set 0 (see the keyword
FRACTURE_TEMPLATE, see 12.2.127), therefore a fracture zone and non fracture zone
coincide in XZ plane;

2. Using the keyword FRACTURE_PLANE (see 12.2.126) define a set of polylines speci-
fied by the keyword FRACTURE_PATH (see 12.2.125);

3. Specify a fracture template using the keyword FRACTURE_TEMPLATE (see 12.2.127);

5.7.11. Well bottom zone keywords 288

 19.1

x
y EFFECTIVE_WIDTH
NONFRACTURE_ZONE
FRACTURE_ZONE
∆

UP
WELL

W2 FRACTURE_PATH
W1 ANCHORPOINT
DOWN

∆
z

∆ L2 L1 ∆
LEN2 LEN1

Figure 25. Schematic model of a fracture (cylinder) and a fracture stimulated zone (ellipsoid).

4. Specify an array of fractures and link it with a well trajectory using the keyword FRAC-
TURE_WELL (see 12.2.128). Fracture(s) will be generated at indicted point (or points)
according to the specified template(s). A well trajectory has to be specified in the GRID
section using the keyword WELLTRACK (see 12.19.9) (if WELLTRACK (see 12.19.9) is
specified in the GRID section you do not need to additionally specify a well trajectory
in the SCHEDULE section). Fractures can be uniformly distributed along a well bore
(or a well branch) interval or can be set at selected points of the well trajectory.

5. The keyword FRACTURE_ARITHMETIC (see 12.2.129) is used to change reservoir

properties in a fracture zone or/and a fracture stimulated zone. For example, perme-
ability of blocks crossed by a fracture can be modified;

6. Activate a created array of fractures using the keyword FRACTURE_STAGE

(see 12.19.147) in the section SCHEDULE. Moreover, arithmetic can be implemented
to the array of fracture using the same keyword.

5.8.1. Fracture Modeling Workflow 289

 19.1

WELL

ANCHOR POINT 4
3 FRACTURE_ZONE
2

FRACTURE_PATH

5
NONFRACTURE_ZONE

5
FRACTURE_PATH

4
WELL
3

2 ANCHOR POINT

z
Figure 26. XY projection of polyline (top view). XZ projection (front view).

5.8.1. Fracture Modeling Workflow 290

 19.1

5.8.2. Fracture Zone (FZ) and Non-Fracture Zone (NFZ)

Using the keyword FRACTURE_TEMPLATE (see 12.2.127) it is possible to create a complex
configuration fracture template. Figure 25 shows a schematic fracture model. A fracture width
is specified by the option EFFECTIVE_WIDTH, its height by options UP and DOWN. A frac-
ture height UP is measured upward from an anchor point, while DOWN height is measured
downward from the anchor point. A fracture zone (FZ) is denoted as FRACTURE_ZONE and
has a cylindrical form.
NONFRACTURE_ZONE x LEVEL_UP
y
∆ ∆

FRACTURE_ZONE

UP UP
FRACTURE_PATH
H W2 W1
ANCHORPOINT
L2 DOWN WELL L1 WELL
∆ ∆ DOWN ANCHOR POINT
∆ ∆
z z
LEN LEVEL_DOWN
y
LEN2 WELL LEN1 NONFRACTURE_ZONE
FRACTURE_ZONE
W1
∆ L2 L1 ∆
W2 ANCHOR POINT EFFECTIVE_WIDTH
x

Figure 27. Front view (plane XZ ). Side view (plane ZY ). Top view (plane XY ).

Around a fracture zone a fracture stimulated zone (or non fracture zone (NFZ)) is created
and denoted as NONFRACTURE_ZONE in figure 25. NFZ width to the right of anchor
point (W1 in figures 25 and 27) and NFZ width to the left of anchor point (W2 in figures
25 and 27) are specified by options STIMULATED_WIDTH_R and STIMULATED_WIDTH_L,
respectively. By default the NFZ sizes in other directions coincide with fracture sizes in the
same directions. If it is required sizes of fracture stimulated zone can be specified different
from sizes of fracture zone using the option STIMULATED_DELTA.
Figure 27 shows projections of fracture and fracture stimulated zones onto XY , XZ and
ZY planes. Let’s consider parameters used to specify a fracture and a stimulated zone around
fracture in each plane.
In XZ plane (a front view of figure 25) the polyline FRACTURE_PATH is specified by

5.8.2. Fracture Zone (FZ) and Non-Fracture Zone (NFZ) 291

 19.1

3 points and shown with dashed line in the figure 27. An anchor point of polyline FRAC-
TURE_PATH to a WELL bore is 2-nd point of polyline and denoted as ANCHOR POINT in
the figure 27. The fracture length to the right of the anchor point is denoted as L1 and to the
left of the anchor point as L2 . The fracture height upwards from the anchor point is denoted
as UP and specified using the option UP. The fracture height downwards from the anchor
point is denoted as DOWN and specified using the option DOWN. Thus, the fracture length is
equal to L1 + L2 and the fracture height is equal to UP+DOWN. The fracture projection onto
XZ plane is an ellipse and denoted as FRACTURE_ZONE in the figure 27.
To create the fracture stimulated zone (NONFRACTURE_ZONE) in this plane an in-
crement ∆ is specified using the option STIMULATED_DELTA. Then the length of the
fracture stimulated zone (nonfracture zone) is equal to LEN = L1 + L2 + 2∆ and its width
is H=UP+DOWN+2∆. As can be seen in the figure 27 the nonfracture zone projection is
an ellipse as well. Notice that if the option STIMULATED_DELTA is not specified, i.e. the
increment ∆ is 0, the nonfracture zone will coincide with the fracture zone in this plane.

x y
αxz3 αxz4
αyz3 αyz4

III IV
III IV
WELL
WELL
II I II I
αxz2 αxz1 αyz2 αyz1
z z
x
y
WELL y αxz3 αxz4
αyz3
αxy2 b1 αxy1
αyz4
II I αxy3 αxy4
a2 a1
III IV αxy2 αxy1
αxy3 b2 αxy4
αyz1 αyz2
x αxz2 αxz1
z
Figure 28. Distribution of curvatures: Front view (plane XZ ). Side view (plane ZY ). Top
view (plane XY ).

In XY plane (a top view of figure 25) the polyline FRACTURE_PATH is specified by 3

points and shown with dashed line in the figure 27. The polyline is linked to the well bore
(WELL) in 2-nd point denoted as ANCHOR POINT. In this plane the fracture zone (FRAC-
TURE_ZONE) is the rectangular (a layer of refined blocks). The fracture length is equal to

5.8.2. Fracture Zone (FZ) and Non-Fracture Zone (NFZ) 292

 19.1

the polyline length L1 + L2 and its width is specified by the option EFFECTIVE_WIDTH. In
addition, the nonfracture zone width to the right of anchor point and to the left of this point
has to be specified by options STIMULATED_WIDTH_R and STIMULATED_WIDTH_L, re-
spectively.
Notice that if the option STIMULATED_DELTA is specified (by default ∆ is 0) the fracture
stimulated zone length along X direction is LEN = L1 +L2 +2∆. The fracture stimulated zone
projection (denoted as NONFRACTURE_ZONE) is an ellipse in this plane.
In ZY plane (side view of 25) the polyline FRACTURE_PATH is specified by 3 points
and shown with dashed line in the figure. An anchor point of polyline FRACTURE_PATH to
WELL bore is 2-nd point of polyline and denoted as ANCHOR POINT in figure 27. In this
plane the fracture zone (FRACTURE_ZONE) is the rectangular (layer of blocks) with length
equal to the polyline length L1 + L2 and width specified by the option EFFECTIVE_WIDTH.
The projection of fracture stimulated zone (denoted as NONFRACTURE_ZONE) is an
ellipse. The width of this zone is specified by options STIMULATED_WIDTH_R and STIM-
ULATED_WIDTH_L denoted as W1 and W2 in the figure 27. The nonfracture zone length is
UP+DOWN+2∆ if the option STIMULATED_DELTA is specified.
Options LEVEL_UP and LEVEL_DOWN set a restriction of fracture length (in terms of
initial coarse grid blocks) measured upward and downward from an anchor point. Thus, using
these options it is possible to change UP and DOWN heights of the fracture. In figure 27 (a
projection on the plane Y Z ) a fracture crosses 3 blocks of the coarse grid upward from the
block, where an anchor point is located, and 1 block of the coarse grid downward from this
block. For example, if LEVEL_UP is set 1 a fracture will cross only one coarse grid block
located above the block containing an anchor point, i.e. the size specified by the option UP
will be decreased.
A fracture stimulated zone and a fracture itself can have a rectangular form or be formed
by curves with specified curvatures. A curvature α is specified by option SHAPE of the
keyword FRACTURE_TEMPLATE (see 12.2.127).
A fracture stimulated zone can be subdivided into 4 regions. In each region a curvature α
can be different. Figure 28 shows the distribution of curvatures formed the fracture stimulated
zone and projections of the fracture and the fracture stimulated zone on XY , XZ and ZY
planes.
Let’s consider a projection on XY . The curvature in I region is represented by αxy1
(option SHAPEXY1), the curvature in II region by αxy2 (option SHAPEXY2), the curvature
in III region by αxy3 (option SHAPEXY3) and the curvature in IV region by αxy4 (option
SHAPEXY4). In the plane XY for each region I, II, III and IV the curve forming the fracture
stimulated zone is calculated as:

5.8.2. Fracture Zone (FZ) and Non-Fracture Zone (NFZ) 293

 19.1

xαxy1 yαxy1

+ in I,

 α α
a1 xy1 b1 xy1










xαxy2 yαxy2




 α + α in II,
a2 xy2 b1 xy2




f (x, y) =


 xαxy3 yαxy3
α + α in III,



a2 xy3 b2 xy3









xαxy4 yαxy4



 αxy4 + αxy4 in IV;


a2 b2

where f (x, y) = 1.

5.8.2. Fracture Zone (FZ) and Non-Fracture Zone (NFZ) 294

 19.1

1 ≤ αxz < 150 αxz ≥ 150

III IV

WELL
II I

z
Figure 29. Curvature types (plan XZ ): 1 ≤ αxz < 150 – ellipse, αxz ≥ 150 – rectangular.

As can be seen in the figure 29 that in the plane XZ the curvature αxz specifies not only
a form of the fracture stimulated zone NFZ, but a form of the fracture zone.
If the value of curvature larger or equal to 150 is set for any SHAPE option then both
fracture and fracture stimulated zone have a rectangular form (see figure 29). If this number
is lower then 150 then the fracture is an elliptic cylinder with the cylinder base in XZ plane,
while the fracture stimulated zone is an ellipsoid. Notice that all curvatures are equal to 2 by
default.

5.8.2. Fracture Zone (FZ) and Non-Fracture Zone (NFZ) 295

 19.1

5.8.3. Local Grid Refinement and Unstructured Grids

The local grid refinement (LGR) is implemented in the domain including both fracture zone
and fracture stimulated zone. Each grid block is subdivided into the number of refined blocks,
which is specified in the keyword FRACTURE_TEMPLATE (see 12.2.127).
By default, Unstructured Refinement is enabled. If other refinement type (Uni-
! form or Logarithmic) is needed then the FRACTURE_BUILD_LOGIC flag of
TNAVCTRL (see 12.1.4) keyword should be changed to .
Unstructured refined grids can be used to reduce the total number of refined blocks and
for more accurate depiction of Fracture Zone (see. Picture 30).
In this case local grid refinement will be made in several steps:

1. The initial refinement will be done for all blocks in SRV zone.

2. The nearest to the the fracture refined blocks will be refined again in order to obtain the
accurate blocks pattern (i.e. the nested refinement will be created).

3. The maximum number of nested refinements can be set via

UNSTRUCTURED_FRACTURE_GRID_LEVELS parameter of TNAVCTRL (see 12.1.4)
keyword.

Figure 30. Examples of Grid Refinement using Unstructured Grids.

5.8.3. Local Grid Refinement and Unstructured Grids 296

 19.1

The following parameters of FRACTURE_TEMPLATE (see 12.2.127) become

unavailable for editing when Unstructured Grid refinement is used:

!
• The number of block’s refinement along X, Y and Z directions.

• REFINEMENT

• LEVEL_UP

• LEVEL_DOWN

When the usage of Unstructured Grids is disabled in TNAVCTRL (see 12.1.4) keyword the
following refinement types become available:
• UNIFORM – corresponding blocks of coarse grid are refined uniformly. Comparing to
other methods, uniform partition yields the least detailed refinement pattern. However,
it could be used to model non-planar shapes of Hydraulic Fractures. An example of
Uniform refinement applied for complex fracture geometry is provided on picture 31.

• LOGARITHMIC_SIMPLE – corresponding blocks of coarse grid are subdivided logarith-

mically in a plane perpendicular to a fracture plane if the fracture located in one layer of
coarse grid blocks. A block containing an anchor point is subdivided logarithmically (if
a block size allows a logarithmic subdivision) in each direction from the anchor point
(in the plane perpendicular to the fracture plane). The smallest step size of grid refine-
ment in the direction perpendicular to the fracture is equal to the fracture width (option
EFFECTIVE_WIDTH), while the smallest step size of grid refinement in the direction
along the fracture is calculated automatically and can be smaller than the fracture width.
The maximum step size of grid refinement is specified automatically such as the number
of refined blocks to the left and right of the anchor point is equal. Furthermore, if the
specified number of refined blocks (in the plane perpendicular to the fracture plane) is
even then the block containing the anchor point will be subdivided into odd number of
blocks (specified number of blocks +1);

• LOGARITHMIC_DETAILED – in contrast to the described above method

(LOGARITHMIC_SIMPLE) the maximum size of refined block along axis perpendicu-
lar to the fracture is specified as: let’s n is the number of refined blocks in the direction
perpendicular to the fracture then the maximum size of refined block can not be larger
than 1/n of corresponding coarse grid block size. This method allows to get a de-
tailed refinement of the fracture zone, however, the number of refined blocks might be
different from the specified value.
Comparison of LOGARITHMIC_SIMPLE and LOGARITHMIC_DETAILED refinement op-
tions is provided on picture 32.
Global grid blocks are subdivided logarithmically in the plane perpendicular to the fracture
plane if the fracture located in one layer of coarse grid blocks, otherwise coarse grid blocks are
subdivided uniformly. For example, it can be seen in the figure 27 that the fracture is within

5.8.3. Local Grid Refinement and Unstructured Grids 297

 19.1

on layer of coarse grid blocks then coarse global blocks will be subdivided logarithmically in
X and Y directions and uniformly in Z direction. However, if a block size does not allow to
carried out a logarithmic subdivision then a block will be subdivided uniformly.

Figure 31. Complex Fracture Geometry defined via uniform refinement.

Figure 32. Comparison of Logarithmic Refinement options. The same Settings were used for
both cases: NX=NY=5, NZ=1

5.8.3. Local Grid Refinement and Unstructured Grids 298

 19.1

5.8.4. Fractures Intersection

SRV zones of different Fracture Stages may intersect each other. In this case:

• Unstructured LGR will be created taking into account all objects on the plane including
points of fractures intersection;

• If tho SRVs with different grid property have an intersections then the higher of two
values will be assigned to the common blocks (both in Fracture Zone (FZ) and Non-
Fracture Zone (NFZ)).
Example. One the picture 33: WELL_1 FZ Permeability is 1000mD, WELL_2 FZ
Permeability is 300mD. Permeability value in the blocks, where fractures intersect each
other will be set equal to 1000mD.

Figure 33. Intersecting Fracture Stages.

5.8.4. Fractures Intersection 299

 19.1

5.8.5. Permeability Adjustment in Fracture Zone

The dynamic properties of Hydraulic Fracture can be characterized by the product of its
Effective Width and Permeability - Fracture Conductivity:

Cf = kf × w (5.17)
In order to adjust the Permeability values in all blocks in Fracture Zone, the additional
parameters of FRACTURE_TEMPLATE (see 12.2.127) keyword can be used – WIDTH and
WIDTH2 (for dual porosity models).
By default WIDTH=WIDTH2=EFFECTIVE_WIDTH
Permeability will be recalculated for each block in Fracture Zone as follows:

• For Uniform Refinement type:


W IDT H
PERMX_MODEL = PERMX_DATA ×






 Davg
PERMY _MODEL = PERMY _DATA × W IDT H



Davg (5.18)
 W IDT H
PERMZ_MODEL = PERMZ_DATA ×





 Davg



D = (DX + DY + DZ)/3
avg

– PERM[X,Y, Z]_DATA – Grid blocks permeability in FZ, defined by the cor-

responding parameters of FRACTURE_TEMPLATE (see 12.2.127) and FRAC-
TURE_ARITHMETIC (see 12.2.129) keywords.
– PERM[X,Y, Z]_MODEL – Recalculated Grid blocks permeability in FZ that will
be used in dynamic model.
– DX , DY , DZ – Dimensions of the refined block.
– WIDTH – Width parameter defined by FRACTURE_TEMPLATE (see 12.2.127)
keyword.

• For Logarithmic Refinement:

– If the refinement is built along X axis (i.e. the Fracture Plane is perpendicular to
Y axis):





PERMX_MODEL = PERMX_DATA
W IDT H

PERMY _MODEL = PERMY _DATA × (5.19)
 DX
W IDT H


PERMZ_MODEL = PERMZ_DATA ×

DX

5.8.5. Permeability Adjustment in Fracture Zone 300

 19.1

– If the refinement is built along Y or Z axis: the permeability in the direction

perpendicular to the Fracture Plane will remain unchanged, whereas the other two
permeabilities will be modified according to the algorithm described above (eq.
5.19).
• In dual porosity / dual permeability models the parameter WIDTH is used for perme-
ability recalculation in Matrix blocks. For the fracture media, the WIDTH in equations
5.18 and 5.19 is substituted by WIDTH2 parameter.

5.8.6. Fracture Rotation

In addition, the fracture can be rotated around vertical axis on the specified angle using the
option ROTATE_XY (see figure 34), the vertical axis can be rotated around an anchor point
in the fracture plane on the angle specified by the option ROTATE_Z.

WELL
Ω

Ω = ROTATE_XY x
Figure 34. Fracture rotation around vertical axis.

5.8.7. Properties of inactive coarse blocks, penetrated by the fracture

Permeability of blocks with nonzero pore volume is specified by the option PERM_FZ (or
PERM_FZ2 in dual porosity models) in the fracture zone (FZ) and using the optionPERM_NFZ
(PERM_NFZ2 in dual porosity models) in the nonfracture zone (NFZ). By default permeability
of refined block is set equal to permeability of correspondent coarse grid block.
Notice that if blocks with zero pore volume end up in the fracture zone or the fracture
stimulated zone then after the fracture has been activated pore volume of these blocks is
calculated as a product of geometrical volume of these blocks, porosity specified by the
option PORO_ACT (or PORO_ACT2 in dual porosity models) and net–to–gross specified by
the option NTG_ACT (or NTG_ACT2 in dual porosity models). Permeability of these blocks is
specified by the option PERM_ACT (or PERM_ACT2 in dual porosity models). It is supposed
that after fracture activation water occurs in these blocks. Furthermore, all required properties
(pressure etc.) are recalculated in these blocks.

5.8.6. Fracture Rotation 301

 19.1

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 conserva-
tion equation for each component (4.82) 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.62)

• for alkaline: ALKALINE (see 12.1.52)

• for surfactant: SURFACT (see 12.1.49)

• for polymer: POLYMER (see 12.1.51)

Initial values are specified via:

Agent Equilibrium initialization Non-equilibrium initialization

Salts SALTVD (see 12.16.48) SALT (see 12.16.47)
Alkaline 0 0
Surfactant 0 SURF (see 12.16.50)
Polymer 0 SPOLY (see 12.16.51)

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 ρWsc (specified

via DENSITY, see 12.5.33).

5.9. ASP model description 302

 19.1

The system of conservation equations:

 asp 
krW asp asp
UW = −βc k asp (∇p + ∇PcW − ρW g∇d) (5.20)
µW
∂
(ϕNw ·Csalt ) = − div (ξW UW ·Csalt ) + Qsalt (5.21)
∂t
∂ ∂  ads

(ϕNw ·Calkl ) + (1 − ϕ)ρrock ·Calkl = − div (ξW UW ·Calkl ) + Qalkl (5.22)
∂t ∂t
∂
∂  
(1 − ϕ)ρrock · Aalkl ads


ϕNw ·Csur f + sur f sur f = − div ξW UW ·Csur f + Qsur f
C (5.23)
∂t ∂t
∂
∂  
(1 − Sd pv )ϕNw ·C poly + (1 − ϕ)ρrock · Aalkl ads
poly poly =
C
∂t ∂t  
= − div ξW UW · Bvisc
polyC poly + Q poly (5.24)

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),

• Calkl
ads – concentration of adsorbed alkaline (kg/kg), as a function of C 3
alkl (kg/sm ) in
ALKADS (see 12.8.41).

• Csur
ads – concentration of adsorbed surfactant (kg/kg), as a function of C
f
3
sur f (kg/sm )
in SURFADS (see 12.8.9).

• Cads
poly – concentration of adsorbed polymer (kg/kg), as a function of adsorbed Csur f
(kg/sm3 ) in PLYADS (see 12.8.26).

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

• Aalkl 3
poly – polymer adsorption multiplier (dimensionless), as a function Calkl (kg/sm ) in
ALPOLADS (see 12.8.40).

• ρrock – rock molar density. In black-oil models (E1) the rock mass density is used, in
compositional models (E3) the rock mass density divided by water molecular weight
MWW is used. Rock mass density is specified via 3-rd parameter of the keyword PLY-
ROCK (see 12.8.30) (if there are polymers then the 2-nd parameter of SURFROCK
(see 12.8.13) is ignored), or via the 2-nd parameter of SURFROCK (see 12.8.13).

5.9. ASP model description 303

 19.1

• Sd pv – dead pore space, specified via 1-st parameter of PLYROCK (see 12.8.30).

• Qsalt – salt sources (wells, aquifers). The keywords WSALT (see 12.19.175), 12-th
parameter of AQUCT (see 12.17.9), 8-th parameter of AQUFETP (see 12.17.6), 3-rd
parameter of AQUFLUX (see 12.17.2), 7-th parameter of AQUCHWAT (see 12.17.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.33).

• Qalkl – alkaline sources (wells). Keyword WALKALIN (see 12.19.173). 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.33).

• Qsur f – surfactant sources (wells). Keyword WSURFACT (see 12.19.172). 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.33).

• Q poly – polymer sources (wells). Keyword WPOLYMER (see 12.19.174). 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.33).

5.9.1. Water relative permeability calculations

asp
Let’s consider the calculation of krW .
Capillary number Kc :
   
kk∇pk −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.10);

• Aalkl 3
st (Calkl ) – surface tension multiplier, specified as function of Csur f (kg/sm ) in
ALSURFST (see 12.8.38);

• Cunit = 9.869234E − 11 – multiplier dependent on unit system.

Denote (see the tables 3 and 5) with
• krW
imm (S ), kimm (S ) – user data for immiscible conditions that are specified via num-
W rOW W
ber of table SATNUM (see 12.4.3) and scaling arrays SWL (see 12.6.26), SWCR
(see 12.6.29), SWU (see 12.6.33), SOWCR (see 12.6.31), KRW (see 12.6.59), KRO
(see 12.6.58), KRORW (see 12.6.58);

5.9.1. Water relative permeability calculations 304

 19.1

• krW
mis (S ), kmis (S ) – user data for miscible conditions that are specified via number of
W rOW W
table SURFNUM (see 12.4.4) and scaling arrays SWL (see 12.6.26), SWU (see 12.6.33),
KRW (see 12.6.59), KRO (see 12.6.58), KRORW (see 12.6.58);
0imm (S ),
The scaled relative permeabilities (calculated according to 4.35.2) we denote as krW W
0imm (S ), k0mis (S ), k0mis (S )
krOW W rW W rOW W
Then phase relative permeabilities in water-oil system if the surfactant is present are:
0 0mis 0imm
krW (SW ) = Fcapd (Kc )krW (SW ) + (1 − Fcapd (Kc ))krW (SW )
0 0mis 0imm
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.12) 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,
see 12.4.3); using these functions the corresponding phase relative permeabilities krG0 (S ),
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
krOW 0 (S ), k0
(SW ), krG (S ) according to the section 4.35.3.
G rOG G

5.9.2. Water viscosity calculations

asp
Let’s consider the calculation of µW and Bvisc
poly .
The keywords that specify the data for these calculations depend on whether there is salt
in the model (keyword BRINE, see 12.1.62) or not.

5.9.3. Water viscosity calculations without salt

Let’s 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.11).
Let’s denote
• µ poly (C poly ) – function (dimensionless), specified in PLYVISC (see 12.8.25);

• Cmax 3
poly – maximal polymer concentration (kg/sm ), specified in the 1-st parameter of
PLYMAX (see 12.8.28);

• ω – parameter, specified in PLMIXPAR (see 12.8.29),

• Krr f – parameter (residual resistance factor), specified via 2-nd parameter of PLYROCK
(see 12.8.30),

5.9.2. Water viscosity calculations 305

 19.1

• Cads,max
poly – maximal adsorbed polymer concentration (kg/sm3 ), specified in 5-th param-
eter of PLYROCK (see 12.8.30).
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 = · · max
· visc
µW Cads,max
poly + (Krr f − 1)Cads
poly
(µ poly (C poly )) (µ poly (C poly ))
ω (1−ω) B 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.10).

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.8) and BDENSITY (see 12.7.7).

5.10. Oil and gas in-place

5.10.1. Overview
Oil and gas in place are presented in tNavigator at the following locations:

5.9.4. Capillary pressure in water-oil system 306

 19.1

• As grids on the tab Grid Properties → Fluid-in-place (see section 5.10.2);

• As graphs on the tab Graphs → Fluid-in-place (see section 9.3 of the tNavigator User
Guide);

• In the *.log file (see section 5.10.3).

!
When calculating models with dual porosity, the fluids in place are repre-
sented in the interface separately for matrix and fracture. To obtain the totals
(corresponding to the records in the log file), it is necessary to add up these
values.

5.10.2. Fluid-in-place tab

In tNavigator in the map tree Fluid-in-place the following properties 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 properties can be used in User Arithmetic in User Maps. Their names in brackets
should be entered in the 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);

5.10.2. Fluid-in-place tab 307

 19.1

• 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 formulae (description of all parame-
ters 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;

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 in-place are considered immobile and
corresponding part of the formula is set equal to zero (negative values don’t sum in this
formula). Mobile oil in place is generally lower than total oil in place, because the latter
includes the immobile oil, while the former doesn’t;

4. Mobile oil in place (Mass) moipm = moip ∗ rho;

5. Free oil in place porv ∗ soil ∗ ibo. Free oil in place is generally lower than total oil in
place, because the latter includes the vaporized oil, while the former doesn’t;

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;

5.10.2. Fluid-in-place tab 308

 19.1

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 in-place are considered immobile and
corresponding part of the formula is set equal to zero (negative values don’t sum in this
formula). Mobile gas in place is generally lower than total gas in place, because the
latter includes the immobile gas, while the former doesn’t;

4. Free gas in place porv ∗ sgas ∗ ibg. Free gas in place is generally lower than total gas in
place, because the latter includes the gas dissolved in oil, while the former doesn’t;

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 block’s oil saturation (soil ) is below the critical oil saturation (sowcr ), the oil is
considered immobile.
If the block’s gas saturation (sgas) is below the critical gas saturation (sgcr ), the gas is con-
sidered 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. It’s calculation depends of
rock properties specification, the keyword ROCK (see 12.5.17) (E1/E3) or CROC, REFE
(MO) or the keyword ROCKTAB (see 12.5.21) (E1/E3) or KVSP (MO). If the keyword
ROCK is used, then

porv = (1 +C ∗ (p − PREF) +C ∗C ∗ (p − PREF) ∗ (p − PREF)/2) ∗V ∗ PORO ∗ NT G

5.10.2. Fluid-in-place tab 309

 19.1

where p is the pressure, C and PREF are specified in the keyword ROCK (see 12.5.17),
V is the geometric volume of the cell (not equal to DX*DY*DZ for a non-uniform rect-
angular 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.33) (E1/E3) or DENSITY/BASIC (MO).

• 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.33) (E1/E3) or DENSITY/BASIC (MO).

5.10.3. Log file

Upon reading a model, a section STATISTICS FOR MODEL is written to the log file.
Depending on the presence of the corresponding phases in the model, it may contain the
following values of fluids in place (calculated in the same way as in the interface, see section
5.10.2):

• Original oil in place (METRIC: sm3 , FIELD: stb);

• Original free oil in place (METRIC: sm3 , FIELD: stb);

• Original vaporized oil in place (METRIC: sm3 , FIELD: stb);

• Original mobile oil in place (rel water) (METRIC: sm3 , FIELD: stb) is mobile oil
replaced by water and calculated as (soil − sowcr) · porv · ibo;

• Original mobile oil in place (rel gas) (METRIC: sm3 , FIELD: stb) is mobile oil replaced
by gas and calculated as (soil − sogcr) · porv · ibo;

• Original water in place (METRIC: sm3 , FIELD: stb);

• Original mobile water in place (METRIC: sm3 , FIELD: stb);

• Original gas in place (METRIC: sm3 , FIELD: stb);

• Original free gas in place (METRIC: sm3 , FIELD: stb);

• Original dissolved gas in place (METRIC: sm3 , FIELD: stb);

• Original mobile gas in place (METRIC: sm3 , FIELD: stb);

• Original hydrocarbon in place (METRIC: rm3 , FIELD: rb);

5.10.3. Log file 310

 19.1

• Original displ. hydrocarbon in place (METRIC: rm3 , FIELD: rb).

As the simulation progresses, a table FIP DATA FIPNUM is written to the log file on
each step. It contains the following values of fluids in place:

• Current oil in place (METRIC: sm3 , FIELD: stb);

• Original oil in place (METRIC: sm3 , FIELD: stb);

• Current mobile oil in place (rel water) (METRIC: sm3 , FIELD: stb);

• Original mobile oil in place (rel water) (METRIC: sm3 , FIELD: stb);

• Current mobile oil in place (rel gas) (METRIC: sm3 , FIELD: stb);

• Original mobile oil in place (rel gas) (METRIC: sm3 , FIELD: stb);

• Current free oil in place (METRIC: sm3 , FIELD: stb);

• Original free oil in place (METRIC: sm3 , FIELD: stb);

• Current vaporized oil in place (METRIC: sm3 , FIELD: stb);

• Original vaporized oil in place (METRIC: sm3 , FIELD: stb);

• Current water in place (METRIC: sm3 , FIELD: stb);

• Original water in place (METRIC: sm3 , FIELD: stb);

• Current mobile water in place (METRIC: sm3 , FIELD: stb);

• Original mobile water in place (METRIC: sm3 , FIELD: stb);

• Current gas in place (METRIC: sm3 , FIELD: stb);

• Original gas in place (METRIC: sm3 , FIELD: stb);

• Current mobile gas in place (METRIC: sm3 , FIELD: stb);

• Original mobile gas in place (METRIC: sm3 , FIELD: stb);

• Current free gas in place (METRIC: sm3 , FIELD: stb);

• Original free gas in place (METRIC: sm3 , FIELD: stb);

• Current dissolved gas in place (METRIC: sm3 , FIELD: stb);

• Original dissolved gas in place (METRIC: sm3 , FIELD: stb);

• Hydrocarbon surface volume (METRIC: sm3 , FIELD: stb);

• Current displ. hydrocarbon in place (METRIC: rm3 , FIELD: rb);

5.10.3. Log file 311

 19.1

• Pore volume (METRIC: rm3 , FIELD: rb);

• Reservoir pore volume (METRIC: rm3 , FIELD: rb);

• Reservoir volume of water (METRIC: rm3 , FIELD: rb);

• Reservoir volume of oil (METRIC: rm3 , FIELD: rb);

• Reservoir volume of gas (METRIC: rm3 , FIELD: rb);

• Reservoir volume of hydrocarbon (METRIC: rm3 , FIELD: rb).

5.10.4. Fluid-in-place 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 enabled 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 in-place for layers from 27 to 84.
tNavigator formula of mass mobile oil in-place 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.10.4. Fluid-in-place density and concentration 312

 19.1

5.10.5. Oil and gas in-place via separators

In compositional case (E3 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.16.24). 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.16.25).
Sum of oil and gas in-place for FIP region (FIPSEP) can be not equal to oil and gas in-place
for field calculated via FIELDSEP (see 12.16.24).

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 spec-
ified via the keywords GPTABLE (see 12.16.26), GPTABLE3 (see 12.16.28) or GPTABLEN
(see 12.16.27).

5.11. 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.16.40) or it can be taken from the 1-st equilibration region reference depth, spec-
ified via EQUIL (see 12.16.2). If keywords DATUM (see 12.16.40), EQUIL (see 12.16.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.16.41). One can specify reference depth different for different fluid-
in-place regions (FIP, see 12.4.11) via the keyword DATUMRX (see 12.16.42).

5.10.5. Oil and gas in-place via separators 313

 19.1

Field oil potential (FPPO in section SUMMARY, see 12.18.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 satura-
tion; Porv – block pore volume;

• in the case that the value of 31-th parameter of OPTIONS (see 12.19.243) is even
∑ POTO ∗ Porv
FPPO =
∑ Porv

5.12. Split and merge (sector modeling)

Detailed description and examples of model split and merge see please
in the training tutorial SIM7.1. How to Split and Merge Model.

The following note should be taken into account to split the model into sec-
tors:

• Grid couldn’t be edited in sector models. If for example you would like
to add LGR in sector, then it should be created in advance in full model
and then splitting performed.

!
• Active blocks shouldn’t be changed in sector models.

• Solver tuning options RUNCTRL (see 12.19.140) should be the same

for full model and it’s sectors. They should be set in advance in full
model. Different tuning settings in sectors are not allowed.

• Aquifer shouldn’t be splitted, whole aquifer should be in one sector.

• Reporting time steps should be the same in full model and in sectors.

In tNavigator, you split and merge the model (sector modeling) the following way:
1. Open a model (but do not run a computation).

2. Create a User Map or a User Cut to assign the regions (sectors) the model is to be split
into. You can split a model using any Cut or any User Map, you can cut out any FIP
region as well.
Note 1. Split on the distance far from wells to reduce the influence of boundary condi-
tions.

5.12. Split and merge (sector modeling) 314

 19.1

Note 2. We recommend splitting the model so that the boundaries run through minimum
cross-flows areas. Cumulative water, oil, and gas cross-flow properties can be requested
prior to a model computation via the keyword RPTMAPS (see 12.16.55).

3. Split the model into sectors via the button Split model in the graphical interface (select
Cut or Map to split).

4. Sector project PATTERNS is created in the folder with the model. The main project file
– .patterns. In the separate folders there are sector models (parts of the big initial model)
(NAME_PATTERNS_PATTERN001_1, NAME_PATTERNS_PATTERN001_2, etc.).
These models are independent from the big case (with their own files, sections with
keywords). Sectors have less active grid blocks than original big model.

5. Compute once the file .patterns. The boundary conditions for sectors are recorded in
.flux files (flow through the boundary). Flux files will be written to the folders with
corresponding sectors. After that model sectors are ready to use.
Note. If the .patterns file is not calculated then sectors can be open and calculated with
zero boundary conditions.

6. All sectors can be open independently and calculated. Sectors are calculated with bound-
ary conditions (.flux files).
We can add modifications to sectors (do history matching on well level, add wells, add
hydraulic fractures, change relative permeabilities, add aquifers).
Note. Sectors can be copied to another computers (several reservoir engineers can work
with different sectors). Reducing the size of model allows to work with sectors on the
computers with less amount of memory (comparing to the amount we need to work with
original model).

7. Then copy the data for sectors back to the folder with .patterns file. Reload .patterns file
to merge all modifications that have been made in sectors.

8. Recalculate .patterns file to update boundary conditions for sectors (.flux files).

9. Then we can continue working with sectors, merging modification together and recal-
culating .patterns file to update boundary conditions.

5.12.1. Split in console version

Add a keyword FIPPATT (see 12.4.13) to the model indicating split parts of the model. Run
the console version of tNavigator with the option --split.
The boundary conditions are written in .flux files, sector models are ready for use. After that
sector models can be calculated in console or GUI version of tNavigator.

5.12.1. Split in console version 315

 19.1

5.12.2. Keywords
• FIPPATT (see 12.4.13) defines to which split region each block belongs. When we split
model in graphical interface this keyword is written automatically. When we split via
console version (section 5.12.1) this keyword should be added to the model in advance.

• USEFLUX (see 12.2.41) defines .flux file name which is used in split part. This keyword
is written automatically.

• In tNavigator approach to splitting is different from E1/E3, so the keywords DUMPFLUX

(see 12.2.42), FLUXNUM (see 12.4.18), FLUXREG (see 12.2.43) are ignored.

Features of splitting a model with wells.

5.12.3. 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;
• water injection;
• gas injection;
• water injection under the reservoir conditions;
• gas injection under the reservoir conditions.

2. When the region’s 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.19.86) (ORAT, WRAT, GRAT, LRAT, RESV);

• GCONINJE (see 12.19.95) (RATE, REIN, VREP, FLD);
• GECON (see 12.19.121) (the minimum rate).

5.12.2. Keywords 316

 19.1

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.19.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.13. Reservoir Coupling

tNavigator supports an option Reservoir Coupling to combine calculations of different models.
The following keywords can be used: SLAVES (see 12.19.262), GRUPMAST (see 12.19.263),
GRUPSLAV (see 12.19.264).

Several SLAVEs (subordinate) models are calculated sharing the groups controls and sur-
face network. One principal model – MASTER – controls simulation.

General description:
• SLAVE models are full-featured models in these possible formats: E1, E3, MO, IM, ST,
GE.

• There is fully implicit model calculation. Equations from all models are combined to
one common system of equations that describes the whole integrated reservoir.

• Number of SLAVE models is limited only with the number of available tNavigator
licenses, there are no any other limits on slaves number.

• MASTER model must be in E1 format or E3 (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.

• Restarts in Reservoir Coupling. Dynamic restarts can be used in graphical interface; op-
tions --continue, --restart can be used in console mode; autorestarts. Restart MASTER
and SLAVE models can be used (keyword RESTART, see 12.16.3).
Dates:
• 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.

5.13. Reservoir Coupling 317

 19.1

• To synchronize results it is recommended to have the same DATES in all slaves and the
master within their schedule.

Working with phases and components in inter-model transitions:

• In MASTER model the number of phases shouldn’t be less then this number in each
SLAVE.

• SLAVE models can be 2 or 3 phase. In different models different number of phases can
be used.

• Phase rates in surface conditions, limits, molar rates and their limits don’t change during
transition from one model to another. For example, even if MASTER and SLAVE
models have different PVT tables, then 5sm3 of oil, produced in SLAVE (in surface
conditions in SLAVE model), remain in the MASTER model 5sm3 (but in surface
conditions in MASTER model).

• 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.

• If at least one of SLAVE models is compositional or thermal, then the components with
the same names from different models are considered in MASTER as the same compo-
nent and component production rates for them will be summarized. In not compositional
models we assume 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.

• Let’s consider the case if one component is missing in SLAVE model. This component is
ignored when rate (limit) is recalculated from master group to be used in the associated
slave group. But this doesn’t affect the phase volume (in surface conditions) in which
this component may be included in MASTER model. This volume is not changed during
recalculation for associated slave group, i.e. the part of phase volume (occupied by
missing component) doesn’t disappear.

5.13.1. Master and subordinate groups

Master groups should be set in MASTER model. Subordinate groups are set in SLAVE models
and are connected to master models. All hierarchy from the top and to the level of subordinate
groups in slaves should be set in MASTER model. Subordinate groups correspond to main
groups in MASTER model that don’t have their subordinate groups or wells.

Subordinate models are set via the keyword SLAVES (see 12.19.262). Well group in the
SLAVE model should be the child of the group in MASTER model (keywords GRUPMAST
(see 12.19.263), GRUPSLAV, see 12.19.264).
Then all group limits (that are set in MASTER model) act on groups/wells in SLAVE models

5.13.1. Master and subordinate groups 318

 19.1

using the extended group tree (set via GRUPTREE, see 12.19.100).

tNavigator checks the pairs of principal-subordinate groups, set using the keywords GRUP-
MAST (see 12.19.263) and GRUPSLAV (see 12.19.264). Two options are possible. If in MAS-
TER model we have GRUPMAST (see 12.19.263) for the group G in the model SLAVE1, and
in the model SLAVE1:

• the corresponding GRUPSLAV (see 12.19.264) is not specified, then the group limits
set in SLAVE1 continue to act on group G (option BOTH);

• the corresponding GRUPSLAV (see 12.19.264) is specified, then its parameters 3-9
define if the group limits (specified in SLAVE1) will affect the group G. In particu-
lar if parameters 3-9 are not specified then GCONPROD (see 12.19.86), GCONINJE
(see 12.19.95) 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.19.263).

5.13.2. Surface network

Models can be coupled via common surface network. Standard network option can be used
(keywords GRUPNET (see 12.19.114), GRUPINJE (see 12.19.49), GNETINJE (see 12.19.107)
etc) or extended network (NETWORK, see 12.1.91).
General description:

• In MASTER and SLAVE models standard network (GRUPNET (see 12.19.114),

GRUPINJE (see 12.19.49), GNETINJE, see 12.19.107) and extended network (NET-
WORK, see 12.1.91) 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.19.263), GRUPSLAV (see 12.19.264), and
there are corresponding network nodes with the same names, then they will be connected
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 with fixed pressure.

• The calculation of surface network is done implicitly 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).

5.13.2. Surface network 319

 19.1

5.13.3. Features of the implementation

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.14.9), Gas field operations model DCQ (2.14.8).

• The only link between SLAVE and MASTER models is the extended 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.19.263), GRUPSLAV
(see 12.19.264).

• Wells/groups with the same names can be specified in different SLAVE models, but this
wells/groups will be considered as different.

5.13.3. Features of the implementation 320

 19.1

6. VFP tables generation

Tubing hole pressure is one of the main parameters of well condition control in simulation
of mixture flow in the well bore. Tubing hole pressure value is measured during well’s work.
This parameter 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 correlations, which accounts
different regimes of mixture flow in wellbore.
VFP tables and related properties are specified in tNavigator with the following keywords:

• Specification of VFP tables: VFPPROD (see 12.19.66) for producers, VFPINJ

(see 12.19.65) for injectors.

• Creation of VFP tables via correlations: VFPCORR (see 12.19.71). tNavigator supports
the following correlations:

– Petalas & Aziz correlation;

– Griffith Correlation (based on Hagedorn-Brown);
– Orkiszewski method;
– Beggs & Brill correlation;
– Gray correlation;
– Aziz, Govier and Fogarasi correlation;
– Mukherjee & Brill correlation.

A detailed comparison of correlations is given below.

Using the tNavigator module called VFP Designer, you can prepare a
i project of the well, select the correlations you need, and export the file
containing the keyword VFPCORR (see 12.19.71). For the detailed de-
scription see the VFP Designer User Guide.

• Dimensions of VFP tables for producers and injectors are specified with the keywords
VFPPDIMS (see 12.1.34) and VFPIDIMS (see 12.1.33), correspondingly.

• VFPTABL (see 12.19.69) is the interpolation method for Artificial Lift Quantity.

• VFPCHK (see 12.19.67) affects the checking of VFP tables for internal consistency.

• VFPCHECK (see 12.19.68) orders the checking of VFP tables for consistency with the
given PVT properties.

• WVFPDP (see 12.19.212) is the adjustment to the well BHP obtained by interpolating
the VFP tables.

6. VFP tables generation 321

 19.1

• WVFPEXP (see 12.19.70) specifies optional closing of the well if it is found to be

operating on the stabilized part of its VFP curve.
• WHTEMP (see 12.19.177) specifies the data for tubing head temperature calculations
for producers.

6.1. Single Phase Flow Theory

Liquid in a wellbore suffers pressure loss that can be divided into three components:
• hydrostatic pressure loss;
• pressure loss due to friction;
• kinetic pressure loss.
Kinetic pressure loss is usually very small, so its influence can be ignored. Hence the
equation which expresses total pressure losses can be written as follows:
∆PTotal = α∆PHydro + β ∆PFrictional
where
• α is the correction factor of hydrostatic pressure gradient ∆PHydro ;
• β is the correction factor of pressure gradient caused by friction ∆PFrictional .

6.1.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 (METRIC: Bara, FIELD: psia);
• f – Fanning friction factor (a function of Reynolds number);
• ρ – density (METRIC: kg/m3 , FIELD: lb/ f t 3 );
• v – average velocity (METRIC: m/s, FIELD: ft/s);
• L – length of pipe section (METRIC: m, FIELD: ft);
• gc – gravitational constant (METRIC: 9.81 m/s2 , FIELD: 32.2 f t/s2 );
• D – inside diameter of pipe (METRIC: m, FIELD: ft).
This correlation can be used either for single-phase gas (Fanning Gas) or for single-phase
liquid (Fanning Liquid).

6.1. Single Phase Flow Theory 322

 19.1

6.1.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.0 log 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 – Reynold’s number.
The single-phase friction factor clearly depends on the Reynold’s number, which is a
function of the fluid density, viscosity, velocity and pipe diameter:
1488ρvD
Re = ,
µ
where:
• ρ – density (lb/ft 3 );

• v – velocity (ft/s);

• D – diameter (ft);

• µ – viscosity (cP).

6.1.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.1.2. Single-Phase Friction Factor (f) 323

 19.1

6.2. 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.2.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
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, METRIC: sm 3 /sm 3 , FIELD:
stb/Mscf);

• R – pipe radius.

6.2. Multiphase Flow Theory 324

 19.1

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.

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.

6.2.1. Nomenclature 325

 19.1

Liquid density and viscosity

To calculate liquid density (ρL ) and viscosity (µL ) we will apply the following formulae:
ρ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 fractions.

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 ).

6.2.1. Nomenclature 326

 19.1

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 ),

where:

• 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 dimen-
sionless 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:

6.2.1. Nomenclature 327

 19.1

• σ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 re-
duced. 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

σ = CσT

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.2.1. Nomenclature 328

 19.1

6.2.2. Griffith Correlation

This type of correlation is a modification to the Hagedorn and Brown Correlation [14]. We
have:

• PT H – tubing hole pressure;

j
• QP – phase P volume rate at surface conditions (P = 1, . . . , nP );
j
• BP – phase P volume fraction;

• µ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 fraction.

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.2.2. Griffith Correlation 329

 19.1

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 g sin Θ
∆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:
1488ρL vL D
ReL = .
µL
It is suggested, if Re < Re1 = 2000 then there is a Poiseuille’s 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 Fanning’s 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.2.2. Griffith Correlation 330

 19.1

6.2.3. Petalas & Aziz correlation

The Petalas and Aziz correlation [17] is capable of handling flow in all directions: horizontal,
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 determined.
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 cal-
culation 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. Let’s suggest that gas in the upper section of pipe, and liquid is in the lower
one.

6.2.3. Petalas & Aziz correlation 331

 19.1

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. Let’s 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

6.2.3. Petalas & Aziz correlation 332

 19.1

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 α
h̃L = = cos2 .
D 4
The following is necessary to multi-phase flow to exist:
s
(ρL − ρG )gAG cos Θ
vG ≤ (1 − h̃L ) ;
ρG dA L
dhL

(if cos Θ ≤ 0.02, cos Θ = 0.02 here)

s
gD(1 − h̃L ) cos Θ
vL ≤ .
fL

To distinguish between stratified smooth and stratified wavy flow regimes: stratified smooth
flow exists if: s
4µL (ρL − ρG )g cos Θ
vG ≤ ;
sρL ρG vL
vL
Fr = √ ≤ 1.4.
ghL
Otherwise multi-phase flow is implemented.

6.2.3. Petalas & Aziz correlation 333

 19.1

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 thickness:

δ̃L = δL /D.

Let’s 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 − 2δ̃L )2 ;
4

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

6.2.3. Petalas & Aziz correlation 334

 19.1

1
k= − 1.
(2δ̃L − 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
= (2δ̃L − 1) − 1 = 1 − (2δ̃L − 1)2 ;
(2δ̃L − 1)2

Af
Ef = = 4δ̃L (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 4δ̃L (1 − δ̃L )

A (vsG + vsL FE)

vc = (vsG + vsL FE) = .
Ac (1 − 2δ̃L )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 = 4δ̃L (1 − δ̃L )D.

Friction factor fc is calculated using standard formulae of pipe roughness and the following
Reynolds number definition:
Dc ρc vc
Rec = ;
µc
Dc = D(1 − 2δ̃L );
µc = Ec µL + (1 − Ec )µG ;
ρc = Ec ρL + (1 − Ec )ρG ;
vsL FE
Ec = .
vsG + vsL FE

6.2.3. Petalas & Aziz correlation 335

 19.1

In order to solve these equations, two additional quantities need to be determined: the interfa-
cial 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 − 2δ̃L )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 ;
gρL2
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.

6.2.3. Petalas & Aziz correlation 336

 19.1

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

g(ρL − ρG )σ 1/4
 
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
ELs vt + vGdb (1 − ELs ) − vsG
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:
−0.031
C0 = (1.64 + 0.12 sin Θ)RemL .
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∞ ,

6.2.3. Petalas & Aziz correlation 337

 19.1

√
where fm = 0.316 Re∞ for fm < 1, otherwise fm = 1, and
ρL vd∞ D
Re∞ = .
2µL

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.278−1.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.

6.2.3. Petalas & Aziz correlation 338

 19.1

Dispersed Bubble Flow Let’s 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:
−0.031
C0 = (1.64 + 0.12 sin Θ)RemL ,
ρ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 – liquid holdup) 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 momentum
balance equations:
g
∆PH = ρL ∆h sin Θ;
gc
g
∆PH = ρG ∆h sin Θ.
gc

6.2.3. Petalas & Aziz correlation 339

 19.1

Annular-mist Flow Liquid volume fraction (EL – liquid holdup) is determined using
geometric considerations and a known liquid thickness, by the following equation:
vcG
EL = 1 − (1 − 2σ˜L )2 .
vsG + FEvsL
The ∆PH is then calculated from the hydrostatic portion of the gas and liquid phase momentum
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 .
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

Intermittent Flow Liquid volume fraction (EL ) is given by:

ELs vt + vGdb (1 − ELs ) − vsG
EL = .
vt
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

6.2.3. Petalas & Aziz correlation 340

 19.1

Friction Pressure Loss The frictional portion of the overall pressure gradient is deter-
mined based on pipe geometry 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 sum-
marized 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 :
Dρm 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:
DρL vm
RemL = .
µL
Now, the expression for the pressure loss due to friction is:
2 fmL v2m ρm
∆PF = .
gc D

6.2.3. Petalas & Aziz correlation 341

 19.1

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 re-
gion, 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.75−EL )
η = 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
 
The frictional pressure gradient for the annular-mist flow portion, ddLp , 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 4τwL
= .
dL f rAM D

When the calculated film height δ̃L is less than 1 × 10−4 , the frictional pressure gradient for
the annular-mist flow portion, is obtained from:
2 fm v2m ρm
 
dp
= .
dL f rAM gc D

6.2.4. Beggs & Brill correlation

The Beggs and Brill multiphase correlation [15] 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.

6.2.4. Beggs & Brill correlation 342

 19.1

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 CL−2.4684

L3∗ = 0.1 CL−1.4516
L4∗ = 0.5 CL−6.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∗

Intermittent flow If

0.01 ≤ CL < 0.4 and L3∗ < Frm ≤ L1∗

or
CL ≥ 0.4 and L3∗ < Frm < L4∗

6.2.4. Beggs & Brill correlation 343

 19.1

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∗
Hydrostatic Pressure Difference
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

6.2.4. Beggs & Brill correlation 344

 19.1

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 = 1 − A
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:

6.2.4. Beggs & Brill correlation 345

 19.1

ALL flow types

0.011 N 0.1244
 
β = (1 −CL ) ln 0.3692 vL0.5056
CL Frm

! β must always be ≥ 0. Therefore, if a negative value is calculated for β , it is

set to 0 instead.
Once the liquid holdup (EL (Θ)) is calculated, it is used to calculate the mixture den-
sity (ρ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 g∆z
∆PH =
144gc
Friction Pressure Loss
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.2.5. Beggs & Brill revised correlation

The revised version of the Beggs & Brill correlation is taken into account pipe roughness and
improves liquid–holdup values by introducing correction factors proposed by Payne [33].

6.2.5. Beggs & Brill revised correlation 346

 19.1

In [33] it was shown that the Beggs & Brill method underpredict friction factors since the
method is based on data obtained in a smooth pipe. For turbulent fluid flow in rough pipes
the friction factor is calculated using the Colebrook–White (CW) equation, which is implicit
in the friction factor f :  
1 ε/D 2.51
√ = −2 log10 + √
f 3.7 Re f
where ε is roughness of the pipe, D is the pipe diameter, Re is the Reynolds number. In [34]
an alternate form of the CW equation was proposed, which is valid over the wide range of
ε/D and Re values and allows accurately estimate f since no iterative solution techniques
are necessary. Above mentioned equation can be rewritten as:
 u
u = − ln b +
d
where

• u= 1
√
a f

• a= 2
ln(10)

• b= ε/D
3.7

• c= 2.51
Re

• d= 1
ac = Re ln(10)
5.02

An alternate mathematically exact representation of the CW equation can be written as

[34]:  
d
u = ln +δ
q
or    
1 d
√ = a ln +δ
f q
where

• s = bd + ln(d)

• q = ss/(s+1)

δ satisfies the implicit equation:

 
δ
δ + ln 1 + =z
g

where
 
q
• z = ln g

6.2.5. Beggs & Brill revised correlation 347

 19.1

 
• g = bd + ln d
q

The solution for δ can be obtained using linear approximation of the logarithmic term:
 
g
δLA = z
g+1

which results in error on the order of (δ /g)2 . A much more accurate solution can be obtained
using continued–fractions approximations (CFA) of the logarithmic term resulting in error on
the oder of (δ /g)4 :  
z/2
δCFA = δLA 1 +
(g + 1)2 + (z/3)(2g − 1)
Moreover, in [33] it was shown that the Beggs & Brill method overpredict liquid holdup
in both uphill and downhill flow. To improve a prediction the following correction factors
should be used:
EL(θ ) = 0.924EL(θ ) f or θ > 0
and
EL(θ ) = 0.685EL(θ ) f or θ <0
where θ is an inclination angle. However, the resulting liquid holdup for θ > 0 should not
be less than CL .

6.2.6. Orkiszewski method

Orkiszewski [13] distinguished four types of flow patterns:

• Bubble Flow;

• Slug Flow;

• 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

6.2.6. Orkiszewski method 348

 19.1

• 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 :
1488ρL DvsL
Re = .
µL EL
Pressure loss due to friction is calculated as:
 2
vsL
f ρL EL
∆PF = .
2gc D

6.2.6. Orkiszewski method 349

 19.1

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:
1488ρL vs D
ReS = ;
µL
1488ρL 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 (6.1 – 6.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 ∗ 10−6 ReL ) gD
p
(6.1)
If ReS ≥ 8000:
vs = (0.35 + 8.74 ∗ 10−6 ReL ) gD
p
(6.2)
If 3000 < ReS < 8000:
s !
13.59µL
vs = 0.5 ψ + ψ2 + √ (6.3)
ρL D

ψ = (0.251 + 8.74 ∗ 10−6 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 ln vm + 0.113 ln D.
D1.415

6.2.6. Orkiszewski method 350

 19.1

If vm ≥ 10:
ln(µL + 1)
δ = 0.0274 + 0.161 + 0.5699 ln D + X;
D1.371
where  
ln(µL + 1)
X = − ln vm 0.01 + 0.397 + 0.63 ln D .
D1.571
Continuous liquid phase-oil:
If vm < 10:
ln µL
δ = 0.013 1.38 − 0.681 + 0.232 ln vm − 0.428 ln D.
D
If vm ≥ 10:
ln µL
δ = 0.045 0.799 − 0.709 − 0.162 ln vm − 0.888 ln D.
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 interpola-
tion between limits of bubble flow and mist flow regimes. Pressure gradient in transition flow
is given by:
∆P = M∆slug + (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

6.2.6. Orkiszewski method 351

 19.1

Pressure loss due to friction is given by:

f ρG v2sG
∆PF = .
2gc D
Friction factor f is determined using Reynolds number:
1488ρG vsG D
Re = .
µG

6.2.7. Gray correlation

Although Gray correlation was developed for vertical flow [18], 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.
Hydrostatic Pressure Difference
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
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

6.2.7. Gray correlation 352

 19.1

Friction Pressure Loss

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 × 10−5 .
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.2.8. Aziz, Govier and Fogarasi correlation

Aziz, Govier and Fogarasi [12] (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).

6.2.8. Aziz, Govier and Fogarasi correlation 353

 19.1

The flow regimes are identified with the following variables:

 ρ 1/3  72 ρ 1/4
G L
NX = vsG ;
0.0764 62.4 σL

72 ρL 1/4
 
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.

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:

6.2.8. Aziz, Govier and Fogarasi correlation 354

 19.1

Pressure calculation due to flow regime

Bubble Flow The liquid holdup (EL ) defined as:
vsG
EL = 1 − ,
vBF
where:
vBF = 1.2vm + vBS ;
σL g(ρL − ρG ) 1/4
 
vBS = 1.41 .
ρL2
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:
g
∆PH = ρm sin Θ.
gc
The friction factor is obtained from standard methods using pipe roughness and Reynolds
number, Rem :
ρL Dvm
Re = .
µL
The expression for the pressure loss due to friction is:

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:
 1/2
gD(ρL − ρG )
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;

6.2.8. Aziz, Govier and Fogarasi correlation 355

 19.1

• if 18 < NV < 250, then m = 69NV−0.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
The expression for the pressure loss due to friction is:
f ρL EL v2m
∆PF = .
2gc D

Transition Flow The transition flow region is, as the name indicates, a region of tran-
sition 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 Reynold’s number of the gas:
1488ρG 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

6.2.8. Aziz, Govier and Fogarasi correlation 356

 19.1

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.0749σL
=
D ρG v2sG D
if NW E Nµ > 0.005
ε 0.3713σL
= (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.2.9. Mukherjee & Brill correlation

To calculate pressure change via Mukherjee & Brill correlation [16] it is necessary to deter-
mine flow pattern at first, and then to calculate pressure change by formulae for according
regime.
Flow-Pattern prediction
The following procedure to determine flow regime is used:
The bubble-slug transition equation for upflow (NLvBS ). Let’s 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.401−2.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.321−0.017NGv −4.267 sin Θ−2.972NL −0.033(log NGv ) .
The following scheme is used to determine flow pattern:

6.2.9. Mukherjee & Brill correlation 357

 19.1

Estimation for liquid volume fraction

The liquid holdup (EL – liquid holdup) data were correlated with an equation of the form:
 c5 
2 2 NGv
EL = exp (c1 + c2 sin Θ + c3 sin Θ + c4 NL ) 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 g
2D + ρm gc sin Θ
∆P =
1 − Ek

6.2.9. Mukherjee & Brill correlation 358

 19.1

where
ρm vm vsG
Ek =
p
The friction factor, f , is obtained from standard methods using pipe roughness and Reynolds
number, Re:
1488ρNS 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
Let’s define some geometrical parameters:
2hL
δ = 2 cos−1 (1 − );
D
s  2
hL hL
Wi = 2D − ;
D D
1
EL = (δ − sin δ ).
2π

6.2.9. Mukherjee & Brill correlation 359

 19.1

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 Reynold’s 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

6.2.9. Mukherjee & Brill correlation 360

 19.1

7. FAQ
In this section we have the overview of interesting questions:

• Various questions – 7.1.

• Reasons for the difference in calculation results – 7.2.

• What is the "right" answer in hydrodynamic simulation – 7.3.

• How to speedup model calculation without its simplification – 7.4.

7.1. Various questions

7.1.1. What does the message mean "Warning: BOM ignored"
BOM – Byte Order Mark – this is a pair of additional non-text characters that is added to the
beginning of the file without the user’s knowledge by some text editors. The BOM affects on
interpretation of double-byte character encodings of not Latin code tables. BOM doesn’t affect
the keywords and their parameters because they are written in the Latin alphabet. Model cal-
culaton is not affected as well. This warning means that BOM has been detected and ignored.
Without the support of such functionality first keyword in the file would be corrupted and not
recognized.

7.1.2. What minimum amount of memory is required for model’s calculation

The required amount of memory is proportional to the number of model’s active grid blocks.
For three-phase black oil model 3 Kb of memory are required for each active grid block;
for 2-phase case 2 Kb are required for each grid block. Compositional and thermal models
require about as many Kb per grid block as there are components in the model (including
water and its components, as well as solid components).
Memory requirements may be further enhanced by the use of additional grid properties that
specify the scaling of relative permeability end points, alkaline/surfactant/polymer injection,
presence of tracers, temperature option in black oil and compositional models, hysteresis of
relative permeabilities, rock compaction, non-equilibrium phase transitions, and other options
that make use of the saved grid propetries from the step before.
If the percentage of active blocks is small, then model loading may require more memory
than its calculation.

7.1.3. What causes the warnings of negative compressibility and/or viscosity

PVT tables should cover completely the pressure range reached in all blocks of the model
during initialization and calculation. If the pressure gets outside of the covered range, the sim-
ulator will have to resort to extrapolation over the nearest available points. This can produce
physically impossible values of certain parameters.

7. FAQ 361
 19.1

When reading PVT tables, the simulator calculates compressibility of oil, gas and gas-oil
mixture for the parameters specified in the tables (pressure, volume coefficients, gas saturation,
etc). Afterwards it checks for negative values of the compressibilities. The checks are run, for
example, in the range of the maximum Pbub from PVTO (see 12.5.4) and the maximum
pressure from PVDG (see 12.5.7), taking into account the intermediate values. It may so
happen that the maximum pressure in the gas table is much higher than the Pbub in the oil
table. Then the extrapolated values of Bo and Rs will be used to calculate the compressibility
of the oil:  
1 dBo dRs
C0 = − + · BG
Bo dp dp
The result may turn out negative. In this case a warning will be issued:
Warning: negative oil compressibility! In range of pressure <...> and <...> for saturated
line in region <number>.

For similar reasons, negative viscosity may be encountered during calculations:

At <calculation step> extrapolation of <PVDG|PVTG|...> table was the cause of the neg-
ative value of gas viscosity in <amount> blocks, it has been reset to small value.

In both cases, the simulator will substitute near-zero positive values (1e-12) instead of
negative, which nominally allows to continue the calculation. However, at this point the model
becomes physically unrealistic. Hence it is recommended to stop the calculations and revise
the PVT tables for the regions of interest.

7.1.3. What causes the warnings of negative compressibility and/or viscosity 362
 19.1

7.2. 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.3.
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 doesn’t 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.19.74), GECON (see 12.19.121);

• keywords ACTION (see 12.19.158), ACTIONG (see 12.19.159), ACTIONR (see 12.19.160),
ACTIONW (see 12.19.161), ACTIONX (see 12.19.162);

• well control mode is THP and VFP table number can change in case if user-defined
ACTION condition takes place;

• keywords UDQ (see 12.19.165).

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.
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.

7.2. Reasons for the difference in calculation results 363

 19.1

If the keywords (that are listed above) trigger at different times, then it can lead to the situation
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.19.74), 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.19.140). 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).
• (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 shouldn’t call one
number a correct solution. A solution is a set of solutions.

7.2. Reasons for the difference in calculation results 364

 19.1

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 don’t 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.19.134) 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 calcu-
lation time may significantly increase due to increase of the number of steps.

7.2. Reasons for the difference in calculation results 365

 19.1

7.3. ”The correct answer” in dynamic modelling

In this section we’ll 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.3.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 equa-

tions with non-symmetric matrix → calculating preconditioner on each linear system
solution iteration

Parameters which influence calculation

• Time step – there may be limits on min and max step, and parameters controlling
automatic step choice.

• Non-linear problem solution parameters – accuracy, minimal and maximal Newton iter-
ations number.

7.3. ”The correct answer” in dynamic modelling 366

 19.1

• 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.3.1. Problem discretization and solution 367

 19.1

Figure 35. Work is distributed evenly between all cores

7.3.2. Influence of the number of cores

Parallel calculation

With parallel calculation, the work is distributed evenly between all cores – picture 35.

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. It’s 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) = ∑ ∑ ai bi
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
10−16 , characterising density of real numbers near 1. If we know it, we can calculate differ-
ence between two numbers at any point. For example, 1016 + 1 is equal to 1016 .

7.3.2. Influence of the number of cores 368

 19.1

Figure 36. Different answers.

Solution calculation

So, for different number of cores we’ll 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 36.
This uncertainty interval due to calculation is much smaller than the uncertainty due to
initial data.

7.3.3. Influence of timestep

Calculation and reporting steps

7.3.3. Influence of timestep 369

 19.1

Figure 37. 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 37.
The well rate on a reporting step is rate on step 3 (picture 37). 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.

7.3.3. Influence of timestep 370

 19.1

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.19.74)

Typical case: well water cut or Gas-oil ratio is checked and the well is closed (WECON,
see 12.19.74). Here two uncertainties influence:

• Current value of parameter is used;

• It’s 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 former case
the well is closed, in the latter it may work for one more year (calculation step) and produce
100 m3 of oil, that is, 30% of its yearly production on the 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.

7.3.3. Influence of timestep 371

 19.1

• Use WTEST (see 12.19.183), designed to reduce uncertainty influence on global model
(well closure). The WTEST (see 12.19.183) may reopen the well. Also, it’s checked on
calculation time steps so it’s subject to uncertainty too.

Compensation – WCONINJP (see 12.19.46)

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.19.86)

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.19.162).

ACTIONX (see 12.19.162) 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.3.3. Influence of timestep 372

 19.1

7.3.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 36.

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.3.4. What can we do? 373

 19.1

7.4. 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.4.1. Problem statement

How to calculate THIS (picture 38) fast?
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
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 ver-
tical 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 an everlasting problem, usually a reservoir engineer
can’t help it;

• quality of the model – how to do your work perfectly using existing data.

Let’s analyze the possible improvements of model quality.

7.4. How to speed-up model calculation without its simplification 374

 19.1

Figure 38. Model with large amount of LGRs

7.4.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
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 in the
block.
The presence of blocks with small pore volume doesn’t slow down calculation. The big
variation in pore volumes slows down calculation - picture 39. If during the time step the
volume of the fluid that is passing through the grid block is significantly larger than its vol-
ume, then the time step will be reduced, calculation will be slower.

How to deal with this problem:

7.4.2. Flow through the block 375

 19.1

Figure 39. Blocks with different pore volumes

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 40. 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.
Fluid-in-place in blocks with small pore volume.
How to calculate fluid-in-place in these blocks – picture 41. Go to map Fluid-in-place.
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-in-place in these blocks.
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.4.2. Flow through the block 376

 19.1

Figure 40. Cut for blocks with small pore volumes

7.4.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 42.
User Maps. Map. Right mouse click on the Map to open Model Editing. Choose the tab
Connected Components, Show all 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 should be excluded, we assign value 0 to the 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.80).

7.4.3. Grid connection 377

 19.1

Figure 41. Fluid-in-place in the blocks with small pore volume

7.4.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 block’s connections to neigh-
bouring blocks. Now we consider only the “holes”, arising from pore volume cut-off – picture
43.
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.58).

PINCH
/

Lateral links through the blocks with zero permeability.

Look at the picture 44. 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.
This problem can be solved using lateral links through the blocks with zero permeability
via the keyword PERMAVE (see 12.2.37). In this case averaged permeability will be used in

7.4.4. Grid stratification factor 378

 19.1

Figure 42. Marking out connected components

Figure 43

transmissibility calculation.

Picture – 44. The usage of averaged permeability in transmissibility calculation will help

7.4.4. Grid stratification factor 379

 19.1

Figure 44. The permeability of the neighboring blocks

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, which 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.4.5. Influence of smoothness of the data

On the pictures 45 and 46 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.
With a large jump on the curve the value of the derivative of this parameter will be very
large as well, which 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.
The resulting system of equations (after approximation) is a non-linear system of algebraic
equations of the form

F(p, N1 , . . . Nnc ) = 0

7.4.5. Influence of smoothness of the data 380

 19.1

Figure 45. Jump on the capillary pressure curve

Figure 46. Jump on RP curves

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):

∂ F(U m ) −1
 
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 Newton’s 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 45, 46);

7.4.5. Influence of smoothness of the data 381

 19.1

• A large number of points of discontinuity of the derivatives (picture 47).

Let’s discuss where a large number of points of discontinuity of the derivatives comes
from.
On the picture 47 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 be-
tween them. Each interval between two points has its own function. So, the derivative has a
large number of points of discontinuity.

Figure 47. Convert RP in Corey correlation

Figure 48. Smooth RP curves

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
(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 48.

7.4.5. Influence of smoothness of the data 382

 19.1

Available tables SWOF (see 12.6.1), SGOF (see 12.6.2) etc. can be converted to Corey or
LET correlation – picture 47.
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.4.6. Influence of end points match

RP end points for drainage and imbibition process (hysteresis) must be the same. Please pay
attention to the following messages during model loading – picture 49:

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 49. Unmatched end points in hysteresis

7.4.6. Influence of end points match 383

 19.1

7.4.7. Conservation equation

It is unacceptable to have blocks in different PVT (EOS) regions with a hydrodynamic con-
nection – picture 50.

Figure 50. 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 conserva-
tion 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.4.7. Conservation equation 384

 19.1

7.4.8. VFP tables

Non-monotonic VFP tables (picture 51) 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 51, it turns out
that 2 different THP values correspond to one value of BHP, which can lead to the instability
in calculation.

Figure 51. Non-monotonic VFP tables

Please pay attention on the corresponding messages during model loading, and edit VFP
tables if necessary.

7.4.8. VFP tables 385

 19.1

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]...

Useful commands in cmd:

• cd <path> – change directory

• cd .. – go to upper directory

• dir – list all files in the current directory

• Arrow up /down – previous or next command

• Tab – continue the name of the file from the current folder.

To see help, use the command line options described in 8.1.1. Help.

8.1. Command line options

Usage: tNavigator-con.exe [OPTIONS]... [FILES]...

i All command line options are applicable to GUI version as well.

8.1.1. Help

OPTION Description
-h, --help Print help and exit
--full-help Print help, including hidden options, and exit
-v, --version Print version and exit

8. tNavigator console version 386


8.1.2. Input data
OPTION
-c, --continue
--restart=<number>
--input=<option>
--physics=<option>
--fast-array-reader=<option>
--nousersch
--source-dir=<string>
--dest-dir=<string>
--base-dest-dir=<string>
8.1.2. Input data
19.1
Description
Continues calculation from last calculated step.
Default: off.
Continues calculation from input step or last
calculated step if input step is not calculated.
Default: off.
Input data file format. Possible values: e1, e3,
im, ge, st, mo. Deduced automatically from the
model if not set.
Default: e1.
Physical model type. Possible values: blackoil,
compositional, thermal, auto (in the latter case
deduced automatically). Overridden if --input
is set.
Default: auto.
Use fast array reader (experimental)=on.
Default: off.
Do not read user schedule.
Default: off.
Prefix for models directory.
Prefix for results directory.
Prefix for base results directory.
387
 19.1

8.1.3. Client-server options

OPTION Description
--server-url=<string> License server URL.
--license-type=<option> 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=<number> Time limit (in seconds) to wait for network li-
cense.
Default: 0.
--license-settings Specifies the connection file to connect to the
license server with the following contents:
[tNavigator_license_settings]
url=<server_URL>
login=<login>
pass=<password>
--reggen Generate the registration file and quit

8.1.4. Simulation process

OPTION
--nosim
--stream-flux=DOUBLE
--stream-flight=<number>
--stop-step=<number>
--use-gpu
--allow-autorestart=<option>
--max-calc-time=<number>
Description
Parse and check only. Don’t start simulation.
Default: off.
Streamlines density (rate per one streamline).
Default: 5.
Streamlines max flight time.
Default: 50000.
Stop the calculation on specified step.
Default: -1 (don’t stop).
Use GPU acceleration
Allows automatic restart of calculation in case
of convergence failure. Possible values: yes,
no.
Default: yes.
Time limit (in minutes) to stop simulation if
reached.

8.1.3. Client-server options 388

 19.1

8.1.5. Parallel computation

OPTION Description
-n, --cpu-num=<number> Number of computational threads.
Default: number of available CPUs.
--memory-bind-logic=<option> NUMA bind logic. Possible values: off, init,
full.
Default: full.
--sync-method=<option> Synchronization method. Possible values: mu-
tex, barrier.
Default: barrier.
--mppn=<number> Number of MPI processes running simultane-
ously on each node.
Default: 1.

8.1.6. Group: thread to CPU bind logic model

OPTION
--thread-bind-logic=<option>
--thread-bind-to-cpu=<CPU ID
<CPU ID 2>,..., <CPU ID N>
Description
Thread bind logic. Possible values:
none, node_uniform, cpu_uniform, pro-
cess_to_first_cpus.
Default: node_uniform.
1>, Where (id of logical CPU) to bind each thread
(N – number of threads). CPU numbering starts
from 0.

8.1.7. Debug

OPTION Description
--drainage-matrix Compute and dump drainage matrix.
Default: off.
--time-detailed=<option> Display detailed information about CPU usage
time. Possible values: off, total (for all pro-
cesses at the end of calculations), all (for all
processes at each time step).
Default: off.

8.1.8. Result files

8.1.5. Parallel computation 389

 19.1

OPTION Description
--no-dump-res Don’t dump result files.
Default: off.
--dump-res Dump res files. Can be used with option --ecl-
dump.
Default: off.
--dump-res-last Dump the last computed step, so that a crashed
calculation could be resumed smoothly after-
wards.
Default: off.
--summary-only Print to log file only summary information.
Default: off.
--dump-result-files=<option> Modify set of result files to dump. Possible
values: all_on, all_off, mesh_on, mesh_off, ini-
tial_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.
--dump-graphs-ts=<option> Set timestep mask for writing graphs. Possible
values: all, monthly, annually, first_and_2last.
Default: all.
--dump-maps-ts=<option> Set timestep mask for writing maps. Possible
values: all, monthly, annually, first_and_2last.
Default: all.
--dump-computed-wells-intersections Dump COMPDAT (see 12.19.6), COMPORD
(see 12.19.31) and WELSPECS (see 12.19.3)
converted from WELLTRACK in MO models.
--ignore-lock Compute model even if a *.lock file exists (that
is, the model is currently being calculated by
another instance of tNavigator).
Default: off.
--use-rptrst-map-freq Use information about output results map fre-
quency from keyword RPTRST (see 12.16.5)
Default: off.
--ecl-rsm RSM file export for E1/E3 models

8.1.8. Result files 390

 19.1

OPTION Description
--touch-before=<extension 1>, Create empty files with specified extensions
<extension 2>,... before model computation.
--touch-after=<extension 1>, Create empty files with specified extensions af-
<extension 2>,... ter model computation.
--log-lang=<option> Log file language. Possible values: eng, rus.
Default: eng.
--no-restart Don’t dump maps needed for restart.
Default: off.

8.1.9. Boundary conditions

OPTION Description
--bc-dont-correct Don’t correct boundary conditions if they seem
to be wrong.
Default: off.
--bc-dump-on-comp-steps Record boundary conditions on every compu-
tational step.
Default: off.

8.1.10. UNRST/UNSMRY compatibility output

When binary files are dumped calculation data is saved at calculation time steps. This option
is used by default and can be turned off using the keyword RPTONLY (see 12.18.2) in SUM-
MARY section (then results will be saved at reporting time steps).

The keyword RPTONLYO (see 12.18.3), defined in the SUMMARY section or SCHED-
ULE section, demands that calculated results be saved at each time step. If RPTONLYO
(see 12.18.3) is defined in the SCHEDULE section, then the results output setting can be
changed during a calculation.

OPTION Description
-p, --ecl-include-path Use include path like in E1/E3 formats. If en-
abled, relative paths are interpreted as starting
at the base file, otherwise at the current file.
Default: on.

8.1.9. Boundary conditions 391

 19.1

OPTION Description
--ecl-root Dump binary files to model directory.
Default: off., files are dumped in RESULTS
folder
-l, --ecl-little Switch UNRST/UNSMRY 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.
Default: off.
-m, --ecl-smspec Dump result binary SMSPEC file.
Default: off.
--rfd-summary Dump short (FIELD only) SMSPEC and UN-
SMRY files.
Default: off.
--ecl-upscaled-dump-xyz=<X-scale, Y- Dump UNRST/UNSMRY binary files upscaled
scale, Z-scale> along X, Y, Z directions.
Default: off.
--ecl-sln Dump streamlines data in SLNSPEC,
SLNxxxx files.
Default: off.
--convert-ecl-bin-to-text Convert input UNRST/UNSMRY binary file to
text file.
Default: off.

8.1.10. UNRST/UNSMRY compatibility output 392

 19.1

8.1.11. MO options

OPTION Description
--dump-converter-maps Use disk space to prevent the memory peak.
Default: off.
--dump-intermediate-model Save intermediate model to data files.
Default: off.
--not-dump-intermediate-maps Don’t save maps in intermediate model to data
files.
Default: off.
--dump-intermediate-sch Save intermediate SCHEDULE section to file.
Default: off.
--multiple-error-messages Don’t hide multiple messages on conversion.
Default: off.

!
8.1.12. GUI

Options of this group are only applicable for the GUI version of tNavigator.

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 Don’t use OpenGL (no graphs and maps at all).
Default: off.
--no-gl-vbo Don’t use OpenGL VBO.
Default: off.
--no-gui Do not show GUI, just calculate the specified
models.
Default: off.
--view-graphs View graphs only, without loading mesh.
Default: off.

8.1.11. MO options 393

 19.1

8.1.13. Remote GUI

OPTION Description
--dispatcher-ip=<string> Dispatcher IP
--dispatcher-task-port=<number> Dispatcher port for tasks.
Default: 0.

8.1.14. Model save

OPTION
--save-model=<string>
--save-scaled-model-xyz=<X-scale, Y-
scale, Z-scale>
--split=<path to save the patterns to>
Description
Save model in tN format (path and file name
are taken from the parameter string)
Save model scaled by X, Y, Z directions
Auto split input models. The pattern is set with
FIPPATT (see 12.4.13) region.
Default: do not split.

8.1.13. Remote GUI 394

 19.1

9. Data files
tNavigator may be started either directly (version with graphical user interface), or from com-
mand 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 argu-
ment. 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).

The keyword INCLUDE (see 12.1.80) allows to include directory to the .data file files
in the archive .gz. Only one file may be inside one archive. The size limitation for file
in Windows is 2Gb. Several archives may be included via several keywords INCLUDE
(see 12.1.80).

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 via graphical interface:

• Load Well Data (trajectories, groups, events, history, RFT (MDT), PLT). Use the menu
Document. Load Well Data to load files. The formats are described in the section 10
of tNavigator User Guide.

• Export grid properties – section 6.10 of tNavigator User Guide.

9.1. Results of tNavigator calculation

It is recommended to limit the recording to certain user-specified time steps so as to save the
disk space. The time steps for recording grid properties and graphs in tNavigator format are
determined as follows:

• As specified by the keywords RPTRSTD (see 12.16.61), RPTRSTT (see 12.16.62), RP-
TRSTL (see 12.16.63), if these are present in the model.

• If they are absent, then as specified by the keywords RPTMAPD (see 12.16.64),
RPTMAPT (see 12.16.65), RPTMAPL (see 12.16.66) (for grid properties) and RPT-
GRAPHD (see 12.16.64), RPTGRAPHT (see 12.16.65), RPTGRAPHL (see 12.16.66)
(for graphs), if these are present in the model.

• If they are absent too, then grid properties are recorded when specified by the RPTRST
(see 12.16.5) keyword, and all graphs are saved at each step.

9. Data files 395

 19.1

• If none of the above keywords is mentioned in the model, then the default behavior for
grid properties is as follows:

– For E1/E3 models: grid properties are recorded only for the first and last step.
– For IM/GE/ST models: grid properties are recorded for all steps.

All graphs are saved at each step.

Whenever grid properties in tNavigator format are saved, all of them are saved together,
regardless of the mnemonics specified by RPTRST (see 12.16.5). Likewise, all graphs are also
saved together, regardless of SUMMARY (see 12.18.1).
The time steps when grid properties are saved are also the time steps when the restart is
possible (see RESTART, see 12.16.3).
There is a command line option --use-rptrst-map-freq (see 8.1.8. Result files)
which gives RPTRST (see 12.16.5) higher priority than other keywords in determining the
time steps for writing results.
Besides keywords, the options of data recording may be set up in GUI via the Wizard
for selective writing of results (Document → Reload With New Recording Options). The
selected options are displayed in the list of model time steps (see Run model).
Results of tNavigator calculation can be saved in the following formats:
tNavigator format files that are saved in the RESULTS folder
• <name>.log is a text file with report on simulation process. The detailed description
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.
It’s better to use modes ViewResults/ViewGraphs when you are not going to calculate
the model;

• <name>.log.old is a saved copy of a .log file with results of previous model opening.
This file is created when the model is opened for the second time;

• <name>.err is a text file with report on all errors in input data and during simulation;

• <name>.end is a text file with number of errors, problems, warnings in the model;

• <name>_*.res are 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.16.3).

• <name>.sdata is a 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.
In these modes you can’t change results: i.e., for example, they can not be deleted or
rewritten;

9.1. Results of tNavigator calculation 396

 19.1

• <name>.lock 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, it’s 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.

!
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.

Binary file in E1 format (*.UNSMRY, *.SMSPEC, *.EGRID, *.INIT, *.RSSPEC,

*.UNRST)
Graphs for saving in this format are chosen using the keyword SUMMARY (see 12.18.1)
and its mnemonics. File format is controlled via the keywords MULTOUT (see 12.1.16), UNI-
FOUT (see 12.1.14), MULTOUTS (see 12.1.17), UNIFOUTS (see 12.1.15).
Grid properties for saving in UNRST/UNSMRY format are chosen using the keyword
RPTRST (see 12.16.5) and its mnemonics. The keyword INIT (see 12.2.118) should be set to
dump initial properties to *.INIT file.
Time steps for recording the grid properties and graphs in UNRST/UNSMRY format are
determined as follows:

• In case of presence of the keywords RPTRSTD (see 12.16.61), RPTRSTT (see 12.16.62),
RPTRSTL (see 12.16.63), or the command line options requesting to record data in
UNRST/UNSMRY format (see section 8.1.10):

– As specified by the keywords RPTMAPD (see 12.16.64), RPTMAPT (see 12.16.65),

RPTMAPL (see 12.16.66) (for grid properties) and RPTGRAPHD (see 12.16.64),
RPTGRAPHT (see 12.16.65), RPTGRAPHL (see 12.16.66) (for graph), if these are
present.
– If they are absent, then as specified by the keyword RPTRST (see 12.16.5).

9.1. Results of tNavigator calculation 397

 19.1

– If it is absent too, then no data is recorded.

• Otherwise no data is recorded.

The options of saving UNRST/UNSMRY files may be overridden by certain settings

made while opening the model (see the menu item Open As in tNavigator User Guide), global
settings (see Dump UNRST/UNSMRY Binaries in section 19.2. Models of tNavigator User
Guide), and/or command line keys (see 8.1.10).
See also the keywords RPTONLY (see 12.18.2) and RPTONLYO (see 12.18.3).
The binary files in E1 format are saved both from graphical interface and from console
version.
Text RSM file
RSM file can be created from graphical interface, remote graphical interface and console
version.
SEPARATE (see 12.18.4) and RUNSUM (see 12.18.4) set the option to dump RSM file for
models in E1 and E3 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: E1, E3, IM, ST, GE, MO.

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 –
keywords FLOWFUNC (see 12.8.4), FLOWFNAMES (see 12.8.6), proppant proper-
ties – keywords NPROPANTS (see 12.8.1), PROPANTNAMES (see 12.8.2), PROPANT-
TABLE, see 12.8.3);

• <name>_pvt.inc (PVT parameters – keywords PVTO (see 12.5.4), PVTW (see 12.5.5),
PVDG (see 12.5.7), ROCK (see 12.5.17), DENSITY (see 12.5.33) 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 tNavigator’s 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 doesn’t change initial model files, tNavigator just writes the new
data to the USER folder. Files <name>_rp.inc, <name>_pvt.inc etc. with new values

9.2. USER folder 398

 19.1

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.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.
It’s 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).

9.3.1. Load Statistics

Load Statistics is saved in the .log file and can be seen on the .log-panel in the following
form:
Example
Load Statistics: max, min, node1, node2, ...
Total elapsed = ... , CPU = ... , steps = ... , NI = ... , LI
= ... .
Load Statistics.
MPI-processes work on cluster nodes. So one MPI-process correspond to one cluster node.
(Threads work inside each process on the node.

So in the Load Statistics the following data is available:

• max – maximum of CPU time for all threads for all MPI-processes;
• min – minimum of CPU time for all threads for all MPI-processes;
• node1 – average of CPU time for all threads of the first MPI-process;
• node2 – average of CPU time for all threads of the second MPI-process, etc.
For example in the model has been calculated on 10 nodes Load Statistics can look the
following way:
Example
Load Statistics: 56608, 12235, 16403, 22642, 26661, 28458,
41284, 46732, 42328, 23627, 30455, 22900.
Calculation time and number of iterations.

9.3. Log file 399

 19.1

Calculation time statistics is available, for example:

Example
Total elapsed = 01.50.30, CPU = 01.15.15, steps = 550, NI =
819, LI = 18678.
Where:

• Total elapsed – full time of model calculation;

• CPU – is calculated as the sum of time for all treads (for all processes), divided by the
total number of threads (in all processes);

• steps – number of calculation time step;

• NI – number of Newton iterations (sum for all calculation steps);

• LI – number of linear iterations (sum for all calculation steps).

9.3.2. Blocks with convergence problems

The visualization of blocks with high linear solver residual is available in graphical user in-
terface Calculated Properties. Number of Convergence problems. This property should
be requested via the option CONVERGENCE_PROBLEM_NUM of the keyword TNAVCTRL
(see 12.1.4).

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.

This method is analogous to CONV RPTRST (see 12.16.5). Option CONV itself is not
supported in tNavigator.

9.3.3. The reason of each Newton iteration

the reasons of each Newton iteration are printed in the log file. The line of the log file for
Newton iteration looks the following way:

9.3.2. Blocks with convergence problems 400

 19.1

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.19.140) 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.19.140), 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.

9.3.3. The reason of each Newton iteration 401

 19.1

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:

10. Units 402

 19.1

• 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;

• T = 16 ◦ C

In case of compositional run, those conditions can be changed by user, STCOND

(see 12.14.11).

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:

• E1, E3 data format – systems METRIC, FIELD, LAB;

• MO data format – systems METR (metric) and POFU (the same to FIELD);

• IM, ST data formats – systems SI and FIELD.

10. Units 403

 19.1

11. Input data format

11.1. Input formats
For best adaptation of user experience the keyword notations in tNavigator are chosen to be
as close as possible to the most common simulators.
tNavigator reads keyword in different formats and converts them into its own inner data
format.
In addition: In formats that are used also in other simulators, additionally special tN key-
words can be used that are not implemented in other formats. The list of all special keywords
is available in the index 17. Also, for some standard keywords additional tNavigator options
can be used that are not implemented in other formats. All possible options are described in
keywords descriptions.

So, tNavigator supports the following data formats:

• E1 (black oil),

• E3 (black oil, compositional, thermal models),

• IM,

• ST,

• GE,

• MO,

• tN format (extension of E1, E3 formats that provide more convenient definition of well
data) – section 11.2.
Keywords description in this User Manual.

E1, E3 format keywords are red. For example: TABDIMS (see 12.1.29). Index of keywords
of these formats is in 15.

IM, ST, GE format keywords are pink. For example: TEMR (see 13.5.26). Index of key-
words of these formats is in 16.

MO format keywords are green. For example: IDATe (see 14.1.5). Index of keywords of
this format is in 18.

The keywords that can be used only in tNavigator are blue. For example: REACCONC
(see 12.15.64). Index of tN format keywords is in 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

11. Input data format 404

 19.1

are checked.

For example. In this table it is checked that the keyword is used in formats tNavigator,
E1, E3.

Data x tN x E1 x E3 IM GE ST MO
format
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 E1, E3 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 E1
(E3) 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.19.3). Then
define well trajectory, including different well branches via WELLTRACK (see 12.19.9), then
define well perforations in measured depth COMPDATMD (see 12.19.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 E1 (E3) can be used to define well data.

11.3. 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 line (formats E1, E3, tN) or can be on
the same line with the keyword (formats IM, ST, MO).

3. If keyword value is not specified by user, tNavigator uses a default value if there is one,
otherwise an error message is issued.

11.2. tNavigator format 405

Keywords for formats tN, E1, E3 19.1

4. Data arrays are terminated with a slash / (formats E1, E3, tN). If fewer entries than
array length are specified, then the remaining entries are filled with the default values if
possible, otherwise an error message is issued.

5. For equal values the standard form hNUMi ∗ hVALi can be used, where hNUMi is the
number of equal values, and hVALi is the value itself.

6. Reading the keywords in formats E1, E3.

Keywords in format E1, E3 are assumed to be no longer than 8 characters. All characters
after the first 8 are ignored. 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 long object names in formats E1, E3.

By default, the names of certain objects (wells, faults, LGRs) are assumed to be no
longer than 8 characters, so only the first 8 characters in their names are read. For ex-
ample, the wells’ names LONGWELL1 and LONGWELL2 are both read as LONGWELL.
To override this setting and read object names of arbitrary length, use the option LONG-
NAMES 1 of the keyword TNAVCTRL (see 12.1.4).

8. Reading of keywords after initial space in formats E1, E3.

By default the keywords that are written after the space symbol in the beginning of the
line are ignored.
To override this setting, use the option KEYWORDS_SPACE 1 of the keyword TNAVC-
TRL (see 12.1.4).

9. Reading the keywords in MO format.

Keywords in format MO are assumed to be 4 characters long. For convenience the
keywords are written in upper case. Sometimes the words may be written in full for
better human readability, for example: FLUId instead of FLUI. This makes no difference
for tNavigator.

11.3. Keywords’ syntax 406

Keywords for formats tN, E1, E3 19.1

12. Keywords for formats tN, E1, E3

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:

• tN;

• E1;

• E3.

In addition: In formats that are used also in other simulators, additionally special tNavi-
gator keywords can be used that are not implemented in other simulators (format extension).
The list of all special keywords is available in the index – 17. Also for some standard key-
words additional tNavigator options can be used that are not implemented in other simulators
(format extension). All possible options are described in keywords descriptions.

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.14)

• Thermal properties (12.15)

• Initialization section (12.16)

• Schedule section (12.19)

• Inflow from aquifer (12.17)

12. Keywords for formats tN, E1, E3 407

Keywords for formats tN, E1, E3 19.1

12.1. Definition section

Definition section contains initial data necessary for oil-and-gas reservoir model specification.

12.1. Definition section 408

Keywords for formats tN, E1, E3 19.1

12.1.1. RUNSPEC

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies the beginning of data section which contains initial data necessary
for oil-and-gas reservoir model specification.

12.1.1. RUNSPEC 409

Keywords for formats tN, E1, E3 19.1

12.1.2. TITLE

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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 410

Keywords for formats tN, E1, E3 19.1

12.1.3. REPORTFILE / REPORTSCREEN

Data x tN x E1 x E3 x IM x GE x ST x MO
format
x RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION x SUMMARY x SCHEDULE

REPORTFILE and REPORTSCREEN keywords provide more advanced capabilities for tun-
ing of output to log file (see section 9.3), 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 (see section 9.3) and to the screen will be performed using unit
system that is defined in the model.
There are two possible syntax of these keywords usage:
1. section and priority, characterizing the amount of output for this section;

2. option LIMIT to limit the number of repeating messages.

Section and priority, characterizing the amount of output for this section.
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

12.1.3. REPORTFILE / REPORTSCREEN 411

Keywords for formats tN, E1, E3 19.1

• priority, characterizing the amount of output to log file (to the screen). The following
options are possible:
<Priority> <Description>
CRIT Turn off report of all messages (including errors)
ERR Report only errors
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 informa-
tion 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 /.

• REPORTFILE
Default:
ALL HIGH
/.

• REPORTSCREEN
Default:
ALL HIGH
PRINT_LOGS WARNING
FIP WARNING
/.

The effect of REPORTFILE and REPORTSCREEN keywords is illustrated in the table

below examples. 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.

12.1.3. REPORTFILE / REPORTSCREEN 412

Keywords for formats tN, E1, E3 19.1

Example 1
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 2
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.3. REPORTFILE / REPORTSCREEN 413

Keywords for formats tN, E1, E3 19.1

Example 3
Example
REPORTFILE
CONN ERR
/
REPORTSCREEN
CONN ERR
/

This combination turns off report of all warnings for connections to the *.log file and to
the screen. This turns off for example the following warnings: Warning: connection [48, 10,
88] of well '2' is located in inactive grid block. It will be removed!

Example 4
Example
REPORTFILE
ALL CRIT
/
REPORTSCREEN
ALL CRIT
/
This combination turns off the report of all messages (including errors) to the *.log file
and to the screen.

12.1.3. REPORTFILE / REPORTSCREEN 414

Keywords for formats tN, E1, E3 19.1

Limitation of the number of messages on the screen and in the file

Default: 100.

!
By default the output of repeating messages is controlled in the settings in
tNavigator main window. Settings → Options → Models → Don’t hide mul-
tiple messages on conversion.
The number of messages can be limited using the following syntax:
Example
REPORTFILE
LIMIT N
/
REPORTSCREEN
LIMIT N
/
N – any integer number. In this case not more than N messages of one type will be
reported sequentially. Messages of other types will be reported but also not more than N mes-
sages sequentially.

For example, it we set this limit to 3 the following messages output is possible:
Warning: connection [39, 41, 85] of well W1 is located in inactive grid block. It will be
removed!
Warning: connection [48, 10, 3] of well W2 is located in inactive grid block. It will be
removed!
Warning: connection [48, 10, 4] of well W2 is located in inactive grid block. It will be
removed!
Warning: reached the maximum number of messages '3'.
Warning: 1-SOWCR(0.168)-SGL(0.) is greater than SWU(0.72) in block [53, 40, 67].
Warning: 1-SOWCR(0.273)-SGL(0.) is greater than SWU(0.72) in block [37, 61, 63].

12.1.3. REPORTFILE / REPORTSCREEN 415

12.1.3. REPORTFILE / REPORTSCREEN

Keywords for formats tN, E1, E3

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 DI-
MENS, TABDIMS
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
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 inactive messages
due to minimal pore
• Total memory allo- volume criteria, • Names of *.data,
cated MINPV (see 12.2.30) *.res, *.for,
*.err, *.log files

to be continued on the next page

416

19.1
12.1.3. REPORTFILE / REPORTSCREEN

Keywords for formats tN, E1, E3

continued from previous page
Priority LOW MEDIUM HIGH HIGHEST WARNING
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 step time step – message
restart – correspond- on time step com-
ing information: pletion and summary
restart moment, old – rates, average
and new time step pressure (REPORT
lengths N .. 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 ...)

to be continued on the next page

417

19.1
12.1.3. REPORTFILE / REPORTSCREEN

Keywords for formats tN, E1, E3

continued from previous page
Priority LOW MEDIUM HIGH HIGHEST WARNING
FIP
• Summary tables are • Summary tables for • Error and warning
enlarged with one all FIP regions – re- messages
column for each FIP serves, average reser-
region with the same voir pressure, pore
data volume

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 group • Message on com- • Error and warning
controls pensation switch off, messages
if total injection for
group is too small

to be continued on the next page

418

19.1
12.1.3. REPORTFILE / REPORTSCREEN

Keywords for formats tN, E1, E3

continued from previous page
Priority LOW MEDIUM HIGH HIGHEST WARNING
WELL
• Messages on well • Information on well • Error and warning
switch / perforation closure messages
due to economic
• Messages on prob- limit on rate or
lems with well calcu- watercut
lation

CONN
• Messages on cross- • Error and warning
flow through connec- messages
tions

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
419

19.1
Keywords for formats tN, E1, E3 19.1

12.1.4. TNAVCTRL

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword is used to set settings of model reading and calculation in tNavigator. The
data should be terminated with a slash /.

To enable option in this keyword use YES (the same as 1), to disable option use NO (the
same as 0). In case if a value or other parameter should be set to use the option it is written
additionally.

The following options can be used:

AQUCON_LGR
Possible options:

• YES – this option allows to build links for numerical aquifer-grid when local
grid refinement LGR is used in the area of aquifer connection. Links with refined
boundary blocks will be built for the face that is set as direction in AQUCON
(see 12.17.14) for global grid blocks;
• NO – aquifer links to refined blocks are not built (this setting is used by default);
Default: NO, option is not used.

API_GROUP_LOGIC_PRE182
Possible options are:

• YES – if this option is selected the following logic will be used:

– In PVTNUM (see 12.4.2) region numbers varies from 1 up to the miximum
number specified in TABDIMS (see 12.1.29);
– Tables of PVT properties of oil and gas are selected according to the number of
PVT region specified in PVTNUM (see 12.4.2) (e.g., if PVTNUM (see 12.4.2)
= 6 then the 6-th table will be chosen);
– For oil phase PVT regions are subdivided into AIP groups. The current grid
block belongs to the API group that its PVT region belongs to.
• NO – if this option is selected and the number of the AIP groups is equal to or
larger than 2 following logic will be used:
– In PVTNUM (see 12.4.2) region numbers varies from 1 to maximum number
of API groups;

12.1.4. TNAVCTRL 420

Keywords for formats tN, E1, E3 19.1

– In this case for oil phase PVTNUM (see 12.4.2) specifies the number of API
group. For water and gas PVTNUM (see 12.4.2) specifies the number of PVT
region.
Default: NO.

CASE_SENSITIVE
This option defines whether the well names are sensitive to UPPERCASE and lowercase
text.

• NO – UPPERCASE is equivalent to lowercase text

(i.e. well names 'w1' and 'W1' refer to the same object);
• YES – UPPERCASE is distinct to lowercase text
(i.e. well names 'w1' and 'W1' refer to different wells);
Default:
– In E1/E3 and MO models – NO
– In IM/GE/ST models – YES

COARSEN_BLOCK_DATA_LOGIC
This option controls the logic of grid coarsening invoked by the keyword COARSEN
(see 12.2.105). Possible values are:

• CENTRAL (or 0) – the centermost block according to I,J,K coordinates is chosen

as the representative of the coarsened block, regardless of its initial status (active
or inactive);
• NEAREST_ACTIVE_TO_CENTRAL (or 1) – the centermost active block is chosen
as the representative of the coarsened block;
Default: CENTRAL, in this case the representative of a coarsened block may be
inactive.

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) val-
ues from matrix to fracture blocks will be turned off. This option is used in E3
dual porosity models. Option DPGRID_PRE2014 with the same functionality is
obsolete;
• ECL_PRE2012 – additionally to the functionality described above this option turns
on logic of using MULTREGP (see 12.3.16).

CONVERGENCE_PROBLEM_NUM
This option allows to request the 3D property of blocks with convergence problems (see
section 9.3). After the option a number A% (from 0 to 100) should be specified – value
in percents.

12.1.4. TNAVCTRL 421

Keywords for formats tN, E1, E3 19.1

The 3D property Number of Convergence problems will be available in user graphical

interface in the option Grid Properties. Calculated.
This 3D property is incremented by one at each timestep if the residual value in the
block is greater than A% of maximum residual value. (+1 at each timestep if condition
fulfilled).
DFACTORSCALING
Possible options are:
• ALL – for calculation of connection D-factor the same value of D-factor will be
used for all branches;
• BRANCH – for calculation of connection D-factor the value of D-factor specified
for each branch will be used.
Formulas for calculation of connection D-factor are given in the description of keywords
COMPDATMD (see 12.19.10), COMPDATL (see 12.19.7) and COMPDAT (see 12.19.6).
DTMAXORIGINAL
If this option is set to YES, then maximum length of time steps from the keyword
TUNING (see 12.19.134) will be applied.
Default: NO, option is not used.

! It is recommended to specify calculation settings via RUNCTRL

(see 12.19.140) keyword.

FRACTURE_BUILD_LOGIC
This option activates the use of nested grid refinements during Hydraulic Fracture mod-
eling via LGR. The detailed description of Hydraulic Fractures modeling via Local Grid
Refinement is provided in section 5.8.
Two options are available:
• LOGARITHMIC_PARTITION_GRID – standard refinement with structured grids.
• UNSTRUCTURED_GRID – unstructured grid with nested refinements. The maxi-
mum number of nested refinement levels can be defined via
UNSTRUCTURED_FRACTURE_GRID_LEVELS parameter.
Default: UNSTRUCTURED_GRID.

The following parameters of FRACTURE_TEMPLATE (see 12.2.127) be-

come unavailable for editing when Unstructured partition is used for

!
Grid refinement:
• The number of block’s refinement along X, Y and Z directions.
• LEVEL_UP
• LEVEL_DOWN

12.1.4. TNAVCTRL 422

Keywords for formats tN, E1, E3 19.1

FRACTURE_INACTIVE_BLOCK_PROPERTIES_LOGIC
This option alters the logic of dynamic properties initialization in the refined inactive
blocks that were penetrated by hydraulic fracture. Porosity, Permeability and NTG can
be defined for these blocks via FRACTURE_TEMPLATE (see 12.2.127) keyword. There
are three possible ways to assign dynamic grid properties to activated blocks.
• SIMPLE_WATER – water saturation will be set equal to 100% ;
• REPRESENTATIVE_ELEMENT – water, gas and oil saturations in the grid block
will be denoted from representative fracture element.
• NEAREST_IJK_ACTIVE_BLOCK – properties will be copied from the nearest (in
I, J and K directions) active refined block. If no active block is found within the
same local grid, the properties will be initialize according to SIMPLE_WATER
option.
Default: NEAREST_IJK_ACTIVE_BLOCK.
GPU_FLASH
If the option is turned on (set to YES), then GPU calculation of vectorized compositional
flash is enabled.
Default: NO, option is not used.
INCRMCE
Option Include Rock Mass Conservation Equation. If value 1 is set then the rock mass
convergence equation is added to filtration equations. If this option is used in combi-
nation with salt dilution (section 2.24.1), then dilution process with be calculated fully
implicitly;
Default: 0, option is not used.
ISOTHERMAL
Energy conservation equation is not imposed in model. As a conclusion, grid cell tem-
peratures will not change from their specified initial values. This option can be used
only with option ZT of the keyword TFORM (see 13.8.2).
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 setting the keyword TNAVCTRL at the begin-
ning of the section, so that all the keywords after it will be read the right way.
Default: 0. The keywords that are written after the space symbol at the beginning of the
line line are ignored (this setting is used by default for compatibility with input format
E1/E3). By default this option is not used, these keywords are ignored, and the following
message is 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.

12.1.4. TNAVCTRL 423

Keywords for formats tN, E1, E3 19.1

LONGNAMES
If set to 1, then tNavigator will read names of objects (wells, faults, LGRs, actions set
via the keyword ACTION (see 12.19.158) and other) that are longer than 8 characters.
By default without this setting, only 8 characters out of each name are read, and the
rest is ignored. So the wells’ names LONGWELL1 and LONGWELL2 are both read as
LONGWELL.
Default: 0. Only the first 8 symbols of object names are read (this setting is used by
default for compatibility with input format E1/E3).

MISCIBLE_ST
Possible options are:

• 1 – activates an option of miscible displacement simulation for models in E1 for-

mat. In this case a miscible displacement model is similar to one applied for models
in E3 format (see keyword MISCIBLE, see 12.1.69), except variation of capillary
pressure with respect to surface tensions. Since for models in E1 format PcOG = 0.
All appropriate keywords except PARACHOR (see 12.6.80) can be used;
• 0 – turns off an option of miscible displacement simulation for models in E1
format;
Default: 1, option is activated.

MODEL_E1, MODEL_E3, MODEL_MO, MODEL_IM, MODEL_ST, MODEL_GE

Specifies explicitly model format. Equivalent to the command line option --input
(see Command line options).

These options may be generated automatically by tNavigator (for exam-

! ple, when AHM module creates model variants). In this case it is not
recommended to change them manually.

NEI
If the option is turned on (set to YES), then non-equilibrium initialization can be speci-
fied explicitly using keywords PRESSURE (see 12.16.12) and ZMF (see 12.16.23). It is
allowed the existence of blocks with SOIL (see 12.16.16) and SGAS (see 12.16.15)
equal to zero. For thermal models (THERMAL, see 12.1.54) pressure (PRESSURE,
see 12.16.12), ZMF (see 12.16.23), saturations and temperature (using RTEMP
(see 12.14.10) or TEMPI (see 12.16.32) or TEMPVD, see 12.15.84) should be speci-
fied;
Default: NO, option is not used.

RECOMPUTEGPMAINT
This option sets the logic of cumulative pressure error recalculation (integral of pres-
sure error). Default logic of the keyword GPMAINT (see 12.19.90) (or GPMAINT3,
see 12.19.91) assumes that if none of the wells is under GPMAINT control then integral
of pressure error is not recalculated.

12.1.4. TNAVCTRL 424

Keywords for formats tN, E1, E3 19.1

If this option is used (value 1) then the integral of pressure error is recalculated at each
time step;
Default: 0, option is not used.

RESGEO_BLOCK_REGULARITY
This option specifies the relative accuracy (in percentage) when constructing the ge-
omechanical grid. To construct the geomechanical grid the blocks of the original grid
are subdivided by tetrahedrons. In such case the volume of the original block may dif-
fer from the volume calculated over all block tetrahedrons. If the difference between
these block volumes exceeds the specified accuracy then such block will be disabled for
geomechanics;
Default: 0.01.

SAT_ADJUST ε
This option sets the minimum value (ε ) for oil and water saturations in case of non-
equilibrium initialization. If ε = 0 then this option is disabled.
The saturation adjustment is performed in the following way:

• If only SW < ε then in the blocks violating this condition water saturation will be
set equal to ε and the largest of remaining two phase saturations will be adjusted.
• If only SO < ε then in the blocks violating this condition oil saturation will be set
equal to ε in the blocks violating this condition and the largest of remaining two
phase saturations will be adjusted.
• If both SW and WO are < ε , then only water saturation will be set equal to ε and
gas saturation will be adjusted. Oil saturation will remain unchanged.

Default: ε = 0 (i.e. option is not used).

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 decreases material balance error. 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 guess to the solution. So this option can possibly slow down
the solving of the system of linear equation;
Default: 1, option is used.

SHOW_WELLS_OUTSIDE
This option sets well visualization in models in MO format. This option should be
added at the begining of RECU section. Moreover, this option does not connect with
GUI option Keep inactive wells in MO models (see the main window menu Settings.
Options. Models). Possible values are:

12.1.4. TNAVCTRL 425

Keywords for formats tN, E1, E3 19.1

• YES (or 1) – all wells, including wells located outside a reservoir, are visualized.
However, to see wells in GUI Draw Trajectories option should be activated;
• NO (or 0) – wells located outside a reservoir are not visualized;
Default: NO, the option is not activated.

SMOOTH_RP
Possible options:

• YES – turns on smoothing of relative permeabilities near critical point of two-phase

hydrocarbon region and the option HCSCAL of keyword FORMOPTS (see 12.1.96)
(if it is defined).
• NO – smoothing near critical point performs only in one-phase hydrocarbon region
and the option HCSCAL of keyword FORMOPTS (see 12.1.96) is ignored;
Default: NO, option is not used.

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.8), 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.19.175), and for producers rates are calculated for
average salt concentration in the wellbore (so, it’s the concentration of salt for
water produced from reservoir).

SWCR_CORR
Used to correct SWCR values in grid blocks using SWU, SWL. New values are calcu-
lated 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 weren’t specified will be calculated
via specified formula;
• 3 – SWCR values in all blocks will be recalculated via specified formula.

12.1.4. TNAVCTRL 426

Keywords for formats tN, E1, E3 19.1

TEST_WELL_FOR_MAX_RATE
If the option is turned on (set to YES), limits the maximum fluid rate or injection rate for
the wells with the sum over all perforations of the estimated maximum inflow to/outflow
from the block with perforation from/to the neighboring blocks calculated using the
specified BHP. Relevant for the models containing wells with very high production or
injection, which may otherwise lead to numeric instability.
Default: NO, option is not used.
UNSTRUCTURED_FRACTURE_GRID_LEVELS
This option defines the maximum number of nested refinement levels when unstruc-
tured grid partition is used during Hydraulic Fracture modeling via LGR (see parameter
FRACTURE_BUILD_LOGIC).
The detailed description of Hydraulic Fractures modeling via Local Grid Refinement is
provided in section 5.8.
Default: 5.
USEGASLIFTFROMSHUTWELLS
The option allows to include (value 1) or ignore (value 0) the value of gas-lift for shut
wells in network.
If the option is used (value 1), then:
• gas-lift from wells all is considered, i.e. it the well is SHUT then its gas-lift is
taken into consideration in network;
• gas-lift is taken into consideration without well efficiency factor (i.e. the keywords
WEFAC (see 12.19.83), GEFAC (see 12.19.84) are not used here).
Default: 0, option is not used.
VEC_FLASH
If the option is turned on (set to YES), the new parallel code for flash phase equilibrium
calculations in compositional models is used;
Default: YES, option is used.
VFP_NORMALIZE
If the option is turned on (set to YES), all VFP tables in the model are checked for mono-
tone dependence of BHP vs. THP, and if it is not monotone, the table is corrected (BHP
value is taken from the neighboring point with higher THP). VFP tables are specified
with the keyword VFPPROD (see 12.19.66) for producers and VFPINJ (see 12.19.65)
for injectors;
Default: NO, option is not used.
VFP_CURVES_NORMALIZE
VFP tables calculated using VFPCORR (see 12.19.71) or imported using IM-
PORT_WELL (see 12.1.11), are always normalized (i.e., option is turned on and set
to YES). To turn off normalization set to NO;

12.1.4. TNAVCTRL 427

Keywords for formats tN, E1, E3 19.1

Default: YES, option is used.

WELLPRESTOL
This option sets tolerance, which is used to calculated bottom hole pressure for the well
which is not on bottom hole pressure control;
Default: 1e-6.

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 greater than the specified value 90% from the
maximum residual value.

12.1.4. TNAVCTRL 428

Keywords for formats tN, E1, E3 19.1

12.1.5. AIMCTRL

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword sets settings of adaptive implicit method (AIM) used as approximation
method in time (see section 5.3).

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.19.140).

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);
Default: 0.2.
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);
Default: 0.125.
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);
Default: 1020 (METRIC), i.e., this criterion is turned off.
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;
Default: 0.01.
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 (di-
mensionless). Fully implicit scheme is used for blocks with open connections;
Default: 1.
6. Percent – minimum percent of non-water blocks that use fully implicit scheme (dimen-
sionless).
Default: 0, i.e., this criterion is turned off.

12.1.5. AIMCTRL 429

Keywords for formats tN, E1, E3 19.1

12.1.6. FLASHCTRL

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

Flash calculations are used for processes with vapor/liquid-equilibrium. The keyword al-
lows to change convergence preferences for compositional flash. The following options and
their parameters can be specified:

1. ADD_PF_FL_CALC n – option runs ”path finder” algorithm in case if stability test

found out instability of one-phase states, and flash solving algorithm didn’t converge.
Allowable values are 1 and 0;
Default: 1.

2. FL_TOL n – flash solution tolerance;

Default: 1E-6.

3. FL_V_PREC n – tolerance of material balance equation solution;

Default: 1E-6.

4. 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);
Default: 1.

5. PH_STBLTY_QNSS_PREC n – QNSS tolerance in stability test;

Default: 1E-6.

6. PH_STBLTY_QNSS_TRIV_TOL n – tolerance used to find trivial solution of test sta-

bility system by QNSS method;
Default: 1E-4.

7. PSCALESHADOW n – parameter of SHADOWREGION option which defines how

much pressure of one-phase hydrocarbon can change to stay it one-phase;
Default: 0.05.

8. SHADOWREGION n – flash boost option. Allowable values are 1 (option is switched

on) and 0 (option is switched off).
Default: 0. This option can be useful for models where most blocks have one-phase
state (no matter, GAS or OIL) and they are don’t turn to two-phase state during the
calculation. If certain criteria are satisfied, then without running stability test it is decided

12.1.6. FLASHCTRL 430

Keywords for formats tN, E1, E3 19.1

that hydrocarbon is in one-phase state (OIL or GAS).

The "certain criteria" are the criteria for checking if block is one-phase or not. Thus,
this option checks the state of each grid block at each time step to determine if it
is one-phase. The algorithm of such checking can be found in the article [30]. These
checkings are faster than flash running ("stability test") for one-phase state blocks. So,
SHADOWREGION 1 allows to speedup the models in described cases;

9. VLW_FLASH n – turns on/off a three-phase flash calculation for a system vapor-liquid-

water for the CO2 /H2 S solution option. If n=1 three-phase flash is turned on and if n=0
the flash is turned off;
Default: 0.

10. ZSCALESHADOW n – parameter of SHADOWREGION option which defines how

much component parameter of one-phase hydrocarbon can change to stay it one-phase;
Default: 0.1.

The data should be terminated with a slash /.

Example
FLASHCTRL
SHADOWREGION 1
/

12.1.6. FLASHCTRL 431

Keywords for formats tN, E1, E3 19.1

12.1.7. NEFLASH

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY x SCHEDULE

This keyword allows to specify a method of simulation of nonequilibrium for composi-

tional models. Methods available in tNavigator are described in details in the section 3.13.
The keyword is followed by a set of data. Each row contains the method number and the
value of parameter α used in the selected method:

• method number. The following methods are available:

– 1– method 1;
– 2– method 2;
– 3– method DKDT.

• parameter α , α ≥ 0 (METRIC: 1/day, FIELD: 1/day). If α = 0 inverse gas disso-

lution in oil or inverse oil vaporization in gas do not exist; α = ∞ is equivalent to
equilibrium flash. The value of parameter α is selected experimentally.

Each row is terminated by symbol /. The number of rows depend on the number of EoS
regions specified by 9-th parameter of the keyword TABDIMS (see 12.1.29).

!
This keyword is not compatible with option VEC_FLASH of the keyword
TNAVCTRL (see 12.1.4) and option VLW_FLASH with option VEC_FLASH
of the keyword FLASHCTRL (see 12.1.6).

Example
NEFLASH
3 0.0005/
2 0.0005/
/

In this example the DKDT method (the method number is 3) is implemented in the first
EoS region, the 2-nd method in the second EoS region. The parameter value is equal to 0.0005
for both methods.

12.1.7. NEFLASH 432

Keywords for formats tN, E1, E3 19.1

12.1.8. VELDEP

Data x tN E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets parameters of velocity dependent relative permeabilities (see section
2.6.14).
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);
Default: 0 – model is inactive.

2. capillary number model which will be active for the gas phase (1 or 2);
Default: 0 – model is inactive.

3. Forchheimer number model which will be active for the oil phase (1 or 2), IGNORED,
this is an E1/E3 compatibility field;
Default: 0 – model is inactive.

4. Forchheimer number model which will be active for the gas phase (1 or 2) for D-factor
calculation (see section 2.6.14);
Default: 0 – model is inactive.

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;
Default: 0 – model is inactive.

Parameters of alternative model (5-th parameter of the keyword) have default values, but
they can be changed using the keyword VDKRGC (see 12.14.63).

Capillary numbers are set by the keywords VDKRO (see 12.14.64) and VDKRG
(see 12.14.62) correspondingly.

Example
VELDEP
1 1 1 0 0 /
In the example first models of capillary numbers are set.

12.1.8. VELDEP 433

Keywords for formats tN, E1, E3 19.1

12.1.9. PHASEID

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies an algorithm of single phase indefication and can be used for
isothermal compostional models and extended black oil model (with keyword VAPOIL,
see 12.1.59).
The following parameters should be specified:

1. In case of isothermal compostional models:

• OIL – single phase hydrocarbon is considered to be oil;
• GAS – single phase hydrocarbon is considered to be gas;
• FACTLI – to specify a phase of single phase hydrocarbon the Li mixing rule;
• COMBINED – is the equation of state (EOS) has three real roots, then a phase of
hydrocarbon is a phase with the lowest Gibbs energy. If the EOS has only one real
root and mixture temperature is higher than critical temperature calculated using
the Li mixing rule then the hydrocarbon phase is gas. If mixture temperature is
less than critical temperature then a heuristic algorithm evaluating a mixture phase
state by a separating curve and based on analysis of EOS under current pressure
and temperature is implemented.
• Default: COMBINED.
2. In case of black oil model:
• OIL – single phase hydrocarbon is considered to be oil;
• GAS – single phase hydrocarbon is considered to be gas (analog to the keyword
ISGAS, see 12.1.78);
• Default: GAS.

The data should be terminated with a slash /.

Notice: For extended black oil models there are cases when for a specified composition
and pressure it is not possible to identify a phase state of system. It can only be stated that
the state is a single phase one. These cases are when Rmaxs < Rsat
s and Rv
max < Rsat (Rmax is
v s
max
the Rs when all gas dissolved in oil in a block, Rv is the Rv when all oil vaporized in a
block) or when Rs · Rv = 1. In such cases if the phase state in the block is a single phase at
the previous time step it will not change at the next time step. However, if at the previous
time step the phase state is a two phase one and an option OIL is specified in PHASEID then
single phase hydrocarbon is considered to be oil, if the option GAS is specified – single phase
hydrocarbon is gas.

12.1.9. PHASEID 434

Keywords for formats tN, E1, E3 19.1

Example
PHASEID
OIL /

12.1.9. PHASEID 435

Keywords for formats tN, E1, E3 19.1

12.1.10. TFORM

Data x tN E1 x E3 IM GE x ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets primary variable in the thermal equation (see section 4.34). One of the
following parameters should be specified:

• 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 ST and E3 format models (variables are chosen
automatically by tNavigator).

12.1.10. TFORM 436

Keywords for formats tN, E1, E3 19.1

12.1.11. IMPORT_WELL

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is used to import a VFP project created using the VFP Designer for a
selected well. Importing a VFP project it is possible to create a standard, multisegment and
multilateral wells in a model. This, it is not required to specify corresponding keywords
such as WELSPECS (see 12.19.3), WELLTRACK (see 12.19.9), COMPDATMD (see 12.19.10),
WELSEGS (see 12.19.11) and COMPSEGS (see 12.19.27).
The keyword is followed by a set of data. Each line contains:

• path to a project.
A relative path to a file containing a VFP project;

• well name (optional).

A well name that a VFP project is imported to. If a well name is different in the VFP
project then the specified well name will be used. If a well name is not specified then a
well name will be taken from the VFP project.

Each data line should be terminated by a slash /. All data should be terminated by a slash

!
/.
To import VFP projects it is recommended to use the keyword IM-
PORT_PROJECT (see 12.1.13).

Example
IMPORT_WELL
'../project_folder/My_vfp_project1.vfpproject' 'PROD1'/
'../project_folder/My_vfp_project2.vfpproject' 'PROD2'/
/
In this example VFP projects 'My_vfp_project1.vfpproject' and 'My_vfp_project2.vfpproject'
located in the folder '../project_folder' are imported to wells 'PROD1' and 'PROD2', respec-
tively.

12.1.11. IMPORT_WELL 437

Keywords for formats tN, E1, E3 19.1

12.1.12. IMPORT_NETWORK

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is used to integrate a hydrodynamic model with a surface network project
created using the Network Designer.
The keyword is followed by a set of data. Each line contains:

• path to a network project.

A relative path to a file containing a network project.

Each data line should be terminated by a slash /. All data should be terminated by a slash

!
/.
In case of several records (paths to projects) are specified only the first path
to a project will be used.

! To integrate a hydrodynamic model with a network project it is recommended

to use the keyword IMPORT_PROJECT (see 12.1.13).

Example
IMPORT_NETWORK
'../project_folder/network.ndproject' /
/

In this example a network project 'network.ndproject' located in the folder '../pro-

ject_folder' is integrated with a hydrodynamic model.

12.1.12. IMPORT_NETWORK 438

Keywords for formats tN, E1, E3 19.1

12.1.13. IMPORT_PROJECT

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is used to integrate a hydrodynamic model with an unified tNavigator

project. The tNavigator project may include:

• surface network project created using the Network Designer;

• VFP project created using the VFP Designer;

• PVT project created using the PVT Designer (may be included in VFP or network
project).

The keyword is followed by a set of data:

1. path to a network project.

A relative path to a file containing a network project. The file has an extension *tnavpro-
ject.

2. case;
If case is not specified the current case will be taken.

3. project type for license reservation on cluster. If calculations run on local host the 3-rd
parameter will be ignored as required license is autodetected and taken automatically. It
is required to specify:

• VFP;
If the tNavigator project contains only VFP project.
• NETWORK;
If the tNavigator project contains only a surface network project.
• VFP_NETWORK.
If the tNavigator project contains both surface network and VFP projects.

Each data line should be terminated by a slash /. All data should be terminated by a slash
/.
Example
IMPORT_PROJECT
'../project_folder/model.tnavproject' 'Case 1' 'VFP_NETWORK' /
/

12.1.13. IMPORT_PROJECT 439

Keywords for formats tN, E1, E3 19.1

In this example a Case 1 of tNavigator project 'modle.tnavproject' containing both surface

network and VFP projects is integrated with a hydrodynamic model. tNavigator project is
located in the folder '../project_folder'.

12.1.13. IMPORT_PROJECT 440

Keywords for formats tN, E1, E3 19.1

12.1.14. UNIFOUT

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword is used for saving calculation results as E1/E3 binary files. It sets mode of
output of RESTART and SUMMARY files. Results of calculations in tNavigator can be saved
in different formats described in the section 9.1. 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.16) to create one output file for one reporting step (multiple
files).
Default: MULTOUT (see 12.1.16).
Example
UNIFOUT

12.1.14. UNIFOUT 441

Keywords for formats tN, E1, E3 19.1

12.1.15. UNIFOUTS

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword is used for saving calculation results as E1/E3 binary files. It sets mode
of output of SUMMARY files. Results of calculations in tNavigator can be saved in different
formats described in the section 9.1. If the keyword is specified, then output of every reporting
step is saving into unified file of this type. This keyword overwrites the behavior of the
MULTOUT (see 12.1.16) keyword which acts on both summary and restart files.
You need to use the keyword MULTOUTS (see 12.1.17) to create one output file for one
reporting step (multiple files).
Default: MULTOUTS (see 12.1.17).
Example
UNIFOUTS

12.1.15. UNIFOUTS 442

Keywords for formats tN, E1, E3 19.1

12.1.16. MULTOUT

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword is used for saving calculation results as E1/E3 binary files. It sets mode of
output of RESTART and SUMMARY files. Results of calculations in tNavigator can be saved
in different formats described in the section 9.1. 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.14) to create one unified file for all reporting
steps.
This keyword is used by default.
Example
MULTOUT

12.1.16. MULTOUT 443

Keywords for formats tN, E1, E3 19.1

12.1.17. MULTOUTS

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword is used for saving calculation results as E1/E3 binary files. It sets mode
of output of SUMMARY files. Results of calculations in tNavigator can be saved in different
formats described in the section 9.1. 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 UNIFOUTS (see 12.1.15) to create one unified file for all
reporting steps. This keyword overwrites the behavior of the UNIFOUT (see 12.1.14) keyword.
This keyword is used by default.
Example
MULTOUTS

12.1.17. MULTOUTS 444

Keywords for formats tN, E1, E3 19.1

12.1.18. START

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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 following
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.19.124) must be later than the start date.

Example
START
01 JUL 1984
/

12.1.18. START 445

Keywords for formats tN, E1, E3 19.1

12.1.19. METRIC

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keywords defines that METRIC system is used in the model.

12.1.19. METRIC 446

Keywords for formats tN, E1, E3 19.1

12.1.20. FIELD

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keywords defines that FIELD system is used in the model.

12.1.20. FIELD 447

Keywords for formats tN, E1, E3 19.1

12.1.21. LAB

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keywords defines that LAB system is used in the model.

12.1.21. LAB 448

Keywords for formats tN, E1, E3 19.1

12.1.22. LANGUAGE

Data x tN E1 E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.22. LANGUAGE 449

Keywords for formats tN, E1, E3 19.1

12.1.23. BLACKOIL

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword defines that black oil model is used. Compositional run is defined via the
keyword COMPS (see 12.14.1).
Example
BLACKOIL

12.1.23. BLACKOIL 450

Keywords for formats tN, E1, E3 19.1

12.1.24. DEFINES

Data x tN x E1 x E3 x IM x GE x ST MO
format
x RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS SOLUTION SUMMARY x SCHEDULE

The description of possibilities of Assisted History Matching (AHM) and Uncertainty

Analysis module is given in the AHM and Uncertainty guide.
Setting variables for Assisted History Matching Module:

• For models in formats tNavigator, E1, E3 – this keyword DEFINES should be used;

• For models in formats IM, ST, GE – this keyword DEFINES should be used, the only dif-
ference is that all parameters should be in the quotes (see the description of parameters
and Example 9 below);

• For models in format MO – the keyword VDEF (see 12.1.25) should be used, whose
syntax is analogous to DEFINES;

• Assisted History Matching module generates automatically the keywords PREDEFINES

(see 12.1.26), OPEN_BASE_MODEL (see 12.1.27) in files of model’s variants. These
keywords are not intended to be entered manually in models.

In DEFINES the data for each variable should be terminated with a slash /. All data should
be terminated with a final slash /.

For each variable the following parameters should be specified:

1. variable name (may contain letters, digits, and underscore characters (_); variable name
can not start with a digit or underscore character);

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, uniform or
log-normal).
Minimum and maximum values can’t 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, uniform or
log-normal).
Minimum and maximum values can’t depend on other variables;

5. type. The following types are available:

12.1.24. DEFINES 451

Keywords for formats tN, E1, E3 19.1

• INTEGER – the variable can be only integer number, for example 1, 2, 3, ... If the
Type is INTEGER then min and max must also be integer numbers;
• REAL – float number, for example 2.44, 3.789999;
• STRING – string, for example, ”my_rp”, ”my_grid” etc. Different files with ex-
tension *.inc (e.g., containing a distribution of porosity) can be included into a
model. Values of string variable can be controlled by algorithm or set by external
grid search.
• Default: REAL.

Note: for models in formats IM, ST, GE all parameters that are specified should be inside
quotes. See an Example 9 below.

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 can’t be used between variable name and @.
In history matching process the variable will be replaced by a number (from the range, speci-
fied in DEFINES via min-max).
Variables can’t be used in the maps with dimensions NXxNYxNZ. Don’t 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.23) is used to assign to an array SWL (see 12.6.26) the

12.1.24. DEFINES 452

Keywords for formats tN, E1, E3 19.1

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.

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 @...@.

12.1.24. DEFINES 453

Keywords for formats tN, E1, E3 19.1

Example
EQUALS
SWCR @SWL+0.1@/
/

Example 4. Use formula inside @...@.

Example
EQUALS
KRW @KRW@/
KRWR @KRW*0.9@/
/

Example 5. Use complex formulae.

Let’s 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.

12.1.24. DEFINES 454

Keywords for formats tN, E1, E3 19.1

Example
DEFINES
'PERMH_MULT_LAYERS_1' 1 0.1 3 REAL/
'PERMH_MULT_LAYERS_2' 2 1 5 INTEGER/
'PERMH_MULT_LAYERS_3' 1 0.1 2 REAL/
'PERMH_MULT_LAYERS_4' 1 0.1 3 REAL/
'PERMH_MULT_LAYERS_5' 1 0.1 3 REAL/
/
...

MULTIPLY
'PERMX' @PERMH_MULT_LAYERS_1@ 1 19 1 28 1 1 /
'PERMX' @PERMH_MULT_LAYERS_2@ 1 19 1 28 2 2 /
'PERMX' @PERMH_MULT_LAYERS_3@ 1 19 1 28 3 3 /
'PERMX' @PERMH_MULT_LAYERS_4@ 1 19 1 28 4 4 /
'PERMX' @PERMH_MULT_LAYERS_5@ 1 19 1 28 5 5 /
/

COPY
'PERMX' 'PERMY'/
/

In this example multipliers for PERMX (permeability in X-direction) are specified for
layers (1, 2, 3, 4, 5).
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 INTEGER type is specified. Other
variables are float numbers – REAL.
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 don’t 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).

12.1.24. DEFINES 455

Keywords for formats tN, E1, E3 19.1

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
(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.

12.1.24. DEFINES 456

Keywords for formats tN, E1, E3 19.1

Example
DEFINES
'PORONUM' 2 1 20 INTEGER/
/
...
INCLUDE
'MODEL_PORO_@PORONUM@.inc '
/

In this example we define integer variable PORONUM (type - INTEGER). It is used in

the file name that is included and contains model porosity realization.

Example 9. Defining variables for models in IM, ST, GE formats.

Example
*DEFINES
'MULTPERM' '1' '0.1' '10'

....

*PERMI *CON 1.0

*MOD * @MULTPERM@
*PERMJ *EQUALSI * 1.00
*PERMK *EQUALSI * 0.1

In this example we define a variable – permeability multiplier.

Example 10. Defining a variable of type STRING.
Example
DEFINES
RP_FILENAME 'my_rp' 1* 1* STRING/
/
...
INCLUDE
@RP_FILENAME+".inc"@/

In this example a variable RP_FILENAME of type STRING is defined as a string my_rp.

Using the keyword INCLUDE (see 12.1.80) a file my_rp.inc will be included into the model.
After that in AHM graphical interface the required values of string variable should be set.

12.1.24. DEFINES 457

Keywords for formats tN, E1, E3 19.1

12.1.25. VDEF

Data x tN E1 E3 IM GE ST x MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is used to specify model variables to tNavigator Assisted History Matching
Module for models in MO (for E1 and E3 format models one should use the keyword DE-
FINES, see 12.1.24). The description of possibilities of Assisted History Matching (AHM) and
Uncertainty Analysis module is given in the AHM and Uncertainty guide.

The syntax of this keyword is analogous to DEFINES (see 12.1.24).

12.1.25. VDEF 458

Keywords for formats tN, E1, E3 19.1

12.1.26. PREDEFINES

Data x tN E1 E3 IM GE ST MO
format

This keyword is automatically generated by tNavigator if you use Assisted

! History Matching (AHM) and Uncertainty Analysis module. The description
of possibilities of this module is given in the AHM and Uncertainty guide.
The keyword is not intended to be entered manually in models.
To define variables for AHM use the keyword DEFINES (see 12.1.24) (for models in for-
mats E1, E3) or VDEF (see 12.1.25) (for models in format MO).

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.24).

The keyword OPEN_BASE_MODEL (see 12.1.27) puts the value of the variable in the
original model instead of @variable_name@.

Example
PREDEFINES
MULT1 1.0000000 0.1000000 3.0000000 REAL /
MULT2 2 1 5 INTEGER /
MULT3 1.0000000 0.1000000 2.0000000 REAL /
MULT4 1.0000000 0.1000000 3.0000000 REAL /
MULT5 1.0000000 0.1000000 3.0000000 REAL /
/

OPEN_BASE_MODEL
'PUNQ_exp1.DATA'/

12.1.26. PREDEFINES 459

Keywords for formats tN, E1, E3 19.1

12.1.27. OPEN_BASE_MODEL

Data x tN E1 E3 IM GE ST MO
format

This keyword is automatically generated by tNavigator if you use Assisted

! History Matching (AHM) and Uncertainty Analysis module. The description
of possibilities of this module is given in the AHM and Uncertainty guide.
The keyword is not intended to be entered manually in models.
See the description of the keyword PREDEFINES (see 12.1.26).

12.1.27. OPEN_BASE_MODEL 460

Keywords for formats tN, E1, E3 19.1

12.1.28. DIMENS

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.28. DIMENS 461

Keywords for formats tN, E1, E3 19.1

12.1.29. TABDIMS

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The data consists of the following items, describing number of regions with different
parameter values. The numbers specify:
1. number of saturation function regions (SATNUM, see 12.4.3);
Default: 1.
2. number of regions with different PVT properties (PVTNUM, see 12.4.2);
Default: 1.
3. maximum number of saturation nodes in any saturation table, entered by keywords
SGFN (see 12.6.14), SGOF (see 12.6.2);
Default: 20.
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);
Default: 20.
5. number of fluid-in-place regions (FIPNUM, see 12.4.10). Also this number may be spec-
ified with keyword REGDIMS (see 12.1.32). If this parameter is set both in REGDIMS
(see 12.1.32) and TABDIMS, then maximum value is taken;
Default: 1.
6. maximum number of nodes of oil vaporization in gas RG,O in one PVT table, entered
by keywords PVTO (see 12.5.4), PVCO (see 12.5.6);
Default: 20.
7. maximum number of nodes of oil-gas ratio RO,G in one PVT table of wet gas, entered
by a keyword;
Default: 20.
8. maximum number of saturation end-point versus temperature tables (tables are specified
using the keyword ENPTVT, see 12.15.85);
Default: 1.
9. maximum number of equation of state regions for reservoir conditions (these regions
are entered using the keyword EOSNUM, see 12.4.20);
Default: 1.

12.1.29. TABDIMS 462

Keywords for formats tN, E1, E3 19.1

10. maximum number of equation of state regions for surface conditions.

Default: 9-th parameter of this keyword.

11. maximum number of flux regions,

12. maximum number of thermal regions,

13. number of rock tables (these regions are entered using the keyword ROCKNUM,
see 12.4.14),

14. maximum number of pressure maintenance regions,

15. the number of temperatures for Ki (p, T ) tables (KVTEMP (see 12.15.13), KVTABTn,
see 12.15.14).

The division of grid blocks into regions and setting of appropriate values should be speci-
fied below.
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.29. TABDIMS 463

Keywords for formats tN, E1, E3 19.1

12.1.30. EQLDIMS

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.16.2);

Default: 1.

2. number of depth nodes in any table of pressure versus depth constructed internally by
the equilibration algorithm; IGNORED, this is an E1/E3 compatibility field; In tNav-
igator number of lines does not have to be specified because the tables are allocated
dynamically;
Default: 100.

3. maximum number of depth nodes in any table RSVD (see 12.16.7), RVVD (see 12.16.9);
IGNORED, this is an E1/E3 compatibility field; In tNavigator number of lines does not
have to be specified because the tables are allocated dynamically;
Default: 20.

4. maximum number of tables of initial tracer concentration versus depth (TVDP,

see 12.16.45);
Default: 1.

5. maximum number of lines in the table of initial tracer concentration versus depth
(TNUM, see 12.16.44);
Default: 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.30. EQLDIMS 464

Keywords for formats tN, E1, E3 19.1

12.1.31. ACTDIMS

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets dimensions for the keywords ACTION (see 12.19.158), ACTIONW
(see 12.19.161), ACTIONG (see 12.19.159), ACTIONR (see 12.19.160). The data should be
terminated with a slash /.

1. the maximum number of types of keywords ACTION (see 12.19.158); ignored, this is an
E1/E3 compatibility field. In tNavigator number of types does not have to be specified
because the memory is allocated dynamically;
Default: 2.

2. the maximum number of lines of SCHEDULE data (including the ENDACTIO keyword)
that can be defined in any one ACTION (see 12.19.158); ignored, this is an E1/E3
compatibility field. In tNavigator number of lines does not have to be specified because
the memory is allocated dynamically;
Default: 50.

3. the maximum number of characters per line of ACTION (see 12.19.158) data; ignored,
this is an E1/E3 compatibility field. In tNavigator number of characters does not have
to be specified because the memory is allocated dynamically;
Default: 80.

Example
ACTDIMS
5 40 100
/

12.1.31. ACTDIMS 465

Keywords for formats tN, E1, E3 19.1

12.1.32. REGDIMS

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The data consists of items, describing number of regions with different parameter values.
The data should be terminated with a slash /.

The numbers specify:

1. maximum number of fluid-in-place regions (FIPNUM, see 12.4.10), also may be spec-
ified with keyword TABDIMS (see 12.1.29). If this parameter is set both in REGDIMS
and TABDIMS (see 12.1.29), then maximum value is taken;
Default: 1.

2. maximum number of families of user-defined fluid-in-place regions (FIP, see 12.4.11);

Default: 1.

3. maximum number of independent reservoir regions;

Default: 0.

4. maximum number of flux regions (FLUXNUM, see 12.4.18);

Default: 0.

5. maximum number of regions for TRACK (see 12.1.135), IGNORED, this is an E1/E3
compatibility field. In tNavigator number of regions does not have to be specified be-
cause the memory is allocated dynamically;
Default: 0.

6. maximum number of Coal Bed Methane regions (COALNUM, see 12.4.15);

Default: 1.

7. maximum number of regions for OPERNUM (see 12.4.21), IGNORED, this is an E1/E3
compatibility field. In tNavigator number of regions does not have to be specified be-
cause the memory is allocated dynamically;
Default: 0.

8. the number of arrays WORK (see 12.3.6) that can be used in OPERATE (see 12.3.26);
Default: 0.

12.1.32. REGDIMS 466

Keywords for formats tN, E1, E3 19.1

9. the number of arrays IWORK (see 12.3.6) that can be used in OPERATE (see 12.3.26);
Default: 0.

10. maximum number of polymer flooding mixing region, which are specified via
PLMIXNUM (see 12.2.107), IGNORED, this is an E1/E3 compatibility field. In tNavi-
gator number of regions does not have to be specified because the memory is allocated
dynamically;
Default: 1.

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.32. REGDIMS 467

Keywords for formats tN, E1, E3 19.1

12.1.33. VFPIDIMS

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets the dimensions of VFP tables for injectors, which are specified using
the keyword VFPINJ (see 12.19.65). The data should be terminated with a slash /. The imple-
mentation of VFP tables, corresponding formulas and keywords are described in the section
6. VFP tables generation.
The following parameters are to be specified:

1. maximum number of flow values (FLO) in each table;

Default: 0.

2. maximum number of tubing head pressure values (THP) in each table;

Default: 0.

3. maximum number of VFP tables for injectors;

Default: 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 VFP
tables for injectors – 3.

12.1.33. VFPIDIMS 468

Keywords for formats tN, E1, E3 19.1

12.1.34. VFPPDIMS

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets the dimensions of VFP tables for producers, which are specified using
the keyword VFPPROD (see 12.19.66). The data should be terminated with a slash /. The
implementation of VFP tables, corresponding formulas and keywords are described in the
section 6. VFP tables generation.
The following parameters are to be specified:

1. maximum number of flow values (FLO) in each table;

Default: 0.

2. maximum number of tubing head pressure values (THP) in each table;

Default: 0.

3. maximum number of water fraction (WFR) in each table;

Default: 0.

4. maximum number of gas fraction (GFR) in each table;

Default: 0.

5. maximum number of artificial lift quantities (ALQ) in each table;

Default: 0.

6. maximum number of VFP tables for producers;

Default: 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 VFP tables for producers – 2.

12.1.34. VFPPDIMS 469

Keywords for formats tN, E1, E3 19.1

12.1.35. GPTDIMS

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is used to specify gas plant table dimensions. Gas plant tables are spec-
ified via the keywords GPTABLE (see 12.16.26), GPTABLE3 (see 12.16.28), GPTABLEN
(see 12.16.27). The data should be terminated with a slash /.

The following parameters are to be specified:

1. maximum number of gas plant tables. (IGNORED). This is an E1/E3 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 E1/E3 compatibil-
ity 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 E1/E3 com-
patibility 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.35. GPTDIMS 470

Keywords for formats tN, E1, E3 19.1

12.1.36. PIMTDIMS

Data x tN x E1 E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is used to specify PI scaling tables dimensions. The tables are specified via
PIMULTAB (see 12.19.38). The data should be terminated with a slash /.

The following parameters are to be specified:

1. maximum number of PI scaling tables. (IGNORED). This is an E1/E3 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 the table. (IGNORED). This is an E1/E3 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.36. PIMTDIMS 471

Keywords for formats tN, E1, E3 19.1

12.1.37. ROCKCOMP

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets the rock compaction option and maximum number of rock regions (ta-
bles of transmissibility dependence on pressure).

There 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);
• HYSTER – rock compaction is hysteretic. If the pressure exceeds an elastic limit
pressure given by the deflation curve the pore space deflates and reinflates elasti-
cally. For cells on the deflation curve, when the pressure increases the pore spaces
will only reinflate partially. Pore volume and transmissibility multipliers dependent
on pressure specified by keyword ROCKTABH (see 12.5.22) in PROPS section;
• BOBERG – rock compaction is hysteretic; For pressures higher than an elastic
minimum one given by the deflation curve and lower than an elastic maximum
given by the dilation curve the pore space deflates and reinflates elastically. For
cells located on the deflation curve, when the pressure increases the pore spaces
will only reinflate partially. For cells located on the dilation curve, the pore spaces
will only deflate partially when the pressure decreases. Pore volume and trans-
missibility multipliers dependent on pressure specified by keyword ROCKTABH
(see 12.5.22) in PROPS section;
• Default: REVERS.

2. the maximum number of rock regions,

3. flag of the Water Induced Compaction option is used: YES or NO. (IGNORED), this is
an E1/E3 compatibility field.

Tables of transmissibility dependence on pressure for each rock region are set using the
keyword ROCKTAB (see 12.5.21). 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.29)

12.1.37. ROCKCOMP 472

Keywords for formats tN, E1, E3 19.1

and in 2-nd parameter of ROCKCOMP (see 12.1.37), then the following logic is used to
calculate the number of rock regions:

• E1 format: only the 2-nd parameter of ROCKCOMP (see 12.1.37) is used;

• E3 format: the maximum value is taken from the 13-th parameter of TABDIMS
(see 12.1.29), and 2-nd parameter of ROCKCOMP (see 12.1.37).

Example
ROCKCOMP
IRREVERS 5
/
In this example there are 5 rock regions and rock compaction is irreversible.

12.1.37. ROCKCOMP 473

Keywords for formats tN, E1, E3 19.1

12.1.38. ROCKDIMS

Data x tN E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can only be used if THERMAL (see 12.1.54) is present.

The keyword specifies the number of types of cap and base rocks with different properties,
which will be used to model the heat exchange between the reservoir and surroundings (see
section 4.30). The data should be terminated with a slash /.

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.85);
Default: the value of 1-st parameter of this keyword.

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.38. ROCKDIMS 474

Keywords for formats tN, E1, E3 19.1

12.1.39. WELLDIMS

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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 E1/E3 compatibility field. In

tNavigator number of wells does not have to be specified because the memory is allo-
cated dynamically;
Default: 0.

2. the maximum number of connections that one well can have, (IGNORED). This is an
E1/E3 compatibility field. In tNavigator number of connections does not have to be
specified because the memory is allocated dynamically;
Default: 0.

3. the maximum number of well groups in the model, (IGNORED). This is an E1/E3
compatibility field. In tNavigator number of well groups does not have to be specified
because the memory is allocated dynamically;
Default: 0.

4. the maximum number of wells in one group, (IGNORED). This is an E1/E3 compati-
bility field. In tNavigator number of wells in one group does not have to be specified
because the memory is allocated dynamically;
Default: 0.

5. the maximum number of separator stages (the last one - the stock tank - is included);
Default: 0.

6. the maximum number of well streams (WELLSTRE, see 12.19.184), (IGNORED). This
is an E1/E3 compatibility field. In tNavigator number of well streams does not have to
be specified because the memory is allocated dynamically;
Default: 0.

7. the maximum number of mixtures (using in injectors), (IGNORED). This is an E1/E3

compatibility field. In tNavigator number of mixtures does not have to be specified
because the memory is allocated dynamically;
Default: 0.

12.1.39. WELLDIMS 475

Keywords for formats tN, E1, E3 19.1

8. the maximum number of separators (field separator is included), (IGNORED). This is

an E1/E3 compatibility field. In tNavigator number of separators does not have to be
specified because the memory is allocated dynamically;
Default: 0.

9. the maximum number of items in any mixture (using in injectors), (IGNORED). This
is an E1/E3 compatibility field. In tNavigator number of items in any mixture does not
have to be specified because the memory is allocated dynamically;
Default: 0.

10. the maximum number of connections groups allowed to cross domain boundary of one
process during a parallel run, (IGNORED). This is an E1/E3 compatibility field. In
tNavigator number of connections groups does not have to be specified because the
memory is allocated dynamically;
Default: 0.

11. the maximum number of the well lists that one well can belong to simultaneously,
(IGNORED). This is an E1/E3 compatibility field. In tNavigator number of the well
lists does not have to be specified because the memory is allocated dynamically;
Default: 0.

12. the maximum number of dynamic well lists during the run, (IGNORED). This is an
E1/E3 compatibility field. In tNavigator number of dynamic well lists does not have to
be specified because the memory is allocated dynamically.
Default: 0.

Example
WELLDIMS
200 7 10 20 5 10 5 4 2 0 1 1
/

12.1.39. WELLDIMS 476

Keywords for formats tN, E1, E3 19.1

12.1.40. FAULTDIM

Data x tN x E1 E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets the number of faults entered via FAULTS (see 12.2.38). Other keywords
used to specify faults and their parameters are listed in the section 5.5.2. The data should be
terminated with a slash /.
The following parameters should be specified:

1. maximum number of faults specified via FAULTS (see 12.2.38); (IGNORED). This is an
E1/E3 compatibility field. In tNavigator number of faults does not have to be specified
because the memory is allocated dynamically.

Example
FAULTDIM
20 /

12.1.40. FAULTDIM 477

Keywords for formats tN, E1, E3 19.1

12.1.41. WSEGDIMS

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets dimensions for multi-segment wells (section 2.15). The data should be
terminated with a slash /.
The following data should be entered:

1. maximum number of multi-segment wells; (IGNORED). This is an E1/E3 compatibility

field. In tNavigator number of multi-segment wells does not have to be specified because
the memory is allocated dynamically;

2. maximum number of segments per well; (IGNORED). This is an E1/E3 compatibility

field. In tNavigator number of segments per well does not have to be specified because
the memory is allocated dynamically;

3. maximum number of branches per multi-segment well. (IGNORED). This is an E1/E3

compatibility field. In tNavigator number of branches per multi-segment well does not
have to be specified because the memory is allocated dynamically;

4. maximum number of segment chord links per well. (IGNORED). This is an E1/E3
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 7 4/

12.1.41. WSEGDIMS 478

Keywords for formats tN, E1, E3 19.1

12.1.42. HEATDIMS

Data x tN E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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 E1/E3 compatibility

field. In tNavigator this dimension does not have to be specified because the memory
is allocated dynamically.

Example
HEATDIMS
20 /

12.1.42. HEATDIMS 479

Keywords for formats tN, E1, E3 19.1

12.1.43. UDQDIMS

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets dimensions for the keyword UDQ (see 12.19.165). The data should be
terminated with a slash /.
The following data should be entered:
1. maximum number of functions (including brackets) that can be used in a quantity def-
inition in UDQ (see 12.19.165); (IGNORED). This is an E1/E3 compatibility field. In
tNavigator number of functions does not have to be specified because the memory is
allocated dynamically;
2. maximum number of arguments that can be used in a quantity definition; (IGNORED).
This is an E1/E3 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 E1/E3
compatibility field. In tNavigator number of defined connection quantities does not have
to be specified because the memory is allocated dynamically;
4. maximum number of user defined field quantities; (IGNORED). This is an E1/E3 com-
patibility field. In tNavigator number of field quantities does not have to be specified
because the memory is allocated dynamically;
5. maximum number of user defined group quantities; (IGNORED). This is an E1/E3 com-
patibility field. In tNavigator number of group quantities does not have to be specified
because the memory is allocated dynamically;
6. maximum number of user defined region quantities; (IGNORED). This is an E1/E3 com-
patibility field. In tNavigator number of region quantities does not have to be specified
because the memory is allocated dynamically;
7. maximum number of user defined segment quantities; (IGNORED). This is an E1/E3
compatibility field. In tNavigator number of segment quantities does not have to be
specified because the memory is allocated dynamically;
8. maximum number of user defined well quantities; (IGNORED). This is an E1/E3 com-
patibility field. In tNavigator number of well quantities does not have to be specified
because the memory is allocated dynamically;
9. maximum number of user defined aquifer quantities; (IGNORED). This is an E1/E3
compatibility field. In tNavigator number of aquifer quantities does not have to be
specified because the memory is allocated dynamically;

12.1.43. UDQDIMS 480

Keywords for formats tN, E1, E3 19.1

10. maximum number of user defined block quantities; (IGNORED). This is an E1/E3 com-
patibility 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.43. UDQDIMS 481

Keywords for formats tN, E1, E3 19.1

12.1.44. UDQPARAM

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets parameters for UDQ (see 12.19.165) keyword. The data should be ter-
minated with a slash /.
The following data should be entered:

1. (IGNORED). This is an E1/E3 compatibility field;

2. (IGNORED). This is an E1/E3 compatibility field;

3. a value given to undefined elements when outputting data or using in keywords AC-
TIONG (see 12.19.159), ACTIONR (see 12.19.160), ACTIONW (see 12.19.161), AC-
TIONX, see 12.19.162);

4. (IGNORED). This is an E1/E3 compatibility field.

Example
UDQPARAM
2* 0.01 /

12.1.44. UDQPARAM 482

Keywords for formats tN, E1, E3 19.1

12.1.45. UDADIMS

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets dimensions for user defined arguments UDA for the keyword UDQ
(see 12.19.165). The data should be terminated with a slash /.
User defined arguments UDA can be used in keywords WCONINJE (see 12.19.44), WE-
CON (see 12.19.74), WELDRAW (see 12.19.123), WCONPROD (see 12.19.42), GCONPROD
(see 12.19.86), GCONINJE (see 12.19.95), GECON (see 12.19.121).

The following data should be entered:

1. maximum number of user defined arguments for well keywords; (IGNORED). This is
an E1/E3 compatibility field. In tNavigator number of does not have to be specified
because the memory is allocated dynamically;

2. maximum number of user defined arguments for group keywords; (IGNORED). This
is an E1/E3 compatibility field. In tNavigator number of does not have to be specified
because the memory is allocated dynamically.

Example
UDADIMS
8 8 /

12.1.45. UDADIMS 483

Keywords for formats tN, E1, E3 19.1

12.1.46. UDTDIMS

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets dimensions for user defined tables UDT for the keyword UDT
(see 12.19.166). The data should be terminated with a slash /.
The following data should be entered:

1. maximum number of user defined tables UDT (see 12.19.166); (IGNORED). This is an
E1/E3 compatibility field. In tNavigator number of does not have to be specified because
the memory is allocated dynamically;

2. maximum number of rows in the table UDT (see 12.19.166); (IGNORED). This is an
E1/E3 compatibility field. In tNavigator number of does not have to be specified because
the memory is allocated dynamically;

3. maximum number of interpolation points in any one dimension; (IGNORED). This is

an E1/E3 compatibility field. In tNavigator number of does not have to be specified
because the memory is allocated dynamically;

4. maximum number of dimensions in one table UDT (see 12.19.166); (IGNORED). This
is an E1/E3 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.46. UDTDIMS 484

Keywords for formats tN, E1, E3 19.1

12.1.47. TCBDIMS

Data x tN E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies a dimension of temperature cutback tables. The keyword can be
used if thermal option is activated (THERMAL, see 12.1.54).
The following parameters describing the dimensions of the temperature cutback table data
used in the run should be specified:

1. the number of temperature cutback tables;

Default: 1.

2. the maximum number of rows in any TCB table.

Default: 10.

Example
TCBDIMS
1 10 /

12.1.47. TCBDIMS 485

Keywords for formats tN, E1, E3 19.1

12.1.48. TRACERS

Data x tN x E1 E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets dimensions for tracers. Other keywords used for tracer modeling are
given in the section 2.17.1. The data should be terminated with a slash /.
1. the maximum number of passive oil tracers (entered via the keyword TRACER,
see 12.7.10);
Default: 50.
2. the maximum number of passive water tracers (entered via the keyword TRACER,
see 12.7.10);
Default: 50.
3. the maximum number of passive gas tracers (entered via the keyword TRACER,
see 12.7.10);
Default: 50.
4. the maximum number of environmental tracers,
Default: 50.
5. ignored, this is an E1/E3 compatibility field,
6. ignored, this is an E1/E3 compatibility field,
7. ignored, this is an E1/E3 compatibility field,
8. ignored, this is an E1/E3 compatibility field,
9. ignored, this is an E1/E3 compatibility field,
10. ignored, this is an E1/E3 compatibility field,
11. ignored, this is an E1/E3 compatibility field,
12. ignored, this is an E1/E3 compatibility field.
Example
TRACERS
4 5
/

In this example there are: 4 passive oil tracers and 5 passive water tracers.

12.1.48. TRACERS 486

Keywords for formats tN, E1, E3 19.1

12.1.49. SURFACT

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword defines that surfactants will be used in the model (see section 2.23. Surfactant
injection).
Example
SURFACT

12.1.49. SURFACT 487

Keywords for formats tN, E1, E3 19.1

12.1.50. SURFACTW

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword defines that surfactants will be used in the model and change of wettability
will be simulated (see section 2.23. Surfactant injection).

Wettability calculation starts in case if one of the tables SURFDW (see 12.8.15) or SUR-
FADDW (see 12.8.14) is specified.
Example
SURFACTW

12.1.50. SURFACTW 488

Keywords for formats tN, E1, E3 19.1

12.1.51. POLYMER

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword indicates that Polymer Flood will be used in the model (see section
2.16. Polymer Flood).

For the full description of ASP (Alkaline-Surfactant-Polymer) mathematical model, see

the section 5.9. ASP model description.
Example
POLYMER

12.1.51. POLYMER 489

Keywords for formats tN, E1, E3 19.1

12.1.52. ALKALINE

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword indicates that Alkaline Flooding will be used in the model – section 2.22.

For the full description of ASP (Alkaline-Surfactant-Polymer) mathematical model, see

the section 5.9. ASP model description.

12.1.52. ALKALINE 490

Keywords for formats tN, E1, E3 19.1

12.1.53. NONNC

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

If this keyword is used, non-neighboring connections won’t be allowed. By default non-

neighboring connections are allowed. This keyword can be used for calculation of transmissi-
bility (see section 5.5.6).
Such connections may be set in various ways, including explicit definition with keyword
NNC (see 12.2.54).
Example
NONNC
In this example non-neighbouring connections are forbidden.

12.1.53. NONNC 491

Keywords for formats tN, E1, E3 19.1

12.1.54. THERMAL

Data x tN E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.15).
Example
THERMAL

12.1.54. THERMAL 492

Keywords for formats tN, E1, E3 19.1

12.1.55. REACTION

Data x tN E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies:

1. Number of chemical reactions (nr ).

2. Number of equilibrium correction terms (EQLDREAC, see 12.15.71).

3. Number of equilibrium constants (K-values) used in the correction terms (EQLDKVCR,

see 12.15.72).

The data should be terminated with a slash /.

Example
REACTION
3 2 2 /
In this example there are 3 chemical reactions, 2 equilibrium correction terms, and 2
equilibrium constants.

12.1.55. REACTION 493

Keywords for formats tN, E1, E3 19.1

12.1.56. OIL

Data x tN x E1 E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword is used to label that a model contains an oil phase (see sections 2.9.1 and
2.9.2). 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.56. OIL 494

Keywords for formats tN, E1, E3 19.1

12.1.57. GAS

Data x tN x E1 E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword is used to label that a model contains a gas phase (see section 2.9.2). 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.57. GAS 495

Keywords for formats tN, E1, E3 19.1

12.1.58. WATER

Data x tN x E1 E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword is used to label that a model contains a water phase (active) (see sections
2.9.1 and 2.9.2). No parameters are to be specified.

12.1.58. WATER 496

Keywords for formats tN, E1, E3 19.1

12.1.59. VAPOIL

Data x tN x E1 E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword is used to label that there is vaporised oil in a wet gas (see section 2.9.2).
One can use this keyword only if OIL (see 12.1.56) and GAS (see 12.1.57) are specified.

Let’s 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.56) and VAPOIL shouldn’t be specified; gas should be considered as a dry gas;
specify vaporised oil concentration using keyword RVCONST (see 12.5.15) 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.59. VAPOIL 497

Keywords for formats tN, E1, E3 19.1

12.1.60. DISGAS

Data x tN x E1 E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword is used to label that there is a dissolved gas in live oil (see section 2.9.2).
One can use this keyword only if OIL (see 12.1.56) and GAS (see 12.1.57) are specified.
Let’s 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 efficiency
in the following way:
GAS (see 12.1.57) and DISGAS shouldn’t be specified; oil should be considered as a dead
oil; specify dissolved gas concentration using keywords RSCONST (see 12.5.13), RSCONSTT
(see 12.5.14) 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.
No parameters are to be specified.

12.1.60. DISGAS 498

Keywords for formats tN, E1, E3 19.1

12.1.61. SOLID

Data x tN E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword is used to label that there is a solid phase in the model (solid phase consists
of one component – coke). A compositional thermal model is described in details in the section
4 along with all used formulas and keywords.

12.1.61. SOLID 499

Keywords for formats tN, E1, E3 19.1

12.1.62. BRINE

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword indicates that the Brine Tracking option is enabled, to allow the modeling
of waters with different salinities.

12.1.62. BRINE 500

Keywords for formats tN, E1, E3 19.1

12.1.63. LOWSALT

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword indicates that low salinity option is used – 2.24.3.

This keyword automatically turns on the option BRINE (see 12.1.62) – simulation of waters
with different salinities – section 2.24.1.

12.1.63. LOWSALT 501

Keywords for formats tN, E1, E3 19.1

12.1.64. TEMP

Data x tN x E1 E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword indicates that the temperature option for a model in E1 format is enabled.
It allows the modeling of the temperature effects, including the injection of water which is
colder or hotter than the reservoir. The temperature is only considered for active blocks with
non-zero pore volume, see 2.26.

12.1.64. TEMP 502

Keywords for formats tN, E1, E3 19.1

12.1.65. TEMPR

Data x tN x E1 E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is the same as TEMP (see 12.1.64), with the only difference that grid blocks
with zero pore volume are considered in simulation (unless they are disabled via ACTNUM,
see 12.2.29). There is no fluid flow in these blocks, but their heat capacity will be taken into
account in temperature calculations.

12.1.65. TEMPR 503

Keywords for formats tN, E1, E3 19.1

12.1.66. API

Data x tN x E1 E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword indicates that the API tracking option is enabled, see 2.8.8.

12.1.66. API 504

Keywords for formats tN, E1, E3 19.1

12.1.67. ASPHALTE

Data x tN E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword indicates that the asphaltene modeling option is enabled – 2.21. The follow-
ing 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;
• Default: WEIGHT.

2. permeability damage model. IGNORED, this is an E1/E3 compatibility field;

3. viscosity model:

• EI – Einstein model (highly diluted solution), one parameter;

• KD – Krieger-Dougherty model, two parameters;
• TAB – viscosity multiplier is set as a function of the asphaltene concentration;
• NO – viscosity is not changed;
• Default: NO.

If the 3-rd parameter is not NO, then keyword ASPVISO (see 12.10.7) must be used.
The data should be terminated with a slash /.

Example
ASPHALTE
WEIGHT 1* TAB /

12.1.67. ASPHALTE 505

Keywords for formats tN, E1, E3 19.1

12.1.68. FOAM

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

That keyword indicates that the foam modeling option is enabled – 2.18. The data should
be terminated with a slash /.

12.1.68. FOAM 506

Keywords for formats tN, E1, E3 19.1

12.1.69. MISCIBLE

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword allows a miscible treatment of hydrocarbon relative permeabilities and cap-
illary pressures for calculations where miscible displacement is taken into account. However,
the treatment defers for different model’s formats. For models in E1 formats this keyword ac-
tivates a miscible flood model based on the Todd-Longstaff empirical approach (the detailed
description of this model is given in the section 2.6.13). For models in E3 formats this keyword
defines the dependence of relative permeability and capillary pressure on surface tensions (see
section 2.6.12) according to values defined by the keyword PARACHOR (see 12.6.80).

E1 format.
The keyword is followed by the following parameters:

1. The number of tables of miscible residual oil saturation versus a water saturation. The
maximum number of mixing areas (see the keywords TLMIXPAR (see 12.6.86) and
SORWMIS (see 12.6.85) in the PROPS section). (IGNORED) This is an E1/E3 compat-
ibility field. In tNavigator number of tables does not have to be specified because the
memory is allocated dynamically.
Default: 1.

E3 format.
For this format above indicated parameters are not required. All values will be ignored.
Parachor values should be defined in the PROPS section using the keyword PARACHOR
(see 12.6.80). Or you can define a variation of surface tension with pressure using the keyword
STVP (see 12.8.43).
Example
MISCIBLE
/

12.1.69. MISCIBLE 507

Keywords for formats tN, E1, E3 19.1

12.1.70. DIFFUSE

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

That keyword indicates that an option of molecular diffusion is enabled.

The keyword doesn’t have any parameters.

The diffusion coefficients are specified via DIFFCGAS (see 12.14.58), DIFFCOIL
(see 12.14.59).

12.1.70. DIFFUSE 508

Keywords for formats tN, E1, E3 19.1

12.1.71. DIFFX

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID x EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies diffusivity values (METRIC: m, FIELD: f t ) between blocks

[I, J, K] and [I + 1, J, K], overwriting values calculated by the program. The molecular dif-
fusion option should be activated in a grid (using the DIFFUSE (see 12.1.70) keyword). Not
overwritten diffusivities remain at the values calculated by the program based on the GRID
data.
The keyword is optional. It should be followed by one non-negative number for each grid
block. The data should be terminated by a slash /.
Note: DIFFX does not affect non-neighbor connections generated by faults.
Example
DIMENS
9 9 9
/
...
DIFFX
729*10
/

In this example diffusivities is equal to 10 for the +X face of each grid block.

12.1.71. DIFFX 509

Keywords for formats tN, E1, E3 19.1

12.1.72. DIFFY

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID x EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies diffusivity values (METRIC: m, FIELD: f t ) between blocks

[I, J, K] and [I, J + 1, K], overwriting values calculated by the program. The molecular dif-
fusion option should be activated in a grid (using the DIFFUSE (see 12.1.70) keyword). Not
overwritten diffusivities remain at the values calculated by the program based on the GRID
data.
The keyword is optional. It should be followed by one non-negative number for each grid
block. The data should be terminated by a slash /.
Note: DIFFY does not affect non-neighbor connections generated by faults.
Example
DIMENS
9 9 9
/
...
DIFFY
729*10
/

In this example diffusivities is equal to 10 for the +Y face of each grid block.

12.1.72. DIFFY 510

Keywords for formats tN, E1, E3 19.1

12.1.73. DIFFZ

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID x EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies diffusivity values (METRIC: m, FIELD: f t ) between blocks

[I, J, K] and [I, J + 1, K], overwriting values calculated by the program. The molecular dif-
fusion option should be activated in a grid (using the DIFFUSE (see 12.1.70) keyword). Not
overwritten diffusivities remain at the values calculated by the program based on the GRID
data.
The keyword is optional. It should be followed by one non-negative number for each grid
block. The data should be terminated by a slash /.
Note: DIFFZ does not affect non-neighbor connections generated by faults.
Example
DIMENS
9 9 9
/
...
DIFFZ
729*10
/

In this example diffusivities is equal to 10 for the +Z face of each grid block.

12.1.73. DIFFZ 511

Keywords for formats tN, E1, E3 19.1

12.1.74. CART

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword indicates that a Cartesian geometry is used. Cartesian geometry is used by
default so this keyword is not necessary. tNavigator doesn’t support radial geometry.

The keyword doesn’t have any parameters.

12.1.74. CART 512

Keywords for formats tN, E1, E3 19.1

12.1.75. SATOPTS

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword provides the following relative permeabilities options:

• DIRECT – directional relative permeabilities (see section 2.6.9 Directional and irre-
versible RP). 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.23),
KRNUMY (see 12.4.23), KRNUMZ, see 12.4.23). 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 (see section 2.6.9 Directional

and irreversible RP). 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.23), KRNUMX- (see 12.4.23), KRNUMY (see 12.4.23),
KRNUMY- (see 12.4.23), KRNUMZ (see 12.4.23) and KRNUMZ- (see 12.4.23);

• HYSTER – hysteresis relative permeabilities (see section 2.7);

• 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.87)
and STOW (see 12.6.88).
The list of the options should be terminated with /.

Hysteresis option allows to specify different saturation functions for drainage (decreasing
wetting phase saturation) and imbibition (increasing wetting phase saturation) processes. Hys-
teresis option is specified via keyword SATOPTS (see 12.1.75) (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 specified
via the keyword EHYSTR (see 12.6.67).

If DIRECT is used with hysteresis, then for each direction I, J and K the imbibition ta-
bles should be specified (IMBNUMX (see 12.4.7), IMBNUMY (see 12.4.7) and IMBNUMZ,

12.1.75. SATOPTS 513

Keywords for formats tN, E1, E3 19.1

see 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.75. SATOPTS 514

Keywords for formats tN, E1, E3 19.1

12.1.76. NUMRES

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets a number of reservoirs (if the is more than one reservoir). Other key-
words used to specify several reservoirs of model are listed in the section 5.5.3.
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.47) and the bounds of reservoirs should be specified using the keyword COORDSYS
(see 12.2.48).
The data should be terminated with a slash /.

Default: 1.

Example
NUMRES
4
/

12.1.76. NUMRES 515

Keywords for formats tN, E1, E3 19.1

12.1.77. KVALUES

Data x tN E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword defines that K-values (partition coefficients) will be used to control liquid-
vapor phase equilibrium. K-values are entered via the keyword KVTABLE (see 12.14.19).
Example
KVALUES

The keyword has no parameters.

12.1.77. KVALUES 516

Keywords for formats tN, E1, E3 19.1

12.1.78. ISGAS

Data x tN E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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

The keyword has no parameters.

12.1.78. ISGAS 517

Keywords for formats tN, E1, E3 19.1

12.1.79. NOMIX

Data x tN E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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

The keyword has no parameters.

12.1.79. NOMIX 518

Keywords for formats tN, E1, E3 19.1

12.1.80. INCLUDE

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION x SUMMARY x SCHEDULE

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 – see
Example 2.
Only one file may be specified after INCLUDE keyword.
This keyword INCLUDE allows to include directly to the .data file files in the archive
.gz. Only one file may be inside one archive. The size limitation for file in Windows is 2Gb.
Several archives may be included via several keywords INCLUDE – see Example 3.

Example 1.
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 2.
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.

Example 3. In this example there are the following files on the disc: a.inc.gz (archive),
b.inc, c.inc, c.inc.gz (archive), d.inc.gz (archive). In example below only the data from the
following files will be available in the model: a.inc.gz, b.inc, c.inc, d.inc.gz.

12.1.80. INCLUDE 519

Keywords for formats tN, E1, E3 19.1

Example
INCLUDE
a.inc /
INCLUDE
b.inc /
INCLUDE
c.inc /
INCLUDE
d.inc /

12.1.80. INCLUDE 520

Keywords for formats tN, E1, E3 19.1

12.1.81. PATHS

Data x tN x E1 E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.80), IMPORT (see 12.2.109), RESTART (see 12.16.3)
and GDFILE (see 12.2.49).
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 /.
The following parameters should be specified:

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.81. PATHS 521

Keywords for formats tN, E1, E3 19.1

12.1.82. IMPLICIT

Data x tN x E1 E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword is used to set the implicit solution procedure for the simulation.
Example
IMPLICIT

12.1.82. IMPLICIT 522

Keywords for formats tN, E1, E3 19.1

12.1.83. DUALPORO

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets that the Dual porosity option ( 2.27) 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 using
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 specified by the keyword DUALPORO.

Dual permeability — DUALPERM (see 12.1.84).

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 or DUALPERM (see 12.1.84) 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.28) (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.83. DUALPORO 523

Keywords for formats tN, E1, E3 19.1

12.1.84. DUALPERM

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets that the Dual permeability option will be used in the run.
This option allows fluid flows between matrix cells ( 2.27).

Example
DUALPERM

12.1.84. DUALPERM 524

Keywords for formats tN, E1, E3 19.1

12.1.85. COAL

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets that the Coal Bed Methane option will be used – 2.28.

12.1.85. COAL 525

Keywords for formats tN, E1, E3 19.1

12.1.86. GRAVDR

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword switches on an option of gravity drainage between matrix and fracture cells
for dual porosity models – 2.27.2).

If this keyword is used Z-dimensions for matrix blocks parts should be specified via
DZMTRX (see 12.2.80), DZMTRXV (see 12.2.82).
Example
GRAVDR
/

12.1.86. GRAVDR 526

Keywords for formats tN, E1, E3 19.1

12.1.87. GRAVDRM

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword switches on an option of alternative gravity drainage between matrix and
fracture cells for dual porosity models – 2.27.2). The data should be terminated with a slash /.

The keyword can be use instead of GRAVDR (see 12.1.86).

The following parameters should be specified:

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: YES.

Example
GRAVDRM
NO/

12.1.87. GRAVDRM 527

Keywords for formats tN, E1, E3 19.1

12.1.88. LGR

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets options and dimensions for local grid refinement (LGR) – section 5.5.8.
The data should be terminated with a slash /.
The following parameters should be specified:

1. maximum number of LGRs in the model. This is an E1/E3 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 E1/E3 compatibility field. (IG-
NORED) In tNavigator specification of this number is not obligatory, because memory
is allocated dynamically;

3. maximum number of amalgamated coarse cells. This is an E1/E3 compatibility field.

(IGNORED) In tNavigator specification of this number is not obligatory, because
memory is allocated dynamically;

4. maximum number of LGR amalgamations. This is an E1/E3 compatibility field. (IG-

NORED) In tNavigator specification of this number is not obligatory, because memory
is allocated dynamically;

5. maximum number of LGRs in any amalgamation. This is an E1/E3 compatibility field.

(IGNORED) In tNavigator specification of this number is not obligatory, because mem-
ory is allocated dynamically;

6. This is an E1/E3 compatibility field. (IGNORED)

7. This is an E1/E3 compatibility field. (IGNORED)

8. This is an E1/E3 compatibility field. (IGNORED)

12.1.88. LGR 528

Keywords for formats tN, E1, E3 19.1

12.1.89. VISCD

Data x tN x E1 E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets that the Viscous displacement option will be used in the dual porosity
run ( 2.27).
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.69), LY (see 12.2.69), LZ (see 12.2.69).

Viscous Displacement. 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 per-
meability is high, the matrix-fracture viscous displacement under the influence of pressure
gradient isn’t 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.72) factor using keywords LX (see 12.2.69), LY
(see 12.2.69), LZ (see 12.2.69) and LTOSIGMA (see 12.2.74). If tNavigator compute SIGMA,
any manually input of this parameter (SIGMA, see 12.2.72) in data file will be ignored.

Example
VISCD

12.1.89. VISCD 529

Keywords for formats tN, E1, E3 19.1

12.1.90. NODPPM

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword NODPPM cancels a multiplication of permeability (for the fracture blocks)
by porosity (fracture blocks) during the dual porosity run (2.27). 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.90. NODPPM 530

Keywords for formats tN, E1, E3 19.1

12.1.91. NETWORK

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets dimensions for extended network model. The extended network model
is specified via keywords NODEPROP (see 12.19.103), BRANPROP (see 12.19.102). The data
should be terminated with a slash /.
For the description of the extended network model see 2.14.11. NETWORK option. Au-
tomatic chokes. Compressors.
The following parameters should be specified:

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.91. NETWORK 531

Keywords for formats tN, E1, E3 19.1

12.1.92. CO2SOL

Data x tN E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword turns on the CO 2 solution option. The CO 2 component is then allowed to
exist in all three phases. All keywords used for the CO 2 /H 2 S solution option are given in the
section 3.3.1.
Example
CO2SOL

12.1.92. CO2SOL 532

Keywords for formats tN, E1, E3 19.1

12.1.93. H2SSOL

Data x tN E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword turns on the H 2 S solution option. The H 2 S component is then allowed to
exist in all three phases. All keywords used for the CO 2 /H 2 S solution option are given in the
section 3.3.1.
Example
H2SSOL

12.1.93. H2SSOL 533

Keywords for formats tN, E1, E3 19.1

12.1.94. EQLOPTS

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies options for the initial equilibration algorithm. The data should be
terminated with a slash /.
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.16.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 doesn’t allow flow between different equilibration regions until the potential
difference exceeds a threshold value (keyword THPRES, see 12.16.11). This option is
also required if faults have threshold pressures (keyword THPRESFT, see 12.2.40).

• IRREVERS – this option allows the threshold pressures for flow in each direction be-
tween equilibration regions to be different. Threshold pressures should be specified for
each direction; option THPRES should be used.

• NONEQSAT – this option indicates that the initial saturations values derived from
EQUIL (see 12.16.2) will be overwritten by SWAT (see 12.16.14) and/or SGAS
(see 12.16.15) in case of mixed initialization. The recalculation algorithm is described
in section 2.3.3.

! It is not recommended to use this option if initial water saturation is

defined by SWATINIT (see 12.6.65).

Example
EQLOPTS
THPRES /

12.1.94. EQLOPTS 534

Keywords for formats tN, E1, E3 19.1

12.1.95. GRIDOPTS

Data x tN x E1 E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword set options for grid data processing. The data should be terminated with a
slash /.
The following parameters should be specified:

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 E1/E3 com-
patibility field

2. maximum number of MULTNUM (see 12.4.22) regions. If this value is greater than
zero, then in the keyword MULTREGP (see 12.3.16) MULTNUM regions are used. Else
– regions FLUXNUM (see 12.4.18);
Default: 0.

3. maximum number of pinchout regions PINCHNUM (see 12.2.62);

Default: 0.

Example
GRIDOPTS
NO 4/

12.1.95. GRIDOPTS 535

Keywords for formats tN, E1, E3 19.1

12.1.96. FORMOPTS

Data x tN E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keywords specifies the options for gas-oil capillary pressure treatment. The data
should be terminated with a slash /.

The following options can be used (switched off by default):

• HCSCAL – this option performs additional scaling hydrocarbon relative permeabilities.
In compostional model oil can change to gas without passing through a two-phase
state. The hydrocarbon relative permeabilities are interpolated to get a smooth transition
between the two states. If the gas relative permeability at connate water is not equal to
the oil relative permeability then a discontinuity can occur in the hydrocarbon relative
permeability. In order to avoid discontinuity the HCSCAL option scales gas relative
permeability near the critical point in an analogous manner to the hydrocarbon relative
permeability.
• NOHCSCAL – this option turns off the option HCSCAL. HCSCAL turns off automati-
cally if the Surfactant Model is active (see section 2.23). Option NOHCSCAL is set 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, corre-
sponding 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 disconti-
nuities 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

12.1.96. FORMOPTS 536

Keywords for formats tN, E1, E3 19.1

SG
pG = p + pcOG
SO + SG

Example
FORMOPTS
NOPCSPT/

12.1.96. FORMOPTS 537

Keywords for formats tN, E1, E3 19.1

12.1.97. NOSIM

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword turns off time step simulation in the SCHEDULE section, tNavigator contin-
ues to read and check the data.
Example
NOSIM

12.1.97. NOSIM 538

Keywords for formats tN, E1, E3 19.1

12.1.98. GASFIELD

Data x tN x E1 E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword turns on special options of Gas Field Model – section 2.14.8.

The following parameters should be specified (The data should be terminated with a slash
/.):

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.98. GASFIELD 539

Keywords for formats tN, E1, E3 19.1

12.1.99. GEOMECH

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies that will be used geomechanical model describing the elastic de-
formation of the rock – section 2.29. In this case in addition to to the fluid mass and energy
conservation a rock stress (force) conservation in each coordinate direction is calculated. The
keyword is followed by a single record indicating a method for the solution of the fluid
filtration and elastic deformation of the rock problems:

• FE – fully coupled method: at each step of simulator the joint system of coupled equa-
tions describing filtration processes in reservoir and geomechanical effects is solved (see
section 2.29.1). The finite element method is used for rock stresses calculation;

• EX – successive method: the fluid filtration problem and elastic deformation of the rock
problem are solved independently and successively (see section 2.29.2);

• Default: FE.

The data should be terminated with a slash /.

Example
GEOMECH
1* 1* ’FE’ /
/

12.1.99. GEOMECH 540

Keywords for formats tN, E1, E3 19.1

12.1.100. GEODIMS

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies dimensions of geomechanics data to be used in calculations. This

keyword is only valid if the keyword GEOMECH (see 12.1.99) (option FE) is set in the section
RUNSPEC. The detailed description of geomechanical model is given in section 2.29.1.
The following dimensions can be specified:

1. number of geomechanics regions in the model (IGNORED, this is an E1/E3 compati-

bility field);

2. number of rows in a permeability multiplieres table specified by keyword PERMSTAB

(see 12.5.25);

3. number of columns in a permeability multiplieres table specified by keyword

PERMSTAB (see 12.5.25).

The data should be terminated by a slash /.

By default:

• number of rows in a permeability multiplieres table specified by keyword PERMSTAB

(see 12.5.25): 1;

• number of columns in a permeability multiplieres table specified by keyword

PERMSTAB (see 12.5.25): 1.

Example
GEODIMS
1* 3 4 /

12.1.100. GEODIMS 541

Keywords for formats tN, E1, E3 19.1

12.1.101. RFD_WFRAC

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword defines that hydraulic fracture keywords will be used in the model:
WFRAC (see 12.19.143), COMPFRAC (see 12.19.148), WFRACP (see 12.19.145), WFRACL
(see 12.19.144), COMPFRACL (see 12.19.149), WFRACPL (see 12.19.146). Keyword is op-
tional, i.e. the keywords above can be used without it.

No parameters are to be specified.

Example
RFD_WFRAC

12.1.101. RFD_WFRAC 542

Keywords for formats tN, E1, E3 19.1

12.1.102. AIM

Data x tN E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword enables an AIM (adaptive implicit) solution option. Time approximation
numerical methods used in tNavigator is described in the section 5.3.

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.19.140) or use the keyword AIM
(see 12.1.102).

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.19.140). Description of AIM 1, AIM 2, ..
is in the keyword RUNCTRL (see 12.19.140).

Use the keyword AIMCTRL (see 12.1.5) to sets the parameters of adaptive implicit method
(AIM).

12.1.102. AIM 543

Keywords for formats tN, E1, E3 19.1

12.1.103. AIMFRAC

Data x tN E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword enables an AIM (adaptive implicit) solution option.

This keyword is IGNORED because of specific methods of solution used in tNavigator.
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.19.140) or use the keyword AIM
(see 12.1.102).

Use the keyword AIMCTRL (see 12.1.5) to sets the parameters of adaptive implicit method
(AIM).

12.1.103. AIMFRAC 544

Keywords for formats tN, E1, E3 19.1

12.1.104. ECHO / NOECHO

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION x SUMMARY x SCHEDULE

These keyword specify echo output for other simulators working in E1/E3 formats.
This keyword is IGNORED because of specific output options used in tNavigator (RPTRST,
see 12.16.5).

12.1.104. ECHO / NOECHO 545

Keywords for formats tN, E1, E3 19.1

12.1.105. IMPES

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword enables an IMPES solution option.

This keyword is IGNORED because of specific methods of solution used in tNavigator.
Detailed description of tNavigator algorithms and keywords to control them is available in the
section 5.

12.1.105. IMPES 546

Keywords for formats tN, E1, E3 19.1

12.1.106. FULLIMP

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword enables a fully 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.19.140) or use the keyword AIM
(see 12.1.102).
Detailed description of tNavigator algorithms and keywords to control them is available in the
section 5.

12.1.106. FULLIMP 547

Keywords for formats tN, E1, E3 19.1

12.1.107. HWELLS

Data x tN E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.19.6) in E1/E3. For tNavigator
this keyword is IGNORED and Z-direction can be used without this keyword.

12.1.107. HWELLS 548

Keywords for formats tN, E1, E3 19.1

12.1.108. PETOPTS

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

One option of this keyword is supported: TRANPORV.

The data entry must be terminated with a slash /.

TRANPORV option defines what connection types will be used for transmissibility calcu-
lation.

If this option is enabled then the following connection types will be taken into account:

• NNC (see 12.2.54) connections;

• Explicitly defined transmissibilities (TRANX (see 12.2.50), TRANY (see 12.2.51),

TRANZ, see 12.2.52),

• Grid connections to Aquifer

• Matrix-to-Fracture links.

All pinch-outs (PINCH, see 12.2.58) and auto-generated block-to-block links will be ignored.

! This option is not compatible with block-centered grid geometry (defined via
DX / DY / DZ, see 12.2.2).

Example
PETOPTS
TRANPORV /

12.1.108. PETOPTS 549

Keywords for formats tN, E1, E3 19.1

12.1.109. PARALLEL / PARAOPTS

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

These keywords set the parallel calculation option.

This keyword is IGNORED because of specific methods of solution used in tNavigator.

12.1.109. PARALLEL / PARAOPTS 550

Keywords for formats tN, E1, E3 19.1

12.1.110. NPROCX / NPROCKY

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

These keywords set the parallel calculation option.

This keyword is IGNORED because of specific methods of solution used in tNavigator.

12.1.110. NPROCX / NPROCKY 551

Keywords for formats tN, E1, E3 19.1

12.1.111. MESSAGE / MESSAGES / MSGFILE

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION x SUMMARY x SCHEDULE

These keywords set the parameters of E1/E3 messages.

This keyword is IGNORED because of specific output options used in tNavigator (RPTRST,
see 12.16.5).

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.111. MESSAGE / MESSAGES / MSGFILE 552

Keywords for formats tN, E1, E3 19.1

12.1.112. WARN / NOWARN / NOWARNEP

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION x SUMMARY x SCHEDULE

These keywords sets the parameters of E1/E3 warnings.

This keyword is IGNORED because of specific output options used in tNavigator (RPTRST,
see 12.16.5).

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.112. WARN / NOWARN / NOWARNEP 553

Keywords for formats tN, E1, E3 19.1

12.1.113. END

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION x SUMMARY x SCHEDULE

The keyword terminates the input of data in data file. This keyword doesn’t have any
parameters.
Example
END

12.1.113. END 554

Keywords for formats tN, E1, E3 19.1

12.1.114. ECINIT

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets values of global economical parameters:

1. Initial capital ($);

2. Discount rate (%);

3. Discount starting time step number.

By these data and keywords’ ECDATES (see 12.1.115) and ECVAL (see 12.1.116) ones
Net Present Value Graph will be calculated. See detailed description of this feature in cor-
responding section of tNavigator User Guide.
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.114) sets values of initial capital (10000000
$) and discount rate (11.4 %). Discount starting time step number is 25.

12.1.114. ECINIT 555

Keywords for formats tN, E1, E3 19.1

12.1.115. ECDATES

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets data list. For these dates values of economical parameters (price of oil,
gas and so on) will be set.

By these data and by keywords’ ECINIT (see 12.1.114) and ECVAL (see 12.1.116) ones
Net Present Value Graph will be calculated. See detailed description of this feature in corre-
sponding section of tNavigator User Guide. tNavigator uses interpolated values from ECVAL
(see 12.1.116) to calculate net present value NPV at reporting time steps.

The data should be terminated with a slash /.

Example
ECDATES
1 Jan 2020
3 Feb 2020
16 Jun 2020
21 Sep 2021
1 Dec 2021
/

12.1.115. ECDATES 556

Keywords for formats tN, E1, E3 19.1

12.1.116. ECVAL

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets values of economical parameters. tNavigator uses interpolated values
from ECVAL (see 12.1.116) 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.115) 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);

• SRVWINJ – maintenance cost of a injection well (c.u./well/year);

12.1.116. ECVAL 557

Keywords for formats tN, E1, E3 19.1

• 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) (%).

By these data and by keywords’ ECINIT (see 12.1.114) and ECDATES (see 12.1.115)
ones Net Present Value Graph will be calculated. See detailed description of this feature in
corresponding section of tNavigator User Guide.
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.116) 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.116. ECVAL 558

Keywords for formats tN, E1, E3 19.1

12.1.117. SCDPDIMS

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.19.252) and
SCDATAB (see 12.19.254). The data should be terminated with a slash /.
Section Scale deposition model – 2.25.

The following parameters should be specified:

1. the number of scale deposition tables to be entered in the keyword SCDPTAB

(see 12.19.252);
Default: 0.

2. IGNORED. This is an E1/E3 compatibility field. The maximum number of entries in

any scale deposition table;
Default: 0.

3. the number of scale damage tables to be entered in the keyword SCDATAB

(see 12.19.254);
Default: 0.

4. IGNORED. This is an E1/E3 compatibility field. The maximum number of entries in

any scale damage table;
Default: 0.

Example
SCDPDIMS
1 5 1 5 /

12.1.117. SCDPDIMS 559

Keywords for formats tN, E1, E3 19.1

12.1.118. LGRCOPY

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword allows blocks of refined grid (the keyword LGR, see 12.1.88) to inherit
formation properties from parent grid host blocks. Full description of local grid refinements
(LGR) and corresponding keywords is given in the section 5.5.8.

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.97) 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.97), ENDFIN (see 12.2.101) – 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.118. LGRCOPY 560

Keywords for formats tN, E1, E3 19.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

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 it’s 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.118. LGRCOPY 561

Keywords for formats tN, E1, E3 19.1

12.1.119. BIGMODEL

Data x tN x E1 E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is used to run big models in simulator E1/E3.

This keyword is IGNORED in tNavigator because of different data input-output.

12.1.119. BIGMODEL 562

Keywords for formats tN, E1, E3 19.1

12.1.120. JALS

Data x tN E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets the usage of linear solver JALS for thermal problems in E1/E3 .
This keyword is IGNORED in tNavigator.

Solution methods that are used in tNavigator are described in the section 5.

12.1.120. JALS 563

Keywords for formats tN, E1, E3 19.1

12.1.121. SKIPSTAB

Data x tN E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets the solution method for compositional problems in E1/E3.
This keyword is IGNORED in tNavigator.

Solution methods that are used in tNavigator are described in the section 5.

12.1.121. SKIPSTAB 564

Keywords for formats tN, E1, E3 19.1

12.1.122. LICENSES

Data x tN x E1 E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets license parameters for other simulators working in E1/E3 formats.
This keyword is IGNORED in tNavigator because of different license policy.

12.1.122. LICENSES 565

Keywords for formats tN, E1, E3 19.1

12.1.123. MEMORY

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets parameters of memory allocation for other simulators working in E1/E3
formats.
This keyword is IGNORED in tNavigator because of different memory allocation.

12.1.123. MEMORY 566

Keywords for formats tN, E1, E3 19.1

12.1.124. FMTIN/ FMTSAVE

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

These keywords define parameters for RESTART files of E1/E3.

This keyword is IGNORED because of specific output options used in tNavigator (RPTRST,
see 12.16.5).

In tNavigator restart is possible only if the base model is calculated in tNavigator. The
keyword RESTART (see 12.16.3).

12.1.124. FMTIN/ FMTSAVE 567

Keywords for formats tN, E1, E3 19.1

12.1.125. MULTIN/ MULTSAVE

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

These keywords define parameters for RESTART files of E1/E3.

This keyword is IGNORED because of specific output options used in tNavigator (RPTRST,
see 12.16.5).

In tNavigator restart is possible only if the base model is calculated in tNavigator. The
keyword RESTART (see 12.16.3).

12.1.125. MULTIN/ MULTSAVE 568

Keywords for formats tN, E1, E3 19.1

12.1.126. MONITOR/ NOMONITO

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

These keywords define parameters of run-time monitoring for other simulators working in
E1/E3 formats.
This keyword is IGNORED because of specific output options used in tNavigator (RPTRST,
see 12.16.5).

In tNavigator calculation run-time monitoring is always available in graphical user inter-

face.

12.1.126. MONITOR/ NOMONITO 569

Keywords for formats tN, E1, E3 19.1

12.1.127. PSPLITX/ PSPLITY/ PSPLITZ

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

These keywords set blocks’ division between MPI processes in parallel version of E1/E3.
This keyword is IGNORED. In MPI-version of tNavigator automatic balancing of active grid
blocks between MPI processes is used.

12.1.127. PSPLITX/ PSPLITY/ PSPLITZ 570

Keywords for formats tN, E1, E3 19.1

12.1.128. RPTHMD/ RPTHMG/ RPTHMW

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

These keywords set parameters of HMD files for other simulators working in E1/E3 for-
mats.
This keyword is IGNORED because of specific output options used in tNavigator (RPTRST,
see 12.16.5).

12.1.128. RPTHMD/ RPTHMG/ RPTHMW 571

Keywords for formats tN, E1, E3 19.1

12.1.129. RPTISOL/ RPTPROPS/ RPTREGS/ RPTRUNSP/ RPTSCHED/ RPTSMRY/

RPTSOL

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION x SUMMARY x SCHEDULE

These keywords set parameters of results files for other simulators working in E1/E3 for-
mats.
This keyword is IGNORED because of specific output options used in tNavigator (RPTRST,
see 12.16.5).

12.1.129. RPTISOL/ RPTPROPS/ RPTREGS/ RPTRUNSP/ RPTSCHED/ RPTSMRY/ RPTSOL572

Keywords for formats tN, E1, E3 19.1

12.1.130. UNIFIN/ UNIFSAVE

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

These keywords define parameters of RESTART files for other simulators working in
E1/E3 formats.
This keyword is IGNORED because of specific output options used in tNavigator (RPTRST,
see 12.16.5).

In tNavigator restart is possible only if the base model is calculated in tNavigator. The
corresponding keyword is RESTART (see 12.16.3).

12.1.130. UNIFIN/ UNIFSAVE 573

Keywords for formats tN, E1, E3 19.1

12.1.131. PVTGEN

Data x tN x E1 E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.
The following parameters should be specified:

1. the number of components;

2. minimal pressure (METRIC: barsa; FIELD: psia);

Default: pressure value defined in STCOND (see 12.14.11).

3. maximal pressure (METRIC: barsa; FIELD: psia);

Default: 100 × minimal pressure.

4. the number of pressure values for which PVT tables will be calculated;
Default: 50.

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;

The data should be terminated with a slash /.

Example
PVTGEN
5 1* 1* 1* NONE PVDG /

12.1.131. PVTGEN 574

Keywords for formats tN, E1, E3 19.1

12.1.132. CBMOPTS

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword is used to set preferences for the Coal Bed Methane Model (see section
2.28). It can be used only if this option is activated by the keyword COAL (see 12.1.85).
The following parameters should be specified:

1. adsorption model:

• INSTANT – in this case adsorption time tends to zero; flows between blocks are
absent, adsorption is considered as an additional source.
• TIMEDEP – in this case adsorption is considered a gradual process with rate de-
pendent on DIFFCOAL (see 12.9.1).
Default: TIMEDEP.

The data should be terminated with a slash /.

Example
CBMOPTS
INSTANT /

12.1.132. CBMOPTS 575

Keywords for formats tN, E1, E3 19.1

12.1.133. DPCDT

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets the maximum rate of change of capillary pressure in explicit cells. In-
stead of setting the capillary pressure the limit is set at which it can change from step to step.
If this keyword is not specified then tNavigator uses the mode without maximum rate of
change of capillary pressure in explicit cells – NODPCDT (see 12.1.134).

The following parameters should be specified:

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.133. DPCDT 576

Keywords for formats tN, E1, E3 19.1

12.1.134. NODPCDT

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is optional because in tNavigator the mode NODPCDT is used by default,
the maximum rate of change of capillary pressure in explicit cells is not set.

To set the maximum rate of change of capillary pressure in explicit cells use the keyword
DPCDT (see 12.1.133).
Example
NODPCDT

12.1.134. NODPCDT 577

Keywords for formats tN, E1, E3 19.1

12.1.135. TRACK

Data x tN E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword activates fluid tracking option (section 2.20). It enables tracking a division of
hydrocarbons in the original reservoir through into recovered surface volumes. The following
parameters should be specified:

1. depth or region where the division of the fluids is to be done:

• GOC – at gas-oil contact depth;

• DEPTH – at certain depth;
• REGONLY – in specified via TRACKREG (see 12.4.29) regions.
• Default: GOC.

2. depth value (if first parameter is DEPTH) (METRIC: m; FIELD: f t );

Default: 0.

3. flag of normalization of the recovered volumes: N – normalization is to be done;

Default: normalization is not performed.

4. a list of components to be tracked. ALL – all components.

Default: ALL.

The data should be terminated with a slash /.

Example
TRACK
GOC 1* U C1 C7+2 /
In the example the division of fluids is set to be done at gas-oil contact depth, normalization
is disabled, components to be tracked are C1 and C7+2.

12.1.135. TRACK 578

Keywords for formats tN, E1, E3 19.1

12.1.136. ENDSCALE

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

Indicates that end point scaling of relative permeabilities and capillary pressures will be
used, see 2.6.7, 2.6.8, 2.11.4 for details. Table end points can then be entered cell by cell
(SWL (see 12.6.26), SWCR (see 12.6.29), SWU (see 12.6.33), KRW (see 12.6.59), PCW,
see 12.6.62) or with respect to depth (ENPTVD (see 12.6.37), ENKRVD (see 12.6.38), EN-
PCVD, see 12.6.39).
Saturation end points (ENPTRC (see 12.6.40), ENPTRCM, see 12.6.43), relative phase
permeabilities (ENPKTRC (see 12.6.41), ENPKTRCM, see 12.6.44), and capillary pressures
(ENPCTRC (see 12.6.42), ENPCTRCM, see 12.6.45) can be specified as dependent on the
concentration of tracer (salt, surfactant). For more details on surfactants, see section 2.23.
Only non-directional reversible end point scaling is supported.
The following parameters should be specified (The data should be terminated with a slash
/.):

1. directional end point scaling switch (DIRECT, NODIR), ignored, this is an E1/E3 com-
patibility field;

2. irreversible end point scaling switch (IRREVERS, REVERS), ignored, this is an E1/E3
compatibility field;

3. the number of saturation end point versus depth tables (keywords ENPTVD (see 12.6.37),
ENKRVD, see 12.6.38); in tNavigator number of tables does not have to be specified
because the memory is allocated dynamically;
Default: 1.

4. the maximum number of nodes in any saturation end point versus depth table (keywords
ENPTVD (see 12.6.37), ENKRVD, see 12.6.38); in tNavigator number of tables does not
have to be specified because the memory is allocated dynamically.
Default: 20.

5. option for combining the temperature-independent (tracer, salt, surfactant-independent)

end points (for example, SWL (see 12.6.26), SWCR (see 12.6.29), SWU (see 12.6.33),
KRW (see 12.6.59), KRWR (see 12.6.59), PCW (see 12.6.62) etc.) with the temperature-
dependent end points (for example, ENPTVT (see 12.15.85), ENKRVT (see 12.15.86),
ENPCVT, see 12.15.87) or tracer (salt, surfactant) concentration-dependent end points
(ENPTRC (see 12.6.40), ENPKTRC (see 12.6.41), ENPCTRC (see 12.6.42), etc.) for sat-
urations, relative permeabilities and capillary pressures.

12.1.136. ENDSCALE 579

Keywords for formats tN, E1, E3 19.1

Temperature-dependent end points are available only for THERMAL (see 12.1.54) op-
tion, for non-thermal option this parameter will be ignored.
One of the following option can be specified:

• 0 – combination is not possible. Keywords ENPTVT (see 12.15.85), ENKRVT

(see 12.15.86), ENPCVT (see 12.15.87), ENPTRC (see 12.6.40), ENPKTRC
(see 12.6.41), ENPCTRC (see 12.6.42), ENPTRCM (see 12.6.43), ENPKTRCM
(see 12.6.44), ENPCTRCM (see 12.6.45) can not be used simultaneously with
ENDSCALE (see 12.1.136);
• 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 non-default;
• 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 non-default.

• 3 – end points independent on temperature of tracer, salt, surfactant are combined

with end points dependent on temperature or concentration of tracer salt, surfactant,
where values of table columns are non-default. If arrays of corresponding end
points are not specified then end points dependent on temperature of tracer, salt,
surfactant are used.
• Default: 0.
If 5-th parameter is set to 2 or 3 then 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 end points dependent on concentration of tracer, salt, surfac-
tant: 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.

6. equilibration of initial water saturation for grid blocks (SWATINIT, see 12.6.65) using
one of the below options:

• SCALE – scaling a capillary pressure;

• SHIFT – shift of capillary pressure.
• Default: SCALE.

! The options defined by the 6 − th parameter are not compatible with

option NONEQSAT of the keyword EQLOPTS (see 12.1.94).

! The option SHIFT is not compatible with option QUIESC of the keyword
EQLOPTS (see 12.1.94).

12.1.136. ENDSCALE 580

Keywords for formats tN, E1, E3 19.1

!
If initial water saturation specified by SWATINIT (see 12.6.65) is less
than SW L then satiration value is set equal to SW L . In grid blocks lo-
cated below WOC saturations specified by SWATINIT (see 12.6.65) are
ignored. If in grid blocks located above GOC saturations are higher than
SWCR then saturations in these blocks will be set equal to SWCR .

Example
ENDSCALE
/

12.1.136. ENDSCALE 581

Keywords for formats tN, E1, E3 19.1

12.2. Grid section

This section describes all keywords necessary for rectangular grid hydrodynamic model de-
scription.
The description of model geometry is in the section 5.5.
In tNavigator local grid refinements can be specified, see section 5.5.8.

12.2. Grid section 582

Keywords for formats tN, E1, E3 19.1

12.2.1. GRID

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies the beginning of data section which contains the keywords neces-
sary for rectangular grid hydrodynamic model description.

12.2.1. GRID 583

Keywords for formats tN, E1, E3 19.1

12.2.2. DX / DY / DZ

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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-centered geometry, see 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
m3 ,next 50 grid blocks are 520 ∗ 470 ∗ 5 m 3 , and the rest 100 grid blocks are 520 ∗ 470 ∗ 10
3
m .
In the three consecutive examples NX=5, NY=3, NZ=2.
Example
DIMENS
5 3 2
/
...
DX
30*200
/
In this example all grid block sizes in X direction are the same and are equal to 200 m.

12.2.2. DX / DY / DZ 584
Keywords for formats tN, E1, E3 19.1

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 585
Keywords for formats tN, E1, E3 19.1

12.2.3. DXV

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.28).
The data should be terminated with a slash /.

This keyword is used in block-centered geometry, see 5.5.

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 586

Keywords for formats tN, E1, E3 19.1

12.2.4. DYV

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.28).
The data should be terminated with a slash /.

This keyword is used in block-centered geometry, see 5.5.

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 587

Keywords for formats tN, E1, E3 19.1

12.2.5. DZV

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.28).
The data should be terminated with a slash /.

This keyword is used in block-centered geometry, see 5.5.

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 588

Keywords for formats tN, E1, E3 19.1

12.2.6. TOPS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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 /.

This keyword is used in block-centered geometry, see 5.5.

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 589

Keywords for formats tN, E1, E3 19.1

12.2.7. MIDS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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 590

Keywords for formats tN, E1, E3 19.1

12.2.8. COORD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is used in corner-point geometry, see 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 spec-
ified by two triplets of X, Y and Z coordinates, representing two distinct points on it.

The data should be terminated with a slash /.

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 591

Keywords for formats tN, E1, E3 19.1

12.2.9. ZCORN

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is used in corner-point geometry, see 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.

The data should be terminated with a slash /.

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 592

Keywords for formats tN, E1, E3 19.1

12.2.10. ADDZCORN

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keywords specifies a constant to be added to the corner point depth array ZCORN
(see 12.2.9).
Any number of data lines, each 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.28);

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. The 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.

9. X1A value: X1 − 1 or X1 ;
Default: X1A = X1 − 1 (if X1 > 1).

10. X2A value: X2 + 1 or X2 (0 ≤ X1A ≤ NX , 0 ≤ X2A ≤ NX );

Default: X2A = X2 + 1 (if X2A < NX ).

11. Y1A value: Y1 − 1 or Y1 ;

Default: Y1A = Y1 − 1 (if Y1 > 1).

12. Y2A value: Y2 + 1 or Y2 (0 ≤ Y1A ≤ NY , 0 ≤ Y2A ≤ NY );

Default: Y2A = Y2 + 1 (if Y2A < NY ).

12.2.10. ADDZCORN 593

Keywords for formats tN, E1, E3 19.1

13. 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);
• Default: 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 594

Keywords for formats tN, E1, E3 19.1

12.2.11. OLDTRAN

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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 doesn’t 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).)

The list of the keywords that can be specified and take part is transmissibility calculation
is available in the section 5.5.6.

12.2.11. OLDTRAN 595

Keywords for formats tN, E1, E3 19.1

12.2.12. NEWTRAN

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies block corner transmissibility method.

Transmissibilities are calculated using grid corner points positions.

This keyword doesn’t 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.

The list of the keywords that can be specified and take part is transmissibility calculation
is available in the section 5.5.6.

12.2.12. NEWTRAN 596

Keywords for formats tN, E1, E3 19.1

12.2.13. PERMX / PERMY / PERMZ

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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. Note that they may be
changed during the calculation by using these keywords in SCHEDULE section.
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 597

Keywords for formats tN, E1, E3 19.1

12.2.14. PERMMF

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets permeability values between matrix and fracture cells. Description of
dual porosity option is in the section 2.27.
The following parameters should be specified:

1. permeability value for each matrix cell (METRIC: mD, FIELD: mD). Nx · Ny · Nz /2
values should be specified.

The data should be terminated with a slash /.

Example
PERMMF
125*0.5 /

12.2.14. PERMMF 598

Keywords for formats tN, E1, E3 19.1

12.2.15. MULTX

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword is used to specify transmissibility multiplier 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 /.

• If keyword MULTX is specified in both GRID and EDIT sections the transmissibility
multiplier between blocks [I, J, K] and [I + 1, J, K] is the result of multiplication of
corresponding multipliers specified in these sections.
Property of transmissibility multiplier in the X direction (Trans. Mult. along X) will
be available via GUI on the tab Grid Properties, sub-tab Initial if keyword MULTX is
specified at least in one section GRID or EDIT.

• If keyword MULTX is specified several times in one section its value will be overwritten.
I.e. the multiplier is equal to the last specified value.

• In SCHEDULE section keyword MULTX can be specified at each time step. The effect
is cumulative (when MULTX is encountered in the SCHEDULE section, it multiplies
the current transmissibility in the X direction).
Property of transmissibility multiplier in the X direction (Trans. Mult. along X) will
be available via GUI on the tab Grid Properties sub-tab Calculated.

Note 1: for models in E3 format MULTX can not be used in the EDIT section. In this case
it will be ignored.

Note 2: If both transmissibility multiplier in X direction (MULTX) and fault transmissibility

multiplier in X direction (MULTFLT, see 12.2.39), and cumulative additional transmissibility
(HMMULTX (see 12.2.22) and/or HMMLTXY, see 12.2.22) are specified for the same cell face
(X), the effect will be cumulative.

Default: 1 in all cells.

12.2.15. MULTX 599

Keywords for formats tN, E1, E3 19.1

Example
DIMENS
5 5 4
/
...
MULTX
100*1.5
/
...
MULTX
100*2.0
/
In this example multipliers MULTX are specified in sections GRID and EDIT, thus the
transmissibility value will by multiplied by 1.5 ∗ 2.0 = 3.0 in X direction.

12.2.15. MULTX 600

Keywords for formats tN, E1, E3 19.1

12.2.16. MULTX-

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword is used to specify transmissibility multiplier 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 data should be terminated with a slash /.

• If keyword MULTX- is specified in both GRID and EDIT sections the transmissibility
multiplier between blocks [I, J, K] and [I − 1, J, K] is the result of multiplication of
corresponding multipliers specified in these sections.
Property of transmissibility multiplier in the X- direction (Trans. Mult. along X-) will
be available via GUI on the tab Grid Properties, sub-tab Initial if keyword MULTX-
is specified at least in one section GRID or EDIT.

• If keyword MULTX- is specified several times in one section its value will be overwrit-
ten. I.e. the multiplier is equal to the last specified value.

• In SCHEDULE section MULTX- can be specified at each time step. The effect is cu-
mulative (when MULTX- is encountered in the SCHEDULE section, it multiplies the
current transmissibility in the X- direction).
Property of transmissibility multiplier in the X- direction (Trans. Mult. along X-) will
be available via GUI on the tab Grid Properties sub-tab Calculated.

Note 1: for models in E3 format MULTX- can’t be used in the EDIT section. In this case
it will be ignored.

Note 2: If both transmissibility multiplier in X- direction (MULTX-) and cumulative ad-

ditional transmissibility (HMMULTX-, see 12.2.23), and fault transmissibility multiplier in
direction X- (MULTFLT, see 12.2.39) are specified for the same cell face (X-), the effect will
be cumulative.

Default: 1 in all cells.

12.2.16. MULTX- 601

Keywords for formats tN, E1, E3 19.1

Example
DIMENS
5 5 4
/
...
MULTX-
100*1.5
/
...
MULTX-
100*2.0
/
In this example multipliers MULTX- are specified in sections GRID and EDIT, thus the
transmissibility value will by multiplied by 1.5 ∗ 2.0 = 3.0 in X- direction.

12.2.16. MULTX- 602

Keywords for formats tN, E1, E3 19.1

12.2.17. MULTY

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword is used to specify transmissibility multiplier in Y direction for plane between
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 /.

• If keyword MULTY is specified in both GRID and EDIT sections the transmissibility
multiplier between blocks [I, J, K] and [I, J + 1, K] is the result of multiplication of
corresponding multipliers specified in these sections.
Property of Transmissibility multiplier in the Y direction (Trans. Mult. along Y) will
be available via GUI on the tab Grid Properties, sub-tab Initial if keyword MULTY is
specified at least in one section GRID or EDIT.

• If keyword MULTY is specified several times in one section its value will be overwritten.
I.e. the multiplier is equal to the last specified value.

• In SCHEDULE section keyword MULTY can be specified at each time step. The effect
is cumulative (when MULTY is encountered in the SCHEDULE section, it multiplies
the current transmissibility in the Y direction).
Property of transmissibility multiplier in the Y direction (Trans. Mult. along Y) will
be available via GUI on the tab Grid Properties sub-tab Calculated.

Note 1: for models in E3 format MULTY can not be used in the EDIT section. In this case
it will be ignored.

Note 2: If both transmissibility multiplier in Y direction (MULTY) and fault transmissibility

multiplier in Y direction (MULTFLT, see 12.2.39), and cumulative additional transmissibility
(HMMULTY (see 12.2.22) and/or HMMLTXY, see 12.2.22) are specified for the same cell face
(Y), the effect will be cumulative.

Default: 1 in all cells.

12.2.17. MULTY 603

Keywords for formats tN, E1, E3 19.1

Example
DIMENS
5 5 4
/
...
MULTY
100*1.5
/
...
MULTY
100*2.0
/
In this example multipliers MULTY are specified in sections GRID and EDIT, thus the
transmissibility value will by multiplied by 1.5 ∗ 2.0 = 3.0 in Y direction.

12.2.17. MULTY 604

Keywords for formats tN, E1, E3 19.1

12.2.18. MULTY-

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword is used to specify transmissibility multiplier in Y- direction for plane between
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 trans-
missibility multiplier between these two blocks is equal to the product of MULTY and MULTY-.

The keyword should be followed by one non-negative real number for every grid block.
The data should be terminated with a slash /.

• If keyword MULTY- is specified in both GRID and EDIT sections the transmissibility
multiplier between blocks [I, J, K] and [I, J − 1, K] is the result of multiplication of
corresponding multipliers specified in these sections.
Property of Transmissibility multiplier in the Y- direction (Trans. Mult. along Y-) will
be available via GUI on the tab Grid Properties, sub-tab Initial if keyword MULTY- is
specified at least in one section GRID or EDIT.

• If keyword MULTY- is specified several times in one section its value will be overwrit-
ten. I.e. the multiplier is equal to the last specified value.

• In SCHEDULE section keyword MULTY- can be specified at each time step. The effect
is cumulative (when MULTY- is encountered in the SCHEDULE section, it multiplies
the current transmissibility in the Y- direction).
Property of Transmissibility multiplier in the Y- direction (Trans. Mult. along Y-) will
be available via GUI on the tab Grid Properties sub-tab Calculated.

Note 1: for models in E3 format MULTY- can’t be used in the EDIT section. In this case
it will be ignored.

Note 2: If both transmissibility multiplier in Y- direction (MULTY-) and cumulative ad-

ditional transmissibility (HMMULTY-, see 12.2.23), and fault transmissibility multiplier in
direction Y- (MULTFLT, see 12.2.39) are specified for the same cell face (Y-), the effect will
be cumulative.

Default: 1 in all the cells.

12.2.18. MULTY- 605

Keywords for formats tN, E1, E3 19.1

Example
DIMENS
5 5 4
/
...
MULTY-
100*1.5
/
...
MULTY-
100*2.0
/
In this example multipliers MULTY- are specified in sections GRID and EDIT, thus the
transmissibility value will by multiplied by 1.5 ∗ 2.0 = 3.0 in Y- direction.

12.2.18. MULTY- 606

Keywords for formats tN, E1, E3 19.1

12.2.19. MULTZ

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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 /.

• If keyword MULTZ is specified in both GRID and EDIT sections the transmissibility
multiplier between blocks [I, J, K] and [I, J, K + 1] is the result of multiplication of
corresponding multipliers specified in these sections.
Property of transmissibility multiplier in the Z direction (Trans. Mult. along Z) will
be available via GUI on the tab Grid Properties, sub-tab Initial if keyword MULTZ is
specified at least in one section GRID or EDIT.

• If keyword MULTZ is specified several times in one section its value will be overwritten.
I.e. the multiplier is equal to the last specified value.

• In SCHEDULE section MULTZ can be specified at each time step. The effect is cumu-
lative (when MULTZ is encountered in the SCHEDULE section, it multiplies the current
transmissibility in the Z direction).
Property of Transmissibility multiplier in the Z direction (Trans. Mult. along Z) will
be available via GUI on the tab Grid Properties sub-tab Calculated.

Note 1: for models in E3 format MULTZ can’t be used in the EDIT section. In this case it
will be ignored.

Note 2: If both transmissibility multiplier in Z direction (MULTZ) and fault transmissibility

multiplier in Z direction (MULTFLT, see 12.2.39), and cumulative additional transmissibility
(HMMULTZ, see 12.2.22) are specified for the same cell face (Z), the effect will be cumulative.

Default: 1 in all cells.

12.2.19. MULTZ 607

Keywords for formats tN, E1, E3 19.1

Example
DIMENS
5 5 4
/
...
MULTZ
100*1.5
/
...
MULTZ
100*2.0
/
In this example multipliers MULTZ are specified in sections GRID and EDIT, thus the
transmissibility value will by multiplied by 1.5 ∗ 2.0 = 3.0 in Z direction.

12.2.19. MULTZ 608

Keywords for formats tN, E1, E3 19.1

12.2.20. MULTZ-

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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 trans-
missibility multiplier between these two blocks is equal to the product of MULTZ and MULTZ-.

The keyword should be followed by one non-negative real number for every grid block.
The data should be terminated with a slash /.

• If keyword MULTZ- is specified in both GRID and EDIT sections the transmissibility
multiplier between blocks [I, J, K] and [I, J, K − 1] is the result of multiplication of
corresponding multipliers specified in these sections.
Property of Transmissibility multiplier in the Z- direction (Trans. Mult. along Z-) will
be available via GUI on the tab Grid Properties, sub-tab Initial if MULTZ- is specified
at least in one section GRID or EDIT.

• If keyword MULTZ- is specified several times in one section its value will be overwrit-
ten. I.e. the multiplier is equal to the last specified value.

• In SCHEDULE section MULTZ- can be specified at each time step. The effect is cu-
mulative (when MULTZ- is encountered in the SCHEDULE section, it multiplies the
current transmissibility in the Z- direction).
Property of Transmissibility multiplier in the Z- direction (Trans. Mult. along Z-) will
be available via GUI on the tab Grid Properties sub-tab Calculated.

Note 1: for models in E3 format MULTZ- can’t be used in the EDIT section. In this case
it will be ignored.

Note 2: If both transmissibility multiplier in Z- direction (MULTZ-) and cumulative ad-

ditional transmissibility (HMMULTZ-, see 12.2.23), and fault transmissibility multiplier in
direction Z- (MULTFLT, see 12.2.39) are specified for the same cell face (Z-), the effect will
be cumulative.

Default: 1 in all cells.

12.2.20. MULTZ- 609

Keywords for formats tN, E1, E3 19.1

Example
DIMENS
5 5 4
/
...
MULTZ-
100*1.5
/
...
MULTZ-
100*2.0
/
In this example multipliers MULTZ- are specified in sections GRID and EDIT, thus the
transmissibility value will by multiplied by 1.5 ∗ 2.0 = 3.0 in Z- direction.

12.2.20. MULTZ- 610

Keywords for formats tN, E1, E3 19.1

12.2.21. HMMLTPX / HMMLTPY / HMMLTPZ / HMMLTPXY

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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
should be terminated with a slash /.
The keywords could be used with the keywords EQUALS (see 12.3.23) 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 611

Keywords for formats tN, E1, E3 19.1

12.2.22. HMMULTX / HMMULTY / HMMULTZ / HMMLTXY / HMMULTPV

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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 be-

tween 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) that
have been previously specified;

• 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) that
have been previously specified;

• HMMULTPV – cumulative pore volume multiplier. The keyword acts as a multiplier on

any values MULTPV (see 12.2.28) that have been previously specified.

The same number of values as the number of grid blocks should be entered. The data
should be terminated with a slash /.
The keywords could be used with the keywords EQUALS (see 12.3.23) and BOX (see 12.3.3).
Note 1: If both cumulative additional transmissibility (HMMULTX and/or HMMLTXY)
and transmissibility multiplier in X direction (MULTX, see 12.2.15), and fault transmissibility
multiplier in X direction (MULTFLT, see 12.2.39) are specified for the same cell face (X), the
effect will be cumulative.
Note 2: If both cumulative additional transmissibility (HMMULTY and/or HMMLTXY)
and transmissibility multiplier in Y direction (MULTY, see 12.2.17), fault transmissibility
multiplier in Y direction (MULTFLT, see 12.2.39) are specified for the same cell face (Y), the
effect will be cumulative.
Note 3: If both cumulative additional transmissibility (HMMULTZ) and transmissibility
multiplier in Z direction (MULTZ, see 12.2.19), and fault transmissibility multiplier in Z

12.2.22. HMMULTX / HMMULTY / HMMULTZ / HMMLTXY / HMMULTPV 612

Keywords for formats tN, E1, E3 19.1

direction (MULTFLT, see 12.2.39) are specified for the same cell face (Z), the effect will be
cumulative.
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 613

Keywords for formats tN, E1, E3 19.1

12.2.23. HMMULTX- / HMMULTY- / HMMULTZ-

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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) that
have been previously specified;
• 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.
The same number of values as the number of grid blocks should be entered. The data
should be terminated with a slash /.
The keywords could be used with the keywords EQUALS (see 12.3.23) and BOX (see 12.3.3).
Note 1: If both cumulative additional transmissibility (HMMULTX-) and transmissibility
multiplier in direction X- (MULTX-, see 12.2.16), and fault transmissibility multiplier in di-
rection X- (MULTFLT, see 12.2.39) are specified for the same cell face (X-), the effect will be
cumulative.
Note 2: If both cumulative additional transmissibility (HMMULTY-) and transmissibility
multiplier in direction Y- (MULTY-, see 12.2.18), and fault transmissibility multiplier in di-
rection Y- (MULTFLT, see 12.2.39), are specified for the same cell face (Y-), the effect will
be cumulative.
Note 3: If both cumulative additional transmissibility (HMMULTZ-), and transmissibility
multiplier in direction Z- (MULTZ-, see 12.2.20), and fault transmissibility multiplier in di-
rection Z- (MULTFLT, see 12.2.39) are specified for the same cell face (Z-), the effect will be
cumulative.
Example
EQUALS
'HMMULTX-' 0.75 5 10 5 10 20 30 /
/

12.2.23. HMMULTX- / HMMULTY- / HMMULTZ- 614

Keywords for formats tN, E1, E3 19.1

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- 615

Keywords for formats tN, E1, E3 19.1

12.2.24. PORO

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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 the function ϕ(x, y, z) in 2.5. Note that porosity
may be changed during the calculation by using this keyword in SCHEDULE section.
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 616

Keywords for formats tN, E1, E3 19.1

12.2.25. NTG

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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 617

Keywords for formats tN, E1, E3 19.1

12.2.26. DZNET

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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 618

Keywords for formats tN, E1, E3 19.1

12.2.27. PORV

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID x EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword defines pore volumes of grid blocks (METRIC: rm3 , FIELD: rb) (see
section 4.25). 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 619

Keywords for formats tN, E1, E3 19.1

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 620

Keywords for formats tN, E1, E3 19.1

12.2.28. MULTPV

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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 (see
section 4.25).

The keyword can be used in SCHEDULE section.

Material is still conserved, that’s why modification of the pore volume leads to the pressure
change. MULTPV in SCHEDULE section is cumulative: each MULTPV keyword provides mul-
tiplication of the current pore volumes.

Default: 1.

12.2.28. MULTPV 621

Keywords for formats tN, E1, E3 19.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

/
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 622

Keywords for formats tN, E1, E3 19.1

12.2.29. ACTNUM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies active/inactive cells. Other keywords used to identify active/inac-
tive grid cells are listed in the section 5.5.1. The number of values should be equal to number
of cells. Values should be integer numbers:

1. For E1 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 E3 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 in all the cells.

Example
DIMENS
5 5 4
/
...
ACTNUM
100*1
/
In this example all cells are active cells.

12.2.29. ACTNUM 623

Keywords for formats tN, E1, E3 19.1

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
/
In this example cell [1, 1, 1] is active, but cell [2, 2, 1] is inactive.

12.2.29. ACTNUM 624

Keywords for formats tN, E1, E3 19.1

12.2.30. MINPV

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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. Other keywords used to identify
active/inactive grid blocks are listed in the section 5.5.1.
Default: 0.000001.
Example
MINPV
1200
/
In this example all grid blocks with pore volume less than 1200 rm3 are switched into
inactive state.

12.2.30. MINPV 625

Keywords for formats tN, E1, E3 19.1

12.2.31. MINPORV

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is an alias for the keyword MINPV (see 12.2.30). Other keywords used to
identify active/inactive grid cells are listed in the section 5.5.1.

12.2.31. MINPORV 626

Keywords for formats tN, E1, E3 19.1

12.2.32. MINPVV

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is used to switch grid block into inactive state if its pore volume (METRIC:
rm3 , FIELD: rb) is smaller than value specified in this keyword and associated with that
block. Other keywords used to identify active/inactive grid blocks are listed in the section
5.5.1.
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, a grid block will be switched into
inactive state.

12.2.32. MINPVV 627

Keywords for formats tN, E1, E3 19.1

12.2.33. MINDZNET

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is used to switch grid block into inactive state if its net thickness (DZ,
see 12.2.2) is smaller than specified in this keyword (METRIC: m, FIELD: f t ). Other key-
words used to identify active/inactive grid blocks are listed in the section 5.5.1.
Default: 0.000001.
Example
MINDZNET
0.2
/
In this example all grid blocks with net thickness less than 0.2 m are switched into inactive
state.

12.2.33. MINDZNET 628

Keywords for formats tN, E1, E3 19.1

12.2.34. MINPVR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is used to switch grid blocks into inactive state if their pore volume is less
than a specified fraction of an average pore volume. Other keywords used to identify active/i-
nactive grid blocks are listed in the section 5.5.1. The data should be terminated with a slash /.

The keyword has E1/E3-compatible analogue MINPV (see 12.2.30).

Example
MINPVR
0.001/

In this example all grid blocks with pore volume less than 0.1% (of an average pore
volume) are switched into inactive state.

12.2.34. MINPVR 629

Keywords for formats tN, E1, E3 19.1

12.2.35. MINROCKV

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword could be used only in thermal run (THERMAL, see 12.1.54). 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.35. MINROCKV 630

Keywords for formats tN, E1, E3 19.1

12.2.36. MINRV

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is an alias of the keyword MINROCKV (see 12.2.35).

12.2.36. MINRV 631

Keywords for formats tN, E1, E3 19.1

12.2.37. PERMAVE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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

Formulae for transmissibility calculations are in the section 5.5.6.

The data should be terminated with a slash /.

The following parameters should be specified:

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.37. PERMAVE 632

Keywords for formats tN, E1, E3 19.1

12.2.38. FAULTS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

A table is specified which defines a set of faults. Fault transmissibility can later be mod-
ified using MULTFLT (see 12.2.39) keyword. Other keywords used to specify faults and their
parameters are listed in the section 5.5.2.
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:

1. fault name, The fault is consist of all the segments with the same name. Segments can
be placed in arbitrary order.

2. lower i coordinate of fault segment;

3. upper i coordinate of fault segment; should be equal to lower i coordinate if fault face
is I or X;

4. lower j coordinate of fault segment;

5. upper j coordinate of fault segment. It should be equal to lower j coordinate if fault

face is J or Y;

6. lower k coordinate of fault segment;

7. upper k coordinate of fault segment. It should be equal to lower k coordinate if fault

face is K or Z;

8. fault face. It should be specified by one of the following letters: I, J, K, X, Y, Z if

the selected direction is positive, and I-, J-, K-, X-, Y-, Z- if the selected direction is
negative.

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 transmis-
sibility in a group of cells with help of keyword MULTFLT (see 12.2.39). They don’t have to
coincide with actual faults in the corner-point geometry (see keywords ZCORN (see 12.2.9)
and COORD, see 12.2.8).

12.2.38. FAULTS 633

Keywords for formats tN, E1, E3 19.1

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'/
/
This example defines two two-segment faults.

12.2.38. FAULTS 634

Keywords for formats tN, E1, E3 19.1

12.2.39. MULTFLT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.38) keyword.
Other keywords used to specify faults and their parameters are listed in the section 5.5.2.

The following data should be specified:

1. fault name (as specified in the FAULTS keyword), or a fault name mask defining a
subset of faults with common prefix (should end with an asterisk *);
Default: *.

2. transmissibility multiplier;
Default: 1.0.

3. diffusivity multiplier, IGNORED (this is an E1/E3 compatibility field).

Default: 1.0.

The table must be terminated with a blank record, containing only a slash (/).
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 spec-
ified more than once in SCHEDULE section, then multipliers will be multiplied (cumulative
behaviour).

Note 2: If both MULTFLT (fault face is specified for positive direction X, or Y, or Z) 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.
Note 3: If both MULTFLT (fault face is specified for negative direction: X-, or Y-, or Z-)
and MULTX- (see 12.2.16) or MULTY- (see 12.2.18) or MULTZ- (see 12.2.20) are used for
the same cell face, the effect will be cumulative.

12.2.39. MULTFLT 635

Keywords for formats tN, E1, E3 19.1

Example
FAULTS
– NAME i1 i2 j1 j2 k1 k2 FACE
'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.
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'/
/

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.39. MULTFLT 636

Keywords for formats tN, E1, E3 19.1

12.2.40. THPRESFT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword is used to set threshold pressure value for flow through fault. The threshold
pressure option THPRES should be set in the keyword EQLOPTS (see 12.1.94) in the RUN-
SPEC section. 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.16.11). Other keywords used to specify faults and their
parameters are listed in the section 5.5.2.
Keyword is followed by a 2-column table, each line should end with slash (/). Last table
line should contain only slash symbol (/).

The following data should be specified:

1. fault name, or a fault name mask defining a subset of faults with common prefix (should
end with an asterisk *);
Default: *.
2. threshold pressure value for flow through this fault (METRIC: barsa, FIELD: psia);
Default: 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.40. THPRESFT 637

Keywords for formats tN, E1, E3 19.1

12.2.41. USEFLUX

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is used in tNavigator for splitting. The keyword should be followed by .flux
file name, which contains boundary conditions for split part of the model.
.flux file and this keyword are generated automatically when you split the model.
Splitting is described in section 5.12 (in tNavigator approach to splitting is different from
E1/E3).

.flux files in tNavigator are generated always in two cases:

• during calculation of .patterns file (common file which contains information about all
split 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 split parts of the model (flow across the bound-
ary).
Example
USEFLUX
'DEMO_SIMPLE_002_2'
/

This keyword defines that file DEMO_SIMPLE_002_2.flux with boundary conditions is

used.

12.2.41. USEFLUX 638

Keywords for formats tN, E1, E3 19.1

12.2.42. DUMPFLUX

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is ignored by tNavigator for splitting because in tNavigator approach to

splitting is different from E1/E3. Splitting is described in section 5.12.

.flux files in tNavigator are generated always in two cases:

• during calculation of .patterns file (common file which contains information about all
split 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 split parts of the model (flow across the bound-
ary).
The keyword FIPPATT (see 12.4.13) for every grid block specifies the split region to which
it belongs.

12.2.42. DUMPFLUX 639

Keywords for formats tN, E1, E3 19.1

12.2.43. FLUXREG / FLUXTYPE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is ignored by tNavigator for splitting because in tNavigator approach to

splitting and boundary conditions is different from E1/E3.
Splitting is described in section 5.12.

12.2.43. FLUXREG / FLUXTYPE 640

Keywords for formats tN, E1, E3 19.1

12.2.44. DOMAINS

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets parameters for parallel run for other simulators working in E1/E3 for-
mats.
This keyword is IGNORED because of specific methods of solution used in tNavigator.

12.2.44. DOMAINS 641

Keywords for formats tN, E1, E3 19.1

12.2.45. ISOLNUM

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies isolated regions for other simulators working in E1/E3 formats.
This keyword is IGNORED because of specific methods of solution used in tNavigator.

12.2.45. ISOLNUM 642

Keywords for formats tN, E1, E3 19.1

12.2.46. SOLVDIRS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword overrides the solver principal directions for other simulators in E1/E3 for-
mats.
This keyword is IGNORED because of specific methods of solution used in tNavigator.

12.2.46. SOLVDIRS 643

Keywords for formats tN, E1, E3 19.1

12.2.47. RESVNUM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.76). NUMRES (see 12.1.76) 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.47. RESVNUM 644

Keywords for formats tN, E1, E3 19.1

12.2.48. COORDSYS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword provides information about coordinate system for each reservoir. Layers of
blocks can be put to several reservoirs at the same time. Other keywords used to specify
several reservoirs of model are listed in the section 5.5.3.

The keyword should be specified only if the is more than one reservoir. The keyword
should be followed by the NUMRES (see 12.1.76) sets of data (equal to the amount of reser-
voirs). 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 shouldn’t be
greater than NZ in DIMENS, see 12.1.28);

2. maximal block index number in Z-direction for this reservoir (this number shouldn’t be
greater than NZ in DIMENS, see 12.1.28);

3. completion of circle for this reservoir (COMP - circle is completed in Y-direction, IN-
COMP - circle is not completed. The circle can be completed if coincident coordinate
lines are identified);
Default: INCOMP.

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);
Default: SEPARATE.

5. lower bound for reservoir number for lateral block connection between reservoirs;
Default: current reservoir number.

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.76).
Default: current reservoir number.

12.2.48. COORDSYS 645

Keywords for formats tN, E1, E3 19.1

Example
NUMRES
4
/
COORDSYS
1 4 'INCOMP' 'SEPARATE' 1 1
/
5 16 'INCOMP' 'SEPARATE' 2 2
/
17 20 'INCOMP' 'SEPARATE' 3 3
/
21 54 'INCOMP' 'SEPARATE' 4 4
/

12.2.48. COORDSYS 646

Keywords for formats tN, E1, E3 19.1

12.2.49. GDFILE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword allows to define model grid by means of file of special format (*.GRID
format of E1/E3). Other possibilities to specify the geometry of model grid are described in
the section 5.5.
The grid defined in this file is a set of cubes, with coordinates of all 8 vertexes given,
a more flexible way than COORD (see 12.2.8), ZCORN (see 12.2.9) allows. Only UNFOR-
MATTED 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: UNFORMATTED.

Example
GDFILE
filegrid.GRID UNFORMATTED
/
In this example grid will be taken from filegrid.GRID.

12.2.49. GDFILE 647

Keywords for formats tN, E1, E3 19.1

12.2.50. TRANX

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID x EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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).

The list of the keywords that can be specified and take part is transmissibility calculation
is available in the section 5.5.6.

This value replaces the 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.50. TRANX 648

Keywords for formats tN, E1, E3 19.1

12.2.51. TRANY

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID x EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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).

The list of the keywords that can be specified and take part is transmissibility calculation
is available in the section 5.5.6.

This value replaces the 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
/
...
TRANY
100*1.5
/

In this example transmissibility is specified for all planes in Y-direction as 1.5.

12.2.51. TRANY 649

Keywords for formats tN, E1, E3 19.1

12.2.52. TRANZ

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID x EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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).

The list of the keywords that can be specified and take part is transmissibility calculation
is available in the section 5.5.6.

This value replaces the 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
/
...
TRANZ
100*1.5
/

12.2.52. TRANZ 650

Keywords for formats tN, E1, E3 19.1

12.2.53. MAXTRANZ

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies the upper threshold of vertical transmissibility between two cells.
If the calculated value for a particular connection is larger than this threshold, it is reduced.
The list of the keywords taking part is transmissibility calculation is available in the sec-
tion 5.5.6.

The following parameter should be specified:

1. Maximum allowed vertical transmissibility (METRIC: cP-rm3 /day/bar , FIELD:

cP-rb/day/psi).

Default: 1.0E20 (all systems of units).

Example
MAXTRANZ
10000 /
In this example vertical transmissibility in the model is limited with 10 000.

12.2.53. MAXTRANZ 651

Keywords for formats tN, E1, E3 19.1

12.2.54. NNC

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

Usually non-neighbor connections are created due to faults, but they can be set explicitly
using this keyword.

The list of the keywords that can be specified and take part is transmissibility calculation
is available in the section 5.5.6.

For each non-neighbor connection one line of data is entered, with coordinates 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;

5. J -coordinate of this cell;

6. K -coordinate of this cell;

7. non-neighbor connection transmissibility (METRIC: cP-rm3 /day/bar , FIELD: cP-rb/day/psi);

Default: 0.

8. saturation table number related to the flow from the first to the second cell (for models
in E1 format). Diffusivity value of the non-neighbor connection (METRIC: m, FIELD:
f t ) (for models in E3 format). IS IGNORED, this is an E1/E3 compatibility field;
Default: 0.

9. saturation table number related to the flow from the second to the first cell (for models in
E1 format). Thermal conduction transmissibility value of the non-neighbor connection
used by the thermal model (keyword THERMAL, see 12.1.54) – section 12.15 (for
models in E3 format). IS IGNORED, this is an E1/E3 compatibility field;

10. pressure table number related to the flow from the first to the second cell (for models
in E1 format). IS IGNORED, this is an E1/E3 compatibility field;
Default: 0.

12.2.54. NNC 652

Keywords for formats tN, E1, E3 19.1

11. pressure table number related to the flow from the second to the first cell (for models
in E1 format). IS IGNORED, this is an E1/E3 compatibility field;

12. face related to flow from the first to the second cell. Define one of the following faces:
X+, X−,Y +,Y −, Z+, Z− (only for models in E1 format). IS IGNORED, this is an
E1/E3 compatibility field;

13. face related to flow from the second to the first cell. Define one of the following faces:
X+, X−,Y +,Y −, Z+, Z− (only for models in E1 format). IS IGNORED, this is an
E1/E3 compatibility field;

14. diffusivity value of the non-neighbor connection (METRIC: m, FIELD: f t ) used by the
molecular diffusion option (keyword DIFFUSE, see 12.1.70);
Default: 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.54. NNC 653

Keywords for formats tN, E1, E3 19.1

12.2.55. EDITNNC

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID x EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

Using this keyword one can modify non-neighbor connections generated by faults in the
grid.

The list of the keywords that can be specified and take part is transmissibility calculation
is available in the section 5.5.6.

For any non-neighbor connection you want to modify, you should specify a line of data
with the 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;

2. J coordinate of this cell;

3. K coordinate of this cell;

4. I coordinate of second cell from non-neighbour connection;

5. J coordinate of this cell;

6. K coordinate of this cell;

7. transmissibility multiplier of this non-neighbor connection (should be greater or equal

to zero); transmissibility is equal to the product of this multiplier and non-neighbor
connection transmissibility, which in turn is calculated by the program or specified by
the keyword NNC (see 12.2.54);
Default: TRANM.

8. number of saturation region corresponding to the flow from the first cell to the second
cell;
Default: 0.

9. number of saturation region corresponding to the flow from the second cell to the first
cell;
Default: 0.

12.2.55. EDITNNC 654

Keywords for formats tN, E1, E3 19.1

10. number of PVT region corresponding to the flow from the first cell to the second cell;
Default: 0.

11. number of PVT region corresponding to the flow from the second cell to the first cell;
Default: 0.

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-;

14. diffusivity multiplier of this non-neighbor connection (should be greater or equal to

zero); the diffusivity is equal to the product of this multiplier and non-neighbor connec-
tion diffusivity.
Default: 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.55. EDITNNC 655

Keywords for formats tN, E1, E3 19.1

12.2.56. EDITNNCR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID x EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

Using this keyword one can replace non-neighbor connections generated by faults in the
grid.

The list of the keywords that can be specified and take part is transmissibility calculation
is available in the section 5.5.6.

For any non-neighbor connection you want to replace, you should specify a line of data
with the 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;

2. J coordinate of this cell;
3. K coordinate of this cell;
4. I coordinate of second cell from non-neighbour connection;
5. J coordinate of this cell;
6. K coordinate of this cell;
7. new transmissibility value for this non-neighbor connection (METRIC: cP-rm3 /day/bar ,
FIELD: cP-rb/day/psi); should be greater or equal to zero;
8. number of saturation region corresponding to the flow from the first cell to the second
cell;
Default: 0.
9. number of saturation region corresponding to the flow from the second cell to the first
cell;
Default: 0.
10. number of PVT region corresponding to the flow from the first cell to the second cell;
Default: 0.
11. number of PVT region corresponding to the flow from the second cell to the first cell;
Default: 0.

12.2.56. EDITNNCR 656

Keywords for formats tN, E1, E3 19.1

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-;

14. new diffusivity value for this non-neighbor connection (METRIC: m, FIELD: f t );
should be greater or equal to zero.
Default: 0.

Example
EDITNNCR
10 4 5 11 6 6 3.5 4* X+ X- 2.5/
/
In this example one non-neighbor connection is replaced with a new one having transmis-
sibility of 3.5 and working in the directions X+ X−.

12.2.56. EDITNNCR 657

Keywords for formats tN, E1, E3 19.1

12.2.57. NNCGEN

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword can be used to specify transmissibility between any two cells in any two
grids.

The list of the keywords that can be specified and take part is transmissibility calculation
is available in the section 5.5.6.

The keyword can contain any number of data lines, each terminated with a slash /. All
data should be terminated with a final slash /.
One data line contains the following parameters:

1. grid of the first cell;

Default: GLOBAL.

2. I -coordinate of the first cell joined to non-neighbor connection;

3. J -coordinate of this cell;

4. K -coordinate of this cell;

5. grid of the second cell;

Default: GLOBAL.

6. I -coordinate of the second cell joined to non-neighbor connection;

7. J -coordinate of this cell;

8. K -coordinate of this cell;

9. non-neighbor connection transmissibility (METRIC: cP-rm3 /day/bar , FIELD: cP-rb/day/psi);

Default: 0 cp-rm3 /day/bar .

10. diffusivity value of the non-neighbor connection (METRIC: m, FIELD: f t );

Default: 0.

12.2.57. NNCGEN 658

Keywords for formats tN, E1, E3 19.1

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/
/

In this example there are 3 non-neighbor connections.

12.2.57. NNCGEN 659

Keywords for formats tN, E1, E3 19.1

12.2.58. PINCH

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets parameters regulating non-neighbor connections for pinched out layers.

This keyword can be used for transmissibility calculation. The full list of the keywords
used for transmissibility calculation is available in the section 5.5.6.

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 fulfilled.

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 );
Default: 0.001 (m).

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 cre-
ated even if thickness exceeds threshold, and second one (NOGAP) – that non-neighbor
connections are created always observing threshold thickness;
Default: GAP.

3. maximal empty gap allowed between cells in adjacent layers for non-zero transmissibil-
ity to be allowed between them (METRIC: m , FIELD: ft ). If PINCH is not used, it’s
equivalent to default value of this parameter;
Default: 1E20.

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;
Default: TOPBOT.

12.2.58. PINCH 660

Keywords for formats tN, E1, E3 19.1

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.
Default: 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 thick-
ness exceeds threshold value.

12.2.58. PINCH 661

Keywords for formats tN, E1, E3 19.1

12.2.59. PINCHXY

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword is used to specify the X and Y-direction pinchout threshold widths.

This keyword can be used for transmissibility calculation. The full list of the keywords
used for transmissibility calculation is available in the section 5.5.6.

The data should be terminated by a slash /. Following parameters are to be specified:

1. X-direction threshold width for horizontal pinchout (METRIC: m, FIELD: f t );

Default: 0.001.

2. Y-direction threshold width for horizontal pinchout (METRIC: m, FIELD: f t );

Default: 0.001.

Model’s vertical parts which are pinched-out in the X or Y-direction correspond in the grid
to columns of inactive cells with zero width in the X or Y-direction. A column of inactive cells
doesn’t allow a flow (between active cells on each sides of it) to cross it in the X or Y-direction.

In case the keyword PINCHXY is specified, horizontal non-neighbor connections in the X

or Y-direction will be created between active cells on each side of the pinch-out column. So
fluid will flow through this column. Columns are considered as pinched-out columns in the X
or Y-direction if their overall cell width in the X or Y-direction is below the value specified
by this keyword.

Non-neighbor connections won’t be generated if the keyword NONNC (see 12.1.53) is

specified.
Example
PINCHXY
0.02 0.04 /
This example sets X-direction threshold width equal to 0.02 and Y-direction threshold
width equal to 0.04.

12.2.59. PINCHXY 662

Keywords for formats tN, E1, E3 19.1

12.2.60. PINCHOUT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

Analog of PINCH (see 12.2.58), but has no parameters. Equivalent to setting

Example
PINCH
/
For more detailed control over non-neighbor connections across pinched out cells see
PINCH (see 12.2.58).
This keyword can be used for transmissibility calculation. The full list of the keywords
used for transmissibility calculation is available in the section 5.5.6.

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.60. PINCHOUT 663

Keywords for formats tN, E1, E3 19.1

12.2.61. PINCHREG

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets parameters regulating non-neighbor connections for pinched out layers
for regions identified by PINCHNUM (see 12.2.62).

This keyword can be used for transmissibility calculation. The full list of the keywords
used for transmissibility calculation is available in the section 5.5.6.

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.58). 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.62), specified via the 3-rd parameter of the keyword GRIDOPTS (see 12.1.95).
If the 3-rd parameter of GRIDOPTS (see 12.1.95) is defaulted (0), then the number of regions
should be specified via the 4-th parameter of REGDIMS (see 12.1.32). 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 );
Default: 0.001.
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 cre-
ated even if thickness exceeds threshold, and second one (NOGAP) – that non-neighbor
connections are created always observing threshold thickness;
Default: GAP.
3. maximal empty gap allowed between cells in adjacent layers for non-zero transmissibil-
ity to be allowed between them (METRIC: m, FIELD: f t );
Default: 1E20.
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

12.2.61. PINCHREG 664

Keywords for formats tN, E1, E3 19.1

one – as harmonic average of cell transmissibilities of pinched out layer(s) between two
active cells;
Default: TOPBOT.

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.
Default: 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.61. PINCHREG 665

Keywords for formats tN, E1, E3 19.1

12.2.62. PINCHNUM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is used to specify pinchout regions for non-neighborhood connections gen-
eration through PINCHREG (see 12.2.61).

This keyword can be used for transmissibility calculation. The full list of the keywords
used for transmissibility calculation is available in the section 5.5.6.

To use this keyword, one should specify a maximum number of pinchout regions in 3-rd
parameter of the keyword GRIDOPTS (see 12.1.95).

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 /.

Default: 1.
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.62. PINCHNUM 666

Keywords for formats tN, E1, E3 19.1

12.2.63. JFUNC

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

If end-point scaling is selected by ENDSCALE (see 12.1.136), 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.64) can
be used to specify data separately for each saturation region.
Formulae for capillary pressure calculation with Leverett J-Function is available in the section
2.11.5.

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;
• Default: BOTH.

2. oil-water surface tension, this is STW in 2.89, 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.89, 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.89;

Default: 0.5.

5. power for permeability, this is β in 2.89;

Default: 0.5.

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)

12.2.63. JFUNC 667

Keywords for formats tN, E1, E3 19.1

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.65). If this keyword is specified then perme-
ability direction (the 6-th parameter of JFUNC (see 12.2.63) is ignored);
Default: 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.63. JFUNC 668

Keywords for formats tN, E1, E3 19.1

12.2.64. JFUNCR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

If end-point scaling is selected by ENDSCALE (see 12.1.136), JFUNCR keyword may be

specified. In this case capillary pressures will be calculated according to Leverett J-Function
option.
This keyword defines parameters separately for each saturation region. The keyword JFUNC
(see 12.2.63) can be used to specify data for whole reservoir.
Formulae for capillary pressure calculation with Leverett J-Function is available in the section
2.11.5.

The number of data lines should be equal to the number of saturation regions (1-st param-
eter of the keyword TABDIMS, see 12.1.29). 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),
• Default: BOTH.

2. oil-water surface tension, this is STW in 2.89, 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.89, 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.89;

Default: 0.5.

5. power for permeability, this is β in 2.89;

Default: 0.5.

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).

12.2.64. JFUNCR 669

Keywords for formats tN, E1, E3 19.1

Instead of this parameter one can specify the special permeability value used for J-
function computation (JFPERM, see 12.2.65). If this keyword is specified then perme-
ability direction (the 6-th parameter of JFUNC (see 12.2.63) is ignored);
Default: XY.

Example
JFUNCR
WATER 22.2 /
GAS 1* 12.2 /
BOTH 22.2 12.2 /

12.2.64. JFUNCR 670

Keywords for formats tN, E1, E3 19.1

12.2.65. JFPERM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets the special permeability value (mD) used for J-function computation
JFUNC (see 12.2.63). the keyword can be used for E1 and E3 format models.
Formulae for capillary pressure calculation with Leverett J-Function is available in the section
2.11.5.

The number of specified values should be equal to the number of grid blocks. The data
should be terminated with a slash /.

If this keyword is specified for the grid block then permeability direction (the 6-th param-
eter of JFUNC (see 12.2.63) (JFUNCR, see 12.2.64) is ignored).
Example
JFPERM
600*4.5/

12.2.65. JFPERM 671

Keywords for formats tN, E1, E3 19.1

12.2.66. GRIDUNIT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword is used to specify length units for grid data and indicates if the coordinate
transformation via MAPAXES (see 12.2.67) will be used or not. The data should be terminated
with a slash /.

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.67).

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.67) will be used.

12.2.66. GRIDUNIT 672

Keywords for formats tN, E1, E3 19.1

12.2.67. MAPAXES

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

To transform grid coordinates to coordinate system associated with the map, MAPAXES
may be specified. Keywords used to transform grid coordinates are listed in the section 5.5.4.
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.67. MAPAXES 673

Keywords for formats tN, E1, E3 19.1

12.2.68. MAPUNITS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword is used to specify MAPAXES (see 12.2.67) data units. Keywords used to
transform grid coordinates are listed in the section 5.5.4. Following units are possible:

• METRES,

• FEET,

• CM.

Default: METRES.
Example
MAPUNITS
FEET
/
In this example MAPAXES data units are feets.

12.2.68. MAPUNITS 674

Keywords for formats tN, E1, E3 19.1

12.2.69. LX / LY / LZ

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword can be specified in dual porosity run (2.27) if the option viscous displace-
ment is enabled (VISCD, see 12.1.89). 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
should be terminated with a slash /.
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.74) is enabled.
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.83), Viscous displacement is specified using the
keyword VISCD (see 12.1.89). 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.69. LX / LY / LZ 675
Keywords for formats tN, E1, E3 19.1

12.2.70. DPNUM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can be used in dual porosity single permeability run (2.27). 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 isn’t 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.83) isn’t specified. DUALPERM
(see 12.1.84) shouldn’t 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.83), then single porosity field is
specified (the half of the reservoir).

12.2.70. DPNUM 676

Keywords for formats tN, E1, E3 19.1

12.2.71. DPGRID

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can be used in dual porosity single permeability run (2.27). If the keyword
is enabled 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.28). This operation is applied only
for fracture blocks which don’t have manually input grid data.
Example
DPGRID

12.2.71. DPGRID 677

Keywords for formats tN, E1, E3 19.1

12.2.72. SIGMA

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can be used in dual porosity or dual permeability run (2.27), specified by
keywords DUALPORO (see 12.1.83), DUALPERM (see 12.1.84). The keyword sets the 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
/.
Sigma-factor is related to the distances between fractures (matrix block sizes) in X, Y and
Z directions:  
1 1 1
σ =4 + + ,
lx2 ly2 lz2
where lx , ly and lz are the characteristic 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: none. If neither of the keywords SIGMA, SIGMAV (see 12.2.73), LTOSIGMA
(see 12.2.74) is specified, an error will be returned.
Different sigma-factors for different blocks can be specified using the keyword SIGMAV
(see 12.2.73).
Example
SIGMA
0.25 /

This example sets sigma-factor equal to 0.25.

12.2.72. SIGMA 678

Keywords for formats tN, E1, E3 19.1

12.2.73. SIGMAV

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can be used in dual porosity run (2.27), specified by keyword DUALPORO
(see 12.1.83). The keyword SIGMAV sets sigma-factor multiplier that is used in matrix-fracture
coupling transmissibilities.

One should enter NX * NY * (NZ/2) values for matrix blocks. The data should be
terminated with a slash /.
Sigma-factor is related to the distances between fractures (matrix block sizes) in X, Y and
Z directions:  
1 1 1
σ =4 + + ,
lx2 ly2 lz2
where lx , ly and lz are the characteristic 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: none. If neither of the keywords SIGMA (see 12.2.72), SIGMAV, LTOSIGMA
(see 12.2.74) is specified, an error will be returned.
Common sigma-factor for all blocks can be specified using the keyword SIGMA
(see 12.2.72).
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.83). First 25 matrix blocks have sigma-factor 0.17,
next 25 – 1, next 50 – 0.26.

12.2.73. SIGMAV 679

Keywords for formats tN, E1, E3 19.1

12.2.74. LTOSIGMA

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can be used in dual porosity run (2.27), if the option Viscous displacement
is enabled (VISCD, see 12.1.89). 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 specified:

1. f x ,

2. f y,

3. f z.

Sigma-factor is related to the distances between fractures (matrix block sizes) in X, Y and
Z directions:
fx fy fz
σ = 2 + 2 + 2,
lx ly lz
where lx , ly and lz are the characteristic 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).) The values of lx , ly, lz that aren’t specified or are equal to zero will not be
used in calculations.
Default: none. If neither of the keywords SIGMA (see 12.2.72), SIGMAV (see 12.2.73),
LTOSIGMA is specified, an error will be returned.
Sigma-factor can be specified manually using the keywords SIGMA (see 12.2.72), SIG-
MAV (see 12.2.73). If LTOSIGMA is enabled, 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.83). f x is equal to 4, f y = 4, f z = 2.

12.2.74. LTOSIGMA 680

Keywords for formats tN, E1, E3 19.1

12.2.75. SIGMAGD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets the vertical size of a block of matrix material in dual porosity run (2.27)
with gravity imbibition option (2.27.2) (METRIC: m−2 , 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.76).

SIGMAGD matrix-fracture transmissibility is used to calculate the oil flow when:

1. gravity imbibition option is used (2.27.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 asso-
ciated with water.

The area where the fractures are filled with gas, are created with transmissibiliry base on
SIGMAGD (see 12.2.75), areas filled with water, are created with transmissibiliry base on
SIGMA (see 12.2.72).
Sigma-factor is related to the distances between fractures (matrix block sizes) in X, Y and
Z directions:  
1 1 1
σ =4 + + ,
lx2 ly2 lz2
where lx , ly and lz are the characteristic 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 SIGMAGD, SIGMAGDV (see 12.2.76), is specified,

sigma-factor will be taken from SIGMA (see 12.2.72), SIGMAV (see 12.2.73).

12.2.75. SIGMAGD 681

Keywords for formats tN, E1, E3 19.1

Example
SIGMAGD
0.018 /

This example sets sigma-factor equal to 0.018.

12.2.75. SIGMAGD 682

Keywords for formats tN, E1, E3 19.1

12.2.76. SIGMAGDV

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets the vertical size of a block of matrix material in dual porosity run (2.27)
with gravity imbibition option (2.27.2) (METRIC: m−2 , 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.28). The data should be termi-
nated with a slash /.

One value of sigma-factor can be specified for all grid via the keyword SIGMAGD
(see 12.2.75).

SIGMAGDV matrix-fracture transmissibility is used to calculate the oil flow when:

1. gravity imbibition option is used (2.27.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 asso-
ciated with water.

The area where the fractures are filled with gas, are created with transmissibiliry base on
SIGMAGD (see 12.2.75), areas filled with water, are created with transmissibiliry base on
SIGMA (see 12.2.72).
Sigma-factor is related to the distances between fractures (matrix block sizes) in X, Y and
Z directions:  
1 1 1
σ =4 + + ,
lx2 ly2 lz2
where lx , ly and lz are the characteristic 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 SIGMAGD (see 12.2.75), SIGMAGDV (see 12.2.76),
is specified, sigma-factor will be taken from SIGMA (see 12.2.72), SIGMAV (see 12.2.73).

12.2.76. SIGMAGDV 683

Keywords for formats tN, E1, E3 19.1

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.76. SIGMAGDV 684

Keywords for formats tN, E1, E3 19.1

12.2.77. THCONMF

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can be used in dual porosity run (2.27) in thermal models (keyword THER-
MAL, see 12.1.54) or in temperature option in black-oil models (2.26).

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. The data should be terminated with a slash /.

Example
THCONMF
1000*2.5 100*2.8 /

12.2.77. THCONMF 685

Keywords for formats tN, E1, E3 19.1

12.2.78. SIGMATH

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies the multiplier used in calculating the matrix–fracture thermal
transmissibilities for each matrix block if dual porosity (DUALPORO, see 12.1.83) or dual
permeability (DUALPERM, see 12.1.84) options are used. Thermal transmissibilities set
matrix–fracture thermal conductivity coupling. The description of dual porosity (DUALPORO,
see 12.1.83) and dual permeability (DUALPERM, see 12.1.84) options is given in the section
2.27. The keyword can be used if THERMAL option is activated (THERMAL, see 12.1.54).
After SIGMATH one should specify NX * NY * (NZ/2) values (for each matrix block). The
data should be terminated with a slash /.

Example
SIGMATH
1000*0.1 /

12.2.78. SIGMATH 686

Keywords for formats tN, E1, E3 19.1

12.2.79. MULTMF

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can be used in dual porosity run (2.27) DUALPORO (see 12.1.83). 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
should be terminated with a slash /.

12.2.79. MULTMF 687

Keywords for formats tN, E1, E3 19.1

12.2.80. DZMTRX

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets the vertical size of a block of matrix material in dual porosity run (2.27)
with gravity imbibition option (2.27.2) (METRIC: m, FIELD: f t ).

This size is lz in the description of the keyword SIGMA (see 12.2.72).

Obe value should be specified for all grid.The data should be terminated with a slash /. To
set different values for different blocks one should use the keyword DZMTRXV (see 12.2.82).

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.80. DZMTRX 688

Keywords for formats tN, E1, E3 19.1

12.2.81. DZMATRIX

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is an alias of DZMTRXV (see 12.2.82).

12.2.81. DZMATRIX 689

Keywords for formats tN, E1, E3 19.1

12.2.82. DZMTRXV

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets the vertical size of a block of matrix material in dual porosity run (2.27)
with gravity imbibition option (2.27.2) (METRIC: m, FIELD: f t ).

This size is lz in the description of the keyword SIGMA (see 12.2.72).

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.28). The data should be termi-
nated with a slash /.

To set one value of the vertical size of a block of matrix material use the keyword DZMTRX
(see 12.2.80).

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.82. DZMTRXV 690

Keywords for formats tN, E1, E3 19.1

12.2.83. MULTREGT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies transmissibility multiplier between (FLUXNUM, see 12.4.18) or

MULTNUM (see 12.4.22) regions. If MULTNUM (see 12.4.22) isn’t specified, then values of
MULTREGT will be applied to FLUXNUM (see 12.4.18).

The keyword can be used in dual porosity models – 2.27.

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.39),
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 trans-
missibilities 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 arbitrarily many data lines, each terminated with a slash /. All data
should be terminated with a final slash /.
One data line contains the following parameters:

1. first region number;

Default: non-positive or defaulted value corresponds to all regions.

2. last region number;

Default: non-positive or defaulted value corresponds to all regions.

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.
Default: XYZ.

5. apply transmissibility multiplier to non-neighbor connections:

• NNC – apply the transmissibility multiplier only to non-neighbor connections be-

tween regions, specified in 1-st and 2-nd parameter;

12.2.83. MULTREGT 691

Keywords for formats tN, E1, E3 19.1

• NONNC – don’t apply the transmissibility multiplier to non-neighbor connections

between regions, specified in 1-st and 2-nd parameter;
• ALL – apply the transmissibility multiplier to all connections between regions,
specified in 1-st and 2-nd parameter;
• NOAQUNNC – don’t apply the transmissibility multiplier to numerical aquifer
connections;
• Default: ALL.

6. region:

• M – MULTNUM (see 12.4.22);

• F – FLUXNUM (see 12.4.18);
• O – OPERNUM (see 12.4.21);
• Default: M.

!
If either fist region number or last region number is set non-positive or de-
faulted, then that region identifier corresponds to all regions and the multi-
plier is applied to regions with numbers between first and last region numbers
(first region number is not equal to last one), matching the template.

!
If the fist region number and last region number are equal and and positive,
then in that region the transmissibilities in the specified directions are multi-
plied by the specified value, as well as any transmissibilities connecting any
other regions.

Example
MULTREGT
1 2 0.3 'XY'/
1 4 0.65 /
3 3 0.2 'Z'/
7 1* 0.4 /
/

12.2.83. MULTREGT 692

Keywords for formats tN, E1, E3 19.1

12.2.84. ROCKPROP

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can only be used if THERMAL (see 12.1.54) is present.

The keyword specifies properties of cap and base rocks, which will be used to model the
heat exchange between the reservoir and surroundings. These parameters are used for calcu-
lation of the heat loss between the reservoir and surroundings 4.30.

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.38),
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 (METRIC:
kJ/m3 /K 2 , FIELD: Btu/ f t 3 /◦ F 2 ),
Default: 0.
6. calculation method for heat loss: V – Vinsome and Westerveld, N – numerical;
Default: V.

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.38) sets the maximum number of rock types – 2).

12.2.84. ROCKPROP 693

Keywords for formats tN, E1, E3 19.1

12.2.85. ROCKCON

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can only be used if THERMAL (see 12.1.54) is present.

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. This param-
eter is used for calculation of the heat loss between the reservoir and surroundings 4.30. The
properties of cap and base rocks are specified using the keyword ROCKPROP (see 12.2.84).
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.38),

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 shouldn’t be greater
than the 3-rd parameter of the keyword ROCKDIMS, see 12.1.38).

Default: 9th parameter: 1.

12.2.85. ROCKCON 694

Keywords for formats tN, E1, E3 19.1

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.85. ROCKCON 695

Keywords for formats tN, E1, E3 19.1

12.2.86. ROCKCONT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can be used in thermal models (THERMAL (see 12.1.54), model type
E3) and in temperature option (TEMP (see 12.1.64), model type E1).

The keyword specifies the connection between the reservoir and cap and base rocks, initial
temperature, volumetric heat capacity, rock conductivity of reservoir surroundings and mini-
mal 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 E1/E3 compatible analogues ROCKCON (see 12.2.85),
ROCKPROP (see 12.2.84).

Example
ROCKCONT
1 I- 70 2347 4 0 /
3 K+ 60 2347 4 0 /
/

12.2.86. ROCKCONT 696

Keywords for formats tN, E1, E3 19.1

In this example there is the heat exchange between 1-st rock region and reservoir sur-
roundings in I- direction, initial temperature – 70C , volumetric heat capacity – 2347kJ/m3 -C ,
rock conductivity – 4kJ/m-day-C , minimal difference between temperatures – 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.86. ROCKCONT 697

Keywords for formats tN, E1, E3 19.1

12.2.87. THCGAS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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
be terminated with a slash /.
This keyword can be used in thermal models (keyword THERMAL, see 12.1.54) or in temper-
ature option in black-oil models (2.26).

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.87);

• T HCoil – oil phase thermal conductivity, specified via THCOIL (see 12.2.88);

• T HCwater – water phase thermal conductivity, specified via THCWATER (see 12.2.89);

• T HCsolid – solid phase thermal conductivity, specified via THCSOLID (see 12.2.90);

• T HCrock – rock thermal conductivity, specified via THCROCK (see 12.2.91).

12.2.87. THCGAS 698

Keywords for formats tN, E1, E3 19.1

Example
FIELD

...

THCROCK
200000*24.56 /

THCWATER
200000*8.587 /

THCOIL
200000*1.846 /

THCGAS
200000*0.1091 /

THCSOLID
200000*12.36 /

12.2.87. THCGAS 699

Keywords for formats tN, E1, E3 19.1

12.2.88. THCOIL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies oil phase thermal conductivity (T HCoil ) (METRIC: kJ/m/day/K ,
FIELD: Btu/ f t/day/R). One value should be entered for each grid block. The data should
be terminated with a slash /.
This keyword can be used in thermal models (keyword THERMAL, see 12.1.54) or in temper-
ature option in black-oil models (2.26).

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.87);

• T HCoil – oil phase thermal conductivity, specified via THCOIL (see 12.2.88);

• T HCwater – water phase thermal conductivity, specified via THCWATER (see 12.2.89);

• T HCsolid – solid phase thermal conductivity, specified via THCSOLID (see 12.2.90);

• T HCrock – rock thermal conductivity, specified via THCROCK (see 12.2.91).

12.2.88. THCOIL 700

Keywords for formats tN, E1, E3 19.1

Example
FIELD

...

THCROCK
200000*24.56 /

THCWATER
200000*8.587 /

THCOIL
200000*1.846 /

THCGAS
200000*0.1091 /

THCSOLID
200000*12.36 /

12.2.88. THCOIL 701

Keywords for formats tN, E1, E3 19.1

12.2.89. THCWATER

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.
The data should be terminated with a slash /.
This keyword can be used in thermal models (keyword THERMAL, see 12.1.54) or in temper-
ature option in black-oil models (2.26).

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.87);

• T HCoil – oil phase thermal conductivity, specified via THCOIL (see 12.2.88);

• T HCwater – water phase thermal conductivity, specified via THCWATER (see 12.2.89);

• T HCsolid – solid phase thermal conductivity, specified via THCSOLID (see 12.2.90);

• T HCrock – rock thermal conductivity, specified via THCROCK (see 12.2.91).

12.2.89. THCWATER 702

Keywords for formats tN, E1, E3 19.1

Example
FIELD

...

THCROCK
200000*24.56 /

THCWATER
200000*8.587 /

THCOIL
200000*1.846 /

THCGAS
200000*0.1091 /

THCSOLID
200000*12.36 /

12.2.89. THCWATER 703

Keywords for formats tN, E1, E3 19.1

12.2.90. THCSOLID

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.
The data should be terminated with a slash /.
This keyword can only be used in thermal models (THERMAL, see 12.1.54).

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.87);

• T HCoil – oil phase thermal conductivity, specified via THCOIL (see 12.2.88);

• T HCwater – water phase thermal conductivity, specified via THCWATER (see 12.2.89);

• T HCsolid – solid phase thermal conductivity, specified via THCSOLID (see 12.2.90);

• T HCrock – rock thermal conductivity, specified via THCROCK (see 12.2.91).

12.2.90. THCSOLID 704

Keywords for formats tN, E1, E3 19.1

Example
FIELD

...

THCROCK
200000*24.56 /

THCWATER
200000*8.587 /

THCOIL
200000*1.846 /

THCGAS
200000*0.1091 /

THCSOLID
200000*12.36 /

12.2.90. THCSOLID 705

Keywords for formats tN, E1, E3 19.1

12.2.91. THCROCK

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies rock thermal conductivity (T HCrock ) (METRIC: kJ/m/day/K ,

FIELD: Btu/ f t/day/R). One value should be entered for each grid block. The data should
be terminated with a slash /.
This keyword can be used in thermal models (keyword THERMAL, see 12.1.54) or in temper-
ature option in black-oil models (2.26).

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.87);

• T HCoil – oil phase thermal conductivity, specified via THCOIL (see 12.2.88);

• T HCwater – water phase thermal conductivity, specified via THCWATER (see 12.2.89);

• T HCsolid – solid phase thermal conductivity, specified via THCSOLID (see 12.2.90);

• T HCrock – rock thermal conductivity, specified via THCROCK (see 12.2.91).

12.2.91. THCROCK 706

Keywords for formats tN, E1, E3 19.1

Example
FIELD

...

THCROCK
200000*24.56 /

THCWATER
200000*8.587 /

THCOIL
200000*1.846 /

THCGAS
200000*0.1091 /

THCSOLID
200000*12.36 /

12.2.91. THCROCK 707

Keywords for formats tN, E1, E3 19.1

12.2.92. HEATTX

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID x EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies heat transmissibility values (METRIC: kJ/day/K , FIELD:

Btu/day/R) between blocks [I, J, K] and [I + 1, J, K] (see section 4.28), overwriting val-
ues calculated by the program. The thermal option should be activated using the THERMAL
(see 12.1.54) keyword.
The heat transmissibility is calculated by multiplying the thermal conductivity of the rock
by the cross sectional area divided by the distance between block centers.
The heat transmissibility values are specified for for each grid blocks in normal grid order.
The data should be terminated by a slash /.
Example
DIMENS
95 84 122
/
...
HEATTX
2 22 26 52 56 1 50
/

12.2.92. HEATTX 708

Keywords for formats tN, E1, E3 19.1

12.2.93. HEATTY

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID x EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies heat transmissibility values (METRIC: kJ/day/K , FIELD:

Btu/day/R) between blocks [I, J, K] and [I, J + 1, K] (see section 4.28), overwriting val-
ues calculated by the program. The thermal option should be activated using the THERMAL
(see 12.1.54) keyword.
The heat transmissibility is calculated by multiplying the thermal conductivity of the rock
by the cross sectional area divided by the distance between block centers.
The heat transmissibility values are specified for for each grid blocks in normal grid order.
The data should be terminated by a slash /.
Example
DIMENS
95 84 122
/
...
HEATTY
2 22 26 52 56 1 50
/

12.2.93. HEATTY 709

Keywords for formats tN, E1, E3 19.1

12.2.94. HEATTZ

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID x EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies heat transmissibility values (METRIC: kJ/day/K , FIELD:

Btu/day/R) between blocks [I, J, K] and [I, J, K + 1] (see section 4.28), overwriting val-
ues calculated by the program. The thermal option should be activated using the THERMAL
(see 12.1.54) keyword.
The heat transmissibility is calculated by multiplying the thermal conductivity of the rock
by the cross sectional area divided by the distance between block centers.
The heat transmissibility values are specified for for each grid blocks in normal grid order.
The data should be terminated by a slash /.
Example
DIMENS
95 84 122
/
...
HEATTZ
2 22 26 52 56 1 50
/

12.2.94. HEATTZ 710

Keywords for formats tN, E1, E3 19.1

12.2.95. SPECGRID

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.
The data should be terminated with a slash /.
The following parameters are to be specified:

1. the number of blocks in the X-direction (NX in DIMENS, see 12.1.28);

2. the number of blocks in the Y-direction (NY in DIMENS, see 12.1.28);

3. the number of blocks in the Z-direction (NZ in DIMENS, see 12.1.28);

4. the number of reservoirs (NUMRES, see 12.1.76), 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.95. SPECGRID 711

Keywords for formats tN, E1, E3 19.1

12.2.96. BG_xxx

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword defines the mask for a group of blocks that can be later used via CARFINBG
(see 12.2.98) keyword for grid refinement in a certain part of the grid.

In mask’s name must be input directly into this keyword in place of xxx:
• Keyword BG_BG1 denotes the definition of blocks group mask 'BG1'.
• Keyword BG_WELL1_LGR denotes the definition of block group mask 'WELL1_LGR'.
• etc.
The following data should be specified on the line below this keyword:
• flag, indicating whether the grid block belongs to this group:
– 1 – the block will be assigned to the group;
– 0 – the block will not be assigned to the group.
The number of values should be equal to number of blocks.
Data entry must be terminated with slash /.
Example
BG_BG1
3*1 12*0 3*1 12*0 3*1 192*0
3*1 12*0 3*1 12*0 3*1 192*0
3*1 12*0 3*1 12*0 3*1 192*0
3*1 12*0 3*1 12*0 3*1 2442*0 /

CARFINBG
'LGR_1' BG1 5 3 2 /
/

ENDFIN

In this example:
1. Certain blocks of the grid are assigned to the block group 'BG1' via BG_BG1 keyword.
2. The blocks from the block group 'BG1' are refined via CARFINBG keyword.
3. Keyword ENDFIN terminates the entry of parameters for this LGR.

12.2.96. BG_xxx 712

Keywords for formats tN, E1, E3 19.1

12.2.97. CARFIN

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies a Cartesian local grid refinement (LGR) – section 5.5.8. 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 specified
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.101), which terminates data for a local grid refinement.

The following parameters should be specified:

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 blocks along X direction;

9. NY Number of refined blocks along Y direction;

10. NZ Number of refined blocks 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.97. CARFIN 713

Keywords for formats tN, E1, E3 19.1

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 mul-
tiplied 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.97. CARFIN 714

Keywords for formats tN, E1, E3 19.1

12.2.98. CARFINBG

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword defines local grid refinement (LGR) for the blocks group. The blocks group
must be previously defined via BG_xxx (see 12.2.96).

The following parameters should be specified on the line below this keyword:
1. name of the local grid refinement;
2. mask of the blocks group (BG_xxx, see 12.2.96);
3. NI Number of refined blocks along I direction;
4. NJ Number of refined blocks along J direction;
5. NK Number of refined blocks along K direction;
6. 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 refinement).
Default: GLOBAL.
Data entry must be terminated with slash /.
Example
BG_BG1
3*1 12*0 3*1 12*0 3*1 192*0
3*1 12*0 3*1 12*0 3*1 192*0
3*1 12*0 3*1 12*0 3*1 192*0
3*1 12*0 3*1 12*0 3*1 2442*0 /

CARFINBG
'LGR_1' BG1 5 3 2 /
/

ENDFIN

In this example:
1. Certain blocks of the grid are assigned to the block group 'BG1' via BG_BG1 keyword.
2. The blocks from the block group 'BG1' are refined via CARFINBG keyword.
3. Keyword ENDFIN terminates the entry of parameters for this LGR.

12.2.98. CARFINBG 715

Keywords for formats tN, E1, E3 19.1

12.2.99. REFINE

Data x tN x E1 x E3 IM GE ST MO
format
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.5.8. The key-
word 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.101) (which terminates data for a local grid refinement) or another
REFINE (see 12.2.99) 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.17), EQUALS
(see 12.3.23), MULTIPLY (see 12.3.14) and COPYBOX (see 12.3.18) 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.50), DEPTH (see 12.3.28), TRANY (see 12.2.51), TRANZ (see 12.2.52). In addi-
tion, the BOX (see 12.3.3), COPY (see 12.3.17), EQUALS (see 12.3.23) 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.1.136) the following keywords
and their directional equivalents are available: SWL (see 12.6.26), SWCR (see 12.6.29),
SWU (see 12.6.33), SGL (see 12.6.28), SGCR (see 12.6.30), SGU (see 12.6.34), SOWCR
(see 12.6.31), SOGCR (see 12.6.32), KRO (see 12.6.58), KRORW (see 12.6.58), KRORG
(see 12.6.58), KRW (see 12.6.59), KRWR (see 12.6.59), KRG (see 12.6.60), KRGR
(see 12.6.60). In addition, the BOX (see 12.3.3), COPY (see 12.3.17), EQUALS (see 12.3.23)
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-
NUM (see 12.4.3), EQLNUM (see 12.4.9), ROCKNUM (see 12.4.14). In addition, the BOX

12.2.99. REFINE 716

Keywords for formats tN, E1, E3 19.1

(see 12.3.3), COPY (see 12.3.17), EQUALS (see 12.3.23) 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.16.12),
SWAT (see 12.16.14), SGAS (see 12.16.15), RS (see 12.16.37) or PBUB (see 12.16.36),
RV (see 12.16.38) or PDEW (see 12.16.39). BOX (see 12.3.3), ADD (see 12.3.21), COPY
(see 12.3.17), EQUALS (see 12.3.23) 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.99. REFINE 717

Keywords for formats tN, E1, E3 19.1

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.99. REFINE 718

Keywords for formats tN, E1, E3 19.1

12.2.100. INNERWIDTH

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

If this keyword is placed between the keywords CARFIN (see 12.2.97) (or CARFINBG,
see 12.2.98) and ENDFIN (see 12.2.101), then logarithmic refinement will be applied.

In this case the width of the first refined blocks in I , J and K directions should be ex-
plicitly specified.

!
The logarithmic refinement can be applied only in the directions with odd
number of refined blocks. Otherwise it would be impossible to set the central
point where the refinement will be originated. In this case INNERWIDTH
parameters will be ignored for this direction and uniformal refinement will
be used.

The following parameters should be specified on the line below the INNERWIDTH:

1. The width of the central refined blocks in I th direction;

Default: if this parameter is not specified, then the uniformal refinement will be used in
I th direction.

2. The width of the central refined blocks in Jth direction;

Default: if this parameter is not specified, then the uniformal refinement will be used in
Jth direction.

3. The width of the central refined blocks in K th direction;

Default: if this parameter is not specified, then the uniformal refinement will be used in
K th direction.

Data entry must be terminated with slash /.

12.2.100. INNERWIDTH 719

Keywords for formats tN, E1, E3 19.1

Example
CARFIN
LGR1 1 3 1 1 1 1 9 7 1 /
INNERWIDTH
2 2 /
ENDFIN

In this example:

1. The grid box of the blocks that where the refinement will be applied and the number of
refined blocks are defined via CARFIN keyword;

2. The logarithmic refinement is introduced via INNERWIDTH keyword. The width of the
inner-most blocks planes is specified for I th and Jth directions.

3. Keyword ENDFIN terminates the entry of parameters for this LGR.

12.2.100. INNERWIDTH 720

Keywords for formats tN, E1, E3 19.1

12.2.101. ENDFIN

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION SUMMARY x SCHEDULE

The keyword terminates data for a local grid refinement (LGR) – section 5.5.8.

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.99) 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.101), which terminates
data for a local grid refinement.

It is not necessary to insert ENDFIN (see 12.2.101) between successive CARFIN

(see 12.2.97) or REFINE (see 12.2.99) keywords. The primary purpose of ENDFIN
(see 12.2.101) 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.101)
keyword tells the program that subsequent data no longer applies to the local grid named in
the previous REFINE (see 12.2.99) keyword.

The ENDFIN keyword has no associated data.

12.2.101. ENDFIN 721

Keywords for formats tN, E1, E3 19.1

12.2.102. NXFIN / NYFIN / NZFIN

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.5.8).

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.97) introducing the local grid, and be-
fore the local grid data is terminated with ENDFIN (see 12.2.101).

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.97). 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 divi-
sions, 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.97). 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
local cells, second global cell – by 4 local cells, 3-rd – by 3, 4-th – by 4, 5-th – by 2.

12.2.102. NXFIN / NYFIN / NZFIN 722

Keywords for formats tN, E1, E3 19.1

12.2.103. HXFIN / HYFIN / HZFIN

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

These keywords can be used to specify the size ratios of each cell in a local grid refine-
ment (LGR) (HXFIN – in X direction, HYFIN – in Y direction, HZFIN – in Z direction) (section
5.5.8).

These keywords should be placed after the CARFIN (see 12.2.97) keyword introducing the
local grid and before the terminating ENDFIN (see 12.2.101).

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.97) 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.103. HXFIN / HYFIN / HZFIN 723

Keywords for formats tN, E1, E3 19.1

12.2.104. AMALGAM

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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 E1/E3 compatibility field. In tNavigator all LGRs are
considered as with AMALGAM keyword.

12.2.104. AMALGAM 724

Keywords for formats tN, E1, E3 19.1

12.2.105. COARSEN

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets blocks coarsening (see section 5.5.7). 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 dimensions of the coarsened grid within this box are specified as NX, NY, NZ. The data
should be terminated with a slash /.

The following parameters should be specified:

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 coarsened cells along X direction. Number I2 −I1 +1 should be divisible

by NX;

8. NY Number of coarsened cells along Y direction. Number J2−J1+1 should be divisible

by NY;

9. NZ Number of coarsened cells along Z direction. Number K2 − K1 + 1 should be divis-

ible 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.105. COARSEN 725

Keywords for formats tN, E1, E3 19.1

2. Then to this new permeability property array COARSEN is applied – during coars-
ening values are recalculated as pore volume weighted average.

• If the keyword PINCH (see 12.2.58) 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
don’t 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.

Technically, one of the original blocks in each coarse block is chosen as a representative.
It stores the summary physical quantities, well perforations, and aquifer connections of the
original blocks. If the representative block was initially inactive for any reason, it is automat-
ically made active. The region numbers (SATNUM, ROCKNUM, PVTNUM, etc.) of the coarse
block are inherited from the representative block.
The COARSEN_BLOCK_DATA_LOGIC option of the keyword TNAVCTRL (see 12.1.4)
controls the logic of selection of the representative block. According to this option, either the
centermost block in the group, or the centermost active block is selected. The latter option is
preferred in case if the model might contain nonsensical data in the inactive blocks.
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.105. COARSEN 726

Keywords for formats tN, E1, E3 19.1

12.2.106. GRIDFILE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword defines save of calculation results in EGRID and INIT format files
(*.EGRID format and *.INIT format of E1/E3). These files will be generated, if simu-
lator (its console version) is run with options -e, -i.
The following parameters should be defined (list should end with a slash, /).

• this is an E1/E3 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 (don’t 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
options -e, -i. File of *.GRID format will not be generated (first argument of keyword
GRIDFILE is ignored in current version of tNavigator).

12.2.106. GRIDFILE 727

Keywords for formats tN, E1, E3 19.1

12.2.107. PLMIXNUM

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies regions with different polymer properties – POLYMER

(see 12.1.51). Polymer Flood is described in the section 2.16.
For the full description of ASP (Alkaline-Surfactant-Polymer) mathematical model, see
the section 5.9. ASP model description.
The number of values should be equal to the number of grid blocks. The data should be
terminated with a slash /.

Maximal number of these regions is defined via the 10-th parameter of REGDIMS
(see 12.1.32).
Each region with different polymer properties can have its own values of Todd-Longstaff mix-
ing parameter (PLMIXPAR, see 12.8.29) and maximum polymer and salt concentrations used
in the mixing parameter calculation of fluid component viscosity (PLYMAX, see 12.8.28).
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.107. PLMIXNUM 728

Keywords for formats tN, E1, E3 19.1

12.2.108. ROCKDEN

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can be used to specify:

• coal density (METRIC: kg/m3 , FIELD: lb/ f t 3 ) in Coal Bed Methane Model – 2.28;

• rock density (METRIC: kg/m3 , FIELD: lb/ f t 3 ) for simulation of solid adsorbation on
to the rock formation – 3.12;

• rock density (METRIC: kg/m3 , FIELD: lb/ f t 3 ) for simulation of geomechanical ef-
fects – 2.29.1. The keyword GEOMECH (see 12.1.99) with option FE should be specified
in the section RUNSPEC.

The number of values should be equal to the number of grid blocks. The data should be
terminated with a slash /.

Example
ROCKDEN
1200*1340 1200*1335 /

12.2.108. ROCKDEN 729

Keywords for formats tN, E1, E3 19.1

12.2.109. IMPORT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword imports cubes into a model. Cubes should be specified in binary format.
Grid geometries supported in tNavigator are described in details in the section 5.5.

The following parameters should be specified:

1. file name;

2. file format: UNFORMATTED;

Default: UNFORMATTED.

The data should be terminated with a slash /.

Example
IMPORT
X.AAA /
In this example the keyword IMPORT (see 12.2.109) imports the file X.AAA to the model.

12.2.109. IMPORT 730

Keywords for formats tN, E1, E3 19.1

12.2.110. VISGRID

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword is used to specify file of .EGRID format to visualize grid. This keyword is
used in models with unstructured grid. Grid geometries supported in tNavigator are described
in details in the section 5.5.
The following parameters should be specified:

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;

Default: UNFORMATTED.

The data should be terminated with a slash /.

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 calculation grid); this affects the DEPTH (see 12.3.28) keyword.
During model reading in the log there will be a warning about maximal displacement of grid
block depths.

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.

In tNavigator the case 0 is supported – composite grid. In this case we check 26-th
parameter that sets the number of composite grids.

12.2.110. VISGRID 731

Keywords for formats tN, E1, E3 19.1

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.110. VISGRID 732

Keywords for formats tN, E1, E3 19.1

12.2.111. DIFFMMF

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword can be used only in model with dual porosity mode (the keyword DU-
ALPORO, see 12.1.83) which uses either the molecular diffusion option (see the keyword
DIFFUSE (see 12.1.70) and section Dual porosity) or the Coal Bed Methane option (the
keyword COAL (see 12.1.85) and section 2.28. Coal Bed Methane Model).
The keyword sets multipliers of diffusivities which calculated for non-neighbour con-
nections (see the keyword NNC, see 12.2.54). Connections represents the matrix-to-fracture
flows.
Values which specified for matrix cells (i.e. upper half of the model) are used as multipli-
ers. Values which specified for fracture cells are ignored.
The following parameters should be specified:

1. multipliers of diffusivities for each grid cell or each box cell (the keyword BOX,
see 12.3.3);
Default: 1 for cells out of specified box.

The data should be terminated with a slash /.

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.111. DIFFMMF 733

Keywords for formats tN, E1, E3 19.1

12.2.112. DIFFMX

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies diffusivity multipliers in the X direction. This value multiplies on
the diffusivities calculated for the +X face of each grid block, e.g. a face between blocks
[I, J, K] and [I + 1, J, K]. Thus, a value of DIFFMX defined for block [I, J, K] multiplies the
diffusivity between blocks [I, J, K] and [I + 1, J, K].
This keyword can be used if the molecular diffusion option is defined by DIFFUSE
(see 12.1.70) in the RUNSPEC section when a Cartesian grid is used.
This keyword is followed by one non negative real number for each grid block in the
current input box. Data should be terminated with a slash /. If DIFFMX value is not specified
in the GRID section, it is set to be 1.0 (default value). If DIFFMX values are defined in the
GRID section, they apply only to the diffusivities calculated based on information defined in
the GRID section.
The multipliers are input by keyword DIFFMX (see 12.2.112) in the same way as MULTX
(see 12.2.15) in the GRID section.
Notice that non-neighbor connections appeared due to faults will have diffusivities which
reflect the DIFFMX values.
See also keyword DIFFMX- (see 12.2.113).
Example
BOX
1 95 1 99 39 76 /
DIFFMX
357390*1.0 /
ENDBOX

12.2.112. DIFFMX 734

Keywords for formats tN, E1, E3 19.1

12.2.113. DIFFMX-

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies diffusivity multipliers in the negative X direction. This value mul-
tiplies on the diffusivities calculated for the -X face of each grid block, e.g. a face between
blocks [I, J, K] and [I − 1, J, K]. Thus, a value of DIFFMX- defined for block [I, J, K] multi-
plies the diffusivity between blocks [I, J, K] and [I − 1, J, K].
This keyword can be used if the molecular diffusion option is defined by DIFFUSE
(see 12.1.70) in the RUNSPEC section when a Cartesian grid is used. Furthermore, the neg-
ative direction transmissibility multipliers should be defined by GRIDOPTS (see 12.1.95)
keyword in the RUNSPEC section.
This keyword is followed by one non negative real number for each grid block in the
current input box. Data should be terminated with a slash /. If DIFFMX- value is not specified
in the GRID section, it is set to be 1.0 (default value). If DIFFMX- values are defined in the
GRID section, they apply only to the diffusivities calculated based on information defined in
the GRID section.
The multipliers are input by keyword DIFFMX- (see 12.2.113) in the same way as MULTX-
(see 12.2.16) in the GRID section.
If both DIFFMX and DIFFMX- are defined then their product is applied. For example, if
DIFFMX is defined for the block [I, J, K] and DIFFMX- is defined for the block [I + 1, J, K]
then the diffusivity multiplier between these adjacent blocks is a product of DIFFMX and
DIFFMX-.
Notice that non-neighbor connections caused by faults appearance will have diffusivities
which reflect the DIFFMX and DIFFMX- values. For example, a fault non-neighbor connec-
tion between a cell [I, J, K1] and a block [I + 1, J, K2] in an adjacent column will have a
diffusivity multiplier of DIFFMX for block [I, J, K1] or DIFFMX- for block [I + 1, J, K2], or
the product of the two.
See the keyword DIFFMX (see 12.2.112).
Example
BOX
1 95 1 99 39 76 /
DIFFMX-
357390*1.0 /
ENDBOX

12.2.113. DIFFMX- 735

Keywords for formats tN, E1, E3 19.1

12.2.114. DIFFMY

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies diffusivity multipliers in the Y direction. This value multiplies on
the diffusivities calculated for the +Y face of each grid block, e.g. a face between blocks
[I, J, K] and [I, J + 1, K]. Thus, a value of DIFFMY defined for block [I, J, K] multiplies the
diffusivity between blocks [I, J, K] and [I, J + 1, K].
This keyword can be used if the molecular diffusion option is defined by DIFFUSE
(see 12.1.70) in the RUNSPEC section when a Cartesian grid is used.
This keyword is followed by one non negative real number for each grid block in the
current input box. Data should be terminated with a slash /. If DIFFMY value is not specified
in the GRID section, it is set to be 1.0 (default value). If DIFFMY values are defined in the
GRID section, they apply only to the diffusivities calculated based on information defined in
the GRID section.
The multipliers are input by keyword DIFFMY (see 12.2.114) in the same way as MULTY
(see 12.2.17) in the GRID section.
Notice that non-neighbor connections appeared due to faults will have diffusivities which
reflect the DIFFMY values.
See also the keyword DIFFMY- (see 12.2.115).
Example
BOX
1 95 1 99 39 76 /
DIFFMY
357390*1.0 /
ENDBOX

12.2.114. DIFFMY 736

Keywords for formats tN, E1, E3 19.1

12.2.115. DIFFMY-

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies diffusivity multipliers in the negative Y direction. This value mul-
tiplies on the diffusivities calculated for the -Y face of each grid block, e.g. a face between
blocks [I, J, K] and [I, J − 1, K]. Thus, a value of DIFFMY- defined for block [I, J, K] multi-
plies the diffusivity between blocks [I, J, K] and [I, J − 1, K].
This keyword can be used if the molecular diffusion option is defined by DIFFUSE
(see 12.1.70) in the RUNSPEC section when a Cartesian grid is used. Furthermore, the neg-
ative direction transmissibility multipliers should be defined by GRIDOPTS (see 12.1.95)
keyword in the RUNSPEC section.
This keyword is followed by one non negative real number for each grid block in the
current input box. Data should be terminated with a slash /. If DIFFMY- value is not specified
in the GRID section, it is set to be 1.0 (default value). If DIFFMY- values are defined in the
GRID section, they apply only to the diffusivities calculated based on information defined in
the GRID section.
The multipliers are input by keyword DIFFMY- (see 12.2.115) in the same way as MULTY-
(see 12.2.18) in the GRID section.
If both DIFFMY and DIFFMY- are defined then their product is applied. For example, if
DIFFMY is defined for the block [I, J, K] and DIFFMY- is defined for the block [I, J + 1, K]
then the diffusivity multiplier between these adjacent blocks is a product of DIFFMY and
DIFFMY-.
Notice that non-neighbor connections caused by faults appearance will have diffusivities
which reflect the DIFFMY and DIFFMY- values. For example, a fault non-neighbor connec-
tion between a cell [I, J, K1] and a block [I, J + 1, K2] in an adjacent column will have a
diffusivity multiplier of DIFFMY for block [I, J + 1, K1] or DIFFMY- for block [I, J + 1, K2],
or the product of the two.
See the keyword DIFFMY (see 12.2.114).
Example
BOX
1 95 1 99 39 76 /
DIFFMY-
357390*1.0 /
ENDBOX

12.2.115. DIFFMY- 737

Keywords for formats tN, E1, E3 19.1

12.2.116. DIFFMZ

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies diffusivity multipliers in the Z direction. This value multiplies on
the diffusivities calculated for the +Z face of each grid block, e.g. a face between blocks
[I, J, K] and [I, J, K + 1]. Thus, a value of DIFFMZ defined for block [I, J, K] multiplies the
diffusivity between blocks [I, J, K] and [I, J, K + 1].
This keyword can be used if the molecular diffusion option is defined by DIFFUSE
(see 12.1.70) in the RUNSPEC section when a Cartesian grid is used.
This keyword is followed by one non negative real number for each grid block in the
current input box. Data should be terminated with a slash /. If DIFFMZ value is not specified
in the GRID section, it is set to be 1.0 (default value). If DIFFMZ values are defined in the
GRID section, they apply only to the diffusivities calculated based on information defined in
the GRID section.
The multipliers are input by DIFFMZ (see 12.2.116) keyword in the same way as MULTZ
(see 12.2.19) in the GRID section.
Notice that non-neighbor connections appeared due to pinchouts will have diffusivities
which reflect the DIFFMZ (see 12.2.116) values. Their behavior is similar to the treatment of
the transmissibility multipliers MULTZ (see 12.2.19).
See also keyword DIFFMZ- (see 12.2.117).
Example
BOX
1 95 1 99 39 76 /
DIFFMZ
357390*1.0 /
ENDBOX

12.2.116. DIFFMZ 738

Keywords for formats tN, E1, E3 19.1

12.2.117. DIFFMZ-

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies diffusivity multipliers in the negative Z direction. This value mul-
tiplies on the diffusivities calculated for the -Z face of each grid block, e.g. a face between
blocks [I, J, K] and [I, J, K − 1]. Thus, a value of DIFFMZ- defined for block [I, J, K] multi-
plies the diffusivity between blocks [I, J, K] and [I, J, K − 1].
This keyword can be used if the molecular diffusion option is defined by DIFFUSE
(see 12.1.70) in the RUNSPEC section when a Cartesian grid is used. Furthermore, the
negative direction transmissibility multipliers should be defined by keyword GRIDOPTS
(see 12.1.95) in the RUNSPEC section.
This keyword is followed by one non negative real number for each grid block in the
current input box. Data should be terminated with a slash /. If DIFFMZ- value is not specified
in the GRID section, it is set to be 1.0 (default value). If DIFFMZ- values are defined in the
GRID section, they apply only to the diffusivities calculated based on information defined in
the GRID section.
The multipliers are input by keyword DIFFMZ- (see 12.2.117) in the same way as MULTZ-
(see 12.2.20) in the GRID section.
If both DIFFMZ and DIFFMZ- are defined then their product is applied. For example, if
DIFFMZ is defined for the block [I, J, K] and DIFFMZ- is defined for the block [I, J, K + 1]
then the diffusivity multiplier between these adjacent blocks is a product of DIFFMZ and
DIFFMZ-.
Notice that non-neighbor connections caused by pinchouts appearance will have diffu-
sivities which reflect the DIFFMZ- values. Their behavior is similar to the treatment of the
transmissibility multipliers MULTZ-.
See the DIFFMZ (see 12.2.116) keyword.
Example
BOX
1 95 1 99 39 76 /
DIFFMZ-
357390*1.0 /
ENDBOX

12.2.117. DIFFMZ- 739

Keywords for formats tN, E1, E3 19.1

12.2.118. INIT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets the output of INIT file placed in the RESULTS folder and contain-
ing model information from sections GRID, PROPS, REGIONS. This keyword is mandatory.
Without it, tNavigator will not write the INIT file. All options of results saving in tNavigator
are available in the section Results of tNavigator calculation.

12.2.118. INIT 740

Keywords for formats tN, E1, E3 19.1

12.2.119. RPTGRID/ RPTGRIDL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

These keywords control output from GRID section for other simulators working in E1/E3
formats.

This keyword is IGNORED because of specific output options used in tNavigator (RP-
TRST, see 12.16.5).

12.2.119. RPTGRID/ RPTGRIDL 741

Keywords for formats tN, E1, E3 19.1

12.2.120. YOUNGMOD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies Young’s modulus (METRIC: bars, FIELD: psi) for rock stress
balance. The geomechanical model is described in the section 2.29.1. YOUNGMOD can be
used if only the keyword GEOMECH (see 12.1.99) (option FE) is set in the section RUNSPEC.
The keyword is followed by one non-negative real value of Young’s modulus for each grid
block. The data should be terminated with a slash /. Grid blocks are in the following order:
index cycles first along X-axis, then along the Y- and Z-axis indices. Repeat counts may be
used for repeated values (e.g., 64*50000).
Young’s modulus is not specified by default. The calculation will stop if the GEOMECH
(see 12.1.99) keyword is specified but the Young’s modulus value is not set.
In this example Young’s modulus equal to 50000 is specified for each grid block.
Example
DIMENS
4 4 4 /
...
YOUNGMOD
64*50000 /

12.2.120. YOUNGMOD 742

Keywords for formats tN, E1, E3 19.1

12.2.121. POISSONR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies Poisson’s ratio for rock stress balance. The geomechanical model
is described in the section 2.29.1. POISSONR can be used if only the keyword GEOMECH
(see 12.1.99) (option FE) is set in the section RUNSPEC.
The keyword is followed by one non-negative real value of Poisson’s ratio for each grid
block. The data should be terminated with a slash /. Grid blocks are in the following order:
index cycles first along X-axis, then along the Y- and Z-axis indices. Repeat counts may be
used for repeated values (e.g., 64*0.2).
Poisson’s ratio is not specified by default. The calculation will stop if the GEOMECH
(see 12.1.99) keyword is specified but the Poisson’s ratio value is not set.
In this example Poisson’s ratio equal to 0.2 is specified for each grid block.
Example
DIMENS
4 4 4 /
...
POISSONR
64*0.2 /

12.2.121. POISSONR 743

Keywords for formats tN, E1, E3 19.1

12.2.122. BIOTC

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies the Biot’s constant for interaction between rock and fluid. The ge-
omechanical model is described in the section 2.29.1. BIOTC can be used if only the keyword
GEOMECH (see 12.1.99) (option FE) is set in the section RUNSPEC.
The keyword is followed by one non-negative real value of the Biot’s constant for each
grid block. The data should be terminated with a slash /. The Biot’s constant is dimensionless
value and should be greater than porosity and less than or equal to 1.
Grid blocks are in the following order: index cycles first along X-axis, then along the Y-
and Z-axis indices. Repeat counts may be used for repeated values (e.g., 64*0.29).
Default: 1.
In this example the Biot’s constant equal to 0.29 is specified for each grid block.
Example
DIMENS
4 4 4 /
...
BIOTC
64*0.29 /

12.2.122. BIOTC 744

Keywords for formats tN, E1, E3 19.1

12.2.123. CORNERS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets coordinates of block grid corners (METRIC: m, FIELD: f t ). The data
should be terminated with a slash /.
Grid geometries supported in tNavigator are described in details in the section 5.5.

!
To this keyword CORNERS 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. In this case grid should be included in the model as .grid
via the keyword GDFILE (see 12.2.49).
Data specification.
In case if the model contains nx · ny · nz blocks (DIMENS, see 12.1.28), then one should set
3 · 8 · nx · ny · nz coordinates of their corners. For models with single porosity the order is the
following:

• 8 · nx · ny · nz – X coordinates of block corners;

• 8 · nx · ny · nz – Y coordinates of block corners;

• 8 · nx · ny · nz – Z coordinates of block corners.

Geometry for dual porosity models.

For models with dual porosity (section 2.27) the order is the following:
nz
• 8 · nx · ny · – X coordinates of matrix block corners;
2
nz
• 8 · nx · ny · – Y coordinates of matrix block corners;
2
nz
• 8 · nx · ny · – Z coordinates of matrix block corners;
2
nz
• 8 · nx · ny · – X coordinates of fracture block corners;
2
nz
• 8 · nx · ny · – Y coordinates of fracture block corners;
2
nz
• 8 · nx · ny · – Z coordinates of fracture block corners.
2
To set the half data (logic of the keyword DPGRID, see 12.2.71) the coordinates should be
specified for matrix blocks:

12.2.123. CORNERS 745

Keywords for formats tN, E1, E3 19.1

nz
• 8 · nx · ny · – X coordinates of matrix block corners;
2
nz
• 8 · nx · ny · – Y coordinates of matrix block corners;
2
nz
• 8 · nx · ny · – Z coordinates of matrix block corners.
2
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 a grid of 2 × 2 × 1 size is specified. Block size along X and Y directions
is 50 m, along Z direction it is 2 m. Depth of the top layer is 500 m, hence z-coordinates of
the top layer is 500.

12.2.123. CORNERS 746

Keywords for formats tN, E1, E3 19.1

Example 2. Format Y-pillar grid

!
To the keyword CORNERS the format Y-pillar grid is converted; so this for-
mat can be used in the model without modifications. In this case grid should
be included in the model as .grid via the keyword GDFILE (see 12.2.49).

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.123. CORNERS 747

Keywords for formats tN, E1, E3 19.1

12.2.124. DEACDEPT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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 the specified value.

The data should be terminated with a slash /.

The keyword can be used in conjunction with the keyword AQUGP (see 12.17.15) for
setting an aquifer on certain depth and deactivating blocks below it.
Aquifer models along with corresponding keywords are described in the section 2.13.
Example
DEACDEPT
2000 /

12.2.124. DEACDEPT 748

Keywords for formats tN, E1, E3 19.1

12.2.125. FRACTURE_PATH

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies a polyline (set of points in format x, y, z) to create a fracture model
based on the local grid refinement (LGR). More detailed information about how to create a
fracture model using the local grid refinement (LGR) is given in the section 5.8.
The line following the keyword contains:

• polyline name. There is no limit on the polyline name length;

• <integer> – the number of polyline point (from the below list of points) in which the
polyline is linked to the well bore.

Further, coordinates of polyline points are listed. Each point coordinates should be written
on new line as:
x1 y1 z1
...
xn yn zn

Data should be terminated with a slash / on a new line.

Example
FRACTURE_PATH
PATH_ONE 3
-500 100 -400
-100 -50 50
0 0 0
100 20 -50
300 -300 -700
/
In this example the polyline PATH_ONE is specified (see figure 52) having 5 points with
coordinates: 1– (-500, 100,-400), 2– (-100,-50,50), 3 –(0,0,0), 4–(100,20,-50) and 5–(300,
-300, -700). The third point (with coordinates (0,0,0)) is the polyline anchor point.

12.2.125. FRACTURE_PATH 749

Keywords for formats tN, E1, E3 19.1

WELL

ANCHOR POINT 4
3 FRACTURE_ZONE
2

FRACTURE_PATH

5
NONFRACTURE_ZONE

5
FRACTURE_PATH

4
WELL
3

2 ANCHOR POINT

z
Figure 52. XY projection of polyline (top view). XZ projection (front view).

12.2.125. FRACTURE_PATH 750

Keywords for formats tN, E1, E3 19.1

12.2.126. FRACTURE_PLANE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies a set of arbitrary polylines defined by the keyword FRAC-
TURE_PATH (see 12.2.125). More detailed information about how to create a fracture model
using the local grid refinement (LGR) is given in the section 5.8.
The line following the keyword contains:

• name of polylines set. There is no limit on the set name length;

Further, names of polylines are listed:

• 'path_name1';

• ...

• 'path_nameN'.

Polylines should be specified in advance by the keyword FRACTURE_PATH (see 12.2.125).

Each polyline name should be written on new line.
Data should be terminated with a slash / on a new line.
If a set of polylines contains only one polyline then it is not required to specify a set
of polylines using FRACTURE_PLANE, instead you can use a polyline name (specified by
FRACTURE_PATH, see 12.2.125) when creating a fracture template (see keyword FRAC-
TURE_TEMPLATE, see 12.2.127).
Example
FRACTURE_PLANE
PLANE_ONE
PATH_ONE
PATH_TWO
/
In this example a set of polylines PLANE_ONE consisting of two polylines – PATH_ONE
and PATH_TWO is created.

12.2.126. FRACTURE_PLANE 751

Keywords for formats tN, E1, E3 19.1

12.2.127. FRACTURE_TEMPLATE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies a fracture template. More detailed information about how to create
a fracture model using the local grid refinement (LGR) is given in the section 5.8.
x
y EFFECTIVE_WIDTH
NONFRACTURE_ZONE
FRACTURE_ZONE
∆

UP
WELL

W2 FRACTURE_PATH
W1 ANCHORPOINT
DOWN

∆
z

∆ L2 L1 ∆
LEN2 LEN1

Figure 53. Schematic model of a fracture (cylinder) and a fracture stimulated zone (ellipsoid).

On a new line, following the keyword, fracture parameters are indicated. Each parameter
starts on a new line and is terminated with a symbol /. It is required to specify the following
parameters:

1. template name <integer 1> <integer 2> <integer 3>

A template name (arbitrary number of characters) and LGR parameters (the number
of refined blocks along X, Y, Z axes, respectively). Each initial coarse grid block is

12.2.127. FRACTURE_TEMPLATE 752

Keywords for formats tN, E1, E3 19.1

subdivided to the number of refined blocks equal to <integer 1> × <integer 2> ×
<integer 3>.
The global grid refinement method can be specified using a parameter REFINEMENT
(see below). Coarse grid blocks are subdivided logarithmically in the plane perpen-
dicular to the fracture plane if the fracture located in one layer of coarse grid blocks,
otherwise coarse grid blocks are subdivided uniformly. Notice that if a block size does
not allow to carried out logarithmic subdivision then the block will be subdivided uni-
formly.

2. PLANE <name of polylines set>

Name of polylines set specified by the keyword FRACTURE_PLANE (see 12.2.126). If a
set of polylines consists of one polyline (specified by FRACTURE_PATH, see 12.2.125)
you can specify here a polyline name instead of a set name. In figure 53 the polyline is
shown with dashed line and denoted by FRACTURE_PATH. The polyline consists of
three points. The polyline is linked to the well bore (WELL) in 2-nd point – ANCHOR
POINT;

3. UP <real>
A fracture height measured upward from an anchor point (e.g., in the figure 53 in the
direction opposite to Z axis) (METRIC: m; FIELD: f t ). The anchor point is specified
in the keyword FRACTURE_WELL (see 12.2.128);

4. DOWN <real>
A fracture height measured downward from an anchor point (e.g., in the figure 53 in Z
axis direction) (METRIC: m; FIELD: f t ). The anchor point is specified in the keyword
FRACTURE_WELL (see 12.2.128);

5. STIMULATED_WIDTH_R <real>
A width of the fracture stimulated zone to the right from an anchor point along Y axis
(METRIC: m; FIELD: f t ). In figure 53 the width of the fracture stimulated zone to the
right from anchor point is denoted by W1 ;

6. STIMULATED_WIDTH_L <real>
A width of the fracture stimulated zone to the left from an anchor point along Y axis
(METRIC: m; FIELD: f t ). In figure 53 the width of the fracture stimulated zone to the
left from the anchor point is denoted by W2 ;

Other parameters are optional:

7. LEVEL_UP <integer>
A restriction of fracture length (in terms of initial grid blocks) measured upward from
an anchor point. Using these options it is possible to change a fracture height specified
by the option UP. The block with an anchor point is considered to be a zero block;

12.2.127. FRACTURE_TEMPLATE 753

Keywords for formats tN, E1, E3 19.1

8. LEVEL_DOWN <integer>
A restriction of fracture length (in terms of initial grid blocks) measured downward from
an anchor point. Using these options it is possible to change a fracture height specified
by the option DOWN. The block with an anchor point is considered to be a zero block;

9. EFFECTIVE_WIDTH <real>
A fracture width (METRIC: m; FIELD: f t );
Default: METRIC: 0.6096 m; FIELD: 2 f t .

10. WIDTH <real>

Fracture width value that will be used for permeability adjustment in refined blocks
of Fracture Zone (METRIC: m; FIELD: f t ). The permeability recalculation algorithm
description is provided in section Permeability Adjustment in Fracture Zone.
Default: The value is taken from EFFECTIVE_WIDTH.

11. WIDTH2 <real>

Dual porosity models: Fracture width value that will be used for permeability adjust-
ment in refined blocks of Fracture Zone (METRIC: m; FIELD: f t ).
In this case the WIDTH parameter refers to Matrix media, whereas WIDTH2 is used for
permeability recalculation in fractures.
Default: The value is taken from EFFECTIVE_WIDTH.

12. REFINEMENT <method of refinement>

This parameter specifies a method of coarse grid refinement (LGR) in fracture zone and
SRV zone (non fracture zone NFZ). The number of refined blocks is specified in the
1-st parameter of this keyword after template name. The following refinement methods
are available:

• UNIFORM – corresponding blocks of coarse grid are refined uniformly;

• LOGARITHMIC_SIMPLE – corresponding blocks of coarse grid are subdivided
logarithmically in a plane perpendicular to a fracture plane if the fracture located in
one layer of coarse grid blocks. A block containing an anchor point is subdivided
logarithmically (if a block size allows a logarithmic subdivision) in each direc-
tion from the anchor point (in the plane perpendicular to the fracture plane). The
smallest step size of grid refinement in the direction perpendicular to the fracture
is equal to the fracture width (option EFFECTIVE_WIDTH), while the smallest step
size of grid refinement in the direction along the fracture is calculated automati-
cally and can be smaller than the fracture width. The maximum step size of grid
refinement is specified automatically such as the number of refined blocks to the
left and right of the anchor point is equal. Furthermore, if the specified number of
refined blocks (in the plane perpendicular to the fracture plane) is even then the
block containing the anchor point will be subdivided into odd number of blocks
(specified number of blocks +1);

12.2.127. FRACTURE_TEMPLATE 754

Keywords for formats tN, E1, E3 19.1

• LOGARITHMIC_DETAILED – in contrast to the described above method

(LOGARITHMIC_SIMPLE) the maximum size of refined block along axis per-
pendicular to the fracture is specified as: let’s n is the number of refined blocks in
the direction perpendicular to the fracture then the maximum size of refined block
can not be larger than 1/n of corresponding coarse grid block size. This method
allows to get a detailed refinement of the fracture zone, however, the number of
refined blocks might be different from the specified value.
• Default: LOGARITHMIC_DETAILED.

13. PERM_FZ <real>

The specified permeability value (mD) is assigned to all refined blocks (with
nonzero pore volume) which the defined fracture crosses through (denoted by FRAC-
TURE_ZONE in figure 53);
Default: permeability value in a coarse grid block.

14. PERM_FZ2 <real>

Dual porosity models: The specified permeability value (mD) is assigned to all re-
fined blocks of fracture (with nonzero pore volume) which the defined fracture crosses
through. In this case the permeability value specified with the option PERM_FZ is
assigned to all refined blocks of matrix;
Default: PERM_FZ.

15. PERM_NFZ <real>

The specified permeability value (mD) is assigned to all refined blocks (with nonzero
pore volume) belonging to the fracture stimulated zone (denoted by NONFRAC-
TURE_ZONE in figure 53);
Default: permeability value in a coarse grid block.

16. PERM_NFZ2 <real>

Dual porosity models: The specified permeability value (mD) is assigned to all refined
blocks of fracture (with nonzero pore volume) belonging to the defined fracture stimu-
lated zone. In this case the permeability value specified with the option PERM_NFZ is
assigned to correspondent refined blocks of matrix;
Default: PERM_NFZ.

17. NTG_ACT <real>

When the defined fracture is activated for all refined blocks with zero pore volume
belonging to the defined fracture or the fracture stimulated zone the pore volume is
calculated as a product of block geometrical volume, porosity (option PORO_ACT)
and net–to–gross (option NTG_ACT), then the specified value of net–to–gross will be
assigned to all these blocks;
Default: 1.

12.2.127. FRACTURE_TEMPLATE 755

Keywords for formats tN, E1, E3 19.1

18. NTG_ACT2 <real>

Dual porosity models: When the defined fracture is activated for all refined blocks
of fracture with zero pore volume belonging to the defined fracture or the fracture
stimulated zone the pore volume is calculated as a product of block geometrical volume,
porosity (option PORO_ACT2) and net–to–gross (option NTG_ACT2) and the specified
value of net–to–gross will be assigned to all these blocks. In this case the net–to–gross
specified with the option NTG_ACT is assigned to all correspondent blocks of matrix;
Default: 1.

19. PORO_ACT <real>

When the defined fracture is activated for all refined blocks with zero pore volume
belonging to the defined fracture or the fracture stimulated zone the pore volume is
calculated as a product of block geometrical volume, porosity (option PORO_ACT) and
net–to–gross (option NTG_ACT) and the specified value of porosity will be assigned to
all these blocks;
Default: 0.001.

20. PORO_ACT2 <real>

Dual porosity models: When the defined fracture is activated for all refined blocks
of fracture with zero pore volume belonging to the defined fracture or the fracture
stimulated zone the pore volume is calculated as a product of block geometrical vol-
ume, porosity (option PORO_ACT2) and net–to–gross (option NTG_ACT2), then the
specified value of porosity will be assigned to all these blocks. In this case the porosity
specified with the option PORO_ACT is assigned to all correspondent blocks of matrix;
Default: 0.0001.

21. PERM_ACT <real>

When the defined fracture is activated for all refined blocks with zero pore volume
belonging to the defined fracture or the fracture stimulated zone the pore volume is
calculated as a product of block geometrical volume, porosity (option PORO_ACT)
and net–to–gross (option NTG_ACT), then the specified value of permeability will be
assigned to all these blocks;

22. PERM_ACT2 <real>

Dual porosity models: When the defined fracture is activated for all refined blocks
of fracture with zero pore volume belonging to the defined fracture or the fracture
stimulated zone the pore volume is calculated as a product of block geometrical volume,
porosity (option PORO_ACT2) and net–to–gross (option NTG_ACT2) and the specified
value of permeability will be assigned to all these blocks. In this case the permeability
specified with the option PERM_ACT is assigned to all correspondent blocks of matrix;

23. SHAPEXY1 <real>

Curvature parameter αxy1 defining the SRV boundary shape in region I of Fracture
Plane top view (see figure 54). The curvature value must be ≥ 1. Value 1 denotes a

12.2.127. FRACTURE_TEMPLATE 756

Keywords for formats tN, E1, E3 19.1

x y
αxz3 αxz4
αyz3 αyz4

III IV
III IV
WELL
WELL
II I II I
αxz2 αxz1 αyz2 αyz1
z z
x
y
WELL y αxz3 αxz4
αyz3
αxy2 b1 αxy1
αyz4
II I αxy3 αxy4
a2 a1
III IV αxy2 αxy1
αxy3 b2 αxy4
αyz1 αyz2
x αxz2 αxz1
z
Figure 54. Distribution of curvatures: Front view (plane xz). Side view (plane yz). Top view
(plane xy).
Note: The axes on the picture correspond to the axes of Fracture Plane and may not correlate
with the Grid geometry!

straight line (rhomboid boundary). Value 2 denotes an arc (ellipsoid boundary). If the
specified value greater than or equal to 150 for any SHAPE parameter, then both FZ
and NFZ would have a rectangular boundaries in all Fracture Plane views;
Default: 2.

24. SHAPEXY2 <real>

Curvature parameter αxy2 defining the SRV boundary shape in region II of Fracture
Plane top view (see figure 54). The curvature value must be ≥ 1. Value 1 denotes a
straight line (rhomboid boundary). Value 2 denotes an arc (ellipsoid boundary). If the
specified value greater than or equal to 150 for any SHAPE parameter, then both FZ
and NFZ would have a rectangular boundaries in all Fracture Plane views;
Default: 2.

12.2.127. FRACTURE_TEMPLATE 757

Keywords for formats tN, E1, E3 19.1

25. SHAPEXY3 <real>

Curvature parameter αxy3 defining the SRV boundary shape in region III of Fracture
Plane top view (see figure 54). The curvature value must be ≥ 1. Value 1 denotes a
straight line (rhomboid boundary). Value 2 denotes an arc (ellipsoid boundary). If the
specified value greater than or equal to 150 for any SHAPE parameter, then both FZ
and NFZ would have a rectangular boundaries in all Fracture Plane views;
Default: 2.

26. SHAPEXY4 <real>

Curvature parameter αxy4 defining the SRV boundary shape in region IV of Fracture
Plane top view (see figure 54). The curvature value must be ≥ 1. Value 1 denotes a
straight line (rhomboid boundary). Value 2 denotes an arc (ellipsoid boundary). If the
specified value greater than or equal to 150 for any SHAPE parameter, then both FZ
and NFZ would have a rectangular boundaries in all Fracture Plane views;
Default: 2.

27. SHAPEXZ1 <real>

Curvature parameter αxz1 defining the SRV boundary shape in region I of Fracture
Plane front view (see figure 54). The curvature value must be ≥ 1. Value 1 denotes a
straight line (rhomboid boundary). Value 2 denotes an arc (ellipsoid boundary). If the
specified value greater than or equal to 150 for any SHAPE parameter, then both FZ
and NFZ would have a rectangular boundaries in all Fracture Plane views;
Default: 2.

28. SHAPEXZ2 <real>

Curvature parameter αxz2 defining the SRV boundary shape in region II of Fracture
Plane front view (see figure 54). The curvature value must be ≥ 1. Value 1 denotes a
straight line (rhomboid boundary). Value 2 denotes an arc (ellipsoid boundary). If the
specified value greater than or equal to 150 for any SHAPE parameter, then both FZ
and NFZ would have a rectangular boundaries in all Fracture Plane views;
Default: 2.

29. SHAPEXZ3 <real>

Curvature parameter αxz3 defining the SRV boundary shape in region III of Fracture
Plane front view (see figure 54). The curvature value must be ≥ 1. Value 1 denotes a
straight line (rhomboid boundary). Value 2 denotes an arc (ellipsoid boundary). If the
specified value greater than or equal to 150 for any SHAPE parameter, then both FZ
and NFZ would have a rectangular boundaries in all Fracture Plane views;
Default: 2.

30. SHAPEXZ4 <real>

Curvature parameter αxz4 defining the SRV boundary shape in region IV of Fracture
Plane front view (see figure 54). The curvature value must be ≥ 1. Value 1 denotes a
straight line (rhomboid boundary). Value 2 denotes an arc (ellipsoid boundary). If the

12.2.127. FRACTURE_TEMPLATE 758

Keywords for formats tN, E1, E3 19.1

specified value greater than or equal to 150 for any SHAPE parameter, then both FZ
and NFZ would have a rectangular boundaries in all Fracture Plane views;
Default: 2.

31. SHAPEYZ1 <real>

Curvature parameter αyz1 defining the SRV boundary shape in region I of Fracture
Plane side view (see figure 54). The curvature value must be ≥ 1. Value 1 denotes a
straight line (rhomboid boundary). Value 2 denotes an arc (ellipsoid boundary). If the
specified value greater than or equal to 150 for any SHAPE parameter, then both FZ
and NFZ would have a rectangular boundaries in all Fracture Plane views;
Default: 2.

32. SHAPEYZ2 <real>

Curvature parameter αyz2 defining the SRV boundary shape in region II of Fracture
Plane side view (see figure 54). The curvature value must be ≥ 1. Value 1 denotes a
straight line (rhomboid boundary). Value 2 denotes an arc (ellipsoid boundary). If the
specified value greater than or equal to 150 for any SHAPE parameter, then both FZ
and NFZ would have a rectangular boundaries in all Fracture Plane views;
Default: 2.

33. SHAPEYZ3 <real>

Curvature parameter αyz3 defining the SRV boundary shape in region III of Fracture
Plane side view (see figure 54). The curvature value must be ≥ 1. Value 1 denotes a
straight line (rhomboid boundary). Value 2 denotes an arc (ellipsoid boundary). If the
specified value greater than or equal to 150 for any SHAPE parameter, then both FZ
and NFZ would have a rectangular boundaries in all Fracture Plane views;
Default: 2.

34. SHAPEYZ4 <real>

Curvature parameter αyz4 defining the SRV boundary shape in region IV of Fracture
Plane side view (see figure 54). The curvature value must be ≥ 1. Value 1 denotes a
straight line (rhomboid boundary). Value 2 denotes an arc (ellipsoid boundary). If the
specified value greater than or equal to 150 for any SHAPE parameter, then both FZ
and NFZ would have a rectangular boundaries in all Fracture Plane views;
Default: 2.

35. STIMULATED_DELTA <real>

An increment of size of the fracture stimulated zone (NFZ) (METRIC: m; FIELD: f t )
along other axes (i.e., along which the right and left NFZ widths W1 and W2 are not
specified). In figure 53 the increment ∆ is specified along X and Z axes. Thus, the
length of the fracture stimulated zone (denoted by NONFRACTURE_ZONE) along X
axis is equal to LEN2 + LEN1 = L1 + L2 + 2∆, while along Z axis is UP+DOWN+ 2∆;
Default: 0.

12.2.127. FRACTURE_TEMPLATE 759

Keywords for formats tN, E1, E3 19.1

36. HLEN_MULT_MINUS <real>

A multiplier allowing to modify the fracture size or the fracture stimulated zone size
to the right from an anchor point. The length of the fracture stimulated zone is equal
to LEN1 = (∆ + L1 ) · HLEN_MULT _MINUS . If the increment ∆=0 then each seg-
ment of polyline to the right from an anchor point is stretched (or compressed) due to
multiplication on HLEN_MULT _MINUS . The anchor point is fixed;
Default: 1.

37. HLEN_MULT_PLUS <real>

A multiplier allowing to modify the fracture size or the fracture stimulated zone to the
left from an anchor point. The length of the fracture stimulated zone is equal to LEN2 =
(∆ + L2 ) · HLEN_MULT _PLUS . If the increment ∆=0 then each segment of polyline
to the left from an anchor point is stretched (or compressed) due to multiplication on
HLEN_MULT _PLUS . The anchor point is fixed;
Default: 1.

38. ROTATE_Z <real>

An angle of rotation around anchor point in the fracture plane (in degree);
Default: 0.

39. ROTATE_XY <real>

A rotation angle of the fracture plane around vertical axis (in degree).
Default: 0.

Data should be terminated with a slash / on a new line.

Example
FRACTURE_TEMPLATE
TEMPLATE_ONE 5 5 5 /
PLANE PLANE_ONE /
UP 150 /
DOWN 150 /
STIMULATED_WIDTH_R 130 /
STIMULATED_WIDTH_L 130 /
EFFECTIVE_WIDTH 10 /
/
In this example a fracture template TEMPLATE_ONE is specified. The local grid refine-
ment (LGR) of 5×5×5 is selected, i.e. each block of coarse grid will be subdivided into 5
blocks in each coordinate direction. This template will be implemented to a set of polylines
PLANE_ONE (keyword FRACTURE_PLANE, see 12.2.126). The fracture height upward from
the anchor point is 150 (option UP) and downward from the anchor point is 150. The frac-
ture width is 10 (option EFFECTIVE_WIDTH). The right (from the anchor point) width of
the fracture stimulated zone is 130 (option STIMULATED_WIDTH_R) and left width is 130

12.2.127. FRACTURE_TEMPLATE 760

Keywords for formats tN, E1, E3 19.1

(option STIMULATED_WIDTH_R). The fracture has a cylindrical form, while the fracture
stimulated zone is an ellipsoid.

12.2.127. FRACTURE_TEMPLATE 761

Keywords for formats tN, E1, E3 19.1

12.2.128. FRACTURE_WELL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword links a set of fractures to a well trajectory. More detailed information about
how to create a fracture model using the local grid refinement (LGR) is given in the section
5.8. The keyword can be used only if the keyword WELLTRACK (see 12.19.9) is given in the
section GRID.
On a new line after the keyword the following parameters should be specified:
• name of set of fractures;
• well name;
• branch number.
If a branch number is not specified it is supposed that the main well bore (number 0) is
given;
Further fracture templates should be listed. Each template should be written on a new line.
A fracture can be linked to the point of well trajectory at the selected depth md . Thus, on
one line the following parameters are specified:
• template name;
• md – depth of well trajectory point linked to the fracture (METRIC: m, FIELD: f t ).

Fractures can be distributed uniformly along a well bore (or a branch) interval. Then, on
one line the following parameters are specified:
• template name;
• mdu – upper depth (METRIC: m, FIELD: f t ). mdu 6= mdl ;
• mdl – lower depth (METRIC: m, FIELD: f t ). mdl 6= mdu;
• number of fractures n. n ≥ 2.
Data should be terminated with a slash / on a new line.
Notice 1: n fracture anchor points are uniformly distributed along the selected interval of
well trajectory [mdu; mdl ], thus, fractures are always located at trajectory points mdu and
mdl . mdu and mdl can be specified in any order.
Notice 2: In case of anchor point is in an inactive block then the block becomes active (i.e.
all blocks crossed by a fracture become active). Grid properties in theses blocks are specified
using the keyword FRACTURE_TEMPLATE (see 12.2.127).

12.2.128. FRACTURE_WELL 762

Keywords for formats tN, E1, E3 19.1

Notice 3: An anchor point can be located outside of a grid. In this case only a fracture
part located within the grid will be visualized.
Example
WELLTRACK 'WELL'
550 1050 300 0
3550 1050 300 3000
/
...
FRACTURE_WELL
'STAGE_ONE' 'well' 0 /
'TEMPLATE_ONE' 500 /
/

In this example a fracture with template 'TEMPLATE_ONE' is linked to the well

'WELL' at the point with depth equal to 500 (in measured depth MD).

12.2.128. FRACTURE_WELL 763

Keywords for formats tN, E1, E3 19.1

12.2.129. FRACTURE_ARITHMETIC

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies the properties of fracture zone (FZ) and non-fracture zone (NFZ)
via arithmetic expressions.
The detailed information about Hydraulic Fractures modeling via Local Grid Refinement
(LGR) is provided in the section 5.8.

The data should be entered in the following format:

FRACTURE_ARITHMETIC
'arithmetic_name'
prop (zone: FZ|NFZ, active: ACT|INACT, dp: M|F) = values /
... ... ...
prop (zone: FZ|NFZ, active: ACT|INACT, dp: M|F) = values /
/
On the lines below the keyword the following parameters should be specified:
• Arithmetic name.
The name is indicated on a new line after the keyword and it can be further be used in
FRACTURE_STAGE (see 12.19.147) keyword.
• An arbitrary number of arithmetic expressions defining the grid properties in a certain
area. Expressions can be written in any order or skipped. Each expression should be
typed on a new line and terminated with a slash /.
Data input should be terminated with a slash / on a new line.

Each arithmetic expression consist of the following parameters:

1. Property name.
The following grid properties are available:
• PORO (see 12.2.24), NTG (see 12.2.25), MULTPV (see 12.2.28),
• PERMX (see 12.2.13), PERMY (see 12.2.13), PERMZ (see 12.2.13),
• SIGMAV (see 12.2.73),
• SWAT (see 12.16.14), SOIL (see 12.16.16), SGAS (see 12.16.15) (available only
in black-oil models).
If after an implementation of the arithmetic the sum of saturations (SWAT + SOIL
+ SGAS) is not equal to 1 then the following correction of saturations is carried
out so that their sum is equal to 1:

12.2.129. FRACTURE_ARITHMETIC 764

Keywords for formats tN, E1, E3 19.1

– If the sum of saturations specified by arithmetic exceeds 1 then their values are
normalized (so that their sum is equal to 1), while the remaining saturations
are assumed to be equal to zero;
– If all saturations are specified by arithmetic and their sum is less than 1 then
all saturations are normalized;
– If the sum of all saturations (specified by arithmetic and remaining ones) is
less than 1 then the specified saturations do not change and the remaining
saturations are normalized.
– If all saturations are equal to zero then the water saturation SWAT is assumed
to be equal to 1.

The following regions are available:

• ROCKNUM (see 12.4.14) – number of rock region;

• SATNUM (see 12.4.3) – saturation regions.
• PVTNUM (see 12.4.2) – PVT regions.

2. Blocks array.
The zone containing blocks in which the selected property will be modified is specified
in brackets: (zone: FZ | NFZ, active: ACT | INACT | ALL, dp: M | F)

• FZ – fracture zone;
• NFZ – non-fracture zone (fracture stimulated zone);
• ACT – refined active blocks;
• INACT – refined inactive blocks, activated by hydraulic fracture;
• ALL – both active and inactive refined blocks ;
• M – matrix;
• F – fracture (valid only for dual porosity or dual permeability models).

Figure 55. Blocks zones around Hydraulic Fracture.

12.2.129. FRACTURE_ARITHMETIC 765

Keywords for formats tN, E1, E3 19.1

3. Values specification.

The value can be set constant in the defined area:

• <real>
The specified value is assigned to all selected blocks;
Or varying in the selected blocks array via one of the following functions:
• LINEAR_VERTICAL (n1 , n2 )
Linear distribution (interpolation) of the selected property between its value n1
given at an anchor point and value n2 at the boundary of the selected zone (fracture
zone FZ or the fracture stimulated zone NFZ) along a polyline to the right and to
the left from the anchor point. In this case the obtained property in the vertical
direction will be constant;
• LINEAR_RADIAL (n1 , n2 )
Linear distribution (interpolation) of the selected property from an anchor point,
where the property value n1 is defined, to the boundary of the selected zone
(fracture zone or the fracture stimulated zone), where the property value is n2 ;
• EXP_VERTICAL (n1 , n2 )
Exponential distribution (interpolation) of the selected property between its value
n1 given at an anchor point and value n2 at the boundary of the selected zone
(fracture zone FZ or the fracture stimulated zone NFZ) along a polyline to the
right and to the left from the anchor point. In this case the obtained property in the
vertical direction is constant;
• EXP_RADIAL (n1 , n2 )
Exponential distribution (interpolation) of the selected property from an anchor
point, where the property value n1 is defined, to the boundary of the selected zone
(fracture zone or the fracture stimulated zone), where the property value is n2 .

Example 1
FRACTURE_ARITHMETIC
'arithmetic_1'/
PERMX (zone : FZ) = LINEAR_VERTICAL (1000, 500) /
PERMX (zone : NFZ) = EXP_RADIAL (300, 200) /
/
In this example Fracture Arithmetic with the name arithmetic_1 is specified. In the frac-
ture zone permeability PERMX is linear distributed between values 1000 and 500 along a
polyline to the right and to the left from the anchor point: n1 =1000 is a permeability value
at anchor point, n2 =500 is a permeability value at boundary of the fracture zone to the right
and to the left from the anchor point. In the fracture stimulated zone permeability PERMX is
exponentially distributed between values 300 and 200 in radial direction from the anchor point.

12.2.129. FRACTURE_ARITHMETIC 766

Keywords for formats tN, E1, E3 19.1

Additional features.

In FRACTURE_ARITHMETIC keyword it is possible to use arithmetic operators instead of

0 = 0:

Keyword entry format with arithmetic operators

FRACTURE_ARITHMETIC
'arithmetic_name'
prop (zone: FZ|NFZ, active: ACT|INACT, dp: M|F) += values /
prop (zone: FZ|NFZ, active: ACT|INACT, dp: M|F) -= values /
prop (zone: FZ|NFZ, active: ACT|INACT, dp: M|F) *= values /
prop (zone: FZ|NFZ, active: ACT|INACT, dp: M|F) /= values /
/

0+ = 0 – The specified value will be added to the current grid property.

0− = 0 – The specified value will be substracted from the current grid property.
0∗ = 0 – The current grid property be multiplied by the specified value.
0/ = 0 – The current grid property be divided by the specified value.

i These operators can be used with any values specification type (constant
value or interpolation within the zone).

! The grid property value in the refined block cannot be lower than its value in
the corresponding parent block.

Example 2
PERMX
300*5 /
... ... ...
FRACTURE_ARITHMETIC
'arithmetic_2'/
PERMX (zone : FZ) *= 10 /
PERMX (zone : NFZ) += LINEAR_RADIAL (30, 10) /
/
In this example the PERMX in coarse blocks is set equal to 5 mD. PERMX in the Fracture
Zone (FZ) is set constant and equal to 5 ∗ 10 = 50 mD. In the fracture stimulated zone (NFZ)
PERMX is linearly interpolated between 35 mD and 15 mD.

12.2.129. FRACTURE_ARITHMETIC 767

Keywords for formats tN, E1, E3 19.1

More Examples.

Example 3
FRACTURE_ARITHMETIC
'arithmetic_3'/
SATNUM (zone : FZ) = 2 /
SATNUM (zone : NFZ) = 2 /
/
In this example Fracture Arithmetic with the name arithmetic_3 is specified. In the frac-
ture zone (FZ) and in the fracture stimulated zone the number of saturation function region is
set equal to 2.

Example 4
FRACTURE_ARITHMETIC
'arithmetic_4'/
SATNUM (zone : FZ, active: INACT) = 2 /
SATNUM (zone : NFZ, active: INACT) = 3 /
ROCKNUM (zone : FZ active: INACT) = 2 /
ROCKNUM (zone : NFZ active: INACT) = 3 /
/
In this example the fracture Arithmetic with the name arithmetic_4 is specified. It defines
the numbers of Saturation Tables (SATNUM) and Rock Compaction tables ROCKNUM) for
the blocks which had initially null pore volume and then were activated via grid refinement.
The data is defined separately in Fracture Zone (FZ) and Non-Fracture Zone (NFZ).

12.2.129. FRACTURE_ARITHMETIC 768

Keywords for formats tN, E1, E3 19.1

12.3. Arithmetic section

This section describes all keywords necessary for performing arithmetic operations.

A lot of keywords are available, for example:

• ARITHMETIC (see 12.3.2) – facilitating work with large data arrays and their modifica-
tion;

• 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.13) – interpolation;

• BLOCK (see 12.3.9) – can be used to prepare source data for interpolation;

• STORE (see 12.3.11) – saving of array into specified file during model reading;

• SYSTEM (see 12.3.12) – allows to run an external script or program (for example, in
Python, Perl, bash, or C++) during model reading.

12.3. Arithmetic section 769

Keywords for formats tN, E1, E3 19.1

12.3.1. EDIT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID x EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies the beginning of data section which contains instructions for modi-
fying 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 770

Keywords for formats tN, E1, E3 19.1

12.3.2. ARITHMETIC

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION SUMMARY x SCHEDULE

The keyword specifies arithmetic operations on arrays. It is followed by operation descrip-

tion. The data should be terminated with a slash /.

Arithmetic operations are performed on arrays element by element. For example, PERMX
= MIN(PERMX,100) means PERMXi, j,k = MIN(PERMXi, j,k , 100) for all i, j, k . Here equality is
an assignment statement. Note that the same array may be used several times in the expression
and appear 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 ARITHMETIC 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, see INTERPOLATE (see 12.3.13).

The following binary operations are supported (with two arguments):

• + – elementwise summation;

• - – elementwise subtraction;

• * – elementwise multiplication;

• / – elementwise division;

• ˆ — elementwise exponentiation (raising to a power);

• == — elementwise comparison (returns an array of boolean values);

• MAX(·,·) – elementwise maximum calculation;

• MIN(·,·) – elementwise minimum calculation;

The following unary operations are supported (with one argument):

• - – elementwise negation

• LOG – elementwise natural logarithm calculation

• LOG10 – elementwise decimal logarithm calculation

12.3.2. ARITHMETIC 771

Keywords for formats tN, E1, E3 19.1

• EXP – elementwise exponent calculation

• SIN – elementwise sine calculation

• COS – elementwise cosine calculation

• TAN – elementwise tangent calculation

• SQRT – elementwise square root calculation

• ABS – elementwise absolute value calculation

• ROUND – elementwise rounding to nearest integer

• MAX — maximum of the array (returns a scalar)

• MIN — minimum of the array (returns a scalar)

• SUM — sum of the array (returns a scalar)

• AVG — average value of the array (returns a scalar)

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).

Numeric zero in boolean context casts to False, and non-zero values cast to
i True. Conversely, when a boolean value produced by comparison is used in
the context of numeric calculations, it casts to 0 if False and to 1 if True (see
Example 3).

Example 1. Use of IF
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 val-
ues 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

12.3.2. ARITHMETIC 772

Keywords for formats tN, E1, E3 19.1

– 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 cal-
culation)
– MULTXM – corresponds to the map MULTX- (see 12.2.16)
– MULTY (see 12.2.17) – transmissibility multipliers in Y-direction (also during cal-
culation)
– MULTYM – corresponds to the map MULTY- (see 12.2.18)
– MULTZ (see 12.2.19) – transmissibility multipliers in Z-direction (also during cal-
culation)
– MULTZM – corresponds to the map MULTZ- (see 12.2.20)
– TRANX (see 12.2.50) – transmissibility in X-direction
– TRANY (see 12.2.51) – transmissibility in Y-direction
– TRANZ (see 12.2.52) – transmissibility in Z-direction
– TOPS (see 12.2.6) – depths for top planes of cells in first layer
– DEPTH (see 12.3.28) – 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
– ARR (see 12.3.5) – temporary user-defined arrays

• Initial conditions:

– SOIL (see 12.16.16) – initial oil saturation

– SWAT (see 12.16.14) – initial water saturation
– SGAS (see 12.16.15) – initial gas saturation
– PRESSURE (see 12.16.12) – initial pressure
– PBUB (see 12.16.36) – initial bubble point pressure
– RS (see 12.16.37) – initial gas solution in oil
– RV (see 12.16.38) – initial oil vaporization in gas

12.3.2. ARITHMETIC 773

Keywords for formats tN, E1, E3 19.1

– PDEW (see 12.16.39) – initial dew point pressure

• Regions:

– ACTNUM (see 12.2.29) – active/inactive cells

– 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.26) – minimal water saturation

– SWCR (see 12.6.29) – critical water saturation
– SWU (see 12.6.33) – maximal water saturation
– SOWCR (see 12.6.31) – critical oil-to-water saturation
– PCW (see 12.6.62) – water capillary pressure
– SWATINIT (see 12.6.65) – initial water saturation
– SGL (see 12.6.28) – minimal gas saturation
– SGCR (see 12.6.30) – critical gas saturation
– SGU (see 12.6.34) – maximal gas saturation
– SOGCR (see 12.6.32) – critical oil-to-gas saturation
– PCG (see 12.6.63) – gas capillary pressure
– KRW (see 12.6.59) – maximal water relative permeability that is used in RP end-
point scaling
– KRWR (see 12.6.59) – 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.58) – oil relative permeability at the critical water saturation
that is used in RP end-point scaling
– KRG (see 12.6.60) – maximal gas relative permeability that is used in RP end-point
scaling
– KRGR (see 12.6.60) – 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.58) – oil relative permeability at the critical gas saturation that
is used in RP end-point scaling
– KRO (see 12.6.58) – maximal oil relative permeability that is used in RP end-point
scaling that is used in RP end-point scaling

12.3.2. ARITHMETIC 774

Keywords for formats tN, E1, E3 19.1

• Immutable variables (only to be used in the right hand side of arithmetic expressions):

– I (map of integer values) – i-coordinate: block numbers in X direction

– J (map of integer values) – j-coordinate: block numbers in Y direction
– K (map of integer values) – k-coordinate: block numbers in Z direction
– NX (see 12.1.28) – number of blocks in X direction
– NY (see 12.1.28) – number of blocks in Y direction
– NZ (see 12.1.28) – number of blocks in Z direction
– X – coordinates of block centers in X direction
– Y – coordinates of block centers in Y direction
– Z – coordinates of block centers in Z direction
– VOL – geometric volume of the block
– CYLINDER (see 12.3.10) – grid property that equals 1 for the grid blocks located
in the cylindrical region and 0 for other blocks. A grid block is assumed to be
included in the cylinder if its center is in this region
– BLOCK (see 12.3.9) – grid property that equals 1 for the grid blocks located near
the vertical line through (x, y) (or the point (x, y, z)) and 0 for other blocks

Usual operation priorities are used. Operations may be grouped by parentheses forming
more complex expressions like PORO = MIN (MAX (1.2*(PORO-0.1), 0), 1).
For performing operations on a fragment of an array, the following options are available:

• To specify a subset of the array (so-called slice) in the left-hand side of the assignment:
PERMX(1:20,1:20,1:10) = 0.125.
The limiting values for some directions may be skipped. In that case the scope in these
directions is extended to the widest possible range:
PERMX( , ,1:10) = 0.125.
All arrays in the right-hand side of the assignment will be taken in the same scope.

• To specify a box using BOX (see 12.3.3) function.

Example 2
ARITHMETIC
PERMX = 8*EXP(10*PORO)
/

This example sets permeability in X direction equal to a certain function of porosity. This
operation is performed on all grid blocks.

12.3.2. ARITHMETIC 775

Keywords for formats tN, E1, E3 19.1

Example 3. Use of conditions

----------------
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
different ARRSAT regions (conditions ARRSAT == 1, ARRSAT == 2 and so on) PERMX is
calculated via different formulae from PORO. Description of defining ARRSAT array see at
the description of the keyword ARR (see 12.3.5).

The next example illustrates performing arithmetic operation on an array subregion:

Example 4. Use of slices
ARITHMETIC
PERMX(50:100,10:20,2:2) = 8*EXP(10*PORO)
/

Here porosity is 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.

12.3.2. ARITHMETIC 776

Keywords for formats tN, E1, E3 19.1

Example 5. Use of slices (advanced)

---------------------------------
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.
Using arrays of different sizes
When a scalar value is used in array context, it is automatically cast to a constant array of
the same size. However, two arrays of different size cannot be cast like that, and using them
simultaneously causes an error
Arithmetic error: there are incompatible types...
This may happen, for instance, when array slices appear together with full-sized arrays in
the right-hand side of an expression.
Example 6: incorrect syntax
ARRFIP = IF( ARRFIP (1:20,1:20,5:10) == 7, 6, ARRFIP) /

This incorrect expression should be redesigned as follows:

Example 6: correct syntax
ARRFIP (1:20,1:20,5:10) = IF( ARRFIP == 7, 6, ARRFIP) /

In this example the ARRFIP values within a certain region are changed from 7 to 6. Other
values are not affected.

12.3.2. ARITHMETIC 777

Keywords for formats tN, E1, E3 19.1

12.3.3. BOX

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION SUMMARY x SCHEDULE

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).
All grid properties modification commands located between BOX and ENDBOX
(see 12.3.4) will only be applied to the blocks within the specified area.
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 778

Keywords for formats tN, E1, E3 19.1

12.3.4. ENDBOX

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION SUMMARY x SCHEDULE

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 779

Keywords for formats tN, E1, E3 19.1

12.3.5. ARR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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 can’t 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
ARRUSER1
15000*2
/
Method 2 – assign one value for all array elements via EQUALS (see 12.3.23):

Example 2
EQUALS
ARRUSER1 2 /
/
Method 3 – assign one value for all array elements via ARITHMETIC (see 12.3.2):

12.3.5. ARR 780

Keywords for formats tN, E1, E3 19.1

Example 3
ARITHMETIC
ARRUSER1=3
/
Examples of usage:
Example 4
COPY
ARRUSER1 MULTX /
/
In this example we assign to MULTX (see 12.2.15) array the values of user-defined array
ARRUSER1.

Example 5
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
—————-
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 781

Keywords for formats tN, E1, E3 19.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
different ARRSAT regions (conditions ARRSAT == 1, ARRSAT == 2 and so on) PERMX is
calculated via different formulae from PORO.

12.3.5. ARR 782

Keywords for formats tN, E1, E3 19.1

12.3.6. WORK/IWORK

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION SUMMARY SCHEDULE

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.26).

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.32).

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 783

Keywords for formats tN, E1, E3 19.1

12.3.7. IF

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION SUMMARY x SCHEDULE

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 784
Keywords for formats tN, E1, E3 19.1

12.3.8. IF-THEN-ELSE-ENDIF

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION SUMMARY x SCHEDULE

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
data should be terminated with a slash /.
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 block’s number in X-direction.
Example 2.

12.3.8. IF-THEN-ELSE-ENDIF 785

Keywords for formats tN, E1, E3 19.1

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 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
different ARRSAT regions (conditions ARRSAT == 1, ARRSAT == 2 and so on) PERMX is
calculated via different formulae from PORO.

12.3.8. IF-THEN-ELSE-ENDIF 786

Keywords for formats tN, E1, E3 19.1

12.3.9. BLOCK

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION SUMMARY SCHEDULE

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.13).
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), with values 1 near
the vertical line (x,y), and zero elsewhere.

• BLOCK (x,y,z)
The function gives as a result a 3D cube (dimensions NX, NY, NZ), with values 1 near
the point (x,y,z), and zero elsewhere. 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 (41500, -89000) == 1, 0.7, ARRPOROSRC)
ARRPOROSRC=IF (block (31500, -29000) == 1, 0.2, 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).

3. We assign the value 0.7 to all blocks through which the vertical line (41500, -89000)
goes (other values remain unchanged, see function IF, see 12.3.7).

12.3.9. BLOCK 787

Keywords for formats tN, E1, E3 19.1

4. We assign the value 0.2 to all blocks through which the vertical line (31500, -29000)
goes (other values remain unchanged, see function IF, see 12.3.7).

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 that the resulting porosity values are in the interval (0, 1). The values that
exceed 1 are changed to 1 (via a function min), and those which are less than 0 are
changed to 0 (via a function max).

12.3.9. BLOCK 788

Keywords for formats tN, E1, E3 19.1

12.3.10. CYLINDER

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION SUMMARY SCHEDULE

This keyword can be used only in the keyword ARITHMETIC (see 12.3.2).

CYLINDER(x,y,r) is the function given the property (with dimension equal to model’s
dimension NX × NY × NZ), for which grid blocks located in the created cylindrical region
are set a value 1, while other blocks are set value 0. Grid block is assumed to be in the created
region if its center is in this region. The following parameters should be specified:

• x, y are coordinates of cylinder’s center (METRIC: m, FIELD: f t );

• r is cylinder’s radius (METRIC: m, FIELD: f t ).

This function can be used in the section GRID only after the model’s grid is specified.
Obtained property will be available via graphical interface (GUI) on the tab Grid Proper-
ties, sub-tab Initial. Moreover, the function CYLINDER(x,y,r) can be directly used in GUI for
property editing (see section 16.5.3 of tNavigator User Guide).
Example
GRID

INCLUDE
'grid.inc'/
ARITHMETIC
ARR_NEW = CYLINDER(2239, 1288, 200)
/

In this example in the section GRID after specifying GRID the cylindrical region is created.
The cylinder center is in the point with coordinates (2239, 1288) and cylinder radius r is equal
to 200. Grid blocks located in this region are set a value 1, other block are set 0.

12.3.10. CYLINDER 789

Keywords for formats tN, E1, E3 19.1

12.3.11. STORE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION SUMMARY SCHEDULE

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
/. The data should be terminated with a slash /.
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.11. STORE 790

Keywords for formats tN, E1, E3 19.1

12.3.12. SYSTEM

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword allows to run an external script or program (for example, in Python, Perl,
bash, or C++) 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 user’s variables can be used. To define user’s variable the keyword DE-
FINES (see 12.1.24) is used. The data should be terminated with a slash /.
Note 1. 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.

Note 2. Using SYSTEM keyword leads to a dependence on the operating system for
model loading. For example, the possible scenario: opening a model in Windows to create
AHM project, and then calculate model variants on the cluster with Linux. In this case, you
must ensure that the script started via SYSTEM works correctly under both operating systems
Windows, Linux.

Example
SYSTEM
'python 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. File python.exe must be executable and be in the folder that is listed in
the variable %PATH%. 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.12. SYSTEM 791

Keywords for formats tN, E1, E3 19.1

12.3.13. INTERPOLATE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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, ...)

The first 3 parameters are common to all algorithms. Beyond that, each algorithm might
have other specific parameters <...> on its own.

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, ...)

Discrete interpolation can be used to build cubes with integer values (for example, cubes
of PVT regions). For the description of work of discrete interpolation see Description of dis-
crete interpolation.

Algorithms and parameters (algorithm name is specified instead of <ALGORITHM>).

INTERPOLATE_ML_TRIVIAL – Trivial
Fills all the blocks where the value is not specified with the constant.

The data is specified the following way:

INTERPOLATE_ML_TRIVIAL (SOURCE, NOVALUE, EMPTY_LAYER_VALUE, ...)

The following parameters should be specified:

12.3.13. INTERPOLATE 792

Keywords for formats tN, E1, E3 19.1

1. 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);
2. NOVALUE — the value of special constant;
3. EMPTY_LAYER_VALUE — the value assigned to the layer (at the end of interpolation
process), if the layer contains no interpolation nodes;
4. VALUE_TO_FILL — the constant value to fill the blocks.

INTERPOLATE_ML_IDW – Inverse Distance Weighting

The data is specified the following way:
INTERPOLATE_ML_IDW (SOURCE, NOVALUE, EMPTY_LAYER_VALUE, ...)

The following parameters should be specified:

1. 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);
2. NOVALUE — the value of special constant;
3. EMPTY_LAYER_VALUE — the value assigned to the layer (at the end of interpolation
process), if the layer contains no interpolation nodes;
4. POWER_PARAMETER — power factor p.

INTERPOLATE_ML_SGS – Sequential Gaussian Simulation

The data is specified the following way:
INTERPOLATE_ML_SGS (SOURCE, NOVALUE, EMPTY_LAYER_VALUE, ...)

The following parameters should be specified:

1. 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);

12.3.13. INTERPOLATE 793

Keywords for formats tN, E1, E3 19.1

2. NOVALUE — the value of special constant;

3. EMPTY_LAYER_VALUE — the value assigned to the layer (at the end of interpolation
process), if the layer contains no interpolation nodes;

4. VARIOGRAM_TYPE. One should enter a 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).

5. 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.

6. 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).

7. VARIOGRAM_NUGGET_EFFECT – non-negative real number; usually 0.

8. 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.

9. 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.

12.3.13. INTERPOLATE 794

Keywords for formats tN, E1, E3 19.1

10. 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.
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.

11. 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 (in-
terpolation nodes) are sparse, and this parameter is small enough, that it can occur that
in some blocks the result value can’t be calculated.

12. KRIGING_POINTS – the number of kriging points. 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).

13. 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 result-
ing 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
The data is specified the following way:
INTERPOLATE_ML_KRIGING (SOURCE, NOVALUE, EMPTY_LAYER_VALUE, ...)

The following parameters should be specified:

1. 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);

2. NOVALUE — the value of special constant;

3. EMPTY_LAYER_VALUE — the value assigned to the layer (at the end of interpolation
process), if the layer contains no interpolation nodes;

4. VARIOGRAM_TYPE. One should enter a value that specifies one of these types:

• 0 – EXPONENTIAL;

12.3.13. INTERPOLATE 795

Keywords for formats tN, E1, E3 19.1

• 1 – SPHERICAL;
• 2 – GAUSS;
• 3 – CUBIC;
• 4 – NUGGET_EFFECT;
• 5 – POWER;
• 6 – CAUCHY;
• 7 – Rationally Quadratic (DE_VIJS).

5. 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.

6. 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).

7. VARIOGRAM_NUGGET_EFFECT – discontinuous jump at zero point. Non-negative

real number; usually 0.

8. 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.

9. 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.

10. 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.
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.

12.3.13. INTERPOLATE 796

Keywords for formats tN, E1, E3 19.1

11. KRIGING_TYPE. One should enter a 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 in 12.3.13.

12.3.13. INTERPOLATE 797

Keywords for formats tN, E1, E3 19.1

Example 1 of porosity interpolation (construction of PORO cube via IDW algorithm).

Example
GRID
INCLUDE
'ARRPOROSRC.map'/

ARITHMETIC
ARRMYPORO = interpolate_ml_idw (ARRPOROSRC, -999.25, 0.5, 2)
PORO = ARRMYPORO
PORO = min (1, max (0, PORO))
/
Example description:

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.

4. We check if the result values of porosity don’t exceed 1. If it happens then we assign a
value 1 to this block (via a function min).

Example of file ARRPOROSRC.map (there is a keyword ARRPOROSRC at the beginning

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 Krig-

ing algorithm).

12.3.13. INTERPOLATE 798

Keywords for formats tN, E1, E3 19.1

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))
/

Example description:

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 arrays
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.

12.3.13. INTERPOLATE 799

Keywords for formats tN, E1, E3 19.1

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.

6. We check if the result values of porosity don’t exceed 1. If it happens then we assign a
value 1 to this block (via a function min).

Example 4 of using interpolation (building PVT-cube by Kriging with discrete inter-

polation ).

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. INTERPOLATE 800

Keywords for formats tN, E1, E3 19.1

12.3.14. MULTIPLY

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION SUMMARY SCHEDULE

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 data line should be terminated with the symbol /. All 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.14. MULTIPLY 801

Keywords for formats tN, E1, E3 19.1

12.3.15. MULTIREG

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION SUMMARY SCHEDULE

This keyword is used to multiply grid properties by a constant in a specific region. The re-
gions must previously have been defined using keyword MULTNUM (see 12.4.22), OPERNUM
(see 12.4.21) or FLUXNUM (see 12.4.18).
An arbitrary number of lines could be specified. Each data line should be terminated with
the symbol /. All 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.22), OPERNUM (see 12.4.21) or FLUXNUM,
see 12.4.18) (region is specified via parameter 4);

4. region M (MULTNUM, see 12.4.22), O (OPERNUM, see 12.4.21), F (FLUXNUM,

see 12.4.18);
Default: 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.15. MULTIREG 802

Keywords for formats tN, E1, E3 19.1

12.3.16. MULTREGP

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies pore volume multiplier for a specific region. The regions
must previously have been defined using keyword MULTNUM (see 12.4.22) 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 data line should be terminated
with the symbol /. All data should be terminated with a final slash /.
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 E1/E3 format this keyword has different workflow logic. The first
parameter of the keyword TNAVCTRL (see 12.1.4) is used to switch it. Let’s define 3 values
to describe workflow logic in different E1/E3 versions:

• gridopts_reg – 2-nd parameter of the keyword GRIDOPTS (see 12.1.95) (it response for
the number of MULTNUM (see 12.4.22) regions);
• regdims4_reg – 4-th parameter of the keyword REGDIMS (see 12.1.32) (it response for
the number of FLUXNUM (see 12.4.18) regions);
• regdims7_reg – 7-th parameter of the keyword REGDIMS (see 12.1.32) (it response for
the number of OPERNUM (see 12.4.21) regions);

New workflow logic. E1 models.

Parameter array of region can be the following:

• M – MULTNUM (see 12.4.22) is using. If MULTNUM (see 12.4.22) is not defined, then
multiplier doesn’t 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.95).
• F – FLUXNUM (see 12.4.18) is using. If FLUXNUM (see 12.4.18) is not defined or
regdims4_reg is 0, then multiplier doesn’t 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.22) is defined in the model. That is, one can use
the greater number of regions than it is specified in REGDIMS (see 12.1.32).

12.3.16. MULTREGP 803

Keywords for formats tN, E1, E3 19.1

• O – OPERNUM (see 12.4.21) is using. If OPERNUM (see 12.4.21) is not defined or

regdims7_reg is 0, then multiplier doesn’t 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.22) is defined in the model. That is, one can use
the greater number of regions than it is specified in REGDIMS (see 12.1.32);

• Default:

– if gridopts_reg is not 0 and MULTNUM (see 12.4.22) 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 E3 models. Let’s define another parameter: tabdims11 – 11-th parameter of the
keyword TABDIMS (see 12.1.29).
Then the value of the 3-rd parameter defines the following:

• M: MULTNUM (see 12.4.22) is using. If MULTNUM (see 12.4.22) is not defined, then
multiplier doesn’t 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 doesn’t applied. Otherwise, region number should be less or equal to max
(tabdims11, gridopts_reg, regdims4_reg, regdims7_reg).

• O: OPERNUM (see 12.4.21) is using. If OPERNUM (see 12.4.21) is not defined, then
multiplier doesn’t applied. Otherwise, region number should be less or equal to max
(tabdims11, gridopts_reg, regdims4_reg, regdims7_reg);

• Default: M.

Old logic

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
/
Evaluation of final region has several stages:

12.3.16. MULTREGP 804

Keywords for formats tN, E1, E3 19.1

1. let’s 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.21) is set, then OPERNUM

(see 12.4.21) is using.
• if gridopts_reg > 0 and MULTNUM (see 12.4.22) is set, then MULTNUM
(see 12.4.22) 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.16).

• if M default value, then pre-final region is MULTNUM (see 12.4.22);

• if F, then pre-final region is FLUXNUM (see 12.4.18);
• if O, then pre-final region is OPERNUM (see 12.4.21).

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.16. MULTREGP 805

Keywords for formats tN, E1, E3 19.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
/
...
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.16. MULTREGP 806

Keywords for formats tN, E1, E3 19.1

12.3.17. COPY

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION SUMMARY SCHEDULE

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.17. COPY 807

Keywords for formats tN, E1, E3 19.1

12.3.18. COPYBOX

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT x PROPS
Section
x REGIONS x SOLUTION SUMMARY SCHEDULE

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.18. COPYBOX 808

Keywords for formats tN, E1, E3 19.1

12.3.19. COPYREG

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword is used to copy data from one property array to another in a specific region.
The regions must previously have been defined using keyword MULTNUM (see 12.4.22),
OPERNUM (see 12.4.21) or FLUXNUM (see 12.4.18). The data should be terminated with a
slash /.

The following parameters should be specified:

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.22), OPERNUM (see 12.4.21), FLUXNUM, see 12.4.18);

4. region (M – MULTNUM (see 12.4.22), O – OPERNUM (see 12.4.21), F – FLUXNUM,

see 12.4.18);
Default: M –MULTNUM (see 12.4.22).

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.19. COPYREG 809

Keywords for formats tN, E1, E3 19.1

12.3.20. EQUALREG

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION SUMMARY SCHEDULE

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.22), OPER-
NUM (see 12.4.21) or FLUXNUM (see 12.4.18). The data should be terminated with a slash /.

The following parameters should be specified:

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.22), OPERNUM (see 12.4.21), FLUXNUM, see 12.4.18);

4. region (M – MULTNUM (see 12.4.22), O – OPERNUM (see 12.4.21), F – FLUXNUM,

see 12.4.18);
Default: M –MULTNUM (see 12.4.22).

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.20. EQUALREG 810

Keywords for formats tN, E1, E3 19.1

12.3.21. ADD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION SUMMARY SCHEDULE

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.
There may be any number of records, each of which is terminated by a slash /.
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.21. ADD 811

Keywords for formats tN, E1, E3 19.1

12.3.22. ADDREG

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION SUMMARY SCHEDULE

This keyword is used to add a constant to grid property array in a specific region. The re-
gions must previously have been defined using keyword MULTNUM (see 12.4.22), OPERNUM
(see 12.4.21) or FLUXNUM (see 12.4.18). The keyword should be followed by grid parameter
to be modified, a constant and a region number.
There may be any number of records, each of which is terminated by a slash /.
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.22. ADDREG 812

Keywords for formats tN, E1, E3 19.1

12.3.23. EQUALS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION SUMMARY SCHEDULE

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 should
be terminated with a final slash /.
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.23. EQUALS 813

Keywords for formats tN, E1, E3 19.1

12.3.24. MAXVALUE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.
There may be any number of records, each of which is terminated by a slash /.
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.24. MAXVALUE 814

Keywords for formats tN, E1, E3 19.1

12.3.25. MINVALUE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.
There may be any number of records, each of which is terminated by a slash /.
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.25. MINVALUE 815

Keywords for formats tN, E1, E3 19.1

12.3.26. OPERATE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION SUMMARY SCHEDULE

This keyword is used to specify arithmetic operations on grid property arrays in current
box. Input parameters:

1. grid property array to be modified,

2. (6 numbers) input box to be modified, it is specified similarly to BOX (see 12.3.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 - -
1
Ri = Xi INV X - -
Ri = aXi MULTX X a -
Ri = a + Xi ADDX X a -
Ri = Xi COPY X - -
Ri = max(a, Xi ) MINLIM X a -
Ri = min(a, Xi ) MAXLIM X a -
Ri = aXib MULTP X a b
Ri = abs(Xi ) ABS X - -
Ri = Xi · Ri MULTIPLY X - -

4. grid property used as an argument,

5. first scalar parameter, if required,

6. second scalar parameter, if required.

Also arbitrary user arrays can be used in this keyword:

12.3.26. OPERATE 816

Keywords for formats tN, E1, E3 19.1

• WORK (WORK, see 12.3.6) – array of real numbers,

• IWORK (IWORK, see 12.3.6) – array of integer numbers.

Any number of lines of data can be specified (each line corresponds to one modified
grid property). Each data line should be terminated with the symbol /. All data should be
terminated with a final slash /.
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.26. OPERATE 817

Keywords for formats tN, E1, E3 19.1

12.3.27. OPERATER

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION SUMMARY SCHEDULE

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.21).
Input parameters:

1. grid property array to be modified,

2. number of region to be modified,

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 - -
1
Ri = Xi 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 - -

4. grid property array used as an argument,

5. first scalar parameter, if required,

6. second scalar parameter, if required.

12.3.27. OPERATER 818

Keywords for formats tN, E1, E3 19.1

Any number of lines of data can be specified (each line corresponds to one modified
grid property). Each data line should be terminated with the symbol /. All data should be
terminated with a final slash /.
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.27. OPERATER 819

Keywords for formats tN, E1, E3 19.1

12.3.28. DEPTH

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID x EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.
The data should be terminated with a slash /.
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.28. DEPTH 820

Keywords for formats tN, E1, E3 19.1

12.4. Region section

This section allows to define regions with different properties. It is also possible to define
fluid-in-place regions (FIPNUM (see 12.4.10), FIP, see 12.4.11), regions with different initial
conditions and other.

12.4. Region section 821

Keywords for formats tN, E1, E3 19.1

12.4.1. REGIONS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
x REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies the beginning of data section which contains regions data.

12.4.1. REGIONS 822

Keywords for formats tN, E1, E3 19.1

12.4.2. PVTNUM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
x REGIONS SOLUTION SUMMARY x SCHEDULE

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.29).
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.17), DENSITY (see 12.5.33), SALTTRM (see 12.7.2), SALT-
PROP (see 12.7.1).
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 823

Keywords for formats tN, E1, E3 19.1

12.4.3. SATNUM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
x REGIONS SOLUTION SUMMARY x SCHEDULE

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.29).
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). The number of
saturation region corresponds to the number of specified RP table.
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 824

Keywords for formats tN, E1, E3 19.1

12.4.4. SURFNUM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
x REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets the number for every grid block specifying the miscible (high surfactant)
saturation function region to which it belongs (if is used in models with surfactant injection –
section 2.23 – when oil and water are miscible at high surfactant concentration).

The number of values should be equal to the number of grid blocks. The data should be
terminated with a slash /.

The number of miscible saturation region corresponds to the number of RP table (spec-
ified by keywords SWFN (see 12.6.13), SOF2 (see 12.6.12), SOF3 (see 12.6.15), SWOF,
see 12.6.1), etc.
The region number should not be less than 1 or greater than the first parameter of TAB-
DIMS (see 12.1.29).

The keyword SATNUM (see 12.4.3) defines the immiscible saturation region numbers
(saturation functions are specified via 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 immiscible 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 825

Keywords for formats tN, E1, E3 19.1

12.4.5. SURFWNUM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
x REGIONS SOLUTION SUMMARY SCHEDULE

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.23).

The number of values should be equal to the number of grid blocks. The data should be
terminated with a slash /.

The region number should not be less than 1 or greater than the first parameter of TAB-
DIMS (see 12.1.29).

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 water wettability 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 826

Keywords for formats tN, E1, E3 19.1

12.4.6. LWSLTNUM / LSNUM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
x REGIONS SOLUTION SUMMARY SCHEDULE

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.24.3).
Option is activated via the keyword LOWSALT (see 12.1.63).

The number of values should be equal to the number of grid blocks. The data should be
terminated with a slash /.

The region number should not be less than 1 or greater than the first parameter of TAB-
DIMS (see 12.1.29).

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 827

Keywords for formats tN, E1, E3 19.1

12.4.7. IMBNUM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
x REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is used for relative permeabilities hysteresis – 2.7 (option HYSTER of the
keyword SATOPTS, see 12.1.75).

The keyword specifies which saturation table is to be used for each grid block for imbibi-
tion 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 (specified
via SATNUM, see 12.4.3).

The keyword should be followed by one integer for every grid block. The data should be
terminated with a slash /.

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.75):

• 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 IMBNUMX (see 12.4.7), IMBNUMY (see 12.4.7), IMBNUMZ, see 12.4.7). 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 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);

• HYSTER – hysteresis relative permeabilities 2.7.

Default: region number, specified via IMBNUM (see 12.4.7).

12.4.7. IMBNUM 828

Keywords for formats tN, E1, E3 19.1

Example
SATNUM
46000*1/

...

IMBNUM
23000*2 23000*3/

In this example for all 46000 model grid blocks 1-st saturation region SATNUM is de-
fined (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 sat-
uration 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 829

Keywords for formats tN, E1, E3 19.1

12.4.8. MISCNUM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
x REGIONS SOLUTION SUMMARY SCHEDULE

This keywords specifies the miscibility region number for each grid block – 2.6.12.

The keyword should be followed by one integer for every grid block. The data should be
terminated with a slash /.

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 830

Keywords for formats tN, E1, E3 19.1

12.4.9. EQLNUM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
x REGIONS SOLUTION SUMMARY SCHEDULE

The keyword should be followed by one integer for every grid block specifying the equi-
librium 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.30).
For each equilibrium region its initial conditions must be specified (EQUIL, see 12.16.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 831

Keywords for formats tN, E1, E3 19.1

12.4.10. FIPNUM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
x REGIONS SOLUTION SUMMARY SCHEDULE

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.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).
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 832

Keywords for formats tN, E1, E3 19.1

12.4.11. FIP

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
x REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies additional families (sets) of fluid-in-place regions, different from
the standard FIPNUM (see 12.4.10) family.

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 family 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 families of fluid-in-place regions (but not greater
than the second parameter of the keyword REGDIMS, see 12.1.32).
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 family FIP1 of three fluid-in-place regions for 3x3x2 grid. Note
that REGDIMS specifies that it is possible to define up to 2 families of fluid-in-place regions
(2-nd parameter of REGDIMS), the number of fluid-in-place regions in one family can be up
to 3 (1-th parameter of REGDIMS).

12.4.11. FIP 833

Keywords for formats tN, E1, E3 19.1

Example
DIMENS
25 25 3
/
...
REGDIMS
3 3
/
...
FIPMA1
1000*1 400*2 475*3
/
FIPMA2
875*1 1000*2
/

This example defines two families 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 families of fluid-in-place
regions (2-nd parameter of REGDIMS), the number of fluid-in-place regions in one family can
be up to 3 (1-st parameter of REGDIMS).

12.4.11. FIP 834

Keywords for formats tN, E1, E3 19.1

12.4.12. FIPOWG

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
x REGIONS SOLUTION SUMMARY SCHEDULE

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.16.2).

Standard FIP regions – FIPNUM (see 12.4.10), user FIP regions – FIP (see 12.4.11).

The keyword doesn’t have any parameters.

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.16.2);

• Oil region (consists of all blocks which are between WOC and GOC);

• Water region (consists of all blocks which are below WOC, specified via 3-th parameter
of EQUIL, see 12.16.2).

Example
FIPOWG

12.4.12. FIPOWG 835

Keywords for formats tN, E1, E3 19.1

12.4.13. FIPPATT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
x REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies the number for each block – the number of split region to which
this block will belong when splitting is done.
Splitting is described in section 5.12 (in tNavigator approach to splitting is different from
E1/E3).

This keyword specifies the number for each block – the number of split 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 split region are set.

12.4.13. FIPPATT 836

Keywords for formats tN, E1, E3 19.1

12.4.14. ROCKNUM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
x REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword should be followed by one integer for every grid block specifying the 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.21).

The table number should not be less or equal the second parameter of ROCKCOMP

!
(see 12.1.37).
Rock regions numbers can be re-specified in SCHEDULE section. It is rec-
ommended to do it carefully.

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 ROCKNUM
specifies that it is possible to define up to 4 rock regions.

12.4.14. ROCKNUM 837

Keywords for formats tN, E1, E3 19.1

12.4.15. COALNUM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
x REGIONS SOLUTION SUMMARY SCHEDULE

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.28.

For each region the following keywords are specified: LANGMUIR, see 12.9.2) or LANG-
MEXT (see 12.9.6).

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.32).
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 838

Keywords for formats tN, E1, E3 19.1

12.4.16. PMANUM

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
x REGIONS SOLUTION SUMMARY SCHEDULE

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 keywords GPMAINT (see 12.19.90), GP-
MAINT3 (see 12.19.91).

Default: 1.

Example
PMANUM
400*1 400*2 400*3 /

12.4.16. PMANUM 839

Keywords for formats tN, E1, E3 19.1

12.4.17. ENDNUM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
x REGIONS SOLUTION SUMMARY SCHEDULE

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.37), ENKRVD,
see 12.6.38) 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.1.136). The end point scaling option should be activated by specifying keyword END-
SCALE (see 12.1.136). 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 840

Keywords for formats tN, E1, E3 19.1

12.4.18. FLUXNUM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.32).
This keyword is ignored by tNavigator for splitting because in tNavigator approach to
splitting is different from E1/E3. Splitting is described in section 5.12.

For each flux region grid property array operations may be specified further, see key-
words ADDREG (see 12.3.22), COPYREG (see 12.3.19), MULTIREG (see 12.3.15), MUL-
TREGP (see 12.3.16).
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 841

Keywords for formats tN, E1, E3 19.1

12.4.19. VISCNUM

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
x REGIONS SOLUTION SUMMARY SCHEDULE

The keyword can only be used if THERMAL (see 12.1.54) 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.29). (The maximum number of viscosity regions is equal to
the maximum number of PVT regions).

Formulas for calculation of water, oil and gas viscosities are in sections 4.11, 4.12 and
4.13, respectively.

Default: In ST data format all blocks belong to the same viscosity region.
Default: In E3 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.19. VISCNUM 842

Keywords for formats tN, E1, E3 19.1

12.4.20. EOSNUM

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
x REGIONS SOLUTION SUMMARY SCHEDULE

The keyword should be followed by one integer for every grid block specifying the equa-
tion 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.29). The data should be
terminated with a slash /.
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.20. EOSNUM 843

Keywords for formats tN, E1, E3 19.1

12.4.21. OPERNUM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
x REGIONS SOLUTION SUMMARY SCHEDULE

The keyword should be followed by one integer for every grid block specifying the per-
forming arithmetic operations region to which it belongs.
For each performing arithmetic region grid property array operations may be specified
further with keyword OPERATER (see 12.3.27).
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.21. OPERNUM 844

Keywords for formats tN, E1, E3 19.1

12.4.22. MULTNUM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword should be followed by one integer for every grid block specifying the region
of applying multipliers to which it belongs.

The number of regions should be set via the 2-nd parameter of the keyword GRIDOPTS
(see 12.1.95). If this parameter is specified, then the regions MULTNUM will be used in the
keyword MULTREGP (see 12.3.16) (pore volume multipliers).
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.22. MULTNUM 845

Keywords for formats tN, E1, E3 19.1

12.4.23. KRNUM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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 function table will be used to calcu-
late 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.75):

• 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.23), KRNUMY (see 12.4.23), KRNUMZ, see 12.4.23). 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.23),
KRNUMX- (see 12.4.23), KRNUMY (see 12.4.23), KRNUMY- (see 12.4.23), KRNUMZ
(see 12.4.23) and KRNUMZ- (see 12.4.23).

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.23. KRNUM 846

Keywords for formats tN, E1, E3 19.1

12.4.24. KRNUMMF

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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
terminated with a slash /.

The keyword can be used for dual porosity runs DUALPORO (see 12.1.83) and dual per-
meability DUALPERM (see 12.1.84) (see section 2.27.1).

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.

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.24. KRNUMMF 847

Keywords for formats tN, E1, E3 19.1

12.4.25. IMBNUMMF

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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-
nated with a slash /.

The keyword can be used for dual porosity runs DUALPORO (see 12.1.83) and dual
permeability DUALPERM (see 12.1.84) in case when hysteresis option is used (parameter
HYSTER of the keyword SATOPTS, see 12.1.75) (see section 2.27.1).

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.25. IMBNUMMF 848

Keywords for formats tN, E1, E3 19.1

12.4.26. WH2NUM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
x REGIONS SOLUTION SUMMARY SCHEDULE

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.44).
The keyword should be followed by one integer for every grid block specifying the sat-
uration 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.29).
The data should be terminated with a slash /.
The following parameters should be specified:

1. saturation function region number for each grid block.

If keyword WAGHYSTR (see 12.8.44) is set, then keyword WH2NUM (see 12.4.26) is
optional. If WH2NUM (see 12.4.26) 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.26. WH2NUM 849

Keywords for formats tN, E1, E3 19.1

12.4.27. WH3NUM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
x REGIONS SOLUTION SUMMARY SCHEDULE

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.44).
The keyword should be followed by one integer for every grid block specifying the sat-
uration 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.29).
The data should be terminated with a slash /.
The following parameters should be specified:

1. saturation function region number for each grid block.

If keyword WAGHYSTR (see 12.8.44) is set, then keyword WH2NUM (see 12.4.26) is
optional. If WH2NUM (see 12.4.26) 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.27. WH3NUM 850

Keywords for formats tN, E1, E3 19.1

12.4.28. ZONES

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
x REGIONS SOLUTION SUMMARY SCHEDULE

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 data line should be terminated with the symbol /. All data should be terminated with
a final slash /.
The following parameters should be specified:

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 don’t 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 /
ZONE8 26 29 BOTTOMres /
ZONE9 30 39 BOTTOMres /
ZONE10 40 46 BOTTOMres /
/

12.4.28. ZONES 851

Keywords for formats tN, E1, E3 19.1

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 /
ZONE8 26 1* BOTTOMres /
ZONE9 30 1* BOTTOMres /
ZONE10 40 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 analogously.

12.4.28. ZONES 852

Keywords for formats tN, E1, E3 19.1

12.4.29. TRACKREG

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
x REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets regions for the tracking of hydrocarbon components when the option
TRACK is enabled (see section 2.20 and the keyword TRACK, see 12.1.135). Tracer group
will be created for the each region, the number of tracers in each group is equal to the number
of components specified in the keyword TRACK (see 12.1.135). Each tracer connected to its
own component.
The following parameters should be specified:

1. region number for the tracking of hydrocarbon components for each grid block.

The data should be terminated with a slash /.

Example
TRACKREG
162*1 162*2 /
In the example 2 regions for the tracking are set.

12.4.29. TRACKREG 853

Keywords for formats tN, E1, E3 19.1

12.5. PVT Properties

12.5.1. PROPS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies the beginning of data section which contains the data describing
reservoir fluid properties and reservoir properties.

12.5. PVT Properties 854

Keywords for formats tN, E1, E3 19.1

12.5.2. PVDO

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets dead oil PVT properties for all PVT regions.
The list of available keywords to set PVT properties is presented in the section Keywords to
set PVT.
The following parameters are to be specified:

1. oil phase pressure (METRIC: barsa, FIELD: psia) ( pO argument in 2.8.2, 2.8.5, 2.8.1),

2. oil formation volume factor (METRIC: rm3 /sm3 , FIELD: rb/stb) (BO in 2.8.2),

3. oil viscosity at this pressure (cP) ( µO in 2.8.1).

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.29).
Default: none.

Note:

• Models in E1 format: linear interpolation of the reciprocals of BO and BO µO is done

(not parameters themselves) between data points;

• Models in E3 format: linear interpolation of parameters BO and µO is done;

• Default method of viscosity and formation volume factor interpolation can be changed
via the keyword PVTOPTS (see 12.5.36).

• Extrapolation may lead to physically unrealistic values, in which case the table needs
revision (see section 7.1.3. What causes the warnings of negative compressibility and/or
viscosity).

12.5.2. PVDO 855

Keywords for formats tN, E1, E3 19.1

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.29) keyword defined 2 PVT regions.

12.5.2. PVDO 856

Keywords for formats tN, E1, E3 19.1

12.5.3. PVCDO

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets dead oil (with constant compressibility) PVT properties for all PVT
regions.
The list of available keywords to set PVT properties is presented in the section Keywords to
set PVT.
The following parameters are to be specified:
1. reference pressure (METRIC: barsa, FIELD: psia) ( pref in 2.8.2, 2.8.1),
2. oil formation volume factor at the reference pressure (METRIC: rm3 /sm3 , FIELD:
rb/stb) (BO in 2.8.2),
∂ 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.1),
∂ µ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 (see 12.1.29).
The oil formation volume factor at the pressure pO is calculated using the formula:

BO (pO ) = BO (pref )exp(−cO (pO − pref ))

Viscosity:
µO (pO ) = µO (pref )exp(cv (pO − pref ))
Default: none.

Example
TABDIMS
1 2 2* 1
/
...
PVCDO
83.20 1.15 1.7e-4 0.22 0 /
102.34 1.15 1.56e-5 0.73 0 /

12.5.3. PVCDO 857

Keywords for formats tN, E1, E3 19.1

In this example there are two regions with different dead oil PVT properties. The keyword
TABDIMS (see 12.1.29) sets the number of such regions equal to 2.

12.5.3. PVCDO 858

Keywords for formats tN, E1, E3 19.1

12.5.4. PVTO

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets live oil PVT properties for all PVT regions.
The list of available keywords to set PVT properties is presented in the section Keywords to
set PVT.
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.8.5),

2. bubble point pressure (METRIC: barsa, FIELD: psia) (this is argument pbub in 2.8.2,
2.8.5, 2.8.1),

3. oil formation volume factor (METRIC: rm3 /sm3 , FIELD: rb/stb) (this is BO in 2.8.2),

4. oil viscosity at bubble point pressure (cP) (this is µO in 2.8.1).

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 shouldn’t be larger than 4-th parameter of TABDIMS, see 12.1.29).
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 additional data for 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.29).
A number of sets of data in one PVT table (number of different RG,O ) shouldn’t be larger
than 6-th parameter of TABDIMS (see 12.1.29).

Default: none.

12.5.4. PVTO 859

Keywords for formats tN, E1, E3 19.1

• Models in E1 format: linear interpolation of the reciprocals of BO and

BO µO is done (not parameters themselves) between data points;

• Models in E3 format: linear interpolation of the reciprocal of BO is

!
done, but for µO interpolation is done directly;

• Default method of viscosity and formation volume factor interpolation

can be changed via the keyword PVTOPTS (see 12.5.36).

• Extrapolation may lead to physically unrealistic values, in which case

the table needs revision (see section 7.1.3. What causes the warnings of
negative compressibility and/or viscosity).

In saturated state there is one-to-one correspondence between bubble point

pressure pbub and gas-oil ratio Rs . The current pressure is the bubble point
pressure: p = pbub . In this case an oil formation volume factor and viscosity
are interpolated based on Rs . An interpolation method is specified by the first
two parameters of the keyword PVTOPTS (see 12.5.36).
If oil is in the undersaturated state then undersaturated branches can be
found based on the current Rs and be used for an interpolation. Let’s only
one undersaturated branch B1undersat exists. Then, all branch pressures will
be shifted to the bubble point pressure (the first value on a branch – p[0]).

!
And an oil formation volume factor is normalized by Bsat /B[0]undersat in oder
to provide value continuity when pressure tends to bubble point pressure:

B1 = Bundersat (prel ) × Bsat /B[0]undersat

The obtained value B1 is interpolated based on relative pressure prel = p −

pbub .
If there are two undersaturated branches – B1undersat and B2undersat , between
which the current Rs is located, values B1 and B2 are calculated in simi-
lar way, as has been done for one branch. If parameter 5 of the keyword
PVTOPTS (see 12.5.36) is set to YES the normalization (multiplication
by Bsat /B[0]undersat ) is not implemented. Further an interpolation between
branch B1 and branch B2 based on Rs is carried out.
The similar approach is used for interpolation of oil viscosity µ.

12.5.4. PVTO 860

Keywords for formats tN, E1, E3 19.1

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.29) 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 861

Keywords for formats tN, E1, E3 19.1

12.5.5. PVTW

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets water PVT properties for all PVT regions.
The list of available keywords to set PVT properties is presented in the section Keywords to
set PVT.
The following parameters are to be specified:

1. Reference pressure (METRIC: barsa, FIELD: psia). This is argument pref in 2.8.2,
2.8.1.
Default: error (E1), 1 atm = 14.6959 psia (E3).

2. Water formation volume factor (METRIC: rm3 /sm3 , FIELD: rb/stb). This is BW
in 2.8.2.
Default: 1.0.

3. Water compressibility (METRIC: 1/bars, FIELD: 1/psi). This is cW in 2.8.2.

Default: 0 (E1), 4 · 10−5 1/atm (E3).

4. Water viscosity (cP). This is µW in 2.8.1.

Default: 0.5 cP (E1), 0.3 cP (E3).
∂ µW 1
5. Water viscosibility (METRIC: 1/bars, FIELD: 1/psi) Cv = .
∂ P µW
Default: 0.0.

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.29).
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

12.5.5. PVTW 862

Keywords for formats tN, E1, E3 19.1

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 863

Keywords for formats tN, E1, E3 19.1

12.5.6. PVCO

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets live oil (in compressibility form) PVT properties.
The list of available keywords to set PVT properties is presented in the section Keywords to
set PVT.
These properties can also be specified by the keyword PVTO (see 12.5.4). The differ-
ence between PVCO and PVTO (see 12.5.4) is following: PVCO is used if undersaturated oil
with a special RG,O ( 2.8.5) has a pressure-independent compressibility and the derivative of
viscosity of undersaturated oil is pressure-independent too. Hence, tables for undersaturated
oil which set the dependence between the formation volume factor, viscosity and pressure
shouldn’t be specified.

Live oil PVT properties for each region should be entered in a new line. Region prop-
erties should be terminated with a slash /. The number of tables is equal to the number of
regions with different PVT properties (set by the second parameter of the keyword TABDIMS,
see 12.1.29).

The following parameters are to be specified:

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.8.2, 2.8.5, 2.8.1),

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.8.5),

3. the formation volume factor (METRIC: rm3 /sm3 , FIELD: rb/stb) of saturated oil at
the bubble point pressure (BO in 2.8.2),

4. the viscosity (cP) of saturated oil at the bubble point pressure ( µO in 2.8.1),

5. the compressibility (METRIC: 1/bars, FIELD: 1/psi) of undersaturated oil with gas-oil
∂ BO 1
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.54) to set the
oil viscosity pressure dependence, you should specify only columns 1 and 4. Other columns

12.5.6. PVCO 864

Keywords for formats tN, E1, E3 19.1

should be defaulted.

Note:

• Models in E1 format: linear interpolation of the reciprocals of BO and BO µO is done

(not parameters themselves) between data points;

• Models in E3 format: linear interpolation of parameters BO and µO is done;

• Default method of viscosity and formation volume factor interpolation can be changed
via the keyword PVTOPTS (see 12.5.36).

• Extrapolation may lead to physically unrealistic values, in which case the table needs
revision (see section 7.1.3. What causes the warnings of negative compressibility and/or
viscosity).

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 865

Keywords for formats tN, E1, E3 19.1

12.5.7. PVDG

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets dry gas PVT properties (no vaporized oil) for all PVT regions.
The list of available keywords to set PVT properties is presented in the section Keywords to
set PVT.
The following parameters are to be specified:

1. reference pressure (METRIC: barsa, FIELD: psia), (this is argument pG in 2.8.2,

2.8.1),

2. gas formation volume factor (METRIC: rm3 /sm3 , FIELD: rb/Msc f ), (this is BG
in 2.8.2),

3. gas viscosity (cP) (this is µG in 2.8.1).

For each PVT region gas 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.29).
Default: none.

Note:

• Models in E1 format: linear interpolation of the reciprocals of BG and BG µG is done

(not parameters themselves) between data points;

• Models in E3 format: linear interpolation of parameters BG and µG is done;

• Default method of viscosity and formation volume factor interpolation can be changed
via the keyword PVTOPTS (see 12.5.36).

• Extrapolation may lead to physically unrealistic values, in which case the table needs
revision (see section 7.1.3. What causes the warnings of negative compressibility and/or
viscosity).

12.5.7. PVDG 866

Keywords for formats tN, E1, E3 19.1

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 867

Keywords for formats tN, E1, E3 19.1

12.5.8. PVTG

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets wet gas PVT properties for all PVT regions.
The list of available keywords to set PVT properties is presented in the section Keywords to
set PVT.
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.8.2,
2.8.6, 2.8.1),

2. oil vaporization in gas (METRIC: sm3 /sm3 , FIELD: stb/Msc f ) (this is RO,G in 2.8.6),

3. gas formation volume factor (METRIC: rm3 /sm3 , FIELD: rb/Msc f ) (this is BG
in 2.8.2),

4. gas viscosity at bubble point pressure (cP) (this is µG in 2.8.1).

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.29).
A number of sets of data in one PVT table (number of different pG ) shouldn’t be larger than
7-th parameter of TABDIMS (see 12.1.29).

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 shouldn’t be larger than 4-th parameter of TABDIMS, see 12.1.29).
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.16.38). For pres-
sures above dew point pressure saturated oil properties are extrapolated linearly.

Default: none.

Note:

• Models in E1 format: linear interpolation of the reciprocals of BG and BG µG is done

(not parameters themselves) between data points;

12.5.8. PVTG 868

Keywords for formats tN, E1, E3 19.1

• Models in E3 format: linear interpolation of parameters BG and µG is done;

• Default method of viscosity and formation volume factor interpolation can be changed
via the keyword PVTOPTS (see 12.5.36).

• Extrapolation may lead to physically unrealistic values, in which case the table needs
revision (see section 7.1.3. What causes the warnings of negative compressibility and/or
viscosity).

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.29) keyword defined 2 PVT regions.

12.5.8. PVTG 869

Keywords for formats tN, E1, E3 19.1

12.5.9. PVZG

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets dry gas PVT properties (compressibility factor is taken into considera-
tion).
The list of available keywords to set PVT properties is presented in the section Keywords to
set PVT.
The data should consist of tables (number of tables less or equal to the 2-nd parameter
of the keyword TABDIMS (see 12.1.29).) 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.1).

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.29).

This formula represent a connection among the formation volume factor BG (BG in 2.8.2),
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.15 K -absolute temperature.
Default: nothing.

12.5.9. PVZG 870

Keywords for formats tN, E1, E3 19.1

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 871

Keywords for formats tN, E1, E3 19.1

12.5.10. OVPG

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies the variation of oil viscosity with the pressure gradient in each
PVT region. After this keyword the following parameters (given one set of data) should be
specified in succession:

• characteristic pressure gradient ∆P0 defined the flow variation (METRIC: barsa/m,
FIELD: psi/ f t );

• value of oil flow multiplier F0 ;

• ...

• characteristic pressure gradient ∆Pi defined the flow variation (METRIC: barsa/m,
FIELD: psi/ f t );

• value of oil flow multiplier Fi ;

• ...

• characteristic pressure gradient ∆PN defined the flow variation (METRIC: barsa/m,
FIELD: psi/ f t );

• value of oil flow multiplier FN ;

where N is the user specified number of pressure gradients.

Each set of data should be terminated by a slash /.
The number of set is equal to the number of PVT region specified by keyword TABDIMS
(see 12.1.29).

If pressure gradient is lower than ∆P0 the oil flow is multiplied by value of oil flow
multiplier F0 . If pressure gradient is higher than ∆PN the oil flow is multiplied by FN . The
value of flow multiplier is linearly interpolated between Fi and Fi+1 , i = 0, ..., N − 1 when
pressure gradient varies between ∆Pi and ∆Pi+1 .
The value of pressure gradient ∆P and multiplier FO can be set equal to 0.
In this example if pressure gradient is smaller than 0.01 oil flow will be multiplied by 0,
if pressure gradient is higher than 0.1 oil flow will be multiplied by 1. If pressure gradient
varies between 0.01 and 0.1 than oil flow will be multiplied by 0.5.

12.5.10. OVPG 872

Keywords for formats tN, E1, E3 19.1

Example
OVPG
0.01 0
0.1 1
/

12.5.10. OVPG 873

Keywords for formats tN, E1, E3 19.1

12.5.11. STANDO

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets data that is used in Oil Standing’s correlations (2.9) to calculate oil
formation volume factor and viscosity. The data should be terminated with a slash /.

The following parameters should be specified:

1. Rsb – gas solubility at bubble point (METRIC: sm3 /sm3 , FIELD: Msc f /stb);

2. pb – bubble-point pressure (METRIC: barsa, FIELD: psia);

3. T – system temperature (METRIC: ◦ C, FIELD: ◦ F);

4. cO – isothermal compressibility coefficient (METRIC: 1/bars, FIELD: 1/psi).

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.11. STANDO 874

Keywords for formats tN, E1, E3 19.1

12.5.12. STANDG

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets data that is used in Gas Standing’s correlations (2.10) to calculate gas
formation volume factor and viscosity. The data should be terminated with a slash /.

The following parameters should be specified:

1. z – gas compressibility factor (Z-factor);

2. T – system temperature (METRIC: ◦ C, FIELD: ◦ F).

Example
STANDG
0.9 121.11 /

12.5.12. STANDG 875

Keywords for formats tN, E1, E3 19.1

12.5.13. RSCONST

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.57) and DISGAS (see 12.1.60) shouldn’t 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). Allowed combinations of key-
words specified relative permeabilities are given in the section 2.6.1.

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 concentration.
The keyword RSCONSTT (see 12.5.14) 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.13. RSCONST 876

Keywords for formats tN, E1, E3 19.1

12.5.14. RSCONSTT

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.57) and DISGAS (see 12.1.60) shouldn’t 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). Allowed combinations of key-
words specified relative permeabilities are given in the section 2.6.1.

The difference between RSCONST (see 12.5.13) 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 should not mix (transmissibility should not 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.29). 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
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 concen-
tration (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.29) is equal to 3.

12.5.14. RSCONSTT 877

Keywords for formats tN, E1, E3 19.1

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.14. RSCONSTT 878

Keywords for formats tN, E1, E3 19.1

12.5.15. RVCONST

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.56) and VAPOIL (see 12.1.59) shouldn’t be specified in the
Definition section (12.1). So oil is not considered as an active phase. The model becomes
two-phase or single-phase (if water phase is presented or not). Allowed combinations of key-
words specified relative permeabilities are given in the section 2.6.1.

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 in
any block falls below this value);

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.16) 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.15. RVCONST 879

Keywords for formats tN, E1, E3 19.1

12.5.16. RVCONSTT

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.56) and VAPOIL (see 12.1.59) shouldn’t be specified in the
Definition section (12.1). So oil is not considered as an active phase. The model becomes
two-phase or single-phase (if water phase is presented or not). Allowed combinations of key-
words specified relative permeabilities are given in the section 2.6.1.

The difference between RVCONST (see 12.5.15) 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 con-
centrations shouldn’t mix (transmissibility shouldn’t 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.29). 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 in
any block falls below this value);
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
(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.16. RVCONSTT 880

Keywords for formats tN, E1, E3 19.1

This example sets vaporized oil concentration in two PVT regions.

12.5.16. RVCONSTT 881

Keywords for formats tN, E1, E3 19.1

12.5.17. ROCK

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies rock properties for each PVT region. Parameters 3-6 are used in
case of geomechanical modeling via option EX of keyword GEOMECH (see 12.1.99) (see
section 2.29.2). Parameters defined by this keyword are used for calculation of porosity (see
section 2.5).
An arbitrary number of data lines can be entered, terminated with a slash /. The number
of lines depends on number of rock regions specified in TABDIMS (see 12.1.29). The number
of rock regions is specified via 13-th parameter of TABDIMS (see 12.1.29); 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.29).

Each data line contains the following parameters:

1. pre f - reference pressure (METRIC: barsa, FIELD: psia);

Default: 1.0132 bar .

2. C pp - rock compressibility (METRIC: 1/bar , FIELD: 1/psi) (coefficient c in 2.5);

Default:

• 0 (for E1 format),
• METRIC: 4.934E-5 1/bar , FIELD: 3.402E-6 1/psi (for E3 format).

3. CR - compressibility of the rock matrix, CR = KS−1 (METRIC: 1/bar , FIELD: 1/psi);

1
4. Cbc = - block compressibility (block that contains mixture), Cbc = K −1 (METRIC:
Kbulk
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;

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.17. ROCK 882

Keywords for formats tN, E1, E3 19.1

• 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 − 2ν0 )(1 − ϕ0 )

• if the value of Poisson coefficient is not specified ν0 :

Cbc
CR = (12.3)
3ϕ0
1+
2(1 − ϕ0 )

• if C pp is not specified, the default value will be used C pp = 0.00005bars−1

• 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.17) or ROCK-
TAB (see 12.5.21). 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 (Ref-
erence 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.29). 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.17. ROCK 883

Keywords for formats tN, E1, E3 19.1

12.5.18. RKTRMDIR

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets the number of parameters in one table row of the keyword ROCKTAB
(see 12.5.21). 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.18. RKTRMDIR 884

Keywords for formats tN, E1, E3 19.1

12.5.19. ROCKTSIG

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies a sigma factor multiplier as a function of pressure in tabulated

form in order to take into account a modification of the matrix–fracture coupling caused by
rock compaction for dual porosity models (see section 2.27). Rock compaction tables can be
specified in addition to tables given by ROCKTAB (see 12.5.21). The keyword can be used
if either DUALPORO (see 12.1.83) or DUALPERM (see 12.1.84) are specified in the section
RUNSPEC, and valid data should be specified by ROCKTAB (see 12.5.21), in order to enable
ROCKTSIG input.
The number of compaction tables is specified by 2-nd parameter of ROCKCOMP
(see 12.1.37). Each table should be terminated by /. Each table consists of two columns
of the same size:

1. pressure (METRIC: barsa, FIELD: psia);

pressure values should monotonically increase, unless the option STRESS (1-st param-
eter of the keyword ROCKOPTS, see 12.5.31) is used. In this case pressure values
monotonically decrease;

2. multiplier for sigma factor σ ;

multiplier values should be level or increasing.

The number of entries in a column should not be less than 2 or greater than number
given by 4-th parameter of the keyword TABDIMS (see 12.1.29). 13-th parameter of the
keyword TABDIMS (see 12.1.29) corresponds to the number of rock compaction tables given
by ROCKNUM (see 12.4.14).

!
If the number of rock compaction tables is specified by both 13-th parameter
of TABDIMS (see 12.1.29) and 2-nd parameter of ROCKCOMP (see 12.1.37)
then the maximum will be taken.

!
Despite of the keyword ROCKNUM (see 12.4.14) is used for the entire grid
only the ROCKNUM (see 12.4.14) numbers corresponding to the matrix cells
are used to obtain rock compaction tables (ROCKTSIG) for the matrix-
fracture coupling modification. For fracture cells ROCKNUM (see 12.4.14) is
ignored.
ROCKTSIG can be used only if reversible/irreversible rock compaction option (options
REVERS and IRREVERS of the keyword ROCKCOMP, see 12.1.37) is specified. The matrix–
fracture coupling transmissibility in a block is adjusted dynamically by multiplying the refer-
ence values (derived from the input data) by the corresponding factors in the table, interpolated

12.5.19. ROCKTSIG 885

Keywords for formats tN, E1, E3 19.1

at the instantaneous pressure in the block.

If the keyword OVERBURD (see 12.5.32) is specified the overburden pressure is sub-
tracted from the grid block pressure before interpolating multipliers for the sigma factor σ .
If the overburden pressure Poverburden , given by OVERBURD (see 12.5.32), is higher than
fluid pressure Pf luid (which is often the case) then the effective fluid pressure will be negative
ef f ef f
(Pf luid = Pf luid −Poverburden , where Pf luid is the effective fluid pressure). In this case rock com-
paction tables (given by ROCKTSIG) should be specified with negative pressure values. This
can be avoided by specifying the option STRESS of the keyword ROCKOPTS (see 12.5.31)
before the keyword ROCKTSIG. In this case multipliers for the sigma factor σ are entered
ef f
in the table versus effective overburden pressures (Poverburden = Poverburden − Pf luid ), which are
positive.
Example
DUALPORO
...
ROCKCOMP
REVERS/
...
ROCKTSIG
100 0.8
500 1
/

In this example one table of data containing sigma factor multipliers versus pressures is
specified. For pressure 100 a multiplier is equal to 0.8, for pressure 500 –1.

12.5.19. ROCKTSIG 886

Keywords for formats tN, E1, E3 19.1

12.5.20. ROCKPAMA

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies parameters of Palmer-Mansoori rock compaction model (see sec-
tion 2.28). The keyword is available if Coal Bed Methane (CBM) Model is activated using
the keyword COAL (see 12.1.85) (see section 2.28).
The keyword is followed by set of data. The number of rows is specified by 2-nd parameter
of the keyword ROCKCOMP (see 12.1.37). Each row should be terminated by the symbol /.
If a row is left empty its parameters are copied from the previous row.
Each row contains the following parameters:

1. K is the bulk modulus (METRIC: barsa, FIELD: psia);

2. M is the constrained axial modulus (METRIC: barsa, FIELD: psia);

3. γ is the grain compressibility (METRIC: 1/barsa, FIELD: 1/psia);

Default: 0.

4. β is the Langmuir curve parameter (METRIC: 1/barsa, FIELD: 1/psia);

Default: 0.

5. εl is the Langmuir curve parameter;

Default: 0.

6. f is the fraction varying from 0 to 1;

Default: 0.5.

7. n is the exponent in permeability-porosity relationship;

Default: 3.

8. g is the geometric factor (from 0 to 1) related to the orientation of the fracture system;
Default: 1.

According to the Palmer-Mansoori model the pore volumes V (p) at the current pressure
p is calculated using the following formula:
   
cm 1 K βp β p0
V (p) = V (p0 ) 1 + (p − p0 ) + −1 −
ϕ0 ϕ0 M 1 + β p 1 + β p0

where

12.5.20. ROCKPAMA 887

Keywords for formats tN, E1, E3 19.1

• ϕ0 is the initial porosity;

• V (p0 ) is the pore volume at the initial pressure, p0 ;

• cm = Mg − M
K 
+ f −1 γ

Suggesting that permeability varies with porosity as

k ϕ
=
k0 ϕ0

then the transmissibility multiplier is calculated as:

   n
cm 1 K βp β p0
1 + (p − p0 ) + −1 −
ϕ0 ϕ0 M 1 + β p 1 + β p0

In the Palmer-Mansoori rock compaction model the input porosities are taken at reser-
voir conditions. The rock model only applies to the pore-volume grid-cells (COALNUM
(see 12.4.15)=0, i.e. there is no coal in a block ).
Example
ROCKPAMA
1000 1000 0 0.001 0.01 /

12.5.20. ROCKPAMA 888

Keywords for formats tN, E1, E3 19.1

12.5.21. ROCKTAB

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is used to set tables of transmissibility dependence on pressure for each rock
region. This dependence is used for calculation of absolute permeability tensor (see section
2.4). 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.37).

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.31).
In this case pressure values should decrease. If the overburden pressure (Poverburden –
OVERBURD, see 12.5.32) 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 - ef-
fective fluid pressure). In this case the rock compaction tables (ROCKTAB, see 12.5.21)
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 transmissi-
bility multipliers will be tabulated against the effective overburden pressure, which will
be positive (Pe f over = Poverburden − Pf luid ).

2. porosity multiplier;

3. transmissibility multiplier (if RKTRMDIR (see 12.5.18) 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.18) is present);

5. transmissibility multiplier in the Z-direction (can be specified only if RKTRMDIR

(see 12.5.18) 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.17) or ROCK-
TAB (see 12.5.21). If these keywords are not set then the default value will be used and the
following warning will be displayed:

12.5.21. ROCKTAB 889

Keywords for formats tN, E1, E3 19.1

Warning: no ROCK or ROCKTAB specified. ROCK with default values will be used (Ref-
erence pressure is (1.013250) bar, rock compressibility is (0.000000) 1/bar).

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.21. ROCKTAB 890

Keywords for formats tN, E1, E3 19.1

12.5.22. ROCKTABH

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is used to specify hysteretic rock compaction data tables. This dependence
is used for calculation of absolute permeability tensor (see section 2.4).
The number of tables should not exceed the value indicated by 2 parameter of keyword
ROCKCOMP (see 12.1.37). Each table consists of 2 records, the number of records should
not exceed the number of PVT tables (specified by parameter 2 of keywords TABDIMS,
see 12.1.29). Each record should be terminated by symbol /.
Each set of records defining the elastic expansion and contraction of the rock contains
curves of pore volume and transmissibility multipliers vs. pressure. The elastic behavior is
bounded at low pressure by the deflation curve. The deflation curve connects the first points
on each elastic curve. If the HYSTER option is selected (see picture 56 a), the elastic curves
are extrapolated to infinite pressure. If the BOBERG option is used, the elastic behavior is
bounded at high pressure by the dilation curve (see picture 56 b). The dilation curve connects
the last points on each elastic curve. Each table is terminated by a symbol / located at new
line.

(a) Option HYSTER. (b) Option BOBERG.

Figure 56. Hysteretic rock compaction.

Each record consists of 3 columns of data and terminates by slash /. If the RKTRMDIR
(see 12.5.18) keyword is specified, each table consists of 5 columns of data. If all values
in the 4–th and 5–th columns are defaulted and the values from the third column are used.
Defaulting these values is equivalent to not specifying RKTRMDIR (see 12.5.18).
The following parameters are to be specified:
1. pressure (METRIC: barsa, FIELD: psia). Pressure values should increase down the
column except for STRESS option (the 1-st parameter of the keyword ROCKOPTS,
see 12.5.31) is used. In this case pressure values should decrease.

12.5.22. ROCKTABH 891

Keywords for formats tN, E1, E3 19.1

2. porosity multiplier. Values should be level or grow down the column;

3. transmissibility multiplier. Values should be level or grow down the column. If RKTR-
MDIR (see 12.5.18) 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.18) is present);

5. transmissibility multiplier in the Z-direction (can be specified only if RKTRMDIR

(see 12.5.18) is present).

ROCKTABH keyword must be used if the Hysteretic Rock Compaction option is used (i.e.,
HYSTER or BOBERG specified by keyword ROCKCOMP (see 12.1.37) in the RUNSPEC sec-
tion). The pore volumes and transmissibilities in grid blocks are adjusted dynamically by
multiplying the input values by the corresponding multipliers specified in the table, interpo-
lated at the instantaneous grid block pressures.

12.5.22. ROCKTABH 892

Keywords for formats tN, E1, E3 19.1

Example
ROCKCOMP
'BOBERG' 2 /
...
RKTRMDIR
ROCKTABH
1000 0.600 0.100 1.100 1.0
1727 0.606 0.106 1.106 1.0
2596 0.614 0.114 1.114 1.0
3345 0.622 0.122 1.122 1.0
4126 0.630 0.130 1.130 1.0 /
1926 0.652 0.152 1.152 1.0
2772 0.658 0.158 1.158 1.0
3513 0.666 0.166 1.166 1.0
4454 0.678 0.178 1.178 1.0 /
2671 0.700 0.200 1.200 1.0
3732 0.716 0.216 1.216 1.0
4772 0.734 0.234 1.234 1.0 /
3257 0.752 0.252 1.252 1.0
5000 0.800 0.300 1.300 1.0 /
/
1000 1.50 2.00 1.100 1.0
1727 1.56 2.06 1.106 1.0
2596 1.64 2.14 1.114 1.0
3345 1.72 2.22 1.122 1.0
4126 1.80 2.30 1.130 1.0 /
1926 2.02 2.52 1.152 1.0
2772 2.08 2.58 1.158 1.0
3513 2.16 2.66 1.166 1.0
4454 2.28 2.78 1.178 1.0 /
2671 2.50 3.00 1.200 1.0
3732 2.66 3.16 1.216 1.0
4772 2.84 3.34 1.234 1.0 /
3257 3.02 3.52 1.252 1.0
5000 3.50 4.00 1.300 1.0 /
/

In this example there are two tables containing 4 records. Each record is an elastic curve.
The first curve (record) consists of 5 lines, the second one consists of 4 lines, the third
one consists of 3 lines and the forth one consists of 2 lines. Each curve pore is a curve of
pore volume and transmissibility multipliers (in X, Y, Z directions) vs. pressure, i.e. a record
consists of 5 columns: 1 column is the pressure, 2 column is the porosity multiplier, 3, 4
and 5 are transmissibility multipliers in X, Y, Z directions, respectively. The deflation curve

12.5.22. ROCKTABH 893

Keywords for formats tN, E1, E3 19.1

connects the following points: 1000, 1926, 2671, 3257.

12.5.22. ROCKTABH 894

Keywords for formats tN, E1, E3 19.1

12.5.23. HMMROCKT

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword defines the values of porosity multiplier modifiers (λ1 and λ2 in equation
2.13) that will be applied to ROCKTAB (see 12.5.21) or ROCKTABH (see 12.5.22) compaction
tables.

The data should be entered in the lines below the keyword. Each line corresponds to one
Rock Compaction Table and is terminated with a slash /. All data should be terminated with
a final slash /.
The following parameters should be specified:

1. Number of ROCKTAB (see 12.5.21) or ROCKTABH (see 12.5.22) table.

2. Dimensionless multiplicative modification parameter (λ1 in equation 2.13).

3. Dimensionless additive modification parameter (λ2 in equation 2.13).

Example
HMMROCKT
1 1.0 1.15 /
2 1.0 1.05 /
3 0.9 1.25 /
/

HMRREF
449.0 500.0 /
500.0 500.0 /
345.0 500.0 /

In this example the porosity multipliers modifications are defined for the Rock Tables 1,
2 and 3:

• Keyword HMMROCKT sets the values of λ1 and λ2 in equation 2.13

• Keyword HMRREF sets the values of pre f and pscale in equation 2.13

12.5.23. HMMROCKT 895

Keywords for formats tN, E1, E3 19.1

12.5.24. HMRREF

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword defines the reference and scaling pressures for porosity multiplier modifiers
( pre f and pscale in equation 2.13) that will be applied to ROCKTAB (see 12.5.21) or ROCK-
TABH (see 12.5.22) compaction tables.

The data should be entered in the lines below the keyword. Each line corresponds to one
Rock Compaction Table and is terminated with a slash /. The data must be specified for all
Rock Tables (see the 2 − nd parameter of ROCKOPTS (see 12.5.31) keyword for details).

1. Pivot reference pressure ( pre f in equation 2.13). (METRIC: barsa, FIELD: psia).

2. Reference scale ( pscale in equation 2.13). (METRIC: barsa, FIELD: psia).

Example
HMMROCKT
1 1.0 1.15 /
2 1.0 1.05 /
3 0.9 1.25 /
/

HMRREF
455.0 490.0 /
500.0 490.0 /
377.0 490.0 /

In this example the porosity multipliers modifications are defined for the Rock Tables 1,
2 and 3:

• Keyword HMMROCKT sets the values of λ1 and λ2 in equation 2.13.

• Keyword HMRREF sets the values of pre f and pscale in equation 2.13

12.5.24. HMRREF 896

Keywords for formats tN, E1, E3 19.1

12.5.25. PERMSTAB

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies permeability multiplier as function of rock stress in a tabular form.
This keyword is only valid if the keyword GEOMECH (see 12.1.99) (option FE) is set in
the section RUNSPEC. The detailed description of geomechanical model is given in section
2.29.1.
The table dimension is given by keyword GEODIMS (see 12.1.100). The number of table
columns is specified by its 3-rd parameter. The number of table rows is specified by its 2-nd
parameter +1.
The first data record contains values of the maximum principal stress. These values should
monotonically increase. In the following records (the number of these records (rows) is speci-
fied by 2-nd parameter of GEODIMS, see 12.1.100) the values of the minimum principal stress
is first specified, followed by the data of the permeability multipliers. Values of the minimum
principal stress should monotonically increase, i.e. each following record should have higher
stress value. Repeat counts may be used only with the multipliers. If a multiplier is equal to 1
then the phase mobilities are unchanged.
Each record should be terminated with /. The table of data should be terminated with /
located on empty line.
The monotonicity of permeability multipliers are not controlled. If input maximum and
minimum principal stresses from the simulation model are outside of the range specified by
this table, constant slope extrapolation is used.
Example
GEODIMS
1* 3 4 /
...
PERMSTAB
-3000 -2000 -1000 1000 /
-4000 2*1 1.1 1.3 /
-3000 1*1 1.1 1.2 1.4 /
1000 1.1 1.3 1.6 1.9 /
/

12.5.25. PERMSTAB 897

Keywords for formats tN, E1, E3 19.1

12.5.26. TRROCK

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets properties to model tracer adsorption on rock (see section 2.17.3). The
number of data lines is equal to the number of saturation regions (see the first parameter of
keyword TABDIMS, see 12.1.29). Each data line should be terminated with the symbol /.
The following parameters should be specified:

1. adsorption index: 1 (desorption can take place if polymer concentration decreases in

grid block) or 2 (desorption is prevented);

2. mass rock density in reservoir conditions at reference pressure (METRIC: kg/rm3 ,

FIELD: lb/rb);

3. the adsorption initialization model:

• 1 – the input tracer concentration is defined from equilibration condition (the total
mass of tracer is conserved and partitioned between the fluid and rock);
• 2 – the input fluid concentration is equal to the input tracer concentration, and
adsorbed tracer concentration is defined from adsorption function (see keyword
TRADS, see 12.7.17).
• Default: 1.

The rock mass for a grid block is calculated from:

1−ϕ
M = Vρr ,
ϕ
where:

• V is the block pore volume at reference pressure;

• ρr is the rock density (parameter 2 of TRROCK, see 12.5.26);

• ϕ is the block porosity.

Note 1. Besides black-oil models, this keyword can be used in compositional isothermal
models with one-component water in E3 format. In such models tracer can be connected to
water only, not other components.
Note 2. If either the polymer (see section 2.16.1) or surfactant (see section 2.23) models
are active, then the mass density entered here will be ignored. The rock mass density will be
taken from the PLYROCK (see 12.8.30) keyword if present, or otherwise from the SURFROCK

12.5.26. TRROCK 898

Keywords for formats tN, E1, E3 19.1

(see 12.8.13) keyword, or FOAMROCK (see 12.11.3) if no one of previous is not present, or
TRROCK (see 12.5.26) if no one of previous is not present.
Example
TRROCK
1 2000 1 /
In the example adsorption properties for one saturation region are set.

12.5.26. TRROCK 899

Keywords for formats tN, E1, E3 19.1

12.5.27. ROCKAXES

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies the azimuth and zenith angle of the regional stress in each ROCK
region. It is used in case of geomechanical modeling via option EX or FE of keyword GE-
OMECH (see 12.1.99) (see section 2.29).
Region number - the same number as in the keyword ROCK (see 12.5.17) (i.e. is under
control of the keyword ROCKOPTS, see 12.5.31).
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 ◦ and zenith angle is 0 ◦ .
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.27. ROCKAXES 900

Keywords for formats tN, E1, E3 19.1

12.5.28. ROCKSTRE

Data x tN E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies the diagonal elements of the stress tensor (the regional stress). It is
used in case of geomechanical modeling via option EX of keyword GEOMECH (see 12.1.99)
(see section 2.29.2).
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.28. ROCKSTRE 901

Keywords for formats tN, E1, E3 19.1

12.5.29. COHESION

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies the intercept of the failure envelope with the τ axis. The Mohr–
Coulomb failure criterion is described in details in the section 2.29.4. This keyword is only
valid if the keyword GEOMECH (see 12.1.99) (option FE) is set in the section RUNSPEC.
The number of values equal to the number of blocks should be specified. The data should
be terminated with a slash /.

Example
DIMENS
64 64 16 /
...
COHESION
72660*900/

12.5.29. COHESION 902

Keywords for formats tN, E1, E3 19.1

12.5.30. THETA

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies the slope of the failure envelope. The Mohr–Coulomb failure
criterion is described in details in the section 2.29.4. This keyword is only valid if the keyword
GEOMECH (see 12.1.99) (option FE) is set in the section RUNSPEC.
The number of values equal to the number of blocks should be specified. The data should
be terminated with a slash /.

Example
DIMENS
64 64 16 /
...
THETA
72660*30/

12.5.30. THETA 903

Keywords for formats tN, E1, E3 19.1

12.5.31. ROCKOPTS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword is used to set options for rock compaction or rock compressibility. The data
should be terminated with a slash /.

The following parameters should be specified:

1. The method of application of the keyword OVERBURD (see 12.5.32) to the pres-
sures (specified via ROCKTAB, see 12.5.21). Two options are possible: PRESSURE
or STRESS.
STRESS option. If the overburden pressure (Poverburden – OVERBURD, see 12.5.32) is
greater than the fluid pressure (Pf luid ) (which is often true), the effective fluid pres-
sure 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.21) will have to be en-
tered with negative pressure values. One can avoid this using STRESS option. Pressure
values in this case can be entered positive: pore volume and transmissibility multipli-
ers 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.32) isn’t used, one should left defaulted this
parameter.
Default: PRESSURE.

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.21) 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.32) should not be used with the STORE
option as the input OVERBURD (see 12.5.32) data will be overwritten and ignored.
If STORE option is used with the keyword ROCK (see 12.5.17) (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 E1 and E3 model formats;
REFFIRST: reference pressure for pore value calculation setting by the first block of the
region.
Default: NOSTORE.

12.5.31. ROCKOPTS 904

Keywords for formats tN, E1, E3 19.1

3. table region to be used: SATNUM, PVTNUM, ROCKNUM.

Default: PVTNUM.

4. this is an E1/E3 compatibility field.

Example 1:
Example
ROCKOPTS STRESS /

Example 2 (pore volume calculation at initial pressure):

Example
ROCKOPTS
1* STORE /
...
ROCK
1* 7E-005 /

12.5.31. ROCKOPTS 905

Keywords for formats tN, E1, E3 19.1

12.5.32. OVERBURD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies rock overburden pressure tables. The keyword can be used if the
number of rock regions is specified (ROCKCOMP, see 12.1.37).
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.37). 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 isn’t present, the overburden pressure is taken to be zero.

STRESS option (the 1-st parameter of the keyword ROCKOPTS, see 12.5.31). If the
overburden pressure (Poverburden – OVERBURD, see 12.5.32) is greater than the fluid pres-
sure (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.21) 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.32. OVERBURD 906

Keywords for formats tN, E1, E3 19.1

12.5.33. DENSITY

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets fluid densities for all PVT regions. Number of strings depends on
number of PVT regions defined in TABDIMS (see 12.1.29).
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.8.4),

Default: 600 kg/m3 = 37.457 lb/ f t 3 .

2. water density (METRIC: kg/m3 , FIELD: lb/ f t 3 ) (this is ρW,SC in 2.8.4),

Default: 999.014 kg/m3 = 62.366 lb/ f t 3 .

3. gas density (METRIC: kg/m3 , FIELD: lb/ f t 3 ) (this is ρG,SC in 2.8.4).

Default: 1 kg/m3 = 0.062428 lb/ f t 3 .

Note. For models in E3 format oil and gas densities are calculated from the equation of
state. Values specified in this keyword are ignored. Water density, specified in this keyword,
is used.

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.33. DENSITY 907

Keywords for formats tN, E1, E3 19.1

12.5.34. GRAVITY

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets fluid densities for all PVT regions. Number of strings depends on
number of PVT regions defined in TABDIMS (see 12.1.29).
The following three parameters are to be specified (terminated with a slash /):

1. oil API gravity,

Default: 45.5.

2. water specific gravity (with reference to pure water),

Default: 1.0.

3. gas gravity (with reference to air).

Default: 0.7773.

Note. For models in E3 format oil and gas densities are calculated from the equation of
state. Values specified in this keyword are ignored. Water gravity, specified in this keyword,
is used.

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.34. GRAVITY 908

Keywords for formats tN, E1, E3 19.1

12.5.35. APIGROUP

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies maximum number of oil PVT tables groups if API tracking option
is used – 2.8.8. The data should be terminated with a slash /.

Example
APIGROUP
3 /

12.5.35. APIGROUP 909

Keywords for formats tN, E1, E3 19.1

12.5.36. PVTOPTS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets the method of PVT properties interpolation (oil and gas viscosity and
formation volume factor). The data should be terminated with a slash /.

Keywords specified PVT properties of water, oil and gas are given in the section 2.8.7.
The following parameters should be specified:

1. Method of oil formation volume factor interpolation BO :

• 1* – default option;
• B – formation volume factor is interpolated itself;
• B1 – reciprocal of formation volume factor is interpolated.

2. Method of oil viscosity interpolation µO :

• 1* – default option;
• MU – viscosity is interpolated itself;
• MU1 – reciprocal of viscosity is interpolated;
• BMU1 – reciprocal of BO µO is interpolated.

3. Method of gas formation volume factor interpolation BG :

• 1* – default option;
• B – formation volume factor is interpolated itself;
• B1 – reciprocal of formation volume factor is interpolated.

4. Method of gas viscosity interpolation µG :

• 1* – default option;
• MU – viscosity is interpolated itself;
• MU1 – reciprocal of viscosity is interpolated;
• BMU1 – reciprocal of BG µG is interpolated.

5. Interpolation approach of oil formation volume factor BO an oil viscosity µO (see the
description of PVTO, see 12.5.4). It is available only for the PVTO (see 12.5.4) table.

• YES – without normalization (see the description of PVTO, see 12.5.4);

12.5.36. PVTOPTS 910

Keywords for formats tN, E1, E3 19.1

• NO – with normalization.

Default: NO.

Default: interpolation method depends on PVT tables that are used (PVTO (see 12.5.4),
PVDO (see 12.5.2) etc.) and input model format (E1, E3, etc.).

Example
PVTOPTS
B1 BMU1 B MU /

12.5.36. PVTOPTS 911

Keywords for formats tN, E1, E3 19.1

12.5.37. DIFFC

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets the fluid diffusion data for each PVT regions in models which use
diffusion option (see keyword DIFFUSE, see 12.1.70). The number of lines should be equal
to the number of PVT regions in the model (2-nd parameter of the keyword TABDIMS,
see 12.1.29). The following parameters should be specified:

1. the oil molecular weight (METRIC: kg/kg-mol ; FIELD: lb/lb-mol );

2. the gas molecular weight (METRIC: kg/kg-mol ; FIELD: lb/lb-mol );

3. the gas-in-gas diffusion coefficient (METRIC: m2 /day; FIELD: f t 2 /day);

4. the oil-in-gas diffusion coefficient (METRIC: m2 /day; FIELD: f t 2 /day);

Default: 3-rd parameter value (the gas-in-gas diffusion coefficient).

5. the gas-in-oil diffusion coefficient (METRIC: m2 /day; FIELD: f t 2 /day);

Default: 3-rd parameter value (the gas-in-gas diffusion coefficient).

6. the oil-in-oil diffusion coefficient (METRIC: m2 /day; FIELD: f t 2 /day);

Default: 5-th parameter value (the gas-in-oil diffusion coefficient).

7. the gas-in-oil diffusion coefficient for cross phase diffusion (METRIC: m2 /day; FIELD:
f t 2 /day);
Default: 0.

8. the oil-in-oil diffusion coefficient for cross phase diffusion (METRIC: m2 /day; FIELD:
f t 2 /day).
Default: 0.

Each data line should be terminated with the symbol /.

Example
DIFFC
100.0 2.317 1.3E-6 1.3E-7 5.5E-7 0.9E-8 4.7E-7 1.2E-8 /
In the example the fluid diffusion data is set for one PVT region.

12.5.37. DIFFC 912

Keywords for formats tN, E1, E3 19.1

12.6. Relative permeabilities and capillary pressures

This section describes keywords used to define relative permeabilities and capillary pressures.
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 perme-
abilities interpolation methods and end point scaling are listed.

12.6. Relative permeabilities and capillary pressures 913

Keywords for formats tN, E1, E3 19.1

12.6.1. SWOF

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies relative permeability tables for all saturation function regions from
TABDIMS (see 12.1.29) 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.11.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 /.

12.6.1. SWOF 914

Keywords for formats tN, E1, E3 19.1

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 915

Keywords for formats tN, E1, E3 19.1

Example
TABDIMS
2 1 2* 1
/
...
SWOF
0.42 0 0.737 0
0.48728 0.000225 0.610213 0
0.55456 0.00438 0.310527 0
0.62184 0.023012 0.072027 0
0.68912 0.069122 0.003178 0
0.7564 0.151 0 0
0.82368 0.267672 0 0
0.89096 0.408671 0 0
0.95824 0.557237 0 0
1 0.645099 0 0
/
0 0 1 0
0.3 0.002 0.81 0
0.4 0.018 0.49 0
0.5 0.05 0.25 0
0.6 0.098 0.09 0
0.7 0.162 0.01 0
1 0.2 0 0
/

This example sets relative permeabilities for a two-phase water-oil system for two satura-
tion function regions.

12.6.1. SWOF 916

Keywords for formats tN, E1, E3 19.1

12.6.2. SGOF

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies relative permeability tables for two-phase gas-oil systems for all
saturation regions from TABDIMS (see 12.1.29).
If water is active phase the keyword SWOF (see 12.6.1) should be specified.

Each table is a 4-column table with the following columns:

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.11.1)

Number of tables depends on number of saturation 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.2. SGOF 917

Keywords for formats tN, E1, E3 19.1

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 918

Keywords for formats tN, E1, E3 19.1

12.6.3. COREYWO

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword approximates relative permeability and capillary pressure functions for
water-oil systems using formulae 2.19, 2.20, 2.21.
The number of lines should be equal to the number of saturation function regions (spec-
ified via TABDIMS, see 12.1.29). The data for each saturation region should be terminated
with a 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;

Default: 0.

2. SWU – maximal water saturation;

Default: 1.

3. SWCR – critical water saturation;

Default: SWCR = SW L .

4. SOWCR – residual oil saturation in the water-oil system;

Default: 0.

5. krOLW = krOW (SW L ) – must be equal to krOG (SGL );

Default: if krOLW and krORW are defaulted, then krOLW = krORW = 1. Otherwise, krOLW
= krORW .

6. krORW = krOW (SWCR ) – must be less or equal to krOLW ;

Default: if krOLW and krORW are defaulted, then krOLW = krORW = 1. Otherwise, krOLW
= krORW .

7. krW R = krW (1 − SOWCR − SGL );

Default: if krW R and krWU are defaulted, then krW R = krWU = 1. Otherwise, krW R =
krWU .

12.6.3. COREYWO 919

Keywords for formats tN, E1, E3 19.1

8. krWU = krW (SWU ), must be greater or equal to krW R ;

Default: if krW R and krWU are defaulted, then krW R = krWU = 1. Otherwise, krW R =
krWU .

9. pcOW = pcOW (SWCR ) oil-water capillary pressure (METRIC: bars, FIELD: psi);
Default: 0.

10. nOW – exponent of krOW curve;

Default: 4.

11. nW – exponent of krW curve;

Default: 4.

12. n p – exponent of pcOW curve; If the value 0 is entered, then capillary pressure will be
taken from tables (SWOF, SGOF, ...), see the note below;
Default: 4.

13. S pcO – point where capillary pressure becomes zero in water-oil system.
Default: -1.

In tNavigator there is a possibility to use Corey (LET) correlation only for

RP and define capillary pressure via a table. In this case one should enter 0
i in parameter 12 (power) of the keyword COREYWO, COREYGO (LETWO,
LETGO) and define tables SWOF, SGOF or other. Values for capillary pres-
sure will be taken from tables and RP will be calculated using Corey (LET)
correlation.

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/

This example sets relative permeability and capillary pressure for a two-phase water-oil
system for two saturation regions.

12.6.3. COREYWO 920

Keywords for formats tN, E1, E3 19.1

12.6.4. COREYGO

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword approximates relative permeability and capillary pressure functions for gas-
oil systems using the formulae 2.25, 2.26, 2.27.
The number of lines should be equal to the number of saturation function regions (spec-
ified via TABDIMS, see 12.1.29). The data for each saturation region should be terminated
with a 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 gas-oil system with points – 2.

The following parameters for each line should be specified:

1. SGL – minimal gas saturation;

Default: 0.

2. SGU – maximal gas saturation;

Default: 1.

3. SGCR – critical gas saturation;

Default: SGCR = SGL .

4. SOGCR – residual oil saturation in the gas-oil system;

Default: 0.

5. krOLG = krOG (SGL ) – must be equal to krOW (SW L );

Default: if krOLG and krORG are defaulted, then krOLG = krORG = 1. Otherwise, krOLG
= krORG .

6. krORG = krOG (SGCR ) – must be less or equal to krOLG ;

Default: if krOLG and krORG are defaulted, then krOLG = krORG = 1. Otherwise, krOLG
= krORG .

7. krGR = krG (1 − SOGCR − SW L );

Default: if krGR and krGU are defaulted, then krGR = krGU = 1. Otherwise, krGR = krGU .

12.6.4. COREYGO 921

Keywords for formats tN, E1, E3 19.1

8. krGU = krG (SGU ), must be greater or equal to krGR ;

Default: if krGR and krGU are defaulted, then krGR = krGU = 1. Otherwise, krGR = krGU .

9. pcOG = pcOG (1 − SOGCR − SW L ) gas-oil capillary pressure (METRIC: bars, FIELD:

psi);
Default: 0.

10. nOG – exponent of krOG curve;

Default: 4.

11. nG – exponent of krG curve;

Default: 4.

12. n pG – exponent of pcOG curve; If the value 0 is entered, then capillary pressure will be
taken from tables (SWOF, SGOF, ...), see the note below;
Default: 4.

13. S pcG – point where capillary pressure becomes zero in gas-oil system.
Default: -1.

In tNavigator there is a possibility to use Corey (LET) correlation only for

RP and define capillary pressure via a table. In this case one should enter 0
i in parameter 12 (power) of the keyword COREYWO, COREYGO (LETWO,
LETGO) and define tables SWOF, SGOF or other. Values for capillary pres-
sure will be taken from tables and RP will be calculated using Corey (LET)
correlation.

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
system for one saturation region.
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/

This example sets relative permeability and capillary pressure for a two-phase gas-oil
system for two saturation regions.

12.6.4. COREYGO 922

Keywords for formats tN, E1, E3 19.1

12.6.5. COREYWG

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword approximates relative permeability and capillary pressure functions for
water-gas systems using formulae 2.31, 2.32, 2.33.
The number of lines should be equal to the number of saturation function regions (spec-
ified via TABDIMS, see 12.1.29). The data for each saturation region should be terminated
with a 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-gas system with points – 3.

The following parameters for each line should be specified:

1. SW L – minimal water saturation;

Default: 0.

2. SWU – maximal water saturation;

Default: 1.

3. SWCR – critical water saturation;

Default: SWCR = SW L .

4. SGCR – critical gas saturation;

Default: SGCR = 1 − SWU (= SGL ).

5. krGU = krG (1 − SW L ), must be greater or equal to krGR ;

Default: if krGU and krGR are defaulted, then krGU = krGR = 1. Otherwise, krGU =
krGR .

6. krGR = krG (1 − SWCR );

Default: if krGU and krGR are defaulted, then krGU = krGR = 1. Otherwise, krGU =
krGR .

7. krW R = krW (1 − SGCR ); must be less or equal to krWU ;

Default: if krW R and krWU are defaulted, then krW R = krWU = 1. Otherwise, krW R =
krWU .

12.6.5. COREYWG 923

Keywords for formats tN, E1, E3 19.1

8. krWU = krW (SWU ), must be greater or equal to krW R ;

Default: if krW R and krWU are defaulted, then krW R = krWU = 1. Otherwise, krW R =
krWU .

9. pcW G = pcW G (SWCR ) water-gas capillary pressure (METRIC: bars, FIELD: psi);
Default: 0.

10. nG – exponent of krG curve;

Default: 4.

11. nW – exponent of krW curve;

Default: 4.

12. n p – exponent of pcW G curve; If the value 0 is entered, then capillary pressure will be
taken from tables (SWOF, SGOF, ...), see the note below;
Default: 4.

13. S pcO – point where capillary pressure becomes zero in water-gas system.
Default: -1.

In tNavigator there is a possibility to use Corey (LET) correlation only for

RP and define capillary pressure via a table. In this case one should enter 0
i in parameter 12 (power) of the keyword COREYWO, COREYGO (LETWO,
LETGO) and define tables SWOF, SGOF or other. Values for capillary pres-
sure will be taken from tables and RP will be calculated using Corey (LET)
correlation.
Note. It is assumed that SGL = 1 − SWU and SGU = 1 − SW L .

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
system for one saturation region.
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
system for two saturation regions.

12.6.5. COREYWG 924

Keywords for formats tN, E1, E3 19.1

12.6.6. COREYWOMOD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword approximates water relative permeability using formulae 2.22, 2.23, 2.24.
These formulae differs from ones which are used by the keyword COREYWO (see 12.6.3).
The following parameters should be specified:

1. YES or NO – to use or not modified Corey correlation formulae.

The data should be terminated with a slash /.

Example
COREYWO
0.05 1 0.15 0.3 0.9 0.7 0.4 0.6 0.11 2 2 2 /

COREYWOMOD
YES /

12.6.6. COREYWOMOD 925

Keywords for formats tN, E1, E3 19.1

12.6.7. COREYGOMOD

Data x tN E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword approximates gas relative permeability using formulae 2.28, 2.29, 2.30.
These formulae are changed from ones which are used by the keyword COREYGO
(see 12.6.4).
The following parameters should be specified:

1. YES or NO – to use or not modified Corey correlation formulae.

The data should be terminated with a slash /.

Example
COREYGO
0.1 0.9 0 0.4 0.9 1* 0.6 0.85 0.22 2 2 2 /

COREYGOMOD
NO /

12.6.7. COREYGOMOD 926

Keywords for formats tN, E1, E3 19.1

12.6.8. LETWO

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword approximates relative permeability and capillary pressure functions for
water-oil systems using formulae 2.34, 2.35.

The number of lines should be equal to the number of saturation function regions (spec-
ified via TABDIMS, see 12.1.29). The data for each saturation region should be terminated
with a 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 following parameters for each line should be specified:

1. SW L – minimal water saturation;

Default: 0.

2. SWU – maximal water saturation;

Default: 1.

3. SWCR – critical water saturation;

Default: SWCR = SW L .

4. SOWCR – residual oil saturation in the water-oil system;

Default: 0.

5. krOLW = krOW (SW L ) – must be equal to krOG (SGL );

Default: if KrOLW and KrORW are defaulted, then KrOLW = KrORW = 1. Otherwise,
KrOLW = KrORW .

6. krORW = krOW (SWCR ) – must be less or equal to krOLW ;

Default: if KrOLW and KrORW are defaulted, then KrOLW = KrORW = 1. Otherwise,
KrOLW = KrORW .

7. krW R = krW (1 − SOWCR − SGL );

Default: if KrW R and KrWU are defaulted, then KrW R = KrWU = 1. Otherwise, KrW R =
KrWU .

12.6.8. LETWO 927

Keywords for formats tN, E1, E3 19.1

8. krWU = krW (SWU ), must be greater or equal to krW R ;

Default: if KrW R and KrWU are defaulted, then KrW R = KrWU = 1. Otherwise, KrW R =
KrWU .
9. pcOW = pcOW (SWCR ) oil-water capillary pressure (METRIC: bars, FIELD: psi);
Default: 0.
10. nOW – exponent of krOW curve; describes the lower part of the curve krOW ;
Default: 4.
11. nW – exponent of krW curve; describes the lower part of the curve krW ;
Default: 4.
12. n p – exponent of pcOW curve; 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;
Default: 4.
13. S pcO – point where capillary pressure becomes zero in water-oil system;
Default: -1.
14. TW – describes the upper part (or the top part) of the curve krW ;
Default: 2.
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;
Default: 1.
16. TOW – describes the upper part (or the top part) of the curve krOW ;
Default: 2.
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: 1.

In tNavigator there is a possibility to use Corey (LET) correlation only for

RP and define capillary pressure via a table. In this case one should enter 0
i in parameter 12 (power) of the keyword COREYWO, COREYGO (LETWO,
LETGO) and define tables SWOF, SGOF or other. Values for capillary pres-
sure will be taken from tables and RP will be calculated using Corey (LET)
correlation.

12.6.8. LETWO 928

Keywords for formats tN, E1, E3 19.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 /

This example sets relative permeability and capillary pressure for a two-phase water-oil
system for one saturation region.

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/

This example sets relative permeability and capillary pressure for a two-phase water-oil
system for two saturation regions.

12.6.8. LETWO 929

Keywords for formats tN, E1, E3 19.1

12.6.9. LETGO

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword approximates relative permeability and capillary pressure functions for gas-
oil systems using the formulae 2.36, 2.37.

The number of lines should be equal to the number of saturation function regions (spec-
ified via TABDIMS, see 12.1.29). The data for each saturation region should be terminated
with a 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 following parameters for each line should be specified:

1. SGL – minimal gas saturation;

Default: 0.

2. SGU – maximal gas saturation;

Default: 1.

3. SGCR – critical gas saturation;

Default: 0.

4. SOGCR – residual oil saturation in the gas-oil system;

Default: 0.

5. krOLG = krOG (SGL ) – must be equal to krOW (SW L );

Default: if KrOLG and KrORG are defaulted, then KrOLG = KrORG = 1. Otherwise,
KrOLG = KrORG .

6. krORG = krOG (SGCR ) – must be less or equal to krOLG ;

Default: if KrOLG and KrORG are defaulted, then KrOLG = KrORG = 1. Otherwise,
KrOLG = KrORG .

7. krGR = krG (1 − SOGCR − SW L );

Default: if KrGR and KrGU are defaulted, then KrGR = KrGU = 1. Otherwise, KrGR =
KrGU .

12.6.9. LETGO 930

Keywords for formats tN, E1, E3 19.1

8. krGU = krG (SGU ), must be greater or equal to krGR ;

Default: if KrGR and KrGU are defaulted, then KrGR = KrGU = 1. Otherwise, KrGR =
KrGU .

9. pcOG = pcOG (1 − SOGCR − SW L ) gas-oil capillary pressure (METRIC: bars, FIELD:

psi);
Default: 0.

10. nOG – exponent of krOG curve; describes the lower part of the curve krOG ;
Default: 4.

11. nG – exponent of krG curve; describes the lower part of the curve krG ;
Default: 4.

12. n pG – exponent of pcOG curve; 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;
Default: 4.

13. S pcG – point where capillary pressure becomes zero in gas-oil system;
Default: -1.

14. TG – describes the upper part (or the top part) of the curve krG ;
Default: 2.

15. EG – describes the position of the slope (or the elevation) of the curve krG . 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: 1.

16. TOG – describes the upper part (or the top part) of the curve krOG ;
Default: 2.

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: 1.

12.6.9. LETGO 931

Keywords for formats tN, E1, E3 19.1

In tNavigator there is a possibility to use Corey (LET) correlation only for

RP and define capillary pressure via a table. In this case one should enter 0
i in parameter 12 (power) of the keyword COREYWO, COREYGO (LETWO,
LETGO) and define tables SWOF, SGOF or other. Values for capillary pres-
sure will be taken from tables and RP will be calculated using Corey (LET)
correlation.

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/

This example sets relative permeability and capillary pressure for a two-phase gas-oil sys-
tem for one saturation region.

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* /

This example sets relative permeability and capillary pressure for a two-phase gas-oil
system for two saturation regions.

12.6.9. LETGO 932

Keywords for formats tN, E1, E3 19.1

12.6.10. LETWG

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword approximates relative permeability and capillary pressure functions for
water-gas systems using formulae 2.38, 2.39.

The number of lines should be equal to the number of saturation function regions (spec-
ified via TABDIMS, see 12.1.29). The data for each saturation region should be terminated
with a 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 following parameters for each line should be specified:

1. SW L – minimal water saturation;

Default: 0.

2. SWU – maximal water saturation;

Default: 1.

3. SWCR – critical water saturation;

Default: SWCR = SW L .

4. SGCR – critical gas saturation;

Default: SGCR = 1 − SWU (= SGL ).

5. krGU = krG (1 − SW L ); should be greater or equal to krGR ;

Default: if krGU and krGR are defaults, then krGU = krGR = 1, otherwise krGU = krGR .

6. krGR = krG (1 − SWCR );

Default: if krGU and krGR are defaults, then krGU = krGR = 1, otherwise krGU = krGR .

7. krW R = krW (1 − SGCR ); should be less or equal to krWU ;

Default: if krWU and krW R are defaults, then krWU = krW R = 1, otherwise krWU = krW R .

8. krWU = krW (SWU ), must be greater or equal to krW R ;

Default: if krWU and krW R are defaults, then krWU = krW R = 1, otherwise krWU = krW R .

12.6.10. LETWG 933

Keywords for formats tN, E1, E3 19.1

9. pcW G = pcW G (SWCR ) – water-gas capillary pressure (METRIC: bars, FIELD: psi);
Default: 0.

10. nG – exponent of krOW curve; describes the lower part of the curve krOW ;
Default: 4.

11. nW – exponent of krW curve; describes the lower part of the curve krW ;
Default: 4.

12. n p – exponent of pcOW curve; 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;
Default: 4.

13. S pcO – point where capillary pressure becomes zero in water-gas system;
Default: -1.

14. TW – describes the upper part (or the top part) of the curve krW ;
Default: 2.

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;
Default: 1.

16. TG – describes the upper part (or the top part) of the curve krG ;
Default: 2.

17. EG – describes the position of the slope (or the elevation) of the curve krG . 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: 1.

In tNavigator there is a possibility to use Corey (LET) correlation only for

RP and define capillary pressure via a table. In this case one should enter 0
i in parameter 12 (power) of the keyword COREYWO, COREYGO (LETWO,
LETGO) and define tables SWOF, SGOF or other. Values for capillary pres-
sure will be taken from tables and RP will be calculated using Corey (LET)
correlation.
Note. It is assumed that SGL = 1 − SWU and SGU = 1 − SW L .

12.6.10. LETWG 934

Keywords for formats tN, E1, E3 19.1

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
system for one saturation region.

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
system for two saturation regions.

12.6.10. LETWG 935

Keywords for formats tN, E1, E3 19.1

12.6.11. SLGOF

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.29). 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.29). 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.11.1)

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.11. SLGOF 936

Keywords for formats tN, E1, E3 19.1

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 937

Keywords for formats tN, E1, E3 19.1

12.6.12. SOF2

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies relative permeability tables for two-phase water-oil systems for
all saturation regions from TABDIMS (see 12.1.29). 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)

Number of tables depends on number of saturation regions defined in TABDIMS. Each

table must be terminated by a slash /.

Default:

• 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.12. SOF2 938

Keywords for formats tN, E1, E3 19.1

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
/

In this example two-phase oil-water relative permeability is specified for one saturation
region.

12.6.12. SOF2 939

Keywords for formats tN, E1, E3 19.1

12.6.13. SWFN

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies oil phase relative permeability tables for all saturation function
regions from TABDIMS (see 12.1.29).

This keyword can be used for two-phase systems gas-water (together with SGFN,
see 12.6.14) as alternative to SGWFN (see 12.6.16). In this case capillary pressure for water-
gas system is taken from the keyword SWFN (see 12.6.13).

Each table is a 3-column table with the following columns:

1. SW (water saturation) (this is argument value for functions below)

2. KRW (water relative permeability) (this is function krW in 2.6)

3. Capillary Pressure (METRIC: bars, FIELD: psi)

• In oil-water and 3-phase systems – POW (oil-water capillary pressure) (this is

function PcOW in 2.11.2)
• In gas-water systems – PGW (gas-water capillary pressure) (this is function PcGW
in 2.11.3)

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 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.13. SWFN 940

Keywords for formats tN, E1, E3 19.1

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 941

Keywords for formats tN, E1, E3 19.1

12.6.14. SGFN

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies gas phase relative permeability tables for all saturation regions from
TABDIMS (see 12.1.29).

This keyword can be used for two-phase systems gas-water (together with SWFN,
see 12.6.13) as alternative to SGWFN (see 12.6.16). In this case capillary pressure for water-
gas system is taken from the keyword SWFN (see 12.6.13).

Each table is a 3-column table with the following columns:

• SG - gas saturation (this is argument value for functions below).

• KRG - gas relative permeability (this is function krG in 2.6). First element of this column
must be zero.

• POG - oil-gas capillary pressure (METRIC: bars, FIELD: psi) (this is function PcGO
in 2.11.1).

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 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.14. SGFN 942

Keywords for formats tN, E1, E3 19.1

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 943

Keywords for formats tN, E1, E3 19.1

12.6.15. SOF3

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies relative permeability tables for three-phase systems for all satura-
tion regions from TABDIMS (see 12.1.29). Each table should be terminated with a slash /.

Allowed combinations of keywords specified relative permeabilities are given in the sec-
tion 2.6.1.

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:

• 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

• 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 /.

The keyword specifies relative permeability tables for two-phase systems – SOF2
(see 12.6.12).

12.6.15. SOF3 944

Keywords for formats tN, E1, E3 19.1

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 945

Keywords for formats tN, E1, E3 19.1

12.6.16. SGWFN

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies relative permeability tables for two-phase gas-water systems for
all saturation regions from TABDIMS. Allowed combinations of keywords specified relative
permeabilities are given in the section 2.6.1.

This keyword can be used for two-phase systems gas-water as alternative to SGFN
(see 12.6.14), SWFN (see 12.6.13).

Each table is a 4-column table with the following columns:

1. SG (gas saturation) (this is argument value for functions below)

2. KRGW (gas relative permeability)

3. KRWG (water relative permeability)

4. PGW (gas-water capillary pressure (METRIC: bars, FIELD: psi))

Number of tables depends on number of saturation 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.16. SGWFN 946

Keywords for formats tN, E1, E3 19.1

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 947

Keywords for formats tN, E1, E3 19.1

12.6.17. SOMWAT

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies minimum oil saturation (used in 3-phase model – First Stone’s
model specified by keyword 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 func-
tion 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 sat-
uration regions defined via 1-st parameter of TABDIMS. Each table must be terminated by a
slash /.

Each 2-column table consists of the following columns:

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 satu-
ration 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 948

Keywords for formats tN, E1, E3 19.1

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 949

Keywords for formats tN, E1, E3 19.1

12.6.18. SOMGAS

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies minimum oil saturation (used in 3-phase model – First Stone’s
model specified by keyword 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 func-
tion 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 sat-
uration regions defined via 1-st parameter of TABDIMS. Each table must be terminated by a
slash /.

Each 2-column table consists of the following columns:

1. gas saturation.
The first value should equal the connate gas saturation in the table SGFN (see 12.6.14)
(usually 0).
The last value should equal 1 − SW c − 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 1 − SOrG − 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 950

Keywords for formats tN, E1, E3 19.1

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 951

Keywords for formats tN, E1, E3 19.1

12.6.19. TOLCRIT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.1.136) (2.6.7).

If TOLCRIT (see 12.6.19) isn’t 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 ∗ 10−6 – in E1 models (krW ≤ 1.0 ∗ 10−20 – in E3 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 ∗ 10−6 – in E1 models, 1.0 ∗ 10−20 – in E3 models.

Example
TOLCRIT
1.0E-9 /

12.6.19. TOLCRIT 952

Keywords for formats tN, E1, E3 19.1

12.6.20. STONE1

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies that Stone 1 model will be used for oil relative permeability calcu-
lation – 2.6.5.

User should specify either STONE1, or STONE2 (see 12.6.21). If none is specified, the
linear Baker’s model will be used – 2.6.4.
Example
STONE1

12.6.20. STONE1 953

Keywords for formats tN, E1, E3 19.1

12.6.21. STONE2

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies that Stone 2 model will be used for oil relative permeability calcu-
lation – 2.6.6.

User should specify either STONE1 (see 12.6.20), or STONE2. If none is specified, the
linear Baker’s model will be used – 2.6.4.
Example
STONE2

12.6.21. STONE2 954

Keywords for formats tN, E1, E3 19.1

12.6.22. STONE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies that Stone 2 model will be used for oil relative permeability calcu-
lation – 2.6.6 (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 Baker’s model will be used – 2.6.4.
Example
STONE

12.6.22. STONE 955

Keywords for formats tN, E1, E3 19.1

12.6.23. STONEPAR

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keywords sets two numbers, A and B. These numbers are parameters of expression for
Som in the first Stone’s model of oil three-phase relative permeability (specified by keyword
STONE1 (see 12.6.20) and described in the section 2.6.5).
Som is mobile oil value 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 .

The following parameters should be specified:

1. parameter A;
Default: 1.

2. parameter B.
Default: 0.

The data should be terminated with a slash /.

Example
STONEPAR
1.0 0.0 /
In the example values of A and B is set to their default values.

12.6.23. STONEPAR 956

Keywords for formats tN, E1, E3 19.1

12.6.24. TZONE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword controls the transition zone option. The keyword can be used only if the
keyword ENDSCALE (see 12.1.136) is active indicating that end point scaling of relative per-
meabilities and capillary pressures will be used. See sections 2.6.7, 2.6.8, 2.11.4 for details.

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.

1. the parameter is set true to oil phase – SOWCR (see 12.6.31) will be modified for oil-
water runs or oil-water-miscible gas runs, SOGCR (see 12.6.32) will be modified only
for oil-gas runs;

2. the parameter is set true to water phase, SWCR (see 12.6.29) will be modified;

3. the parameter is set true to gas phase, SGCR (see 12.6.30) will be modified for gas-water
runs and oil-gas runs.

Example
TZONE
F T T /

12.6.24. TZONE 957

Keywords for formats tN, E1, E3 19.1

12.6.25. SCALECRS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

Keyword may be present in data file, if ENDSCALE (see 12.1.136) is selected. Allows to
define three-point scaling method for saturation tables end point scaling. See 2.6.7, 2.6.8 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.25. SCALECRS 958

Keywords for formats tN, E1, E3 19.1

12.6.26. SWL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword defines minimal water saturation for grid blocks, used for saturation end
point scaling. Keyword may be used only if ENDSCALE (see 12.1.136) is present in data file.
See 2.6.7, 2.6.8, 2.11.4 for details of end point scaling.

The same number of values as number of cells must be specified. The data should be
terminated with a slash /.

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.26. SWL 959

Keywords for formats tN, E1, E3 19.1

12.6.27. SWLPC

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword defines minimal water saturation for grid blocks, used for saturation end
point scaling only for capillary pressure Pc curves without scaling the corresponding oil RP
curves.

Keyword may be used only if ENDSCALE (see 12.1.136) is present in data file. See 2.6.7,
2.6.8, 2.11.4 for details of end point scaling.

The same number of values as number of cells must be specified. The data should be
terminated with a slash /.

Default: if this keyword isn’t specified then the oil-water (or gas-water) capillary pressure
scaling is done via the connate water saturation specified with the keyword SWL (see 12.6.26).

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
0.23 for last 5000 blocks.

12.6.27. SWLPC 960

Keywords for formats tN, E1, E3 19.1

12.6.28. SGL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword defines minimal gas saturation for grid blocks, used for saturation end point
scaling. Keyword may be used only if ENDSCALE (see 12.1.136) is present in data file. See
2.6.7, 2.6.8, 2.11.4 for details of end point scaling.

The same number of values as number of cells must be specified. The data should be
terminated with a slash /.

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 0.45
for last 50 blocks.

12.6.28. SGL 961

Keywords for formats tN, E1, E3 19.1

12.6.29. SWCR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword defines critical water saturation for grid blocks, used for saturation end point
scaling. Keyword may be used only if ENDSCALE (see 12.1.136) is present in data file. See
2.6.7, 2.6.8, 2.11.4 for details of end point scaling.

The same number of values as number of cells must be specified. The data should be
terminated with a slash /.

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
0.45 for last 50 blocks.

12.6.29. SWCR 962

Keywords for formats tN, E1, E3 19.1

12.6.30. SGCR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword defines critical gas saturation for grid blocks, used for saturation end point
scaling. Keyword may be used only if ENDSCALE (see 12.1.136) is present in data file. See
2.6.7, 2.6.8, 2.11.4 for details of end point scaling.

The same number of values as number of cells must be specified. The data should be
terminated with a slash /.

Default: critical gas saturations in corresponding saturation region, i.e. maximal gas satu-
ration 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.30. SGCR 963

Keywords for formats tN, E1, E3 19.1

12.6.31. SOWCR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.1.136) is present in data
file. See 2.6.7, 2.6.8, 2.11.4 for details of end point scaling.

The same number of values as number of cells must be specified. The data should be
terminated with a slash /.

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.31. SOWCR 964

Keywords for formats tN, E1, E3 19.1

12.6.32. SOGCR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword defines critical oil-to-gas saturation for grid blocks, used for saturation end
point scaling. Keyword may be used only if ENDSCALE (see 12.1.136) is present in data file.
See 2.6.7, 2.6.8, 2.11.4 for details of end point scaling.

The same number of values as number of cells must be specified. The data should be
terminated with a slash /.

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.32. SOGCR 965

Keywords for formats tN, E1, E3 19.1

12.6.33. SWU

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword defines maximal water saturation for grid blocks, used for saturation end
point scaling. Keyword may be used only if ENDSCALE (see 12.1.136) is present in data file.
See 2.6.7, 2.6.8, 2.11.4 for details of end point scaling.

The same number of values as number of cells must be specified. The data should be
terminated with a slash /.

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
0.85 for last 50 blocks.

12.6.33. SWU 966

Keywords for formats tN, E1, E3 19.1

12.6.34. SGU

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword defines maximal gas saturation for grid blocks, used for saturation end point
scaling. Keyword may be used only if ENDSCALE (see 12.1.136) is present in data file. See
2.6.7, 2.6.8, 2.11.4 for details of end point scaling.

The same number of values as number of cells must be specified. The data should be
terminated with a slash /.

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
0.85 for last 50 blocks.

12.6.34. SGU 967

Keywords for formats tN, E1, E3 19.1

12.6.35. ISGL, ISGCR, ISGU, ISWL, ISWLPC, ISWCR, ISWU, ISOGCR, ISOWCR

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

These keywords are used in scaling the imbibition saturation table (hysteresis option de-
scription – 2.7):

• ISGL – minimal (connate) gas saturation (for drainage process this value is specified via
the keyword SGL, see 12.6.28);

• ISGCR – critical gas saturation (for drainage process this value is specified via the
keyword SGCR, see 12.6.30);

• ISGU – maximal gas saturation (for drainage process this value is specified via the
keyword SGU, see 12.6.34);

• ISWL – minimal (connate) water saturation (for drainage process this value is specified
via the keyword SWL, see 12.6.26);

• ISWLPC – 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.27);

• ISWCR – critical water saturation (for drainage process this value is specified via the
keyword SWCR, see 12.6.29);

• ISWU – maximal water saturation (for drainage process this value is specified via the
keyword SWU, see 12.6.33);

• ISOGCR – critical oil saturation in oil-gas system (for drainage process this value is
specified via the keyword SOGCR, see 12.6.32);

• ISOWCR – critical oil saturation in oil-water system (for drainage process this value is
specified via the keyword SOWCR, see 12.6.31).

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.1.136) and SATOPTS
(see 12.1.75) are present.

12.6.35. ISGL, ISGCR, ISGU, ISWL, ISWLPC, ISWCR, ISWU, ISOGCR, ISOWCR 968
Keywords for formats tN, E1, E3 19.1

12.6.36. SCALELIM

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.1.136). 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.36. SCALELIM 969

Keywords for formats tN, E1, E3 19.1

12.6.37. ENPTVD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies saturation end point versus depth tables. See for details the section
2.6.7. The number of tables should not be greater then 3-rd parameter of the keyword END-
SCALE (see 12.1.136). 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.26) 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.29) 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.33) 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.28) 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.30) 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.34) 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.31) 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.32) can be used).

Each saturation entry (parameters 2-9) should be in the range 0.0 to 1.0 inclusive.

12.6.37. ENPTVD 970

Keywords for formats tN, E1, E3 19.1

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.37. ENPTVD 971

Keywords for formats tN, E1, E3 19.1

12.6.38. ENKRVD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies relative permeability end point versus depth tables. See for details
the section 2.6.7. The number of tables should not be greater then 3-rd parameter of the key-
word ENDSCALE (see 12.1.136). 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 maximum water relative permeability (if relative permeabil-
ities are entered cell by cell – the keyword KRW (see 12.6.59) 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.60) 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.58) 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.59) 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.60) can be used);
7. oil relative permeability at the critical gas saturation (if relative permeabilities are en-
tered cell by cell – the keyword KRORG (see 12.6.58) 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.58) 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 /

In this example one table is specified.

12.6.38. ENKRVD 972

Keywords for formats tN, E1, E3 19.1

12.6.39. ENPCVD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies maximum capillary pressure versus depth tables. See for details the
section 2.11.4. The number of tables should not be greater then 3-rd parameter of the keyword
ENDSCALE (see 12.1.136). 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 maximum gas-oil capillary pressure (if capillary pressures
are entered cell by cell – the keyword PCG (see 12.6.63) 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.62) 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 /

In this example one table is specified.

12.6.39. ENPCVD 973

Keywords for formats tN, E1, E3 19.1

12.6.40. ENPTRC

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies the phase relative permeability end points dependent on the con-
centration of tracer (salt, surfactant, polymer).
For more details on surfactants, see section 2.23. These chemical agents are
injected to the formation as an admixture to the phase (water in case of sur-
factants, or oil in case of solvents), and change the oil-water surface tension.
i In tNavigator the effect of admixture (surfactants, salts, any other tracers)
on fluid permeation behavior is simulated by altering saturation end points
(ENPTRC, ENPTRCM, see 12.6.43), relative phase permeabilities (ENPKTRC
(see 12.6.41), ENPKTRCM, see 12.6.44), and capillary pressures (ENPCTRC
(see 12.6.42), ENPCTRCM, see 12.6.45).

!
To specify the option of combining permeability specifications which are de-
pendent on the concentration of tracer (salt, surfactant) with those indepen-
dent on it, set the 5th parameter of ENDSCALE (see 12.1.136) to 2.
Each table should be terminated with a slash /.
The number of tables is equal to the number of end point scaling of relative permeability
regions.
The tables contain the following parameters:
1. tracer name (for salts – SALT, for surfactants – SURFACTANT, for polymers – POLY-
MER);
2. one of 8 saturation end points: SWL (see 12.6.26), SWCR (see 12.6.29), SWU
(see 12.6.33), SGL (see 12.6.28), SGCR (see 12.6.30), SGU (see 12.6.34), SOWCR
(see 12.6.31), SOGCR (see 12.6.32).
Then the table should be entered, one table row contains parameters:
1. admixture concentration (in case of tracer, dimensionless value from 0 to 1; in case of
salts, surfactants, polymers, METRIC: kg/sm3 , FIELD: lb/stb);
2. the value of the corresponding end point.
Example
ENPTRC
SURFACTANT SOWCR
0.0 0.2
100.0 0.15 /

12.6.40. ENPTRC 974

Keywords for formats tN, E1, E3 19.1

In this example there is one table for surfactant and SOWCR. When surfactant concentra-
tion 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.40. ENPTRC 975

Keywords for formats tN, E1, E3 19.1

12.6.41. ENPKTRC

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies the phase relative permeabilities dependent on the concentration of
tracer (salt, surfactant, polymer).
For more details on surfactants, see section 2.23. These chemical agents
i are injected to the formation as an admixture to the phase (water in case
of surfactants, or oil in case of solvents), and change the oil-water surface
tension.

!
To specify the option of combining permeability specifications which are de-
pendent on the concentration of tracer (salt, surfactant) with those indepen-
dent on it, set the 5th parameter of ENDSCALE (see 12.1.136) to 2.
Each table should be terminated with a slash /.
The number of tables is equal to the number of end point scaling of relative permeability
regions.
The tables contain the following parameters:

1. tracer name (for salts – SALT, for surfactants – SURFACTANT, for polymers – POLY-
MER);

2. one of 7 permeabilities: KRW (see 12.6.59), KRG (see 12.6.60), KRO (see 12.6.58),
KRWR (see 12.6.59), KRGR (see 12.6.60), KRORG (see 12.6.58), KRORW (see 12.6.58).

Then the table should be entered, one table row contains parameters:

1. admixture concentration (in case of tracer, dimensionless value from 0 to 1; in case of

salts, surfactants, polymers, METRIC: kg/sm3 , FIELD: lb/stb);

2. the value of the corresponding permeability.

Example
ENPKTRC
TRACERWAT1 KRW
0.0 0.8
0.1 0.85
0.2 0.9 /
In this example the maximum phase permeability of water (KRW) is specified as dependent
on tracer concentration.

12.6.41. ENPKTRC 976

Keywords for formats tN, E1, E3 19.1

12.6.42. ENPCTRC

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies the capillary pressures dependent on the concentration of tracer
(salt, surfactant, polymer).
For more details on surfactants, see section 2.23. These chemical agents
i are injected to the formation as an admixture to the phase (water in case
of surfactants, or oil in case of solvents), and change the oil-water surface
tension.

!
To specify the option of combining permeability specifications which are de-
pendent on the concentration of tracer (salt, surfactant) with those indepen-
dent on it, set the 5th parameter of ENDSCALE (see 12.1.136) to 2.
Each table should be terminated with a slash /.
The number of tables is equal to the number of end point scaling of relative permeability
regions.
The tables contain the following parameters:

1. tracer name (for salts – SALT, for surfactants – SURFACTANT, for polymers – POLY-
MER);

2. one of 2 capillary pressures: PCG (see 12.6.63), PCW (see 12.6.62).

Then the table should be entered, one table row contains parameters:

1. admixture concentration (in case of tracer, dimensionless value from 0 to 1; in case of

salts, surfactants, polymers, METRIC: kg/sm3 , FIELD: lb/stb);

2. the value of the corresponding capillary pressure.

Example
ENPCTRC
SURFACTANT PCW
0.0 3.0
50. 2.1
100. 1.6 /
In this example the maximum water-oil capillary pressure (PCW) is specified as dependent
on surfactant concentration.

12.6.42. ENPCTRC 977

Keywords for formats tN, E1, E3 19.1

12.6.43. ENPTRCM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies the multipliers for phase relative permeability end points dependent
on the concentration of tracer (salt, surfactant, polymer).
For more details on surfactants, see section 2.23. These chemical agents
i are injected to the formation as an admixture to the phase (water in case
of surfactants, or oil in case of solvents), and change the oil-water surface
tension.
Each table should be terminated with a slash /.
The number of tables is equal to the number of end point scaling of relative permeability
regions.
The tables contain the following parameters:

1. tracer name (for salts – SALT, for surfactants – SURFACTANT, for polymers – POLY-
MER);

2. one of 8 saturation end points: SWL (see 12.6.26), SWCR (see 12.6.29), SWU
(see 12.6.33), SGL (see 12.6.28), SGCR (see 12.6.30), SGU (see 12.6.34), SOWCR
(see 12.6.31), SOGCR (see 12.6.32).

Then the table should be entered, one table row contains parameters:

1. admixture concentration (in case of tracer, dimensionless value from 0 to 1; in case of

salts, surfactants, polymers, METRIC: kg/sm3 , FIELD: lb/stb);

2. the value of the corresponding multiplier.

Example
ENPTRCM
SURFACTANT SOWCR
0.0 1.0
100.0 0.75 /
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 point multiplier for SOWCR is
0.75.

12.6.43. ENPTRCM 978

Keywords for formats tN, E1, E3 19.1

12.6.44. ENPKTRCM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies the phase relative permeability multipliers dependent on the con-
centration of tracer (salt, surfactant, polymer).
For more details on surfactants, see section 2.23. These chemical agents
i are injected to the formation as an admixture to the phase (water in case
of surfactants, or oil in case of solvents), and change the oil-water surface
tension.
Each table should be terminated with a slash /.
The number of tables is equal to the number of end point scaling of relative permeability
regions.
The tables contain the following parameters:

1. tracer name (for salts – SALT, for surfactants – SURFACTANT, for polymers – POLY-
MER);

2. one of 7 permeabilities: KRW (see 12.6.59), KRG (see 12.6.60), KRO (see 12.6.58),
KRWR (see 12.6.59), KRGR (see 12.6.60), KRORG (see 12.6.58), KRORW (see 12.6.58).

Then the table should be entered, one table row contains parameters:

1. admixture concentration (in case of tracer, dimensionless value from 0 to 1; in case of

salts, surfactants, polymers, METRIC: kg/sm3 , FIELD: lb/stb);

2. the value of the corresponding multiplier.

Example
ENPKTRCM
TRACERWAT1 KRW
0.0 1.0
0.1 1.05
0.2 1.1 /
In this example the multipliers for maximum phase permeability of water (KRW) is speci-
fied as dependent on tracer concentration.

12.6.44. ENPKTRCM 979

Keywords for formats tN, E1, E3 19.1

12.6.45. ENPCTRCM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies the capillary pressure multipliers dependent on the concentration
of tracer (salt, surfactant, polymer).
For more details on surfactants, see section 2.23. These chemical agents
i are injected to the formation as an admixture to the phase (water in case
of surfactants, or oil in case of solvents), and change the oil-water surface
tension.
Each table should be terminated with a slash /.
The number of tables is equal to the number of end point scaling of relative permeability
regions.
The tables contain the following parameters:

1. tracer name (for salts – SALT, for surfactants – SURFACTANT, for polymers – POLY-
MER);

2. one of 2 capillary pressures: PCG (see 12.6.63), PCW (see 12.6.62).

Then the table should be entered, one table row contains parameters:

1. admixture concentration (in case of tracer, dimensionless value from 0 to 1; in case of

salts, surfactants, polymers, METRIC: kg/sm3 , FIELD: lb/stb);

2. the value of the corresponding multiplier.

Example
ENPCTRCM
SURFACTANT PCW
0.0 1.0
50. 0.7
100. 0.55 /
In this example the multiplier for maximum water-oil capillary pressure (PCW) is specified
as dependent on surfactant concentration.

12.6.45. ENPCTRCM 980

Keywords for formats tN, E1, E3 19.1

12.6.46. LSWL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword allows to specify the connate water saturation (i.e., the smallest water satura-
tion in a water saturation function table) in each grid block, which can be used for scaling the
(oil-wet) oil-water capillary pressure and oil relative permeability to water tables in modelling
water with low salinity. The keyword LSWL can be implemented if water is present in the
model and keywords ENDSCALE (see 12.1.136) (the end–point scaling methods are described
in 2.6.7, 2.6.8, 2.11.4) and LOWSALT (see 12.1.63) (the low salinity option is decribed in
2.24.3) are specified.
The tabulated oil-water capillary pressure functions are scaled linearly between the connate
water saturation specified with LSWL keyword and the maximum water saturation specified
with LSWU (see 12.6.48). LSWL can be used for scaling the oil relative permeability curves.
If the connate water saturation was additionally specified with the keyword LSWLPC
(see 12.6.47), then the end–point corresponding to this saturation will be used for scaling the
oil-water capillary pressure curves. In this case the connate water saturation specified with
LSWL will only be used to scale the oil relative permeability curves.
The keyword is followed by one real number (the connate water saturation) for each grid
block. The saturation value can vary from 0 to 1 inclusive. The data should be terminated
with a slash /.
Grid blocks are in the following order: index cycles first along X-axis, then along the Y-
and Z-axis indices. Repeat counts may be used for repeated values (e.g., 64*0.19).
If the keyword LSWL is not specified for some or all of the grid blocks in a model, the
connate water saturations for calculations of low salinity (oil-wet) oil relative permeability
and capillary pressure will be taken by default from appropriate relative permeability tables.
Example
DIMENS
4 4 4 /
ENDSCALE
/
BRINE
LOWSALT
...
LSWL
64*0.1/

In this example the connate water saturation is set equal to 0.1 in each grid blocks.

12.6.46. LSWL 981

Keywords for formats tN, E1, E3 19.1

12.6.47. LSWLPC

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword allows to specify the connate water saturation (i.e., the smallest water satu-
ration in a water saturation function table) in each grid block, which can be used for scaling
the (oil-wet) oil-water capillary pressure tables in modelling water with low salinity. The
keyword LSWLPC can be implemented if water is present in the model and keywords END-
SCALE (see 12.1.136) (the end–point scaling methods are described in 2.6.7, 2.6.8, 2.11.4)
and LOWSALT (see 12.1.63) (the low salinity option is decribed in 2.24.3) are specified.
The tabulated oil-water capillary pressure functions are scaled linearly between the connate
water saturation specified with LSWLPC keyword and the maximum water saturation specified
with LSWU (see 12.6.48). LSWLPC can not be used for scaling the oil relative permeability
curves.
The keyword is followed by one real number (the connate water saturation) for each grid
block. The saturation value can vary from 0 to 1 inclusive. The data should be terminated
with a slash /.
Grid blocks are in the following order: index cycles first along X-axis, then along the Y-
and Z-axis indices. Repeat counts may be used for repeated values (e.g., 64*0.9).
If the keyword LSWLPC is not specified for some or all of the grid blocks in a model, the
connate water saturations for calculations of low salinity (oil-wet) water-oil capillary pressure
will be specified with the keyword LSWL (see 12.6.46) by default.
Example
DIMENS
4 4 4 /
ENDSCALE
/
BRINE
LOWSALT
...
LSWLPC
64*0.9/

In this example the connate water saturation is set equal to 0.9 in each grid blocks.

12.6.47. LSWLPC 982

Keywords for formats tN, E1, E3 19.1

12.6.48. LSWU

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword allows to specify the maximum water saturation (i.e., the highest water
saturation in a water saturation function table) in each grid block, which can be used for
scaling the (oil-wet) oil-water capillary pressure and water relative permeability saturation
tables in modelling water with low salinity. The keyword LSWU can be implemented if
water is present in the model and keywords ENDSCALE (see 12.1.136) (the end–point scaling
methods are described in 2.6.7, 2.6.8, 2.11.4) and LOWSALT (see 12.1.63) (the low salinity
option is decribed in 2.24.3) are specified.
The maximum water saturation is used for scaling both the oil-water capillary pressure
and water relative permeability curves. The tabulated oil-water capillary pressure functions
are scaled linearly between the connate water saturation specified with LSWL (see 12.6.46) or
LSWLPC (see 12.6.47) keyword and the maximum water saturation specified with LSWU. The
tabulated water relative permeability curves are scaled between the critical water saturation
specified with LSWCR (see 12.6.52) and the maximum water saturation specified with LSWU
(see 12.6.48).
The keyword LSWU is followed by one real number (the maximum water saturation) for
each grid block. The saturation value can vary from 0 to 1 inclusive. The data should be
terminated with a slash /.
Grid blocks are in the following order: index cycles first along X-axis, then along the Y-
and Z-axis indices. Repeat counts may be used for repeated values (e.g., 64*0.8).
If the keyword LSWU is not specified for some or all of the grid blocks in a model, the
maximum water saturations for calculations of low salinity water relative permeability and
capillary pressure will be taken by default from appropriate relative permeability tables.
Example
DIMENS
4 4 4 /
ENDSCALE
/
BRINE
LOWSALT
...
LSWU
64*0.8/

In this example the maximum water saturation is set equal to 0.8 in each grid block.

12.6.48. LSWU 983

Keywords for formats tN, E1, E3 19.1

12.6.49. LPCW

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keywords allows to specify the maximum value of oil-water capillary pressure (MET-
RIC: bars, FIELD: psi) in each grid block, which can be used for scaling the (oil-wet) water-oil
capillary pressure saturation tables in modelling water with low salinity.
The keyword LPCW can be implemented if water and oil are present in the model and
keywords ENDSCALE (see 12.1.136) (the end–point scaling methods are described in 2.6.7,
2.6.8, 2.11.4) and LOWSALT (see 12.1.63) (the low salinity option is decribed in 2.24.3) are
specified.
The keyword LPCW is followed by one real number (the maximum value of capillary
pressure) for each grid block. The data should be terminated with a slash /.
Grid blocks are in the following order: index cycles first along X-axis, then along the Y-
and Z-axis indices. Repeat counts may be used for repeated values (e.g., 64*1.0).
If the keyword LPCW is not specified for some or all of the grid blocks in a model, the
maximum oil-water capillary pressure at connate water saturation will be taken by default
from appropriate capillary pressure tables.
The keyword LPCW should not be used along with the J-function option specified with
keywords JFUNC (see 12.2.63) or JFUNCR (see 12.2.64) since the J-function calculation is
used for scaling the water capillary pressure and any values specified by the LPCW will be
ignored.
The values specified with LPCW and used for oil-water capillary pressure scaling should
be consistent with the capillary pressure values in the tables. In particular both values should
have the same sign.
Example
DIMENS
4 4 4 /
ENDSCALE
/
BRINE
LOWSALT
...
LPCW
64*1.0/

In this example the maximum value of oil-water capillary pressure is set equal to 1.

12.6.49. LPCW 984

Keywords for formats tN, E1, E3 19.1

12.6.50. LSOGCR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword allows to specify the critical oil in gas saturation (i.e., the highest oil satu-
ration at which the oil relative permeability to gas is zero) in each grid block, which can be
used for scaling the (oil–wet) oil relative permeability to gas saturation tables in modelling
water with low salinity. The keyword LSOGCR can be implemented if gas is present in the
model and keywords ENDSCALE (see 12.1.136) (the end–point scaling methods are described
in 2.6.7, 2.6.8, 2.11.4) and LOWSALT (see 12.1.63) (the low salinity option is decribed in
2.24.3) are specified.
The tabulated oil relative permeability to gas functions are scaled between the critical oil
in gas saturation specified with LSOGCR and the maximum oil saturation defined in terms of
the minimum water and gas saturations (keywords LSWL (see 12.6.46) and SGL (see 12.6.28),
respectively).
The keyword LSOGCR is followed by one real number (the critical oil in gas saturation)
for each grid block. The saturation value can vary from 0 to 1 inclusive. The data should be
terminated with a slash /.
Grid blocks are in the following order: index cycles first along X-axis, then along the Y-
and Z-axis indices. Repeat counts may be used for repeated values (e.g., 64*0.1).
If the keyword LSOGCR is not specified for some or all of the grid blocks in a model, the
critical oil in gas saturations for calculations of low salinity oil relative permeability to gas
will be taken by default from appropriate relative permeability tables.
Example
DIMENS
4 4 4 /
ENDSCALE
/
BRINE
LOWSALT
...
LSOGCR
64*0.1/

In this example the critical oil in gas saturation is set equal to 0.1 in each grid block.

12.6.50. LSOGCR 985

Keywords for formats tN, E1, E3 19.1

12.6.51. LSOWCR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword allows to specify the critical oil in water saturation (i.e., the highest oil
saturation at which the oil relative permeability to water is zero) in each grid block, which
can be used for scaling the (oil–wet) oil relative permeability to water saturation tables in
modelling water with low salinity. The keyword LSOWCR can be implemented if water is
present in the model and keywords ENDSCALE (see 12.1.136) (the end–point scaling methods
are described in 2.6.7, 2.6.8, 2.11.4) and LOWSALT (see 12.1.63) (the low salinity option is
decribed in 2.24.3) are specified.
The tabulated oil relative permeability to water functions are scaled between the critical
oil in water saturation specified with LSOWCR and the maximum oil saturation defined in
terms of the minimum water and gas saturations (keywords LSWL (see 12.6.46) and SGL
(see 12.6.28), respectively).
The keyword LSOWCR is followed by one real number (the critical oil in water saturation)
for each grid block. The saturation value can vary from 0 to 1 inclusive. The data should be
terminated with a slash /.
Grid blocks are in the following order: index cycles first along X-axis, then along the Y-
and Z-axis indices. Repeat counts may be used for repeated values (e.g., 64*0.4).
If the keyword LSOWCR is not specified for some or all of the grid blocks in a model,
the critical oil in water saturations for calculations of low salinity oil relative permeability to
water will be taken by default from appropriate relative permeability tables.
Example
DIMENS
4 4 4 /
ENDSCALE
/
BRINE
LOWSALT
...
LSOWCR
64*0.4/

In this example the critical oil in water saturation is set equal to 0.4 in each grid block.

12.6.51. LSOWCR 986

Keywords for formats tN, E1, E3 19.1

12.6.52. LSWCR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword allows to specify the critical water saturation (i.e., the highest water sat-
uration at which the water relative permeability is equal to zero) in each grid block, which
can be used for scaling the (oil–wet) water relative permeability saturation tables in modelling
water with low salinity. The keyword LSWCR can be implemented if water is present in the
model and keywords ENDSCALE (see 12.1.136) (the end–point scaling methods are described
in 2.6.7, 2.6.8, 2.11.4) and LOWSALT (see 12.1.63) (the low salinity option is decribed in
2.24.3) are specified.
The tabulated water relative permeability functions are scaled between the critical water
saturation specified with LSWCR and the maximum water saturation specified with keywords
LSWU (see 12.6.48).
The keyword LSWCR is followed by one real number (the critical water saturation) for
each grid block. The saturation value can vary from 0 to 1 inclusive. The data should be
terminated with a slash /.
Grid blocks are in the following order: index cycles first along X-axis, then along the Y-
and Z-axis indices. Repeat counts may be used for repeated values (e.g., 64*0.3).
If the keyword LSWCR is not specified for some or all of the grid blocks in a model, the
critical water saturations for calculations of the low salinity water relative permeability will
be taken by default from appropriate relative permeability tables.
Example
DIMENS
4 4 4 /
ENDSCALE
/
BRINE
LOWSALT
...
LSWCR
64*0.3/

In this example the critical water saturation is set equal to 0.3 in each grid block.

12.6.52. LSWCR 987

Keywords for formats tN, E1, E3 19.1

12.6.53. LKRW

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword allows to specify the value of water relative permeability at the maximum
water saturation in each grid block, which can be used for scaling the (oil–wet) water relative
permeability saturation tables in modelling water with low salinity. The keyword LKRW can
be implemented if water is present in the model and keywords ENDSCALE (see 12.1.136) (the
end–point scaling methods are described in 2.6.7, 2.6.8, 2.11.4) and LOWSALT (see 12.1.63)
(the low salinity option is decribed in 2.24.3) are specified.
The keyword LKRW is followed by one real number (the value of water relative perme-
ability at the maximum water saturation) for each grid block. The data should be terminated
with a slash /.
Grid blocks are in the following order: index cycles first along X-axis, then along the Y-
and Z-axis indices. Repeat counts may be used for repeated values (e.g., 64*0.4).
If the keyword LKRW is not specified for some or all of the grid blocks in a model, water
relative permeabilities at maximum water saturation will be taken by default from appropriate
relative permeability tables.
Example
DIMENS
4 4 4 /
ENDSCALE
/
BRINE
LOWSALT
...
LKRW
64*0.4/

In this example the value of water relative permeability at the maximum water saturation
is set equal to 0.4 in each grid block.

12.6.53. LKRW 988

Keywords for formats tN, E1, E3 19.1

12.6.54. LKRWR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword allows to specify the value of water relative permeability at the critical
oil saturation in each grid block, which can be used for scaling the (oil–wet) water relative
permeability saturation tables in modelling water with low salinity. The keyword LKRWR can
be implemented if water is present in the model and keywords ENDSCALE (see 12.1.136) (the
end–point scaling methods are described in 2.6.7, 2.6.8, 2.11.4) and LOWSALT (see 12.1.63)
(the low salinity option is decribed in 2.24.3) are specified.
The keyword LKRWR is followed by one real number (the value of water relative perme-
ability at the critical oil saturation) for each grid block. The data should be terminated with a
slash /.
Grid blocks are in the following order: index cycles first along X-axis, then along the Y-
and Z-axis indices. Repeat counts may be used for repeated values (e.g., 64*0.2).
If the keyword LKRWR is not specified for some or all of the grid blocks in a model,
water relative permeabilities at critical oil saturation will be taken by default from appropriate
relative permeability tables.
Example
DIMENS
4 4 4 /
ENDSCALE
/
BRINE
LOWSALT
...
LKRWR
64*0.2/

In this example the value of water relative permeability at the critical oil saturation is set
equal to 0.2 in each grid block.

12.6.54. LKRWR 989

Keywords for formats tN, E1, E3 19.1

12.6.55. LKRO

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword allows to specify the value of oil relative permeability at the maximum
oil saturation in each grid block, which can be used for scaling the (oil–wet) oil relative
permeability saturation tables in modelling water with low salinity. The keyword LKRO can
be implemented if oil is present in the model and keywords ENDSCALE (see 12.1.136) (the
end–point scaling methods are described in 2.6.7, 2.6.8, 2.11.4) and LOWSALT (see 12.1.63)
(the low salinity option is decribed in 2.24.3) are specified.
The keyword LKRO is followed by one real number (the maximum oil relative permeabil-
ity) for each grid block. The data should be terminated with a slash /.
Grid blocks are in the following order: index cycles first along X-axis, then along the Y-
and Z-axis indices. Repeat counts may be used for repeated values (e.g., 64*0.8).
If the keyword LKRO is not specified for some or all of the grid blocks in a model, oil
relative permeabilities at maximum oil saturation will be taken by default from appropriate
relative permeability tables.
Example
DIMENS
4 4 4 /
ENDSCALE
/
BRINE
LOWSALT
...
LKRO
64*0.8/

In this example the value of oil relative permeability at the maximum oil saturation is set
equal to 0.8 in each grid block.

12.6.55. LKRO 990

Keywords for formats tN, E1, E3 19.1

12.6.56. LKRORW

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword allows to specify the value of oil relative permeability at the critical wa-
ter saturation in each grid block, which can be used for scaling the (oil–wet) oil relative
permeability saturation tables in modelling water with low salinity. The keyword LKRORW
can be implemented if oil and water are present in the model and keywords ENDSCALE
(see 12.1.136) (the end–point scaling methods are described in 2.6.7, 2.6.8, 2.11.4) and
LOWSALT (see 12.1.63) (the low salinity option is decribed in 2.24.3) are specified.
The keyword LKRORW is followed by one real number (the value of oil relative perme-
ability at the critical water saturation) for each grid block. The data should be terminated with
a slash /.
Grid blocks are in the following order: index cycles first along X-axis, then along the Y-
and Z-axis indices. Repeat counts may be used for repeated values (e.g., 64*0.5).
If the keyword LKRORW is not specified for some or all of the grid blocks in a model,
oil relative permeabilities at critical water saturation will be taken by default from appropriate
relative permeability tables.
Example
DIMENS
4 4 4 /
ENDSCALE
/
BRINE
LOWSALT
...
LKRORW
64*0.5/

In this example the value of oil relative permeability at the critical water saturation is set
equal to 0.5 in each grid block.

12.6.56. LKRORW 991

Keywords for formats tN, E1, E3 19.1

12.6.57. LKRORG

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword allows to specify the value of oil relative permeability at the critical gas sat-
uration in each grid block, which can be used for scaling the (oil–wet) oil relative permeability
saturation tables in modelling water with low salinity. The keyword LKRORG can be imple-
mented if oil and water are present in the model and keywords ENDSCALE (see 12.1.136) (the
end–point scaling methods are described in 2.6.7, 2.6.8, 2.11.4) and LOWSALT (see 12.1.63)
(the low salinity option is decribed in 2.24.3) are specified.
The keyword LKRORG is followed by one real number (the value of oil relative perme-
ability at the critical gas saturation) for each grid block. The data should be terminated with a
slash /.
Grid blocks are in the following order: index cycles first along X-axis, then along the Y-
and Z-axis indices. Repeat counts may be used for repeated values (e.g., 64*0.5).
If the keyword LKRORG is not specified for some or all of the grid blocks in a model,
oil relative permeabilities at critical gas saturation will be taken by default from appropriate
relative permeability tables.
Example
DIMENS
4 4 4 /
ENDSCALE
/
BRINE
LOWSALT
...
LKRORG
64*0.5/

In this example the value of oil relative permeability at the critical gas saturation is set
equal to 0.5 in each grid block.

12.6.57. LKRORG 992

Keywords for formats tN, E1, E3 19.1

12.6.58. KRO, KRORW, KRORG

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.

The values should be specified for all grid blocks, they will be used for saturation end
point scaling.

Keywords may be used only if ENDSCALE (see 12.1.136) is present in data file. See 2.6.7,
2.6.8 for details of end point scaling.

The same number of values as number of cells must be specified. The data should be
terminated with a slash /.

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.58. KRO, KRORW, KRORG 993

Keywords for formats tN, E1, E3 19.1

12.6.59. KRW, KRWR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

These keywords define:

• 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.47).

The values should be specified for all grid blocks, they will be used for saturation end
point scaling.

Keywords may be used only if ENDSCALE (see 12.1.136) is present in data file. See 2.6.7,
2.6.8 for details of end point scaling.

The same number of values as number of cells must be specified. The data should be
terminated with a slash /.

Default: value of relative permeability from table for corresponding saturation.

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.59. KRW, KRWR 994

Keywords for formats tN, E1, E3 19.1

12.6.60. KRG, KRGR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

These keywords define:

• 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.52).

The values should be specified for all grid blocks, they will be used for saturation end
point scaling.

Keywords may be used only if ENDSCALE (see 12.1.136) is present in data file. See 2.6.7,
2.6.8 for details of end point scaling.

The same number of values as number of cells must be specified. The data should be
terminated with a slash /.

Default: value of relative permeability from table for corresponding saturation.

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.60. KRG, KRGR 995

Keywords for formats tN, E1, E3 19.1

12.6.61. IKRG, IKRGR, IKRW, IKRWR, IKRO, IKRORW, IKRORG

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

These keywords specify imbibition (hysteresis option – 2.7) end point relative permeabil-
ities:

• IKRG – maximal gas relative permeability (for drainage process this value is specified
via the keyword KRG, see 12.6.60);

• 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.60);

• IKRW – maximal water relative permeability (for drainage process this value is specified
via the keyword KRW, see 12.6.59);

• IKRWR – water relative permeability at the residual oil (of residual gas in gas-water sys-
tem) (for drainage process this value is specified via the keyword KRWR, see 12.6.59);

• IKRO – maximal oil relative permeability (for drainage process this value is specified
via the keyword KRO, see 12.6.58);

• IKRORG – oil relative permeability at the critical gas saturation (for drainage process
this value is specified via the keyword KRORG, see 12.6.58);

• IKRORW – oil relative permeability at the critical water saturation (for drainage process
this value is specified via the keyword KRORW, see 12.6.58).

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.1.136) and SATOPTS
(see 12.1.75) are present.

12.6.61. IKRG, IKRGR, IKRW, IKRWR, IKRO, IKRORW, IKRORG 996

Keywords for formats tN, E1, E3 19.1

12.6.62. PCW

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.1.136) is present in data file. See 2.11.4 for details.
In case of hysteresis option is activated (parameter HYSTER of the keyword SATOPTS
(see 12.1.75) this keyword PCW scales only drainage curve. The imbibition curve is scaled
by using the keyword IPCW (see 12.6.64).

The same number of values as number of cells must be specified.

Default: maximal oil-water capillary pressure in corresponding saturation region, i.e. max-
imum capillary pressure from table SWOF (see 12.6.1).

Note: If the keyword SWATINIT (see 12.6.65) is specified then the values specified via
PCW (see 12.6.62), will be ignored. The keyword PPCWMAX (see 12.6.66) 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.62. PCW 997

Keywords for formats tN, E1, E3 19.1

12.6.63. PCG

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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 ENDSCALE
(see 12.1.136) is present in data file. See 2.11.4 for details.
In case of hysteresis option is activated (parameter HYSTER of the keyword SATOPTS
(see 12.1.75) this keyword PCG scales only drainage curve. The imbibition curve is scaled by
using the keyword IPCG (see 12.6.64).

The same number of values as number of cells must be specified.

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.63. PCG 998

Keywords for formats tN, E1, E3 19.1

12.6.64. IPCW, IPCG

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

These keywords define end–points values of imbibition capillary pressure for each block.
These keywords can be used if only keywords ENDSCALE (see 12.1.136) and SATOPTS
(see 12.1.75) are used in the model’s data file. Capillary pressure scaling is described in the
section 2.11.4.
The data should be terminated with a slash /.
The imbibition tables can be scaled in the same way as the drainage ones.

• IPCW – maximum water capillary pressures (drainage water capillary pressure is defined
by PCW, see 12.6.62);

• IPCG – maximum gas capillary pressures (drainage gas capillary pressure is defined by
PCG, see 12.6.63).

Example
DIMENS
4 1 1
/
...
IPCW
4*1000 /
In this example the maximum water capillary pressure is equal to 1000 for each cell.

12.6.64. IPCW, IPCG 999

Keywords for formats tN, E1, E3 19.1

12.6.65. SWATINIT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.16.2) should be used for
initialization). When SWATINIT is used, maximum capillary pressure array PCW is generated
(see 2.11.4 for details). Water saturation set up by SWATINIT will not always be honored, es-
pecially for the case when division by zero should be performed to scale pressure (see notes).

The keyword PPCWMAX (see 12.6.66) can be used to specify maximum values of capil-
lary pressure in saturation regions PPCWMAX (see 12.6.66).

!
Keyword may be used only if ENDSCALE (see 12.1.136) is presented in
data file. For models in E1 format: even if the keyword ENDSCALE is not
specified, it is assumed anyway that it is presented in the model and the
simulation goes with default ENDSCALE parameters.
The same number of values as number of cells must be specified.

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 it’s 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.16.2) is not set to zero, SWATINIT saturation will not
exactly be honored due to fine layer equilibrium calculation.

• If PCW (see 12.6.62) keyword is set, its values will be ignored.

• If JFUNC (see 12.2.63) keyword is used, maximum capillary pressures Pcw calculated
from it will be ignored.

12.6.65. SWATINIT 1000

Keywords for formats tN, E1, E3 19.1

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.65. SWATINIT 1001

Keywords for formats tN, E1, E3 19.1

12.6.66. PPCWMAX

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.65) (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 shouldn’t be greater than the 1-st parameter of the keyword
TABDIMS (see 12.1.29) (number of saturation regions). Each data line should be terminated
with a slash /.

One data line contains the following parameters:

1. maximum capillary pressure in the saturation region (the value should be greater than the
maximum capillary pressure in the corresponding saturation function table) (METRIC:
barsa, FIELD: psia);

2. flag YES or NO (connate saturation should be modified to correspond to the input water
saturation (SWATINIT, see 12.6.65) 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.65);
• NO – input saturation values (SWATINIT, see 12.6.65) 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.66. PPCWMAX 1002

Keywords for formats tN, E1, E3 19.1

12.6.67. EHYSTR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is used to specify phase permeabilities hysteresis – 2.7.

Hysteresis curvature parameters for saturation regions (SATNUM, see 12.4.3) can be set
via the keyword EHYSTRR (see 12.6.68).

The following parameters should be specified (The data should be terminated with a slash
/.):
1. curvature parameter for capillary pressure hysteresis (in the range from 0.005 to 0.1);
Default: 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 – Carlson’s Hysteresis model used for the non-wetting phase(s), drainage (SAT-
NUM, see 12.4.3) curve used for the wetting phase.
◦ 1 – Carlson’s Hysteresis model used for the non-wetting phase(s), imbibition (IMB-
NUM, see 12.4.7) curve used for the wetting phase.
◦ 2 – Killough’s Hysteresis model used for the non-wetting phase(s), drainage (SAT-
NUM, see 12.4.3) curve used for the wetting phase.
◦ 3 – Killough’s Hysteresis model used for the non-wetting phase(s), imbibition (IMB-
NUM, see 12.4.7) curve used for the wetting phase.
◦ 4 – Killough’s hysteresis model used for both wetting and non-wetting phases.
◦ 5 – Carlson’s non-wetting model for gas and water phases, drainage (SATNUM,
see 12.4.3) curve used for the wetting phase.
◦ 6 – Killough’s non-wetting model for the gas and water phases, drainage (SATNUM,
see 12.4.3) curve used for the wetting phase.
◦ 7 – Killough’s Hysteresis Model used for the non-wetting gas and water phases and
the wetting oil phase.
◦ 8 – Jargon’s Hysteresis Model used for the non-wetting phase, drainage (SATNUM,
see 12.4.3) curve used for the wetting phase.
◦ 9 – Jargon’s Hysteresis Model used for the non-wetting phase, imbibition (IMBNUM,
see 12.4.7) curve used for the wetting phase.

12.6.67. EHYSTR 1003

Keywords for formats tN, E1, E3 19.1

◦ -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 imbi-
bition curve (IMBNUM, see 12.4.7).
Default: 0 for E1, 2 for E3 models.

3. curvature parameter for Killough’s wetting phase relative permeability hysteresis (posi-
tive number);
Default: 1.

4. modification parameter for the trapped non-wetting phase saturation in the Killough
model.
Default: 0.1.

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.
• NONE – this option turns off hysteresis.
Default: BOTH.

6. parameter defining the shape of the capillary pressure scanning curves when secondary
reversal occurs. This parameter can be used only for capillary pressure hysteresis (the
Killough model).

• RETR – if an imbibition is swithes to drainage, then the secondary drainage process

will follow the same path as the previous scanning curve.
• NEW – if an imbibition is swithes to drainage, then the new scanning curve will
be constructed for the secondary drainage process.
Default: RETR.

7. parameter defining whether the initial fluid mobility correction (option MOBILE in key-
word EQLOPTS, see 12.1.94) or the transition zone calculation (keyword TZONE,
see 12.6.24) implements just to the drainage curve or to both the drainage and im-
bibition curves.

• DRAIN – the end points of the drainage curves are changed only to get the initial
fluid mobility correction in each grid block;
Default: DRAIN.

8. select the wetting phase in models of black-oil type:

12.6.67. EHYSTR 1004

Keywords for formats tN, E1, E3 19.1

• OIL – oil is wetting to gas;

• GAS – oil is non-wetting to gas.
Default: OIL.

9. parameter specifying relative permeability model with hysteresis for the oil phase
(BAKER1 or BAKER2). The two phase relative permeability is calculated using the
hysteresis model defined by parameter 2. IS IGNORED. This is an E1/E3 compatibility
field;

10. parameter specifying relative permeability model with hysteresis for the gas phase
(BAKER1 or BAKER2). The two phase relative permeability is calculated using the
hysteresis model defined by parameter 2. IS IGNORED. This is an E1/E3 compatibility
field;

11. parameter specifying relative permeability model with hysteresis for the water phase
(BAKER1 or BAKER2). The two phase relative permeability is calculated using the
hysteresis model defined by parameter 2. IS IGNORED. This is an E1/E3 compatibility
field;

12. a threshold saturation of Killough’s hysteresis model for both wetting and non-wetting
phases. The threshold saturation allows to control of the numerical sensitivity of the sys-
tem in order to avoid its unstable behavior. IS IGNORED. This is an E1/E3 compatibility
field;

13. parameter allowing to modify the location of relative permeability scanning curve for
the wetting phase in order to decrease the deviation of scanning curve from the region
bounded by the drainage and imbibition curves. Such behavior can occur if the initial
gradients of the relative permeability curves are small. The modification of scanning
curve location is only implemented to the Killough wetting phase relative permeability
hysteresis model specified by parameter 2 (4 or 7 model). Otherwise this parameter will
be ignored.
Default: 0 (NO).

Example
EHYSTR
0.07 0 1 0.1 /

12.6.67. EHYSTR 1005

Keywords for formats tN, E1, E3 19.1

12.6.68. EHYSTRR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is used to specify phase permeabilities hysteresis – 2.7.

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.67).
The following parameters should be specified:
1. curvature parameter for capillary pressure hysteresis (in the range from 0.005 to 0.1);
Default: 0.1.
2. curvature parameter for Killough’s 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.67) is equal 4 (Killough’s hysteresis model used for both
wetting and non-wetting phases);
Default: 0.
3. modification parameter for the trapped non-wetting phase saturation in the Killough
model.
Default: 1.
4. 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.
• NONE – this option turns off hysteresis.
Default: BOTH.

Example
EHYSTRR
0.06 1.0 0.1 /
0.08 1.0 0.1 /

12.6.68. EHYSTRR 1006

Keywords for formats tN, E1, E3 19.1

In this example the data are set for 2 regions.

12.6.68. EHYSTRR 1007

Keywords for formats tN, E1, E3 19.1

12.6.69. DRAINAGE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword enables the drainage option in hysteresis – 2.7. It imposes the upper limit for
relative permeability values K r . If this keyword is defined, the scanning curves for relative
permeability hysteresis will not be allowed to lie above the drainage curve.

12.6.69. DRAINAGE 1008

Keywords for formats tN, E1, E3 19.1

12.6.70. HYSTKRW / HYSTKROW / HYSTKRG / HYSTKROG

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword defines the properties of relative permeability hysteresis for varios phases:
The hysteresis option should be previously enabled via HYSTER parameter of SATOPTS
(see 12.1.75) keyword.

• HYSTKRW – hysteresis parameters for water relative permeability in oil-water system.

• HYSTKROW – hysteresis parameters for oil relative permeability in oil-water system.
• HYSTKRG – hysteresis parameters for gas relative permeability in gas-liquid system.
• HYSTKROG – hysteresis parameters for oil relative permeability in gas-oil system.

The algorithms for relative permeability hysteresis calculations are described in Relative
permeability hysteresis in the non-wetting phase and Relative permeability hysteresis in the
wetting phase sections.

The entry format and available parameters are the same for all these keywords.
The parameters should be entered in the lines below the keyword. Each parameter starts
on a new line and is terminated with a slash /. All data should be terminated with a final
slash /.
The list of available parameters:
1. Methods for phase relative permeability hysteresis calculations.
Only one parameter from the following list can be indicated:
• DRAIN – Hysteresis option is disabeled, the darinage curve will be used to deter-
mine phase relative permeability (SATNUM, see 12.4.3). If no other parameters
are specified, this option will be used by default.
• IMB – Hysteresis option is disabeled, the imbibition curve will be used to determine
phase relative permeability (IMBNUM, see 12.4.7) The imbibition curve is used to
determine phase relative permeability (i.e. hysteresis option is disabeled).
• KILLOUGH – This parameter indicates that Killough’s method will be used for
phase relative permeability hysteresis calculations.
This method can be used both for wetting and non-wetting phases.
• KILLOUGH_MOD – This parameter indicates that modified Killough’s method will
be used for phase relative permeability hysteresis calculations.
This method can be used only for wetting phase.

12.6.70. HYSTKRW / HYSTKROW / HYSTKRG / HYSTKROG 1009

Keywords for formats tN, E1, E3 19.1

• CARLSON – This parameter indicates that Carlson’s method will be used for phase
relative permeability hysteresis calculations.
This method can be used only for non-wetting phase.
• CARLSON_A – This parameter indicates that Analytical Carlson’s method will be
used for phase relative permeability hysteresis calculations.
This method can be used only for non-wetting phase.
• JARGON – This parameter indicates that Jargon’s method will be used for phase
relative permeability hysteresis calculations.
This method can be used only for non-wetting phase.

2. Additional properties:

• SPTMAX – the maximum residual phase saturation for imbibition process.

This parameter is only used for analytical Carlson’s method (CARLSON_A).
Default: If the for SPTMAX is not specified, the simulator will use the midpoint
saturation value on the line between maximum and critical oil saturations..
• NONWET_POW –The exponent of Killough’s saturation interpolation equation
for non-wetting phase 2.64. This parameter defines the curvature and position of
relative permeability scanning curve for non-wetting phase.
This parameter can be used only for non-wetting phase in KILLOUGH method.
Default: 1.
• WET_POW – The exponent of Killough’s saturation interpolation equation for
wetting phase 2.66. This parameter defines the curvature and position of phase
relative permeability scanning curve for wetting phase.
This parameter can be used only for wetting phase in KILLOUGH or KIL-
LOUGH_MOD methods.
Default: 1.
• TRAP_PARAM – Modification parameter for the trapped non-wetting phase satu-
ration.
This parameter can be used both for wetting and non-wetting phases in KIL-
LOUGH, KILLOUGH_MOD and CARLSON_A methods.
Default: 0.1.

12.6.70. HYSTKRW / HYSTKROW / HYSTKRG / HYSTKROG 1010

Keywords for formats tN, E1, E3 19.1

Example
SATOPTS
HYSTER /
... ... ...
HYSTKROW
-- type value
CARLSON /
SPTMAX 0.27 /
/

HYSTKRW
-- type value
KILLOUGH /
WET_POW 2 /
/

In this example:

• Hysteresis option is triggered in the model via HYSTER parameter of SATOPTS key-
word.

• Properties of oil relative permebility hysteresis are defined via HYSTKROW keyword.

• Carlson’s method is used for oil relative permebility hysteresis.

• Properties of water relative permebility hysteresis are defined via HYSTKRW keyword.

• Killough’s method is used for water relative permebility hysteresis.

12.6.70. HYSTKRW / HYSTKROW / HYSTKRG / HYSTKROG 1011

Keywords for formats tN, E1, E3 19.1

12.6.71. HYSTKRWR / HYSTKROWR / HYSTKRGR / HYSTKROGR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

These keywords define the properties of relative permeability hysteresis for varios phases
per saturation region:
The hysteresis option should be previously enabled via HYSTER parameter of SATOPTS
(see 12.1.75) keyword.

• HYSTKRWR – hysteresis parameters for water relative permeability in oil-water sys-

tem.

• HYSTKROWR – hysteresis parameters for oil relative permeability in oil-water system.

• HYSTKRGR – hysteresis parameters for gas relative permeability in gas-liquid system.

• HYSTKROGR – hysteresis parameters for oil relative permeability in gas-oil system.

Different hysteresis models can be assigned to each saturation region.

The algorithms for relative permeability hysteresis calculations are described in Relative
permeability hysteresis in the non-wetting phase and Relative permeability hysteresis in the
wetting phase sections.

These keywords have the same entry format as HYSTKRW / HYSTKROW / HYSTKRG
/ HYSTKROG (see 12.6.70) keywords, but the data should be entered for each saturation
region. The number of saturation regions is defined via TABDIMS (see 12.1.29) keyword. The
data for each saturation region should be terminated with a slash /.

12.6.71. HYSTKRWR / HYSTKROWR / HYSTKRGR / HYSTKROGR 1012

Keywords for formats tN, E1, E3 19.1

Example
SATOPTS
HYSTER /

TABDIMS
3 /
... ... ...
HYSTKROWR
-- type value
CARLSON / -- oil RP hysteresis model for SATNUM=1
SPTMAX 0.27 /
/
JARGON / -- oil RP hysteresis model for SATNUM=2
/
/

HYSTKRW
-- type value
CARLSON / -- water RP hysteresis model for SATNUM=1
SPTMAX 0.27 /
/
KILLOUGH / -- water RP hysteresis model for SATNUM=2
/
/

In this example:

1. Hysteresis option is triggered in the model via HYSTER parameter of SATOPTS key-
word.

2. Three saturation regions are defined in the model via TABDIMS keyword.

3. Parameters of oil relative permeability hysteresis are defined via HYSTKROWR key-
word:

• Carlson’s hysteresis model and maximum residual phase saturation are set for the
first saturation region
• Jargon’s hysteresis model is set for the second saturation region
• No data is entered for the third saturation region, hence the hysteresis option is
disabled for this region (equal to the DRAIN option).

4. Parameters of water relative permeability hysteresis are defined via HYSTKRWR key-
word:

• Carlson’s hysteresis model is set for the first saturation region

• Killough’s hysteresis model is set for the second saturation region

12.6.71. HYSTKRWR / HYSTKROWR / HYSTKRGR / HYSTKROGR 1013

Keywords for formats tN, E1, E3 19.1

• No data is entered for the third saturation region, hence the hysteresis option is
disabled for this region (equal to the DRAIN option).

12.6.71. HYSTKRWR / HYSTKROWR / HYSTKRGR / HYSTKROGR 1014

Keywords for formats tN, E1, E3 19.1

12.6.72. HYSTPCW / HYSTPCG

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

These keywords define the parameters of capillary pressure hysteresis for various systems:
The hysteresis option should be previously enabled via HYSTER parameter of SATOPTS
(see 12.1.75) keyword.

• HYSTPCW – capillary pressure hysteresis in oil-water system.

• HYSTPCG – capillary pressure hysteresis in gas-liquid system.

The algorithms for capillary pressure hysteresis calculations are described in Capillary
pressure hysteresis section.

The entry format and available parameters are the same for all these keywords.
The parameters should be entered in the lines below the keyword. Each parameter starts
on a new line and is terminated with a slash /. All data should be terminated with a final
slash /.
The list of available parameters:

1. The available methods of capillary pressure calculation.

• DRAIN – The darinage curve is used to determine capillary pressure (i.e. hysteresis
option is disabeled).
If no other parameters are specified, this option will be used by default.
• IMB – The imbibition curve is used to determine capillary pressure (i.e. hysteresis
option is disabeled).
• KILLOUGH – This parameter enables hysteresis option for capillary pressure and
indicates that. Killough’s method will be used for hysteresis calculations.

2. If hysteresis option is enabled by KILLOUGH, the following parameters might be set in

order to define additional properties:

• EPS – The value which determines the transition between capillary pressure imbi-
bition and drainage curves.
This is a dimensionless parameter which has a value in the range from 0.005 to
0.1.
Default: 0.1.

12.6.72. HYSTPCW / HYSTPCG 1015

Keywords for formats tN, E1, E3 19.1

• NEW – This parameter indicates that if an imbibition is swithes to drainage, then

the new scanning curve will be constructed for the secondary drainage process.

Example
SATOPTS
HYSTER /
... ... ...
HYSTPCW
-- type value
KILLOUGH /
EPS 0.023 /
/

HYSTPCG
-- type value
KILLOUGH /
EPS 0.037 /
NEW /
/

In this example:

• Hysteresis option is triggered in the model via HYSTER parameter of SATOPTS key-
word.

• Capillary pressure hysteresis in oil-water system is defined via HYSTPCW keyword.

• Capillary pressure hysteresis in gas-liquid system is defined via HYSTPCG keyword.

12.6.72. HYSTPCW / HYSTPCG 1016

Keywords for formats tN, E1, E3 19.1

12.6.73. HYSTPCWR / HYSTPCGR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

These keywords define the parameters of capillary pressure hysteresis for various systems
per saturation region:

• HYSTPCWR – capillary pressure in oil-water system.

• HYSTPCGR – capillary pressure in gas-liquid system.

Different hysteresis models can be assigned to each saturation region.

The hysteresis option should be previously enabled via HYSTER parameter of SATOPTS
(see 12.1.75) keyword.

The algorithms for capillary pressure hysteresis calculations are described in Capillary
pressure hysteresis section.

These keywords have the same entry format as HYSTPCW / HYSTPCG (see 12.6.72)
keywords, but the data should be entered for each saturation region. The number of saturation
regions is defined via TABDIMS (see 12.1.29) keyword. The data for each saturation region
should be terminated with a slash /.

Example
SATOPTS
HYSTER /

TABDIMS
2 /
... ... ...
HYSTPCWR
-- type value
KILLOUGH / -- Pc hysteresis option for SATNUM=1
EPS 0.023 /
NEW /
/
DRAIN / -- Pc hysteresis option for SATNUM=2
/

In this example:

12.6.73. HYSTPCWR / HYSTPCGR 1017

Keywords for formats tN, E1, E3 19.1

• Hysteresis option is triggered in the model via HYSTER parameter of SATOPTS key-
word.

• Two saturation regions are defined in the model via TABDIMS keyword.

• Capillary pressure hysteresis is defined in the first saturation region via the parameter
KILLOUGH.

• For the second saturation region the parameter DRAIN is indicated. Hence the hysteresis
option is not enabled in this region and capillary pressure follows the drainage curve.

12.6.73. HYSTPCWR / HYSTPCGR 1018

Keywords for formats tN, E1, E3 19.1

12.6.74. HYSTOPTS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets additional parameters of hysteresis option.

The hysteresis option should be previously enabled via HYSTER parameter of SATOPTS
(see 12.1.75) keyword.

The algorithms for hysteresis calculations are described in 2.7.2 - 2.7.4 sections.

The list of available parameters:

• OILWET – this parameter indicates that oil is treated as a wetting phase in oil-water
system.
• GASWET – this parameter indicates that both oil and gas are treated as a non-wetting
phases in gas-oil system.
• THSAT_KR – value of threshold saturation for relative permeability hysteresis calcula-
tion.
Default: 1e-12.
• THSAT_PC – value of threshold saturation for capillary pressure hysteresis calculation.
Default: 1e-6.
• DPCDS – The maximum value of partial derivative of capillary pressure with respect to
saturation (METRIC: bar , FIELD: psi).
If 0 value is specified, then it is assumed there is no limit.
Default: 1000.

Example
SATOPTS
HYSTER /
... ... ...
HYSTOPTS
OILWET /
THSAT_KR 0.0001 /
THSAT_KR 0.001 /
DPCDS 0 /
/

In this example:

12.6.74. HYSTOPTS 1019

Keywords for formats tN, E1, E3 19.1

• Hysteresis option is triggered in the model via HYSTER parameter of SATOPTS key-
word.

• Oil set to be treated as the wetting phase in gas-oil system via OILWET parameter.

• The threshold saturation values are set via THSAT_KR and THSAT_PC parameters.

• The value of DPCDS parameter is set equal to 0. Hence, no limit is imposed for the
maximum partial derivative of capillary pressure.

12.6.74. HYSTOPTS 1020

Keywords for formats tN, E1, E3 19.1

12.6.75. HYSTOPTSR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets additional parameters of hysteresis option per saturation region.
The hysteresis option should be previously enabled via HYSTER parameter of SATOPTS
(see 12.1.75) keyword.

The algorithms for hysteresis calculations are described in 2.7.2 - 2.7.4 sections.

This keyword has the same entry format as HYSTOPTS (see 12.6.74) keywords, but the
data should be entered for each saturation region. The number of saturation regions is defined
via TABDIMS (see 12.1.29) keyword. The data for each saturation region should be terminated
with a slash /.

Example
SATOPTS
HYSTER /

TABDIMS
2 /
... ... ...
HYSTOPTSR
OILWET / -- hysteresis option for SATNUM=1
/
GASWET / -- hysteresis option for SATNUM=2
/

In this example:
1. Hysteresis option is triggered in the model via HYSTER parameter of SATOPTS key-
word.

2. Two saturation regions are defined in the model via TABDIMS keyword.

3. Different wettability options are set for these regions:

• In the first saturation region, oil is set to be treated as the wetting phase in oil-water
system via OILWET parameter.
• In the second saturation region, oil is set to be treated as a non-wetting phase in
gas-oil system via GASWET parameter.

12.6.75. HYSTOPTSR 1021

Keywords for formats tN, E1, E3 19.1

12.6.76. MISCSTR

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keywords specifies the miscibility reference surface tension – 2.6.12. One should use
the keyword MISCSTRR (see 12.6.78) to set the miscibility reference surface tension for each
saturation region.

Interpolation factor that is used in miscibility:

σ N
F =( )
σ0
σ0 – reference surface tension.
N – an exponent (specified via MISCEXP, see 12.6.79).

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.

The following parameters should be specified (The data should be terminated with a slash
/.):

1. reference surface tension (Dynes/cm);

2. maximum expected surface tension. IGNORED. This is an E1/E3 compatibility field

3. maximum surface tension that is used to scale the input capillary pressure curves. IG-
NORED. This is an E1/E3 compatibility field

Example
MISCSTR
49 /

12.6.76. MISCSTR 1022

Keywords for formats tN, E1, E3 19.1

12.6.77. MISCSTRP

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is used to specify miscibility surface tension reference pressure (METRIC:
barsa, FIELD: psia) (see section 2.6.12). If option MISCIBLE (see 12.1.69) is applied the
keyword can be used as an alternative to MISCSTR (see 12.6.76) to specify the surface
tension at which immiscible conditions are supposed to exist.
In general case the surface tension at which the rock curve data was measured is not
known. This causes the problem in using the keyword MISCSTR (see 12.6.76). On the other
hand, the keyword MISCSTRP allows a pressure to be specified at which the reservoir fluid
composition will be flashed to obtain the reference value. This value is below the initial
reservoir pressure and far from the critical point for the oil and gas to be totally immiscible.

12.6.77. MISCSTRP 1023

Keywords for formats tN, E1, E3 19.1

12.6.78. MISCSTRR

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keywords specifies the miscibility reference surface tension for saturation regions –
2.6.12. One should use the keyword MISCSTR (see 12.6.76) to set the miscibility reference
surface tension for the whole reservoir.

Interpolation factor that is used in miscibility:

σ N
F =( )
σ0
σ0 – reference surface tension.
N – an exponent (specified via MISCEXP, see 12.6.79).

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.

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 E1/E3 compatibility field

3. maximum surface tension that is used to scale the input capillary pressure curves. IG-
NORED. This is an E1/E3 compatibility field

Example
MISCSTRR
49 /
40 /
38 /

12.6.78. MISCSTRR 1024

Keywords for formats tN, E1, E3 19.1

12.6.79. MISCEXP

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specified the miscibility exponent (2.6.12).

The data should be terminated with a slash /.
Interpolation factor that is used in miscibility:
σ N
F =( )
σ0
σ0 – reference surface tension (specified via MISCSTR, see 12.6.76).
N – an exponent (specified via MISCEXP, see 12.6.79).

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.

Example
MISCEXP
0.2 /

12.6.79. MISCEXP 1025

Keywords for formats tN, E1, E3 19.1

12.6.80. PARACHOR

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.14.1). The data should be terminated with a slash /.
Example
COMPS
3/

...

PARACHOR
74.92 192.74 390.4 /

12.6.80. PARACHOR 1026

Keywords for formats tN, E1, E3 19.1

12.6.81. PMISC

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword defines tables that model the transition between immiscible and miscible
displacement as a function of oil pressure. This keyword is optional and can be used only in
calculations where miscibility exists (see keywords MISCIBLE, see 12.1.69). If this keyword
is not defined in miscible calculations, it is assumed that a miscible displacement occurs at
any pressure, in other words, pressure does not affect the miscibility. The detailed description
of miscible displacement model is given in the section 2.6.13.
Saturation functions for the immiscible fluid must be specified if PMISC is used in calcu-
lations where miscibility exists.
The number of tables for this keyword is specified by 1-st parameter of the keyword
MISCIBLE (see 12.1.69). Each table consists of two columns:

1. the local pressure of oil phase is defined in 1-st column. The value should increase down
the column. (METRIC: barsa, FIELD: psi);

2. the corresponding miscibility (varies from 0 to 1). The miscibility equal to 0 corresponds
to immiscible displacement, and 1 to miscible displacement. The values should be at
constant level or increase down the column.

In each column the number of values should coincide.

Example
PMISC
2000 0.0
8000 1.0 /

12.6.81. PMISC 1027

Keywords for formats tN, E1, E3 19.1

12.6.82. MSFN

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword allows to use a relative permeability curve for the miscible displacement
model activated by keyword MISCIBLE (see 12.1.69) in the section RUNSPEC. This key-
word is optional and can be used only in calculations where miscibility exists. The detailed
description of miscible displacement model is given in the section 2.6.13.
The number of tables for this keyword is specified by 1-st parameter of keyword TABDIMS
(see 12.1.29). The last row of table should be terminated by slash /.
Each table consists of three columns:

1. normalized total gas phase fraction. The value of fraction varies from 0 to 1, monotoni-
cally increasing down the column;

2. corresponding relative permeability multiplier for gas MkrG . The multiplier varies from
0 to 1. It can be set at constant level or increase down the column;

3. corresponding relative permeability multiplier for oil MkrO . The multiplier varies from
0 to 1. It can be set at constant level or decrease down the column.

In each column the number of values should coincide. Furthermore, the number of values
should not be less than 2.
It should be noticed that the relative permeabilities are normalized and take into account
the end points provided by keywords SORWMIS (see 12.6.85) and SGCWMIS (see 12.6.84).
SORWMIS (see 12.6.85) provides the critical oil saturation as a function of water saturation.
SGCWMIS (see 12.6.84) provides the critical gas saturation. Therefore, when the flood is
totally miscible (see keyword PMISC, see 12.6.81) oil and gas relative permeabilities are
calculated as:
SG − SGr
krG = MkrG krt (St )
St − SGr − SOr
SO − SOr
krO = MkrO krt (St )
St − SGr − SOr
where SG , St = SG + SO is the total hydrocarbon saturation, SGr is the critical gas saturation,
SOr is the critical oil saturation, krt (St ) is the relative permeability of hydrocarbon to water.
If keyword MSFN is not used, the relative permeabilities are defined as linear function:
SG − SGr
krG = krt (St )
St − SGr − SOr

12.6.82. MSFN 1028

Keywords for formats tN, E1, E3 19.1

SO − SOr
krO = krt (St )
St − SGr − SOr

Example
MSFN
0.0 0.0 1.0
0.3 0.2 0.6
0.4 0.5 0.4
1.0 1.0 0.0 /

12.6.82. MSFN 1029

Keywords for formats tN, E1, E3 19.1

12.6.83. SDENSITY

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies the surface density of miscible injection gas for the miscible dis-
placement model activated by keyword MISCIBLE (see 12.1.69) in the section RUNSPEC.
The detailed description of miscible displacement model is given in the section 2.6.13.
The number of density gas values (METRIC: kg/m3 , FIELD: lb/ f t 3 ) should be equal to
the number of PVT regions (2-nd parameter of the keyword TABDIMS, see 12.1.29). Each
line contains on value of density and should be terminated by symbol /.
For the miscible displacement model the value of gas surface density specified by this
keyword is used to calculate the effective oil and gas densities in each grid block. The density
of miscible gas within a grid block is specified by PVT region number (see keyword PVTNUM,
see 12.4.2), to which this block corresponds, not by its miscibility region number (see keyword
MISCNUM, see 12.4.8).
Surface density of solution gas is specified by keywords DENSITY (see 12.5.33) or GRAV-
ITY (see 12.5.34).
Notice that for miscible gas it is not possible to define its surface gravity (with respect to
air).
Example
SDENSITY
0.06243 /

12.6.83. SDENSITY 1030

Keywords for formats tN, E1, E3 19.1

12.6.84. SGCWMIS

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword defines tables of miscible critical gas saturation versus water saturation.
This keyword can be used for miscible calculations using the miscible flood option defined
by MISCIBLE (see 12.1.69) in RUNSPEC section and where oil, water and gas are all exists.
For miscible flood simulations involving the water phase this keyword can be skipped. In
such case a miscible critical gas saturation is set to zero. The detailed description of miscible
displacement model is given in the section 2.6.13.
The number of tables is defined by 1-st parameter of the keyword MISCIBLE (see 12.1.69).
Each table should be terminated by symbol /. Each table consists of two columns:

1. Water saturation value. Its values varies from 0 to 1, monotonically increasing down the
column;

2. The corresponding miscible critical gas saturation. Its values varies from 0 to 1. It can
be set at constant level or increase down the column.

In each column the number of values should coincide. Furthermore, the number of values
should not be less than 2.
Example
SGCWMIS
0.0 0.00
1.0 0.60 /

12.6.84. SGCWMIS 1031

Keywords for formats tN, E1, E3 19.1

12.6.85. SORWMIS

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword defines tables of miscible residual oil saturation versus water saturation.
This keyword can be used for miscible calculations using the miscible flood option defined
by MISCIBLE (see 12.1.69) in RUNSPEC section and where oil, water and gas are all exists.
For miscible flood simulations involving the water phase this keyword may be skipped. In
such case a miscible critical gas saturation is set to zero. The detailed description of miscible
displacement model is given in the section 2.6.13.
The number of tables is defined by 1-st parameter of the keyword MISCIBLE (see 12.1.69).
Each table should be terminated by symbol /. Each table consists of two columns:

1. Water saturation value. Its values varies from 0 to 1, monotonically increasing down the
column;

2. The corresponding miscible residual oil saturation. Its values varies from 0 to 1. It can
be set at constant level or increase down the column.

In each column the number of values should coincide. Furthermore, the number of values
should not be less than 2.
Example
SORWMIS
0.0 0.00
1.0 0.30 /

12.6.85. SORWMIS 1032

Keywords for formats tN, E1, E3 19.1

12.6.86. TLMIXPAR

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword defines the Todd-Longstaff mixing parameter. This keyword can be used for
miscible calculations using the miscible flood option defined by MISCIBLE (see 12.1.69) in
RUNSPEC section. The keyword is obligatory in these calculations. The detailed description
of miscible displacement model is given in the section 2.6.13.
It does not affect the polymer model (keyword POLYMER, see 12.1.51), for which the
keyword PLMIXPAR (see 12.8.29) should be used.
The number of lines defines 1-st parameter of the keyword MISCIBLE (see 12.1.69). Each
line contains two values and should be terminated by symbol /.

1. Todd-Longstaff mixing parameter for the viscosity calculation. The parameter is dimen-
sionless and varies from 0 to 1 for each miscibility region;

2. Todd-Longstaff mixing parameter for the density calculation.

Default: The same value as for the viscosity mixing parameter.

The second value in a line will be ignored if TLMIXPAR is used for the polymer model.
For calculations it is possible to use both miscible displacement model and polymer model. In
this case the mixing parameter for polymer model should be defined by keyword PLMIXPAR
(see 12.8.29).
Example
TLMIXPAR
0.7 /

12.6.86. TLMIXPAR 1033

Keywords for formats tN, E1, E3 19.1

12.6.87. STOG

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.75).
The number of tables of this keyword is specified by 2-nd parameter of the keyword TABDIMS
(see 12.1.29). 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.29).
The following parameters should be specified:

• in the next after the keyword line:

1. oil phase reference pressure (METRIC: bar , FIELD: psi). The data should be
terminated with a slash /.

• 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.87) one table of surface tension depen-
dence on pressure in oil-gas system is set. Oil reference pressure is 100 psi.

12.6.87. STOG 1034

Keywords for formats tN, E1, E3 19.1

12.6.88. STOW

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.75).
The number of tables of this keyword is specified by 2-nd parameter of the keyword TABDIMS
(see 12.1.29). 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.29).
The following parameters should be specified:

• in the next after the keyword line:

1. oil phase reference pressure (METRIC: bar , FIELD: psi). The data should be
terminated with a slash /.

• 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.87) one table of surface tension depen-
dence on pressure in oil-water system is set. Oil reference pressure is 100 psi.

12.6.88. STOW 1035

Keywords for formats tN, E1, E3 19.1

12.6.89. KRSMOOTH

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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 smoothing 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 analogue for model in syntax IM, ST: the option SMOOTHEND in
the keywords SWT (see 13.6.5), SLT (see 13.6.6), SGT (see 13.6.7).

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.89. KRSMOOTH 1036

Keywords for formats tN, E1, E3 19.1

12.6.90. LINEAR_ISOPERM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword indicates that oil relative permeability krO is calculated using the Linear
Isoperm model (see section 4.35.3).
This option is analogous to the option LININTERP of the keyword RPT (see 13.6.2) and
option LINEAR_ISOPERM of the keyword KROIL (see 13.6.3).
Example
LINEAR_ISOPERM

12.6.90. LINEAR_ISOPERM 1037

Keywords for formats tN, E1, E3 19.1

12.7. Salts and tracers

This section contains the keywords for salt and tracer properties description.

12.7. Salts and tracers 1038

Keywords for formats tN, E1, E3 19.1

12.7.1. SALTPROP

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.62). The simulation
of waters with different salinities and corresponding keywords are described in details in the
section 2.24.1.

Number of data records depends on number of PVT regions (defined in TABDIMS,

see 12.1.29). 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);
Default: 300 kg/sm3 .

2. density of reservoir salt at reference pressure pre f (specified via the keyword ROCK,
see 12.5.17) i.e. we suppose that reservoir salt compressibility is equal to rock com-
pressibility (METRIC: kg/sm3 , FIELD: lb/ f t 3 );
Default: 2165 kg/sm3 .

3. solution rate constant of reservoir salt ϑsalt (1/day).

Default: 0 (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 is the current salt quantity in the solution (kg), mmax is the salt quantity in the
saturated salt solution (kg) in the volume V .
Example
SALTPROP
350 2165 0.0001 /
/

12.7.1. SALTPROP 1039

Keywords for formats tN, E1, E3 19.1

12.7.2. SALTTRM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.62). The simulation of waters with different salinities and corresponding key-
words are described in details in the section 2.24.1.

Number of tables depends on number of PVT regions (defined in TABDIMS, see 12.1.29).
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.2. SALTTRM 1040

Keywords for formats tN, E1, E3 19.1

12.7.3. SALTNODE

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword defines salt concentration that is used in polymer solution viscosity cal-
culations. Supported options for polymer flood modelling and corresponding keywords are
described in the section 2.16.
Data are represented as tables, which number is specified by parameter 2 of the keyword TAB-
DIMS (see 12.1.29). 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.29). 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.6) or PLYVSCST, see 12.8.36).
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.3. SALTNODE 1041

Keywords for formats tN, E1, E3 19.1

12.7.4. ADSALNOD

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword defines salt concentration that is used in polymer adsorption by rock calcu-
lations (keyword PLYADSS, see 12.8.27). Supported options for polymer flood modelling and
corresponding keywords are described in the section 2.16.
Data are represented as tables which quantity is specified by the first parameter of keyword
TABDIMS (see 12.1.29). Each table should be terminated with a symbol /. Tables set the nodal
values for salt concentration that will be used in the calculation of the polymer adsorption by
rock.
The number of these values should not be greater than value of the third parameter of the
keyword TABDIMS (see 12.1.29). Values must be positive and strictly increasing.
The number of lines in each table must correspond to the number of lines of polymer
adsorption function varying with salinity (the keyword PLYADSS, see 12.8.27).
Each line of each table should contain the following parameters:

1. salt concentration (METRIC: kg/m3 , FIELD: lb/stb);

Example
ADSALNOD
.0
40.0
80.0
120.0 /
There is only one SAT region in the model, then only one table of salt concentration values
is set.

12.7.4. ADSALNOD 1042

Keywords for formats tN, E1, E3 19.1

12.7.5. ESSNODE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.16). The number of tables is
determined by the 2-nd parameter of the keyword TABDIMS (see 12.1.29). The number of
lines in each table shouldn’t exceed the value of the 4-th parameter of keyword TABDIMS
(see 12.1.29) 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 /.
The following parameters should be specified:

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.5. ESSNODE 1043

Keywords for formats tN, E1, E3 19.1

12.7.6. PLYVISCS

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword should be used only in the BRINE (see 12.1.62) option (mixing of waters
with different salinities). Supported options for polymer flood modelling and corresponding
keywords are described in the section 2.16.

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.29). 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.29). 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.3).

Other lines of one set (overall value of them is equal to the parameter 4 of the keyword
TABDIMS, see 12.1.29) contains of the 2-nd parameter only.

12.7.6. PLYVISCS 1044

Keywords for formats tN, E1, E3 19.1

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.3) (see example).

12.7.6. PLYVISCS 1045

Keywords for formats tN, E1, E3 19.1

12.7.7. BDENSITY

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies the brine surface density variation with the salt concentration (see
section 5.9.5). The keyword can be used only for runs in which the Brine option is active
(the keyword BRINE, see 12.1.62). The simulation of waters with different salinities and cor-
responding keywords are described in details in the section 2.24.1.
If the keyword is not specified, the surface density of water is taken which is specified via
DENSITY (see 12.5.33).
The data comprises a number of data lines equal to the 2-nd parameter of TABDIMS
(see 12.1.29), each data line should be terminated with a slash (/). Each data line con-
sists 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.8).
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.7. BDENSITY 1046

Keywords for formats tN, E1, E3 19.1

12.7.8. PVTWSALT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword supplies the water PVT data (see section 5.9.5) for runs in which the Brine
option is active (the keyword BRINE, see 12.1.62). The simulation of waters with different
salinities and corresponding keywords are described in details in the section 2.24.1. The
keyword is used in place of PVTW (see 12.5.5).

!
The keyword PVTWSALT shouldn’t be used in the models with polymer flood-
ing option (BRINE+POLYMER). Water viscosity in this case should be set via
PLYVISCS (see 12.7.6).
The data consists of tables. The number of tables is equal to the second parameter of the
keyword TABDIMS (see 12.1.29). 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.8. PVTWSALT 1047

Keywords for formats tN, E1, E3 19.1

12.7.9. LSALTFNC

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
x REGIONS SOLUTION SUMMARY SCHEDULE

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.63) – section 2.24.3).

The data consists of tables. The number of tables is equal to the first parameter of the
keyword TABDIMS (see 12.1.29). Each table should be terminated by a slash (/).

One table row contains the following parameters:

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.9. LSALTFNC 1048

Keywords for formats tN, E1, E3 19.1

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.9. LSALTFNC 1049

Keywords for formats tN, E1, E3 19.1

12.7.10. TRACER

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets passive tracers. Other keywords used for tracer modeling are given in
the section 2.17.1. In E1 each tracer is associated with one of three phases (water, oil, gas).
In E3 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 data line should be terminated with
the symbol /. All data should be terminated with a final slash /.
Each line should consist of the following parameters:

1. tracer name (in E1/E3 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: E1 – OIL, WAT, GAS; E3 – 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 E1/E3 compatibility field(this parameter is specified for partitioned

tracers only),

5. ignored, this is an E1/E3 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.10. TRACER 1050

Keywords for formats tN, E1, E3 19.1

12.7.11. TRACERM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets passive tracers for which the holding time in the reservoir will be cal-
culated.

Tracer name should be specified in its own new line and be terminated with a slash /. All
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.11. TRACERM 1051

Keywords for formats tN, E1, E3 19.1

12.7.12. TRACEROPTS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets passive tracers and parameters of their method calculation. The key-
word can be used in black oil and compositional models for modelling all passive tracers,
environmental tracers (see section 2.17), API (see section 2.8.8) and for waters with different
salinities (see section 2.24).

Each data line should be terminated with the symbol /. All data should be terminated with
a final slash /.
The following parameters should be specified:

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 time step;
DCY1 – foam/tracer decays instantaneously at the end of time step, adsorbed foam/-
tracer does not participate in decay process. So, at the end of time step there is no
equilibration between foam/tracer concentration in solution and in rock;
DCY2 – foam/tracer decays instantaneously at the end of time step, 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 time step there is the
equilibration state between foam/tracer concentration in solution and in rock;
DCY3 – if tracer decay and adsorption are used in the model, then adsorbed part
of the tracer and soluted one take part in decay process.
DCY4 – the equation of tracer mass conservation takes into account decay of tracer;
TRACERLOOP – is used for the time step refinement for the solution of the equa-
tion of tracer mass conservation. It specifies the number of iterations used to
subdivide the model time step.
TOLLIN n
tolerance of linear solver (this option affects on passive tracers for which option
FI is not set).
Default: 1.e-3.

12.7.12. TRACEROPTS 1052

Keywords for formats tN, E1, E3 19.1

TOLNEWT n
Maximal allowed residual to finish Newton iterations (this option affects on tracers
for which with respect to their concentration the system of non-linear algebraic
equations needed to be solved, for example polymers, alkalines, surfactants).
Default: 1.e-3.
TOLVARNEWT n
Maximal allowed main variables variation to finish Newton iterations (this option
affects on tracers for which with respect to their concentration the system of non-
linear algebraic equations needed to be solved, for example polymers, alkalines,
surfactants).
Default: 1.e-3.

The list of keywords used for foam simulation are given in the section 2.18.
Default:

• parameters of tracer method calculation:

– for API and salts with option BRINE (see 12.1.62): FI;
– for other tracers and salts, if polymer is used in a model (the keyword POLYMER,
see 12.1.51): EXP;
– TRACERLOOP – the time step for the solution of the equation of tracer mass
conservation is equal to the ratio of the model time step and the tracer half–time
period.

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.12. TRACEROPTS 1053

Keywords for formats tN, E1, E3 19.1

12.7.13. TRMMULTC

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets the dependence between absolute permeability multiplier and tracer con-
centration (kconc in 2.16.2), for which the option of holding time calculation in the reservoir
is enabled, (keyword TRACERM, see 12.7.11).

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.14). Dependences between
absolute permeability multiplier and tracer concentration should be entered as a table and be
terminated with a slash /. All data should be terminated with a final slash /.

12.7.13. TRMMULTC 1054

Keywords for formats tN, E1, E3 19.1

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.13. TRMMULTC 1055

Keywords for formats tN, E1, E3 19.1

12.7.14. TRMMULTT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets the dependence between absolute permeability multiplier and holding
time in the reservoir (keyword TRACERM, see 12.7.11).

One should specify tracer name and the following data:

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.13). Dependences be-
tween absolute permeability multiplier and holding time should be entered as a table and be
terminated with a slash /. All 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.14. TRMMULTT 1056

Keywords for formats tN, E1, E3 19.1

12.7.15. TRMTEMP

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.16.2). The data should be terminated with a slash /.

One should specify tracer name and the following data:

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.15. TRMTEMP 1057

Keywords for formats tN, E1, E3 19.1

12.7.16. TRDCY

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets decay time of tracer. The tracer decay model is described in the section
2.17.2. This keyword can be set if the 4-th parameter of the keyword TRACERS (see 12.1.48)
is greater than 0. The keyword should be used in the form TRDCYXXX where XXX is tracer
name which is set via TRACER (see 12.7.10). The number of data lines must be equal to
the value of the 2-nd parameter of keyword TABDIMS (see 12.1.29). 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 terminated with 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.16. TRDCY 1058

Keywords for formats tN, E1, E3 19.1

12.7.17. TRADS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets tracer adsorption by rock function as a table. Tracer adsorption model is
described in the section 2.17.3. This function can be set if the 4-th parameter of the keyword
TRACERS (see 12.1.48) is greater than 0. The keyword should be inputed as TRADSABC,
where ABC is the tracer name.
The number of tables is equal to the number of SAT regions (see the first parameter of
keyword TABDIMS, see 12.1.29). Each table should be ended by the symbol /.
The following parameters should be specified:

1. The local tracer concentration in the solution surrounding the rock. (In E1 models,
METRIC: kg/kg, FIELD: lb/lb; in E3 models, METRIC: kg-mol/kg-mol , FIELD:
lb-mol/lb-mol .) The values should increase monotonically down the column.

2. The corresponding saturated concentration of adsorbed tracer (In E1 models, METRIC:

kg/kg, FIELD: lb/lb; in E3 models, METRIC: kg-mol/kg, FIELD: lb-mol/lb.) The
values also should increase monotonically down the column.

In the first line values of both parameters should be 0.

Note. Besides black-oil models, this keyword can be used in compositional isothermal
models with one-component water in E3 format. In such models tracer can be connected to
water only, not other components.
Example
TRADSSR1
.00 .0000
.03 .0003
.05 .0005
.08 .0008
.10 .0010 /
In the example adsorption function for tracer SR1 is set.

12.7.17. TRADS 1059

Keywords for formats tN, E1, E3 19.1

12.8. EOR: Enhanced Oil Recovery

This section contains keywords for EOR (Enhanced Oil Recovery) methods:

• Hydraulic fracture (section 5.7.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.22): keywords ALSURFST (see 12.8.38), ALSUR-

FAD (see 12.8.39), ALPOLADS (see 12.8.40), ALKADS (see 12.8.41), ALKROCK
(see 12.8.42);

• Surfactant injection (section 2.23): keywords SOCRS (see 12.8.8), SURFADS

(see 12.8.9), SURFST (see 12.8.10), SURFVISC (see 12.8.11), SURFCAPD (see 12.8.12),
SURFROCK (see 12.8.13), SURFADDW (see 12.8.14), SURFDW (see 12.8.15);

• Polymer injection (section 2.16): keywords PLYVISC (see 12.8.25), PLYADS

(see 12.8.26), PLYMAX (see 12.8.28), PLMIXPAR (see 12.8.29), PLYROCK (see 12.8.30).

These methods are considered within the ASP (Alkaline-Surfactant-Polymer flooding)

model. For the mathematical description, see 5.9. ASP model description.

12.8. EOR: Enhanced Oil Recovery 1060

Keywords for formats tN, E1, E3 19.1

12.8.1. NPROPANTS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keywords sets the number of proppants in the model. The data should be terminated
with a slash /.
The description of the mathematical model of hydraulic fracture in tNavigator is in the
section Modified well model (5.7).

Example
NPROPANTS
2/

In this example there are 2 proppants.

12.8.1. NPROPANTS 1061

Keywords for formats tN, E1, E3 19.1

12.8.2. PROPANTNAMES

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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 /.
The description of the mathematical model of hydraulic fracture in tNavigator is in the
section Modified well model (5.7).

Example
NPROPANTS
2/
PROPANTNAMES
'proppant 12/18' 'proppant 16/20'/

In this example 2 proppants are specified. 1-st proppant name is 'proppant 12/18', 2-nd
proppant name – 'proppant 16/20'.

12.8.2. PROPANTNAMES 1062

Keywords for formats tN, E1, E3 19.1

12.8.3. PROPANTTABLE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword sets the table of relation between pressure and proppant permeability.

The description of the mathematical model of hydraulic fracture in tNavigator is in the

section Modified well model (5.7).

The number of columns of this table depends on the number of proppants (keyword
NPROPANTS, see 12.8.1).
One table row consists of the following parameters:

1. pressure (FIELD: psi, METRIC: bar);

2. proppant permeability (proppant 1) at this pressure (mD);

3. proppant permeability (proppant 2) at this pressure (mD);

4. ...

5. proppant permeability (proppant NPROPANTS) at this pressure (mD).

An arbitrary number of table rows could be specified with different pressures. The data
should be terminated with a slash /.

Default: Pressure values couldn’t be defaulted.

Permeability values couldn’t 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 proppants (pressure of fraction closing).

12.8.3. PROPANTTABLE 1063

Keywords for formats tN, E1, E3 19.1

Example
NPROPANTS
2/
PROPANTNAMES
'proppant 12/18' 'proppant 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 'proppant 12/18', 2-nd
proppant name – 'proppant 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 1064

Keywords for formats tN, E1, E3 19.1

12.8.4. FLOWFUNC

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies the coefficients of flow functions (the dependence between perme-
ability and flow (or time) in the model 5.7.7).

The description of the mathematical model of hydraulic fracture in tNavigator is in the

section Modified well model (5.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;

2. f (s) ≥ 0 for all s.

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 1065

Keywords for formats tN, E1, E3 19.1

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
terminated with a slash /.

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 1066

Keywords for formats tN, E1, E3 19.1

12.8.5. NFLOWFTB

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies the number of tabular flow functions f (s) (the dependence be-
tween permeability and flow (or time) in the model 5.7.7). The data should be terminated with
a slash /.

The description of the mathematical model of hydraulic fracture in tNavigator is in the

section Modified well model (5.7).

Function f (s) is the following:

1. f (0) = 1;

2. f (s) ≥ 0 for all s.

Example
NFLOWFTB
2 /

In this example there are 2 tabular flow functions.

12.8.5. NFLOWFTB 1067

Keywords for formats tN, E1, E3 19.1

12.8.6. FLOWFNAMES

Data x tN E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.7.7).

The description of the mathematical model of hydraulic fracture in tNavigator is in the

section Modified well model (5.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 1068

Keywords for formats tN, E1, E3 19.1

12.8.7. FLOWFTAB

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies the table of flow functions (the dependence between permeability
and flow (or time) in the model 5.7.7).

The description of the mathematical model of hydraulic fracture in tNavigator is in the

section Modified well model (5.7).

Function f (s) is the following:

1. f (0) = 1;

2. f (s) ≥ 0 for all s.

The number of table columns depends on the number of flow functions in the model (the
keyword NFLOWFTB, see 12.8.5).

One table row consists of the following parameters:

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.
The data should be terminated with a slash /.

Default: Argument s values couldn’t be defaulted.

Function values couldn’t 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 1069

Keywords for formats tN, E1, E3 19.1

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 1070

Keywords for formats tN, E1, E3 19.1

12.8.8. SOCRS

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword defines the scaled critical oil-in-water saturations at miscible conditions us-
ing for scaling of end points of saturation tables for miscible regions defined by SURFNUM
(see 12.4.4) for the surfactant injection simulation (see section 2.23).

This keyword acts in miscible regions SURFNUM (see 12.4.4) in the similar way as key-
word SOWCR (see 12.6.31) acts in immiscible regions SATNUM (see 12.4.3).
Keyword can be used only if ENDSCALE (see 12.1.136) is in the data file. In each block
the scaled critical oil-in-water saturation should be defined. The value of scaled saturation
varies from 0 to 1. The data should be terminated with a slash /.
Example
SOCRS
33712*0.5 /

In this example the scaled critical oil-in-water saturation is equal to 0.5 in all blocks and
does not depend on scaling direction (if it is active).

12.8.8. SOCRS 1071

Keywords for formats tN, E1, E3 19.1

12.8.9. SURFADS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies surfactant adsorption functions (for more details on surfactants, see
section 2.23).
Alkaline reduces surfactant adsorption (alkaline flooding – section 2.22).

This is a part of ASP (Alkaline-Surfactant-Polymer flooding) model. For the mathematical

description, see 5.9. ASP model description.
The number of specified tables should be equal to the number of saturation tables (first
parameter of the keyword TABDIMS, see 12.1.29). 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) for models in E1 format, (METRIC: kg-mol/kg,
FIELD: lb-mol/lb) for models in E3 format.

(The first row of the table should contain two zeroes.)

Note. Besides models in E1 format, this keyword can be used in compositional isothermal
models with one-component water in E3 format.
Example
SURFADS
.000 .000
.0023 .00045
.0065 .00067
.0078 .00078
.00110 .00082 /

12.8.9. SURFADS 1072

Keywords for formats tN, E1, E3 19.1

12.8.10. SURFST

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies the table of water-oil surface tension as a function of surfactant
concentration in water (SURFACT (see 12.1.49) – section 2.23). Surfactant affects on water-oil
surface tension in combination with alkaline (alkaline flooding – section 2.22).

This is a part of ASP (Alkaline-Surfactant-Polymer flooding) model. For the mathematical

description, see 5.9. ASP model description.
The number of specified tables should be equal to the number of PVT regions (second
parameter of the keyword TABDIMS, see 12.1.29). Each table should be terminated with a
slash /.

One table row contains the following parameters:

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.10. SURFST 1073

Keywords for formats tN, E1, E3 19.1

12.8.11. SURFVISC

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword specifies the table of water solution viscosity as a function of surfactant
concentration (SURFACT (see 12.1.49) – section 2.23).

This is a part of ASP (Alkaline-Surfactant-Polymer flooding) model. For the mathematical

description, see 5.9. ASP model description.
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.25).

The number of specified tables should be equal to the number of PVT regions (second
parameter of the keyword TABDIMS, see 12.1.29). Each table should be terminated with a
slash /.

One table row contains the following parameters:

1. surfactant concentration in the solution (METRIC: kg/sm3 , FIELD: lb/stb);

2. water solution viscosity at this surfactant concentration and the reference pressure, spec-
ified 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 /

In this example there are 2 tables.

12.8.11. SURFVISC 1074

Keywords for formats tN, E1, E3 19.1

12.8.12. SURFCAPD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies the surfactant capillary de-saturation functions (surfactant – section
2.23). This function describes the transition between immiscible conditions (at low surfactant
concentration) and miscibility conditions (at high surfactant concentration).

This is a part of ASP (Alkaline-Surfactant-Polymer flooding) model. For the mathematical

description, see 5.9. ASP model description.
The number of specified tables should be equal to the number of saturation tables (first
parameter of the keyword TABDIMS, see 12.1.29). Each table should be terminated with a
slash /.

One table row contains the following parameters:

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.12. SURFCAPD 1075

Keywords for formats tN, E1, E3 19.1

12.8.13. SURFROCK

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies the surfactant-rock properties (for more details on surfactants, see
section 2.23).

This is a part of ASP (Alkaline-Surfactant-Polymer flooding) model. For the mathematical

description, see 5.9. ASP model description.
The number of specified tables should be equal to the number of saturation tables (first
parameter of the keyword TABDIMS, see 12.1.29). Each table should be terminated with a
slash /.

The table contains 2 parameters:

1. desorption index:

• 1 – ASP desorption is on;

• 2 – ASP desorption 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 /
In this example there are 3 tables.

12.8.13. SURFROCK 1076

Keywords for formats tN, E1, E3 19.1

12.8.14. SURFADDW

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies the coefficient that is used in RP calculations as weighted average
of the oil-wettability value and of the water-wettability value (For more details on surfactants,
see section 2.23).

The number of specified tables should be equal to the number of saturation tables (first
parameter of the keyword TABDIMS, see 12.1.29). Each table should be terminated with a
slash /.
If a table is defaulted (/is used instead of table), then all its values are copied from previ-
ous table.

The table contains 2 parameters:

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).

The keyword SURFDW (see 12.8.15) can be used instead of the keyword SURFADDW
(see 12.8.14). In the keyword SURFDW (see 12.8.15): F – function of the concentration of
dissolved (in the water) surfactant in grid block.
In SURFADDW (see 12.8.14): F – function of adsorbed surfactant concentration in grid block.
In case of table SURFDW (see 12.8.15) 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 SUR-
FADDW (see 12.8.14) adsorbed surfactant affects all three phases RP.

Example
SURFADDW
0.0 1.0
0.0001 0.5
0.001 0.2
/
0.0 1.0
0.001 0.3
/

In this example there are 2 tables.

12.8.14. SURFADDW 1077

Keywords for formats tN, E1, E3 19.1

12.8.15. SURFDW

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies the coefficient that is used in RP calculations as weighted average
of the oil-wettability value and of the water-wettability value (For more details on surfactants,
see section 2.23).

The number of specified tables should be equal to the number of saturation tables (first
parameter of the keyword TABDIMS, see 12.1.29). Each table should be terminated with a
slash /.
If a table is defaulted (/is used instead of table), then all its values are copied from previ-
ous table.

The table contains 2 parameters:

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).
The keyword SURFDW (see 12.8.15) can be used instead of the keyword SURFADDW
(see 12.8.14). In the keyword SURFDW (see 12.8.15): F – function of the concentration of
dissolved (in the water) surfactant in grid block.
In SURFADDW (see 12.8.14): F – function of adsorbed surfactant concentration in grid block.
In case of table SURFDW (see 12.8.15) 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 SUR-
FADDW (see 12.8.14) adsorbed surfactant affects all three phases RP.

Example
SURFDW
0.0 1.0
0.01 0.5
0.1 0.2
/
0.0 1.0
0.1 0.3
/

In this example there are 2 tables.

12.8.15. SURFDW 1078

Keywords for formats tN, E1, E3 19.1

12.8.16. SURFSTES

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets surface tension in oil-water system dependence on surfactant (see section
2.23) and salt concentrations as a table. This keyword can be used only with option BRINE
(see 12.1.62).
The number of tables is set by the 2-nd parameter of keyword TABDIMS (see 12.1.29).
Each table consists of data sets, the number of which shouldn’t exceed the value of the 4-th
parameter of the keyword TABDIMS (see 12.1.29). 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.5).
The following parameters should be specified:

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).

12.8.16. SURFSTES 1079

Keywords for formats tN, E1, E3 19.1

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 /
/
In the example surface tension in oil-water system dependence on surfactant and salt
concentrations is set.

12.8.16. SURFSTES 1080

Keywords for formats tN, E1, E3 19.1

12.8.17. SSWL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword allows to specify the connate water saturation (i.e., the smallest water satu-
ration in a water saturation function table) for miscible conditions in each grid block, which
can be used for scaling the oil relative permeability to water and gas in modelling surfac-
tant injection. The keyword SSWL can be implemented if water is present in the model and
keywords ENDSCALE (see 12.1.136) (the end–point scaling methods are described in 2.6.7,
2.6.8, 2.11.4) and SURFACT (see 12.1.49) (surfactant option – 2.23) are specified.
The keyword is followed by one real number (the connate water saturation) for each grid
block. The saturation value can vary from 0 to 1 inclusive. The data should be terminated
with a slash /.
Grid blocks are in the following order: index cycles first along X-axis, then along the Y-
and Z-axis indices. Repeat counts may be used for repeated values (e.g., 64*0.1).
If the keyword SSWL is not specified for some or all of the grid blocks in a model, the
connate water saturations will be taken by default from appropriate relative permeability tables
via SURFNUM (see 12.4.4).
Example
DIMENS
4 4 4 /
ENDSCALE
/
SURFACT
...
SSWL
64*0.1/

In this example the connate water saturation is set equal to 0.1 in each grid blocks.

12.8.17. SSWL 1081

Keywords for formats tN, E1, E3 19.1

12.8.18. SSWCR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword allows to specify the critical water saturation (i.e., the highest water sat-
uration at which the water relative permeability is equal to zero) for miscible conditions in
each grid block, which can be used for scaling the surfactant water relative permeability in
modelling surfactant injection. The keyword SSWCR can be implemented if water is present
in the model and keywords ENDSCALE (see 12.1.136) (the end–point scaling methods are
described in 2.6.7, 2.6.8, 2.11.4) and SURFACT (see 12.1.49) (surfactant option – 2.23) are
specified.
The keyword SSWCR is followed by one real number (the critical water saturation) for
each grid block. The saturation value can vary from 0 to 1 inclusive. The data should be
terminated with a slash /.
Grid blocks are in the following order: index cycles first along X-axis, then along the Y-
and Z-axis indices. Repeat counts may be used for repeated values (e.g., 64*0.3).
If the keyword SSWCR is not specified for some or all of the grid blocks in a model, the
critical water saturations for calculations of the surfactant water relative permeability will be
taken by default from appropriate relative permeability tables via SURFNUM (see 12.4.4).
Example
DIMENS
4 4 4 /
ENDSCALE
/
SURFACT
...
SSWCR
64*0.3/

In this example the critical water saturation is set equal to 0.3 in each grid block.

12.8.18. SSWCR 1082

Keywords for formats tN, E1, E3 19.1

12.8.19. SSWU

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword allows to specify the maximum water saturation (i.e., the highest water
saturation in a water saturation function table) for miscible conditions in each grid block,
which can be used for scaling the surfactant water relative permeability in modelling surfactant
injection. The keyword SSWU can be implemented if water is present in the model and
keywords ENDSCALE (see 12.1.136) (the end–point scaling methods are described in 2.6.7,
2.6.8, 2.11.4) and SURFACT (see 12.1.49) (surfactant option – 2.23) are specified.
The keyword SSWU is followed by one real number (the maximum water saturation) for
each grid block. The saturation value can vary from 0 to 1 inclusive. The data should be
terminated with a slash /.
Grid blocks are in the following order: index cycles first along X-axis, then along the Y-
and Z-axis indices. Repeat counts may be used for repeated values (e.g., 64*0.8).
If the keyword SSWU is not specified for some or all of the grid blocks in a model, the
maximum water saturations for calculations of the surfactant water relative permeability will
be taken by default from appropriate relative permeability tables via SURFNUM (see 12.4.4).
Example
DIMENS
4 4 4 /
ENDSCALE
/
SURFACT
...
SSWU
64*0.8/

In this example the maximum water saturation is set equal to 0.8 in each grid block.

12.8.19. SSWU 1083

Keywords for formats tN, E1, E3 19.1

12.8.20. SSOWCR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword allows to specify the critical oil in water saturation (i.e., the highest oil
saturation at which the oil relative permeability to water is zero) for miscible conditions in
each grid block, which can be used for scaling the surfactant oil relative permeability to water
in modelling surfactant injection. The keyword SSOWCR can be implemented if water and
oil are present in the model and keywords ENDSCALE (see 12.1.136) (the end–point scaling
methods are described in 2.6.7, 2.6.8, 2.11.4) and SURFACT (see 12.1.49) (surfactant option
– 2.23) are specified.
The keyword SSOWCR is followed by one real number (the critical oil in water saturation)
for each grid block. The saturation value can vary from 0 to 1 inclusive. The data should be
terminated with a slash /.
Grid blocks are in the following order: index cycles first along X-axis, then along the Y-
and Z-axis indices. Repeat counts may be used for repeated values (e.g., 64*0.4).
If the keyword SSOWCR is not specified for some or all of the grid blocks in a model,
the critical oil in water saturations for calculations of the surfactant relative permeability to
water will be taken by default from appropriate relative permeability tables via SURFNUM
(see 12.4.4).
Example
DIMENS
4 4 4 /
ENDSCALE
/
SURFACT
...
SSOWCR
64*0.4/

In this example the critical oil in water saturation is set equal to 0.4 in each grid block.

12.8.20. SSOWCR 1084

Keywords for formats tN, E1, E3 19.1

12.8.21. SKRW

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword allows to specify the value of water relative permeability at the maxi-
mum water saturation for miscible conditions in each grid block, which can be used for
scaling the surfactant water relative permeability in modelling surfactant injection. The key-
word SKRW can be implemented if water is present in the model and keywords ENDSCALE
(see 12.1.136) (the end–point scaling methods are described in 2.6.7, 2.6.8, 2.11.4) and SUR-
FACT (see 12.1.49) (surfactant option – 2.23) are specified.
The keyword SKRW is followed by one real number (the value of water relative perme-
ability at the maximum water saturation) for each grid block. The data should be terminated
with a slash /.
Grid blocks are in the following order: index cycles first along X-axis, then along the Y-
and Z-axis indices. Repeat counts may be used for repeated values (e.g., 64*0.4).
If the keyword SKRW is not specified for some or all of the grid blocks in a model, water
relative permeabilities at maximum water saturation will be taken by default from appropriate
relative permeability tables via SURFNUM (see 12.4.4).
Example
DIMENS
4 4 4 /
ENDSCALE
/
SURFACT
...
SKRW
64*0.4/

In this example the value of water relative permeability at the maximum water saturation
is set equal to 0.4 in each grid block.

12.8.21. SKRW 1085

Keywords for formats tN, E1, E3 19.1

12.8.22. SKRWR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword allows to specify the value of water relative permeability at the critical oil
saturation for miscible conditions in each grid block, which can be used for scaling the surfac-
tant water relative permeability in modelling surfactant injection. The keyword SKRWR can
be implemented if water is present in the model and keywords ENDSCALE (see 12.1.136) (the
end–point scaling methods are described in 2.6.7, 2.6.8, 2.11.4) and SURFACT (see 12.1.49)
(surfactant option – 2.23) are specified.
The keyword SKRWR is followed by one real number (the value of water relative perme-
ability at the critical oil saturation) for each grid block. The data should be terminated with a
slash /.
Grid blocks are in the following order: index cycles first along X-axis, then along the Y-
and Z-axis indices. Repeat counts may be used for repeated values (e.g., 64*0.2).
If the keyword SKRWR is not specified for some or all of the grid blocks in a model,
water relative permeabilities at critical oil saturation will be taken by default from appropriate
relative permeability tables via SURFNUM (see 12.4.4).
Example
DIMENS
4 4 4 /
ENDSCALE
/
SURFACT
...
SKRWR
64*0.2/

In this example the value of water relative permeability at the critical oil saturation is set
equal to 0.2 in each grid block.

12.8.22. SKRWR 1086

Keywords for formats tN, E1, E3 19.1

12.8.23. SKRO

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword allows to specify the value of oil relative permeability at the maximum
oil saturation for miscible conditions in each grid block, which can be used for scaling the
surfactant oil relative permeability in modelling surfactant injection. The keyword SKRO can
be implemented if oil is present in the model and keywords ENDSCALE (see 12.1.136) (the
end–point scaling methods are described in 2.6.7, 2.6.8, 2.11.4) and SURFACT (see 12.1.49)
(surfactant option – 2.23) are specified.
The keyword SKRO is followed by one real number (the maximum oil relative permeabil-
ity) for each grid block. The data should be terminated with a slash /.
Grid blocks are in the following order: index cycles first along X-axis, then along the Y-
and Z-axis indices. Repeat counts may be used for repeated values (e.g., 64*0.8).
If the keyword SKRO is not specified for some or all of the grid blocks in a model, oil
relative permeabilities at maximum oil saturation will be taken by default from appropriate
relative permeability tables via SURFNUM (see 12.4.4).
Example
DIMENS
4 4 4 /
ENDSCALE
/
SURFACT
...
SKRO
64*0.8/

In this example the value of oil relative permeability at the maximum oil saturation is set
equal to 0.8 in each grid block.

12.8.23. SKRO 1087

Keywords for formats tN, E1, E3 19.1

12.8.24. SKRORW

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword allows to specify the value of oil relative permeability at the critical wa-
ter saturation for miscible conditions in each grid block, which can be used for scaling the
surfactant oil relative permeability in modelling surfactant injection. The keyword SKRORW
can be implemented if oil and water are present in the model and keywords ENDSCALE
(see 12.1.136) (the end–point scaling methods are described in 2.6.7, 2.6.8, 2.11.4) and SUR-
FACT (see 12.1.49) (surfactant option – 2.23) are specified.
The keyword SKRORW is followed by one real number (the value of oil relative perme-
ability at the critical water saturation) for each grid block. The data should be terminated with
a slash /.
Grid blocks are in the following order: index cycles first along X-axis, then along the Y-
and Z-axis indices. Repeat counts may be used for repeated values (e.g., 64*0.5).
If the keyword SKRORW is not specified for some or all of the grid blocks in a model,
oil relative permeabilities at critical water saturation will be taken by default from appropriate
relative permeability tables via SURFNUM (see 12.4.4).
Example
DIMENS
4 4 4 /
ENDSCALE
/
SURFACT
...
SKRORW
64*0.5/

In this example the value of oil relative permeability at the critical water saturation is set
equal to 0.5 in each grid block.

12.8.24. SKRORW 1088

Keywords for formats tN, E1, E3 19.1

12.8.25. PLYVISC

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword specify the multiplier for water viscosity as a function of polymer concen-
tration (Polymer Flood is described in the section 2.16).

This is a part of ASP (Alkaline-Surfactant-Polymer flooding) model. For the mathematical

description, see 5.9. ASP model description.
If surfactant injection is used then the viscosity value, specified with SURFVISC
(see 12.8.11), is multiplied by polymer viscosity multiplier, specified by PLYVISC
(see 12.8.25).

The number of specified tables should be equal to the number of PVT regions (second
parameter of the keyword TABDIMS, see 12.1.29). Each table should be terminated with a
slash /.

One table row contains the following parameters:

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.25. PLYVISC 1089

Keywords for formats tN, E1, E3 19.1

12.8.26. PLYADS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies polymer adsorption functions (Polymer Flood is described in the
section 2.16).
Polymer adsorption can be reduced in the case of alkaline injection (alkaline – section 2.22).

This is a part of ASP (Alkaline-Surfactant-Polymer flooding) model. For the mathematical

description, see 5.9. ASP model description.
The number of specified tables should be equal to the number of saturation tables (first
parameter of the keyword TABDIMS, see 12.1.29). Each table should be terminated with a
slash /.

One table row contains the following parameters:

1. polymer concentration in the solution (METRIC: kg/sm3 , FIELD: lb/stb);

2. corresponding saturated concentration of polymer adsorbed by the rock formation (MET-

RIC: kg/kg, FIELD: lb/lb) for models in E1 format, (METRIC: kg-mol/kg, FIELD:
lb-mol/lb) for models in E3 format.

(The first row of the table should contain two zeroes)

Note. Besides models in E1 format, this keyword can be used in compositional isothermal
models with one-component water in E3 format.
Example
PLYADS
.0000 .00000
.0005 .00009
.0012 .00020 /

12.8.26. PLYADS 1090

Keywords for formats tN, E1, E3 19.1

12.8.27. PLYADSS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies polymer adsorption functions varying with salinity (Polymer Flood
is described in the section 2.16).
Polymer adsorption can be reduced in the case of alkaline injection (alkaline – section 2.22).

This is a part of ASP (Alkaline-Surfactant-Polymer flooding) model. For the mathematical

description, see 5.9. ASP model description.
The number of specified tables should be equal to the number of saturation regions (first
parameter of keyword TABDIMS, see 12.1.29). Tables consist of data sets. The number of
data sets in one table should not be greater than the value of the 3-rd parameter of TAB-
DIMS (see 12.1.29). Each data set should be terminated with a slash /. Each table should be
terminated with a slash /.
First table row contains the following parameters:

1. polymer concentration in the solution (METRIC: kg/sm3 , FIELD: lb/stb) for models
in E1 format, (METRIC: kg-mol/kg, FIELD: lb-mol/lb) for models in E3 format;

2. corresponding saturated concentration of polymer adsorbed by the rock formation (MET-

RIC: kg/kg, FIELD: lb/lb). This function depends on the first parameter of the first
line and the first parameter of keyword ADSALNOD (see 12.7.4) in corresponding table.

The first row of the table should contain two zeroes.

In all next lines one parameter should be specified:

1. polymer concentration function value, which is adsorbed by rock (METRIC: kg/kg,

FIELD: lb/lb). This function depends on the first parameter of the first line and the nth
parameter of the keyword ADSALNOD (see 12.7.4) in corresponding table, where n is
a number of current line.

The number of lines in each table must be equal to the number of values in corresponding
table specified in keyword ADSALNOD (see 12.7.4).

12.8.27. PLYADSS 1091

Keywords for formats tN, E1, E3 19.1

Example
PLYADSS
0 0
0
0
0 /
0.347001516 1.69913E-05
2.69913E-05
3.69913E-05
4.69913E-05 /
/
In the example polymer adsorption function is set. One table and two data sets are set.
Polymer concentration in the solution takes two values – 0 and 0.347001516. Four values of
salt concentration are set by keyword ADSALNOD (see 12.7.4), that is why there are four
lines in the table as well.

12.8.27. PLYADSS 1092

Keywords for formats tN, E1, E3 19.1

12.8.28. PLYMAX

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keywords is used to specify polymer and salt concentrations for mixing calculations
(Polymer Flood is described in the section 2.16).

This is a part of ASP (Alkaline-Surfactant-Polymer flooding) model. For the mathematical

description, see 5.9. ASP model description.
The number of specified tables should be equal to the 10-th parameter of REGDIMS
(see 12.1.32) (the number of regions with different polymer properties).
Each table should be terminated with a slash /.

One table row contains the following parameters:

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.62).

Example
PLYMAX
15.8 7.5/

In this example one table is entered.

12.8.28. PLYMAX 1093

Keywords for formats tN, E1, E3 19.1

12.8.29. PLMIXPAR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies the Todd-Longstaff mixing parameter for the viscosity calculation
in the case of Polymer Flood (POLYMER (see 12.1.51) – section 2.16).

This is a part of ASP (Alkaline-Surfactant-Polymer flooding) model. For the mathematical

description, see 5.9. ASP model description.
The number of specified tables should be equal to the 10-th parameter of REGDIMS
(see 12.1.32) (the number of regions with different polymer properties).
Each table should be terminated with a slash /.

One table row contains the following parameters:

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.29. PLMIXPAR 1094

Keywords for formats tN, E1, E3 19.1

12.8.30. PLYROCK

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies rock properties for Polymer Flood (Polymer Flood is described in
the section 2.16).

This is a part of ASP (Alkaline-Surfactant-Polymer flooding) model. For the mathematical

description, see 5.9. ASP model description.
The number of specified tables should be equal to the number of saturation tables (first
parameter of the keyword TABDIMS, see 12.1.29). Each table should be terminated with a
slash /.

One table row contains the following parameters:

1. dead pore space (the value shouldn’t 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 calcu-
lations 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);
Default: 1.

5. maximum polymer adsorption value (METRIC: kg/kg, FIELD: lb/lb).

Example
PLYROCK
0.14 1.3 2115 2 0.0004 /

In this example one table is entered.

12.8.30. PLYROCK 1095

Keywords for formats tN, E1, E3 19.1

12.8.31. PLYKRRF

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies the residual resistance factor for use in the Polymer Flood Model
(see 2.16. Polymer Flood for the physical details). This is a part of ASP (Alkaline-Surfactant-
Polymer flooding) model. For the mathematical description, see 5.9. ASP model description.
The factor represents the decrease in the water permeability when the maximum polymer
adsorption is reached.
This keyword is followed by a series of real numbers, one for each grid block in the
current input box. Values must be greater than or equal to 1. The data should be terminated
with a slash /.
Blocks which are not affected by this keyword use the corresponding value set by the
second parameter of the PLYROCK (see 12.8.30) keyword.
Example
BOX
11 20 11 20 21 20 /
PLYKRRF
1000*1.65 /
In this example the values are specified within a box of the size 10 × 10 × 10 blocks.

12.8.31. PLYKRRF 1096

Keywords for formats tN, E1, E3 19.1

12.8.32. PLYSHEAR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies polymer shear thinning data (factor for polymer solution viscosity)
for Polymer Flood (section 2.16).

To set polymer shear via logarithmic formula use the keyword PLYSHLOG (see 12.8.33).
This is a part of ASP (Alkaline-Surfactant-Polymer flooding) model. For the mathematical
description, see 5.9. ASP model description.
The number of specified tables should be equal to the number of PVT regions (second
parameter of the keyword TABDIMS, see 12.1.29). Each table should be terminated with a
slash /.

One table row contains the following parameters:

1. water phase flow velocity (taking shear correction into account) (METRIC: m/day,
FIELD: f t/day).

2. factor by which the water and polymer (specified by PVTW (see 12.5.5), PLYVISC,
see 12.8.25) is modified due to shear thinning/thickening of the polymer.
The resulting shear viscosity of the water and polymer (for a given polymer concentration
and flow velocity) is calculated via the formula:
 
1 + (B − 1)F
µW,sh = µW,e
B
 
1 + (B − 1)F
µ poly,sh = µ poly,e
B
where:
• µW,sh , µ poly,sh – shear water viscosity, shear polymer viscosity;

• µW,e , µ poly,e – effective water viscosity, effective polymer viscosity;

• B – viscosity multiplier without shear effect, specified via PLYVISC (see 12.8.25);

• F – viscosity multiplier with shear effect, specified via this keyword.

If F = 1 (should be entered in the first table row), then µW,sh = µW,e , µ poly,sh = µ poly,e .
µ µ poly,e
If F = 0, then µW,sh = W,e
B , µ poly,sh = B .

12.8.32. PLYSHEAR 1097

Keywords for formats tN, E1, E3 19.1

Example
PLYSHEAR
0.00 1.00
4.45 0.60
7.00 0.55 /

12.8.32. PLYSHEAR 1098

Keywords for formats tN, E1, E3 19.1

12.8.33. PLYSHLOG

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets polymer shear thinning/thickening (via logarithmic formula) for Poly-
mer Flood (section 2.16).

To set polymer shear via factor for polymer solution viscosity use the keyword PLYSHEAR
(see 12.8.32).
If the keyword SHRATE (see 12.8.34) is defined then the multiplier is used instead a table
as a function of water/polymer flow shear rate.

The following parameters should be specified:

• 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 (see SHRATE, see 12.8.34) (units for
velocity – METRIC: m/day, FIELD: f t/day; units for shear rate – 1/day). The
values must increase monotonically 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.29). The number of tables is equal to the value of
2-nd parameter of TABDIMS (see 12.1.29). The data should be terminated with a slash
/.

12.8.33. PLYSHLOG 1099

Keywords for formats tN, E1, E3 19.1

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
/
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.33. PLYSHLOG 1100

Keywords for formats tN, E1, E3 19.1

12.8.34. SHRATE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword allows to define shear rate form and the shear rate constant for a polymer
shear thinning/thickening in logarithmic form. This keyword can be used if only the keyword
PLYSHLOG (see 12.8.33) is defined.
The number of specified tables should be equal to the number of PVT regions (second
parameter of the keyword TABDIMS, see 12.1.29). Each PVT region corresponds to its shear
rate constant. Each table should be terminated with a slash /. Furthermore, the shear rate
constants should be positive.
Default: 4.8.

Using a relationship between the apparent viscosity and the Darcy velocity for the power-
law fluid in porous media the shear rate constant can be calculated as:
  n
3n + 1 n−1
Cγ = C
4n
where C is the constant and equal to 6, n is the index, equal to 0.5. Substituting these values
into the formula above the default shear rate constant is equal to 4.8.
Example
SHRATE
0.1/

12.8.34. SHRATE 1101

Keywords for formats tN, E1, E3 19.1

12.8.35. PLYVISCT

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets polymer viscosity multiplier functions via tables. These functions de-
scribe the effect of increasing temperature on the viscosity of pure water. The number of tables
should be equal to the value of the 2-nd parameter of the keyword TABDIMS (see 12.1.29).
The number of records in each table and the number of lines in each record shouldn’t exceed
value of the 4-th parameter of the keyword TABDIMS (see 12.1.29).
This keyword should be used only in conjunction with the temperature option (see the
keyword TEMP (see 12.1.64) and section 2.26).
Polymer flooding option – see 2.16.1.
The first line of each table entry contains the following:

1. the polymer concentration in the solution (METRIC: kg/sm3 , FIELD: lb/stb). The
values should increase monotonically, the first one should be equal to 0;

2. the corresponding water viscosity multiplier (viscosity values are set by PVTW,
see 12.5.5). Obtained value is the value of solution viscosity at specified polymer
concentration and temperature value which is set in the first line of the correspond-
ing record of TEMPNODE (see 12.8.37).

The others lines of each record contains only water viscosity multipliers. Obtained value
is the value of solution viscosity at specified polymer concentration (1-st parameter) and tem-
perature value which is set in the corresponding line and record of TEMPNODE (see 12.8.37).
Each record should be ended by the symbol /. Each table should be ended by the symbol
/.

12.8.35. PLYVISCT 1102

Keywords for formats tN, E1, E3 19.1

Example
PLYVISCT
0.0 1.0
1.0
1.0
1.0 /
10.0 10.0
8.0
6.0
4.0 /
30.0 25.0
20.0
15.0
10.0 /
70.0 50.0
30.0
20.0
12.0 /
/
In the example one table of viscosity multipliers is set. It has 4 records, each record has
4 lines. At zero polymer concentration (first parameter of the first line) and each of four
temperature values set by TEMPNODE (see 12.8.37) viscosity multiplier is 1.

12.8.35. PLYVISCT 1103

Keywords for formats tN, E1, E3 19.1

12.8.36. PLYVSCST

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword specifies viscosity multipliers as function of concentration of polymer and

salt in the solution, and the temperature of the solution in table form.
This keyword can be used for polymer studies (see section 2.16.1) when the brine tracking
option option has been activated (keyword BRINE (see 12.1.62), see section 2.24.1) and when
the temperature option has been activated (keyword TEMP (see 12.1.64), see section 2.26).
The number of tables should be equal to the value of the 2-nd parameter of the keyword
TABDIMS (see 12.1.29). Each table is terminated by a symbol /. The number of records in
each table is equal to the product of the number of polymer concentrations and the number
of salt concentrations (specified by keyword SALTNODE, see 12.7.3) and the number of
temperature points (specified by keyword TEMPNODE, see 12.8.37).
The first line of each table entry contains the following:

1. the polymer concentration in the solution (METRIC: kg/sm3 , FIELD: lb/stb). The
values should increase monotonically, the first one should be equal to 0;

2. the corresponding water viscosity multiplier. Obtained value is the value of solution
viscosity at specified polymer concentration, salt concentration which is set in the first
line of the corresponding record of SALTNODE (see 12.7.3) and temperature value
which is set in the first line of the corresponding record of TEMPNODE (see 12.8.37).

The set of records for one polymer concentration is terminated by a symbol / at new line.
In the example one table of viscosity multipliers is set. It has 3 records for each polymer
concentrations (0.0, 0.5 and 1). Each record has 3 recods corresponding to the number of
salt concentrations specified by SALTNODE (see 12.7.3) (7.01, 10.515 and 14.02). Each of
this record consists of three lines corresponding to the number of temperature nodes set
by TEMPNODE (see 12.8.37) (70, 125 and 200). Each line contains one value of viscosity
multiplier. At zero polymer concentration (first parameter of the first line) and the first salt
concentration and the first temperature value viscosity multiplier is 1.

12.8.36. PLYVSCST 1104

Keywords for formats tN, E1, E3 19.1

Example
TEMPNODE
70
125
200 /
SALTNODE
7.01
10.515
14.02 /
PLYVSCST
0.0 1.0
2.0
3.0 /
1.0
2.0
3.0 /
1.0
2.0
3.0 /
/
0.5 5
10
14 /
4
9
13 /
3
8
12 /
/
1.0 7
12
19 /
6
11
18 /
5
10
17 /
/
/

12.8.36. PLYVSCST 1105

Keywords for formats tN, E1, E3 19.1

12.8.37. TEMPNODE

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword set temperature values to calculate viscosity of polymer solution via tables.
It can be used only with the temperature option (see the keyword TEMP (see 12.1.64) and
section 2.26).
The number of tables should not exceed the value of the 2-nd parameter of the keyword
TABDIMS (see 12.1.29). The number of records in each table shouldn’t exceed the value of
the 4-th parameter of the keyword TABDIMS (see 12.1.29) and must be equal to the number
of records of the keyword PLYVISCT (see 12.8.35) or PLYVSCST (see 12.8.36).
The following parameters should be specified:

1. temperature values (METRIC: ◦ C, FIELD: ◦ F).

The data should be terminated with a slash /.

Example
TEMPNODE
50
100
150
200 /

12.8.37. TEMPNODE 1106

Keywords for formats tN, E1, E3 19.1

12.8.38. ALSURFST

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies oil-water surface tension multiplier as a function of alkaline con-
centration (Ast (Calkl ) in the section 2.22).

This is a part of ASP (Alkaline-Surfactant-Polymer flooding) model. For the mathematical

description, see 5.9. ASP model description.
The number of specified tables should be equal to the number of PVT regions (second
parameter of the keyword TABDIMS, see 12.1.29). Each table should be terminated with a
slash /. If the table is specified for default with /, then the values will be copied from the
previous specified table.

One table row contains the following parameters:

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.10).
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.38. ALSURFST 1107

Keywords for formats tN, E1, E3 19.1

12.8.39. ALSURFAD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies surfactant adsorption multiplier as a function of alkaline concen-

tration (Aad (Calkl ) in the section Alkaline Flooding – 2.22).

This is a part of ASP (Alkaline-Surfactant-Polymer flooding) model. For the mathematical

description, see 5.9. ASP model description.
The number of specified tables should be equal to the number of saturation regions (first
parameter of the keyword TABDIMS, see 12.1.29). Each table should be terminated with a
slash /. If the table is specified for default with /, then the values will be copied from the
previous specified table.

One table row contains the following parameters:

1. alkaline concentration in the grid block (METRIC: kg/sm3 , FIELD: lb/stb);

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 /
/

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.39. ALSURFAD 1108

Keywords for formats tN, E1, E3 19.1

12.8.40. ALPOLADS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies polymer adsorption multiplier as a function of alkaline concentra-

tion (Aad (Calkl ) in the section Alkaline Flooding – 2.22).

This is a part of ASP (Alkaline-Surfactant-Polymer flooding) model. For the mathematical

description, see 5.9. ASP model description.
The number of specified tables should be equal to the number of saturation regions (first
parameter of the keyword TABDIMS, see 12.1.29). Each table should be terminated with a
slash /. If the table is specified for default with /, then the values will be copied from the
previous specified table.

One table row contains the following parameters:

1. alkaline concentration in the grid block (METRIC: kg/sm3 , FIELD: lb/stb);

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 /
/

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.40. ALPOLADS 1109

Keywords for formats tN, E1, E3 19.1

12.8.41. ALKADS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies the alkaline adsorption functions (Alkaline Flooding – section
2.22).

This is a part of ASP (Alkaline-Surfactant-Polymer flooding) model. For the mathematical

description, see 5.9. ASP model description.
The number of specified tables should be equal to the number of saturation regions (first
parameter of the keyword TABDIMS, see 12.1.29). Each table should be terminated with a
slash /.

One table row contains the following parameters:

1. alkaline concentration in the grid block (METRIC: kg/sm3 , FIELD: lb/stb);

2. corresponding saturated concentration of alkaline adsorbed by the rock (METRIC:

kg/kg, FIELD: lb/lb) for models in E1 format, (METRIC: kg-mol/kg, FIELD:
lb-mol/lb) for models in E3 format.

(The first table row should contain two zeros.)

Note. Besides models in E1 format, this keyword can be used in compositional isothermal
models with one-component water in E3 format.
Example
ALKADS
0.00000 0.00000
0.00027 0.00005
0.00078 0.00007
0.00140 0.00011 /

12.8.41. ALKADS 1110

Keywords for formats tN, E1, E3 19.1

12.8.42. ALKROCK

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies the rock properties for alkaline adsorption – adsorption index (Al-
kaline Flooding – section 2.22).

This is a part of ASP (Alkaline-Surfactant-Polymer flooding) model. For the mathematical

description, see 5.9. ASP model description.
The number of adsorption indexes should be equal to the number of saturation regions
(first parameter of the keyword TABDIMS, see 12.1.29). 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.42. ALKROCK 1111

Keywords for formats tN, E1, E3 19.1

12.8.43. STVP

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets surface tension dependence on pressure value for miscible option (the
keyword MISCIBLE, see 12.1.69) as a table. For each PVT region its own SPVT table should
be set.
The data should be terminated with a slash /.

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.76),
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.43. STVP 1112

Keywords for formats tN, E1, E3 19.1

12.8.44. WAGHYSTR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets parameters of hysteresis model. It can be used only if hysteresis option
is activated (see the keyword SATOPTS, see 12.1.75).

The following parameters should be specified:

1. parameter C (Land’s 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, α ;

Default: 0.

3. gas model flag:

• YES - use hysteresis model for gas relative permeability;

• NO - turn off hysteresis model.
• Default: YES.

4. residual oil model flag. This is an E1/E3 compatibility field.

5. water model flag:

• YES - use hysteresis model for water relative permeability;

• NO - turn off hysteresis model.
• Default: YES.

6. imbibition curve linear part;

Default: 0.1.

12.8.44. WAGHYSTR 1113

Keywords for formats tN, E1, E3 19.1

7. three-phase model threshold saturation;

Default: 0.001.

8. residual oil modification fraction.

Default: 1.

The number of data lines must be equal to the number of filtration regions (1-st parameter of
the keyword TABDIMS, see 12.1.29). Each line should be ended by a symbol /.

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.44) sets parameters of hysteresis model
for 4 filtration regions. In each region hysteresis model for gas relative permeability is used.

12.8.44. WAGHYSTR 1114

Keywords for formats tN, E1, E3 19.1

12.8.45. WAGHALT

Data x tN E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies that an alternative model of WAG hysteresis (keyword

WAGHYSTR, see 12.8.44) should be used.
This keyword is ignored. This is an E1/E3 compatibility field. In tNavigator the WAG
hysteresis is always considered within the alernative model, as if WAGHALT were always on.

12.8.45. WAGHALT 1115

Keywords for formats tN, E1, E3 19.1

12.9. Coal Bed Methane properties

12.9.1. DIFFCOAL

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets gas diffusion data for Coal Bed Methane model (2.28).
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.32).

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;

Default: 1.

3. solvent diffusion coefficient (METRIC: m2 /day, FIELD: f t 2 /day).

Default: 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. Coal Bed Methane properties 1116

Keywords for formats tN, E1, E3 19.1

12.9.2. LANGMUIR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets the tables of coal surface gas concentration that is used in Coal Bed
Methane model (2.28).
The number of tables 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.32).
Each table should be terminated with a slash /.
The number of columns is equal 2 for black-oil models in E1 format and NCOMPS+1 for
compositional models in E3 format.

One table line contains the following parameters:

1. fracture pressure (METRIC: barsa, FIELD: psia); In the case of compositional model
in E3 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 E3 format this parameter sets corresponding
surface concentration of the first component;

3. in the case of compositional model in E3 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 1117

Keywords for formats tN, E1, E3 19.1

12.9.3. LANGMPL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keywords scales the pressure used for calculation of the adsorption capacity in the
cell when modelling the coal bed methane (see section 2.28).
After the keyword one value of multiplier for each grid block should be specified. The
data must be terminated by a slash /.
Only multiplier values specified for the coal cells (see keyword COALNUM, see 12.4.15)
will be used.
Example
DIMENS
10 10 2
/
...
LANGMPL
121*0.5 /

In this example pressure is multiplied by 0.5 in 121 grid cells for calculation of the
adsorption capacity.

12.9.3. LANGMPL 1118

Keywords for formats tN, E1, E3 19.1

12.9.4. LANGMULT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword sets multipliers of coal surface gas concentration that is used in Coal Bed
Methane model (2.28). Coal surface gas concentration is set via the keyword LANGMUIR
(see 12.9.2).
The following parameters should be specified:

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: 1.

The data should be terminated with a slash /.

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.4. LANGMULT 1119

Keywords for formats tN, E1, E3 19.1

12.9.5. MLANG

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword sets the maximum surface gas concentration that will be used for Lang-
muir Isotherm scaling. The scaling will be applied at the maximum fracture pressure entry in
LANGMUIR (see 12.9.2) table. The detailed description of Coal Bed Methane (CBM) model-
ing is provided in section 2.28.

A maximum value of surface gas concentration should be entered for each matrix block
of the grid or specified box (BOX, see 12.3.3). (METRIC: sm3 /m3 , FIELD: Msc f / f t 3 ).

The data entry must be terminated by a slash /.

Example
LANGMUIR
0 0.00
1 0.48
10 4.01
20 6.81
50 11.76
100 15.51
150 17.36
200 18.46
300 19.70
500 20.93
700 21.05

MLANG
500*17.85
/

In this example:
1. The Langmuir Isotherm is entered via LANGMUIR table;
2. The maximum fracture pressure will be taken from the last table’s line (700 bars);
3. The maximum surface gas concentration is set by MLANG keyword. This value will be
used for scaling;
4. The initial Langmuir table will be scaled and assigned the specified blocks.

12.9.5. MLANG 1120

Keywords for formats tN, E1, E3 19.1

12.9.6. LANGMEXT

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets extended Langmuir Isotherm for compositional models in Coal Bed
Methane simulation (2.28).
The number of data sets 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.32).

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). Pos-
itive number. Langmuir pressure constant can be zero if Langmuir volume constant is
zero;
Default: 0.

• Langmuir volume constant Vi for component i (METRIC: sm3 /kg, FIELD: Msc f /ton).
Non-negative number.
Default: 0.

The values pi and Vi specify the Langmuir curve for the component i.

12.9.6. LANGMEXT 1121

Keywords for formats tN, E1, E3 19.1

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.6. LANGMEXT 1122

Keywords for formats tN, E1, E3 19.1

12.9.7. DIFFCBM

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets the diffusion coefficients for each component that are used in Coal Bed
Methane model (2.28).
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.32).

Each data line should be terminated with the symbol /. All data should be terminated with
a final 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: 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.7. DIFFCBM 1123

Keywords for formats tN, E1, E3 19.1

12.9.8. RESORB

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets the readsorption factor for each component that are used in Coal Bed
Methane model (2.28).
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.32).

Each data line should be terminated with the symbol /. All data should be terminated with
a final 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: 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.8. RESORB 1124

Keywords for formats tN, E1, E3 19.1

12.10. Asphaltene properties

12.10.1. ASPP1P

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.21) is activated by the keyword ASPHALTE
(see 12.1.67). The following parameters should be specified:

1. variable:

• P – pressure;
• Z – total molar fraction.
• Default: P.

2. component number (this parameter is specified only if the first parameter is Z).

The data should be terminated with a slash /.

Example
ASPP1P
'P'/
Asphaltene precipitation is set as a function of pressure.

12.10. Asphaltene properties 1125

Keywords for formats tN, E1, E3 19.1

12.10.2. ASPREWG

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.21) is activated by the keyword
ASPHALTE (see 12.1.67). 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 /
The data should be terminated with a slash /.
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 1126

Keywords for formats tN, E1, E3 19.1

12.10.3. ASPP2P

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.21) is activated by
the keyword ASPHALTE (see 12.1.67). 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.

The data should be terminated with a slash /.

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 1127

Keywords for formats tN, E1, E3 19.1

12.10.4. ASPPW2D

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets fracture of molar weight dissolved in solution as a function of two vari-
ables: pressure and the molar fraction of component. The keyword ASPP2P (see 12.10.3)
should be used in conjunction with this keyword. These keywords can be used only if
asphaltene precipitation model option (see 2.21) is activated by the keyword ASPHALTE
(see 12.1.67).
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 molar weight fractures of asphaltene
dissolved in the oil phase (%) at these pressure and molar fraction values. The number of
fractures should be equal to the number of molar component fractures.
Each data line should be terminated with 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. At pressure
of 2000 psi and molar fraction of 0.015 molar weight fractures of asphaltene dissolved in the
oil phase is 5%.

12.10.4. ASPPW2D 1128

Keywords for formats tN, E1, E3 19.1

12.10.5. ASPFLRT

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets the kinetic reaction rates for the flocculation and dissociation processes
for flocs and fines. This keyword can be used only if asphaltene precipitation model option
(see 2.21) is activated by the keyword ASPHALTE (see 12.1.67). The following parameters
should be specified:

1. rates of the flocculation process (1/day);

2. rates of the dissociation process (1/day).

The data should be terminated with a slash /.

Example
ASPFLRT
0.01
0.001 /

12.10.5. ASPFLRT 1129

Keywords for formats tN, E1, E3 19.1

12.10.6. ASPLCRT

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is used to set properties of asphaltene plugging process. The following
parameters should be specified:

1. critical volume fraction of asphaltene deposit above which plugging can happen. The
volume fraction is measured as a proportion of the pore volume, and the critical solid
saturation;

2. critical asphaltene flocs molar concentration above which plugging can happen (MET-
RIC: kg-mol/rm3 ; FIELD: lb-mol/rb);

The data should be terminated with a slash /.

Example
ASPLCRT
0.002 1.e-4 /

12.10.6. ASPLCRT 1130

Keywords for formats tN, E1, E3 19.1

12.10.7. ASPVISO

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets parameters of oil viscosity change model in asphaltene precipitation run
(see 2.21). Asphaltene precipitation option is activated by keyword ASPHALTE (see 12.1.67),
model type is set also there. With respect to selected type the following parameters are set:

• Einstein model, EI:

1. slope coefficient of relative viscosity with respect to concentration.

• Krieger and Dougherty model, KD:

1. mass concentration at maximum packing;

2. intrinsic viscosity.

• table data, TAB. Two-column table:

1. the mass fraction of the asphaltene precipitate;

2. the oil viscosity multiplier.

The data should be terminated with a slash /.

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.7. ASPVISO 1131

Keywords for formats tN, E1, E3 19.1

12.10.8. ASPDEPO

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets properties of the asphaltene deposition process in asphaltene precipi-
tation run (see 2.21). Asphaltene precipitation option is activated by keyword ASPHALTE
(see 12.1.67), model type is set also there. The following parameters should be specified:

1. a static deposition or adsorption coefficient (METRIC: 1/day, FIELD: 1/day);

2. IGNORED, this is an E1/E3 compatibility field;

3. an entrainment coefficient (METRIC: 1/m, FIELD: 1/ f t );

4. a critical oil phase velocity above which entrainment takes place (METRIC: m/day,
FIELD: f t/day);

5. a plugging coefficient (METRIC: 1/m, FIELD: 1/ f t ).

The data should be terminated with a slash /.

Example
ASPDEPO
5.0E-4 1* 1.0E-4 2500 2.5E-5 /

12.10.8. ASPDEPO 1132

Keywords for formats tN, E1, E3 19.1

12.10.9. CATYPE

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.21 and keyword
ASPHALTE, see 12.1.67). The following parameters should be specified:

1. component property:

• PREC – component that can precipitate as asphaltene;

• FLOC – component that represents the flocculated asphaltene;
• NONE – component doesn’t participate in precipitation process.
• Default: NONE.

Only one property can be set for each component. Properties FLOC and PREC can be
assigned to only one component.

The data should be terminated with a slash /.

Example
CATYPE
5* PREC FLOC /
In the example the first five components don’t participate in precipitation process. The
6-th one can precipitate as asphaltene, the 7-th one is the flocculated asphaltene.

12.10.9. CATYPE 1133

Keywords for formats tN, E1, E3 19.1

12.11. Foam properties

12.11.1. FOAMADS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.29). Foam modeling option – 2.18.
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.29).
The data should be terminated with a slash /.
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. Foam properties 1134

Keywords for formats tN, E1, E3 19.1

12.11.2. FOAMOPTS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets foam modeling options. It can be used only if foam model option (see
2.18) is activated by the keyword FOAM (see 12.1.68). The following parameters should be
specified:

1. transport phase for foam:

• GAS – gas;
• WATER or WAT – water.
• Default: GAS.

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: TAB.

The data should be terminated with a slash /.

Example
FOAMOPTS
WATER TAB /

12.11.2. FOAMOPTS 1135

Keywords for formats tN, E1, E3 19.1

12.11.3. FOAMROCK

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.29). 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 concentration
in the solution decreases;
• 2 – no foam desorption may occur.
• Default: 1.

2. the mass density of this rock type at reservoir conditions (METRIC: kg/rm3 , FIELD:
lb/rb).

The data should be terminated with a slash /.

Example
FOAMROCK
1 2650 /
2 2650 /

12.11.3. FOAMROCK 1136

Keywords for formats tN, E1, E3 19.1

12.11.4. FOAMDCYW

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets foam decay dependence on water saturation. It can be used only if foam
model option (see 2.18) is activated by the keyword FOAM (see 12.1.68). 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.29). 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).

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.29).
The data should be terminated with a slash /.
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 /
In the example 2 functions are set.

12.11.4. FOAMDCYW 1137

Keywords for formats tN, E1, E3 19.1

12.11.5. FOAMDCYO

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets foam decay dependence on oil saturation. It can be used only if foam
model option (see 2.18) is activated by the keyword FOAM (see 12.1.68). 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.29). 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).

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.29).
The data should be terminated with a slash /.
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 /
In the example 2 functions are set.

12.11.5. FOAMDCYO 1138

Keywords for formats tN, E1, E3 19.1

12.11.6. FOAMMOB

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets dependence of the gas phase mobility factor on foam concentration.
It can be used only if foam model option (see 2.18) is activated by the keyword FOAM
(see 12.1.68). 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.29). Each table contains 2 columns:

1. foam concentration. 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 increasing;

2. gas mobility factor.

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.29).
The data should be terminated with a slash /.
Example
FOAMMOB
0 1
0.001 0.4
0.1 0.1
1.2 0.05 /

12.11.6. FOAMMOB 1139

Keywords for formats tN, E1, E3 19.1

12.11.7. FOAMMOBP

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets dependence of the foam-induced gas phase mobility factor on oil pres-
sure. It is an optional keyword; it can be used only if foam model option (see 2.18) is activated
by the keyword FOAM (see 12.1.68). 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.29). Each
table contains 2 columns:

1. oil pressure (METRIC: barsa, FIELD: psia);

2. multiplier M p (P) which is used to calculate the gas mobility factor as follows:

M = (1 − M(C f )) · M p (P) + M(C f ),

where:

• M is the foam-induced gas phase mobility factor;

• M(C f ) is the coefficient that depends on foam concentration (keyword FOAM-
MOB, see 12.11.6);
• M p (P) is the coefficient defined by this keyword as a function of oil pressure
value;
• P is the oil pressure.

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.29).
The data should be terminated with a slash /.
Example
FOAMMOBP
3000 0
6000 0.2 /

12.11.7. FOAMMOBP 1140

Keywords for formats tN, E1, E3 19.1

12.11.8. FOAMMOBS

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets dependence of the foam-induced gas phase mobility factor on the gas
phase flow velocity. It is an optional keyword; it can be used only if foam model option (see
2.18) is activated by the keyword FOAM (see 12.1.68). 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.29). 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 gas mobility factor as follows:

M f = (1 − M) · Ms (v) + M,

where:

• M f is the final foam-induced gas phase mobility factor;

• M is the coefficient specified by the keywords FOAMMOB (see 12.11.6) and
FOAMMOBP (see 12.11.7);
• Ms (v) is the coefficient defined by this keyword as a function of velocity;
• 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.29).
The data should be terminated with a slash /.
Example
FOAMMOBS
0.0 0
4.0 0.1 /

12.11.8. FOAMMOBS 1141

Keywords for formats tN, E1, E3 19.1

12.12. Residual oil properties

12.12.1. SOR

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword activates residual oil modeling option (see section 2.19) 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.14.6) 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.29).)
The following parameters should be specified:

1. residual oil saturation values in each SATNUM (see 12.4.3) region.

Each data line should be terminated with 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. Residual oil properties 1142

Keywords for formats tN, E1, E3 19.1

12.12.2. SOROPTS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets compressibility model of residual oil. It can be used only if residual oil
saturation option (see 2.19) 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 cell’s 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 sim-
plest 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: ZERO.
The data should be terminated with a slash /.
Example
SOROPTS
FLASH /

12.12.2. SOROPTS 1143

Keywords for formats tN, E1, E3 19.1

12.13. Solid phase

12.13.1. SOLIDMMC

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies tables of mobility multiplier as a function of adsorbed solid con-
centration for each saturation region (see section 3.12). The table describes a reduction in
mobility caused by solid adsorbed on to the rock formation. The number of tables depend on
the number of saturation regions defined in the keyword TABDIMS (see 12.1.29). Each table
is terminated by a slash (/).

Each table consists of 2 columns of data:

1. the concentration of solid adsorbed by the rock formation (METRIC: kg/kg, FIELD:
lb/lb). Concentration values should monotonically increase down the column;

2. the corresponding mobility multiplier.

The number of entries should not be less than 2 or greater than 3-rd parameter of keyword
TABDIMS (see 12.1.29).
The adsorbed concentration is defined as a ratio between weight of solids and weight of
rock. The rock density is specified by ROCKDEN (see 12.2.108) keyword.
The amount of solids adsorbed can be specified by the SOLIDADS (see 12.13.3) keyword.
As an alternative to SOLIDMMC the keyword SOLIDMMS (see 12.13.2), specifying the
mobility multiplier as a function of the adsorbed solid saturation, can be used.
Example
SOLIDMMC
0.0000 1.00
0.0001 0.99
0.0010 0.90
0.0100 0.80
0.1000 0.50 /

12.13. Solid phase 1144

Keywords for formats tN, E1, E3 19.1

12.13.2. SOLIDMMS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies tables of mobility multiplier as a function of adsorbed solid satura-
tion for each saturation region (see section 3.12). The table describes a reduction in mobility
caused by solid adsorbed on to the rock formation. The number of tables depend on the
number of saturation regions defined in the keyword TABDIMS (see 12.1.29). Each table is
terminated by a slash (/).

Each table consists of 2 columns of data:

1. the saturation of solid adsorbed by the rock formation (METRIC: kg/kg, FIELD:
lb/lb). Saturation values should monotonically increase down the column;

2. the corresponding mobility multiplier.

The number of entries should not be less than 2 or greater than 3-rd parameter of keyword
TABDIMS (see 12.1.29).
The amount of solids adsorbed can be specified by the SOLIDADS (see 12.13.3) keyword.
As an alternative to SOLIDMMS the keyword SOLIDMMC (see 12.13.1), specifying the
mobility multiplier as a function of the adsorbed solid concentration, can be used.
Example
SOLIDMMS
0.0000 1.00
0.0001 0.99
0.0010 0.90
0.0100 0.80
0.1000 0.50 /

12.13.2. SOLIDMMS 1145

Keywords for formats tN, E1, E3 19.1

12.13.3. SOLIDADS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies tables of solid adsorption function for each saturation region (see
section 3.12). The table describes an adsorption of solid by the rock formation. The num-
ber of tables depend on the number of saturation regions defined in the keyword TABDIMS
(see 12.1.29). Each table is terminated by a slash (/).

Each table consists of 2 columns of data:

1. the local solid concentration in the solution surrounding the rock (METRIC: kg/m3 ,
FIELD: lb/ f t 3 ). Values should monotonically increase down the column;

2. the corresponding concentration of solid adsorbed by the rock formation.

The number of entries should not be less than 2 or greater than 3-rd parameter of keyword
TABDIMS (see 12.1.29).
The adsorbed concentration is defined as a ratio between weight of solids and weight of
rock. The rock density is specified by ROCKDEN (see 12.2.108) keyword.
If this keyword is not specified it is presumed that all solids are adsorbed to the rock. If
the rock density is set to zero (or not set) even if this keyword is specified it is presumed that
no solids are adsorbed to the rock.
Example
SOLIDADS
0.0000 0.00000
0.0003 0.00005
0.0005 0.00007
0.0008 0.00008
0.0010 0.00008 /

12.13.3. SOLIDADS 1146

Keywords for formats tN, E1, E3 19.1

12.14. 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 – see the
section 3.

12.14. Compositional properties 1147

Keywords for formats tN, E1, E3 19.1

12.14.1. COMPS

Data x tN E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets the number of components in a compositional run – N . Presence of this
keyword indicates that the compositional model (see section 3) 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.14.1. COMPS 1148

Keywords for formats tN, E1, E3 19.1

12.14.2. COMPW

Data x tN E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword activates multiple water component option (see chapter 3.10) in a model and
sets the number of water components. The following parameters should be specified:

1. the number of water components in a model.

The data should be terminated with a slash /.

Example
COMPW
3 /
There are 3 water components in a model.

12.14.2. COMPW 1149

Keywords for formats tN, E1, E3 19.1

12.14.3. CNAMES

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword introduces component names in a compositional run (see section 3). If
component name coincides with name from the internal database, then 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 (n-C4 H10 ), isobutane (i-C4 H10 ) and decane (C10 H22 ).

12.14.3. CNAMES 1150

Keywords for formats tN, E1, E3 19.1

12.14.4. DETAILMF

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies the molar fractions of original components of one or more lumped
pseudocomponents in the fluid (see the section 3.9 for details).
The data may be specified for multiple regions (as many as defined by TNUM,
see 12.16.44). Each region is terminated by a slash /. Inside each region, there are data
for one or more depths (the number of depth points is the 4th parameter of EQLDIMS,
see 12.1.30). Each depth point contains the depth value followed by the fractions of origi-
nal components of the first pseudocomponent in the fluid, then the second (if any) and so on,
as follows:

• d1 , the first depth value;

• x1,1 (1), the molar fraction of the first original component of the first pseudocomponent
in the fluid at this depth;

• ...

• xn1c ,1 (1), the molar fraction of the last original component of the first pseudocomponent
in the fluid at this depth;

• x1,2 (1), the molar fraction of the first original component of the second pseudocompo-
nent in the fluid at this depth;

• ...

• xn2c ,1 (1), the molar fraction of the last original component of the second pseudocompo-
nent in the fluid at this depth;

• ...

• d2 , the second depth value;

• x1,1 (2), the molar fraction of the first original component of the first pseudocomponent
in the fluid at this depth;

• ...

The order of pseudocomponents and the numbers of original components in them are
never specified in this keyword. It is assumed that they are the same as specified in LUMPING
(see 12.14.9).
The data should be terminated with a slash /.

12.14.4. DETAILMF 1151

Keywords for formats tN, E1, E3 19.1

Grids of the concentrations will be available in the GUI on the tab Grid Properties in the
node Calculated → ASP Flood and Tracers. Graphs of the concentrations will be available
on the tab Graphs in the node Tracers.
Default: none.
Example
DETAILMF
100.0 0.05 0.05 0.075 0.075 0.1 0.1 0.1 0.05 0.05
200.0 0.025 0.025 0.035 0.04 0.12 0.12 0.12 0.07 0.07/

12.14.4. DETAILMF 1152

Keywords for formats tN, E1, E3 19.1

12.14.5. DETAILVD

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies the fractions of original components in one or more lumped pseu-
docomponents (see the section 3.9 for details).
The data may be specified for multiple regions (as many as defined by TNUM,
see 12.16.44). Each region is terminated by a slash /. Inside each region, there are data
for one or more depths (the number of depth points is the 4th parameter of EQLDIMS,
see 12.1.30). Each depth point contains the depth value followed by the fractions of origi-
nal components in the first pseudocomponent, then the second (if any) and so on, as follows:

• d1 , the first depth value;

• x1,1 (1), the fraction of the first original component in the first pseudocomponent at this
depth;

• ...

• xn1c ,1 (1), the fraction of the last original component in the first pseudocomponent at this
depth;

• x1,2 (1), the fraction of the first original component in the second pseudocomponent at
this depth;

• ...

• xn2c ,1 (1), the fraction of the last original component in the second pseudocomponent at
this depth;

• ...

• d2 , the second depth value;

• x1,1 (2), the fraction of the first original component in the first pseudocomponent at this
depth;

• ...

For each pseudocomponent the fractions must sum up to 1.

The order of pseudocomponents and the numbers of original components in them are
never specified in this keyword. It is assumed that they are the same as specified in LUMPING
(see 12.14.9).
The data should be terminated with a slash /.

12.14.5. DETAILVD 1153

Keywords for formats tN, E1, E3 19.1

Grids of the concentrations will be available in the GUI on the tab Grid Properties in the
node Calculated → ASP Flood and Tracers. Graphs of the concentrations will be available
on the tab Graphs in the node Tracers.
Default: none.
Example
DETAILVD
100.0 0.2 0.2 0.3 0.3 0.25 0.25 0.25 0.125 0.125
200.0 0.2 0.2 0.28 0.32 0.24 0.24 0.24 0.14 0.14/

12.14.5. DETAILVD 1154

Keywords for formats tN, E1, E3 19.1

12.14.6. EOS

Data x tN E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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). The use of equations of state is described in the section 3.5.
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.29)
(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.14.6. EOS 1155

Keywords for formats tN, E1, E3 19.1

12.14.7. EOSS

Data x tN E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.14.6) is used. If this keyword EOSS is specified then for calculations in surface condi-
tions the EOS specified by EOSS is used; and for calculations in reservoir conditions – EOS,
specified by EOS (see 12.14.6). The list of keyword that specify parameters for calculations
in surface and reservoir conditions is in the section 3.5.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 12.1.29)
(9-th parameter).
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.14.7. EOSS 1156

Keywords for formats tN, E1, E3 19.1

12.14.8. LUMPDIMS

Data x tN E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword prepares the data structure for the keyword LUMPING (see 12.14.9) (see the
section 3.9 for details).
The parameters of the keyword are:

1. Number of pseudocomponents detailed in the keyword LUMPING (see 12.14.9).

2. Maximum number of original components in one lumped component.

The data should be terminated with a slash /.

Default: none.
Example
LUMPDIMS
2 5 /
This example announces the presence of two lumped components, each having no more
than five detailed components.

12.14.8. LUMPDIMS 1157

Keywords for formats tN, E1, E3 19.1

12.14.9. LUMPING

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies the composition of one or more pseudocomponents produced by

lumping, so that the results could display the original components in the form of tracers (see
the section 3.9 for details). If this keyword is not specified, then the output grids and graphs
would contain just the results for the pseudocomponent(s).
The keyword may contain multiple lines of data if multiple pseudocomponents are detailed.
Each data line should be terminated with the symbol /. A line related to one pseudocomponent
contains the following parameters:

• name of the pseudocomponent as it appears in CNAMES (see 12.14.3);

• nc , the number of original components included in it;

• name1 , the name of the first original component in this pseudocomponent;

• ...

• namen1c , the name of the last original component in this pseudocomponent.

The data should be terminated with a slash /.

The keyword LUMPDIMS (see 12.14.8) must be also present.
Default: none.
Example
LUMPING
'PSEUDO 1' 4 C7 C8 C9 C10 /
'PSEUDO 2' 5 C11 C12 C13 C14 C15 /
/

12.14.9. LUMPING 1158

Keywords for formats tN, E1, E3 19.1

12.14.10. RTEMP

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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 12.1.29) (9-th parameter).
Default: none.
Example
TABDIMS
2 1 2* 4 4*1
/
...
RTEMP
80
/
Here isothermal compositional reservoir model is used, reservoir temperature is 80 Celsius
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.14.10. RTEMP 1159

Keywords for formats tN, E1, E3 19.1

12.14.11. STCOND

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.
Moreover, this temperature is used for calculation of the component liquid enthalpy (see
section 4.17). User should specify two values: standard temperature and pressure.
Default: values from 10.
Example
STCOND
20 2
/

12.14.11. STCOND 1160

Keywords for formats tN, E1, E3 19.1

12.14.12. WATERTAB

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.29).

One table row contains the following parameters:

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.14.12. WATERTAB 1161

Keywords for formats tN, E1, E3 19.1

12.14.13. ZI

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets initial composition for each equation of state region (EOSNUM,
see 12.4.20) for a compositional run. An explicit specification of initial conditions is de-
scribed in the section 4.37.2. Each value – molar composition of corresponding component.
(N is number of components defined in COMPS, see 12.14.1) 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 parameter
of TABDIMS (see 12.1.29). Each table must be terminated by a slash /.
Note:

1. If in the PROPS section there is COMPVD (see 12.14.14) or ZMFVD (see 12.14.17) or
ZI (see 12.14.13), then it is used.

2. If in the PROPS section component composition versus depth is not specified (no COM-
PVD (see 12.14.14), ZMFVD (see 12.14.17), ZI, see 12.14.13), but component compo-
sition is specified in SOLUTION in each grid block (ZMF (see 12.16.23) 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.16.23) correspondingly);
• the table ZMFVD (see 12.14.17) is constructed and used in EQUIL (see 12.16.2);
• the table ZMFVD (see 12.14.17) 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.14.13. ZI 1162
Keywords for formats tN, E1, E3 19.1

12.14.14. COMPVD

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies the total compositions with respect to depth for compositional mod-
els (see section 4.37.2). The table should be specified for each equilibrium region (EQLDIMS,
see 12.1.30) and be terminated with a slash /.

The numbers of columns depends on the number of components (COMPS, see 12.14.1).

One table row contains the following parameters:

• 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:

1. If in the keyword EQUIL (see 12.16.2) 10-th parameter is set to 1, then the two last
columns COMPVD (see 12.14.14) (0 (vapor) or 1 (liquid)) and (saturation pressure) are
ignored;

2. If in the PROPS section there is COMPVD (see 12.14.14) or ZMFVD (see 12.14.17) or
ZI (see 12.14.13), then it is used.

3. If in the PROPS section component composition versus depth is not specified (no COM-
PVD (see 12.14.14), ZMFVD (see 12.14.17), ZI, see 12.14.13), but component compo-
sition is specified in SOLUTION in each grid block (ZMF (see 12.16.23) 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.16.23) correspondingly);
• the table ZMFVD (see 12.14.17) is constructed and used in EQUIL (see 12.16.2);

12.14.14. COMPVD 1163

Keywords for formats tN, E1, E3 19.1

• the table ZMFVD (see 12.14.17) is saved in the .log file.

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.14.14. COMPVD 1164

Keywords for formats tN, E1, E3 19.1

12.14.15. XMFVP

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies the table of liquid composition versus pressure (distribution of con-
centration matrix xc,O , c = 1, . . . , n0c ) for Calculations of initial conditions from hydrostatic
and thermodynamic equilibrium conditions. The data should be terminated with a slash /.
The table should be specified for each equilibrium region (EQLDIMS, see 12.1.30).

The numbers of columns depends on the number of components (COMPS, see 12.14.1).

One table row contains the following parameters:

• 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 be
terminated with a slash /.

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.14.15. XMFVP 1165

Keywords for formats tN, E1, E3 19.1

12.14.16. YMFVP

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies the table of vapor composition versus pressure (distribution of con-
centration matrix xc,G , c = 1, . . . , n0c ) for Calculations of initial conditions from hydrostatic
and thermodynamic equilibrium conditions. The data should be terminated with a slash /.
The table should be specified for each equilibrium region (EQLDIMS, see 12.1.30).

The numbers of columns depends on the number of components (COMPS, see 12.14.1).

One table row contains the following parameters:

• 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 be
terminated with a slash /.

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.14.16. YMFVP 1166

Keywords for formats tN, E1, E3 19.1

12.14.17. ZMFVD

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets initial composition with respect to depth data for each equilibration
region (for a compositional run) for Calculations of initial conditions from hydrostatic and
thermodynamic equilibrium conditions. First column lists depth values, the rest N columns
(N is number of components defined in COMPS, see 12.14.1) list molar composition of
corresponding 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 distribu-
tion for all equilibration regions.
Number of tables depends on number of equilibration regions defined in EQLDIMS
(see 12.1.30). Each table must be terminated by a slash /.
Default: none.
Note:

1. If in the PROPS section there is COMPVD (see 12.14.14) or ZMFVD (see 12.14.17) or
ZI (see 12.14.13), then it is used.

2. If in the PROPS section component composition versus depth is not specified (no COM-
PVD (see 12.14.14), ZMFVD (see 12.14.17), ZI, see 12.14.13), but component compo-
sition is specified in SOLUTION in each grid block (ZMF (see 12.16.23) 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.16.23) correspondingly);
• the table ZMFVD (see 12.14.17) is constructed and used in EQUIL (see 12.16.2);
• the table ZMFVD (see 12.14.17) is saved in the .log file.

12.14.17. ZMFVD 1167

Keywords for formats tN, E1, E3 19.1

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.14.17. ZMFVD 1168

Keywords for formats tN, E1, E3 19.1

12.14.18. NEI

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets initial composition for non-equilibrium initialization for each equilibra-
tion region (for a compositional run). (EQLDIMS (see 12.1.30), 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.14.1).

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.16.21),
YMF (see 12.16.22), XMFVP (see 12.14.15), YMFVP (see 12.14.16).
Example
NEI
0.384480 0.067150 0.141940 0.067050 0.089940 0.109580 0.087820
0.052040 /

12.14.18. NEI 1169

Keywords for formats tN, E1, E3 19.1

12.14.19. KVTABLE

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies the table of partition coefficients (K-values) to control liquid-vapor
phase equilibrium (see section Thermodynamic equilibrium condition).
If the keyword KVALUES (see 12.1.77) is enabled, then the values specified via this keyword
will be used instead of the equation of state equal fugacity relationships to obtain the compo-
sition 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 /.

One table row contains the following parameters:

• 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.14.19. KVTABLE 1170

Keywords for formats tN, E1, E3 19.1

12.14.20. TCRIT

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword associates critical temperature (METRIC: K, FIELD: ◦ R) with each compo-
nent of a compositional model for each EoS region.

For surface conditions these values can be overridden by the keyword TCRITS
(see 12.14.21), if it is present. 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.5.1.
For each region a line of N values should be entered, where N is number of components
defined in COMPS (see 12.14.1). Each line must be terminated by a slash /. Number of lines
depends on number of EoS regions defined in TABDIMS (see 12.1.29) (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).

Default: none.
Example
TABDIMS
2 1 2* 4 4*1
/
...
COMPS
4
/
CNAMES
CO2 C1 NC4 C10
/
...
TCRIT
3.047000000E+02 1.9060000000E+02 4.252000000E+02
6.260000000E+02
/
Here critical temperature is specified for components {CO2 ,C1 , NC4 ,C10 }.

12.14.20. TCRIT 1171

Keywords for formats tN, E1, E3 19.1

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 re-
gion default temperature values will be taken from the internal database, in the second region
all values except that for component C8 will also be taken by default.

12.14.20. TCRIT 1172

Keywords for formats tN, E1, E3 19.1

12.14.21. TCRITS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword associates critical temperature (METRIC: K, FIELD: ◦ R) with each compo-
nent of a compositional model for each EoS region for calculations in surface conditions.

If this keyword is specified, it overrides the settings of TCRIT (see 12.14.20) for surface
conditions, not affecting the reservoir conditions. Thus two sets of parameters can be used.
The list of all keywords that specify parameters for calculations in surface and reservoir con-
ditions is in the section 3.5.1.

For each region a line of N values should be entered, where N is number of components
defined in COMPS (see 12.14.1). Each line must be terminated by a slash /. Number of lines
depends on number of EoS regions defined in TABDIMS (see 12.1.29) (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).

Default: values from TCRIT (see 12.14.20).

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.14.21. TCRITS 1173

Keywords for formats tN, E1, E3 19.1

12.14.22. PCRIT

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword associates critical pressure (METRIC: barsa, FIELD: psia) with each com-
ponent of a compositional model for each EoS region.

For surface conditions these values can be overridden by the keyword PCRITS
(see 12.14.23), if it is present. 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.5.1.

For each region a line of N values should be entered, where N is number of components
defined in COMPS (see 12.14.1). Each line must be terminated by a slash /. Number of lines
depends on number of EoS regions defined in TABDIMS (see 12.1.29) (9-th parameter).

Default: none.
Example
TABDIMS
2 1 2* 4 4*1
/
...
COMPS
4
/
CNAMES
CO2 C1 NC4 C10
/
...
PCRIT
7.382000000E+01 4.604208000E+01 3.796647750E+01
2.419641000E+01
/
Here critical pressure for components {CO2 ,C1 , NC4 ,C10 } is specified.

12.14.22. PCRIT 1174

Keywords for formats tN, E1, E3 19.1

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 the internal database.

12.14.22. PCRIT 1175

Keywords for formats tN, E1, E3 19.1

12.14.23. PCRITS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.

If this keyword is specified, it overrides the settings of PCRIT (see 12.14.22) for surface
conditions, not affecting the reservoir conditions. Thus two sets of parameters can be used.
The list of all keywords that specify parameters for calculations in surface and reservoir con-
ditions is in the section 3.5.1.

For each region a line of N values should be entered, where N is number of components
defined in COMPS (see 12.14.1). Each line must be terminated by a slash /. Number of lines
depends on number of EoS regions defined in TABDIMS (see 12.1.29) (9-th parameter).

Default: values from PCRIT (see 12.14.22).

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.14.23. PCRITS 1176

Keywords for formats tN, E1, E3 19.1

12.14.24. VCRIT

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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 surface conditions these values can be overridden by the keyword VCRITS
(see 12.14.25), if it is present. 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.5.1.

For each region a line of N values should be entered, where N is number of components
defined in COMPS (see 12.14.1). Each line must be terminated by a slash /. Number of lines
depends on number of EoS regions defined in TABDIMS (see 12.1.29) (9-th parameter).

Default: values calculated from ZCRIT (see 12.14.27).

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 calculated from their corresponding ZCRIT (see 12.14.27).

12.14.24. VCRIT 1177

Keywords for formats tN, E1, E3 19.1

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 the internal database.

12.14.24. VCRIT 1178

Keywords for formats tN, E1, E3 19.1

12.14.25. VCRITS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.

If this keyword is specified, it overrides the settings of VCRIT (see 12.14.24) for surface
conditions, not affecting the reservoir conditions. Thus two sets of parameters can be used.
The list of keywords specifying parameters for calculations in surface and reservoir conditions
is in the section 3.5.1.

For each region a line of N values should be entered, where N is number of components
defined in COMPS (see 12.14.1). Each line must be terminated by a slash /. Number of lines
depends on number of EoS regions defined in TABDIMS (see 12.1.29) (9-th parameter).

Default: values from VCRIT (see 12.14.24).

Example
TABDIMS
2 1 2* 4 4*1
/
...
COMPS
4
/
CNAMES
CO2 C1 NC4 C10
/
...
VCRITS
3* 5.340000000E-01

12.14.25. VCRITS 1179

Keywords for formats tN, E1, E3 19.1

12.14.26. VCRITVIS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specify critical volumes (METRIC: m3 /kg.M , FIELD: f t 3 /lb.M ) for each
component of a compositional model for each EoS region. Critical volumes are used for vis-
cosity calculation using correlation Lohrenz-Bray-Clark (see section 3.8.1).

For each region a line of N values should be entered, where N is number of components
defined in COMPS (see 12.14.1).

Each line must be terminated by a slash /. Number of lines depends on number of EoS
regions defined in TABDIMS (see 12.1.29) (9-th parameter).

If the keywords ZCRITVIS (see 12.14.29), VCRITVIS (see 12.14.26) are not specified, the
data from the keywords ZCRIT (see 12.14.27), VCRIT (see 12.14.24) 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.14.26. VCRITVIS 1180

Keywords for formats tN, E1, E3 19.1

12.14.27. ZCRIT

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.14.1).

For surface conditions these values can be overridden by the keyword ZCRITS
(see 12.14.28), if it is present. 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.5.1.

Each line must be terminated by a slash /. Number of lines depends on number of EoS
regions defined in TABDIMS (see 12.1.29) (9-th parameter).

Critical Z-factors are used to calculate critical molar volumes via the following relation-
ship:
Vc = Zc RTc /Pc
Default: none.
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.14.27. ZCRIT 1181

Keywords for formats tN, E1, E3 19.1

12.14.28. ZCRITS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specify critical Z-factor for each component of a compositional model for
each EoS region for calculations in surface conditions.

If this keyword is specified, it overrides the settings of ZCRIT (see 12.14.27) for surface
conditions, not affecting the reservoir conditions. Thus two sets of parameters can be used.
The list of all keywords that specify parameters for calculations in surface and reservoir con-
ditions is in the section 3.5.1.

For each region a line of N values should be entered, where N is number of components
defined in COMPS (see 12.14.1).

Each line must be terminated by a slash /. Number of lines depends on number of EoS
regions defined in TABDIMS (see 12.1.29) (9-th parameter).

Critical Z-factors are used to calculate critical molar volume via the following relationship:

Vc = Zc RTc /Pc

Default: values from ZCRIT (see 12.14.27).

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.14.28. ZCRITS 1182

Keywords for formats tN, E1, E3 19.1

12.14.29. ZCRITVIS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specify critical Z-factor for each component of a compositional model for
each EoS region. Parameters defined by this keyword are used for viscosity calculation using
correlation Lohrenz-Bray-Clark (see section 3.8.1). For each region a line of N values should
be entered, where N is number of components defined in COMPS (see 12.14.1).

Each line must be terminated by a slash /. Number of lines depends on number of EoS
regions defined in TABDIMS (see 12.1.29) (9-th parameter).
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.14.29), VCRITVIS (see 12.14.26) are not specified, the
data from the keywords ZCRIT (see 12.14.27), VCRIT (see 12.14.24) 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.14.29. ZCRITVIS 1183

Keywords for formats tN, E1, E3 19.1

12.14.30. MW

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword associates molecular weight of each component for a compositional model
in each EoS region (METRIC: kg/kg-mol , FIELD: lb/lb-mol ). Molecular weight of each
component is used for calculation of phase molar density (see section 3.7) and viscosity (see
section 3.8).
For each region a line of N values should be entered, where N is number of components
defined in COMPS (see 12.14.1). Each line must be terminated by a slash /. Number of lines
depends on number of EoS regions defined in TABDIMS (see 12.1.29) (9-th parameter).

Default: none.
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.14.30. MW 1184
Keywords for formats tN, E1, E3 19.1

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 the internal database.

12.14.30. MW 1185
Keywords for formats tN, E1, E3 19.1

12.14.31. MWS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword associates molecular weight with each component of a compositional model
for each EoS region for calculations in surface conditions (METRIC: kg/kg-mol , FIELD:
lb/lb-mol ).

If this keyword is specified, it overrides the settings of MW (see 12.14.30) for surface con-
ditions, not affecting the reservoir conditions. 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.5.1.

For each region a line of N values should be entered, where N is number of components
defined in COMPS (see 12.14.1). Each line must be terminated by a slash /. Number of lines
depends on number of EoS regions defined in TABDIMS (see 12.1.29) (9-th parameter).

Default: values from MW (see 12.14.30).

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.14.31. MWS 1186

Keywords for formats tN, E1, E3 19.1

12.14.32. MWW

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets molecular weight of water components for a compositional model in
each EoS region (METRIC: kg/kg-mol , FIELD: lb/lb-mol ).
Molecular weight of water components is used for calculation of phase molar density (see
section 3.7) and viscosity (see section 3.8).
Multiple water components option is activated with the keyword COMPW (see 12.14.2).
Description of this option is in the section 3.10.
The values for all water components should be set (Nw values, where Nw – is the number
from COMPW, see 12.14.2).
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.29) (9-th parameter).

Default: 18.0.
Example
MWW 18.3 /
In this example water molecular weight is set for one EoS region.

12.14.32. MWW 1187

Keywords for formats tN, E1, E3 19.1

12.14.33. MWWS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keywords sets molecular weight for water components which will be used in surface
calculations for Multiple component water option (METRIC: kg/kg-mol , FIELD: lb/lb-mol ).
If this keyword is not specified then the values from the keyword MWW (see 12.14.32) are
used.
Multiple water components option is activated with the keyword COMPW (see 12.14.2).
Description of this option is in the section 3.10.
The values for all water components should be set (Nw values, where Nw – is the number
from COMPW, see 12.14.2).
If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /. The data should be terminated
with a slash /.

12.14.33. MWWS 1188

Keywords for formats tN, E1, E3 19.1

12.14.34. PREFW

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets reference pressure values for water components in multiple component
water run.
Multiple water components option is activated with the keyword COMPW (see 12.14.2).
Description of this option is in the section 3.10.
The following parameters should be specified:

1. reference pressure values for each water component (METRIC: bars, FIELD: psi). Nw
values should be specified, where Nw is the number from COMPW (see 12.14.2).
Default: 1 atm.

The data should be terminated with a slash /.

If there are several equation of states in the model, then this data set should be specified
for each state regions.
If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.

Example
PREFW
1.0 2.0 1.0 /
There are reference pressure values for three water components.

12.14.34. PREFW 1189

Keywords for formats tN, E1, E3 19.1

12.14.35. PREFWS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keywords sets reference pressures for water components which will be used in surface
calculations for Multiple component water option. If this keyword is not specified then the
values from the keyword PREFW (see 12.14.34) are used.
Multiple water components option is activated with the keyword COMPW (see 12.14.2).
Description of this option is in the section 3.10.
The values for all water components should be set (Nw values, where Nw – is the number
from COMPW, see 12.14.2).
If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /. The data should be terminated
with a slash /.

12.14.35. PREFWS 1190

Keywords for formats tN, E1, E3 19.1

12.14.36. DREFW

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets water component densities at reference pressure in multiple component
water run.
Multiple water components option is activated with the keyword COMPW (see 12.14.2).
Description of this option is in the section 3.10.
The following parameters should be specified:

1. water component densities (METRIC: kg/m3 , FIELD: lb/ f t 3 ). Nw values should be

specified, where Nw is the number from COMPW (see 12.14.2).
Default: 999.014 kg/m3 .

If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /. The data should be terminated
with a slash /.
Example
DREFW
1010.0 1020.0 1000.0/
In the example density values at reference pressure of water component are set.

12.14.36. DREFW 1191

Keywords for formats tN, E1, E3 19.1

12.14.37. DREFWS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keywords sets reference densities for water components which will be used in surface
calculations for Multiple component water option. If this keyword is not specified then the
values from the keyword DREFW (see 12.14.36) are used.
Multiple water components option is activated with the keyword COMPW (see 12.14.2).
Description of this option is in the section 3.10.
The values for all water components should be set (Nw values, where Nw – is the number
from COMPW, see 12.14.2).
If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /. The data should be terminated
with a slash /.

12.14.37. DREFWS 1192

Keywords for formats tN, E1, E3 19.1

12.14.38. ACF

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.14.1). Each line must be terminated by a slash /.
Number of lines depends on number of EoS regions defined in TABDIMS (see 12.1.29) (9-th
parameter).

For surface conditions these values can be overridden by the keyword ACFS
(see 12.14.39), if it is present. 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.5.1.

Default: none.
Example
TABDIMS
2 1 2* 4 4*1
/
...
COMPS
4
/
CNAMES
CO2 C1 NC4 C10
/
...
ACF
2.250000000E-01 1.300000000E-02 2.01000000E-01 3.850000000E-01
/
Here acentric factors are specified for components {CO2 ,C1 , NC4 ,C10 }.

12.14.38. ACF 1193

Keywords for formats tN, E1, E3 19.1

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 compo-
nents {CO2 ,C1 , NC4 } in the first region and for component NC4 in the second region will be
taken by default from the internal database.

12.14.38. ACF 1194

Keywords for formats tN, E1, E3 19.1

12.14.39. ACFS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword associates acentric factor with each component of a compositional model for
each EoS region for calculations in surface conditions.

If this keyword is specified, it overrides the settings of ACF (see 12.14.38) for surface
conditions, not affecting the reservoir conditions. Thus two sets of parameters can be used.
The list of all keywords that specify parameters for calculations in surface and reservoir con-
ditions is in the section 3.5.1.

For each region a line of N values should be entered, where N is number of components
defined in COMPS (see 12.14.1). Each line must be terminated by a slash /. Number of lines
depends on number of EoS regions defined in TABDIMS (see 12.1.29) (9-th parameter).

Default: values from ACF (see 12.14.38).

Example
ACFS
2.250000000E-01 1.300000000E-02 1* 3.850000000E-01
/

12.14.39. ACFS 1195

Keywords for formats tN, E1, E3 19.1

12.14.40. BIC

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.14.1). These ele-
ments form lower triangular part of binary interaction matrix.

For surface conditions these values can be overridden by the keyword BICS (see 12.14.41),
if it is present. 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.5.1.

Number of tables depends on number of EoS regions defined in TABDIMS (see 12.1.29)
(9-th parameter). Each table must be terminated by a slash /.
Default: none.
Example
TABDIMS
2 1 2* 4 4*1
/
...
COMPS
4
/
CNAMES
CO2 C1 NC4 C10
/
...
BIC
0.1
0.1 0.0
0.1 0.041 0.0
/

Here binary interaction coefficients for components {CO2 ,C1 , NC4 ,C10 } are specified.

12.14.40. BIC 1196

Keywords for formats tN, E1, E3 19.1

Example
TABDIMS
2 2 2* 4 4*2
/
...
COMPS
3
/
CNAMES
methane ethane Cplus
/
...
BIC
0.1
0.1 0.0
/
0.1
0.1 0.0
/

Here binary interaction coefficients are specified for two EoS regions.

12.14.40. BIC 1197

Keywords for formats tN, E1, E3 19.1

12.14.41. BICS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies binary interaction coefficients between the components of a com-
positional model for each EoS region for calculations in surface conditions.

If this keyword is specified, it overrides the settings of BIC (see 12.14.40) for surface con-
ditions, not affecting the reservoir conditions. 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.5.1.

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.14.1). 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.29)
(9-th parameter). Each table must be terminated by a slash /.
Default: values from BIC (see 12.14.40).
Example
TABDIMS
2 1 2* 4 4*1
/
...
COMPS
4
/
CNAMES
CO2 C1 NC4 C10
/
...
BICS
0.1
0.1 0.0
0.1 0.041 0.0
/

Here binary interaction coefficients for components {CO2 ,C1 , NC4 ,C10 } are specified.

12.14.41. BICS 1198

Keywords for formats tN, E1, E3 19.1

12.14.42. OMEGAA / OMEGAB

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

These keywords specify the values of parameters Ωa0 and Ωb0 used in the equation of
state. For surface conditions these values can be overridden by the keywords OMEGAAS
(see 12.14.43) and OMEGABS (see 12.14.43), if they are present. 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.5.1.

One value should be specified for one component. The data should be terminated with a
slash /.
The following equations of state are considered
RT a
p= − .
v − b (v + m1 b)(v + m2 b)

tNavigator supports the following equation types: Redlich-Kwong (RK), Soave-Redlich-

Kwong (SRK), Peng-Robinson (PR).
Default: depends on the equation type.

EOS m1 m2 Ωa0 Ωb0

RK, SRK 0 1 0.4274802 0.08664035
√ √
PR 1+ 2 1− 2 0.457235529 0.07796074

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.14.42. OMEGAA / OMEGAB 1199

Keywords for formats tN, E1, E3 19.1

12.14.43. OMEGAAS / OMEGABS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

These keywords specify the values of parameters Ωa0 and Ωb0 for calculations in surface
conditions.
If these keywords are specified, they override the settings of OMEGAA (see 12.14.42)
and OMEGAB (see 12.14.42) for surface conditions, not affecting the reservoir conditions.
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.5.1.

One value should be specified for one component. The data should be terminated with a
slash /.

Default: values from OMEGAA / OMEGAB (see 12.14.42).

Example
OMEGAAS
0.459 0.457 0.461 0.462 0.457 /
OMEGABS
0.07791 0.07794 0.0777 0.0780 0.0777 /

12.14.43. OMEGAAS / OMEGABS 1200

Keywords for formats tN, E1, E3 19.1

12.14.44. LBCCOEF

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies the values of coefficients in viscosity correlation formula Lohrenz-
Bray-Clark (3.8.1). 5 values should be specified. The data should be terminated with a slash /.

One should use the keyword LBCCOEFR (see 12.14.45) to set different coefficients for
each EoS region.

Default: 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, while the values of coeffi-
cients a3 , a5 are overridden.

12.14.44. LBCCOEF 1201

Keywords for formats tN, E1, E3 19.1

12.14.45. LBCCOEFR

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies the values of coefficients in viscosity correlation formula Lohrenz-
Bray-Clark (3.8.1) for each equation of state region. Equation of state regions are specified
via EOSNUM (see 12.4.20).

One should use the keyword LBCCOEF (see 12.14.44) to set the coefficients for whole
reservoir.

5 values should be specified for each equation of state region. The data for each region
should be terminated with a slash /.

Default: a1 = 0.1023000, a2 = 0.0233640, a3 = 0.0585330, a4 = −0.0407580, a5 =

0.0093324.
Example
LBCCOEFR
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 over-
ridden.

12.14.45. LBCCOEFR 1202

Keywords for formats tN, E1, E3 19.1

12.14.46. VCOMPACT

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword indicates that Modified Lohrenz-Bray-Clark Correlation (see 3.8.2) will be
used and defines the minimum molar volume of the components.

The following data should be specified:

• nc minimum molar volume values for nc number of model components

m3 f t3
(METRIC: ; FIELD: ).
kg − mol lb − mol
Default: no default value.

The data should be entered for each EoS region. The number of EoS regions is defined via
TABDIMS (see 12.1.29) keyword. The data for each EoS region should be terminated with a
slash /.

Example
VCOMPACT
1.68 6.37 9.82/

In this example minimum molar volume are defined for three components in one EoS
region.

12.14.46. VCOMPACT 1203

Keywords for formats tN, E1, E3 19.1

12.14.47. FACTLI

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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
should be terminated with a slash /.

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.14.47. FACTLI 1204

Keywords for formats tN, E1, E3 19.1

12.14.48. LILIM

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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 .
Default: 0.75.
2. upper limit for hydrocarbon-water interpolation fO .
Default: 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:
∑ TciVci zi
Tcrit = i
∑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.
Example
LILIM
0.82 1.12 /

12.14.48. LILIM 1205

Keywords for formats tN, E1, E3 19.1

12.14.49. PRCORR

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword defines that modified Peng-Robinson equation of state is used. This equation
is called PR∗ in the section 3.5.

The keyword doesn’t have any parameters.

12.14.49. PRCORR 1206

Keywords for formats tN, E1, E3 19.1

12.14.50. SSHIFT

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies Equation of State shift parameters si in equation 3.24.

The following data should be specified:

• nc volume shift values for nc number of model components.

It is a dimensionless parameter.
If the temperature-dependent volume shift model is initialized (VSHIF1, see 12.14.52),
then these values would correspond to volumetric correction at reference temperature
(TREFVS, see 12.14.53).
Default: 0.

The data should be entered for each EoS region. The number of EoS regions is defined via
TABDIMS (see 12.1.29) keyword. The data for each EoS region should be terminated with a
slash /.

Example
TABDIMS
8* 2 /
... ... ...
SSHIFT
0 -0.13093 0.00706 -0.03954 -0.04588 / -- data for EOSNUM=1
/ -- data for EOSNUM=2

In this example:

• Two EoS regions are initialized in the model via 9−th parameter of TABDIMS keyword.

• Volume shift parameters are specified for the first EoS region.

• For the second EoS region, empty data set is defined, hence the shift option is not used
in this region.

12.14.50. SSHIFT 1207

Keywords for formats tN, E1, E3 19.1

12.14.51. SSHIFTS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies equation of states shift parameters si 3.24 for calculation in surface
conditions. The data should be terminated with a slash /.
If this keyword is specified, it overrides the settings of SSHIFT (see 12.14.50) for surface
conditions, not affecting the reservoir conditions. Thus two sets of parameters can be used.
The list of all keywords that specify parameters for calculations in surface and reservoir con-
ditions is in the section 3.5.1.

Default: values from SSHIFT (see 12.14.50).

Example
SSHIFTS
0.0 0.019066509 -0.4412272 -0.5106669 -0.10078032 -0.11951863
/

12.14.51. SSHIFTS 1208

Keywords for formats tN, E1, E3 19.1

12.14.52. VSHIF1

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword enables a linear temperature-dependent shift model and specifies the tem-
perature gradients sti in equation 3.24.
The following data should be specified:

• nc temperature gradient values for nc number of model components

(METRIC: K1 ; FIELD: ◦1R ).
Default: 0.

The data should be entered for each EoS region. The number of EoS regions is defined via
TABDIMS (see 12.1.29) keyword. The data for each EoS region should be terminated with a
slash /.

Example
SSHIFT
0 -0.13093 0.00706 -0.03954 -0.04588 /

VSHIF1
0.000441 -0.000016 0.000518 0.000463 0.000012 /

In this example:

• Equation of State shift parameters si are specified for each component via SSHIFT
keyword.

• Temperature gradient sti for temperature-dependent shift model are specified for each
component via VSHIF1 keyword.

12.14.52. VSHIF1 1209

Keywords for formats tN, E1, E3 19.1

12.14.53. TREFVS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies the reference temperatures for linear temperature-dependent shift
model (Tre f vs in equation 3.24).

The following data should be specified:

• nc reference temperature values for nc number of model components

(METRIC: K, FIELD: ◦ R).
Default: METRIC: 15.56 K, FIELD: 519.68 ◦ R.

Example
SSHIFT
0 -0.13093 0.00706 -0.03954 -0.04588 /

VSHIF1
0.000441 -0.000016 0.000518 0.000463 0.000012 /

TREFVS
373.15 373.15 373.15 373.15 373.15 /

In this example:

• Equation of State shift parameters si are specified for each component via SSHIFT
keyword.

• Temperature gradient sti for temperature-dependent shift model are specified for each
component via VSHIF1 keyword.

• Reference temperatures for are specified for each component via TREFVS keyword.

12.14.53. TREFVS 1210

Keywords for formats tN, E1, E3 19.1

12.14.54. EPSCOMP

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specified the number of component which molar concentration is used in
interpolation of end-point scaling tables ENKRVC (see 12.14.55), ENPCVC (see 12.14.56),
ENPTVC (see 12.14.57).

The number of specified values should be equal to the number of saturation function region
(1-st parameter of TABDIMS, see 12.1.29). 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.14.54. EPSCOMP 1211

Keywords for formats tN, E1, E3 19.1

12.14.55. ENKRVC

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies relative permeability end point versus composition tables. Other
methods of end points scaling are described in the section 4.35. The number of specified ta-
bles should be equal to the number of saturation function region (1-st parameter of TABDIMS,
see 12.1.29). Each table should be terminated with a slash /.

One table row contains the following parameters:

1. molar concentration of the component specified via the keyword EPSCOMP

(see 12.14.54);

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 - mini-
mum 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 method of end points scaling can be used:

• usual end points scaling (ENDSCALE).

• temperature-dependent end points (ENPTVT (see 12.15.85), ENKRVT (see 12.15.86),

ENPCVT, see 12.15.87).

• composition-dependent end points (ENPTVC (see 12.14.57), ENKRVC (see 12.14.55),

ENPCVC, see 12.14.56).

12.14.55. ENKRVC 1212

Keywords for formats tN, E1, E3 19.1

Possible combinations can be specified using 5-th parameter of the keyword ENDSCALE
(see 12.1.136).

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 /

In this example one table is specified.

12.14.55. ENKRVC 1213

Keywords for formats tN, E1, E3 19.1

12.14.56. ENPCVC

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies maximum capillary pressure end point versus composition tables.
Other methods of end points scaling are described in the section 4.35. The number of spec-
ified tables should be equal to the number of saturation function region (1-st parameter of
TABDIMS, see 12.1.29). Each table should be terminated with a slash /.

One table row contains the following parameters:

1. molar concentration of the component specified via the keyword EPSCOMP

(see 12.14.54);

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).

By default one one method of end points scaling can be used:

• usual end points scaling (ENDSCALE).

• temperature-dependent end points (ENPTVT (see 12.15.85), ENKRVT (see 12.15.86),

ENPCVT, see 12.15.87).

• composition-dependent end points (ENPTVC (see 12.14.57), ENKRVC (see 12.14.55),

ENPCVC, see 12.14.56).

Possible combinations can be specified using 5-th parameter of the keyword ENDSCALE
(see 12.1.136).

Example
ENPCVC
0 0.11 1.52
1 0.09 2.14 /

In this example one table is specified.

12.14.56. ENPCVC 1214

Keywords for formats tN, E1, E3 19.1

12.14.57. ENPTVC

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies saturation end point versus composition tables. Other methods of
end points scaling are described in the section 4.35. The number of specified tables should be
equal to the number of saturation function region (1-st parameter of TABDIMS, see 12.1.29).
Each table should be terminated with a slash /.

One table row contains the following parameters:

1. molar concentration of the component specified via the keyword EPSCOMP

(see 12.14.54);

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.33) 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.

By default one one method of end points scaling can be used:

• usual end point scaling (ENDSCALE).

• temperature-dependent end points (ENPTVT (see 12.15.85), ENKRVT (see 12.15.86),

ENPCVT, see 12.15.87).

• composition-dependent end points (ENPTVC (see 12.14.57), ENKRVC (see 12.14.55),

ENPCVC, see 12.14.56).

12.14.57. ENPTVC 1215

Keywords for formats tN, E1, E3 19.1

Possible combinations can be specified using 5-th parameter of the keyword ENDSCALE
(see 12.1.136).

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 /

In this example one table is specified.

12.14.57. ENPTVC 1216

Keywords for formats tN, E1, E3 19.1

12.14.58. DIFFCGAS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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 described in the section 3.11 and switched on via the key-
word DIFFUSE (see 12.1.70). The diffusion coefficients for oil phase is specified via DIFFCOIL
(see 12.14.59). 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 components in the model. The
data should be terminated with a slash /.
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.14.58. DIFFCGAS 1217

Keywords for formats tN, E1, E3 19.1

12.14.59. DIFFCOIL

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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 described in the section 3.11 and switched on via the keyword
DIFFUSE (see 12.1.70). The diffusion coefficients for gas phase is specified via DIFFCGAS
(see 12.14.58). 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 components in the model. The
data should be terminated with a slash /.
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.14.59. DIFFCOIL 1218

Keywords for formats tN, E1, E3 19.1

12.14.60. DIFFCGO

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets cross phase diffusion coefficients. They are used to define cross phase
diffusion from a cell containing gas to a cell containing oil (see section 3.11.1). The opposite
diffusive flow is set by the keyword DIFFCOG (see 12.14.61).
Option of molecular diffusion is switched on via the keyword DIFFUSE (see 12.1.70).
The following parameters should be specified:

1. cross phase diffusion coefficient for each model component (METRIC: m2 /day;
FIELD: f t 2 /day).
Default: 0.

The data should be terminated with a slash /.

Example
DIFFCGO
0.016 0.018 0.004 0.0016 0.0021 /

12.14.60. DIFFCGO 1219

Keywords for formats tN, E1, E3 19.1

12.14.61. DIFFCOG

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets cross phase diffusion coefficients. They are used to define cross phase
diffusion from a cell containing oil to a cell containing gas (see section 3.11.1). The opposite
diffusive flow is set by the keyword DIFFCGO (see 12.14.60).
Option of molecular diffusion is switched on via the keyword DIFFUSE (see 12.1.70).
The following parameters should be specified:

1. cross phase diffusion coefficient for each model component (METRIC: m2 /day;
FIELD: f t 2 /day).
Default: 0.

The data should be terminated with a slash /.

Example
DIFFCOG
0.016 0.018 0.004 0.0016 0.0021 /

12.14.61. DIFFCOG 1220

Keywords for formats tN, E1, E3 19.1

12.14.62. VDKRG

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword is used to specify the tables of gas velocity dependent relative permeability
(see section 2.6.14). The number of tables is specified by the first parameter of the keyword
TABDIMS (see 12.1.29). 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 parameter ag for gas. This value should be specified for Forchheimer
model B1 (UNITS: Forch(mD)d , 1 Forch = 1 atm.s2 .gm−1 ; 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 (UNITS: Forch/(mD)d , 1 Forch = 1 atm.s2 .gm−1 ; value of d is set by
parameter 8).
Default: 0 for all parameters.

Example
VDKRG
– M N1 N2 Ncb
23.89 6.23 0.0 6.0E-05 /

12.14.62. VDKRG 1221

Keywords for formats tN, E1, E3 19.1

In the example is specified one table. The base gas capillary number was specified by the
keyword VELDEP.

12.14.62. VDKRG 1222

Keywords for formats tN, E1, E3 19.1

12.14.63. VDKRGC

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets data for capillary number based model of velocity dependent relative
permeability for near wellbore gas flow in a gas condensate reservoir (see section 2.6.14).
The number of data lines should be equal to the value of the 1-st parameter of the keyword
TABDIMS (see 12.1.29).
Capillary number and Forchheimer model are set via the keyword VELDEP (see 12.1.8). If
the 5-th parameter of VELDEP (see 12.1.8) is 1, then parameters of VDKRGC (see 12.14.63)
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.
Default: 0.65.

2. coefficient αc0 . It is used to scale capillary number.

Default: 1.0E4.

Each data line should be ended by a symbol /.

Example
VDKRGC
0.7 1000 /
0.65 1000 /

12.14.63. VDKRGC 1223

Keywords for formats tN, E1, E3 19.1

12.14.64. VDKRO

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword is used to specify the tables of oil velocity dependent relative permeability
(see section 2.6.14). The number of tables is specified by the first parameter of the keyword
TABDIMS (see 12.1.29). 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 parameter ag for oil. This value should be specified for Forchheimer model
B1 (UNITS: Forch(mD)d , 1 Forch = 1 atm.s2 .gm−1 ; 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 .gm−1 ; value of d is set by
parameter 8).
Default: 0 for all parameters.

Example
VDKRO
– M N1 N2 Ncb
79.62 24.2 0.0 6.0E-05 /

12.14.64. VDKRO 1224

Keywords for formats tN, E1, E3 19.1

In the example is specified one table. The base oil capillary number was specified by the
keyword VELDEP.

12.14.64. VDKRO 1225

Keywords for formats tN, E1, E3 19.1

12.14.65. PEDERSEN

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies that viscosities will be calculated via Pedersen’s method (see section
Pedersen Correlation).
If this keyword is not specified default method will be used - Lohrenz-Bray-Clark Correlation
(see section 3.8.1).
Example
PEDERSEN

12.14.65. PEDERSEN 1226

Keywords for formats tN, E1, E3 19.1

12.14.66. PEDTUNE

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword is used to set user parameters of Pedersen viscosity correlation (3.8.3)) in
the entire reservoir. If you need to set user parameters in each EoS region use the keyword
PEDTUNER (see 12.14.67).
The following parameters should be specified:
1. parameter 1 value. Allowed values: 0.1 − 10.
Default: 1.
2. parameter 2 value. Allowed values: 0.1 − 10.
Default: 1.
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 × 10−4 (M¯w 2 − M̄n 2 ) + Mn ,
where:
• M¯w – weight average mole weight.
• M̄n – number average mole weight.
• c1 and c2 – parameters 1 and 2 which are set above.
3. parameter 3 value. Allowed values: -100 − 100.
Default: 1.847.
4. parameter 4 value. Allowed values: -1000 − 1.5.
Default: 0.5173.
5. parameter 5 value. Allowed values: -0.15 − 0.1.
Default: 7.378E-3.
6. parameter 6 value. Allowed values: -0.2 − 1.1.
Default: 3.1E-2.
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:

12.14.66. PEDTUNE 1227

Keywords for formats tN, E1, E3 19.1

• ρrmix – reduced density;

• c3 , c4 , c5 and c6 – parameters 3-6 which are set above.

The data should be terminated with a slash /.

Example
PEDTUNE
0.1000 1.2190 /
In the example via the keyword PEDTUNE (see 12.14.66) user values of the first two
parameters of Pedersen correlation are set. Other ones are set by default.

12.14.66. PEDTUNE 1228

Keywords for formats tN, E1, E3 19.1

12.14.67. PEDTUNER

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword is analogous to the keyword PEDTUNE (see 12.14.66), but it is used to set
user values of Pedersen (3.8.3)) 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.14.67) parameters of Pedersen viscos-
ity correlation are set for two EoS regions. The first two parameters are set by user, the others
are set by default.

12.14.67. PEDTUNER 1229

Keywords for formats tN, E1, E3 19.1

12.14.68. NCOMPS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword confirms the number of components for compositional run in E1/E3 format.
The keyword is optional and it shouldn’t be used in tNavigator. Use the keyword COMPS
(see 12.14.1) to set the number of components.

12.14.68. NCOMPS 1230

Keywords for formats tN, E1, E3 19.1

12.14.69. DNGL

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword is used for compositional models which use gas plants producing NGLs
(natural gas liquid) (see section 2.14.5). It sets densities for components of NGL which defined
via the keyword GPTABLEN (see 12.16.27). Densities are converted to partial molar volumes,
and the molar volume of a NGL mixture is calculated as a mole fraction weighted sum.
The following parameters should be specified:

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: values from DREF (see 12.15.41), and if it is not specified either, then 799.2
kg/m3 .

The data should be terminated with a slash /.

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.14.69. DNGL 1231

Keywords for formats tN, E1, E3 19.1

12.14.70. SOLUBILI

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets properties of water-gas system as a table. The dissolved gas can either
be CO 2 (CO2SOL, see 12.1.92) or H2 S (H2SSOL, see 12.1.93). All keywords used for the
CO 2 or H2 S solution option are given in the section 3.3.1. 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).

The data should be terminated with a slash /.

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-gas system are set.

12.14.70. SOLUBILI 1232

Keywords for formats tN, E1, E3 19.1

12.14.71. RSWVD

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword sets dissolved gas concentration in water phase dependence on depth as
a table. The dissolved gas can either be CO 2 (CO2SOL, see 12.1.92) or H2 S (H2SSOL,
see 12.1.93). All keywords used for the CO 2 or H2 S solution option are given in the section
3.3.1. Each line of the table contains the following parameters:

1. depth values (METRIC: m; FIELD: f t ). They should increase monotonically down

column;

2. gas (CO 2 or H2 S ) concentration in water phase (METRIC: sm3 /sm3 ; FIELD:

stb/Msc f ).

The data should be terminated with a slash /.

Example
RSWVD
200 0.001
20000 0.002
/

12.14.71. RSWVD 1233

Keywords for formats tN, E1, E3 19.1

12.15. Thermal properties

Compositional thermal model is described in details in the section 4, where all used formulas
and references to keywords are given.

12.15. Thermal properties 1234

Keywords for formats tN, E1, E3 19.1

12.15.1. CGDTYPE

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can only be used if THERMAL (see 12.1.54) option is present. This keyword
is specify how the gas phase molar density is computed using an equation of state (EoS). The
detailed information is given in the section 4.7.
By default Peng-Robinson (PR) equation of state is defined. The type of equations of state
can be defined by keyword EOS (see 12.14.6).
If this keyword is used all of the keywords required by the EoS, such as BIC (see 12.14.40),
should be added in the PROPS section (even when all items are NO).
The keyword should be followed by one of the following types:

• NO
Not used. The molar volume for this component is computed as if this keyword were
not defined;

• EMIX
An equation of state is solved for the EMIX components. The highest (vapor) root of
the cubic equation of state is selected.

Default: EMIX.
If several equations of state are used, a set of abovementioned data should be defined
for each reservoir EoS. The number of EoS regions is defined by 9-th parameter of keyword
TABDIMS (see 12.1.29).
The data for each region should be terminated with a symbol slash /.
Notice that if subset of the mixture selected for EoS calculation includes mostly heavy
components, but the number of light components are small, the mixture can produce a molar
volume similar to that of a oil or give an unphysical molar volume.
In a thermal calculation 2 hydrocarbon components are used:
Example
CGDTYPE
EMIX EMIX /

12.15.1. CGDTYPE 1235

Keywords for formats tN, E1, E3 19.1

12.15.2. CGVTYPE

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can only be used if THERMAL (see 12.1.54) option is present. This keyword
is specify how the gas viscosity is computed. Other approaches to input oil phase component
viscosities (as function of temperature) are given in the section 4.13. If this keyword is defined
an equation of state (EoS) can be used.
The keyword should be followed by one of the following types:

• NO
Not used. The viscosity for this component is computed as if this keyword is not defined;

• LEMIX
The Lorentz-Bray-Clark (LBC) viscosity model is applied on the LEMIX components
densities. The phase molar density is computed using the EoS.

If several equations of state are used, a set of abovementioned data should be defined
for each reservoir EoS. The number of EoS regions is defined by 9-th parameter of keyword
TABDIMS (see 12.1.29).
The data for each region should be terminated with a symbol slash /.
Notice that if subset of the mixture selected for EoS calculation includes mostly heavy
components, but the number of light components are small, the mixture can produce a molar
volume similar to that of a oil, thus, the obtained viscosity can be similar to oil viscosity.
In the thermal calculation 7 hydrocarbon components are used:
Example
CGVTYPE
LEMIX LEMIX LEMIX LEMIX LEMIX LEMIX LEMIX/

12.15.2. CGVTYPE 1236

Keywords for formats tN, E1, E3 19.1

12.15.3. CODTYPE

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can only be used if THERMAL (see 12.1.54) option is present. This keyword
specifies how the oil phase molar density is computed using an equation of state (EoS). The
detailed information is given in the section 4.6.
By default Peng-Robinson (PR) equation of state is assumed. The type of equations of
state can be defined by keyword EOS (see 12.14.6).
If this keyword is used all of the keywords required by the EoS, such as BIC (see 12.14.40),
should be added in the PROPS section (even when all items are NO).
The keyword should be followed by one of the following types:

• NO
Not used. The molar volume for this component is computed as if this keyword were
not defined;

• EMIX
An equation of state is solved for the EMIX components. The lowest (liquid) root of
the cubic equation of state is selected.
Default: EMIX.

If several equations of state are used, a set of abovementioned data should be defined
for each reservoir EoS. The number of EoS regions is defined by 9-th parameter of keyword
TABDIMS (see 12.1.29).
The data for each region should be terminated with a symbol slash /.
Notice that if subset of the mixture selected for EoS calculation includes mostly light
components, but the number of heavy components is small, the mixture can produce a molar
volume similar to that of a gas.
In a thermal calculation 2 hydrocarbon components are used:
Example
CODTYPE
EMIX EMIX /

12.15.3. CODTYPE 1237

Keywords for formats tN, E1, E3 19.1

12.15.4. COVTYPE

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can only be used if THERMAL (see 12.1.54) option is present. This keyword
is specify how the oil viscosity is computed. Other approaches to input oil phase component
viscosities (as function of temperature) are given in the section 4.12. If this keyword is defined
an equation of state (EoS) can be used.
The keyword should be followed by one of the following types:

• NO
Not used. The viscosity for this component is computed as if this keyword is not defined;

• LEMIX
The Lorentz-Bray-Clark (LBC) viscosity model is applied on the LEMIX components
densities. The phase molar density is computed using the EoS.

If several equations of state are used, a set of abovementioned data should be defined
for each reservoir EoS. The number of EoS regions is defined by 9-th parameter of keyword
TABDIMS (see 12.1.29).
The data for each region should be terminated with a symbol slash /.
Notice that if subset of the mixture selected for EoS calculation includes mostly light
components, but the number of heavy components are small, the mixture can produce a molar
volume similar to that of a gas, thus, the obtained viscosity can be similar to gas viscosity.
In a thermal calculation 7 hydrocarbon components are used:
Example
COVTYPE
LEMIX LEMIX LEMIX LEMIX LEMIX LEMIX LEMIX/

12.15.4. COVTYPE 1238

Keywords for formats tN, E1, E3 19.1

12.15.5. CVTYPE

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can only be used if THERMAL (see 12.1.54) is present.

The detailed description of compositional thermal model is given in the section 4.
The keyword sets the component volatility type for each component. The same number
of values as the number of components (COMPS, see 12.14.1) should be entered. 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 and 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.15.5. CVTYPE 1239

Keywords for formats tN, E1, E3 19.1

12.15.6. CVTYPES

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies the component volatility types for surface calculations.
Volatility types for reservoir calculation are set via CVTYPE (see 12.15.5).
This keyword is optional. If it is not specified, then reservoir values will be used for
surface calculation.
Keyword syntax is similar to CVTYPE (see 12.15.5).

12.15.6. CVTYPES 1240

Keywords for formats tN, E1, E3 19.1

12.15.7. CCTYPE

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can only be used if THERMAL (see 12.1.54) is present.

It specifies the compressibility type of hydrocarbon components in the liquid phase.
The component’s density is calculated using one of the two approaches:

• As for a liquid, according to the formula 4.11 with the use of constants defined by
CREF (see 12.15.45), DREF (see 12.15.41), PREF (see 12.15.35), TREF (see 12.15.38),
and THERMEX1 (see 12.15.32) (see section 4.6);

• As for a gas, via ZFACTOR (see 12.15.50) (see section 4.7).

The keyword should be followed by a series of values, one for each component. The value
should be selected from:

• OIL for liquid-like compressibility;

• GAS for gas-like compressibility.

The values may be enclosed in quotes. Only the first character is significant.
If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.
Example
CCTYPE
OIL OIL GAS GAS /
In this example the compressibility type is defined for 4 components, with liquid type
specified for the first and second components, and gas type for the rest.

12.15.7. CCTYPE 1241

Keywords for formats tN, E1, E3 19.1

12.15.8. CCTYPES

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies the compressibility type of hydrocarbon components for surface
calculations.
Compressibility types for reservoir calculation are set via CCTYPE (see 12.15.7).
This keyword is optional. If it is not specified, then reservoir values will be used for
surface calculation.
Keyword syntax is similar to CCTYPE (see 12.15.7).

12.15.8. CCTYPES 1242

Keywords for formats tN, E1, E3 19.1

12.15.9. WATDENT

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can only be used if THERMAL (see 12.1.54) is present.

The keyword sets water molar density as a function of temperature for each PVT region (the
number of PVT regions is equal to the 2-nd parameter of TABDIMS, see 12.1.29). Formulas
for calculation of mass and molar water density for models in E3 format are given in the
section 4.5 – Eq.(4.6). The data for each region should be terminated with a slash /.

The following parameters are to be specified:

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 ).

Example
WATDENT
293 0.00027 0.0000034 /

12.15.9. WATDENT 1243

Keywords for formats tN, E1, E3 19.1

12.15.10. THANALB

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can only be used if THERMAL (see 12.1.54) is present.

The keyword sets that water molar and mass densities are calculated using the formulae (4.5)
given in the section 4.5.
If the keyword is not defined but WATDENT (see 12.15.9) is specified, then densities are
calculated using Eqs. (4.6) (see section 4.5)
Example
THANALB

12.15.10. THANALB 1244

Keywords for formats tN, E1, E3 19.1

12.15.11. KVCR

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can only be used if THERMAL (see 12.1.54) is present.

The keyword sets 5 constants (Ai , Bi , Ci , Di , Ei ) for each component which are used
in the correlation formula 4.22 for calculation of the partition coefficient, i.e., the ratio of
mole fraction of the component in vapor to its mole fraction in liquid phases Ki (p, T ) (see
section 4.9), where p is the pressure (METRIC: barsa, FIELD: psia), T is the temperature
(METRIC: K, FIELD: ◦ R).
The data should be terminated with a slash /.

The following parameters are to be specified:

1. Ai (dimensionless); N values should be entered (number of components, see COMPS,

see 12.14.1).

2. Bi (METRIC: barsa, FIELD: psia); N values should be entered (number of compo-

nents, see COMPS, see 12.14.1).

3. Ci (METRIC: 1/barsa, FIELD: 1/psia); N values should be entered (number of com-

ponents, see COMPS, see 12.14.1).

4. Di (METRIC: K , FIELD: ◦ R); N values should be entered (number of components,

see COMPS, see 12.14.1).

5. Ei (METRIC: K , FIELD: ◦ R); N values should be entered (number of components,

see COMPS, see 12.14.1).

If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
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.15.13),
KVTABTn (see 12.15.14).
K-values for calculations at surface condition can be set optionally via KVCRS (see 12.15.12).

12.15.11. KVCR 1245

Keywords for formats tN, E1, E3 19.1

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.15.11. KVCR 1246

Keywords for formats tN, E1, E3 19.1

12.15.12. KVCRS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets K-values for surface calculation for thermal runs (THERMAL,
see 12.1.54).
K-values for reservoir calculation are set via KVCR (see 12.15.11).

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.15.11).

12.15.12. KVCRS 1247

Keywords for formats tN, E1, E3 19.1

12.15.13. KVTEMP

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can only be used if THERMAL (see 12.1.54) is present.

The keyword sets the temperature values (METRIC: ◦ C, FIELD: ◦ F) for Ki (p, T ) tables en-
tered using the keyword KVTABTn (see 12.15.14) for each component, where Ki (p, T ) are the
partition coefficients, i.e., ratios of mole fraction of a component in vapor to its mole fraction
in liquid phases (see section 4.9). The number of temperature values should be equal to the
15-th parameter of TABDIMS (see 12.1.29). The data should be terminated with a slash /.

Ki (p, T )-values can be entered using the correlation formula (KVCR, see 12.15.11).

Example
KVTEMP
300 500 700
/

This example sets 3 temperature values for Ki (p, T ) tables.

12.15.13. KVTEMP 1248

Keywords for formats tN, E1, E3 19.1

12.15.14. KVTABTn

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can only be used if THERMAL (see 12.1.54) is present.

The keyword sets Ki (p, T ) tables for each component, where Ki (p, T ) are the partition coeffi-
cients, i.e., ratios of mole fraction of a component in vapor to its mole fraction in liquid phases
(see section 4.9). Each KVTABTn (see 12.15.14) corresponds to its temperature, entered using
KVTEMP (see 12.15.13).

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.14.1).

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.15.11).

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.15.13).

12.15.14. KVTABTn 1249

Keywords for formats tN, E1, E3 19.1

12.15.15. KVTABLIM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can only be used if THERMAL (see 12.1.54) is present.

The keyword sets Ki (p, T ) tables for components, where Ki (p, T ) are the partition coeffi-
cients, i.e., ratios of mole fraction of a component in vapor to its mole fraction in liquid
phases (see section 4.9). For each component one should use individual keyword KVTABLIM.

The following parameters are to be specified:

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: bar , FIELD: psi) – plow.

5. The maximal value of pressure for Ki (p, T ) (METRIC: bar , FIELD: psi) – phigh.

6. The minimal value of temperature for Ki (p, T ) (METRIC: K, FIELD: ◦ R) – T low.

7. The maximal value of temperature for Ki (p, T ) (METRIC: K, FIELD: ◦ R) – 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 lin-
early 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.15.15. KVTABLIM 1250

Keywords for formats tN, E1, E3 19.1

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.15.15. KVTABLIM 1251

Keywords for formats tN, E1, E3 19.1

12.15.16. KVWI

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can only be used if THERMAL (see 12.1.54) is present.

If KVWI is specified then the ratio of mole fraction of component in vapor to its mole frac-
tion in liquid phases Ki (p, T ) (see section 4.9) for oil components are calculated using the
following correlation formula:
pci 5.372697·(1+Ai )·(1−Tci /T )
Ki (p, T ) = ·e
p
where

• Tci – component critical temperature TCRIT (see 12.14.20);

• pci – component critical pressure PCRIT (see 12.14.22);

• Ai – component acentric factor ACF (see 12.14.38).

K-values Ki = Ki (p, T ) can be entered either directly using the tables KVTEMP
(see 12.15.13), KVTABTn (see 12.15.14), or via the correlation formula KVCR (see 12.15.11).
Example
KWVI

12.15.16. KVWI 1252

Keywords for formats tN, E1, E3 19.1

12.15.17. HEATCR

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can only be used if THERMAL (see 12.1.54) is present.

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 num-
ber of grid blocks. The rock volumetric heat capacity specified by this keyword is used for
calculation of rock enthalpy (see section 4.21). The data should be terminated with a slash /.
Example
DIMENS
10 10 2
/
...
HEATCR
100*32 50*35 50*37 /
/
This example sets the rock volumetric heat capacity: for the first 100 grid blocks – 32
kJ/m3 /K , for the next 50 blocks – 35 kJ/m3 /K , and for the remaining 50 blocks – 37
kJ/m3 /K .

12.15.17. HEATCR 1253

Keywords for formats tN, E1, E3 19.1

12.15.18. HEATCRT

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can only be used if THERMAL (see 12.1.54) is present.

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 rock volumetric heat capacity
specified by this keyword is used for calculation of rock enthalpy (see section 4.21). The
same number of values should be specified as the number of grid blocks. The data should be
terminated with a slash /.
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
the first 100 grid blocks – 0.0004 kJ/m3 /K 2 , for the next 50 blocks – 0.0003 kJ/m3 /K 2 , and
for the remaining 50 blocks – 0.0001 kJ/m3 /K 2 .

12.15.18. HEATCRT 1254

Keywords for formats tN, E1, E3 19.1

12.15.19. HEATTCR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can only be used if THERMAL (see 12.1.54) is present.

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 to which it belongs, and hence the corresponding table of transmissibility vs.
pressure). Parameters specified by this keyword are used for calculation of rock enthalpy (see
section 4.21).

The same number of data entries should be specified as the number of rock regions (see
below the note on setting the number of rock regions). The following data should be specified
for each region:

1. Rock volumetric heat capacity.

Default: not specified.

2. Temperature dependence of the rock volumetric heat capacity.

Default: 0.

The data for each region should be terminated with a slash /.

The keyword has E1/E3-compatible analogues HEATCR (see 12.15.17), HEATCRT
(see 12.15.18).
Setting the number of rock regions
The number of rock regions can be set in TABDIMS (see 12.1.29) (13-th parameter) and
ROCKCOMP (see 12.1.37) (2-nd parameter). The option to set the number of rock regions
depends on the way to set rock properties:

• ROCKCOMP (see 12.1.37) – ROCKTAB (see 12.5.21).

If the number of rock regions is specified both in 13-th parameter of TABDIMS
(see 12.1.29) and in 2-nd parameter of ROCKCOMP (see 12.1.37), then the follow-
ing logic is used to calculate the number of rock regions:

– E1 format: only the 2-nd parameter of ROCKCOMP (see 12.1.37) is used;

– E3 format: the maximum value is taken from the 13-th parameter of TABDIMS
(see 12.1.29), and 2-nd parameter of ROCKCOMP (see 12.1.37).

• ROCK (see 12.5.17).

The number of rock regions is specified via 13-th parameter of TABDIMS (see 12.1.29);

12.15.19. HEATTCR 1255

Keywords for formats tN, E1, E3 19.1

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.29)..

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.15.19. HEATTCR 1256

Keywords for formats tN, E1, E3 19.1

12.15.20. HEATVAP

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword can only be used if THERMAL (see 12.1.54) is present.

The keyword specifies the coefficient Ac (METRIC: kJ/kg, FIELD: Btu/lb) in the formula
for calculation of the vaporization enthalpy of a gaseous oil component (see section 4.18).
Default: 0.
The same number of values as the number of components (COMPS, see 12.14.1) should
be entered. The data should be terminated with a slash /.

If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.

Example
HEATVAP
322 118 109 /

This example specifies the coefficient Ac for three components.

12.15.20. HEATVAP 1257

Keywords for formats tN, E1, E3 19.1

12.15.21. HEATVAPE

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword can only be used if THERMAL (see 12.1.54) is present.

The keyword specifies the coefficient Bc in the formula for calculation of the vaporization
enthalpy of a gaseous oil component (see section 4.18). The same number of values as the
number of components N (COMPS, see 12.14.1) should be entered. The data should be ter-
minated with a slash /.

Default: 0.38.
If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.

Example
HEATVAPE
3* /

This example specifies default values 0.38 for the coefficient Bc for three components.

12.15.21. HEATVAPE 1258

Keywords for formats tN, E1, E3 19.1

12.15.22. THCONR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can be used in thermal models (keyword THERMAL, see 12.1.54) or in
temperature option in black-oil models (2.26).
The keyword sets the rock thermal conductivity (METRIC: kJ/m/day/C , FIELD:
Btu/ f t/day/F ). Formulas for calculation of thermal conductivity of the grid block are given
in the section 4.28. The same number of values as the number of grid blocks should be spec-
ified. 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.15.22. THCONR 1259

Keywords for formats tN, E1, E3 19.1

12.15.23. THCONSF

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can be used in thermal models (keyword THERMAL, see 12.1.54) or in
temperature option in black-oil models (2.26).
If the keyword is enabled the thermal conductivity (specified using THCONR, see 12.15.22)
is multiplied by a multiplier 1 − αSG .
The value of α should not be less than 0 and greater than 1. α is specified using this
keyword. Formulas for calculation of thermal conductivity of the grid block are given in the
section 4.28. The same number of values should be specified as the number of grid blocks.
The data should be terminated with a slash /.
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.15.23. THCONSF 1260

Keywords for formats tN, E1, E3 19.1

12.15.24. ROCKT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.

The following parameters should 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 parameter;

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.29).
In ST 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.15.24) to specify cT , c pT ;

• pref – reference pressure for ϕ(x, y, z) (PRPOR) (default – the pressure in the first active
grid block).

12.15.24. ROCKT 1261

Keywords for formats tN, E1, E3 19.1

• Tre f – reference temperature TEMR (see 13.5.26).

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.15.24. ROCKT 1262

Keywords for formats tN, E1, E3 19.1

12.15.25. THCONMIX

Data x tN E1 x E3 IM GE x ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets the method of block thermal conductivity calculation for each rock
region. Data for each region is set in separate line.
The detailed description of thermal conductivity calculation is provided in section 4.28.
The avaliable methods are:

• SIMPLE (see 4.64);

• LOG (see 4.65);

• COMPLEX (see 4.66);

• TEMPER (see 4.67).

Each line should be terminated with a slash /.

Example
THCONMIX
SIMPLE /
/
This example specifies the method of block thermal conductivity calculation – SIMPLE.

12.15.25. THCONMIX 1263

Keywords for formats tN, E1, E3 19.1

12.15.26. STHERMX1

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets the thermal expansion coefficient for each component (METRIC: 1/K,
FIELD: 1/◦ R) in the solid phase. This thermal expansion coefficient is used for calculation
of the component density k in the solid phase at pressure p and temperature T for models in
E3 and ST formats (see section 4.8).
The same number of values as the number of components should be specified (COMPS,
see 12.14.1). The data should be terminated with a slash /.

Default: 0.
If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.

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.15.26. STHERMX1 1264

Keywords for formats tN, E1, E3 19.1

12.15.27. STHERMX2

Data x tN E1 x E3 IM GE x ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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)). This coef-
ficient is used for calculation of the component density k in the solid phase at pressure p and
temperature T for models in E3 and ST formats (see section 4.8).
The same number of values as the number of components should be specified (COMPS,
see 12.14.1). The data should be terminated with a slash /.

Default: 0.
If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.

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.15.27. STHERMX2 1265

Keywords for formats tN, E1, E3 19.1

12.15.28. SDREF

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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 ). The formula used for calcula-
tion of the component density k in the solid phase at pressure p and temperature T is given
in the section 4.8.
The same number of values as the number of components should be specified (COMPS,
see 12.14.1). The data should be terminated with a slash /.

If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.

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.15.28. SDREF 1266

Keywords for formats tN, E1, E3 19.1

12.15.29. SPREF

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets the reference pressure for each component in the solid phase (METRIC:
bars, FIELD: psi), which is used for calculation of the component density k in the solid
phase at pressure p and temperature T (see section 4.8).
The same number of values as the number of components should be specified (COMPS,
see 12.14.1). The data should be terminated with a slash /.

If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.

Example
SPREF
120 125
/

This example sets the reference pressure for two components: for 1-st component – 120,
for 2-nd component – 125.

12.15.29. SPREF 1267

Keywords for formats tN, E1, E3 19.1

12.15.30. SCREF

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets the component compressibility for each component in the solid phase
(METRIC: 1/bars, FIELD: 1/psi). This component compressibility is used for calculation
of the component density k in the solid phase at pressure p and temperature T (see section
4.8).
The same number of values as the number of components should be specified (COMPS,
see 12.14.1). The data should be terminated with a slash /.

If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.

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.15.30. SCREF 1268

Keywords for formats tN, E1, E3 19.1

12.15.31. STREF

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets the reference temperature for each component in the solid phase (MET-
RIC: K, FIELD: ◦ R), which is used for calculation of the component density k in the solid
phase at pressure p and temperature T (see section 4.8).
The same number of values as the number of components should be specified (COMPS,
see 12.14.1). The data should be terminated with a slash /.

If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.

Example
STREF
320 380 280
/

This example sets the reference temperature for three components.

12.15.31. STREF 1269

Keywords for formats tN, E1, E3 19.1

12.15.32. THERMEX1

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets the first thermal expansion coefficient for each component in the liquid
phase (METRIC: 1/K, FIELD: 1/◦ R. The first thermal expansion coefficient is used for cal-
culation of the component k liquid density at pressure p and temperature T for models in E3
and ST formats (see section 4.6).

The same number of values as the number of components should be specified (COMPS,
see 12.14.1). The data should be terminated with a slash /.

Default: 0.
If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.

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.
Second and third expansion coefficients are specified by keywords THERMEX2
(see 12.15.33) and THERMEX3 (see 12.15.34), respectively.

12.15.32. THERMEX1 1270

Keywords for formats tN, E1, E3 19.1

12.15.33. THERMEX2

Data x tN E1 x E3 IM GE x ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets the second thermal expansion coefficient for each component in the
liquid phase (METRIC: 1/◦C2 , FIELD: 1/◦ F 2 . The second thermal expansion coefficient is
used for calculation of the component k liquid density at pressure p and temperature T for
models in E3 and ST formats (see section 4.6).
The same number of values as the number of components should be specified (COMPS,
see 12.14.1). The data should be terminated with a slash /.

Default: 0.
If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.

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.
First and third expansion coefficients are specified keywords THERMEX1 (see 12.15.32)
and THERMEX3 (see 12.15.34), respectively.

12.15.33. THERMEX2 1271

Keywords for formats tN, E1, E3 19.1

12.15.34. THERMEX3

Data x tN E1 x E3 IM GE x ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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 third
thermal expansion coefficient is used for calculation of the component k liquid density at
pressure p and temperature T for models in E3 and ST formats (see section 4.6).
The same number of values as the number of components should be specified (COMPS,
see 12.14.1). The data should be terminated with a slash /.

Default: 0.
If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.

Example
THERMEX3
0.0000024 0.0000033 2*
/

This example sets the coefficient of density dependence on temperature and pressure 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.
First and second expansion coefficients are specified keywords THERMEX1 (see 12.15.32)
and THERMEX2 (see 12.15.33), respectively.

12.15.34. THERMEX3 1272

Keywords for formats tN, E1, E3 19.1

12.15.35. PREF

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets the reference pressure for each component in the liquid phase (METRIC:
bars, FIELD: psi), which is used for calculation of the component k density in the liquid
phase at pressure p and temperature T (see section 4.6).

The same number of values as the number of components should be specified (COMPS,
see 12.14.1). The data should be terminated with a slash /.

Default: pressure from STCOND (see 12.14.11).

If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.

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.15.35. PREF 1273

Keywords for formats tN, E1, E3 19.1

12.15.36. PREFT

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is an alias for the keyword PREF (see 12.15.35).

12.15.36. PREFT 1274

Keywords for formats tN, E1, E3 19.1

12.15.37. PREFS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets the reference pressure of the components for surface calculations. The
detailed description of compositional thermal model is given in the section 4.

It is optional; if not specified, the reservoir values specified by PREF (see 12.15.35) are
used instead.
Keyword syntax is similar to PREF (see 12.15.35).

12.15.37. PREFS 1275

Keywords for formats tN, E1, E3 19.1

12.15.38. TREF

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets the reference temperature for each component in the liquid phase (MET-
RIC: K, FIELD: ◦ R), which is used for calculation of the component k density in the liquid
phase at pressure p and temperature T (see section 4.6).

The same number of values as the number of components should be specified (COMPS,
see 12.14.1). The data should be terminated with a slash /.

Default: temperature from STCOND (see 12.14.11).

If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.

Example
TREF
120 180 200
/

This example sets the reference temperature for 3 components in the liquid phase.

12.15.38. TREF 1276

Keywords for formats tN, E1, E3 19.1

12.15.39. TREFT

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is analogue of the keyword TREF (see 12.15.38).

12.15.39. TREFT 1277

Keywords for formats tN, E1, E3 19.1

12.15.40. TREFS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets the reference temperature of the components for surface calculations.
The detailed description of compositional thermal model is given in the section 4.

It is optional; if not specified, the reservoir values specified by TREF (see 12.15.38) are
used instead.
Keyword syntax is similar to TREF (see 12.15.38).

12.15.40. TREFS 1278

Keywords for formats tN, E1, E3 19.1

12.15.41. DREF

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets the density at reference pressure and reference temperature for each com-
ponent in the liquid phase (METRIC: kg/m3 , FIELD: lb/ f t 3 ), which is used for calculation of
the component k density in the liquid phase at pressure p and temperature T (see section 4.6).

The same number of values as the number of components should be specified (COMPS,
see 12.14.1). The data should be terminated with a slash /.

Default: 80% of the water density.

If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.

Example
DREF
49.2 39.3 37.4
/

This example sets the density of three components at reference pressure and reference
temperature.

12.15.41. DREF 1279

Keywords for formats tN, E1, E3 19.1

12.15.42. DREFT

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword is analogue of the keyword DREF (see 12.15.41).

12.15.42. DREFT 1280

Keywords for formats tN, E1, E3 19.1

12.15.43. DREFS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets the density of the components at their respective reference pressures
and temperatures for surface calculations. The detailed description of compositional thermal
model is given in the section 4.

It is optional; if not specified, the reservoir values specified by DREF (see 12.15.41) are
used instead.
Keyword syntax is similar to DREF (see 12.15.41).

12.15.43. DREFS 1281

Keywords for formats tN, E1, E3 19.1

12.15.44. VREFW

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets reference viscosity and viscosibility values for water components in
multiple component water run.
Multiple component water option is activated with the keyword COMPW (see 12.14.2).
Description of this option is in the section 3.10.
The following parameters should be specified:

1. reference viscosity values for water components (cP). Nw values should be specified,
where Nw is the number from COMPW (see 12.14.2).
Default: 0.3 cP.

2. reference viscosibility values for water components (METRIC: 1/bar , FIELD: 1/psi).
Nw values also should be specified.
Default: 0.

If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /. The data should be terminated
with a slash /.
Example
VREFW
0.33 0.35 0.31
0.0 0.0 0.0 /
In the example reference viscosity and reference viscosibility values are specified for 3
water components.

12.15.44. VREFW 1282

Keywords for formats tN, E1, E3 19.1

12.15.45. CREF

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets the compressibility for each component in the liquid phase (METRIC:
1/bars, FIELD: 1/psi), which is used for calculation of the component k density in the liquid
phase at pressure p and temperature T (see section 4.6).

The same number of values as the number of components should be specified (COMPS,
see 12.14.1). The data should be terminated with a slash /.

Default: 0.
If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.

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.15.45. CREF 1283

Keywords for formats tN, E1, E3 19.1

12.15.46. CREFW

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets compressibility values for water components in multiple component
water run.
Multiple component water option is activated with the keyword COMPW (see 12.14.2).
Description of this option is in the section 3.10.
The following parameters should be specified:

1. water component compressibility (METRIC: 1/bars; FIELD: 1/psi). Nw values should

be specified, where Nw is the number from COMPW (see 12.14.2).
Default: 4.0e-5 1/atm.

If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /. The data should be terminated
with a slash /.
Example
CREFW
5.0E-06 5.1E-06 5.3E-06 /
In the example compressibility for 3 water component are set.

12.15.46. CREFW 1284

Keywords for formats tN, E1, E3 19.1

12.15.47. WI

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword sets water composition in multiple component water run.

Multiple component water option is activated with the keyword COMPW (see 12.14.2).
Description of this option is in the section 3.10.
The following parameters should be specified:

1. water composition. Nw values should be specified, where Nw is the number from

COMPW (see 12.14.2).

If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /. The data should be terminated
with a slash /.
Example
WI
0.5 0.0 0.5 /
In the example water composition is set. There are three water components.

12.15.47. WI 1285
Keywords for formats tN, E1, E3 19.1

12.15.48. WMFVD

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword sets molar fractures of water components dependence on depth. This depen-
dence is set in each EQUIL region. The keyword can be used only in multiple component
water run.
Multiple component water option is activated with the keyword COMPW (see 12.14.2).
Description of this option is in the section 3.10.
There is a table is set, which has Nw + 1 columns. Nw is the number from COMPW
(see 12.14.2). Columns:

1. depth (METRIC: m, FIELD: f t ). The values should increase monotonically;

2. molar fractures of water components on this depth. Nw values should be specified.

Each table should be ended by symbol /.

Example
WMFVD
1000 0.9 0.1
10000 0.9 0.1 /
In this example molar fractures of two components are set.

12.15.48. WMFVD 1286

Keywords for formats tN, E1, E3 19.1

12.15.49. WNAMES

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets names of water components for reporting purposes in multiple compo-
nent water run.
Multiple component water option is activated with the keyword COMPW (see 12.14.2).
Description of this option is in the section 3.10.
The following parameters should be specified:

1. water component name. Nw strings should be specified, where Nw is the number from
COMPW (see 12.14.2). They should be enclosed in quotes when blank characters are
used, or the name starts with a non-alphabetical character.

The data should be terminated with a slash /.

Example
WNAMES
Fresh1 Fresh2 /

12.15.49. WNAMES 1287

Keywords for formats tN, E1, E3 19.1

12.15.50. ZFACTOR

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can only be used if THERMAL (see 12.1.54) is present.

The keyword sets coefficients Zc,0 for each component for calculation of molar and mass gas
densities. Formulas for models in E3 and ST formats are given in the section 4.7.

The same number of values as the number of components N should be specified (COMPS,
see 12.14.1). The data should be terminated with a slash /.

Default: 0.96.
If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.

The coefficients Zc,1 are set via the keyword ZFACT1 (see 12.15.51).
Example
ZFACTOR
5*0.96
/

This example sets the coefficients Zc,0 of five components equal to 0.96.

12.15.50. ZFACTOR 1288

Keywords for formats tN, E1, E3 19.1

12.15.51. ZFACT1

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can only be used if THERMAL (see 12.1.54) is present.

The keyword sets the coefficients Zc,1 for each component for calculation of molar and mass
gas densities. All formulas for models in E3 and ST formats are given in the section 4.7.

The same number of values as the number of components N should be specified (COMPS,
see 12.14.1). The data should be terminated with a slash /.
The coefficient Zc,1 is set via ZFACT1 (see 12.15.51), pre f – STCOND (see 12.14.11). Mul-
tiplier 102 (4.47) results from units transformation: Zc,1 – m3 /kg-mol , so Zc,1 · (p − pre f ) –
m3 /kg-mol · bar = 105 · m3 · Pa/kg-mol = 102 · kJ/kg-mol .

Default: 0.
If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.

The coefficients Zc,0 are set via the keyword ZFACTOR (see 12.15.50).
Example
ZFACT1
5*0.15
/

This example sets the coefficients Zc,1 of five components equal to 0.15.

12.15.51. ZFACT1 1289

Keywords for formats tN, E1, E3 19.1

12.15.52. VISCREF

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can be used if THERMAL (see 12.1.54) is present or if temperature option
is enabled (2.26). The keyword sets reference pressure, which is used for calculation of oil or
water viscosity as a function of pressure and temperature (see sections 4.11, 4.12).

For models in E1 format (temperature option) this keyword is required if keywords OIL-
VISCT (see 12.15.54) or WATVISCT (see 12.15.53) are specified. For models in E3 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.60). For models in E1 format;

3. reference API gravity ( ◦ API). Specifying of this parameter is only required if the API
Tracking option is active (see keyword API (see 12.1.66) and chapter 2.8.8). For models
in E1 format.

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.15.52. VISCREF 1290

Keywords for formats tN, E1, E3 19.1

12.15.53. WATVISCT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can be used if THERMAL (see 12.1.54) is present or temperature option is
enabled (2.26).
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.29).
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:
µ 0 (p)
µW (p, T ) = µW (T ) 0 W
µW (pre f )
• µW (T ) – water viscosity (depends on temperature);

• µW
0 (p) – water viscosity as a function of pressure (specified using PVTW, see 12.5.5);

• pre f – reference pressure (specified using VISCREF, see 12.15.52).

Ways to specify water viscosity for models in E3 and ST formats and corresponding key-
words are given in the section 4.11.

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.15.53. WATVISCT 1291

Keywords for formats tN, E1, E3 19.1

12.15.54. OILVISCT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can be used if THERMAL (see 12.1.54) is present or if the temperature op-
tion is enabled (2.26). Additional information about ways to specify oil viscosity for models
in E3 and ST formats, corresponding formulas and keywords are given in the section 4.12.

Temperature option for models E1.

The keyword sets the table of oil viscosity as a function of temperature for each PVT re-
gion (The number of PVT regions is equal to the second parameter of TABDIMS, see 12.1.29).
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.15.52);

• µ p – viscosity from PVCO (see 12.5.6) (or PVDO, see 12.5.2);

• pre f – reference pressure, specified via VISCREF (see 12.15.52);

• Rsre f – reference Rs , specified via VISCREF (see 12.15.52).

Example
OILVISCT
75 3.0
128 0.58
/
In this example there is a table for one PVT region.

12.15.54. OILVISCT 1292

Keywords for formats tN, E1, E3 19.1

Thermal simulation for models E3.

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.29).
For each PVT region the table should be terminated with a slash /. Each row of the table
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.14.1).
Oil viscosity is calculated using the formula
n0c
µO (T ) = ∏ (µk,O ) fk (xk,O )
k=2

where oil component viscosity µk,O (T ) can be specified as a function of temperature using
the tables of this keyword OILVISCT (in E3 data format), VISCTABLE (see 13.5.68) (ST), or
using correlation (OILVISCC, see 12.15.55).
fk (x) (default: fk (x) = x ) are specified using OILVINDX (see 12.15.56) (in E3 data format) or
VSMIXCOMP (see 13.5.69), VSMIXENDP (see 13.5.70), VSMIXFUNC (see 13.5.71) (ST).
In E3 data format pressure dependence can be set:
µO0 (p)
µO (p, T ) = µO (T )
µ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);
• pre f – reference pressure (specified using VISCREF, see 12.15.52).

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.15.54. OILVISCT 1293

Keywords for formats tN, E1, E3 19.1

12.15.55. OILVISCC

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can only be used if THERMAL (see 12.1.54) is present. The keyword allows
to specify an oil viscosity – temperature correlation formula.
Ways to specify oil viscosity for models in E3 and ST formats, corresponding formulas and
keywords are given in the section 4.12.

For models in E3 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 ST 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.66), BVISC (see 13.5.67).

Using OILVISCC the oil viscosity – temperature correlation can be specified as:

• correlation. In this case values of temperature and viscosity should be specified and
coefficients A, B and C (if required) will be calculated by the program;

• formula. In this case coefficients A, B and C (if required) should be specified.

The keyword is followed by set of data. The first line consists of the name of the corre-
lation formula. Other lines contain data or the coefficients A, B and C. The data should be
terminated with a slash /.

To use ASTM correlation it is required to specify either:

1. ASTM CORRELATION

2. N +1 (COMPS, see 12.14.1) values: temperature T1 and viscosities µk,O (T1 ), k = 1, ..., N
(one value per component); a condition µk,O (T1 ) + 1 > µk,O (∞) should be valid

3. N +1 (COMPS, see 12.14.1) values: temperature T2 and viscosities µk,O (T2 ), k = 1, ..., N
(one value per component); a condition µk,O (T2 ) + 1 > µk,O (∞) should be valid

4. N (COMPS, see 12.14.1) values of viscosity µk,O (∞), k = 1, ..., N . The limiting viscos-
ity per component at temperature tending to infinity.

12.15.55. OILVISCC 1294

Keywords for formats tN, E1, E3 19.1

or coefficients:
1. ASTM FORMULA

2. coefficient A (N (COMPS, see 12.14.1) values: one value per component); A < 1

3. coefficient B (N (COMPS, see 12.14.1) values: one value per component); B > 0

4. coefficient C (N (COMPS, see 12.14.1) values: one value per component); C > 0
To use Andrade correlation it is required to specify either:
1. ANDRADE CORRELATION

2. N +1 (COMPS, see 12.14.1) values: temperature T1 and viscosities µk,O (T1 ), k = 1, ..., N
(one value per component); a condition µk,O (T1 ) + 1 > µk,O (∞) should be valid

3. N (COMPS, see 12.14.1) values of viscosity µk,O (∞), k = 1, ..., N . The limiting viscos-
ity per component at temperature tending to infinity.
or coefficients:
1. ANDRADE FORMULA

2. coefficient A (N (COMPS, see 12.14.1) values: one value per component);

3. coefficient B (N (COMPS, see 12.14.1) values: one value per component);

To use Vogel correlation it is required to specify either:
1. VOGEL CORRELATION

2. N +1 (COMPS, see 12.14.1) values: temperature T1 and viscosities µk,O (T1 ), k = 1, ..., N
(one value per component); a condition µk,O (T1 ) + 1 > µk,O (∞) should be valid

3. N +1 (COMPS, see 12.14.1) values: temperature T2 and viscosities µk,O (T2 ), k = 1, ..., N
(one value per component); a condition µk,O (T2 ) + 1 > µk,O (∞) should be valid

4. N (COMPS, see 12.14.1) values of viscosity µk,O (∞), k = 1, ..., N . The limiting viscos-
ity per component at temperature tending to infinity.
or coefficients:
1. VOGEL FORMULA

2. coefficient A (N (COMPS, see 12.14.1) values: one value per component);

3. coefficient B (N (COMPS, see 12.14.1) values: one value per component);

4. coefficient C (N (COMPS, see 12.14.1) values: one value per component);

To use Logarithmic correlation it is required to specify either:

12.15.55. OILVISCC 1295

Keywords for formats tN, E1, E3 19.1

1. LOG CORRELATION

2. N +1 (COMPS, see 12.14.1) values: temperature T1 and viscosities µk,O (T1 ), k = 1, ..., N
(one value per component); a condition µk,O (T1 ) + 1 > µk,O (∞) should be valid

3. N +1 (COMPS, see 12.14.1) values: temperature T2 and viscosities µk,O (T2 ), k = 1, ..., N
(one value per component); a condition µk,O (T2 ) + 1 > µk,O (∞) should be valid

or coefficients:

1. LOG FORMULA

2. coefficient A (N (COMPS, see 12.14.1) values: one value per component);

3. coefficient B (N (COMPS, see 12.14.1) values: one value per component);

If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
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.15.55. OILVISCC 1296

Keywords for formats tN, E1, E3 19.1

12.15.56. OILVINDX

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can only be used if THERMAL (see 12.1.54) is present. Ways to specify oil
viscosity for models in E3 and ST formats, corresponding formulas and keywords are given
in the section 4.12.

The keyword sets the table of functions fk (x) (indices in oil viscosity formula below) for
each PVT region (The number of PVT regions is equal to the second parameter of TABDIMS,
see 12.1.29).
For each PVT region the table should be terminated with a slash /. Each row of the table
consists of parameters:

• mole fraction value x (the number between 0 and 1);

• N values of fk (x) (N – the number of components COMPS, see 12.14.1). fk (0) =

0, fk (1) = 1.

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.15.56. OILVINDX 1297

Keywords for formats tN, E1, E3 19.1

12.15.57. OILVINDT

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION x SUMMARY SCHEDULE

This keyword can only be used if THERMAL (see 12.1.54) is present. Ways to specify oil
viscosity for models in E3 and ST formats, corresponding formulas and keywords are given
in the section 4.12.

The keyword sets the table of functions fk (x) (indices in oil viscosity formula below) for
each PVT region (The number of PVT regions is equal to the second parameter of TABDIMS,
see 12.1.29).

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.14.1).

fk (0) = 0, fk (1) = 1.

12.15.57. OILVINDT 1298

Keywords for formats tN, E1, E3 19.1

If the are more than one PVT region, the tables for all regions should be specified one
after another in this keyword.

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.15.57. OILVINDT 1299

Keywords for formats tN, E1, E3 19.1

12.15.58. GASVISCT

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can only be used if THERMAL (see 12.1.54) is present. Ways to specify gas
viscosity for models in E3 and ST formats, corresponding formulas and keywords are given
in the section 4.13.

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.29).
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);

• N values of gas component viscosities (cP) for this temperature µk,G (T ) (N – the
number of components COMPS, see 12.14.1).

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.15.58. GASVISCT 1300

Keywords for formats tN, E1, E3 19.1

12.15.59. GASVISCF

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can only be used if THERMAL (see 12.1.54) is present. Ways to specify gas
viscosity for models in E3 and ST formats, corresponding formulas and keywords are given
in the section 4.13.
The keyword sets the table of coefficients for correlation formula (gas component viscosity as
a function of temperature).

If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.

The rows of table for one EoS region contains the following parameters:

• coefficient A (N (COMPS, see 12.14.1) values: each value for one component);

• coefficient B (N (COMPS, see 12.14.1) values: each value for one component);

Example
GASVISCF
0.00022 0.00017
0.8 0.7
/

This example sets the coefficients for correlation formula for one EoS region.

12.15.59. GASVISCF 1301

Keywords for formats tN, E1, E3 19.1

12.15.60. REACRATE

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets the rate constants of chemical reactions (remains constant for each re-
action). The same number of values as the number of chemical reactions nr (REACTION,
see 12.1.55) should be specified. The data should be terminated with a slash /.

Default: 0.
The implementation of chemical reactions, corresponding formulas and keywords are de-
scribed in the section 4.29.

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 constants for nine chemical reactions, the fourth reac-
tion has default zero rate constant (that is, does not occur). 9 reactions are specified using the
keyword REACTION (see 12.1.55).

12.15.60. REACRATE 1302

Keywords for formats tN, E1, E3 19.1

12.15.61. REACACT

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets the activation energy in chemical reaction rates (kJ/kg-mol); 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.55) should be specified. The data should be ter-
minated with a slash /.

Default: 0.
The implementation of chemical reactions, corresponding formulas and keywords are de-
scribed in the section 4.29.

Example
REACTION
8 /
...
REACACT
138629 45942.9 87719.8 1* 138629 85645.1 36573.3 21700 /

This example sets the activation energy for eight chemical reactions, the fourth reaction
has default zero activation energy. 8 reactions are specified using the keyword REACTION
(see 12.1.55).

12.15.61. REACACT 1303

Keywords for formats tN, E1, E3 19.1

12.15.62. REACCORD

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets the orders of chemical reactions with respect to components (this pa-
rameter can possess different values for the same component at different reactions).
The same number of rows as the number of chemical reactions nr (REACTION, see 12.1.55)
should be specified. Each row should be terminated with a slash /. Each row contains N + Nw
values, where N is the number of hydrocarbon components (COMPS, see 12.14.1) and Nw is
the number of water components.
If the order is a positive number, the reactant in question enhances the reaction (1 means
linear dependence between the reaction rate and the concentration, 2 means quadratic depen-
dence, etc). If the order is negative, then the reactant in question slows the reaction down
(-1 means inversely proportional dependence, etc). If this order is 0, then the reaction rate is
independent on the concentration of this component. Non-zero orders can be specified even
for the components which are not among the reagents according to the reaction stoichiometry
(STOREAC (see 12.15.67), STOPROD, see 12.15.66). In this case positive order indicates a
catalyst, and negative order indicates an inhibitor.
Default: 0.
The implementation of chemical reactions, corresponding formulas and keywords are de-
scribed in the section 4.29.

Example
REACTION
2 /
COMPS
6 /
...
REACCORD
0 0 1 1 0 0 /
1 0 0 0 -1 0 /

In this example two chemical reactions are specified using the keyword REACTION
(see 12.1.55) and 6 components – using the keyword COMPS (see 12.14.1). 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.15.62. REACCORD 1304

Keywords for formats tN, E1, E3 19.1

12.15.63. REACLIMS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets the maximum and minimum temperature and pressure for each chemical
reaction, which is used in the reaction rate calculations.

The implementation of chemical reactions, corresponding formulas and keywords are de-
scribed in the section 4.29.

The same number of lines as the number of chemical reactions nr (REACTION,

see 12.1.55) should be specified. Each line should be terminated with a slash /.

Default: 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
(according the formula below);

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
(according the formula below);

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).

Example
REACTION
2 /
...
REACLIMS
20 75 120 320 /
30 80 100 220 /

12.15.63. REACLIMS 1305

Keywords for formats tN, E1, E3 19.1

In this example two chemical reactions are specified using the keyword REACTION
(see 12.1.55). The maximum and minimum temperature and pressure are specified.

12.15.63. REACLIMS 1306

Keywords for formats tN, E1, E3 19.1

12.15.64. REACCONC

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets the critical value of reactant concentration (this (METRIC: barsa,
FIELD: psi, if the pressure is used or METRIC: kg-mol/m3 , FIELD: lb-mol/ 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 implementation of chemical reactions, corresponding formulas and keywords are de-
scribed in the section 4.29.

The same number of rows as the number of chemical reactions nr (REACTION,

see 12.1.55) 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.14.1).
Default: 0.
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.55) and 6 components – using the keyword COMPS (see 12.14.1). For first re-
action 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.15.64. REACCONC 1307

Keywords for formats tN, E1, E3 19.1

12.15.65. REACPORD

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets the order of pore volume in chemical reaction rates – nr,p (formula
4.72). The implementation of chemical reactions, corresponding formulas and keywords are
described in the section 4.29.
The same values should be specified as the number of chemical reactions. The data should be
terminated with a slash /.
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.55). 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.15.65. REACPORD 1308

Keywords for formats tN, E1, E3 19.1

12.15.66. STOPROD

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies the stoichiometric coefficients for all products in each chemical
reaction as a line of numbers. The implementation of chemical reactions, corresponding for-
mulas and keywords are described in the section 4.29.

The same number of lines as the number of chemical reactions nr (REACTION,

see 12.1.55) should be entered. Each line should be terminated with a slash /.
Each line should contain N values (number of components entered using COMPS,
see 12.14.1). If water is included, then N + 1 values should be specified in each line. If
the multi-component water model with Nw water components is used, then N + Nw values
should be specified in each line. If the component isn’t a product of the reaction, one should
enter zero or default value.

Stoichiometric coefficients are specified using this keyword and STOREAC (see 12.15.67).
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.55) and 9
components using the keyword COMPS (see 12.14.1).
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
component (with the coefficient 6).
2-nd, 5-th, 6-th, 8-th, 9-th components are not present in this reaction.

12.15.66. STOPROD 1309

Keywords for formats tN, E1, E3 19.1

12.15.67. STOREAC

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies the stoichiometric coefficients for all reactants in each chemical
reaction as a line of numbers. The implementation of chemical reactions, corresponding for-
mulas and keywords are described in the section 4.29.
The same number of lines as the number of chemical reactions nr (REACTION, see 12.1.55)
should be entered. Each line should be terminated with a slash /.
Each line should contain N values (number of components entered using COMPS,
see 12.14.1). If water is included, then N + 1 values should be specified in each line. If
the multi-component water model with Nw water components is used, then N + Nw values
should be specified in each line.
If the component isn’t a reactant in this reaction, one should enter zero or default value.

Stoichiometric coefficients are specified using this keyword and STOPROD (see 12.15.66).
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.55) and 9
components using the keyword COMPS (see 12.14.1).
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
component (with the coefficient 6).
2-nd, 5-th, 6-th, 8-th, 9-th components are not present in this reaction.

12.15.67. STOREAC 1310

Keywords for formats tN, E1, E3 19.1

12.15.68. REACPHA

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies the component phase in chemical reaction. The implementation of
chemical reactions, corresponding formulas and keywords are described in the section 4.29.

Each line of phases corresponds to one chemical reaction. The same number of lines as
the number of chemical reactions nr (REACTION, see 12.1.55) should be entered. Each line
should be terminated with a slash /. Each line should contain N values (number of compo-
nents entered using COMPS, see 12.14.1). If the component isn’t a reactant in this reaction
one can enter default value — ALL (component phase is not used in the calculations if the
component isn’t a 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 partial pressure,

• WAT – water in water phase reacts,

• NONE – the reaction rate doesn’t depend on the component.

• Default: ALL.

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.15.67) and different REACPHA).

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.15.68. REACPHA 1311

Keywords for formats tN, E1, E3 19.1

Example
REACTION
1 /
COMPS
5 /
...
STOPROD
0 0 0 3 4 /

STOREAC
0 1 5 0 0 /

REACPHA
1* OIL GAS 2* /

This example sets 1 chemical reaction using the keyword REACTION (see 12.1.55) and 5
components using the keyword COMPS (see 12.14.1). 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 isn’t 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 doesn’t depend on
them.

12.15.68. REACPHA 1312

Keywords for formats tN, E1, E3 19.1

12.15.69. REACSORD

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies the order of dependence between solid saturation and chemical re-
action rate. The implementation of chemical reactions, corresponding formulas and keywords
are described in the section 4.29.

The same number of values as the number of chemical reactions nr (REACTION,

see 12.1.55) should be entered.
The chemical reaction rate is proportional to the multiplier:

(1 − SˆS )ns

where ns – order, SˆS – solid saturation.

In there is a solid phase in the model then the equation 2.4 is replaced by the equation

SˆO + SˆG + SˆW + SˆS = 1

Oil, gas and water saturation are:

SˆO SˆG SˆW

SO = , SG = , SW =
1 − SˆS 1 − SˆS 1 − SˆS

Example
REACTION
3 /
...
REACSORD
0 1 0 /

12.15.69. REACSORD 1313

Keywords for formats tN, E1, E3 19.1

12.15.70. REACENTH

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies the enthalpy of each chemical reaction (METRIC: kJ/kg-mol ,
FIELD: Btu/lb-mol ). The implementation of chemical reactions, corresponding formulas and
keywords are described in the section 4.29.

It can only be used if THERMAL (see 12.1.54) is present. The same number of values as
the number of chemical reactions nr (REACTION, see 12.1.55) should be entered. The data
should be terminated with a slash /.

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.55).

12.15.70. REACENTH 1314

Keywords for formats tN, E1, E3 19.1

12.15.71. EQLDREAC

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword can only be used if THERMAL (see 12.1.54) is present. It specifies the
corrections to the rate of a chemical reaction as it nears equilibrium.

!
The reaction in question is supposed to model the distribution of a com-
ponent between phases, when the distribution is essentially non-equilibrium
and hence can’t be adequately modeled with partition coefficients (K-values,
see KVCR, see 12.15.11). Usage of the keyword in a broader scope, though
possible, may cause convergence problems.
A reaction rate is multiplied by the term:

 |d|n , d > 0

−|d|n , d < 0


where n is the order of the equilibrium deviation term and d is given by one of the
following models: 
θ · bO · SO · (xi − y j /Kk ), m = 1





d = θ · bG · SG · (Kk · xi − y j ), m = 2 (12.4)



θ · b · S · (1 − 1/K ), m = 3

W W k
where
• θ is porosity;
• bO , bG and bW are oil, gas and water molar densities;
• SO , SG and SW are oil, gas and water saturations;
• xi is oil component mole fraction;
• yi is gas component mole fraction;
• Kk is the partition coefficient at equilibrium.
The implementation of chemical reactions, corresponding formulas and keywords are de-
scribed in the section 4.29.
The keyword is followed by a number of records, each specifying a correction term. There
must be as many records as specified in the second parameter of the REACTION (see 12.1.55)
keyword. Each record is terminated by a slash and contains the following data:

12.15.71. EQLDREAC 1315

Keywords for formats tN, E1, E3 19.1

1. Reaction number.

2. Number of model m used for this correction term (1, 2 or 3), according to the equations
12.4.
Note: model m = 3 is applicable only for single component water model.

3. Component number i.

4. Component number j .

5. Partition coefficient number k which specifies the location of the partition coefficient
Kk in the list defined by EQLDKVCR (see 12.15.72).

6. The direction in which the reaction can proceed:

• FORWARD – reaction rate is forced to remain non-negative;

• BACKWARD – reaction rate is forced to remain non-positive;
• BOTH – reaction can proceed in any direction, rate is not restrained.

Default: BOTH.

7. Order of the correction n > 0.

Default: 1.0.

Restraining the reaction with the 6th parameter to proceed in only one direction is not
recommended, since it introduces a non-smooth behavior and can cause numerical instability.
The reaction stoichiometry (STOREAC (see 12.15.67), STOPROD, see 12.15.66) should
be in accordance with component i producing component j for positive reaction rates.
Component numbers i and j must relate to hydrocarbon components: that is, 0 6 i, j 6
Ncomps . If i or j is set to 0, then the corresponding mole fraction (xi or y j ) is replaced by 1
in equation 12.4.
Example
EQLDREAC
1 1 1 2 1 BOTH /
2 2 5 0 3 BOTH /
In this example the correction terms for reaction rates 1 and 2 are:

d = θ · bo · So · (x1 − y2 /K1 )

and
d = θ · bg · Sg · (K3 · x5 − 1).

12.15.71. EQLDREAC 1316

Keywords for formats tN, E1, E3 19.1

12.15.72. EQLDKVCR

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword specifies equilibrium constants (K-values) for the reactions that have a cor-
rection to their rate specified by the keyword EQLDREAC (see 12.15.71). The implementation
of chemical reactions, corresponding formulas and keywords are described in the section 4.29.
The number of constants Nk is specified by the third parameter of the REACTION
(see 12.1.55) keyword.
Constants are specified as pressure- and temperature-dependent according to the formula
4.22, similar to KVCR (see 12.15.11) (see section 4.9). The temperature and pressure values
are subject to limitations by REACLIMS (see 12.15.63).
The numbers must be specified in five series, each containing Nk numbers described
below. The set of records should be terminated with a slash /.

1. Nk values of Ai (dimensionless).

2. Nk values of Bi (METRIC: barsa, FIELD: psia).

3. Nk values of Ci (METRIC: 1/bars, FIELD: 1/psi).

4. Nk values of Di (METRIC: K, FIELD: ◦ R).

5. Nk values of Ei (METRIC: K, FIELD: ◦ R).

6. Default: 0 for all values (Ai , Bi , Ci , Di , Ei ).

If multiple equations of state are being used, these constants still apply to all EOS regions
and are specified only once.
Example
EQLDKVCR
1.13E6 670.0
0 144.5E3
0 0.01
12000 3500
0 280
/
In this example two K-values are specified. The first one depends on temperature, but not
on pressure, since B1 = C1 = 0. The second depends both on pressure and temperature.

12.15.72. EQLDKVCR 1317

Keywords for formats tN, E1, E3 19.1

12.15.73. SPECHA

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword can only be used if THERMAL (see 12.1.54) is present.

The keyword specifies the first coefficient of the oil component liquid specific heats CP1,c
(METRIC: kJ/kg/K , FIELD: Btu/lb/R), which is used for the calculation of the component
liquid enthalpy. Corresponding formulas for models in E3 and ST formats are given in the
section 4.17.
The same number of values as the number of components N (COMPS, see 12.14.1) should
be entered. The data should be terminated with a slash /.

Default: 0.
If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.

Example
SPECHA
0.66 0.52 /

This example specifies the first coefficient of the formula of component liquid enthalpy
for two components.

12.15.73. SPECHA 1318

Keywords for formats tN, E1, E3 19.1

12.15.74. SPECHB

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword can only be used if THERMAL (see 12.1.54) is present.

The keyword specifies the second coefficient of the oil component liquid specific heats CP2,c
(METRIC: kJ/kg/K/K , FIELD: Btu/lb/R/R), which is used for the calculation of the com-
ponent liquid enthalpy. Corresponding formulas for models in E3 and ST formats are given in
the section 4.17.
The same number of values as the number of components N (COMPS, see 12.14.1) should
be entered. The data should be terminated with a slash /.

Default: 0.
If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.

Example
SPECHB
0.0066 0.0052 /

This example specifies the second coefficient of the formula of component liquid enthalpy
for two components.

12.15.74. SPECHB 1319

Keywords for formats tN, E1, E3 19.1

12.15.75. SPECHC

Data x tN E1 x E3 IM GE x ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword can only be used if THERMAL (see 12.1.54) is present.

The keyword specifies the third coefficient of the oil component liquid specific heats CP3,c
(METRIC: kJ/kg/K/K/K , FIELD: Btu/lb/R/R/R), which is used for the calculation of the
component liquid enthalpy. Corresponding formulas for models in E3 and ST formats are
given in the section 4.17.
The same number of values as the number of components N (COMPS, see 12.14.1) should
be entered. The data should be terminated with a slash /.

Default: 0.
If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.

Example
SPECHC
0.00066 0.00052 /

This example specifies the third coefficient of the formula of component liquid enthalpy
for two components.

12.15.75. SPECHC 1320

Keywords for formats tN, E1, E3 19.1

12.15.76. SPECHD

Data x tN E1 x E3 IM GE x ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword can only be used if THERMAL (see 12.1.54) is present.

The keyword specifies the third coefficient of the oil component liquid specific heats CP4,c
(METRIC: kJ/kg/K/K/K/K , FIELD: Btu/lb/R/R/R/R), which is used for the calculation
of the component liquid enthalpy. Corresponding formulas for models in E3 and ST formats
are given in the section 4.17.
The same number of values as the number of components N (COMPS, see 12.14.1) should
be entered. The data should be terminated with a slash /.

Default: 0.
If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.

Example
SPECHD
0.000066 0.000052 /

This example specifies the fourth coefficient of the formula of component liquid enthalpy
for two components.

12.15.76. SPECHD 1321

Keywords for formats tN, E1, E3 19.1

12.15.77. SPECHG

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword can only be used if THERMAL (see 12.1.54) is present.

The keyword specifies the first coefficient of the gas component specific heats CP1,c (MET-
RIC: kJ/kg/K , FIELD: Btu/lb/R), which is used for the calculation of the enthalpy of
component in gas phase (Eq. 4.44). Corresponding formulas for models in E3 and ST formats
are given in the section 4.19.
The same number of values as the number of components N (COMPS, see 12.14.1) should
be entered. The data should be terminated with a slash /.

Default: 0.
If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.

Example
SPECHG
0.0066 0.0052 /

This example specifies the first coefficient of the formula of component gas phase enthalpy
for two components.

12.15.77. SPECHG 1322

Keywords for formats tN, E1, E3 19.1

12.15.78. SPECHH

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword can only be used if THERMAL (see 12.1.54) is present.

The keyword specifies the second coefficient of the gas component specific heats CP2,c (MET-
RIC: kJ/kg/K/K , FIELD: Btu/lb/R/R), which is used for the calculation of the enthalpy of
component in gas phase (Eq. 4.44). Corresponding formulas for models in E3 and ST formats
are given in the section 4.19.
The same number of values as the number of components N (COMPS, see 12.14.1) should
be entered. The data should be terminated with a slash /.

Default: 0.
If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.

Example
SPECHH
0.00066 0.00052 /

This example specifies the second coefficient of the formula of component gas phase
enthalpy for two components.

12.15.78. SPECHH 1323

Keywords for formats tN, E1, E3 19.1

12.15.79. SPECHI

Data x tN E1 x E3 IM GE x ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword can only be used if THERMAL (see 12.1.54) is present.

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), which is used for the calculation of the en-
thalpy of component in gas phase (Eq. 4.45). Corresponding formulas for models in E3 and
ST formats are given in the section 4.19.
The same number of values as the number of components N (COMPS, see 12.14.1) should
be entered. The data should be terminated with a slash /.

Default: 0.
If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.

Example
SPECHI
0.000066 0.000052 /

This example specifies the third coefficient of the formula of component gas phase en-
thalpy for two components.

12.15.79. SPECHI 1324

Keywords for formats tN, E1, E3 19.1

12.15.80. SPECHJ

Data x tN E1 x E3 IM GE x ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword can only be used if THERMAL (see 12.1.54) is present.

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), which is used for the calculation of the
enthalpy of component in gas phase (Eq. 4.45). Corresponding formulas for models in E3 and
ST formats are given in the section 4.19.
The same number of values as the number of components N (COMPS, see 12.14.1) should
be entered. The data should be terminated with a slash /.

Default: 0.
If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.

Example
SPECHJ
0.0000066 0.0000052 /

This example specifies the fourth coefficient of the formula of component gas phase en-
thalpy for two components.

12.15.80. SPECHJ 1325

Keywords for formats tN, E1, E3 19.1

12.15.81. HEATVAPS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword can only be used if THERMAL (see 12.1.54) is present.

The keyword specifies the coefficient hc,G (METRIC: kJ/kg, FIELD: Btu/lb) (heat of va-
porization at temperature STCOND, see 12.14.11), which is used for the calculation of the
enthalpy of component in gas phase (Eq. 4.44). Corresponding formulas for models in E3 and
ST formats are given in the section 4.19.
The same number of values as the number of components N (COMPS, see 12.14.1) should
be entered. The data should be terminated with a slash /.

Default: 0.
If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.

Example
HEATVAPS
1200 2100 /

This example specifies the coefficient hc,G (heat of vaporization) of the formula of com-
ponent gas phase enthalpy for two components.

12.15.81. HEATVAPS 1326

Keywords for formats tN, E1, E3 19.1

12.15.82. SPECHS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword can only be used if THERMAL (see 12.1.54) is present.

The keyword specifies the first coefficient of the solid phase specific heats CP1,c (METRIC:
kJ/kg/K , FIELD: Btu/lb/R), which is used for the calculation of the enthalpy of component
in solid phase (Eq. 4.48). Corresponding formulas for models in E3 and ST formats are given
in the section 4.20.
The same number of values as the number of components N (COMPS, see 12.14.1) should
be entered. The data should be terminated with a slash /.

Default: 0.
If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.

Then the solid phase enthalpy is calculated according to (4.36).

Example
SPECHS
0.52 0.58 /

This example specifies the first coefficient of the formula of component solid phase en-
thalpy for two components.

12.15.82. SPECHS 1327

Keywords for formats tN, E1, E3 19.1

12.15.83. SPECHT

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword can only be used if THERMAL (see 12.1.54) is present.

The keyword specifies the second coefficient of the solid phase specific heats CP2,c (MET-
RIC: kJ/kg/K/K , FIELD: Btu/lb/R/R), which is used for the calculation of the enthalpy
of component in solid phase (Eq. 4.48). Corresponding formulas for models in E3 and ST
formats are given in the section 4.20.
The same number of values as the number of components N (COMPS, see 12.14.1) should
be entered. The data should be terminated with a slash /.

Default: 0.
If there are more then one EoS region, the data should be entered for all regions (the
number of EoS regions is equal to the 9-th parameter of the keyword TABDIMS, see 12.1.29).
The data for each region should be terminated with a slash /.

Example
SPECHT
0.0052 0.0058 /

This example specifies the second coefficient of the formula of component solid phase
enthalpy for two components.

12.15.83. SPECHT 1328

Keywords for formats tN, E1, E3 19.1

12.15.84. TEMPVD

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies the table of initial temperature distribution versus depth for each
equilibrium region (EQLDIMS, see 12.1.30). The data should be terminated with a slash /.
The calculation of initial conditions from hydrostatic and thermodynamic equilibrium con-
ditions is described in details in the section 4.37.2.
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.15.84. TEMPVD 1329

Keywords for formats tN, E1, E3 19.1

12.15.85. ENPTVT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

In tNavigator this keyword may be used:

• in temperature option (TEMP (see 12.1.64), model type E1);

• in compositional non-thermal models (model type E3);

• in thermal models (THERMAL (see 12.1.54), model type E3).

This keyword specifies the temperature variation of the saturation table end points (for
the saturation table regions) for end–point scaling, two–point method (see section 2.6.7).
The number of tables can not be greater then the 1-st parameter of the keyword TABDIMS
(see 12.1.29). 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.15.85).

Each row should contain the following parameters:

1. temperature (METRIC: ◦ C, FIELD: ◦ F);

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.

12.15.85. ENPTVT 1330

Keywords for formats tN, E1, E3 19.1

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 three different temperatures.

12.15.85. ENPTVT 1331

Keywords for formats tN, E1, E3 19.1

12.15.86. ENKRVT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

In tNavigator this keyword may be used:

• in temperature option (TEMP (see 12.1.64), model type E1);

• in compositional non-thermal models (model type E3);

• in thermal models (THERMAL (see 12.1.54), model type E3).

The keyword sets the tables of relative permeabilities versus temperature for end–point
scaling, two–point method (see section 2.6.7). The table should be specified for every sat-
uration table region (the number of saturation table regions is set via the 1-st parameter of
TABDIMS (see 12.1.29). Each table should be terminated with a slash /.

Each row should contain the following parameters:

1. temperature (METRIC: ◦ C, FIELD: ◦ F);

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 three different temperatures.

12.15.86. ENKRVT 1332

Keywords for formats tN, E1, E3 19.1

12.15.87. ENPCVT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

In tNavigator this keyword may be used:

• in temperature option (TEMP (see 12.1.64), model type E1);

• in compositional non-thermal models (model type E3);

• in thermal models (THERMAL (see 12.1.54), model type E3).

The keyword sets the tables of capillary pressures versus temperature for capillary pres-
sure endpoint scaling – section 2.11.4. 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.29). Each table should be terminated with a slash /.

Each row should contain the following parameters:

1. temperature (METRIC: ◦ C, FIELD: ◦ F);

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.15.87. ENPCVT 1333

Keywords for formats tN, E1, E3 19.1

12.15.88. ROCKV

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword can only be used if THERMAL (see 12.1.54) is present.

The keyword sets rock volume in each grid block (METRIC: m3 , FIELD: BBL ). The
same number of values as the number of grid blocks should be specified. The data should be
terminated with a slash /.

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.15.88. ROCKV 1334

Keywords for formats tN, E1, E3 19.1

12.15.89. THSVC

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword can only be used if THERMAL (see 12.1.54) is present.

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).

The following parameters should be specified:

1. Ag .
Default: 4.9402 × 10−3 .

2. Bg .
Default: 5.0956 × 10−5 .

3. Cg .
Default: 2.9223 × 10−6 .

4. Dg .
Default: 2.5077.

The data should be terminated with a slash /.

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.15.89. THSVC 1335

Keywords for formats tN, E1, E3 19.1

12.15.90. THWVC

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword can only be used if THERMAL (see 12.1.54) is present.

This keyword allows to specify coefficients in water viscosity expression:

Aw
µw = ,
−1 + Bw TF +Cw TF 2

where:

• TF – temperature ( ◦ F).

The following parameters should be specified:

1. Aw .
Default: 2.1850.

2. Bw .
Default: 0.04012.

3. Cw .
Default: 5.1547 × 10−6 .

The data should be terminated with a slash /.

Example
THWVC
2.16E-2
3.15
1.21E-3
/
In the example 3 coefficients for water viscosity expression are specified.

12.15.90. THWVC 1336

Keywords for formats tN, E1, E3 19.1

12.15.91. SPECROCK

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword can be used only if temperature option is enabled, see section 2.26.

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.29) should be entered. Each table should be terminated with a slash /.

One table row contains the following parameters:

1. temperature (METRIC: ◦ C, FIELD: ◦ F);

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.15.91. SPECROCK 1337

Keywords for formats tN, E1, E3 19.1

12.15.92. SPECHEAT

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword can be used only if temperature option is enabled, see section 2.26.

The keyword specifies the volume specific heat of oil, gas, water as a function of tempera-
ture. The same number of tables as the number of PVT regions (2-nd parameter of TABDIMS,
see 12.1.29) should be entered. Each table should be terminated with a slash /.

One table row contains the following parameters:

1. temperature (METRIC: ◦ C, FIELD: ◦ F);

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.15.92. SPECHEAT 1338

Keywords for formats tN, E1, E3 19.1

12.15.93. CALVAL

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

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.15.94).
The following parameters should be specified:

1. component calorific values (METRIC: kJ/kg-mol , FIELD: Btu/lb-mol ). Nc values

should be specified (i.e. the same value as the number of model components).

The data should be terminated with a slash /.

Example
CALVAL
1776.0
202.0
5424.6
547.5
2581.1
/
In the example calorific values of 5 components are set.

12.15.93. CALVAL 1339

Keywords for formats tN, E1, E3 19.1

12.15.94. CALVALR

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword sets component calorific values in each EoS region (see the keyword
EOSNUM, see 12.4.20). If it is needed to set component calorific values for entire reser-
voir, use the keyword CALVAL (see 12.15.93).
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-mol , FIELD: Btu/lb-mol ). 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.15.94. CALVALR 1340

Keywords for formats tN, E1, E3 19.1

12.16. Initialization section

This section describes model initialization. See the section 2.3.

12.16. Initialization section 1341

Keywords for formats tN, E1, E3 19.1

12.16.1. SOLUTION

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword specifies the beginning of data section which contains initial data. The initial
conditions are described in details in the section 2.3.

12.16.1. SOLUTION 1342

Keywords for formats tN, E1, E3 19.1

12.16.2. EQUIL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

This keyword specifies for each equilibrium region properties used in initial conditions
computations (see section 2.3). 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);

Default: 0.

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);

Default: 0.

7. parameter regulating table RSVD (see 12.16.7) (or PBVD, see 12.16.8) usage for initial-
ization 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 can’t exceed saturated
solution gas oil ratio value for current pressure). If parameter is set to negative or zero
value, tables RSVD (see 12.16.7) and PBVD (see 12.16.8) will be ignored, in this case
for live oil it’s 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.16.9) (or PDVD, see 12.16.10) usage for initial-
ization calculation. If set to positive integer, the noted table will be used to calculate gas
dew point pressure (under condition that vaporized oil concentration can’t exceed satu-
rated vaporized oil concentration for current pressure). If parameter is set to negative or
zero value, tables RVVD (see 12.16.9) and PDVD (see 12.16.10) will be ignored, in this
case for wet gas it’s 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.16.2. EQUIL 1343

Keywords for formats tN, E1, E3 19.1

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.
• Default: 1.

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 reference depth (value in
parameter 2) more than ε = 1, then pressure at reference 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.30). Each line must end with slash (/).

Notes:

• For depths specified the following relation must be fulfilled: DGOc ≤ DWOc .

• 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.16.7) or PBVD (see 12.16.8).

12.16.2. EQUIL 1344

Keywords for formats tN, E1, E3 19.1

• 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 pres-
sures in the third region are zero values. Since GOC coincides with Ddat for all three regions,
there’s no need to define RSVD (see 12.16.7) or PBVD (see 12.16.8).

12.16.2. EQUIL 1345

Keywords for formats tN, E1, E3 19.1

12.16.3. RESTART

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

This keyword is used to restart a calculation basing on a previously calculated model from
N-th time step. It is also possible to restart computation process from the specified date, see
RESTARTDATE (see 12.16.4).
Restart data are read from the saved results files of the corresponding base model.
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. Restart can be performed
only from the time step at which grid properties and graphs have been recorded.
Please make sure that results recording on this date was not switched off via keywords
RPTMAPT (see 12.16.65), RPTMAPD (see 12.16.64), RPTGRAPHD (see 12.16.64),
RPTGRAPHT (see 12.16.65), or otherwise.

!
Restart is available for the models calculated in tNavigator only, i.e., the base
model must be calculated in tNavigator. Restart from calculation results from
other simulators is not possible.
Restart model can be made in two styles:
• Case 1. The .data file begins with the RESTART keyword (see Example 1 below). In
this case the restart model has no RUNSPEC and GRID sections, and inherits the corre-
sponding parameters (including RUNCTRL (see 12.19.140) settings, grid geometry, etc.)
from the base model. Some of them can be modified in the SCHEDULE section of the
restart model, if necessary.
Note that in this case the initial data of restart model are stored among the results of
base model, so if the latter are removed, viewing the former becomes impossible.

• Case 2. In the restart model the RESTART keyword is written in the SOLUTION section. In
this case, the RUNCTRL settings of the base case (if any) are ignored in the restart run
and the defaults are used instead. If you need to add some settings to the restart model
then they should be specified in it. The grid should be set in the restart model, grid
properties are inherited from the base model. Additionally it is possible for the restart
model to set new instances of LGR (see 12.1.88) and FRACTURE_WELL (see 12.2.128)
which were not there in the base model.
In this case, once the restart model is calculated, it remains self-contained and indepen-
dent on the base model. All relevant data of the restart model are stored in its own result
files.

12.16.3. RESTART 1346

Keywords for formats tN, E1, E3 19.1

Example 1
Whole .data file of a restart model (tNavigator style)
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):
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 /
W1072 WATER OPEN BHP +1.23806000e+002 1* +4.35565959e+002 /
/

DATES
01 OCT 2004 /
/

DATES
01 NOV 2004 /
/

DATES
01 DEC 2004 /
/

12.16.3. RESTART 1347

Keywords for formats tN, E1, E3 19.1

Example 2
Part of .data file of a restart model (E1/E3 style)
...
PROPS

STONE1

INCLUDE
'pvt.inc'/

INCLUDE
'rp.inc'/

REGIONS

INCLUDE
'regs.inc'/

SOLUTION

INCLUDE
'init.inc'/

RESTART
'modelSmall' 139
/

SUMMARY
ALL

SCHEDULE
INCLUDE
'modelSmall_FORECAST_sch.inc'/

END

In this example sections are going in their usual order ..., PROPS, REGIONS, SOLUTION.
In SOLUTION section restart of the model modelSmall is from time step 139. Next there are
sections SUMMARY, SCHEDULE.

12.16.3. RESTART 1348

Keywords for formats tN, E1, E3 19.1

12.16.4. RESTARTDATE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

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.16.3).

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 /.):

1. model name with saved calculation results data, file extension need not be specified,

2. time step number from which computation should restart; this parameter should be
defaulted (* symbol) to restart calculation from the date specified in parameter 3;

3. date from which computation should restart; if start of model time step does not coin-
cide with this date, then computation starts from the nearest date before specified one.
Restart can be performed only from the time step at which grid properties and
graphs have been recorded. Please make sure that results recording on this date was
not switched off via keywords RPTMAPT (see 12.16.65), RPTMAPD (see 12.16.64),
RPTGRAPHD (see 12.16.64), RPTGRAPHT (see 12.16.65).

Example
RESTARTDATE
'modelSmall' 1* 01 SEP 2004
/

SCHEDULE
INCLUDE
'modelSmall_FORECAST_sch.inc'/

END

12.16.4. RESTARTDATE 1349

Keywords for formats tN, E1, E3 19.1

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):
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 /
W1072 WATER OPEN BHP +1.23806000e+002 1* +4.35565959e+002 /
/

DATES
01 OCT 2004 /
/

DATES
01 NOV 2004 /
/

DATES
01 DEC 2004 /
/

12.16.4. RESTARTDATE 1350

Keywords for formats tN, E1, E3 19.1

12.16.5. RPTRST

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY x SCHEDULE

This keyword allows to save additional data to results file and specify the options of their
saving in E1 format. If the keyword is specified in SOLUTION section, then initial maps and
graphs will be saved, and if one is specified in SCHEDULE section, then calculated maps and

!
graphs will be saved.
Saving of initial maps is only possible if the keyword INIT (see 12.2.118) is
specified in GRID section.
Results of calculations in tNavigator can be saved in different formats described in the
section 9.1.
The keyword is followed by the list of mnemonics. These mnemonics corresponds to
saving parameters. The list should end with a slash (/).
The following mnemonics may be used:

• 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 parameter
is not changed.
• n = 3. Then data will be saved to binaries at every kth report step. The value of
parameter k is specified 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 kth 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 kth
month.
• n = 6. Then data will be saved to binaries at every time step.

• BG – output of gas formation volume factor;

• BGAS – output of gas reservoir molar densities;

• BO – output of oil formation volume factor;

12.16.5. RPTRST 1351

Keywords for formats tN, E1, E3 19.1

• BOIL – output of oil reservoir molar densities;

• BSOL – output of solid reservoir molar densities (for models with SoLID option);

• BW – output of water formation volume factor;

• BWAT – output of water reservoir molar densities;

• DEN – output of phase reservoir densities;

• DENG – output of gas mass densities at reservoir conditions;

• DENO – output of oil mass densities at reservoir conditions;

• DENW – output of water mass densities at reservoir conditions;

• ENERGY – output of internal energy / bulk volume (for models in E3 format with Thermal
option);

• FIP – output of fluids-in-place at separator conditions for models in E1 format, and at

reservoir conditions for E3 format. For E1 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 of all phases in all directions, calculated at reser-
voir conditions (includes flows between global and local grids, and also flows in non-
neighbor connections);

• FOAMMOB – output of gas mobility multiplier for the Foam Model;

• FREQ – frequency of saving data to binaries, if the value of BASIC is greater than 2;

• FVFG – output of gas formation volume factor;

• FVFO – output of oil formation volume factor;

• FVFW – output of water formation volume factor;

• HGAS – output of gas enthalpy values (for models in E3 format with Thermal option);

• HOIL – output of oil enthalpy values (for models in E3 format with Thermal option);

• HROCK – output of rock enthalpy values (for models in E3 format with Thermal option);

• HSOL – output of solid enthalpy values (for models in E3 format with Thermal and SoLID
options);

• HWAT – output of water enthalpy values (for models in E3 format with Thermal option);

• KRG – output of gas relative permeabilities: outputs the array GASKR (E1 models) or KRG
(E3 models);

12.16.5. RPTRST 1352

Keywords for formats tN, E1, E3 19.1

• KRO – output of oil relative permeabilities: outputs the array OILKR (E1 models) or KRO
(E3 models);

• KRW – output of water relative permeabilities: outputs the array WATKR (E1 models) or
KRW (E3 models);

• PBUB – output of bubble pooint pressures;

• PCOG – output of gas-oil capillary pressures;

• PCOW – output of oil-water capillary pressures;

• PDEW – output of dew point pressures;

• POLYVM – output of polymer viscosity multiplier;

• PORV – output of reservoir pore volumes at reference conditions;

• PRES – for models in E1 format, output of water and gas phase pressures; for models in
E3 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 E1 format this is the

product of pore volume at reservoir conditions with saturation. In models of E3 format,
this is a synonym for FIP;

• RK – output of permeability reduction factor for water phase due to polymer adsorption on
the rock (Polymer option);

• RS – output of dissolved GOR (RS) (In compositional runs this is interpreted as the GOR
at surface conditions of the liquid phase in the reservoir);

• RV – output of vaporized OGR (RV) (In compositional runs this is interpreted as the OGR
at surface conditions of what was the vapor phase in the reservoir);

• SCON – output of data for all well completions, including their connection factors and
effective Kh;

• SFIP – output of fluids-in-place at surface/separator conditions;

• SFIPGAS – output of separator volumes for gas FIP data;

• SFIPOIL – output of separator volumes for oil FIP data;

• SFIPWAT – output of separator volumes for water FIP data (single component water only
at present);

• SGAS – output of grid block gas saturations;

12.16.5. RPTRST 1353

Keywords for formats tN, E1, E3 19.1

• SOIL – output of grid block oil saturations;

• SSOLID – output of grid block solid saturations;

• SURFACT – output of surfactant concentrations;

• SURFADS – output of adsorbed surfactant concentrations;

• SURFBLK – same as SURFACT, SURFADS, SURFCNM, SURFMAX, and SURFST put

together;

• SURFCNM – output of logarithm of capillary number;

• SURFMAX – output of maximum surfactant concentrations;

• SURFST – output of water/oil surface tension values considering the surfactant;

• SWAT – output of grid block water saturations;

• TEMP – output of reservoir temperatures (for models in E3 format with Thermal option);

• TRANX – output of transmissibilities in X direction;

• TRANY – output of transmissibilities in Y direction;

• TRANZ – output of transmissibilities in Z direction;

• VELGAS – output of velocities of gas;

• VELOCITY – same as VELGAS, VELOIL, and VELWATER put together, i.e., output of
velocities of oil, gas and water in each of three directions, I, J, K , 9 maps in total. For
calculation of velocities, see 2.12;

• VELOIL – output of velocities of oil;

• VELWAT – output of velocities of water;

• VGAS – output of gas viscosities;

• VISC – output of fluid viscosities. If polymer option (2.16.1)is used, then parameter VISC
enables output of extra viscosity maps:

• EPVIS – effective polymer viscosity;

• EMVIS – effective mixture (water/polymer) viscosity;
• EMV_POL – effective water viscosity;
• SHWVISI, SHWVISJ, SHWVISK – shear viscosity of the water/polymer solution
due to shear thinning/thickening in the positive I, J and K directions, respectively.

• VOIL – output of oil viscosities;

12.16.5. RPTRST 1354

Keywords for formats tN, E1, E3 19.1

• VWAT – output of water viscosities;

• WMF – output of mole fractions of all components in the water phase;

• XMF – output of mole fractions of all components in the liquid phase;

• YMF – output of mole fractions of all components in the gas phase;

• ZMF – output of total component mole fractions.

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 other report step.

12.16.5. RPTRST 1355

Keywords for formats tN, E1, E3 19.1

12.16.6. OUTSOL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY x SCHEDULE

The keyword is identical with the keyword RPTRST (see 12.16.5). Results of calculations
in tNavigator can be saved in different formats described in the section 9.1.

12.16.6. OUTSOL 1356

Keywords for formats tN, E1, E3 19.1

12.16.7. RSVD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

This keyword specifies for each equilibrium region initial solution gas ratio distribution,
used in initial conditions computations (see section 2.3) in case of equilibrium initialization
using EQUIL (see 12.16.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.16.7) or PBVD (see 12.16.8). Otherwise
either RSVD or PBVD (see 12.16.8) should be specified.
The following parameters are to be specified:

1. depth (METRIC: m, FIELD: f t );

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.30). Each table should end with slash (/). Between depth points dissolved
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.16.7. RSVD 1357

Keywords for formats tN, E1, E3 19.1

12.16.8. PBVD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

This keyword specifies for each equilibrium region initial bubble point pressure distribu-
tion, used in initial conditions computations (see section 2.3) in case of equilibrium initializa-
tion using EQUIL (see 12.16.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.16.7) or PBVD (see 12.16.8).
Otherwise either PBVD or RSVD (see 12.16.7) should be specified.

The following parameters are to be specified:

1. depth (METRIC: m, FIELD: f t );
2. bubble point pressure value at this depth (METRIC: barsa, FIELD: psia).
The number of tables specified is equal to number of equilibrium regions defined in
EQLDIMS (see 12.1.30). 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.
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.16.8. PBVD 1358

Keywords for formats tN, E1, E3 19.1

12.16.9. RVVD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

This keyword specifies for each equilibrium region initial vaporized oil concentration
distribution, used in initial conditions computations (see section 2.3) in case of equilibrium
initialization using EQUIL (see 12.16.2). If in a 3-phase wet gas model all equilibrium re-
gions have GOC equal to Ddat , there is no need to define RVVD (see 12.16.9) or PDVD
(see 12.16.10). Otherwise either RVVD or PDVD (see 12.16.10) should be specified.
The following parameters are to be specified:
1. depth (METRIC: m, FIELD: f t );
2. vaporized oil concentration value at this depth (METRIC: sm3 /sm3 , FIELD:
stb/Msc f ).
The number of tables specified is equal to number of equilibrium regions defined in
EQLDIMS (see 12.1.30). Each table should end with slash (/). Between depth points dissolved
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
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) RVVD
table will be used to calculate gas dew point pressure.

12.16.9. RVVD 1359

Keywords for formats tN, E1, E3 19.1

12.16.10. PDVD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

This keyword specifies for each equilibrium region initial dew point pressure distribution,
used in initial conditions computations (see section 2.3) in case of equilibrium initializa-
tion using EQUIL (see 12.16.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.16.9) or PDVD (see 12.16.10).
Otherwise either PDVD or RVVD (see 12.16.9) should be specified.
The following parameters are to be specified:

1. depth (METRIC: m, FIELD: f t );

2. dew point pressure value at this depth (METRIC: barsa, FIELD: psia).

The number of tables specified is equal to number of equilibrium regions defined in

EQLDIMS (see 12.1.30). 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
pressure on GOC and below will be set equal to datum pressure, 205.
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.16.10. PDVD 1360

Keywords for formats tN, E1, E3 19.1

12.16.11. THPRES

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword is used to set threshold pressure value for flow between equilibration regions.
The threshold pressure option THPRES should be set in the keyword EQLOPTS (see 12.1.94)
in the RUNSPEC section. 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.
Default: threshold value is equal to 0.
See also keyword THPRESFT (see 12.2.40). Other keywords used to specify faults and
their parameters are listed in the section 5.5.2.
Keyword is followed by a 3-column table, each line should end with slash /. Last table
line should contain only slash symbol (/).
The following data should be specified:
1. number of first equilibration region (flow from this equilibration region);
2. number of second equilibration region (flow to this equilibration region);
3. threshold pressure value for flow between these regions (METRIC: barsa, FIELD:
psia) in this direction. The option IRREVERS of the keyword EQLOPTS (see 12.1.94)
allows the threshold pressures for flow in each direction between equilibration regions
to be different.
Note: if two regions are indicated several times, last value of threshold pressure will be
used in calculations.
Default:
• if in the table there is no line corresponding to some regions in one of directions, 0
threshold value will be used for flow between those regions in this direction;
• if in the table there is a line for some two regions, but threshold value is not specified
for this direction (the line is terminated via / after two regions), it will be calculated
as maximum pressure difference for communicating cells in those two regions at initial
time moment (only the phases present in upstream cells will be used in calculation).
Calculated values of threshold pressures will be available in the log during model ini-
tialization as THPRES report. For example:
THPRES report
from \ to (Bars) 1 2
1 0.0000 31.4765
2 31.4765 0.0000

12.16.11. THPRES 1361

Keywords for formats tN, E1, E3 19.1

Example
EQLOPTS
THPRES IRREVERS /

...

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 /
/

The option IRREVERS of the keyword EQLOPTS (see 12.1.94) allows the threshold
pressures for flow in each direction between equilibration regions to be different.
In this example different threshold pressure values are defined for flows from first region to
second region and vice versa. For first and third regions, those values coincide. For flow from
second region to third region, threshold value 7 will be used; for flow in opposite direction
zero threshold pressure will be used (since there is no line for this direction in the table).
Threshold pressures for flows between first and fourth regions will be calculated from initial
pressure distribution.

12.16.11. THPRES 1362

Keywords for formats tN, E1, E3 19.1

12.16.12. PRESSURE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

This keyword specifies initial pressures (METRIC: barsa, FIELD: psia). The same num-
ber of values as number of grid blocks must be specified. This is initial value of pO in 2.3.

!
Default: none.
The maximal value of initial pressure has to be less than 106 for any units
system.

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.16.12. PRESSURE 1363

Keywords for formats tN, E1, E3 19.1

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.16.12. PRESSURE 1364

Keywords for formats tN, E1, E3 19.1

12.16.13. PRVD

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

This keyword specifies initial pressure for each depth level. It can be used to specify initial
pressure distribution instead of PRESSURE (see 12.16.12) keyword.
Table should consist of at least two lines. The following parameters are to be specified on
each line:

1. depth (METRIC: m, FIELD: f t );

2. pressure value at this depth (METRIC: barsa, FIELD: psia).

The number of tables specified is equal to number of equilibrium regions defined in

EQLDIMS (see 12.1.30). 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.16.13. PRVD 1365

Keywords for formats tN, E1, E3 19.1

12.16.14. SWAT

Data x tN x E1 x E3 IM GE ST x MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY x SCHEDULE

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.
SWAT (see 12.16.14) can be specified in SCHEDULE only in black-oil mod-
els.
If the sum of saturations specified in SCHEDULE (SWAT (see 12.16.14) +
SOIL (see 12.16.16) + SGAS, see 12.16.15) is not equal to 1 then the fol-
lowing correction of saturations is carried out so that their sum is equal to
1:

• If the sum of specified saturations exceeds 1 then their values are nor-

!
malized (so that their sum is equal to 1), while the remaining saturations
are assumed to be equal to zero;

• If all saturations are specified in SCHEDULE and their sum is less than
1 then all saturations are normalized;

• If the sum of all saturations (specified by user and remaining ones)

is less than 1 then the specified saturations do not change and the
remaining saturations are normalized.

If all saturations are equal to zero then the water saturation SWAT
(see 12.16.14) is assumed to be equal to 1.

Example
DIMENS
5 5 1
/
...
SWAT
25*0.25
/

12.16.14. SWAT 1366

Keywords for formats tN, E1, E3 19.1

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.
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.16.14. SWAT 1367

Keywords for formats tN, E1, E3 19.1

12.16.15. SGAS

Data x tN x E1 x E3 IM GE ST x MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY x SCHEDULE

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.16.15) 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.
SGAS (see 12.16.15) can be specified in SCHEDULE only in black-oil mod-
els.
If the sum of saturations specified in SCHEDULE (SWAT (see 12.16.14) +
SOIL (see 12.16.16) + SGAS, see 12.16.15) is not equal to 1 then the fol-
lowing correction of saturations is carried out so that their sum is equal to
1:

• If the sum of specified saturations exceeds 1 then their values are nor-

!
malized (so that their sum is equal to 1), while the remaining saturations
are assumed to be equal to zero;

• If all saturations are specified in SCHEDULE and their sum is less than
1 then all saturations are normalized;

• If the sum of all saturations (specified by user and remaining ones)

is less than 1 then the specified saturations do not change and the
remaining saturations are normalized.

If all saturations are equal to zero then the water saturation SWAT
(see 12.16.14) is assumed to be equal to 1.

Example
DIMENS
5 5 1
/
...
SGAS
25*0.75
/

12.16.15. SGAS 1368

Keywords for formats tN, E1, E3 19.1

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.
Example
DIMENS
5 3 2
/
...
SGAS
15*0.75 15*0.50
/
This example is equivalent to the previous one, but it uses short form with asterisks.

12.16.15. SGAS 1369

Keywords for formats tN, E1, E3 19.1

12.16.16. SOIL

Data x tN x E1 x E3 IM GE ST x MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY x SCHEDULE

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.16.16) 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.
SOIL (see 12.16.16) can be specified in SCHEDULE only in black-oil models.
If the sum of saturations specified in SCHEDULE (SWAT (see 12.16.14) +
SOIL (see 12.16.16) + SGAS, see 12.16.15) is not equal to 1 then the fol-
lowing correction of saturations is carried out so that their sum is equal to
1:

• If the sum of specified saturations exceeds 1 then their values are nor-

!
malized (so that their sum is equal to 1), while the remaining saturations
are assumed to be equal to zero;

• If all saturations are specified in SCHEDULE and their sum is less than
1 then all saturations are normalized;

• If the sum of all saturations (specified by user and remaining ones)

is less than 1 then the specified saturations do not change and the
remaining saturations are normalized.

If all saturations are equal to zero then the water saturation SWAT
(see 12.16.14) is assumed to be equal to 1.

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).

12.16.16. SOIL 1370

Keywords for formats tN, E1, E3 19.1

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.
Example
DIMENS
5 3 2
/
...
SOIL
15*0.21 15*0.50
/
This example is equivalent to the previous one, but it uses short form with asterisks.

12.16.16. SOIL 1371

Keywords for formats tN, E1, E3 19.1

12.16.17. SSOLID

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword specifies the initial solid saturation. An explicit specification of initial con-
ditions is described in the section 4.37.1.
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.16.17. SSOLID 1372

Keywords for formats tN, E1, E3 19.1

12.16.18. APIVD

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword specifies tables of oil API density versus depth for API tracking option –
2.8.8.
The number of tables should be equal to the number of equilibration regions. Each table
should be terminated with a slash /.

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 /

In this example one table is specified.

12.16.18. APIVD 1373

Keywords for formats tN, E1, E3 19.1

12.16.19. OILAPI

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword is used to specify initial oil API values for API tracking option – 2.8.8.

The same number of values as the number of grid blocks must be specified. The data
should be terminated with a slash /.

! The maximum of initial oil API value has to be less than 106 for any units
system.

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.16.19. OILAPI 1374

Keywords for formats tN, E1, E3 19.1

12.16.20. SMF

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

This keyword specifies cell initial solid composition. An explicit specification of initial
conditions is described in the section 4.37.1. The same number of values as the product of
grid blocks NX * NY * NZ (DIMENS, see 12.1.28) and the number of components (COMPS,
see 12.14.1) 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.16.20. SMF 1375

Keywords for formats tN, E1, E3 19.1

12.16.21. XMF

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword sets the initial oil composition for each grid block. An explicit specification
of initial conditions is described in the section 4.37.1. One should specify the same number
of values as the product of numbers of grid blocks NX * NY * NZ (DIMENS, see 12.1.28)
and the number of components (COMPS, see 12.14.1). For thermal models with water it is
required to specify NX * NY * NZ values corresponding to initial water composition in a
block. The data should be terminated with a slash /.
If the sum of values for any grid block isn’t 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.16.21. XMF 1376

Keywords for formats tN, E1, E3 19.1

12.16.22. YMF

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword sets the initial gas composition for each grid block. An explicit specification
of initial conditions is described in the section 4.37.1. One should specify the same number
of values as the product of numbers of grid blocks NX * NY * NZ (DIMENS, see 12.1.28)
and the number of components (COMPS, see 12.14.1). For thermal models with water it is
required to specify NX * NY * NZ values corresponding to initial water composition in a
block. The data should be terminated with a slash /.
If the sum of values for any grid block isn’t 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 /
...
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.16.22. YMF 1377

Keywords for formats tN, E1, E3 19.1

12.16.23. ZMF

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword sets the initial total composition for each grid block (values z0c = Nc /Ntot
0 ,
n0c
c = 2, . . . , n0c , Ntot
0 =
∑ Nc ). An explicit specification of initial conditions is described in the
c=2
section 4.37.1. One should specify the same number of values as the product of numbers of
grid blocks NX * NY * NZ (DIMENS, see 12.1.28) and the number of components (COMPS,
see 12.14.1). For thermal models with water it is required to specify NX * NY * NZ values
corresponding to initial water composition in a block. The data should be terminated with a
slash /.
If the sum of values for any grid block isn’t 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.

Note:

1. If in the PROPS section there is COMPVD (see 12.14.14) or ZMFVD (see 12.14.17) or
ZI (see 12.14.13), then it is used.

2. If in the PROPS section component composition versus depth is not specified (no
COMPVD (see 12.14.14), ZMFVD (see 12.14.17), ZI, see 12.14.13), but component
composition is specified in SOLUTION in each grid block (ZMF (see 12.16.23) or XMF
(see 12.16.21)/YMF (see 12.16.22) is present), then:

• a message will be written: that the constant distribution of the component com-
position for EQUIL regions will be built, based on the composition in the blocks
of each EQUIL region (using ZMF (see 12.16.23) or XMF (see 12.16.21)/YMF
(see 12.16.22) correspondingly);
• the table ZMFVD (see 12.14.17) is constructed and used in EQUIL (see 12.16.2);
• the table ZMFVD (see 12.14.17) is saved in the .log file.

12.16.23. ZMF 1378

Keywords for formats tN, E1, E3 19.1

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.16.23. ZMF 1379

Keywords for formats tN, E1, E3 19.1

12.16.24. FIELDSEP

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

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.19.156), WSEPCOND (see 12.19.157). All keywords used to set a separator
for models in E1 or E3 formats, are given in the section 2.14.4.

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.16.25).
Sum of oil and gas in-place for FIP region (FIPSEP) can be not equal to oil and gas in-place
for field calculated via FIELDSEP (see 12.16.24).

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 data line should be terminated with the symbol /. All data should
be terminated with a final slash /.
One data row contains the following parameters:

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;
Default: 15.56 ◦ C.

3. separator stage pressure (METRIC: barsa, FIELD: psia);

Default: 1.013 barsa.

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;
Default: 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).

12.16.24. FIELDSEP 1380

Keywords for formats tN, E1, E3 19.1

5. gas destination output from the separator;

Default: 0. Gas is accumulated in the stock-tank or field separator vapor. The volume is
converted to the standard conditions.

6. k-value table number (IGNORED), this is an E1/E3 compatibility field;

7. gas plant table number. Tables are specified via keywords GPTABLE (see 12.16.26),
GPTABLE3 (see 12.16.28), GPTABLEN (see 12.16.27). If 0 value is specified then gas
plant table is not used and calculation of equation of state will be done;
Default: 0.

8. surface equation of state number.

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.
Liquid 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.16.24. FIELDSEP 1381

Keywords for formats tN, E1, E3 19.1

12.16.25. FIPSEP

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

This keyword specifies separator for FIP regions. This separator is used to calculated oil
and gas in-place volumes for FIP region (see section 5.10.5).
Oil and gas volume in-place are calculated via field separator FIELDSEP (see 12.16.24), that’s
why sum of oil and gas in-place for FIP region (FIPSEP) can be not equal to oil and gas
in-place for field calculated via FIELDSEP (see 12.16.24).

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 data line should be terminated with the symbol /. All data should
be terminated with a final slash /.
One data row contains the following parameters:

1. number of the FIP region in which this separator is used for oil and gas-in-place calcu-
lations;

2. stage number;

3. separator stage temperature (METRIC: ◦ C, FIELD: ◦ F);

Default: 15.56 ◦ C.

4. separator stage pressure (METRIC: barsa, FIELD: psia);

Default: 1.013 barsa.

5. 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;
Default: 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).

6. gas destination output from the separator;

Default: 0. Gas is accumulated in the stock-tank or field separator vapor. The volume is
converted to the standard conditions.

7. k-value table number (IGNORED), this is an E1/E3 compatibility field;

12.16.25. FIPSEP 1382

Keywords for formats tN, E1, E3 19.1

8. gas plant table number. Tables are specified via keywords GPTABLE (see 12.16.26),
GPTABLE3 (see 12.16.28), GPTABLEN (see 12.16.27). If 0 value is specified then gas
plant table is not used and calculation of equation of state will be done.
Default: 0.

9. surface equation of state number.

Example
FIPSEP
2 1 15 1.03 3* 1 /
/

In this example for FIP region number 2 a one-stage separator is specified.

12.16.25. FIPSEP 1383

Keywords for formats tN, E1, E3 19.1

12.16.26. GPTABLE

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY x SCHEDULE

This keyword is used to specify gas plant recovery factors (see section 2.14.5). (Also
gas plant table can be specified via the keywords GPTABLE3 (see 12.16.28), GPTABLEN,
see 12.16.27).

The number of gas plant table should be specified in the keywords FIELDSEP
(see 12.16.24), FIPSEP (see 12.16.25), SEPCOND (see 12.19.156) to use these tables in con-
verting flow rates into surface conditions (see section 5.10.5).

Each table should be terminated with a slash /.

The first table row contains the following parameters:

1. gas plant table number;
2. first component number to define the heavy fractions;
Default: number of the last model component.
3. last component number to define the heavy fractions.
Default: number of the last model component.
After the first row goes the table itself. It consists of the recovery fractions for all compo-
nents 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 number of component in the run COMPS, see 12.14.1): liquid
recovery fractions for each hydrocarbon component. Liquid recovery fraction for one
component – the number of moles of liquid per one mole of feed.

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
/

12.16.26. GPTABLE 1384

Keywords for formats tN, E1, E3 19.1

In this example first table column contains heavy component mole fractions for 8-th com-
ponent. Other columns – liquid recovery factors for components from 1-st to 8-th.

12.16.26. GPTABLE 1385

Keywords for formats tN, E1, E3 19.1

12.16.27. GPTABLEN

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY x SCHEDULE

This keyword is used to specify gas plant recovery table containing oil recovery fraction
and NGL (natural gas liquid) recovery fraction (see section 2.14.5). (Also gas plant table can
be specified via the keywords GPTABLE (see 12.16.26), GPTABLE3, see 12.16.28).

The number of gas plant table should be specified in the keywords FIELDSEP
(see 12.16.24), FIPSEP (see 12.16.25), SEPCOND (see 12.19.156) to use these tables in con-
verting flow rates into surface conditions (see section 5.10.5).

Each table should be terminated with a slash /.

The first table row contains the following parameters:

1. gas plant table number;

2. first component number to define the heavy fractions;

Default: number of the last model component.

3. last component number to define the heavy fractions.

Default: number of the last model component.

After the first row goes the table itself. It consists of the recovery fractions for all compo-
nents 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 number of component in the run COMPS, see 12.14.1):
oil recovery fractions for each hydrocarbon component. Oil recovery fraction for one
component – the number of moles of oil per one mole of feed;

3. Nc values (is equal to the number of component in the run COMPS, see 12.14.1): NGL
recovery fractions for each hydrocarbon component.

12.16.27. GPTABLEN 1386

Keywords for formats tN, E1, E3 19.1

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 doesn’t 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.16.27. GPTABLEN 1387

Keywords for formats tN, E1, E3 19.1

12.16.28. GPTABLE3

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY x SCHEDULE

This keyword is used to specify gas plant recovery table containing oil, NGL (natural gas
liquid) and gas recovery fraction (see section 2.14.5). (Also gas plant table can be specified
via the keywords GPTABLE (see 12.16.26), GPTABLEN, see 12.16.27).

The number of gas plant table should be specified in the keywords FIELDSEP
(see 12.16.24), FIPSEP (see 12.16.25), SEPCOND (see 12.19.156) to use these tables in con-
verting flow rates into surface conditions (see section 5.10.5).

Each table should be terminated with a slash /.

The first table row contains the following parameters:

1. gas plant table number;

2. first component number to define the heavy fractions;

Default: number of the last model component.

3. last component number to define the heavy fractions.

Default: number of the last model component.

After the first row goes the table itself. It consists of the recovery fractions for all compo-
nents 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 number of component in the run COMPS, see 12.14.1):
oil recovery fractions for each hydrocarbon component. Oil recovery fraction for one
component – the number of moles of oil per one mole of feed;

3. Nc values (is equal to the number of component in the run COMPS, see 12.14.1): NGL
recovery fractions for each hydrocarbon component;

4. Nc values (is equal to the number of component in the run COMPS, see 12.14.1): gas
recovery fractions for each hydrocarbon component.

12.16.28. GPTABLE3 1388

Keywords for formats tN, E1, E3 19.1

The sum for each component of oil, gas and NGL recovery fractions does not have to be
equal to 1.
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 do not change with the heavy mole fraction, so only one
value is specified – 0.2 and recovery fractions for it.
If recovery fractions are not constant, one should specify the next value of heavy mole fraction
and corresponding recovery fractions data arrays for it.

12.16.28. GPTABLE3 1389

Keywords for formats tN, E1, E3 19.1

12.16.29. RECOVERY

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY x SCHEDULE

This keywords specified recovery plant table.

The data should be terminated with a slash /.

The first table row contains the following parameters:

1. first component number to define the heavy fractions;

Default: number of the last model component.

2. last component number to define the heavy fractions.

Default: number of the last model component.

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.14.1).

One row of the table contains the following data:

• 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.

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.16.29. RECOVERY 1390

Keywords for formats tN, E1, E3 19.1

12.16.30. DENSTRMIX

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY x SCHEDULE

This keyword specifies the tables of components’ densities that could be used for surface
stream mass density computation.

Usage of this keyword does not affect EOS calculations or reservoir fluid flow equations.

The data should be entered in the following format:

DENSTRMIX
set_no ρ1 ρ2 ... ρnc /

Data entry should be terminated with a slash /

The following parameters are specified:

1. set_no – the number of the components mass density set. This number can be used by
SEPDEN (see 12.16.31) keyword in order to assign the set to the separator stream.

2. ρ1 ρ2 ... ρnc – components mass densities (METRIC: kg/m3 FIELD: lb/ f t 3 ).

The list must contain one value for each component of the model.

Example
DENSTRMIX
1 799 799 799 799 799 100 100 100 /
In this example the mass densities are defined for 8 components.

12.16.30. DENSTRMIX 1391

Keywords for formats tN, E1, E3 19.1

12.16.31. SEPDEN

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY x SCHEDULE

This keyword defines the separator’s conditions.

The data should be entered in the following format:

SEPDEN
sep_name stream method EOS_num den_set Pstream Tstream Z f actor /
/
Any number of lines can be indicated below SEPDEN keyword. Each data line should be
terminated with the symbol /. All data should be terminated with a final slash /.
One data row contains the following parameters:

1. sep_name – separator’s name. This name can further be used in WSEPCOND

(see 12.19.157) keyword.
If the keyword SEPDEN is used to define the parameters of Filed or Fluid In Place
separator:

• FIELDSEP should be indicated as the separator’s name if this keyword is defined

for FIELDSEP (see 12.16.24).
• FIPSEP should be indicated as the separator’s name if this keyword is defined for
FIPSEP (see 12.16.25).

2. stream – fluid type. Three options are avaliable:

• GAS – gas stream.

• OIL – oil stream.
• INL – intermediate fluid stream.

3. method – The method of strream density calculation. Three options are avaliable:

• EOS – the stream density will be determined by a single-phase EOS density cal-
culation at the stream pressure and temperature.
• GASLAW – the stream molar density will be determined from the stream pressure
and temperature with respect to the campressibility factor Z :
mstream ∗ Pstream
ρstream = (12.5)
Z ∗ R ∗ Tstream

12.16.31. SEPDEN 1392

Keywords for formats tN, E1, E3 19.1

• MIX – the stream density will be calclated with a use of mixing rule for molar
volumes. In this case the molar densities of each component must be specified by
DENSTRMIX (see 12.16.30) keyword.

Default: EOS.

4. EOS_num – the number of Equation Of State region (EOSNUM, see 12.4.20) that will
be used for stream density calculation if EOS is set as the calculation method.
This parameter will be ignored if MIX or GASLAW is set as the calculation method.
Default: 1.

5. den_set – the number of components density set (DENSTRMIX, see 12.16.30) that will
be used for stream density calculation if MIX is set as the calculation method.
This parameter will be ignored if EOS or GASLAW is set as the calculation method.
Default: 1.

6. Pstream – the pressure value that will be used for stream density calculation (METRIC:
barsa; FIELD: psia).
This parameter will be ignored if MIX is set as the calculation method.
Default: Standard pressure defined by STCOND (see 12.14.11).

7. Tstream – the temperature value that will be used for stream density calculation (MET-
RIC: ◦ C, FIELD: ◦ F).
This parameter will be ignored if MIX is set as the calculation method.
Default: Standard temperature defined by STCOND (see 12.14.11).

8. Z f actor – the value of gas compressibility that will be used for stream density calcula-
tions if GASLAW is set as the calculation method.
This parameter will be ignored if EOS or MIX is set as the calculation method.
Default: 1.

Example
SEPDEN
’FIELDSEP’ GAS EOS 1 1* 60 14.69 /
’FIELDSEP’ OIL GASLAW 1 1* 60 14.69 /
’FIELDSEP’ INL MIX 1* 1 /
/
In this example:
• The separator properties are set for the field separator FIELDSEP (see 12.16.24).

• The separator’s properties are defined for all three fluid types (GAS, OIL and INL).

• Different density calculation methods are selected for each fluid.

12.16.31. SEPDEN 1393

Keywords for formats tN, E1, E3 19.1

12.16.32. TEMPI

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword sets the initial temperature (METRIC: ◦ C, FIELD: ◦ F) in each grid block.
An explicit specification of initial conditions is described in the section 4.37.1. The same
number of values as the number of grid blocks must be specified. The data should be termi-
nated with a slash /.

Default: none.

Example
DIMENS
10 10 5 /
...
TEMPI
250*100 250*120
/
This example sets the initial temperature in the reservoir: 100 ◦C in the first 250 grid
blocks and 120 ◦ C in the next 250 grid blocks.

12.16.32. TEMPI 1394

Keywords for formats tN, E1, E3 19.1

12.16.33. RTEMPA

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword specifies initial reservoir temperature (METRIC: ◦ C, FIELD: ◦ F) when tem-
perature option is used (2.26). One temperature value should be specified. The data should be
terminated with a slash /.

Default: temperature: 60 ◦ F for E1 models, 100 ◦ C for E3 models.

Example
RTEMPA
90 /
In this example initial reservoir temperature is 90 ◦ C.

12.16.33. RTEMPA 1395

Keywords for formats tN, E1, E3 19.1

12.16.34. RTEMPVD

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword specifies the dependence between initial reservoir temperature and depth
(METRIC: ◦ C, FIELD: ◦ F) when temperature option is used (2.26). The same number of ta-
bles as the number of equilibration regions should be entered (first parameter of the keyword
EQLDIMS, see 12.1.30). Each table should be terminated with a slash /.

One table row contains the following parameters:

• 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
/
In this example one table is specified.

12.16.34. RTEMPVD 1396

Keywords for formats tN, E1, E3 19.1

12.16.35. WTEMPDEF

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword specifies the default water temperature for injectors (METRIC: ◦ C, FIELD:
◦ F) in case if the keyword WTEMP (see 12.19.176) is not specified. Temperature option

allowing to model the temperature effects of cold water injection is described in the section
2.26.
In E1/E3 default temperature of injected water is 0 ◦ C. In case when WTEMPDEF is used
in E1/E3 format models, it overrides this value.

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 ter-
minated with a slash /.

Example
WTEMPDEF
15 6 12 /
/

In this example default temperature of injected water is specified for 3 PVT regions.

12.16.35. WTEMPDEF 1397

Keywords for formats tN, E1, E3 19.1

12.16.36. PBUB

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

This keyword specifies initial bubble point pressure (METRIC: barsa, FIELD: psia) for
undersaturated reservoir. The initial conditions are described in details in the section 2.3. The
same number of values as number of grid blocks must be specified. The data should be termi-
nated by a slash /.

This keyword is an alternative to the keyword RS (see 12.16.37) (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;

! The maximal value of initial bubble point pressure for undersaturated

reservoir has to be less than 106 for any units system.

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.16.36. PBUB 1398

Keywords for formats tN, E1, E3 19.1

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
/
This example is equivalent to the previous one, but uses the short form with asterisks.

12.16.36. PBUB 1399

Keywords for formats tN, E1, E3 19.1

12.16.37. RS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

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 (see section 2.3).

This keyword is an alternative to the keyword PBUB (see 12.16.36) (only one of them
should be specified).

! The maximal value of initial gas solution in oil for live oil model has to be
less than 106 for any units system.

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
dimensions are 5x5x1).
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.16.37. RS 1400
Keywords for formats tN, E1, E3 19.1

Example
DIMENS
3 3 2
/
...
RS
9*.235 9*.250
/
This example is equivalent to the previous one, but uses the short form with asterisks.

12.16.37. RS 1401
Keywords for formats tN, E1, E3 19.1

12.16.38. RV

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

This keyword specifies initial oil vaporization in gas for wet gas model (METRIC:
sm3 /sm3 , FIELD: stb/Msc f ). The same number of values as number of grid blocks must
be specified. This is initial value of RO,G in 2.3.
The data should be terminated by a slash /.

This keyword is an alternative to the keyword PDEW (see 12.16.39) (only one of them
should be specified).

Default: none.

! The maximal value of initial oil vaporization in gas for wet gas model has to
be less than 106 for any units system.

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
/

12.16.38. RV 1402
Keywords for formats tN, E1, E3 19.1

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.
Example
DIMENS
5 3 2
/
...
RV
15*.0235 15*.0250
/
This example is equivalent to the previous one, but uses the short form with asterisks.

12.16.38. RV 1403
Keywords for formats tN, E1, E3 19.1

12.16.39. PDEW

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

This keyword specifies initial dew point pressure (METRIC: barsa, FIELD: psia) for
black oil model. The initial conditions are described in details in the section 2.3. 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 RV (see 12.16.38) (only one of them should
be specified).

Default: none.

! The maximal value of initial dew point pressure has to be less than 106 for
any units system.

Example
DIMENS
6 5 2
/
...
PDEW
60*193
/
This example sets equal initial dew point pressure = 193 in all 60 grid blocks (grid dimen-
sions are 6x5x2).
Example
DIMENS
7 5 2
/
...
PDEW
35*162 35*170
/
This example specifies initial dew point pressure to 162 in the first layer of a 5x3x2
two-layer grid, and equal to 170 in the second layer.

12.16.39. PDEW 1404

Keywords for formats tN, E1, E3 19.1

12.16.40. DATUM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword sets the datum depth (METRIC: m, FIELD: f t ) for calculations of depth
corrected pressures (see section 5.11). If this keyword is not specified the depth entered by
1-st parameter of EQUIL (see 12.16.2) for 1-st equilibrium region will be used.
The data should be terminated with a slash /.
Example
DATUM
3000 /

12.16.40. DATUM 1405

Keywords for formats tN, E1, E3 19.1

12.16.41. DATUMR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword sets the datum depth (METRIC: m, FIELD: f t ) for calculations of depth
corrected pressures for each FIP region (see section 5.11).
One should specify the same number of values as the number of FIP regions (5-th parameter
of TABDIMS (see 12.1.29) or 1-st parameter of REGDIMS (see 12.1.32), if this parameter is
specified in both keywords, then maximum is taken).
The data should be terminated with a slash /.
Example
TABDIMS
3 2 2* 4/

DATUMR
3000 4200 5100 2800 /

This example sets datum depths for 4 FIP regions.

12.16.41. DATUMR 1406

Keywords for formats tN, E1, E3 19.1

12.16.42. DATUMRX

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword sets datum depths (METRIC: m, FIELD: f t ) 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) for calculations of depth corrected pressures (see section 5.11). The
number of values for each family can’t exceed the number of regions in this family. If depths
are not specified for all regions, and if the keyword DATUMR (see 12.16.41) 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;
Default: standard fluid-in-place regions FIPNUM (see 12.4.10).

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
/.

Example
DATUMRX
NUM 100 600 1100 /
/
In the example for three regions of FIP-family NUM datum depths are specified.

12.16.42. DATUMRX 1407

Keywords for formats tN, E1, E3 19.1

12.16.43. TBLK

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword specifies the initial concentration of a tracer in each grid block. Other key-
words used for tracer modeling are given in the section 2.17.1. The keyword should be fol-
lowed 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: E1 and E3.

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 E1 format:

• characters 1-4 should be – TBLK;

• 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).
Letters S and F are ignored (they are used to compatibility with E1/E3 input syntax),
tNavigator reads then other characters (starting from 6-th) that set tracer name;

• other characters – name of the tracer whose concentration is initialized (name is specified
via the keyword TRACER (see 12.7.10); in E1/E3 tracer name may consist of up to 3
characters, but in tN tracer name may consist of any number of characters).

The keyword in E3 format:

• characters 1-4 should be – TBLK;

• other characters (starting from the character number 5) – name of the tracer whose
concentration is initialized (name is specified via the keyword TRACER (see 12.7.10);
in E1/E3 tracer name may consist of up to 3 characters, but in tN tracer name may
consist of any number of characters).

! The maximal value of initial concentration of a tracer has to be less than 106
for any units system.

12.16.43. TBLK 1408

Keywords for formats tN, E1, E3 19.1

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.16.43. TBLK 1409

Keywords for formats tN, E1, E3 19.1

12.16.44. TNUM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
x REGIONS SOLUTION SUMMARY SCHEDULE

The keyword specifies tracer concentration region numbers for each grid block. For each
tracer concentration region the keyword TVDP (see 12.16.45) specifies the table of initial
tracer concentration with respect to depth. Other keywords used for tracer modeling are given
in the section 2.17.1.

The keyword may be entered in two formats: E1 and E3.

The keyword in E1 format:

1. characters 1-4 should be – TNUM;

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 E3 format;

3. other characters – name of the tracer whose tracer concentration regions are initialized
(name is specified via the keyword TRACER (see 12.7.10); in E1/E3 tracer name may
consist of up to 3 characters, but in tN tracer name may consist of any number of
characters).

The keyword in E3 format:

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.10); in E1/E3 tracer name may
consist of up to 3 characters, but in tN tracer name may consist of any number of
characters).

The keyword should be followed by one integer for every grid block, specifying the ini-
tial 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.30). 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.16.44. TNUM 1410

Keywords for formats tN, E1, E3 19.1

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.16.44): 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.16.45).

12.16.44. TNUM 1411

Keywords for formats tN, E1, E3 19.1

12.16.45. TVDP

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

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.16.44). Other keywords used for tracer modeling are given in the section 2.17.1.

The keyword may be entered in two formats: E1 and E3.

The keyword in E1 format:

1. characters 1-4 should be – TVDP;

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 E3 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.10);
in E1/E3 tracer name may consist of up to 3 characters, but in tN tracer name may consist
of any number of characters).

The keyword in E3 format:

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.10);
in E1/E3 tracer name may consist of up to 3 characters, but in tN 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.16.44) should be specified one
table. Each data line should be terminated with the symbol /. All data should be terminated
with a final slash /.
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.30):

1. depth (METRIC: m, FIELD: f t );

2. the corresponding initial tracer concentration at this depth (the concentration should be
non-negative).

12.16.45. TVDP 1412

Keywords for formats tN, E1, E3 19.1

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.16.44): 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.16.45).

12.16.45. TVDP 1413

Keywords for formats tN, E1, E3 19.1

12.16.46. ROCKSALT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword is used to specify initial mass of reservoir salt (METRIC: kg, FIELD: lb)
using for simulation of salt washing–out with fresh water (see section 2.24.1). The same
number of values as the number of grid blocks should be specified. The data should be
terminated with a slash /.
This keyword can be used only if the Brine option is active (the keyword BRINE,
see 12.1.62). The dissolution rate constant ϑsalt (the keyword SALTPROP, see 12.7.1) 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.16.46. ROCKSALT 1414

Keywords for formats tN, E1, E3 19.1

12.16.47. SALT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

This keyword specifies the initial salt concentration (METRIC: kg/m3 , FIELD: lb/stb)
using for simulation of salt washing–out with fresh water (see section 2.24.1). The keyword
should be followed by one real number for each grid block. 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 /.

The keyword should be used when the initial state has been set by enumeration (keywords
PRESSURE (see 12.16.12), RS (see 12.16.37), RV (see 12.16.38), SGAS (see 12.16.15) and
SWAT, see 12.16.14). For a run initialized by equilibration EQUIL (see 12.16.2), the keyword
SALTVD (see 12.16.48) should be used instead of SALT (see 12.16.47) (salt concentration

!
versus depth for equilibration).
The maximal value of initial salt concentration has to be less than 106 for
any units system.

Example
SALT
50*0
50*0.75
50*2.6
50*9.2
50*21.0 /

12.16.47. SALT 1415

Keywords for formats tN, E1, E3 19.1

12.16.48. SALTVD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword sets salt concentration versus depth for each equilibration region using for
simulation of salt washing–out with fresh water (see section 2.24.1).

The keyword should be used when the initial state has been set by equilibration EQUIL
(see 12.16.2). For a run initialized by enumeration (keywords PRESSURE (see 12.16.12), RS
(see 12.16.37), RV (see 12.16.38), SGAS (see 12.16.15) and SWAT, see 12.16.14). the key-
word SALT (see 12.16.47) should be used instead of SALTVD (see 12.16.48).

The data consists of the tables. Number of tables should be equal to the number of equili-
bration region (first parameter of the keyword EQLDIMS, see 12.1.30). Each table should be
terminated with a slash /.

One table row consists of:

1. depth (METRIC: m, FIELD: f t );

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.16.48. SALTVD 1416

Keywords for formats tN, E1, E3 19.1

12.16.49. SRSALT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword specifies initial reservoir salt distribution through its saturation (Saturation
Rock SALT) using for simulation of salt washing–out with fresh water (see section 2.24.1).
The keyword can be used only for runs in which the Brine option is active (the keyword
BRINE, see 12.1.62).

The number of values to be entered is equal to the number of blocks in the model. The
data should be terminated with a slash /.
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.17).
Example
SRSALT
2000*0.2
/

This example sets the initial ratio of reservoir salt volume to the rock volume - 0.2.

12.16.49. SRSALT 1417

Keywords for formats tN, E1, E3 19.1

12.16.50. SURF

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword should be followed by one real number for every grid block specifying the
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 /.

For the description of surfactant injection, see the section 2.23.

For the full description of ASP (Alkaline-Surfactant-Polymer) mathematical model, see

!
the section 5.9. ASP model description.
The maximal value of initial surfactant concentration has to be less than 106
for any units system.

Example
SURF
500*0
500*0.75
500*0.6
500*0 /

12.16.50. SURF 1418

Keywords for formats tN, E1, E3 19.1

12.16.51. SPOLY

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword should be followed by one real number for every grid block specifying the
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
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 /.

Polymer injection – section 2.16.

For the full description of ASP (Alkaline-Surfactant-Polymer) mathematical model, see

!
the section 5.9. ASP model description.
The maximal value of initial polymer concentration has to be less than 106
for any units system.

Example
SPOLY
500*0
500*3.75
500*0
500*3.75 /

12.16.51. SPOLY 1419

Keywords for formats tN, E1, E3 19.1

12.16.52. GASCONC

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword should be followed by one real number for every matrix block specifying the
initial coal gas concentration (METRIC: sm3 /m3 , FIELD: Msc f / f t 3 ) in Coal Bed Methane
model – 2.28.

The number of values should be equal to the number of matrix 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 /.

Note: for compositional model in E3 format the keyword GASCONC can set the initial
coal gas concentration for one component defined via GASCCMP (see 12.16.54).

! The maximal value of initial coal gas concentration has to be less than 106
for any units system.

Example
GASCONC
1200*79.3 1200*77.2 1200*75.4 /

12.16.52. GASCONC 1420

Keywords for formats tN, E1, E3 19.1

12.16.53. GASSATC

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

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.28.

The number of values should be equal to the number of matrix 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 /.

Note 1: for the model in the format E1 the keyword GASSATC is used for the Langmuir
isotherm scaling LANGMUIR (see 12.9.2) at the initial reservoir pressure. In case if the key-
word GASSATC is not specified, LANGMUIR (see 12.9.2) data will be used without scaling.

Note 2: for compositional model in E3 format the keyword GASSATC is used for the
Langmuir isotherm scaling (LANGMUIR (see 12.9.2) or LANGMEXT, see 12.9.6) at the ini-
tial reservoir pressure and composition in the reservoir for one component. The component
is defined via the keyword GASCCMP (see 12.16.54). This scaling factor is used for other
components.

! The maximal value of initial saturated gas concentration in the coal has to
be less than 106 for any units system.

Example
GASSATC
1200*80.3 1200*87.2 1200*85.4 /

12.16.53. GASSATC 1421

Keywords for formats tN, E1, E3 19.1

12.16.54. GASCCMP

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword sets the number of component that is used in the keywords GASSATC
(see 12.16.53) and GASCONC (see 12.16.52) for Coal Bed Methane Model (see section
2.28). If there is only one component in the run you may not define this keyword.
The data should be terminated with a slash /.
Example
GASCCMP
4 /

12.16.54. GASCCMP 1422

Keywords for formats tN, E1, E3 19.1

12.16.55. RPTMAPS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword allows to save additional properties and graphs of calculation results. The
data should be terminated with a slash /.

The following mnemonics can be requested:

• FLOWW – accumulated interblock flows of water phase;

• FLOWO – accumulated interblock flows of oil phase;

• FLOWG – accumulated interblock flows of gas phase;

• FLOWWZ – accumulated interblock flows of water phase in horizontal direction;

• FLOWOZ – accumulated interblock flows of oil phase in horizontal direction;

• FLOWGZ – accumulated interblock flows of gas phase in horizontal direction;

• FIPFLOW – enable FIP flow calculations (crossflow between FIPS through the well
bores are not taken into account for this calculations);

• KRO – relative permeability of oil;

• KRW – relative permeability of water;

• KRG – relative permeability of gas;

• PCOG – capillary pressure in the oil-gas system;

• PCWO – capillary pressure in the water-oil system.

Interblock flows are calculated the following way. The sum of phase flow to the block and
from the block is calculated (absolute values are taken). Then this value is divided by two.
After that we add to this value phase flow from block to the connection (from connection)
and from aquifer (to aquifer).

Properties of accumulated interblock flows will be available via GUI on the tab Grid Prop-
erties, sub-tab Calculated. It is recommended to split a model along smallest accumulated
interblock flows (see section 5.12).
A graph of flow between FIPs will be available on the tab Graphs –Flow Between FIPs.

12.16.55. RPTMAPS 1423

Keywords for formats tN, E1, E3 19.1

Relative permeabilities and capillary pressures will be available for each block on the tab
Graphs – Block Info.
Default: None.
Example
RPTMAPS
FLOWO FLOWG /
This example requests saving two additional parameter maps to results file – oil and gas
accumulated flows.

12.16.55. RPTMAPS 1424

Keywords for formats tN, E1, E3 19.1

12.16.56. RSW

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword sets initial concentration of dissolved gas in water phase. The dissolved gas
can either be CO 2 (CO2SOL, see 12.1.92) or H2 S (H2SSOL, see 12.1.93). All keywords used
for the CO 2 or H2 S solution option are given in the section 3.3.1. The following parameters
should be specified:

1. initial concentration of dissolved gas (CO 2 or H2 S ) in water phase for each grid block
(METRIC: m3 /sm3 ; FIELD: stb/Msc f .

!
The data should be terminated with a slash /.
The maximal value of initial concentration of dissolved gas in water phase
has to be less than 106 for any units system.

Example
RSW 200*0.145 /
In the example initial concentration of dissolved gas in water phase is 0.145 in each grid
block.

12.16.56. RSW 1425

Keywords for formats tN, E1, E3 19.1

12.16.57. SFOAM

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword sets initial foam concentration in grid blocks. It can be used only if foam
model option (see 2.18) is activated by the keyword FOAM (see 12.1.68). 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):

• if it is GAS – METRIC: kg/sm3 , FIELD: lb/Msc f ;

• if it is WATER – METRIC: kg/sm3 , FIELD: lb/stb.

!
The data should be terminated with a slash /.
The maximal value of initial foam concentration has to be less than 106 for
any units system.

Example
SFOAM
300*0.4 /
In the example initial foam concentration in each block is 0.4.

12.16.57. SFOAM 1426

Keywords for formats tN, E1, E3 19.1

12.16.58. SOILR

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword sets initial residual oil saturation values in each grid block. It can be used
only if residual oil saturation option (see 2.19) is activated by the keyword SOR (see 12.12.1).
The following parameters should be specified:

1. initial residual oil saturation values in each grid block.

The data should be terminated with a slash /.

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.16.58. SOILR 1427

Keywords for formats tN, E1, E3 19.1

12.16.59. ROMF

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword sets initial composition of residual oil in each grid block. It can be used only
if residual oil saturation option (see 2.19) is activated by the keyword SOR (see 12.12.1).
The following parameters should be specified:

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.

The data should be terminated with a slash /.

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.16.59. ROMF 1428

Keywords for formats tN, E1, E3 19.1

12.16.60. WMF

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword sets initial molar concentration of water components in each grid block. This
keyword can be used only in multiple component water run.
Multiple component water option is activated with the keyword COMPW (see 12.14.2).
Description of this option is in the section 3.10.
The following parameters should be specified:

1. initial concentration of water components 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. So, Nx · Ny · Nz · Nw values should be specified, where Nw is the
number from COMPW (see 12.14.2).

The data should be terminated with a slash /.

Example
WMF
400*0.9
400*0.1
/
In the example initial concentration of two water components is set.

12.16.60. WMF 1429

Keywords for formats tN, E1, E3 19.1

12.16.61. RPTRSTD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

This keyword defines time steps at which the data required for restart (that is, all maps and
graphs in tNavigator format) are saved to the result files. It has higher priority than RPTMAPD
(see 12.16.64), RPTMAPT (see 12.16.65), and similar keywords. The detailed description of
options for selective recording of calculation results is given in the section 9.1.
After the keyword the dates should be specified (at which the 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 (an alias for JUL).
The data should be terminated with a slash /.

Example
RPTRSTD
01 JAN 2018
01 JUL 2018
01 JAN 2019
/
In this example the maps and graphs will be saved on the specified dates.

12.16.61. RPTRSTD 1430

Keywords for formats tN, E1, E3 19.1

12.16.62. RPTRSTT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

This keyword defines time intervals after which the data required for restart (that is, all
maps and graphs in tNavigator format) are saved to the result files. It has higher priority than
RPTMAPD (see 12.16.64), RPTMAPT (see 12.16.65), and similar keywords. The detailed
description of options for selective recording of calculation results is given in the section 9.1.
After the keyword the time unit should be entered, and then the array defining the time
intervals to record the data. Possible time units are MONTH (month), DAY (day), YEAR (year).
The data should be terminated with a slash /.
Data for the first and last time step are always recorded.

Example
RPTRSTT
MONTH
2 3 4
/
In this example the time unit is given as month. Below there are numbers 2, 3 and 4. This
means that the data will be recorded on the first time step, then in 2 months, then in 3 months,
then in 4 months, and then every 4 months until the end.

12.16.62. RPTRSTT 1431

Keywords for formats tN, E1, E3 19.1

12.16.63. RPTRSTL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

This keyword specifies that the data required for restart (that is, all maps and graphs in
tNavigator format) are saved to the result files only on the first and last time steps. It has higher
priority than RPTMAPD (see 12.16.64), RPTMAPT (see 12.16.65), and similar keywords. The
detailed description of options for selective recording of calculation results is given in the
section 9.1.
The keywords has no parameters. The data should be terminated with a slash /.
Example
RPTRSTL
/

12.16.63. RPTRSTL 1432

Keywords for formats tN, E1, E3 19.1

12.16.64. RPTMAPD/RPTGRAPHD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY x SCHEDULE

This keyword allows to manage the recording of calculated maps (RPTMAPD) and graphs
(RPTGRAPHD) to the hard disk (record data only for time steps selected by the user). Thus
the amount of data written to disk can be reduced. The detailed description of options for
recording results of calculations and corresponding keywords are given in the section 9.1.

After the keyword the dates should be specified (at which the 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 (an alias for JUL).
Each data line should be terminated with the symbol /. All data should be terminated with a
final slash /.
Data for the first and last time step are 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.

The following possibilities are available:

1. Keywords to record data in specified dates – RPTMAPD, RPTGRAPHD.

2. Keywords to record data in selected time intervals – RPTMAPT (see 12.16.65), RPT-
GRAPHT (see 12.16.65).

3. Keywords to record data only for first and last time steps – RPTMAPL (see 12.16.66),
RPTGRAPHL (see 12.16.66).

In graphical interface in the window with model one should choose "Reload with New
Recording Options". Choose "As in RPTMAPD and RPTGRAPHD keywords".

12.16.64. RPTMAPD/RPTGRAPHD 1433

Keywords for formats tN, E1, E3 19.1

Example
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 disk for the
dates: August 1, 1995; September 1, 1995; October 1, 1995; November 1, 1997; December 1,
1997; and January 1, 1998.

12.16.64. RPTMAPD/RPTGRAPHD 1434

Keywords for formats tN, E1, E3 19.1

12.16.65. RPTMAPT/RPTGRAPHT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY x SCHEDULE

This keyword allows to manage the recording of calculated maps (RPTMAPT) and graphs
(RPTGRAPHT) to the hard disk (record data only for time steps selected by the user). Thus
the amount of data written to disk can be reduced. The detailed description of options for
recording results of calculations and corresponding keywords are given in the section 9.1.

After the keyword the time unit should be entered, and then the array defining the time
intervals between data recordings. If the field development history is longer than the sum of
all specified time intervals, then the last specified time interval will be applied repeatedly.
Detailed description is shown in the example below. Possible time units are MONTH (month),
DAY (day), YEAR (year). The data should be terminated with a slash /.
Data for the first and last time step are 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.

The following possibilities are available:

1. Keywords to record data in specified dates – RPTMAPD (see 12.16.64), RPTGRAPHD

(see 12.16.64).

2. Keywords to record data in selected time intervals – RPTMAPT, RPTGRAPHT.

3. Keywords to record data only for first and last time steps – RPTMAPL (see 12.16.66),
RPTGRAPHL (see 12.16.66).

In graphical interface in the window with model one should choose "Reload with New
Recording Options". Choose "As in RPTMAPD and RPTGRAPHD keywords".

12.16.65. RPTMAPT/RPTGRAPHT 1435

Keywords for formats tN, E1, E3 19.1

Example
RPTMAPT
MONTH
2 3 4
/

RPTGRAPHT
MONTH
2 3 4
/

In this example the time unit is given as month. Below there are numbers 2, 3 and 4. This
means that Map and Graphs results will be recorded on the first time step, then in 2 months,
then in 3 months, then in 4 months, and then every 4 months until the end.
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 recorded 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.16.65. RPTMAPT/RPTGRAPHT 1436

Keywords for formats tN, E1, E3 19.1

12.16.66. RPTMAPL/RPTGRAPHL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY x SCHEDULE

This keyword allows to manage the recording of calculated maps (RPTMAPL) and graphs
(RPTGRAPHL) to the hard disk (record data only for time steps selected by the user). Thus
the amount of data written to disk can be reduced. The detailed description of options for
recording results of calculations and corresponding keywords are given in the section 9.1.

If these keywords are used results will be recorded on disk only for first and last time
steps. The data should be terminated with a slash /.

• 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.

The following possibilities are available:

1. Keywords to record data in specified dates – RPTMAPD (see 12.16.64), RPTGRAPHD

(see 12.16.64).

2. Keywords to record data in selected time intervals – RPTMAPT (see 12.16.65), RPT-
GRAPHT (see 12.16.65).

3. Keywords to record data only for first and last time steps – RPTMAPL, RPTGRAPHL.

In graphical interface in the window with model one should go to "Reload with New
Recording Options", then select "As in RPTMAPD and RPTGRAPHD keywords".

Example
RPTMAPL
/

RPTGRAPHL
/

12.16.66. RPTMAPL/RPTGRAPHL 1437

Keywords for formats tN, E1, E3 19.1

12.17. Inflow from aquifer

The list of supported aquifer models and options is available in the section 2.13.

12.17. Inflow from aquifer 1438

Keywords for formats tN, E1, E3 19.1

12.17.1. AQUDIMS

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword sets dimensions for aquifers. The data should be terminated with a slash /.
The description of aquifer’s models, corresponding formulas and keywords are given in the
section 2.13.
The following parameters should be entered:
1. maximum number of lines of numerical aquifer data entered via keyword AQUNUM
(see 12.17.13); this is an E1/E3 compatibility field. (IGNORED) In tNavigator number
of lines does not have to be specified because the tables are allocated dynamically;
Default: 1.

2. maximum number of lines of connection data for numerical aquifers entered via key-
word AQUCON (see 12.17.14); this is an E1/E3 compatibility field. (IGNORED) In
tNavigator number of lines does not have to be specified because the tables are allo-
cated dynamically;
Default: 1.

3. maximum number of influence tables for Carter-Tracy aquifers, entered via the
keyword AQUTAB (see 12.17.10), (if there are any user supplied tables AQUTAB
(see 12.17.10) this number should be 2 or greater, because first table is default);
Default: 1.

4. maximum number of rows in a Carter-Tracy aquifer influence table;

Default: 36.

5. maximum number of analytic aquifers in the model;

Default: 1.

6. maximum number of grid blocks connected to any single analytic aquifer; this is an
E1/E3 compatibility field. (IGNORED) In tNavigator number of lines does not have to
be specified because the tables are allocated dynamically.
Default: 1.

7. maximum number of aquifer lists; this is an E1/E3 compatibility field. (IGNORED) In

tNavigator number of lines does not have to be specified because the tables are allocated
dynamically.
Default: 0.

12.17.1. AQUDIMS 1439

Keywords for formats tN, E1, E3 19.1

8. maximum number of analytic aquifers in any single aquifer list; this is an E1/E3 com-
patibility field. (IGNORED) In tNavigator number of lines does not have to be specified
because the tables are allocated dynamically.
Default: 0.

For E3 models parameters 1 and 5 of this keyword are similar. Analogously parameters 2
and 6 are similar. If both parameters are specified then the maximum value will be taken.

Example
AQUDIMS
0 0 6 100 100 100 0 0 /

12.17.1. AQUDIMS 1440

Keywords for formats tN, E1, E3 19.1

12.17.2. AQUFLUX

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY x SCHEDULE

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.17.11). The description of aquifer’s models, corresponding formulas
and keywords are given in the section 2.13.

Formula of water inflow from the aquifer – 2.91 (see section section 2.13).

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 );
can be either positive or negative,

3. initial salt concentration in the aquifer (METRIC: kg/sm3 , FIELD: lb/stb) (this param-
eter can be entered only if Brine option is active BRINE, see 12.1.62).

4. temperature in aquifer (METRIC: ◦ C, FIELD: ◦ F) (this parameter is used only if tem-

perature TEMP (see 12.1.64) or thermal option THERMAL (see 12.1.54) 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 THER-
MAL (see 12.1.54) is used.

All data should be terminated with a final slash /.

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.17.11), and then by block face area.

12.17.2. AQUFLUX 1441

Keywords for formats tN, E1, E3 19.1

12.17.3. AQUCHWAT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY x SCHEDULE

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.17.11). The description of aquifer’s models, corresponding formulas
and keywords are given in the section 2.13.

Formula of water inflow from the aquifer – 2.100 (see section 2.13).

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 /.
One data line contains the following parameters:

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;
• Default: PRESSURE.

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 pa-
rameter 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);

Default: 1.

12.17.3. AQUCHWAT 1442

Keywords for formats tN, E1, E3 19.1

7. initial salt concentration in the aquifer (METRIC: kg/sm3 , FIELD: lb/stb) (this param-
eter can be entered only if Brine option is active BRINE, see 12.1.62).
Default: 0.

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 E1/E3 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 E1/E3 compatibility field.

10. flag for ignoring the capillary pressure term: (YES or NO). IGNORED. This is an E1/E3
compatibility field.
Default: NO.

11. minimum value of allowed flow per aquifer connection (METRIC: sm3 /day, FIELD:
stb/day). IGNORED. This is an E1/E3 compatibility field.

12. maximum value of allowed flow per aquifer connection (METRIC: sm3 /day, FIELD:
stb/day). IGNORED. This is an E1/E3 compatibility field.

13. flag for ignoring the depth term: (YES or NO). IGNORED. This is an E1/E3 compati-
bility field.
Default: NO.

14. impose min. and max. flow rates (parameters 11 and 12) before (0 value) or after (non-
zero value) the flow rate scaling by the grid block saturation when water goes in aquifer
from grid. IGNORED. This is an E1/E3 compatibility field.
Default: 0.

15. temperature in aquifer (METRIC: ◦ C, FIELD: ◦ F) (this parameter is used only if tem-
perature TEMP (see 12.1.64) or thermal option THERMAL (see 12.1.54) is used).

Example
AQUCHWAT
1 2400 'PRESSURE' 90 0.00002 1 /
/

12.17.3. AQUCHWAT 1443

Keywords for formats tN, E1, E3 19.1

12.17.4. AQUFET

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

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.17.6),
AQUANCON, see 12.17.11). The description of aquifer’s models, corresponding formulas and
keywords are given in the section 2.13.

Formula of water inflow from the aquifer – 2.92 (see section 2.13).

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),

Default: If this parameter is defaulted (or set as negative value) then initial pressure is
calculated to make the aquifer as nearly as possible in equilibrium with the reservoir.

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.28),

12.17.4. AQUFET 1444

Keywords for formats tN, E1, E3 19.1

14. initial salt concentration in the aquifer (METRIC: kg/sm3 , FIELD: lb/stb) (this param-
eter can be entered only if Brine option is active BRINE, see 12.1.62).
Default: 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 pro-
portion 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.17.4. AQUFET 1445

Keywords for formats tN, E1, E3 19.1

12.17.5. AQUOPTS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword set preferences of analytical aquifers calculation. The description of aquifer’s
models, corresponding formulas and keywords are given in the section 2.13. The following
parameters should be specified:
1. number of aquifer;
2. aquifer calculation option:
• type of numerical scheme, which is used to calculate aquifer’s 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.17.3) and AQUFLUX (see 12.17.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. Moreover, it is possible to indicate the parameter ε , specifying
deviation from critical water saturation SWCR , i.e. the point SWCR −ε , at which
the outflow smoothing starts;
– OUTFLOW_RP – water RP is being to account at calculation of flow from
reservoir to aquifer.
– Default: in E1/E3 models for Fetkovich, Carter-Tracy and AQUCHWAT
(see 12.17.3) aquifers OUTFLOW_S option is used by default. In MO models
for these aquifers OUTFLOW_RP option is used by default.
OUTFLOW_S_SMOOTH default deviation ε from critical water saturation
SWCR : 0.001.
• capillary pressure consideration:
– PCOW_IGNORE – capillary pressure values are not accounted during aquifer
flow calculation;

12.17.5. AQUOPTS 1446

Keywords for formats tN, E1, E3 19.1

– PCOW_CONSIDER – capillary pressure values are accounted during aquifer

flow calculation. Note: it is important only for Fetkovich, Carter-Tracy and
AQUCHWAT (see 12.17.3) aquifer types.
– Default: in E1/E3 models for Fetkovich and AQUCHWAT (see 12.17.3)
aquifers capillary pressures are accounted, for Carter-Tracy they are not ac-
counted. For MO models capillary pressures are not accounted.
• gravity effect consideration:
– BD – bottom-drive option for Carter-Tracy aquifer type.

3. percent of aquifer blocks, which will be calculated by fully implicit method. This value
should obtain to interval (0; 100).
Default: 0.

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.
Each data line should be ended by a symbol /. The data should be terminated with a slash
/.

Example
AQUOPTS
1 ’FI’ /
/
In the example the first aquifer is calculated by fully implicit scheme.
Example
AQUOPTS
1 ’FI’ /
1 ’OUTFLOW_RP’ /
2 ’OUTFLOW_S_SMOOTH’ 0.005/
/
In the example for aquifer 1 two options are set: FI and OUTFLOW_RP. For the aquifer 2
the outflow smoothing starts at SWCR − 0.005.

12.17.5. AQUOPTS 1447

Keywords for formats tN, E1, E3 19.1

12.17.6. AQUFETP

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY x SCHEDULE

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.17.11). The description of aquifer’s models, corresponding formulas and keywords are
given in the section 2.13.

Formula of water inflow from the aquifer – 2.92 (see section 2.13).

Below the following data should be input:

1. aquifer ID number (positive number),
2. datum depth (METRIC: m, FIELD: f t ),
3. initial pressure on datum depth (METRIC: bars, FIELD: psi),
Default: If this parameter is defaulted (or set as negative value) then initial pressure is
calculated to make the aquifer as nearly as possible in equilibrium with the reservoir.
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),
7. number of PVTW (see 12.5.5) table, describing properties of water in aquifer,
8. initial salt concentration in the aquifer (METRIC: kg/sm3 , FIELD: lb/stb) (this param-
eter can be entered only if Brine option is active BRINE, see 12.1.62).
Default: 0kg/sm3 .
9. temperature in aquifer (METRIC: ◦ C, FIELD: ◦ F) (this parameter is used only if tem-
perature TEMP (see 12.1.64) or thermal option THERMAL (see 12.1.54) is used).
Each data line should be terminated with the symbol /. All data should be terminated with
a final slash /.
Example
AQUFETP
1 2000 250 100000 1e-5 20 1/
2 2000 250 100000 1e-5 40 1 /
/

12.17.6. AQUFETP 1448

Keywords for formats tN, E1, E3 19.1

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.17.6. AQUFETP 1449

Keywords for formats tN, E1, E3 19.1

12.17.7. AQSTREAW

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY x SCHEDULE

The keyword sets water composition of AQUCHWAT (see 12.17.3), AQUCT (see 12.17.9),
AQUFETP (see 12.17.6) or AQUFLUX (see 12.17.2) aquifers. The description of aquifer’s
models, corresponding formulas and keywords are given in the section 2.13. The keyword can
be used only in multiple component water run.
Multiple component water option is activated with the keyword COMPW (see 12.14.2).
Description of this option is in the section 3.10.
One data line contains the following parameters:

1. aquifer id;

2. mole fraction of the components. Nw values should be specified, where Nw is the

number from COMPW (see 12.14.2). The sum of the mole fractions must be 1.

Any number of data lines can be specified. Each data line should be terminated with the
symbol /. The data should be terminated with a slash /.
Example
AQSTREAW
1 0.4 0.3 0.3 /
2 0.4 0.4 0.2 /
/
In the example molar fractions are set for two aquifers.

12.17.7. AQSTREAW 1450

Keywords for formats tN, E1, E3 19.1

12.17.8. AQANTRC

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword specifies initial tracer concentrations for analytic aquifers (keywords
AQUFET (see 12.17.4), AQUFETP (see 12.17.6), AQUCT (see 12.17.9), AQUFLUX,
see 12.17.2). The description of aquifer’s models, corresponding formulas and keywords are
given in the section 2.13.

Arbitrarily many data lines terminated with a slash / may be entered. All data should be
terminated with a final slash /.
One data line contains the following parameters:

1. aquifer number (positive value),

2. tracer name (tracer should be defined to exist in the water phase TRACER, see 12.7.10),

3. initial tracer concentration in the aquifer (from 0 to 1).

Default: if tracer isn’t specified its concentration is – 0.

Example
AQANTRC
1 A1 0.3 /
/
Initial tracer A1 concentration in the aquifer 1 is 30%.

12.17.8. AQANTRC 1451

Keywords for formats tN, E1, E3 19.1

12.17.9. AQUCT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT x PROPS
Section
REGIONS x SOLUTION SUMMARY x SCHEDULE

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.17.11). The description of aquifer’s models, corresponding formulas and keywords are
given in the section 2.13.

Dimensions for aquifer are set via AQUDIMS (see 12.17.1).

Formula of water inflow from the aquifer – 2.93 (see section 2.13).

Below the following data should be input:

1. aquifer number (positive number),

2. datum depth (METRIC: m, FIELD: f t ),

3. initial pressure on datum depth (METRIC: bars, FIELD: psi),

Default: If this parameter is defaulted (or set as negative value) then initial pressure is
calculated to make the aquifer as nearly as possible in equilibrium with the reservoir.

4. aquifer permeability (mD),

5. aquifer porosity,
Default: 1.

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), de-
grees,
Default: 360 degrees.

10. number of PVTW (see 12.5.5) table, describing properties of water in aquifer,
Default: 1.

12.17.9. AQUCT 1452

Keywords for formats tN, E1, E3 19.1

11. AQUTAB (see 12.17.10) table number, controlling dependence of pressure on dimen-
sionless time,
Default: 1.

12. initial salt concentration in the aquifer (METRIC: kg/sm3 , FIELD: lb/stb) (this param-
eter can be entered only if Brine option is active BRINE, see 12.1.62),
Default: 0.

13. temperature in aquifer (METRIC: ◦ C, FIELD: ◦ F) (this parameter is used only if tem-
perature TEMP (see 12.1.64) or thermal option THERMAL (see 12.1.54) is used);

14. deny or not water backflow to the aquifer (YES – deny or NO – don’t deny).
Default: NO – don’t deny.

Each data line should be terminated with the symbol /. All data should be terminated with
a final slash /.
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.17.9. AQUCT 1453

Keywords for formats tN, E1, E3 19.1

12.17.10. AQUTAB

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT x PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword defines an influence function tables for Carter-Tracy aquifers. (the number
of tables in set via AQUDIMS, see 12.17.1). Each table should be terminated with a slash /.
The description of aquifer’s models, corresponding formulas and keywords are given in the
section 2.13.

Formula of water inflow from the aquifer – 2.93 (see section 2.13).

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.
One table row should contain the following parameters:

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.17.10. AQUTAB 1454

Keywords for formats tN, E1, E3 19.1

12.17.11. AQUANCON

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

Used to define connections of analytic aquifers (AQUFLUX (see 12.17.2), AQUFETP

(see 12.17.6), AQUCT (see 12.17.9), AQUFET, see 12.17.4) and grid blocks of the main grid.
To connect an aquifer to the LGR blocks, use the related keyword AQANCONL (see 12.17.12).
The description of aquifer’s models, corresponding formulas and keywords are given in the
section 2.13.

The keyword accepts multiple lines of data, each line defines a cube of grid blocks. Each
data line should be terminated with the symbol /. Each block will be connected to analytic
aquifer by the face indicated for the whole cube. The data should be terminated with a slash
/.
The following data is input on each line:

1. aquifer number,

2. i-coordinate of start of cube connected with aquifer,

3. i-coordinate of end of cube connected with aquifer,

4. j -coordinate of start of cube connected with aquifer,

5. j -coordinate of end of cube connected with aquifer,

6. k -coordinate of start of cube connected with aquifer,

7. k -coordinate of end of cube connected with aquifer,

8. index denoting which face will be connected with aquifer; possible values: I− (face 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.17.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,
Default: grid block area.

12.17.11. AQUANCON 1455

Keywords for formats tN, E1, E3 19.1

10. influx coefficient multiplier; for constant flux aquifer, specified by AQUFLUX
(see 12.17.2) keyword, when multiplier is specified, grid block face area changes, being
multiplied on it,
Default: 1.

11. whether connections from faces connected to 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: 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 reser-
voir will have water influx. The cells along the edge of reservoir will have double inflow,
because they all have two faces connected, in I− direction and in J− direction.

12.17.11. AQUANCON 1456

Keywords for formats tN, E1, E3 19.1

12.17.12. AQANCONL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

Used to define connections of analytic aquifers (AQUFLUX (see 12.17.2), AQUFETP

(see 12.17.6), AQUCT (see 12.17.9), AQUFET, see 12.17.4) and grid blocks from local grid
refinements. To connect an aquifer to the blocks of the main grid, use the related keyword
AQUANCON (see 12.17.11). The description of aquifer’s models, corresponding formulas and
keywords are given in the section 2.13.

The keyword accepts multiple lines of data, each line defines a cube of grid blocks within
the LGR. Each data line should be terminated with the symbol /. Each block will be connected
to analytic aquifer by the face indicated for the whole cube. The data should be terminated
with a slash /.
The following data is input on each line:
1. aquifer number,

2. local grid refinement name,

3. i-coordinate of start of cube connected with aquifer,

4. i-coordinate of end of cube connected with aquifer,

5. j -coordinate of start of cube connected with aquifer,

6. j -coordinate of end of cube connected with aquifer,

7. k -coordinate of start of cube connected with aquifer,

8. k -coordinate of end of cube connected with aquifer,

9. index denoting which face will be connected with aquifer; possible values: I− (face 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 ),

10. 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.17.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,
Default: grid block area.

12.17.12. AQANCONL 1457

Keywords for formats tN, E1, E3 19.1

11. influx coefficient multiplier; for constant flux aquifer, specified by AQUFLUX
(see 12.17.2) keyword, when multiplier is specified, grid block face area changes, being
multiplied on it,
Default: 1.

12. whether connections from faces connected to 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: NO.

Example
AQANCONL
1 LGR2 1 5 1 5 15 15 K- 3* /
/
In this example the cells from local grid refinement LGR2 are connected to the aquifer
number 1 in the direction K−.

12.17.12. AQANCONL 1458

Keywords for formats tN, E1, E3 19.1

12.17.13. AQUNUM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

The keyword assigns a numerical aquifer to a block (aquifer is set via the keyword
AQUCON, see 12.17.14).The description of aquifer’s models, corresponding formulas and
keywords are given in the section 2.13.

Each line is a grid block representing a numerical aquifer. Each data line should be termi-
nated with the symbol /. 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;
Default: value for block i jk .
8. permeability (mD);
9. aquifer depth (METRIC: m, FIELD: f t ) (may be larger than real depth of the block
i jk );
Default: value for block i jk .
10. initial pressure (METRIC: barsa, FIELD: psia);
11. PVT table number for aquifer (this parameter is taken into account for models in E1
format, for model in E3 format this parameter will be ignored);
Default: PVTNUM (see 12.4.2) value for block i jk .
12. saturation table number for aquifer (this parameter is taken into account for models in
E1 format, for model in E3 format this parameter will be ignored).
Default: PVTNUM (see 12.4.2) value for block i jk .

12.17.13. AQUNUM 1459

Keywords for formats tN, E1, E3 19.1

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 pres-
sure, PVT table number and saturation table number.

12.17.13. AQUNUM 1460

Keywords for formats tN, E1, E3 19.1

12.17.14. AQUCON

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC x GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

Used to define connections of numerical aquifers (AQUNUM, see 12.17.13) and grid
blocks. The description of aquifer’s models, corresponding formulas and keywords are given
in the section 2.13.

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,

2. i-coordinate of start of cube connected with aquifer,

3. i-coordinate of end of cube connected with aquifer,

4. j -coordinate of start of cube connected with aquifer,

5. j -coordinate of end of cube connected with aquifer,

6. k -coordinate of start of cube connected with aquifer,

7. k -coordinate of end of cube connected with aquifer,

8. index denoting which face will be connected with aquifer; possible values — I− (face
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),
Default: 1.

10. transmissibility option (0 or 1) The transmissibility between the numerical aquifer and
grid block is calculated via the formula:
CDARCY
T=
( T1a ) + ( T1c )

12.17.14. AQUCON 1461

Keywords for formats tN, E1, E3 19.1

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
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.17.13),
Aa – aquifer area (entered via AQUNUM, see 12.17.13),
Da – half of aquifer length (entered via AQUNUM, see 12.17.13).
If 1 option:
Ka ∗ Ac
Ta =
Da
Default: 0.

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: 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.28).

12.17.14. AQUCON 1462

Keywords for formats tN, E1, E3 19.1

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.17.14. AQUCON 1463

Keywords for formats tN, E1, E3 19.1

12.17.15. AQUGP

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

The keyword defines geometry of aquifer connection to reservoir. The description of

aquifer’s models, corresponding formulas and keywords are given in the section 2.13. Prop-
erties for several aquifers can be specified. Each aquifer’s properties are specified in separate
line. The following parameters should be specified:

1. aquifer id;

2. aquifer’s 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 connected, links of
the other directions are connected only if connecting block doesn’t have active
neighbor one of the same direction. If aquifer is set by AQUFLUX (see 12.17.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.28) 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 model’s 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.28). Connection is performed by links with I+, I-, J+,
J- directions only. If aquifer is set by AQUFLUX (see 12.17.2) then productiv-
ity 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.

12.17.15. AQUGP 1464

Keywords for formats tN, E1, E3 19.1

For Dual Porosity/Dual Permeability models:

• DEPTHF | DEPTHM – extention of DEPTH connection type for DP models.
Aquifer will be connected only to fractures (DEPTHF) or matrix (DEPTHM) blocks
at the specified depth;
• BOUNDARYF | BOUNDARYM – extention of BOUNDARY connection type for
DP models.
Aquifer will be connected only to fractures (BOUNDARYF) or matrix
(BOUNDARYM) blocks of the model’s boundary;
• RESBNDF | RESBNDM – extention of RESBND connection type for DP models.
Aquifer will be connected only to fractures (RESBNDF) or matrix (RESBNDM)
blocks of the real reservoir boundary (active blocks near reservoir boundary);

!
If DEPTH, BOTTOM, BOUNDARY or RESBND connection type is de-
fined in DP model, the aquifer will be connected to fractures. If some
fracture blocks are inactive in the defined blocks array, the connections
will be created in corresponding matrix blocks corresponding to inactive
fracture blocks.

3. aquifer connection depth. This parameter is used only for DEPTH, DEPTHF, DEPTHM,
connection types and it must be specified for them;
4. equil region number, block of which are allowed to connect to aquifer. This parameter
is used only for DEPTH, DEPTHF, DEPTHM, connection types.
Default: all regions.
5. weighting type to calculate blocks’ productivity indexes for DEPTH, DEPTHF, DEPTHM,
connection types:
• EVEN – all productivity indexes are equal to 1;
• AREA – productivity indexes are equal to connection area considering NTG
(see 12.2.25);
• Default: EVEN.
Each data line should be terminated with the symbol /. All data should be terminated with
a final slash /.

i Aquifer connections defined by AQUANCON (see 12.17.11) keyword can be

combined with DEPTH, DEPTHM, DEPTHF connection types.

Several connection types from the same group can be set for one aquifer:

i • Group 1: DEPTH, DEPTHM, DEPTHF and AQUANCON (see 12.17.11)

• Group 2: RESBND, RESBNDM, RESBNDF

12.17.15. AQUGP 1465

Keywords for formats tN, E1, E3 19.1

Example
AQUGP
1 RESBND /
/

12.17.15. AQUGP 1466

Keywords for formats tN, E1, E3 19.1

12.17.16. HMMLCTAQ

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

This keyword specifies modifiers for Carter-Tracy aquifer (defined via AQUCT,
see 12.17.9). This keyword can be used for history matching. The description of aquifer’s
models, corresponding formulas and keywords are given in the section 2.13.

An arbitrary number of lines can be specified. Each data line should be terminated with
the symbol /. All data should be terminated with a final slash /.
One data line contains the following parameters:

1. aquifer number (1-st parameter of AQUCT, see 12.17.9),

2. multiplier on aquifer permeability,

Default: 1.

3. multiplier on aquifer angle of influence (angle subtended by mutual boundary of reser-

voir and aquifer),
Default: 1.

4. multiplier on aquifer depth.

Default: 1.

Example
HMMLCTAQ
1 3.0 1.7 /
2 3.0 1.7 /
/

12.17.16. HMMLCTAQ 1467

Keywords for formats tN, E1, E3 19.1

12.17.17. HMMLFTAQ

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY SCHEDULE

This keyword specifies modifiers for Fetkovich aquifer (defined via AQUFET (see 12.17.4)
(or AQUFETP (see 12.17.6) and AQUANCON, see 12.17.11)). This keyword can be used for
history matching. The description of aquifer’s models, corresponding formulas and keywords
are given in the section 2.13.

An arbitrary number of lines can be specified. Each data line should be terminated with
the symbol /. All data should be terminated with a final slash /.
One data line contains the following parameters:

1. aquifer number (1-st parameter of AQUFETP, see 12.17.6),

2. multiplier on initial volume of water in the aquifer,

Default: 1.

3. multiplier on aquifer productivity index,

Default: 1.

4. multiplier on aquifer depth.

Default: 1.

Example
HMMLFTAQ
1 2.5 1.7 /
2 1.5 1.7 /
/

12.17.17. HMMLFTAQ 1468

Keywords for formats tN, E1, E3 19.1

12.18. Data output

12.18.1. SUMMARY

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
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 saved 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:

12.18. Data output 1469

Keywords for formats tN, E1, E3 19.1

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.
in res.c. – in reservoir conditions.

12.18.1. SUMMARY 1470

Keywords for formats tN, E1, E3 19.1

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 rate above GOC FOPRA GOPRA WOPRA
Oil rate below GOC FOPRB GOPRB WOPRB
Oil production FOPP GOPP WOPP
potential
Oil production WOPP2
potential including
shut/stopped wells
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 above GOC FOPTA GOPTA WOPTA
Oil total below GOC FOPTB GOPTB WOPTB
Oil rate at n-th FOnPR GOnPR WOnPR
separator 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.18.1. SUMMARY 1471

Keywords for formats tN, E1, E3 19.1

Oil density at surface WODN

conditions

Water production and injection parameters

Parameter Field Region Group Well Connection Completion

Water rate FWPR RWPR GWPR WWPR CWPR
Water rate (H) FWPRH GWPRH WWPRH
Water production FWPP GWPP WWPP
potential
Water production WWPP2
potential including
shut/stopped wells
Water total FWPT RWPT GWPT WWPT CWPT CWPTL
WWPTL
Water total (H) FWPTH GWPTH WWPTH
Water production FWPRTT
target total
Water injection rate FWIR RWIR GWIR WWIR CWIR CWIRL
WWIRL
Water injection rate FWIRH GWIRH WWIRH
(H)
Water injection FWPI WWPI
potential
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.18.1. SUMMARY 1472

Keywords for formats tN, E1, E3 19.1

Tracer production and injection parameters

Parameter Well
Tracer injection concentration WTIC
Tracer production concentration WTPC
Tracer injection rate WTIR
Tracer production rate WTPR
Tracer injection total WTIT
Tracer production total WTPT
Polymer injection concentration WCIC
Salt injection concentration WSIC
Alkaline injection concentration WTICALK
Surfactant injection concentration WTICSUR
Tracer A injection concentration WTICA
Polymer production concentration WCPC
Salt production concentration WSPC
Alkaline production concentration WTPCALK
Surfactant production concentration WTPCSUR
Tracer 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
Tracer A production WTPRA
Polymer injection total WCIT
Salt injection total WSIT
(to be continued)

12.18.1. SUMMARY 1473

Keywords for formats tN, E1, E3 19.1

(continued)
Alkaline injection total WTITALK
Surfactant injection total WTITSUR
Tracer A injection total WTITA
Polymer production total WCPT
Salt production total WSPT
Alkaline production total WTPTALK
Surfactant production total WTPTSUR
Tracer A production total WTPTA

Gas production and injection parameters

Parameter Field Region Group Well Connection Completion

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 rate above GOC FGPRA GGPRA WGPRA
Gas rate below GOC FGPRB GGPRB WGPRB
Gas production FGPP GGPP WGPP
potential
Gas production WGPP2
potential including
shut/stopped wells
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
(to be continued)

12.18.1. SUMMARY 1474

Keywords for formats tN, E1, E3 19.1

(continued)
Gas total above GOC FGPTA GGPTA WGPTA
Gas total below GOC FGPTB GGPTB WGPTB
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 FGnPR GGnPR WGnPR
separator stage
Gas flow rate CGFR CGFRL
WGFRL
CGPRL
WGPRL
Free gas flow rate CGFRF
Solution gas flow rate CGFRS
Gas density at surface WGDN
conditions

12.18.1. SUMMARY 1475

Keywords for formats tN, E1, E3 19.1

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. FVPR GVPR WVPR
cond.
Molar production rate WMPR
Molar production rate WMPRWEF
(WEFAC)
Liquid total FLPT GLPT WLPT CLPT CLPTL
WLPTL
Liquid total (H) FLPTH GLPTH WLPTH
Liquid total in res. FVPT GVPT WVPT CVPT CVPTL
cond. WVPTL
Molar production total GMPT
Molar production GMPTT
target total
Liquid injection rate FWIR GWIR WWIR CWIR
Liquid injection rate FWIRH GWIRH WWIRH
(H)
Liquid injection rate in FVIR GVIR WVIR
res. cond.
Liquid injection total FWIT GWIT WWIT CWIT
Liquid injection total FWITH GWITH WWITH
(H)
Liquid injection total FVIT GVIT WVIT CVIT CVITL
in res. cond. WVITL
Liquid flow rate CLFR CLFRL
WLFRL
Liquid flow rate in res. CVFR CVFRL
cond. WVFRL

12.18.1. SUMMARY 1476

Keywords for formats tN, E1, E3 19.1

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
connection (H)
1-point pressure WBP
average (WPAVE)
1-point pressure WBP0
average recalculated to
reference depth
4-point pressure WBP4
average (WPAVE)
5-point pressure WBP5
average (WPAVE)
9-point pressure WBP9
average (WPAVE)

Pore volume

Parameter Field Region Block

Pore volume in res. conditions FRPV RRPV
Pore volume containing oil FOPV ROPV
Pore volume containing gas FGPV RGPV
Pore volume containing water FWPV RWPV

12.18.1. SUMMARY 1477

Keywords for formats tN, E1, E3 19.1

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

Oil in regions and grid blocks. Oil recovery efficiency

Parameter Field Region Block

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
Oil-in-place at reservoir conditions FOIPR
((Initial Oil-in-place) - (current))/initial FOE ROE
((Initial Oil-in-place) - (current))/Initial FOEIG ROEIG
mobile oil with respect to Gas
((Initial Oil-in-place) - (current))/Initial FOEIW ROEIW
mobile oil 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

Parameter Field Region Block

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.18.1. SUMMARY 1478

Keywords for formats tN, E1, E3 19.1

Gas in regions and grid blocks

Parameter Field Region Block

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
Gas-liquid ratio FGLR GGLR WGLR CGLR CGLRL
WGLRL
Gas-liquid ratio (H) FGLRH GGLRH WGLRH
Water-gas ratio WWGR CWGR CWGRL
WWGRL
Water-gas ratio (H) WWGRH
Bottom hole gas-liquid ratio WBGLR

12.18.1. SUMMARY 1479

Keywords for formats tN, E1, E3 19.1

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

Numerical aquifer

Parameter Field Aquifer

Aquifer influx rate FNQR ANQR
Cumulative aquifer influx FNQT ANQT
Aquifer pressure (weighted by water volume) ANQP

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

12.18.1. SUMMARY 1480

Keywords for formats tN, E1, E3 19.1

Well and connection parameters

Parameter Region Well Connection

Well artificial lift quantity (ALQ) WALQ
Well control mode (0 – shut or stopped, 1 – WMCTL
ORAT, 2 – WRAT, 3 – GRAT, 4 – LRAT, 5 –
RESV, 6 – THP, 7 – BHP, 13 – NGL, 31 –
REIN, 32 – TMRA, 33 – WGRA, 34 – CVAL,
41 – STRA, 42 – SATP, 43 – SATT, <0 –
group control)
Well status (1 – producer, 2 – injector, 3 – WSTAT
shut, 4 – stopped)
Productivity Index of well’s preferred phase WPI
Oil phase PI WPIO
Gas phase PI WPIG
Water phase PI WPIW
Efficiency factor GEFF WEFF
Blocking factor for generalized pseudo- CDBF
pressure 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.18.1. SUMMARY 1481

Keywords for formats tN, E1, E3 19.1

Multisegment wells

Parameter Segment
Segment oil flow rate SOFR
Segment free oil flow rate SOFRF
Segment vaporized oil flow rate SOFRS
Segment water flow rate SWFR
Segment gas flow rate SGFR
Segment free gas flow rate SGFRF
Segment liquid flow rate SLPR
Segment oil flow total SOFT
Segment oil absolute flow total SOFTA
Segment water flow total SWFT
Segment water absolute flow total SWFTA
Segment gas flow total SGFT
Segment gas absolute flow total SGFTA
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
(to be continued)

12.18.1. SUMMARY 1482

Keywords for formats tN, E1, E3 19.1

(continued)
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

Parameters for compositional models E3 type

Parameter Field Group Well Connection

Energy injection rate FEIR GEIR WEIR
Energy injection total FEIT GEIT WEIT
Energy production rate FEPR GEPR WEPR
Energy production total FEPT GEPT WEPT
Energy rate WENR
Steam quality WSQU
Well tubing head temperature WTHT
Hydrocarbons molar injection rate FHMIR GHCMIR
Hydrocarbons molar injection total FHMIT GHCMIT
Hydrocarbons molar production rate FHMPR GHCMPR
Hydrocarbons molar production total FHMPT GHCMPT
Hydrocarbon component molar FCMPR GCMPR WCMPR
production rates
Hydrocarbon component molar FCMPT GCMPT WCMPT
production totals
Hydrocarbon component molar rates FCOMR GCOMR WCOMR
in the oil phase
Hydrocarbon component molar rates FCGMR GCGMR WCGMR
in the gas phase
Hydrocarbon component molar totals WCOMT
in the oil phase
(to be continued)

12.18.1. SUMMARY 1483

Keywords for formats tN, E1, E3 19.1

(continued)
Hydrocarbon component molar totals WCGMT
in the gas phase
Liquid mole fraction FXMF GXMF WXMF
Vapor mole fraction FYMF GYMF WYMF
Total mole fraction FZMF GZMF WZMF
Water component molar injection FWMIR GWMIR WWMIR
rates
Water component molar injection FWMIT GWMIT WWMIT
totals
Water component molar production FWMPR GWMPR WWMPR
rates
Water component molar production FWMPT GWMPT WWMPT
totals
Component hydrocarbon as moles FCMIP

General parameters

Parameter Whole model

Date (as DAY, MONTH, YEAR) DATE

12.18.1. SUMMARY 1484

Keywords for formats tN, E1, E3 19.1

12.18.2. RPTONLY

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION x SUMMARY SCHEDULE

This keyword is used to save reporting parameters for wells, groups in binary files in
E1 format at only reporting time steps when the model is calculated by tNavigator console
version. The keyword does not 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 UNRST/UNSMRY
binaries) only at reporting time step (not calculation steps) (regardless of whether the keyword
RPTONLY is present or not). The detailed description of options for recording results of
calculations and corresponding keywords are given in the section 9.1.
Example
RPTONLY

12.18.2. RPTONLY 1485

Keywords for formats tN, E1, E3 19.1

12.18.3. RPTONLYO

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION x SUMMARY x SCHEDULE

This keyword is used to save reporting parameters for wells (groups) in binary files in
UNRST/UNSMRY format at each time steps when the model is calculated by tNavigator con-
sole version. Such conditions of saving results are set in tNavigator by default. This keyword
does not require any parameters after it.

It is recommended to use this keyword if the keyword RPTONLY (see 12.18.2) is defined
in the data file and it is required to turn off its action further in the calculation. For example,
if the size of SUMMARY file is limited, but the detailed data for particular period is required.
The detailed description of options for recording results of calculations and corresponding
keywords are given in the section 9.1.
If keyword RPTONLYO (see 12.18.3) is defined in the SCHEDULE section the results
output setting can change during the calculation. Moreover, the setting will be saved and
the restart calculation will be used setting from a previous calculation. In order to change
restart’s setting the keyword RPTONLY (see 12.18.2) and RPTONLYO (see 12.18.3) should be
defined at or after the restart time. If the keyword RPTONLY (see 12.18.2) and RPTONLYO
(see 12.18.3) are defined in SUMMARY or SCHEDULE sections before the restart time, these
keywords will be ignored.
Example
RPTONLYO

12.18.3. RPTONLYO 1486

Keywords for formats tN, E1, E3 19.1

12.18.4. SEPARATE / RUNSUM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION x SUMMARY SCHEDULE

Keywords SEPARATE and RUNSUM activate export RSM file option for E1 and E3
models respectively.
If console version of tNavigator is used, then one can use option --ecl-rsm to activate
RSM file exporting. The detailed description of options for recording results of calculations
and corresponding keywords are given in the section 9.1.
Description of console version tNavigator – section 8.

Example
SEPARATE

12.18.4. SEPARATE / RUNSUM 1487

Keywords for formats tN, E1, E3 19.1

12.19. Schedule section

SCHEDULE section can be used to specify well’s data and to edit region numbers and some
properties (see section 12.19).
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.19.3). Then well trajectory is defined via WELL-
TRACK (see 12.19.9) and after that perforations are defined via the keyword COMPDATMD
(see 12.19.10).

Data specification in E1/E3 format.

In E1/E3 format well is specified by keyword WELSPECS (see 12.19.3) and its perforated
intervals by keyword COMPDAT (see 12.19.6).

To specify wells in local grid refinement special keywords should be used – section 5.5.8.

In order to set well schedule it is necessary to specify well name (or number) and name of
group it belongs to.
Either a fully qualified well name or a mask with wildcards may be used. In the latter case
the operation desired will be applied to a subset of wells with names matching the mask. In
the well mask along with usual alphanumeric 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 exist);
Mask cannot be used instead of well name for new well introduction, but the only for changing
of work mode of 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.

12.19. Schedule section 1488

Keywords for formats tN, E1, E3 19.1

Well masks and wildcards in ACTION keywords

If any well keyword is indicated after ACTIONX (see 12.19.162) keyword and before EN-
DACTIO (see 12.19.164) keyword, then, instead of explicit well specification, the well name
or well mask with wildcard can be copied from the keyword defining triggering condition. To
do this, the question mark '?' should be input in place of well’s name. See the example below
for explanations:
Example
ACTIONW

ACT 'P*' WLPR < 500 1 /

WELSPECS
'?' 4* OIL /
/

ENDACTIO

In this example:

• The triggering conditions is applied to all wells which name starts with 'P'

• The keyword WELSPECS defines the action that will be implemented if triggering
condition is satisfied.

• The first parameter of WELSPECS is '?', hence the well mask will be copied from the
condition defined above ('P*') and the condition will be applied to the same wells (i.e.
the wells which name starts with 'P').

Edited properties in the SCHEDULE

In the SCHEDULE section it is possible to edit the following region numbers and proper-
ties:

• SATNUM (see 12.4.3), PVTNUM (see 12.4.2), ROCKNUM (see 12.4.14);

• MULTSIGV (see 12.19.142), LANGMULT (see 12.9.4);

• MULTX (see 12.2.15), MULTY (see 12.2.17), MULTZ (see 12.2.19), MULTX-
(see 12.2.16), MULTY- (see 12.2.18), MULTZ- (see 12.2.20);

• PORO (see 12.2.24), NTG (see 12.2.25), PERMX (see 12.2.13), PERMY (see 12.2.13),
PERMZ (see 12.2.13);

• LX (see 12.2.69), LY (see 12.2.69), LZ (see 12.2.69);

• SOIL (see 12.16.16), SWAT (see 12.16.14), SGAS (see 12.16.15).

12.19. Schedule section 1489

Keywords for formats tN, E1, E3 19.1

12.19.1. SCHEDULE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies the beginning of data section which contains well data.

12.19.1. SCHEDULE 1490

Keywords for formats tN, E1, E3 19.1

12.19.2. WELSOMIN

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets minimum oil saturation in a block for automatic opening of well connec-
tions (well working mode AUTO in WCONPROD, see 12.19.42). If the limit WELSOMIN isn’t
reached connections can be opened manually (using the keyword COMPDAT, see 12.19.6).
If the keyword isn’t specified well connections (well working mode AUTO), will be opened
automatically for any block oil saturation.
The data should be terminated with a slash /.
Example
WELSOMIN
0.35 /

12.19.2. WELSOMIN 1491

Keywords for formats tN, E1, E3 19.1

12.19.3. WELSPECS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword introduces a new well, defining information on its name, coordinates and
other technical data. A set of data for every well should be terminated with a slash /. All data
should be terminated with a final slash /.
The following data should be specified:

1. well name (or number),

2. name of the group to which this well belongs;

Default: FIELD.

3. bottom hole or well head coordinates in X direction (IW);

Default: 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.6.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.19.6);
Default: 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.19.6). Otherwise model read error will occur.

5. reference depth for bottom hole pressure.

Recommended location - first perforated interval depth (METRIC: m, FIELD: f t );
Default: first perforated interval depth.

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.19.86) (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 well’s potential flow rate is printed in the well reports instead

12.19.3. WELSPECS 1492

Keywords for formats tN, E1, E3 19.1

of the productivity index. (The well’s potential rate is the flow rate it would achieve in
the absence of any rate constraint, limited only by its BHP and THP constraint);
Default: 0.

8. 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.19.213). 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).
If this option is not defined, STD is assumed.
• Default: STD.

9. well can be automatically shut or stopped if a well or group economic limit or group
flow limit is violated: STOP – stop well above formation, SHUT – isolate well from the
formation;
Default: SHUT.

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;
Default: YES.

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 well’s connection;
Default: 0.

12. type of density calculations for the wellbore hydrostatic head:

• SEG – segmented model of density calculations. This model is supported in tNav-

igator for black-oil models and compositional models, this option can also be used
with BRINE (see 12.1.62) 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 well’s BHP;
Formula for averaged density calculation is in the section 5.6.6;

12.19.3. WELSPECS 1493

Keywords for formats tN, E1, E3 19.1

• Default: SEG (for black-oil and compositional models), AVG (for thermal models).

13. defines the way of retrieving the pressure that will be used in the calculations of the
well rate in reservoir conditions:

• positive value: use the pressure value averaged over the FIP region with this num-
ber;
• 0: use the pressure value averaged over the entire field;
• negative value: use the pressure value averaged over the FIP region where the last
well perforation is located, with "last" being understood according to COMPORD
(see 12.19.31);
• Default: 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.19.3. WELSPECS 1494

Keywords for formats tN, E1, E3 19.1

12.19.4. WELSPECL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword introduces a new well, defining information on its name, coordinates and
other technical data in local grids (LGR) – section 5.5.8.

WELSPECL must be used in place of WELSPECS (see 12.19.3) to set the general specifi-
cation data for wells in local refined grids. The keyword data is similar to that for WELSPECS
(see 12.19.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.19.7) instead of COMPDAT (see 12.19.6).

A set of data for every well should be terminated with a slash /. All data should be
terminated with a final slash /.
The following data should be specified:

1. well name (or number),

2. name of the group to which this well belongs;

Default: FIELD.

3. name of the local refined grid in which the well is located (CARFIN, see 12.2.97),

4. bottom hole or well head coordinates in X direction (IW);

Default: 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.6.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.19.7);
Default: 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.19.7). Otherwise model read error will occur.

6. reference depth for bottom hole pressure.

Recommended location - first perforated interval depth (METRIC: m, FIELD: f t );
Default: first perforated interval depth.

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.19.86) (7-th parameter).

12.19.4. WELSPECL 1495

Keywords for formats tN, E1, E3 19.1

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
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 well’s potential flow rate is printed in the well reports instead
of the productivity index. (The well’s potential rate is the flow rate it would achieve in
the absence of any rate constraint, limited only by its BHP and THP constraint);
Default: 0.

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.19.213). Generalized pseudo-
pressure equation alters both the gas and oil mobilities and takes accounts also of the
effects of condensate dropout;
Default: STD.

10. well can be automatically shut or stopped if a well or group economic limit or group
flow limit is violated: STOP – stop well above formation, SHUT – isolate well from the
formation;
Default: SHUT.

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;
Default: YES.

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 well’s connection;
Default: 0.

13. type of density calculations for the wellbore hydrostatic head:

• SEG – segmented model of density calculations. This model is supported in tNav-

igator 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.

12.19.4. WELSPECL 1496

Keywords for formats tN, E1, E3 19.1

• 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 well’s BHP;
Formula for averaged density calculation is in the section 5.6.6;
• Default: 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.19.4. WELSPECL 1497

Keywords for formats tN, E1, E3 19.1

12.19.5. WELLSPEC

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword can be used in tNavigator, but it is highly recommended to use the keyword
WELSPECS (see 12.19.3) instead of WELLSPEC.

12.19.5. WELLSPEC 1498

Keywords for formats tN, E1, E3 19.1

12.19.6. COMPDAT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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 /.
The following parameters are to be specified:

1. well name (or number);

Default: non specified.

2. perforated interval coordinate in X direction (IW); there is i in 5.6.1;

Default: i is taken from WELSPECS (see 12.19.3) parameter 3 (if that parameter in
WELSPECS is also defaulted, then model read error will occur).

3. perforated interval coordinate in Y direction (JW); there is j in 5.6.1;

Default: j is taken from WELSPECS (see 12.19.3) parameter 4 (if that parameter in
WELSPECS is also defaulted, then model read error will occur).

4. number of layer where this vertical perforated interval starts (layers are numbered top-
down starting from 1). This is number k in 5.6.1;
Default: 1.

5. number of layer where this vertical perforated interval ends. This is number k in 5.6.1;
Default: NZ .

6. completion status:

• OPEN,
• SHUT,
• AUTO – connection is initially closed. It will be opened automatically when an-
other 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;
• Default: OPEN.

7. saturation table number;

Default: tNavigator will use the saturation table number that is specified for block with
connection via SATNUM (see 12.4.3).

12.19.6. COMPDAT 1499

Keywords for formats tN, E1, E3 19.1

8. transmissibility factor (CF - connection 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.6.1;
Default: calculated.

9. well diameter (METRIC: m, FIELD: f t ), value dw in 5.6.2;

Default: dw = 0.3048 m.

10. effective KH (METRIC: mD − m, FIELD: mD − f t ) (permeability x thickness) for each

connection in this interval, (see 5.6.2);
Default: calculated.

11. skin factor, this is value s in 5.6.2;

Default: s = 0.

12. D-factor for non-Darcy flow handling (METRIC: day/sm3 , FIELD: day/Msc f ).

Default: non specified. To specify D-factor for a connection you need to specify it with
negative sign. tNavigator will skip minus sign.
If keyword COMPDAT specifies a D-factor for well – Dwell , then D-factor for ith
connection can be calculated as:

Di = (Dwell ∗ ∑ c f )/c fi
i

where c fi is a connection factor (cf) of ith connection, the sum of connection factors is
calculated over all well connections.
For multilateral well the different logic can be used to specify D-factor value. If the
option DFACTORSCALING of keyword TNAVCTRL (see 12.1.4) is set as ALL, then
for all branches the same value of Dwell specified in the last keyword COMPDAT (if
for each branch separate keyword COMPDAT is specified) will be used in computation.
Thus, specification of the same D-factor for all branches is analogous to specifying the
keyword WDFAC (see 12.19.168) with the same value of D-factor.
If the option DFACTORSCALING of keyword TNAVCTRL (see 12.1.4) is set as
BRANCH, then for each branch the value of D-factor specified for this branch will
be used in computation. Then D-factor for ith connection is calculated as:

Di = (Dbranch ∗ ∑ c f branch )/c fi

i

where Dbranch is the value of branch D-factor, specified in keyword COMPDAT, c fi is

a connection factor (cf) of ith connection, the sum of connection factors is calculated
over all branch connections.

12.19.6. COMPDAT 1500

Keywords for formats tN, E1, E3 19.1

13. direction in which this interval penetrates grid block: X, Y or Z;

Default: Z.

14. effective radius (METRIC: m, FIELD: f t ), this is value ro in 5.6.2;

Default: calculated.

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.
If all connections for a well are in SHUT mode then this well automatically will be
switched to working mode SHUT (WCONPROD (see 12.19.42), WCONINJE, see 12.19.44).
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 ori-
entation 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.19.6. COMPDAT 1501

Keywords for formats tN, E1, E3 19.1

12.19.7. COMPDATL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword defines well completions in local grids – section 5.5.8. 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.19.6) to specify the connec-
tion data for wells in local refined grids, after the wells have been introduced with keyword
WELSPECL (see 12.19.4) (instead of WELSPECS, see 12.19.3). The keyword data for COMP-
DATL (see 12.19.7) is the same as for COMPDAT (see 12.19.6), except for an extra parameter
2 which names the local grid containing the connections specified in the record.

The following parameters are to be specified:

1. well name (or number);

Default: non specified.

2. local grid name (CARFIN, see 12.2.97);

Default: non specified.

3. perforated interval coordinate in X direction (IW); there is i in 5.6.1;

Default: i is taken from WELSPECL (see 12.19.4) parameter 3 (if that parameter in
WELSPECS is also defaulted, then model read error will occur).

4. perforated interval coordinate in Y direction (JW); there is j in 5.6.1;

Default: j is taken from WELSPECL (see 12.19.4) parameter 4 (if that parameter in
WELSPECS is also defaulted, then model read error will occur).

5. number of layer where this vertical perforated interval starts (layers are numbered top-
down starting from 1). This is number k in 5.6.1;
Default: 1.

6. number of layer where this vertical perforated interval ends. This is number k in 5.6.1;
Default: NZ .

7. completion status:

• OPEN,
• SHUT,

12.19.7. COMPDATL 1502

Keywords for formats tN, E1, E3 19.1

• AUTO – connection is initially closed. It will be opened automatically when an-

other 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.
• Default: OPEN.

8. saturation table number (IGNORED, this is an E1/E3 compatibility field);

Default: non specified.

9. transmissibility factor (CF - connection 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.6.1;
Default: calculated.

10. well diameter (METRIC: m, FIELD: f t ), value dw in 5.6.2;

Default: dw = 0.3048 m.

11. effective KH (METRIC: mD − m, FIELD: mD − f t ) (permeability x thickness) for each

connection in this interval, (see 5.6.2);
Default: calculated.

12. skin factor, this is value s in 5.6.2;

Default: s = 0.

13. D-factor for non-Darcy flow handling (METRIC: day/sm3 , FIELD: day/Msc f ).

Default: non specified. To specify D-factor for a connection you need to specify it with
negative sign. tNavigator will skip minus sign.
If keyword COMPDATL specifies a D-factor for well – Dwell , then D-factor for ith
connection can be calculated as:

Di = (Dwell ∗ ∑ c f )/c fi
i

where c fi is a connection factor (cf) of ith connection, the sum of connection factors is
calculated over all well connections.
For multilateral well the different logic can be used to specify D-factor value. If the
option DFACTORSCALING of keyword TNAVCTRL (see 12.1.4) is set as ALL, then for
all branches the same value of Dwell specified in the last keyword COMPDATL (if for
each branch separate keyword COMPDATL is specified) will be used in computation.
Thus, specification of the same D-factor for all branches is analogous to specifying the
keyword WDFAC (see 12.19.168) with the same value of D-factor.

12.19.7. COMPDATL 1503

Keywords for formats tN, E1, E3 19.1

If the option DFACTORSCALING of keyword TNAVCTRL (see 12.1.4) is set as

BRANCH, then for each branch the value of D-factor specified for this branch will
be used in computation. Then D-factor for ith connection is calculated as:

Di = (Dbranch ∗ ∑ c f branch )/c fi

i

where Dbranch is the value of branch D-factor, specified in keyword COMPDATL, c fi

is a connection factor (cf) of ith connection, the sum of connection factors is calculated
over all branch connections.

14. direction in which this interval penetrates grid block: X, Y or Z;

Default: Z.

15. effective radius (METRIC: m, FIELD: f t ), this is value ro in 5.6.2.

Default: calculated.

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.
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 ori-
entation 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.19.7. COMPDATL 1504

Keywords for formats tN, E1, E3 19.1

12.19.8. COMPDATM

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword is an analogue for the keyword COMPDATL (see 12.19.7).

12.19.8. COMPDATM 1505

Keywords for formats tN, E1, E3 19.1

12.19.9. WELLTRACK

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword is used to define well trajectory, including different well branches. The well
should be defined first via the keyword WELSPECS (see 12.19.3). Then well trajectory is de-
fined via WELLTRACK (see 12.19.9) and after that perforations are defined via the keyword
COMPDATMD (see 12.19.10).
This keyword can’t be used inside any of ACTION (see 12.19.158) 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.19.9. WELLTRACK 1506

Keywords for formats tN, E1, E3 19.1

Case 2: There are several well branches.

WELLTRACK keyword should be used to define each branch. The data for each branch should
be terminated with a slash /.

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.19.9. WELLTRACK 1507

Keywords for formats tN, E1, E3 19.1

12.19.10. COMPDATMD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.19.3), and well’s
trajectory using the keyword WELLTRACK (see 12.19.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 can’t be used inside any of ACTION (see 12.19.158) type keywords.

If the perforations defined by COMPDATMD are located in refined grid blocks and the local
grid is disabled by LGROFF (see 12.19.273) keyword, then the perforations will be automat-
ically transferred by the simulator to the blocks of coarse grid. Otherwise, if the perforations
defined by COMPDATMD are located in coarse grid blocs and the local grid is enabled by
LGRON (see 12.19.272) keyword, then the perforations will be automatically transferred by
the simulator to the blocks of local (refined) grid.

If STAGE is set for the 5th parameter, then the perforations will be only active in the
blocks of local grid. In this case, if LGR is disabled, all these perforations will be closed.

This keyword has E1/E3-compatible analogues COMPDAT (see 12.19.6), COMPDATL

(see 12.19.7).

An arbitrary number of data lines can be entered, terminated with a slash /. All data should
be terminated with a final slash /.
The following parameters should be specified in one line:

1. name of the well or hydraulic fracture stage.

• well’s name/number (if MD or TVD is set for the 5th parameter).

• fracture stage name (if STAGE is set for the 5th parameter).
The name and the properties of this stage should be previously specified via the
first parameter of FRACTURE_WELL (see 12.2.128) keyword.

2. branch number.

• well bore branch number (if MD or TVD is set for the 5th parameter).
The branches can be spicified via WELLTRACK (see 12.19.9) keyword.

12.19.10. COMPDATMD 1508

Keywords for formats tN, E1, E3 19.1

Default: 0 (main branch).

• fracture stage number (if STAGE is set for the 5th parameter).
It can be indicated if several fracture stages are initialized via the same FRAC-
TURE_WELL (see 12.2.128) keyword.
Default: COMPDATMD is applied to all stages indicated in FRACTURE_WELL
(see 12.2.128) keyword.

3. lower limit for completion’s depth.

• MDL – lower depth (if MD or TVD is set for the 5th parameter).
(METRIC: m, FIELD: f t );
• The distance to the left from the anchor point of the fracture stage (if STAGE is
set for the 5th parameter).
(METRIC: m, FIELD: f t ).

4. upper limit for completion’s depth.

• MDU – upper depth (if MD or TVD is set for the 5th parameter).
(METRIC: m, FIELD: f t );
Default: bottom depth of the reservoir.
• The distance to the left from the anchor point of the fracture stage (if STAGE is
set for the 5th parameter).
(METRIC: m, FIELD: f t ).

5. indicator of completion depth measurement type:

• MD – indicates that the values of the parameters 3 and 4 represent the Measured
Depth.
• TVD – indicates that the values of the parameters 3 and 4 represent the True Vertical
Depth.
• STAGE – indicates that the well will be perforated at the the anchor point of
the fracture stage (i.e. the connection point of the fracture and the wellbore). The
anchor point is defined via FRACTURE_WELL (see 12.2.128) keyword.
In order to use this parameter, the fracture must be previously enabled via
FRACTURE_STAGE (see 12.19.147) keyword.

Default: MD (measured depth).

6. completion status:

• OPEN,
• SHUT,
Default: OPEN.

12.19.10. COMPDATMD 1509

Keywords for formats tN, E1, E3 19.1

7. saturation table number; this parameter should be defaulted;

Default: tNavigator will use the saturation table number that is specified for block with
connection via SATNUM (see 12.4.3).

8. transmissibility factor (CF - connection factor) (METRIC: cP-rm3 /day-bar , FIELD:

cP-rb/day-psi) this is coefficient T (t) in 5.6.1; this parameter should be defaulted,
tNavigator calculates it automatically;
Default: calculated.

9. well diameter (METRIC: m, FIELD: f t ), value dw in 5.6.2,

Default: dw = 0.3048 m.

10. effective KH (METRIC: mD − m, FIELD: mD − f t ) (permeability x thickness),

(see 5.6.2); this parameter should be defaulted, tNavigator calculates it automati-
cally;
Default: calculated.

11. skin factor, this is value s in 5.6.2,

Default: s = 0.

12. D-factor for non-Darcy flow handling (METRIC: day/sm3 , FIELD: day/Msc f ).
Default: non specified. To specify D-factor for a connection you need to specify it with
negative sign. tNavigator will skip minus sign.
If keyword COMPDATMD specifies a D-factor for well – Dwell , then D-factor for ith
connection can be calculated as:

Di = (Dwell ∗ ∑ c f )/c fi
i

where c fi is a connection factor (cf) of ith connection, the sum of connection factors is
calculated over all well connections.
For multilateral well the different logic can be used to specify D-factor value. If the
option DFACTORSCALING of keyword TNAVCTRL (see 12.1.4) is set as ALL, then for
all branches the same value of Dwell specified in the last keyword COMPDATMD (if for
each branch separate keyword COMPDATMD is specified) will be used in computation.
Thus, specification of the same D-factor for all branches is analogous to specifying the
keyword WDFAC (see 12.19.168) with the same value of D-factor.
If the option DFACTORSCALING of keyword TNAVCTRL (see 12.1.4) is set as
BRANCH, then for each branch the value of D-factor specified for this branch will
be used in computation. Then D-factor for ith connection is calculated as:

Di = (Dbranch ∗ ∑ c f branch )/c fi

i

12.19.10. COMPDATMD 1510

Keywords for formats tN, E1, E3 19.1

where Dbranch is the value of branch D-factor specified in keyword COMPDATMD, c fi

is a connection factor (cf) of ith connection, the sum of connection factors is calculated
over all branch connections.

13. connection factor multiplier;

Default: 1.

14. completion type. This parameter should be used in conjunction with DUALPERM
(see 12.1.84) keyword.

! In the models with double porosity (DUALPORO, see 12.1.83) perfora-

tions are created in fracture blocks only.
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: FRAC.

Example
COMPDATMD
-- wname branch mdu mdl md_type status filt.tbl pi diameter
'PROD' 1* 2438 2469 1* OPEN 2* 0.16 /
/

In this example the well is perforated in the certain interval (from 2438m to 2469m (MD)).

Example
FRACTURE_WELL
'STAGE1' 'PROD' 0 /
'TEMPLATE1' 2453.5 /
/

FRACTURE_STAGE
-- stage_name on/off arithmetic_name
'STAGE1' ON 'ARITHMETIC1' /
/

COMPDATMD
-- wname branch mdu mdl md_type status filt.tbl pi diameter
STAGE1 1* 15.5 15.5 STAGE OPEN 2* 0.16 /
/

12.19.10. COMPDATMD 1511

Keywords for formats tN, E1, E3 19.1

In this example the well’s perforation interval coincides with anchor point of the hydraulic
fracture stage.

12.19.10. COMPDATMD 1512

Keywords for formats tN, E1, E3 19.1

12.19.11. WELSEGS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies the segment structure of a multisegment well (section 2.15). One
keyword can specify only one well. The well should be previously defined via the keyword
WELSPECS (see 12.19.3) (WELSPECL, see 12.19.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 segment’s 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;
Default: 0.0 (m).

4. effective wellbore volume of the top segment (METRIC: m3 , FIELD: f t 3 );

Default: 1.0e-5 (m3 ).

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 well’s
segments:

12.19.11. WELSEGS 1513

Keywords for formats tN, E1, E3 19.1

• HFA – hydrostatic + friction + acceleration (the acceleration pressure drop is calcu-

lated using a homogeneous flow model and is added to the pressure drop calculated
from interpolation of VFP table);
• HF- – hydrostatic + friction;
• H– – hydrostatic;
• Default: HFA.

7. default Multi-phase Flow Model for the well’s segments:

• HO – homogeneous flow (the phases all flow with the same velocity);
• DF – drift flux that allows for slip between phases;
• Default: HO.

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 E1/E3 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 E1/E3 compatibility field.

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.19.11. WELSEGS 1514

Keywords for formats tN, E1, E3 19.1

• 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 range’s 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 ).

6. • if parameter 5 of first data record (for top segment) – INC:

depth change along each segment in the range, that is, the depth of its nodal point
minus the depth of its outlet segment’s nodal point (METRIC: m, FIELD: f t ).
• if parameter 5 of first data record (for top segment) – ABS:
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 range’s 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. segment’s volume (METRIC: m3 , FIELD: f t 3 );

11. • if parameter 5 of first data record (for top segment) – INC:

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 ).
• if parameter 5 of first data record (for top segment) – ABS:
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 range’s outlet seg-
ment ( parameter 4), linearly according to their length down the tubing (METRIC:
m, FIELD: f t ).

12. • if parameter 5 of first data record (for top segment) – INC:

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 ).
• if parameter 5 of first data record (for top segment) – ABS:
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 range’s outlet segment
(parameter 4), linearly according to their length down the tubing (METRIC: m,
FIELD: f t ).

12.19.11. WELSEGS 1515

Keywords for formats tN, E1, E3 19.1

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.19.11. WELSEGS 1516

Keywords for formats tN, E1, E3 19.1

12.19.12. WSEGINIT

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keywords specifies initial conditions in a multisegment well.

This keyword is IGNORED because of specific methods of solution used in tNavigator.

12.19.12. WSEGINIT 1517

Keywords for formats tN, E1, E3 19.1

12.19.13. WSEGLINK

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword defines chord segment links required to occur looped flow paths in mul-
tisegment wells (see section 2.15). If there is a chord segment link between specified well
segments then values of variables (segment pressure and phase flowing fractions for models
in E1 format, segment pressure and molar densities for models in E3 format) at the segment
nodes are equal. One of these segments has to be located at the end of a branch.
Two segments connected by link are called the primary link segment and the secondary
link segment. By default, the first segment specified in the link will be the primary link
segment, the secondary link segment can be only the segment located at the end of a branch.
Before defining chord segment links the segment structure of multisegment well has to
be specified using the WELSEGS (see 12.19.11) keyword. The maximum number of chord
segment links for a particular well can be specified in parameter 4 of the WSEGDIMS
(see 12.1.41) keyword.
The keyword contains any number of records, each record is terminated with a slash /.
The set of records is terminated with a separated slash /.

Each record contains the following data:

1. Well name;

2. Segment number of the first segment in the chord segment link;

3. Segment number of the second segment in the chord segment link.

Note 1: If WSEGLINK is specified several times, every time it appears new chord segment
links will be added to existing list of links. If one of the segment numbers is defaulted then all
the segment links associated with this segment will be deleted. If both segments are defaulted,
then all segment links associated with the well will be deleted.
Note 2: For any multisegment well the friction effects should be included in segment
pressure drop calculation (parameter 6 of keyword WELSEGS, see 12.19.11).
Example
WSEGLINK
PROD 21 27 /
PROD 18 28 /
PROD 19 29 /
PROD 20 30 /
/

12.19.13. WSEGLINK 1518

Keywords for formats tN, E1, E3 19.1

In this example for well PROD 4 chord segment links are specified between the following
segments: 21 – 27, 18 – 28, 19 – 29, 20 – 30.

12.19.13. WSEGLINK 1519

Keywords for formats tN, E1, E3 19.1

12.19.14. WSEGTABL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword defines calculation of segment pressure drop from VFP tables (section 2.15).
Multi-segment well should be entered via the keyword WELSEGS (see 12.19.11), tables
should be entered via VFPPROD (see 12.19.66) (VFPCORR, see 12.19.71).
The data for each well should be terminated with a slash /. All data should be terminated
with a final slash /.
The following parameters should be specified:

1. well name (or number),

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.19.66), VFPCORR, see 12.19.71).
Second parameter of the main data in the keyword VFPPROD (see 12.19.66) 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.
Default: 0, pressure drop is calculated according to homogeneous flow model.

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.

7. way of scaling the interpolated pressure drop for each segment:

12.19.14. WSEGTABL 1520

Keywords for formats tN, E1, E3 19.1

◦ LEN The second entry in the basic data of VFPPROD (see 12.19.66) is interpreted
as the table’s datum length, and the pressure drop is scaled proportionally to the
length of the segment relative to the datum length. This option is suitable for
horizontal segments of the well.
◦ DEP The second entry in the basic data of VFPPROD (see 12.19.66) is interpreted as
the table’s datum depth span, and the pressure drop is scaled proportionally to the
depth span of the segment relative to the datum depth span. This option is suitable
for vertical segments of the well.
◦ NO Pressure drop is not scaled automatically. This option is suitable for a segment
representing a choke.

Default: LEN.

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.19.14. WSEGTABL 1521

Keywords for formats tN, E1, E3 19.1

12.19.15. WSEGVALV

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword specifies calculation of segment pressure drops for sub-critical valve (Multi-
segment well should be specified via the keyword WELSEGS (see 12.19.11), see section
2.15. Multisegment well).
The data for each well should be terminated with a slash /. All data should be terminated
with a final slash /.
The following parameters should be specified:

1. well name (or number), or well list name defined via WLIST (see 12.19.33), or well
mask defining a subset of wells with common prefix (should end with an asterisk *);

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;
Default: according to WELSEGS (see 12.19.11).

6. D – pipe diameter for the friction pressure drop (METRIC: m, FIELD: f t ). This pa-
rameter overrides the 7-th parameter of WELSEGS (see 12.19.11);
Default: 7-th parameter of the keyword WELSEGS (see 12.19.11).

7. absolute roughness of the pipe wall (METRIC: m, FIELD: f t ). This parameter overrides
the 8-th parameter of WELSEGS (see 12.19.11);
Default: 8-th parameter of the keyword WELSEGS (see 12.19.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.19.11);
Default: 9-th parameter of the keyword WELSEGS (see 12.19.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 enabled, it is allowed
for this segment.

12.19.15. WSEGVALV 1522

Keywords for formats tN, E1, E3 19.1

10. Amax – maximum cross-sectional area for flow in the constriction (METRIC: m2 ,
FIELD: f t 2 );
Default: 8-th parameter of this keyword or 9-th parameter of the keyword WELSEGS
(see 12.19.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);
• 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.19.15. WSEGVALV 1523

Keywords for formats tN, E1, E3 19.1

12.19.16. WSEGAICD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword designates specific well segments to represent an autonomous inflow control
device (ICD) in a multisegment well (see section 2.15). 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 · qx−2

• 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 = αoa ρo + αwb ρw + αgc ρg – 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;

f
• µmix = αod µo + αwe µw + αg µg – is the viscosity of the fluid mixture in the segment at
local conditions;

• αo , αw , αg – is the volume fraction of the free oil, water and gas phases at local condi-
tions;

• µo , µw , µg – is the viscosity of the oil, water and gas phases at local conditions;

• a, b, c, d, e, f – are exponents in the formulas for ρmix and µmix .

The following parameters should be specified:

12.19.16. WSEGAICD 1524

Keywords for formats tN, E1, E3 19.1

1. well name, or well list name defined via WLIST (see 12.19.33), or well mask defining
a subset of wells with common prefix (should end with an asterisk *);

2. segment number at the start of the segment range;

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)2 ), FIELD:
psi/((lb/ f t 3 )(r f t 3 /day)2 ));

5. the length of the ICD, lICD (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 a description of the parameter 11).
If parameter 11 is defaulted and the length of the ICD is positive, then the flow scaling
factor is equal to the ratio of the ICD length to the length of the encased tubing segment,
and if lICD is negative then the flow scaling factor is equal to the absolute value of length
lICD ;
Default: METRIC: 12m, FIELD: 39.37 f t .

6. the density of the calibration fluid (METRIC: kg/m3 , FIELD: lb/ f t 3 );

Default: METRIC: 1000.25kg/m3 , FIELD: 62.416lb/ f t 3 .

7. the viscosity of the calibration fluid (METRIC: cP, FIELD: cP);

Default: 1.45 cP.

8. critical value of the local water in liquid fraction. IGNORED, this is an E1/E3 compati-
bility field;

9. width of the transition region in the vicinity of the critical value of the local water in
liquid fraction (see parameter 8). IGNORED, this is an E1/E3 compatibility field;

10. maximum permitted value of the ratio of the emulsion viscosity to continuous phase
viscosity. IGNORED, this is an E1/E3 compatibility field;

11. parameter determining how the flow scaling factor is calculated:

• 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;

12.19.16. WSEGAICD 1525

Keywords for formats tN, E1, E3 19.1

• 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 parameter 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 parameter 5 is negative then the flow scaling factor is equal to the absolute
value of ICD length;
• Default: -1.

12. maximum absolute value of qICD for which equation of pressure drop holds. IGNORED,
this is an E1/E3 compatibility field;

13. volume flow rate exponent;

14. viscosity function exponent;

15. flag indicating whether 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;
• Default: OPEN.

16. exponent of the oil flowing fraction in the formula for calculating ρmix ;
Default: 1.

17. exponent of the water flowing fraction in the formula for calculating ρmix ;
Default: 1.

18. exponent of the gas flowing fraction in the formula for calculating ρmix ;
Default: 1.

19. exponent of the oil flowing fraction in the formula for calculating µmix ;
Default: 1.

20. exponent of the water flowing fraction in the formula for calculating µmix ;
Default: 1.

21. exponent of the gas flowing fraction in the formula for calculating µmix .
Default: 1.

Each data line should be ended by a symbol /. The data should be terminated with a slash
/.
Note: The emulsion viscosity model is the default model for the keyword WSEGSICD
(see 12.19.17).

12.19.16. WSEGAICD 1526

Keywords for formats tN, E1, E3 19.1

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.19.16. WSEGAICD 1527

Keywords for formats tN, E1, E3 19.1

12.19.17. WSEGSICD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword assigns selected well segments as a spiral inflow control device (ICD) in a
multisegment well (the description of multisegment well is given in the section 2.15).
This type of device controls the inflow profile along a horizontal well or branch by im-
posing an additional pressure drop between the sand face and the tubing. The device located
around a section of the tubing redirect the fluid inflowing from the formation into the tubing.
Before entering the tubing the fluid passes through a sand screen and then into a spiral.
The pressure drop across the device is calculated using calibration data, adapted such as
density and viscosity of the reservoir fluid flowing through the device vary in the wide range:
   1
ρcal µmix 4
δP = · · ρmix · K · q2 ,
ρmix µcal
where:
• ρmix – the density of the fluid mixture in the segment at local conditions. The density
of the fluid mixture is calculated as: ρmix = αo ρo + αw ρw + αg ρg ,
where:

– αo,w,g – the volume fraction of the free oil, water, gas phases at local conditions;
– ρo,w,g – the density of the oil, water, gas phases at local conditions.

• ρcal – the density of the fluid used to calibrate the ICD (see parameter 6);

• µmix – the viscosity of the fluid mixture in the segment at local conditions. The viscosity
is calculated as: µmix = (αo + αw )µemul + αg µg ,
where:

– µemul – the viscosity of the oil – water emulsion at local conditions (see section
Emulsion viscosity);
– µg – the viscosity of gas at local conditions.

• µcal – the viscosity of the fluid used to calibrate the ICD (see parameter 7);

• K – the base strength of the ICD, with dimension of inverse area squared, defined as:
aSICD
K=
ρcal

• aSICD – the strength of the SICD (see parameter 4);

12.19.17. WSEGSICD 1528

Keywords for formats tN, E1, E3 19.1

• q – the volume flow rate of fluid mixture through the ICD at local conditions. It is
equal to the volume flow rate through the ICD segment multiplied by a scaling factor
depending on the length of the device (see parameter 5).

For multisegment well a series of devices (ICD) can be used. In this case the devices
should be represented by segments branching off the tubing. The grid block connections will
be located in the ICD segments instead of the well tubing segments.
The ICD segments are introduced in the normal way using keyword WELSEGS
(see 12.19.11), then defined as ICD segments with keyword WSEGSICD. The length of
ICD segments specified in the keyword WELSEGS (see 12.19.11) should be small, e.g.,
of the order of the wellbore radius. The length only affects the location of the connections in
COMPSEGS (see 12.19.27) or COMPSEGL (see 12.19.28) and is not used in pressure drop
calculation. The depth of ICD segments is equal to the depth of their ”parent” tubing seg-
ments in order to hydrostatic head does not occur across them. The pressure loss across an
ICD segment is reported as the friction pressure loss; the acceleration pressure loss is set to
zero.
When creating complicated configuration of ICD segment in keyword WSEGSICD up-
stream segments (located further from the wellhead) should be specified before downstream
segments
This keyword is followed by a set of data records, containing the following parameters.
Unless otherwise stated, entering a negative value for a parameter defaults it. Each record is
terminated with a slash /. The set of records is terminated with separated slash /.

1. well name, or well list name defined via WLIST (see 12.19.33), or well mask defining
a subset of wells with common prefix (should end with an asterisk *);

2. segment number at the start of the segment range. Integer;

3. segment number at the end of the segment range. Integer number should be larger than
the number indicated in the parameter 2. All segments in this range are assumed to be
ICD segments. The below described data parameters will be implemented to them. To
enter data for a single segment, set parameter 2 and 3 equal to each other;

4. strength of the SICD, aSICD . This is an empirical constant based on measurements

of the calibrating fluid flow through a particular type of ICD device (METRIC:
bars/(rm3 /day)2 , FIELD: psi/(r f t 3 /day)2 );

5. length of the ICD, lICD (METRIC: m, FIELD: f t ). This parameter (together with
parameter 11) is used to define a scaling factor used to scale the flow from the reservoir
in order to establish the flow qICD through each ICD (see section Flow scaling). To
calculate a scaling factor 3 possibilities (see parameter 11) can be used;
Default: METRIC: 12m, FIELD: 39.37 f t .

6. density of the calibration fluid (METRIC: kg/m3 , FIELD: lb/ f t 3 );

Default: METRIC: 1000.25kg/m3 , FIELD: 62.416lb/ f t 3 .

12.19.17. WSEGSICD 1529

Keywords for formats tN, E1, E3 19.1

7. viscosity of the calibration fluid (METRIC: cP, FIELD: cP);

Default: 1.45 cP.

8. critical value of the local water in liquid fraction used to select between a water-in-oil
or oil-in-water equation for the calculation of emulsion viscosity (see section Emulsion
viscosity);
Default: 0.5.

9. width of the transition region in the vicinity of the critical value of the local water
in liquid fraction (see parameter 8). For water in liquid fractions within this region,
the emulsion viscosity is a linear interpolation between the water-in-oil and oil-in-water
viscosity values defined at sides of the region. This transition region is required to ensure
continuity of viscosity as function of water in liquid fraction (see section Emulsion
viscosity);
Default: 0.05.

10. maximum permitted value of the ratio of the emulsion viscosity to continuous phase
viscosity. This restriction affects the water-in-oil viscosity resulting in emulsion vis-
cosity becomes constant reaching its maximum permitted value (see section Emulsion
viscosity);
Default: 5.

11. parameter determining how the flow scaling factor is calculated:

• 0 – the flow scaling factor is equal to the ratio between ICD length lICD (pa-
rameter 5) and the length of the ”parent” tubing segment taken from the keyword
WELSEGS (see 12.19.11);
• 1 – the flow scaling factor is equal to the absolute value of ICD length lICD
(parameter 5);
• 2 – the flow scaling factor is equal to the ratio between ICD length lICD (parameter
5) and the total length of all completions supplying the ICD;
• Default: -1.

If the value of this parameter is set to a negative value and parameter 5 is a positive
value then the flow scaling factor is equal to the ICD length divided by the length of
the encased tubing segment; and if parameter 5 is negative then the flow scaling factor
is the absolute value of length lICD (parameter 5).

12. maximum absolute value of flow–rate trough the device qICD (METRIC: m3 /day,
FIELD: f t 3 /day) for which equation for δ P calculation holds. IGNORED, this is
an E1/E3 compatibility field;

13. flag indicating whether the device is open or shut:

12.19.17. WSEGSICD 1530

Keywords for formats tN, E1, E3 19.1

• OPEN – ICD is open and there is flow through the device;

• SHUT – ICD is shut and there is flow through the device;
• Default: OPEN.

Each data record is terminated with symbol /. The set of data records is terminated with
symbol /.
Example
WSEGSICD
PROD 18 18 0.0002 2 5* 1 1* /
PROD 19 19 0.0002 2 5* 1 1* /
PROD 20 20 0.0002 2 5* 1 1* /
PROD 21 21 0.0002 2 5* 1 1* /
PROD 22 22 0.0002 2 5* 1 1* /
/
In this example PROD well segments from 18 to 22 represent spiral inflow control device.

Emulsion viscosity
The emulsion viscosity is a function of the local phase volume fractions in the segment and
calculated using different formulas at low water in liquid fractions (when oil is the continuous
phase) and at high water in liquid fractions (when water is the continuous phase).
A critical water in liquid fraction (see parameter 8) is used to select between these formulas
given below:
!2.5
1
µwio = µo ·
1 − 0.8415


0.7480 · αwl
!2.5
1
µoiw = µw ·
1 − 0.6019


0.6410 · α ol

where

• µwio – water-in-oil emulsion viscosity (when oil is the continuous phase);

• µoiw – oil-in-water emulsion viscosity (when water is the continuous phase);

• µo – oil viscosity at local conditions;

• µw – water viscosity at local conditions;

• αwl = αw /(αw + αo ) – local water in liquid fraction;

• αol = αo /(αw + αo ) – local oil in liquid fraction.

12.19.17. WSEGSICD 1531

Keywords for formats tN, E1, E3 19.1

The water-in-oil viscosity has an upper limit equal to a maximum ratio between water-
in-oil viscosity and oil viscosity (see parameter 10). This usually results in appearance of
”plateau” region. In this region the water-in-oil viscosity is at its maximum permitted value.
The upper limit can also apply to the oil-in-water viscosity, but is not generally used.
At the critical water in liquid fraction there is a jump in emulsion viscosity when the
continuous phase changes. This discontinuity can cause stability problems in the simulator. In
order to avoid such behavior a transition region is defined in the vicinity of the critical water
in liquid fraction. Within this region the emulsion viscosity is linearly interpolated between
the water-in-oil and oil-in-water viscosities at the edges of the region; Thus, the viscosity is
a continuous function of the water in liquid fraction. The width of the transition region is
specified in the parameter 9.
To calculate the emulsion viscosity for a given local water in liquid fraction the following
rules should be used:

• If local water in liquid fractions is below the critical value and is outside the transition
region then the emulsion viscosity is the water-in-oil viscosity and calculated using the
formula for µwio . The viscosity is subjected to a maximum permitted viscosity ratio
specified by parameter 10;

• If local water in liquid fractions is within the transition region then the emulsion viscos-
ity is a linear interpolation between the water-in-oil viscosity and oil-in-water viscosities
calculated at the edges of the region;

• If local water in liquid fractions is above the critical value and is outside the transition
region then the emulsion viscosity is the oil-in-water viscosity and calculated using the
formula for µoiw . The viscosity can subjected to a maximum permitted viscosity ratio
specified by parameter 10.

Flow scaling
ICD segment can be consist of a series of ICDs in parallel. In this case the flow rate passing
through each ICD is equal to the flow rate through the segment divided by the number of
ICDs in the segment.
To estimate the number of parallel ICD devices in the ICD segment, the length of a single
ICD is compared with the length of the tubing segment that the devices encase.
Thus the segment flow is scaled as follows:
lICD
qICD = qseg ×
lcomp

where

• qICD – scaled volume flow rate to be used in the above equation for pressure drop
calculation ∆P;

• qseg – volume flow rate from the reservoir into the ICD segment;

12.19.17. WSEGSICD 1532

Keywords for formats tN, E1, E3 19.1

• lseg – length of an actual ICD device (see parameter 5);

• lcomp – length of the ”parent” tubing segment (keyword WELSEGS, see 12.19.11).

The above mentioned equation for flow scaling is also used if the tubing segment length
is smaller than the ICD length. If the tubing segment length is not an exact multiple of the
ICD length then the non-integer scaling factor will be used.
The number of parallel ICDs in the ICD segment can be estimated by comparing the
length of the ICD with the total length of all completions supplying fluid in it. The
length of all completions on the ICD segment and on any upstream segment (including
branches) are included in the calculation of total length. If other devices created by key-
words WSEGSICD (see 12.19.17), WSEGFLIM (see 12.19.19), WSEGVALV (see 12.19.15),
WSEGAICD (see 12.19.16), WSEGTABL (see 12.19.14) exist on upstream segments, only
completions located before these devices are included in calculation.
Thus the segment flow is scaled as follows:
lICD
qICD = qseg ×
lcomp

where

• qICD – scaled volume flow rate to be used in the above equation for pressure drop
calculation ∆P;

• qseg – volume flow rate from the reservoir into the ICD segment;

• lseg – length of an actual ICD device (see parameter 5);

• lcomp – total length of all completions upstream of the ICD feeding the fluid into it.

For more complicated conditions, the scaling calculations above may not be appropriate. In
such case the scaling factor can be specified by parameter 5 (either by setting both parameters
5 and 11 to negative values or setting parameter 11 to 1). Specified value will not be considered
as the ICD length, but this value directly multiplies the segment flow rate qseg to calculate
the flow rate qICD used in the pressure drop ∆P calculation.
Note 1: A segment can only represent a single device. Other previously generated de-
vices (using keywords WSEGFLIM (see 12.19.19), WSEGPULL (see 12.19.23), WSEGVALV
(see 12.19.15) and WSEGAICD, see 12.19.16) will be replaced.
Note 2: Because the device pressure drop is taken into account via the segment’s friction
pressure drop, friction effects must be included for multisegment well for which keyword
WSEGSICD is specified (see parameter 6 of WELSEGS, see 12.19.11).

12.19.17. WSEGSICD 1533

Keywords for formats tN, E1, E3 19.1

12.19.18. WSEGEXSS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword imports or removes fluids to or from a segment in a multisegment well.

Keywords to specify parameters of multisegment well are given in the section 2.15. 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 /.
The following parameters should be specified:

1. well name, or well list name defined via WLIST (see 12.19.33);

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;
• Default: NONE.

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 speci-
fied (METRIC: sm3 /day, FIELD: Msc f /day);
• if the 3rd parameter is WIMPP, then limit on water rate should be specified (MET-
RIC: sm3 /day, FIELD: stb/day);
• if the 3rd parameter is GIMPP, then limit on water rate should be specified (MET-
RIC: sm3 /day, FIELD: Msc f /day);
• Default:
– WIMPR – 0;
– GIMPR – 0;
– WIMPP – no limit;

12.19.18. WSEGEXSS 1534

Keywords for formats tN, E1, E3 19.1

– GIMPP – no limit

5. rate of fluid to add per unit of pressure difference (only with WIMPP or GIMPP op-
tions) (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

• 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).

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.19.18. WSEGEXSS 1535

Keywords for formats tN, E1, E3 19.1

12.19.19. WSEGFLIM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword defines segment of multisegment well as a flow limiting valve. Keywords to
specify parameters of multisegment well are given in the section 2.15.
Limiting valve is simulated as a device that limits the flow rate of fluid (at surface condi-
tions) 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 /.
The data should be terminated with a slash /.

One data line should contain:

1. well name, or well list name defined via WLIST (see 12.19.33), or well mask defining
a subset of wells with common prefix (should end with an asterisk *);

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.19.19. WSEGFLIM 1536

Keywords for formats tN, E1, E3 19.1

• LIQ – liquid total at surface conditions;

• NONE – flow is not limited;
• Default: NONE.

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;
• Default: NONE.

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.

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.19.19. WSEGFLIM 1537

Keywords for formats tN, E1, E3 19.1

12.19.20. WSEGFMOD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies a multiphase flow model used to calculate the pressure losses within
segments of a multisegment well. Keywords to specify parameters of multisegment well are
given in the section 2.15. The following models can be used:

• no-slip homogeneous flow model. In this model all the phases flow with the same
velocity;

• a drift flux model. In this model there is a slip between the phases, which can result
in countercurrent flow, i.e. at low flow rates heavy and light phases flow in opposite
directions.

Moreover, pressure losses in individual segments can be obtained from a VFP table (see
keyword WSEGTABL, see 12.19.14) or calculated using a model of a flow control device
(WSEGVALV (see 12.19.15), WSEGFLIM, see 12.19.19).
For segments, in which a flow model is not specified in keyword WSEGFMOD,
WSEGTABL (see 12.19.14), WSEGVALV (see 12.19.15) or WSEGFLIM (see 12.19.19) the
flow model set in parameter 7 of keyword WELSEGS (see 12.19.11) will be used.
This keyword is followed by a set of data records, containing the following parameters.
Each record is terminated with a slash /. The set of records is terminated with separated slash
/.

1. well name, or well list name defined via WLIST (see 12.19.33), or well name template
(or well list template enclosed in quotes and starting with an asterisk *);

2. segment number at the start of the segment range. Integer;

3. segment number at the end of the segment range. Integer number should be larger than
the number indicated in the parameter 2. The below described data parameters will be
implemented to the segments in the selected range. To enter data for a single segment,
set parameter 2 and 3 equal to each other;

4. multiphase flow model used for pressure drop calculations:

• HO – no-slip homogeneous flow model (all the phases flow with the same veloc-
ity);

12.19.20. WSEGFMOD 1538

Keywords for formats tN, E1, E3 19.1

• DF – drift flux model (phases flows with deferent velocity). Slip between the
phases is a combination of profile slip (a velocity ratio) and local slip (a vertical
relative velocity). When flow rates are low the local slip can cause countercurrent
flow. In this case the heavy and light phases flow in opposite directions;
• Default: HO.

If for any segment the drift flux model is specified then the well’s flow model set in
parameter 7 of keyword WELSEGS (see 12.19.11) should be the drift flux model (DF)
as well.

5. multiplying factor for the gas-liquid drift velocity (drift flux model only).
The drift velocity is calculated as for a vertical pipe, then automatically scaled accord-
ing to the segment’s inclination (see section 2.15.11). This multiplying factor will be
implemented to the scaled local slip velocity. A value of 0.0 turns off the local slip.
The oil-water drift velocity multiplier is set for all segments in parameter 7 of keyword
WSEGDFPA (see 12.19.21);
Default: parameter 1 of keyword WSEGDFPA (see 12.19.21).

6. coefficient A for the gas-liquid profile parameter (drift flux model only).

The value of the profile parameter at low values of the gas holdup fraction and flow
velocity is calculated as (see section 2.15.11):
A
C0 =
(1 + (A − 1)β ∗2 )

If coefficient A is equal to 1, then there is no a profile slip. A should be higher than 1;

Default: 1.2 or parameter 4 of keyword WSEGDFPA (see 12.19.21).

7. coefficient B for the gas-liquid profile parameter (drift flux model only).
The coefficient B defines the value of the gas holdup fraction or the flooding velocity
fraction above which the profile parameter starts to decrease.

β −B
β∗ = , 0 ≤ β∗ ≤ 1
1−B
where  
αg | j|
β = max αg , Fv
vsg f
Coefficients A and B obey the following relation:

B ≤ (2 − A)/A

Default: 0.3 or parameter 5 of keyword WSEGDFPA (see 12.19.21).

12.19.20. WSEGFMOD 1539

Keywords for formats tN, E1, E3 19.1

8. multiplier Fv of the flooding velocity fraction in the profile reduction term β in the gas-
liquid profile parameter C0 (drift flux model only). A multiplier value of 1.0 decreases
the profile parameter to 1.0 when the gas superficial velocity reaches the flooding ve-
locity. When a value equal to 0 means that the profile parameter is independent of the
flow velocity;
Default: 1.0 or parameter 6 of keyword WSEGDFPA (see 12.19.21).

9. coefficient B1 for the oil-water profile parameter C00 (see section 2.15.12) (drift flux
model only);

C00 = A αol ≤ B1
C00 = 1 αol ≤ B2
 
0 αol − B1
C0 = A − (A − 1) B1 < αol < B2
B2 − B1
A value of A set in 6 parameter of this keyword.
Default: 0.4 or parameter 9 of keyword WSEGDFPA (see 12.19.21).

10. coefficient B2 for the oil-water profile parameter (drift flux model only). Coefficients
B1 and B2 should obey the relation B1 ≤ (2 − A)B2
Default: 0.7 or parameter 10 of keyword WSEGDFPA (see 12.19.21).

Note: If this keyword is applied to a segment that has previously been declared as a flow
limiting valve ( WSEGFLIM, see 12.19.19), a sub-critical valve (WSEGVALV, see 12.19.15) or
VFP table (WSEGTABL, see 12.19.14) its former characteristics will be destroyed and it will
become a standard segment, in which homogeneous or the drift flux flow model (according
to parameter 4) will be used.
In the first (top) segment the homogeneous flow model is always specified. There are no
pressure losses calculated along this segment.
Example
WSEGFMOD
PROD 55 69 HO /
/

12.19.20. WSEGFMOD 1540

Keywords for formats tN, E1, E3 19.1

12.19.21. WSEGDFPA

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword is used to modify the parameters that control the drift flux slip model in
multisegment wells. Keywords to specify parameters of multisegment well are given in the
section 2.15.
The keyword is followed by a data record consisting of the following parameters and
terminated with a slash (/).

1. multiplying factor for the gas-liquid drift velocity vd .

First, the drift velocity is calculated for a vertical pipe, then scaled automatically ac-
cording to the segment’s inclination (see section 2.15.11). This factor is applied to the
scaled drift velocity.
If factor is equal to 0.0 there is no the local slip between gas and liquid;
Default: 1.0.

2. parameter a1 in the expression for the gas-liquid drift velocity coefficient K(ag ).
The parameter defines the start of the transition between the two expressions for K(ag )
(see section 2.15.11);
Default: 0.2.

3. parameter a2 in the expression for the gas-liquid drift velocity coefficient K(ag ).
The parameter defines the end of the transition between the two expressions for K(ag )
(see section 2.15.11);
Default: 0.4.

4. coefficient A for the gas-liquid profile parameter.

The value of the gas-liquid profile parameter at low values of the gas holdup fraction
and flow velocity is calculated as (see section 2.15.11):
A
C0 =
(1 + (A − 1)β ∗2 )

If coefficient A is equal to 1, then there is no the profile slip. A should be higher than
1.
Default: 1.2.

12.19.21. WSEGDFPA 1541

Keywords for formats tN, E1, E3 19.1

5. coefficient B for the gas-liquid profile parameter.

The coefficient B defines the value of the gas holdup fraction or the flooding velocity
fraction above which the profile parameter starts to decrease.
β −B
β∗ = , 0 ≤ β∗ ≤ 1
1−B
where  
αg | j|
β = max αg , Fv
vsg f
Coefficients A and B obey the following relation:

B ≤ (2 − A)/A

Default: 0.3.

6. multiplier Fv of the flooding velocity fraction in the profile reduction term β in the
gas-liquid profile parameter C0 . A multiplier value of 1.0 decreases the profile parame-
ter to 1.0 when the gas superficial velocity reaches the flooding velocity. When a value
equal to 0 means that the profile parameter is independent of the flow velocity.

Default: 1.0.

7. multiplying factor for the oil-water drift velocity v0d .

The drift velocity is calculated as for a vertical pipe, then automatically scaled according
to the segment’s inclination (see section 2.15.12). This multiplying factor will be imple-
mented to the scaled local slip velocity. A value of 0 turns off the local slip between oil
and water.
If a negative value is specified, then the multiplier for the oil-water drift velocity is
equal to the value of multiplier for the gas-liquid drift velocity set in parameter 1 of this
keyword.
Default: negative value (implies the same value as in parameter 1).

8. coefficient A for the oil-water profile parameter C00 (see section 2.15.12);

C00 = A αol ≤ B1

C00 = 1 αol ≤ B2
 
0 αol − B1
C0 = A − (A − 1) B1 < αol < B2
B2 − B1
Default: 1.2.

9. coefficient B1 for the oil-water profile parameter C00 .

Default: 0.4.

12.19.21. WSEGDFPA 1542

Keywords for formats tN, E1, E3 19.1

10. coefficient B2 for the oil-water profile parameter C00 .

CoefficientB1 and B2 must obey the relation: B1 ≤ (2 − A)B2 ;
Default: 0.7.

11. exponent n0 in the expression for the oil-water drift velocity v0d :
0
v0d = 1.53v0c (1 − αol )n

Default: 2.0.

Example
WSEGDFPA
0.045 0 0.2 1.7 0.1 1* 1* 1* 0.2 /

12.19.21. WSEGDFPA 1543

Keywords for formats tN, E1, E3 19.1

12.19.22. WSEGSEP

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword defines a segment of a multisegment well as a down-hole separator. Key-

words to specify parameters of multisegment well are summarized in the section 2.15.
A down-hole separator is a device that can separate water or gas from the fluid within a
multisegment well and send it via a lateral branch to be reinjected into the reservoir.
The segment must have three segments connected to it:

• An inlet segment via which the stream enters the separator;

• An offtake segment via which the separated water or gas are sent to the lateral branch;

• An outlet segment via which the remaining fluid flows to the wellhead.

Any number of data lines can be specified. Each data line should be terminated with the
symbol /. All data should be terminated with a final slash /.
One data line should contain:

1. well name, or well list name defined via WLIST (see 12.19.33), or well mask defining
a subset of wells with common prefix (should end with an asterisk *). The well should
be defined as having multisegment structure by the keyword WELSEGS (see 12.19.11);

2. segment number of the down-hole separator (integer not less than 2);

3. segment number of the separator offtake (integer not less than 2). This segment must be
located on a lateral branch and connected to the separator segment;

4. the phase that is preferentially removed by the separator and sent to the offtake:

• WAT – the separator removes water;

• GAS – the separator removes free gas (at local pressure);
• NONE – there is no separation;
• Default: NONE.

5. the maximum separation efficiency for the offtake, Emax . A number between 0.0 and
1.0. Defines the fraction of the preferentially removed phase in the offtake as long as the
fraction of this phase within the remaining mixture exceeds the limiting holdup fraction
specified by parameter 6 (see below);
Default: 1.0.

12.19.22. WSEGSEP 1544

Keywords for formats tN, E1, E3 19.1

6. the limiting holdup fraction, αlim . A number between 0.0 and 1.0. Defines the threshold
below which the separation efficiency decreases linearly towards zero (see below);
Default: 0.01.

The fraction of the preferentially removed phase in the offtake is:


E
max if αsep > αlim
αo f f =
Emax · (αsep /αlim ) otherwise


Example
WSEGSEP
P1 5 15 'WAT' 1.0 0.05 /
/
In this example, a separator is set up on the segment 5 of the well P1. It separates water
and removes it to segment 15.

12.19.22. WSEGSEP 1545

Keywords for formats tN, E1, E3 19.1

12.19.23. WSEGPULL

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword defines segment of multisegment well as a pull through pump for a down-
hole separator. Keywords to specify parameters of multisegment well are given in the section
2.15. A pull through pump can be implemented to control the rate of water removal from
the separator and water reinjection into the formation. The pump should be located in the
water offtake segment of the separator (parameter 3 of keyword WSEGSEP, see 12.19.22) or
anywhere further along the water injection branch.
The pressure drop across the device is calculated as:

δ P = δ Ppump − δ Preduc

where δ Ppump is the the pressure boost from a pump working at a specific net power and
specified as:  
Powmax
δ Ppump = min Cu , δ Pmax
V
• Cu is a units conversion constant;

– power METRIC: 864.0 kW , FIELD: 3.301 × 105 hp;

– flow rate METRIC: 864.0 m3 /day, FIELD: 3.301 × 105 f t 3 /day;
– pressure METRIC: 864.0 bar , FIELD: 3.301 × 105 psi.

• Powmax is the maximum net power of the pump (parameter 3);

• V is the local volumetric fluid rate through the pump;

• δ Pmax is a maximum pressure boost (parameter 4).

If the pump power is extremely low, the water flow rate along the offtake branch may not
correspond to the water flow from the formation into the separator. In this case the excess
water remains in the production flow stream going to the surface. On the other hand, if the
pump power is extremely high the fluid flow along the offtake branch may exceed the water
flow from the formation into the separator. In this case the flow in the outlet branch also
includes an amount of oil from the formation. This amount will be reinjected along with the
water. To optimize separation process, the flow in the outlet branch should be maintained
equal to the inflow of water into the separator. The pressure reduction term δ Preduc is used to
reduce the pump pressure boost when an excessive amount of oil is carried over into the water

12.19.23. WSEGPULL 1546

Keywords for formats tN, E1, E3 19.1

injection stream. This term reduces the pressure boost by an amount that grows extremely
with the excess oil flow rate in the water outlet branch:

δ Preduc = F(Q0 − Q0lim ) Q0 > Q0lim

where
• F is a gradient factor (6 parameter);

• Q0 is the flow rate of oil through the device (from the water outlet of the separator);

• Q0lim is the oil rate limit that triggers the pressure reduction (5 parameter).
To achieve optimum separation maximum pressure boost and the pump power should be
large enough to reinject all the produced water and the gradient factor (6 parameter) should
be set to a value that allows δ Preduc to balance δ Ppump over an acceptable range of oil carry-
over rates. A large gradient factor may prevent the convergence of the multisegment well; It
is recommended to use WSEGITER (see 12.19.133) to assist the convergence.
This keyword is followed by a set of data records, containing the following parameters.
Each record is terminated with a slash /. The set of records is terminated with separated slash
/.

1. well name, or well list name defined via WLIST (see 12.19.33), or well mask defining
a subset of wells with common prefix (should end with an asterisk *);

2. segment number containing the pullthrough pump. An integer (≥ 2).

The pump should be located in the water offtake segment of the separator (parameter
3 of keyword WSEGSEP, see 12.19.22) or anywhere further along the water injection
branch;

3. maximum pump power (METRIC: kW , FIELD: hp);

4. maximum pressure boost, δ Pmax , (METRIC: bars, FIELD: psi);

5. limiting oil rate from the water offtake through the pump, Q0lim , (METRIC: m3 /day,
FIELD: stb/day);
Default: 0.0.

6. gradient factor (for the pressure reduction term), F ;

Default: 0.0.

Note: A segment can only represent a single device. Other previously generated de-
vices (using keywords WSEGFLIM (see 12.19.19), WSEGSICD (see 12.19.17), WSEGVALV
(see 12.19.15) and WSEGAICD, see 12.19.16) will be replaced.

In this example, for 13 segment of well PROD a pullthrough pump for a down–hole
separator is specified. The maximum pump power is 10 kW and maximum pressure boost is

12.19.23. WSEGPULL 1547

Keywords for formats tN, E1, E3 19.1

300 bar . A limiting oil rate from the water offtake through the pump is 0. A gradient factor
F equals 4.
Example
WSEGPULL
PROD 13 10 300 0.0 4 /
/

12.19.23. WSEGPULL 1548

Keywords for formats tN, E1, E3 19.1

12.19.24. WFRICTN

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies a friction well. tNavigator will calculate for this well the frictional
pressure losses between the connections and the well’s 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.15).
One keyword can specify only one well. Well’s geometry should be previously defined via
the keyword COMPDAT (see 12.19.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 termi-
nated with a final /.

First data record:

1. well name (or well number);

2. tubing internal diameter (METRIC: m, FIELD: f t ). This parameter is used to calculate

the frictional pressure drop between the connections and the well’s bottom hole reference
point (it can be not equal to the 9-th parameter of COMPDAT (see 12.19.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: 1.

Second and other data records describe connections.

For horizontal well: each connection should be entered in the keyword just once, (individu-
ally 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.19.6).

Second and other data records:

12.19.24. WFRICTN 1549

Keywords for formats tN, E1, E3 19.1

1. I-coordinate of one connection (or I-coordinate of the connection at the start of the range
(nearest the well’s bottom hole reference point));

2. J-coordinate of one connection (or J-coordinate of the connection at the start of the
range (nearest the well’s bottom hole reference point));

3. K-coordinate of one connection (or K-coordinate of the connection at the start of the
range (nearest the well’s bottom hole reference point));

4. distance down the tubing from the well’s bottom hole reference point to the start of the
perforations in the grid block, specified via parameters 1-3 (METRIC: m, FIELD: f t );
Default: For the first data line – 0, for next data lines – the distance to the end of the
previous connection or range.

5. distance down the tubing from the well’s bottom hole reference point to the end of the
perforations in the grid block, specified via parameters 1-3 (METRIC: m, FIELD: f t );
Default: The sum of value of parameter 4 and the thickness of the grid block in the
direction of penetration, specified via parameter 6.

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: 2-nd parameter in the first data record.

12.19.24. WFRICTN 1550

Keywords for formats tN, E1, E3 19.1

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 well’s bottom
hole reference point to the start (and end) of the perforations in the grid block is defaulted.

12.19.24. WFRICTN 1551

Keywords for formats tN, E1, E3 19.1

12.19.25. WFRICTNL

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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 well’s 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.15).
One keyword can specify only one well. Well’s geometry should be previously defined via
the keyword COMPDATL (see 12.19.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 termi-
nated with a final /.

First data record:

1. well name (or well number);

2. tubing internal diameter (METRIC: m, FIELD: f t ). This parameter is used to calculate

the frictional pressure drop between the connections and the well’s bottom hole reference
point (it can be not equal to the 10-th parameter of COMPDATL (see 12.19.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: 1.

Second and other data records describe connections.

For horizontal well: each connection should be entered in the keyword just once, (individu-
ally 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.19.6).

Second and other data records:

12.19.25. WFRICTNL 1552

Keywords for formats tN, E1, E3 19.1

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 range
(nearest the well’s bottom hole reference point));

3. J-coordinate of one connection (or J-coordinate of the connection at the start of the
range (nearest the well’s bottom hole reference point));

4. K-coordinate of one connection (or K-coordinate of the connection at the start of the
range (nearest the well’s bottom hole reference point));

5. distance down the tubing from the well’s bottom hole reference point to the start of the
perforations in the grid block, specified via parameters 1-3 (METRIC: m, FIELD: f t );
Default: For the first data line – 0, for next data lines – the distance to the end of the
previous connection or range.

6. distance down the tubing from the well’s bottom hole reference point to the end of the
perforations in the grid block, specified via parameters 1-3 (METRIC: m, FIELD: f t );
Default: The sum of value of parameter 4 and the thickness of the grid block in the
direction of penetration, specified via parameter 6.

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: 2-nd parameter in the first data record.

Example
WFRICTN
WELL1 0.1 0.001 /
LGR1 10 22 8 2* I 7 /
/

12.19.25. WFRICTNL 1553

Keywords for formats tN, E1, E3 19.1

12.19.26. WFRICSEG / WFRICSGL

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.19.24) (WFRICTN
(see 12.19.24) for LGR case). WFRICSEG (WFRICSGL (see 12.19.26) 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.19.26). Keywords to specify parameters of
multisegment well are given in the section 2.15.
Friction wells and multisegment wells can’t exist in the same run. If this keyword is used,
then all friction wells should be converted.
Parameters of the keyword WFRICSEG (see 12.19.26) (WFRICSGL, see 12.19.26) is anal-
ogous to the keyword WFRICTN (see 12.19.24) (WFRICTN, see 12.19.24) 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 well’s bottom

12.19.26. WFRICSEG / WFRICSGL 1554

Keywords for formats tN, E1, E3 19.1

hole reference point to the start (and end) of the perforations in the grid block is defaulted.

12.19.26. WFRICSEG / WFRICSGL 1555

Keywords for formats tN, E1, E3 19.1

12.19.27. COMPSEGS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies completions in a multisegment well (section 2.15). One keyword
can specify only one well. The well should be previously defined via the keyword WEL-
SPECS (see 12.19.3) (WELSPECL, see 12.19.4) and the segment structure – WELSEGS
(see 12.19.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 termi-
nated 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 connection’s perforations as a distance along the
tubing from the well’s 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 (pa-
rameter 3 of the first record of WELSEGS (see 12.19.11). All connections should be defined
via COMPDAT (see 12.19.6) or COMPDATMD (see 12.19.10).

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.
The following data should be specified:

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.19.27. COMPSEGS 1556

Keywords for formats tN, E1, E3 19.1

5. length down the well bore from the well’s zero tubing length reference point to the start
of the connection in this grid block (METRIC: m, FIELD: f t );
Default: zero (for first data record).

6. length down the well bore from the well’s zero tubing length reference point to the end
of the connection in this grid block (METRIC: m, FIELD: f t );
Default: parameter 5 plus thickness of the grid block in penetration direction.

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.19.6).

10. thermal contact length (length of the well in the completion cell), IGNORED, this is an
E1/E3 compatibility field;
Default: 0.0.

11. segment number to allocate to all connections within the specified range. If this parame-
ter 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: 0.

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 well’s zero

12.19.27. COMPSEGS 1557

Keywords for formats tN, E1, E3 19.1

tubing length reference point to the start of the connection in this grid block – 30m. Length
down the well bore from the well’s 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.19.27. COMPSEGS 1558

Keywords for formats tN, E1, E3 19.1

12.19.28. COMPSEGL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies completions in a multisegment well (section 2.15) in local grid
LGR.
One keyword can specify only one well. The well should be previously defined via the
keyword WELSPECL (see 12.19.4) and the segment structure – WELSEGS (see 12.19.11).

All the parameters of this keyword are identical to parameters of COMPSEGS

(see 12.19.27). Additionally in the second and other data records name of LGR should be
specified. Parameters 2, 3, 4, 8 are in local grid coordinates.
Example
COMPSEGL
'PROD'/
LGR1 1 1 2 2 30 1* 'X' 5 /
/

12.19.28. COMPSEGL 1559

Keywords for formats tN, E1, E3 19.1

12.19.29. COMPLUMP

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword lumps connections together into completions to provide realization

of simultaneous actions. Completions numbers could be used in the keywords WPI-
MULT (see 12.19.35), WELOPEN (see 12.19.128), WBHZONE (see 12.19.152), WPIFUNC
(see 12.19.150), WSKFUNC (see 12.19.151). Connections should first have been defined with
the keyword COMPDAT (see 12.19.6). When a connection is first defined with COMPDAT
(see 12.19.6), it is given a completion number equal to its order of introduction in the well. If
the keyword COMPLUMP (see 12.19.29) 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
slash /. All data should be terminated with a final slash /.
Each record should contain the following parameters:

1. well name (or number), or well list name defined via WLIST (see 12.19.33);

2. connection coordinate in X direction;

Default: 0 (any value).

3. connection coordinate in Y direction;

Default: 0 (any value).

4. coordinate of upper connection block in this completion;

Default: 0 (the top connection of this well).

5. coordinate of lower connection block in this completion;

Default: 0 (the bottom connection of this well).

6. completion number of these connections.

The set of connections in the well which match the location indexes specified in parameters
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 can be used
together in the keywords WPIMULT (see 12.19.35), WBHZONE (see 12.19.152), WPIFUNC
(see 12.19.150), WSKFUNC (see 12.19.151).
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

12.19.29. COMPLUMP 1560

Keywords for formats tN, E1, E3 19.1

in parameter 6. If all four location indexes are defaulted, all the well’s 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.19.29. COMPLUMP 1561

Keywords for formats tN, E1, E3 19.1

12.19.30. COMPLMPL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword lumps connections together into completions to provide realization of simul-
taneous actions for the wells in local grids (section 5.5.8). Completions numbers could be used
in the keywords WPIMULT (see 12.19.35), WELOPENL (see 12.19.129). Connections should
first have been defined with the keyword COMPDATL (see 12.19.7). When a connection is first
defined with COMPDATL (see 12.19.7), it is given a completion number equal to its order of
introduction in the well. If the keyword COMPLMPL (see 12.19.30) is not used, each connec-
tion is in its own separate completion and the terms completion and connection are equivalent.

COMPLMPL must be used in place of COMPLUMP (see 12.19.29) to lumps connections

together into completions for wells in local refined grids, after the wells have been introduced
with keywords WELSPECL (see 12.19.4), COMPDATL (see 12.19.7). The keyword data for
COMPLMPL is the same as for COMPLUMP (see 12.19.29), except for an extra parameter 2
which names the local grid containing the connections specified in the record.

Any number of data records could be specified. Each record should be terminated with a
slash /. All data should be terminated with a final slash /.
Each record should contain the following parameters:

1. well name (or number), or well list name defined via WLIST (see 12.19.33);

2. local grid name (CARFIN, see 12.2.97);

3. connection coordinate in X direction;

Default: 0 (any value).

4. connection coordinate in Y direction;

Default: 0 (any value).

5. coordinate of upper connection block in this completion;

Default: 0 (the top connection of this well).

6. coordinate of lower connection block in this completion;

Default: 0 (the bottom connection of this well).

7. completion number of these connections.

12.19.30. COMPLMPL 1562

Keywords for formats tN, E1, E3 19.1

The set of connections in the well which match the location indexes specified in parameters
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.19.35).
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 well’s 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.19.30. COMPLMPL 1563

Keywords for formats tN, E1, E3 19.1

12.19.31. COMPORD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.19.74). In these workovers, all connections be-
low (further from the wellhead according to the connection order) the offending one will be
closed.

Any number of data records could be specified. Each record should be terminated with a
slash /. All data should be terminated with a final slash /.
Each record should contain the following parameters:

1. well name, or well list name defined via WLIST (see 12.19.33);

2. method for ordering well’s 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.19.6) (or COMPDATL, see 12.19.7).
• INPUT Connections order: according to their declaration in COMPDAT
(see 12.19.6) (or COMPDATL, see 12.19.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 MO 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.19.6), connections or-
der: according to DEPTH (see 12.3.28). 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.19.3), WELSPECL, see 12.19.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.19.31. COMPORD 1564

Keywords for formats tN, E1, E3 19.1

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.19.31. COMPORD 1565

Keywords for formats tN, E1, E3 19.1

12.19.32. COMPINJK

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword is used to specify the injection well relative permeabilities used for calcula-
tion of the mobility of the injected phase (see section 2.6.11).

Any number of data records could be specified. Each record should be terminated with a
slash /. All data should be terminated with a final slash /.
Each record should contain the following parameters:
1. well name, or well list name defined via WLIST (see 12.19.33);
Default: no default value.
2. X-coordinate of well connection;
Default: 0 (any value).
3. Y-coordinate of well connection;
Default: 0 (any value).
4. Z-coordinate of upper well connection;
Default: 0 (any value).
5. Z-coordinate of lower well connection;
Default: 0 (any value).
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: 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 /
/

12.19.32. COMPINJK 1566

Keywords for formats tN, E1, E3 19.1

In this example for all WELL1 connections (all connection coordinates are defaulted)
relative permeability of the injected phase is set to 1.

12.19.32. COMPINJK 1567

Keywords for formats tN, E1, E3 19.1

12.19.33. WLIST

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword is used to specify well lists. These well lists can be used in schedule section
keywords to specify several wells at once.
Any number of data records could be specified. Each record should be terminated with a
slash /. All data should be terminated with a final slash /.
Each record should contain the following parameters:
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 shouldn’t be members of any
other list);
• ADD – adds the following well names to this list (these wells shouldn’t be members
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.19.3). If an oper-
ation DEL is used only full well names should be entered. If NEW, ADD are used both
well names and well masks could be entered, see an example below.
Example
WLIST
'*L1' NEW W1 W3 W17 W22 /
'*L2' NEW W2 W6 W12 W14 W18 /
'*L3' NEW '?*PG'/
/
WELOPEN
'*L1' OPEN /
'*L2' OPEN /
'*L3' OPEN /
/
WLIST
'*L3' ADD W19 W13 /
/

12.19.33. WLIST 1568

Keywords for formats tN, E1, E3 19.1

In this example two well lists are created – L1 and L2 — specifying all wells. Well list L3
is created via well mask: it contains all wells whose name ends in PG. All wells are opened
via the keyword WELOPEN (see 12.19.128). Then 2 wells are added to the list L3.

12.19.33. WLIST 1569

Keywords for formats tN, E1, E3 19.1

12.19.34. WLISTDYN

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.
Any number of data records could be specified. Each record should be terminated with a
slash /. All data should be terminated with a final slash /.
Each record should contain the following parameters:
1. well list name in quotes (first character should be *);

2. well group name or group mask defining a subset of groups with common prefix (should
end with an asterisk *). 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;
• WVIT – Well voidage injection total;

12.19.34. WLISTDYN 1570

Keywords for formats tN, E1, E3 19.1

• 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.19.34. WLISTDYN 1571

Keywords for formats tN, E1, E3 19.1

12.19.35. WPIMULT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword is used to multiply well connection transmissibility factors by specified

value for well’s approximation (see section 2.14.1). 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 name defined via WLIST (see 12.19.33),

2. connection transmissibility factor multiplier. Can be specified by user via UDQ

(see 12.19.165);
Default: 1.0.

3. perforated interval coordinate in X direction, this is i in 5.6.1;

Default: any.

4. perforated interval coordinate in Y direction, this is j in 5.6.1;

Default: any.

5. perforated interval coordinate in Z direction, this is k in 5.6.1;

Default: any.

6. number of first completion in a range (completion numbers are set via COMPLUMP,
see 12.19.29);
Default: any.

7. number of last completion in a range (completion numbers are set via COMPLUMP,
see 12.19.29);
Default: any.

If WPIMULT is used several times for the same connection transmissibility factor (such
specifications of WPIMULT should be separated by keywords DATES (see 12.19.124) or
TSTEP, see 12.19.125), its effect is cumulative, i.e. multiplying factor is applied each time
the keyword is entered.
If a COMPDAT (see 12.19.6) keyword contains data inducing transmissibility factor recal-
culation, multiplier previously defined by WPIMULT is reset to 1.0.
Note:
The keyword WPIMULT has different behavior for model E1 and E3 formats in the case be-
low. If at one time step there are several WPIMULT keywords with defaulted parameters then

12.19.35. WPIMULT 1572

Keywords for formats tN, E1, E3 19.1

only the last one is used in E1 format, but all of them are used in E3 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 /
/
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

12.19.35. WPIMULT 1573

Keywords for formats tN, E1, E3 19.1

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.19.35. WPIMULT 1574

Keywords for formats tN, E1, E3 19.1

12.19.36. WPIMULTL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword is used to multiply well connection transmissibility factors by specified

value for well’s approximation (see section 2.14.1) in local grids (section 5.5.8). A set of data
for every well should be terminated with a slash /.

WPIMULTL must be used in place of WPIMULT (see 12.19.35) to multiply well connection
transmissibility factors by specified value for wells in local refined grids, after the wells have
been introduced with keywords WELSPECL (see 12.19.4), COMPDATL (see 12.19.7). The
keyword data for WPIMULT is the same as for WPIMULT (see 12.19.35), except for an extra
parameter 3 which names the local grid containing the connections specified in the record.

The following parameters are to be specified:

1. well name (or number), or well list name defined via WLIST (see 12.19.33),

2. connection transmissibility factor multiplier. Can be specified by user via UDQ

(see 12.19.165);
Default: 1.0.

3. local grid name (CARFIN, see 12.2.97);

4. perforated interval coordinate in X direction, this is i in 5.6.1;

Default: any.

5. perforated interval coordinate in Y direction, this is j in 5.6.1;

Default: any.

6. perforated interval coordinate in Z direction, this is k in 5.6.1;

Default: any.

7. number of first completion in a range (completion numbers are set via COMPLMPL,
see 12.19.30);
Default: any.

8. number of last completion in a range (completion numbers are set via COMPLMPL,
see 12.19.30);
Default: any.

12.19.36. WPIMULTL 1575

Keywords for formats tN, E1, E3 19.1

If WPIMULTL is used several times for the same connection transmissibility factor (such
specifications of WPIMULTL should be separated by keywords DATES (see 12.19.124) or
TSTEP, see 12.19.125), its effect is cumulative, i.e. multiplying factor is applied each time
the keyword is entered.
If a COMPDATL (see 12.19.7) keyword contains data inducing transmissibility factor re-
calculation, multiplier previously defined by WPIMULTL is reset to 1.0.
Note:
The keyword WPIMULTL has different behavior for model E1 and E3 formats in the case
below. If at one time step there are several WPIMULTL keywords with defaulted parameters
then only the last one is used in E1 format, but all of them are used in E3 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.19.36. WPIMULTL 1576

Keywords for formats tN, E1, E3 19.1

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.19.36. WPIMULTL 1577

Keywords for formats tN, E1, E3 19.1

12.19.37. WPITAB

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword can be used to assign PI multiplier table to the well. The tables scale the
well’s connection factors according to the maximum water cut it achieved. Tables are specified
via the keyword PIMULTAB (see 12.19.38). It is required to specify dimension of PI scaling
tables using the keyword PIMTDIMS (see 12.1.36).

An arbitrary number of data lines can be entered. Each data line should be terminated with
the symbol /. All data should be terminated with a final slash /.
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 name
defined via WLIST (see 12.19.33);

2. PI multiplier table number, (tables are specified via PIMULTAB, see 12.19.38). Zero or
negative value of this parameter means that no PI multiplier table is assigned to the
well;
Default: 0.

Example
WPITAB
W1 1 /
W1 2 /
/

12.19.37. WPITAB 1578

Keywords for formats tN, E1, E3 19.1

12.19.38. PIMULTAB

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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. It is required to specify
dimension of PI scaling tables using the keyword PIMTDIMS (see 12.1.36). The tables are
assigned to the wells via the keyword WPITAB (see 12.19.37).

Each table should be terminated with a slash /.

One table row contains the following parameters:

1. maximum watercut (METRIC: sm3 /sm3 , FIELD: stb/stb);

2. corresponding value of PI scaling factor.

Empty table that contains only a slash / is considered a copy of the previous table.
Example
PIMULTAB
0 1
0.2 0.86
0.3 0.44
0.7 0.39 /

In this example one table is specified.

12.19.38. PIMULTAB 1579

Keywords for formats tN, E1, E3 19.1

12.19.39. COMPRP

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword specifies the data for rescaling saturations at wells connections (well con-
nections should be previously defined via COMPDAT, see 12.19.6).

The set of data for each well should be terminated with a slash /. All data should be
terminated with a final slash /.
For each well the following parameters should be specified:
1. well name (or number), or well list name defined via WLIST (see 12.19.33),
2. X-coordinate of connection – i number of grid block;
Default: all possible i numbers of grid block.
3. Y-coordinate of connection – j number of grid block;
Default: all possible j number of grid block.
4. Z-coordinate of upper connection – k number of grid block;
Default: all possible k number of grid block.
5. Z-coordinate of lower connection – k number of grid block;
Default: all possible 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.19.6). In case with
hysteresis this number is used in both imbibition and drainage processes;
Default: negative (data specified via 7-th parameter of COMPDAT (see 12.19.6) are not
overridden).
7. SWMIN scaled value of the minimum water saturation;
Default: SW c .
8. SWMAX scaled value of the maximum water saturation;
Default: 1 − SOW cr (for three-phase cases or water-oil systems) or 1 − SGcr (for gas-
water systems).
9. SGMIN scaled value of the critical gas saturation;
Default: SGcr .

12.19.39. COMPRP 1580

Keywords for formats tN, E1, E3 19.1

10. SGMAX scaled value of the maximum gas saturation;

Default: 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.19.39. COMPRP 1581

Keywords for formats tN, E1, E3 19.1

12.19.40. FBHPDEF

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword changes the default BHP values for well controls used by WCON-
PROD (see 12.19.42), WCONHIST (see 12.19.43), WCONINJE (see 12.19.44), WCONINJH
(see 12.19.47), and WCONINJP (see 12.19.46).
The data should be terminated with a slash /.
The following parameters should be specified:

1. Target BHP for production wells.

Default:
For E1: 1 atma.
For E3 (history matching): 1 atma.
For E3 (otherwise): 100 atma.

2. Target BHP for injection wells.

Default:
For E1: 6803 atma.
For E3 (thermal): 200 atma.
For E3 (otherwise): 1000 atma.

Example
FBHPDEF
50 450 /
In this example the target BHP for production wells is set to 50 and for injection wells to
450.

12.19.40. FBHPDEF 1582

Keywords for formats tN, E1, E3 19.1

12.19.41. WINJMULT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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
should be terminated with a final slash /.
One data line contains the following parameters:
1. well name (or number), or well list name defined via WLIST (see 12.19.33),

2. Pf – fracturing pressure (METRIC: barsa, FIELD: psia);

Default: can be specified as default value only if multiplier gradient is default value.

3. a – multiplier gradient (METRIC: 1/bars, FIELD: 1/psi);

Default: 0.

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. Injec-
tivity increase is reversed for all connections if the wellbore pressure subsequently
declines.

12.19.41. WINJMULT 1583

Keywords for formats tN, E1, E3 19.1

• 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;
• Default: WREV.

5. i-coordinate of grid block with connection;

Default: negative (allows any value).

6. j-coordinate of grid block with connection;

Default: negative (allows any value).

7. k-coordinate of grid block with connection;

Default: 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.19.41. WINJMULT 1584

Keywords for formats tN, E1, E3 19.1

12.19.42. WCONPROD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword could be specified for a well or a group of wells that work as producing.
If the group control option with well prioritization (see section 2.14.13) is set a well’s rate
exceeding the group’s limit will be cut (in spite of its limit).
Parameters that are set via this keyword can be modified via WELTARG (see 12.19.60).

A set of data for every well should be terminated with a slash /.

All data should be terminated with a final slash /.
The following data should be specified:

1. well name (or number), or well list name defined via WLIST (see 12.19.33),

2. well working mode:

• OPEN,
• STOP,
• SHUT,
• AUTO — well has SHUT status, but is open automatically, if the constraints
allow. If no constraints are set then the well will open immediately. Possible
constraints – drilling rate WDRILTIM (see 12.19.228), drilling rig availability –
GRUPRIG (see 12.19.233), maximum number of open wells for group – GECON
(see 12.19.121), WELSOMIN (see 12.19.2);
• Default: OPEN.

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 E3 format models),
• RESV — reservoir voidage (total fluid (oil+gas+water) flow rate at reservoir con-
ditions according to the 13th parameter of WELSPECS, see 12.19.3),
• THP — tubing head pressure control,
• BHP — bottom hole pressure control (see section 5.6),

12.19.42. WCONPROD 1585

Keywords for formats tN, E1, E3 19.1

• TMRA — total molar rate control,

• STRA — steam rate control (only for thermal E3 models),
• SATP — water saturation pressure control (see parameter 16; only for thermal E3
models),
• SATT — water saturation temperature control (see parameter 17; only for thermal
E3 models),
• CVAL — calorific rate control (only for E3 models),
• NGL — NGL rate control (only for E3 models),
• GRUP — control of group rate well’s fracture. Group rate value is specified via the
keyword GCONPROD (see 12.19.86);
• Default: ' '(well control mode can be undefined in case if the well is shut or
stopped and is not in the drilling queue).

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. fluid rate at reservoir conditions (or upper limit) (METRIC: rm3 /day, FIELD: rb/day);
Default: 1e + 20 m 3 / day.

9. BHP value or lower limit (METRIC: barsa, FIELD: psia);

Default: for E1 format models – patm = 14.7 psia (atmosphere pressure), for E3 format
models – 100 atma = 1470 psia, unless overridden by FBHPDEF (see 12.19.40).

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);
Default: 0.

11. well VFP table number (VFPPROD (see 12.19.66), VFPCORR, see 12.19.71); if zero,
THP will not be reported;
Default: 0.

12. ALQ quantity (artificial lift or other parameter) that will be used in THP calcula-
tions (see the keyword VFPPROD, see 12.19.66). Can be specified by user via UDQ
(see 12.19.165);
Default: 0.

13. wet gas production rate (or upper limit) (METRIC: sm3 /day, FIELD: Msc f /day);

12.19.42. WCONPROD 1586

Keywords for formats tN, E1, E3 19.1

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.54) runs.
Can be specified by user via UDQ (see 12.19.165).

16. pressure offset for saturation pressure control ∆P (METRIC: bar , FIELD: psia). This
parameter can be used only in THERMAL (see 12.1.54) runs. Can be specified by user
via UDQ (see 12.19.165).
The constraint for BHP is BHP ≥ Psat + ∆P, where Psat is maximum saturated water
pressure in all blocks with producing connections;

17. temperature offset for saturation temperature control ∆T (METRIC: ◦ C, FIELD: ◦ F).
This parameter can be used only in THERMAL (see 12.1.54) runs. Can be specified by
user via UDQ (see 12.19.165).
The constraint for BHP is BHP ≥ Psat (T + ∆T ), where T is maximum temperature in
all blocks with producing 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 E1/E3 compatibility
field;

20. natural gas liquid (NGL) rate (or upper limit) (METRIC: sm3 /day, FIELD: stb/day).
Can be specified by user via UDQ (see 12.19.165).

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.103).
All well control switching times are logged, REPORTFILE / REPORTSCREEN
(see 12.1.3).

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

12.19.42. WCONPROD 1587

Keywords for formats tN, E1, E3 19.1

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 /
/
In this example both wells are on BHP control. In this case rates are calculated by simula-
tor. 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.19.42. WCONPROD 1588

Keywords for formats tN, E1, E3 19.1

12.19.43. WCONHIST

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword may be specified for a well or a group of wells (instead of the keyword
WCONPROD, see 12.19.42) that work as producers and are being history matched. The key-
word WCONINJH (see 12.19.47) is used for wells that work as injectors and are being history
matched.

A set of data for every well should be terminated with a slash /. All data should be
terminated with a final slash /.
The following data should be specified:

1. well name (or number), or well list name defined via WLIST (see 12.19.33),

2. well status (OPEN, STOP or SHUT);

Default: OPEN.

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 E3 format models),
◦ RESV — reservoir voidage control (total fluid (oil+gas+water) flow rate at reservoir
conditions according to the 13th parameter of WELSPECS (see 12.19.3), calculated
from observed flow rates),
◦ BHP — bottom hole pressure;
◦ THP — tubing head pressure;
◦ TGRUP – fraction of group rate specified by GRUPTARG (see 12.19.63) (the group
rate is distributed among the wells based on their potentials);

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),

12.19.43. WCONHIST 1589

Keywords for formats tN, E1, E3 19.1

7. well VFP table number (VFPPROD (see 12.19.66), VFPCORR, see 12.19.71); if zero,
THP will not be reported; if non-zero, THP will be calculated and reported;
Default: last indicated value.

8. ALQ quantity (artificial lift or other parameter) that will be used in THP calculations
(see the keyword VFPPROD, see 12.19.66);

9. observed tubing head pressure THP (METRIC: barsa, FIELD: psia);

Default: 0.

10. observed bottom hole pressure BHP (METRIC: barsa, FIELD: psia);
Default: 0.

11. observed wet gas production rate (METRIC: sm3 /day, FIELD: Msc f /day);
Default: 0.

12. observed natural gas liquid (NGL) rate (METRIC: sm3 /day, FIELD: stb/day);
Default: 0.

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 the keyword WELTARG (see 12.19.60). Otherwise de-
fault 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 doesn’t violate BHP limit, the well will return to rate control mode.
All well control switching times are logged, REPORTFILE / REPORTSCREEN
(see 12.1.3).
This keyword is convenient for history matching purposes.
Example
WCONHIST
1043 OPEN LRAT 18.9 0 0 /
1054 OPEN LRAT 16.38 1.765 0 3* 57 /
/
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

12.19.43. WCONHIST 1590

Keywords for formats tN, E1, E3 19.1

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.19.43. WCONHIST 1591

Keywords for formats tN, E1, E3 19.1

12.19.44. WCONINJE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword could be specified for a well or a group of wells that work as injectors.
Parameters that are set via this keyword can be modified via WELTARG (see 12.19.60).

A set of data for every well should be terminated with a slash /.

All data should be terminated with a final slash /.
The following data should be specified:
1. name of well (or number), or well list name defined via WLIST (see 12.19.33),

2. injected fluid:

• WATER (also WAT is possible),

• OIL,
• GAS;
Note: for model in E3 format the composition of the injected gas should be speci-
fied via WINJGAS (see 12.19.190), unless the well belongs to the group with gas
injection control where the injected gas is defined.
• MULTI — multi-phase injection (water, oil, gas) (see section 2.14.6). In this case
the preferred phase of the well will be injected (specified via WELSPECS,
see 12.19.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.
• HCGAS – gas,
Note: for models in E3 format the composition of the injected gas should be
specified using the keyword WINJGAS (see 12.19.190). As alternative CodeGAS
can be used as the injected fluid. The difference between HCGAS and GAS is
described in the section below Calculation of molar rates for E3 format.
• HCOIL – oil.
Note: for models in E3 format the composition of the injected oil is specified using
the keyword WINJGAS (see 12.19.190). The difference between HCOIL and OIL
is described in the section below Calculation of molar rates for E3 format.

3. well working mode (OPEN, STOP or SHUT);

Default: OPEN.

4. well control:

12.19.44. WCONINJE 1592

Keywords for formats tN, E1, E3 19.1

• RATE — controlled by surface flow rate target,

• BHP — controlled by BHP target,
• THP — controlled by THP target,
• RESV — controlled by reservoir volume rate target (at conditions defined by the
13th parameter of WELSPECS, see 12.19.3),
• GRUP — group control (the keyword GCONINJE, see 12.19.95)),

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.19.3);
Default: 1000000 m 3 / day.

6. reservoir rate of injected fluid (METRIC: rm3 /day, FIELD: rb/day),

7. BHP for injection or limit (METRIC: barsa, FIELD: psia);

Default: 6801patm , unless overridden by FBHPDEF (see 12.19.40).

8. THP for injection or limit (METRIC: barsa, FIELD: psia).

9. VFP table number for the injector (the keyword VFPINJ, see 12.19.65);

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 E1/E3 compatibility field,

11. IGNORED, this is an E1/E3 compatibility field;

12. surface volume proportion of oil in case of MULTI injection (dimensionless, should be
positive value);
Default: 0.

13. surface volume proportion of water in case of MULTI injection (dimensionless, should
be positive value);
Default: 0.

14. surface volume proportion of gas in case of MULTI injection (dimensionless, should be
positive value);
Default: 0.

User may specify one of the following combinations:

12.19.44. WCONINJE 1593

Keywords for formats tN, E1, E3 19.1

• Specify BHP value pBH , and set well to BHP control, in this case injection rate is
calculated from (2.103). 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).

Calculation of molar rates for E3 format

In compositional injection model, volume rates are converted to molar rates (2-nd param-
eter of keyword WCONINJE (see 12.19.44) is specified type of injected fluid):

• if injected fluid type is GAS and WATER molar density is constant. Gas molar density
is defined from the ideal gas law. Water molar density is defined from the water gravity
density using keywords DENSITY (see 12.5.33), GRAVITY (see 12.5.34).

• if injected fluid type is HCGAS and HCOIL, flash at stock tank conditions (STCOND,
see 12.14.11) is used for calculation of the phase molar densities.

It may happen that production of stock-tank flash used for HCGAS and HCOIL is not a
single phase fluid of the expected type. For example, for HCGAS stock-tank flash may not
produce single phase gas.
Therefore:

• If the flash produces two-phase fluid, then both phases will be injected and the well will
be controlled by the rate of the selected phase. This approach can be used for injection
of two-phase hydrocarbons.

• If the flash produces single-phase fluid of the wrong type then a molar density is set to
be constant and is computed as:
n P
=
V RT Z
A molar density for HCGAS coincides with density for GAS and compressibility Z is
set to 1, if the surface flash does not produce gas. For HCOIL compressibility is Z = 0.05
if surface flash does not produce oil.

12.19.44. WCONINJE 1594

Keywords for formats tN, E1, E3 19.1

HCGAS allows that different injection streams correspond to different molar densities.
It is not recommended to use this injected type in case of reservoir gas is reinjected (see
WINJGAS, see 12.19.190), since the injection fluid composition is not known in advance.
For models in E1 format HCGAS and GAS types are the same, and type HCOIL is equiv-
alent to type OIL.
Example 1.

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 auto-
matically 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 pro-
portion of oil – 0.8, Surface volume proportion of water – 0.2

12.19.44. WCONINJE 1595

Keywords for formats tN, E1, E3 19.1

12.19.45. WCONINJ

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword can be used in tNavigator, but it is highly recommended to use the keyword
WCONINJE (see 12.19.44) instead of WCONINJ.

This keyword could be specified for a well or a group of wells that work as injectors.

A set of data for every well should be terminated with a slash /.

All data should be terminated with a final slash /.
The following data should be specified:

1. name of well (or number), or well list name defined via WLIST (see 12.19.33),

2. injected fluid:

• WATER (also WAT is possible);

• OIL;
• GAS.

3. well working mode:

• OPEN;
• STOP;
• SHUT;
• Default: OPEN.

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 (at conditions defined by the
13th parameter of WELSPECS, see 12.19.3).

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);
Default: 1020 m 3 /day.

12.19.45. WCONINJ 1596

Keywords for formats tN, E1, E3 19.1

6. reservoir rate of injected fluid (METRIC: rm3 /day, FIELD: rb/day);

Default: 1020 m 3 /day.

7. reinjection or voidage replacement fraction;

Default: 0.

8. reinjection or voidage replacement flag:

• NONE – no reinjection or voidage replacement;

• GPRD – well reinjects a fraction of its group’s production;
• FPRD – well reinjects a fraction of the field’s production;
• GVDG – well replaces a fraction of its group’s voidage;
• FVD – well replaces a fraction of the field’s voidage;
• Default: NONE.

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.

9. BHP for injection or limit (METRIC: barsa, FIELD: psia);

Default: 6804patm , unless overridden by FBHPDEF (see 12.19.40).

10. THP for injection or limit (METRIC: barsa, FIELD: psia);

Default: 1020 patm .

11. VFP table number for the injector (the keyword VFPINJ, see 12.19.65);
Default: 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.19.45. WCONINJ 1597

Keywords for formats tN, E1, E3 19.1

12.19.46. WCONINJP

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies the injector which injects at a rate equal to the sum of parts of vol-
umes 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 can’t 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 termi-
nated 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:

• WATER (also WAT is possible),

• OIL,
• GAS,
• MULTI — multi-phase injection (water, oil, gas) (see section 2.14.6). In this case
the preferred phase of the well will be injected (specified via WELSPECS,
see 12.19.3). Parameters 9-11 specify surface volume proportion of phases in a
multi-phase injector;
• Default: WATER.

3. well working mode (OPEN, STOP or SHUT);

Default: OPEN.

4. BHP for injection or limit (METRIC: barsa, FIELD: psia),

5. THP for injection or limit (METRIC: barsa, FIELD: psia),

12.19.46. WCONINJP 1598

Keywords for formats tN, E1, E3 19.1

6. VFP table number for the injector (the keyword VFPINJ, see 12.19.65);

7. 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 E1/E3 compatibility field,

8. factor; calculated injection volume for this injector will be multiplied by this factor;
Default: 1.

9. surface volume proportion of oil in case of MULTI injection;

Default: 0.

10. surface volume proportion of water in case of MULTI injection;

Default: 0.

11. surface volume proportion of gas in case of MULTI injection;

Default: 0.

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-computed 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 /
/

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.19.46. WCONINJP 1599

Keywords for formats tN, E1, E3 19.1

12.19.47. WCONINJH

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword may be specified for a well or a group of wells (instead of the keyword
WCONINJE, see 12.19.44) that work as injectors and are being history matched. The keyword
WCONHIST (see 12.19.43) is used for wells that work as producers and are being history
matched.

A set of data for every well should be terminated with a slash /.

All data should be terminated with a final slash /.
The following data should be specified:

1. name of well (or number), or well list name defined via WLIST (see 12.19.33),

2. injected fluid:

• WATER (also WAT is possible),

• OIL,
• GAS,
• MULTI — multi-phase injection (water, oil, gas) (see section 2.14.6). In this
case the preferred phase of the well will be injected (specified via WELSPECS,
see 12.19.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;
• Default: WATER.

3. well working mode (OPEN, STOP or SHUT);

Default: OPEN.

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.19.3).

5. observed bottom hole pressure BHP (METRIC: barsa, FIELD: psia), will be used for
reporting, it’s not a limit (well will not switch to BHP control if the calculated BHP is
above this value);
Default: 0.

12.19.47. WCONINJH 1600

Keywords for formats tN, E1, E3 19.1

6. observed tubing head pressure THP (METRIC: barsa, FIELD: psia);

Default: 0.

7. well VFP table number;

8. 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 E1/E3 compatibility field,

9. surface volume proportion of oil in case of MULTI injection;

Default: 0.

10. surface volume proportion of water in case of MULTI injection;

Default: 0.

11. surface volume proportion of gas in case of MULTI injection;

Default: 0.

12. well control mode:

• RATE – well is controlled by injection rate;

• BHP – well is controlled by bottom hole pressure;
• THP – well is controlled by tubing head pressure;
• Default: RATE.

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 con-
trol. If the switch doesn’t violate BHP limit, the well will return to injection rate control mode.

All well control switching times are logged, REPORTFILE / REPORTSCREEN

(see 12.1.3).

This keyword is convenient for history matching purposes.

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).

12.19.47. WCONINJH 1601

Keywords for formats tN, E1, E3 19.1

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.19.47. WCONINJH 1602

Keywords for formats tN, E1, E3 19.1

12.19.48. WELLINJE

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword could be specified for a well or a group of wells that work as injectors.

A set of data for every well should be terminated with a slash /.

All data should be terminated with a final slash /.
The following data should be specified:

1. name of well (or number), or well list name defined via WLIST (see 12.19.33),

2. nature of injected fluid (tNavigator supports the following options):

• WATER (also WAT is possible),

• 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.19.184) (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.19.188) or WINJORD (see 12.19.189) (mixture name
should be entered via parameter 3 of this keyword);
• GV – injected gas composition corresponds to gas composition, produced by spec-
ified group (group name should be entered via parameter 3 of this keyword);
• WV – injected gas composition corresponds to gas composition, produced by spec-
ified 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 key-
word:

• 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:

• WAT – injects a target water volume specified via parameter 6;

12.19.48. WELLINJE 1603

Keywords for formats tN, E1, E3 19.1

• 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;
• RE – reinjection or voidage replacement control; a fraction is specified via param-
eter 12.

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);

8. BHP for injection or limit (METRIC: barsa, FIELD: psia),

9. THP for injection or limit (METRIC: barsa, FIELD: psia).

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 E1/E3 com-
patibility field;

12. target (or limit) re-injection fraction or voidage replacement fraction. If parameter 18 is
set to S, then parameter 12 is re-injection fraction. In case of target value is considered
the well will attempt to inject the fluid specified by parameter 2 on condition that surface
rate is equal to the re-injection fraction multiplied by the water or available produced
gas rate of the group or well specified by parameter 14. By default the available gas rate
of a group of wells for re-injection is equal to the group’s gas production rate plus the
rate of any advanced gas for this group (keyword GADVANCE, see 12.19.192) minus its
fuel rate (see keyword GRUPFUEL, see 12.19.195) minus its sales target (see keyword
GRUPSALE, see 12.19.193). However, the ordering of this definition can be changed
using keyword WTAKEGAS (see 12.19.196). In the case of a re-injection fluid defined
by a stream or mixture, the specified fraction of the available surface gas production
rate is implemented as a wet gas re-injection rate target. If parameter 18 is set to R,
parameter 12 is a voidage replacement fraction. In case of target value is considered the
well attempts to inject the fluid specified by parameter 2 on condition that a reservoir
volume rate equal to the voidage replacement fraction multiplied by the total reservoir
volume production rate of the group or well specified by parameter 14.

12.19.48. WELLINJE 1604

Keywords for formats tN, E1, E3 19.1

A make-up gas stream is specified in parameter 17. If the target gas injection rate
exceeds the available gas rate then make-up gas stream is mixed with the injection
stream;
Default: 0.

13. production type that is used to define the rate under re-injection or voidage replacement
control:

• W – re-injection or voidage replacement rate is controlled by production of well,

defined in parameter 14;
• G – re-injection or voidage replacement rate is controlled by production of group,
defined in parameter 14.

Default:

• if parameter 2 is WV: W;
• if parameter 2 is GV: G.

14. name of the production well or group that controls the re-injection or voidage replace-
ment rate. If parameter 13 is set to W the name of a production well should be specified.
If parameter 13 is set to G the name of a group of wells should be specified;
Default: for injected fluids WV or GV in parameter 2 it is selected the source name
produced the fluid composition specified in parameter 3.

15. gas rate that is subtracted from the re-injection rate target (METRIC: sm3 /day, FIELD:
Msc f /day). This is important only for re-injection of a fraction of a named well’s
production. The well specified in parameter 1 attempts to inject at a rate equal to the
re-injection fraction multiplied by the production rate of the well specified in parameter
14, minus the rate set in parameter 15;

16. VFP table number for the injector (the keyword VFPINJ, see 12.19.65);

17. well stream which will be used as make-up gas. If make-up gas is used when the injected
gas rate exceeds the advance and/or available produced gas from the source group or
well;

18. the way in which re-injection or voidage replacement fraction in parameter 12 is to be

interpreted:

• S is the re-injection. Reinject a fraction of surface volume production;

• R is the voidage replacement. Replace a fraction of reservoir volume production;
• Default: S.

12.19.48. WELLINJE 1605

Keywords for formats tN, E1, E3 19.1

19. the stage of the separator which defines the fluid composition for injection. The vapor
extracted at any stage of the separator can be a source of injection fluid. The choice
of separator stage affects the available produced gas supply rate from the group or
well specified by parameter 3 if the nature of injected fluid is GV or WV (specified
by parameter 2), and also the rate of the control group or well (parameter 14) for
re-injection;
Default: 0.

20. the target or limit total molar rate (METRIC: kg-mol/day, FIELD: lb-mol/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-mol , FIELD:
Btu/lb-mol ). 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 don’t need to be specified (3-rd, 5-th, 7-th and
24-th) or they are ignored (9-20-th).

12.19.48. WELLINJE 1606

Keywords for formats tN, E1, E3 19.1

12.19.49. GRUPINJE

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword could be specified for a group of injector wells.

A set of data for every group should be terminated with a slash /.

All data should be terminated with a final slash /.
The following data should be specified:

1. well group name, or group mask defining a subset of groups with common prefix (should
end with an asterisk *), or FIELD.

2. composition of injection fluid:

• WATER (also WAT is possible) – water;

• 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.19.184) (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.19.188) or WINJORD (see 12.19.189) (mixture name
should be entered via parameter 3 of this keyword);
• GV – injected gas composition corresponds to gas composition, produced by spec-
ified group (group name should be entered via parameter 3 of this keyword);
• WV – injected gas composition corresponds to gas composition, produced by spec-
ified well (well name should be entered via parameter 3 of this keyword).

3. character string that specifies the data in accordance with the parameter 2 of the key-
word:

• 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:

• WAT – injects a target water volume specified via parameter 6;

12.19.49. GRUPINJE 1607

Keywords for formats tN, E1, E3 19.1

• GAS – injects a target gas volume specified via parameter 7;

• 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;
• GR – the well is under group control;
• 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);

8. fluid volume rate at reservoir conditions (or limit) (METRIC: rm3 /day, FIELD:
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;
• Default:
– if parameter 4 is RE: 1;
– otherwise: 0
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.19.49. GRUPINJE 1608

Keywords for formats tN, E1, E3 19.1

• Default:
– if parameter 2 is WV: W;
– if parameter 2 is GV: G.

12. name of the production well or group that controls the reinjection or voidage replace-
ment rate:

• 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;
• Default: 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.

13. IGNORED, this is an E1/E3 compatibility field;

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;
• Default: S.

16. separator stage that defines the fluid composition for injection;

17. Default: 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.19.49. GRUPINJE 1609

Keywords for formats tN, E1, E3 19.1

12.19.50. WCYCLE

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword can be used to specified automatic cycling of wells on and off.
For example for WAG cycle – 2.14.7 (alternating injection of water and gas).

A set of data for every well should be terminated with a slash /.

All data should be terminated with a final slash /.
The following data should be specified:

1. name of well (or number), or well list name defined via WLIST (see 12.19.33),

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;
Default: 0 (days).

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;
Default: 0 (days).

4. well start-up time Tstart (days).

The well’s efficiency factor will be increasing when it is turned on by automatic cycling.
At each time step 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;
Default: 0 (days) (instantaneous start-up).

5. maximum time step 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.19.140).

12.19.50. WCYCLE 1610

Keywords for formats tN, E1, E3 19.1

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;
Default: 0 (default length of the time step will be used).

6. are the time steps controlled to coincide exactly with the on/off cycling times of this
well?

• YES – The time steps coincide with this well’s on/off cycling times. Well works
with cycles with specified periods.
• NO – The time steps does not automatically coincide with this well’s on/off cycling
times. The well cycles at the beginning of the next time step which starts after the
specified period has elapsed;
• Default: NO.

Example
WCYCLE
WELL1 50 30 /
/

In this example WELL1 on-period is 50 days, off-period – 30 days.

12.19.50. WCYCLE 1611

Keywords for formats tN, E1, E3 19.1

12.19.51. WELLWAG

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword can be used to specified WAG option (water and gas injection).
For example for WAG cycle – 2.14.7 (alternating injection of water and gas).

The keyword WELLINJE (see 12.19.48) (or WCONINJE, see 12.19.44) should be defined
before this keyword to set injection parameters.

A set of data for every well should be terminated with a slash /.

All data should be terminated with a final slash /.
The following data should be specified:

1. name of well (or number), or well list name defined via WLIST (see 12.19.33),

2. type of WAG cycle: T – time; M – months, Y – years;

Default: T – time.

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.19.65);
Default: the value that was previously specified for this well.

8. VFP table number for the second injected fluid (VFPINJ, see 12.19.65);
Default: the value that was previously specified for this well.

9. control for the first injected fluid (RATE — control by surface flow rate (5-th parameter
of WCONINJE (see 12.19.44) or WELTARG, see 12.19.60), BHP — BHP control, THP
— THP control);
Default: RATE — control by surface flow rate.

12.19.51. WELLWAG 1612

Keywords for formats tN, E1, E3 19.1

10. control for the second injected fluid (RATE — control by surface flow rate (5-th param-
eter of WCONINJE (see 12.19.44) or WELTARG, see 12.19.60), BHP — BHP control,
THP — THP control);
Default: RATE — control by surface flow rate.

11. BHP (or BHP upper limit) for the first injected fluid (METRIC: barsa, FIELD: psia);
Default: the value that was previously specified for this well via WCONINJE
(see 12.19.44) or WELTARG (see 12.19.60).

12. BHP (or BHP upper limit) for the second injected fluid (METRIC: barsa, FIELD:
psia);
Default: the value that was previously specified for this well via WCONINJE
(see 12.19.44) or WELTARG (see 12.19.60).

13. THP (or THP upper limit) for the first injected fluid (METRIC: barsa, FIELD: psia);
Default: the value that was previously specified for this well via WCONINJE
(see 12.19.44) or WELTARG (see 12.19.60).

14. THP (or THP upper limit) for the second injected fluid (METRIC: barsa, FIELD: psia);
Default: the value that was previously specified for this well via WCONINJE
(see 12.19.44) or WELTARG (see 12.19.60).

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.19.51. WELLWAG 1613

Keywords for formats tN, E1, E3 19.1

12.19.52. WWAG

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword can be used to specified automatic cycling of wells on and off.
For example for WAG cycle – 2.14.7 (alternating injection of water and gas).

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 data
should be terminated with a final slash /.
First set of parameters:
1. name of well (or number),

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.
• Default: ON.

3. type of the specified value:

• TIME – time;
• RATE – injection rate in the surface conditions;
• RESV – injection rate in the reservoir conditions.
• Default: TIME.

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):

12.19.52. WWAG 1614

Keywords for formats tN, E1, E3 19.1

• WATER (also WAT is possible),

• 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.19.184) (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.19.188) or WINJORD (see 12.19.189) (mixture name
should be entered via parameter 3 of this keyword);
• GV – injected gas composition corresponds to gas composition, produced by spec-
ified group (group name should be entered via parameter 3 of this keyword);
• WV – injected gas composition corresponds to gas composition, produced by spec-
ified 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 key-
word:

• 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:

• WAT – injects a target water volume specified via parameter 7;

• GAS – injects a target gas volume specified via parameter 8;
• BHP – maintains a target BHP specified via parameter 9;
• THP – maintains a target THP specified via parameter 10;
• RV – injects a target fluid volume in reservoir conditions specified via parameter
11;
• GR – the well is under group control;
• RE – reinjection or voidage replacement control; a fraction is specified via param-
eter 12.

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
– for gas);

12.19.52. WWAG 1615

Keywords for formats tN, E1, E3 19.1

8. BHP for injection or limit (METRIC: barsa, FIELD: psia),

9. THP for injection or limit (METRIC: barsa, FIELD: psia).

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 E1/E3 com-
patibility field;

12. target (or limit) re-injection fraction or voidage replacement fraction. If parameter 18 is
set to S, then parameter 12 is re-injection fraction. In case of target value is considered
the well will attempt to inject the fluid specified by parameter 2 on condition that surface
rate is equal to the re-injection fraction multiplied by the water or available produced
gas rate of the group or well specified by parameter 14. By default the available gas rate
of a group of wells for re-injection is equal to the group’s gas production rate plus the
rate of any advanced gas for this group (keyword GADVANCE, see 12.19.192) minus its
fuel rate (see keyword GRUPFUEL, see 12.19.195) minus its sales target (see keyword
GRUPSALE, see 12.19.193). However, the ordering of this definition can be changed
using keyword WTAKEGAS (see 12.19.196). In the case of a re-injection fluid defined
by a stream or mixture, the specified fraction of the available surface gas production
rate is implemented as a wet gas re-injection rate target. If parameter 18 is set to R,
parameter 12 is a voidage replacement fraction. In case of target value is considered the
well attempts to inject the fluid specified by parameter 2 on condition that a reservoir
volume rate equal to the voidage replacement fraction multiplied by the total reservoir
volume production rate of the group or well specified by parameter 14.
A make-up gas stream is specified in parameter 17. If the target gas injection rate
exceeds the available gas rate then make-up gas stream is mixed with the injection
stream;
Default: 0.

13. production type that is used to define the rate under re-injection or voidage replacement
control:

• W – re-injection or voidage replacement rate is controlled by production of well,

defined in parameter 14;
• G – re-injection or voidage replacement rate is controlled by production of group,
defined in parameter 14.

Default:

• if parameter 2 is WV: W;
• if parameter 2 is GV: G.

12.19.52. WWAG 1616

Keywords for formats tN, E1, E3 19.1

14. name of the production well or group that controls the re-injection or voidage replace-
ment rate. If parameter 13 is set to W the name of a production well should be specified.
If parameter 13 is set to G the name of a group of wells should be specified;
Default: for injected fluids WV or GV in parameter 2 it is selected the source name
produced the fluid composition specified in parameter 3.

15. gas rate that is subtracted from the re-injection rate target (METRIC: sm3 /day, FIELD:
Msc f /day). This is important only for re-injection of a fraction of a named well’s
production. The well specified in parameter 1 attempts to inject at a rate equal to the
re-injection fraction multiplied by the production rate of the well specified in parameter
14, minus the rate set in parameter 15;

16. VFP table number for the injector (the keyword VFPINJ, see 12.19.65);

17. well stream which will be used as make-up gas. IGNORED, this is an E1/E3 compati-
bility field;

18. the way in which re-injection or voidage replacement fraction in parameter 12 is to be

interpreted:

• S is the re-injection. Reinject a fraction of surface volume production;

• R is the voidage replacement. Replace a fraction of reservoir volume production;
• Default: S.

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
– gas etc.

Example 2.

12.19.52. WWAG 1617

Keywords for formats tN, E1, E3 19.1

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.19.52. WWAG 1618

Keywords for formats tN, E1, E3 19.1

12.19.53. WHISTCTL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies parameters for all History Matching wells (WCONHIST
(see 12.19.43) – history matching producers, WCONINJH (see 12.19.47) – history match-
ing injectors. The data should be terminated with a slash /.

The following parameters should be entered:

1. new control which will be applied to all wells specified in WCONHIST (see 12.19.43)
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 (at conditions defined by the
13th parameter of WELSPECS, see 12.19.3);
• NONE – no new control. Control specified in WCONHIST (see 12.19.43) 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.19.43) 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.19.53. WHISTCTL 1619

Keywords for formats tN, E1, E3 19.1

12.19.54. WCUTBACK

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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 the symbol /. All data should be terminated with a final slash /.
One data line consists of the following data:

1. name of well (or number),

2. water cut upper limit for producer rate cutback (METRIC: sm3 /sm3 , FIELD: stb/stb)
(0 switches off this limit);
Default: no limit.

3. gas-oil ratio upper limit for producer rate cutback (METRIC: sm3 /sm3 , FIELD:
Msc f /stb) (0 switches off this limit);
Default: no limit.

4. gas-liquid ratio upper limit for producer rate cutback (METRIC: sm3 /sm3 , FIELD:
Msc f /stb) (0 switches off this limit);
Default: no limit.

5. water-gas ratio upper limit for producer rate cutback (METRIC: sm3 /sm3 , FIELD:
stb/Msc f ) (0 switches off this limit);
Default: no 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.

12.19.54. WCUTBACK 1620

Keywords for formats tN, E1, E3 19.1

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 well’s current flow rate, multiplied by the cutback
factor specified in parameter 6;

8. grid block pressure limit for well rate cutback (METRIC: barsa, FIELD: psia). Applied
to any block containing an open connection to the well. This is treated as an upper limit
for injection wells of lower limit for producers.
A value of 0.0 or > 1.0E19 switches off this limit;

9. grid block pressure limit for reversing the cutback process (METRIC: barsa, FIELD:
psia). Applied to any block containing an open connection to the well. This is treated
as a lower limit for injection wells or upper limit for producers.
A value of 0.0 or > 1.0E19 switches off this limit.
Default: 0.

10. water cut lower limit (METRIC: sm3 /sm3 , FIELD: stb/stb) for reversing the cutback
process for producers only.
A value of 0.0 turns off this limit.
Default: 0.

11. gas-oil ratio lower limit (METRIC: sm3 /sm3 , FIELD: Msc f /stb) for reversing the
cutback process for producers only.
A value of 0.0 turns off this limit.
Default: 0.

12. gas-liquid ratio lower limit (METRIC: sm3 /sm3 , FIELD: Msc f /stb) for reversing the
cutback process for producers only.
A value of 0.0 turns off this limit.
Default: 0.

13. water-gas ratio lower limit (METRIC: sm3 /sm3 , FIELD: Msc f /stb) for reversing the
cutback process for producers only.
A value of 0.0 turns off this limit.
Default: 0.

14. cutbacks can be removed (YES) or kept (NO) when the well is worked out:

• YES – if the well is worked over after exceeding an economic limit defined by
keywords CECON (see 12.19.80),WECON (see 12.19.74), any cutbacks fulfilled on
the well are completely reversed by removing the rate limit on the control phase
specified by 7-th parameter;

12.19.54. WCUTBACK 1621

Keywords for formats tN, E1, E3 19.1

• NO – any cutbacks made to the well do not change (unless reversed by the appli-
cation of cutback reversal limits);
• Default: NO.

The instruction applies to both this keyword and the keyword WBHGLR (see 12.19.57).
If WBHGLR (see 12.19.57) has been entered previously, this parameter overwrites 8-th
parameter used in that keyword. If parameter is entered subsequently, its 8-th parameter
overwrites this parameter.

Example
WCUTBACK
1095 0.7 3.0 2* 0.8 OIL /
/

12.19.54. WCUTBACK 1622

Keywords for formats tN, E1, E3 19.1

12.19.55. WCUTBACKX

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword allows to flexibly specify 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 the symbol /. All data should be terminated with a final slash /.
One data line consists of the following data:

1. name of well (or number) or well list name defined via WLIST (see 12.19.33);

2. 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;
• OFF – disable all previous WCUTBACKX operations for this well.

Default: OFF.

3. rate cutback factor (the ratio of reduced flow rate to current flow rate), the value varies
from 0 to 1;
Default: 1.

4. under control parameter. If the control phase is not OFF it should be specified explicitly.
Moreover, it can be specified by user via UDQ (see 12.19.165).

• WCT – Watercut;
• GOR – Gas-oil ratio;
• GGLR – Gas-liquid ratio;
• GWR – Gas-water ratio;
• BLKP – Block pressure (METRIC: bars, FIELD: psi);
• STRA – Steam rate (only for thermal model) (METRIC: sm3 /day, FIELD:
stb/day).

12.19.55. WCUTBACKX 1623

Keywords for formats tN, E1, E3 19.1

5. direct limit of the under control parameter. It can be value or specified using UDQ
(see 12.19.165). The reduced rate is multiplied by rate cutback factor given by 3-rd
parameter.
Default: no limitation.

6. reversal limit of the under control parameter. It can be value or specified using UDQ
(see 12.19.165). The reduced rate is divided by rate cutback factor given by 3-rd pa-
rameter.
Default: no limitation.

7. cutbacks can be removed (YES) or kept (NO) when the well is worked out:

• YES – if the well is worked over after exceeding an economic limit defined by
keywords CECON (see 12.19.80),WECON (see 12.19.74), any cutbacks fulfilled on
the well are completely reversed by removing the rate limit on the control phase
specified by 2-nd parameter;
• NO – any cutbacks made to the well do not change (unless reversed by the appli-
cation of cutback reversal limits);
• Default: NO.

The instruction applies to both this keyword and the keyword WBHGLR (see 12.19.57).
If WBHGLR (see 12.19.57) has been entered previously, this parameter overwrites 8-th
parameter used in that keyword. If parameter is entered subsequently, its 8-th parameter
overwrites this parameter.

Example
WCUTBACKX
W1 WAT 0.8 STRA 250 100 /
/

In this example water rate will be multiplied by 0.8 if the steam rate exceeds 250 (MET-
RIC: sm3 /day, FIELD: stb/day) and divided by 0.8 the steam rate becomes lower than 100
(METRIC: sm3 /day, FIELD: stb/day).

12.19.55. WCUTBACKX 1624

Keywords for formats tN, E1, E3 19.1

12.19.56. GCUTBACK

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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 the symbol /. All data should be terminated with a final slash /.
One data line consists of the following data:

1. name of group or group mask defining a subset of groups with common prefix (should
end with an asterisk *),

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);
Default: no limit (1.0E20).

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);
Default: no limit (1.0E20).

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);
Default: no limit (1.0E20).

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);
Default: no limit (1.0E20).

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.

12.19.56. GCUTBACK 1625

Keywords for formats tN, E1, E3 19.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 group’s current flow rate of that phase,
multiplied by the cutback factor (parameter 6). The group’s production rate target is met
by guide rate control GCONPROD (see 12.19.86) (unless the group is under GCONPRI,
see 12.19.89).

Example
GCUTBACK
'FIELD' 1* 1* 1* 55E-3 0.90 'GAS' /
/

12.19.56. GCUTBACK 1626

Keywords for formats tN, E1, E3 19.1

12.19.57. WBHGLR

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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 WEL-
SPECS, see 12.19.3).

The keywords works analogously to WCUTBACK (see 12.19.54) and WECON

(see 12.19.74).
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 well’s current flow rate of that phase, multiplied by the cutback factor
(parameter 4).
Reversing the cutback process: if well’s GLR at bottom hole pressure is below then parameter
3, then the rate will nor be reduced.

The keyword can be followed by an arbitrary number of data lines. Each data line should
be terminated with the symbol /. All data should be terminated with a final slash /.
One data line consists of the following data:
1. name of well (or number), or well list name defined via WLIST (see 12.19.33);

2. upper limit bottom hole GLR for well rate cutback (METRIC: rm3 /rm3 , FIELD:
rb/rb);
Default: 1e20.

3. lower limit bottom hole GLR for reversing the cutback process (METRIC: rm3 /rm3 ,
FIELD: rb/rb)
Default: 0.

4. rate cutback factor (the ratio of reduced flow rate to current flow rate), the value should
be less than 1 (the same cutback factor is applied also in the keyword WCUTBACK
(see 12.19.54). If WCUTBACK (see 12.19.54) is specified, then this parameter over-
writes parameter 6 of WCUTBACK (see 12.19.54). Or if WCUTBACK (see 12.19.54) is
specified later, then its 6-th parameter overwrites the parameter of WBHGLR);
Default: 1 or 6-th parameter of WCUTBACK (see 12.19.54) (is it was previously speci-
fied).

5. 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):

12.19.57. WBHGLR 1627

Keywords for formats tN, E1, E3 19.1

• OIL – reduced oil rate;

• WAT – reduced water rate;
• GAS – reduced gas rate;
• LIQ – reduced liquid rate;
• RESV – reduced reservoir fluid volume rate;
• Default: RESV or 7-th parameter of WCUTBACK (see 12.19.54), if it was previ-
ously specified.

The same control phase is applied also in the keyword WCUTBACK (see 12.19.54). If
WCUTBACK (see 12.19.54) is specified, then this parameter overwrites parameter 7 of
WCUTBACK (see 12.19.54). Or if WCUTBACK (see 12.19.54) 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;
Default: 1e20.

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.19.3);
• Default: NONE or 7-th parameter of WECON (see 12.19.74), if it was previously
specified.

Example
WBHGLR
1095 0.25 0.09 0.7 GAS /
/

12.19.57. WBHGLR 1628

Keywords for formats tN, E1, E3 19.1

12.19.58. WTMULT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword is used to multiply control or limit value for the well, defined by WCON-
PROD (see 12.19.42), WCONINJE (see 12.19.44) by a multiplying factor.

The keyword can be followed by an arbitrary number of data lines. Each data line should
be terminated with the symbol /. All data should be terminated with a final slash /.
One data line consists of the following data:

1. name of well (or number), or well list name defined via WLIST (see 12.19.33),

2. control or limit to be changed are listed below. This parameter can be specified by user
as UDA using UDQ (see 12.19.165) and UDADIMS (see 12.1.45). If UDA is used the
values in brackets specify the control quantity.

• ORAT [1] – oil rate;

• WRAT [2] – water rate;
• GRAT [3] – gas rate;
• LRAT [4] – liquid rate;
• RESV [6] – reservoir fluid volume rate;
• BHP [7] – bottom hole pressure;
• THP [8] – tubing head pressure (non zero VFP table number should be specified);
• LIFT [9] – artificial lift quantity (non zero VFP table number should be specified);
• GUID [10] – guide rate (for wells under group control). Can be changed only is
was previously defined by user in the keyword WGRUPCON (see 12.19.94).
• CVAL [11] – calorific rate;
• NGL [12] – nature gas liquid rate (NGL).

3. multiplying factor for this control or limit. Can be set as UDA via UDQ (see 12.19.165)
and UDADIMS (see 12.1.45);

4. number of times multiplication will be performed. This parameter is used only if 3-rd
parameter is set as UDA;
Default: 1.

12.19.58. WTMULT 1629

Keywords for formats tN, E1, E3 19.1

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.19.58. WTMULT 1630

Keywords for formats tN, E1, E3 19.1

12.19.59. WTADD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword is used to increase control or limit value for the well, defined by WCON-
PROD (see 12.19.42), WCONINJE (see 12.19.44) by a specified value.

The keyword can be followed by an arbitrary number of data lines. Each data line should
be terminated with the symbol /. All data should be terminated with a final slash /.
One data line consists of the following data:

1. name of well (or number), or well list name defined via WLIST (see 12.19.33),

2. control or limit to be changed:

• ORAT – oil rate;

• WRAT – water rate;
• GRAT – gas rate;
• LRAT – liquid rate;
• BHP – bottom hole pressure;
• 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.19.94).
• 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: 1.

Example
WTADD
B3 GRAT -17740 /
In the example gas control value decreased by 17740.

12.19.59. WTADD 1631

Keywords for formats tN, E1, E3 19.1

12.19.60. WELTARG

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword resets the target or limit value without respecifying all other quantities
required by the control keywords WCONPROD (see 12.19.42) or WCONINJE (see 12.19.44).
These other quantities remain unchanged, including the open/shut status of the well. The
well control data should be initially specified using WCONPROD (see 12.19.42), WCONINJE
(see 12.19.44).
For the wells that work in history matching mode (WCONHIST (see 12.19.43), WCON-
INJH, see 12.19.47) BHP limit can be changed, THP limit, 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.

A set of data for every well should be terminated with a slash /. All data should be
terminated with a final slash /.
The following data should be specified:

1. well name, well name template, or well list name defined via WLIST (see 12.19.33), or
well list template. A template enclosed in quotes is used to refer to multiple wells or
well lists. Well list names should be enclosed in quotes and begin with an asterisk (*);

2. control or limit quantity to be changed:

• ORAT – oil rate;

• WRAT – water rate;
• GRAT – gas rate;
• LRAT – liquid rate;
• RESV – reservoir fluid volume rate (reservoir conditions);
• BHP – bottom hole pressure;
• THP – tubing head pressure (non zero VFP table number should be specified). This
option can be used for wells specified via keywords WCONPROD (see 12.19.42),
WCONINJE (see 12.19.44) and can not be used for wells specified via WCONHIST
(see 12.19.43), WCONINJH (see 12.19.47). To change the limit for wells working
in history matching mode use the option TARGTHP;

12.19.60. WELTARG 1632

Keywords for formats tN, E1, E3 19.1

• TARGTHP – tubing head pressure (non zero VFP table number should be specified).
This option allows to change THP limit for wells specified via keywords WCON-
PROD (see 12.19.42), WCONINJE (see 12.19.44), WCONHIST (see 12.19.43),
WCONINJH (see 12.19.47);
• VFP – VFP table number (VFPPROD (see 12.19.66), VFPINJ (see 12.19.65), VFP-
CORR, see 12.19.71);
• LIFT – artificial lift quantity (non zero VFP table number should be specified);
• WGRA – wet gas production rate (for models in E3 format);
• TMRA – molar rate;
• STRA – steam production rate (can be used in THERMAL (see 12.1.54) option only
for models in E3 format);
• SATP – saturation pressure offset (available only if THERMAL (see 12.1.54) is spec-
ified for models in E3 format);
• SATT – saturation temperature offset (available only if THERMAL (see 12.1.54) is
specified for models in E3 format);
• GUID – guide rate (for wells under group control);
• REIN – re-injection fraction (for models in E3 format);
• CVAL – calorific production rate (for models in E3 format);
• NGL – natural gas liquid rate (for models in E3 format);
• DEPTH – reference depth for the well specified earlier by the 5-th parameter of the
keyword WELSPECS (see 12.19.3);
• bottom hole phase velocity. Non-negative value should be entered to set this limit.
Negative value should be entered to remove the limit. Phase velocities are cal-
culated using diameter of top connection (can be open or shut, not important),
bottom hole pressure and temperature (if available). The following parameters can
be specified:
◦ FLOWW – bottom hole velocity control for water;
◦ FLOWO – bottom hole velocity control for oil;
◦ FLOWL – bottom hole velocity control for liquid;
◦ FLOWG – bottom hole velocity control for gas;
◦ FLOWV – bottom hole voidage velocity control.

3. new value of this quantity. It can be specified by the keyword UDQ (see 12.19.165),
unless the parameter is VFP, GUID, or CVAL.

For a well on BHP control, WELTARG will simply reset control value.
For a well on rate control, WELTARG will change the BHP limit.

12.19.60. WELTARG 1633

Keywords for formats tN, E1, E3 19.1

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.19.60. WELTARG 1634

Keywords for formats tN, E1, E3 19.1

12.19.61. WELLTARG

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword is a full analog of the keyword WELTARG (see 12.19.60).

12.19.61. WELLTARG 1635

Keywords for formats tN, E1, E3 19.1

12.19.62. WELCNTL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword is used to alter the control mode and target value for a well without respec-
ifying all the other quantities required by the control keywords WCONPROD (see 12.19.42)
and WCONINJE (see 12.19.44). These other quantities remain unchanged, including the
open/shut status of the well. The well control data should be initially specified using WCON-
PROD (see 12.19.42), WCONINJE (see 12.19.44), WCONHIST (see 12.19.43) or WCONINJH
(see 12.19.47).
This keyword is similar to keyword WELTARG (see 12.19.60), but in contrast to it the
keyword WELCNTL can change the control mode (when parameter 3 is defaulted), not just an
operating target or limit. Changing the control mode, particularly when the operating target is
not changed, can be useful when switching from history matching mode to predictive mode
during a simulation.
The keyword is followed by any number of records. Each data line should be terminated
with the symbol /. All data should be terminated with a final slash /.
Each record contains the following data:
1. well name, well name template, or well list name defined via WLIST (see 12.19.33), or
well list template. A template enclosed in quotes is used to refer to multiple wells or
well lists. Well list names should be enclosed in quotes and begin with an asterisk (*);
2. new control mode for the well:
• ORAT – oil rate;
• WRAT – water rate;
• GRAT – gas rate;
• LRAT – liquid rate;
• RESV – reservoir fluid volume rate;
• BHP – bottom hole pressure;
• THP – tubing head pressure (non zero VFP table number should be specified). This
option can be used for wells specified via keywords WCONPROD (see 12.19.42),
WCONINJE (see 12.19.44) and can not be used for wells specified via WCONHIST
(see 12.19.43), WCONINJH (see 12.19.47). To change the limit for wells working
in history matching mode use the option TARGTHP;
• TARGTHP – tubing head pressure (non zero VFP table number should be spec-
ified). This option allows to change THP limit for wells specified via key-
words WCONPROD (see 12.19.42), WCONINJE (see 12.19.44), WCONHIST
(see 12.19.43), WCONINJH (see 12.19.47);

12.19.62. WELCNTL 1636

Keywords for formats tN, E1, E3 19.1

• WGRA – wet gas rate (for models in E3 format);

• STRA – steam rate (available only if THERMAL (see 12.1.54) is specified for
models in E3 format);
• SATP – saturation pressure offset (available only if THERMAL (see 12.1.54) is
specified for models in E3 format);
• SATT – saturation temperature offset (available only if THERMAL (see 12.1.54) is
specified for models in E3 format);
• CVAL – calorific production rate (for models in E3 format);
• REIN – reinjection fraction (for models in E3 format);
• NGL – NGL rate (for models in E3 format).

3. new value of the operating target for this control mode.

Note: This keyword is introduced in order to simplify the transition from history matching
mode to prediction mode. However, if this keyword is used to change the control mode of a
well which was previously specified using keywords WCONHIST (see 12.19.43) or WCON-
INJH (see 12.19.47), then the old historical target (e.g., oil rate) does not change. This may
results in the interference between old limit and new control mode specified by the key-
word WELCNTL and causes the well switch to the old control mode. In order to avoid this,
set instead the old limit a large value (e.g., 1.0E+8) by using the WELTARG (see 12.19.60)
keyword.
Example
WELCNTL
'GP*' BHP 500/
/
In this example for wells with names starting with ”GP” the keyword reset BHP control
value.

12.19.62. WELCNTL 1637

Keywords for formats tN, E1, E3 19.1

12.19.63. GRUPTARG

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword resets control or limit value for the well, defined by GCONPROD
(see 12.19.86), GCONPRI (see 12.19.89).
An arbitrary number of data lines could be entered (ended with /). All data should be
terminated with a final slash /.
The following options are available:

1. name of group or group mask defining a subset of groups with common prefix (should
end with an asterisk *),

2. control or limit to be changed:

• ORAT – oil rate;

• WRAT – water rate;
• GRAT – gas rate;
• LRAT – liquid rate;
• RESV – liquid rate in reservoir conditions according to the 13th parameter of
WELSPECS (see 12.19.3);
• WGRA – wet gas rate;
• TM – total molar rate (including water molar rate).

3. new value of this control or limit.

Example
GRUPTARG
GROUP1 LRAT 30000/
/

12.19.63. GRUPTARG 1638

Keywords for formats tN, E1, E3 19.1

12.19.64. WELPI

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies productivity (injectivity) index (PI) for the wells. Well connections
should be specified via the keywords COMPDAT (see 12.19.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 drawdown. Drawdown is the difference between well’s BHP and the reservoir pressure at
well’s drainage radius.)

An arbitrary number of data lines could be entered (ended with /). All data should be
terminated with a final slash /.
The following parameters are to be specified in one data line:

1. name of well (or number), or well list name defined via WLIST (see 12.19.33),

2. steady-state productivity (injectivity) index (PI) (METRIC: sm3 /day-bar , FIELD:

stb/day-psi for liquid or Msc f /day-psi for gas). Can be specified by user via UDQ
(see 12.19.165).

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.19.64. WELPI 1639

Keywords for formats tN, E1, E3 19.1

12.19.65. VFPINJ

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword inputs a table of BHP values versus FLO (oil, water or gas injection rate),
THP (tubing head pressure) for injectors.
The implementation of VFP tables, corresponding formulas and keywords are described in the
section 6. VFP tables generation.
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 VF-
PINJ 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 val-
ues). 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
• table number (a number between 1 and the 3-rd parameter of VFPIDIMS,
see 12.1.33);

12.19.65. VFPINJ 1640

Keywords for formats tN, E1, E3 19.1

• 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 E3 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 water,
Msc f /day – for gas); for models in E3 format – molar rate (METRIC: kg-mol/day,
FIELD: lb-mol/day)) (NFLO values), entered in ascending order, terminated with a
slash (/) (the number NFLO should not be greater than the 1-st parameter of VFPIDIMS,
see 12.1.33).

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.33).

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.

12.19.65. VFPINJ 1641

Keywords for formats tN, E1, E3 19.1

Example
VFPINJ
107 3.48330E+003 'WGV' 'THP' 'METRIC' 'BHP'/

2.00000E+005 3.00000E+005 6.00000E+005 1.00000E+006

1.50000E+006 2.50000E+006 /
2.50000E+002 4.00000E+002 5.00000E+002 6.00000E+002 /

1 3.36337E+002 3.35544E+002 3.31321E+002 3.21264E+002

3.01044E+002 2.27975E+002 /
2 5.07951E+002 5.07332E+002 5.04060E+002 4.96369E+002
4.81272E+002 4.31438E+002 /
3 6.17087E+002 6.16519E+002 6.13527E+002 6.06516E+002
5.92824E+002 5.48292E+002 /
4 7.24091E+002 7.23555E+002 7.20743E+002 7.14169E+002
7.01368E+002 6.60044E+002 /

This example defines a VFP table for water injector.

12.19.65. VFPINJ 1642

Keywords for formats tN, E1, E3 19.1

12.19.66. VFPPROD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

i In tNavigator VFP tables can be generated automatically using the selected

correlation via the keyword VFPCORR (see 12.19.71).
The implementation of VFP tables, corresponding formulas and keywords are described
in the section 6. VFP tables generation.
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 VF-
PPROD keyword.

In addition, VFP tables is used for simulation of gas lift (2.14.9).

The table consists of the following records of data, each record terminated with a slash (/).
1. Basic data:

1.1. table number (a number between 1 and the 6-th parameter of VFPPDIMS,
see 12.1.34);
1.2. bottom hole datum depth for this table (METRIC: m, FIELD: f t );
1.3. definition of variable FLO (OIL – Oil production rate, LIQ – Liquid (oil + water)
production rate, GAS – Gas production rate; for models in E3 format: WG –
Hydrocarbon wet gas rate, TM – total molar rate);
1.4. definition of variable WFR (WOR – Water-oil ratio, WCT – Water cut (water-
liquid ratio), WGR – Water-gas ratio; for models in E3 format: WWR – Water-wet
gas ratio, WTF – water molar fraction);
1.5. definition of variable GFR (GOR – Gas-oil ratio, GLR – Gas-liquid ratio, OGR –
Oil-gas ratio; for models in E3 format: MMW – Mean molecular weight);

12.19.66. VFPPROD 1643

Keywords for formats tN, E1, E3 19.1

1.6. definition of variable THP (only THP value is supported);

1.7. definition of variable ALQ (GRAT – lift gas injection rate (for gas lift), IGLR –
injection gas/liquid ratio (for gas lift), PUMP – pump rating, COMP – compressor
power);
1.8. units of this VFP table (METRIC or FIELD);
1.9. definition of the tabulated quantity in the body of the table, parameter number 7
(BHP – bottom hole pressure, TEMP – tubing head temperature THT);
Default: BHP – bottom hole pressure.

2. FLO (flow rate) values (METRIC: sm3 /day, FIELD: stb/day – for oil and water,
Msc f /day – for gas); for models in E3 data format – molar rate (METRIC: kg-mol/day,
FIELD: lb-mol/day), entered in ascending order, terminated with a slash (/) (NFLO
values in total; the number NFLO should not be greater than the 1-st parameter of
VFPPDIMS, see 12.1.34).

3. THP values (METRIC: barsa, FIELD: psia), entered in ascending order, terminated
with a slash (/) (NTHP values in total; the number NTHP should not be greater than the
2-nd parameter of VFPPDIMS, see 12.1.34).

4. WFR values (METRIC: sm3 /sm3 , FIELD: stb/stb – WOR, WCT, stb/Msc f – WGR),
entered in ascending order, terminated with a slash (/) (NWFR values in total; the num-
ber NWFR should not be greater than the 3-rd parameter of VFPPDIMS, see 12.1.34).

5. GFR values (METRIC: sm3 /sm3 , FIELD: Msc f /stb – GOR, GLR, stb/Msc f – OGR);
for models in E3 data format – mean molecular weight (METRIC: kg/kg-mol , FIELD:
lb/lb-mol ), entered in ascending order, terminated with a slash (/) (NGFR values in
total; the number NGFR should not be greater than the 4-th parameter of VFPPDIMS,
see 12.1.34).

6. ALQ values. Units depend on ALQ definition as follows.

GRAT – METRIC: sm3 /day, FIELD: Msc f /day,
IGLR – METRIC: sm3 /sm3 , FIELD: Msc f /stb,
PUMP or COMP – same as in the keyword that defines ALQ for the wells: WCONHIST
(see 12.19.43), WCONPROD (see 12.19.42), etc.)
The values are entered in ascending order, terminated with a slash (/) (NALQ values in
total; the number NALQ should not be greater than the 5-th parameter of VFPPDIMS,
see 12.1.34).

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);

12.19.66. VFPPROD 1644

Keywords for formats tN, E1, E3 19.1

• 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.

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.

Extrapolation of VFP tables

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

12.19.66. VFPPROD 1645

Keywords for formats tN, E1, E3 19.1

that the given values in the table cover all cases that may occur during your model calculation.

To calculate, for example, a rate distribution between group’s members when group con-
trol turns on, it is required to calculate a well’s potential, i.e. its production rate without any
limitations. Probably, the calculation of well’s potential after extrapolation results in incorrect
distribution of rates under group control.

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.

12.19.66. VFPPROD 1646

Keywords for formats tN, E1, E3 19.1

12.19.67. VFPCHK

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets the threshold BHP value (METRIC: barsa, FIELD: psia) to use when
checking the VFP tables for internal consistency. The data should be terminated with a slash
/.
The implementation of VFP tables, corresponding formulas and keywords are described
in the section 6. VFP tables generation.
The records having BHP equal to or above the threshold value are ignored in VFP table
check.
The keyword should be specified before VFPPROD (see 12.19.66).
VFP tables for producer wells are checked to ensure that the curves of BHP
i vs. flow rate at adjacent THP values do not intersect. If they do (that is, if the
BHP increases as THP decreases), a warning will be printed.
Default: 1e10.
Example
VFPCHK
400 /

12.19.67. VFPCHK 1647

Keywords for formats tN, E1, E3 19.1

12.19.68. VFPCHECK

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword instructs the simulator to check the VFP tables (VFPPROD (see 12.19.66)
and VFPINJ, see 12.19.65) for consistency against the given PVT properties. The implementa-
tion of VFP tables, corresponding formulas and keywords are described in the section 6. VFP
tables generation.
The data should be terminated with a slash /. The following parameters must be specified:

1. water density at standard conditions (METRIC: kg/m3 , FIELD: lb/ f t 3 );

2. molecular weight of water (METRIC: kg/kg-mol, FIELD: lb/lb-mol);

3. standard pressure (METRIC: barsa, FIELD: psia);

4. standard temperature (METRIC: ◦ C, FIELD: ◦ F);

5. unit system;

6. number of components.

If an inconsistency in some of these properties is encountered, a warning message is

thrown, for example:
Mismatch in number of components. VFP has 8, the model has 6.
Example
VFPCHECK
999.2 18.0 1.013 15.0 METRIC 8 /
This example specifies that the VFP tables are calculated in metric units considering water
density of 999.2 kg/m 3 , water molar mass of 18.0 kg/kg-mol, standard pressure of 1.013
Barsa, standard temperature of 15 ◦ C, and 8 components.

12.19.68. VFPCHECK 1648

Keywords for formats tN, E1, E3 19.1

12.19.69. VFPTABL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword sets interpolation method for Artificial Lift Quantity ALQ in VFP tables.
The data should be terminated with a slash /.
By default all parameter in VFP tables (FLOW, THP, WFR, GFR, ALQ) are interpolated
linearly.
The implementation of VFP tables, corresponding formulas and keywords are described in the
section 6. VFP tables generation.
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 Artificial 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.19.69. VFPTABL 1649

Keywords for formats tN, E1, E3 19.1

12.19.70. WVFPEXP

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.
The implementation of VFP tables, corresponding formulas and keywords are described
in the section 6. VFP tables generation.
Any number of data lines can be specified. Each data line should be terminated with the
symbol /. All data should be terminated with a final slash /.
One line contains the following parameters:

1. name of well (or number), or well list name defined via WLIST (see 12.19.33),

2. implicit or explicit flag:

• IMP – VFP table for the well will be interpolated implicitly (latest values 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);
• Default: IMP.

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;
Default: NO.

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.

• YES1 – control can be considered satisfied;

• YES2 – same as YES1, added for compatibility;
• NO – then THP value will be calculated at calculated fluid rate value. If a new
THP value doesn’t satisfy control one, then well will be closed;

12.19.70. WVFPEXP 1650

Keywords for formats tN, E1, E3 19.1

• Default: NO.

5. the way to extrapolate VFP table values for water fracture, gas fracture and ALQ (this
parameter can be set for models in E3 format only):

• WG – constant values for water and gas fraction, linear interpolation for ALQ;
• WGA – constant values for water and gas fraction and ALQ;
• NONE – linear interpolation for water and gas fraction and ALQ;
• Default: WG.

Example
WVFPEXP
p45 1* YES /
p46 1* YES /
/

12.19.70. WVFPEXP 1651

Keywords for formats tN, E1, E3 19.1

12.19.71. VFPCORR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keywords sets correlation properties for producers. VFPPROD (see 12.19.66) table is
calculated by this data. Correlation methods description and calculation formulae are in the
section VFP tables generation.
Any number of data lines can be specified. Each data line should be terminated with the
symbol /. All data should be terminated with a final slash /.
The following parameters should be specified:

1. table number;

2. table type:

• PROD – producing;
• Default: PROD.

3. correlation type (correlation formulae are in the section VFP tables generation):

• PA – Petalaz & Aziz;

• HB – Hagedorn & Brown;
• BB – Beggs & Brill;
• O – Orkiszewski;
• G – Gray;
• AGF – Aziz, Govier & Fogarasi;
• MB – Mukherjee & Brill;
• Default: PA.

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 57). 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.19.66).
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.19.71. VFPCORR 1652

Keywords for formats tN, E1, E3 19.1

Figure 57. Well bore illustration

7. MD – Measured Depth (well bore length) (METRIC: m, FIELD: f t ) (parameter l =

a + b on the picture 57). 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 57).

This is the TVD of the heel of the well;

10. PVT region number.

For the Beggs & Brill correlation α angle is used (see the picture 57). This angle is cal-
culated from the triangle (as we know its sides).

! If well trajectory is not specified a correlation will be calculated based on

parameters given in the VFPCORR.

!
If the keyword WELLTRACK (see 12.19.9) is specified then the correlation is
calculated along well trajectory up to depth given in the VFPCORR. If well
trajectory is shorter than depth specified in VFPCORR then the depth of well
trajectory point is used in the VFPCORR.

12.19.71. VFPCORR 1653

Keywords for formats tN, E1, E3 19.1

Example
VFPCORR
1 1* HB 0.0015 0.05 2200 3437 40 2200 1 /
/
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.19.71. VFPCORR 1654

Keywords for formats tN, E1, E3 19.1

12.19.72. WELLTCB

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword specifies well temperature cutback tables. Each table is terminated by a
slash /. Each table consists of 2 columns of data:

• the well name;

• the corresponding cutback table number.

If a table number is set equal to zero there is no cutback for this well. The table number
should be less or equal to the number of well cutback tables in the run specified by the
keyword TCBDIMS (see 12.1.47).
Default: 0.

This keyword can be repeated at the following time step to assign different tables to a
well.
See also the keyword WELLTCBT (see 12.19.73).
Example
TCBDIMS
1 10 /
...

WELLTCB
I1 1 /
/

In this example a well I1 uses the temperature cutback table with number 1.

12.19.72. WELLTCB 1655

Keywords for formats tN, E1, E3 19.1

12.19.73. WELLTCBT

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword specifies tables of temperature cutback factors. Each table is terminated by
a slash /. Each table consists of 2 columns of data:
• the temperature (METRIC: ◦ C, FIELD: ◦ F).
Temperature values should be larger than zero and monotonically increase down the
column;
• The corresponding cutback factor. Factor values varies from 0 and 1 and should decrease
down the column. The first value in the column should be 1.
The number of tables should be equal to the number of well cutback tables in the run,
specified by the keyword TCBDIMS (see 12.1.47). The number of table rows should be less
than or equal to the maximum number of rows of data specified by the keyword TCBDIMS
(see 12.1.47).
A cutback factor is used to multiply the maximum or target oil rate, gas rate, water
rate, liquid rate, voidage rate, and hydrocarbon rate for each well specified in the keyword
WELLTCB (see 12.19.72).
The cutback factor used at the next time step is not interpolated between the values spec-
ified in the tables. The cutback factor specified at a particular temperature is used until the
next highest temperature is reached.
Example
TCBDIMS
1 10 /

WELLTCBT
170 1.0
250 0.5
290 0.25 /

WELLTCB
I1 1 /
/

In this example a table of temperature cutback factors is I1. The factor of 1 (i.e. there
is no cutback) is applied for all temperatures up to 250, then a factor of 0.5 is applied for
all temperatures from 250 to 290. The factor of 0.25 is used for all temperatures higher than
290.

12.19.73. WELLTCBT 1656

Keywords for formats tN, E1, E3 19.1

12.19.74. WECON

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword defines the economic limit for production wells. Economic control possibil-
ities of tNavigator are summarized in the section 2.14.3.
The use of this keyword may result in differences between tNavigator’s results calculated
using different number of cores and a deviation of tNavigator results from results obtained by
other simulators (see section 7.2).
The following parameters have to be specified (terminated with a slash /):

1. name of well (or number), or well list name defined via WLIST (see 12.19.33),

2. lower economic limit of oil rate (METRIC: sm3 /day, FIELD: stb/day), in case of
violation the well will be SHUT or STOP according to the 9-th parameter of the keyword
WELSPECS (see 12.19.3);
Default: 0.

3. lower economic limit of gas rate (METRIC: sm3 /day, FIELD: Msc f /day), in case of
violation well will be SHUT or STOP according to the 9-th parameter of the keyword
WELSPECS (see 12.19.3);
Default: 0.

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;
Default: 0 (no limit).

5. upper economic limit of gas-oil ratio (METRIC: sm3 /sm3 , FIELD: Msc f /stb).
tNavigator additional functionality: if negative value −X is specified, the value X
will be used as lower economic limit of gas-oil ratio;
Default: no limit.

6. upper economic limit of water-gas ratio (METRIC: sm3 /sm3 , FIELD: stb/Msc f ).
tNavigator additional functionality: if negative value −X is specified, the value X
will be used as lower economic limit of water-gas ratio;
Default: no limit.

7. workover action for watercut violation, gas-oil ratio violation, water-gas ratio violation
or gas-liquid ratio violation:

12.19.74. WECON 1657

Keywords for formats tN, E1, E3 19.1

• NONE – do nothing,
• CON – shut in the worst offending perforation,
• CON+ – close the worst offending perforation and all below it,
• +CON – the same as CON+,
• WELL – shut in or stop the well (9-th parameter of WELSPECS, see 12.19.3),
Default: NONE.

8. end run flag;

• NO – the run continues,

• 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;
• Default: NO.

9. name of the 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.19.228). Also there can be a non-zero waiting time of drilling rig
availability (GRUPRIG, see 12.19.233);

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.19.89). 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.19.123). Well potentials – 5.6.7.
If the well’s 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.19.89), then its potential is
checked against the minimum economic limits (which is also the case if the well
is not currently working). The well will be closed if the potential is too small.
• Default: RATE.

11. secondary maximum watercut limit. This parameter is applied according to the workover
action for watercut violation specified in 12-th parameter
Default: 0 (no limit).;

12.19.74. WECON 1658

Keywords for formats tN, E1, E3 19.1

12. workover action for secondary watercut (parameter 11) violation.

For the operations CON, CON+, WELL tNavigator works the following way.
If the workover operations were applied to the well because of the violation of the
primary water cut limit (parameter 4), then it is shut when the last connection is closed.
If the secondary water cut limit is specified then the well will be reopened at the next
time step and the secondary water cut limit will be checked instead of primarily limit.
All well’s 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,
• 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.19.3),
• 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
well’s 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.
• Default: workover action specified in the 7-th parameter.

13. upper economic limit of gas-liquid ratio (METRIC: sm3 /sm3 , FIELD: Msc f /stb).
tNavigator additional functionality: if negative value −X is specified, the value X
will be used as lower economic limit of gas-liquid ratio;
Default: no limit.

14. lower economic limit of liquid 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.19.3);
Default: 0.

12.19.74. WECON 1659

Keywords for formats tN, E1, E3 19.1

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.19.74. WECON 1660

Keywords for formats tN, E1, E3 19.1

12.19.75. WECONX

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword allows to specify economical limits of any type for producers. This keyword
is a generalization of the keyword WECON (see 12.19.74). Economical limits for injectors can
be set via WECONINJX (see 12.19.82).
Economic control possibilities of tNavigator are summarized in the section 2.14.3.
The following parameters should be specified:

1. well name/mask;

2. value to check. It can be a number or, for example, value of an expression specified by
the keyword UDQ (see 12.19.165);

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 specified by the keyword UDQ (see 12.19.165). In addition the
following parameters are available:

• ORAT – oil rate (METRIC: sm3 /day; FIELD: stb/day);

• GRAT – gas rate (METRIC: sm3 /day; FIELD: stb/day);
• WRAT – water rate (METRIC: sm3 /day; FIELD: stb/day);
• RESV – fluid (oil+gas+water) rate at reservoir conditions (METRIC: rm3 /day;
FIELD: rb/day);
• BHP – bottom hole pressure (METRIC: barsa, FIELD: psi);
• THP – tubing head pressure (METRIC: barsa, FIELD: psi);
• LRAT – liquid rate (METRIC: sm3 /day; FIELD: stb/day);
• GOR – gas–oil ratio (METRIC: ksm3 /sm3 ; FIELD: Msc f /stb);
• OGR – oil–gas ratio (METRIC: sm3 /ksm3 ; FIELD: stb/Msc f );
• WCT – watercut (METRIC: sm3 /sm3 ; FIELD: stb/stb);
• WOR – water–oil ratio (METRIC: sm3 /sm3 ; FIELD: stb/stb);
• GWR – gas–water ratio (METRIC: ksm3 /sm3 ; FIELD:Msc f /stb);
• WGR – water–gas ratio (METRIC: sm3 /ksm3 ; FIELD: stb/Msc f ).

5. workover operation:

12.19.75. WECONX 1661

Keywords for formats tN, E1, E3 19.1

• WELL – stop or shut a well;

• NONE – no action;
• CON_TOP – close the top connection;
• CON_BOTTOM – close the bottom connection;
• CON_WORST – close the worst connection.
• Default: NONE.

If no action (NONE) is set and any parameter from the list is specified in 2-nd parameter
and ’==’ (equal) is set in 3-rd parameter then the well economical limit will be canceled.

6. end calculation option:

• YES – calculation stops at the next timestep if the well is shut or stopped;
• NO – calculation will not be stopped;
• Default: NONE.

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 /.
Example
UDQ
DEFINE WUBHP WBHP /
/

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.19.165). Then it is specified that well ’WELL’ will be shut if
pressure value will fall below 100 atm.

12.19.75. WECONX 1662

Keywords for formats tN, E1, E3 19.1

12.19.76. GECONX

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword allows to specify economical limits of arbitrary type for groups of wells. This
keyword is an extension of the keyword GECON (see 12.19.121), which is used by E1/E3.
The following parameters should be specified:

1. well group name/mask;

2. value to check. It can be a number or, for example, value of an expression specified by
the keyword UDQ (see 12.19.165);

3. comparison sign (’>’ – greater, ’<’ – less, ’>=’ – greater or equal, ’<=’ – less or equal,
’==’ – equal, ’!=’ – not equal);

4. economical parameter limit value. It can be a number or, for example, value of an
expression specified by the keyword UDQ (see 12.19.165);

5. workover operation:

• ALL – shut all wells belonging to the group;

• NONE – no action;
• Default: NONE.

6. end calculation option:

• YES – calculation stops at the next time step if the wells are shut;
• NO – calculation will not be stopped;
• Default: NO.

7. [additional parameter] maximum allowed number of opened wells of the group.

Each line should be ended by a symbol /. The data should be terminated with a slash /.
This keyword has an E1/E3 compatible analogue GECON (see 12.19.121).
Maximal number of opened wells of the group is given by the last specified keyword
GECON (see 12.19.121) or GECONX.

12.19.76. GECONX 1663

Keywords for formats tN, E1, E3 19.1

Example
UDQ
DEFINE GUOPR GOPR /
DEFINE GUVAL 2500 /
/

GECONX
'FIELD' GUOPR < GUVAL ALL YES /
/

In this example a vector GUOPR equal to GOPR and a vector GUVAL equal to 2500 are
set using the keyword UDQ (see 12.19.165). The keyword GECONX (see 12.19.76) indicates
that a group of wells ’FIELD’ will be shut and a calculation will be stopped if group oil
production rate becomes lower than 2500.

12.19.76. GECONX 1664

Keywords for formats tN, E1, E3 19.1

12.19.77. WECONCMF

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets economical limits on component mole fractions for production wells.
Economic control possibilities of tNavigator are summarized in the section 2.14.3.
The following parameters should be specified:

1. well name (or number), or well list name defined via WLIST (see 12.19.33);

2. component index corresponding with the keyword COMPS (see 12.14.1);

3. maximal mole fraction of this component in the produced fluid. It can be specified by
the keyword UDQ (see 12.19.165);

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;
• Default: NONE.

5. end calculation option:

• YES – calculation stops at the next timestep if the well is shut or stopped;
• NO – calculation will not be stopped;
• Default: NONE.

Each line should be ended by symbol /. The data should be terminated with a slash /.

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.19.77. WECONCMF 1665

Keywords for formats tN, E1, E3 19.1

12.19.78. WGORPEN

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword is used to control well’s oil production rate target for each month via the
value of its previous month’s 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 doesn’t exceed maximum rate limit.

The following parameters should be specified:

1. well name (or number), or well list name defined via WLIST (see 12.19.33);

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);

5. Default: if the limit on GOR has just been turned on, then the value average GOR over
previous month is used by default, while if limit on GOR is not in use yet, then set
equal to the well’s GOR at the previous step. If the well has just been opened, then the
second value is taken by default .

Each line with data should be ended by symbol /. The data should be terminated with a
slash /.

Example
WGORPEN
vw1 60 8000 60 /
horw1 60 300000 60 /
/
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.19.78. WGORPEN 1666

Keywords for formats tN, E1, E3 19.1

12.19.79. WELLLIM

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword is an alias for WECON (see 12.19.74).

12.19.79. WELLLIM 1667

Keywords for formats tN, E1, E3 19.1

12.19.80. CECON

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword defines economic limit for production well connections. If any connection
violates one of its economic limits it will be automatically closed.
Economic control possibilities of tNavigator are summarized in the section 2.14.3.
If COMPLUMP (see 12.19.29) lumps connections into completions, the connection eco-
nomic limits are applied to completions. All connections in one completion should have the
same limits.

An arbitrary number of data lines could be entered (ended with /). All data should be
terminated with a final slash /.
The following parameters are to be specified in one data line:

1. name of well (or number), or well list name defined via WLIST (see 12.19.33),

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),
Default: no limit.

7. upper economic limit of gas-oil ratio (METRIC: sm3 /sm3 , FIELD: Msc f /stb),
Default: no limit.

8. upper economic limit of water-gas ratio (METRIC: sm3 /sm3 , FIELD: stb/Msc f ),
Default: no limit.

9. workover action for limit violation:

• CON – shut the connection,

• +CON – shut the connection and all below (the keyword COMPORD,
see 12.19.31),

12.19.80. CECON 1668

Keywords for formats tN, E1, E3 19.1

• WELL – the well will be stopped or shut (depends on parameter 9 of the keyword
WELSPECS, see 12.19.3),
• Default: CON.

10. continue checking stopped wells? IGNORED, this is an E1/E3 compatibility field,

11. lower economic limit of oil rate (in case of violation connection will be shut and all con-
nections below if it is specified in parameter 9) (METRIC: sm3 /day, FIELD: stb/day)
Default: no limit.,

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: 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.19.80. CECON 1669

Keywords for formats tN, E1, E3 19.1

12.19.81. WECONINJ

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword defines economic limit for injection wells. Economic control possibilities of
tNavigator are summarized in the section 2.14.3.
The data (for every well) should be terminated with a slash /. All data should be terminated
with a final slash /.
The following parameters are to be specified:

1. name of well (or number), or well list name defined via WLIST (see 12.19.33),

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 100 sm3 /day as minimum possible injection rate for the well i35.

12.19.81. WECONINJ 1670

Keywords for formats tN, E1, E3 19.1

12.19.82. WECONINJX

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword allows to specify economical limits of any type on injector wells. This
keyword is a generalization of the keyword WECONINJ (see 12.19.81). Economical limits for
producers can be set via WECONX (see 12.19.75).
Economic control possibilities of tNavigator are summarized in the section 2.14.3.
The following parameters should be specified:

1. well name/mask;

2. value to check. It can be a number or, for example, value of an expression specified by
the keyword UDQ (see 12.19.165);

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 an expression specified by the keyword UDQ (see 12.19.165);

5. workover operation:

• WELL – stop or shut a well;

• NONE – no action;
• Default: NONE.

6. end calculation option:

• YES – calculation stops at the next timestep if the well is shut or stopped;
• NO – calculation will not be stopped;
• Default: NO.

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 /.

12.19.82. WECONINJX 1671

Keywords for formats tN, E1, E3 19.1

Example
UDQ
DEFINE WUBHP WBHP /
/

WECONINJX
'INJ1' WUBHP > 100 WELL /
/
In the example parameter WUBHP (which is equal to the value of WBHP) is specified by
the keyword UDQ (see 12.19.165). Then it is specified that well ’INJ1’ will be shut if pressure
value will grow above 100 atm.

12.19.82. WECONINJX 1672

Keywords for formats tN, E1, E3 19.1

12.19.83. WEFAC

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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 have to be specified:

1. name of well (or number) or well list name defined via WLIST (see 12.19.33),

2. well efficiency factor

Default: 1.

3. should a well’s efficiency factor be included in calculations of the branch flows and pres-
sure losses in the Extended Network (keywords BRANPROP (see 12.19.102), NODE-
PROP, see 12.19.103):

• YES – The extended network branch pressure losses is calculated using the well’s
time averaged flow rate (well rate is multiplied by its efficiency factor).
• NO – The extended network branch pressure losses is calculated using the well’s
maximum flow (well rate is not multiplied by its efficiency factor);
• Default: YES.

Example
WEFAC
P25 .89 NO/
P12 .7 /
P13 .8 /
I* .97 /
/
In this example well P25 efficiency factor is set to 89%. A well’s 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.19.83. WEFAC 1673

Keywords for formats tN, E1, E3 19.1

12.19.84. GEFAC

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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 /.
A row has to contain the following parameters:

1. group name or group mask defining a subset of groups with common prefix (should end
with an asterisk *),

2. group efficiency factor (a part of time for which the group is working. If the group
doesn’t work for 15% of time, then its efficiency factor should be 0.85);
Default: 1.

3. does the group’s efficiency factor automatically transfer to its corresponding node in the
extended network (YES or NO)? IGNORED, this is an E1/E3 compatibility field.

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.19.84. GEFAC 1674

Keywords for formats tN, E1, E3 19.1

12.19.85. WORKTHP

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword specifies the workover procedure for the well if the well can’t 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 can’t 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 well’s connection are
shut.
If the connections are lumped into completions (COMPLUMP, see 12.19.29), then all connec-
tions is the worst completion will be closed.

An arbitrary number of data lines can be specified, each terminated with a slash /. All
data should be terminated with a final slash /.
One data line contains the following parameters:

1. name of well (or number), or well list name defined via WLIST (see 12.19.33),

2. workover procedure for the well if the well can’t 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: 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.19.85. WORKTHP 1675

Keywords for formats tN, E1, E3 19.1

12.19.86. GCONPROD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword could be specified for a well group or several groups with the same group
name root.
Group control possibilities of tNavigator are described in the section 2.14.2.

Any number of lines can be specified, each terminated with a slash /. All data should be
terminated with a final slash /.
The following parameters should be specified in one data line:

1. group name, or group mask defining a subset of groups with common prefix (should
end with an asterisk *), or FIELD (for field control)
Default: default group (group of wells with default group in WELSPECS, see 12.19.3).

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 – control by reservoir fluid volume production rate at conditions defined by
the 13th parameter of WELSPECS (see 12.19.3) (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 of E3
type),
• PBGS – surface gas production rate control (target is specified via parameter 18)
(only for models with E3 type),
• PBWS – surface water production rate control (target specified via parameter 19)
(only for models with E3 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 (speci-
fied via parameters 9 and 10);

12.19.86. GCONPROD 1676

Keywords for formats tN, E1, E3 19.1

If set to ORAT, GRAT, WRAT, or LRAT, the workover action on exceeding the maxi-
mum limit for the relevant phases is set to RATE. This overrides any other actions that
may be defined in items 7, 11, 12, and 13.

Default: NONE.
3. oil rate (or limit) (METRIC: sm3 /day, FIELD: stb/day);
Default: no rate or limit.
4. water rate (or limit) (METRIC: sm3 /day, FIELD: stb/day);
Default: no rate or limit.
5. gas rate (or limit) (METRIC: sm3 /day, FIELD: Msc f /day);
Default: no rate or limit.
6. liquid rate on the surface (or limit) (METRIC: sm3 /day, FIELD: stb/day);
Default: no rate or limit.
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),
• +CON – the same as CON+,
• 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 can’t 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
Default: YES.
9. group’s production guide rate. Dimensionless number governing the group’s share of a
higher level production rate target; phase (OIL, WAT, GAS or LIQ) is set using the next
parameter of this keyword
Default: no limit.

12.19.86. GCONPROD 1677

Keywords for formats tN, E1, E3 19.1

10. phase for the previous parameter of this keyword:

• OIL,
• WAT,
• GAS,
• LIQ – liquid,
• WGA – wet gas,
• CVAL – calorific value production,
• POTN – group’s guide rate in the beginning of each time step is set equal to the
group’s production potential (sum of subordinate producers’ potentials). Parameter
9 is ignored in this case.
Wells’ potentials – section 5.6.7.
• FORM – group’s guide rate is calculated via the potential formula defined in the
keyword GUIDERAT (see 12.19.87) (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);
Default: workover specified in the parameter 7.

12. workover action for gas rate violation (limit is specified via parameter 5); Workover
choice is the same as in parameter 7 (NONE, CON, CON+, +CON, WELL, RATE);
Default: workover specified in the parameter 7.

13. workover action for liquid rate violation (limit is specified via parameter 6); Workover
choice is the same as in parameter 7 (NONE, CON, CON+, +CON, WELL, RATE);
Default: workover specified in the parameter 7.

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 E1/E3 compatibility field;

18. surface gas production balancing fraction target or upper limit. The group’s 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 group’s surface gas
volume injection rate. Workover if the limit is exceeded – RATE,

12.19.86. GCONPROD 1678

Keywords for formats tN, E1, E3 19.1

19. surface water production balancing fraction target or upper limit. The group’s surface
water volume production rate is limited to the specified fraction (or multiple) of the
group’s 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 well’s potential
flow rate is in the section 5.6.7).
In the current version only the limit chosen by control mode will be matched, all other
limits are ignored.
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.19.86. GCONPROD 1679

Keywords for formats tN, E1, E3 19.1

12.19.87. GUIDERAT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies a general formula for calculating production guide rates (for group
control, keyword – GCONPROD, see 12.19.86). Group control possibilities of tNavigator are
described in the section 2.14.2.

Group flow rate targets are distributed among the wells in proportion to their guide rates.
Default: well’s 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 – well’s or group’s potential flow rate of the phase p (description
of well’s potential flow rate is in the section 5.6.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).

The following parameters should be specified (The data should be terminated with a slash
/.):

1. minimum time interval between guide rate calculations (METRIC: days, FIELD: days).
The guide rate is calculated at the beginning of each timestep starting after the specified
interval from previous guide rate calculation;

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 well’s or
group’s production ratios at the beginning of the time step);
Default: NONE. Phase:

12.19.87. GUIDERAT 1680

Keywords for formats tN, E1, E3 19.1

• 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);
• 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,
Default: 0.

4. B (non-negative),
Default: 0.

5. C ,
Default: 0.

6. D,
Default: 0.

7. E ,
Default: 0.

8. F ,
Default: 0.

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 can’t 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
Default: YES.

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:

12.19.87. GUIDERAT 1681

Keywords for formats tN, E1, E3 19.1

GRused = GRDAMP GRcalculated + (1 − GRDAMP)GR previous .

Default: 1.

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;
• Default: NO.

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 > 10−19 ×
f low,
Default: 10−6 .

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.19.87. GUIDERAT 1682

Keywords for formats tN, E1, E3 19.1

12.19.88. WREGROUP

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword sets automatic regrouping of wells depending of watercut, oil rate or another
specified parameter.

The well transfer take place at the start of the next time step after a time step when speci-
fied limit of parameter has been passed. The transfer take place instantaneously.

Any number of lines can be specified, each terminated with a slash /. All data should be
terminated with a final slash /.
The following parameters should be specified in one data line:
1. well name, well name template, or well list name defined via WLIST (see 12.19.33),
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
• Default: ' '.
3. group name into which the well should be moved when its specified parameter value
exceeds the value in parameter 4;
Default: the group to which the well was assigned in the keyword WELSPECS
(see 12.19.3).
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);
Default: 1e20.
5. group name into which the well should be moved when its specified parameter value
falls below the value in parameter 6;
Default: the group to which the well was assigned in the keyword WELSPECS
(see 12.19.3).

12.19.88. WREGROUP 1683

Keywords for formats tN, E1, E3 19.1

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)
Default: 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 be-
low 30 bar, then the well will be moved to the group to which the well was assigned in the
keyword WELSPECS (see 12.19.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.19.3).

12.19.88. WREGROUP 1684

Keywords for formats tN, E1, E3 19.1

12.19.89. GCONPRI

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword specifies production rate limits for well group when an option of well pri-
oritization is used – 2.14.13. Priority formulae are specified in PRIORITY (see 12.19.92).

Any number of lines can be specified, each terminated with a slash /. All data should be
terminated with a final slash /.
The following parameters should be specified:
1. group name, or group mask defining a subset of groups with common prefix (should
end with an asterisk *), or FIELD (for field control),

2. oil production rate upper limit (METRIC: sm3 /day, FIELD: stb/day);
Default: no limit.

3. workover action for oil rate violation:

• NONE – no action,
• 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),
• +CON – the same as CON+,
• WELL – shut in the worst offending well,
• PRI – control group production rate by prioritization (using the first priority for-
mula if there are two formulae in PRIORITY, see 12.19.92),
• PR2 – control group production rate by prioritization (using the second formula)
• Default: NONE.

4. water production rate upper limit (METRIC: sm3 /day, FIELD: stb/day),
Default: no limit.

5. workover action for water rate violation:

• NONE – no action,
• 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),

12.19.89. GCONPRI 1685

Keywords for formats tN, E1, E3 19.1

• +CON – the same as CON+,

• WELL – shut in the worst offending well,
• PRI – control group production rate by prioritization (using the first priority for-
mula if there are two formulae in PRIORITY, see 12.19.92),
• PR2 – control group production rate by prioritization (using the second formula),
• Default: NONE.

6. gas production rate upper limit (METRIC: sm3 /day, FIELD: Msc f /day),
Default: no limit.

7. workover action for gas rate violation:

• NONE – no action,
• 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),
• +CON – the same as CON+,
• WELL – shut in the worst offending well,
• PRI – control group production rate by prioritization (using the first priority for-
mula if there are two formulae in PRIORITY, see 12.19.92),
• PR2 – control group production rate by prioritization (using the second formula),
• Default: NONE.

8. liquid production rate or upper limit in surface conditions (METRIC: sm3 /day, FIELD:
stb/day),
Default: no limit.

9. workover action for liquid rate violation:

• NONE – no action,
• 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),
• +CON – the same as CON+,
• WELL – shut in the worst offending well,
• PRI – control group production rate by prioritization (using the first priority for-
mula if there are two formulae in PRIORITY, see 12.19.92),
• PR2 – control group production rate by prioritization (using the second formula),
• Default: NONE.

12.19.89. GCONPRI 1686

Keywords for formats tN, E1, E3 19.1

10. liquid production rate upper limit in reservoir conditions (METRIC: rm3 /day, FIELD:
rb/day). If this limit is violated PRI is taken.
Default: no limit.

11. reservoir volume production balancing fraction upper limit. IGNORED. This is an E1/E3
compatibility field.

12. wet gas production rate upper limit (METRIC: sm3 /day, FIELD: Msc f /day),
Default: no limit.

13. workover action for wet gas rate violation:

• NONE – no action,
• 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),
• +CON – the same as CON+,
• WELL – shut in the worst offending well,
• PRI – control group production rate by prioritization (using the first priority for-
mula if there are two formulae in PRIORITY, see 12.19.92),
• PR2 – control group production rate by prioritization (using the second formula),
Default: NONE.

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.19.89. GCONPRI 1687

Keywords for formats tN, E1, E3 19.1

12.19.90. GPMAINT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies well group data for pressure maintenance in fluid-in-place regions
(FIP regions) (E1) or in pressure maintenance region (E3, regions are specified via PMANUM,
see 12.4.16) at specified target value.

Group’s 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);

• Ctime – integral time constant (parameter 7 of this keyword);

• E – region’s 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 /.
The following parameters should be specified:
1. group name, or group mask defining a subset of groups with common prefix (should
end with an asterisk *), or FIELD.
This group maintains the average pressure in the specified region, by adjusting its pro-
duction or injection rate (parameter 2). One or more groups can maintain pressure in
one region.

2. flow target to pressure control:

• PROD – group’s production rate in reservoir conditions is adjusted (RESV)

(for PROD the group shouldn’t be under prioritization group control GCONPRI,
see 12.19.89),

12.19.90. GPMAINT 1688

Keywords for formats tN, E1, E3 19.1

• OINJ – group’s oil injection rate in reservoir conditions is adjusted (RESV),

• WINJ – group’s water injection rate in reservoir conditions is adjusted (RESV),
• GING – group’s gas injection rate in reservoir conditions is adjusted (RESV) (for
compositional models composition of injected gas should be specified via GINJ-
GAS, see 12.19.191),
• OIS – group’s oil injection rate in surface conditions is adjusted,
• WINS – group’s water injection rate in surface conditions is adjusted,
• GINS – group’s gas injection rate in surface conditions is adjusted (for compo-
sitional models composition of injected gas should be specified via GINJGAS,
see 12.19.191),
• NONE – group’s flow is no longer adjusted to maintain pressure.

3. region number, whose pressure this group controls.

• E1 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.
• E3 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.);
Default: FIPNUM (see 12.4.10).

5. target pressure for the region (METRIC: barsa, FIELD: psia). The well group tries to
maintain the region’s average pressure at this value;

6. proportionality constant. At each time step, the group’s target rate is equal to the pro-
portionality constant multiplied by the region’s pressure error term (METRIC: rm3 or
sm3 /day/bar , FIELD: rb or stb/day/psi);

7. integral time constant. The integral of the region’s pressure error over time, divided
by the integral time constant, is added to the current pressure error (METRIC: days,
FIELD: days).

Note:

• The value of cumulative pressure error (integral of pressure error) is calculated for
GPMAINT. If for the long period the pressure was significantly less than target value,
then it is allowed to inject a lot to compensate the period of low pressure.

• Cumulative pressure error can be very high and is can start to decrease slowly when the
pressure will be higher than target pressure. So at the beginning if the pressure exceeds
average reservoir pressure we will not see the limit of injection, injection still will go
on maximum.

12.19.90. GPMAINT 1689

Keywords for formats tN, E1, E3 19.1

• This fact can get worse if there are no wells on group control, then the sum will not
change at all. So if at the beginning we obtain the high value of cumulative pressure
error, then the injection limit will be very high and the wells will work on their own
control modes, which may lead to impression that GPMAINT is not used.

• To improve this behavior the special option RECOMPUTEGPMAINT can be used

TNAVCTRL (see 12.1.4). If it is enabled then the value of cumulative pressure error
will be updated independently from are wells on GPMAINT control or not.

Example
GPMAINT
FIELD WINJ 0 1* 3700 40 70 /
/
In this example group FIELD will try to maintain the field average pressure at the value
3700 psia, via group’s water injection rate in reservoir conditions is adjusting.

12.19.90. GPMAINT 1690

Keywords for formats tN, E1, E3 19.1

12.19.91. GPMAINT3

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.19.90).
Each line should be ended by a symbol /. The data should be terminated with a slash /.

In each line the following parameters should be specified:

1. group name;

2. flow target to control the pressure:

• PROD – the group’s production in reservoir conditions (RESV) rate is controlled;

• WINJ – the group’s water injection rate in reservoir conditions (RESV) rate is
controlled,
• GINJ – the group’s gas injection rate in reservoir conditions (RESV) rate is con-
trolled, (only for E1 models – for E3 models gas composition should be specified
by the keyword GINJGAS, see 12.19.191),
• WINS – the group’s water injection rate in surface conditions rate is controlled,
• GINS – the group’s gas injection rate in surface conditions rate is controlled, (only
for E1 models – for E3 models gas composition should be specified by the keyword
GINJGAS, see 12.19.191),
• 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.19.184). 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 mixture
using either the WINJMIX (see 12.19.188) or WINJORD (see 12.19.189) 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 vapor
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.19.91. GPMAINT3 1691

Keywords for formats tN, E1, E3 19.1

• 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 group’s flow is no longer adjusted to maintain pressure.

3. pressure maintenance region number. Specified group controls pressure of this region.
Pressure maintenance regions are defined via PMANUM (see 12.4.16);
Default: 1.

4. this item is not used in E3 models; it is retained for compatibility with E1 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 group’s rate (METRIC: rm3 /day/bar ;
FIELD: rb/day/psi);

7. the integral time constant, for controlling the group’s 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;
Default: 0.

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;
• Default:

12.19.91. GPMAINT3 1692

Keywords for formats tN, E1, E3 19.1

– W, if the parameter 2 is WV;

– G otherwise.

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;

13. name of a wellstream to be used as make-up gas (specified via WELLSTRE,

see 12.19.184). This is only required if make-up gas is to be used when there is in-
sufficient 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: TOT.

Note:

• The value of cumulative pressure error (integral of pressure error) is calculated for
GPMAINT. If for the long period the pressure was significantly less than target value,
then it is allowed to inject a lot to compensate the period of low pressure.

• Cumulative pressure error can be very high and is can start to decrease slowly when the
pressure will be higher than target pressure. So at the beginning if the pressure exceeds
average reservoir pressure we will not see the limit of injection, injection still will go
on maximum.

• This fact can get worse if there are no wells on group control, then the sum will not
change at all. So if at the beginning we obtain the high value of cumulative pressure
error, then the injection limit will be very high and the wells will work on their own
control modes, which may lead to impression that GPMAINT is not used.

• To improve this behavior the special option RECOMPUTEGPMAINT can be used

TNAVCTRL (see 12.1.4). If it is enabled then the value of cumulative pressure error
will be updated independently from are wells on GPMAINT control or not.

12.19.91. GPMAINT3 1693

Keywords for formats tN, E1, E3 19.1

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 group’s rate is 100 rb/day/psi, controlling time of the group’s rate is 30 days.
Fluid 'IGAS'is injected, target which is controlled to maintain the pressure is gas at surface
conditions.

12.19.91. GPMAINT3 1694

Keywords for formats tN, E1, E3 19.1

12.19.92. PRIORITY

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets coefficients to the well priority formula in group control with well pri-
oritization option – 2.14.13, keyword GCONPRI (see 12.19.89).

This option is an 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.19.86).

Well prioritization option description.

• Wells priorities are calculated according to formula specified in PRIORITY (see 12.19.92).

• Wells are turned on in decreasing order of their priority (well with the highest priority
is the first).

• Wells are turned on until group’s production rate limit is exceeded.

• A rate of well, which exceeds the group’s limit, is cut to meet the limit (in spite of its
own limits WCONPROD, see 12.19.42).

• Wells with low priority are closed until they are selected to produce.

• Wells, which violate economic limits, and are closed manually can’t be selected to
produce.

• 2 priority formulae can be specified and they can be used as PRI and PR2 in GCONPRI,
see 12.19.89).

• If 2 limits that have different priority formulae 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 NUP-
COL (see 12.19.234) iterations via the formula (coefficients are specified in PRIORITY,
see 12.19.92):
A + BPO +CPW + DPG
PRIORITY =
E + FPO + GPW + HPG
where:

12.19.92. PRIORITY 1695

Keywords for formats tN, E1, E3 19.1

– Pp – potential well rate for the phase p (description of well’s potential flow rate
is in the section 5.6.7);
– A, B, C , D, E , F , G, H – coefficient from PRIORITY (see 12.19.92).

• Wells’ priorities calculated via formulae PRIORITY (see 12.19.92) can be overridden via
numbers specified directly in the keyword WELPRI (see 12.19.93);

• In group hierarchy both methods of potential guide rates GCONPROD (see 12.19.86)
and well prioritization GCONPRI (see 12.19.89) 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.
The following parameters should be specified (The data should be terminated with a slash
/.):
1. minimum time interval between well priority calculations. If zero value is specified
priorities will be recalculated every timestep;

2. non-negative coefficients A − H for the first priority formula (PRI in GCONPRI,

see 12.19.89). One or more coefficient from first four coefficients and one of more
coefficient from next four coefficients should not be zero;
Default: 0.

3. non-negative coefficients A − H for the second priority formula (PR2 in GCONPRI,

see 12.19.89). One or more coefficient from first four coefficients and one of more
coefficient from next four coefficients should should not zero.
Default: 0.

Example
PRIORITY
1* 0 0 0 1 1 0 0 0 0 1 0 0 1 0 0 0 /

2 priority formulae 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.19.92. PRIORITY 1696

Keywords for formats tN, E1, E3 19.1

12.19.93. WELPRI

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword sets priority numbers for production wells when the option of well prioriti-
zation is applied – 2.14.13. These numbers will override priority values calculated via priority
formulae (the keyword PRIORITY, see 12.19.92).

An arbitrary number of data lines could be entered (ended with /). All data should be
terminated with a final slash /.
The following parameters are to be specified in one data line:

1. name of well (or number), or well list name defined via WLIST (see 12.19.33),

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;
• Default: negative.

3. first priority factor. The well’s first priority number (specified via 2-nd parameter or
calculated via the first priority formula) is multiplied by this factor;
Default: 1.

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;
• Default: negative.

5. second priority factor. The well’s second priority number (specified via 4-th parameter
or calculated via the second priority formula) is multiplied by this factor;
Default: 1.

12.19.93. WELPRI 1697

Keywords for formats tN, E1, E3 19.1

Example
WELPRI
W1 1* 2.0 /
/

12.19.93. WELPRI 1698

Keywords for formats tN, E1, E3 19.1

12.19.94. WGRUPCON

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies well guide rates for group control. Group control possibilities of
tNavigator are described in the section 2.14.2. An arbitrary number of data lines can be
specified (terminated with a slash /). All data should be terminated with a final slash /.
One data line contains the following parameters:

1. well name, or well list name defined via WLIST (see 12.19.33);

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;
Default: YES.

3. well’s guide rate (the value that specifies well’s share in the group’s 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.19.87). If
the formula is not specified then it is equal to well’s production or injection potentials
(description of well’s potential flow rate is in the section 5.6.7);

4. phase to which the well’s 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;
• Default: negative.

5. guide rate factor (well’s guide rate, specified in parameter 3, or calculated will be
multiplied by this factor;
Default: 1.

12.19.94. WGRUPCON 1699

Keywords for formats tN, E1, E3 19.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.19.94. WGRUPCON 1700

Keywords for formats tN, E1, E3 19.1

12.19.95. GCONINJE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword could be specified for a well group or several groups with the same group
name root. Group control possibilities of tNavigator are described in the section 2.14.2. The
following parameters should be specified:
1. group name, or group mask defining a subset of groups with common prefix (should
end with an asterisk *), or FIELD (for field control),
Default: default group (group of wells with default group in WELSPECS, see 12.19.3).

2. injected fluid to which group control will apply (WATER; GAS or OIL).
Note: for model in E3 format the composition of the injected gas should be specified
via GINJGAS (see 12.19.191), 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 at conditions defined by the 13th parameter
of WELSPECS (see 12.19.3) (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 mul-
tiplied 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,
• Default: NONE.

4. surface rate of injected fluid (or limit) (METRIC: sm3 /day, FIELD: stb/day – for oil
and water, Msc f /day – for gas),
Default: no rate or limit.

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,

12.19.95. GCONINJE 1701

Keywords for formats tN, E1, E3 19.1

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,
Default: no limit.
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,
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,
Default: YES.
9. group’s 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 E3 format if a zero guide rate is specified: the group’s guide rate
at the beginning of each timestep is set equal to the group’s 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 group’s surface injection rate;
• NETV – guide rate is set at the beginning of each time step equal to the group’s
net voidage potential (that is its voidage production potential minus the reservoir
volume injection potential of any other phases);
• VOID – guide rate is set at the beginning of each time step equal to the value of
group’s production rate in reservoir conditions. The value that is set in parameter
9 is not used.
• Default: groups’s share of a higher rate of phase injection: no limit.
11. group name. The group specified in parameter 1 can re-inject a fraction of another
group’s production rate, the name of this group should be specified here. The re-injection
fraction is specified in parameter 6.
Default: the group specified in parameter 1 can re-inject a fraction of another group’s
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..
12. group name. The group specified in parameter 1 can replace a fraction of another group’s
voidage, the name of this group should be specified here. The voidage replacement
fraction is specified in parameter 7.
Default: The group specified in parameter 1 can replace a fraction of another group’s
voidage, the name of this group should be specified here: The group, specified in pa-
rameter 1 replaces a fraction of its own voidage..

12.19.95. GCONINJE 1702

Keywords for formats tN, E1, E3 19.1

If user specifies group control, and control mode is not NONE, the 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.

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.19.95. GCONINJE 1703

Keywords for formats tN, E1, E3 19.1

12.19.96. GCONSUMP

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets gas consumption and import rates for well groups. Group control possi-
bilities of tNavigator are described in the section 2.14.2.

For group re-injection control (GCONINJE, see 12.19.95):

Group’s gas injection rate = Group’s re-injection fraction *
(Group’s gas production rate + Gas import rate to the group (and subordinate) -
Group’s gas consumption rate (and subordinate groups gas consumption)).

An arbitrary number of data lines can be entered (terminated with a slash /). All data
should be terminated with a final slash /.
One data line contains the following parameters:

1. group name, or group mask defining a subset of groups with common prefix (should
end with an 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.19.165);
Default: 0 (METRIC: sm3 /day, FIELD: Msc f /day).

3. gas import rate for the group (METRIC: sm3 /day, FIELD: Msc f /day).
Can be specified by the user via UDQ (see 12.19.165);
Default: 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.19.96. GCONSUMP 1704

Keywords for formats tN, E1, E3 19.1

12.19.97. GSATPROD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies oil, water, gas rate for satellite group. Group control possibilities
of tNavigator are described in the section 2.14.2.
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 shouldn’t 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.19.98).

An arbitrary number of data lines can be entered (terminated with a slash /). All data
should be terminated with a final slash /.
One data line contains the following parameters:
1. satellite group name or group mask defining a subset of groups with common prefix
(should end with an asterisk *).
When the group is used first time in the keyword GSATPROD (see 12.19.97) or GSAT-
INJE (see 12.19.98), it is defined as a satellite group. In a multilayer hierarchy the group
should be defined previously in the keyword GRUPTREE (see 12.19.100) (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),
Default: 0 (METRIC: sm3 /day, FIELD: stb/day).

3. water production rate from the satellite group (METRIC: sm3 /day, FIELD: stb/day),
Default: 0 (METRIC: sm3 /day, FIELD: stb/day).

4. gas production rate from the satellite group (METRIC: sm3 /day, FIELD: Msc f /day),
Default: 0 (METRIC: sm3 /day, FIELD: stb/day).

5. fluid production rate from the satellite group in reservoir conditions (METRIC:
rm3 /day, FIELD: rb/day);
Default: 0 (METRIC: sm3 /day, FIELD: stb/day).
Note. For models in E3 formats it is necessary to define oil or gas composition using the
keyword GSATCOMP (see 12.19.99) since the stream is not defined by default.

12.19.97. GSATPROD 1705

Keywords for formats tN, E1, E3 19.1

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.19.100).
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.19.97. GSATPROD 1706

Keywords for formats tN, E1, E3 19.1

12.19.98. GSATINJE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies oil, water, gas injection rate for satellite group. Group control pos-
sibilities of tNavigator are described in the section 2.14.2.
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 shouldn’t 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.19.97).

An arbitrary number of data lines can be entered (terminated with a slash /). All data
should be terminated with a final slash /.
One data line contains the following parameters:

1. satellite group name or group mask defining a subset of groups with common prefix
(should end with an asterisk *).
When the group is used first time in the keyword GSATPROD (see 12.19.97) or GSAT-
INJE (see 12.19.98), it is defined as a satellite group. In a multilayer hierarchy the group
should be defined previously in the keyword GRUPTREE (see 12.19.100) (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),
Default: 0 (METRIC: sm3 /day, FIELD: stb/day).

4. phase injection rate in reservoir condition (METRIC: rm3 /day, FIELD: rb/day);
Default: 0 (METRIC: sm3 /day, FIELD: stb/day).

Note. For models in E3 formats it is necessary to define oil or gas composition using the
keyword GSATCOMP (see 12.19.99) since the stream is not defined by default.

12.19.98. GSATINJE 1707

Keywords for formats tN, E1, E3 19.1

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.19.100).
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.19.98. GSATINJE 1708

Keywords for formats tN, E1, E3 19.1

12.19.99. GSATCOMP

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword defines the composition of the oil or gas injected or produced by a satellite
group (see keywords GSATINJE (see 12.19.98) and GSATPROD, see 12.19.97).
This keyword is followed by arbitrary number of records. Each record contains parameters
described below and is terminated by symbol /.
The records can be terminated early with a symbol /, in this case the remaining parameters
defined by default values. The set of records is ended by a blank line, containing only a symbol
/.

1. Satellite group name or group mask defining a subset of groups with common prefix
(should end with an asterisk *). If a group name root is enclosed in quotes and ending
with an symbol (*) it can be used to refer to several groups in one record. The group(s)
must previously have been declared with keyword GRUPTREE (see 12.19.100), to define
their position in the grouping hierarchy;

2. String of characters defining a composition to be defined:

• IG – Set composition of injected gas;

• PG – Set composition of produced gas.

3. well stream name (defining the composition). The stream is defined via the keyword
WELLSTRE (see 12.19.184).

Example
'MAKE_GAS' PG 'UZGAS'/
/

12.19.99. GSATCOMP 1709

Keywords for formats tN, E1, E3 19.1

12.19.100. GRUPTREE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets tree structure for multi-level group control. Group control possibilities
of tNavigator are described in the section 2.14.2. 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.19.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.19.100. GRUPTREE 1710

Keywords for formats tN, E1, E3 19.1

12.19.101. DGRDT

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword specified maximum rate of change of guide rate for wells under group con-
trol (it the default guide rate option is used – potentials are used instead of used defined values
or GUIDERAT, see 12.19.87).
The keyword limits the current timestep’s guide rate inside the bounds defined by the previous
timestep’s guide rate. The data should be terminated with a slash /.

The following parameters should be specified:

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 timestep’s guide rate: multiplication
of the above fractional bounds by the previous timestep’s guide rate;
Default: 100.

2. the smallest permitted lower fractional bound as calculated above;

Default: 0.5.

3. the largest permitted upper fractional bound as calculated above;

Default: 1.5.

Example
DGRDT
0.05 /

12.19.101. DGRDT 1711

Keywords for formats tN, E1, E3 19.1

12.19.102. BRANPROP

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies the extended network branches (extended network model is speci-
fied via the keyword NETWORK, see 12.1.91). This network structure can be different from
the structure specified by GRUPTREE (see 12.19.100) (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.19.103).
For the description of the extended network model see 2.14.11. NETWORK option. Au-
tomatic chokes. Compressors.
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 branch’s downtree node (this node is nearer to the well);

2. name of the branch’s uptree node (this node is nearer to the top of tree);

3. VFP table number VFPPROD (see 12.19.66) (for producers) and VFPINJ (see 12.19.65)
(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.19.103),
should have a value 9999.
A value 0 closes the branch (removes it from the network). Node’s production (or node’s
injection) is not added to the network flows;

4. artificial Lift Quantity (ALQ) that is used in the pressure loss calculations for the branch.
It can be defined by user using the keyword UDQ (see 12.19.165). 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.19.108), this value should correspond to its off position (usually 0);
Default: 0.

All data should be terminated with a final slash /.

12.19.102. BRANPROP 1712

Keywords for formats tN, E1, E3 19.1

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.19.100):

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).
BRANPROP (see 12.19.102):
Table VFPPROD (see 12.19.66) 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.19.103) for nodes G1, G2, G3, G4).

NODEPROP (see 12.19.103):

The terminal node FIELD has terminal pressure 20barsa.

12.19.102. BRANPROP 1713

Keywords for formats tN, E1, E3 19.1

12.19.103. NODEPROP

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword defines the extended network node properties (extended network model
is specified via the keyword NETWORK, see 12.1.91). The keyword BRANPROP
(see 12.19.102) should previously describe branch properties. An extended network should
be defined via BRANPROP (see 12.19.102) and NODEPROP (see 12.19.103).
For the description of the extended network model see 2.14.11. NETWORK option. Au-
tomatic chokes. Compressors.
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). It can be defined
by user using the keyword UDQ (see 12.19.165);

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 net-
work.) 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.19.102) 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 node’s uptree branch acts as an automatic choke. NO – A production target
applied to the corresponding group is met by the standard methods of group control.
Default: NO.

Manifold groups, and groups for automatic chokes, should have their rate targets set di-
rectly with GCONPROD (see 12.19.86) or indirectly as a share of a higher level group’s
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

12.19.103. NODEPROP 1714

Keywords for formats tN, E1, E3 19.1

should be given guide rates in keyword GCONPROD (see 12.19.86). Groups subordi-
nate to an automatic choke’s target group should not have guide rates. Production wells
subordinate to an automatic choke’s target group are not subject to guide rate group
control.

4. flag indicating whether gas-lift gas from the corresponding group’s subordinate wells
should be added to the produced gas entering the network at this source node: YES or
NO.
If the node isn’t a source node in a production network this parameter should be de-
faulted;
Default: NO.

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 group’s production (injection) rate target (GCONPROD (see 12.19.86) for
production, GCONINJE (see 12.19.95) for injection).
The 3-rd parameter should be set YES to use this parameter;
Default: same as the parameter 1.

6. for a source/sink node, the name of the corresponding well group or a satellite group.
This item is relevant only to source nodes in production networks and sink nodes in
injection networks. If the node is not a source/sink node, the item is ignored. It is also
ignored for E1 models where the source/sink nodes must have the same names as their
corresponding groups. The source/sink node’s inflow/outflow will be equated with the
production/injection of the specified group. The third parameter of the keyword WEFAC
(see 12.19.83) specifies whether or not the well flows are multiplied by their efficiency
factors for this purpose;
Default: same as parameter 1, if such group exists.

All data should be terminated with a final slash /.

12.19.103. NODEPROP 1715

Keywords for formats tN, E1, E3 19.1

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.19.100):

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).
BRANPROP (see 12.19.102):
Table VFPPROD (see 12.19.66) 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.19.103) for nodes G1, G2, G3, G4).

NODEPROP (see 12.19.103):

The terminal node FIELD has terminal pressure 20barsa.

12.19.103. NODEPROP 1716

Keywords for formats tN, E1, E3 19.1

12.19.104. NETCHOKE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets choke properties in extended network (see the keyword NETWORK,
see 12.1.91). The keyword BRANPROP (see 12.19.102) should before describe branch prop-
erties.
For the description of the extended network model see 2.14.11. NETWORK option. Au-
tomatic chokes. Compressors.
For more detailed description of choke workflows, see the section 2.14.12.
Properties of several chokes can be defined there. For each of them properties are set on
separate line. One data line contains the following parameters:

1. choke name. It should be single quoted;

2. subcritical correlation type:
• MECHANISTIC;
Default: MECHANISTIC.
3. critical correlation type:
• MECHANISTIC;
Default: MECHANISTIC.
4. critical flow criteria:
• PRESS_RATIO;
Default: PRESS_RATIO.
5. critical pressure ratio;
Default: 0.53.
6. bean diameter (METRIC: m, FIELD: f t );
7. upstream pipe internal diameter (METRIC: m, FIELD: f t );
8. discharge coefficient. It will be used to calculate gas flow coefficient, cvG , or liquid
flow coefficient, cvL , if some of them is not set. Otherwise it doesn’t used;
Default: 0.6.
9. gas flow coefficient, cvG ;
Default: it will be calculated with discharge coefficient.

12.19.104. NETCHOKE 1717

Keywords for formats tN, E1, E3 19.1

10. liquid flow coefficient, cvL ;

Default: it will be calculated with discharge coefficient.

11. heat capacity ratio.

Any number of data lines can be specified. Each data line should be terminated with the
symbol /. The data should be terminated with a slash /.
Example
NETCHOKE
'choke1' 1* 1* 1* 0.53 0.04 0.25 1* 1* 1* 1.4 /
/

12.19.104. NETCHOKE 1718

Keywords for formats tN, E1, E3 19.1

12.19.105. NCONSUMP

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.91) and to assign the consumption also to a
group (see the keyword GRUPTREE, see 12.19.100).
For the description of the extended network model see 2.14.11. NETWORK option. Au-
tomatic chokes. Compressors.
The following parameters should be specified:

1. node name;

2. gas consumption rate at the node (METRIC: sm3 /day, FIELD: Msc f /day);
Default: 0.

3. name of the group from which the node’s consumption should also be removed.
Default: no group.

Any number of data lines can be specified. Each data line should be terminated with the
symbol /. The data should be terminated with a slash /.

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 node’s consumption is removed from group T-ALP.

12.19.105. NCONSUMP 1719

Keywords for formats tN, E1, E3 19.1

12.19.106. GNETDP

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.91). Automatic chokes. Compressors. – 2.14.11.)

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 net-
work 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 maxi-
mum 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 data line should be terminated with the
symbol /. All data should be terminated with a final slash /.
One line contains the following parameters:

1. name of the fixed-pressure group (fixed-pressure node);

2. phase to which parameters 3 and 4 correspond: OIL, WAT, GAS, LIQ;

Default: GAS.

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);
Default: 0 (no pressure adjustment to increase the flow).

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);
Default: 1e+20 (no pressure adjustment to decrease the flow).

12.19.106. GNETDP 1720

Keywords for formats tN, E1, E3 19.1

5. pressure increment that is subtracted from the fixed pressure when the flow rate falls
below the minimum (parameter 3) (METRIC: barsa, FIELD: psia);
Default: 0.

6. pressure increment that is added to the fixed pressure when the flow rate exceeds the
maximum (parameter 4) (METRIC: barsa, FIELD: psia);
Default: 0.

7. minimum allowed pressure in the group (node) (METRIC: barsa, FIELD: psia);
Default: 0.

8. maximum allowed pressure in the group (node) (METRIC: barsa, FIELD: psia)
Default: 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.19.106. GNETDP 1721

Keywords for formats tN, E1, E3 19.1

12.19.107. GNETINJE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword defines the injection network in extended network model (NETWORK,
see 12.1.91). The keyword BRANPROP (see 12.19.102) should previously describe
branch properties. An extended production network should be defined via BRANPROP
(see 12.19.102) and NODEPROP (see 12.19.103).
For the description of the extended network model see 2.14.11. NETWORK option. Au-
tomatic chokes. Compressors.
An arbitrary number of data rows can be entered (ended with a slash /). One data row
consists of the following parameters:

1. group name or group mask defining a subset of groups with common prefix (should end
with an asterisk *);

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.19.65) for the pipeline between the group
and its parent group.
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 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.19.103), then this parameter should be defaulted (a group with fixed pressure is
a terminal node and it can’t be connected with a parent group.)
Default: 0.

All data should be terminated with a final slash /.

12.19.107. GNETINJE 1722

Keywords for formats tN, E1, E3 19.1

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.19.107. GNETINJE 1723

Keywords for formats tN, E1, E3 19.1

12.19.108. NETCOMPA

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword defines automatic compressors or pumps in the extended production network
(extended network model is specified via the keyword NETWORK, see 12.1.91). An extended
network should be defined via BRANPROP (see 12.19.102) and NODEPROP (see 12.19.103).
For the description of the extended network model see 2.14.11. NETWORK option. Au-
tomatic chokes. Compressors.
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.

An arbitrary number of data rows can be entered (ended with a slash /). One data row
consists of the following parameters:

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 the group whose production rate this compressor will respond to; The compres-
sor 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.19.86) 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
group’s production target.
Default: compressor is turned off.

4. phase whose production rate this compressor responds to.

OIL, GAS.
Default: 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.19.102), which is applied whenever the compressor is off. 0 – original VFP
table number will be unchanged.
Default: 0.

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 keyword
BRANPROP (see 12.19.102), which is applied whenever the compressor is off. Multi-
level compressors operating at an intermediate level has an intermediate value of the

12.19.108. NETCOMPA 1724

Keywords for formats tN, E1, E3 19.1

ALQ (parameters 9, 10 and 11). The artificial lift quantity may be regarded as the com-
pressor or pump power, according to the definition used when the table was calculated
(for example with VFP).
7. rate of gas consumption by the compressor when fully on. This is an E1/E3 compatibility
field. IGNORED.
8. name of the group from which the compressor’s gas consumption should also be ex-
tracted. This is an E1/E3 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 group’s 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 group’s 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:
i−1
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.

12.19.108. NETCOMPA 1725

Keywords for formats tN, E1, E3 19.1

All data should be terminated with a final slash /.

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 produc-
tion rate of the group FIELD, phase – gas. VFP table number for this branch – 2. Compressor
type – MULT. Number of compression levels – 1.

12.19.108. NETCOMPA 1726

Keywords for formats tN, E1, E3 19.1

12.19.109. COMPOFF

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword switches off automatic compressors (see section 2.14.11) defined by NET-
COMPA (see 12.19.108), except for compressors that define to stay on permanently (9-th
parameter PERM in the keyword NETCOMPA, see 12.19.108). If necessary all compressors
will turn on automatically.

This keyword does not switch off compressors specified by GNETPUMP (see 12.19.113).

The keyword does not have any parameters.

12.19.109. COMPOFF 1727

Keywords for formats tN, E1, E3 19.1

12.19.110. NWATREM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword removes water from a node in the extended network (extended net-
work – NETWORK, see 12.1.91). An extended network should be defined via BRANPROP
(see 12.19.102) and NODEPROP (see 12.19.103).
For the description of the extended network model see 2.14.11. NETWORK option. Au-
tomatic chokes. Compressors.
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. The keyword does not affect
the reported group production rates or the operation of any group water rate limits, group
economic limits.

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. 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 node’s
water flow specified via parameter 3);
Default: e20 .

3. maximum fraction of the node’s water flow to be removed (the specified fraction of
the node’s water flow will be removed, corresponding to a maximum rate specified via
parameter 2);
Default: 1.

All data should be terminated with a final slash /.

Example
NWATREM
W1NODE1 1* 0.6 /
W1NODE2 1* 0.2 /
W1NODE3 1* 0.3 /
/
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.19.110. NWATREM 1728

Keywords for formats tN, E1, E3 19.1

12.19.111. NGASREM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword is used to remove gas from the selected node in the extended network
created by keywords NETWORK (see 12.1.91), BRANPROP (see 12.19.102) and NODEPROP
(see 12.19.103) (see section 2.14.11).
The amount of removed gas can be specified as either a constant rate or fraction of the rate
flowing through the selected node. The gas removal affects the pressure loss in the downstream
network branches since their VFP tables will be considered at a smaller gas fraction. This the
only effect that can appear. The gas removal does not affect the reported group production
rates or the operation of any group gas rate targets/limits, re-injection or group economic
limits. The keyword NGASREM is used to remove gas from network node to account for gas
removal from the production stream by the keyword GRUPFUEL (see 12.19.195).
An arbitrary number of records (terminated with a slash /) can be specified. Each record
contains the following data:
1. node name;
2. maximum rate of gas removed from the node (METRIC: sm3 / f ay, FIELD: Msc f /day).
The specified rate of gas will be removed in accordance with the maximum fraction of
the node’s gas flow specified by parameter 3;
Default: e20 .
3. maximum fraction of removed gas in the node’s flow;
Default: 1. The specified fraction of gas will be removed in accordance with the maxi-
mum rate of gas specified by parameter 2.
The set of records is terminated with separate a slash /.

Note 1: The defaults values specified in parameters 2 and 3 only apply to nodes specified
in parameter 1 of this keyword. For other nodes parameters are equal to 0, i.e. there is no gas
removal from them.
Note 2: Since gas removal only affects the pressure losses in the downstream branches,
an error is reported if the node specified in parameter 1 does not have outflow branch.
Example
NGASREM
W1NODE1 1* 0.1 /
W1NODE2 1* 0.3 /
W1NODE3 1* 0.5 /
/

12.19.111. NGASREM 1729

Keywords for formats tN, E1, E3 19.1

In this example 10% of gas is removed from node W1NODE1, 30% of gas is removed
from node W1NODE2, 50% of gas is removed from node W1NODE3.

12.19.111. NGASREM 1730

Keywords for formats tN, E1, E3 19.1

12.19.112. NOILREM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword is used to remove oil from the selected node in the extended network
created by keywords NETWORK (see 12.1.91), BRANPROP (see 12.19.102) and NODEPROP
(see 12.19.103) (see section 2.14.11).
The amount of removed oil can be specified as either a constant rate or fraction of the rate
flowing through the selected node. The oil removal affects the pressure loss in the downstream
network branches since their VFP tables will be considered at a smaller oil fraction. This the
only effect that can appear. The oil removal does not affect the reported group production rates
or the operation of any group oil rate targets/limits, or group economic limits. An arbitrary
number of records (terminated with a slash /) can be specified. Each record contains the
following data:

1. node name;

2. maximum rate of oil removed from the node (METRIC: sm3 / f ay, FIELD: Msc f /day).
The specified rate of oil will be removed in accordance with the maximum fraction of
the node’s oil flow specified by parameter 3;
Default: e20 .

3. maximum fraction of removed oil in the node’s flow;

Default: 1. The specified fraction of oil will be removed in accordance with the maxi-
mum rate of oil specified by parameter 2.

The set of records is terminated with the separate slash /.

Note: The defaults values specified in parameters 2 and 3 only apply to nodes specified
in parameter 1 of this keyword. For other nodes parameters are equal to 0, i.e. there is no oil
removal from them.
Example
NOILREM
W1NODE1 1* 0.2 /
W1NODE2 1* 0.35 /
W1NODE3 1* 0.5 /
/
In this example 20% of oil is removed from node W1NODE1, 35% of oil is removed from
node W1NODE2, 50% of oil is removed from node W1NODE3.

12.19.112. NOILREM 1731

Keywords for formats tN, E1, E3 19.1

12.19.113. GNETPUMP

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword defines automatic pump (compressor) switching in a standard network –

2.14.10.

An arbitrary number of data rows can be entered (ended with a slash /). All data should
be terminated with a final slash /.
One data row consists of the following parameters:

1. group name or group mask defining a subset of groups with common prefix (should end
with an asterisk *);

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);
Default: 0 (METRIC: sm3 /day, FIELD: stb/day).

3. phase to which the production rate (specified in parameter 2) corresponds: OIL – oil,
GAS – gas;
Default: OIL – oil.

4. new VFP table number. When the compressor is switched on this replaces the table
number previously specified in GRUPNET (see 12.19.114). 0 or negative number –
original VFP table number will be unchanged.
Default: 0.

5. new ALQ (Artificial Lift Quantity). IGNORED. This is an E1/E3 compatibility field.

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.19.113. GNETPUMP 1732

Keywords for formats tN, E1, E3 19.1

12.19.114. GRUPNET

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword defines standard production network structure – 2.14.10.

An arbitrary number of data rows can be entered (ended with a slash /). All data should
be terminated with a final slash /.
One data row consists of the following parameters:

1. group name or group mask defining a subset of groups with common prefix (should end
with an asterisk *);

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 char-
acteristics. 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 can’t have a pipe connection with a higher group).
A value 0 – the group doesn’t have a pipeline to its parent group.
Default: 0.

4. artificial lift quantity (ALQ) value that is used in the pressure loss calculations for the
group’s pipeline;
Default: 0.

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.
Default: NO.

12.19.114. GRUPNET 1733

Keywords for formats tN, E1, E3 19.1

!
For a manifold group which is subordinate to a higher level group hav-
ing production rate target, a guide rate should be defined (9th parameter
of GCONPROD, see 12.19.86). Otherwise this flag for the subordinate
group is ignored and interpreted as NO.

6. flag indicating whether gas-lift gas from the subordinate wells flows through this group’s
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.
• 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.
Default: NO.

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.

Example
GRUPNET
FIELD 20
GROUP1 1* 3/
GROUP2 1* 4/
/

Group FIELD is specified as a node with fixed pressure.

12.19.114. GRUPNET 1734

Keywords for formats tN, E1, E3 19.1

12.19.115. DRSDT

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets maximum rate of increase of solution gas-oil ratio (see section 2.8.5).
The data should be terminated with a slash /.
The following parameters should be specified:

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: 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 isn’t specified).
If the keyword is not used, the resolution rate limit is infinity.
If a system containing both dissolved gas and vaporized oil all constraints imposed by
DRSDT will be disabled if the keyword VAPPARS (see 12.19.116) is subsequently specified.
Analogously, the constraints imposed by the keyword VAPPARS (see 12.19.116) will be
disabled if the keyword DRSDT is subsequently specified.
Example
DRSDT
0.000001365/

12.19.115. DRSDT 1735

Keywords for formats tN, E1, E3 19.1

12.19.116. VAPPARS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY x SCHEDULE

This keyword controls oil vaporization. The keyword can be used if both gas solution in
the oil phase and oil vaporization in the gas phase exist in the model (see sections 2.8.5 and
2.8.6). Keywords DISGAS (see 12.1.60) and VAPOIL (see 12.1.59) should be specified in the
section RUNSPEC.
The keyword is followed by two non-dimensional parameters – p1 , p2 :

1. p1 determines the ability of oil to vaporize in the presence of undersaturated gas.The

parameter can vary from 0 to 5. If parameter is equal to zero, the model behavior is the
standard black oil model one (i.e., all oil vaporizes as long as there is any undersaturated
gas in the block). Larger parameter values suppress vaporization especially in blocks
where a lot of oil has already vaporized;

2. p2 determines the ability of remaining oil to get heavier (i.e., the ability of solution gas-
oil ratio RG,O to decrease) as lighter fractions vaporize. The value of parameter should
be less than 1. If this parameter is set to zero, the model behavior is the standard black
oil model one (i.e., RG,O of remaining oil does not change as oil vaporizes). Larger
values increase the differentiation between light and heavy fractions.

The line of two parameters should be terminated by a slash.

Parameters p1 , p2 tend to reduce the maximum allowed values of RG,O and RO,G (key-
words DRSDT (see 12.19.115) and DRVDT (see 12.19.119), respectively) in the block, using
the formulas:  S  p1
O
RO,G = RO,G sat
SOmax
 S  p2
O
RG,O = RG,O sat
SOmax
where SOmax is the largest oil saturation reached in the grid block so far. SO decreasing due
to vaporization leads to further suppressing of vaporization.
If the keyword is not set and a model containing both live oil and wet gas, both parameters
are supposed to be zero, corresponding to standard black oil model behavior.
If a system containing both dissolved gas and vaporized oil all constraints imposed by
VAPPARS will be disabled if the keyword DRSDT (see 12.19.115) or DRVDT (see 12.19.119)
is subsequently specified. Analogously, the constraints imposed by the keyword DRSDT
(see 12.19.115) or DRVDT (see 12.19.119) will be disabled if the keyword VAPPARS is
subsequently specified.
By default: p1 = 0, p2 = 0.

12.19.116. VAPPARS 1736

Keywords for formats tN, E1, E3 19.1

Example
VAPPARS
5 1 /

12.19.116. VAPPARS 1737

Keywords for formats tN, E1, E3 19.1

12.19.117. DRSDTVP

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.19.115).

The description and formulae are in the section 2.8.5.

The table should be specified. The data should be terminated with a slash /.
One table row contains the following parameters:

1. dimensionless pressure (∆p in the section 2.8.5);

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);

3. flag: ALL – parameter 1 is applied to all grid blocks, FREE – parameter 1 is applied
only to grid blocks that contain free gas.
Default: ALL.

Example
DRSDTVP
1 0.0 ALL
2 0.5 ALL
/

12.19.117. DRSDTVP 1738

Keywords for formats tN, E1, E3 19.1

12.19.118. DRSDTVPE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.19.115).

The description and formulae are in the section 2.8.5.

The table should be specified. The data should be terminated with a slash /.
One table row contains the following parameters:

1. dimensionless pressure (∆p in the section 2.8.5);

2. λ – relaxation parameter of nonequilibrium Rs to equilibrium;

3. flag: ALL – parameter 1 is applied to all grid blocks, FREE – parameter 1 is applied
only to grid blocks that contain free gas.
Default: ALL.

Example
DRSDTVPE
1 0.01 ALL
/

12.19.118. DRSDTVPE 1739

Keywords for formats tN, E1, E3 19.1

12.19.119. DRVDT

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets maximum rate of increase of vapor oil-gas ratio (METRIC:
sm3 /sm3 /day, FIELD stb/Msc f /day) – section 2.8.6. One real number should be speci-
fied. The data should be terminated with a slash /.

Default: if this keyword isn’t 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).
If a system containing both dissolved gas and vaporized oil
all constraints imposed by DRVDT will be disabled if the keyword VAPPARS
(see 12.19.116) is subsequently specified. Analogously, the constraints imposed by the key-
word VAPPARS (see 12.19.116) will be disabled if the keyword DRVDT is subsequently
specified.
Example
DRVDT 0.0065/

12.19.119. DRVDT 1740

Keywords for formats tN, E1, E3 19.1

12.19.120. COMPENSATION

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.19.120. COMPENSATION 1741

Keywords for formats tN, E1, E3 19.1

12.19.121. GECON

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword defines economic limit for group or several groups with the same group
name root. Economic control possibilities of tNavigator are summarized in the section 2.14.3.
The following parameters should be specified:

1. group name, or group mask defining a subset of groups with common prefix (should
end with an asterisk *), or FIELD (for field 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
keyword WELSPECS (see 12.19.3);
Default: 0.

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
keyword WELSPECS (see 12.19.3);
Default: 0.

4. upper economic limit of water cut (METRIC: sm3 /sm3 , FIELD: stb/stb),
Default: no limit.

5. upper economic limit of gas-oil ratio (METRIC: sm3 /sm3 , FIELD: Msc f /stb),
Default: no limit.

6. upper economic limit of water-gas ratio (METRIC: sm3 /sm3 , FIELD: stb/Msc f ),
Default: no limit.

7. workover action in case of water cut violation:

• NONE – do nothing
• CON – shut in the worst offending perforation,
• CON+ – shut in worst offending perforation and all below,
• +CON – the same as CON+,
• WELL – shut in the worst offending well
• Default: NONE.

8. end calculations flag:

12.19.121. GECON 1742

Keywords for formats tN, E1, E3 19.1

• 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.
• Default: NO.

9. maximum allowed number of open wells subordinate to this group. This parame-
ter doesn’t allow wells to be opened automatically (option AUTO in WCONPROD
(see 12.19.42), WCONINJE (see 12.19.44), WELOPEN, see 12.19.128) or from the
drilling queue QDRILL (see 12.19.229), if their number will violate this limit. But
the wells can be opened manually (OPEN in WCONPROD (see 12.19.42), WCON-
INJE, see 12.19.44).

10. Default: 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.19.121. GECON 1743

Keywords for formats tN, E1, E3 19.1

12.19.122. GRUPLIM

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword is a full analog of the keyword GECON (see 12.19.121).

12.19.122. GRUPLIM 1744

Keywords for formats tN, E1, E3 19.1

12.19.123. WELDRAW

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets maximum drawdown allowed for production wells (single well or group
of wells). This limitation is taken into account for calculation of well potential (see section
5.6.7). 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 well list name defined via WLIST (see 12.19.33); or FIELD (to set
maximum drawdown allowed for field);

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 phase’s mobility in
corresponding connections:

• LIQ – if well produces oil;

• GAS – if well produces gas.
• Default: LIQ.

This formula converts maximum drawdown allowed for the well (group) into maximum
production rate for the phase:

QMax = DMax ∑(Tci ∗ Mi ) (12.6)

i

Here

• QMax is the maximum production rate for the phase,

• DMax is the maximum drawdown allowed for the well,
• Tc is the connection transmissibility factor,
• M is the phase’s mobility in this connection,
• the summation is over all open connections at current time step.

4. maximum drawdown allowed for the well availability for well’s production potential:

• YES – means that the well’s production potential depends on limits: BHP, THP
and drawdown,

12.19.123. WELDRAW 1745

Keywords for formats tN, E1, E3 19.1

• NO – means that the well’s production potential depends on limits: BHP and THP.
• Default: NO.

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?

• AVG – Limit the PI-weighted average drawdown using formula: The formula 12.6
calculates the drawdown as
D = pavg − pwell
where:
pwell – well’s bottom hole pressure;
pavg – PI-weighted (productivity index) average of the pressures p in the grid
blocks with well’s 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 well’s
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: 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.19.42) or WELTARG, see 12.19.60), tNavigator will take the minimum
of these two values.
Example
WELDRAW
LEFT_SIDE 4 LIQ NO /
WELL136 3 GAS YES /
/

12.19.123. WELDRAW 1746

Keywords for formats tN, E1, E3 19.1

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 phase’s mobility in corresponding
connections), well’s production potential doesn’t depend on drawdown limit. Maximum draw-
down allowed for the well WELL136 is set to 3 bar, phase – GAS, well’s production potential
depends on drawdown limit.

12.19.123. WELDRAW 1747

Keywords for formats tN, E1, E3 19.1

12.19.124. DATES

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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: 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.19.124. DATES 1748

Keywords for formats tN, E1, E3 19.1

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.19.124. DATES 1749

Keywords for formats tN, E1, E3 19.1

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.19.124. DATES 1750

Keywords for formats tN, E1, E3 19.1

12.19.125. TSTEP

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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 aster-
isks 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.19.125. TSTEP 1751

Keywords for formats tN, E1, E3 19.1

12.19.126. NEXTSTEP

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword explicitly defines the maximum possible size for the next simulation step.
The data should be entered in the following format (The data should be terminated with a
slash /.):

1. Maximum length of step (days);

Default: None.

2. Flag to define whether this size limitation should be applied to this step only (NO) or to
all subsequent steps (YES).
Default: NO.

Typically, this keyword is used on time steps where a well with high rate is opened, so as
to damp the potential numeric instability effects of the drastic change.
This keyword has higher priority than the option DTMAX of the keyword RUNCTRL
(see 12.19.140).
Example
WCONPROD
'PROD*' 'OPEN' 'ORAT' 2500 4* 1000 /
/

NEXTSTEP 1
/

This example sets a short 1-day step after the opening of a high-producing well.

12.19.126. NEXTSTEP 1752

Keywords for formats tN, E1, E3 19.1

12.19.127. WELLSHUT

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword is used to shut an existing well(s). This keyword is deprecated, it is recom-
mended to use the keyword WELOPEN (see 12.19.128).

The keyword is followed by an arbitrary number of records each terminated by a slash /.

Each record contains:

1. Well name, well name template, well list name defined via WLIST (see 12.19.33)or well
list template.

The set of records is terminated by a a slash /, located on a new line.

Example
WELLSHUT
Well1 /
Well2 /
Well3 /
Well4 /
/

12.19.127. WELLSHUT 1753

Keywords for formats tN, E1, E3 19.1

12.19.128. WELOPEN

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword shuts or reopens wells and well connections. The data for each well should
be terminated with a slash /. All data 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.19.29) – their numbers
should be specified via parameters 6-7.

The following parameters are to be specified:

1. well name (well number), or well list name defined via WLIST (see 12.19.33),

2. status:

• OPEN,
• STOP,
• SHUT,
• AUTO — well or connection has status SHUT initially but opens automatically (see
WCONPROD (see 12.19.42) parameter 2 option AUTO, COMPDAT (see 12.19.6)
parameter 6, WELSOMIN, see 12.19.2),
• POPN — well opens if it is closed due to priorities; the well stays closed if it was
closed due to other reasons. Section Well prioritization option – 2.14.13.
• Default: OPEN.

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.19.29),

7. number of the last completion in the range (completions are specified via COMPLUMP,
see 12.19.29).

12.19.128. WELOPEN 1754

Keywords for formats tN, E1, E3 19.1

Note. For wells with perforations both in local and global grid, the keyword WELOPEN
(see 12.19.128) is able to close perforations in global grid only. If you need to close perfora-
tions in local grid, then use the keyword WELOPENL (see 12.19.129).
In this case (shut connections in global grid but connections in local grid stay open) the fol-
lowing 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.

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.19.128. WELOPEN 1755

Keywords for formats tN, E1, E3 19.1

12.19.129. WELOPENL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword shuts or reopens wells and well connections in Local Grid Refinement (LGR
– 5.5.8). In case without LGR the keyword WELOPEN (see 12.19.128).

The data for each well should be terminated with a slash /. All data 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 COMPLMPL (see 12.19.30) – their numbers
should be specified via parameters 7-8.

The following parameters are to be specified:

1. well name (well number), or well list name defined via WLIST (see 12.19.33),

2. local grid refinement name that contains the wells connection;

Default: taken from WELSPECL (see 12.19.4).

3. status:

• OPEN,
• STOP,
• SHUT,
• AUTO — well or connection has status SHUT initially but opens automatically (see
WCONPROD (see 12.19.42) parameter 2 option AUTO, COMPDAT (see 12.19.6)
parameter 6, WELSOMIN, see 12.19.2),
• POPN — well opens if it is closed due to priorities; the well stays closed if it was
closed due to other reasons. Section Well prioritization option – 2.14.13,
• Default: OPEN.

4. X - coordinate of connection,

5. Y - coordinate of connection,

6. Z - coordinate of connection,

12.19.129. WELOPENL 1756

Keywords for formats tN, E1, E3 19.1

7. number of the first completion in the range (completions are specified via COMPLMPL,
see 12.19.30),

8. number of the last completion in the range (completions are specified via COMPLMPL,
see 12.19.30).

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.19.129. WELOPENL 1757

Keywords for formats tN, E1, E3 19.1

12.19.130. WELLOPEN

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword opens wells which were shut automatically.

The data for each well should be terminated with a slash /. All data should be terminated
with a final slash /.
The analogue of this keyword is WELOPEN (see 12.19.128).

The following parameters should be specified:

1. well name (well number), or well list name defined via WLIST (see 12.19.33).

Example
WELLOPEN
Well1 /
Well2 /
Well3 /
/

This example opens wells Well1, Well2, Well3.

12.19.130. WELLOPEN 1758

Keywords for formats tN, E1, E3 19.1

12.19.131. MATCORR

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword enables a material balance correction option.

This keyword is IGNORED because of specific methods of solution used in tNavigator.

To set tNavigator iteration process parameters use the keyword RUNCTRL (see 12.19.140).
To do optimization of error of material balance – use an option SMARTMB.

12.19.131. MATCORR 1759

Keywords for formats tN, E1, E3 19.1

12.19.132. NETBALAN

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword sets the network (NETWORK, see 12.1.91) calculation parameters (see sec-
tion 2.14.11). The data should be terminated with a slash /.

The following parameters should be specified:

1. network balancing interval, IGNORED, this is an E1/E3 compatibility field;

2. convergence tolerance for network nodal pressures (METRIC: bars, FIELD: psi);
Default: 0.1 bars.

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.
Default: 20.

4. convergence tolerance for calculating the pressure drop across automatic chokes con-
trolling a group’s production rate. The specified value is the fraction of each group’s
rate target that is a possible error.
Default: 0.01 – There is a convergence of iterations when the group’s rate target is met
within one percent. .

Example
NETBALAN
1* 0.05 10.0 /

12.19.132. NETBALAN 1760

Keywords for formats tN, E1, E3 19.1

12.19.133. WSEGITER

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword sets an iteration parameters for multi-segment wells. The data should be
terminated with a slash /.

The following parameters should be specified:

1. maximum number of well iterations per cycle of calculation.

Default: 40.

Example
WSEGITER
25 /

12.19.133. WSEGITER 1761

Keywords for formats tN, E1, E3 19.1

12.19.134. TUNING / TUNINGDP / TUNINGL / TUNINGS

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets E1/E3 control parameters.

This keyword is IGNORED because of specific methods of solution used in tNavigator.

To set tNavigator iteration process parameters use the keyword RUNCTRL (see 12.19.140).

12.19.134. TUNING / TUNINGDP / TUNINGL / TUNINGS 1762

Keywords for formats tN, E1, E3 19.1

12.19.135. TIGHTENP / TSCRIT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets E1/E3 control parameters.

This keyword is IGNORED because of specific methods of solution used in tNavigator.

To set tNavigator iteration process parameters use the keyword RUNCTRL (see 12.19.140).

12.19.135. TIGHTENP / TSCRIT 1763

Keywords for formats tN, E1, E3 19.1

12.19.136. ZIPPY2

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets E1/E3 control parameters.

This keyword is IGNORED because of specific methods of solution used in tNavigator.

To set tNavigator iteration process parameters use the keyword RUNCTRL (see 12.19.140).

12.19.136. ZIPPY2 1764

Keywords for formats tN, E1, E3 19.1

12.19.137. NSTACK

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets simulator control parameters and time step parameters.
This keyword is IGNORED because of specific methods of solution used in tNavigator.

To set tNavigator iteration process parameters use the keyword RUNCTRL (see 12.19.140).

12.19.137. NSTACK 1765

Keywords for formats tN, E1, E3 19.1

12.19.138. LGRLOCK / LGRFREE

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword sets calculation parameters for LGRs in E1/E3.

This keyword is IGNORED because of specific methods of solution used in tNavigator.

In tNavigator local grid is always calculated with global grid that corresponds to LGR-
LOCK method.

12.19.138. LGRLOCK / LGRFREE 1766

Keywords for formats tN, E1, E3 19.1

12.19.139. CVCRIT

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets E1/E3 control parameters.

This keyword is IGNORED because of specific methods of solution used in tNavigator.

To set tNavigator iteration process parameters use the keyword RUNCTRL (see 12.19.140).

12.19.139. CVCRIT 1767

Keywords for formats tN, E1, E3 19.1

12.19.140. RUNCTRL

Data x tN x E1 x E3 x IM x GE x ST x MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword is used to specify the iterative process parameters for solution of system of
differential equations – 2.1.
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 /.):
AIM N
Controls the usage of implicit method:
• 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,
• 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.
AIM can be switched on via the keyword AIM (see 12.1.102). AIM 1 is used if this
keyword is specified.
Settings of AIM can be changed in the keyword AIMCTRL (see 12.1.5).
This option can not be used in SCHEDULE section.
CHECKSAT N
Controls the initial approximation:
• If N = 0, no additional actions are performed;
• If N6= 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.

12.19.140. RUNCTRL 1768

Keywords for formats tN, E1, E3 19.1

• Default: CHECKSAT 1 - option is used by default for 2-phase water-gas models

and CHECKSAT 0 – option is not used for other models.

CHOPSAT n
This option ”cuts” main variables of filtration equations so that the variations of temper-
ature and saturation at each iteration do not exceed specified limits. It can be used for
black oil and thermal models when in the block drastic variations of saturation/tem-
perature occur or a phase appears/disappears, or if a phase mobility varies.

• n = 0 – nothing will be done;

• n = 1 – the following conditions are controlled:
– the difference of saturations for each phase (P) on two successive Newton
iterations is checked:
|SPi − SPi+1 | < 0.1
In case of for some phase this inequality is violated (the new saturation differs
from the previous one by more than 0.1), then the saturation at i + 1 iteration
is taken equal to SPi+1 = SPi ± 0.1 and an additional iteration is performed.
– tNavigator controls that the saturation does not pass through the point of
immobility;
Notice: The option n=1 is kept for a compatibility with previous versions of tNav-
igator. It is recommended to use n = 2 and 3 options for calculations.
• n = 2, the following limitations on variations of temperature and saturation at the
Newton iteration are specified in a block:
– if at i + 1 iteration an inequality for a temperature

|T i − T i+1 | < 20 ◦C

is violated, then at i + 1 iteration the temperature is specified as T i+1 =

T i ± 20 ◦ C
– if at i + 1 iteration an inequality for a saturation

|SPi − SPi+1 | < 0.2

is violated for some phase, then at i + 1 iteration the saturation is specified as

SPi+1 = SPi ± 0.2;
– if at appearance/disappearance of new phase P at i + 1 iteration an inequality
for its saturation
|SPi − SPi+1 | < 0.01
is violated then at i + 1 iteration the saturation is set equal to 0.01.
• n = 3 – in addition to limits for n = 2 case a limit on relative permeability is used
when a mobility of phase changes.

12.19.140. RUNCTRL 1769

Keywords for formats tN, E1, E3 19.1

– if at variation of mobility of phase at i + 1 an inequality for relative perme-

ability
|krPi − krPi+1 | < 0.01
is violated then at i + 1 iteration its relative permeability is set equal to 0.01.
Default: 0.
DNLIM n
Maximal allowed molar volume relative variation. The positive number should be spec-
ified – fraction.
For example if the value 0.5 is specified – this corresponds to 50% variation of this pa-
rameter 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 re-
duced. 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).
Default: 1.
DPLIM n
Maximal allowed pressure 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
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).
Default: 1.
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.83) but not dual permeability
(DUALPERM, see 12.1.84) models.
This option is used by default for dual porosity models.
This option can not be used in SCHEDULE section.
Default: DPREDUCE 1 speed up calculations of dual porosity models; DPREDUCE 0
– option is not used for other types of models.
DSLIM n
Maximal allowed phase saturation relative variation (maximum is taken over all phases).

12.19.140. RUNCTRL 1770

Keywords for formats tN, E1, E3 19.1

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 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).
Default: 0.0025.

DTINITIAL n
Length of first time step at model start.
Default: 0.1.

DTLIM n
Maximal allowed temperature relative variation. The positive number should be speci-
fied – fraction.
For example if the value 0.5 is specified – this corresponds to 50% variation of this pa-
rameter 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
temperature 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
temperature 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).
Default: 1.

DTLOGIC n
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.
Default: 0.

DTMAX n
Maximum allowed time step; may temporarily get overridden by NEXTSTEP
(see 12.19.126) and certain other instructions;
Default: 100.

12.19.140. RUNCTRL 1771

Keywords for formats tN, E1, E3 19.1

DTMIN n
Minimum allowed time step;
Default: For compositional and black oil models: 0.001; for thermal models: 1.e-6.

DTPRED n
If n=1 time step of the solver is selected by analysing the convergence of the New-
ton method in several previous steps. If n=0 time step is automatically specified by
tNavigator.
Default: 0.

DVLIM n
Maximal allowed pore volume relative variation. The positive number should be speci-
fied – fraction.
For example if the value 0.5 is specified – this corresponds to 50% variation of this pa-
rameter 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
pore volume variation exceeds this value then the length of the time step will be re-
duced. For example, if the allowed variation is set to 10, and at the current calculation
step the pore 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).
Default: 0.2.

FULLSEPDER n
If n=0 the option is turned off, if n=1 the option is turned on. This option allows to
calculate full derivatives for producers connected with separator if one of rate con-
trols (ORAT, WRAT, GRAT, LRAT or NGL) is specified. This option can be used for
compositional and thermal models.
Default: 0.

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.
This option can not be used in SCHEDULE section.
Default: 0 – the main variable (the last hydrocarbon component) is excluded.

LINEARSOLVERPARAM n
Number of last approximations during partial orthogonalization in the solvers DQGM-
RES and ORTHOMIN.
Default: 15.

12.19.140. RUNCTRL 1772

Keywords for formats tN, E1, E3 19.1

LINEARSOLVERRESTART n
Number of iterations before solver restart.
Default: 50.

MAXELAPSED n
Maximal time of one calculation step (minutes).
Default: -1.

MAXLINIT n
Maximal number of iterations in linear solver.
Default: 400.

MAXNEWTIT n
Maximal number of Newton iterations.
Default: 100 (if the option CHECKSAT is on this limit is set to 10).

MAXWELLHUNTING n
Maximal allowed well mode switches per report timestep.
Default: -1 (not limited).

MAXWELLIT n
Maximal number of iterations for one well.
Default: 8.

MAXSEGWELLIT n
Maximal number of iterations of the linear solver when solving the linear systems for
multisegment wells.
Default: 200.

MBERRLIM n
Maximum allowed material balance error relative variation. The positive number should
be specified. Zero value disables this option.
For example if value 2 is specified then material balance error can increase two times
comparing to its value on the previous time step. If balance error increases more than
two times then restart will be done for this time step.
Default: 2.

MINNEWTIT n
Minimal number of Newton iterations:

• 1 is used by default for 2-phase water-gas models;

• 0 is used for other models.

12.19.140. RUNCTRL 1773

Keywords for formats tN, E1, E3 19.1

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.

NDTAVG n
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.
Default: 1.

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.
Default: 4.

OVERDRAFT n
Coefficient to choose new time step length. MAXNEWTIT divided by the parameter
OVERDRAFT, MAXLINIT divided by the parameter OVERDRAFT.
Default: 2.

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.
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 OPTIONS
parameter):
∑ Porv ∗ pO
PRESSURE =
∑ Porv
Default: 0. The 31-th parameter of OPTIONS (see 12.19.243) is converted into this
keyword.

SMARTMB n
If the option is enabled (1 is set), then the test (experimental) solver will be used. Sig-
nificant optimization of error of material balance is possible (this option can not be used
with dual porosity and dual permeability models).

12.19.140. RUNCTRL 1774

Keywords for formats tN, E1, E3 19.1

This option is experimental and is not part of the standard procedures recom-
mended to increase the accuracy of the numerical convergence process.
This option can not be used in SCHEDULE section.
Default: 0.

TMAXMULT n
Allowed maximal time step increasing factor per one time step (must be > 1).
Default: 3.

TOLLIN n
tolerance of linear solver (the appliance of this parameter see in the section 5.4).
Default: 1.e-3.

TOLNEWT n
Maximal allowed residual to finish Newton iterations (the appliance of this parameter
see in the section 5.4).
Default: 1.e-3.

TOLSEGWELL n
Target convergence tolerance, at which iterations of linear solver for the multisegment
well will be terminated.
Default: 1.e-3.

TOLVARAQ n
Maximal allowed aquifer flow relative variation.
Default: 0.3.

TOLVARNEWT n
Maximal allowed main variables variation to finish.
Default: 1.e-3. Newton iterations (the appliance of this parameter see in the section 5.4).

TOLVARWELL n
Maximal allowed well rate variation between Newton iterations. This value can be
negative then in addition to the restriction on well rate it is required that a well status
doesn’t change during two successive iterations.
Default: 1.e+20.

TOLWELL n
Tolerance of linear solver for one well.
Default: 1.e-3.

12.19.140. RUNCTRL 1775

Keywords for formats tN, E1, E3 19.1

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.
Default: 0.

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.

WDENIMP n
0 – use well average density from previous step, else density is calculated implicitly.
Default: 0.

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;

WELLDENWEIGHTOPEN n
This option applies correction to the calculation of wellbore mixture density in open
wells (i.e. the wells with non-zero rate). This option is similar to 44 − th parameter of
OPTIONS3 (see 12.19.244) keyword, but here the averaging will be applied to the open
wells only.
An integer value n should be specified. The wellbore mixture density will be averaged
according to the equation 12.7.
Default: -1.

WELLDENWEIGHTSTOP n
This option applies correction to the calculation of wellbore mixture density in stopped
wells (i.e. the wells with zero rate). This option is similar to 44 − th parameter of
OPTIONS3 (see 12.19.244) keyword, but here the averaging will be applied to the
stopped wells only.

12.19.140. RUNCTRL 1776

Keywords for formats tN, E1, E3 19.1

An integer value n should be specified. The wellbore mixture density will be averaged
according to the equation 12.7.
Default: -1.

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
approximating the filtering problem consists of two parts, describing flow in the grid
blocks and the flow in the wells respectively.
Default: 1.
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 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.19.6).
This option can not be used in SCHEDULE section.

WFRACFLOW n
0 – use flows between well and fracture connections in Jacobian, 1 – in Jacobian all
flows between fractures and well bore are used.
This option can not be used in SCHEDULE section.

Default: 1.

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 resid-
ual of the equation is equal to the difference of material balance of the left and right sides.
The default value of this residual is 1.e-3 (kg). Which corresponds to 1.e-6 (m 3 at reservoir

12.19.140. RUNCTRL 1777

Keywords for formats tN, E1, E3 19.1

conditions) for the liquid phases.

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

12.19.140. RUNCTRL 1778

Keywords for formats tN, E1, E3 19.1

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.19.140. RUNCTRL 1779

Keywords for formats tN, E1, E3 19.1

12.19.141. MULTSIG

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword can be used in dual porosity run 2.27 (DUALPORO, see 12.1.83) if
matrix-fracture coupling transmissibilities (sigma-factor) is set using the keywords SIGMA
(see 12.2.72), SIGMAV (see 12.2.73). 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.19.142).

The effect of the keyword is cumulative: if it is used multiple times or it is used with
MULTSIGV (see 12.19.142).
Example
MULTSIG
0.3 /

12.19.141. MULTSIG 1780

Keywords for formats tN, E1, E3 19.1

12.19.142. MULTSIGV

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword can be used in dual porosity run 2.27 (DUALPORO, see 12.1.83) if
matrix-fracture coupling transmissibilities (sigma-factor) is set using the keywords SIGMA
(see 12.2.72), SIGMAV (see 12.2.73). Sigma-factor is multiplied by the multiplier MULTSIGV.

One should enter NX * NY * (NZ/2) values (matrix blocks). The data should be ter-
minated with a slash /. The common multiplier for all grid blocks can be entered using the
keyword MULTSIG (see 12.19.141).

The effect of the keyword is cumulative: if it is used multiple times or it is used with
MULTSIG (see 12.19.141).
Example
MULTSIGV
20*0.44 30*0.21/
In this example the multiplier is set for 50 blocks: for 20 blocks it is equal to 0.44, and
for 30 blocks – 0.21.

12.19.142. MULTSIGV 1781

Keywords for formats tN, E1, E3 19.1

12.19.143. WFRAC

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies the hydraulic fracture. 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 /.
The description of the mathematical model of hydraulic fracture in tNavigator is in the
section Modified well model (5.7).

Keywords to specify hydraulic fractures: WFRAC (see 12.19.143), WFRACP

(see 12.19.145), COMPFRAC (see 12.19.148). An in local grid refinements LGR: WFR-
ACL (see 12.19.144), WFRACPL (see 12.19.146), COMPFRACL (see 12.19.149). 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.19.145) (WFRACPL,
see 12.19.146). WFRAC (see 12.19.143) and COMPFRAC (see 12.19.148) are its reductions.
The differences between COMPFRAC (see 12.19.148) and WFRAC (see 12.19.143):

• 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 .

The following parameters should be specified in one line of WFRAC (see 12.19.143):

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;

7. last connection (or trajectory) coordinate in Z direction;

12.19.143. WFRAC 1782

Keywords for formats tN, E1, E3 19.1

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);
Default: not defined; infinite permeability along the fracture (pipe).

13. dependence between fracture permeability and flown phase volume or time. One of the
following parameters should be specified:

• flow function name (the dependence between fracture permeability and phase flow
or time). 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);
• number of days (is case if the next parameter is – TIME). Dependence of perme-
ability versus time is set via the the following formula:
D−T
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.
Default: not defined; there is no dependance from the flow.

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).

Example
WFRAC
'WELL123' 38 426 13 38 426 21 30 0.5 250 0.02 'proppant 16/20'
'func 5' 'LIQ'
/

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 – 0.02, proppant 16/20, flow function –
func 5, dependence of liquid flow – LIQ.

12.19.143. WFRAC 1783

Keywords for formats tN, E1, E3 19.1

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 proppants and flow functions.

12.19.143. WFRAC 1784

Keywords for formats tN, E1, E3 19.1

12.19.144. WFRACL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies the hydraulic fracture for the wells in local grids (section 5.5.8).
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 /.
The description of the mathematical model of hydraulic fracture in tNavigator is in the
section Modified well model (5.7).

WFRACL must be used in place of WFRAC (see 12.19.143) to specify the hydraulic frac-
ture for wells in local refined grids, after the wells have been introduced with keywords
WELSPECL (see 12.19.4), COMPDATL (see 12.19.7). The keyword data for WFRACL is the
same as for WFRAC (see 12.19.143), except for an extra parameter 2 which names the local
grid containing the connections specified in the record.

Keywords to specify hydraulic fractures: WFRAC (see 12.19.143), WFRACP

(see 12.19.145), COMPFRAC (see 12.19.148). An in local grid refinements LGR: WFR-
ACL (see 12.19.144), WFRACPL (see 12.19.146), COMPFRACL (see 12.19.149). 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.19.145) (WFRACPL,
see 12.19.146).
WFRAC (see 12.19.143) and COMPFRAC (see 12.19.148) are its reductions. The differences
between COMPFRAC (see 12.19.148) and WFRAC (see 12.19.143):

• 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 .

The following parameters should be specified in one line of WFRACL (see 12.19.144):

1. well name;

2. local grid name (CARFIN, see 12.2.97);

3. first connection (or trajectory) coordinate in X direction;

12.19.144. WFRACL 1785

Keywords for formats tN, E1, E3 19.1

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;

9. azimuth angle (from 0 ◦ to 360 ◦ );

10. zenith angle (from 0 ◦ to 90 ◦ );

11. half of fracture length (METRIC: m, FIELD: f t );

12. fracture width (METRIC: m, FIELD: f t );

13. proppant name (the name should be input via the keyword PROPANTNAMES,
see 12.8.2);
Default: not defined; infinite permeability along the fracture (pipe).

14. dependence between fracture permeability and flown phase volume or time. One of the
following parameters should be specified:

• flow function name (the dependence between fracture permeability and phase flow
or time). 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);
• number of days (is case if the next parameter is – TIME). Dependence of perme-
ability versus time is set via the the following formula:
D−T
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.
Default: not defined; there is no dependance from the flow.

15.• 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).

12.19.144. WFRACL 1786

Keywords for formats tN, E1, E3 19.1

Example
WFRACL
'WELL123' 'LGR2' 38 426 13 38 426 21 30 0.5 250 0.02 'proppant
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 – 0.02, proppant
16/20, flow function – func 5, dependence of liquid flow – LIQ.

12.19.144. WFRACL 1787

Keywords for formats tN, E1, E3 19.1

12.19.145. WFRACP

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies the hydraulic fracture. This keyword is the expansion of the key-
word WFRAC (see 12.19.143). 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 /.
The description of the mathematical model of hydraulic fracture in tNavigator is in the
section Modified well model (5.7).

On the pictures below there is scheme of hydraulic fracture in the plane, which contains
the well bore, - picture 58, and hydraulic fracture for horizontal well, which contains one
connection, - picture 59.

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.19.143), WFRACL (see 12.19.144),
WFRACP (see 12.19.145), WFRACPL (see 12.19.146), COMPFRAC (see 12.19.148),
COMPFRACL (see 12.19.149) passes through the inactive blocks until it reaches its half-
length. Thus, the flow through inactive blocks is possible.

The following parameters should be specified:

1. well name;

2. i1 – first connection coordinate in X direction;

Default: if parameters 2-7 of this keyword (i1, i2, j1, j2, k1, k2) are defaulted then
all well’s connections will be taken;.

3. j1 – first connection coordinate in Y direction;

Default: if parameters 2-7 of this keyword (i1, i2, j1, j2, k1, k2) are defaulted then
all well’s connections will be taken;.

4. k1 – first connection coordinate in Z direction;

Default: if parameters 2-7 of this keyword (i1, i2, j1, j2, k1, k2) are defaulted then
all well’s connections will be taken;.

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;

12.19.145. WFRACP 1788

Keywords for formats tN, E1, E3 19.1

Default: if parameters 2-7 of this keyword (i1, i2, j1, j2, k1, k2) are defaulted then
all well’s connections will be taken;.

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;
Default: if parameters 2-7 of this keyword (i1, i2, j1, j2, k1, k2) are defaulted then
all well’s connections will be taken;.

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;
Default: if parameters 2-7 of this keyword (i1, i2, j1, j2, k1, k2) are defaulted then
all well’s connections will be taken;.

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 (60) and tNavigator 3D map (61) 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) doesn’t correspond to this logic in
graphical interface check please if the keyword MAPAXES (see 12.2.67) is specified or
the visualization option Flip vertically is used.
Note 2: Default values of azimuth angle and GEOMECH (see 12.1.99) 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);
Default: Default values of azimuth and zenith angle and GEOMECH (see 12.1.99) op-
tion 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 ◦ .

9. zenith angle (from 0 ◦ to 90 ◦ ).

Default: 0.

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);

12.19.145. WFRACP 1789

Keywords for formats tN, E1, E3 19.1

Figure 58. Fracture in the plane, which contains the well bore

Figure 59. Fracture on horizontal well

12.19.145. WFRACP 1790

Keywords for formats tN, E1, E3 19.1

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);
Default: not defined; inifite permeability along the fracture.
• proppant permeability (mD). In this case proppant will have constant permeability
(see Example 5).

16. dependence between fracture permeability and flown phase volume or time. One of the
following parameters should be specified:

• flow function name (the dependence between fracture permeability and phase flow
or time). 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);
Default: not defined, there is no dependance from flow.
• number of days (is case if the next parameter is – TIME). Dependence of perme-
ability versus time is set via the the following formula:
D−T
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.

17. 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);

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 multiplier
to account for the contribution of fracture to the well productivity.

!
This parameter may be used as a tuning parameter for history matching.
User can leave it in default value, if there is no need to make a history
matching.
Default: 1.

19. X1-coordinate of bounding box (the fracture shouldn’t be outside this box) (number of
layer in X direction should be specified);
Default: 1 (if this parameter is set as zero, the default value will be used as well).

12.19.145. WFRACP 1791

Keywords for formats tN, E1, E3 19.1

20. Y1-coordinate of bounding box (the fracture shouldn’t be outside this box) (number of
layer in Y direction should be specified);
Default: 1 (if this parameter is set as zero, the default value will be used as well).

21. Z1-coordinate of bounding box (the fracture shouldn’t be outside this box) (number of
layer in Z direction should be specified);
Default: 1 (if this parameter is set as zero, the default value will be used as well).

22. X2-coordinate of bounding box (the fracture shouldn’t be outside this box) (number of
layer in X direction should be specified);
Default: NX (see 12.1.28) (If this parameter is set as zero then default value will be
used as well).

23. Y2-coordinate of bounding box (the fracture shouldn’t be outside this box) (number of
layer in Y direction should be specified);
Default: NY (see 12.1.28) (If this parameter is set as zero then default value will be
used as well).

24. Z2-coordinate of bounding box (the fracture shouldn’t be outside this box) (number of
layer in Z direction should be specified).
Default: NZ (see 12.1.28) (If this parameter is set as zero then default value will be
used as well).

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.

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 con-
nection – [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
dependence), fracture productivity multiplier - 3, coordinate of bounding box – non specified
(i.e. the reservoir).

12.19.145. WFRACP 1792

Keywords for formats tN, E1, E3 19.1

Figure 60. Scheme: Azimuth angle and half-length L1 and L2

Figure 61. 3D map: Azimuth angle and half-length L1 and L2

12.19.145. WFRACP 1793

Keywords for formats tN, E1, E3 19.1

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,
proppant PROPPANT1, flow function FLOWFUNC1, time dependence (TIME).

Example 3.

12.19.145. WFRACP 1794

Keywords for formats tN, E1, E3 19.1

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 calcu-
lated 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.19.145. WFRACP 1795

Keywords for formats tN, E1, E3 19.1

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.28) specifies the diagonal elements of
the stress tensor (the regional stress), the keyword ROCKAXES (see 12.5.27) specifies the
direction of the principal axes X, Y, Z of stress tensor (the regional stress). 8 and 9 parameters
of WFRACP (see 12.19.145) 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.19.145. WFRACP 1796

Keywords for formats tN, E1, E3 19.1

12.19.146. WFRACPL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies the hydraulic fracture for the wells in local grids (section 5.5.8).
This keyword is the extension of the keyword WFRAC (see 12.19.143). WFRACP is used to
specify hydraulic fracture from graphical interface.

The description of the mathematical model of hydraulic fracture in tNavigator is in the

section Modified well model (5.7).

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.19.145) to specify the hydraulic
fracture for wells in local refined grids, after the wells have been introduced with keywords
WELSPECL (see 12.19.4), COMPDATL (see 12.19.7). The keyword data for WFRACPL is the
same as for WFRACP (see 12.19.145), 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.19.145) there is scheme
of hydraulic fracture in the plane, which contains the well bore, - picture 58, and hydraulic
fracture for horizontal well, which contains one connection, - picture 59.

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.19.143), WFRACL (see 12.19.144),
WFRACP (see 12.19.145), WFRACPL (see 12.19.146), COMPFRAC (see 12.19.148),
COMPFRACL (see 12.19.149) passes through the inactive blocks until it reaches its half-
length. Thus, the flow through inactive blocks is possible.

The following parameters should be specified:

1. well name;

2. local grid name (CARFIN, see 12.2.97);

3. i1 – first connection coordinate in X direction;

Default: if parameters 3-8 of this keyword (i1, i2, j1, j2, k1, k2) are defaulted then
all well’s connections will be taken;.

12.19.146. WFRACPL 1797

Keywords for formats tN, E1, E3 19.1

4. j1 – first connection coordinate in Y direction;

Default: if parameters 3-8 of this keyword (i1, i2, j1, j2, k1, k2) are defaulted then
all well’s connections will be taken;.

5. k1 – first connection coordinate in Z direction;

Default: if parameters 3-8 of this keyword (i1, i2, j1, j2, k1, k2) are defaulted then
all well’s connections will be taken;.

6. 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;
Default: if parameters 3-8 of this keyword (i1, i2, j1, j2, k1, k2) are defaulted then
all well’s connections will be taken;.

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;
Default: if parameters 3-8 of this keyword (i1, i2, j1, j2, k1, k2) are defaulted then
all well’s connections will be taken;.

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;
Default: if parameters 3-8 of this keyword (i1, i2, j1, j2, k1, k2) are defaulted then
all well’s connections will be taken;.

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 (60) and tNavigator 3D map (61) 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) doesn’t correspond to this logic in
graphical interface check please if the keyword MAPAXES (see 12.2.67) is specified or
the visualization option Flip vertically is used.

10. zenith angle (from 0 ◦ to 90 ◦ );

Default: 0.

11. 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);

12. 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);

13. h1 – fracture height in one direction from the well bore (METRIC: m, FIELD: f t );

12.19.146. WFRACPL 1798

Keywords for formats tN, E1, E3 19.1

14. h2 – fracture height in second direction from the well bore (METRIC: m, FIELD: f t );
15. fracture width (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);
Default: not defined, infinite permaebility along the fracture (pipe).
• proppant permeability (mD). In this case proppant will have constant permeability.
17. dependence between fracture permeability and flown phase volume or time. One of the
following parameters should be specified:
• flow function name (the dependence between fracture permeability and phase flow
or time). 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);
• number of days (is case if the next parameter is – TIME). Dependence of perme-
ability versus time is set via the the following formula:
D−T
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.
Default: phase volume or time not defined, there is no dependence from flow.
18.• 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);
19. 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 multiplier
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.

!
This parameter may be used as a tuning parameter for history matching.
User can leave it in default value, if there is no need to make a history
matching.
Default: 1.

12.19.146. WFRACPL 1799

Keywords for formats tN, E1, E3 19.1

20. X1-coordinate of bounding box (the fracture shouldn’t be outside this box) (number of
layer in X direction should be specified);
Default: 1 (if this parameter is set to 0, then default value will be taken).
21. Y1-coordinate of bounding box (the fracture shouldn’t be outside this box) (number of
layer in Y direction should be specified);
Default: 1 (if this parameter is set to 0, then default value will be taken).
22. Z1-coordinate of bounding box (the fracture shouldn’t be outside this box) (number of
layer in Z direction should be specified);
Default: 1 (if this parameter is set to 0, then default value will be taken).
23. X2-coordinate of bounding box (the fracture shouldn’t be outside this box) (number of
layer in X direction should be specified);
Default: NX (see 12.1.28) (If this parameter is set as zero then default value will be
used as well).
24. Y2-coordinate of bounding box (the fracture shouldn’t be outside this box) (number of
layer in Y direction should be specified);
Default: NY (see 12.1.28) (If this parameter is set as zero then default value will be
used as well).
25. Z2-coordinate of bounding box (the fracture shouldn’t be outside this box) (number of
layer in Z direction should be specified).
Default: NZ (see 12.1.28) (If this parameter is set as zero then default value will be
used as well).
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.
Fracture is presented as a part of plane (is visualized in graphical interface), virtual perfo-
rations 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 'prop-
pant 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 – proppant 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.19.146. WFRACPL 1800

Keywords for formats tN, E1, E3 19.1

12.19.147. FRACTURE_STAGE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword activates a set of fractures specified with the keyword FRACTURE_WELL
(see 12.2.128). More detailed information about how to create a fracture model using the local
grid refinement (LGR) is given in the section 5.8.
On a new line after the keyword the following parameters should be specified:

1. name of set of fractures (stage);

2. status of set of fractures:

• ON – set of fractures is activated;

• OFF – set of fractures is not activated.

3. arithmetic name – if arithmetic is specified it will be applied to the stage.

Data should be terminated with a slash / on a new line.

Example
FRACTURE_WELL
'STAGE_ONE' 'well' 0 MD /
'TEMPLATE_ONE' 0 /
/
...
FRACTURE_STAGE
STAGE_ONE ON ARITHMETIC_ONE /
/
In this example the set of fractures 'STAGE_ONE'is activated. The arithmetic 'ARITH-
METIC_ONE'is applied to this set of fractures.

12.19.147. FRACTURE_STAGE 1801

Keywords for formats tN, E1, E3 19.1

12.19.148. COMPFRAC

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets the hydraulic fracture for connection in the grid layer.

The description of the mathematical model of hydraulic fracture in tNavigator is in the

section Modified well model (5.7).

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 /.
Keywords to specify hydraulic fractures: WFRAC (see 12.19.143), WFRACP
(see 12.19.145), COMPFRAC (see 12.19.148). An in local grid refinements LGR: WFR-
ACL (see 12.19.144), WFRACPL (see 12.19.146), COMPFRACL (see 12.19.149). 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.19.145) (WFRACPL,
see 12.19.146).
WFRAC (see 12.19.143) and COMPFRAC (see 12.19.148) are its reductions. The differences
between COMPFRAC (see 12.19.148) and WFRAC (see 12.19.143):
• 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 .
The following parameters should be specified in one line of COMPFRAC (see 12.19.148):
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.19.6). Via ACTIONC
(see 12.19.167) 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 be
defaulted (the values specified via the keyword COMPDAT, see 12.19.6). Via ACTIONC
(see 12.19.167) all values could be defaulted, i.e. "the value should be taken from the
connection for which "ACTIONC" condition is satisfied";

12.19.148. COMPFRAC 1802

Keywords for formats tN, E1, E3 19.1

4. k – connection coordinate in Z direction. Via ACTIONC (see 12.19.167) 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;

6. azimuth angle (from 0 ◦ to 360 ◦ );

7. proppant name (the name should be input via the keyword PROPANTNAMES,
see 12.8.2);
Default: not defined, infinite permeability along the fracture (pipe).

8. dependence between fracture permeability and flown phase volume or time. One of the
following parameters should be specified:

• 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.
Default: no dependence defined; fracture permeability does not change. (keywords
FLOWFUNC (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:
D−T
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.

9. 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);

10. skin – fracture efficiency; specified as skin-factor in classical approximation of hydraulic

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;
Default: 0.

11. pi – fracture productivity multiplier;

Default: 1.

12.19.148. COMPFRAC 1803

Keywords for formats tN, E1, E3 19.1

12. mult – fracture length multiplier;

Default: 1.

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: BLOCK.

The keyword creates the hydraulic fracture. The differences with the fracture, created with
WFRAC (see 12.19.143), are the following:

• 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 .

Example
COMPFRAC
'WELL123' 38 426 13 OPEN 30 'proppant 16/20' 'func 5' 'LIQ' -4 3*
/
/

In this example hydraulic fracture is specified the following way: well WELL123, connec-
tion – [38, 426, 13], azimuth angle – 30 ◦ , proppant 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.19.148. COMPFRAC 1804

Keywords for formats tN, E1, E3 19.1

12.19.149. COMPFRACL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets the hydraulic fracture for connection in the grid layer for the wells in
local grids (section 5.5.8).

The description of the mathematical model of hydraulic fracture in tNavigator is in the

section Modified well model (5.7).

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 /.
COMPFRACL must be used in place of COMPFRAC (see 12.19.148) 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.19.4), COMPDATL (see 12.19.7).
The keyword data for COMPFRACL is the same as for COMPFRAC (see 12.19.148), except
for an extra parameter 2 which names the local grid containing the connections specified in
the record.

Keywords to specify hydraulic fractures: WFRAC (see 12.19.143), WFRACP

(see 12.19.145), COMPFRAC (see 12.19.148). An in local grid refinements LGR: WFR-
ACL (see 12.19.144), WFRACPL (see 12.19.146), COMPFRACL (see 12.19.149). 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.19.145) (WFRACPL,
see 12.19.146).
WFRAC (see 12.19.143) and COMPFRAC (see 12.19.148) are its reductions. The differences
between COMPFRAC (see 12.19.148) and WFRAC (see 12.19.143):

• 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 .

The following parameters should be specified in one line of COMPFRACL (see 12.19.149):

1. well name – well name;

12.19.149. COMPFRACL 1805

Keywords for formats tN, E1, E3 19.1

2. local grid name (CARFIN, see 12.2.97);

3. i – connection coordinate in X direction. For vertical wells coordinates i, j can be

defaulted (the values specified via the keyword COMPDAT, see 12.19.6). Via ACTIONC
(see 12.19.167) all values could be defaulted, i.e. "the value should be taken from the
connection for which "ACTIONC" condition is satisfied";

4. j – connection coordinate in Y direction; For vertical wells coordinates i, j can be

defaulted (the values specified via the keyword COMPDAT, see 12.19.6). Via ACTIONC
(see 12.19.167) all values could be defaulted, i.e. "the value should be taken from the
connection for which "ACTIONC" condition is satisfied";

5. k – connection coordinate in Z direction. Via ACTIONC (see 12.19.167) 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;

7. azimuth angle (from 0 ◦ to 360 ◦ );

8. proppant name (the name should be input via the keyword PROPANTNAMES,
see 12.8.2);
Default: not defined; infinite permeability along the fracture (pipe).

9. dependence between fracture permeability and flown phase volume or time. One of the
following parameters should be specified:

• 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);
Default: no dependence defined; fracture permeability does not change.
• 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:
D−T
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.

12.19.149. COMPFRACL 1806

Keywords for formats tN, E1, E3 19.1

10. 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);

11. skin – fracture efficiency; specified as skin-factor in classical approximation of hydraulic

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;
Default: 0.

12. pi – fracture productivity multiplier;

Default: 1.

13. mult – fracture length multiplier;

Default: 1.

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: BLOCK.

The keyword creates the hydraulic fracture. The differences with the fracture, created with
WFRACL (see 12.19.144), are the following:

• 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 .

Example
COMPFRACL
'WELL123' 'LGR2' 38 426 13 OPEN 30 'proppant 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 ◦ , proppant 16/20, flow
function (dependence of phase LIQ) – func 5, skin = -4.

12.19.149. COMPFRACL 1807

Keywords for formats tN, E1, E3 19.1

12.19.150. WPIFUNC

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies for the connection the function of dependence between permeability
and phase flow. Efficiency factor (the keyword WPIMULT, see 12.19.35) is multiplied by this
function (5.14).
The data should be terminated with a slash /. All data should be terminated with a final
slash /.
The following parameters should be specified:

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);
Default: not defined; there is no dependence from flow rate.

3. 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);

4. connection (or trajectory) coordinate in X direction;

5. connection (or trajectory) coordinate in Y direction;

6. connection (or trajectory) coordinate in Z direction;

7. number of first completion in range (completion numbers are set via COMPLUMP,
see 12.19.29),
Default: any number.

8. number of last completion in range (completion numbers are set via COMPLUMP,
see 12.19.29),
Default: any number.

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.

12.19.150. WPIFUNC 1808

Keywords for formats tN, E1, E3 19.1

Example
WPIFUNC
'WELL123' 'func 5' 'LIQ' 38 426 13 3 9 /
/

12.19.150. WPIFUNC 1809

Keywords for formats tN, E1, E3 19.1

12.19.151. WSKFUNC

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies for the connection the function of dependence between skin-factor
and phase flow. Skin-factor (the keyword COMPDAT, see 12.19.6) is multiplied by this func-
tion (5.15).
The data should be terminated with a slash /. All data should be terminated with a final
slash /.
The following parameters should be specified:

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);
Default: not defined; there is no dependence from flow rate.

3. 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);

4. connection (or trajectory) coordinate in X direction;

5. connection (or trajectory) coordinate in Y direction;

6. connection (or trajectory) coordinate in Z direction;

7. number of first completion in range (completion numbers are set via COMPLUMP,
see 12.19.29),
Default: any number.

8. number of last completion in range (completion numbers are set via COMPLUMP,
see 12.19.29),
Default: any number.

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.

12.19.151. WSKFUNC 1810

Keywords for formats tN, E1, E3 19.1

Example
WSKFUNC
'WELL34' 'func 2' 'OIL' 38 426 13 3 9 /
/

12.19.151. WSKFUNC 1811

Keywords for formats tN, E1, E3 19.1

12.19.152. WBHZONE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies the properties of well bottom zone (5.15).

The data should be terminated with a slash /. All data should be terminated with a final
slash /.
The following parameters should be specified:

1. well name;
w,l
2. radius of well bottom zone rbhz (5.15) (METRIC: m, FIELD: f t );
Default: not specified.

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);
Default: not defined; there is no dependence from flow rate.

4. 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: LIQ.
w,l
5. permeability of well bottom zone in radial direction Kbhz (5.15);
Default: not defined.

6. permeability of well bottom zone in vertical direction K w,l (5.15);

Default: not defined.

7. connection (or trajectory) coordinate in X direction;

8. connection (or trajectory) coordinate in Y direction;

9. connection (or trajectory) coordinate in Z direction;

10. number of first completion in range (completion numbers are set via COMPLUMP,
see 12.19.29),
Default: any number.

12.19.152. WBHZONE 1812

Keywords for formats tN, E1, E3 19.1

11. number of last completion in range (completion numbers are set via COMPLUMP,
see 12.19.29),
Default: any number.

After processing acids, surfactants etc. the inflow is calculated using the formula 5.16 (see
section 5.7.10).
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.

Example
WBHZONE
'PROD' 2 'func 2' 'OIL' 10 0.1 4 17 2/
/

12.19.152. WBHZONE 1813

Keywords for formats tN, E1, E3 19.1

12.19.153. WLIMTOL

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets tolerance fractures for economic and other limits. The data should be
terminated with a slash /.

The tolerance fraction is applied to the following limits:

1. connection, well, group, field economic limits (WECON (see 12.19.74), GECON
(see 12.19.121), WECONINJ, see 12.19.81);

2. group, field maximum rate limits resulting in well workovers or closures (GCONPROD,
see 12.19.86).

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.19.153. WLIMTOL 1814

Keywords for formats tN, E1, E3 19.1

12.19.154. SEPVALS

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.19.155), which allocates well groups to separators. If the
separator corresponds to a group, all wells of this group use this separator. If the separator’s
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. Keywords used to specify a separator
for models in E1 and E3 formats are given in the section 2.14.4.

There must be at least one TSTEP (see 12.19.125) or DATES (see 12.19.124) 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 data line should be
terminated with the symbol /. All 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.39);

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).

12.19.154. SEPVALS 1815

Keywords for formats tN, E1, E3 19.1

Example
SEPVALS
SEP1A 1.24 0.49 /
SEP1B 1.243 0.50 /
SEP1C 1.252 0.514 /
/
...
GSEPCOND
GROUP1 SEP1A /
GROUP2 SEP1B /
P* SEP1C /
/

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.19.154. SEPVALS 1816

Keywords for formats tN, E1, E3 19.1

12.19.155. GSEPCOND

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword assigns separators to well groups. Each separator should be specified earlier
via SEPVALS (see 12.19.154). If the separator corresponds to a group, all wells of this group
use this separator. If the separator’s conditions are altered by redefining them via SEPVALS
(see 12.19.154), then the oil and gas rates of these wells are transformed to reflect the change
in conditions. Keywords used to specify a separator for models in E1 and E3 formats are given
in the section 2.14.4.

The keyword can be followed by any number of data rows. Each data line should be
terminated with the symbol /. All data should be terminated with a final slash /.
Each row consists of the following parameters:

• group name, or group mask defining a subset of groups with common prefix (should
end 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).

Example
GSEPCOND
GROUP1 SEP1A /
GROUP2 SEP1B /
P* SEP1C /
/

In this example well group GROUP1 uses the separator SEP1A, well group GROUP2 uses
the separator SEP1B, all wells with name begins with P use the separator SEP1C.
Example
GSEPCOND
FIELD SEP1A /
/

In this example all wells belonging to the field use a separator SEP1A.

12.19.155. GSEPCOND 1817

Keywords for formats tN, E1, E3 19.1

12.19.156. SEPCOND

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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 associ-
ated with the well via the keyword WSEPCOND (see 12.19.157). Keywords used to specify a
separator for models in E1 and E3 formats are given in the section 2.14.4.

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 data line should be terminated with the symbol /. All data should
be terminated with a final slash /.
One data row contains the following parameters:

1. Separator name.

2. Group name or group mask defining a subset of groups with common prefix (should end
with an asterisk *), 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.19.157), then it will
be used instead of group separator. Similarly, if the group contains subgroups having
default separators, then these subgroups will use their assigned separators instead of the
group separator.
Default: not specified.

3. Stage number.
Default: 1.

4. Separator stage temperature (METRIC: ◦ C, FIELD: ◦ F).

Default: 15.56 ◦ C.

5. Separator stage pressure (METRIC: barsa, FIELD: psia).

Default: 1.013 barsa.

6. 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.
Default: 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).

12.19.156. SEPCOND 1818

Keywords for formats tN, E1, E3 19.1

7. Gas destination output from the separator;

Default: 0. Gas is accumulated in the stock tank or field separator vapor. The volume is
converted to the standard conditions.

8. K-value table number (IGNORED), this is an E1/E3 compatibility field;

9. Gas plant table number. If for the separator instead of the equation of state gas plant
table will be used (see section 2.14.5). Tables are specified via keywords GPTABLE
(see 12.16.26), GPTABLE3 (see 12.16.28), GPTABLEN (see 12.16.27). If 0 value is
specified then gas plant table is not used and calculation of equation of state will be
done.
Default: 0.

10. Surface equation of state number.

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.19.156. SEPCOND 1819

Keywords for formats tN, E1, E3 19.1

12.19.157. WSEPCOND

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword assigns separator to well. Separator name should be previously defines via
the keyword SEPCOND (see 12.19.156). Keywords used to specify a separator for models in
E1 and E3 formats are given in the section 2.14.4.

The keyword can be followed by any number of data rows. Each data line should be
terminated with the symbol /. All data should be terminated with a final slash /.
Each row consists of the following parameters:

• well name (or a first part of name ending with an asterisk), or well list name defined
via WLIST (see 12.19.33);

• name of the separator associated with this well (separator name should be previously
defines via SEPCOND, see 12.19.156).

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.19.157. WSEPCOND 1820

Keywords for formats tN, E1, E3 19.1

12.19.158. ACTION

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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 key-
words that are to be stored for later processing when a specified condition is satisfied. The
keyword ACTION specifies a field condition for triggering an action. Keywords ACTIONG
(see 12.19.159), ACTIONR (see 12.19.160), ACTIONW (see 12.19.161) offer greater flexibil-
ity, and specify actions triggered by group, region, well conditions respectively.

Keyword ACTIONX (see 12.19.162) 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 EN-
DACTIO, with the exception of time stepping keywords (TSTEP (see 12.19.125), DATES
(see 12.19.124), 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.19.158. ACTION 1821

Keywords for formats tN, E1, E3 19.1

• 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.19.158. ACTION 1822

Keywords for formats tN, E1, E3 19.1

12.19.159. ACTIONG

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.19.125), DATES
(see 12.19.124), etc.).

Each action keyword set must be bracketed by a pair of ACTION (G, R, W) and ENDAC-
TIO 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 previously declared
action is deleted and replaced with the new action.

The following parameters are to be specified (The data should be terminated with a slash
/.):

1. action name;

2. group name or group mask defining a subset of groups with common prefix (should
end with an asterisk *) 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 action’s 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.19.159. ACTIONG 1823

Keywords for formats tN, E1, E3 19.1

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;
Default: 1.
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 spec-
ified increment is added to the triggering condition value (initialized in parameter 5).
The increment may be negative, if desired.
Default: 0.

12.19.159. ACTIONG 1824

Keywords for formats tN, E1, E3 19.1

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.19.159. ACTIONG 1825

Keywords for formats tN, E1, E3 19.1

12.19.160. ACTIONR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword initiates a set of keywords to be processed when a region satisfies a specified
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.19.125), DATES
(see 12.19.124), etc.).

Each action keyword set must be bracketed by a pair of ACTION (G, R, W) and ENDAC-
TIO 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 previously declared
action is deleted and replaced with the new action.

The following parameters are to be specified (The data should be terminated with a slash
/.):
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).

4. the quantity to which the triggering condition applies:

• RPR — Region pressure,

12.19.160. ACTIONR 1826

Keywords for formats tN, E1, E3 19.1

• ROIP — Region oil in place,

• RWIP — Region water in place,
• RGIP — Region gas in place (in liquid and gas phases).

5. the operator for the triggering condition:

• < – Less than;

• > – Greater than.

6. the value of the triggering condition;

Default: 1.

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;

8. increment to the triggering condition. After each time the action is performed, the spec-
ified increment is added to the triggering condition value (initialized in parameter 6).
The increment may be negative, if desired.
Default: 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.19.160. ACTIONR 1827

Keywords for formats tN, E1, E3 19.1

12.19.161. ACTIONW

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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-
DACTIO, with the exception of timestepping keywords (TSTEP (see 12.19.125), DATES
(see 12.19.124), etc.).

Each action keyword set must be bracketed by a pair of ACTION (G, R, W) and ENDAC-
TIO 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 previously declared
action is deleted and replaced with the new action.

The following parameters are to be specified (The data should be terminated with a slash
/.):
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 action’s
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;

3. the quantity to which the triggering condition applies:

• WOPR — Well oil production rate,

• WOPT — Well oil production cumulative total,
• WOIR — Well oil injection rate,

12.19.161. ACTIONW 1828

Keywords for formats tN, E1, E3 19.1

• 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.

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 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: 1.

7. increment to the triggering condition. After each time the action is performed, the spec-
ified increment is added to the triggering condition value (initialized in parameter 5).
The increment may be negative, if desired.
Default: 0.

12.19.161. ACTIONW 1829

Keywords for formats tN, E1, E3 19.1

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.19.161. ACTIONW 1830

Keywords for formats tN, E1, E3 19.1

12.19.162. ACTIONX

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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-
DACTIO, with the exception of timestepping keywords (TSTEP (see 12.19.125), DATES
(see 12.19.124), etc.).

Keywords ACTION (G, R, W) set the condition only for one parameter for group, well,
field. Keyword ACTIONX (see 12.19.162) 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.19.33). The condition on specified
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 conditions
is satisfied;

12.19.162. ACTIONX 1831

Keywords for formats tN, E1, E3 19.1

• 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 as long as the specified set of conditions is satisfied and until the action
is applied this many times. The number 10000 or greater is interpreted as infinity;
Default: 1.

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: 0 (days).
Second and next data rows (The data should be terminated with a slash /.):
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 can’t 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);
• OR – or (a condition specified in this row OR a condition in the next row must be
true).

All data should be terminated with a final slash /.

12.19.162. ACTIONX 1832

Keywords for formats tN, E1, E3 19.1

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.19.162. ACTIONX 1833

Keywords for formats tN, E1, E3 19.1

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.18.1) are
available.
FIELD:
1. parameter for FIELD: all parameters that are supported in SUMMARY (see 12.18.1) are
available.
Group:
1. parameter for group: all parameters that are supported in SUMMARY (see 12.18.1) are
available.
Connection:
1. parameter for connection: all parameters that are supported in SUMMARY (see 12.18.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.

6. Default: i,j,k — coordinates of grid block with connection – negative (allows any value).
Multisegment well:
1. well segment keyword: all segment keywords supported in SUMMARY (see 12.18.1)
are available.

12.19.162. ACTIONX 1834

Keywords for formats tN, E1, E3 19.1

2. multisegment well name;

3. well segment number. An integer belonging to the interval from 1 to maximal number
of well segments (specified by WSEGDIMS, see 12.1.41).

Below the list of options that are not supported in ACTIONX (see 12.19.162) in this mo-
ment.

ALWAYS condition: 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.19.97) and water injection rate is specified for satellite group
(GSATINJE, see 12.19.98).

Example 2.

12.19.162. ACTIONX 1835

Keywords for formats tN, E1, E3 19.1

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.

Example 3.
Example
ACTIONX
ACT_VALV 10000 /
SGFR 'WELL1' 3 > 10000 /
/
WSEGVALV
WELL1 3 3 3E-4 1* 4E-1 1* 1E-1 SHUT 3.2E-4 /
/
ENDACTIO

In this example the action ACT_VALV will close an inflow control device (ICD) if the
gas ratio from the first segment exceeds 10000.

12.19.162. ACTIONX 1836

Keywords for formats tN, E1, E3 19.1

12.19.163. DELAYACT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.19.164).
The following parameters should be specified:

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).

Each data line should be ended by a symbol /. The data should be terminated with a slash
/.

Default:

• number of times this action can be performed: 1;

• number of days to add to delay after each action activating: 0.

12.19.163. DELAYACT 1837

Keywords for formats tN, E1, E3 19.1

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.19.163) 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.19.162).

12.19.163. DELAYACT 1838

Keywords for formats tN, E1, E3 19.1

12.19.164. ENDACTIO / ENDACTION

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

These keyword are used at the end of data when keywords ACTION (see 12.19.158),
ACTIONG (see 12.19.159), ACTIONR (see 12.19.160), ACTIONW (see 12.19.161), ACTIONX
(see 12.19.162) of DELAYACT (see 12.19.163) are used.
ENDACTION is a full analog of ENDACTIO.

12.19.164. ENDACTIO / ENDACTION 1839

Keywords for formats tN, E1, E3 19.1

12.19.165. UDQ

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword allows to specify User defined quantities in SCHEDULE (see 12.19.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.18.1) section;

• a combination of parameters from SUMMARY (see 12.18.1) section with mathematical

functions and operations.

User defined quantities can be used one of the following ways:

• for output in SUMMARY (see 12.18.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.44);

• in the keywords ACTIONG (see 12.19.159), ACTIONR (see 12.19.160), ACTIONW

(see 12.19.161), ACTIONX (see 12.19.162) (If the value of any quantity remain unini-
tialized then it will be replaced by the value specified in 3-rd parameter of the keyword
UDQPARAM, see 12.1.44).

• as user defined argument UDA in keywords WCONINJE (see 12.19.44), WECON

(see 12.19.74), WELDRAW (see 12.19.123), WCONPROD (see 12.19.42), GCONPROD
(see 12.19.86), GCONINJE (see 12.19.95), GECON (see 12.19.121);

• to visualize user defined quantities in graphical interface. UDQs are available in graph
and table form in Graph Templates tab – see the picture 62. Values can be copied from
the table on the right.

12.19.165. UDQ 1840

Keywords for formats tN, E1, E3 19.1

Figure 62. UDQ in Graph Templates

The keyword consists of an arbitrary number of data lines, each data row specifies its own
user defined quantity. Each data line should be terminated with the symbol /. All data should
be terminated with a final slash /.
One data row contains the following parameters:
1. operation name:

• ASSIGN – assigns a numeric value to elements of a quantity (this operation takes

place at the moment of operation initialization);
• 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 should start with: CU – connection quantity, FU – field quantity, GU

– group quantity, RU – region quantity, WU – well quantity. Quantity name shouldn’t
exceed 8 symbols. Region quantity name shouldn’t exceed 5 symbols.

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.18.1) section can be used.

12.19.165. UDQ 1841

Keywords for formats tN, E1, E3 19.1

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 num-
bers);
• CWPR WELL1 1 2 3 – water rate for the connection in block (1, 2, 3) belonging
to well WELL1 (number);
• 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 groups (set of numbers);

• RWPR 4 – water rate for the group GROUP4 (one number);
• RGIP – total gas–in–place in all regions and all FIP (see 12.4.11) sets, including
FIPNUM (see 12.4.10) set (set of numbers);
• RGIP_NUM – total gas–in–place in all regions in FIPNUM set (set of numbers);
• RGIP_REG – total gas–in–place in all regions FIP set named ”REG” (set of num-
bers);
• RGIP_REG 5 – total gas–in–place in the region 5 of the FIP regions set named
”REG” (one number). The name of FIP set should be indicated if a region index is
specified. Use NUM for the FIPNUM set.

Note: If it is required to specify a non-default region, the set name is indicated by

the last three characters in the name used in UDQ keyword, just as it would for the
SUMMARY vector. For example, to use quantities in FIP set named ”REG” it is required
to specify the name RUXXXREG in UDQ keyword. Region quantities from more than
one FIP set cannot be used in the same UDQ keyword.

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 num-
bers).

12.19.165. UDQ 1842

Keywords for formats tN, E1, E3 19.1

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);
• 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.

12.19.165. UDQ 1843

Keywords for formats tN, E1, E3 19.1

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.19.166). One parameter for
each table dimension should be specified. Inside square brackets any com-
putations can’t be used.
NINT() Nearest integer to a given number. Numbers which fraction part is 0.5 are
rounded to nearest even.
SORTA() Position of the element in ascending sorting of defined elements.
SORTD() Position of the element in descending sorting of defined elements.

Dates that are available in ACTIONX (see 12.19.162): 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.

12.19.165. UDQ 1844

Keywords for formats tN, E1, E3 19.1

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.19.165. UDQ 1845

Keywords for formats tN, E1, E3 19.1

12.19.166. UDT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword allows to set user defined lookup table in the SCHEDULE (see 12.19.1) sec-
tion. These tables can be used to assign values to user defined quantities UDQ (see 12.19.165).
Dimensions are set via UDTDIMS (see 12.1.46).

The number of lines depends on table dimension. Each data line should be terminated with
the symbol /. All data should be terminated with a final slash /.
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 corre-
spondingly outside the table;
• LL – 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 dimen-
sion, we should have two rows containing only slashes /;

12.19.166. UDT 1846

Keywords for formats tN, E1, E3 19.1

• 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.19.166. UDT 1847

Keywords for formats tN, E1, E3 19.1

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
31 32 33 34 / – corresponds to the 1-st value in NV dimension
48 58 68 78 / – corresponds to the 2-nd value in NV dimension
/ – terminates NV dimension
– 2 rows below correspond to the 3-rd value in LC dimension
41 42 43 44 / – corresponds to the 1-st value in NV dimension
40 42 44 46 / – corresponds to the 2-nd value in NV dimension
/ – terminates NV dimension
/ – terminates LC dimension
/ – terminates UDT keyword

...
UDQ
DEFINE FUTUDIM3 TUDIM3[FUTUDIM1,FUFOO,FUTOT] / – reference to
three-dimensional table UDT
/

12.19.166. UDT 1848

Keywords for formats tN, E1, E3 19.1

12.19.167. ACTIONC

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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 4 below) to automatically create fractures (see section 5.7.2)
for injectors when block pressure 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

The following parameters should be specified:

12.19.167. ACTIONC 1849

Keywords for formats tN, E1, E3 19.1

1. action name – name of this action;

2. well name – well name, or well list name defined via WLIST (see 12.19.33);
Default: all wells.

3. well status – well status, for which actionc operations will take place:

• ALL – all;
• PROD – producers;
• INJ – injectors;
• STOP – stopped;
• Default: ALL.

4. i1 – first connection coordinate in X direction;

Default: 1.

5. i2 – last connection coordinate in X direction;

Default: NX.

6. j1 – first connection coordinate in Y direction;

Default: 1.

7. j2 – last connection coordinate in Y direction;

Default: NY.

8. k1 – first connection coordinate in Z direction;

Default: 1.

9. k2 – last connection coordinate in Z direction;

Default: NZ.

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 possi-
ble:

• < – less than value;

• > – greater than value.

12. value – the value of the triggering condition;

12.19.167. ACTIONC 1850

Keywords for formats tN, E1, E3 19.1

13. times – number of times this action can be triggered;

Default: 1.

14. increment – increment to the triggering condition value;

Default: 0.

The keywords in actionc operations syntax.

In actions enumerated in actionc operations (for example in the keyword COMPFRAC,

see 12.19.148) 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.19.148) 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.19.148) 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.19.167. ACTIONC 1851

Keywords for formats tN, E1, E3 19.1

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.19.148) 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.19.148) 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 connec-
tion.

Example 4.

12.19.167. ACTIONC 1852

Keywords for formats tN, E1, E3 19.1

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.19.148) should be done in this block. The fracture with
following properties is created: azimuth angle – 100 ◦ , infinite permeability along the frac-
ture, there is no dependence from flow, fracture efficiency with skin-factor -1.5, productivity
multiplier – 10, fracture length multiplier – 1. Operation will take place until limit of times is
exhausted (parameter times is 10000).

12.19.167. ACTIONC 1853

Keywords for formats tN, E1, E3 19.1

12.19.168. WDFAC

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets well’s D-factor (flow-dependent skin for gas).

The keyword can be followed by any number of data rows. Each data line should be
terminated with the symbol /. All data should be terminated with a final slash /.
Each row consists of the following parameters:

1. well name, or well list name defined via WLIST (see 12.19.33);

2. D-factor for this well (METRIC: day/sm3 , FIELD: day/Msc f ).

Default: 0.

Well’s D-factor can also be specified via the 12-th parameter of COMPDAT (see 12.19.6),
COMPDATL (see 12.19.7), COMPDATMD (see 12.19.10).
Connection’s D-factor is calculated from well’s D-factor. Connections D-factor can be en-
tered directly via the 12-th parameter of COMPDAT (see 12.19.6), COMPDATL (see 12.19.7),
COMPDATMD (see 12.19.10).

If this keyword specifies a D-factor for well – Dwell , then D-factor for ith connection can
be calculated as:
Di = (Dwell ∗ ∑ c f )/c fi
i

where c fi is a connection factor (cf) of ith connection, the sum of connection factors is
calculated over all well connections.
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.19.168. WDFAC 1854

Keywords for formats tN, E1, E3 19.1

12.19.169. WDFACCOR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets D-factor correlation (flow-dependent skin factor for gas).

The keyword can be followed by any number of data rows. Each data line should be
terminated with the symbol /. All data should be terminated with a final slash /.
Each row consists of the following parameters:

1. Well name, or well list name defined via WLIST (see 12.19.33).

2. Coefficient A in D-factor formula below.

Default: 0.

3. Power B of permeability of grid block with connection in D-factor formula below.

Default: 0.

4. Power C of porosity of grid block with connection in D-factor formula below.

Default: 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;

• γ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.

12.19.169. WDFACCOR 1855

Keywords for formats tN, E1, E3 19.1

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.

Well’s D-factor can also be specified via the 12-th parameter of COMPDAT (see 12.19.6).
Connection’s D-factor is calculated from well’s D-factor. Connections D-factor can be en-
tered directly via the 12-th parameter of COMPDAT (see 12.19.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.19.169. WDFACCOR 1856

Keywords for formats tN, E1, E3 19.1

12.19.170. WDFACCORL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets D-factor correlation (flow-dependent skin factor for gas). It can be set
for certain block with connection (for block in global grid and for LGR block as well). For-
mula for D-factor is in the description of the keyword WDFACCOR (see 12.19.169).

The keyword can be followed by any number of data rows. Each data line should be
terminated with the symbol /. All data should be terminated with a final slash /.
The following parameters should be specified:

1. well name, or well list name defined via WLIST (see 12.19.33);

2. coefficient A for D-factor formula;

3. coefficient B for D-factor formula;

4. coefficient C for D-factor formula;

5. [additional parameter] local grid refinement (LGR) name;

Default: it is assumed that the keyword is applied to global grid.

6. [additional parameter] i-coordinate (along X direction) of block with connection;

7. [additional parameter] j -coordinate (along Y direction) of block with connection;

8. [additional parameter] k -coordinate (along Z direction) of block with connection.

If parameter 5 is set, then it is necessary to set parameters 6-8. Yet parameters 6-8 can
be set without parameter 5; in this case it is assumed that keyword is applied to global grid.
Parameters 6-8 should be set or not set simultaneously.
Example
W1 3.536488538E-05 -0.5 -5.5 1* 6 6 1 /
/
In the example for well W1 and global grid block which has coordinates (6, 6, 1) coeffi-
cient for D-factor formula are set.

12.19.170. WDFACCORL 1857

Keywords for formats tN, E1, E3 19.1

12.19.171. WTRACER

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets the value of concentration of a tracer in the injection streams of its
associated phase for flooding. If the tracer isn’t present in the list of tracer names in this
keyword, concentration is assumed to be equal to 0. The possibility to inject several passive
tracers in one well is available.
Other keywords used for tracer modeling are given in the section 2.17.1.
The keyword is followed by any number of lines. Each data line should be terminated with
the symbol /. All data should be terminated with a final slash /.
Each line consists of the following parameters:

1. well name (each well should be previously declared as injector), or well list name
defined via WLIST (see 12.19.33),

2. tracer name (specified via the keyword TRACER (see 12.7.10); in E1/E3 tracer name
may consist of up to 3 characters, but in tN 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 E1/E3 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 E1/E3 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.19.171. WTRACER 1858

Keywords for formats tN, E1, E3 19.1

12.19.172. WSURFACT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies the concentration of surfactant in the injection stream of injector.
For more details on surfactants, see section 2.23.

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 name defined via WLIST
(see 12.19.33),

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.19.172. WSURFACT 1859

Keywords for formats tN, E1, E3 19.1

12.19.173. WALKALIN

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies the concentration of alkaline in the injection stream of injector.
Alkaline Flooding – section 2.22.

For the full description of ASP (Alkaline-Surfactant-Polymer) mathematical model, see

the section 5.9. ASP model description.
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 name defined via WLIST
(see 12.19.33),

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.19.173. WALKALIN 1860

Keywords for formats tN, E1, E3 19.1

12.19.174. WPOLYMER

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies the concentration of polymer in the injection stream of injector.
(Polymer Flood is described in the section 2.16).

For the full description of ASP (Alkaline-Surfactant-Polymer) mathematical model, see

the section 5.9. ASP model description.
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 name defined via WLIST
(see 12.19.33);

2. concentration of polymer in the injection stream (METRIC: kg/sm3 , FIELD: lb/stb);

3. salt concentration in the injection stream (METRIC: kg/sm3 , FIELD: lb/stb);

4. group name, whose produced polymer concentration will be used in the injection stream
for the well. If the group is not specified, then concentration value of parameter 2 will
be used;

5. group name, whose produced salt concentration will be used in the injection stream for
the well. If the group is not specified, then concentration value of parameter 3 will be
used.

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.19.174. WPOLYMER 1861

Keywords for formats tN, E1, E3 19.1

12.19.175. WSALT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword is used to specify the concentration of salt in the injection stream of each
well for simulation of water injection into the saline reservoir 2.24.1. If the keyword WSALT
does not appear, then concentration values of zero are assumed.

The keyword is followed by any number of data records. Each data line should be termi-
nated with the symbol /. All data should be terminated with a final slash /.
Each data record should consist of the following parameters:

1. well name (each well should be previously declared as injector), or well list name
defined via WLIST (see 12.19.33);

2. the concentration of salt in the injection stream of well (METRIC: kg/sm3 , FIELD:
lb/stb). It could be defined by the keyword UDQ (see 12.19.165).

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.19.175. WSALT 1862

Keywords for formats tN, E1, E3 19.1

12.19.176. WTEMP

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies the temperature of injected water when temperature option is used
(2.26).

The keyword is followed by any number of data records. Each data line should be termi-
nated with the symbol /. All data should be terminated with a final slash /.
Each data record should consist of the following parameters:

1. well name (each well should be previously declared as injector), or well list name
defined via WLIST (see 12.19.33),

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 is 10 ◦ C, the temperature of
water injected by Well2 is 10 ◦ C, Well3 – 18 ◦ C, Well4 – 18 ◦ C.

12.19.176. WTEMP 1863

Keywords for formats tN, E1, E3 19.1

12.19.177. WHTEMP

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies the data for tubing head temperature calculations (THT) for pro-
ducers.
The implementation of VFP tables, corresponding formulas and keywords are described in the
section 6. VFP tables generation.
The keyword is followed by any number of data records. Each data line should be termi-
nated with the symbol /. All data should be terminated with a final slash /.
Each data record should consist of the following parameters (parameter 2 or 3 should be
specified: they can’t be defined simultaneous):

1. well name (each well should be previously declared as producer), or well list name
defined via WLIST (see 12.19.33),

2. VFP table number (tables are specified via VFPPROD (see 12.19.66), VFPCORR
(see 12.19.71), the table should contains THT values. To provide well THT calcula-
tions the well should have 2 tables: pressure VFP table and THT VFP table);

3. constant THT (METRIC: ◦ C, FIELD: ◦ F), IGNORED, this is an E1/E3 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.19.177. WHTEMP 1864

Keywords for formats tN, E1, E3 19.1

12.19.178. WINJTEMP

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies the temperature of injected water when thermal option is used
THERMAL (see 12.1.54).

The keyword is followed by any number of data records. Each data line should be termi-
nated with the symbol /. All data should be terminated with a final slash /.
Each data record should consist of the following parameters:

1. well name, or well list name defined via WLIST (see 12.19.33);

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 shouldn’t specify the steam quality or the temperature.

Example
WINJTEMP
INJ840 0.7 350/
INJ219 0.8 210/
/

12.19.178. WINJTEMP 1865

Keywords for formats tN, E1, E3 19.1

12.19.179. WINJWAT

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword in an alias to the keyword WINJTEMP (see 12.19.178).

12.19.179. WINJWAT 1866

Keywords for formats tN, E1, E3 19.1

12.19.180. WINJW

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword is used to specify the nature of water injected by injector when the multiple
water component model (see section 3.10) is used.
This keyword can contain an arbitrary number of data records. Each data record should be
terminated with /. All data should be terminated with slash /.

One data record contains the following parameters:

1. Well name, or well name template, or well list name defined via WLIST (see 12.19.33),
or well list template.
A template enclosed in quotes can be used to refer to multiple wells or well lists.
Well list names should be enclosed in quotes and begin with symbol (∗). Well lists are
constructed using the keyword WLIST (see 12.19.33).

2. A character string specifying the nature of the injected fluid.

• STREAM The molar composition of the injected fluid is defined using the keyword
WELLSTRW (see 12.19.185). The stream name is specified by 3–rd parameter of
this keyword.

Default: STREAM.

3. A character string specifying the name of the well stream which is used as an injection
stream.

Example
WINJW
'Inje' ST 'Fresh'/
/

12.19.180. WINJW 1867

Keywords for formats tN, E1, E3 19.1

12.19.181. HEATER

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies the position and parameters of a heater connections when thermal
option is used THERMAL (see 12.1.54). If the connection is in a local grid, then use keyword
HEATERL (see 12.19.182). The description of heater with constant energy injection rate is in
the section 4.31.1 and heater with energy density dependent injection rate is in the section
4.31.2.

The keyword is followed by any number of data records. Each data line should be termi-
nated with the symbol /. All data should be terminated with a final slash /.
Each data record should consist of the following parameters:

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 between

heat rate and the difference between current block temperature and maximum tempera-
ture) 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.19.181. HEATER 1868

Keywords for formats tN, E1, E3 19.1

12.19.182. HEATERL

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies the position and parameters of a heater connections in a local grid
refinement (LGR) when thermal option is used THERMAL (see 12.1.54). If the connection is
not in a local grid, then use keyword HEATER (see 12.19.181). The description of heater with
constant energy injection rate is in the section 4.31.1 and heater with energy density dependent
injection rate is in the section 4.31.2.

The maximum number of heater connections should be set using the keyword HEATDIMS
(see 12.1.42).
The keyword is followed by any number of data records. Each data line should be termi-
nated with the symbol /. All data should be terminated with a final slash /.
Each data record should consist of the following parameters:

1. name of the heater;

2. name of the local grid;

3. I-block coordinate of the heater connection (X-axis);

4. J-block coordinate of the heater connection (Y-axis);

5. K-block coordinate of the heater connection (Z-axis);

6. maximum heat injection rate, Hmax (METRIC: kJ/day, FIELD: Btu/day);

Default: 0.

7. maximum temperature in the block where heater is connected, Tmax (METRIC: C◦ ,

FIELD: F ◦ );

8. temperature-dependent heat injection rate (proportional heat transfer coefficient between

heat rate and the difference between current block temperature and maximum tempera-
ture) R (METRIC: kJ/day/K , FIELD: Btu/day/R◦ ).

Example
HEATERL
PRODA LGR1 3 2 1 100000 150.0 1.0E6 /
/

12.19.182. HEATERL 1869

Keywords for formats tN, E1, E3 19.1

12.19.183. WTEST

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets instructions for testing of closed wells.

The keyword is followed by any number of data records. Each data line should be termi-
nated with the symbol /. All data should be terminated with a final slash /.
Each data record should consist of the following parameters:

1. well name, or well list name defined via WLIST (see 12.19.33);

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.19.74), CECON (see 12.19.80), WECONINJ, see 12.19.81). If
there is at least one open connection then the well is opened if all limits are
satisfied in WECON (see 12.19.74). (All closed connections will not be reopened.)
If the well doesn’t 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
not violated (WECON (see 12.19.74) and CECON, see 12.19.80). (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.19.121) or GCON**** family. The
well will be opened unconditionally, because it can’t 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 doesn’t have open connections,
then all connections (closed due to automatic workovers) are reopened.

12.19.183. WTEST 1870

Keywords for formats tN, E1, E3 19.1

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;
Default: 0.

5. start-up time – time (days). At each time step after well’s 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: 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.19.183. WTEST 1871

Keywords for formats tN, E1, E3 19.1

12.19.184. WELLSTRE

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies the composition of the injected stream (oil or gas). Well stream can
be used in the keyword WINJGAS (see 12.19.190), GINJGAS (see 12.19.191).

The keyword is followed by any number of data records. Each data line should be termi-
nated with the symbol /. All data should be terminated with a final slash /.
Each data record should consist of the following parameters:

• well stream name;

• x1 -mole fraction of the 1-st component;

• x2 -mole fraction of the 2-nd component;

• ...;

• xNc is the 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.19.184. WELLSTRE 1872

Keywords for formats tN, E1, E3 19.1

12.19.185. WELLSTRW

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword is used to specify the composition of injected water stream when the Mul-
tiple water component model (see section 3.10) is implemented. The defined wellstream can
be used in the WINJW (see 12.19.180) to specify an injected composition.
This keyword can contain an arbitrary number of data records. Each data record should be
terminated with /. All data should be terminated with /.

One data record consists of the following parameters:

• x1 – mole fraction of the 1-st component;

• x2 – mole fraction of the 2-nd component;

• ...;

• xNw – mole fraction of the Nw component (Nw – number of components in the run).
The sum of mole fractions should be equal to 1.

Example
WELLSTRW
'Fresh' 1.0 0.0 /
/

12.19.185. WELLSTRW 1873

Keywords for formats tN, E1, E3 19.1

12.19.186. COMPMOBI

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.

The keyword is followed by any number of data records. Each data line should be termi-
nated with the symbol /. All data should be terminated with a final slash /.
Each data record should consist of the following parameters:

1. Well name, or well list name defined via WLIST (see 12.19.33).

2. I coordinate of connecting grid block.

Default: 0 (any value is allowed).

3. J coordinate of connecting grid block.

Default: 0 (any value is allowed).

4. K coordinate of upper connecting grid block.

Default: 0 (any value is allowed).

5. K coordinate of lower connecting grid block.

Default: 0 (any value is allowed).

6. Total voidage mobility (METRIC: cP−1 , FIELD: cP−1 ).

Default: 1.0 cP−1 .

Example
COMPMOBI
I1 4* 10.0 /
I2 7 14 22 34 10.0 /
/

12.19.186. COMPMOBI 1874

Keywords for formats tN, E1, E3 19.1

12.19.187. COMPMBIL

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.

The keyword is followed by any number of data records. Each data line should be termi-
nated with the symbol /. All data should be terminated with a final slash /.
Each data record should consist of the following parameters:
1. Well name, or well list name defined via WLIST (see 12.19.33).
2. LGR name.
3. I coordinate of connecting grid block.
Default: 0 (any value is allowed).
4. J coordinate of connecting grid block.
Default: 0 (any value is allowed).
5. K coordinate of upper connecting grid block.
Default: 0 (any value is allowed).
6. K coordinate of lower connecting grid block.
Default: 0 (any value is allowed).
7. Total voidage mobility (METRIC: cP−1 , FIELD: cP−1 ).
Default: 1.0 cP−1 .

Example
COMPMBIL
I1 LGR1 4* 10.0 /
I2 LGR4 7 14 22 34 10.0 /
/

12.19.187. COMPMBIL 1875

Keywords for formats tN, E1, E3 19.1

12.19.188. WINJMIX

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.19.190), GINJGAS (see 12.19.191) (parameter MIX).

The keyword is followed by any number of data records. Each data line should be termi-
nated with the symbol /. All data should be terminated with a final slash /.
Each data record should consist of the following parameters:

1. Mixture name.

2. Mixture contribution index of the fluid defined below (integer number); calculation of
the injection mixture doesn’t depend on the order of fluid specification.

3. Fraction of this fluid in the mixture.

4. Nature of injected gas:

• GAS – gas composition corresponds to the field separator gas composition;

• STREAM – molar composition of the injected fluid is defined via the keyword
WELLSTRE (see 12.19.184) (stream name should be entered via parameter 5 of
this keyword);
• GV – injected gas composition corresponds to gas composition, produced by spec-
ified group (group name should be entered via parameter 5 of this keyword);
• WV – injected gas composition corresponds to gas composition, produced by spec-
ified well (well name should be entered via parameter 5 of this keyword).

5. Character string that specifies the data in accordance with the parameter 4 of the key-
word:

• 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.
Default: 0 (the vapor from the whole separator is used as the injection fluid).

12.19.188. WINJMIX 1876

Keywords for formats tN, E1, E3 19.1

Example
WINJMIX
M1 1 0.5 GV GROUP1 /
M1 2 0.5 GV GROUP2 /
/

12.19.188. WINJMIX 1877

Keywords for formats tN, E1, E3 19.1

12.19.189. WINJORD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword defines composition of fluids for injection. It specifies fluids order. These
are taken in this order subject to their availability.
Each line should be ended by a symbol /. The data should be terminated with a slash /.

The following parameters should be specified:

1. Mixture name (maximum number of mixtures is set the keyword WELLDIMS,
see 12.1.39).
2. Mixture contribution index of the fluid defined below. The fluids will be taken in in-
creasing order of their contribution fraction (maximum number of mixture fluids is set
in the keyword WELLDIMS, see 12.1.39).
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 keyword
WELLSTRE (see 12.19.184). 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 fluid’s composition. It is necessary if value of parameter 3 is not GAS.
5. stage of the separator that defines the fluid composition.
Default: 0.

Example
WINJORD
IGAS 1 GV FIELD /
IGAS 2 ST A1GAS /
/

12.19.189. WINJORD 1878

Keywords for formats tN, E1, E3 19.1

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.19.184).

12.19.189. WINJORD 1879

Keywords for formats tN, E1, E3 19.1

12.19.190. WINJGAS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies the nature of injected gas. The keyword should be used in compo-
sitional runs to specify data for injectors when the keyword WCONINJE (see 12.19.44) is used.

The keyword is followed by any number of data records. Each data line should be termi-
nated with the symbol /. All data should be terminated with a final slash /.
Each data record should consist of the following parameters:
1. Well name, or well list name defined via WLIST (see 12.19.33).
2. Nature of injected gas (tNavigator supports the following options):
• GAS – gas composition corresponds to the field separator gas composition;
• STREAM – molar composition of the injected fluid is defined via the keyword
WELLSTRE (see 12.19.184) (stream name should be entered via parameter 3 of
this keyword);
• MIX – the molar composition of injected fluid is specified as a mixture via WIN-
JMIX (see 12.19.188) (the name of the mixture should be specified via parameter
3 of this keyword);
• GV – injected gas composition corresponds to gas composition, produced by spec-
ified group (group name should be entered via parameter 3 of this keyword);
• WV – injected gas composition corresponds to gas composition, produced by spec-
ified well (well name should be entered via parameter 3 of this keyword);
• GRUP – injected fluid is specified for the superior group.
Default: GRUP.
3. Character string that specifies the data in accordance with the parameter 2 of the key-
word:
• if the 2-nd parameter is STREAM, 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. Name of a wellstream to be used as make-up gas (specified via WELLSTRE,
see 12.19.184). 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.19.190. WINJGAS 1880

Keywords for formats tN, E1, E3 19.1

5. 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.
Default: 0 (the vapor from the whole separator is used as the injection fluid).

Example
WINJGAS
Well1 STREAM 'stream1'/
/

12.19.190. WINJGAS 1881

Keywords for formats tN, E1, E3 19.1

12.19.191. GINJGAS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.19.95) is used.

The keyword is followed by any number of data records. Each data line should be termi-
nated with the symbol /. All data should be terminated with a final slash /.
Each data record should consist of the following parameters:

1. Group name or group mask defining a subset of groups with common prefix (should
end with an asterisk *).

2. Nature of injected gas (tNavigator supports the following options):

• GAS – gas composition corresponds to the field separator gas composition;

• STREAM – molar composition of the injected fluid is defined via the keyword
WELLSTRE (see 12.19.184) (stream name should be entered via parameter 3 of
this keyword);
• MIX – the molar composition of injected fluid is specified as a mixture via WIN-
JMIX (see 12.19.188) (the name of the mixture should be specified via parameter
3 of this keyword);
• GV – injected gas composition corresponds to gas composition, produced by spec-
ified group (group name should be entered via parameter 3 of this keyword);
• WV – injected gas composition corresponds to gas composition, produced by spec-
ified well (well name should be entered via parameter 3 of this keyword);
• GRUP – injected fluid is specified for the superior group.

Default: GRUP.

3. Character string that specifies the data in accordance with the parameter 2 of the key-
word:

• if the 2-nd parameter is STREAM, 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.

12.19.191. GINJGAS 1882

Keywords for formats tN, E1, E3 19.1

4. Name of a wellstream to be used as make-up gas (specified via WELLSTRE,

see 12.19.184). Make up gas is used in case if there is no enough gas for injection
from the source specified via parameters 2 and 3.

5. 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.
Default: 0 (the vapor from the whole separator is used 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.19.191. GINJGAS 1883

Keywords for formats tN, E1, E3 19.1

12.19.192. GADVANCE

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies a supply of advance import gas to a group that provides gas for
reinjection (GINJGAS, see 12.19.191).

First, the advance import gas for this group is used for re-injection. Second, the gas pro-
duced 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).

The keyword is followed by any number of data records. Each data line should be termi-
nated with the symbol /. All data should be terminated with a final slash /.
Each data record should consist of the following parameters:

1. group name or group mask defining a subset of groups with common prefix (should end
with an asterisk *);

2. name of the well stream that specifies the molar composition of the imported gas (well
streams are defined via WELLSTRE, see 12.19.184);

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.19.192. GADVANCE 1884

Keywords for formats tN, E1, E3 19.1

12.19.193. GRUPSALE

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword specifies the group gas sales rate (the volume of gas available for re-injection
is reduced by this amount).
Group control possibilities of tNavigator are described in the section 2.14.2.

Gas available for re-injection.

The available for re-injection gas of a group is equal to the group’s gas production rate mi-
nus its fuel rate (GRUPFUEL, see 12.19.195) minus its sales rate (GRUPSALE, see 12.19.193).

The keyword GRUPSALE is followed by any number of data records. Each data line
should be terminated with the symbol /. All data should be terminated with a final slash /.
Each data record should consist of the following parameters:

1. Group name or group mask defining a subset of groups with common prefix (should
end with an asterisk *)or FIELD.

2. Constant gas sales rate (METRIC: sm3 /day, FIELD: Msc f /day).
Default: 0.

3. Fractional gas sales rate.

Default: 0.

4. Each component fraction to sale.

Default: 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.19.193. GRUPSALE 1885

Keywords for formats tN, E1, E3 19.1

12.19.194. GCONSALE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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 /.
The data should be terminated with a slash /.
Group control possibilities of tNavigator are described in the section 2.14.2.
The following parameters should be specified:

1. Group name or group mask defining a subset of groups with common prefix (should
end with an asterisk *).

2. Value of gas rate for sale (METRIC: sm3 /day, FIELD: Msc f /day). It could be defined
by the keyword UDQ (see 12.19.165).

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.
Default: no limit.

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.

Default: 0.

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,

12.19.194. GCONSALE 1886

Keywords for formats tN, E1, E3 19.1

• +CON – analogue of CON+,

• WELL – shut or stop the worst-offending well (parameter 9 WELSPECS,
see 12.19.3),
• RATE – group’s 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 well’s preferred phase (parameter 6 of WELSPECS, see 12.19.3).
Default: NONE.

Example
GCONSALE
FIELD 50000 /
/
Value of gas rate of a field for sale is 50000 Msc f /day.

12.19.194. GCONSALE 1887

Keywords for formats tN, E1, E3 19.1

12.19.195. GRUPFUEL

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword specifies the group gas fuel rate (the volume of gas available for re-injection
is reduced by this amount).
Group control possibilities of tNavigator are described in the section 2.14.2.

Gas available for re-injection.

The available for re-injection gas of a group is equal to the group’s gas production rate mi-
nus its fuel rate (GRUPFUEL, see 12.19.195) minus its sales rate (GRUPSALE, see 12.19.193).

The keyword GRUPFUEL is followed by any number of data records. Each data line
should be terminated with the symbol /. All data should be terminated with a final slash /.
Each data record should consist of the following parameters:

1. Group name or group mask defining a subset of groups with common prefix (should
end with an asterisk *)or FIELD.

2. Constant gas fuel usage rate (METRIC: sm3 /day, FIELD: Msc f /day). Can be specified
by user via UDQ (see 12.19.165).
Default: 0.

3. Fractional gas fuel usage rate. Can be specified by user via UDQ (see 12.19.165).
Default: 0.

4. Each component fraction to use as fuel.

Default: 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.19.195. GRUPFUEL 1888

Keywords for formats tN, E1, E3 19.1

12.19.196. WTAKEGAS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword defines the order in which fuel, sales and reinjection gas are takes from pro-
duction gas steam (fuel gas – GRUPFUEL (see 12.19.195), sales – GRUPSALE, reinjection –
GCONINJE, see 12.19.95). 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.19.196. WTAKEGAS 1889

Keywords for formats tN, E1, E3 19.1

12.19.197. WAVAILIM

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword sets that the availability of injection fluids can be taken into account in
injection rate calculations. This keyword doesn’t 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.19.191),
WINJGAS (see 12.19.190) or WELLINJE (see 12.19.48), 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 pro-
duced gas, minus fuel (GRUPFUEL, see 12.19.195) and sales gas (GRUPSALE) (unless
other conditions are specified in WTAKEGAS, see 12.19.196), plus advance gas rate
specified via GADVANCE (see 12.19.192).

• If the source of injection stream is a well then the gas available for injection is its
produced gas.

12.19.197. WAVAILIM 1890

Keywords for formats tN, E1, E3 19.1

12.19.198. SWINGFAC

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword activates the Gas Field Model – section 2.14.8.

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 month’s profile factor.

The keywords GASYEAR (see 12.19.201) and GASPERIO (see 12.19.202) sets con-
tract periods. These keywords should be used instead of DATES (see 12.19.124), TSTEP
(see 12.19.125). 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.19.199) should be used instead of SWINGFAC.
The keyword GASFIELD (see 12.1.98) 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:
• i – number of the month;

12.19.198. SWINGFAC 1891

Keywords for formats tN, E1, E3 19.1

• 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.19.198. SWINGFAC 1892

Keywords for formats tN, E1, E3 19.1

12.19.199. GSWINGF

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword activates the Gas Field Model – section 2.14.8.

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.19.198) 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 month’s profile factor.

The keywords GASYEAR (see 12.19.201) and GASPERIO (see 12.19.202) sets con-
tract periods. These keywords should be used instead of DATES (see 12.19.124), TSTEP
(see 12.19.125). 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.19.199. GSWINGF 1893

Keywords for formats tN, E1, E3 19.1

• 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.19.199. GSWINGF 1894

Keywords for formats tN, E1, E3 19.1

12.19.200. GDCQ

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets initial DCQ for each contract group (Gas Daily Contracted Quantity.
The keyword is used in the Gas Field Model – section 2.14.8.

Contract groups are defined via GSWINGF (see 12.19.199); each contract group has its
name, swing and profile factors. The keywords GASYEAR (see 12.19.201) and GASPERIO
(see 12.19.202) sets contract periods. These keywords should be used instead of DATES
(see 12.19.124), TSTEP (see 12.19.125).

Initial DCQ value can be reset at any time by further use of QDCQ.

An arbitrary number of lines can be entered. Each data line should be terminated with the
symbol /. All data should be terminated with a final slash /.
One data line contains the following parameters:
1. Group name or group mask defining a subset of groups with common prefix (should
end with an asterisk *).
2. Initial DCQ of the group (METRIC: sm3 /day, FIELD: Msc f /day).
Default: the group’s current DCQ.
3. Is the group’s DCQ variable or fixed?
• VAR – group DCQ is reduced to obey the swing requirement specified by param-
eter 3 of the keyword GASYEAR (see 12.19.201) (or parameter 4 of GASPERIO,
see 12.19.202). 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 can’t meet its target rate). At the first pass of each contract
period the group’s target rate is equal to DCQ, multiplied by a swing factor. If
in the keyword GASYEAR (see 12.19.201) parameter 3 is (or parameter 4 in the
keyword GASPERIO, see 12.19.202) – PRO, then group’s target rate is equal to
DCQ, multiplied by a profile factor. At the second pass of each contract period
the group’s 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.19.200. GDCQ 1895

Keywords for formats tN, E1, E3 19.1

Default: VAR.

Example
GDCQECON
G1 78000 VAR /
G2 45000 FIX1 /
G2 50000 FIX1 /
/

12.19.200. GDCQ 1896

Keywords for formats tN, E1, E3 19.1

12.19.201. GASYEAR

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.19.202) should be used instead of GASYEAR (see 12.19.201) if the
length of the contract period is less than a year (These keywords should be used instead of
DATES (see 12.19.124), TSTEP, see 12.19.125).

The keyword is used in the Gas Field Model – section 2.14.8. Seasonality profile is cal-
culated according to the profile coefficients specified via SWINGFAC (see 12.19.198) (or
GSWINGF (see 12.19.199), 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.19.198) (or GSWINGF (see 12.19.199), if there are several contract groups).

The following parameters should be specified:

1. Number of contract years to simulate (the contracts year begins when the keyword
GASYEAR (see 12.19.201) 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.19.200).
Default: current value of DCQ.

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 con-
tract 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
(an alias for JUL).

12.19.201. GASYEAR 1897

Keywords for formats tN, E1, E3 19.1

The group must be able to work at the DCQ, multiplied by the swing factor until
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 can’t 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.19.200), then one can use only options YEAR or NO.
Default: YEAR.

4. Flag that specifies whether the timesteps should be limited so that each month starts
with a new timestep. In tNavigator always assumed to be YES.
Default: 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).
Default: 0 (unlimited DCQ reduction is allowed).

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.
Default: 1 (no reduction is anticipated).

7. Maximum allowed number of iterations of the first pass of each contract year to calculate
the DCQ.

12.19.201. GASYEAR 1898

Keywords for formats tN, E1, E3 19.1

Default: 3.

8. Convergence tolerance for the calculation DCQ when using the accelerated iteration.
IGNORED. This is an E1/E3 compatibility field. tNavigator doesn’t use tNavigator the
accelerated iteration scheme.

Example
GASYEAR
2 150000 MAR /
/

GASYEAR
20 1* MAR /
/

12.19.201. GASYEAR 1899

Keywords for formats tN, E1, E3 19.1

12.19.202. GASPERIO

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.19.202) should be used instead of GASYEAR (see 12.19.201) if the
length of the contract period is less than a year (These keywords should be used instead of
DATES (see 12.19.124), TSTEP, see 12.19.125).

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.14.8. Seasonality profile is cal-
culated according to the profile coefficients specified via SWINGFAC (see 12.19.198) (or
GSWINGF (see 12.19.199), 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.19.198) (or GSWINGF (see 12.19.199), if there are several contract groups).

The following parameters should be specified:

1. Number of contract periods to simulate (the contract period begins when the keyword
GASPERIO (see 12.19.202) is specified).

2. Number of months in a contract period (1, 2, 3, 4, 6 or 12).

Default: 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.19.200);
Default: current value of DCQ.

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.

12.19.202. GASPERIO 1900

Keywords for formats tN, E1, E3 19.1

• PRO. The group must be able to increase the production rate at any time of the con-
tract period from the DCQ, multiplied by the profile factor, to the DCQ, multiplied
by the swing factor.
• 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 can’t 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.19.200), then one can use only options PER or NO.
Default: YEAR.

5. Flag that specifies whether the timesteps should be limited so that each month starts
with a new timestep. In tNavigator always assumed to be YES.
Default: 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).
Default: 0 (unlimited DCQ reduction is allowed).

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.

12.19.202. GASPERIO 1901

Keywords for formats tN, E1, E3 19.1

Default: 1 (no reduction is anticipated).

8. Maximum allowed number of iterations of the first pass of each contract year to calculate
the DCQ.
Default: 3.

9. Convergence tolerance for the calculation DCQ when using the accelerated iteration.
IGNORED. This is an E1/E3 compatibility field. tNavigator doesn’t use tNavigator the
accelerated iteration scheme.

Example
GASPERIO
3 4 150000 PER /
/

12.19.202. GASPERIO 1902

Keywords for formats tN, E1, E3 19.1

12.19.203. DCQDEFN

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword defines whether the DCQ targets set in keywords GASYEAR (see 12.19.201),
GASPERIO (see 12.19.202) or GDCQ (see 12.19.200) correspond to energy or gas production
rate. In tNavigator always – gas production rate.

The keyword is used in the Gas Field Model – section 2.14.8.

The following parameters should be specified:

1. GAS – DCQ corresponds to gas production rate.

The data should be terminated with a slash /.

Example
DCQDEFN
GAS /

12.19.203. DCQDEFN 1903

Keywords for formats tN, E1, E3 19.1

12.19.204. GDCQECON

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword sets the minimum economic DCQ limit for contract. The keyword is used
in the Gas Field Model – section 2.14.8.
Economic control possibilities of tNavigator are summarized in the section 2.14.3.
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.19.3). If the contract group is FIELD, then the calculation will be terminated.

An arbitrary number of lines can be entered. Each data line should be terminated with the
symbol /. All data should be terminated with a final slash /.
One data line contains the following parameters:

1. Group name or group mask defining a subset of groups with common prefix (should
end with an asterisk *).

2. Minimum economic DCQ value (METRIC: sm3 /day, FIELD: Msc f /day).
Default: 0 (no limit).

Example
GDCQECON
G1 38000 /
G2 45000 /
/

12.19.204. GDCQECON 1904

Keywords for formats tN, E1, E3 19.1

12.19.205. GASBEGIN

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword starts the set of keywords that specify well operations and reports during
the contract period.
The keyword is used in the Gas Field Model – section 2.14.8.
After this keyword the keyword that are listed below can go, they should be terminated with
GASEND (see 12.19.206). Time in the contract period (between GASBEGIN (see 12.19.205)
and GASEND, see 12.19.206) when the operation should take place are specified via GAS-
MONTH (see 12.19.207).

Creation of Annual Scheduling File.

The keywords GASYEAR (see 12.19.201) and GASPERIO (see 12.19.202) advance the sim-
ulation 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.19.205)
and GASEND (see 12.19.206) before the keywords GASYEAR (see 12.19.201) and
GASPERIO (see 12.19.202). The data between GASBEGIN (see 12.19.205) and GASEND
(see 12.19.206) is read but not performed until the keywords GASYEAR (see 12.19.201) or
GASPERIO (see 12.19.202) are used.

If the Annual Scheduling File doesn’t change then it can be specified only once. Annual
Scheduling File will be automatically performed from its beginning when any new GASYEAR
(see 12.19.201) or GASPERIO (see 12.19.202) is read. If the Annual Scheduling File is varied
then a new File should be specified at the beginning of the contract year via GASBEGIN
(see 12.19.205) and GASEND (see 12.19.206).
To specify an empty Annual Scheduling File (no well operations and reports during the
contract period) you should specify GASBEGIN (see 12.19.205), and immediately after it
– GASEND (see 12.19.206).

Possible keywords for Annual Scheduling File creation:

• BRANPROP (see 12.19.102);
• GASMONTH (see 12.19.207);
• GCONPRI (see 12.19.89);
• GCONPROD (see 12.19.86);

12.19.205. GASBEGIN 1905

Keywords for formats tN, E1, E3 19.1

• GCONSUMP (see 12.19.96);

• GRUPNET (see 12.19.114);

• GRUPTARG (see 12.19.63);

• GRUPTREE (see 12.19.100);

• GSATINJE (see 12.19.98);

• GSATPROD (see 12.19.97);

• NODEPROP (see 12.19.103);

• RPTSCHED (see 12.1.129);

• WEFAC (see 12.19.83);

• WELOPEN (see 12.19.128);

• WELTARG (see 12.19.60);

• WGRUPCON (see 12.19.94).

12.19.205. GASBEGIN 1906

Keywords for formats tN, E1, E3 19.1

12.19.206. GASEND

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword ends the set of keywords that specify well operations and reports during the
contract period after the keyword GASBEGIN (see 12.19.205).
The keyword is used in the Gas Field Model – section 2.14.8.

well operations and reports during the contract period are specified between GASBEGIN
(see 12.19.205) and GASEND (see 12.19.206). Time in the contract period (between GASBE-
GIN (see 12.19.205) and GASEND, see 12.19.206) when the operation should take place are
specified via GASMONTH (see 12.19.207).

12.19.206. GASEND 1907

Keywords for formats tN, E1, E3 19.1

12.19.207. GASMONTH

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword specifies a month when in Annual Scheduling File creation the well opera-
tions will be performed or reports will be written.
The keyword is used in the Gas Field Model – section 2.14.8.

Time moments in the contract period are specified between the keywords GASBEGIN
(see 12.19.205) and GASEND, see 12.19.206).

The following parameters should be specified (The data should be terminated with a slash
/.):

1. month. One of the following names: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG,
SEP, OCT, NOV, DEC, and JLY (an alias for 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.19.207. GASMONTH 1908

Keywords for formats tN, E1, E3 19.1

12.19.208. WGASPROD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword can be used to declare several production wells to be special in that their
opening from the drilling queue has higher priority than that of the others when the sales gas
production rate falls below the minimum limit (keyword GCONSALE, see 12.19.194).
Initially the wells must be declared as shut producers (keyword WCONPROD,
see 12.19.42), and placed in the drilling queue (keyword QDRILL, see 12.19.229).
The wells should be placed under GRAT control (GRAT value is set by 6-th parameter of
the keyword WCONPROD, see 12.19.42). 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.
The following parameters should be specified:

1. well name, or well name mask, or well list name defined via WLIST (see 12.19.33), or
well list mask;

2. gas rate value (METRIC: sm3 /day, FIELD: msc f /day). The well’s target gas produc-
tion rate is increased by this amount;

3. Maximum permitted number of applying operation from parameter 2.

Any number of data lines can be specified. Each data line should be terminated with the
symbol /. The data should be terminated with a slash /.
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.19.208. WGASPROD 1909

Keywords for formats tN, E1, E3 19.1

12.19.209. GASFTARG

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword is used in the Gas Field Model – section 2.14.8.

It sets monthly gas rate values which are the field to be produced in the second pass of
the gas field operations model.

The following parameters should be specified:

1. 12 gas rate values which corresponds to each month of one calendar year (METRIC:
sm3/day, FIELD: Msc f /day).

The data should be terminated with a slash /.

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 pro-
duced at DCQ ∗ PROFILE . DCQ is Daily Contracted Quantity, PROFILE – multipliers for
gas rates (the keyword SWINGFAC, see 12.19.198).
The GASFTARG (see 12.19.209) keyword can also be used in conjunction with the
GASFDECR (see 12.19.210) 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.19.209. GASFTARG 1910

Keywords for formats tN, E1, E3 19.1

12.19.210. GASFDECR

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword is used in the Gas Field Model – section 2.14.8.

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 SWING-
FAC, see 12.19.198), DEC – decrement value which is set there.
This keyword can be used in conjunction with the keyword GASFTARG (see 12.19.209).
In this case field is to be produced lesser of DCQ ∗ PROFILE − DEC and specified in GAS-
FTARG (see 12.19.209) gas rate value.

The following parameters should be specified:

1. 12 decrement values which corresponds to each month of one calendar year (METRIC:
sm3/day, FIELD: Msc f /day).
Default: 0.

The data should be terminated with a slash /.

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.19.210. GASFDECR 1911

Keywords for formats tN, E1, E3 19.1

12.19.211. GASFCOMP

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword is used in the Gas Field Model – section 2.14.8.

The keyword sets compressors for models with option of standard network (see section
2.14.10). For each network branch only one compressor can be set.
Compressors are activated when the field doesn’t achieve target gas rate value. If this
value is decreased, then compressors would be deactivated – it is necessary to see if the field
can meet it without them. The automatic compressors are also turned on while calculating the
field’s maximal production.
Each data line should contain the following parameters:

1. Well group name or group mask defining a subset of groups with common prefix (should
end with an asterisk *).

2. Number of VFP table, which is used when the compressor is operating (see the keyword
VFPPROD, see 12.19.66).
Default: 0 (i.e. the same which is used in the keyword GRUPNET, see 12.19.114).

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.19.66).
Default: 0.

Each data line should be ended by the symbol /. The data should be terminated with a
slash /.
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.19.114), ALQ is 50.

12.19.211. GASFCOMP 1912

Keywords for formats tN, E1, E3 19.1

12.19.212. WVFPDP

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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 well’s
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 well’s production. Negative adjustment improves well’s production).
The implementation of VFP tables, corresponding formulas and keywords are described in the
section 6. VFP tables generation.
The third parameter of the keyword is a tubing pressure loss scaling factor. Well’s 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 well’s production.
The keyword is followed by any number of lines. Each data line should be terminated with
the symbol /. All data should be terminated with a final slash /.
Each line consists of the following parameters:
1. Well name, or well list name defined via WLIST (see 12.19.33).
2. Pressure adjustment (METRIC: bars, FIELD: psi).
Default: 0.
3. Tubing pressure loss scaling factor f p . Well’s BHP will be adjusted to BHP1: BHP1 =
T HP + f p ∗ (BHPtab − T HP).
Default: 1.
Independently of the use of this keyword, well’s BHP is automatically adjusted to take
account of any difference between its BHP reference depth (5-th parameter of WELSPECS,
see 12.19.3) and reference depth of VFP table (VFPPROD, see 12.19.66), by adding or sub-
tracting 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 /
/
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.19.212. WVFPDP 1913

Keywords for formats tN, E1, E3 19.1

12.19.213. PICOND

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword controls the calculations of generalized pseudo-pressure option for modeling
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 parameter of the
keyword WELSPECS, see 12.19.3). The data should be terminated with a slash /.

The following parameters should be specified:

1. Maximum interval between pressure quadrature points below the dew point pressure
in the calculation of the generalized pseudo-pressure integral (METRIC: bars, FIELD:
psi).
Default: 4 · patm ( patm is the atmospheric pressure).

2. Maximum interval between pressure quadrature points above the dew point pressure
in the calculation of the generalized pseudo-pressure integral (METRIC: bars, FIELD:
psi).
Default: for E3 data format: 10 · patm ( patm is the atmospheric pressure), for E1 data
format: 0.

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 is the calculated value at the time step, β previous
is the value from previous time step.
Default: 1.

4. Use the option of velocity dependent relative permeability in pseudo-pressure calcula-

tion: YES or NO.
If YES is used then the option of velocity dependent relative permeability should
be initialized via the keyword VELDEP (see 12.1.8). See also the keywords VDKRO
(see 12.14.64) and VDKRG (see 12.14.62).
Default: NO.

5. Coefficient PPBFAC to generate lower bound pL of generalized pseudo-pressure inte-

gral table:
pL = PPBFAC · pcomp .

12.19.213. PICOND 1914

Keywords for formats tN, E1, E3 19.1

PPAFAC may be from 0 to 0.95.

Default: 0.

6. Coefficient PPAFAC to generate upper bound pL of generalized pseudo-pressure inte-

gral table:
pU = PPAFAC · pcomp .
PPBFAC may be from 1.05 to 2.
Default: 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.19.213. PICOND 1915

Keywords for formats tN, E1, E3 19.1

12.19.214. WPAVE

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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 con-
nection 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.18.1) via WBP, WBP0, 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-
nated with a slash /.

The following parameters should be specified:

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
P̄k = F1 · Pi,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.

!
If this parameter is set as 0, then central blocks will be excluded from
WBP9 calculation, i.e. blocks with connections. So WBP8 can be esti-
mated using WBP9 graph.
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

12.19.214. WPAVE 1916

Keywords for formats tN, E1, E3 19.1

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 :

Vi,k Pi,k + ∑o,k Vo,k Po,k

P̄k =
Vi,k + ∑o,k Vo,k
The pressure in each individual grid block Pi,k or Po,k is corrected to the well’s bottom
hole reference depth according to the option selected in parameter 3. The number of sur-
rounding 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 av-
erages 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 perpen-
dicular to the direction of penetration of the connection (see parameter 13 of keyword
COMPDAT, see 12.19.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.
Default: F1 = 0.5.
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 :

P¯w = F2 · P̄w,c f + (1 − F2) · P̄w,pv

Connection factor weighted average – this is the average over connections of the av-
erage block pressure Pk at each connection k , weighted according to the connection
transmissibility factors Tk :

∑k Tk P̄k
P̄w,c f =
∑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
P̄w,pv =
∑ j Vj
Default: F2 = 1.

12.19.214. WPAVE 1917

Keywords for formats tN, E1, E3 19.1

3. depth correction flag. This flag controls how the grid block pressures are corrected
to the well’s bottom hole reference depth (parameter 5 of the keyword WELSPECS,
see 12.19.3).

• 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 well’s 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 well’s status
changes between shut and open/stopped.
Default: WELL.

4. well connection flag. This flag controls whether the grid blocks associated with all the
well’s declared connections contribute to the average pressure, or just those associated
with the currently open connections. Also blocks with virtual connections of hydraulic
fractures can be taken into account.

• 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.
• FLOW – blocks with crossflow are not taking into account in well WBP calcula-
tion. Option works the following way:
– Crossflow is switched off in parameter 10 of the keyword WELSPECS
(see 12.19.3) (XFLO (see 14.6.40) for MO format);
– If crossflow is switched off and FLOW option is not used: for blocks in which
during calculation crossflow is obtained (connection rate is negative), negative
rates are replaced by zero. However pressures in these grid blocks are taking
into account in well WBP calculation, which may lead to negative drawdown
values on graphs for well in graphical interface.
– If crossflow is switched off and FLOW option is used: for blocks in which
during calculation crossflow is obtained (connection rate is negative), negative
rates are replaced by zero. These blocks are not taking into account in well
WBP calculation.

12.19.214. WPAVE 1918

Keywords for formats tN, E1, E3 19.1

Figure 63. Grid block configuration in well block average pressure calculations

• FALL – average pressure is calculated taking into account virtual perforations of

hydraulic fractures; opened and closed connections are used;
• FOPEN – average pressure is calculated taking into account virtual perforations of
hydraulic fractures; only open connections are used.

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 select-
ing ALL and defining all the well’s connections at the start of the run (whether initially
open or closed).
Default: OPEN.

5. Type of weighting for pressure.

• PV – pore volume weighting;

• CF – weighting for connection factor;
• MOB – weighting for connection’s reservoir rate;
• KH – weighting for connection’s kh;
• NONE – no weighting, arithmetic average is calculated.
• Default: PV.

Example
WPAVE
0.33 0 2* /

12.19.214. WPAVE 1919

Keywords for formats tN, E1, E3 19.1

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.19.214. WPAVE 1920

Keywords for formats tN, E1, E3 19.1

12.19.215. WPAVEDEP

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword can be used to modify reference depth for the calculation of well block aver-
age pressures (keyword WPAVE, see 12.19.214). The depth correction is calculated according
to parameter 3 of the keyword WPAVE (see 12.19.214).

An arbitrary number of data lines can be entered. Each data line should be terminated with
the symbol /. All data should be terminated with a final slash /.
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 name
defined via WLIST (see 12.19.33).

2. Reference depth for the calculation of well block average pressures (METRIC: m,
FIELD: f t ).
Default: well bottom hole reference depth.

Example
WPAVEDEP
W1 2500 /
W1 3100 /
/

12.19.215. WPAVEDEP 1921

Keywords for formats tN, E1, E3 19.1

12.19.216. WRFT

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets output of well RFT data (see section 2.14.1). 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 data lines can be entered. Each data line should be terminated with
the symbol /. All data should be terminated with a final slash /.
One data line contains the following parameters:

1. well name (or number), or well mask defining a subset of wells with common prefix
(should end with an asterisk *), or well list name defined via WLIST (see 12.19.33);

If the keyword doesn’t have any parameters, well RFT data will be output whenever a
well is first opened.
Example
WRFT
'WELL3*' /
'PROD11' /
/

12.19.216. WRFT 1922

Keywords for formats tN, E1, E3 19.1

12.19.217. WRFTPLT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.
An arbitrary number of data lines can be entered. Each data line should be terminated with
the symbol /. All data should be terminated with a final slash /.
One data line contains the following parameters:
1. well name (or number), or well mask defining a subset of wells with common prefix
(should end with an asterisk *), or well list name defined via WLIST (see 12.19.33).
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 – don’t 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 opened or stopped;
• NO – don’t output data.

Example
WRFTPLT
'WELL3*' REPT REPT /
'P1' YES YES /
'P2' YES NO /
/

12.19.217. WRFTPLT 1923

Keywords for formats tN, E1, E3 19.1

For the wells having names starting 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 this time only.
For the well P2, output of RFT data this time only.

12.19.217. WRFTPLT 1924

Keywords for formats tN, E1, E3 19.1

12.19.218. SKIP

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION x SUMMARY x SCHEDULE

The keyword provides all data below this keyword to be ignored till the keyword END-
SKIP (see 12.19.225), 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.19.218),
SKIP100 (see 12.19.220), SKIP300 (see 12.19.221), SKIPTNAV (see 12.19.222), SKIPON
(see 12.19.224), SKIPOFF (see 12.19.223), ENDSKIP (see 12.19.225).
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.19.218. SKIP 1925

Keywords for formats tN, E1, E3 19.1

12.19.219. SKIPREST

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY SCHEDULE

This keyword allows to ignore all subsequent keywords in SCHEDULE section, until a
restart time has been reached RESTART (see 12.16.3). You shouldn’t delete the keywords
(that should be ignored) manually.

Example
SKIPREST

12.19.219. SKIPREST 1926

Keywords for formats tN, E1, E3 19.1

12.19.220. SKIP100

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION x SUMMARY x SCHEDULE

The keyword provides all data below this keyword to be ignored (if the model is open
in tNavigator as E1 model) till the keyword ENDSKIP (see 12.19.225), which terminates the
skipping of the keywords. (If the model is open in tNavigator as E3 model the data will be
read and used.)

This keyword can be used in any section (not only SCHEDULE section).

All the keywords specifying data skipping are the following: SKIP (see 12.19.218),
SKIP100 (see 12.19.220), SKIP300 (see 12.19.221), SKIPTNAV (see 12.19.222), SKIPON
(see 12.19.224), SKIPOFF (see 12.19.223), ENDSKIP (see 12.19.225).
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.19.220. SKIP100 1927

Keywords for formats tN, E1, E3 19.1

12.19.221. SKIP300

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION x SUMMARY x SCHEDULE

The keyword provides all data below this keyword to be ignored (if the model is open
in tNavigator as E3 model) till the keyword ENDSKIP (see 12.19.225), which terminates the
skipping of the keywords. (If the model is open in tNavigator as E1 model the data will be
read and used.)

This keyword can be used in any section (not only SCHEDULE section).

All the keywords specifying data skipping are the following: SKIP (see 12.19.218),
SKIP100 (see 12.19.220), SKIP300 (see 12.19.221), SKIPTNAV (see 12.19.222), SKIPON
(see 12.19.224), SKIPOFF (see 12.19.223), ENDSKIP (see 12.19.225).
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.19.221. SKIP300 1928

Keywords for formats tN, E1, E3 19.1

12.19.222. SKIPTNAV

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION x SUMMARY x SCHEDULE

The keyword provides all data below this keyword to be ignored till the keyword END-
SKIP (see 12.19.225), which terminates the skipping of the keywords.
The keyword is analogous to the E1/E3-compatible keyword SKIP (see 12.19.218). This key-
word can be used in any section (not only SCHEDULE section).

All the keywords specifying data skipping are the following: SKIP (see 12.19.218),
SKIP100 (see 12.19.220), SKIP300 (see 12.19.221), SKIPTNAV (see 12.19.222), SKIPON
(see 12.19.224), SKIPOFF (see 12.19.223), ENDSKIP (see 12.19.225).
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.19.222. SKIPTNAV 1929

Keywords for formats tN, E1, E3 19.1

12.19.223. SKIPOFF

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION x SUMMARY x SCHEDULE

The keyword puts an end to data skipping started earlier with the keywords
SKIP (see 12.19.218), SKIP100 (see 12.19.220), SKIP300 (see 12.19.221), SKIPT-
NAV (see 12.19.222). The data after SKIPOFF will be read till the keyword SKIPON
(see 12.19.224), which switches data skipping on again.

So the keywords SKIPON (see 12.19.224) and SKIPOFF (see 12.19.223) should be used
between SKIP (see 12.19.218) (SKIP100 (see 12.19.220), SKIP300 (see 12.19.221), SKIPT-
NAV, see 12.19.222) and ENDSKIP (see 12.19.225).
This keyword can be used in any section (not only SCHEDULE section).

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

12.19.223. SKIPOFF 1930

Keywords for formats tN, E1, E3 19.1

ignored (between SKIPON and ENDSKIP).

12.19.223. SKIPOFF 1931

Keywords for formats tN, E1, E3 19.1

12.19.224. SKIPON

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION x SUMMARY x SCHEDULE

The keyword switches on data skipping which was switched of via the keyword SKIPOFF
(see 12.19.223). The data after SKIPON (see 12.19.224) will be ignored till the keyword END-
SKIP (see 12.19.225).

So the keywords SKIPON (see 12.19.224) and SKIPOFF (see 12.19.223) should be used
between SKIP (see 12.19.218) (SKIP100 (see 12.19.220), SKIP300 (see 12.19.221), SKIPT-
NAV, see 12.19.222) and ENDSKIP (see 12.19.225).
This keyword can be used in any section (not only SCHEDULE section).

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.19.224. SKIPON 1932

Keywords for formats tN, E1, E3 19.1

12.19.225. ENDSKIP

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC x GRID x EDIT x PROPS
Section
x REGIONS x SOLUTION x SUMMARY x SCHEDULE

The keyword terminates data that is below the keyword SKIP (see 12.19.218) (SKIP100
(see 12.19.220), SKIP300 (see 12.19.221), SKIPTNAV, see 12.19.222) and is ignored. The
data after ENDSKIP will be read and used.

All the keywords specifying data skipping are the following: SKIP (see 12.19.218),
SKIP100 (see 12.19.220), SKIP300 (see 12.19.221), SKIPTNAV (see 12.19.222), SKIPON
(see 12.19.224), SKIPOFF (see 12.19.223), ENDSKIP (see 12.19.225).
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.19.225. ENDSKIP 1933

Keywords for formats tN, E1, E3 19.1

12.19.226. DRILPRI

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword defines the default priority formula for the prioritized drilling queue – sec-
tion 2.14.14. A well can be placed to prioritized drilling queue via the keyword WDRIL-
PRI (see 12.19.227) without a fixed priority (parameter 2 of the keyword WDRILPRI
(see 12.19.227).
Drilling priorities for the prioritized drilling queue are calculated at constant time intervals,
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 – well’s potential oil, water and gas production rates (description of well’s
potential flow rate is in the section 5.6.7),
a, b, c, d, e, f , g, h – coefficients specified via this keyword. These coefficients shouldn’t 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.19.227).

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 WDRIL-
PRI, see 12.19.227);

2. a;

3. b;

4. c;

5. d ;

6. e;

12.19.226. DRILPRI 1934

Keywords for formats tN, E1, E3 19.1

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.19.226. DRILPRI 1935

Keywords for formats tN, E1, E3 19.1

12.19.227. WDRILPRI

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword puts wells into the prioritized drilling queue and defines their drilling pri-
ority values – section 2.14.14. The wells should be specified as shut or stopped producers or
injectors. (Drilling queue doesn’t 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.19.226).

Any number of data rows could be entered (terminated with a slash /). All data should be
terminated with a final slash /.
One data row consists of the following parameters:

1. Well name of well list (WLIST, see 12.19.33);

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.19.226) from wells potential rates via the formula, whose coefficients are
set in DRILPRI (see 12.19.226) (for producers). For injectors – drilling priority is
equal to their injection potentials.

Default: negative value.

3. Drilling unit number. If a number greater than 0 is set, then all wells with the same
unit number are drilled simultaneously. Their priorities (calculated or set by users) are
summed during the procedure of choosing candidates from the drilling queue. When the
wells with the same drilling unit number are selected then the drilling rig is occupied
for the sum of the wells’ drilling times (parameter 2 WDRILTIM, see 12.19.228). All
wells start to produce immediately if nothing else is set in parameter 3 of the keyword
WDRILTIM (see 12.19.228).
Default: 0.

12.19.227. WDRILPRI 1936

Keywords for formats tN, E1, E3 19.1

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.19.227. WDRILPRI 1937

Keywords for formats tN, E1, E3 19.1

12.19.228. WDRILTIM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies the time taken to drill the well. Section Prioritized drilling queue.
Sequential drilling queue – 2.14.14.

Any number of data rows could be entered (terminated with a slash /). All data should be
terminated with a final slash /.
One data row consists of the following parameters:

1. Well name, or well list name defined via WLIST (see 12.19.33).

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.19.229) or WDRILPRI, see 12.19.227).
Default: 0.

3. Closure of well during drilling and workovers:

YES – the well will be closed during its drilling and workovers (well’s efficiency factor
WEFAC (see 12.19.83) is temporary set to zero) at the time steps during drilling and
workovers. The closure time for workovers is set via WORKLIM (see 12.19.232) (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: 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.19.228. WDRILTIM 1938

Keywords for formats tN, E1, E3 19.1

12.19.229. QDRILL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword places the wells to sequential drilling queue. Section Prioritized drilling
queue. Sequential drilling queue – 2.14.14.

The wells should be specified as shut or stopped producers or injectors. (Drilling queue
doesn’t 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.19.229. QDRILL 1939

Keywords for formats tN, E1, E3 19.1

12.19.230. GDRILPOT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword defines minimum potential rates for drilling. In the case if the group’s pro-
duction or injection potential falls below the specified limit then in the drilling queue (QDRILL
(see 12.19.229) or WDRILPRI, see 12.19.227) a new well will be found to open to support the
group’s potential.

Any number of data rows could be entered (terminated with a slash /). All data should be
terminated with a final slash /.
One data row consists of the following parameters:

1. group name or group mask defining a subset of groups with common prefix (should end
with an asterisk *);

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.19.230. GDRILPOT 1940

Keywords for formats tN, E1, E3 19.1

12.19.231. WDRILRES

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.19.42) 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.19.229), WDRILPRI (see 12.19.227), the section Prioritized drilling queue. Sequential
drilling queue – 2.14.14).
In this case the well will be removed from drilling queue or automatic opening queue.

This keyword doesn’t prevent if a new well is opened manually via the keyword
WELOPEN (see 12.19.128).

The keyword doesn’t have any parameters.

12.19.231. WDRILRES 1941

Keywords for formats tN, E1, E3 19.1

12.19.232. WORKLIM

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies the time taken for well automatic workover days. The data should
be terminated with a slash /.

Default: 0 days.
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.19.74), CECON (see 12.19.80), GECON (see 12.19.121), GCONPROD (see 12.19.86),
GCONPRI (see 12.19.89), GCONSALE (see 12.19.194), PRORDER (see 12.19.238) and
WORKTHP (see 12.19.85).

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.

Example
WORKLIM 7 /

12.19.232. WORKLIM 1942

Keywords for formats tN, E1, E3 19.1

12.19.233. GRUPRIG

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.19.232). 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.19.74), GECON (see 12.19.121), CECON (see 12.19.80), GCON-
PROD (see 12.19.86), GCONPRI (see 12.19.89), PRORDER (see 12.19.238), WORKTHP
(see 12.19.85).

• Manual closure and opening of connections (COMPDAT, see 12.19.6) don’t depend of
rig availability and don’t occupy any rig.

A drilling rig.

• A drilling of a well takes a time that is specified in the keyword WDRILTIM

(see 12.19.228). One rig is assigned for one well during the time of drilling and is
unavailable 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.19.229), WDRILPRI, see 12.19.227), wells on automatic opening (parameter 2 of
the keyword WCONPROD (see 12.19.42) is AUTO) or if there are wells that are opened
on the closure of another well (parameter 8 of the keyword WECON, see 12.19.74).

• Manual well opening doesn’t depend of drilling rig availability and doesn’t occupy any
rig.

Any number of data rows could be entered (terminated with a slash /). All data should be
terminated with a final slash /.
One data row consists of the following parameters:

12.19.233. GRUPRIG 1943

Keywords for formats tN, E1, E3 19.1

1. Group name, or group mask defining a subset of groups with common prefix (should
end with an asterisk *), 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. Don’t make any changes to existing group’s 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.

Default: 0.

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. Don’t make any changes to existing group’s 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.

Default: 0.

4. Add or remove specified rigs: ADD – add these rigs to group, REM – delete these rigs
from group.
Default: ADD.

Example
GRUPRIG
GROUP1 1 1 ADD /
GROUP2 2 2 ADD /
GROUP3 2 2 ADD /
FIELD 3 1 ADD /
/

12.19.233. GRUPRIG 1944

Keywords for formats tN, E1, E3 19.1

12.19.234. NUPCOL

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword specifies the number of Newton method 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) (see section 2.14.13). 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 /.

Default: 3.
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 Newton’s method for the time
step is reached in NUPCOL iterations.

Example
NUPCOL
5 /

12.19.234. NUPCOL 1945

Keywords for formats tN, E1, E3 19.1

12.19.235. WELLOPTS

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword is a full analog of the keyword NUPCOL (see 12.19.234) (see also section
2.14.13).

12.19.235. WELLOPTS 1946

Keywords for formats tN, E1, E3 19.1

12.19.236. GCONTOL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword will override the value of NUPCOL (see 12.19.234), specified earlier.

(NUPCOL (see 12.19.234) – 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 itera-
tions at the time step the well targets will stay unchanged.)

The following parameters should be specified (The data should be terminated with a slash
/.):

1. tolerance fraction to which group/field flow targets must be met. IGNORED, this is an
E1/E3 compatibility field;

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.19.234) or previously
defined GCONTOL.

Example
GCONTOL
* 4 /

12.19.236. GCONTOL 1947

Keywords for formats tN, E1, E3 19.1

12.19.237. WLIFT

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword specifies an automatic retubing and THP or lift switching.

Retubing, THP or lift switching are performed in the following cases:

• well’s production rate falls below the value specified in parameter 2,

• well’s water cut exceeds the value specified in parameter 7,

• well’s 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 well’s 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.19.237. WLIFT 1948

Keywords for formats tN, E1, E3 19.1

Any number of data rows could be entered (terminated with a slash /). All data should be
terminated with a final slash /.
One data row consists of the following parameters:

1. Well name, or well list name defined via WLIST (see 12.19.33).

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.19.238) or if the well dies under THP control.
Default: 0.

3. Phase to which the production rate is specified in parameter 2: OIL or LIQUID.

Default: OIL.

4. New VFP table number for retubing (this number replaces the number, specified in
WCONPROD, see 12.19.42).
Negative or zero value: retubing operation is not performed.
Default: 0.

5. New artificial lift quantity for lift switching (this number replaces the number, specified
in WCONPROD (see 12.19.42) WELTARG, see 12.19.60). 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.
Default: 0.

6. New well efficiency factor after lift switching (this number replaces the number, speci-
fied in WEFAC (see 12.19.83).
Negative or zero value: original value of well efficiency factor stays unchanged.
Default: 0.

7. Well’s 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.19.238) or if the well dies under THP control.
Default: 0.

8. New THP limit (this number replaces the number, specified in WCONPROD
(see 12.19.42) or WELTARG, see 12.19.60). To perform THP switching in stages the
decrement value should be specified in parameter 11.
Negative or zero value: switching operation is not performed.
Default: 0.

12.19.237. WLIFT 1949

Keywords for formats tN, E1, E3 19.1

9. Well’s 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.19.238) or if the well dies under THP control.
Default: 0.

10. Increment that will be added to (or subtracted from) the well’s ALQ value at each lift
switching event until the final ALQ value (specified in parameter 5) will be reached.
Default: change to the value of parameter 5 in one operation.

11. Decrement (METRIC: barsa, FIELD: psia) which will be subtracted from the well’s
THP value at each THP switching event, until the final THP value (specified in param-
eter 8) will be reached.
Default: change to the value of parameter 8 in one operation.

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.19.237. WLIFT 1950

Keywords for formats tN, E1, E3 19.1

12.19.238. PRORDER

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies the order of actions to be performed if a group can’t meet its
production rate target specified in GCONPROD (see 12.19.86). Two lines of parameters must
be specified, each terminated with a slash /.
The first line contains the possible actions. The actions will be performed in the order
in which they are specified. Next action is performed 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.19.229) or Priori-
tized – WDRILPRI (see 12.19.227). Time of drilling one well is specified in WDRILTIM
(see 12.19.228), drilling rigs – GRUPRIG (see 12.19.233).

• REPERF – open new connections on AUTO mode in existing wells.

Wells connections should stay on automatic opening (parameter 6 of the keyword COM-
PDAT (see 12.19.6) or the keyword WELOPEN, see 12.19.128). Time of well’s workover
is specified in WORKLIM (see 12.19.232), workover rigs – GRUPRIG (see 12.19.233).

• THP – reduce each well’s THP limit to a specified lower value.

If a new THP limit is specified (parameter 8 of WLIFT, see 12.19.237), the well switches
on it (this is analog to the switching the well to a separator with lower pressure to
increase well’s productivity). If parameter 11 of WLIFT (see 12.19.237) 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.19.237) 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.19.237), then the
well will use it to interpolate the VFP table (this is analog to the switching on or updat-
ing of artificial lift in the well). If parameter 10 of WLIFT (see 12.19.237) 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

12.19.238. PRORDER 1951

Keywords for formats tN, E1, E3 19.1

(see 12.19.237).
Restrictions on the total amount of group’s lift can be specified via GLIFTLIM
(see 12.19.240).

Default: empty (no actions).

If no parameter is specified in this line (the terminating slash / comes immediately af-
ter the keyword), then no operations will be performed in case if the group can’t meet its
production rate target.
The second line contains the flags that control the application of the production rules:

1. The flag that controls the application of the production rules when a well is shut for
drilling or workover operations (that is, when the 3rd parameter of keyword WDRILTIM
(see 12.19.228) is set to YES; otherwise this flag has no effect). The possible values are:
YES: Allows further actions to take place in the timestep while a well is shut for drilling
or workover operations, if the group cannot immediately make its target rate.
NO: Denies further production rule actions to take place within this group while a
production well is shut for drilling or workover operations until the next timestep that
begins after the completion of the operations.

2. The flag that controls the order in which the actions included in the keyword WLIFT
(see 12.19.237) are performed when triggered by individual wells rather than by group
behavior. The possible values are:
YES: Apply the three actions (THP, RETUBE, LIFT) in the order specified in the first
line of data within this keyword.
NO: Apply the actions in the order specified by the keyword WLIFT (see 12.19.237),
which is: first THP, then RETUBE, then LIFT.

Default: YES YES.

Example
PRORDER
DRILL RETUBE /
NO /
This example causes the following behavior when a group fails to make its GCONPROD
(see 12.19.86) production target: first the new wells from the drilling queue are opened.
When the queue runs empty, the wells having secondary VFP numbers are reset to the new
VFP tables. While doing that, no actions are performed when a well is shut for drilling or
workover operations.

12.19.238. PRORDER 1952

Keywords for formats tN, E1, E3 19.1

12.19.239. LIFTOPT

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword sets that Gas Lift Optimization option is used – 2.14.9.
The keyword should be specified before GLIFTOPT (see 12.19.241), WLIFTOPT (see 12.19.242).
The data should be terminated with a slash /.

The following parameters should be specified:

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
well’s 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.
Default: 0.

4. Should tNavigator optimize gas lift during each of the first NUPCOL (see 12.19.234)
iterations of the time step: tNavigator supports only YES (the value of NUPCOL can be
also redefined via GCONTOL, see 12.19.236).
Default: YES.

Example
LIFTOPT
35000 0.0 50.0 /

12.19.239. LIFTOPT 1953

Keywords for formats tN, E1, E3 19.1

12.19.240. GLIFTLIM

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies the maximum group capacity for artificial lift – 2.14.9.

Any number of data rows could be entered (terminated with a slash /). All data should be
terminated with a final slash /.
The following parameters should be specified:

1. group name, or group mask defining a subset of groups with common prefix (should
end with an asterisk *), or FIELD;

2. maximum total lift capacity.

This value is a limit of the sum of the artificial lift quantity (ALQ) values of all sub-
ordinate 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 group’s 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.19.240. GLIFTLIM 1954

Keywords for formats tN, E1, E3 19.1

12.19.241. GLIFTOPT

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword specifies the group lift gas limits for gas lift optimization option – 2.14.9.

Any number of data rows could be entered (terminated with a slash /). All data should be
terminated with a final slash /.
The following parameters should be specified:

1. group name, or group mask defining a subset of groups with common prefix (should
end with an asterisk *), or FIELD;

2. maximum lift gas supply limit for the group (METRIC: sm3 /day, FIELD: Msc f /day).
The group’s 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.19.83), for
groups – GEFAC, see 12.19.84). This parameter can be set via user defined quantity
UDQ (see 12.19.165);

3. maximum total gas rate for the group (METRIC: sm3 /day, FIELD: Msc f /day). The
group’s 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 well’s or group’s efficiency factor (for
wells – WEFAC (see 12.19.83), for groups – GEFAC, see 12.19.84). The wells below
this group are not assigned a lift gas increments if they would cause this limit to be
exceeded.
This parameter can be set via user defined quantity UDQ (see 12.19.165).

Example
GLIFTOPT
GROUP1 100000 /
GROUP2 90000 /
/

12.19.241. GLIFTOPT 1955

Keywords for formats tN, E1, E3 19.1

12.19.242. WLIFTOPT

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword sets well parameters for Gas lift optimization – 2.14.9.

Any number of data rows could be entered (terminated with a slash /). All data should be
terminated with a final slash /.
The following parameters should be specified:
1. Well name, or number, or well list name defined via WLIST (see 12.19.33);.
2. Should tNavigator calculate the well’s lift gas injection rate with optimization: YES or
NO – in this case the well’s 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.19.42) or
WELTARG (see 12.19.60).
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 spec-
ifies the fixed lift gas injection rate for the well. This parameter can be set via user
defined quantity UDQ (see 12.19.165).
Default: if 2-nd parameter is YES, then the largest ALQ in well’s VFP table, otherwise
stays unchanged.
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
well’s 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 – well’s 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.19.242. WLIFTOPT 1956

Keywords for formats tN, E1, E3 19.1

Default: 1.

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 receiv-
ing 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).
Default: 0.

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.
Default: 0.

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 can’t
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: NO.

Example
WLIFTOPT
W34 YES 100000 1.01 1* 1.0 YES /
/

12.19.242. WLIFTOPT 1957

Keywords for formats tN, E1, E3 19.1

12.19.243. OPTIONS

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword activates special option of model reading, calculation and saving results. The
data should be terminated with a slash /.

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 doesn’t change model calcula-
tion – E1/E3 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.19.140) – parameter PAVWEIGHT.

Parameter PAVWEIGHT of RUNCTRL (see 12.19.140) 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.18.1) is specified one of the
following ways:

• default
∑ POTO ∗ SO ∗ Porv
FPPO =
∑ SO ∗ Porv
where POTO – oil potential, SO – oil saturation;

12.19.243. OPTIONS 1958

Keywords for formats tN, E1, E3 19.1

• 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.16.40) or it can be taken from the 1-st equilibration region reference depth,
specified via EQUIL (see 12.16.2). If keywords DATUM (see 12.16.40), EQUIL
(see 12.16.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.16.41).

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 un-
specified 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 pressure.

12.19.243. OPTIONS 1959

Keywords for formats tN, E1, E3 19.1

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 keywords
MULTNUM (see 12.4.22), FLUXNUM (see 12.4.18), PINCHNUM (see 12.2.62) or OPER-
NUM (see 12.4.21). If this parameter value is 1, then regions specified via the keyword
MULTNUM (see 12.4.22) 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.

141. The value can be set equal to 1. This option is used for compatibility with obsolete
E1/E3 logic to work with grid coarsening COARSEN, see 12.2.105).

145. This option can be used as an additional tuning parameter for wellbore mixture density
averaging in stopped wells (i.e. the wells with zero rate). When this parameter is set
equal to non-zero value, then the density of wellbore mixture will be averaged in the
same way as in the open wells. In other words, in RUNCTRL (see 12.19.140) keyword
the properties of WELLDENWEIGHTSTOP parameter will copied fromdefault values
WELLDENWEIGHTOPEN parameter.
Default: 0 (option in not enabled).

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.19.243. OPTIONS 1960

Keywords for formats tN, E1, E3 19.1

12.19.244. OPTIONS3

Data x tN x E1 x E3 IM GE ST MO
format
x RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword activates special option of model reading, calculation and saving results. The
data should be terminated with a slash /.

tNavigator supports only 44-th parameter of this keyword. All other parameters are ignored
(tNavigator reads them but they does not apply to the model – E1/E3 data format compatibil-
ity).

Description of supported parameter:

44. This option may be used to apply correction to calculation of the wellbore mixture
density.

NEW
ρwellbore OLD
+ n · ρwellbore
ρwellbore = (12.7)
n+1
Where:

• ρwellbore
NEW – the actual value of wellbore mixture density on the current timestep;
• ρwellbore
OLD – the value of of wellbore mixture density from the previous timestep;
• n – integer value, specified by this option.
– If n > 0 then the density of wellbore mixture will be averaged according to
equation 12.7.
– If n = −1 then density averaging will not be used.
Default: -1 .

If non-default value is specified, then this option will be converted into tNavigator key-
word RUNCTRL (see 12.19.140) – parameter WELLDENWEIGHT .

Example
OPTIONS3
43* 2 /

12.19.244. OPTIONS3 1961

Keywords for formats tN, E1, E3 19.1

12.19.245. COMPVAL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets length of perforated interval in specified block. To set this in local grid
refinement use the keyword COMPVALL (see 12.19.246).
The following parameters should be specified:

1. well name;

2. X -coordinate of well connection;

Default: 0 (any value).

3. Y -coordinate of well connection;

Default: 0 (any value).

4. Z -coordinate of upper neighbor block for well connection;

Default: 0 (any value).

5. Z -coordinate of lower neighbor block for well connection;

Default: 0 (any value).

6. type of 7-th parameter:

• LENGTH;

7. length of perforated interval (METRIC: m, FIELD: f t ).

Each line should be ended by symbol /. The data should be terminated with a slash /.

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 consecu-
tive blocks are set. Length of each perforated interval is equal to 3.048 ft.

12.19.245. COMPVAL 1962

Keywords for formats tN, E1, E3 19.1

12.19.246. COMPVALL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets length of perforated interval in specified block.

The following parameters should be specified:
1. well name;
2. name of the local grid refinement where this well is (LGRs name is set via CARFIN,
see 12.2.97);
3. X -coordinate of well connection;
Default: 0 (any value).
4. Y -coordinate of well connection;
Default: 0 (any value).
5. Z -coordinate of upper neighbor block for well connection;
Default: 0 (any value).
6. Z -coordinate of lower neighbor block for well connection;
Default: 0 (any value).
7. type of 7-th parameter:
• LENGTH;
8. length of perforated interval (METRIC: m, FIELD: f t ).
Each line should be ended by symbol /. The data should be terminated with a slash /.

Example
COMPVALL
'NO_HTWI' 'LGR1' 3 3 1 1 LENGTH 3.048 /
'NO_HTWI' 'LGR1' 3 3 2 2 LENGTH 3.048 /
'NO_HTWI' 'LGR1' 3 3 3 3 LENGTH 3.048 /
'NO_HTWI' 'LGR1' 3 3 4 4 LENGTH 3.048 /
/
In the example for well NO_HTWI (that is in the LGR1) lengths of four perforated inter-
vals in four consecutive blocks are set. Length of each perforated interval is equal to 3.048
ft.

12.19.246. COMPVALL 1963

Keywords for formats tN, E1, E3 19.1

12.19.247. WNETDP

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword is should be used only with the option NETWORK (2.14.11). It sets fixed
pressure drop value between a well’s tubing head pressure and its group’s corresponding node
in the network.

The following parameters should be specified:

1. Well name, name mask, or well list name defined via WLIST (see 12.19.33).

2. Fixed pressure drop value between a well’s tubing head pressure and its group’s corre-
sponding node in the network (METRIC: bar , FIELD: psi).
Default: 0.

Each line should be ended by /. The data should be terminated with a slash /.

Example
WNETDP
'28' 5.0 /
'29' 2.0 /
'30' 5.0 /
/
In the example fixed pressure drop values are specified for 3 wells.

12.19.247. WNETDP 1964

Keywords for formats tN, E1, E3 19.1

12.19.248. WELLPROD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword sets the production targets for a well.

The keyword is obsolete. It is recommended to use the keyword WCONPROD

(see 12.19.42).

The following parameters should be specified:

1. Well name, well name mask, or well list name defined via WLIST (see 12.19.33).
2. Well control mode:
• OIL – oil rate;
• WAT – water rate;
• GAS – gas rate;
• LIQ – liquid rate;
• BHP – bottom hole pressure;
• 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.54) option);
• SATT – water saturation temperature (see parameter 16; only for models with
THERMAL (see 12.1.54) 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).
Default: rate limit = 1e + 20 m3 /day.

12.19.248. WELLPROD 1965

Keywords for formats tN, E1, E3 19.1

7. BHP value or limit (METRIC: barsa, FIELD: psia).

Default: for E1 format models – 1atma = patm (atmospheric pressure), for E3 format
models – 100 atma = 1470 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).
Default: 0.

9. Liquid rate in reservoir conditions (METRIC: rm3 /day, FIELD: rb/day).

10. Wet gas rate or limit (METRIC: sm3 /day, FIELD: /day).

11. Well VFP table number (VFPPROD (see 12.19.66), VFPCORR, see 12.19.71); if zero,
THP will not be reported.
Default: 0.

12. Artificial lift quantity (ALQ) that will be used in THP calculations (see the keyword
VFPPROD, see 12.19.66).
Default: 0.

13. The target or limit total molar rate (METRIC: kg-mol/day, FIELD: lb-mol/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.54).
Rate can be set by UDQ (see 12.19.165).

15. Pressure offset ∆P for water saturation pressure control (METRIC: bar , FIELD: psia).
This parameter can be used only in THERMAL (see 12.1.54) runs. Can be specified by
user via UDQ (see 12.19.165).
The constraint for BHP is BHP ≥ Psat + ∆P, where Psat is maximum saturated water
pressure in all blocks with producing 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.54) runs. Can be specified

by user via UDQ (see 12.19.165).

The constraint for BHP is BHP ≥ Psat (T + ∆T ), where T is maximum temperature in
all blocks with producing connections.

Each line of data should be ended by /. The data should be terminated with a slash /.

Example
WELLPROD
'HAIL-3' 'GROUP' 2* 20000 1* 2000 6* /
/

12.19.248. WELLPROD 1966

Keywords for formats tN, E1, E3 19.1

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 de-
fault.

12.19.248. WELLPROD 1967

Keywords for formats tN, E1, E3 19.1

12.19.249. GRUPPROD

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.19.86).

The following parameters should be specified:

1. Group name, or group mask defining a subset of groups with common prefix (should
end with an asterisk *), or FIELD (for field control).
Default: default group (group of wells with default group in WELSPECS, see 12.19.3).

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.

Default: NONE.

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).
Default: rates have no limit.

12.19.249. GRUPPROD 1968

Keywords for formats tN, E1, E3 19.1

Each line of data should be ended by /. The data should be terminated with a slash /.

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.19.249. GRUPPROD 1969

Keywords for formats tN, E1, E3 19.1

12.19.250. WELLCOMP

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets location and properties of one or several connections of specified well.
It should be used after the keyword WELSPECS (see 12.19.3), which defines that well.
The keyword is obsolete. It is recommended to use the keyword COMPDAT (see 12.19.6).

Each line of data should be ended by a symbol /. The data should be terminated with a
slash /.
The following parameters should be specified:
1. Well name, well name mask, or well list name defined via WLIST (see 12.19.33).
2. Perforated interval coordinate in X direction (IW); there is i in 5.6.1.
Default: taken from WELSPECS (see 12.19.3).
3. Perforated interval coordinate in Y direction (JW); there is j in 5.6.1.
Default: taken from WELSPECS (see 12.19.3).
4. Number of layer where this vertical perforated interval starts (layers are numbered
top-down starting from 1); this is number k in 5.6.1.
Default: 1.
5. Number of layer where this vertical perforated interval ends, this is number k in 5.6.1.
Default: 1.
6. Saturation table number.
Default: tNavigator will use the saturation table number that is specified for block with
connection via SATNUM (see 12.4.3).
7. Well diameter (METRIC: m, FIELD: f t ).
Default: dw = 0.156 m.
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.6.1.
Default: calculated.
9. Skin factor, this is value s in 5.6.2.
Default: 0.

12.19.250. WELLCOMP 1970

Keywords for formats tN, E1, E3 19.1

10. Imbibition table number, IGNORED, this is an E1/E3 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.6.2).
Default: negative value.

12. Direction in which this interval penetrates grid block: X, Y or Z.

Default: Z.

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.

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.19.250. WELLCOMP 1971

Keywords for formats tN, E1, E3 19.1

12.19.251. TRANGE

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies minimal and maximal temperature of formation. The values can be
changed during calculation. The data should be terminated with a slash /.
The following parameters should be specified:

1. Minimal formation temperature (METRIC: ◦ C, FIELD: ◦ F);

Default: 1 ◦ C.

2. Maximal formation temperature (METRIC: ◦ C, FIELD: ◦ F).

Default: 500 ◦ C.

Example
TRANGE
50 250

12.19.251. TRANGE 1972

Keywords for formats tN, E1, E3 19.1

12.19.252. SCDPTAB

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.

Section Scale deposition model – 2.25.

The sea water fraction is equated to the concentration of a passive water tracer which
is noted in keyword SCDPTRAC (see 12.19.253). Tables which defined via SCDPTAB are
allocated to individual wells with the keyword WSCTAB (see 12.19.255). The effect of the
deposited scale on the productivity index of the well should be defined in scale damage tables
(keyword SCDATAB, see 12.19.254).
The number of tables is set via the keyword SCDPDIMS (see 12.1.117). 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.19.252) sets one dependence table. The
left column contains sea water concentration values, the right one – values of total rate of
scale deposition.

12.19.252. SCDPTAB 1973

Keywords for formats tN, E1, E3 19.1

12.19.253. SCDPTRAC

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.25). 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.10)
with water injectors given a tracer value of 1.0 (keyword WTRACER, see 12.19.171), while
the tracer value of the water initially in the reservoir is set to 0.0.
The data should be terminated with a slash /.
The following parameters should be specified:

1. tracer name.

Example
SCDPTRAC
AAA /
In the example the keyword SCDPTRAC (see 12.19.253) notes tracer name ”AAA”.

12.19.253. SCDPTRAC 1974

Keywords for formats tN, E1, E3 19.1

12.19.254. SCDATAB

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.

Section Scale deposition model – 2.25.

Parameters of this keyword are tables which number is set via the keyword SCDPDIMS
(see 12.1.117). 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.19.254. SCDATAB 1975

Keywords for formats tN, E1, E3 19.1

12.19.255. WSCTAB

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword may be used to assign scale deposition (the keyword SCDPTAB,
see 12.19.252) and scale damage (the keyword SCDATAB, see 12.19.254) tables to indi-
vidual 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 /.
The following parameters should be specified:

1. Well name, well name template and symbol * (i.e. a mask), or well list name defined
via WLIST (see 12.19.33).

2. Scale deposition table number. 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 deposited around its
connections.
Default: 0.

3. Scale damage table number. A value which is less or equal to 0 means that no scale
damage table is assigned to that well. So, the well performance has no influence from
the currently deposited scale.
Default: 0.

Example
WSCTAB
WA-1 1 1 /
WA-2 1 1 /
WA-3 1 1 /
/
In the example the keyword WSCTAB (see 12.19.255) assigns scale deposition and scale
damage tables to three wells (WA-1, WA-2, WA-3). In each case table #1 is assigned.

12.19.255. WSCTAB 1976

Keywords for formats tN, E1, E3 19.1

12.19.256. WSEGCNTL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword is used to specify settings of precision of equations system solution manually.
The data should be terminated with a slash /.
The following parameters should be specified:

1. Well name.

2. Residual value which leads to exit of Newton’s iterations.

Default: 1e-3.

3. Variation of main variables which leads to exit of Newton’s iterations.

Default: 1e-3.

4. Weight.
Default: 0.5.

5. Minimal variation from pressure in perforation which is used as initial approximation.

Default: 1.

6. Initial approximation of pressure in well segments. The following types of approxima-

tion are possible:

• CONN – pressure in one of segment connections is taken as an initial approxima-

tion of pressure;
• SEG – pressure in parent segment is taken as an initial approximation of pressure
in child segment.
• Default: CONN.

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.19.256. WSEGCNTL 1977

Keywords for formats tN, E1, E3 19.1

12.19.257. PSEUPRES

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.19.213)
keyword.
Example
PSEUPRES

12.19.257. PSEUPRES 1978

Keywords for formats tN, E1, E3 19.1

12.19.258. GWRATMUL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.
The following parameters should be specified:

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
should be terminated with a slash /.
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.19.258. GWRATMUL 1979

Keywords for formats tN, E1, E3 19.1

12.19.259. APILIM

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword is used to control API tracking calculation in E1/E3.

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.12).

The list of supported keywords is in the section 2.8.8.

12.19.259. APILIM 1980

Keywords for formats tN, E1, E3 19.1

12.19.260. AUTOSAVE

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword is used to control frequency of SAVE file writing in E1/E3.

In tNavigator this keyword is IGNORED due to different approach to saving calculation re-
sults.

12.19.260. AUTOSAVE 1981

Keywords for formats tN, E1, E3 19.1

12.19.261. WELLGR

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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 /.

The following parameters should be specified:

1. Well name, or well list name defined via WLIST (see 12.19.33), or well mask defining
a subset of wells with common prefix (should end with an asterisk *).

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.

Default: Y.

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;

12.19.261. WELLGR 1982

Keywords for formats tN, E1, E3 19.1

• ALL – set all guide rates.

Default: 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.19.261. WELLGR 1983

Keywords for formats tN, E1, E3 19.1

12.19.262. SLAVES

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.13.

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 should
be terminated with a slash /.

The following parameters should be specified:

1. name of SLAVE (will be used later in the keyword GRUPMAST, see 12.19.263);

2. root name of the slave reservoir’s data file;

3. this parameter should be defaulted (*) (the host name where the model should be calcu-
lated; this is an E1/E3 compatibility field);

4. path to the folder in which the data file is located, from the root folder of the host.

Example
SLAVES
'SLAVE1' 'test1' * 'folder1'/
'SLAVE2' 'test2' * 'folder2'/
'SLAVE3' 'test3' * 'folder3'/
/

12.19.262. SLAVES 1984

Keywords for formats tN, E1, E3 19.1

12.19.263. GRUPMAST

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword sets principal (master) and subordinate (slave) groups in Reservoir coupling
option. The detailed description of Reservoir Coupling is in the section 5.13.

Any number of lines can be specified, each one terminated with a slash /. The data should
be terminated with a slash /.

The following parameters should be specified:

1. master group’s name or group mask defining a subset of groups with common prefix
(should end with an asterisk *). Master groups should be set in the keyword GRUPTREE
(see 12.19.100). 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.19.262);

3. name of the master group’s 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.
If this parameter is defaulted, then the name of the slave group (associated with master
group) is considered the same as the name of master group.

On the picture 64 there is a scheme of MASTER group and SLAVES that are set in this
example.

12.19.263. GRUPMAST 1985

Keywords for formats tN, E1, E3 19.1

Figure 64. 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.19.263. GRUPMAST 1986
Keywords for formats tN, E1, E3 19.1

12.19.264. GRUPSLAV

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

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.13.

Any number of lines can be specified, each one terminated with a slash /. The data should
be terminated with a slash /.

The following parameters should be specified:

1. slave group’s name or group mask defining a subset of groups with common prefix
(should end with an asterisk *). Groups are set via GRUPTREE (see 12.19.100) or
WELSPECS (see 12.19.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 group’s 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.19.263) and GRUPSLAV (see 12.19.264). Two options are pos-
sible. If in MASTER model we have GRUPMAST (see 12.19.263) for the group G in
the model SLAVE1, and in the model SLAVE1:

• the corresponding GRUPSLAV (see 12.19.264) is not specified, then the group
limits set in SLAVE1 continue to act on group G (option BOTH);
• the corresponding GRUPSLAV (see 12.19.264) is specified, then its parameters
3-9 define if the group limits (specified in SLAVE1) will affect the group G. In
particular if parameters 3-9 are not specified then GCONPROD (see 12.19.86),
GCONINJE (see 12.19.95) specified in SLAVE model for SLAVE group will be
ignored (option MAST).

4. filter flag for water and liquid production rate constraints. Meaning is similar to param-
eter 3;

5. filter flag for gas production rate constraints. Meaning is similar to parameter 3;

12.19.264. GRUPSLAV 1987

Keywords for formats tN, E1, E3 19.1

6. filter flag for reservoir fluid volume production rate constraints. Meaning is similar to
parameter 3;

7. filter flag for oil injection rate constraints. Meaning is similar to parameter 3;

8. filter flag for water injection rate constraints. Meaning is similar to parameter 3;

9. filter flag for gas injection rate constraints. Meaning is similar to parameter 3.
Default: parameters 3-9 are set to MAST.

Example
GRUPSLAV
W W1 /
G G1 /
/

12.19.264. GRUPSLAV 1988

Keywords for formats tN, E1, E3 19.1

12.19.265. CSKIN

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword updates skin factor values for specified perforations. Single data line should
contain the following parameters:
1. Well name, or well list name defined via WLIST (see 12.19.33), or well mask defining
a subset of wells with common prefix (should end with an asterisk *);
2. I coordinate of block with perforation;
Default: 0.
3. J coordinate of block with perforation;
Default: 0.
4. Upper K coordinate of block with perforation;
Default: coordinate of the topmost connection of the well.
5. Lower K coordinate of block with perforation;
Default: coordinate of the bottommost connection of the well.
6. Skin factor value. Can be specified by user via UDQ (see 12.19.165).
Default: 0.
Any number of data lines can be specified. Each of them should be terminated by the
symbol /. The data should be terminated with a slash /.
Example
CSKIN
'*' 4* -1 /
/
In this example the skin factor for all perforations of each well is set to -1.
Example
CSKIN
PROD1 2* 15 25 CUSKN /
/
In this example the skin factor for those perforations of the well PROD1 which are located
at the layers from K=15 to K=25 is set to the value of UDQ (see 12.19.165) named CUSKN
defined by the user earlier.

12.19.265. CSKIN 1989

Keywords for formats tN, E1, E3 19.1

12.19.266. WFOAM

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets foam concentration in injecting stream. It can be used only if foam
model option (see 2.18) is activated by the keyword FOAM (see 12.1.68). The following
parameters should be specified:

1. well name, or well list name defined via WLIST (see 12.19.33), or well mask defining
a subset of wells with common prefix (should end with an asterisk *);

2. foam concentration in injecting stream. 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.

One can set any number of data lines. Each data line should be terminated with the symbol
/. The data should be terminated with a slash /.
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.19.266. WFOAM 1990

Keywords for formats tN, E1, E3 19.1

12.19.267. WELLINCL

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets well trajectory in inclinometry notions, i.e. relatively to well head. This
keyword and two other (WELLDATA (see 12.19.268) and WELLBRANCH, see 12.19.269)
are set data to calculate bottom hole pressure via VFP correlations (see keyword VFPCORR,
see 12.19.71).
The following parameters should be specified:

1. well name (only well name is allowed; no well mask). It should be specified in format
NAME:BRANCH, where NAME is well name, BRANCH is branch number. Trajecto-
ries which name coincides with well name (and only such trajectories) are considered
belonging to this well and they rewrite trajectories with corresponding branch.

Then coordinates of well head and its trajectory relative to its head are specified. Well
head coordinates are specified firstly, then, in the following lines, trajectory coordinates. The
following parameters should be specified: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 ).

To set well in absolute coordinates use keyword WELLTRACK (see 12.19.9).

The data should be terminated with a slash /.
Example
WELLINCL 'TRAJ:1'
500 500 500 0
0 10 0 10
/
In the example coordinates of the first branch of well PROD1 are set.

12.19.267. WELLINCL 1991

Keywords for formats tN, E1, E3 19.1

12.19.268. WELLDATA

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets well properties along its trajectory. This keyword and two other
(WELLINCL (see 12.19.267) and WELLBRANCH, see 12.19.269) are set data to calculate
bottom hole pressure via VFP correlations (see keyword VFPCORR, see 12.19.71). The fol-
lowing parameters should be specified:

1. Trajectory name.

2. Branch number.
Default: 0.

3. MDU – upper depth of property action interval.

4. MDL – lower depth of property action interval.

5. Type of MDU/MDL values:

• MD – measured depth;
• TVD – true vertical depth;

Default: MD.

6. Well property and its value (if applicable):

• OPEN – open completion;

• SHUT – shut completion;
• COMPNUM – completion number;
• SKIN – skin factor value, dimensionless;
• PIMULT – transmissibility multiplier coefficient, dimensionless;
• CORRTYPE – correlation type. List of available ones is in the description of
keyword VFPCORR (see 12.19.71), 3-rd parameter;
• FLOWTYPE – flow area:
– TUBE – inside the wellbore;
– CASE – outside the wellbore;
– BOTH – inside and outside the wellbore.
• DIAMTUBEIN – inside wellbore diameter (METRIC: m, FIELD: f t );

12.19.268. WELLDATA 1992

Keywords for formats tN, E1, E3 19.1

• DIAMTUBEOUT – outside wellbore diameter (METRIC: m, FIELD: f t );

• DIAMINSU – insulation diameter (METRIC: m, FIELD: f t );
• DIAMCASEIN – internal casing diameter (METRIC: m, FIELD: f t );
• DIAMCASEOUT – external casing diameter (METRIC: m, FIELD: f t );
• DIAMHOLE – well diameter (METRIC: m, FIELD: f t );
• ROUGHTUBE – relative pipe roughness, dimensionless;
• ROUGHCASE – relative case roughness, dimensionless;
• EMTUBE – wellbore emissivity, dimensionless;
• EMINSU – insulation emissivity, dimensionless;
• EMCASE – case emissivity, dimensionless;
• EMFORM – formation emissivity, dimensionless;
• CONDTUBE – tube thermal conductivity, (METRIC: J/m/day/◦ C; FIELD:
Btu/ f t/day/◦ F);
• CONDINSU – insulation thermal conductivity, (METRIC: J/m/day/◦ C; FIELD:
Btu/ f t/day/◦ F);
• CONDCASE – case thermal conductivity, (METRIC: J/m/day/◦ C; FIELD:
Btu/ f t/day/◦ F);
• CONDCEME – cement thermal conductivity, (METRIC: J/m/day/◦ C; FIELD:
Btu/ f t/day/◦ F);
• CONDFORM – formation thermal conductivity, (METRIC: J/m/day/◦ C; FIELD:
Btu/ f t/day/◦ F).
• TEMPERATURE – temperature inside the well (METRIC: ◦ C; FIELD: ◦ F); in-
terpolated linearly between the locations where it is specified and extrapolated as
constant beyond the range where it is specified.

Default: property value: −1.

Any number of data lines can be specified. Each data line should be terminated with the
symbol /. The data should be terminated with a slash /.
Example
WELLDATA
'VW1' 0 100 500 MD CORRTYPE PA /
'VW1' 0 100 500 MD TEMPERATURE 95 /
/
In this example the well 'VW1', branch 0, at depths from 100 to 500 m (by MD) is
assigned the correlation of Petalaz & Aziz and temperature of 95 ◦ C.

12.19.268. WELLDATA 1993

Keywords for formats tN, E1, E3 19.1

12.19.269. WELLBRANCH

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets structure of well branches. This keyword and two other (WELLINCL
(see 12.19.267) and WELLDATA, see 12.19.268) are set data to calculate bottom hole pressure
via VFP correlations (see keyword VFPCORR, see 12.19.71). The following parameters should
be specified:
1. Well name. It should be single quoted. Masks are not allowed.
2. Trajectory name. It should be single quoted. If 3-rd parameter is absent, then this tra-
jectory is considered as main wellbore.
3. Branch name for trajectory which is specified by 2-nd parameter. This parameter may
be absent, in this case the other parameters are ignored.
4. Branch trajectory merge type:
• NO – trajectory and branch are no merged. In this case it is assumed that the mix-
ture is replaced to the point of main branch, which corresponds to the coordinate
specified by 5-th parameter;
• MOVE – branch replaced parallel to the point of main branch, which corresponds
to the coordinate specified by 5-th parameter;
• JOIN – interval between start of the branch and to the point of main branch, which
corresponds to the coordinate specified by 5-th parameter is put. This interval is
added to well trajectory.
Default: NO.
5. Point (MD notion) of the main trajectory to which branch will be connected.
Default: the nearest point to the start of the branch.
Note. All trajectories which are added to the well got name 'WELL NAME:BRANCH
NUMBER', where BRANCH NUMBER is the greatest branch number of the well, increased
by unit.
Example
WELLBRANCH
'VW2' 'VW2:0' 'TRAJ:1' MOVE /
'VW2' 'VW1:0' /
'VW2' 'VW2:2' 'TRAJ:1' JOIN /
/

12.19.269. WELLBRANCH 1994

Keywords for formats tN, E1, E3 19.1

In the example 2 trajectories are connected to well VW2. They will got names VW2:1
and VW2:3.

12.19.269. WELLBRANCH 1995

Keywords for formats tN, E1, E3 19.1

12.19.270. AIMPVI

Data x tN E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets pore volume value; all grid cells which pore volume is less than the
specified value are calculated implicitly. This keyword should be used with option AIM
(see 12.1.102).
The following parameters should be specified:

1. pore volume value (METRIC: rm3 ; FIELD: rb).

The data should be terminated with a slash /.

Example
AIMPVI
24 /

12.19.270. AIMPVI 1996

Keywords for formats tN, E1, E3 19.1

12.19.271. CALTRAC

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword sets tracer which concentration represents the calorific value of the gas (i.e.
measure of energy released when gas is burned). The tracer must be already defined as a gas
phase passive tracer via the keyword TRACER (see 12.7.10); it should be initialized in the
following units: METRIC – kJ/sm3 ; FIELD – Btu/Msc f . The following parameters should
be specified:

1. tracer name.

The data should be terminated with a slash /.

Example
CALTRAC
CLT /

12.19.271. CALTRAC 1997

Keywords for formats tN, E1, E3 19.1

12.19.272. LGRON

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword activates a local grid refinement. Other keywords to work with local grid
refinement are given in the section 5.5.8. LGRON can be used at any time during calculation
and inside any of ACTION (see 12.19.158) type keywords.
The keyword is followed by the parameter:

1. name of the local grid refinement. The name length should not exceed 8 characters. To
refer to several local grids use a local grid name root ending in an asterisk (*).

Data should be terminated by slash /.

See keyword LGROFF (see 12.19.273).

12.19.272. LGRON 1998

Keywords for formats tN, E1, E3 19.1

12.19.273. LGROFF

Data x tN x E1 E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword switches a local grid refinement off. Other keywords to work with local grid
refinement are given in the section 5.5.8. LGROFF can be used at any time during calculation
and inside any of ACTION (see 12.19.158) type keywords.

If the perforations defined by COMPDATMD are located in refined grid blocs and the local
grid is disabled by LGROFF (see 12.19.273) keyword, then the perforations will be automati-
cally transferred by the simulator to the blocks of coarse grid.

The keyword is followed by the parameter:

1. name of the local grid refinement. The name length should not exceed 8 characters. To
refer to several local grids use a local grid name root ending in an asterisk (*).

Data should be terminated by slash /.

See keyword LGRON (see 12.19.272).

12.19.273. LGROFF 1999

Keywords for formats tN, E1, E3 19.1

12.19.274. GMDISBC

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY x SCHEDULE

This keyword specifies displacement boundary conditions in case of fluid flow calcu-
lation taken into account rock stress specified with the keyword GEOMECH (see 12.1.99)
(option FE) in the RUNSPEC section. The geomechanical model is described in the section
2.29.1. GMDISBC allows displacement boundary conditions to be specified on all boundaries.
If a boundary condition is not specified on a boundary using this keyword or GMPSTBC
(see 12.19.275), then this boundary is considered rigid by default.
This keyword is followed by any number of records, terminated with a slash /. Each
record contains the following data:
1. A character string specifying the boundary to which the displacement boundary con-
dition is implemented. Boundary conditions can be specified on the following outer
faces:

• X+;
• X-;
• Y+;
• Y-;
• Z+ is the top boundary of the simulation;
• Z- is the bottom of the simulation;

2. An integer specifying the type of boundary condition on this face:

• 1 – A normal rock displacement is specified on the boundary denoted by parameter

1;
• 2 – A rock displacement with X, Y, Z components. A single X, Y, Z displace-
ment component is defined in parameter 3 and the component name can be set
in parameter 4. Displacements for different components should be set on different
lines;

Default: 2.

3. The value of normal rock displacement on the boundary if the boundary condition type
specified by parameter 2 is set 1, or value of rock displacement with X or Y or Z
component if the boundary condition type specified by parameter 2 is set 2 (METRIC:
m, FIELD: f t ).
Default: 0.

12.19.274. GMDISBC 2000

Keywords for formats tN, E1, E3 19.1

4. A character specifying the component of displacement (X, Y or Z) if the boundary

condition type specified by parameter 2 is set 2.
Default: None.

5. First block starting with the boundary condition is applied in the X direction.
Default: 1 (face X-).

6. Last block ending with the boundary condition is applied in the X direction.
Default: NX (face X+).

7. First block starting with the boundary condition is applied in the Y direction.
Default: 1 (face Y-).

8. Last block ending with the boundary condition is applied in the Y direction.
Default: NY (face Y+).

9. First block starting with the boundary condition is applied in the Z direction.
Default: 1 (face Z-).

10. Last block ending with the boundary condition is applied in the Z direction.
Default: NZ (face Z+).

The record should be terminated by a symbol / located on the new empty line. The records
can be terminated early with a symbol /, then unspecified parameters are given by default
values.
Defaults can be specified by a symbol *. N number of consecutive parameters are specified
by default using the expression: N*.
In this example rock displacement equal to 0.1 with X, Y, Z components is implemented
on the boundary Z-.
Example
GMDISBC
’Z-’ 2 0.1 X /
’Z-’ 2 0.1 Y /
’Z-’ 2 0.1 Z /
/

12.19.274. GMDISBC 2001

Keywords for formats tN, E1, E3 19.1

12.19.275. GMPSTBC

Data x tN x E1 x E3 IM GE ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS x SOLUTION SUMMARY x SCHEDULE

This keyword specifies principal stress boundary conditions if rock stress is calculated
using finite volume or finite element. The geomechanical model is described in the section
2.29.1. It can be used if keyword GEOMECH (see 12.1.99) (option FE) is specified in the
section RUNSPEC.
GMPSTBC specifies the full set of three principal stress vectors on all boundaries. This
data set suffices to fully define the stress tensor at the chosen boundary. Moreover, displace-
ments can be specified using the GMDISBC (see 12.19.274) keyword.
This keyword is followed by any number of records, terminated with a slash /. Each
record contains the following data:

1. A character string specifying the boundary to which the principal stress boundary con-
dition is implemented. Boundary conditions can be specified on the following outer
faces:

• X+;
• X-;
• Y+;
• Y-;
• Z+ is the top boundary of the simulation;
• Z- is the bottom of the simulation;

2. X component of the first principal stress vector (METRIC: bars, FIELD: psi);

3. Y component of the first principal stress vector (METRIC: bars, FIELD: psi);

4. Z component of the first principal stress vector (METRIC: bars, FIELD: psi);

5. X component of the second principal stress vector (METRIC: bars, FIELD: psi);

6. Y component of the second principal stress vector (METRIC: bars, FIELD: psi);

7. Z component of the second principal stress vector (METRIC: bars, FIELD: psi);

8. X component of the third principal stress vector (METRIC: bars, FIELD: psi);

9. Y component of the third principal stress vector (METRIC: bars, FIELD: psi);

12.19.275. GMPSTBC 2002

Keywords for formats tN, E1, E3 19.1

10. Z component of the third principal stress vector (METRIC: bars, FIELD: psi).
Default: 0 for all components.

The record should be terminated by a symbol / located on the new empty line. The records
can be terminated early with a symbol /, then unspecified parameters are given by default
values.
Defaults can be specified by a symbol *. N number of consecutive parameters are specified
by default using the expression: N*.
In this example X component of the first principal stress vector, Y component of the second
vector and Z component of the third vector are specified as boundary condition on outer edge
X+.
Example
GMPSTBC
X+ 40 0 0 0 40 0 0 0 40 /
/

12.19.275. GMPSTBC 2003

Keywords for formats tN, IM, ST, GE 19.1

12.19.276. WLOGCALC

Data x tN x E1 x E3 x IM x GE x ST x MO
format

! This keyword is generated by tNavigator automatically and is not intended

for manual use in models.
WLOGCALC is written to the user files of the model automatically when the user assigns
any well log in the simulator GUI (see section 9.10.2 of tNavigator User Guide).
The following parameters should be specified:

1. Name of the well;

2. Type of the measurement:

• PRES for RFT well log;

• OIL for PLT Oil log;
• WATER for PLT Water log;
• LIQ for PLT Liquid log;
• GAS for PLT Gas log;
• NONE (default) for non-assigned log;

3. Conditions of measurement: RC (reservoir conditions) or SC (surface conditions);

4. Flag indicating whether the log contains accumulated (YES) or instantaneous (NO) val-
ues.

Example
WLOGCALC
'WELL10_PLT' OIL RC YES /
/

In this example a well log called 'WELL10_PLT' is declared a PLT Oil accumulated log
measured in reservoir conditions.

12.19.276. WLOGCALC 2004

Keywords for formats tN, IM, ST, GE 19.1

13. Keywords for formats tN, IM, ST, GE

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:

• tN;

• IM;

• ST;

• GE.

In addition: In formats that are used also in other simulators, additionally special tNavi-
gator keywords can be used that are not implemented in other simulators (format extension).
The list of all special keywords is available in the index – 17. Also for some standard key-
words additional tNavigator options can be used that are not implemented in other simulators
(format extension). All possible options are described in keywords descriptions.

For convenience keyword are grouped in several sections similar to IM, ST, GE sections.

• Input – 13.2. Input/Output Control;

• Reservoir – 13.3. Reservoir description;

• Other – 13.4. Other Reservoir Properties;

• Component – 13.5. Component properties;

• Rockfluid – 13.6. Rock-Fluid data;

• Initial – 13.7. Initial conditions;

• Numerical – 13.8. Numerical methods control;

• Well – 13.9. Well and recurrent data.

13. Keywords for formats tN, IM, ST, GE 2005

Keywords for formats tN, IM, ST, GE 19.1

13.1. Data entry system

13.1.1. MATRIX

Data x tN E1 E3 x IM x GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

This keyword is a modifier used after keywords that set grid properties. The keyword is
used in dual porosity runs (DUALPOR, see 13.3.6) and specifies that the properties correspond
to matrix blocks.
There is also FRACTURE (see 13.1.2) modifier to specify properties of fracture blocks. If
none of these modifiers is present, then MATRIX is assumed.
Instead of numeric values, more modifier keywords may follow in order to further narrow
down the set of affected blocks.
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. Data entry system 2006

Keywords for formats tN, IM, ST, GE 19.1

13.1.2. FRACTURE

Data x tN E1 E3 x IM x GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

This keyword is a modifier used after keywords that set grid properties. The keyword is
used in dual porosity run (DUALPOR, see 13.3.6) and specifies that the properties correspond
to fracture blocks.
There is also MATRIX (see 13.1.1) keyword to specify properties of matrix blocks. If none
of these modifiers is present, then MATRIX is assumed.
Instead of numeric values, more modifier keywords may follow in order to further narrow
down the set of affected blocks.
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 2007

Keywords for formats tN, IM, ST, GE 19.1

13.1.3. CON

Data x tN E1 E3 x IM GE x ST MO
format
This keyword is a modifier used after a property keyword if constant value array is entered.
After CON one should specify the value (which is then assigned 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 2008

Keywords for formats tN, IM, ST, GE 19.1

13.1.4. IVAR / JVAR / KVAR

Data x tN E1 E3 x IM x GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

These keywords are modifiers used after grid property keywords to specify common con-
stant values for all blocks of a 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 following parameters should be specified:

• 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.46). 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 2009

Keywords for formats tN, IM, ST, GE 19.1

13.1.5. IJK

Data x tN E1 E3 x IM x GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

This keyword is a modifier used after grid property keywords to specify common constant
value for all blocks within the 3D box defined by its bounds in X, Y and Z directions.
The following parameters should be specified:

• Colon-separated I bounding values for the box;

• Colon-separated J bounding values for the box;

• Colon-separated K bounding values for the box;

• Value assigned to blocks within the box.

i If the bounding values in any direction coincide, then the value may be spec-
ified only once with colon omitted.

Example
POR IJK 1:10 11:20 3:6 0.15
In the example the porosity is set to 0.15 for all blocks inside the box that spans from 1 to
10 by I, from 11 to 20 by J, and from 3 to 6 by K.

13.1.5. IJK 2010

Keywords for formats tN, IM, ST, GE 19.1

13.1.6. BG

Data x tN E1 E3 x IM x GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

This keyword is a modifier used after grid property keywords to specify values to a
group of blocks defined beforehand. The latter may be done, for example, using the keyword
PLNRFRAC (see 13.3.45).
The following parameters should be specified:

• Input modifier, may be one of:

– CON (see 13.1.3);

– EQUALSI (see 13.1.8);
– FZ (see 13.1.7);
– NFZ (see 13.1.7);

• Values assigned to blocks.

13.1.6. BG 2011
Keywords for formats tN, IM, ST, GE 19.1

13.1.7. FZ / NFZ

Data x tN E1 E3 x IM x GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

These keyword are modifiers used after grid property keywords to specify a common value
for all blocks inside (FZ) or outside of (NFZ) a local grid refinement (LGR).
The following parameters should be specified:

• Value assigned to blocks inside an LGR (FZ) or outside of it (NFZ).

Example
POR *MATRIX *BG 'Fracture1' *FZ 0.15
POR *MATRIX *BG 'Fracture1' *NFZ 0.08

In this example the porosity for matrix blocks within the group 'Fracture1' is set to 0.15
inside an LGR and to 0.08 outside of it.

13.1.7. FZ / NFZ 2012

Keywords for formats tN, IM, ST, GE 19.1

13.1.8. EQUALSI

Data x tN E1 E3 x IM x GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

This keyword is a modifier used after grid property keywords for direction-dependent
properties. It specifies the property values in the directions J and K via its property in the
direction I, probably multiplied by a constant coefficient.
The following parameters should be specified:

• (Optional) Multiplication sign followed by a constant multiplier.

Example
PERMI *CON 1.0
PERMJ *EQUALSI * 1.0
PERMK *EQUALSI * 0.1

In this example the permeability along I is specified as a constant, permeability along J is

specified as equal to it, and the value along K is set to the same value times 0.1.

13.1.8. EQUALSI 2013

Keywords for formats tN, IM, ST, GE 19.1

13.2. Input/Output Control

13.2.1. TITLE1 / TITLE2 / TITLE3

Data x tN E1 E3 x IM GE x ST MO
format
x Input Reservoir Other Component
Section
Rockfluid Initial Numerical Well

The keyword is used to specify model name (this name can consist of letters and numbers).
It has an E1/E3-compatible analogue TITLE (see 12.1.2).
Example
TITLE1 'Model number 1'

This example sets the model name Model number 1.

13.2. Input/Output Control 2014

Keywords for formats tN, IM, ST, GE 19.1

13.2.2. INUNIT

Data x tN E1 E3 x IM GE x ST MO
format
x Input Reservoir Other Component
Section
Rockfluid Initial Numerical Well

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 2015

Keywords for formats tN, IM, ST, GE 19.1

13.2.3. RESTART

Data x tN E1 E3 x IM x GE x ST MO
format
x Input Reservoir Other Component
Section
Rockfluid Initial Numerical Well

This keyword initiates a restart run from the last calculated timestep.

i To set Restart from the specific timestep use the keyword RESDATE
(see 13.2.4).

!
Restart is available for the models calculated in tNavigator only, i.e., the base
model must be calculated in tNavigator. Restart from calculation results from
other simulators is not possible.
The name of the input file is specified by the keyword FILENAMES (see 13.2.5).

This keyword has an E1/E3 compatible analogue RESTART (see 12.16.3).

Example
*RESTART

13.2.3. RESTART 2016

Keywords for formats tN, IM, ST, GE 19.1

13.2.4. RESDATE

Data x tN E1 E3 x IM x GE x ST MO
format
x Input Reservoir Other Component
Section
Rockfluid Initial Numerical Well

This keyword initiates a restart run from a particular date.

The data should be entered in the following format:

RESDATE date

• date – simulation restart date written in the same format as DATE (see 13.9.3)
(YYYY MM DD).

!
Restart is available for the models calculated in tNavigator only, i.e., the base
model must be calculated in tNavigator. Restart from calculation results from
other simulators is not possible.
Restart can be performed only from the time step at which grid properties and graphs
have been recorded. If they are not available for the specified date, then the run is restarted
from the nearest possible earlier date.

The name of the input file is specified by the keyword FILENAMES (see 13.2.5).

The keyword is analog of RESTARTDATE (see 12.16.4), which is used in tNavigator.

Example
*RESDATE 2009 02 01
This example initiates a restart from 01.02.2009.

13.2.4. RESDATE 2017

Keywords for formats tN, IM, ST, GE 19.1

13.2.5. FILENAMES

Data x tN E1 E3 x IM x GE x ST MO
format
x Input Reservoir Other Component
Section
Rockfluid Initial Numerical Well

This keyword specifies file names of various input and output files. It may contain one or
more of the following suboptions, each followed by a filename:

• *OUTPUT IGNORED, this is an IM/ST/GE compatibility field.

• *INDEX-OUT IGNORED, this is an IM/ST/GE compatibility field.

• *MAIN-RESULTS-OUT IGNORED, this is an IM/ST/GE compatibility field.

• *REWIND-OUT IGNORED, this is an IM/ST/GE compatibility field.

• *INDEX-IN Indicates the name of the index file to be used for restart runs (see RESTART,
see 13.2.3).

• *MAIN-RESULTS-IN IGNORED, this is an IM/ST/GE compatibility field.

• *REWIND-IN IGNORED, this is an IM/ST/GE compatibility field.

Example
*FILENAMES *INDEX-IN 'mxdrm001.rstr.irf'

This example specifies that the data for restart will be read from the file mxdrm001.rstr.irf.

13.2.5. FILENAMES 2018

Keywords for formats tN, IM, ST, GE 19.1

13.2.6. INCLUDE

Data x tN E1 E3 x IM x GE x ST MO
format
x Input x Reservoir x Other x Component
Section
x Rockfluid x Initial x Numerical x Well

This keyword indicates the input of external file. In this case, the reading of the current
file will be stopped and the included file’s data will be read. The included file may, in turn,
contain *INCLUDE keywords.

The data should be entered in the following format:

*INCLUDE f ilepath

• f ilepath – the relative path name to the include file.

Only one file may be specified after *INCLUDE keyword. The Include files should be in
text format.

Example
*INCLUDE 'INCLUDES\schedule.txt'

13.2.6. INCLUDE 2019

Keywords for formats tN, IM, ST, GE 19.1

13.3. Reservoir description

13.3.1. GRID

Data x tN E1 E3 x IM GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

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. Reservoir description 2020

Keywords for formats tN, IM, ST, GE 19.1

13.3.2. DI / DJ / DK

Data x tN E1 E3 x IM GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

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 2021
Keywords for formats tN, IM, ST, GE 19.1

13.3.3. ZCORN

Data x tN E1 E3 x IM x GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

The keyword enables the depths of each corner of each grid block (8 corners) to be
separately specified.
It has an E1/E3-compatible analogue ZCORN (see 12.2.9). Data input is identical with this
keyword.

13.3.3. ZCORN 2022

Keywords for formats tN, IM, ST, GE 19.1

13.3.4. COORD

Data x tN E1 E3 x IM x GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

The keyword is used to specify coordinate lines in Z-direction.

It has an E1/E3-compatible analogue COORD (see 12.2.8). Data input is identical with this
keyword.

13.3.4. COORD 2023

Keywords for formats tN, IM, ST, GE 19.1

13.3.5. BLOCKGROUP

Data x tN E1 E3 x IM x GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

This keyword defines the blockgroups that can be later referenced by BG (see 13.1.6)
array modifier.

The data should be entered in the following format:

*BLOCKGROUP bg_name bg_de f inition f lag

Where:
1. bg_name – name of the block group;
2. bg_de f inition – specification of the blocks array. The blocks array definition is de-
scribed described in Data entry system section.
3. f lag – flag defining whether the specified blocks array should be assigned to the block
group or excluded from it. There are two possible values for this flag:
• 1 – the blocks array will be assigned to the block group;
• 0 – the blocks array will not be assigned to the block group. If these blocks were
already part of the group, they will be excluded from it.

Example
*BLOCKGROUP 'BlockGroup-1' *IJK 1:10 1:10 1:10 1:5

*BLOCKGROUP 'BlockGroup-2' *BG 'BlockGroup-1' 1

*IJK 1:10 1:10 2 0
*IJK 1:10 1:10 4 0

In this example:
1. The group ’BlockGroup-1’ is defined for a blocks array within the box:
• In I direction from I = 1 to I = 10
• In J direction from J = 1 to J = 10
• In K direction from K = 1 to K = 5
2. The group ’BlockGroup-2’ is defined as a copy of the group ’BlockGroup-1’.
3. The blocks with indexes K = 2 and K = 4 are excluded from ’BlockGroup-2’.

13.3.5. BLOCKGROUP 2024

Keywords for formats tN, IM, ST, GE 19.1

13.3.6. DUALPOR

Data x tN E1 E3 x IM x GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

The keyword sets dual porosity run. One should specify matrix block properties and frac-
ture block properties using keywords MATRIX (see 13.1.1) and FRACTURE (see 13.1.2).
It has an E1/E3-compatible analogue DUALPORO (see 12.1.83).
Example
DUALPOR

13.3.6. DUALPOR 2025

Keywords for formats tN, IM, ST, GE 19.1

13.3.7. SHAPE

Data x tN E1 E3 x IM x GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

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 transmis-

sibility:
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.8), MV – matrix volume.

• WR (Warren and Root) Matrix-fracture flow in one block is proportional to transmissi-

bility:
1 1 1
4 ∗ k ∗ ( 2 + 2 + 2 ) ∗ MV
lx ly lz
Current version of Navigator support only GK type.
It has an E1/E3-compatible analogue VISCD (see 12.1.89). VISCD sets that the viscous
displacement option will be used (matrix-fracture flows), but doesn’t specify the type of
shape-factor. E1/E3 compatible analogue – sigma-factor (keywords SIGMA (see 12.2.72),
LTOSIGMA, see 12.2.74).
Example
SHAPE GK

13.3.7. SHAPE 2026

Keywords for formats tN, IM, ST, GE 19.1

13.3.8. DIFRAC / DJFRAC / DKFRAC

Data x tN E1 E3 x IM x GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

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.6) is enabled. Matrix-fracture
flows are calculated using this keyword (one can observe formula in the description of the
keyword SHAPE, see 13.3.7).

It has an E1/E3-compatible analogue LX / LY / LZ (see 12.2.69).

13.3.8. DIFRAC / DJFRAC / DKFRAC 2027

Keywords for formats tN, IM, ST, GE 19.1

13.3.9. NULL

Data x tN E1 E3 x IM x GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

The keyword sets if block is active or inactive (doesn’t participate in the run).

• 0 – inactive block,

• 1 – active block.

Default: all blocks are active.

It has an E1/E3-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.9. NULL 2028

Keywords for formats tN, IM, ST, GE 19.1

13.3.10. POR

Data x tN E1 E3 x IM x GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

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 models that can be used in tNavigator (Linear Elastic, Nonlinear Elastic, Dilation-
Recompaction) are described in the section 4.24.

It has an E1/E3-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.10. POR 2029

Keywords for formats tN, IM, ST, GE 19.1

13.3.11. PERMI / PERMJ / PERMK

Data x tN E1 E3 x IM x GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

These keywords specify absolute permeabilities in X (PERMI), Y (PERMJ), Z (PERMK)

directions. In dual porosity run (DUALPOR, see 13.3.6) one should enter permeabilities for
matrix blocks (MATRIX, see 13.1.1) and fracture blocks (FRACTURE, see 13.1.2). MATRIX
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.

Note that the permeabilities may be changed during the calculation by using these key-
words in Well section.
These keywords have E1/E3-compatible analogues 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.11. PERMI / PERMJ / PERMK 2030

Keywords for formats tN, IM, ST, GE 19.1

13.3.12. NETGROSS

Data x tN E1 E3 x IM x GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

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 E1/E3-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.12. NETGROSS 2031

Keywords for formats tN, IM, ST, GE 19.1

13.3.13. PINCHOUTARRAY

Data x tN E1 E3 x IM GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

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 E1/E3-compatible analogues PINCH (see 12.2.58), PINCHREG

(see 12.2.61), PINCHNUM (see 12.2.62).
Example
PINCHOUTARRAY CON 1

This example sets that no one block is pinched out.

13.3.13. PINCHOUTARRAY 2032

Keywords for formats tN, IM, ST, GE 19.1

13.3.14. VOLMOD

Data x tN E1 E3 IM GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

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 E1/E3-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.14. VOLMOD 2033

Keywords for formats tN, IM, ST, GE 19.1

13.3.15. NETPAY

Data x tN E1 E3 x IM GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

The keyword defines net thickness of grid blocks. Net thickness values are used in poros-
ity calculations. The models that can be used in tNavigator (Linear Elastic, Nonlinear Elastic,
Dilation-Recompaction) are described in the section 4.24.

This keyword is fully analogous to the keyword DZNET (see 12.2.26) which is used by
E1/E3. More details are in DZNET (see 12.2.26) description.

13.3.15. NETPAY 2034

Keywords for formats tN, IM, ST, GE 19.1

13.3.16. AQLEAK

Data x tN E1 E3 x IM GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

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;

Default: OFF.
Example
AQLEAK ON

13.3.16. AQLEAK 2035

Keywords for formats tN, IM, ST, GE 19.1

13.3.17. AQMETHOD

Data x tN E1 E3 x IM x GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

The keyword specifies the aquifer type in a model.

• CARTER-TRACY – Carter-Tracy’s aquifer;

• FETKOVITCH – Fetkovitch’s aquifer.

• SEMI-ANALYTICAL – semi-analytical aquifer.

Default: CARTER-TRACY.

The keyword has an E1/E3-compatible analogues AQUCT (see 12.17.9), AQUFET

(see 12.17.4).

13.3.17. AQMETHOD 2036

Keywords for formats tN, IM, ST, GE 19.1

13.3.18. AQVISC

Data x tN E1 E3 x IM GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

The keyword sets aquifer water viscosity. It can be used only with SEMI-ANALYTICAL
aquifer type (see AQMETHOD, see 13.3.17).
The following parameters should be specified:

1. aquifer water viscosity (cp).

Default: if this keyword is omitted, then calculated water viscosity is taken.

Example
AQVISC 0.61

13.3.18. AQVISC 2037

Keywords for formats tN, IM, ST, GE 19.1

13.3.19. AQPROP

Data x tN E1 E3 x IM GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

The keyword specifies aquifer’s properties. The following parameters should be specified:

1. thickness (SI: m, FIELD: f t );

Default: For this parameter default value is supported according to the logic of ST
syntax..

2. porosity;
Default: average porosity of reservoir (For this parameter default value is supported
according to the logic of ST syntax.).

3. permeability (SI: mD, FIELD: mD);

Default: average permeability of reservoir in aquifer flow direction (For this parameter
default value is supported according to the logic of ST syntax.).

4. radius (SI: m, FIELD: f t );

Default: For this parameter default value is supported according to the logic of ST
syntax..

5. angle of influence (expressed by a fraction (a ratio to 360◦ )).

Default: For this parameter default value is supported according to the logic of ST
syntax..

Radius and angle of influence should be specified for Carter-Tracy and Fetkovitch aquifer.
For SEMI-ANALYTICAL model one should enter 0 value.

The keyword has an E1/E3-compatible analogues AQUCT (see 12.17.9), AQUNUM

(see 12.17.13).
Example
INUNIT FIELD
...
AQPROP
100 0.28 70 15500 0.2
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.19. AQPROP 2038

Keywords for formats tN, IM, ST, GE 19.1

13.3.20. AQUIFER

Data x tN E1 E3 x IM x GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

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 E1/E3-compatible analogue AQUANCON (see 12.17.11).

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.20. AQUIFER 2039

Keywords for formats tN, IM, ST, GE 19.1

13.3.21. AQFUNC

Data x tN E1 E3 x IM GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

This keyword is a full analog of the keyword AQUTAB (see 12.17.10).

13.3.21. AQFUNC 2040

Keywords for formats tN, IM, ST, GE 19.1

13.3.22. DUALPERM

Data x tN E1 E3 x IM GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

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 E1/E3-compatible analogue DUALPERM (see 12.1.84).

13.3.22. DUALPERM 2041

Keywords for formats tN, IM, ST, GE 19.1

13.3.23. CORNERS

Data x tN E1 E3 x IM x GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

The keyword is an analog of the keyword CORNERS (see 12.2.123) which is used by
tNavigator.
The keyword sets coordinates of block grid corners (SI: 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 corners. 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.23. CORNERS 2042

Keywords for formats tN, IM, ST, GE 19.1

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 this example a grid of size 2 × 2 × 1 is specified. Length of a block along x and y

directions is equal to 50 m, along z direction it is equal to 2 m. Depth of the top layer is 500
m, that’s why z-coordinates of the top layer are set to 500.

13.3.23. CORNERS 2043

Keywords for formats tN, IM, ST, GE 19.1

13.3.24. CTYPE

Data x tN E1 E3 x IM x GE ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

This keyword sets rock type number for each grid block.

The data should be entered in following format:

*CTYPE array rock_num

Where:

1. array – specification of the blocks array. The blocks array definition is described in
Data entry system section.

2. rock_num – rock type number corresponding to the specified blocks array.

Compaction properties of each rock type can be set via CROCKTYPE (see 13.3.25) and
its associated keywords (CROCKTAB (see 13.3.28), CROCKTABH (see 13.3.29), CCPOR
(see 13.3.27), CPRPOR, see 13.3.26).

This keyword has E1/E3-compatible analogs: ROCKNUM (see 12.4.14) and ROCKOPTS
(see 12.5.31).
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 2044

Keywords for formats tN, IM, ST, GE 19.1

13.3.25. CROCKTYPE

Data x tN E1 E3 x IM x GE ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

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.28).
The following parameters should be specified:

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.25. CROCKTYPE 2045

Keywords for formats tN, IM, ST, GE 19.1

13.3.26. CPRPOR

Data x tN E1 E3 x IM x GE ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

This keyword sets the reference pressure pre f , which is used in porosity calculations (SI:
kPa, FIELD: psi).

The models that can be used in tNavigator (Linear Elastic, Nonlinear Elastic, Dilation-
Recompaction) are described in the section 4.24.

This keyword is the equivalent the keyword PRPOR (see 13.4.4), can be specified sepa-
rately for each rock type defined by CROCKTYPE (see 13.3.25) keyword.

This keyword can be used simultaneously with CROCKTAB (see 13.3.28) in different
CROCKTYPE (see 13.3.25) regions.
Example
*CROCKTYPE 1
*CPRPOR 16450
*CCPOR 1.4e-6

*CROCKTYPE 2
*CPRPOR 13750
*CCPOR 1.1e-6

This example sets different reference pressures and rock compressibility coefficients for
two different *CROCKTYPE regions.
Example
*CROCKTYPE 1
*CPRPOR 15000
*CCPOR 1.2e-6

*CROCKTYPE 2
*CROCKTAB
2200 0.831 0.105 0.105
6500 0.972 0.105 0.105
12000 0.994 0.11 0.11

In this example different compaction models are used for two different *CROCKTYPE
regions.

13.3.26. CPRPOR 2046

Keywords for formats tN, IM, ST, GE 19.1

13.3.27. CCPOR

Data x tN E1 E3 x IM x GE ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

The keyword sets the rock compressibility coefficient c p , which is used in porosity calcu-
1 1
lations (SI: , FIELD: ).
kPa psi
The models that can be used in tNavigator (Linear Elastic, Nonlinear Elastic, Dilation-
Recompaction) are described in the section 4.24.

This keyword is the equivalent the keyword CPOR (see 13.4.5), can be specified sepa-
rately for each rock type defined by CROCKTYPE (see 13.3.25) keyword.

This keyword can be used simultaneously with CROCKTAB (see 13.3.28) in different
CROCKTYPE (see 13.3.25) regions.
Example
*CROCKTYPE 1
*CPRPOR 16450
*CCPOR 1.4e-6

*CROCKTYPE 2
*CPRPOR 13750
*CCPOR 1.1e-6

This example sets different reference pressures and rock compressibility coefficients for
two different CROCKTYPE (see 13.3.25) regions.
Example
*CROCKTYPE 1
*CPRPOR 15000
*CCPOR 1.2e-6

*CROCKTYPE 2
*CROCKTAB
2200 0.831 0.105 0.105
6500 0.972 0.105 0.105
12000 0.994 0.11 0.11

In this example different compaction models are used for two different CROCKTYPE
(see 13.3.25) regions.

13.3.27. CCPOR 2047

Keywords for formats tN, IM, ST, GE 19.1

13.3.28. CROCKTAB

Data x tN E1 E3 x IM x GE ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

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;

Default: 1.

4. vertical transmissibility multiplier.

Default: horizontal transmissibility multiplier.

This keyword can be used simultaneously with CCPOR (see 13.3.27) and CPRPOR
(see 13.3.26) in different regions.
The keyword has an E1/E3-compatible analogue ROCKTAB (see 12.5.21).
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 speci-
fied for the 1st type of rock.

13.3.28. CROCKTAB 2048

Keywords for formats tN, IM, ST, GE 19.1

13.3.29. CROCKTABH

Data x tN E1 E3 x IM x GE ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

This keyword specifies tables defining hysteresis path for modeling hysteretic rock com-
paction.
The keyword CROCKTAB (see 13.3.28) allows to specify non-linear relationships be-
tween porosity, permeability, transmissibility or matrix-fracture transfer term multipliers and
pressures the rock behavior is reversible, i.e. the relationship between multipliers and pressures
varies along a deflation curve (see picture 56 a) defined by the single table in the keyword
CROCKTAB (see 13.3.28) for this region. The keyword CROCKTABH allows to simulate hys-
teretic rock compaction effects by specifying relationships between porosity, permeability etc.
multipliers and pressure for elastic (hysteresis) curves.
When pressure decreases a variation of porosity multiplier with pressure is defined by
the deflation (non-hysteresis) curve specified with a table given in the keyword CROCKTAB
(see 13.3.28). When pressure starts to increase the rebound pressure is set. the multiplier value
varies with pressure increase along an elastic curve specified with the keyword CROCKTABH.
If a deflation curve given by CROCKTAB (see 13.3.28) is stringly non-linear it is required
to specify sufficient number of elastic curves using CROCKTABH in oder to avoid a porosity
discontinuity at rebound pressure. This problem can be totally eliminated by specifying elastic
curves for each pressure values given in the table of the keyword CROCKTAB (see 13.3.28).
The keyword is followed by an option indicating a property for which tables (multipliers
vs pressure) will be created:

• PERMMULT – permeability multipliers;

• TRANMULT – transmiability multipliers.

If the keyword CROCKTABH is used to create a table for permeability multipliers the
following parameters should be indicated:

1. pressure (SI: kPa, FIELD: psia).

Minimal pressure value is 101 kPa (14.7 psia). Pressure values should increase;

2. porosity multipliers.
Multipliers values should decrease. A porosity multiplier is a nondimensional value
equal to V /Vi , where:

• V is the pore volume at above pressure;

• Vi is the initial pore volume. Porosity (POR, see 13.3.10) is indicated at initial
pressure.

13.3.29. CROCKTABH 2049

Keywords for formats tN, IM, ST, GE 19.1

3. permeability multiplier in I–direction.

A multiplier is nondimensional value equal to permI/permIi , where

• permI is the permeability at above pressure;

• permIi is the permeability (PERMI, see 13.3.11) at initial pressure.

4. permeability multiplier in J–direction.

It is specified in the similar way as a permeability multiplier in I–direction;

5. permeability multiplier in K–direction;

It is specified in the similar way as a permeability multiplier in I–direction;

6. transmissibility multiplier (dimensionless) for fluid flow between matrix and fracture at
above pressure press.
It is an optional multiplier.
Default: 1.

If the keyword CROCKTABH is used for transmissibility multipliers then transmissibility

multipliers should be specified insted permeability multipliers in I, J and K directions. These
multipliers and corresponding transmissibility multipliers specified with keywords TRANSI
(see 13.3.31), TRANSJ (see 13.3.31) and TRANSK (see 13.3.31) are applied accumulatively.
If neither option PERMMULT nor option TRANMULT is selected then the following
parameters should be specified:

1. pressure (SI: kPa, FIELD: psia).

Minimal pressure value is 101 kPa (14.7 psia). Pressure values should increase;

2. porosity multipliers.
Multipliers values should decrease.

3. horizontal permeability multiplier (dimensionless);

Default: 1.

4. vertical permeability multiplier (dimensionless).

Default: horizontal permeability multiplier.

In the keyword CROCKTABH at least two tables (elastic curves) should be specified.
CROCKTABH should be specified after the keyword CROCKTYPE (see 13.3.25) along
with the keyword CROCKTAB (see 13.3.28). A format of table specified with CROCKTABH
should be of the same format as table in CROCKTAB (see 13.3.28) for the same rock type
region.
If the option PERMMULT or TRANMULT is selected each table should contain at least
5 columns. If the multiplier is not required its values can be set equal to 1. 6-th column is
optional and specifies the transmissibility multipliers for matrix-fracture flow. If multipliers in
6-th column is not specified then defaulted values will be used.

13.3.29. CROCKTABH 2050

Keywords for formats tN, IM, ST, GE 19.1

First two columns (pressure and porosity multipliers) in each table are always specified.
Permeability multipliers (3-rd and 4-th columns) are optional. If the option TRANMULT is
selected transmissibility multipliers in I-, J-, or K-directions for an inter–block flow connection
are calculated as the arithmetic average of the transmissibility multipliers from neighboring
blocks. For the flow through a matrix–fracture connection, the transmissibility multiplier is
the arithmetic average of multipliers in matrix and fracture blocks.
Pressure and multipliers in the first row (begining of elastic curve) of each table specified
with CROCKTABH should be located on the deflation curve, i.e. coincide with corresponding
values form table specified with CROCKTAB (see 13.3.28).
The keyword CCPOR (see 13.3.27) should not be specified along with the keyword
CROCKTAB (see 13.3.28) in the same region of rock type, otherwise it will be ignored.
If an analytical aquifer model is used the keyword CPOR (see 13.4.5) can be required. If the
current pressure is outside the pressure range given in the table of the keyword CROCKTAB
(see 13.3.28) then to calculate corresponding multipliers the linear interpolation is used.
To interpolate data of hysteresis curves tables the rebound pressure (the begining of elastic
curve) should fell between pressure of first row of first table and pressure of first row of last
table. If the rebound pressure is less than pressure (of first row) of first table or larger than the
pressure (of first row) of last table then the rock behavior is described by the deflation curve
and hysteresis does not occur.
The keyword has an E1/E3-compatible analogue ROCKTABH (see 12.5.22).
In this example in the 1-st region of rock type the relationship between multipliers and
pressure is specified with keyword CROCKTAB (see 13.3.28). To simulate a rock hysteresis
the keyword CROCKTABH specifies two tables (elastic curves). Notice that the first row of the
first and second tables coincide with corresponding rows (rebound pressures on the deflation
curve) of the table specified with CROCKTAB (see 13.3.28).

13.3.29. CROCKTABH 2051

Keywords for formats tN, IM, ST, GE 19.1

Example
CROCKTYPE 1
CROCKTAB
1000 0.957269479 0.00984098
1500 0.959987188 0.013283933
2000 0.962712614 0.017931434
2500 0.965445776 0.024204905
3000 0.968186698 0.032673204
3500 0.970935402 0.044104212
4000 0.97369191 0.059534458
4500 0.976456243 0.080363113
5000 0.979228424 0.108478856
5500 0.982008475 0.146431139
6000 0.984796419 0.197661363
6500 0.987592278 0.266814932
7000 0.990396075 0.360162486
7500 0.993207832 0.486168504
8000 0.996027571 0.656258837
8500 0.998855316 0.885856771
9000 1 1

CROCKTABH
7000 0.990396075 0.36
7500 0.992 0.46
8000 0.994 0.588
8500 0.996 0.7
9000 0.998 0.8

CROCKTABH
8000 0.996027571 0.656258837
8500 0.9974 0.8
9000 0.999 0.97

13.3.29. CROCKTABH 2052

Keywords for formats tN, IM, ST, GE 19.1

13.3.30. DEPLETION

Data x tN E1 E3 x IM x GE ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

This keyword specifies the so-called depletion option. If it is used, then the pressure for the
purpose of rock properties calculation is shifted so that the initial pressure effectively becomes
equal to the reference pressure specified by PRPOR (see 13.4.4) or CPRPOR (see 13.3.26).
This is applied to all regions of rock properties.
The keyword does not accept any parameters.
The keyword has an E1/E3-compatible analogue: option STORE as the second parameter
of the keyword ROCKOPTS (see 12.5.31).

13.3.30. DEPLETION 2053

Keywords for formats tN, IM, ST, GE 19.1

13.3.31. TRANSI / TRANSJ / TRANSK

Data x tN E1 E3 x IM x GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

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.

Default: transmissibility multipliers: 1.0.

These keywords have E1/E3-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.31. TRANSI / TRANSJ / TRANSK 2054

Keywords for formats tN, IM, ST, GE 19.1

13.3.32. TRANLI / TRANLJ / TRANLK

Data x tN E1 E3 x IM x GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

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.32. TRANLI / TRANLJ / TRANLK 2055

Keywords for formats tN, IM, ST, GE 19.1

13.3.33. TRANSMULT

Data x tN E1 E3 x IM x GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keyword determines the action of consecutive transmissibility multipliers specified

by TRANSI/J/K (see 13.3.31), TRANLI/J/K (see 13.3.32), etc.
The following parameters should be specified:

1. How to interpret consecutive multipliers:

◦ REPLACE: replace the current multiplier value with the new value;
◦ ACCUMULATE: multiply the current multiplier value by the new value.

Default: REPLACE.

Example
TRANSMULT ACCUMULATE
In the example it is specified that the consecutive transmissibility multipliers should be
multiplied.

13.3.33. TRANSMULT 2056

Keywords for formats tN, IM, ST, GE 19.1

13.3.34. TRANSF

Data x tN E1 E3 x IM GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

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 assumed 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.

This keyword has E1/E3-compatible analogues FAULTS (see 12.2.38) and MULTFLT
(see 12.2.39).

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.34. TRANSF 2057

Keywords for formats tN, IM, ST, GE 19.1

13.3.35. FRFRAC

Data x tN E1 E3 IM GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

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.
The following parameters should be specified:

1. value of cell volume fraction which corresponds to fracture volume.

Default:

• if fracture doesn’t contain rock, then the FRFRAC value is equal to porosity fracture
value;

• if this keyword is absent, then the fracture doesn’t 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.35. FRFRAC 2058

Keywords for formats tN, IM, ST, GE 19.1

13.3.36. FORMINFRAC

Data x tN E1 E3 IM GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

This keyword should be used in dual porosity model. It sets value of ratio between rock
volume in fracture and fracture volume.
The following parameters should be specified:

1. value of ratio between rock volume in fracture and fracture volume.

Default: if the keyword is absent, then fracture doesn’t 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.36. FORMINFRAC 2059

Keywords for formats tN, IM, ST, GE 19.1

13.3.37. SECTORARRAY

Data x tN E1 E3 x IM GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

The keyword specifies named FIP region.

The following parameters should be specified:

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.37) specifies FIP region ”ABC”.
Layers 1-7 along X axis, 2-9 along Y axis and 7 along Z axis are selected.

13.3.37. SECTORARRAY 2060

Keywords for formats tN, IM, ST, GE 19.1

13.3.38. ISECTOR / SECTORNAMES

Data x tN E1 E3 x IM x GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

This keyword specifies a sector via sector number and grid array. ISECTOR assigns sector
number defined by SECTORNAMES to sector blocks. SECTORNAMES must be specified at
least once before ISECTOR. Any values assigned in the keyword ISECTOR should be indicated
in the list of sectors defined by SECTORNAMES. The keyword ISECTOR can be specified
several times.
Data can be defined in the following format:

• SECTORNAMES list
list consists of an arbitrary number of pairs sector_name, sector_number , where

– sector_name – sector name;

– sector_number – sector number (unique positive integer).

• ISECTOR

– sector_name – sector name. A sector name should be unique;

– sector_number – sector number (unique positive integer) associated with sector
name sector_name that is assigned to grid blocks.

This keyword has an E1/E3 compatible analogue FIPNUM (see 12.4.10).

In this example in the grid 5 × 5 × 2 two sectors ”1” and ”2” are specified in layer 1 and
2 along axis Z (K index), respectively. 1 will be assigned to all blocks belonging to the sector
”1”, 2 will be assigned to blocks from the sector ”2”.
Example
SECTORNAMES '1' 1 '2' 2
ISECTOR *KVAR 1 2

13.3.38. ISECTOR / SECTORNAMES 2061

Keywords for formats tN, IM, ST, GE 19.1

13.3.39. DEPTH

Data x tN E1 E3 x IM GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

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.
• Default: CENTRE.

2. coordinate i of the block;

3. coordinate j of the block;

4. coordinate k of the block;

5. block depth (SI: m; FIELD: f t ).

This keyword has an E1/E3 compatible analogue DEPTH (see 12.3.28).

Example
DEPTH 1 1 1 600

13.3.39. DEPTH 2062

Keywords for formats tN, IM, ST, GE 19.1

13.3.40. DTOP

Data x tN E1 E3 x IM GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

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 (SI:
m; FIELD: 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.40. DTOP 2063

Keywords for formats tN, IM, ST, GE 19.1

13.3.41. PVCUTOFF

Data x tN E1 E3 x IM GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

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 (SI: m3 ; FIELD: f t 3 ).

This keyword has an E1/E3 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.41. PVCUTOFF 2064

Keywords for formats tN, IM, ST, GE 19.1

13.3.42. REFINE

Data x tN E1 E3 x IM x GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

The keyword specifies local grid refinement.

The data should be entered in one of the following formats:

I For uniformal grid refinement:

*REFINE block_coord *INTO nI nJ nK

II For logarithmic grid refinement:

*REFINE *INNERWIDTH width
block_coord *INTO nI nJ nK

Where:

1. *INNERWIDTH – sub-keyword which indicates that logarithmic refinement will be used;

2. width – width of the inner-most planes of blocks (SI: m, FIELD: f t ).

The blocks, contained in these planes will be assigned to the Fracture Zone and can be
further referenced with array indicator *FZ (FZ / NFZ, see 13.1.7).
Default: SI: 0.6096m, FIELD: 2 f t .

3. block_coord – 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.

4. *INTO – sub-keyword which indicates new refinement;

5. n_I – number of refined blocks in the I direction inside each block to refine;

6. n_J – number of refined blocks in the J direction inside each block to refine;

7. n_K – number of refined blocks in the K direction inside each block to refine.

13.3.42. REFINE 2065

Keywords for formats tN, IM, ST, GE 19.1

This keyword has an E1/E3 compatible analogue CARFIN (see 12.2.97).

Example 1
Example
*REFINE 1:2 2:3 1 *INTO 2 3 3
In this example 4 blocks are uniformly refined (all refined blocks will have the same di-
mensions): 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 2
Example
*REFINE *INNERWIDTH 3.0
1:2 2:3 1 *INTO 2 3 3
In this example the blocks are refined in the same manner as in the first example, but the
width of the first refined blocks (fracture plane) is explicitly specified via *INNERWIDTH sub-
keyword. Size of the other refined blocks will increase logarithmically away from the fracture.

Example 3
Example
*REFINE 2 3 2 / 2 2 2 *INTO 2 3 2
In this 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.42. REFINE 2066

Keywords for formats tN, IM, ST, GE 19.1

13.3.43. SCONNECT

Data x tN E1 E3 x IM GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

The keyword sets non-neighbor connection between two cells. The following parameters
should be specified:

1. I -coordinate of the first cell;

2. J -coordinate of this cell;

3. K -coordinate of this cell;

4. I -coordinate of the second cell;

5. J -coordinate of this cell;

6. K -coordinate of this cell;

7. transmissibility value (SI: md -m; FIELD: md - f t ).

This keyword has an E1/E3 compatible analogue NNCGEN (see 12.2.57).

Example
SCONNECT 2 1 2 10 1 3 100
In the example the keyword SCONNECT (see 13.3.43) sets connection between cells
(2,1,2) and (10,1,3). Transmissibility value is 100 md - f t .

13.3.43. SCONNECT 2067

Keywords for formats tN, IM, ST, GE 19.1

13.3.44. PLNRFRAC_TEMPLATE

Data x tN E1 E3 x IM x GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

This keyword specifies the planar fracture template for its implementation in multiple
locations in a model. The created template can be used via PLNRFRAC (see 13.3.45) specified
in the section Reservoir description (see section 13.3) and Well and recurrent data (see section
13.9). The template should be specified before it can be used by PLNRFRAC (see 13.3.45).
The following parameters should be specified:

1. PLNRFRAC_TEMPLATE ”template_name”
An unique template name for fracture. The name length should not exceed 80 characters.
The template name should be defined at least once.

2. PLNR_REFINE *INTO nir n jr nkr

A local grid for the planar fracture template. Local nir ×n jr ×nkr grid refinement is done
in fundamental blocks containing the fracture. All refined blocks are gathered together
into a block group ”bg_name” which can be used to refer to them. The fracture zone is a
single plane of blocks that extends from the centre outward to the fracture tips. To refer
to the refined blocks belonging to the fracture zone use an expression: *BG ”bg_name”
*FZ. To refer to the refined blocks out of the fracture zone use an expression: *BG
”bg_name” *NFZ;

3. BWHLEN Lhal f (SI: m, FIELD: f t )

Half-length of a planar hydraulic fracture. The fracture refinement starts from
f racture_origin in the specified direction until the half-length is reached, possibly into
neighbouring blocks;

4. (IDIR | JDIR)
Direction in which the planar hydraulic fracture is propagated from f racture_origin.
The direction should be specified;

5. INNERWIDTH Winner (SI: m, FIELD: f t )

Inner width of planes of blocks for a complex fracture grid. These blocks are formed
the fracture zone and can be refered separately via *FZ or skipped via *NFZ. Outside of
the fracture zone, block sizes normal to the fracture-zone plane increase logarithmically
away from the fracture zone. Winner is not a actual width of the fracture (which is on
the order of 0.001 m). Winner is a width on which an effective fracture permeability
is calculated so as to maintain the conductivity of the original fracture. Normally this
values varies from 2/3 m to 1 m;
Default: 0.6096 m (2 f t ).

13.3.44. PLNRFRAC_TEMPLATE 2068

Keywords for formats tN, IM, ST, GE 19.1

6. K2INT k2int
Secondary intrinsic permeability. k2int redefines the fracture permeability of the sec-
ondary fracture network (natural fractures) within the planar fracture region. k2int along
with DIFRAC (see 13.3.8), DJFRAC (see 13.3.8) and DKFRAC (see 13.3.8) are used to
model the effective permeability enhancement of the naturally fractured network caused
by the hydraulic fractures. If K2INT are not present, the effective natural fracture perme-
ability is specified by keywords PERMI (see 13.3.11), PERMJ (see 13.3.11) and PERMK
(see 13.3.11);

7. LAYERSUP nlayup
The number of K layers to include above f racture_origin. This keyword should be
used only when f racture_origin corresponds to the completion of a horizontal well.
Default: 0.

8. LAYERSDOWN nlaydown
The number of K layers to include below f racture_origin. This keyword should be
used only when f racture_origin corresponds to the completion of a horizontal well.
Default: 0.

9. grid_array (*MATRIX|*FRACTURE) (*FZ | *NFZ ...) ...

Assigns any number of grid–array property to refined grid blocks (”bg_name”).

• FZ – assigns grid-array property (see a list below) to all refined blocks belonging
to a matrix or a fracture;
• NFZ – assigns grid-array property (see a list below) to all refined blocks not
belonging to a matrix or a fracture.

Available grid-array properties are:

• POR (see 13.3.10);

• PERMI (see 13.3.11);
• PERMJ (see 13.3.11);
• PERMK (see 13.3.11);
• DIFRAC (see 13.3.8);
• DJFRAC (see 13.3.8);
• DKFRAC (see 13.3.8).

10. END_TEMPLATE

Geometry parameters (e.g., block size) associated with PLNR_REFINE can not be over-
written once a planar fracture grid is created.
In this example the planar fracture template with the name ”Upper_Frac” is created. Blocks
passed by the fracture with this template will be localy refined (option PLNR_REFINE) as

13.3.44. PLNRFRAC_TEMPLATE 2069

Keywords for formats tN, IM, ST, GE 19.1

5 × 5 × 1. The half–length of a planar hydraulic fracture (option BWHLEN) in the I direction

(option IDIR) will be equal to 200 m. The fracture inner width (INNERWIDTH) will be equal
to 2 m. Options LAYERSUP and LAYERSDOWN specify 4 block layers in up and down direc-
tions, respectively. The fracture origin will be assigned permeabilities (in X, Y, Z directions)
equal to 500 mD and its tips will be assigned permeabilities equal to 2.5 mD.
Example
PLNRFRAC_TEMPLATE 'Upper_Frac'
PLNR_REFINE *INTO 5 5 1
BWHLEN 200
IDIR
INNERWIDTH 2
LAYERSUP 4
LAYERSDOWN 4
PERMI MATRIX *FZ 500 2.5
PERMJ MATRIX *FZ 500 2.5
PERMK MATRIX *FZ 500 2.5
END_TEMPLATE

13.3.44. PLNRFRAC_TEMPLATE 2070

Keywords for formats tN, IM, ST, GE 19.1

13.3.45. PLNRFRAC

Data x tN E1 E3 x IM x GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

This keyword implements the planar fracture template created by PLNRFRAC_TEMPLATE

(see 13.3.44). The template should be specified before it can be used by PLNRFRAC.
After keyword the following parameters should be specified:

1. ”template_name”
A template name specified by PLNRFRAC_TEMPLATE (see 13.3.44);

2. f racture_origin
The origin of the planar hydraulic fracture located at well perforation connecting to the
fracture. This block must be a member of the global grid;

3. *BG_NAME ”bg_name”
A blockgroup name ”bg_name”. The blockgroup name ”bg_name” should not be used
previously.

For each definition of PLNRFRAC the following steps execute:

• the planar fracture is created using f racture_origin and template parameters;

• new refined cells are assigned to blockgroup with name ”bg_name”;

• grid-array data are assigned to blockgroup with name ”bg_name”.

Having created a blockgroup ”bg_name” using PLNRFRAC, individual template properties

can be overwritten by conventional grid-array keywords specified after this keyword. For
example, I-direction permeability can be overwritten using PERMI (see 13.3.11).
In this example the planar fracture template ”Upper_Frac” created by keyword PLNR-
FRAC_TEMPLATE (see 13.3.44) is implemented for construction of the fracture with origin
in the block (41,76,10). All refined blocks will be assigned to the group block with the name
”Frac_1”.
Example
PLNRFRAC_TEMPLATE 'Upper_Frac'
...
END_TEMPLATE
...
PLNRFRAC 'Upper_Frac' 41,76,10 *BG_NAME 'Frac_1'

13.3.45. PLNRFRAC 2071

Keywords for formats tN, IM, ST, GE 19.1

13.3.46. VAMOD

Data x tN E1 E3 x IM GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

This keyword is used to define modification to grid block volumes and face areas. Block
geometry modifiers can be used to locate centres of blocks at the reservoir boundary, model
symmetry elements of repeating patterns and model a reservoir with an irregular shape. The
following parameters should be specified:

1. key – is the modifier type key. An integer number specifying a modifier type for blocks
defined in keyword VATYPE. To define your own modifier type select the key from
2 and higher. It is not required to specify key for unmodified or null-block types. For
null-blocks key is 0, for unmodified (whole) blocks key is 1.

2. v – is the block volume modification factor. The factor is equal to (desired gross volume)
/ (DI (see 13.3.2) × DJ (see 13.3.2) × DK, see 13.3.2), where DI (see 13.3.2) is the
block length in X direction, DJ (see 13.3.2) is the block length in Y direction, DK
(see 13.3.2) is the block length in Z direction. It is required even for zero–porosity
blocks to correctly account for energy in rock. A zero–porosity block means a null-
block.

3. ai – is the area modifier factor in the X direction ([I, J, K] and [I + 1, J, K]). The factor is
equal to (desired area) / (area formed by block sizes DJ (see 13.3.2) and DK, see 13.3.2).
If the factor is zero there is no flow through this face;

4. aj – is the area modifier factor in the Y direction ([I, J, K] and [I, J + 1, K]). The factor is
equal to (desired area) / (area formed by block sizes DI (see 13.3.2) and DK, see 13.3.2).
If the factor is zero there is no flow through this face;

5. ak – is the area modifier factor in the Z direction ([I, J, K] and [I, J, K +1]). The factor is
equal to (desired area) / (area formed by block sizes DI (see 13.3.2) and DJ, see 13.3.2).
If the factor is zero there is no flow through this face;

6. ai- – is the area modifier factor in the direction opposite to X direction ([I − 1, J, K]
and [I, J, K]). The factor is equal to (desired area) / (area formed by block sizes DJ
(see 13.3.2) and DK, see 13.3.2). If the factor is zero there is no flow through this face;

7. aj- – is the area modifier factor in the direction opposite to Y direction ([I, J − 1, K]
and [I, J, K]). The factor is equal to (desired area) / (area formed by block sizes DI
(see 13.3.2) and DK, see 13.3.2). If the factor is zero there is no flow through this face;

13.3.46. VAMOD 2072

Keywords for formats tN, IM, ST, GE 19.1

8. ak- – is the area modifier factor in the direction opposite to Z direction ([I, J, K] and
[I, J, K − 1]). The factor is equal to (desired area) / (area formed by block sizes DI
(see 13.3.2) and DJ, see 13.3.2). If the factor is zero there is no flow through this face;

If VATYPE (see 13.3.47) and VAMOD are not specified all blocks are assumed to be active
and their full volumes and areas are used. If ai-, aj- and ak- are not specified then ai- = ai,
aj = aj- and ak- = ak. This is allowed if a factor does not vary along selected direction (X or
Y or Z). If the factor varies then a face between blocks [I, J, K] and [I + 1, J, K] and the face
between blocks [I − 1, J, K] and [I, J, K] have different factor, therefore, both values ai and ai-
should be specified.
Referencing Grid Block Faces
For example, in positive X direction the area modifier factor ai specified in the block [I, J, K]
is implemented to the face between block [I, J, K] and its adjacent block [I + 1, J, K]. In
direction opposite to X direction the area modifier factor ai- defined in block [I, J, K] is im-
plemented to the face between block [I, J, K] and its adjacent block [I − 1, J, K].

In this example the keyword VAMOD specifies modifier types. Two modifier type keys
will be further assigned to two blocks layers using the keyword VATYPE (see 13.3.47).
For key 2 the pore volume will be multiplied by 10, the area modifier factor in the X
direction (ai) is 0.5, the area modifier factor in the Y direction (aj) is 0.5 and the area modifier
factor in the Z direction (ak) is 1.
For key 3 the pore volume will be multiplied by 1. The area modifier factors in positive
X, Y and Z directions (ai, aj and ak) are 1. The area modifier factors in directions opposite to
X, Y and Z directions (ai-, aj- and ak-) are 0.5. Modifier type key equal to 4 is not used.
Example
VAMOD 2 10 0.5 0.5 1
VAMOD 3 1 1 1 1 0.5 0.5 0.5
VAMOD 4 10 1 10 1
VATYPE CON 1
*MOD
1:3 1:3 2 = 3
1:3 1:3 1 = 2

13.3.46. VAMOD 2073

Keywords for formats tN, IM, ST, GE 19.1

13.3.47. VATYPE

Data x tN E1 E3 x IM GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

This keyword specifies what modifications specified by keyword VAMOD (see 13.3.46)
will be done for the selected grid blocks.
VATYPE assigns a modifier type key (VAMOD, see 13.3.46) to the selected grid blocks,
including refined blocks. If key is 0 then blocks are null (inactive) blocks. If a key is not
specified by VAMOD then all blocks corresponds to this key are considered to be unmodified
type.
If VATYPE and VAMOD are not specified all blocks are assumed to be active and their
full volumes and areas are used. If ai-, aj- and ak- are not specified then ai- = ai, aj = aj-
and ak- = ak. This is allowed if a factor does not vary along selected direction (X or Y or Z).
If the factor varies then a face between blocks [I, J, K] and [I + 1, J, K] and the face between
blocks [I − 1, J, K] and [I, J, K] have different factor, therefore, both values ai and ai- should
be specified.
Referencing Grid Block Faces
For example, in positive X direction the area modifier factor ai specified in the block [I, J, K] is
implemented to the face between block [I, J, K] and its adjacent block [I +1, J, K]. In direction
opposite to X direction the area modifier factor ai- defined in block [I, J, K] is implemented
to the face between block [I, J, K] and its adjacent block [I − 1, J, K].
In this example VATYPE assigns two modifier type keys to two blocks layers: for the layer
1 key is equal 2, for the layer 2 key is equal 3. The keyword VAMOD (see 13.3.46) specifies
modifier types.
Example
VAMOD 2 10 0.5 0.5 1
VAMOD 3 1 1 1 1 0.5 0.5 0.5
VAMOD 4 10 1 10 1
VATYPE CON 1
*MOD
1:3 1:3 2 = 3
1:3 1:3 1 = 2

13.3.47. VATYPE 2074

Keywords for formats tN, IM, ST, GE 19.1

13.4. Other Reservoir Properties

13.4.1. ROCKTYPE

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir x Other Component
Section
Rockfluid Initial Numerical Well

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.17), HLOSSPROP (see 13.4.19), HLOSSTDIFF (see 13.4.18).

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

13.4. Other Reservoir Properties 2075

Keywords for formats tN, IM, ST, GE 19.1

In this example rock properties are specified for 2 rock regions.

13.4.1. ROCKTYPE 2076

Keywords for formats tN, IM, ST, GE 19.1

13.4.2. THTYPE

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir x Other Component
Section
Rockfluid Initial Numerical Well

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 ROCKTYPE
(see 13.4.1) is allowed.

Default: all grid blocks belong to one region.

The keyword has an E1/E3-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 2077

Keywords for formats tN, IM, ST, GE 19.1

13.4.3. ROCKCP

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir x Other Component
Section
Rockfluid Initial Numerical Well

The keyword sets the coefficients CP1 , CP2 of the rock enthalpy formula 4.49:
1
HR (T ) = (CP1 (T − Tre f ) + CP2 (T − Tre f )2 )
2
Tre f is set via TEMR (see 13.5.26).
The following parameters are to be specified:

1. CP1 (SI: J/m3 /◦ C, FIELD: Btu/ f t 3 /◦ F),

2. CP2 (SI: J/m3 /◦C2 , FIELD: Btu/ f t 3 /◦ F 2 ).

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 E1/E3-compatible analogues HEATCR (see 12.15.17), HEATCRT

(see 12.15.18).
In tNavigator the coefficients CP1 , CP2 can be specified via the keyword HEATTCR
(see 12.15.19).
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 2078

Keywords for formats tN, IM, ST, GE 19.1

13.4.4. PRPOR

Data x tN E1 E3 x IM x GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

For models in IM, GE data format these keywords should be in the section Reservoir
(Reservoir properties), for models in ST format – Other (Other reservoir properties).

This keyword sets the reference pressure pre f (SI: kPa, FIELD: psi), which is used in
porosity calculations.
The models that can be used in tNavigator (Linear Elastic, Nonlinear Elastic, Dilation-
Recompaction) are described in the section 4.24.

In IM and GE models this keyword is set for the whole model.

In ST models, different values can be entered for different rock regions (see an example
in the description of ROCKTYPE, see 13.4.1).

Default: if PRPOR (see 13.4.4) is absent

• for IM, GE models: SI: 101.3kPa, FIELD: 14.7psi;

• for ST 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 E1/E3-compatible keyword ROCK

(see 12.5.17).

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 2079

Keywords for formats tN, IM, ST, GE 19.1

Example
*ROCKTYPE 1
*PRPOR 16450
*CPOR 1.4e-6

*ROCKTYPE 2
*PRPOR 13750
*CPOR 1.1e-6

This example sets different reference pressures and rock compressibility coefficients for
different ROCKTYPE (see 13.4.1) regions.

13.4.4. PRPOR 2080

Keywords for formats tN, IM, ST, GE 19.1

13.4.5. CPOR

Data x tN E1 E3 x IM GE x ST MO
format
Input x Reservoir Other Component
Section
Rockfluid Initial Numerical Well

For models in IM data format these keywords should be in the section Reservoir (Reservoir
properties), for models in ST 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.

In IM and GE models this keyword is set for the whole model.

In ST models, different values can be entered for different rock regions (see an example
in the description of ROCKTYPE, see 13.4.1).

The models that can be used in tNavigator (Linear Elastic, Nonlinear Elastic, Dilation-
Recompaction) are described in the section 4.24.

Default: 0.

The keyword is analogous to the 2-nd parameter of E1/E3-compatible keyword ROCK

(see 12.5.17).

Example
*CPOR 1.3e-6

In this example the rock compressibility coefficient is 1.3e-6 (1/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 2081

Keywords for formats tN, IM, ST, GE 19.1

Example
*ROCKTYPE 1
*PRPOR 16450
*CPOR 1.4e-6

*ROCKTYPE 2
*PRPOR 13750
*CPOR 1.1e-6

This example sets different reference pressures and rock compressibility coefficients for
different ROCKTYPE regions.

13.4.5. CPOR 2082

Keywords for formats tN, IM, ST, GE 19.1

13.4.6. CTPOR

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir x Other Component
Section
Rockfluid Initial Numerical Well

The keyword sets the effective thermal expansion coefficient of the formation cT (SI:
1/C , FIELD: 1/F ), 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).

The models that can be used in tNavigator (Linear Elastic, Nonlinear Elastic, Dilation-
Recompaction) are described in the section 4.24.

Default: 0.

The keyword is analogous to the 1-st parameter of ROCKT (see 12.15.24), 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 2083

Keywords for formats tN, IM, ST, GE 19.1

13.4.7. CPTPOR

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir x Other Component
Section
Rockfluid Initial Numerical Well

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.
Different values can be entered for different rock regions (see an example in the description
of ROCKTYPE, see 13.4.1).

The models that can be used in tNavigator (Linear Elastic, Nonlinear Elastic, Dilation-
Recompaction) are described in the section 4.24.

Default: 0.

The keyword is analogous to the 2-nd parameter of ROCKT (see 12.15.24), 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 2084

Keywords for formats tN, IM, ST, GE 19.1

13.4.8. THCONR

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir x Other Component
Section
Rockfluid Initial Numerical Well

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.64 when
THCONMIX (see 13.4.13) sets the option SIMPLE:
 
Kb = ϕ 1 − SS · (kW SW + kO SO + kG SG ) + ϕ · kS · SbS + (1 − ϕ) · kR
b

Different values can be entered for different rock regions (see an example in the descrip-
tion of ROCKTYPE, see 13.4.1).

Default: 149.6kJ/m/day/C .

The keyword has an E1/E3-compatible analogue THCONR (see 12.15.22).

Example
THCONR 187000

In this example the rock thermal conductivity is 187000J/m/day/C .

13.4.8. THCONR 2085

Keywords for formats tN, IM, ST, GE 19.1

13.4.9. THCONW

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir x Other Component
Section
Rockfluid Initial Numerical Well

The keyword specifies the water thermal conductivity kW (SI: J/m/day/C , FIELD:
Btu/ f t/day/F ), which is used in the block thermal conductivity calculations 4.64 when
THCONMIX (see 13.4.13) sets the option SIMPLE:
 
Kb = ϕ 1 − SS · (kW SW + kO SO + kG SG ) + ϕ · kS · SbS + (1 − ϕ) · kR
b

Different values can be entered for different rock regions (see an example in the descrip-
tion of ROCKTYPE, see 13.4.1).

Default: 1.496 ∗ 105 J/m/day/C = 24Btu/ f t/day/F .

Example
THCONW 4.85E4

In this example the water thermal conductivity is 4.85E4J/m/day/C .

13.4.9. THCONW 2086

Keywords for formats tN, IM, ST, GE 19.1

13.4.10. THCONO

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir x Other Component
Section
Rockfluid Initial Numerical Well

The keyword specifies the oil thermal conductivity kO (SI: J/m/day/C , FIELD:
Btu/ f t/day/F ), which is used in the block thermal conductivity calculations 4.64 when
THCONMIX (see 13.4.13) sets the option SIMPLE:
 
Kb = ϕ 1 − SS · (kW SW + kO SO + kG SG ) + ϕ · kS · SbS + (1 − ϕ) · kR
b

Different values can be entered for different rock regions (see an example in the descrip-
tion of ROCKTYPE, see 13.4.1).

Default: 1.496 ∗ 105 J/m/day/C = 24Btu/ f t/day/F .

Example
THCONO 2.03E4

In this example the oil thermal conductivity is 2.03E4J/m/day/C .

13.4.10. THCONO 2087

Keywords for formats tN, IM, ST, GE 19.1

13.4.11. THCONG

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir x Other Component
Section
Rockfluid Initial Numerical Well

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.64 when
THCONMIX (see 13.4.13) sets the option SIMPLE:
 
Kb = ϕ 1 − SS · (kW SW + kO SO + kG SG ) + ϕ · kS · SbS + (1 − ϕ) · kR
b

Different values can be entered for different rock regions (see an example in the descrip-
tion of ROCKTYPE, see 13.4.1).

Default: 1.496 ∗ 105 J/m/day/C = 24Btu/ f t/day/F .

Example
THCONG 3800

In this example the gas thermal conductivity is 3800J/m/day/C .

13.4.11. THCONG 2088

Keywords for formats tN, IM, ST, GE 19.1

13.4.12. THCONS

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir x Other Component
Section
Rockfluid Initial Numerical Well

The keyword specifies the solid phase thermal conductivity kS (SI: J/m/day/C , FIELD:
Btu/ f t/day/F ), which is used in the block thermal conductivity calculations 4.64 when
THCONMIX (see 13.4.13) sets the option SIMPLE:
 
Kb = ϕ 1 − SS · (kW SW + kO SO + kG SG ) + ϕ · kS · SbS + (1 − ϕ) · kR
b

Different values can be entered for different rock regions (see an example in the descrip-
tion of ROCKTYPE, see 13.4.1).

Example
THCONS 152000

In this example the solid phase thermal conductivity is 152000J/m/day/C .

13.4.12. THCONS 2089

Keywords for formats tN, IM, ST, GE 19.1

13.4.13. THCONMIX

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir x Other Component
Section
Rockfluid Initial Numerical Well

The keyword sets the method of block thermal conductivity calculation.

The detailed description of thermal conductivity calculation is provided in section 4.28.

The data should be entered in the following format:

*THCONMIX method

Where:

• method – the methos of block thermal conductivity calculation.The avaliable options

are:

– *SIMPLE (see 4.64);

– *LOG (see 4.65);
– *COMPLEX (see 4.66);
– *TEMPER (see 4.67).

This keyword has an analogue THCONMIX (see 12.15.25), which is used in tNavigator.

Example
*THCONMIX *SIMPLE
This example specifies the method of block thermal conductivity calculation – SIMPLE.

13.4.13. THCONMIX 2090

Keywords for formats tN, IM, ST, GE 19.1

13.4.14. RXEQFOR

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir x Other Component
Section
Rockfluid Initial Numerical Well

This keyword specifies the data for forward chemical reaction that deviates from equilib-
rium.

The detailed description of thermodynamic equilibrium is provided in section 4.9 and the
chemical reactions are described in section 4.29.

If *RXEQFOR option is used, the rate of forward chemical reaction will be modified for
the specified fluid component by replacing its composition ci, j with deviated composition
∆ci, j :
∆c j,i = max[0, x j,i − cequil ] (13.1)
cbase
If cbase is defined via RXEQBASE (see 13.4.16), then ∆ci, j = .
K
cbase
If RXEQBASE (see 13.4.16) is not defined, then ∆ci, j = .
K
Equlibrium constants (K-values) are calculated as follows:

Ki (p, T ) = (kv1 /p + kv2 · p + kv3 ) · ekv4 /(T −kv5 ) (13.2)

The data should be entered in the following format:

*RXEQFOR ‘comp_name’ kv1 kv2 kv3 kv4 kv5

Where:
• ‘comp_name’ – name of the component;

• kv1 kv2 kv3 kv4 kv5 – the values of the corresponding coefficients in equation 13.2.
The corresponding units for these cofficients are:
In SI: [kPa], [1/kPa], [dimentionless], [C], [C];
In FIELD: [psi], [1/psi], [dimentionless], [F], [F].

Example
*COMPNAME 'Water' 'Methane' 'Oil' `Intermediate' 'Gas'
*STOREAC 0 1 0 0 0
*STOPROD 0 0 0 1 0
*RXEQFOR 'methane' 42000 0 0 0 0

In this example:

13.4.14. RXEQFOR 2091

Keywords for formats tN, IM, ST, GE 19.1

1. The chemical reaction (transition of Methane component to intermediate state) is de-

fined via keywords STOREAC (see 13.5.47) and STOPROD (see 13.5.48);

2. Keyword *RXEQFOR specifies that the correction will be applied for non-equlibrium
forward reaction and defines kv coefficients for 13.2 equation.

13.4.14. RXEQFOR 2092

Keywords for formats tN, IM, ST, GE 19.1

13.4.15. RXEQBAK

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir x Other Component
Section
Rockfluid Initial Numerical Well

This keyword specifies the data for backward chemical reaction that deviates from equi-
librium.

The detailed description of thermodynamic equilibrium is provided in section 4.9 and the
chemical reactions are described in section 4.29.

If *RXEQBAK option is used, the rate of backward chemical reaction will be modified
for the specified fluid component by replacing its composition ci, j with deviated composition
∆ci, j :
∆c j,i = max[0, x j,i − cequil ] (13.3)
cbase
If cbase is defined via RXEQBASE (see 13.4.16), then ∆ci, j = .
K
cbase
If RXEQBASE (see 13.4.16) is not defined, then ∆ci, j = .
K
Equlibrium constants (K-values) are calculated as follows:

Ki (p, T ) = (kv1 /p + kv2 · p + kv3 ) · ekv4 /(T −kv5 ) (13.4)

The data should be entered in the following format:

*RXEQBAK ‘comp_name’ kv1 kv2 kv3 kv4 kv5

Where:
• ‘comp_name’ – name of the component;

• kv1 kv2 kv3 kv4 kv5 – the values of the corresponding coefficients in equation 13.4.
The corresponding units for these cofficients are:
In SI: [kPa], [1/kPa], [dimentionless], [C], [C];
In FIELD: [psi], [1/psi], [dimentionless], [F], [F].

Example
*COMPNAME 'Water' 'Methane' 'Oil' `Intermediate' 'Gas'
*STOREAC 0 1 0 0 0
*STOPROD 0 0 0 1 0
*RXEQBAK 'Methane' 42000 0 0 0 0

In this example:

13.4.15. RXEQBAK 2093

Keywords for formats tN, IM, ST, GE 19.1

1. The chemical reaction (transition of Methane component to intermediate state) is de-

fined via keywords STOREAC (see 13.5.47) and STOPROD (see 13.5.48);

2. Keyword *RXEQBAK specifies that the correction will be applied for non-equlibrium
backward reaction and defines kv coefficients for 13.4 equation.

13.4.15. RXEQBAK 2094

Keywords for formats tN, IM, ST, GE 19.1

13.4.16. RXEQBASE

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir x Other Component
Section
Rockfluid Initial Numerical Well

This keyword specifies the base component which will be used for calculations of com-
ponet’s deviated composition (RXEQFOR (see 13.4.14), RXEQBAK, see 13.4.15).

The detailed description of thermodynamic equilibrium is provided in section 4.9 and the
chemical reactions are described in section 4.29.

The data should be entered in the following format:

*RXEQBASE ‘comp_name’

Where:

• ‘comp_name’ – name of the base component. It must not be the same component as
the one described by RXEQFOR (see 13.4.14) or RXEQBAK (see 13.4.15).

Example
*COMPNAME 'Water' 'Methane' 'Oil' `Intermediate' 'Gas'
*STOREAC 0 1 0 0 0
*STOPROD 0 0 0 1 0
*RXEQFOR 'Methane' 42000 0 0 0 0
*RXEQBASE `Gas'

In this example:

1. The chemical reaction (transition of Methane component to intermediate state) is de-

fined via keywords STOREAC (see 13.5.47) and STOPROD (see 13.5.48);

2. Keyword *RXEQFOR specifies that the correction will be applied for non-equlibrium
forward reaction and defines kv coefficients for 13.2 equation;

3. Component Gas is set as a base component for the equilibrium reference.

13.4.16. RXEQBASE 2095

Keywords for formats tN, IM, ST, GE 19.1

13.4.17. HLOSST

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir x Other Component
Section
Rockfluid Initial Numerical Well

This keyword specifies the initial temperature of reservoir surroundings (SI: ◦ C, FIELD:
◦ F), (see the section 4.30. The heat loss between the reservoir and surroundings).

Different values can be entered for different rock regions (see an example in the descrip-
tion of ROCKTYPE, see 13.4.1).

The keyword is analogous to the 2-nd parameter of E1/E3 compatible keyword ROCK-
PROP (see 12.2.84).

Example
HLOSST 43

In this example the initial temperature of reservoir surroundings is 43 ◦ C.

13.4.17. HLOSST 2096

Keywords for formats tN, IM, ST, GE 19.1

13.4.18. HLOSSTDIFF

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir x Other Component
Section
Rockfluid Initial Numerical Well

This keyword specifies the minimal difference between temperatures when the calculations
of the heat exchange should start (SI: ◦ C, FIELD: ◦ F), (see the section 4.30. The heat loss
between the reservoir and surroundings).

Different values can be entered for different rock regions (see an example in the descrip-
tion of ROCKTYPE, see 13.4.1).

Default: 0.

Example
HLOSSTDIFF 1

In this example the minimal difference between temperatures when the calculations of the
heat exchange should start is set to 1 ◦ C.

13.4.18. HLOSSTDIFF 2097

Keywords for formats tN, IM, ST, GE 19.1

13.4.19. HLOSSPROP

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir x Other Component
Section
Rockfluid Initial Numerical Well

The keyword sets the connection between the reservoir and cap and base rocks, volumet-
ric 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.

The following parameters are to be specified:

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 ).

Different values can be entered for different rock regions (see an example in the descrip-
tion of ROCKTYPE, see 13.4.1).

The keyword has an E1/E3-compatible analogues ROCKCON (see 12.2.85), ROCKPROP

(see 12.2.84).
The keyword is also analogous to ROCKCONT (see 12.2.86), 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.19. HLOSSPROP 2098

Keywords for formats tN, IM, ST, GE 19.1

13.4.20. CPORPD

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir x Other Component
Section
Rockfluid Initial Numerical Well

The keyword specifies formation compressibility pressure dependence.

The models that can be used in tNavigator (Linear Elastic, Nonlinear Elastic, Dilation-
Recompaction) are described in the section 4.24.

The following parameters should be specified:

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.15.24), which is used in tNavigator.
Example
CPORPD 13.5E-06 1. 850.

13.4.20. CPORPD 2099

Keywords for formats tN, IM, ST, GE 19.1

13.4.21. PORMAX

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir x Other Component
Section
Rockfluid Initial Numerical Well

The keyword specifies maximal fractional increase in porosity due to pressure.

The models that can be used in tNavigator (Linear Elastic, Nonlinear Elastic, Dilation-
Recompaction) are described in the section 4.24.

The following parameters should be specified:

1. fractional increase in porosity due to pressure.

The keyword is analogous to the 6th parameter of the keyword ROCKT (see 12.15.24),
which is used in tNavigator.
Example
PORMAX 0.1

13.4.21. PORMAX 2100

Keywords for formats tN, IM, ST, GE 19.1

13.4.22. PORFORM

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir x Other Component
Section
Rockfluid Initial Numerical Well

This keyword specifies the type of dependence of porosity on temperature and pressure.
The following parameter should be specified:

1. Dependence type:

• LINEAR — linear,
• EXP — exponential.

Porosity ϕ = ϕ(p, T, x, y, z) is calculated as follows:

PORFORM value Porosity


LINEAR ϕ(p, T, x, y, z) = ϕre f (x, y, z) · 1 + c(p,t)


EXP ϕ(p, T, x, y, z) = ϕre f (x, y, z) · exp c(p,t)

Here c(p,t) is a dimensionless parameter which may be calculated in various ways accord-
ing to the model used. The models that can be used in tNavigator (Linear Elastic, Nonlinear
Elastic, Dilation-Recompaction) are described in the section 4.24.

Default: LINEAR.
Example
PORFORM EXP

13.4.22. PORFORM 2101

Keywords for formats tN, IM, ST, GE 19.1

13.4.23. DILATION

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir x Other Component
Section
Rockfluid Initial Numerical Well

The keyword specifies the parameters of dilation/recompaction model. The models that can
be used in tNavigator (Linear Elastic, Nonlinear Elastic, Dilation-Recompaction) are described
in the section 4.24.
The following parameters may be specified in any order:
• PBASE <number>
Sets reference pressure for elastic curve in a reservoir dilation/recompaction model (SI:
kPa, FIELD: psi).
Default: according to PRPOR (see 13.4.4).
• PDILA <number>
Sets pressure value at which dilation begins (SI: kPa, FIELD: psi).
Default: 0.
• PPACT <number>
Sets boundary pressure value at which recompaction phase begins (SI: kPa, FIELD:
psi). This value should be less than value specified in PDILA.
Default: 0.
• CRD <number>
Sets rock compressibility coefficient at dilation phase (SI: 1/kPa, FIELD: 1/psi).
Default: 0.
• FR <number>
Sets residual dilation fraction, i.e. ratio of difference between porosity value after re-
compaction phase and initial porosity value to difference between changing of porosity
value during dilation phase.
Default: 0.
• PORRATMAX
Sets coefficient of maximal porosity increasing over reference porosity (see the keyword
POR, see 13.3.10). Dilation process will stop when porosity value will be maximal.
Default: 1.
• CPEPAC <number>
Sets pore volume compressibility value for elastic curve in a reservoir dilation/recom-
paction model (SI: 1/kPa, FIELD: 1/psi).

13.4.23. DILATION 2102

Keywords for formats tN, IM, ST, GE 19.1

Default: according to CPOR (see 13.4.5).

• CTD <number>
Sets pore volume thermal expansion coefficient for dilation phase (SI: 1/◦ C, FIELD:
1/◦ F). This value must be non-negative.
Default: according to CTPOR (see 13.4.6).

• CTPPAC <number>
Sets pore volume thermal expansion coefficient for recompaction phase (SI: 1/◦ C,
FIELD: 1/◦ F). This value must be non-negative.
Default: according to CTPOR (see 13.4.6).

Example
DILATION
PBASE 200
PDILA 420.0
FR 0.4
PORRATMAX 1.3
CTD 6E-6
CTPPAC 2E-6

13.4.23. DILATION 2103

Keywords for formats tN, IM, ST, GE 19.1

13.5. Component properties

13.5.1. K_SURF

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword specifies component K-values at surface conditions. The following parame-
ters 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. Component properties 2104

Keywords for formats tN, IM, ST, GE 19.1

13.5.2. SURFLASH

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

This keyword is used to calculate fluid-in-place 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).

3. Default: SEGREGATED.

Example
SURFLASH KVALUE

13.5.2. SURFLASH 2105

Keywords for formats tN, IM, ST, GE 19.1

13.5.3. MOLVOL

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword sets the component molar volume at reference temperature TEMR
(see 13.5.26) and reference pressure PRSR (see 13.5.25). This value is inverse to the compo-
nent molar density MOLDEN (see 13.5.29).
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 E1/E3-compatible analogue DREF (see 12.15.41).

13.5.3. MOLVOL 2106

Keywords for formats tN, IM, ST, GE 19.1

13.5.4. MODEL

Data x tN E1 E3 x IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

For models in IM, ST and GE format this keyword has different syntax.

For models in IM format: (ST and GE are below)

The keyword specifies a type of model. tNavigator read the following types (the keyword
doesn’t have in influence on the simulation):
• BLACKOIL – oil, gas, water;

• OILWATER – two-phase model, without gas phase. Concentration of dissolved gas is

constant and uniformly distributed. Analog of this option is the keyword RSCONST
(see 12.5.13);

• POLY – polymer model (oil, gas, water and polymer). Description of polymer flood
model is given in section Polymer flood in IM format;

• API-INT – API tracking option, see 2.8.8;

• API-INTO;

• GASWATER – gas-water model, without gas phase;

• GASWATER_WITH_CONDENSATE – gas-water model with condensate. It is an ex-

tension of the GASWATER option. Oil (as condensate) can initially present in the gas
phase either in a saturated or undersaturated state. Condensate can be produced at surface
or can drop out in the reservoir.
Three keywords have an E1/E3-compatible analogue OIL (see 12.1.56), WATER
(see 12.1.58), GAS (see 12.1.57), VAPOIL (see 12.1.59), DISGAS (see 12.1.60).
Example
MODEL BLACKOIL
This example specifies the black oil model.
For models in ST 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 2107

Keywords for formats tN, IM, ST, GE 19.1

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 E1/E3-compatible analogue COMPS (see 12.14.1). COMPS
(see 12.14.1) sets the number of hydrocarbon components, MODEL – total number of compo-
nents (including water).

In the example below there are 7 components. ”1” indicates in the table that the component
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
enabled.

Component name Water Oil Gas Solid phase

Water 1 0 1 0
Asphaltenes 0 1 0 0
Light oil 0 1 1 0
CO2 1 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 GE format:

In this case the keyword sets type of equation of state for a model. The following param-
eters should be specified:
1. type of equation of state:
• SRK – Soave-Redlich-Kwong equation;
• PR – Peng-Robinson equation.

Example
MODEL SRK

13.5.4. MODEL 2108

Keywords for formats tN, IM, ST, GE 19.1

13.5.5. NC

Data x tN E1 E3 IM x GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

This keyword defines the number of primary hydrocarbon components in the fluid, ex-
cluding water component. This keyword is obligatory and follows the keyword MODEL
(see 13.5.4).
It is possible to define two types of components:

• Library components – nc;

• User components – nuser.

This keyword is followed by the number of library components (nc) and then the number of
user components (nuser). If the number of user components (nuser) is absent, it is presumed
nuser=0.
Example
*NC 9 9

13.5.5. NC 2109
Keywords for formats tN, IM, ST, GE 19.1

13.5.6. HCFLAG

Data x tN E1 E3 IM x GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

This keyword indicates whether the user component is a hydrocarbon one. For each com-
ponent this keyword is followed by 0 or 1.

• If 1 is selected the user component is a hydrocarbon component;

• If 0 is selected the user component is a non-hydrocarbon component.

Example
*HCFLAG 1 1 1 1 1 1 1 1 1

13.5.6. HCFLAG 2110

Keywords for formats tN, IM, ST, GE 19.1

13.5.7. PVC3

Data x tN E1 E3 IM x GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

This keyword defines the parameter used for the calculation of binary interaction coeffi-
cients between each hydrocarbon-hydrocarbon component pair using the following formula:
q
1/3 1/3 !PVC3
2 Vci Vc j
ki j = 1 − 1/3 1/3
Vci +Vc j
where Vci and Vc j are critical volume of ith and jth component, respectively. Typically, PVC3
value is equal to 1.2. PVC3 equal to 0 means that binary interaction coefficient is 0.
Default: PVC3 is 0.

This keyword should be defined in the Component section after keywords MODEL
(see 13.5.4) and NC (see 13.5.5).
Above indicated formula for calculation of binary interaction coefficients is applied for all
components, library and user–defined components, i.e. for components, having a value 1 in
the keyword HCFLAG (see 13.5.6).
Thus, ki j values for user components defined by keyword BIN (see 13.5.85) may be
overwritten. In order to avoid overwriting, set 0 for the user components in the keyword
HCFLAG (see 13.5.6).
Example
*PVC3 1.3539480E-01

13.5.7. PVC3 2111

Keywords for formats tN, IM, ST, GE 19.1

13.5.8. CRIT

Data x tN E1 E3 IM x GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

This keyword specifies the correlation to be used for calculation of the critical properties
of user-defined components (for details of the physical model see section 3.6).
The following correlations are available:

• LEEKESLER
The Lee-Kesler correlation (Lee and Kesler, 1975) will be used;

• RIAZI
The Riazi-Daubert correlation (Riazi and Daubert, 1980) will be used;

• TWU
The Twu correlation (Twu, 1984) will be used.

Default: the Lee-Kesler correlation is used (LEEKESLER).

This keyword should be defined in the Component section after keywords MODEL
(see 13.5.4) and NC (see 13.5.5).
This keyword is used only when user components are defined, but their critical properties
are not specified. In this case, they are calculated based on specific gravity, boiling temperature
and molecular weight data using the selected correlation. See keywords PCRIT (see 13.5.35)
and TCRIT (see 13.5.36).
Example
*CRIT *LEEKESLER

13.5.8. CRIT 2112

Keywords for formats tN, IM, ST, GE 19.1

13.5.9. PVT

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword sets PVT properties of oil and gas. One of the keywords PVT, PVTCOND
(see 13.5.10), or DIFLIB (see 13.5.11) must be present in a model.
The data should be entered the following way:
PVT (BG|EG|ZG) number

The header parameters have the following meaning:

1. BG means that the gas formation volume factor will be used (EG stands for the gas
expansion factor, ZG for the 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.

2. number is the number of PVT region to which the following table applies.

The table consists of arbitrary number of lines (two or more). Pressure (the first parameter)
should increase down the column.
Each line contains the following 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. formation volume factor of saturated oil at the bubble point pressure (SI: m3 /m3 ,
FIELD: rb/stb),

4. Bg – gas formation volume factor (SI: m3 /m3 , FIELD: rb/sc f ) (or Eg – gas expansion
factor (SI: m3 /m3 , FIELD: sc f /rb), or Zg – gas compressibility factor, if EG or ZG
was specified after PVT),

5. viscosity of saturated oil at the bubble point pressure (SI: mPa · s, FIELD: cp),

6. viscosity of gas at the bubble point pressure (SI: mPa · s, FIELD: cp),

7. (optional) oil compressibility,

8. (optional) gas-oil surface tension (SI, FIELD: dyne/cm).

13.5.9. PVT 2113

Keywords for formats tN, IM, ST, GE 19.1

The keyword has an E1/E3-compatible analogue PVCO (see 12.5.6), PVDG (see 12.5.7).
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 the 1st PVT region (gas-oil surface tension isn’t
specified – default value will be used).

13.5.9. PVT 2114

Keywords for formats tN, IM, ST, GE 19.1

13.5.10. PVTCOND

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword sets PVT properties of oil and wet gas. One of the keywords PVT
(see 13.5.9), PVTCOND, or DIFLIB (see 13.5.11) must be present in a model.
The data should be entered the following way:
PVTCOND (BG|EG|ZG) number

The header parameters have the following meaning:

1. BG means that the gas formation volume factor will be used (EG stands for the gas
expansion factor, ZG for the 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.

2. number is the number of PVT region to which the following table applies.

The table consists of arbitrary number of lines (two or more). Pressure (the first parameter)
should increase down the column.
Each line contains the following 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. oil content in the saturated gas at the given pressure (SI: m3 /m3 , FIELD: stb/sc f ),

4. formation volume factor of saturated oil at the given bubble point pressure (SI: m3 /m3 ,
FIELD: rb/stb),

5. Bg – gas formation volume factor (SI: m3 /m3 , FIELD: rb/sc f ) (or Eg – gas expansion
factor (SI: m3 /m3 , FIELD: sc f /rb), or Zg – gas compressibility factor, if EG or ZG
was specified after PVTCOND),

6. viscosity of saturated oil at the bubble point pressure (SI: mPa · s, FIELD: cp),

7. viscosity of gas at the bubble point pressure (SI: mPa · s, FIELD: cp),

8. (optional) gas-oil surface tension (SI, FIELD: dyne/cm).

13.5.10. PVTCOND 2115

Keywords for formats tN, IM, ST, GE 19.1

The keyword has no direct analogue in E1/E3, the closest substitute being PVTO
(see 12.5.4)/PVTG (see 12.5.8).
Example
PVTCOND BG 1
5000 0.0 8.444e-005 1.0 0.029979 0.15485 0.015191
10000 0.0 0.00017063 1.0 0.01454 0.13568 0.016492
20000 0.0 0.00025476 1.0 0.007249 0.11153 0.021845
29269 0.0 0.00036609 1.0 0.005287 0.10276 0.029242
30000 0.0 0.00037604 1.0 0.0051953 0.10222 0.029875
30404.1 0.0 0.00038166 1.0 0.0051472 0.10192 0.030227
This example specifies PVT table for the 1st PVT region (gas-oil surface tension isn’t
specified – default value will be used).

13.5.10. PVTCOND 2116

Keywords for formats tN, IM, ST, GE 19.1

13.5.11. DIFLIB

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword specifies the results of differential liberation experiment that serve to recon-
struct the PVT properties of oil and gas. One of the keywords PVT (see 13.5.9), PVTCOND
(see 13.5.10), or DIFLIB must be present in a model.
The data should be entered the following way:
DIFLIB (BG|EG|ZG) number
BUBBLE pressure
BOBF bobf
RSIF rsif
The header parameters have the following meaning:

1. BG means that the gas formation volume factor will be used (EG stands for the gas
expansion factor, ZG for the 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.

2. number is the number of PVT region to which the following table applies.

3. pressure is the bubble point pressure used for converting DIFLIB data to PVT table (SI:
kPa, FIELD: psi).

4. bobf is the oil formation volume factor at bubble point measured relative to the standard
conditions (SI: m3 /m3 , FIELD: rb/stb).

5. rsif is the solution gas-oil-ratio at bubble point measured relative to the standard condi-
tions (SI: m3 /m3 , FIELD: sc f /ST B).

The table consists of arbitrary number of lines (two or more). Pressure (the first parameter)
should increase down the column.
Each line contains the following parameters:

1. the bubble point pressure (SI: kPa, FIELD: psi),

2. differential 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. differential formation volume factor of saturated oil at the given bubble point pressure
(SI: m3 /m3 , FIELD: rb/stb),

13.5.11. DIFLIB 2117

Keywords for formats tN, IM, ST, GE 19.1

4. Bg – gas formation volume factor (SI: m3 /m3 , FIELD: rb/sc f ) (or Eg – gas expansion
factor (SI: m3 /m3 , FIELD: sc f /rb), or Zg – gas compressibility factor, if EG or ZG
was specified after DIFLIB),

5. viscosity of saturated oil at the bubble point pressure (SI: mPa · s, FIELD: cp),

6. viscosity of gas at the bubble point pressure (SI: mPa · s, FIELD: cp),

7. (optional) oil compressibility,

8. (optional) gas-oil surface tension (SI, FIELD: dyne/cm).

Example
DIFLIB BG 1
BOBF 1.137
BUBBLE 8101
RSIF 35.9
689 5.6 1.066 0.1716 5.96 0.0117
1724 11.0 1.080 0.0673 5.11 0.0125
2758 15.3 1.090 0.0415 4.79 0.0129
4137 20.4 1.101 0.0273 4.55 0.0132
5516 25.2 1.110 0.0203 4.41 0.0136
6895 29.6 1.119 0.0162 4.34 0.0139
8101 33.4 1.127 0.0125 4.28 0.0142
This example specifies the differential liberation table for the 1st PVT region (compress-
ibility and gas-oil surface tension aren’t specified – default values will be used).

13.5.11. DIFLIB 2118

Keywords for formats tN, IM, ST, GE 19.1

13.5.12. EGUST / BGUST / ZGUST

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

These keywords set the table of gas properties in dependence on pressure for undersatu-
rated gas with condensate. BGUST specifies the gas formation volume factor, EGUST specifies
the gas expansion factor, and ZGUST specifies the the gas compressibility factor.
The table is preceded by the following header:
(EGUST|BGUST|ZGUST) number
Here number is the number of PVT region to which the following table applies.
The table consists of arbitrary number of lines (two or more). Pressure (the first parameter)
should increase down the column.
Each line contains the following parameters:

1. dew point pressure of a new saturated gas mixture formed by reducing oil contents. 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 value of Bg – gas formation volume factor (SI: m3 /m3 , FIELD: rb/sc f ),
or Eg – gas expansion factor (SI: m3 /m3 , FIELD: sc f /rb), or Zg – gas compressibility
factor.

Multiple undersaturated branches, if required, are specified by repeated usage of EGUST

/ BGUST / ZGUST.
Example
BGUST 1
101.32 0.02979
5000 0.029979
BGUST 1
101.32 0.014485
5000 0.014517
10000 0.01454
BGUST 1
101.32 0.0072395
5000 0.0072452
10000 0.0072482
20000 0.007249
The example specifies the gas formation volume factor for three undersaturated branches.

13.5.12. EGUST / BGUST / ZGUST 2119

Keywords for formats tN, IM, ST, GE 19.1

13.5.13. DENSITY

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword sets oil, water and gas density at standard conditions (SI: kg/m3 , FIELD:
lbm/ f t 3 ). Should be followed by the phase name (OIL, GAS or WATER) and the numeric
value.
The keyword has an E1/E3-compatible analogue DENSITY (see 12.5.33).
Example
DENSITY OIL 948.2
DENSITY WATER 1001.48

This example sets oil density equal to 948.2 and water density to 1001.48.

13.5.13. DENSITY 2120

Keywords for formats tN, IM, ST, GE 19.1

13.5.14. AQUEOUS-DENSITY

Data x tN E1 E3 IM x GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

This keyword defines the method that will be used for aqueous phase density calculation
in reservoir conditions.

The data should be entered in the following format:

*AQUEOUS-DENSITY method

Where:

• method – the method that will be used for aqueous phase density calculation. There are
two options available:

– *LINEAR – this sub-keyword indicates that the density of aqueous phase will be
based on the correlation where the water density is a linear function of pressure:

ρW = ρWre f + (1 +CW (P − Pre f )) (13.5)

Where:
ρWre f – density of pure water at standard conditions (can be specified via RHOW
(see 13.5.22) keyword);
CW – water compressibility (can be specified via CW (see 13.5.21) keyword);
P – pressure;
Pre f – reference pressure (can be specified via REFPW (see 13.5.21) keyword).
– *ROWE-CHOU – this sub-keyword indicates that Rowe-Chou correlation will be
used.
The calculation methodology is described in [43].

Default: *LINEAR.

Example
*AQUEOUS-DENSITY *ROWE-CHOU

In this example Rowe-Chou method is used for aqueous phase density calculation.

13.5.14. AQUEOUS-DENSITY 2121

Keywords for formats tN, IM, ST, GE 19.1

13.5.15. SALINITY

Data x tN E1 E3 IM x GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

This keyword defines the aqueous phase salinity.

The data should be entered in the following format:

*SALINITY units value

Where:

1. units – specifies the measurement units for salinity value. One of the following param-
eters should be specified:

• *PPMWT – this sub-keyword indicates that the value of salinity is entered in

mg(NaCl)/kg(brine).
• *PPMVOL – this sub-keyword indicates that the value of salinity is entered in
mg(NaCl)/L(brine).
• *MOLAL – this sub-keyword indicates that the value of salinity is entered in
gmol(NaCl)/kg(H2 O) (molality units).
• *MOLAR – this sub-keyword indicates that the value of salinity is entered in
gmol(NaCl)/L(brine) (molarity units).
• *WTFRAC – this sub-keyword indicates that the value of salinity is entered in
g(NaCl)/g(brine) (weight fraction).
• *MOLFRAC – this sub-keyword indicates that the value of salinity is entered in
gmol(NaCl)/gmol(brine) (mole fraction).

2. value – the salinity value.

Example
*SALINITY *PPMVOL 250000

In this example the salinity of aqueous phase is set equal to 250000 mg(NaCl)/L(brine).

13.5.15. SALINITY 2122

Keywords for formats tN, IM, ST, GE 19.1

13.5.16. GRAVITY

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword sets specific gravity of the gas relative to air (dimensionless). Should be
followed by GAS and the numeric value.
The keyword has an E1/E3-compatible analogue GRAVITY (see 12.5.34).
Example
GRAVITY GAS 0.76
This example sets gas specific gravity equal to 0.76.

13.5.16. GRAVITY 2123

Keywords for formats tN, IM, ST, GE 19.1

13.5.17. PVTAPI

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword sets PVT properties of gas in models with API tracking option, see 2.8.8.
Oil properties must be specified via the accompanying APIGRAD (see 13.5.18) keyword.
The data should be entered the following way:
*PVTAPI (BG|EG|ZG) number

The header parameters have the following meaning:

1. BG means that the gas formation volume factor will be used (EG stands for the gas
expansion factor, ZG for the 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.
Default: EG.
2. number is the number of PVT region to which the following table applies.
The table consists of arbitrary number of lines (two or more). Pressure (the first parameter)
should increase down the column.
Each line contains the following parameters:
1. pressure (SI: kPa, FIELD: psi),
2. Bg – gas formation volume factor (SI: m3 /m3 , FIELD: rb/sc f ) (or Eg – gas expansion
factor (SI: m3 /m3 , FIELD: sc f /rb), or Zg – gas compressibility factor, if EG or ZG
was specified after PVT),
3. viscosity of gas at given pressure (SI: mPa · s, FIELD: cp).
The keyword has no direct E1/E3-compatible analogue; ordinary keywords PVTG
(see 12.5.8), PVDG (see 12.5.7) are used instead.
Example
*PVTAPI 1
1000. 5.00000 0.010000
2000. 516.000 0.023600
3000. 772.000 0.028500
4000. 1028.000 0.033500
5000. 2160.000 0.058000

This example specifies PVTAPI table for the 1st PVT region.

13.5.17. PVTAPI 2124

Keywords for formats tN, IM, ST, GE 19.1

13.5.18. APIGRAD

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword sets PVT properties of oil in models with API tracking option, see 2.8.8.
Gas properties must be specified via the preceding PVTAPI (see 13.5.17) keyword. The series
of APIGRAD keywords must follow immediately after PVTAPI for the corresponding PVT
region.
The data should be entered the following way:
APIGRAD density

The header parameter has the following meaning:

1. density is the density of oil (SI: kg/m3 , FIELD: lbm/ f t 3 ). The first APIGRAD should
correspond to the density of the heavy oil component, and the last one to the density of
the light oil component.

The table consists of arbitrary number of lines (two or more). Pressure (the first parameter)
should increase down the column.
Each line contains the following 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. formation volume factor of saturated oil at the bubble point pressure (SI: m3 /m3 ,
FIELD: rb/stb),

4. viscosity of saturated oil at the bubble point pressure (SI: mPa · s, FIELD: cp; for
unsaturated branches should be specified via VOTAPI, see 13.5.20),

5. (optional) oil compressibility (for unsaturated branches should be specified via BOTAPI,
see 13.5.19),

6. (optional) gas-oil surface tension (SI, FIELD: dyne/cm).

The keyword has no direct E1/E3-compatible analogue; ordinary keywords PVTO

(see 12.5.4), PVCO (see 12.5.6) are used instead.

13.5.18. APIGRAD 2125

Keywords for formats tN, IM, ST, GE 19.1

Example
*APIGRAD 60.0
1000. 90. 1.0000 140.
2000. 157. 1.0250 100.
3000. 225. 1.0488 70.
4000. 300. 1.0730 45.
5000. 1310. 1.0980 35.

*APIGRAD 40.0
1000. 90. 1.13 1.5
2000. 450. 1.26 1.0
3000. 780. 1.38 .80
4000. 1050. 1.51 .70
5000. 1310. 1.63 .65

This example specifies APIGRAD tables for two values of oil density.

13.5.18. APIGRAD 2126

Keywords for formats tN, IM, ST, GE 19.1

13.5.19. BOTAPI

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword sets formation volume factor of oil in models with API tracking option, see
2.8.8. It refers to a particular APIGRAD (see 13.5.18) table and represents an unsaturated
branch. The first entry in the pressure column is interpreted as the bubble point pressure.
Multiple BOTAPI keywords may be defined for one APIGRAD table; they must follow in the

!
order of increasing bubble point pressure.
Instead of BOTAPI, oil compressibility may be specified via CO (see 13.5.78)
and COT (see 13.5.77). In that case BOTAPI must not be used.
The data should be entered the following way:
BOTAPI region table

The header parameters have the following meaning:

1. region is the number of PVT region to which the following table applies.

2. table is the number of APIGRAD table for the specified region to which the following
table applies.

The table consists of arbitrary number of lines (two or more). Pressure (the first parameter)
should increase down the column.
Each line contains the following parameters:

1. pressure exceeding the corresponding bubble point pressure (SI: kPa, FIELD: psi),

2. oil formation volume factor at the given pressure (SI: m3 /m3 , FIELD: rb/stb).

The keyword has no direct E1/E3-compatible analogue; ordinary keywords PVTO

(see 12.5.4), PVCO (see 12.5.6) are used instead.

13.5.19. BOTAPI 2127

Keywords for formats tN, IM, ST, GE 19.1

Example
*BOTAPI 1 1
14.70 1.0346
365.00 1.0321
865.00 1.0287
1365.00 1.0257
1929.61 1.0225
3182.53 1.0163
5123.39 1.0085
*BOTAPI 1 1
365.00 1.0660
865.00 1.0618
1365.00 1.0579
1929.61 1.0539
3182.53 1.0461
5123.39 1.0364

This example specifies oil FVF for two unsaturated branches of APIGRAD table 1 in
region 1.

13.5.19. BOTAPI 2128

Keywords for formats tN, IM, ST, GE 19.1

13.5.20. VOTAPI

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword sets oil viscosity in models with API tracking option, see 2.8.8. It refers to a
particular APIGRAD (see 13.5.18) table and represents an unsaturated branch. The first entry
in the pressure column is interpreted as the bubble point pressure. Multiple VOTAPI keywords
may be defined for one APIGRAD table; they must follow in the order of increasing bubble

!
point pressure.
Instead of VOTAPI, oil viscosity may be specified via CVO (see 13.5.80) and
VOT (see 13.5.81). In that case VOTAPI must not be used.
The data should be entered the following way:
VOTAPI region table

The header parameters have the following meaning:

1. region is the number of PVT region to which the following table applies.

2. table is the number of APIGRAD table for the specified region to which the following
table applies.

The table consists of arbitrary number of lines (two or more). Pressure (the first parameter)
should increase down the column.
Each line contains the following parameters:

1. pressure exceeding the corresponding bubble point pressure (SI: kPa, FIELD: psi),

2. oil viscosity at the given pressure (SI: mPa · s, FIELD: cp).

The keyword has no direct E1/E3-compatible analogue; ordinary keywords PVTO

(see 12.5.4), PVCO (see 12.5.6) are used instead.

13.5.20. VOTAPI 2129

Keywords for formats tN, IM, ST, GE 19.1

Example
*VOTAPI 1 1
14.70 2.3982
365.00 2.4762
865.00 2.5843
1365.00 2.6889
1929.61 2.8029
3182.53 3.0416
5123.39 3.3767
*VOTAPI 1 1
865.00 2.1701
1365.00 2.2905
1929.61 2.4231
3182.53 2.7050
5123.39 3.1102

This example specifies oil viscosity for two unsaturated branches of APIGRAD table 1 in
region 1.

13.5.20. VOTAPI 2130

Keywords for formats tN, IM, ST, GE 19.1

13.5.21. BWI / CW / REFPW / CVW / VWI

Data x tN E1 E3 x IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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 E1/E3-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.21. BWI / CW / REFPW / CVW / VWI 2131

Keywords for formats tN, IM, ST, GE 19.1

13.5.22. RHOW

Data x tN E1 E3 IM x GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

This keyword the molar water density at reservoir conditions.

The data should be entered in following format:

*RHOW value

Where

• value – the value of water density at the reference pressure (SI: gmol/rm3 , FIELD:
gmol/ f t 3 ).
The value of reference pressure can be specified via REFPW (see 13.5.21) keyword.

13.5.22. RHOW 2132

Keywords for formats tN, IM, ST, GE 19.1

13.5.23. PTYPE

Data x tN E1 E3 x IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword should be followed by one integer for every grid block specifying the PVT
region to which it belongs. This keyword should be entered after all PVT tables for all PVT
regions.

The keyword has an E1/E3-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.23. PTYPE 2133

Keywords for formats tN, IM, ST, GE 19.1

13.5.24. COMPNAME

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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 E1/E3-compatible analogue CNAMES (see 12.14.3).

In the example below there are 7 components. ”1” indicates in the table that the component
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
enabled.

Component name Water Oil Gas Solid phase

Water 1 0 1 0
Asphaltenes 0 1 0 0
Light oil 0 1 1 0
CO2 1 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.24. COMPNAME 2134

Keywords for formats tN, IM, ST, GE 19.1

13.5.25. PRSR

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

This keyword specifies the reference pressure (SI :kPa, FIELD: psi). The reference pres-
sure corresponds to the densities entered via the keywords MOLDEN (see 13.5.29), MASSDEN
(see 13.5.30), SOLID_DEN.
The reference pressure is used in the formulae 4.7, 4.12, and 4.19 (component phase density
calculations).

The keyword has an E1/E3-compatible analogues PREF (see 12.15.35), SPREF

(see 12.15.29).

Example
PRSR 101

In this example reference pressure is equal to 101.

13.5.25. PRSR 2135

Keywords for formats tN, IM, ST, GE 19.1

13.5.26. TEMR

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

This keyword specifies the reference temperature (SI: C , FIELD: F ). The reference tem-
perature corresponds to the densities entered via the keywords MOLDEN (see 13.5.29), MASS-
DEN (see 13.5.30), SOLID_DEN.
The reference temperature is used in the formulae 4.7, 4.12, 4.19 (component phase density
calculations), 4.40, 4.43, 4.48, 4.49, 4.24.

The keyword has an E1/E3-compatible analogues TREF (see 12.15.38), STREF

(see 12.15.31).

Example
TEMR 70

In this example reference temperature is equal to 101.

13.5.26. TEMR 2136

Keywords for formats tN, IM, ST, GE 19.1

13.5.27. PSURF

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword sets the standard pressure (that corresponds to surface conditions) for calcu-
lation od gas, oil, water volumes at surface conditions (SI: kPa, FIELD: psi).
Default: (SI:) 101kPa = (FIELD:) 14.65 psi.

The keyword has an E1/E3-compatible analogue STCOND (see 12.14.11).

13.5.27. PSURF 2137

Keywords for formats tN, IM, ST, GE 19.1

13.5.28. TSURF

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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 E1/E3-compatible analogue STCOND (see 12.14.11).

13.5.28. TSURF 2138

Keywords for formats tN, IM, ST, GE 19.1

13.5.29. MOLDEN

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword sets the component molar density (SI: gmol/m3 , FIELD: lbmol/ f t 3 ) at ref-
erence temperature TEMR (see 13.5.26) and reference pressure PRSR (see 13.5.25).
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 formulae 4.7, 4.12.

Component mass density (MASSDEN, see 13.5.30) is equal to the product of the compo-
nent molar density and molecular mass.

13.5.29. MOLDEN 2139

Keywords for formats tN, IM, ST, GE 19.1

13.5.30. MASSDEN

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword sets the component mass density (SI: kg/m3 , FIELD: lb/ f t 3 ) at reference
temperature TEMR (see 13.5.26) and reference pressure PRSR (see 13.5.25).
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 mass density is used in the formulae 4.7, 4.12.

Component mass density is equal to the product of the component molar density
(MOLDEN, see 13.5.29) 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.30. MASSDEN 2140

Keywords for formats tN, IM, ST, GE 19.1

13.5.31. CP

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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 calcu-
lations 4.12.
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 E1/E3-compatible analogue CREF (see 12.15.45).

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.31. CP 2141
Keywords for formats tN, IM, ST, GE 19.1

13.5.32. CT1

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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.12.
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 E1/E3-compatible analogue THERMEX1 (see 12.15.32).

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.32. CT1 2142

Keywords for formats tN, IM, ST, GE 19.1

13.5.33. CT2

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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.12.
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.15.33), which is used in tNavigator.
There is no E1/E3 compatible analogue.

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.33. CT2 2143

Keywords for formats tN, IM, ST, GE 19.1

13.5.34. CPT

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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.15.34), which is used in tNavigator.
There is no E1/E3 compatible analogue.

Example
MODEL 3 3 3 1

0.000006643 4.8977e-006 4.3512e-006

This example sets the coefficient of density dependence on temperature and pressure for
3 components (the number of components in the oil and water phases – 3-rd parameter of
MODEL, see 13.5.4).

13.5.34. CPT 2144

Keywords for formats tN, IM, ST, GE 19.1

13.5.35. PCRIT

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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 E1/E3-compatible analogue PCRIT (see 12.14.22). The difference is
that E1/E3-compatible PCRIT doesn’t 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 com-
ponents in the oil, water or gas phases – 2-nd parameter of MODEL, see 13.5.4).

13.5.35. PCRIT 2145

Keywords for formats tN, IM, ST, GE 19.1

13.5.36. TCRIT

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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 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 E1/E3-compatible analogue TCRIT (see 12.14.20). The difference is
that E1/E3-compatible TCRIT doesn’t 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.36. TCRIT 2146

Keywords for formats tN, IM, ST, GE 19.1

13.5.37. SOLID_DEN

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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.24);

2. density of component k (kg/m3 ) at reference pressure PRSR (see 13.5.25) and reference
temperature TEMR (see 13.5.26);

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 E1/E3-compatible analogues SDREF (see 12.15.28), SCREF (see 12.15.30),
STHERMX1 (see 12.15.26). For the parameter ck,pT tNavigator uses this keyword STHERMX2
(see 12.15.27).

13.5.37. SOLID_DEN 2147

Keywords for formats tN, IM, ST, GE 19.1

13.5.38. SOLID_CP

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword sets the properties of component k in the solid phase that are used in the
solid phase enthalpy calculations 4.48.

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.24);

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.15.82), SPECHT (see 12.15.83) 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.38. SOLID_CP 2148

Keywords for formats tN, IM, ST, GE 19.1

13.5.39. KVTABLIM

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword sets the pressure and temperature range for Ki (p, T ) table (here Ki (p, T )
is the partition coefficient, i.e., the ratio of mole fractions of component in vapor and liquid
phases, also known as K-value). These tables are used in the formulae of thermodynamic
equilibrium condition 4.9.
The table Ki (p, T ) is set via KVTABLE (see 13.5.40).

The following parameters are to be specified:

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 E1/E3-compatible analogues KVTEMP (see 12.15.13), KVTABTn

(see 12.15.14). tNavigator also uses the keyword KVTABLIM (see 12.15.15).

An example of use of KVTABLIM (see 13.5.39) is given in the description of the keyword
KVTABLE (see 13.5.40).

13.5.39. KVTABLIM 2149

Keywords for formats tN, IM, ST, GE 19.1

13.5.40. KVTABLE

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword sets the table Ki (p, T ) (here Ki (p, T ) is the ratio of mole fractions of compo-
nent in vapor and liquid phases, also known as K-value). These tables are used in the formulae
of thermodynamic equilibrium condition 4.9.
The pressure and temperature range for Ki (p, T ) table is set via KVTABLIM (see 13.5.39).

The keyword has an E1/E3-compatible analogues KVTEMP (see 12.15.13), KVTABTn

(see 12.15.14). tNavigator also uses the keyword KVTABLIM (see 12.15.15).

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.24)
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 lin-
early 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.40. KVTABLE 2150

Keywords for formats tN, IM, ST, GE 19.1

13.5.41. KV1 / KV2 / KV3 / KV4 / KV5

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

These keywords specify the coefficients of the correlation formula ( 4.22):

Ki (p, T ) = (Ai + Bi /p +Ci p) · e−Di /(T −Ei ) (13.6)

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 13.5.4)
should be specified.

The keywords have an E1/E3-compatible analogue KVCR (see 12.15.11). 1-st parameter of
KVCR (see 12.15.11) 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.41. KV1 / KV2 / KV3 / KV4 / KV5 2151

Keywords for formats tN, IM, ST, GE 19.1

13.5.42. CPL1 / CPL2 / CPL3 / CPL4

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

These keywords specify the coefficients in the component liquid enthalpy calculations
( 4.41):
4
1
Hc,O (T ) = ∑ CPi,c (T − Tre f )i
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.5∗1.05506/0.453592∗1.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
MODEL, see 13.5.4) should be specified.

The keywords CPL1, CPL2 have an E1/E3-compatible analogues SPECHA (see 12.15.73),
SPECHB (see 12.15.74). tNavigator also uses the keywords CP3,c = SPECHC (see 12.15.75),
CP4,c = SPECHD (see 12.15.76).

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.42. CPL1 / CPL2 / CPL3 / CPL4 2152

Keywords for formats tN, IM, ST, GE 19.1

13.5.43. CPG1 / CPG2 / CPG3 / CPG4

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

These keywords specify the coefficients in the component gas enthalpy calculations ( 4.45):
4
1
Hc,G (T ) = hc,G + ∑ CPi,c (T − Tre f )i
i=1 i
where the coefficients:
hc,G – HVAPR (see 13.5.44),
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.43)

Default values: hc,G = 0.25Btu/lb/F = 0.25∗1.05506/0.453592∗1.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
MODEL, see 13.5.4) should be specified.

The keywords CPG1, CPG2 have an E1/E3-compatible analogues SPECHG (see 12.15.77),
SPECHH (see 12.15.78). tNavigator also uses the keywords CP3,c = SPECHI (see 12.15.79),
CP4,c = SPECHJ (see 12.15.80).

Example
CPG1
0.0066 0.0052
CPG2
0.00071 0.00054
CPG3
0.000062 0.000046
CPG4
0.0000055 0.0000078

In this example the coefficients of component gas enthalpy formula are specified for 2
components.

13.5.43. CPG1 / CPG2 / CPG3 / CPG4 2153

Keywords for formats tN, IM, ST, GE 19.1

13.5.44. HVAPR

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

This keyword specifies the coefficients in the component gas enthalpy calculations ( 4.45):
4
1
Hc,G (T ) = hc,G + ∑ CPi,c (T − Tre f )i
i=1 i

where the coefficients:

hc,G – HVAPR (see 13.5.44),
CP1,c – CPG1 (kJ/kg/◦ C),
CP2,c – CPG2 (kJ/kg/◦C2 ),
CP3,c – CPG3 (kJ/kg/◦C3 ),
CP4,c – CPG4 (kJ/kg/◦C4 ).
(CPG1 / CPG2 / CPG3 / CPG4, see 13.5.43)

Default values: hc,G = 0.25Btu/lb/F = 0.25∗1.05506/0.453592∗1.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 num-
ber of components in the oil or water phases (3-rd parameter of MODEL, see 13.5.4) should
be specified.

The keyword has an E1/E3-compatible analogue HEATVAPS (see 12.15.81).

Example
HVAPR 3*

In this example the coefficients hc,G of component gas enthalpy formula are specified on
default for 3 components.

13.5.44. HVAPR 2154

Keywords for formats tN, IM, ST, GE 19.1

13.5.45. HVR

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

These keywords specify the coefficients in the vaporization enthalpy calculations ( 4.42):

HVc (T ) = Ac · (1 − T /Tc,crit )Bc = A0c (Tc,crit − T )Bc , A0c = Ac /Tc,crit

Bc

where the coefficients:

A0c – HVR (kJ/mol/C ),
Bc – EV (see 13.5.46).
Default values A0c = 0.25Btu/lbmol/F = 0.25∗1.05506/0.453592∗1.8kJ/mol/C = 1.0467kJ/mol/C ,
Bc = 0.38.
Critical temperature of the component Tc,crit is specified via TCRIT (see 13.5.36).
If HVc (T ) = 0 then T ≥ Tc,crit .

After each keyword HVR and EV (see 13.5.46) one should specify the same number of co-
efficients 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 E1/E3-compatible analogue HEATVAP (see 12.15.20).

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.45. HVR 2155

Keywords for formats tN, IM, ST, GE 19.1

13.5.46. EV

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

These keywords specify the coefficients in the vaporization enthalpy calculations ( 4.42):

HVc (T ) = Ac · (1 − T /Tc,crit )Bc = A0c (Tc,crit − T )Bc , A0c = Ac /Tc,crit

Bc

where the coefficients:

A0c – HVR (see 13.5.45) (kJ/mol/C ),
Bc – EV.
Default values A0c = 0.25Btu/lbmol/F = 0.25∗1.05506/0.453592∗1.8kJ/mol/C = 1.0467kJ/mol/C ,
Bc = 0.38.
Critical temperature of the component Tc,crit is specified via TCRIT (see 13.5.36).
If HVc (T ) = 0 then T ≥ Tc,crit .

After each keyword HVR (see 13.5.45) and EV one should specify the same number of co-
efficients 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 E1/E3-compatible analogue HEATVAPE (see 12.15.21).

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.46. EV 2156
Keywords for formats tN, IM, ST, GE 19.1

13.5.47. STOREAC

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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.48), STOREAC (see 13.5.47), FREQFAC
(see 13.5.49), RENTH (see 13.5.53) 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 equal to the number of components
including water (first parameter of MODEL, see 13.5.4). If the component isn’t the reactant of
the reaction one should enter zero.
The keyword has an E1/E3-compatible analogue STOREAC (see 12.15.67).

For the chemical reaction

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 isn’t 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.47. STOREAC 2157

Keywords for formats tN, IM, ST, GE 19.1

13.5.48. STOPROD

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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.

The number of reaction (for which all properties are specified) is not set explicitly. So
for first reaction all keywords STOPROD (see 13.5.48), STOREAC (see 13.5.47), FREQFAC
(see 13.5.49), RENTH (see 13.5.53) 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 equal to the number of components
including water (first parameter of MODEL, see 13.5.4). If the component isn’t the product of
the reaction one should enter zero.
The keyword has an E1/E3-compatible analogue STOPROD (see 12.15.66).

For the chemical reaction

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 isn’t 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.48. STOPROD 2158

Keywords for formats tN, IM, ST, GE 19.1

13.5.49. FREQFAC

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword sets the reaction rate constant Ar of each chemical reaction. 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.48), STOREAC (see 13.5.47), FREQFAC
(see 13.5.49), RENTH (see 13.5.53) etc. should appear as a group. Then for second reaction
all these keywords should appear, for third reaction, etc.

The keyword has an E1/E3-compatible analogue REACRATE (see 12.15.60).

Example
FREQFAC 0.0000038
In this example reaction rate constant is equal to 0.0000038.

13.5.49. FREQFAC 2159

Keywords for formats tN, IM, ST, GE 19.1

13.5.50. FREQFACP

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword sets reaction rate constant 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 constant at corresponding
pressure are specified. 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.48), STOREAC (see 13.5.47), FREQFAC
(see 13.5.49), RENTH (see 13.5.53) etc.). Then for second reaction all these keywords should
appear, for third reaction, etc. Pressure values must be increasing.

The keyword has an E1/E3-compatible analogue REACRATE (see 12.15.60).

Example
FREQFACP
100 0.0000038
120 0.0000041
In the example the table of pressure-dependent reaction rate constant is specified.

13.5.50. FREQFACP 2160

Keywords for formats tN, IM, ST, GE 19.1

13.5.51. EACT

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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 number of reaction (for which all properties are specified) is not set explicitly. So
for first reaction all keywords STOPROD (see 13.5.48), STOREAC (see 13.5.47), FREQFAC
(see 13.5.49), RENTH (see 13.5.53) etc. should appear as a group. Then for second reaction
all these keywords should appear, for third reaction, etc.

The keyword has an E1/E3-compatible analogue REACACT (see 12.15.61).

Example
EACT 18400
In this example activation energy is equal to 18400 J/gmol .

13.5.51. EACT 2161

Keywords for formats tN, IM, ST, GE 19.1

13.5.52. EACT_TAB

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword sets activation energy of reactions values dependence on temperature.

The following parameters should be specified:

• 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.51) and EACT_TAB are absent, then reaction is
independable 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.52. EACT_TAB 2162

Keywords for formats tN, IM, ST, GE 19.1

13.5.53. RENTH

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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 STOPROD (see 13.5.48), STOREAC (see 13.5.47), FREQFAC
(see 13.5.49), RENTH (see 13.5.53) etc. should appear as a group. Then for second reaction
all these keywords should appear, for third reaction, etc.

The keyword has an E1/E3-compatible analogue REACENTH (see 12.15.70).

Example
EACT 15200
In this example reaction enthalpy is equal to 15200 J/gmol .

13.5.53. RENTH 2163

Keywords for formats tN, IM, ST, GE 19.1

13.5.54. RORDER

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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.

The number of reaction (for which all properties are specified) is not set explicitly. So
for first reaction all keywords STOPROD (see 13.5.48), STOREAC (see 13.5.47), FREQFAC
(see 13.5.49), RENTH (see 13.5.53) 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 equal to the number of components
including water (first parameter of MODEL, see 13.5.4). If the reaction rate doesn’t depend of
the component concentration one should enter zero.
The keyword has an E1/E3-compatible analogues REACCORD (see 12.15.62), REACSORD
(see 12.15.69).

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.54. RORDER 2164

Keywords for formats tN, IM, ST, GE 19.1

13.5.55. RPHASE

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword sets the component phase in each chemical reaction. 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.48), STOREAC (see 13.5.47), FREQFAC
(see 13.5.49), RENTH (see 13.5.53) 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).
The values could be the following:

• 0 component doesn’t 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 E1/E3-compatible analogue REACPHA (see 12.15.68).

Example
RPHASE 0 0 2 3 3 4

In this example there are 6 components. 1-st and 2-nd component doesn’t react, 3-rd
component reacts in oil phase, 4-th and 5-th – gas phase, 6-th – solid phase.

13.5.55. RPHASE 2165

Keywords for formats tN, IM, ST, GE 19.1

13.5.56. RTEMUPR

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword sets the maximal temperature Tu (SI: C , FIELD: F ), which is used in the
reaction rate calculations 4.68. 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.48), STOREAC (see 13.5.47), FREQFAC
(see 13.5.49), RENTH (see 13.5.53) etc. should appear as a group. Then for second reaction
all these keywords should appear, for third reaction, etc.

The keyword has an E1/E3-compatible analogue REACLIMS (see 12.15.63).

Example
RTEMUPR 230

In this example the maximal temperature is equal to 230 ◦ C.

13.5.56. RTEMUPR 2166

Keywords for formats tN, IM, ST, GE 19.1

13.5.57. RTEMLOWR

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword sets the minimal temperature Tl (SI: C , FIELD: F ), which is used in the
reaction rate calculations 4.68. 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.48), STOREAC (see 13.5.47), FREQFAC
(see 13.5.49), RENTH (see 13.5.53) etc. should appear as a group. Then for second reaction
all these keywords should appear, for third reaction, etc.

The keyword has an E1/E3-compatible analogue REACLIMS (see 12.15.63).

Example
RTEMLOWR 120

In this example the minimal temperature is equal to 120 ◦ C.

13.5.57. RTEMLOWR 2167

Keywords for formats tN, IM, ST, GE 19.1

13.5.58. RXCRITCON

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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.68. 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.48), STOREAC (see 13.5.47), FREQFAC
(see 13.5.49), RENTH (see 13.5.53) etc. should appear as a group. Then for second reaction
all these keywords should appear, for third reaction, etc.

The data should be entered in the following format:

• 'component name';

• critical value of concentration.

The keyword has an analogue REACCONC (see 12.15.64), which is used in tNavigator.
There is no E1/E3 compatible analogue.

Example
RXCRITCON 'comp1' 0.00022

In this example the critical value of comp1 concentration is equal to 0.00022.

13.5.58. RXCRITCON 2168

Keywords for formats tN, IM, ST, GE 19.1

13.5.59. O2PP

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword sets that the gas partial pressure will be used in calculations of c0ri in the
formula 4.70. The keyword O2PP is used only for components in gas phase (if the 'component
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 number of reaction (for which all properties are specified) is not set explicitly. So
for first reaction all keywords STOPROD (see 13.5.48), STOREAC (see 13.5.47), FREQFAC
(see 13.5.49), RENTH (see 13.5.53) etc. should appear as a group. Then for second reaction
all these keywords should appear, for third reaction, etc.

The keyword is analogous to GPP in E1/E3-compatible keyword REACPHA (see 12.15.68).

Example
O2PP

In this example in calculations of c0ri will be used oxygen partial pressure.

13.5.59. O2PP 2169

Keywords for formats tN, IM, ST, GE 19.1

13.5.60. VSTYPE

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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.61)
is allowed.
Default: all grid blocks belong to one region.

The keyword is analogous to VISCNUM (see 12.4.19), 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.60. VSTYPE 2170

Keywords for formats tN, IM, ST, GE 19.1

13.5.61. VISCTYPE

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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.66), BVISC (see 13.5.67), VISCTABLE
(see 13.5.68), VSMIXCOMP (see 13.5.69), VSMIXCOMP (see 13.5.69), VSMIXFUNC
(see 13.5.71), AVG (see 13.5.72), BVG (see 13.5.73).

The keyword VSTYPE (see 13.5.60) 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.61. VISCTYPE 2171

Keywords for formats tN, IM, ST, GE 19.1

13.5.62. VISCOR

Data x tN E1 E3 IM x GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword sets type of correlation to calculate hydrocarbon phase viscosities. The fol-
lowing parameters should be specified:

1. correlation type:

• HZYT – Herning and Zipperer and Yoon and Thodos correlation formulae;
• PEDERSEN – Pedersen correlation (keyword PEDERSEN, see 12.14.65).

Example
VISCOR HZYT

13.5.62. VISCOR 2172

Keywords for formats tN, IM, ST, GE 19.1

13.5.63. VISVC

Data x tN E1 E3 IM x GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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 (SI: m3 /kg.M , SI: f t 3 /lb.M ).

This keyword has an E1/E3 compatible analogue VCRITVIS (see 12.14.26).

Example
VISVC 5.350000E-01 5.340000E-01 4.320000E-01 3.890000E-01

13.5.63. VISVC 2173

Keywords for formats tN, IM, ST, GE 19.1

13.5.64. VISCOEFF

Data x tN E1 E3 IM x GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword sets correlation coefficients. If PEDERSEN is set in VISCOR (see 13.5.62),
then this keyword sets Pedersen correlation coefficients; otherwise, Lorenz-Bray-Clark (LBC-
COEF, see 12.14.44) correlation coefficients are set. The following parameters should be
specified:

1. 5 coefficients.

This keyword has E1/E3-compatible analogs PEDTUNE (see 12.14.66) and LBCCOEF
(see 12.14.44).
Example
VISCOEFF 1 1 1.847 0.5173 7.378E-3

13.5.64. VISCOEFF 2174

Keywords for formats tN, IM, ST, GE 19.1

13.5.65. MIXVC

Data x tN E1 E3 IM x GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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.65. MIXVC 2175

Keywords for formats tN, IM, ST, GE 19.1

13.5.66. AVISC

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

This keyword specifies coefficients in water and oil viscosity correlation formulae AW
( 4.28) and A0k ( 4.30).
BW and B0k are specified via BVISC (see 13.5.67).

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.

Different values can be entered for different viscosity regions (see an example in the de-
scription of VISCTYPE, see 13.5.61).

In E3 data format the coefficients of correlations are set via OILVISCC (see 12.15.55).
Grabovski correlation is used in water viscosity calculations 4.27.
Example
AVISC 0.4 0.5 0.6
BVISC 12 18 20

In this example correlation coefficients are specified for 3 components.

13.5.66. AVISC 2176

Keywords for formats tN, IM, ST, GE 19.1

13.5.67. BVISC

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

This keyword specifies coefficients in water and oil viscosity correlation formulae BW
( 4.28) and B0k ( 4.30).
AW and A0k are specified via AVISC (see 13.5.66).

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.

Different values can be entered for different viscosity regions (see an example in the de-
scription of VISCTYPE, see 13.5.61).

In E3 data format the coefficients of correlations are set via OILVISCC (see 12.15.55).
Grabovski correlation is used in water viscosity calculations 4.27.
Example
AVISC 0.4 0.5 0.6
BVISC 12 18 20

In this example correlation coefficients are specified for 3 components.

13.5.67. BVISC 2177

Keywords for formats tN, IM, ST, GE 19.1

13.5.68. VISCTABLE

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

This keyword specifies the table viscosity-versus-temperature dependence (water viscos-

ity – 4.28, oil viscosity – 4.30).
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))

Different values can be entered for different viscosity regions (see an example in the de-
scription of VISCTYPE, see 13.5.61).

In E3 data format water viscosity as a function of temperature is specified via the keyword
WATVISCT (see 12.15.53), oil viscosity – OILVISCT (see 12.15.54).
Example 1.

13.5.68. VISCTABLE 2178

Keywords for formats tN, IM, ST, GE 19.1

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.68. VISCTABLE 2179

Keywords for formats tN, IM, ST, GE 19.1

13.5.69. VSMIXCOMP

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

This keyword specifies the function fk (x) (which is used in oil viscosity calculations –
4.30).

Function fk (x) should be specified via 3 keywords:

• VSMIXCOMP (see 13.5.69): 'component name';

• VSMIXENDP (see 13.5.70): minimal and maximum values of x (in a range from 0 to
1);

• VSMIXFUNC (see 13.5.71): 11 values of fk (x).

Different values can be entered for different viscosity regions (see an example in the de-
scription of VISCTYPE, see 13.5.61).

The keyword has an E1/E3-compatible analogue OILVINDX (see 12.15.56). tNavigator also
uses the keyword OILVINDT (see 12.15.57).

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.69. VSMIXCOMP 2180

Keywords for formats tN, IM, ST, GE 19.1

13.5.70. VSMIXENDP

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

This keyword specifies the function fk (x) (which is used in oil viscosity calculations –
4.30).

Function fk (x) should be specified via 3 keywords:

• VSMIXCOMP (see 13.5.69): 'component name';

• VSMIXENDP (see 13.5.70): minimal and maximum values of x (in a range from 0 to
1);

• VSMIXFUNC (see 13.5.71): 11 values of fk (x).

Different values can be entered for different viscosity regions (see an example in the de-
scription of VISCTYPE, see 13.5.61).

The keyword has an E1/E3-compatible analogue OILVINDX (see 12.15.56). tNavigator also
uses the keyword OILVINDT (see 12.15.57).

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.70. VSMIXENDP 2181

Keywords for formats tN, IM, ST, GE 19.1

13.5.71. VSMIXFUNC

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

This keyword specifies the function fk (x) (which is used in oil viscosity calculations –
4.30).

Function fk (x) should be specified via 3 keywords:

• VSMIXCOMP (see 13.5.69): 'component name';

• VSMIXENDP (see 13.5.70): minimal and maximum values of x (in a range from 0 to
1);

• VSMIXFUNC (see 13.5.71): 11 values of fk (x).

Different values can be entered for different viscosity regions (see an example in the de-
scription of VISCTYPE, see 13.5.61).

The keyword has an E1/E3-compatible analogue OILVINDX (see 12.15.56). tNavigator also
uses the keyword OILVINDT (see 12.15.57).

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.71. VSMIXFUNC 2182

Keywords for formats tN, IM, ST, GE 19.1

13.5.72. AVG

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

This keyword specifies coefficients Ak in gas viscosity correlation formulae 4.33.

Bk are specified via BVG (see 13.5.73).

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.

Different values can be entered for different viscosity regions (see an example in the de-
scription of VISCTYPE, see 13.5.61).

In E3 data format the coefficients of correlations are set via GASVISCF (see 12.15.59).
Example
AVG 0.00022 0.00017
BVG 0.8 0.7

In this example correlation coefficients are specified for 2 components.

13.5.72. AVG 2183

Keywords for formats tN, IM, ST, GE 19.1

13.5.73. BVG

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

This keyword specifies coefficients Bk in gas viscosity correlation formulae 4.33.

Ak are specified via AVG (see 13.5.72).

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.

Different values can be entered for different viscosity regions (see an example in the de-
scription of VISCTYPE, see 13.5.61).

In E3 data format the coefficients of correlations are set via GASVISCF (see 12.15.59).
Example
AVG 0.00022 0.00017
BVG 0.8 0.7

In this example correlation coefficients are specified for 2 components.

13.5.73. BVG 2184

Keywords for formats tN, IM, ST, GE 19.1

13.5.74. CMM

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword specifies component molecular weight (SI: kg/gmol , FIELD: lb/lbmol ),
which is used in gas viscosity calculations 4.34
The same number of values as the number of components (1-st parameter of MODEL,
see 13.5.4) should be specified.

In E3 data format molecular weight of hydrocarbon components is specified via the key-
word MW (see 12.14.30), 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.74. CMM 2185

Keywords for formats tN, IM, ST, GE 19.1

13.5.75. GASD-ZCOEF

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

This keyword specifies the method of gas density calculations. Navigator supports implicit
method only.
Parameter IMPLICIT should be specified after the keyword.

13.5.75. GASD-ZCOEF 2186

Keywords for formats tN, IM, ST, GE 19.1

13.5.76. GASLIQKV

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword announces the tables of K-values to manage gas-liquid phase equilibration.
These tables are specified by keywords KVTABLIM (see 13.5.39) and KVTABLE (see 13.5.40).
The keyword has an E1/E3-compatible analogue KVTABLE (see 12.14.19).
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.76. GASLIQKV 2187

Keywords for formats tN, IM, ST, GE 19.1

13.5.77. COT

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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 ))

The following parameters should be specified:

• 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 parameters:

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.79) 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.77) sets oil compressibility dependence on
pressure in the 1-st PVT region.

13.5.77. COT 2188

Keywords for formats tN, IM, ST, GE 19.1

13.5.78. CO

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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 )).

The following parameters should be specified:

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.77) it is available to set oil compressibility dependence on
pressure. The keyword BOT (see 13.5.79) 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.78) oil compressibility value for pressure
values greater than bubble pressure is set. It is equal to 9.2810 ×10−6 /psi.

13.5.78. CO 2189
Keywords for formats tN, IM, ST, GE 19.1

13.5.79. BOT

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword sets oil formation volume factor, Bo , dependence on pressure, P, and on
bubble pressure Pbub in particular.
The following parameters should be specified:

• in the same line with the keyword:

1. oil compressibility PVT region number.

• in the following lines table is specified. Each line 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. 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.79) sets oil formation volume factor depen-
dence on pressure.

13.5.79. BOT 2190

Keywords for formats tN, IM, ST, GE 19.1

13.5.80. CVO

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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.
The following parameters should be specified:

1. oil viscosity value (SI: mPa · s/kPa, FIELD: cp/psi).

The keyword VOT (see 13.5.81) allows to set oil viscosity dependence on pressure explic-
itly, as a table.
Example
CVO 4.6000E-5
In the example oil viscosity value is 4.6000 ×10−5 .

13.5.80. CVO 2191

Keywords for formats tN, IM, ST, GE 19.1

13.5.81. VOT

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword sets oil viscosity dependence on pressure, on bubble pressure in particular,
as a table.
The following parameters should be specified:

• in the same line with the keyword:

1. oil viscosity PVT region.

• in the following lines table is set. Each line should contain the following parameters:

1. pressure (SI: kPa, FIELD: psi). The first value in this column is bubble pressure
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.81) sets oil viscosity dependence on pressure.
Bubble pressure Pbub – the first value in the first column – is 32.2 psi.

13.5.81. VOT 2192

Keywords for formats tN, IM, ST, GE 19.1

13.5.82. IDEALGAS

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword specifies that gas-phase density is obtained from the ideal gas law.
Note. Only one of IDEALGAS (see 13.5.82) and PCRIT (see 13.5.35) can be specified in
the model.
Example
IDEALGAS

13.5.82. IDEALGAS 2193

Keywords for formats tN, IM, ST, GE 19.1

13.5.83. EOSSET

Data x tN E1 E3 IM x GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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 PCRIT

(see 13.5.35), TCRIT (see 13.5.36), BIN (see 13.5.85), PCHOR (see 13.5.86), AC (see 13.5.87),
OMEGA (see 13.5.88), OMEGB (see 13.5.88), VSHIFT (see 13.5.89) and others).
Example
EOSSET 1
...

13.5.83. EOSSET 2194

Keywords for formats tN, IM, ST, GE 19.1

13.5.84. EOSTYPE

Data x tN E1 E3 IM x GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword should be followed by one integer for every grid block specifying the equa-
tion of state region (EoS region) to which it belongs.
This keyword has an E1/E3 compatible analogue EOSNUM (see 12.4.20).
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.84. EOSTYPE 2195

Keywords for formats tN, IM, ST, GE 19.1

13.5.85. BIN

Data x tN E1 E3 IM x GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword sets interaction coefficients for user components. The following parameters
should be specified:

1. interaction coefficient. nuser·(2·nc−1−nuser)

2 numbers should be specified. nc is the total
number of components, nuser the total number of user components.

This keyword has an E1/E3 compatible analogue BIC (see 12.14.40).

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.85. BIN 2196

Keywords for formats tN, IM, ST, GE 19.1

13.5.86. PCHOR

Data x tN E1 E3 IM x GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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 num-

ber of user components in the model should be entered.

This keyword has an E1/E3 compatible analogue PARACHOR (see 12.6.80).

Example
PCHOR 74.92 192.74 390.4 /
In the example parachors are entered for 3 user components.

13.5.86. PCHOR 2197

Keywords for formats tN, IM, ST, GE 19.1

13.5.87. AC

Data x tN E1 E3 IM x GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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 E1/E3 compatible analogue ACF (see 12.14.38).

Example
AC 0.225 0.132 0.385
In the example acentric factor values for 3 components are set.

13.5.87. AC 2198
Keywords for formats tN, IM, ST, GE 19.1

13.5.88. OMEGA / OMEGB

Data x tN E1 E3 IM x GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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 E1/E3-compatible analogs OMEGAA (see 12.14.42) and OMEGAB
(see 12.14.42).
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.88. OMEGA / OMEGB 2199

Keywords for formats tN, IM, ST, GE 19.1

13.5.89. VSHIFT

Data x tN E1 E3 IM x GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

This keyword sets the volume shifts that will be applied to the EoS molar volumes.

The data should be entered in the following format:

*VSHIFT shi f t_v

Where:

• shi f t_v – volume shift value. It is a dimensionless parameter.

nc values should be specified for nc number of model components.
If the temperature-dependent volume shift model is initialized (VSHIF1, see 13.5.90),
then shi f t_v would correspond to correction at reference temperature (TREFVS,
see 13.5.91).
Default: 0.

This keyword has an E3 compatible analogue SSHIFT (see 12.14.50).

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.89. VSHIFT 2200

Keywords for formats tN, IM, ST, GE 19.1

13.5.90. VSHIF1

Data x tN E1 E3 IM x GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

This keyword sets the linear temperature-dependent volume shifts that will be applied to
the EoS molar volumes.
The reference temperatures for temperature-dependent correction can be specified via key-
word TREFVS (see 13.5.91).

The data should be entered in the following format:

*VSHIF1 shi f t_v1

Where:

• shi f t_v – temperature gradients for volume shifts (SI: ◦1C ; FIELD: ◦1F ).
nc values should be specified for nc number of model components.
Default: 0.

This keyword is an analogue of the keyword VSHIF1 (see 12.14.52) used by tNavigator.

Example
*VSHIFT 0.019066 -0.44122 -0.51069 -0.100732 -0.119513

*VSHIF1 0.000513 -0.000023 -0.000045 -0.000069 -0.000081

*TREFVS 120.0 120.0 120.0 120.0 120.0

In this example:

• Volume shift values at reference temperature are defined via *VSHIFT for 5 components.

• Temperature gradients for volume shifts are defined via *VSHF1 keyword for 5 compo-
nents.

• Reference temperatures are defined via *TREFVS keyword for 5 components.

13.5.90. VSHIF1 2201

Keywords for formats tN, IM, ST, GE 19.1

13.5.91. TREFVS

Data x tN E1 E3 IM x GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

This keyword sets the reference temperatures for linear temperature-dependent volume
shift model.
The temperature gradient for temperature-dependent correction can be specifies via keyword
VSHIF1 (see 13.5.90).

The data should be entered in the following format:

*TREFVS tre f _vs

Where:

• tre f _vs – temperature gradients for volume shifts (SI: ◦ C, FIELD: ◦ F).
nc values should be specified for nc number of model components.
Default: SI: 15.56 ◦ C, FIELD: 60 ◦ F.

This keyword is an analogue of the keyword TREFVS (see 12.14.53) used by tNavigator.

Example
*VSHIFT 0.019066 -0.44122 -0.51069 -0.100732 -0.119513

*VSHIF1 0.000513 -0.000023 -0.000045 -0.000069 -0.000081

*TREFVS 120.0 120.0 120.0 120.0 120.0

In this example:

• Volume shift values at reference temperature are defined via *VSHIFT for 5 components.

• Temperature gradients for volume shifts are defined via *VSHF1 keyword for 5 compo-
nents.

• Reference temperatures are defined via *TREFVS keyword for 5 components.

13.5.91. TREFVS 2202

Keywords for formats tN, IM, ST, GE 19.1

13.5.92. VGUST

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword sets gas viscosity table dependence on pressure for condensate undersaturated
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.92. VGUST 2203

Keywords for formats tN, IM, ST, GE 19.1

13.5.93. PADSORP

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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 IM format.
This keyword has an E1/E3 compatible analogue PLYADS (see 12.8.26).
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.93. PADSORP 2204

Keywords for formats tN, IM, ST, GE 19.1

13.5.94. PPERM

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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).

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 IM format.
Example
PPERM
10.0 0.3 0.15 0.9 1.2
10000. 0.2 0.1 0.999 1.2

13.5.94. PPERM 2205

Keywords for formats tN, IM, ST, GE 19.1

13.5.95. PMIX

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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:
1.1. ratio of local polymer concentration to the reference one (the keyword PREF-
CONC, see 13.5.96);
1.2. ratio of polymer viscosity to water viscosity.
• VELTABLE – tables of viscosity dependence on velocity and polymer concentration
are set. In the next lines the following is set:
1.1. VWT vv – sub-keyword VWT and velocity value vv. One table corresponds to
each value (see description of the following parameter);
1.2. table which is analogous to the one from the TABLE parameter.

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 IM format.
Example
PMIX LINEAR

13.5.95. PMIX 2206

Keywords for formats tN, IM, ST, GE 19.1

13.5.96. PREFCONC

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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.

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 IM format.
Example
PREFCONC 3.3

13.5.96. PREFCONC 2207

Keywords for formats tN, IM, ST, GE 19.1

13.5.97. PVISC

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

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.96) (SI: mPa-s; FIELD: cp).

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 IM format.
Example
PVISC 1.1

13.5.97. PVISC 2208

Keywords for formats tN, IM, ST, GE 19.1

13.5.98. INCOMP

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

The keyword sets polymer concentration in injecting phase. The following parameters
should be specified:

1. phase in which polymer is injecting:

• WATER – water.

2. polymer concentration in the phase (SI: kg/m3 ; FIELD: lb/ST B).

Default: 0.

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 IM format.
This keyword has an E1/E3 compatible analogue WPOLYMER (see 12.19.174).
Example
INCOMP WATER 1.1

13.5.98. INCOMP 2209

Keywords for formats tN, IM, ST, GE 19.1

13.5.99. DIFFUSION

Data x tN E1 E3 IM x GE ST MO
format
Input Reservoir Other x Component
Section
Rockfluid Initial Numerical Well

This keyword activates the gas diffusion option in fractured reservoir and specifies the
required for this option parameters. Diffusion is not included by default in calculation of the
matrix-fracture molecular fluxes.
The keyword is followed by parameters:

• t is the tortuosity of the porous medium. A positive real number defining a tortuosity
in porous media. Tortuosity is the ratio of the true path length traveled by a particle
flowing through the medium to the macroscopic distance measured from the first and
last point of this path. A standard measured value of tortuosity is equal to 1.5. The value
of tortuosity can be used as an adjustable parameter for matching transfer rates. Large
values of tortuosity result in decrease of rate at which gas flows due to diffusion;
Default: 1.

• Vector of diffusion coefficients dk (cm2 /sec) containing nc positive real numbers (nc
is the number of hydrocarbon components). Coefficients have the same units in all
unit system used for calculations. True molecular diffusivities may be specified, how-
ever these coefficients may be used as adjustable parameters for reproducing observed
transfer rates.
Default: 0, for k = 1, .., nc .

If the diffusion effect is taken into account all parameters (the tortuosity and diffusion
coefficients).
The keyword DIFFUSION should be specified after keywords MODEL (see 13.5.4) and NC
(see 13.5.5).
Using DIFFUSION gas phase diffusion term is included into the molecular flux between
a fracture block and its collocated matrix block. The gas phase diffusion rate (mol/day) for
component k from block i to collocated block j is calculated as:

rate = (Area/Separation) × dk /t × phi × Sg × (C(k, gas, i) −C(gas, j))

where

• Area is the contact area between blocks i and j ;

• Separation is the distance between blocks i and j ;

• phi is the porosity of the matrix block;

13.5.99. DIFFUSION 2210

Keywords for formats tN, IM, ST, GE 19.1

• Sg is the smaller of the gas saturations in blocks i and j ;

• C(k, gas, i) is the concentration of component k in the gas phase of block i (moles per
unit volume of the gas phase);

• C(k, gas, j) is the concentration of component k in the gas phase of block j .

Values of molecular diffusivities vary with temperature, pressure (via molar density) and
molecular weight. At low pressure diffusivities is directly proportional to o the square root
of the Kelvin temperature, inversely proportional to pressure, and inversely proportional to
the square root of the molecular weight. At high pressure, which are typical of reservoir
conditions, the dependencies become more complicated and cannot be simply characterized.
Example
*NC 9 9
...
*DIFFUSION 1.0 6.4e-05 6.4e-05 6.4e-05 6.4e-05 6.4e-05 6.4e-05
6.4e-05 6.4e-05 6.4e-05
In this example the tortuosity is set to 1 and 9 diffusion coefficients are set to 6.4e-05.

13.5.99. DIFFUSION 2211

Keywords for formats tN, IM, ST, GE 19.1

13.6. Rock-Fluid data

13.6.1. ROCKFLUID

Data x tN E1 E3 x IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

The keyword starts the ”Rock-Fluid data” section (13.6).

Example
ROCKFLUID

13.6. Rock-Fluid data 2212

Keywords for formats tN, IM, ST, GE 19.1

13.6.2. RPT

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

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.5)
and liquid-gas (SLT, see 13.6.6) permeability tables are entered. Then RTYPE (see 13.6.11)
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;

• LININTERP – the Linear Isoperm model (see section 4.35.3). This option is analogous
to LINEAR_ISOPERM of the keyword KROIL (see 13.6.3).

In the description of the keyword SLT (see 13.6.6) there is a common example for the
keywords RPT, SWT (see 13.6.5) and SLT (see 13.6.6).

13.6.2. RPT 2213

Keywords for formats tN, IM, ST, GE 19.1

13.6.3. KROIL

Data x tN E1 E3 x IM x GE ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

This keyword indicates how oil relative permeability krO is evaluated. In the line with the
keyword the following models can be specified:

• STONE1 – the Stone’s First model. Optionally you can specify:

– SWSG – krOW is a function of water saturation SW and krOG is a function of gas

saturation SG .

• STONE2 – the Stone’s Second model. Optionally you can specify:

– SWSG – krOW is a function of water saturation SW and krOG is a function of gas

saturation SG .

• LINEAR_ISOPERM – the Linear Isoperm model (see section 4.35.3). This option is
analogous to LININTERP of the keyword RPT (see 13.6.2);

• SEGREGATED – the Segregated model (see section 4.35.3).

If KROIL is specified with no following option, the default option is STONE2.

13.6.3. KROIL 2214

Keywords for formats tN, IM, ST, GE 19.1

13.6.4. KROGCG

Data x tN E1 E3 x IM x GE ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

The keyword sets krOG (Cg ) – value of oil relative permeability at connate gas saturation
in each grid block.
The same number of values as the number of grid blocks should be entered.
Detailed description of phase relative permeabilities scaling is in the section 4.35.2.
This keyword has an E1/E3-compatible analogue KRO (see 12.6.58).
This keyword should be entered after the keywords SWT (see 13.6.5) and/or SLT
(see 13.6.6).

13.6.4. KROGCG 2215

Keywords for formats tN, IM, ST, GE 19.1

13.6.5. SWT

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

This keyword defines water-oil relative permeability table for one saturation region, pre-
viously specified by RPT (see 13.6.2) keyword. If more than one rock type is defined, this
keyword must be defined for each PRT keyword.

The data should be entered in the following format:

*SWT *SMOOTHNED method *SWTKRTHR value
SW KrW KrOW PcOW PcOWi

Where:
1. The data entered in the first line:

• *SMOOTHEND – this is an optional sub-keyword. It has tNavigator special ana-

logue – the keyword KRSMOOTH (see 12.6.89).
This sub-keyword activates an option to smooth table RP values via several inter-
polation types.
• method – interpolation method that will be used for RP table smoothening:
– *LINEAR or *OFF – linear interpolation;
– *QUAD – quadratic interpolation;
– *CUBIC – cubic interpolation.
Default:
– In IM and GE types models – *QUAD;

– In ST types models – *LINEAR.

• *SWTKRTHR – this is an optional sub-keyword.
It activates an option for krWO and krOW end-point specification.
• value – a threshold value for krWO and krOW end-point specification.
– ε is the threshold value. If a tabular value for krWO and krOW is less than
or equal to ε then permeability is set to 0. In this case critical water saturation
can be changed. If the entered threshold value is out of region [5 · 10−16 ,
5 · 10−7 ] then its value will be replaced by the value 5 · 10−16 , if the threshold
value is smaller than 5 · 10−16 or by 5 · 10−7 , if the threshold value is larger
than 5 · 10−7 .
Default: ε is equal to 5 · 10−7 . .

13.6.5. SWT 2216

Keywords for formats tN, IM, ST, GE 19.1

2. The data entered in the table. One collumn is assigned to each parameter:

• SW – water saturation.
• KrW – water relative permeability (krwo function in 2.6)
• KrOW – oil relative permeability (krow function in 2.6)
• PcOW – oil-water capillary pressure (SI: kPa, FIELD: psi) (Pcow function
in 2.11.2).
This is an optional collumn.
• PcOWi – oil-water capillary pressure on imbibition curve (SI: kPa, FIELD: psi).
This is an optional collumn.
The methodology for capillary pressure hysteresis calculations is described in sec-
tion 2.7.4. The list of avaliable hysteresis keywords compatible with IM/GE/ST
format is provided in section 2.7.6.

This keyword has an E1/E3-compatible analogue SWOF (see 12.6.1).

Example
*RPT 1
*SWT *SMOOTHEND *OFF
** sw krw krow pcow pcowi
0.08 0.000 1.000 70.0 70.0
0.10 0.000 0.962 59.2 41.2
0.14 0.001 0.889 47.6 15.6
0.20 0.008 0.783 36.2 4.8
0.28 0.021 0.649 25.4 -1.7
0.32 0.032 0.585 21.6 -4.0
0.36 0.046 0.524 18.5 -6.4
0.40 0.064 0.464 16.2 -8.3
0.44 0.085 0.407 14.4 -10.4
0.56 0.175 0.252 11.3 -17.7
0.60 0.216 0.207 10.8 -23.3
0.64 0.262 0.164 10.4 -33.4
0.68 0.314 0.125 10.2 -50.0
0.82 0.609 0.020 10.0 -50.0
0.86 0.804 0.000 10.0 -50.0
0.90 1.000 0.000 10.1 -50.0

in this example:

• *SWT table is set for saturation region 1.

• 5th collumn indicated the input of capillary pressure imbibition curve and, hence, trig-
gers the hysteresis calculations.

13.6.5. SWT 2217

Keywords for formats tN, IM, ST, GE 19.1

13.6.6. SLT

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

This keyword defines gas-liquid relative permeability table for one saturation region, pre-
viously specified by RPT (see 13.6.2) keyword. If more than one rock type is defined, this
keyword must be defined for each PRT keyword.
For this keyword the argument of the table’s function is liqud saturation.

The data should be entered in the following format:

*SLT *SMOOTHNED method *SLTKRTHR value
SL KrG KrOG PcOG PcOGi

1. The data entered in the first line:

• *SMOOTHEND – this is an optional sub-keyword. It has tNavigator special ana-
logue – the keyword KRSMOOTH (see 12.6.89).
This sub-keyword activates an option to smooth table RP values via several inter-
polation types.
• method – interpolation method that will be used for RP table smoothening:
– *LINEAR or *OFF – linear interpolation;
– *QUAD – quadratic interpolation;
– *CUBIC – cubic interpolation.
Default:
– In IM types models – *QUAD;

– In ST types models – *LINEAR.

• *SLTKRTHR – this is an optional sub-keyword.
It activates an option for krg and krog end-point determination.
• value – a threshold value for krg and krog end-point determination.
– ε is the threshold value. If a tabular value for krwo and krow is less than or
equal to ε then permeability is set to 0. In this case critical water saturation
can be changed. If the entered threshold value is out of region [5 · 10−16 ,
5 · 10−7 ] then its value will be replaced by the value 5 · 10−16 , if the threshold
value is smaller than 5 · 10−16 or by 5 · 10−7 , if the threshold value is larger
than 5 · 10−7 .
Default: ε is equal to 5 · 10−7 . .

13.6.6. SLT 2218

Keywords for formats tN, IM, ST, GE 19.1

2. The data entered in the table. One collumn is assigned to each parameter:

• SL – liquid saturation.
• KrG – gas relative permeability (krgo function in 2.6)
• KrOG – oil relative permeability (krog function in 2.6)
• PcOG – gas-oil capillary pressure (SI: kPa, FIELD: psi) (Pcog function in 2.11.2).
This is an optional collumn.
• PcOGi – gas-oil capillary pressure on imbibition curve (SI: kPa, FIELD: psi).
This is an optional collumn.
The methodology for capillary pressure hysteresis calculations is described in sec-
tion 2.7.4. The list of avaliable hysteresis kewords compatible with IM/GE/ST
format is provided in section 2.7.6.

This keyword has an E1/E3-compatible analogue SGOF (see 12.6.2).

Example
*RPT 1
*SLT *SMOOTHEND *OFF
** sl krg krog pcog
0.08 1.00 0.00 0.00
0.30 0.94 0.00 0.00
0.40 0.87 0.01 0.00
0.50 0.72 0.02 0.00
0.55 0.60 0.03 0.00
0.60 0.41 0.05 0.00
0.70 0.19 0.09 0.00
0.75 0.12 0.20 0.00
0.80 0.07 0.35 0.00
0.88 0.02 0.70 0.00
0.95 0.00 0.98 0.00
1.00 0.00 1.00 0.00

In this example:

• *SLT table is set for saturation region 1.

• 5th column is not specified, hence capillary pressure hysteresis option will not be
applied in this saturation region.

13.6.6. SLT 2219

Keywords for formats tN, IM, ST, GE 19.1

13.6.7. SGT

Data x tN E1 E3 x IM x GE ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

This keyword defines gas-oil relative permeability table for one saturation region, pre-
viously specified by RPT (see 13.6.2) keyword. If more than one rock type is defined, this
keyword must be defined for each PRT keyword.
For this keyword the argument of the table’s function is gas saturation.

The data should be entered in the following format:

*SGT *SMOOTHNED method *SLTKRTHR value
SG KrG KrOG PcOG PcOGi

1. The data entered in the first line:

• *SMOOTHEND – this is an optional sub-keyword. It has tNavigator special ana-
logue – the keyword KRSMOOTH (see 12.6.89).
This sub-keyword activates an option to smooth table RP values via several inter-
polation types.
• method – interpolation method that will be used for RP table smoothening:
– *LINEAR or *OFF – linear interpolation;
– *QUAD – quadratic interpolation;
– *CUBIC – cubic interpolation.
Default:
– In IM types models – *QUAD;

– In ST types models – *LINEAR.

• *SLTKRTHR – this is an optional sub-keyword.
It activates an option for krg and krog end-point determination.
• value – a threshold value for krg and krog end-point determination.
– ε is the threshold value. If a tabular value for krwo and krow is less than or
equal to ε then permeability is set to 0. In this case critical water saturation
can be changed. If the entered threshold value is out of region [5 · 10−16 ,
5 · 10−7 ] then its value will be replaced by the value 5 · 10−16 , if the threshold
value is smaller than 5 · 10−16 or by 5 · 10−7 , if the threshold value is larger
than 5 · 10−7 .
Default: ε is equal to 5 · 10−7 . .

13.6.7. SGT 2220

Keywords for formats tN, IM, ST, GE 19.1

2. The data entered in the table. One collumn is assigned to each parameter:

• SG – gas saturation.
• KrG – gas relative permeability (krgo function in 2.6)
• KrOG – oil relative permeability (krog function in 2.6)
• PcOG – gas-oil capillary pressure (SI: kPa, FIELD: psi) (Pcog function in 2.11.2).
This is an optional collumn.
• PcOGi – gas-oil capillary pressure on imbibition curve (SI: kPa, FIELD: psi).
This is an optional collumn.
The methodology for capillary pressure hysteresis calculations is described in sec-
tion 2.7.4. The list of avaliable hysteresis kewords compatible with IM/GE/ST
format is provided in section 2.7.6.

This keyword has an E1/E3-compatible analogue SGOF (see 12.6.2).

Example
*RPT 1
*SGT *SMOOTHEND *OFF
** sg krg krog pcog
0.00 0.00 1.00 0.00
0.05 0.00 0.98 0.00
0.12 0.02 0.70 0.00
0.20 0.07 0.35 0.00
0.25 0.12 0.20 0.00
0.30 0.19 0.09 0.00
0.40 0.41 0.05 0.00
0.45 0.60 0.03 0.00
0.50 0.72 0.02 0.00
0.60 0.87 0.01 0.00
0.70 0.94 0.00 0.00
0.92 1.00 0.00 0.00

In this example:

• *SGT table is set for saturation region 1.

• 5th column is not specified, hence capillary pressure hysteresis option will not be
applied in this saturation region.

13.6.7. SGT 2221

Keywords for formats tN, IM, ST, GE 19.1

13.6.8. JFUNC

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

This keyword indicates that capillary pressures will be calculated according to Leverett
J-Function. This keyword defines parameters for whole reservoir.

Calculation algorithm for Leverett J-Function is provided in the section 2.11.5.

The data should be entered in the following format:

*JFUNC phase_ f lag

• phase_ f lag can be one of the following:

– *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.
Default: *BOTH.

This keyword has an E1/E3-compatible analog JFUNC (see 12.2.63).

Example
*JFUNC *WATER

In this example only oil-water capillary pressure will be scaled according to J-function.

13.6.8. JFUNC 2222

Keywords for formats tN, IM, ST, GE 19.1

13.6.9. SRFTNW

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

This keyword is used for J-function calculation and defines water-oil surface tension (in
dynes/cm) for each grid block (STW in equation 2.89).

The data should be entered for each block according to IM/GE/ST Data entry system.

! To use this keyword, the J-function option must be activated via JFUNC
(see 13.6.8) keyword with the parameter *WATER or *BOTH.

Example
*SRFTNW *ALL
3*1 0.637 2*1 2*0.736 1

In this example different PcOW values are defined for the blocks .

13.6.9. SRFTNW 2223

Keywords for formats tN, IM, ST, GE 19.1

13.6.10. SRFTNG

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

This keyword is used for J-function calculation and defines gas-oil surface tension (in
dynes/cm) for each grid block (STG in equation 2.89).

The data should be entered for each block according to IM/GE/ST Data entry system.

! To use this keyword, the J-function option must be activated via JFUNC
(see 13.6.8) keyword with the parameter *GAS or *BOTH.
The data should be entered for each block according to IM/GE/ST Data entry system.

Example
*SRFTNG *CON
12.2

In this example the same PcOG value is defined for all blocks of the grid .

13.6.10. SRFTNG 2224

Keywords for formats tN, IM, ST, GE 19.1

13.6.11. RTYPE

Data x tN E1 E3 x IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

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.5), SLT (see 13.6.6) for all saturation function
regions.

The keyword has an E1/E3-compatible analogue SATNUM (see 12.4.3).

The keyword also has ST compatible analogue KRTYPE (see 13.6.12).
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.11. RTYPE 2225

Keywords for formats tN, IM, ST, GE 19.1

13.6.12. KRTYPE

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

This keyword is a full analog of RTYPE (see 13.6.11).

13.6.12. KRTYPE 2226

Keywords for formats tN, IM, ST, GE 19.1

13.6.13. KRTEMTAB

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

The keyword specifies temperature dependence for critical saturations and endpoints. This
keyword should be entered after the keywords SWT (see 13.6.5), SLT (see 13.6.6). 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.14),
SWCRIT (see 13.6.16), SOIRW (see 13.6.18), SGCON (see 13.6.20), SGR (see 13.6.22),
SOIRG (see 13.6.24), SORW (see 13.6.26), SORG (see 13.6.28), KRWIRO (see 13.6.30),
KRGCW (see 13.6.32), KROCW (see 13.6.34), PCGEND (see 13.6.36), PCWEND
(see 13.6.38).

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 E1/E3-compatible analogue ENPTVT (see 12.15.85).

Detailed description of phase relative permeabilities scaling is in the section 4.35.2.

The keywords in the list above (SWR (see 13.6.14), SWCRIT (see 13.6.16) etc), specify
properties in whole saturation table region. To specify properties in each grid block, use the
keywords BSWR (see 13.6.15), BSWCRIT (see 13.6.17), BSOIRW (see 13.6.19), BSGCON
(see 13.6.21), BSGR (see 13.6.23), BSOIRG (see 13.6.25), BSORW (see 13.6.27), BSORG
(see 13.6.29), BKRWIRO (see 13.6.31), BKRGCW (see 13.6.33), BKROCW (see 13.6.35),
BPCGMAX (see 13.6.37), BPCWMAX (see 13.6.39).

13.6.13. KRTEMTAB 2227

Keywords for formats tN, IM, ST, GE 19.1

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.13. KRTEMTAB 2228

Keywords for formats tN, IM, ST, GE 19.1

13.6.14. SWR

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

The keyword sets SW L – minimal value of water saturation SW for one saturation table
region (RPT, see 13.6.2).

Detailed description of phase relative permeabilities scaling is in the section 4.35.2.

The keyword is analogous to the 2-nd parameter of E1/E3 compatible keyword ENPTVT
(see 12.15.85).

This keyword is used with KRTEMTAB (see 13.6.13); in the description of KRTEMTAB
(see 13.6.13) 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.15).

13.6.14. SWR 2229

Keywords for formats tN, IM, ST, GE 19.1

13.6.15. BSWR

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

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.

Detailed description of phase relative permeabilities scaling is in the section 4.35.2.

This keyword has an E1/E3-compatible analogue SWL (see 12.6.26).

This keyword should be entered after the keywords SWT (see 13.6.5), SLT (see 13.6.6),
KRTEMTAB (see 13.6.13).

To specify properties in whole saturation table region (not in each grid block), use the
keyword SWR (see 13.6.14).

13.6.15. BSWR 2230

Keywords for formats tN, IM, ST, GE 19.1

13.6.16. SWCRIT

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

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).

Detailed description of phase relative permeabilities scaling is in the section 4.35.2.

The keyword is analogous to the 3-rd parameter of E1/E3 compatible keyword ENPTVT
(see 12.15.85).

This keyword is used with KRTEMTAB (see 13.6.13); in the description of KRTEMTAB
(see 13.6.13) there is an example of theirs usage.

To specify properties in each grid block (not in saturation point region), use the keyword
BSWCRIT (see 13.6.17).

13.6.16. SWCRIT 2231

Keywords for formats tN, IM, ST, GE 19.1

13.6.17. BSWCRIT

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

The keyword sets SWCR – maximal (critical) value of water saturation SW (for which
krW (SW ) = 0) in each grid block.
The same number of values as the number of grid blocks should be entered.

Detailed description of phase relative permeabilities scaling is in the section 4.35.2.

This keyword has an E1/E3-compatible analogue SWCR (see 12.6.29).

This keyword should be entered after the keywords SWT (see 13.6.5), SLT (see 13.6.6),
KRTEMTAB (see 13.6.13).

To specify properties in whole saturation table region (not in each grid block), use the
keyword SWCRIT (see 13.6.16).

13.6.17. BSWCRIT 2232

Keywords for formats tN, IM, ST, GE 19.1

13.6.18. SOIRW

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

The keyword sets SWU – maximal value of water saturation SW for one saturation table
region (RPT, see 13.6.2).

Detailed description of phase relative permeabilities scaling is in the section 4.35.2.

The keyword is analogous to the 4-th parameter of E1/E3 compatible keyword ENPTVT
(see 12.15.85).

This keyword is used with KRTEMTAB (see 13.6.13); in the description of KRTEMTAB
(see 13.6.13) there is an example of theirs usage.

To specify properties in each grid block (not in saturation point region), use the keyword
BSOIRW (see 13.6.19).

13.6.18. SOIRW 2233

Keywords for formats tN, IM, ST, GE 19.1

13.6.19. BSOIRW

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

The keyword sets SWU – maximal value of water saturation SW in each grid block.
The same number of values as the number of grid blocks should be entered.

Detailed description of phase relative permeabilities scaling is in the section 4.35.2.

This keyword has an E1/E3-compatible analogue SWU (see 12.6.33).

This keyword should be entered after the keywords SWT (see 13.6.5), SLT (see 13.6.6),
KRTEMTAB (see 13.6.13).

To specify properties in whole saturation table region (not in each grid block), use the
keyword SOIRW (see 13.6.18).

13.6.19. BSOIRW 2234

Keywords for formats tN, IM, ST, GE 19.1

13.6.20. SGCON

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

The keyword sets SGL – minimal value of gas saturation SG for one saturation table region
(RPT, see 13.6.2).

Detailed description of phase relative permeabilities scaling is in the section 4.35.2.

The keyword is analogous to the 5-th parameter of E1/E3 compatible keyword ENPTVT
(see 12.15.85).

This keyword is used with KRTEMTAB (see 13.6.13); in the description of KRTEMTAB
(see 13.6.13) there is an example of theirs usage.

To specify properties in each grid block (not in saturation point region), use the keyword
BSGCON (see 13.6.21).

13.6.20. SGCON 2235

Keywords for formats tN, IM, ST, GE 19.1

13.6.21. BSGCON

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

The keyword sets SGL – minimal value of gas saturation SG in each grid block.
The same number of values as the number of grid blocks should be entered.

Detailed description of phase relative permeabilities scaling is in the section 4.35.2.

This keyword has an E1/E3-compatible analogue SGL (see 12.6.28).

This keyword should be entered after the keywords SWT (see 13.6.5), SLT (see 13.6.6),
KRTEMTAB (see 13.6.13).

To specify properties in whole saturation table region (not in each grid block), use the
keyword SGCON (see 13.6.20).

13.6.21. BSGCON 2236

Keywords for formats tN, IM, ST, GE 19.1

13.6.22. SGR

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

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).

Detailed description of phase relative permeabilities scaling is in the section 4.35.2.

The keyword is analogous to the 6-th parameter of E1/E3 compatible keyword ENPTVT
(see 12.15.85).

This keyword is used with KRTEMTAB (see 13.6.13); in the description of KRTEMTAB
(see 13.6.13) there is an example of theirs usage.

To specify properties in each grid block (not in saturation point region), use the keyword
BSGR (see 13.6.23).

13.6.22. SGR 2237

Keywords for formats tN, IM, ST, GE 19.1

13.6.23. BSGR

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

The keyword sets SGCR – maximal (critical) value of gas saturation SG (for which
krG (SG ) = 0) in each grid block.
The same number of values as the number of grid blocks should be entered.

Detailed description of phase relative permeabilities scaling is in the section 4.35.2.

This keyword has an E1/E3-compatible analogue SGCR (see 12.6.30).

This keyword should be entered after the keywords SWT (see 13.6.5), SLT (see 13.6.6),
KRTEMTAB (see 13.6.13).

To specify properties in whole saturation table region (not in each grid block), use the
keyword SGR (see 13.6.22).

13.6.23. BSGR 2238

Keywords for formats tN, IM, ST, GE 19.1

13.6.24. SOIRG

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

The keyword sets SGU – maximal value of gas saturation SG for one saturation table
region (RPT, see 13.6.2).

Detailed description of phase relative permeabilities scaling is in the section 4.35.2.

The keyword is analogous to the 7-th parameter of E1/E3 compatible keyword ENPTVT
(see 12.15.85).

This keyword is used with KRTEMTAB (see 13.6.13); in the description of KRTEMTAB
(see 13.6.13) there is an example of theirs usage.

To specify properties in each grid block (not in saturation point region), use the keyword
BSOIRG (see 13.6.25).

13.6.24. SOIRG 2239

Keywords for formats tN, IM, ST, GE 19.1

13.6.25. BSOIRG

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

The keyword sets SGU – maximal value of gas saturation SG in each grid block.
The same number of values as the number of grid blocks should be entered.

Detailed description of phase relative permeabilities scaling is in the section 4.35.2.

This keyword has an E1/E3-compatible analogue SGU (see 12.6.34).

This keyword should be entered after the keywords SWT (see 13.6.5), SLT (see 13.6.6),
KRTEMTAB (see 13.6.13).

To specify properties in whole saturation table region (not in each grid block), use the
keyword SOIRG (see 13.6.24).

13.6.25. BSOIRG 2240

Keywords for formats tN, IM, ST, GE 19.1

13.6.26. SORW

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

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).

Detailed description of phase relative permeabilities scaling is in the section 4.35.2.

The keyword is analogous to the 8-th parameter of E1/E3 compatible keyword ENPTVT
(see 12.15.85).

This keyword is used with KRTEMTAB (see 13.6.13); in the description of KRTEMTAB
(see 13.6.13) there is an example of theirs usage.

To specify properties in each grid block (not in saturation point region), use the keyword
BSORW (see 13.6.27).

13.6.26. SORW 2241

Keywords for formats tN, IM, ST, GE 19.1

13.6.27. BSORW

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

The keyword sets SOWCR – maximal (critical) value of the function SO = 1 − SW − SGL ,
for which krOW (SW ) = 0 in each grid block.
The same number of values as the number of grid blocks should be entered.

Detailed description of phase relative permeabilities scaling is in the section 4.35.2.

This keyword has an E1/E3-compatible analogue SOWCR (see 12.6.31).

This keyword should be entered after the keywords SWT (see 13.6.5), SLT (see 13.6.6),
KRTEMTAB (see 13.6.13).

To specify properties in whole saturation table region (not in each grid block), use the
keyword SORW (see 13.6.26).

13.6.27. BSORW 2242

Keywords for formats tN, IM, ST, GE 19.1

13.6.28. SORG

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

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).

Detailed description of phase relative permeabilities scaling is in the section 4.35.2.

The keyword is analogous to the 9-th parameter of E1/E3 compatible keyword ENPTVT
(see 12.15.85).

This keyword is used with KRTEMTAB (see 13.6.13); in the description of KRTEMTAB
(see 13.6.13) there is an example of theirs usage.

To specify properties in each grid block (not in saturation point region), use the keyword
BSORG (see 13.6.29).

13.6.28. SORG 2243

Keywords for formats tN, IM, ST, GE 19.1

13.6.29. BSORG

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

The keyword sets SOGCR – maximal (critical) value of the function SO = 1 − SG − SW L ,

for which krOG (SG ) = 0 in each grid block.
The same number of values as the number of grid blocks should be entered.

Detailed description of phase relative permeabilities scaling is in the section 4.35.2.

This keyword has an E1/E3-compatible analogue SOGCR (see 12.6.32).

This keyword should be entered after the keywords SWT (see 13.6.5), SLT (see 13.6.6),
KRTEMTAB (see 13.6.13).

To specify properties in whole saturation table region (not in each grid block), use the
keyword SORG (see 13.6.28).

13.6.29. BSORG 2244

Keywords for formats tN, IM, ST, GE 19.1

13.6.30. KRWIRO

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

The keyword sets krW max – maximal value of water relative permeability krW (SW ) for one
saturation table region (RPT, see 13.6.2).

Detailed description of phase relative permeabilities scaling is in the section 4.35.2.

The keyword is analogous to the 2-nd parameter of E1/E3 compatible keyword ENKRVT
(see 12.15.86).

This keyword is used with KRTEMTAB (see 13.6.13); in the description of KRTEMTAB
(see 13.6.13) there is an example of theirs usage.

To specify properties in each grid block (not in saturation point region), use the keyword
BKRWIRO (see 13.6.31).

13.6.30. KRWIRO 2245

Keywords for formats tN, IM, ST, GE 19.1

13.6.31. BKRWIRO

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

The keyword sets krW max – maximal value of water relative permeability krW (SW ) in each
grid block.
The same number of values as the number of grid blocks should be entered.

Detailed description of phase relative permeabilities scaling is in the section 4.35.2.

This keyword has an E1/E3-compatible analogue KRW (see 12.6.59).

This keyword should be entered after the keywords SWT (see 13.6.5), SLT (see 13.6.6),
KRTEMTAB (see 13.6.13).

To specify properties in whole saturation table region (not in each grid block), use the
keyword KRWIRO (see 13.6.30).

13.6.31. BKRWIRO 2246

Keywords for formats tN, IM, ST, GE 19.1

13.6.32. KRGCW

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

The keyword sets krGmax – maximal value of gas relative permeability krG (SG ) for one
saturation table region (RPT, see 13.6.2).

Detailed description of phase relative permeabilities scaling is in the section 4.35.2.

The keyword is analogous to the 3-rd parameter of E1/E3 compatible keyword ENKRVT
(see 12.15.86).

This keyword is used with KRTEMTAB (see 13.6.13); in the description of KRTEMTAB
(see 13.6.13) there is an example of theirs usage.

To specify properties in each grid block (not in saturation point region), use the keyword
BKRGCW (see 13.6.33).

13.6.32. KRGCW 2247

Keywords for formats tN, IM, ST, GE 19.1

13.6.33. BKRGCW

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

The keyword sets krGmax – maximal value of gas relative permeability krG (SG ) in each
grid block.
The same number of values as the number of grid blocks should be entered.

Detailed description of phase relative permeabilities scaling is in the section 4.35.2.

This keyword has an E1/E3-compatible analogue KRG (see 12.6.60).

This keyword should be entered after the keywords SWT (see 13.6.5), SLT (see 13.6.6),
KRTEMTAB (see 13.6.13).

To specify properties in whole saturation table region (not in each grid block), use the
keyword KRGCW (see 13.6.32).

13.6.33. BKRGCW 2248

Keywords for formats tN, IM, ST, GE 19.1

13.6.34. KROCW

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

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).

Detailed description of phase relative permeabilities scaling is in the section 4.35.2.

The keyword is analogous to the 4-th parameter of E1/E3 compatible keyword ENKRVT
(see 12.15.86).

This keyword is used with KRTEMTAB (see 13.6.13); in the description of KRTEMTAB
(see 13.6.13) there is an example of theirs usage.

To specify properties in each grid block (not in saturation point region), use the keyword
BKROCW (see 13.6.35).

13.6.34. KROCW 2249

Keywords for formats tN, IM, ST, GE 19.1

13.6.35. BKROCW

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

The keyword sets krOmax – maximal value of oil relative permeability (functions krOW (SW )
and krOG (SG )) in each grid block.
The same number of values as the number of grid blocks should be entered.

Detailed description of phase relative permeabilities scaling is in the section 4.35.2.

This keyword has an E1/E3-compatible analogue KRO (see 12.6.58).

This keyword should be entered after the keywords SWT (see 13.6.5), SLT (see 13.6.6),
KRTEMTAB (see 13.6.13).

To specify properties in whole saturation table region (not in each grid block), use the
keyword KROCW (see 13.6.34).

13.6.35. BKROCW 2250

Keywords for formats tN, IM, ST, GE 19.1

13.6.36. PCGEND

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

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).

Detailed description of phase relative permeabilities scaling is in the section 4.35.2.

The keyword is analogous to the 2-nd parameter of E1/E3 compatible keyword ENPCVT
(see 12.15.87).

This keyword is used with KRTEMTAB (see 13.6.13); in the description of KRTEMTAB
(see 13.6.13) there is an example of theirs usage.

To specify properties in each grid block (not in saturation point region), use the keyword
BPCGMAX (see 13.6.37).

13.6.36. PCGEND 2251

Keywords for formats tN, IM, ST, GE 19.1

13.6.37. BPCGMAX

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

The keyword sets PCGmax – maximal value of gas capillary pressure PcOG (SG ) (SI: kPa,
FIELD: psi) in each grid block.
The same number of values as the number of grid blocks should be entered.

Detailed description of phase relative permeabilities scaling is in the section 4.35.2.

This keyword has an E1/E3-compatible analogue PCG (see 12.6.63).

This keyword should be entered after the keywords SWT (see 13.6.5), SLT (see 13.6.6),
KRTEMTAB (see 13.6.13).

To specify properties in whole saturation table region (not in each grid block), use the
keyword PCWEND (see 13.6.38). PCGEND (see 13.6.36).

13.6.37. BPCGMAX 2252

Keywords for formats tN, IM, ST, GE 19.1

13.6.38. PCWEND

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

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).

Detailed description of phase relative permeabilities scaling is in the section 4.35.2.

The keyword is analogous to the 3-rd parameter of E1/E3 compatible keyword ENPCVT
(see 12.15.87).

This keyword is used with KRTEMTAB (see 13.6.13); in the description of KRTEMTAB
(see 13.6.13) there is an example of theirs usage.

To specify properties in each grid block (not in saturation point region), use the keyword
BPCWMAX (see 13.6.39).

13.6.38. PCWEND 2253

Keywords for formats tN, IM, ST, GE 19.1

13.6.39. BPCWMAX

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

The keyword sets PCW max – maximal value of water capillary pressure PcOW (SW ) (SI:
kPa, FIELD: psi) in each grid blocks.
The same number of values as the number of grid blocks should be entered.

Detailed description of phase relative permeabilities scaling is in the section 4.35.2.

This keyword has an E1/E3-compatible analogue PCW (see 12.6.62).

This keyword should be entered after the keywords SWT (see 13.6.5), SLT (see 13.6.6),
KRTEMTAB (see 13.6.13).

To specify properties in whole saturation table region (not in each grid block), use the
keyword PCWEND (see 13.6.38).

13.6.39. BPCWMAX 2254

Keywords for formats tN, IM, ST, GE 19.1

13.6.40. EPSPC

Data x tN E1 E3 x IM x GE ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

This keyword defines the curvature parameter for oil-water capillary pressure hysteresis.

The algorithms for capillary pressure hysteresis calculations are described in Capillary
pressure hysteresis section.

The list of avaliable hysteresis kewords compatible with IM/GE/ST format is provided in
Hysteresis definition in IM/GE/ST format section.

The data should be entered in the following format:

*EPSPC value

Where:

• value – the value which determines the transition between imbibition and drainage
curves for oil-water capillary pressure.
This is a dimensionless parameter which has a value in the range from 0.005 to 0.1.

This keyword is an analogue of the EPS parameter of the keywords HYSTPCW

(see 12.6.72) and HYSTPCWR (see 12.6.73) that are used by tNavigator.

Example
*EPSPC 0.023

13.6.40. EPSPC 2255

Keywords for formats tN, IM, ST, GE 19.1

13.6.41. EPSPCG

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

This keyword defines the curvature parameter for gas-oil capillary pressure hysteresis.

The algorithms for capillary pressure hysteresis calculations are described in Capillary
pressure hysteresis section.

The list of avaliable hysteresis kewords compatible with IM/GE/ST format is provided in
Hysteresis definition in IM/GE/ST format section.

The data should be entered in the following format:

*EPSPCG value

Where:

• value – the value which determines the transition between imbibition and drainage
curves for gas-oil capillary pressure.
This is a dimensionless parameter which has a value in the range from 0.005 to 0.1.

This keyword is an analogue of the EPS parameter of the keywords HYSTPCG

(see 12.6.72) and HYSTPCGR (see 12.6.73) that are used by tNavigator.

Example
*EPSPCG 0.032

13.6.41. EPSPCG 2256

Keywords for formats tN, IM, ST, GE 19.1

13.6.42. SWTI

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

This keyword defines water-oil imbibition table for relative permeabilities. If more than
one rock type is defined, different SWTI tables may be assigned tor each RPT keyword.

This table is mandotory for Killough’s hysteresis option.

If the parameters *SMOOTHEND and *SWTKRTHR options were previously defined in

SWT (see 13.6.5) keyword, they would be applied for the SWTI table as well.

The algorithms for relative permeability hysteresis calculations are described in Relative
permeability hysteresis in the non-wetting phase and Relative permeability hysteresis in the
wetting phase sections.

The list of avaliable hysteresis kewords compatible with IM/GE/ST format is provided in
Hysteresis definition in IM/GE/ST format section.

The data should be entered in the following format:

*SWTI (*KROWI_ONLY | *KRWI_ONLY)
SW KrOWi KrWi

Where:

1. The data entered in the first line:

• *KROWI_ONLY – optional parameter.

This sub-keyword indicates that *SWTI table contains only two columns: SW and
KrOWi ;
• *KRWI_ONLY – optional parameter.
This sub-keyword indicates that *SWTI table contains only two columns: SW and
KrWi .

2. The data entered in the table:

• SW – water saturation;
• KrOWi – Imbibition OIL relative permeability in oil-water system;
• KrWi – Imbibition WATER relative permeability in oil-water system.

13.6.42. SWTI 2257

Keywords for formats tN, IM, ST, GE 19.1

Example
*RPT 1
... ... ...
*SWTI
** Sw Krowi Krwi
0.08 1.000 0.000
0.12 0.871 0.000
0.14 0.810 0.002
0.20 0.640 0.016
0.28 0.444 0.052
0.36 0.284 0.110
0.44 0.160 0.189
0.51 0.072 0.285
0.60 0.017 0.408
0.68 0.000 0.550

In this example *SWTI table is set for saturation region 1.

13.6.42. SWTI 2258

Keywords for formats tN, IM, ST, GE 19.1

13.6.43. HYSKRO

Data x tN E1 E3 x IM x GE ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

This keyword defines the method of oil relative permeability hysteresis calculations in
oil-water systems.

The algorithms for relative permeability hysteresis calculations are described in Relative
permeability hysteresis in the non-wetting phase and Relative permeability hysteresis in the
wetting phase sections.

The list of avaliable hysteresis kewords compatible with IM/GE/ST format is provided in
Hysteresis definition in IM/GE/ST format section.

The data should be entered in one of the following formats:

I. First data input format

*HYSKRO *CARLSON SOrmax

Where:
1. *CARLSON – This sub-keyword defines Carlson’s hysteresis method;
This sub-keyword can be omitted if SOrmax is specified. In this case Carlson’s hysteresis
method will be assumed automatically by the simulator.
2. SOrmax – the maximum possible residual Oil saturation.

II. Second data input format

*HYSKRO *KILLOUGH *HYEXO exp_value

Where:
1. *KILLOUGH – This sub-keyword defines Killough’s hysteresis method for relative per-
meability.
In order to implement this option correctly, water-oil imbibition RP table SWTI
(see 13.6.42) table must be defined as well;
2. *HYEXO – optional parameter.
This sub-keyword indicates that the exponent of Killough’s hysteresis equation will be
used.

13.6.43. HYSKRO 2259

Keywords for formats tN, IM, ST, GE 19.1

3. exp_value – the value of the exponent of Killough’s saturation interpolation equation.

Default: 1.5.

This keyword is an analogue of the keywords HYSTKROW (see 12.6.70) and HYS-
TKROWR (see 12.6.71) that are used by tNavigator.

Example
*SWTI
** Sw Krowi Krwi
0.08 1.000 0.000
0.12 0.871 0.000
0.14 0.810 0.002
0.20 0.640 0.016
0.28 0.444 0.052
0.36 0.284 0.110
0.44 0.160 0.189
0.51 0.072 0.285
0.60 0.017 0.408
0.68 0.000 0.550
...
*HYSKRO *KILLOUGH *HYEXO 2.0

In this example:

• The hysteresis for Oil Relative Permeabilies is set via *HYSKRO keyword.

• Killough’s hysteresis method for Relative Permeability is set via *KILLOUGH sub-
keyword.

• Killough’s saturation interpolation method is set via *HYEXO sub-keyword.

the value of the exponent of Killough’s saturation interpolation equation is set equal to
2.0.

• Previously, oil-water Imbibition table was defined via *SWTI keyword.

This definition is mandatory for Killough’s hysteresis method.

13.6.43. HYSKRO 2260

Keywords for formats tN, IM, ST, GE 19.1

13.6.44. SORMAX

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

This keyword defines the maximum residual oil saturation during Imbibition process in oil-
water systems. This end point formulation is applied only for the blocks that utilize hysteresis
option, triggered by HYSKRO (see 13.6.43) keyword.
The algorithms for relative permeability hysteresis calculations are described in Relative
permeability hysteresis in the non-wetting phase and Relative permeability hysteresis in the
wetting phase sections.

The list of avaliable hysteresis kewords compatible with IM/GE/ST format is provided in
Hysteresis definition in IM/GE/ST format section.

The data should be entered in the following format:

*SORMAX blocks_array SOrmax

Where:

• blocks_array – Definition of block array for which the property will be assigned. The
detailed description of avaliable input options is provided in Data entry system section.

• SOrmax – the maximum possible Imbibition residual oil saturation.

This keyword is an analogue of the SPTMAX parameter of the keywords HYSTKROW

(see 12.6.70) and HYSTKROWR (see 12.6.71) that are used by tNavigator.

Example
*SORMAX *CON 0.62
...
*HYSKRO *KILLOUGH

In this example the maximum residual oil saturation for imbibition process is set equal to
0.34.
Later, the hysteresis option for oil relative permeability is triggered by *HYSKRO keyword.

13.6.44. SORMAX 2261

Keywords for formats tN, IM, ST, GE 19.1

13.6.45. HYSKRW

Data x tN E1 E3 x IM x GE ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

This keyword defines the method of water relative permeability hysteresis calculations in
oil-water systems.

The algorithms for relative permeability hysteresis calculations are described in Relative
permeability hysteresis in the non-wetting phase and Relative permeability hysteresis in the
wetting phase sections.

The list of avaliable hysteresis kewords compatible with IM/GE/ST format is provided in
Hysteresis definition in IM/GE/ST format section.

The data should be entered in one of the following formats:

*HYSKRW method *HYEXW exp_value

Where:

1. method – method that will be used for hysteresis calculations.

• *KILLOUGH – This sub-keyword defines Killough’s hysteresis method for relative

permeability.
In order to implement this option correctly, oil-water Imbibition Relative Perme-
abilities table SWTI (see 13.6.42) must be defined as well;
• *KILLOUGH_MOD – This sub-keyword defines modified Killough’s hysteresis
method for relative permeability.
In order to implement this option correctly, oil-water Imbibition Relative Perme-
abilities table SWTI (see 13.6.42) must be defined as well.

2. *HYEXW – optional parameter.

This sub-keyword indicates that the exponent of Killough’s hysteresis equation will be
used.

3. exp_value – the value of the exponent of Killough’s hysteresis equation.

Default: 1.5.

This keyword is an analog of the keywords HYSTKRW (see 12.6.70) and HYSTKRWR
(see 12.6.71) that are used by tNavigator.

13.6.45. HYSKRW 2262

Keywords for formats tN, IM, ST, GE 19.1

Example
*SWTI
** Sw Krowi Krwi
0.08 1.000 0.000
0.12 0.871 0.000
0.14 0.810 0.002
0.20 0.640 0.016
0.28 0.444 0.052
0.36 0.284 0.110
0.44 0.160 0.189
0.51 0.072 0.285
0.60 0.017 0.408
0.68 0.000 0.550
...
*HYSKRW *KILLOUGH *HYEXW 1.5

In this example:

• The hysteresis for water relative permeabilities is set via *HYSKRW keyword.

• Killough’s hysteresis method for relative permeability is set via *KILLOUGH sub-
keyword.

• Killough’s hysteresis exponent is imposed via *HYEXW sub-keyword.

the value of the exponent of Killough’s saturation interpolation equation is set equal to
1.5.

• Previously, oil-water Imbibition table was defined via *SWTI keyword.

This definition is mandatory for Killough’s hysteresis method.

13.6.45. HYSKRW 2263

Keywords for formats tN, IM, ST, GE 19.1

13.6.46. HYSKRG

Data x tN E1 E3 x IM x GE ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

This keyword defines the hysteresis calculations for gas relative permeability.
This keyword refers to the rock type described in RPT (see 13.6.2) keyword, which must be
entered before HYSKRG.

The algorithms for relative permeability hysteresis calculations are described in Relative
permeability hysteresis in the non-wetting phase and Relative permeability hysteresis in the
wetting phase sections.

The list of avaliable hysteresis kewords compatible with IM/GE/ST format is provided in
Hysteresis definition in IM/GE/ST format section.

The data should be entered in the following format:

*HYSKRG SGrmax

Where:

• SGrmax – the maximum possible imbibition residual gas saturation.

This keyword is an analogue of the keywords HYSTKRG (see 12.6.70) and HYSTKRGR
(see 12.6.71) that are used by tNavigator.

Example
*HYSKRG 0.34

In this example hysteresis option for Gas Relative Permeability is triggered by *HYSKRG
keyword. Maximum residual gas saturation for imbibition process is set equal to 0.34.

13.6.46. HYSKRG 2264

Keywords for formats tN, IM, ST, GE 19.1

13.6.47. HYSKROW

Data x tN E1 E3 IM x GE ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

This keyword defines the method of oil relative permeability hysteresis calculations in
oil-water systems.

The algorithms for relative permeability hysteresis calculations are described in Relative
permeability hysteresis in the non-wetting phase and Relative permeability hysteresis in the
wetting phase sections.

The list of avaliable hysteresis kewords compatible with IM/GE/ST format is provided in
Hysteresis definition in IM/GE/ST format section.

The data should be entered in one of the following formats:

I. First data input format

*HYSKROW *CARLSON SOW rmax

Where:
1. *CARLSON – This sub-keyword defines Carlson’s hysteresis method;
This sub-keyword can be omitted if SOW rmax is specified. In this case Carlson’s hystere-
sis method will be assumed automatically by the simulator.

2. SOW rmax – the maximum possible residual oil saturation in Water-Oil system.

II. Second data input format

*HYSKROW *KILLOUGH *HYEXO exp_value

Where:
1. *KILLOUGH – This sub-keyword defines Killough’s hysteresis method for relative per-
meability.
In order to implement this option correctly, oil-water Imbibition Relative Permeabilities
table SWTI (see 13.6.42) must be defined as well;

2. *HYEXO – optional parameter. This sub-keyword defines Killough’s hysteresis method

for relative permeability and Killough’s saturation interpolation;

13.6.47. HYSKROW 2265

Keywords for formats tN, IM, ST, GE 19.1

3. exp_value – the value of the exponent of Killough’s saturation interpolation equation.

Default: 1.5.

This keyword is an analogue of the keywords HYSTKROW (see 12.6.70) and HYS-
TKROWR (see 12.6.71) that are used by tNavigator.

Example
*SWTI
** Sw Krowi Krwi
0.08 1.000 0.000
0.12 0.871 0.000
0.14 0.810 0.002
0.20 0.640 0.016
0.28 0.444 0.052
0.36 0.284 0.110
0.44 0.160 0.189
0.51 0.072 0.285
0.60 0.017 0.408
0.68 0.000 0.550
...
*HYSKROW *KILLOUGH *HYEXO 2.0

In this example:

• The hysteresis for Oil Relative Permeabilies is set via *HYSKRO keyword.

• Killough’s hysteresis method for Relative Permeability is set via *KILLOUGH sub-
keyword.

• Killough’s saturation interpolation method is set via *HYEXO sub-keyword.

the value of the exponent of Killough’s saturation interpolation equation is set equal to
2.0.

• Previously, oil-water Imbibition table was defined via *SWTI keyword.

This definition is mandatory for Killough’s hysteresis method.

13.6.47. HYSKROW 2266

Keywords for formats tN, IM, ST, GE 19.1

13.6.48. HYSKROG

Data x tN E1 E3 IM x GE ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

This keyword defines the hysteresis calculations for oil relative permeability in gas-oil
systems.
This keyword refers to the rock type described in RPT (see 13.6.2) keyword, which must be
entered before HYSKRG.
The algorithms for relative permeability hysteresis calculations are described in Relative
permeability hysteresis in the non-wetting phase and Relative permeability hysteresis in the
wetting phase sections.

The list of avaliable hysteresis kewords compatible with IM/GE/ST format is provided in
Hysteresis definition in IM/GE/ST format section.

The data should be entered in the following format:

*HYSKROG SOGrmax

Where:

• SOGrmax – the maximum possible imbibition oil residual saturation in gas-oil system.

This keyword is an analogue of the keywords HYSTKROG (see 12.6.70) and HYSTKROGR
(see 12.6.71) that are used by tNavigator.

Example
*HYSKROG 0.62

13.6.48. HYSKROG 2267

Keywords for formats tN, IM, ST, GE 19.1

13.6.49. HYS_KRO

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

This keyword defines the parameters of OIL and WATER relative permeability hysteresis
calculations. This keyword is used for water-wet rocks.

The algorithms for relative permeability hysteresis calculations are described in Relative
permeability hysteresis in the non-wetting phase and Relative permeability hysteresis in the
wetting phase sections.

The list of avaliable hysteresis kewords compatible with IM/GE/ST format is provided in
Hysteresis definition in IM/GE/ST format section.

The data should be entered in one of the following formats:

I. First data input format

*HYS_KRO *CARLSON *SOTMAX value

Where:

1. *CARLSON – this sub-keyword indicates that Carlson’s method will be used for non-
wetting phase relative permeability hysteresis.
In this method only OIL relative permeability hysteresis is calculated.

2. *SOTMAX – this sub-keyword indicates that the maximum trapped oil saturation will
be specified.

3. value – the value of the maximum trapped oil saturation.

Default: If the value is not specified, the simulator will use the midpoint saturation
value on the line between maximum and critical oil saturations..

II. Second data input format

*HYS_KRO method *HYEXO hyexo *HYEXW huexw

*SWTI
SW Kri_nonwet Kri_wet

Where:

1. method – method that would be used for hysteresis calculations.

13.6.49. HYS_KRO 2268

Keywords for formats tN, IM, ST, GE 19.1

• *KILLOUGH – If this sub-keyword is used, Killough’s method will be applied to

non-wetting phase (OIL) and, optionally, for wetting phase (WATER) relative
permeability hysteresis.
• *KILLOUGH_MOD – If this sub-keyword is used, Killough’s method will be ap-
plied to non-wetting phase and modified Killough’s method will be applied to
wetting phase relative permeability hysteresis.
2. *HYEXO – optional sub-keyword.
This sub-keyword indicates that Killough’s hysteresis equation will be used to determine
the curvature and position of OIL relative permeability scanning curve.
hyexo is the value of the exponent of Killough’s saturation interpolation equation.
Default: hyexo = 1.
3. *HYEXW – optional sub-keyword.
This sub-keyword indicates that Killough’s hysteresis equation will be used to determine
the curvature and position of WATER relative permeablity scanning curve.
hyexw is the value of the exponent of Killough’s saturation interpolation equation.
Default: hyexw = 1.
4. *SWTI – keyword indicating the input oil-water imbibition table.
It contains two or three columns:
• SW – water saturation. The data must be entered in the table in increasing order;
• Kri_nonwet – imbibition relative permeability of non-wetting phase OIL;
• Kri_wet – imbibition relative permeability of wetting phase WATER.
This is an optional column.
This keyword is an analogue of the keywords HYSTKROW (see 12.6.70) and HYS-
TKROWR (see 12.6.71) that are used by tNavigator.

Example
*HYS_KRO *KILLOUGH *HYEXO 2.5 *HYEXW 1.5
*SWTI
** swti krowi krwi
0.08 1.000 0.000
0.12 0.871 0.000
0.14 0.810 0.002
0.20 0.640 0.016
0.28 0.444 0.052
0.36 0.284 0.110
0.44 0.160 0.189
0.51 0.072 0.285
0.60 0.017 0.408
0.68 0.000 0.550

13.6.49. HYS_KRO 2269

Keywords for formats tN, IM, ST, GE 19.1

In this example:

• Relative permeability hysteresis option is triggered via *HYS_KRO keyword.

• Killough’s method is defined via *KILLOUGH keyword.

• Keyword *HYEXO indicated that the shape and position of oil RP imbibition curve
is defined by the exponent of Killough’s saturation interpolation equation (set equal
to2.5).

• Keyword *HYEXW indicated that the Hysteresis calculations will be performed for
water relative permeabilities as well.
The shape and position of water RP imbibition curve is defined by the exponent of
Killough’s saturation interpolation equation (set equal to1.5).

• Oil-water RP Imbibiton table is entered via *SWTI sub-keyword.

13.6.49. HYS_KRO 2270

Keywords for formats tN, IM, ST, GE 19.1

13.6.50. HYS_KRG

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

This keyword defines the parameters of GAS relative permeability hysteresis calculations.

The algorithms for relative permeability hysteresis calculations are described in Relative
permeability hysteresis in the non-wetting phase and Relative permeability hysteresis in the
wetting phase sections.

The list of avaliable hysteresis kewords compatible with IM/GE/ST format is provided in
Hysteresis definition in IM/GE/ST format section.

The data should be entered in one of the following formats:

I. First data input format

*HYS_KRG *CARLSON *SGTMAX value

Where:
1. *CARLSON – this sub-keyword indicates that Carlson’s method will be used for non-
wetting phase relative permeability hysteresis.
2. *SGTMAX – this sub-keyword indicates that the maximum trapped gas saturation will
be specified.
3. value – the value of the maximum trapped gas saturation.
Default: If the value is not specified, the simulator will use the midpoint saturation
value on the line between maximum and critical gas saturations..
II. Second data input format

*HYS_KRG *KILLOUGH
*HYEXG (hyexg)
*SLTI
SL KrGi

Where:
1. *KILLOUGH – If this sub-keyword is used, Killough’s method will be applied to non-
wetting phase (GAS) and relative permeability hysteresis.

13.6.50. HYS_KRG 2271

Keywords for formats tN, IM, ST, GE 19.1

2. *HYEXG – optional parameter.

This sub-keyword indicates that Killough’s hysteresis equation will be used to determine
the curvature and position of GAS Relative Permeability scanning curve.
hyexg is the value of the exponent of Killough’s saturation interpolation equation.

3. *SLTI – keyword indicating the enput of liquid-gas imbibition table.

It contains two columns:

• SL - Liquid saturation. The data must be entered in the table in increasing order;
• KrGi – gas relative permeability (imbibition curve).

This keyword is an analogue of the keywords HYSTKRG (see 12.6.70) and HYSTKRG
(see 12.6.70) that are used by tNavigator.

Example
*HYS_KRG *KILLOUGH *HYEXG 1.7
*SLTI
** slti krgi
0.08 1.000
0.12 0.854
0.14 0.790
0.20 0.650
0.28 0.421
0.36 0.278
0.44 0.155
0.51 0.061
0.60 0.011
0.68 0.000

In this example:

• Relative permeability hysteresis option for gas relative permeability is triggered via
*HYS_KRG keyword.

• Killough’s method is defined via *KILLOUGH keyword.

• Keyword *HYEXG indicated that the shape and position of oil RP Imbibition curve
is defined by the exponent of Killough’s saturation interpolation equation (set equal
to1.7).

• Liquid-gas RP imbibiton table is entered via *SLTI sub-keyword.

13.6.50. HYS_KRG 2272

Keywords for formats tN, IM, ST, GE 19.1

13.6.51. HYS_PCOW

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

This keyword triggers the hysteresis option for oil-water capillary pressure.

The algorithms for capillary pressure hysteresis calculations are described in Capillary
pressure hysteresis section.

The list of avaliable hysteresis kewords compatible with IM/GE/ST format is provided in
Hysteresis definition in IM/GE/ST format section.

The data should be entered in the following format:

*HYS_PCOW *EPSOW value

Where:

1. *EPSOW – this sub-keyword defines the curvature parameter for oil-water capillary
pressure hysteresis.

2. value – the value which determines the transition between imbibition and drainage
curves for oil-water capillary pressure.
This is a dimensionless parameter which has a value in the range from 0.005 to 0.1.

This keyword is an analogue of the EPS parameter of the keywords HYSTPCW

(see 12.6.72) and HYSTPCWR (see 12.6.73) that are used by tNavigator.

Example
*HYS_PCOW *EPSOW 0.023

13.6.51. HYS_PCOW 2273

Keywords for formats tN, IM, ST, GE 19.1

13.6.52. HYS_PCOG

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

This keyword triggers the hysteresis option for gas-oil capillary pressure.

The algorithms for capillary pressure hysteresis calculations are described in Capillary
pressure hysteresis section.

The list of avaliable hysteresis kewords compatible with IM/GE/ST format is provided in
Hysteresis definition in IM/GE/ST format section.

The data should be entered in the following format:

*HYS_PCOG *EPSOG value

Where:

1. *EPSOG – this sub-keyword defines the curvature parameter for gas-oil capillary pres-
sure hysteresis.

2. value – the value which determines the transition between imbibition and drainage
curves for gas-oil capillary pressure.
This is a dimensionless parameter which has a value in the range from 0.005 to 0.1.

This keyword is an analogue of the EPS parameter of the keywords HYSTPCG

(see 12.6.72) and HYSTPCGR (see 12.6.73) that are used by tNavigator.

Example
*HYS_PCOG *EPSOW 0.023

13.6.52. HYS_PCOG 2274

Keywords for formats tN, IM, ST, GE 19.1

13.6.53. HYS_LEVEL

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

This keyword triggers hysteresis option and defines the properties of capillary pressure
hysteresis calculations for all interpolation sets.

The algorithms for capillary pressure hysteresis calculations are described in Capillary
pressure hysteresis section.

The list of avaliable hysteresis kewords compatible with IM/GE/ST format is provided in
Hysteresis definition in IM/GE/ST format section.

The data should be entered in the following format:

*HYS_LEVEL value

Where:

• value – the number of levels of scanning curves for capillary pressure hysteresis. It
must be equal either to 1 or 2:

– 1 – if an imbibition process on a scanning imbibition curve is reversed into a

drainage process then in the secondary drainage process it will be placed trans-
versely to the same scanning curve.
– 2 – if an imbibition process on a scanning imbibition curve is reversed into a
drainage process then in the the secondary drainage process it will use a new scan-
ning drainage curve (Killough model). Each new reversal a new scanning curve is
constructed.
This value is an analogue of the NEW parameter of the keywords HYSTPCW
(see 12.6.72) / HYSTPCWR (see 12.6.73) and HYSTPCG (see 12.6.72) / HYST-
PCGR (see 12.6.73) that are used by tNavigator.

Example
*HYS_LEVEL 1

13.6.53. HYS_LEVEL 2275

Keywords for formats tN, IM, ST, GE 19.1

13.6.54. SORM

Data x tN E1 E3 IM x GE ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

This keyword activates residual oil saturation option and assigns the values of residual oil
saturation to the grid blocks. This keyword has a E3-compatible analog SOILR (see 12.16.58).

The data should be entered in the following format:

*SORM blocks_array SOrm

Where:
• blocks_array – Definition of block array for which the property will be assigned. The
detailed description of available input options is provided in Data entry system section.
• SOrm – the value of residual oil saturation.

The residual oil saturation is the ratio of the residual oil volume in a cell to the cell’s pore
volume:
VOrm
SOrm = .
PORVOL
This value must be less than the residual oil saturation defined by Relative Permeability
table. If the initial oil saturation in lower than the value of residual oil saturation, then SOrm
will be set equal to the initial oil saturation.

The residual oil composition remains constant (equal to the initial oil composition), and,
consequently, the volume of residual oil depends only on reservoir pressure. Therefore, the
residual oil saturation also depends only on pressure:
1
dSOrm 1 dPORVOL
· = −COILR − · ,
SOrm dP PORVOL dP
where COILR – compressibility of residual oil:
1 dVOrm
COILR = − .
VOrm dP
The residual oil volume is determined by flashing the residual oil composition at the cell
pressure.
Example
*SORM *CON 0.12

13.6.54. SORM 2276

Keywords for formats tN, IM, ST, GE 19.1

In this example the value of residual oil saturation is set equal to 0.12 in all grid blocks.

13.6.54. SORM 2277

Keywords for formats tN, IM, ST, GE 19.1

13.6.55. DAMP-PCOW-TROIL

Data x tN E1 E3 x IM x GE ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

This keyword is used in order to avoid numerical issues during the calculation of Capillary
Pressure hysteresis with oil trapping.
It linearly reduces vertical extent of PcOW cycle when maximum oil saturation on the
scanning curve approaches residual oil saturation.

The Capillary Pressure hysteresis can be defined via HYS_PCOW (see 13.6.51) keyword.

The data should be entered in the following format:

*DAMP-PCOW-TROIL (*ON | *OFF)

• *ON – option is enabled.

• *OFF – option is not used

Example
*DAMP-PCOW-TROIL *ON

13.6.55. DAMP-PCOW-TROIL 2278

Keywords for formats tN, IM, ST, GE 19.1

13.6.56. PTHRESHI / PTHRESHJ / PTHRESHK

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

The keyword sets pressure gradient threshold for the flow between block (I, J, K) and an-
other one connected to it in I + / J + / K + direction correspondingly. The following parameters
should be specified:

1. pressure gradient threshold for each grid block (SI: kPa/m, FIELD: Psi/ f t );
Default: 0.

This keyword has an E1/E3 compatible analogue THPRES (see 12.16.11).

13.6.56. PTHRESHI / PTHRESHJ / PTHRESHK 2279

Keywords for formats tN, IM, ST, GE 19.1

13.6.57. ADGMAXC

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

This keyword specifies the maximum adsorption capacity for the gas (in black oil models)
or a particular gas component (in compositional models) when using the Coal Bed Methane
model (see section 2.28.1). This keyword should be used in dual porosity model (see DUAL-
POR, see 13.3.6).
The following parameters should be specified:

1. Maximum gas adsorption capacity for each grid block (SI: sm3 /kg, FIELD: s f t 3 /lb).

! Currently tNavigator supports only the constant value for this parameter,
hence the array must be filled with a constant value using CON (see 13.1.3).
Defalut value is not set. If this keywords is not specified, then gas desorption is not
considered.
This keyword has an E1/E3 compatible analogue : Langmuir volume constant from LANG-
MEXT (see 12.9.6).

13.6.57. ADGMAXC 2280

Keywords for formats tN, IM, ST, GE 19.1

13.6.58. ADGCSTC

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

This keyword specifies the adsorption coefficient for the gas (in black oil models) or a
particular gas component (in compositional models) when using the Coal Bed Methane model
(see section 2.28.1). This keyword should be used in dual porosity model (see DUALPOR,
see 13.3.6).
The following parameters should be specified:

1. Gas adsorption coefficient for each grid block (SI: 1/kPa, FIELD: 1/psi).

! Currently tNavigator supports only the constant value for this parameter,
hence the array must be filled with a constant value using CON (see 13.1.3).
Defalut value is not set. If this keywords is not specified, then gas desorption is not
considered.
This keyword has an E1/E3 compatible analogue : inverse Langmuir pressure constant
from LANGMEXT (see 12.9.6).

13.6.58. ADGCSTC 2281

Keywords for formats tN, IM, ST, GE 19.1

13.6.59. COAL-DIF-COMP

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

This keyword specifies the diffusion coefficient for the gas (in black oil models) or a
particular gas component (in compositional models) when using the Coal Bed Methane model
(see section 2.28.1). This keyword should be used in dual porosity model (see DUALPOR,
see 13.3.6).
The following parameters should be specified:

1. Gas diffusion coefficient for each grid block (cm 2 /s).

! Currently tNavigator supports only the constant value for this parameter,
hence the array must be filled with a constant value using CON (see 13.1.3).
Only one of the keywords COAL-DIF-COMP (see 13.6.59) and COAL-DIF-TIME must be
specified.
Defalut value is not set. If none of these keywords is specified, then gas desorption is not
considered.
This keyword has an E1/E3 compatible analogue DIFFCOAL (see 12.9.1) (E1) or DIFFCBM
(see 12.9.7) (E3).

13.6.59. COAL-DIF-COMP 2282

Keywords for formats tN, IM, ST, GE 19.1

13.6.60. COAL-DIF-TIME

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
x Rockfluid Initial Numerical Well

This keyword specifies the characteristic time of diffusion for the gas (in black oil models)
or a particular gas component (in compositional models) when using the Coal Bed Methane
model (see section 2.28.1). This keyword should be used in dual porosity model (see DUAL-
POR, see 13.3.6).
The following parameters should be specified:

1. Characteristic time of gas diffusion for each grid block (in days).

! Currently tNavigator supports only the constant value for this parameter,
hence the array must be filled with a constant value using CON (see 13.1.3).
Only one of the keywords COAL-DIF-TIME and COAL-DIF-COMP (see 13.6.59) must be
specified.
Defalut value is not set. If none of these keywords is specified, then gas desorption is not
considered.
This keyword has an E1/E3 compatible analogue : inverse product of SIGMA (see 12.2.72)
and DIFFCOAL (see 12.9.1) (E1) or DIFFCBM (see 12.9.7) (E3).

13.6.60. COAL-DIF-TIME 2283

Keywords for formats tN, IM, ST, GE 19.1

13.7. Initial conditions

13.7.1. INITIAL

Data x tN E1 E3 x IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical Well

The keyword starts the section ”Initial conditions” (13.7).

Example
INITIAL

13.7. Initial conditions 2284

Keywords for formats tN, IM, ST, GE 19.1

13.7.2. VERTICAL

Data x tN E1 E3 x IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical Well

This option sets that pressures are obtained from hydrostatic equation and saturations –
from capillary pressure tables.

The option has the following suboptions:

VERTICAL DEPTH_AVE|BLOCK_CENTER WATER_OIL EQUIL

• DEPTH_AVE – block saturation is determined as average saturation over the depth in-
terval stretched over the grid block. This option uses information from the keywords
DWOC (see 13.7.14), DGOC (see 13.7.15), SW (see 13.7.19), SO (see 13.7.17), SG
(see 13.7.18). The E1/E3-compatible analogue is EQUIL (see 12.16.2) with its 9th pa-
rameter set to a non-zero value.

• BLOCK_CENTER – block saturation is determined as the value at the center of the grid
block. The E1/E3-compatible analogue is EQUIL (see 12.16.2) with its 9th parameter set
to zero.

• WATER_OIL – perform gravity-capillary equilibrium initialization of a reservoir initially

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 sat-
urations over depth. Hence gravitational equilibrium isn’t established just by setting
saturations from capillary pressure tables.

13.7.2. VERTICAL 2285

Keywords for formats tN, IM, ST, GE 19.1

13.7.3. USER_INPUT

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical Well

This option sets that the initial pressures and saturations are specified directly by the user
and not obtained from hydrostatic equations.
The E1/E3-compatible analogue is the absence of EQUIL (see 12.16.2) keyword.
Example
*USER_INPUT
*GOC_PC 0
*WOC_PC 0
*PRES *ALL
26*988.568 807.9764 799.9263
...

13.7.3. USER_INPUT 2286

Keywords for formats tN, IM, ST, GE 19.1

13.7.4. SWINIT

Data x tN E1 E3 x IM x GE ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical Well

The keyword sets initial water saturation while maintaining gravity-capillary equilibrium
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.
The following parameters should be specified:

1. initial water saturation for each cell.

Default: if for some cell SWINIT (see 13.7.4) value is not specified, then its initial wa-
ter saturation is determined via option DEPTH_AVE or via keywords SW (see 13.7.19), SO
(see 13.7.17) and SG (see 13.7.18).

The keyword has an E1/E3-compatible analogue SWATINIT (see 12.6.65).

Example
*SWINIT CON 0.3
In the example initial water saturation of entire reservoir is 0.3.

13.7.4. SWINIT 2287

Keywords for formats tN, IM, ST, GE 19.1

13.7.5. SWNEQ

Data x tN E1 E3 x IM x GE ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical Well

This keyword specifies initial water saturation in a local area, overriding that defined by
the gravity-capillary equilibrium initialization. Note that the pressures in the affected area are
still taken from the equilibrium initialization. This may be useful, for example, to model a
reservoir where earlier measures of enhanced oil recovery have created a water-filled fracture
with non-equilibrium distribution of saturations around it.
The following parameters should be specified:

1. initial water saturation for each block in the whole reservoir or a part of it.

Default: if for some cell SWNEQ is not specified, then its initial water saturation is defined
by the gravity-capillary equilibrium (VERTICAL, see 13.7.2) or a keyword SW (see 13.7.19).

Example
SWNEQ MATRIX BG 'Fracture1' *FZ 0.65
SWNEQ MATRIX BG 'Fracture1' *NFZ 0.5

In this example the initial water saturation in the matrix blocks belonging to the group
named 'Fracture1' is set to 0.65 for LGR blocks and to 0.5 for blocks outside of LGR.

13.7.5. SWNEQ 2288

Keywords for formats tN, IM, ST, GE 19.1

13.7.6. SONEQ

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical Well

This keyword specifies initial oil saturation in a local area, overriding that defined by
the gravity-capillary equilibrium initialization. Note that the pressures in the affected area are
still taken from the equilibrium initialization. This may be useful, for example, to model a
reservoir where earlier measures of enhanced oil recovery have created a water-filled fracture
with non-equilibrium distribution of saturations around it.
The following parameters should be specified:

1. initial oil saturation for each block in the whole reservoir or a part of it.

Default: if for some cell SONEQ is not specified, then its initial oil saturation is defined
by the gravity-capillary equilibrium (VERTICAL, see 13.7.2) or a keyword SO (see 13.7.17).

Example
VERTICAL DEPTH_AVE
SONEQ IJK 10:15 10:15 5:10 0.2

In this example the initial oil saturation in a certain box is set equal to 0.2.

13.7.6. SONEQ 2289

Keywords for formats tN, IM, ST, GE 19.1

13.7.7. PB

Data x tN E1 E3 x IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical Well

The keyword sets initial bubble point pressure for each grid block (SI: kPa, FIELD: psi).
The keyword has an E1/E3-compatible analogue PBUB (see 12.16.36).
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.7. PB 2290
Keywords for formats tN, IM, ST, GE 19.1

13.7.8. DATUMDEPTH

Data x tN E1 E3 x IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical Well

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 E1/E3-compatible analogue DATUM (see 12.16.40) (for whole reser-
voir) and DATUMR (see 12.16.41) (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.8. DATUMDEPTH 2291

Keywords for formats tN, IM, ST, GE 19.1

13.7.9. GASZONE

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical Well

This keyword specifies a method of computing residual oil saturation in gas zone where
the difference between the oil and gas phase pressures exceeds the largest tabulated value the
oil-gas capillary pressure. The keyword can be used if sub-option DEPTH_AVE of keyword
VERTICAL (see 13.7.2) is turned on.
The keyword has two sub-options:

• NOOIL If this sub-option is selected and the computed pressure difference between the
oil and gas phases exceeds the tabulated value of the capillary pressure, then the water
saturation Sw is specified by the oil-water phase pressure difference. Gas saturation SG
is set to min(SG (tab), 1 − Sw ). Oil saturation SO is set equal to zero;

• OIL If this sub-option is selected and the computed pressure difference between the
oil and gas phases exceeds the tabulated value of the capillary pressure, then the wa-
ter saturation Sw is specified by the oil-water phase pressure difference. SG is set
to min(SG (tab), max(1 − Sw − SO (min), 0). Oil saturation SO (min) = max(SOrG + Swc −
Sw , 0) (SOrG is gas saturation at residual oil)

• Default: NOOIL.

The keyword is optional. If it is not specified in a model then oil saturation SO is set zero
in the gas zone.

Example
*GASZONE *OIL

13.7.9. GASZONE 2292

Keywords for formats tN, IM, ST, GE 19.1

13.7.10. INITREGION

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical Well

The keyword sets the initialization region number. The data below is assigned to this re-
gion. The following keywords can be specified after INITREGION: REFPRES (see 13.7.12),
REFDEPTH (see 13.7.13), DWOC (see 13.7.14).
INTYPE (see 13.7.11) 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.13), reference pressure (REFPRES, see 13.7.12), water-oil contact depth
(DWOC, see 13.7.14) and gas-oil contact depth (DGOC, see 13.7.15) are given.

13.7.10. INITREGION 2293

Keywords for formats tN, IM, ST, GE 19.1

13.7.11. INTYPE

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical Well

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.10), properties of each region
– REFPRES (see 13.7.12), REFDEPTH (see 13.7.13), DWOC (see 13.7.14).

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
(REFDEPTH, see 13.7.13), reference pressure (REFPRES, see 13.7.12), water-oil contact
depth (DWOC, see 13.7.14) and gas-oil contact depth (DGOC, see 13.7.15) are given. All
grid blocks belong to this initialization region (CON specifies the constant value array).

13.7.11. INTYPE 2294

Keywords for formats tN, IM, ST, GE 19.1

13.7.12. REFPRES

Data x tN E1 E3 x IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical Well

The keyword specifies the reference pressure (SI: kPa, FIELD: psi) at the reference depth
– REFDEPTH (see 13.7.13).
REFDEPTH and REFPRES can be specified for multiple initialization regions (use INITRE-
GION, see 13.7.10).

The keywords REFPRES (see 13.7.12), REFDEPTH (see 13.7.13), DWOC (see 13.7.14),
DGOC (see 13.7.15), VERTICAL (see 13.7.2) have an E1/E3-compatible analogue EQUIL
(see 12.16.2).
1-st parameter of EQUIL (see 12.16.2) corresponds to REFDEPTH (see 13.7.13), 2-nd – REF-
PRES (see 13.7.12), 3-rd – DWOC (see 13.7.14), 5-th – DGOC (see 13.7.15).

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.13), reference pressure (REFPRES, see 13.7.12), water-oil contact depth
(DWOC, see 13.7.14) and gas-oil contact depth (DGOC, see 13.7.15) are given.

13.7.12. REFPRES 2295

Keywords for formats tN, IM, ST, GE 19.1

13.7.13. REFDEPTH

Data x tN E1 E3 x IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical Well

The keyword specifies the reference depth (SI: m, FIELD: f t ). At the reference depth the
keyword REFPRES (see 13.7.12) specifies the reference pressure.
REFDEPTH and REFPRES can be specified for multiple initialization regions (use INITRE-
GION, see 13.7.10).

The keywords REFPRES (see 13.7.12), REFDEPTH (see 13.7.13), DWOC (see 13.7.14),
DGOC (see 13.7.15), VERTICAL (see 13.7.2) have an E1/E3-compatible analogue EQUIL
(see 12.16.2).
1-st parameter of EQUIL (see 12.16.2) corresponds to REFDEPTH (see 13.7.13), 2-nd – REF-
PRES (see 13.7.12), 3-rd – DWOC (see 13.7.14), 5-th – DGOC (see 13.7.15).

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.13), reference pressure (REFPRES, see 13.7.12), water-oil contact depth
(DWOC, see 13.7.14) and gas-oil contact depth (DGOC, see 13.7.15) are given.

13.7.13. REFDEPTH 2296

Keywords for formats tN, IM, ST, GE 19.1

13.7.14. DWOC

Data x tN E1 E3 x IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical Well

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.10).

If VERTICAL DEPTH_AVE (VERTICAL, see 13.7.2) is present, the resulting water satu-
ration will reflect the water-oil transition zone caused by non-zero capillary pressure.

The keywords REFPRES (see 13.7.12), REFDEPTH (see 13.7.13), DWOC (see 13.7.14),
DGOC (see 13.7.15), VERTICAL (see 13.7.2) have an E1/E3-compatible analogue EQUIL
(see 12.16.2).
1-st parameter of EQUIL (see 12.16.2) corresponds to REFDEPTH (see 13.7.13), 2-nd – REF-
PRES (see 13.7.12), 3-rd – DWOC (see 13.7.14), 5-th – DGOC (see 13.7.15).

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.13), reference pressure (REFPRES, see 13.7.12), water-oil contact depth
(DWOC, see 13.7.14) and gas-oil contact depth (DGOC, see 13.7.15) are given.

13.7.14. DWOC 2297

Keywords for formats tN, IM, ST, GE 19.1

13.7.15. DGOC

Data x tN E1 E3 x IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical Well

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.10).

If VERTICAL DEPTH_AVE (VERTICAL, see 13.7.2) is present, the resulting gas satura-
tion will reflect the liquid-gas transition zone caused by non-zero capillary pressure.

The keywords REFPRES (see 13.7.12), REFDEPTH (see 13.7.13), DWOC (see 13.7.14),
DGOC (see 13.7.15), VERTICAL (see 13.7.2) have an E1/E3-compatible analogue EQUIL
(see 12.16.2).
1-st parameter of EQUIL (see 12.16.2) corresponds to REFDEPTH (see 13.7.13), 2-nd – REF-
PRES (see 13.7.12), 3-rd – DWOC (see 13.7.14), 5-th – DGOC (see 13.7.15).

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.13), reference pressure (REFPRES, see 13.7.12), water-oil contact depth
(DWOC, see 13.7.14) and gas-oil contact depth (DGOC, see 13.7.15) are given.

13.7.15. DGOC 2298

Keywords for formats tN, IM, ST, GE 19.1

13.7.16. WOC_SW

Data x tN E1 E3 x IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical Well

The keyword set water saturation value below water-oil contact in each initialization re-
gion. The following parameters should be specified:

1. water saturation value.

Default: 0.9999.

This keyword has a MO compatible analog AQUW (see 14.5.15).

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.16. WOC_SW 2299

Keywords for formats tN, IM, ST, GE 19.1

13.7.17. SO

Data x tN E1 E3 x IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical Well

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 E1/E3-compatible analogue SOIL (see 12.16.16).

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.17. SO 2300
Keywords for formats tN, IM, ST, GE 19.1

13.7.18. SG

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical Well

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 E1/E3-compatible analogue SGAS (see 12.16.15).

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.18. SG 2301
Keywords for formats tN, IM, ST, GE 19.1

13.7.19. SW

Data x tN E1 E3 x IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical Well

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 E1/E3-compatible analogue SWAT (see 12.16.14).

Example
SW CON 0.3

In this example the initial water saturation in all grid blocks is equal to 0.3 (CON
(see 13.1.3) specifies the constant value array).

13.7.19. SW 2302
Keywords for formats tN, IM, ST, GE 19.1

13.7.20. SAT_ADJUST

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical Well

This keyword indicates that the minimum value of water and oil saturation will be set
equal to 10−4 .

The saturation adjustment is performed in the following way:

• If only SW < 10−4 then in the blocks violating this condition water saturation will be
set equal to 10−4 and the largest of remaining two phase saturations will be adjusted.

• If only SO < 10−4 then in the blocks violating this condition oil saturation will be set
equal to 10−4 in the blocks violating this condition and the largest of remaining two
phase saturations will be adjusted.

• If both SW and WO are < 10−4 , then only water saturation will be set equal to 10−4
and gas saturation will be adjusted. Oil saturation will remain unchanged.

This keyword has an E1/E3-compatible analog: TNAVCTRL (see 12.1.4), option SAT_ADJUST.

Example
*SAT_ADJUST

*SO *IJK
1 1 1 0.00005
1 1 2 0.00006
1 1 3 0.3

*SW *IJK
1 1 1 0.00004
1 1 2 0.00005
1 1 3 0.3

In this example:

• Some blocks have the values of SW and SO lower than 10−4 .

• Keyword *SAT_ADJUST indicates that water saturation will be set equal to 10−4 in
these blocks.

13.7.20. SAT_ADJUST 2303

Keywords for formats tN, IM, ST, GE 19.1

13.7.21. API

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical Well

The keyword sets the initial volume fraction of light oil in models with API tracking
option, see 2.8.8. The same number of values as the number of grid blocks should be specified.
The keyword has an E1/E3-compatible analogue OILAPI (see 12.16.19).

Example
*API *KVAR 1.0 .77 .69 .61 .53 .47 .39 .31 .23 .15 .10

In this example the initial light oil fraction is set to certain values specific to each layer
using the keyword KVAR (see 13.1.4).

13.7.21. API 2304

Keywords for formats tN, IM, ST, GE 19.1

13.7.22. APIT

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical Well

The keyword specifies the initial volume fraction of light oil in models with API tracking
option (see 2.8.8) as a function of depth.
The data should be entered the following way:
*APIT number

The header parameter has the following meaning:

1. number is the number of initialization region to which the following table applies.

The table consists of arbitrary number of lines (two or more). Depth (the first parameter)
should increase down the column.
Each line contains the following parameters:

1. depth (SI: m, FIELD: ft),

2. initial volume fraction of light oil.

The keyword has an E1/E3-compatible analogue APIVD (see 12.16.18).

Example
*APIT 1
8300. 0.05
8400. 0.10
9900. 0.90
10000. 0.95

In this example the initial fraction of light oil is specified at four depths.

13.7.22. APIT 2305

Keywords for formats tN, IM, ST, GE 19.1

13.7.23. PRES

Data x tN E1 E3 x IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical Well

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 E1/E3-compatible analogue PRESSURE (see 12.16.12).

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.23. PRES 2306

Keywords for formats tN, IM, ST, GE 19.1

13.7.24. TEMP

Data x tN E1 E3 x IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical Well

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 E1/E3-compatible analogue TEMPI (see 12.16.32).

Example
TEMP CON 90

In this example the same initial temperature is specified in all grid blocks (CON
(see 13.1.3) specifies the constant value array).

13.7.24. TEMP 2307

Keywords for formats tN, IM, ST, GE 19.1

13.7.25. CONC_SLD

Data x tN E1 E3 x IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical Well

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.25. CONC_SLD 2308

Keywords for formats tN, IM, ST, GE 19.1

13.7.26. MFRAC_OIL

Data x tN E1 E3 x IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical Well

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 E1/E3-compatible analogue XMF (see 12.16.21).

Default: 0.
Example
MFRAC_OIL 'DeadOil' CON 0.48223

In this example the same initial mole fraction of the component 'DeadOil' in the oil phase
is specified in all grid blocks (CON (see 13.1.3) specifies the constant value array).

13.7.26. MFRAC_OIL 2309

Keywords for formats tN, IM, ST, GE 19.1

13.7.27. MFRAC_GAS

Data x tN E1 E3 x IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical Well

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 E1/E3-compatible analogue YMF (see 12.16.22).

Default: 0.
Example
MFRAC_GAS 'comp4' CON 0.0087

In this example the same initial mole fraction of the component 'comp4' in the gas phase
is specified in all grid blocks (CON (see 13.1.3) specifies the constant value array).

13.7.27. MFRAC_GAS 2310

Keywords for formats tN, IM, ST, GE 19.1

13.7.28. PBC

Data x tN E1 E3 x IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical Well

The keyword specifies bubble point pressure at initial temperature at each block for spec-
ified 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.41), evaluated at initial temper-
ature T and Pbi value.

The following parameters should be specified:

1. component name;

2. bubble point pressure (SI: kPa, FIELD: psi).

! The maximal value of bubble point pressure at initial temperature has to be

less than 106 for any units system.

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.28. PBC 2311

Keywords for formats tN, IM, ST, GE 19.1

13.7.29. SEPARATOR

Data x tN E1 E3 IM x GE ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical Well

This keyword sets separator stages conditions. Parameters of this keyword can be entered
by two ways: standard one and advanced one.

Standard input format:

*SEPARATOR
Psep1 T sep1
Psep2 T sep2
... ... ...
Psepn T sepn

Where:

1. Psepi – separator stage pressure (SI: kPa; FIELD: psi);

2. T sepi – separator stage temperature (SI: kPa; FIELD: psi).

Advanced input format:

*SEPARATOR
stage_lines stream_lines

Where:

I. stage_lines – one or several lines (one per stage) defining the properties of separator stage.

The data should be entered in the following format:

*EOS eos_num Psep T sep phase destination

1. *EOS – sub-keyword indicating that EOS region number and 2 characteristics of the
stage will be entered next;

2. eos_num – EOS region number (see keyword EOSSET, see 13.5.83);

3. Psep – separator stage pressure (SI: kPa; FIELD: psi);

4. T sep – separator stage temperature (SI: kPa; FIELD: psi);

13.7.29. SEPARATOR 2312

Keywords for formats tN, IM, ST, GE 19.1

5. phase – type of the fluid, which destination will be defined next. Several fluids can be
defined separately (each fluid on the new line). Two options are available:

• *LIQUID-TO – liquid output of the current separator stage;

• *VAPOR-TO – vapor output of the current separator stage.

6. destination – stage outlet destination of the fluid defined previously. The available
options are:

• Stage_number – the number of separator’s stage;

• 'GAS' – gas stream is indicated as the surface destination stream;
• 'OIL' – oil stream is indicated as the surface destination stream;
• 'INL' – intermediate fluid stream is indicated as the surface destination stream.

II. stream_lines – one or several lines (one per stage) defining which fluid density calculation
method will be used.

The data should be entered in the following format:

*STREAM-DEN f luid method param Psep T sep

1. *STREAM-DEN – sub-keyword indicating that density calculation method will be en-

tered next;

2. f luid – fluid type. Three options are available:

• 'GAS' – gas stream;

• 'OIL' – oil stream;
• 'INL' – intermediate fluid stream.

3. method – fluid density calculation method:

• *EOS – stream density will be calculated from Equation Of State.

• *MIX – stream density will be calculated as a combination of its components mass
densities.
• *GASLAW – stream density will be calculated from Gas Law with consideration
of gas compressibility (z-factor).
mstream ∗ Pstream
ρstream = (13.7)
Z ∗ R ∗ Tstream

4. param – additional parameter required for fluid density calculation. Depending on the
calculation method defined previously, one of the following parameters should be spec-
ified:

13.7.29. SEPARATOR 2313

Keywords for formats tN, IM, ST, GE 19.1

• If *EOS is set – EOS region number;

• If *MIX is set – number of components densities table (DENSTR-MIX, see 13.9.36);
• If *GASLAW is set – compressibility factor value (z-factor).

5. Psep – separator stage pressure (SI: kPa; FIELD: psi).

! This parameter is not compatible with *MIX method of stream density

calculation.

6. T sep – separator stage temperature (SI: kPa; FIELD: psi).

! This parameter is not compatible with *MIX method of stream density

calculation.

This keyword has E3-compatible analogs: FIPSEP (see 12.16.25) and SEPDEN
(see 12.16.31).

Example
*SEPARATOR 815.00 80.00
65.00 80.00
14.70 60.00

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.29. SEPARATOR 2314

Keywords for formats tN, IM, ST, GE 19.1

13.8. Numerical methods control

13.8.1. NUMERICAL

Data x tN E1 E3 x IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial x Numerical Well

The keyword starts the section ”Numerical methods control” (13.8).

Example
NUMERICAL

13.8. Numerical methods control 2315

Keywords for formats tN, IM, ST, GE 19.1

13.8.2. TFORM

Data x tN E1 x E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial x Numerical Well

See the keyword TFORM (see 12.1.10).

13.8.2. TFORM 2316

Keywords for formats tN, IM, ST, GE 19.1

13.8.3. ISOTHERMAL

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial x Numerical Well

See description of the option ISOTHERMAL of the keyword TNAVCTRL (see 12.1.4).

13.8.3. ISOTHERMAL 2317

Keywords for formats tN, IM, ST, GE 19.1

13.8.4. MINTEMP

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial x Numerical Well

The keyword specifies minimal formation temperature. The following parameters should
be specified:

1. minimal formation temperature (SI: ◦ C, FIELD: ◦ F);

Default: 1.

Analogous to the keyword is the 1-st parameter of the keyword TRANGE (see 12.19.251),
which is used by E1/E3.
Example
MINTEMP 50

13.8.4. MINTEMP 2318

Keywords for formats tN, IM, ST, GE 19.1

13.8.5. MAXTEMP

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial x Numerical Well

The keyword specifies maximal formation temperature. The following parameters should
be specified:

1. maximal formation temperature (SI: ◦ C, FIELD: ◦ F).

Default: 200.

Analogous to the keyword is the 2-nd parameter of the keyword TRANGE (see 12.19.251),
which is used by E1/E3.
Example
MAXTEMP 250

13.8.5. MAXTEMP 2319

Keywords for formats tN, IM, ST, GE 19.1

13.8.6. RELAX

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial x Numerical Well

The keyword sets control parameters for simulator.

This keyword is IGNORED because of specific methods of solution used in tNavigator.
To set tNavigator iteration process parameters use the keyword RUNCTRL (see 12.19.140).

13.8.6. RELAX 2320

Keywords for formats tN, IM, ST, GE 19.1

13.8.7. SOLVER / PNTHRDS

Data x tN E1 E3 IM GE ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial x Numerical Well

These keywords allow to specify which solver (parallel on non-parallel) will be used for
calculations and the number of threads in other simulators.
This keyword is IGNORED because of specific methods of solution used in tNavigator.

13.8.7. SOLVER / PNTHRDS 2321

Keywords for formats tN, IM, ST, GE 19.1

13.9. Well and recurrent data

13.9.1. RUN

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

The keyword starts the section ”Well and recurrent data” (13.9).
Example
RUN

13.9. Well and recurrent data 2322

Keywords for formats tN, IM, ST, GE 19.1

13.9.2. STOP

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

The keyword terminates the simulation. The data after STOP is ignored.
The keyword has an E1/E3-compatible analogue END (see 12.1.113).
Example
DATE 1973 4 17
STOP

The simulation terminates on April 17, 1973.

13.9.2. STOP 2323

Keywords for formats tN, IM, ST, GE 19.1

13.9.3. DATE

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

The keyword sets the date and exact 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.1) to denote the
date of simulation start (an E1/E3-compatible analogue is START, see 12.1.18).
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 E1/E3-compatible analogue DATES (see 12.19.124).

Example
DATE 1973 4 17.5
This example sets the date: April 17, 1973, at noon.

13.9.3. DATE 2324

Keywords for formats tN, IM, ST, GE 19.1

13.9.4. TIME

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keyword indicates the moment in time when changes occur. It should be specified in
the following format:

TIME num

num – elapsed time after beginning of simulation (days). Must be a real number.
Example
*TIME 0.0

...
*TIME 31.0
This example sets the time moment one month after beginning of simulation.

13.9.4. TIME 2325

Keywords for formats tN, IM, ST, GE 19.1

13.9.5. GROUP

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

The keyword sets tree structure for multi-level group control and cumulative output. The
tree can consist of an arbitrary number of levels.

The data should be entered in the following format:

*GROUP 'child_1' 'child_2' ... 'child_n' *ATTACHTO 'parent'

Where:

• 'child_i' – name of child group that is attached to the 'parent' group. All groups must
have a unique name (40 characters maximum) and each child must be assigned to one
'parent' group via *ATTACHTO sub-keyword.

• 'parent' – name of the parent group. Top-level group will be identified by simulator
while reading the groups’ structure. Note that the top-level group cannot be used as a
child.

If no groups are identified, simulator will use 'FIELD' for cumulative output. However, group
control cannot be used in this case.
For any level of the group hierarchy must have either wells or other groups connected to them.
Both wells and groups cannot be attached to the same parent.
The keyword is analogous to the first parameter of an E1/E3-compatible keyword GRUPTREE
(see 12.19.100).
The pictures below illustrate correct and incorrect GROUP settings:

13.9.5. GROUP 2326

Keywords for formats tN, IM, ST, GE 19.1

Correct GROUP setting:

'Producer1'
'Pad1'
'Producer2'
'Producers'

'Pad2' 'Producer3'

'FIELD'

'Injector1'

'Injectors' 'Injector2'

'Injector3'

Incorrect GROUP setting:

'Producer1'
'Pad1'
'Producer2'
'Producers'

'Producer3'

'FIELD'

'Injector1'

'Injectors' 'Injector2'

'Injector3'

13.9.5. GROUP 2327

Keywords for formats tN, IM, ST, GE 19.1

Example
*GROUP ’Producers’ ’Injectors’ *ATTACHTO ’FIELD’
*GROUP ’Pad1’ ’Pad2’ *ATTACHTO ’Producers’
*WELL ’Producer1’ *ATTACHTO ’Pad1’
*WELL ’Producer2’ *ATTACHTO ’Pad1’
*WELL ’Producer3’ *ATTACHTO ’Pad2’
*WELL ’Injector1’ *ATTACHTO ’Injectors’
*WELL ’Injector2’ *ATTACHTO ’Injectors’
*WELL ’Injector3’ *ATTACHTO ’Injectors’

This example sets group structure according to the tree diagram provided above.

13.9.5. GROUP 2328

Keywords for formats tN, IM, ST, GE 19.1

13.9.6. WELL

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

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 both 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 E1/E3-compatible analogue WELSPECS (see 12.19.3) (four parame-
ters 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 2329

Keywords for formats tN, IM, ST, GE 19.1

13.9.7. PRODUCER

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

The keyword specifies a producer (first a well should be entered using the keyword WELL,
see 13.9.6).

The data should be specified in the following format:

*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 E1/E3-compatible keyword WCON-
PROD (see 12.19.42).
Example
*WELL 7
*PRODUCER 7
The example specifies the well number 7 as producer.

13.9.7. PRODUCER 2330

Keywords for formats tN, IM, ST, GE 19.1

13.9.8. INJECTOR

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

The keyword specifies an injector (first a well should be entered using the keyword WELL,
see 13.9.6).

The data should be specified in the following format:

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 E1/E3-compatible analogue WCONINJE (see 12.19.44).

Example
*WELL 10
*INJECTOR *UNWEIGHT 10
In this example the well 10 is unweighted injector.

13.9.8. INJECTOR 2331

Keywords for formats tN, IM, ST, GE 19.1

13.9.9. BHPDEPTH

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keyword redefines the reference depth for a well or for several wells. The wells must
be previously initialized via keyword WELL (see 13.9.6).

The data should be entered in the following format:

*BHPDEPTH well_list values

Where:

1. well_list — list of well names or well numbers.

2. values — updated values of reference depths. One number should be entered for each
well from the well-list.

The keyword has an E1/E3-compatible analogue WELTARG (see 12.19.60).

Example
*BHPDEPTH 'Producer1' 'Producer2'
1250 1400

In this example new refence depths are defined for the wells 'Producer1' and 'Producer2'.
These depth may not coincide with the wells’ completions.

13.9.9. BHPDEPTH 2332

Keywords for formats tN, IM, ST, GE 19.1

13.9.10. GEOMETRY

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

The keyword specifies several geometric characteristics of the well. The data is used to
obtain the well flow index.

The data should be entered in the following format:

*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 corre-
sponds 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 E1/E3-compatible analogue COMPDAT (see 12.19.6) (several param-
eters of COMPDAT correspond to GEOMETRY).
Example
WELL 8
PRODUCER 8
OPERATE MIN BHP 250 CONT
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;

• well radius is equal to 0.0762 m;

• geometric well factor – 0.37;

13.9.10. GEOMETRY 2333

Keywords for formats tN, IM, ST, GE 19.1

• the hole circle is corresponding to the well;

• skin – 0.

13.9.10. GEOMETRY 2334

Keywords for formats tN, IM, ST, GE 19.1

13.9.11. PERF

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keywords describes the grid blocks in which the wellbore was completed. At first the
well must be initialized with keywords WELL (see 13.9.6), PRODUCER (see 13.9.7), INJEC-
TOR (see 13.9.8), GEOMETRY (see 13.9.10).

The data should be entered in the following format:

PERF (WI)(GEO|GEOA)(KH|KHA)(SKIN)(TURB)(QUAD|PSEUDOP)wn
location well − index rel − perm status connection

Where:

1. Data entered in the same line with *PERF keyword:

• WI – this subkeyword indicates that the well index is defined explicitly. This
parameter prevails over all other definitions of well index. Thus, if *WI is defined,
well index will be set according to *WI.
• GEO – this sub-keyword indicates that the well index is calculated from the ge-
ometric information, dimensions and permeability of the grid blocks in which
wellbore is situated. Initial data must be specified previously in GEOMETRY
(see 13.9.10) keyword. In this case well pressure equivalent radius is computed
with a use of geometric well factor:

For a vertical well (Z direction):

re = geo f ac × (DX · DY / (π · w f rac))1/2

For a horizontal well (X direction):

re = geo f ac × (DX · DZ/ (π · w f rac))1/2

For a horizontal well (Y direction):

re = geo f ac × (DY · DZ/ (π · w f rac))1/2

where DX, DY, DZ are the block’s dimentions, geo f ac and w f rac are the well
factors components defined in GEOMETRY (see 13.9.10).

13.9.11. PERF 2335

Keywords for formats tN, IM, ST, GE 19.1

• GEOA – the same as GEO, but the well pressure equivalent radius is computed
with Peaceman formula:
For a vertical well (Z direction):

1/2  1/2 
re = 0.28 DX 2 ky + DY 2 kx / kx + ky1/2

For a horizontal well (X direction):

1/2  1/2 
re = 0.28 DX 2 kz + DZ 2 kx / kx + kz1/2

For a horizontal well (Y direction):

1/2  1/2 
re = 0.28 DY 2 ky + DZ 2 kx / ky + kz1/2

• KH – permeability-thickness of the block (average permeability in the plane or-

thogonal to the wellbore times block’s thickness). (SI: mD−m, FIELD: mD− f t ).
This parameter can be used only if GEOMETRY, see 13.9.10) keyword has been
specified previously.
• KHA – the same as KH, but the well pressure equivalent radius is computed with
Peaceman formula: (see parameter GEOA. (SI: md−m, FIELD: md− f t ).
This parameter can be used only if GEOMETRY, see 13.9.10) keyword has been
specified previously.
• SKIN – skin factor. (SI: dimensionless, FIELD: dimensionless).
• TURB – turbulent skin-factor, used for gas flow calculation. (SI: day−m3 , FIELD:
day− f t 3 ).
If this parameter is specified, then total skin would computed as follows:
skin0 = skin + di · qg
where skin is the constant skin, di is the flow-dependent skin defined by *TURB
and qg is the molar gas flow rate.
• QUAD – gas inflow to / outflow from a well is calculated using a quadratic in-
flow relationship. It is assumed that the density of the gas near the wellbore is
proportional to its pressure and a flow rate is:
2 2
q = wi × MP (Pblock − Pwell )/2Pblock
where wi is the well index (see 4-th parameter), MP is the phase mobility.
• PSEUDOP – gas inflow to / outflow from a well is calculated using the expression
which includes variation in both gas molar density and gas viscosity with pressure:
q = wi × Krg × (ρ/µ)avg × (Pblock − Pwell )
where ρ is molar density and µ is viscosity.
If neither QUAD nor PSEUDOP were defined, the standard formulation will be
used.

13.9.11. PERF 2336

Keywords for formats tN, IM, ST, GE 19.1

• wn – well number or well name.

2. Data entered in the lines below *PERF keyword:

• location – three numbers i, j, k – X, Y and Z coordinates of grid block in which

the wellbore is perforated.
• well-index – set values corresponding to the parameters defining well index (*WI,
*GEO|*GEOA, *SKIN, *TURB) entered in the first line.
• well-index – value corresponding to the parameter defining permeability-thikness
of perforation (*KH|*KHA) entered in the first line.
• status – block status: OPEN or CLOSED. OPEN – perforated interval is open (this
is default status if status isn’t specified). CLOSED – this block is specified to define
the well trajectory. Perforated interval can be opened using the keyword *PERF or
*PERFV next time.
• 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.
Here ily is the 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.

This keyword is a partial analogue of E1/E3-compatible keywords COMPDAT (see 12.19.6)

and WELSPECS (see 12.19.3).
Example
*PERF *GEO *SKIN *TURB *KH ’Producer1’
4 7 3 5.0 12 3 4000 OPEN *FLOW-TO ’SURFACE’ REFLAYER
4 7 4 5.0 12 3 4000 OPEN *FLOW-TO 1
4 7 5 5.0 12 3 4000 OPEN *FLOW-TO 2
4 7 6 5.0 12 3 4000 CLOSED *FLOW-TO 3
4 7 7 5.0 12 3 4000 OPEN *FLOW-TO 4

In this example five blocks with perforations are described (1-st block (4, 7, 3), 2-nd
block: (4, 7, 4), 3-rd block: (4, 7, 5), 4-th block: (4, 7, 6), 5-th block: (4, 7, 7)) for the well
'Producer1'.

The sub-keyword *GEO sets that the well index is calculated from the geometric informa-
tion provided in GEOMETRY (see 13.9.10), dimensions and permeability of the grid blocks
in which wellbore is situated. Here, the multiplier for *GEO is equal to 5 in all blocks (well

13.9.11. PERF 2337

Keywords for formats tN, IM, ST, GE 19.1

index is multiplied by this multiplier).

Sub-keywords *SKIN *TURB set the constant and flow-dependent components of total
skin. Here, the value for *SKIN is equal to 12 the value for *TURB is equal to 3 day−m3 in
all blocks.

The sub-keyword *KH sets the permeability-thickness of perforations Here, the value for
*KH is equal to 4000 mD−m in all blocks.

Perforated intervals are opened in all blocks except the 4th 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.11. PERF 2338

Keywords for formats tN, IM, ST, GE 19.1

13.9.12. PERFV

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keywords describes the grid blocks in which the wellbore was completed. It is a
another form of PERF (see 13.9.11) keyword that could be used for vertical wells. In this case
horizontal locations are specified via *VERT sub-keyword of the WELL (see 13.9.6) keyword.
Several vertical wells can be defined with a single *PERFV keyword it all of them are com-
pleted in the same set of layers.
At first the well must be initialized with keywords WELL (see 13.9.6), PRODUCER
(see 13.9.7), INJECTOR (see 13.9.8), GEOMETRY (see 13.9.10).

The data should be entered in the following format:

PERFV (WI)(GEO|GEOA)(KH|KHA)(SKIN)(TURB)(QUAD|PSEUDOP)wn
location well − index rel − perm status
Where:
1. Data entered in the same line with *PERFV keyword:

• WI – this subkeyword indicates that the well index is defined explicitly. This
parameter prevails over all other definitions of well index. Thus, if *WI is defined,
well index will be set according to *WI.
• GEO – this sub-keyword indicates that the well index is calculated from the ge-
ometric information, dimensions and permeability of the grid blocks in which
wellbore is situated. Initial data must be specified previously in GEOMETRY
(see 13.9.10) keyword. In this case well pressure equivalent radius is computed
with a use of geometric well factor:

For a vertical well (Z direction):

re = geo f ac × (DX · DY / (π · w f rac))1/2
For a horizontal well (X direction):
re = geo f ac × (DX · DZ/ (π · w f rac))1/2
For a horizontal well (Y direction):
re = geo f ac × (DY · DZ/ (π · w f rac))1/2

where DX, DY, DZ are the block’s dimentions, geo f ac and w f rac are the well
factors components defined in GEOMETRY (see 13.9.10).

13.9.12. PERFV 2339

Keywords for formats tN, IM, ST, GE 19.1

• GEOA – the same as GEO, but the well pressure equivalent radius is computed
with Peaceman formula:
For a vertical well (Z direction):

1/2  1/2 
re = 0.28 DX 2 ky + DY 2 kx / kx + ky1/2

For a horizontal well (X direction):

1/2  1/2 
re = 0.28 DX 2 kz + DZ 2 kx / kx + kz1/2

For a horizontal well (Y direction):

1/2  1/2 
re = 0.28 DY 2 ky + DZ 2 kx / ky + kz1/2

• KH – permeability-thickness of the block (average permeability in the plane or-

thogonal to the wellbore times block’s thickness). (SI: mD−m, FIELD: mD− f t ).
This parameter can be used only if GEOMETRY, see 13.9.10) keyword has been
specified previously.
• KHA – the same as KH, but the well pressure equivalent radius is computed with
Peaceman formula: (see parameter GEOA. (SI: md−m, FIELD: md− f t ).
This parameter can be used only if GEOMETRY, see 13.9.10) keyword has been
specified previously.
• SKIN – skin factor. (SI: dimensionless, FIELD: dimensionless).
• TURB – turbulent skin-factor, used for gas flow calculation. (SI: day/sm3 , FIELD:
day/sc f 3 ).
If this parameter is specified, then total skin would computed as follows:
skin0 = skin + di · qg
where skin is the constant skin, di is the flow-dependent skin defined by *TURB
and qg is the molar gas flow rate.
• QUAD – gas inflow to / outflow from a well is calculated using a quadratic in-
flow relationship. It is assumed that the density of the gas near the wellbore is
proportional to its pressure and a flow rate is:
2 2
q = wi × MP (Pblock − Pwell )/2Pblock
where wi is the well index (see 4-th parameter), MP is the phase mobility.
• PSEUDOP – gas inflow to / outflow from a well is calculated using the expression
which includes variation in both gas molar density and gas viscosity with pressure:
q = wi × Krg × (ρ/µ)avg × (Pblock − Pwell )
where ρ is molar density and µ is viscosity.
If neither QUAD nor PSEUDOP were defined, the standard formulation will be
used.

13.9.12. PERFV 2340

Keywords for formats tN, IM, ST, GE 19.1

• wn – well number/range of well numbers/list of well numbers.

2. Data entered in the lines below *PERFV keyword:

• location – Z coordinate of grid block in which wellbore is located.

• well-index – set values corresponding to the parameters defining well index (*WI,
*GEO|*GEOA, *SKIN, *TURB) entered in the first line.
• well-index – value corresponding to the parameter defining permeability-thikness
of perforation (*KH|*KHA) entered in the first line.
• status – block status: OPEN or CLOSED. OPEN – perforated interval is open (this
is default status if status isn’t specified). CLOSED – this block is specified to define
the well trajectory. Perforated interval can be opened using the keyword *PERF or
*PERFV next time.

This keyword is a partial analogue of E1/E3-compatible keywords COMPDAT (see 12.19.6)

and WELSPECS (see 12.19.3).
Example
*WELL ’Producer1’ *VERT 4 7
*WELL ’Producer2’ *VERT 3 10
*PERFV *GEO *SKIN *TURB *KH ’Producer1’ ’Producer2’
3:7 5.0 12 3 4000 OPEN

In this example two vertical wells are defined by single *PERFV keyword. Consequently,
the same completion properties will be defined for both wells.

The sub-keyword *GEO sets that the well index is calculated from the geometric informa-
tion provided in GEOMETRY (see 13.9.10), dimensions and permeability of the grid blocks
in which wellbore is situated. Here, the multiplier for *GEO is equal to 5 in all blocks (well
index is multiplied by this multiplier).

Sub-keywords *SKIN *TURB set the constant and flow-dependent components of total
skin. Here, the value for *SKIN is equal to 12 the value for *TURB is equal to 3 day/sm3 in
all blocks.

The sub-keyword *KH sets the permeability-thickness of perforations Here, the value for
*KH is equal to 4000 mD−m in all blocks.

Perforated intervals are opened in all blocks except the 4th block.

13.9.12. PERFV 2341

Keywords for formats tN, IM, ST, GE 19.1

13.9.13. LAYERXYZ

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

The keyword defines perforations which are situated on the deviated wellbore. Previously
these perforations should be initialized using the keyword PERF (see 13.9.11).

The data should be entered in the following format:

*LAYERXYZ wn location x1 y1 z1 x2 y2 z2 plength

where:

1. wn is the well name (number).

2. location is a set of 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 are the 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 are the 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 is the 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 IM and ST:

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.13. LAYERXYZ 2342

Keywords for formats tN, IM, ST, GE 19.1

• 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.8)
π · h( j) · w f rac

where
• j ∈ x, y, z; geo f ac — geometric well factor (see GEOMETRY, see 13.9.10);
• 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.9)

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.10)

( 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.13. LAYERXYZ 2343

Keywords for formats tN, IM, ST, GE 19.1

13.9.14. KRPERF

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keyword defines the relative permeability table set numbers and end points for well
completions.
Previously the perforations should be initialized using the keyword PERF (see 13.9.11).

The data should be entered in the following format:

*KRPERF wn
location permeability_dat

where:

1. wn is the well name (number). This token is optional. If absent, it is inherited from the
immediately preceeding PERF (see 13.9.11).

2. location is a set of integers that define the coordinates of the grid block with the per-
foration: I, J, K, optionally followed by /I1 , J1 , K1 (these refer to the coordinates of the
parent block in the original grid, if the block with perforation is located within an LGR);

3. permeability_data is a set of one or more sub-keywords described below, each followed

by a number:

• SETN is the saturation function region number to be applied to this block. If not
specified, the default region for this grid block is used;
• SWCON is the minimal water saturation (here and below are the parameters used for
scaling of endpoints of saturation tables, see 2.6.7, 2.6.8);
• SWCRIT is the critical water saturation;
• SOIRW equals one minus maximal water saturation;
• SORW is the critical oil-to-water saturation;
• SGCON is the minimal gas saturation;
• SGCRIT is the critical gas saturation;
• SOIRG equals one minus maximal gas saturation;
• SORG is the critical oil-to-gas saturation.

13.9.14. KRPERF 2344

Keywords for formats tN, IM, ST, GE 19.1

Example
KRPERF
8 8 5 / 3 3 2 SETN 2 SWCON 0.0000 SWCRIT 0.0000 ...
8 8 6 / 3 3 2 SETN 2 SWCON 0.0000 SWCRIT 0.0000 ...
8 8 8 / 3 3 2 SETN 2 SWCON 0.0000 SWCRIT 0.0000 ...

In this example, three block from an LGR are assigned to the saturation function region 2
and given the parameters for scaling of endpoints of saturation tables.

13.9.14. KRPERF 2345

Keywords for formats tN, IM, ST, GE 19.1

13.9.15. SETPI

Data x tN E1 E3 x IM x GE x ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

The keyword specifies productivity/injectivity index (PI) for the wells, or multiplies it by
a factor.
Productivity index (PI) is equal to the production (injection) rate of the phase divided by
the drawdown, where the drawdown is the difference between well’s BHP and the reservoir
pressure at well’s drainage radius.
The data should be entered in the following format:
*SETPI type wells values

where

1. type is the type of condition to be applied, selected from the following:

◦ *OIL: PI of oil will be set to the values specified (SI: sm3 /day/kPa, FIELD:
stb/day/psi);
◦ *WAT: PI of water will be set to the values specified (SI: sm3 /day/kPa, FIELD:
stb/day/psi);
◦ *GAS: PI of gas will be set to the values specified (SI: sm3 /day/kPa, FIELD:
sc f /day/psi);
◦ *LIQ: Summary PI of oil and water will be set to the values specified (SI:
sm3 /day/kPa, FIELD: stb/day/psi);
◦ *TOT: Summary PI of oil, water and gas will be set to the values specified (SI:
sm3 /day/kPa, FIELD: sc f /day/psi);
◦ *MULT: Current PI’s that may have been modified by previous uses of SETPI will
be multiplied by the values specified;
◦ *MULTO: Original PI’s will be multiplied by the values specified. Current well in-
dices that may have been modified/multiplied by previous uses of SETPI will be
ignored.

2. wells is a well name or well names list;

3. values is the list of numbers, one for each well in the list.

Default: none (PI retain their values set before or calculated automatically from the reser-
voir properties).

13.9.15. SETPI 2346

Keywords for formats tN, IM, ST, GE 19.1

This keyword has an E1/E3 compatible analogue WELPI (see 12.19.64).

Example
*SETPI *LIQ PROD1
18.0
In this example productivity index for liquids at the well PROD1 is set to 18.

13.9.15. SETPI 2347

Keywords for formats tN, IM, ST, GE 19.1

13.9.16. WELGEO

Data x tN E1 E3 x IM x GE x ST MO
format
RUNSPEC GRID EDIT PROPS
Section
REGIONS SOLUTION SUMMARY x SCHEDULE

This keyword updates skin factor values for selected wells.

The data should be entered in the following format:
*WELGEO well-list
*SKIN value
Where:

• well-list — list of well names or well numbers.

• value — new value of skin-factor for all wells from well-list. The value should be a real
number. Only one number can be entered in this line

The keyword has an E1/E3-compatible analogue CSKIN (see 12.19.265).

Example
*WELL 'Producer1' *VERT 4 7
*PERFV *SKIN 'Producer1'
3:7 0 OPEN
...
*WELL 'Producer2' *VERT 3 10
*PERFV *SKIN 'Producer2'
3:7 0.75 OPEN
...
*TIME 35.0
*WELGEO 1:2
*SKIN -1.5

In this example two wells are initialized via WELL (see 13.9.6) and PERFV (see 13.9.12)
keywrods.
Their initial skin factors are defined by *SKIN option of *PERFV keyword. Initial skin factor
is 0 for the well 'Producer1' and 0.75 for the well 'Producer2'.
At a certain time moment (35days) the skin factor of both wells is altered and set equal to
−1.5.

13.9.16. WELGEO 2348

Keywords for formats tN, IM, ST, GE 19.1

13.9.17. SHUTIN / OPEN

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

These keywords indicate wells’ status. The wells must be previously initialized via WELL
(see 13.9.6), PRODUCER (see 13.9.7) or INJECTOR (see 13.9.8) keywords).

Keyword *SHUTIN indicates that a well or several of wells are closed at the surface
Keyword *OPEN indicates that a wel or several of wells are reopened .

The data should be entered in the following format:

*SHUTIN|*OPEN well-list
Where:

• well-list — list of well names or well numbers.

The keyword has an E1/E3-compatible analogue WELOPEN (see 12.19.128).

Example
*DATE 1973 4 17
*SHUTIN 1:3 5 7
*DATE 1973 10 17
*OPEN 1:3 5 7

In this example the wells with numbers 1, 2, 3, 5 and 7 are shut-in on April 17, 1973 and
reopened on October 17, 1973.

13.9.17. SHUTIN / OPEN 2349

Keywords for formats tN, IM, ST, GE 19.1

13.9.18. WLISTSHUT / WELISTOPEN

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

These keywords are the equivaletnts of SHUTIN / OPEN (see 13.9.17) keywords.
Keyword WLISTSHUT indicates that a wel or several of wells are closed at the surface
(first a well should initialized via WELL (see 13.9.6), PRODUCER (see 13.9.7) or INJECTOR
(see 13.9.8) keywords).

Keyword WELISTOPEN indicates that a wel or several of wells are reopened .

The data should be entered in the following format:

*WLISTSHUT|*WLISTOPEN well-list
Where:

• well-list — list of well names or well numbers.

These keywords have an E1/E3-compatible analogue WELOPEN (see 12.19.128).

Example
*DATE 1973 4 17
*WLISTSHUT 1:3 5 7
*DATE 1973 10 17
*WELISTOPEN 1:3 5 7

In this example the wells with numbers 1, 2, 3, 5 and 7 are shut-in on April 17, 1973 and
reopened on October 17, 1973.

13.9.18. WLISTSHUT / WELISTOPEN 2350

Keywords for formats tN, IM, ST, GE 19.1

13.9.19. DRILLQ

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keyword defines the autodrilling sequence for the wells. Section Prioritized drilling
queue. Sequential drilling queue – 2.14.14.

The data should be entered in the following format:

*DRILLQ well_list

• well_list – list of names or numbers of the wells that defines the sequence in which they
will be drilled (i.e. swithced from SHUTIN (see 13.9.17) status to OPEN, see 13.9.17).
The wells will be drilled in the same order as they are indicated in the list.

The well list may contain both producers and injectors.

This keyword has an E1/E3-compatible analog – QDRILL (see 12.19.229)

Example
*DRILLQ 'Well_1' 'Well_2' 'Well_3' 'Well_4'

13.9.19. DRILLQ 2351

Keywords for formats tN, IM, ST, GE 19.1

13.9.20. MODELSHUT

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keyword activates crossflow option for the wells closed above reservoir.
The data should be entered in the following format:
*MODELSHUT (well-list)(*ON|*OFF)
where:

• well-list – one or several well names. The wells may be producers or injectors. If no
well is selected the keyword is applied to all wells;

• ON – Crossflow option is switched on.

• OFF – Crossflow option is switched off.

Example
*MODELSHUT 'Producer1' ON
In this example the well 'Producer1' is closed at surface and cross-flow in its wellbore is
allowed.

13.9.20. MODELSHUT 2352

Keywords for formats tN, IM, ST, GE 19.1

13.9.21. XFLOW-MODEL

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keyword is used to define the method for modeling well backflow and crossflow for
a specified set of well.

The data should be entered in the following format:

*XFLOW-MODEL (well_list )(*FULLY-MIXED | *ZERO-FLOW)

where:

• well_list – one or several well names. The wells may be producers or injectors. If no
well is selected the keyword is applied to all wells;

• *FULLY-MIXED – Backflow or crossflow in the wellbore is modelled based on the

assumption of complete mixing in a wellbore of zero volume (Coats et al, SPE 29111,
1995).

• *ZERO-FLOW – Backflow or crossflow is handled by setting layer flows to zero. The

layer is not closed and pressures changes may result in forward flow.

Default: For all wells, for which the keyword XFLOW-MODEL (see 13.9.21) is not defined,
it is assumed zero flow (option *ZERO-FLOW). If neither XFLOW-MODEL (see 13.9.21), nor
*ZERO-FLOW is not selected after list of wells (well_list ) in the keyword XFLOW-MODEL
(see 13.9.21) then for all wells from the list *FULLY-MIXED option is applied. Options
*FULLY-MIXED and *ZERO-FLOW can not be used simultaneously for one well. Option
*FULLY-MIXED is not available for unweighted injectors and limited entry perforation (LEP)
wells.

An E1/E3-compatible analogue is the crossflow ability flag (10-th parameter of the key-
word WELSPECS, see 12.19.3).
Example
*well 1 "prod"
*xflow-model "prod" *fully-mixed
*well 2 "prod"
*xflow-model "prod" *zero-flow
In this example, for the well 1 *FULLY-MIXED is selected and for the well 2 option
*ZERO-FLOW is selected.

13.9.21. XFLOW-MODEL 2353

Keywords for formats tN, IM, ST, GE 19.1

13.9.22. ON-TIME

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

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.

The data should be entered in the following format:

*ON-TIME well_name
OT F_input

where:

• well_name is the well name (should be entered immediately after *ON-TIME, on the
same line);

• OT F_input is the 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 E1/E3-compatible analogue WEFAC (see 12.19.83).

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.22. ON-TIME 2354

Keywords for formats tN, IM, ST, GE 19.1

13.9.23. OPERATE

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

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:

First data input format

*OPERATE (*MAX|*MIN) well_control value action

Second data input format

*OPERATE *MIN *STEAMTRAP value
Third data input format
*OPERATE *WCUTBACK well_control control_phase value value2 value3 action

where:

1. control type:

• MAX (or MIN) – maximum (MAX) or minimum (MIN) control is specified using
value;
• WCUTBACK – specifies well cutback limits. A rate will be reduced if under control
parameter (control p hase) violates a limit specified by value.

2. well − control – well control:

• STL – liquid rate control (oil and water) (SI: sm3 /day, FIELD: stb/day) (LRAT
in E1/E3-compatible keywords).
This control is valid for producers only,
• STO – oil rate control (SI: sm3 /day, FIELD: stb/day) (ORAT in E1/E3-
compatible keywords),
• STG – gas rate control (SI: sm3 /day, FIELD: sc f /day) (GRAT in E1/E3-
compatible keywords),
• STW – water rate control (SI: sm3 /day, FIELD: stb/day) (WRAT in E1/E3-
compatible keywords),
• BHF – reservoir fluid rate control (oil+gas+water) (SI: rm3 /day, FIELD: rb/day)
(RESV in E1/E3-compatible keywords).

13.9.23. OPERATE 2355

Keywords for formats tN, IM, ST, GE 19.1

• 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 E1/E3-compatible keywords),
• WHP – tubing head pressure control (SI: kPa, FIELD: psi) (THP in E1/E3-
compatible keywords),
• STEAM – This control is applicable only for Thermal models.
Steam rate expressed in CWE – cold water equivalent (SI: m3 /day, FIELD:
b/day). In case if STEAM is used the 1-st parameter of OPERATE should be
MAX. (STEAM corresponds to CWE, specified via 15-th parameter of WCON-
PROD (see 12.19.42), compatible with E3);
• STEAMTRAP value – This control is applicable only for Thermal models.
the value is by which the steam saturation temperature exceeds the temperature of
the produced water (SI: ◦ C, FIELD: ◦ F) (corresponds to the 17-th parameter of
the keyword WCONPROD (see 12.19.42) compatible with E3);
• STEAM1 – steam rate control. Steam rate is expressed in cold water equiva-
lent (CWE) (SI: m3/day, FIELD: bbl/day). See also STEAM. To use STEAM1
WCUTBACK should be set as the first parameter in the keyword OPERATE.

3. control_phase – The phase for which the rate is reduced. It is specified only for pro-
ducers.

• BHF – reservoir fluid rate (oil+gas+water) (SI: rm3 /day, FIELD: rb/day) (RESV
in E1/E3 compatible keywords).

4. value – control value (if the 2-nd parameter is not STEAMTRAP);

5. value2 – rate cutback factor (the ratio of reduced flow rate to current flow rate), it
varies from 0 to 1. The reduced rate is multiplied by rate cutback factor. If value2 is
not specified or larger than or equal to 1 then the internally calculated cutback factor
will be implemented. value must be entered before value2 . value2 can be specified if
only the first parameter is set to WCUTBACK;

6. value3 – rate cutback factor, positive value. The reduced rate is divided by rate cut-
back factor. This value should be in agreement with value. value3 must be entered
after value2 . If value3 is not specified the division is not implemented. value3 can be
specified if only the first parameter is set to WCUTBACK.

7. action – action to be done if this control is violated: CONT – well will switch to the
violated control.

This keyword has an E1/E3 compatible analogues: WCONPROD (see 12.19.42) for pro-
ducers and WCONINJE (see 12.19.44) for injectors.
The keyword OPERATE with control type WCUTBACK has an E1/E3 compatible ana-
logues WCUTBACK (see 12.19.54) and WCUTBACKX (see 12.19.55).

13.9.23. OPERATE 2356

Keywords for formats tN, IM, ST, GE 19.1

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.
Example
*WELL 9
*PRODUCER 9
*OPERATE WCUTBACK STEAM1 BHF 10 0.8

In this example the reservoir fluid rate will be multiplied by 0.8 if the steam rate exceeds
10 (SI: m3 /day, FIELD: /day).

13.9.23. OPERATE 2357

Keywords for formats tN, IM, ST, GE 19.1

13.9.24. OPERATE-HIST

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keyword applies historical control for wells operating under constraints set by OP-
ERATE (see 13.9.23) keyword.

The data should be entered in the following format:

*OPERATE-HIST well_list type
where:
1. well-list – the list of wells names or wells numbers, to which historical control will be
applied;
2. type – defines the constraint type, which would be used for history matching. It should
be defined as one on the following items:
• STL – liquid rate control (oil and water) (SI: sm3 /day, FIELD: stb/day) (LRAT
in E1/E3-compatible keywords),
• STO – oil rate control (SI: sm3 /day, FIELD: stb/day) (ORAT in E1/E3-
compatible keywords),
• STG – gas rate control (SI: sm3 /day, FIELD: sc f /day) (GRAT in E1/E3-
compatible keywords),
• STW – water rate control (SI: sm3 /day, FIELD: stb/day) (WRAT in E1/E3-
compatible keywords),
• OFF – disables historical control.
The keyword has an E1/E3-compatible analogues: WCONHIST (see 12.19.43) and WCON-
INJH (see 12.19.47).
Example
*TIME 1.0
*WELL 1 `Producer1'
*PRODUCER 1
*OPERATE *MAX *STO 350 *CONT
*OPERATE *MIN *BHP 250 *CONT
*OPERATE-HIST 1 *STL
... ... ...
*TIME 365.0
*OPERATE-HIST 1 *OFF

13.9.24. OPERATE-HIST 2358

Keywords for formats tN, IM, ST, GE 19.1

This example:

• Operation constraints and historical control are assigned to the well 1 via *OPERATE
and *OPERATE-HIST keywords.

• Later, historical control is disabled for this well via *OPERATE-HIST ... *OFF.

13.9.24. OPERATE-HIST 2359

Keywords for formats tN, IM, ST, GE 19.1

13.9.25. ALTER

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keyword alters the first control value for the well, defined by OPERATE (see 13.9.23),
Second and other controls defined by OPERATE (see 13.9.23) can’t be altered using ALTER.

The data should be entered in the following format:

*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 E1/E3-compatible analogue WELTARG (see 12.19.60).

Example
*TIME 1.0
*WELL 1 `Producer1'
*PRODUCER 1
*OPERATE *MAX *STO 350 *CONT
*OPERATE *MIN *BHP 250 *CONT
... ... ...
*TIME 365.0
ALTER 1 450

In this example:

• Operation constraints and historical control are assigned to the well 1.

• Later, the maximum oil rate is altered for this welll.

13.9.25. ALTER 2360

Keywords for formats tN, IM, ST, GE 19.1

13.9.26. ALTER-HIST

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keyword modifies observed flow rates defined in OPERATE (see 13.9.23) keyword
and applies special historical control mode to the wells.

The data should be entered in the following format:

*ALTER-HIST well_list
values
Where:
1. well-list – the list of wells names or wells numbers, which historical data will be modi-
fied;
2. values – defines the values of observed surface flow rate. These values must be entered
in the same order as they were defined by keyword OPERATE (see 13.9.23).
The data for observed rates must be entered in the same order as it was defined in
*OPERATE keywords (see the example for details).
This keyword has an E1/E3-compatible analogues WCONHIST (see 12.19.43) and WCON-
INJH (see 12.19.47).
Example
*TIME 1.0
*WELL 1 `Producer1'
*WELL 2 `Producer2'

*PRODUCER 1
*OPERATE *MAX *STO 350
*OPERATE *MAX *STG 75000
*OPERATE *MIN *BHP 250 **not affected by *ALTER-HIST

*PRODUCER 2
*OPERATE *MAX *STO 750
*OPERATE *MAX *STW 1500
*OPERATE *MIN *BHP 250 **not affected by *ALTER-HIST
... ... ...
*TIME 365.0
*ALTER-HIST 1:2
**STO-1 STG-1 STO-2 STW-2
230 55000 450 990

13.9.26. ALTER-HIST 2361

Keywords for formats tN, IM, ST, GE 19.1

In this example:

• Operation constraints are defined for the wells 1 and 2 via *OPERATE keywords.

• Later, the observed rates for these wells are altered and historical control is applied via
*ALTER-HIST keyword.
The new values are input in the list below *ALTER-HIST in the same order as they were
previously defined by *OPERATE keywords.

13.9.26. ALTER-HIST 2362

Keywords for formats tN, IM, ST, GE 19.1

13.9.27. MONITOR

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keyword sets the well control and action to be done if the control is violated. Un-
like OPERATE (see 13.9.23), the action is applied only after the current timestep has been
completed.
(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 the following format:

*OPERATE well_control value action

where:

1. well-control — type of control parameter:

• GOR – maximum gas/oil ratio control (SI: sm3 /sm3 , FIELD: sc f /stb; WGOR in
E1/E3-compatible keywords),
• WCUT – maximum water cut control (SI: sm3 /sm3 , FIELD: stb/stb; WWCT in
E1/E3-compatible keywords),
• WGR – maximum water/gas ratio control (SI: sm3 /sm3 , FIELD: stb/Msc f ;
WGLR in E1/E3-compatible keywords),
• MAX (or MIN) STL – liquid rate control (SI: sm3 /day, FIELD: stb/day; LRAT
in E1/E3-compatible keywords),
• MAX (or MIN) STO – oil rate control (SI: sm3 /day, FIELD: stb/day; ORAT in
E1/E3-compatible keywords),
• MAX (or MIN) STG – gas rate control (SI: sm3 /day, FIELD: sc f /day; GRAT in
E1/E3-compatible keywords),
• MAX (or MIN) BHP – bottom hole pressure control (SI: kPa, FIELD: psi; BHP
in E1/E3-compatible keywords).

2. value – control value.

3. action – action to be done if this control is violated:

• STOP – the simulation terminates;

• SHUTIN – the well is shut;
• SHUTLAYER – the worst offending perforation is shut;

13.9.27. MONITOR 2363

Keywords for formats tN, IM, ST, GE 19.1

• SHUTLAYER1 – the perforation which, when closed, will have the greatest effect
in terms of bringing the value for the well within the control limits, is shut (for
extensive values like STO this has the same effect as SHUTLAYER; for intensive
values like GOR it can differ);
• AUTOWELL <frequency> – the well is shut, but checked periodically with the
specified frequency in days, and reopened if the limitation is no longer violated.

This keyword has an E1/E3-compatible analogues: WECON (see 12.19.74) for producers
and WECONINJ (see 12.19.81) for injectors.
Example
*MONITOR *MIN BHP 500.0 STOP
*MONITOR *WCUT 0.95 STOP

In this example a well is specified to be shut if the bottom hole pressure drops below 500
kPa or the water cut exceeds 95%.

13.9.27. MONITOR 2364

Keywords for formats tN, IM, ST, GE 19.1

13.9.28. TARGET

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keyword modifies well control constraints. Initially, well control must be defined by
OPERATE (see 13.9.23) keyword.

The data should be entered in the following format:

*TARGET well_control well_list
values
where:
1. well-control – well control:
• STL – liquid rate control (oil and water) (SI: sm3 /day, FIELD: stb/day) (LRAT
in E1/E3-compatible keywords).

• STO – oil rate control (SI: sm3 /day, FIELD: stb/day) (ORAT in E1/E3-
compatible keywords),
• STG – gas rate control (SI: sm3 /day, FIELD: sc f /day) (GRAT in E1/E3-
compatible keywords),
• STW – water rate control (SI: sm3 /day, FIELD: stb/day) (WRAT in E1/E3-
compatible keywords),
• BHF – reservoir fluid rate control (oil+gas+water) (SI: rm3 /day, FIELD: rb/day)
(RESV in E1/E3-compatible keywords).
• BHP – bottom hole pressure control (SI: kPa, FIELD: psi) (BHP in E1/E3-
compatible keywords),
• WHP – tubing head pressure control (SI: kPa, FIELD: psi) (THP in E1/E3-
compatible keywords),
• STEAM – This control is applicable only for Thermal models.
Steam rate expressed in CWE – cold water equivalent (SI: m3 /day, FIELD:
b/day). In case if STEAM is used the 1-st parameter of OPERATE should be
MAX. (STEAM corresponds to CWE, specified via 15-th parameter of WCON-
PROD (see 12.19.42), compatible with E3);
• STEAMTRAP value – This control is applicable only for Thermal models.
the value is by which the steam saturation temperature exceeds the temperature of
the produced water (SI: ◦ C, FIELD: ◦ F) (corresponds to the 17-th parameter of
the keyword WCONPROD (see 12.19.42) compatible with E3).

13.9.28. TARGET 2365

Keywords for formats tN, IM, ST, GE 19.1

2. well-list — list of well names or well numbers.

3. value – list of control values. One number should be entered for each well from the
well-list.

This keyword has an E1/E3-compatible analogues: WCONPROD (see 12.19.42) for pro-
ducers and WCONINJE (see 12.19.44) for injectors.
Example
WELL 1 'Injector1'
*INJECTOR 'Injector1'
*INCOMP *WATER
*OPERATE *MIN *STW 750
*OPERATE *MAX *BHP 3000
...
WELL 2 'Producer1'
*PRODUCER 'Producer1'
*OPERATE *MIN *STO 500
*OPERATE *MIN *BHP 2000
...
*TIME 15.0
*TARGET *BHP 1 2
4500 1500
...
*TIME 115.0
*WTINCR *STW 'Injector1'
1500
*TARGET *STO 'Producer1'
425

In this example two wells are initialized: one injector and one producer. The following
control modes are applied:

• Initial well controls are defined via OPERATE keyword;

• Later on, the BHP controls are altered both for producer and for injector via single
TARGET keyword;

• Finally, flow rate constraints (STW and STO) are modified separately for injector and
for producer.

13.9.28. TARGET 2366

Keywords for formats tN, IM, ST, GE 19.1

13.9.29. WTINCR

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keyword modifies well control constraints by adding an increment to its initial value.
The increment value can be positive or negative. Initially, well control must be defined by
OPERATE (see 13.9.23) keyword. WTINCR keyword cannot be used for specification of new
constraints.

The data should be entered in the following format:

*WTINCR well_control well_list
values
Where:

1. well-control – well control:

• STL – liquid rate control (oil and water) (SI: sm3 /day, FIELD: stb/day) (LRAT
in E1/E3-compatible keywords).
This control is valid for producers only,
• STO – oil rate control (SI: sm3 /day, FIELD: stb/day) (ORAT in E1/E3-
compatible keywords),
• STG – gas rate control (SI: sm3 /day, FIELD: sc f /day) (GRAT in E1/E3-
compatible keywords),
• STW – water rate control (SI: sm3 /day, FIELD: stb/day) (WRAT in E1/E3-
compatible keywords),
• BHF – reservoir fluid rate control (oil+gas+water) (SI: rm3 /day, FIELD: rb/day)
(RESV in E1/E3-compatible keywords).
• BHP – bottom hole pressure control (SI: kPa, FIELD: psi) (BHP in E1/E3-
compatible keywords),
• WHP – tubing head pressure control (SI: kPa, FIELD: psi) (THP in E1/E3-
compatible keywords).

2. well-list — list of well names or well numbers.

3. value – the increments applied to the well constraints . The values should be real num-
bers. One number should be entered for each well from the well-list.

This keyword has an E1/E3-compatible analogue: WTADD (see 12.19.59).

13.9.29. WTINCR 2367

Keywords for formats tN, IM, ST, GE 19.1

Example
WELL 1 'Injector1'
*INJECTOR 'Injector1'
*INCOMP *WATER
*OPERATE *MIN *STW 750
*OPERATE *MAX *BHP 3000
...
WELL 2 'Producer1'
*PRODUCER 'Producer1'
*OPERATE *MIN *STO 500
*OPERATE *MIN *BHP 2000
...
*TIME 15.0
*WTINCR *BHP 1 2
1500 -500
...
*TIME 115.0
*WTINCR *STW 'Injector1'
750
*WTINCR *STO 'Producer1'
-75

In this example two wells are initialized: one injector and one producer. The following
control modes are applied:

• Initial well controls are defined via OPERATE keyword;

• Later on, the BHP controls are altered both for producer and for injector via single
WTINCR keyword;

• Finally, flow rate constraints (STW and STO) are modified separately for injector and
for producer.

13.9.29. WTINCR 2368

Keywords for formats tN, IM, ST, GE 19.1

13.9.30. WTMULT

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keyword modifies well control constraints by applying a multiplier to its initial value.
The multiplier muat be a positive number. Initially, well control must be defined by OPERATE
(see 13.9.23) keyword. WTMULT keyword cannot be used for specification of new constraints.

The data should be entered in the following format:

*WTMULT well_control well_list
values
Where:

1. well-control – well control:

• STL – liquid rate control (oil and water) (SI: sm3 /day, FIELD: stb/day) (LRAT
in E1/E3-compatible keywords).
This control is valid for producers only,
• STO – oil rate control (SI: sm3 /day, FIELD: stb/day) (ORAT in E1/E3-
compatible keywords),
• STG – gas rate control (SI: sm3 /day, FIELD: sc f /day) (GRAT in E1/E3-
compatible keywords),
• STW – water rate control (SI: sm3 /day, FIELD: stb/day) (WRAT in E1/E3-
compatible keywords),
• BHF – reservoir fluid rate control (oil+gas+water) (SI: rm3 /day, FIELD: rb/day)
(RESV in E1/E3-compatible keywords).
• BHP – bottom hole pressure control (SI: kPa, FIELD: psi) (BHP in E1/E3-
compatible keywords),
• WHP – tubing head pressure control (SI: kPa, FIELD: psi) (THP in E1/E3-
compatible keywords).

2. well-list — list of well names or well numbers.

3. value – the multiplers applied to the well constraints . The values should be positive
numbers. One number should be entered for each well from the well-list.

This keyword has an E1/E3-compatible analogue WTMULT (see 12.19.58).

13.9.30. WTMULT 2369

Keywords for formats tN, IM, ST, GE 19.1

Example
WELL 1 'Injector1'
*INJECTOR 'Injector1'
*INCOMP *WATER
*OPERATE *MIN *STW 750
*OPERATE *MAX *BHP 3000
...
WELL 2 'Producer1'
*PRODUCER 'Producer1'
*OPERATE *MIN *STO 500
*OPERATE *MIN *BHP 2000
...
*TIME 15.0
*WTMULT *BHP 1 2
1.5 0.75
...
*TIME 115.0
*WTMULT *STW 'Injector1'
2
*WTMULT *STO 'Producer1'
0.85

In this example two wells are initialized: one injector and one producer. The following
control modes are applied:

• Initial well controls are defined via OPERATE keyword;

• Later on, the BHP controls are altered both for producer and for injector via single
WTMULT keyword;

• Finally, flow rate constraints (STW and STO) are modified separately for injector and
for producer.

13.9.30. WTMULT 2370

Keywords for formats tN, IM, ST, GE 19.1

13.9.31. GCONP

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keyword defines control mode for a group or several groups of producers.

The data should be entered in the following format:

*GCONP groups
mode control value action
where:

1. groups – the name of a group or the list of groups, to which the group control will be
applied.

2. mode – the control mode (type of constraints) assigned to the control.

• MAX – this mode sets the control parameters as the maximum constraints.
• GTARGET – this mode sets the control parameters as the target constraints.

3. control – type of control’s constraint:

• STO – surface oil rate (SI: sm3 /day, FIELD: stb/day; ORAT in E1/E3-compatible
keywords),
• STG – surface gas rate (SI: sm3 /day, FIELD: sc f /day; GRAT in E1/E3-
compatible keywords),
• STW – surface water rate (SI: sm3 /day, FIELD: stb/day; WRAT in E1/E3-
compatible keywords),
• STL – surface liquid rate (SI: sm3 /day, FIELD: stb/day LRAT in E1/E3-
compatible keywords),

4. value – constraint value.

5. action – workover action in case of MAX constraint violation:

• CONT – the violated MAX constraint is switched to GTARGET constrain;

• SHUTMOW – shut in the worst offending well;
• SHUTMOL – shut in the worst offending layer;
• SHUTMOWDOWN – shut in worst offending layers and all layers below.

13.9.31. GCONP 2371

Keywords for formats tN, IM, ST, GE 19.1

This keyword has an E1/E3-compatible analogue: GCONPROD (see 12.19.86).

Example
*GCONP 'Producers'
*GTARGET *STO 5000
*MAX *STG 3000 *SHUTMOW
*MAX *STW 2000 *SHUTMOL

This example shows various definition of group control modes. Here, the group control
constraints are set for the group 'Producers':

• First, the target oil rate is set;

• Then the maximum gas rate is defined. If gas production rate exceeds this value, the
most offensive well (i.e the well with the highest gas production rate) will be shut in;

• Finally, the maximum water rate is defined. If gas production rate exceeds this value,
the most offensive layer (i.e the layer with the highest gas production rate) will be shut
in.

13.9.31. GCONP 2372

Keywords for formats tN, IM, ST, GE 19.1

13.9.32. GCONI

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keyword defines control mode for a group or several groups of injectors.

The data should be entered in the following format:

*GCONI groups
mode control value
where:
1. groups – the name of a group or the list of groups, to which the group control will be
applied.
2. mode – the control mode (type of constraints) assigned to the control.
• MAX – this mode sets the control parameters as the maximum constraints.
• GTARGET – this mode sets the control parameters as the target constraints.
• RECYCLE – this mode is apllicable for the groups that contain both injectors and
producers. It sets the the recycling (reinjection) control parameters, (i.e. the group’s
injection target volume is calculated as a part of the group’s recovered volume).
(SI: rm3 /rm3 , FIELD: rb/rb).
• VREP – this mode is apllicable for the groups that contain both injectors and
producers. It sets a voidage fraction injection target (i.e. injectors from this group
compensate the voidage created by producers from the same group)
(SI: rm3 /rm3 , FIELD: rb/rb).
3. control – type of control’s constraint:
• STG – surface gas rate (SI: sm3 /day, FIELD: sc f /day).
This parameter is applicable for MAX and GTARGET modes only;
• STW – surface water rate (SI: sm3 /day, FIELD: stb/day).
This parameter is applicable for MAX and GTARGET modes only;
• STL – surface liquid rate (SI: sm3 /day, FIELD: stb/day).
This parameter is applicable for MAX and GTARGET modes only;
• BHW – reservoir water rate (SI: rm3 /day, FIELD: rb/day).
This parameter is applicable for MAX and GTARGET modes only;
• BHG – reservoir gas rate (SI: rm3 /day, FIELD: rb/day).
This parameter is applicable for MAX and GTARGET modes only;

13.9.32. GCONI 2373

Keywords for formats tN, IM, ST, GE 19.1

• GAS | WATER – the phase used for voidage replacement or reninjection (SI:
rm3 /rm3 , FIELD: rb/rb).
These parameters are applicable for RECYCLE and VREP modes only. If more
than one phase are injected, then there should be a separate *RECYCLE or *VREP
sub-keyword for each phase.

4. value – constraint value.

This keyword has an E1/E3-compatible analogue: GCONINJE (see 12.19.95).

Inj3
Pad2-INJ
Inj2
Pad2
Prod3
Pad2-PROD
Prod2
FIELD

Inj1
Pad1
Prod1

Example
*GCONI 'Pad1'
*VREP *WATER 0.9

*GCONI 'Pad2-INJ'
*MAX *STW 3000

The group structure corresponding to this example is displayes above.

In this example reservoir voidage replacement contro is defined for the group 'Pad1'containing
both poroducers and injectors. For the second well pad water injection constrains are set for
the grop that contains injectors only - 'Pad2-INJ'.

13.9.32. GCONI 2374

Keywords for formats tN, IM, ST, GE 19.1

13.9.33. GPRODGROUP

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keyword specifies:

1. The well group, or the list of well groups operating under reinjection mode.
2. The well group which production stream rate and composition will be taken for reinjec-
tion.
The well groups are defined by GROUP (see 13.9.5) keyword. The reinjection constraints
can be set via *RECYCLE and *VREP parameters of GCONI (see 13.9.32) keyword.

The data should be entered in the following format:

*GPRODGROUP rein j_group_list *FROM source_group
Where:
• rein j_group_list – the list well groups operating under recycling (*RECYCLE parameter
of GCONI, see 13.9.32) or reservoir voidage (*VREP parameter of GCONI, see 13.9.32)
control mode.
• *FROM – the sub-keyword separating target groups from a source group.
• source_group – the name of the well group, which production stream will be used for
reinjection by the groups listed previously.
This keyword has an E1/E3-compatible analogue: GCONINJE (see 12.19.95) (parameter 11).

Example
*GCONI 'INJ_1'
*RECYCLE *GAS 0.60

*GCONI 'INJ_2'
*VREP *GAS 0.50

*GPRODGROUP 'INJ_1' 'INJ_2' *FROM 'FIELD'

In this example:
1. Gas reinjection is set as the operating mode for the well groups 'INJ_1' and 'INJ_2'.
2. Production stream of the group 'FIELD' is set as the source for 'INJ_1' and 'INJ_2'.

13.9.33. GPRODGROUP 2375

Keywords for formats tN, IM, ST, GE 19.1

13.9.34. GCONM

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keyword defines economic limit for a group or several groups of wells. It sets group
control and defines the action that would be implemented if the limits are violated
Economic control possibilities of tNavigator are summarized in the section 2.14.3.

The data should be entered in the following format:

*GCONM groups
control value action
where:

1. groups – the name of a group or the list of groups, to which the group control will be
applied.

2. control – type of group control:

• GOR – maximum gas-oil ratio (SI: sm3 /sm3 , FIELD: sc f /stb).

Possible actions if the limit is exceeded:
STOP, SHUTMOW, SHUTMOL, SHUTMOLDOWN;
• WCUT – maximum water cut (SI: sm3 /sm3 , FIELD: stb/stb).
Possible actions if the limit is exceeded:
STOP, SHUTMOW, SHUTMOL, SHUTMOLDOWN;
• WGR – maximum water-gas ratio (SI: sm3 /sm3 , FIELD: stb/sc f ).
Possible actions if the limit is exeeded:
STOP, SHUTMOW, SHUTMOL, SHUTMOLDOWN;
• MINOIL – minimum oil rate (SI: sm3 /day, FIELD: stb/day).
Possible actions if the limit is exceeded: STOP;
• MINGAS – minimum gas rate (SI: sm3 /day, FIELD: sc f /day).
Possible actions if the limit is exceeded: STOP.

3. value – constraint value.

4. action – workover action in case of constraint violation:

• STOP – shut in all well of the group and terminate calculations at the next report
time;
• SHUTMOW – shut in the worst offending well;

13.9.34. GCONM 2376

Keywords for formats tN, IM, ST, GE 19.1

• SHUTMOL – shut in the worst offending layer;

• SHUTMOWDOWN – shut in worst offending layers and all layers below.

Only one control can be specified via single keyword. Hence, if several control modes
needed, separate keywords should be used for each control.

This keyword has an E1/E3-compatible analogue: GECON (see 12.19.121).

Example
*GCONM 'Producers'
*WCUT 0.9 *SHUTMOL

*GCONM 'Producers'
*MINOIL 500 *STOP

In this example the economic limits are set for the group 'Producers': maximum water cut
and minimum oil rate.

13.9.34. GCONM 2377

Keywords for formats tN, IM, ST, GE 19.1

13.9.35. WELSEP

Data x tN E1 E3 IM x GE ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

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. sub-keyword 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. sub-keyword STAGE indicating that separator stages will be entered next;
3. sub-keyword 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.83);
5. stage pressure;
6. stage temperature;
7. sub-keyword 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 E1/E3-compatible analogs WSEPCOND (see 12.19.157) and SEPCOND
(see 12.19.156).
Example
*WELSEP 1:4,5 *STAGES 400.0 100.0 101.3 60.0

13.9.35. WELSEP 2378

Keywords for formats tN, IM, ST, GE 19.1

13.9.36. DENSTR-MIX

Data x tN E1 E3 IM x GE ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical x Well

This keyword specifies the tables of components’ densities that could be used for surface
stream mass density computation.

Usage of this keyword does not affect EOS calculations or reservoir fluid flow equations.

The data should be entered in the following format:

*DENSTR-MIX set_number
*DENUNITS (*LIQUID | *GAS)
*COMP-DEN d(1) ... d(nc)

Where:

1. set_number – the number of the component mass density set. This number can
be used by *STREAM-DEN subkeyword of WELSEP (see 13.9.35) or SEPARATOR
(see 13.7.29) keyword in order to assign the set to the separator stream.

2. DENUNITS – this sub-keyword defines density unit in FIELD units system. It should
be followed by another sub-keyword:

• *LIQUID – if FIELD units are set and this sub-keyword is introduced, then the
units for components’ mass density are lbm/bbl .
This unit system is siutable for liquid surface streams, but can be used for any
phase.
• *GAS – if FIELD units are set and this sub-keyword is introduced, then the units
for components’ mass density are lbm/sc f .
This unit system is siutable for gas surface streams, but can be used for any phase.

If FIELD units are set and *DENUNITS sub-keyword is not specified or not followed by
*LIQUID or *GAS identifier, then the units for components’ mass density are lbm/bbl .
If SI unit system is set, then this sub-keyword will be ignored.

3. COMP-DEN – this subkeyword defines the list of components’ mass densities. The list
should contain one value for each component of the system.

• d(1) ... d(nc) – component’s mass densities. nc is the number of last component
of the system.
SI: kg/m3 ; FIELD: lbm/bbl or lbm/sc f .

13.9.36. DENSTR-MIX 2379

Keywords for formats tN, IM, ST, GE 19.1

This keyword has E3-compatible analog: DENSTRMIX (see 12.16.30).

Example
*DENSTR-MIX 1
*DENUNITS *GAS
*COMP-DEN 310 125 430 40 10 15 30 100

In this example the set of components’ mass densities is defines. The density units are
lbm/sc f , specified by *DENUNITS *GAS option.

13.9.36. DENSTR-MIX 2380

Keywords for formats tN, IM, ST, GE 19.1

13.9.37. PLANT-TABLE

Data x tN E1 E3 IM x GE ST MO
format
Input Reservoir Other Component
Section
Rockfluid x Initial Numerical x Well

This keyword is used to specify gas plant recovery table containing oil, NGL (natural
gas liquid) and gas recovery fraction (see section 2.14.5). This table can be used in order to
determine fluid volumes at surface conditions.

The data should be entered in the following format:

*PLANT-TABLE table_number
*KEYF k f KEYL kl *KEYFRAC key_component_mole_ f raction
liquid_ f ractionvapour_ f ractionmiddle_ f raction

Where:

1. Fist line input (a value following *PLANT-TABLE keyword).

• table number – gas plant table number. This number can be user by WELSEP
(see 13.9.35) keyword in order to crate connection betwen separator stage and
fluid stream.

2. Second line input (values following *KEYF and KEYL sub-keywords).

• kf – number of the first component number to define the heavy fractions;

• kl – number of the last component number to define the heavy fractions;

3. Third line input (a value following *KEYFRAC sub-keyword).

• key_component_mole_fraction – heavy component mole fractions;

4. Table input (one line for each component).

• liquid_fraction – oil recovery fraction for one component (the number of moles of
liquid phase per one mole of feed);
• vapour_fraction – gas recovery fraction for one component (the number of moles
of vapour phase per one mole of feed);
• middle_fraction – NGL recovery fraction for one component (the number of moles
of intermediate phase per one mole of feed);

This keyword has an E1/E3-compatible analogue GPTABLE3 (see 12.16.28).

13.9.37. PLANT-TABLE 2381

Keywords for formats tN, IM, ST, GE 19.1

Example
*PLANT-TABLE 1
*KEYF 8 *KEYL 8
*KEYFRAC 0.055
** Liquid Frac. Vapor Frac.
0 1
0 1
0 0
1 0
1 0
1 0
1 0
1 0
Middle Frac.
0 **Component_1
0 **Component_2
1 **Component_3
0 **Component_4
0 **Component_5
0 **Component_6
0 **Component_7
0 **Component_8

In this example:

• Component 8 is the only component that defines the heavy hydrocarbon phase;

• Each line of the table corresponds to individual component;

• First collumn of the table corresponds to the oil recovery fraction of the component;

• Second collumn of the table corresponds to the gas recovery fraction of the component;

• Third collumn of the table corresponds to the NGL recovery fraction of the component.

13.9.37. PLANT-TABLE 2382

Keywords for formats tN, IM, ST, GE 19.1

13.9.38. PTUBE1

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keyword specifies tubing–head (or outlet) pressure data tables for a production (or
manifold group). The bottom–hole (or inlet) pressure and tubing-head (or outlet) pressure
are tabulated along with several independent variables: FLO (rates), water-oil ratio WFR ,
water-gas ratio GFR etc.
The data should be entered in the following format:
*PTUBE1 table_number
*DEPTH re f depth
Flo
f lo(1) f lo(2) ... f lo(NFlo )
Gfr
g f r(1) g f r(2) ... g f r(NG f r )
Wfr
w f r(1) w f r(2) ... w f r(NW f r )
Add
add(1) add(2) ... add(NAdd )
*WHP
whp(1) whp(2) ... whp(NW HP )
*BHP|*THP
i f lo ig f r(2) iw f r iadd bhp(1) ... bhp(NW HP )

On one line, after the keyword a table number should be specified. On the next line the
following parameters should be specified:

• *DEPTH
reference depth (SI: m; FIELD: f t );

• Flo – independent variable: oil rate, liquid rate or gas rate at surface conditions. It is
specified by one of the following keywords:

◦ OIL – oil rate (SI: m3 /day; FIELD: stb/day);

◦ LIQ – liquid rate (SI: m3 /day; FIELD: stb/day);
◦ GAS – gas rate (SI: m3 /day; FIELD: sc f /day);

• Gfr – independent variable: gas-oil ratio, gas-liquid ratio or oil-gas ratio. It is specified
by one of the following keywords:

13.9.38. PTUBE1 2383

Keywords for formats tN, IM, ST, GE 19.1

◦ GOR – gas-oil ratio (SI: sm3 /m3 ; FIELD: sc f /stb);

◦ GLR – gas-liquid ratio (SI: m3 /m3 ; FIELD: sc f /stb);
◦ OGR – oil-gas ratio (SI: m3 /m3 ; FIELD: stb/sc f ).

• Wfr – independent variable: water-oil ratio, water cut (water-liquid ratio), water-gas
ratio. It is specified by one of the following keywords:

◦ WOR – water-oil ratio;

◦ WCUT – water cut (water-liquid ratio);
◦ WGR – water-gas ratio (SI: m3 /m3 ; FIELD: bbl/sc f ).

• Add – additional independent variable can be specified by one of the following key-
words:

◦ LFG – lift gas injection rate (SI: m3 /day; FIELD: sc f /day);

◦ LFR – injection gas-liquid ratio for gas lift (SI: m3 /m3 ; FIELD: sc f /stb);
◦ LFT – total gas-liquid ratio for gas lift (SI: m3 /m3 ; FIELD: sc f /stb);
◦ DNO – surface mass density of oil (SI: kg/m3 ; FIELD: lb/ f t 3 ). The volumetric
weighted average value is taken for a manifold group;
◦ DNG – surface mass density of gas (SI: kg/m3 ; FIELD: lb/ f t 3 ). The volumetric
weighted average value is taken for a manifold group;
◦ ALQ – artificial lift quantity.

• WHP
The well-head (or manifold outlet) pressures (SI: kPa; FIELD: psi);

• BHP
The bottom-hole (or manifold inlet) pressure table (SI: kPa; FIELD: psi);

This keyword has an E1/E3-compatible analogue VFPPROD (see 12.19.66).

13.9.38. PTUBE1 2384

Keywords for formats tN, IM, ST, GE 19.1

Example
PTUBE1 1
DEPTH 213.0
OIL
1000.0 2000.0 3000.0 4000.0 5000.0 7500.0 10000.0 12500.0
15000.0
GOR
0.0 500.0 1000.0 1500.0 2000.0 2500.0
WCUT
0.0 0.2 0.4 0.6 0.8 0.9
LFG
0.0
WHP
500.0 1000.0 2000.0 3000.0 4000.0 5000.0
BHP
1 1 1 1 1904.7 2405.3 3406.8 4406.5 5410.2 6417.4
1 1 2 1 2190.3 2691.2 3693.4 4695.1 5695.2 6703.1
...

13.9.38. PTUBE1 2385

Keywords for formats tN, IM, ST, GE 19.1

13.9.39. PWELLBORE

Data x tN E1 E3 x IM x GE ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keyword allows to specify a well-bore hydraulic pressure table which is used for
pressure loss calculations for a producer.
The data should be entered in the following format:
PWELLBORE (*TABLE)
wdepth table_number
where:

• TABLE
the well-bore hydraulic pressure table specified by keyword PTUBE1 (see 13.9.38) will
be used for pressure loss calculations;

• wdepth
well depth of an producer well (SI: m; FIELD: f t );

• table_number
table number.

This keyword has an E1/E3-compatible analogue WELTARG (see 12.19.60).

Example
PTUBE1 2
DEPTH 12954.0
...
PWELLBORE TABLE 12954.0 2

13.9.39. PWELLBORE 2386

Keywords for formats tN, IM, ST, GE 19.1

13.9.40. PHWELLBORE

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keyword specifies the quantities related to the pressure drop and heat loss for a
producer. It may include a number of parameters:

• SAMODEL
Use semi-analytical model to calculate pressure drop and heat loss along the wellbore
(should always be on; other options are not supported).

• RTUBIN <number>
Inner tubing radius (SI: m, FIELD: ft), analogous to the 5-th parameter of E1/E3-
compatible keyword VFPCORR (see 12.19.71).

• DEPTH <number>
Wellbore depth (SI: m, FIELD: ft), analogous to the 6-th parameter of E1/E3-compatible
keyword VFPCORR (see 12.19.71).

• WLENGTH <number>
Wellbore length (SI: m, FIELD: ft), analogous to the 7-th parameter of E1/E3-compatible
keyword VFPCORR (see 12.19.71).

• KICKOFF_DEPTH <number>
Depth at which the wellbore deviates from vertical (SI: m, FIELD: ft), analogous to the
9-th parameter of E1/E3-compatible keyword VFPCORR (see 12.19.71).
Default: 0.

• RELROUGH <number>
Relative tubing roughness (dimensionless).
Default: 0.0001.

• GEOGRAD <number>
Geothermal gradient (SI: ◦ C/m, FIELD: ◦ F/ft).
Default: 0.

• SURFACE_TEMP <number>
Surface temperature (SI: ◦ C, FIELD: ◦ F).
Default: TSURF (see 13.5.28).

13.9.40. PHWELLBORE 2387

Keywords for formats tN, IM, ST, GE 19.1

Example
PHWELLBORE SAMODEL
DEPTH 65.
RELROUGH 0.00015
RTUBIN 0.15
In this example a tubing with depth 65 m, relative roughness 0.00015, and inner radius 15
cm is defined.

13.9.40. PHWELLBORE 2388

Keywords for formats tN, IM, ST, GE 19.1

13.9.41. GLIFT

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keyword sets parameters for gas lift operations. It either defines lift gas rates for a
given producers or specifies the method for lift gas rates calculation (gas lift optimization).
First, wells must be initialized with keywords WELL (see 13.9.6), PRODUCER (see 13.9.7),
and their well-bore hydraulic pressure table should be specified with keywords PTUBE1
(see 13.9.38) and PWELLBORE (see 13.9.39).

The data should be entered in the following format:

*GLIFT mode well_list
values
where
1. mode – specifies the method of lift gas rate definition.
• *RATE – defines direct rate specification. If this parameter is set, lift gas rate must
be entered manually. This is the default option;
• *OPT – defines gas lift optimization. If this parameter is set, lift gas rate is calcu-
lated automatically according to specifications defined in GLOPT (see 13.9.42).
This keyword does not require specification of values on the line below, but the
values can be set. In this case it will be interpreted as the maximum lift gas rate.
This keyword must be used in combination with GLOPT (see 13.9.42) keyword;
2. well-list – the list of wells names or wells numbers.
3. values – values of lift gas rates (SI: sm3 /day, FIELD: sc f /day).

Example
*GLIFT *RATE ’Producer1’ ’Producer2’
2500 1700

*GLIFT *OPT 3 4
In this example gas lift parameters are specified for several production wells:
• For the wells 'Producer1' and 'Producer2' lift gas rates are defined explicitly;
• For the wells with numbers 3 and 4 gas lift optimization is set, and their lift gas rates
will be calculated by simulator.

13.9.41. GLIFT 2389

Keywords for formats tN, IM, ST, GE 19.1

13.9.42. GLOPT

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keyword defines parameters for automatic allocation for lift gas.
It must be preceded by GLIFT (see 13.9.41) keyword with *OPT parameter that triggers gas
lift optimization.

The data should be entered in the following format:

*GLOPT econ_ f actor consum_rate
*MAXGAS max_gas_rate
*GLOPT-TIME interval
Where
1. *GLOPT
• econ_factor – a minimum acceptable ratio of oil rate vs. lift gas rate. (SI:
sm3 /sm3 , FIELD: stb/sc f );
• consum_rate – compressor’s gas consumption rate required for a unit of injected
gas. (SI: sm3 /sm3 , FIELD: sc f /sc f ).
2. *MAXGAS – this sub-keyword defines the maximum amount of gas avaliable for gas
lift.
• max_gas_rate – maximum lift gas supply limit for the group (SI: sm3 /day,
FIELD: sc f /day). The group’s lift gas supply is equal to the sum of the lift
gas injection rates of its wells.
3. *GLOPT-TIME – this sub-keyword defines the time interval between gas lift calcula-
tions.
• interval – Minimum interval between gas lift optimizations (days). Gas lift op-
timization is made at each time step which starts after the end of this minimum
interval time from previous optimization.

Example
*GLIFT *OPT 3 4 ... *GLOPT 0.0 0.0 *MAXGAS 2.5E+7 *GLOPT-TIME
31
In this example gas lift optimization is specified for the wells with numbers 3 and 4.
The maximum amount of available gas and the time interval between optimization calculations
are defined.

13.9.42. GLOPT 2390

Keywords for formats tN, IM, ST, GE 19.1

13.9.43. GLCONTROL

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keyword specifies controls of gas lift operations. Initially gas lift option must be
triggered by GLIFT (see 13.9.41) keyword.

The data should be entered in the following format:

*GCONTROL well_list
control value
Where:

1. well-list — list of well names or well numbers.

2. control — defines the control of gas lift operations.

• *WHP — the minimum well head pressure (THP) (SI: kPa, FIELD: psi).
Gas lift will be initialized for the well if its THP falls below the specified limit;
• *WCUT — the maximum water cut. Gas lift will be initialized for the well if its
water cut exceeds the specified limit;
• *TABLE — alters wellbore hydraulic table if gas lift is automatically started on the
well. The number, following this subkeyword should correspond to hydraulic table
specified in PTUBE1 (see 13.9.38) keyword.

3. value — a value corresponding to the control.

This keyword has an E1/E3-compatible analogue WLIFT (see 12.19.237).

Example
*GLIFT *RATE 'Producer1' 'Producer2'
1500
*GLCONTROL 'Producer1' 'Producer2'
*WHP 170 *WCUT 0.70
...
*TIME 365
*GLCONTROL 'Producer1'
*WHP 170 *WCUT 0.70 *TABLE 3

In this example gas lift is initialized for the wells 'Producer1' and 'Producer2'.
Later the number of VFP table was altered for the well 'Producer2' (retubing).

13.9.43. GLCONTROL 2391

Keywords for formats tN, IM, ST, GE 19.1

13.9.44. LAYER-CTRL

Data x tN E1 E3 x IM x GE ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keyword allows to to change the layer status (open or close) and/or connection trans-
missibility factor multipliers for selected completions. If the well has been respecified by
a new PERF (see 13.9.11) keyword, multipliers for layers given by previous LAYER-CTRL
remain as long as layers are still active.
The data should be entered in the following format:
*LAYER-CTRL wn action
locat.
where

• wn – well number or well name written in single quotes;

• locat. – layer location specified earlier using the keyword PERF (see 13.9.11) for the
well wn. Three numbers i, j, k – X, Y and Z coordinates of grid block in which the layer
is located. Specifying the layer location it is possible to use ”0” template for i, j or k. If
0 is specified for index i then all layers along i will be included into consideration.

• action – possible actions with selected layers:

• CLOSE
Close selected layers. The well wn will be shut if there is no open layer left;
• OPEN
Open selected layers. The well wn will be open only if it was previously shut due
to the absence of open layers;
• WIMULT val
Specify non-negative transmissibility factor multiplier in the selected layer of well
wn (see option MULT of the keyword SETPI, see 13.9.15);
• WIMULTO val
Specify non-negative transmissibility factor multiplier in the selected layer of well
wn (see option MULTO of the keyword SETPI, see 13.9.15).

This keyword has an E1/E3-compatible analogue WPIMULT (see 12.19.35).

13.9.44. LAYER-CTRL 2392

Keywords for formats tN, IM, ST, GE 19.1

Example
WELL 1 ’PROD-1’
PERF *GEO 1
109 99 4 1.0
109 99 5 1.0
109 99 6 1.0
...
LAYER-CTRL 1 *OPEN
109 99 4:6
LAYER-CTRL 1 *WIMULT 0.2
109 99 6

In this example all layers with indexes i=109, j=99 and k varying from 4 to 6 for the well
’PROD-1’ will be opened. A transmissibility factor multiplier equal to 0.2 is specified in the
block with indexes i=109, j=99 and k=6.

13.9.44. LAYER-CTRL 2393

Keywords for formats tN, IM, ST, GE 19.1

13.9.45. TMPSET

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

The keyword specifies maximal value of temperature for UHTR (see 13.9.47) 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.45) are constant in each block of the layer in
Z direction (it is specified by the keyword KVAR) and equal correspondingly to 15 ◦ C in the
first 4 layers, 500 ◦C in the fifth one and 15 ◦ C for five other layers of the model.

13.9.45. TMPSET 2394

Keywords for formats tN, IM, ST, GE 19.1

13.9.46. HEATR

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

The keyword indicates constant heat transfer rate to blocks and sets the value of this trans-
fer 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.

Default: value of transfer rate is equal to 0.

The keyword has an E1/E3-compatible analogue HEATER (see 12.19.181).

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.46) 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.46. HEATR 2395

Keywords for formats tN, IM, ST, GE 19.1

13.9.47. UHTR

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

The keyword sets the proportional heat transfer coefficient between value of heat transfer
and difference of current block temperature and maximal block temperature which was speci-
fied by the keyword TMPSET (see 13.9.45) (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.

Default: coefficient is equal to 0.

Example
UHTR KVAR
4*0 1500 5*0
In the example values of UHTR (see 13.9.47) 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.47. UHTR 2396

Keywords for formats tN, IM, ST, GE 19.1

13.9.48. TINJW

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keyword defines the temperature of the injected fluid.

The data should be entered in the following format:

*TINJW tin j_value

Where:

• tinj_value is the temperature of the injected steam (SI: ◦ C, FIELD: ◦ F).

This keyword is the equivalent of the 3-rd parameter of E1/E3-compatible keyword WIN-
JTEMP (see 12.19.178).

Utilization of this keyword is mandatory for thermal models. It must appear after INJEC-
TOR (see 13.9.8) keyword and before OPERATE (see 13.9.23) keyword.

Default: For this parameter default value is supported according to the logic of ST syntax..
Example
*WELL 'Injector1'
*INJECTOR *MOBWEIGHT *EXPLICIT 'Injector 1'
*INCOMP *WATER 1. 0.
*QUAL 0
*TINJW 20.
*PINJW 10000

In this example the steam is injected by the well 'Injector'. The properties of injected fluid
are the following:

• Steam quality (mass fraction of vapour in the stream) is 0% (i.e. injected fluid is pure
water);

• Fluid stream temperature is 20 ◦ C;

• Fluid stream pressure is 10000 kPa.

13.9.48. TINJW 2397

Keywords for formats tN, IM, ST, GE 19.1

13.9.49. QUAL

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keyword defines the steam quality of the injected fluid.

The data should be entered in the following format:

*QUAL qual_value

Where:

• qual_value is a mass or mole fraction of vapour steam in the injected fluid. The value
should be in a range from 0 to 1.
(SI: ◦ C, FIELD: ◦ F).

This keyword is the equivalent of the 2-nd parameter of E1/E3-compatible keyword WIN-
JTEMP (see 12.19.178).

Default: For this parameter default value is supported according to the logic of ST syntax..
Example
*WELL 'Injector1'
*INJECTOR *MOBWEIGHT *EXPLICIT 'Injector 1'
*INCOMP *WATER 1. 0.
*QUAL 0
*TINJW 20.
*PINJW 10000

In this example the steam is injected by the well 'Injector'. The properties of injected fluid
are the following:

• Steam quality (mass fraction of vapour in the stream) is 0% (i.e. injected fluid is pure
water);

• Fluid stream temperature is 20 ◦ C;

• Fluid stream pressure is 10000 kPa.

13.9.49. QUAL 2398

Keywords for formats tN, IM, ST, GE 19.1

13.9.50. PINJW

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keyword defines the pressure of the injected fluid.

The data should be entered in the following format:

*PINJW pin j_value

Where:

• pinj_value is the pressure of the injected fluid (SI: kPa, FIELD: psi).

This keyword is recomended to use if the steam quality QUAL (see 13.9.49) is missing or
equal to 0 or 1.

This keyword is the equivalent of the 4-th parameter of E1/E3-compatible keyword WIN-
JTEMP (see 12.19.178).

Default: For this parameter default value is supported according to the logic of ST syntax..
Example
*WELL 'Injector1'
*INJECTOR *MOBWEIGHT *EXPLICIT 'Injector 1'
*INCOMP *WATER 1. 0.
*QUAL 0
*TINJW 20.
*PINJW 10000

In this example the steam is injected by the well 'Injector'. The properties of injected fluid
are the following:

• Steam quality (mass fraction of vapour in the stream) is 0% (i.e. injected fluid is pure
water);

• Fluid stream temperature is 20 ◦ C;

• Fluid stream pressure is 10000 kPa.

13.9.50. PINJW 2399

Keywords for formats tN, IM, ST, GE 19.1

13.9.51. HTWELL / HTWRATE / HTWRATEPL / HTWTEMP / HTWI

Data x tN E1 E3 IM GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

The keyword specifies properties of heater wells.

The following parameters should be specified:

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.51. HTWELL / HTWRATE / HTWRATEPL / HTWTEMP / HTWI 2400

Keywords for formats tN, IM, ST, GE 19.1

13.9.52. ALTERCP

Data x tN E1 E3 x IM GE ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

This keyword allows to modify the polymer concentration initially specified by the key-
word INCOMP (see 13.5.98) for an injection well or a group of injection wells. The following
parameters should be specified:

• well_list – one or more well names (with keyword WELL, see 13.9.6) or well numbers
required an alteration of polymer concentration. Well names or numbers should be
specified on the same line as the keyword ALTERCP. If more than one line is required
to specify all the wells, then the keyword ALTERCP should be specified on a new line
before enumeration of well is continued;

• cpvalues – new value of the polymer concentration (SI: kg/m3 ; FIELD: lb/stb). If it is
required one value is specified for each well entered in the well list (well_list ). Values
of the polymer concentration should be specified on one or more new lines following
the keyword ALTERCP. If only one value of concentration is set it will be assigned to
all wells from the well list (well_list ).

Example
*WELL 1
*INJECTOR 1
*INCOMP *WATER 1.1
...
*ALTERCP 1
0.5

In this example for the well with number 1 the concentration equal to 1.1, specified by the
keyword INCOMP (see 13.5.98), is altered by 0.5 using the keyword ALTERCP.

13.9.52. ALTERCP 2401

Keywords for formats tN, IM, ST, GE 19.1

13.9.53. TRIGGER

Data x tN E1 E3 x IM x GE x ST MO
format
Input Reservoir Other Component
Section
Rockfluid Initial Numerical x Well

The keyword specifies a set of keywords to perform at defined conditions satisfied. The
following parameters should be specified:

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
following parameters should be specified:
2.1. 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);
2.2. well quantity characteristic. List of allowed ones is in table 1;
2.3. comparison operator (< or >);
2.4. 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
parameters should be specified:
2.1. string ’FIELD’ which means field name;
2.2. field quantity characteristic. List of allowed ones is in table 2;
2.3. comparison operator (< or >);
2.4. 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.
The following parameters should be specified:
2.1. string ’TIME’, which means that type of using trigger is ”time”;
2.2. 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).
2.3. comparison operator (< or >);
2.4. time value (i.e trigger value) (SI: day, FIELD:day). 3 last parameters set
trigger condition to be tested.

13.9.53. TRIGGER 2402

Keywords for formats tN, IM, ST, GE 19.1

3. [additional parameter] APPLY_TIMES – sub-keyword 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 – sub-keyword specifies the increment to the trig-

ger value. It should be followed by one real number;

5. [additional parameter] TEST_TIMES – sub-keyword 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 – sub-keyword 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 – sub-keyword 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 speci-
fied 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)

13.9.53. TRIGGER 2403

Keywords for formats tN, IM, ST, GE 19.1

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)
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 )

13.9.53. TRIGGER 2404

Keywords for formats tN, IM, ST, GE 19.1

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)
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 production
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

13.9.53. TRIGGER 2405

Keywords for formats tN, MO 19.1

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.
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 E1/E3 compatible analogue ACTION (see 12.19.158).
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.53. TRIGGER 2406

Keywords for formats tN, MO 19.1

14. Keywords for formats tN, MO

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:

• tN;

• MO.

In addition: In formats that are used also in other simulators, additionally special tNavi-
gator keywords can be used that are not implemented in other simulators (format extension).
The list of all special keywords is available in the index – 17. Also for some standard key-
words additional tNavigator options can be used that are not implemented in other simulators
(format extension). All possible options are described in keywords descriptions.

MO keywords have 4 significant characters. For convenience (analogous to MO) 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 the sections of the
input file.

• 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 for formats tN, MO 2407

Keywords for formats tN, MO 19.1

14.1. INPUt Data Section

14.1.1. INPUt

Data x tN E1 E3 IM GE ST x MO
format
x INPU FLUI RELA
Section
GRID INIT RECU

This keyword begins INPUt Data Section.

14.1. INPUt Data Section 2408

Keywords for formats tN, MO 19.1

14.1.2. TITLe

Data x tN E1 E3 IM GE ST x MO
format
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 2409

Keywords for formats tN, MO 19.1

14.1.3. PRINt

Data x tN E1 E3 IM GE ST x MO
format
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 2410

Keywords for formats tN, MO 19.1

14.1.4. UNIT

Data x tN E1 E3 IM GE ST x MO
format
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 2411

Keywords for formats tN, MO 19.1

14.1.5. IDATe

Data x tN E1 E3 IM GE ST x MO
format
x INPU FLUI RELA
Section
GRID INIT RECU

The keyword specifies the initial date of the simulation.

The following parameters should be specified:

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 E1/E3-compatible analogue START (see 12.1.18).

Example
IDATE 18 MAY 2003

14.1.5. IDATe 2412

Keywords for formats tN, MO 19.1

14.1.6. SDATe

Data x tN E1 E3 IM GE ST x MO
format
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
isn’t specified, the run will start at the initial date IDATe (see 14.1.5).

The keyword is followed by the initial date in one of the following formats:

• DD MMM YYYY;

• MMM DD YYYY.

where:

1. DD – value DAYS, where value is the number of days after the initial date IDATe
(see 14.1.5);

2. MMM – value MONT, where value is the number of month after the initial date IDATe
(see 14.1.5);

3. YYYY – value YEAR, where value is 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 2413

Keywords for formats tN, MO 19.1

14.1.7. CNAMe

Data x tN E1 E3 IM GE ST x MO
format
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 E1/E3-compatible analogue CNAMES (see 12.14.3).

Example
CNAMe OIL GAS WAT

14.1.7. CNAMe 2414

Keywords for formats tN, MO 19.1

14.1.8. IMPLicit

Data x tN E1 E3 IM GE ST x MO
format
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 E1/E3-compatible analogue IMPLICIT (see 12.1.82).

Example
IMPL FULL

14.1.8. IMPLicit 2415

Keywords for formats tN, MO 19.1

14.1.9. INCLude

Data x tN E1 E3 IM GE ST x MO
format
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 2416

Keywords for formats tN, MO 19.1

14.1.10. SCMP

Data x tN E1 E3 IM GE ST x MO
format
x INPU FLUI RELA
Section
GRID INIT x RECU

The keyword specifies description of standard composition for a fluid stream. The follow-
ing parameters should be specified:

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 com-
ponents 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 data should
be terminated with a slash /.

Default: quantity of moles of each component: 0.

This keyword has an E1/E3 compatible analogue WELLSTRE (see 12.19.184).

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 2417

Keywords for formats tN, MO 19.1

14.1.11. DPORo

Data x tN E1 E3 IM GE ST x MO
format
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.29) should be specified.
This keyword has an E1/E3 compatible analogue DUALPORO (see 12.1.83).
Example
DPOR

14.1.11. DPORo 2418

Keywords for formats tN, MO 19.1

14.1.12. EPS

Data x tN E1 E3 IM GE ST x MO
format
x INPU FLUI RELA
Section
GRID INIT RECU

The keyword sets scaling method of the relative permeability endpoints. The following
parameters should be specified:
The following scaling methods are available:

• 3POINT (analog: 3) – scale a relative permeability at the connate, critical and upper
saturations. The E1/E3-compatible analogue of this scaling method is option NO of the
keyword SCALECRS (see 12.6.25);

• 4POINT (analog: 4) – scale a relative permeability at connate, critical, other phase

residual and upper saturations. The E1/E3-compatible analogue of this scaling method
is option YES of the keyword SCALECRS (see 12.6.25).

Default: scaling method: 3POINT.

This keyword has an E1/E3 compatible analogue SCALECRS (see 12.6.25).

Example
EPS 3

14.1.12. EPS 2419

Keywords for formats tN, MO 19.1

14.1.13. EPSP

Data x tN E1 E3 IM GE ST x MO
format
x INPU FLUI RELA
Section
GRID INIT RECU

The keyword sets scaling method of the capillary pressure endpoints. The following pa-
rameters should be specified:

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 2420

Keywords for formats tN, MO 19.1

14.1.14. DWPW

Data x tN E1 E3 IM GE ST x MO
format
x INPU FLUI RELA
Section
GRID INIT RECU

The keyword is used to set the default well pressure weighting method. The following
parameters should be specified:

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 2421

Keywords for formats tN, MO 19.1

14.1.15. OPEN

Data x tN E1 E3 IM GE ST x MO
format
x INPU x FLUI x RELA
Section
x GRID x INIT x RECU

The keyword is used to put all output files into directory, which is differ from default
directory.
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 parameters should be specified:

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 2422

Keywords for formats tN, MO 19.1

14.1.16. ETUNe

Data x tN E1 E3 IM GE ST x MO
format
x INPU FLUI RELA
Section
GRID INIT RECU

The keyword is used to calculate connection factor via the following formula for MO-
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 2423

Keywords for formats tN, MO 19.1

14.1.17. GPP

Data x tN E1 E3 IM GE ST x MO
format
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.74) should be specified.

This keyword has an E1/E3 compatible analogue PSEUPRES (see 12.19.257)

Example
GPP ALL

14.1.17. GPP 2424

Keywords for formats tN, MO 19.1

14.1.18. MPGP

Data x tN E1 E3 IM GE ST x MO
format
x INPU FLUI RELA
Section
GRID INIT RECU

The keyword activates the using of multi-phase gas pseudo-pressure for well inflow cal-
culation. The following parameters should be specified:

1. [additional parameter] ALL – option will be applied to all wells. If this parameter is
absent, then keyword WMPG (see 14.6.75) should be specified.

This keyword has an E1/E3 compatible analogue PSEUPRES (see 12.19.257)

Example
MPGP ALL

14.1.18. MPGP 2425

Keywords for formats tN, MO 19.1

14.1.19. RG

Data x tN E1 E3 IM GE ST x MO
format
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
should be specified:

1. [additional parameter] ALL – option will be applied to all wells. If this parameter is
absent, then keyword WRG (see 14.6.76) should be specified.

This keyword has an E1/E3 compatible analogue WELSPECS (see 12.19.3) (8-th parame-
ter).
Example
RG ALL

14.1.19. RG 2426
Keywords for formats tN, MO 19.1

14.1.20. THER

Data x tN E1 E3 IM GE ST x MO
format
x INPU x FLUI RELA
Section
GRID INIT RECU

The keyword activates thermal option in a model.

Example
THER

14.1.20. THER 2427

Keywords for formats tN, MO 19.1

14.2. FLUId Data Section

14.2.1. FLUId

Data x tN E1 E3 IM GE ST x MO
format
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. FLUId Data Section 2428

Keywords for formats tN, MO 19.1

14.2.2. WATR

Data x tN E1 E3 IM GE ST x MO
format
INPU x FLUI RELA
Section
GRID INIT RECU

The keyword sets water properties.

The following parameters should be specified:

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 E1/E3-compatible analogues DENSITY (see 12.5.33), PVTW (see 12.5.5).
Example
WATR 999.551 1008.59 4.77175e-05 276.804 0.31

14.2.2. WATR 2429

Keywords for formats tN, MO 19.1

14.2.3. BASIc

Data x tN E1 E3 IM GE ST x MO
format
INPU x FLUI RELA
Section
GRID INIT RECU

The keyword is used to specify basic fluid properties.

The following parameters should be specified:

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 E1/E3-compatible analogue DENSITY (see 12.5.33).

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 2430

Keywords for formats tN, MO 19.1

14.2.4. TEMPerature (FLUI)

Data x tN E1 E3 IM GE ST x MO
format
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 (FLUI) 2431

Keywords for formats tN, MO 19.1

14.2.5. OPVT

Data x tN E1 E3 IM GE ST x MO
format
INPU x FLUI RELA
Section
GRID INIT RECU

The keyword specifies oil PVT tables (black oil model). Each table’s row should be ter-
minated with a slash /.

Each row consists of the following parameters:

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 E1/E3-compatible analogues PVCO (see 12.5.6), PVCDO (see 12.5.3),
DISGAS (see 12.1.60).
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 2432

Keywords for formats tN, MO 19.1

14.2.6. GPVT

Data x tN E1 E3 IM GE ST x MO
format
INPU x FLUI RELA
Section
GRID INIT RECU

The keyword specifies gas PVT tables (black oil model). Each table’s row should be ter-
minated with a slash /.

Each row consists of the following parameters:

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 E1/E3-compatible analogues PVDG (see 12.5.7), PVTG (see 12.5.8),
VAPOIL (see 12.1.59).
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 2433

Keywords for formats tN, MO 19.1

14.2.7. OPVD

Data x tN E1 E3 IM GE ST x MO
format
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 E1/E3 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.7. OPVD 2434

Keywords for formats tN, MO 19.1

14.2.8. OMGA

Data x tN E1 E3 IM GE ST x MO
format
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 (see 14.6.77) in FLUId section. The data should be terminated with a slash /.
The following parameters should be specified:

1. in one line with the keyword:

• [additional parameter] parameter format (one of the following variants):

– CONS – constant value of Ω◦a is specified;
– MULT – multiplier values are specified.

2. in the following line:

• values for ith component (one of the following variants):

– multipler value (MULT);
– constant value Ω◦a (CONS).

Default: parameter format: MULT.

Example
CNAME: N2 CO2 H2S C1 C2 C3 IC4 C4 IC5 C5 C6 C71 C72 C73 C74
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.8. OMGA 2435

Keywords for formats tN, MO 19.1

14.2.9. OMGB

Data x tN E1 E3 IM GE ST x MO
format
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
terminated with a slash /.

The following parameters should be specified:

1. in one line with the keyword:

• [additional parameter] parameter format (one of the following variants):

– CONS – constant value of Ω◦b is specified;
– MULT – multiplier values are specified.

2. in the following line:

• values for ith component (one of the following variants):

– multipler value (MULT);
– constant value Ω◦a (CONS).

Default: parameter format: MULT.

Example
CNAME: N2 CO2 H2S C1 C2 C3 IC4 C4 IC5 C5 C6 C71 C72 C73 C74
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.9. OMGB 2436

Keywords for formats tN, MO 19.1

14.2.10. VOLU

Data x tN E1 E3 IM GE ST x MO
format
INPU x FLUI RELA
Section
GRID INIT RECU

This keyword is a full analog of the keyword SSHIFT (see 12.14.50) which is used by
E1/E3.

14.2.10. VOLU 2437

Keywords for formats tN, MO 19.1

14.2.11. KVSP

Data x tN E1 E3 IM GE ST x MO
format
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
terminated with a slash /.
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 E1/E3 compatible analogue ROCKTAB (see 12.5.21).

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.11. KVSP 2438

Keywords for formats tN, MO 19.1

14.2.12. KVPX / KVPY / KVPZ

Data x tN E1 E3 IM GE ST x MO
format
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 E1/E3 compatible analogue ROCKTAB (see 12.5.21).

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.12. KVPX / KVPY / KVPZ 2439

Keywords for formats tN, MO 19.1

14.2.13. SDEN

Data x tN E1 E3 IM GE ST x MO
format
INPU x FLUI RELA
Section
GRID INIT RECU

The keyword is used to specify oil and gas densities at surface conditions. By this keyword
it is possible to define different densities for each PVT region.

The following parameters should be specified:

1. oil density at surface conditions (METRIC: kg/m3 , FIELD: lb/ f t 3 );

Default: 881 kg/m3 (METRIC), 55 lb/ f t 3 (FIELD).

2. gas density at surface conditions (METRIC: kg/m3 , FIELD: lb/ f t 3 );

Default: 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.33), which is used by E1/E3. Alternative for the keyword SDEN (see 14.2.13) 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.13) oil and gas densities at surface condi-
tions are specified. They are equal to 600 and 1 kg/m3 correspondingly.

14.2.13. SDEN 2440

Keywords for formats tN, MO 19.1

14.2.14. EQUA

Data x tN E1 E3 IM GE ST x MO
format
INPU x FLUI RELA
Section
GRID INIT RECU

This keyword specifies the type of equation of state for compositional model.
The following parameters should be specified:

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 E1/E3 compatible analogue EOS (see 12.14.6).

Example
EQUA RK

14.2.14. EQUA 2441

Keywords for formats tN, MO 19.1

14.2.15. VCOR

Data x tN E1 E3 IM GE ST x MO
format
INPU x FLUI RELA
Section
GRID INIT RECU

The keyword redefines coefficients in Lohrenz-Bray-Clark (3.8.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.28 as multipliers for default
values of ai ;
– CONS – values specified below are used in 3.28 instead of default values of
ai .

• in the following line:

1. 5 values of ai , which will be used in 3.28.

Default:

• coefficient values which are used in 3.28:

1. 0.10230;
2. 0.023364;
3. 0.058533;
4. -0.040758;
5. 0.0099324.

This keyword has an E1/E3 compatible analogue LBCCOEF (see 12.14.44).

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 2442

Keywords for formats tN, MO 19.1

14.2.16. F(DE

Data x tN E1 E3 IM GE ST x MO
format
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:

• in one line with the keyword:

1. [additional parameter] EQUIL region number for which function is set.

Default: if number is omitted then properties are applied to entire grid.

• in the following lines a table is specified. Each line of this table should contain:

1. depth (METRIC: m, FIELD: f t );

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.
Default: 0 for each component.

Each data line should be terminated with the symbol /..

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 2443

Keywords for formats tN, MO 19.1

14.2.17. INTE (FLUID)

Data x tN E1 E3 IM GE ST x MO
format
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.

Default: 0 for unspecified pairs.

This keyword has an E1/E3 compatible analogue BIC (see 12.14.40).

The data should be terminated with a slash /.

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) 2444

Keywords for formats tN, MO 19.1

14.2.18. PROP

Data x tN E1 E3 IM GE ST x MO
format
INPU x FLUI RELA
Section
GRID INIT RECU

The keyword is used to define component properties in an equation-of-state model. The

following parameters should be specified:

1. name or number of the component (numbering is according to the order of components

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 MO compatibility field. Gravity of the liquid;

8. component parachor.

The data should be terminated with a slash /.

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 2445

Keywords for formats tN, MO 19.1

14.2.19. TRAC (FLUI)

Data x tN E1 E3 IM GE ST x MO
format
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 E1/E3 compatible analogue TRACER (see 12.7.10).

Example
TRAC TRC1 H2S
In the example tracer TRC1 is assigned with component H2S.

14.2.19. TRAC (FLUI) 2446

Keywords for formats tN, MO 19.1

14.2.20. UOIL

Data x tN E1 E3 IM GE ST x MO
format
INPU x FLUI RELA
Section
GRID INIT RECU

The keyword sets coefficients Ao and Bo for volume oil specific heat:

Co = Ao + Bo · T,
where T is the block temperature at the current time step (METRIC: ◦ C, FIELD: ◦ F).
The keyword can be used only in black-oil models which uses temperature option (key-
word THER, see 14.1.20).
The following parameters should be specified:

1. coefficient Ao (METRIC: kJ/kg/◦ C, FIELD: btu/lbm/◦ F);

√
Default: METRIC: 1.6848 · γo ; FIELD: 0.388
√ .
γo

2. coefficient Bo (METRIC: kJ/kg/◦ C2 , FIELD: btu/lbm/◦ F2 ).

√ −4
Default: METRIC: 3.2913 × 10−3 · γo ; FIELD: 4.5×10
√
γo .

This keyword has an E1/E3 compatible analogue SPECHEAT (see 12.15.92).

γo is oil gravity (keyword BASIc, see 14.2.3).
Example
UOIL 2*

14.2.20. UOIL 2447

Keywords for formats tN, MO 19.1

14.2.21. UGAS

Data x tN E1 E3 IM GE ST x MO
format
INPU x FLUI RELA
Section
GRID INIT RECU

The keyword sets coefficients Ag and Bg for volume gas specific heat:

Cg = Ag + Bg · T,
where T is the block temperature at the current time step (METRIC: ◦ C, FIELD: ◦ F).
The keyword can be used only in black-oil models which uses temperature option (key-
word THER, see 14.1.20).
The following parameters should be specified:

1. coefficient Ag (METRIC: kJ/kg/◦ C, FIELD: btu/lbm/◦ F);

12.682+37.73γg 3.0962+8.455γg
Default: METRIC: Mw γg ; FIELD: Mw γg .

2. coefficient Bg (METRIC: kJ/kg/◦ C2 , FIELD: btu/lbm/◦ F2 ).

−0.0158+0.1211γg −0.0021+0.0174γg
Default: METRIC: Mw γg ; FIELD: Mw γg .

This keyword has an E1/E3 compatible analogue SPECHEAT (see 12.15.92).

γg is gas gravity (keyword BASIc, see 14.2.3).
Example
UGAS 2*

14.2.21. UGAS 2448

Keywords for formats tN, MO 19.1

14.2.22. UWAT

Data x tN E1 E3 IM GE ST x MO
format
INPU x FLUI RELA
Section
GRID INIT RECU

The keyword sets coefficients Aw and Bw for volume water specific heat:

Cw = Aw + Bw · T,
where T is the block temperature at the current time step (METRIC: ◦ C, FIELD: ◦ F).
The keyword can be used only in black-oil models which uses temperature option (key-
word THER, see 14.1.20).
The following parameters should be specified:

1. coefficient Aw (METRIC: kJ/kg/◦ C, FIELD: btu/lbm/◦ F);

Default: METRIC: 4.2; FIELD: 1.

2. coefficient Bw (METRIC: kJ/kg/◦ C2 , FIELD: btu/lbm/◦ F2 ).

Default: METRIC: 0.0007536; FIELD: 0.0001.

This keyword has an E1/E3 compatible analogue SPECHEAT (see 12.15.92).

Example
UWAT 4.0 0.00075

14.2.22. UWAT 2449

Keywords for formats tN, MO 19.1

14.2.23. UROC

Data x tN E1 E3 IM GE ST x MO
format
INPU x FLUI RELA
Section
GRID INIT RECU

The keyword sets coefficients Ar and Br for volume rock specific heat:

Cr = Ar + Br · T,
where T is the block temperature at the current time step (METRIC: ◦ C, FIELD: ◦ F).
The keyword can be used only in black-oil models which uses temperature option (key-
word THER, see 14.1.20).
The following parameters should be specified:

1. coefficient Ar (METRIC: kJ/kg/◦ C, FIELD: btu/lbm/◦ F);

Default: METRIC: 0.820; FIELD: 0.192.

2. coefficient Br (METRIC: kJ/kg/◦ C2 , FIELD: btu/lbm/◦ F2 );

Default: METRIC: 8.89 × 10−4 ; FIELD: 1.18 × 10−4 .

3. IGNORED, this is a MO compatibility field;

4. IGNORED, this is a MO compatibility field.

The keyword has an E1/E3-compatible analogue HEATTCR (see 12.15.19).

Example
UROC 0.84 0.0008

14.2.23. UROC 2450

Keywords for formats tN, MO 19.1

14.2.24. THCO

Data x tN E1 E3 IM GE ST x MO
format
INPU x FLUI RELA
Section
GRID INIT RECU

The keyword sets coefficients Ao , Bo and Co for oil heat conductivity:

Ho = Ao + Bo · T +Co (P − Pre f ),

where:

• T is the block temperature at the current time step (METRIC: ◦ C, FIELD: ◦ F);

• P is pressure in the block at the current time step (METRIC: bar , FIELD: psi);

• Pre f – reference pressure (METRIC: bar , FIELD: psi).

The keyword can be used only in black-oil models which uses temperature option (key-
word THER, see 14.1.20).
The following parameters should be specified:

1. coefficient Ao (METRIC: kJ/m/day/◦ C, FIELD: btu/ f t/day/◦ F);

11.6
√ ; 1.637
√ .
Default: METRIC: γo FIELD: γo

2. coefficient Bo (METRIC: kJ/m/day/◦ C2 , FIELD: btu/ f t/day/◦ F2 );

−5.45×10−3 −4.86×10 −4
Default: METRIC: √ ; FIELD: √ .
γo γo

3. coefficient Co .
Default: 0.

This keyword has an E1/E3 compatible analogue THCOIL (see 12.2.88).

γo is oil gravity (keyword BASIc, see 14.2.3).
Example
THCO 3*

14.2.24. THCO 2451

Keywords for formats tN, MO 19.1

14.2.25. THCG

Data x tN E1 E3 IM GE ST x MO
format
INPU x FLUI RELA
Section
GRID INIT RECU

The keyword sets coefficients Ag , Bg and Cg for gas heat conductivity:

Hg = Ag + Bg · T +Cg (P − Pre f ),

where:

• T is the block temperature at the current time step (METRIC: ◦ C, FIELD: ◦ F);

• P is pressure in the block at the current time step (METRIC: bar , FIELD: psi);

• Pre f – reference pressure (METRIC: bar , FIELD: psi).

The keyword can be used only in black-oil models which uses temperature option (key-
word THER, see 14.1.20).
The following parameters should be specified:

1. coefficient Ag (METRIC: kJ/m/day/◦ C, FIELD: btu/ f t.day.◦ F);

Default: 0.

2. coefficient Bg (METRIC: kJ/m/day/◦ C2 , FIELD: btu/ f t.day.◦ F2 );

Default: 0.

3. coefficient Cg .
Default: 0.

This keyword has an E1/E3 compatible analogue THCGAS (see 12.2.87).

Example
THCG 3*

14.2.25. THCG 2452

Keywords for formats tN, MO 19.1

14.2.26. THCW

Data x tN E1 E3 IM GE ST x MO
format
INPU x FLUI RELA
Section
GRID INIT RECU

The keyword sets coefficients Aw , Bw and Cw for water heat conductivity:

Hw = Aw + Bw · T +Cw (P − Pre f ),

where:

• T is the block temperature at the current time step (METRIC: ◦ C, FIELD: ◦ F);

• P is pressure in the block at the current time step (METRIC: bar , FIELD: psi);

• Pre f – reference pressure (METRIC: bar , FIELD: psi).

The keyword can be used only in black-oil models which uses temperature option (key-
word THER, see 14.1.20).
The following parameters should be specified:

1. coefficient Aw (METRIC: kJ/m/day/◦ C, FIELD: btu/ f t/day/◦ F);

Default: METRIC: 49.78; FIELD: 7.525.

2. coefficient Bw (METRIC: kJ/m/day/◦ C2 , FIELD: btu/ f t/day/◦ F2 );

Default: METRIC: 0.15333; FIELD: 0.01542.

3. coefficient Cw .
Default: 0.

This keyword has an E1/E3 compatible analogue THCWATER (see 12.2.89).

Example
THCW 3*

14.2.26. THCW 2453

Keywords for formats tN, MO 19.1

14.2.27. THCR

Data x tN E1 E3 IM GE ST x MO
format
INPU x FLUI RELA
Section
GRID INIT RECU

The keyword sets coefficients Ar , Br and Cr for water heat conductivity:

Hr = Ar + Br · T +Cr (P − Pre f ),

where:

• T is the block temperature at the current time step (METRIC: ◦ C, FIELD: ◦ F);

• P is pressure in the block at the current time step (METRIC: bar , FIELD: psi);

• Pre f – reference pressure (METRIC: bar , FIELD: psi).

The keyword can be used only in black-oil models which uses temperature option (key-
word THER, see 14.1.20).
The following parameters should be specified:

1. coefficient Ar (METRIC: kJ/m/day/◦ CC, FIELD: btu/ f t/day/◦ F);

Default: METRIC: 124.6; FIELD: 20.0.

2. coefficient Br (METRIC: kJ/m/day/◦ C2 , FIELD: btu/ f t/day/◦ F2 );

Default: 0.

3. coefficient Cr .
Default: 0.

This keyword has an E1/E3 compatible analogue THCROCK (see 12.2.91).

Example
THCR 3*

14.2.27. THCR 2454

Keywords for formats tN, MO 19.1

14.2.28. OVVT

Data x tN E1 E3 IM GE ST x MO
format
INPU x FLUI RELA
Section
GRID INIT RECU

The keyword sets values of oil viscosity multipliers dependence on temperature as a table.
The table contains two columns:

1. temperature (METRIC: ◦ C, FIELD: ◦ F);

2. oil viscosity multiplier value.

The data should be terminated with a slash /.

This keyword has an E1/E3 compatible analogue OILVISCT (see 12.15.54).
Example
OVVT
50.0 1.3
69.0 1.0
90.0 0.8
/

14.2.28. OVVT 2455

Keywords for formats tN, MO 19.1

14.2.29. GVVT

Data x tN E1 E3 IM GE ST x MO
format
INPU x FLUI RELA
Section
GRID INIT RECU

The keyword sets values of gas viscosity multipliers dependence on temperature as a table.
The table contains two columns:

1. temperature (METRIC: ◦ C, FIELD: ◦ F);

2. gas viscosity multiplier value.

The data should be terminated with a slash /.

This keyword has an E1/E3 compatible analogue GASVISCT (see 12.15.58).
Example
GVVT
50.0 1.3
69.0 1.0
90.0 0.8
/

14.2.29. GVVT 2456

Keywords for formats tN, MO 19.1

14.2.30. WVVT

Data x tN E1 E3 IM GE ST x MO
format
INPU x FLUI RELA
Section
GRID INIT RECU

The keyword sets values of water viscosity multipliers dependence on temperature as a

table. The table contains two columns:

1. temperature (METRIC: ◦ C, FIELD: ◦ F);

2. water viscosity multiplier value.

The data should be terminated with a slash /.

This keyword has an E1/E3 compatible analogue WATVISCT (see 12.15.53).
Example
WVVT
50.0 1.3
69.0 1.0
90.0 0.8
/

14.2.30. WVVT 2457

Keywords for formats tN, MO 19.1

14.2.31. OVPG

Data x tN E1 E3 IM GE ST x MO
format
INPU x FLUI RELA
Section
GRID INIT RECU

This keyword specifies the variation of oil viscosity with the pressure gradient. The fol-
lowing parameters should be specified in succession after this keyword:

1. oil flow multiplier FO . If the pressure gradient is less than GP0 the oil flow is multiplied
by FO . The multiplier can be equal to 0;

2. characteristic pressure gradient defined the flow variation GP0 (METRIC: barsa/m,
FIELD: psi/ f t ). It can be equal to 0;

3. characteristic pressure gradient defined the flow variation GP1 (METRIC: barsa/m,
FIELD: psi/ f t ).

If pressure gradient is lower than GP0 the oil flow is multiplied by FO . If pressure gradient
is higher than GP1 the oil flow is not altered. The flow multiplier varies smoothly from FO
to 1 when pressure gradient varies between GP0 and GP1.
This keyword has the tNavigator compatible analogue OVPG (see 12.5.10).
Example
OVPG 0.0 0.338 4

14.2.31. OVPG 2458

Keywords for formats tN, MO 19.1

14.2.32. SOLU

Data x tN E1 E3 IM GE ST x MO
format
INPU x FLUI RELA
Section
GRID INIT RECU

This keyword defines a variation of solubility with pressure presented in table form. The
table consists of two columns:

1. pressure (METRIC: bar , FIELD: psi);

2. solubility (METRIC: sm3 /sm3 , FIELD: sc f /ST B).

This keyword has an E1/E3-compatible analogue SOLUBILI (see 12.14.70).

Example
SOLU CO2
20 0.005
1050 0.020
2050 0.040
3050 0.080
6000 0.200
/
In this example solubility of CO2 in water is shown.
Furthermore, it is possible to define initial gas water ratio using an array RHAQ (see
keyword RHAQ, see 14.5.17), if only one soluble component exists, or arrays RHA1, RHA,
if there are several soluble components.

14.2.32. SOLU 2459

Keywords for formats tN, MO 19.1

14.2.33. VCVI

Data x tN E1 E3 IM GE ST x MO
format
INPU x FLUI RELA
Section
GRID INIT RECU

This keyword specifies critical volumes used for viscosity calculation in the Equation-
of-State. On the new line following the keyword a list of critical volumes is specified. The
entered data should be terminated by the slash /.
If a default or negative value is specified the normal critical value given by the keyword
PROP (see 14.2.18) will be used.
This keyword has an E1/E3 compatible analogue VCRITVIS (see 12.14.26).
Example
VCVI
0.094
0.09
0.098
0.148
0.2
0.263
0.255
0.308
0.311
0.3397514956
0.6092549045
0.2
0.2
0.2
/

14.2.33. VCVI 2460

Keywords for formats tN, MO 19.1

14.2.34. ZCOR

Data x tN E1 E3 IM GE ST x MO
format
INPU x FLUI RELA
Section
GRID INIT RECU

This keyword allows to modify parameters of correlation used for calculation of critical
Z-factors in an equation-of-state simulation. If a component does not have neither a library
nor a supplied critical Z-factor the critical Z-factor correlation can be used:

Zcriti = aZcrit − bZcrit ωi

where aZcrit , bZcrit are correlation parameters and ωi is the acentric factor for the ith compo-
nent.
The keyword is followed by correlation parameters, located in the same line:

1. aZcrit ;

Default: 0.291.

2. bZcrit .

Default: 0.080.

Correlation parameters can be specified by default using the notation 1*. This notation
must be used to indicated that the parameter should be taken by default and to keep the
correct order for the entry of correlation parameters. If parameters are not specified then
default values will be used for critical Z-factor correlation.
Example
ZCOR 0.3 0.1

14.2.34. ZCOR 2461

Keywords for formats tN, MO 19.1

14.3. RELAtive Permeability Data Section

14.3.1. RELA

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI x RELA
Section
GRID INIT RECU

The keyword begins RELAtive Permeability Section.

Example
RELA

14.3. RELAtive Permeability Data Section 2462

Keywords for formats tN, MO 19.1

14.3.2. WETT

Data x tN E1 E3 IM GE ST x MO
format
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 E1/E3-compatible keyword STONE1 (see 12.6.20); STN2 is anal-

ogous to an E1/E3-compatible keyword STONE2 (see 12.6.21); LINE is analogous to E1/E3
and tN default interpolation of three phase relative permeability data.
Example
WETT LINE

14.3.2. WETT 2463

Keywords for formats tN, MO 19.1

14.3.3. KRWO

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI x RELA
Section
GRID INIT RECU

The keyword specifies relative permeability tables for water-oil systems. Each table’s row
should be terminated with a slash /.

Each row consists of the following parameters:

1. water saturation;

2. water permeability;

3. oil permeability;

4. oil-water capillary pressure;

5. ignored, this is a MO compatibility field;

6. ignored, this is a MO compatibility field.

The keyword has an E1/E3-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 2464

Keywords for formats tN, MO 19.1

14.3.4. KRGO

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI x RELA
Section
GRID INIT RECU

The keyword specifies relative permeability tables for gas-oil systems. Each table’s row
should be terminated with a slash /.

Each row consists of the following parameters:

1. gas saturation;

2. gas permeability;

3. oil permeability;

4. gas-oil capillary pressure;

5. ignored, this is a MO compatibility field;

6. ignored, this is a MO compatibility field.

The keyword has an E1/E3-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 2465

Keywords for formats tN, MO 19.1

14.3.5. TFUN

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI x RELA
Section
GRID INIT RECU

This keyword specifies the table of multipliers for permeability-related parameters as a

function of the tracer concentration.
Table header contains the following arguments:

1. one of the possible properties: SOWC (see 14.4.61), SOGC (see 14.4.60), SWCR
(see 14.4.64), XKRO (see 14.4.66), XKRG (see 14.4.65), or XKRW (see 14.4.67), for
which the multiplier will be specified.

2. tracer name (should be created by TRAC (see 14.2.19) beforehand).

Each line of the table contains the following data:

1. tracer concentration (dimensionless);

2. coresponding multiplier to be applied to the selected property.

The data entry must be terminated with slash /.

The keyword is analogous to E1/E3 keywords ENPTRCM (see 12.6.43) or ENPKTRCM
(see 12.6.44), depending on the selected property.
Example
TFUN XKRW TRC1
0.0 1.0
0.1 1.2
0.2 1.25
0.3 1.3

In this example the scaling mutiplier for relative permeability of water is specified as a
function of tracer concentration.

14.3.5. TFUN 2466

Keywords for formats tN, MO 19.1

14.4. GRID Data Section

14.4.1. GRID

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

The keyword begins GRID Section.

14.4. GRID Data Section 2467

Keywords for formats tN, MO 19.1

14.4.2. VERT

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

The keyword specifies a vertical data input mode.

tNavigator supports the following MO input data modes:

• VERT BLOCK – grid array layers are input successively in a vertical order.

Example
VERT BLOCK

14.4.2. VERT 2468

Keywords for formats tN, MO 19.1

14.4.3. HORI

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

The keyword specifies a horizontal data input mode.

tNavigator supports the following MO input data modes:

• HORI BLOCK – values of parameter enters in every cell of block layer.

14.4.3. HORI 2469

Keywords for formats tN, MO 19.1

14.4.4. SIZE

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

The keyword specifies size and type of grid.

The following parameters should be specified:

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 E1/E3 keyword DIMENS (see 12.1.28).

Example
SIZE 120 120 10

Coordinate system of size 120x120x10 is set in this example.

14.4.4. SIZE 2470

Keywords for formats tN, MO 19.1

14.4.5. DATUm

Data x tN E1 E3 IM GE ST x MO
format
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 E1/E3 keyword DATUM (see 12.16.40).

Example
DATUM 2560.32

In this example the specified value of datum depth is 2560.32 meters. Bottom hole pres-
sures will be calculated for specified depth.

14.4.5. DATUm 2471

Keywords for formats tN, MO 19.1

14.4.6. X-DIrection

Data x tN E1 E3 IM GE ST x MO
format
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 MO ways:

• VARI (see 14.4.53) – definition of block sizes in X-direction (different block sizes, non-
uniform grid). After VARI, all grid block lengths in X-direction in meters should be
specified;

• CONS (see 14.4.20) – specify a uniform grid spacing in X-direction. After CONS, the
total value of length in X-direction in meters should be specified.

The keyword is analogous to an E1/E3 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 2472

Keywords for formats tN, MO 19.1

14.4.7. Y-DIrection

Data x tN E1 E3 IM GE ST x MO
format
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 MO ways:

• VARI (see 14.4.53) – definition of block sizes in Y-direction (different block sizes, non-
uniform grid). After VARI, all grid block lengths in Y-direction in meters should be
specified;

• CONS (see 14.4.20) – specify a uniform grid spacing in Y-direction. After CONS, the
total value of length in Y-direction in meters should be specified.

The keyword is analogous to an E1/E3 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 2473

Keywords for formats tN, MO 19.1

14.4.8. DEPTh / ZGRI

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

The keyword defines values of cells depth (METRIC: m, FIELD: f t ).

tNavigator supports the following MO 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 MO 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 E1/E3-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 2474

Keywords for formats tN, MO 19.1

14.4.9. THICkness

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

The keyword defines values of cells thickness (METRIC: m, FIELD: f t ).

tNavigator supports the following MO 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 MO 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 are specified once
(one value for every layer).

The keyword has an E1/E3-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 2475

Keywords for formats tN, MO 19.1

14.4.10. POROsity

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

The keyword defines values of cells porosity.

tNavigator supports the following MO 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 MO 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 E1/E3-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 2476

Keywords for formats tN, MO 19.1

14.4.11. MINPv

Data x tN E1 E3 IM GE ST x MO
format
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
terminated with a slash /.

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 MO 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).
• MO. Use MO volume units (METRIC: m3 , FIELD: f t 3 ).
• ECLI. Use E1/E3 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 E1/E3-compatible analogue – MINPV (see 12.2.30). tNavigator uses
the keyword MINPVR (see 12.2.34).
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/

14.4.11. MINPv 2477

Keywords for formats tN, MO 19.1

Make cells with the value of pore volume less than 0.001 rm3 inactive.

14.4.11. MINPv 2478

Keywords for formats tN, MO 19.1

14.4.12. K_X / K_Y / K_Z (KX / KY / KZ, PERMX / PERMY / PERMZ)

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

The keyword defines values of cells permeability in X-, Y-, Z-direction (METRIC: mD,
FIELD: mD).

tNavigator supports the following MO 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 MO 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 only one 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 E1/E3-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 (KX / KY / KZ, PERMX / PERMY / PERMZ) 2479
Keywords for formats tN, MO 19.1

14.4.13. CROC

Data x tN E1 E3 IM GE ST x MO
format
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.
tNavigator supports the following MO 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 MO 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 only one value should be entered;
• ZVARiable – values are constant in one layer; values for all layers should be specified
once (one value for every layer).
Analogous to this keyword is the 2-nd parameter of the keyword ROCK (see 12.5.17),
which is used by E1/E3.
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 2480

Keywords for formats tN, MO 19.1

14.4.14. REFE

Data x tN E1 E3 IM GE ST x MO
format
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 MO modes of input data and editing it in vertical direc-
tion:

• 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 MO modes of input data and editing it in horizontal
direction:

• VARIable – for every layer the full set of values should be entered;

• CONStant – for every layer only one value should be entered;

• ZVARiable – values are constant in one layer; values for all layers should be specified
once (one value for every layer).

Analogous to this keyword is the 1-st parameter of the keyword ROCK (see 12.5.17),
which is used by E1/E3.
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 2481

Keywords for formats tN, MO 19.1

14.4.15. ACTN

Data x tN E1 E3 IM GE ST x MO
format
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 E1/E3 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 5 × 4 × 1 is specified.

14.4.15. ACTN 2482

Keywords for formats tN, MO 19.1

14.4.16. COORd

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

The keyword specify coordinate lines. Geometry of grid is building by these lines. The
following parameters should be specified:

• in one line with the keyword:

1. ZXY or X&Y:
– ZXY – (Nx + 1) · (Ny + 1) coordinate lines are specified, each of them is de-
fined by two points with different depths. (Nx is the number of blocks in
X -direction, Ny is 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.

The data should be terminated with a slash /.

This keyword has an E1/E3 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 coordi-
nates of two points with different depths.

14.4.16. COORd 2483

Keywords for formats tN, MO 19.1

14.4.17. FIPN

Data x tN E1 E3 IM GE ST x MO
format
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 E1/E3 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 2484

Keywords for formats tN, MO 19.1

14.4.18. SATNum / ROCK

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

The keyword should be followed by one integer for every grid block specifying the satu-
ration 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 E1/E3 compatible analogue SATNUM (see 12.4.3).
Note. The number of sets of relative permeability tables given by KRWO (see 14.3.3) and
KRGO (see 14.3.4) in the RELA section should be equal to the number of saturation tables
numbers used by SATNum / ROCK in the GRID section.
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 2485

Keywords for formats tN, MO 19.1

14.4.19. AQCD

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

The keyword is used to connect aquifer at specified depth. The following parameters
should be specified:

1. aquifer name (it is specified via the keyword AQCT, see 14.5.12);

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 E1/E3 compatible analogue AQUANCON (see 12.17.11).
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 2486

Keywords for formats tN, MO 19.1

14.4.20. CONS (GRID)

Data x tN E1 E3 IM GE ST x MO
format
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.20. CONS (GRID) 2487

Keywords for formats tN, MO 19.1

14.4.21. DEFI

Data x tN E1 E3 IM GE ST x MO
format
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:

• in one line with the keyword:

– 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 MO compatibility field.

Example
DEFI PINIT
’ORIGINAL PERMEABILITY’
In the example name PINIT is specified for a new array.

14.4.21. DEFI 2488

Keywords for formats tN, MO 19.1

14.4.22. DPSS

Data x tN E1 E3 IM GE ST x MO
format
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.22) sets that dual porosity model with single
grid and net values of fracture permeabilities will be used.

14.4.22. DPSS 2489

Keywords for formats tN, MO 19.1

14.4.23. FSAT

Data x tN E1 E3 IM GE ST x MO
format
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
following parameters should be specified:

• 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.23. FSAT 2490

Keywords for formats tN, MO 19.1

14.4.24. FSWA

Data x tN E1 E3 IM GE ST x MO
format
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
should be specified:

1. water saturation values for each fracture block.

This keyword has an E1/E3 compatible analogue SWAT (see 12.16.14).

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.24. FSWA 2491

Keywords for formats tN, MO 19.1

14.4.25. FSWL

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

This keyword specifies connate water saturation for each fracture block. This keyword is
used in the dual porosity model with a single grid (see DPOR, see 14.1.11).
The following parameters should be specified:

1. connate water saturation for each fracture block.

This keyword has an E1/E3 compatible analogue SWL (see 12.6.26).

Example
FSWL
0.35 0.35 0.35 0.35 0.35 0.35
0.35 0.35 0.35 0.35 0.35
0.45 0.45 0.45 0.45 0.45 0.45

In this example connate water saturation is set 0.35 in 11 fracture blocks and 0.45 in the
remaining 6 blocks.

14.4.25. FSWL 2492

Keywords for formats tN, MO 19.1

14.4.26. FKPT

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

This keyword specifies the number of rock region (and hence the number of table of
transmissibility as a function of pressure) to which it belongs. Tables for each rock region are
specifying using the keyword KVSP (see 14.2.11). This keyword is used in the dual porosity
model with a single grid (see DPOR, see 14.1.11).
The following parameters should be specified:

1. the number of rock region for each fracture block.

The number of specified regions should be equal to the number of fracture blocks. The
table number can not exceed the number of tables specified by KVSP (see 14.2.11).
This keyword has an E1/E3 compatible analogue ROCKNUM (see 12.4.14).
Example
FKPT
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 this example for each fracture block the number of rock region are specified.

14.4.26. FKPT 2493

Keywords for formats tN, MO 19.1

14.4.27. FPVT

Data x tN E1 E3 IM GE ST x MO
format
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
following parameters should be specified:

1. PVT region number.

Default: correspondingly to the keyword PVTN (see 14.4.28).

This keyword has an E1/E3 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.27. FPVT 2494

Keywords for formats tN, MO 19.1

14.4.28. PVTNum

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

The keyword should be followed by one integer for every grid block specifying the PVT
region to which it belongs. The number of values should be equal to the number of blocks.
The following parameters should be specified:

1. PVT region number.

Default: PVT region number: 1 for each block.

This keyword has an E1/E3 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.28. PVTNum 2495

Keywords for formats tN, MO 19.1

14.4.29. DZMA

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

This keyword has an E1/E3 compatible analogue DZMTRXV (see 12.2.82).

14.4.29. DZMA 2496

Keywords for formats tN, MO 19.1

14.4.30. EQUI / EQLN

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

The keyword should be followed by one integer for every grid block specifying the equi-
librium 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.2).

Default: 1 for all blocks.

This keyword has an E1/E3 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.30. EQUI / EQLN 2497

Keywords for formats tN, MO 19.1

14.4.31. F(PO

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID x INIT RECU

The keyword specifies values array of some parameter as a porosity function. The follow-
ing parameters should be specified:

• in one line with the keyword:

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.31). The data
should be terminated with a slash /.

This keyword has an E1/E3 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.31. F(PO 2498

Keywords for formats tN, MO 19.1

14.4.32. FAUL

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

The keyword is used to mark a group of connections as a fault for the following modifi-
cation by the keyword FMUL (see 14.4.33). Marked connections can define a part of the fault
or several faults.The following parameters should be specified:

• in one line with the keyword:

1. fault name;
2. starting layer in Z -direction;
Default: 1.
3. ending layer in Z -direction;
Default: nz .

• 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.

This keyword has an E1/E3 compatible analogue FAULTS (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/
In the example via the keyword FAUL (see 14.4.32) 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.32. FAUL 2499

Keywords for formats tN, MO 19.1

14.4.33. FMUL

Data x tN E1 E3 IM GE ST x MO
format
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.32). The following parameters should be specified:

1. fault name;

2. transmissibility multiplier value.

Default: 0.

This keyword has an E1/E3 compatible analogue MULTFLT (see 12.2.39).

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.33) 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.32).

14.4.33. FMUL 2500

Keywords for formats tN, MO 19.1

14.4.34. FCRO

Data x tN E1 E3 IM GE ST x MO
format
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
should be specified:

1. rock compressibility values for each fracture block.

Default: 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.34. FCRO 2501

Keywords for formats tN, MO 19.1

14.4.35. FKX / FKY / FKZ

Data x tN E1 E3 IM GE ST x MO
format
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.35. FKX / FKY / FKZ 2502

Keywords for formats tN, MO 19.1

14.4.36. FMLX / FMLY / FMLZ

Data x tN E1 E3 IM GE ST x MO
format
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.36. FMLX / FMLY / FMLZ 2503

Keywords for formats tN, MO 19.1

14.4.37. FEQL

Data x tN E1 E3 IM GE ST x MO
format
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.30).
Example
EQLN
2 2 1 1 1
2 1 1 1 2
This example defines disposition of two equilibration regions for fracture.

14.4.37. FEQL 2504

Keywords for formats tN, MO 19.1

14.4.38. FPOR

Data x tN E1 E3 IM GE ST x MO
format
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 should be
specified:

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.38. FPOR 2505

Keywords for formats tN, MO 19.1

14.4.39. FREF

Data x tN E1 E3 IM GE ST x MO
format
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.39. FREF 2506

Keywords for formats tN, MO 19.1

14.4.40. IEQ

Data x tN E1 E3 IM GE ST x MO
format
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 being compared to 0 and 1 via the keyword IEQ.

14.4.40. IEQ 2507

Keywords for formats tN, MO 19.1

14.4.41. INTE (GRID)

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID x INIT RECU

The keyword specifies distance weighted interpolation for array of values. The following
parameters should be specified:

• in one line with the keyword:

1. exponential weighting coefficient (minimal value: 0.1; maximal value: 10);

Default: 1.
2. number of nearest neighbors to interpolate (minimal value: 2; maximal value: is
not limited);
Default: 4.
3. interpolation range (values outside this range will be ignored) (minimal value:
10−6 ; maximal value: is not limited). Parameter is IGNORED;
Default: unlimited.
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;
– QUAD – quartets (x, y, v, r) are specified, where r is the radius of influence
of the point.
– Default: TRIP.
5. [additional parameter] SWIT – switch to another file with data to read.

• in the next line:

1. coordinate of ith point of interpolation in X -direction;

2. coordinate of ith point of interpolation in Y -direction;
3. function value at point (xi , yi )

14.4.41. INTE (GRID) 2508

Keywords for formats tN, MO 19.1

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.41) with ALLX option is used to set perme-
ability values in Z -direction.

14.4.41. INTE (GRID) 2509

Keywords for formats tN, MO 19.1

14.4.42. KPTA

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

The keyword should be followed by one integer for every grid block specifying the number
of rock region (and hence the number of transmissibility vs pressure table) to which it belongs.
Tables for each rock region are specifying using the keyword KVSP (see 14.2.11).
The following parameters should be specified:

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.11).
Default: the number of rock region: 1 for each grid cell.

This keyword has an E1/E3 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.42. KPTA 2510

Keywords for formats tN, MO 19.1

14.4.43. LAYE

Data x tN E1 E3 IM GE ST x MO
format
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.

The data should be terminated with a slash /.

Example
LAYE
1 3 2 3*1 /
In the example 9 layers of model are grouped into 6 geological layers.

14.4.43. LAYE 2511

Keywords for formats tN, MO 19.1

14.4.44. LEVJ

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

The keyword is used to specify Leverett J-factors to modify capillary pressures (the key-
words 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.

The following parameters should be specified:

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.44. LEVJ 2512

Keywords for formats tN, MO 19.1

14.4.45. LGRD

Data x tN E1 E3 IM GE ST x MO
format
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 E1/E3 compatible analogue CARFIN (see 12.2.97).

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.45. LGRD 2513

Keywords for formats tN, MO 19.1

14.4.46. MINDznet

Data x tN E1 E3 IM GE ST x MO
format
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.46. MINDznet 2514

Keywords for formats tN, MO 19.1

14.4.47. MODI

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

The keyword is used to modify data array values. The following parameters should be
specified:

• in one line with the keyword:

1. first coordinate of modifying block in X -direction;

Default: 1.
2. last coordinate of modifying block in X -direction;
Default: Nx .
3. first coordinate of modifying block in Y -direction;
Default: 1.
4. last coordinate of modifying block in Y -direction;
Default: Ny .
5. first coordinate of modifying block in Z -direction;
Default: 1.
6. last coordinate of modifying block in Z -direction;
Default: Nz .
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.

• in the following line:

1. value to add to all array values;

Default: 0.
2. value by which all array values will be multiplied;
Default: 1.
3. minimal value;
Default: 0.
4. maximal value;
Default: 1020 .

14.4.47. MODI 2515

Keywords for formats tN, MO 19.1

Example
KX
MODI 1 63 1 65 2*
2* 120/
In the example values of array KX are changing.

14.4.47. MODI 2516

Keywords for formats tN, MO 19.1

14.4.48. MULX / MULY / MULZ (MX / MY / MZ, M_X / M_Y / M_Z, M-X / M-Y /
M-Z, MULTX / MULTY / MULTZ)

Data x tN E1 E3 IM GE ST x MO
format
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 E1/E3.
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.48. MULX / MULY / MULZ (MX / MY / MZ, M_X / M_Y / M_Z, M-X / M-Y / M-Z, MULTX / MULTY
Keywords for formats tN, MO 19.1

14.4.49. PINCh

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

The keyword is used to pinch out blocks which thickness is less than specified value.

The following parameters should be specified:

1. in one line with the keyword:

• [additional parameter] ON or OFF

– ON – pinchout is turned on;
– OFF – pinchout is turned off.
– Default: ON.

2. in the following line:

• block thickness (METRIC: m, FIELD: f t ).

Default: 0.1 m.

This keyword has an E1/E3 compatible analogue PINCH (see 12.2.58).

Example
UNITS FIELD
...
PINCH ON
1 /
In the example all blocks which thickness is less than 1 ft will be pinched out.

14.4.49. PINCh 2518

Keywords for formats tN, MO 19.1

14.4.50. PORV

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

The keyword is analogous to the keyword PVOL (see 14.4.51) with the option REPL. This
keyword uses another units – METRIC: m3 , FIELD: stb.

14.4.50. PORV 2519

Keywords for formats tN, MO 19.1

14.4.51. PVOL / RVOL / PVR

Data x tN E1 E3 IM GE ST x MO
format
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 ).

The following parameters should be specified:

1. coordinate of the first block to modify in X -direction;
Default: 1.

2. coordinate of the last block to modify in X -direction;

Default: Nx .

3. coordinate of the first block to modify in Y -direction;

Default: 1.

4. coordinate of the last block to modify in Y -direction;

Default: Ny .

5. coordinate of the first block to modify in Z -direction;

Default: 1.

6. coordinate of the last block to modify in Z -direction;

Default: Nz .

7. modification type: MODI (see 14.4.47) or REPL (see 14.4.56).

Default: MODI.
In the following line should be specified:
1. if the keyword MODI (see 14.4.47) is used:

• value to add (add );

Default: 0.
• multiplier (mult );
Default: 1.
• minimal value (min);
Default: 0.

14.4.51. PVOL / RVOL / PVR 2520

Keywords for formats tN, MO 19.1

• maximal value (max ).

Default: 1020 .

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.56) is used:

• new values for blocks, which coordinates are specified above.

This keyword has an E1/E3 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.51. PVOL / RVOL / PVR 2521

Keywords for formats tN, MO 19.1

14.4.52. T_X / T_Y / T_Z (TX / TY / TZ, T-X / T-Y / T-Z)

Data x tN E1 E3 IM GE ST x MO
format
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;

Default: 1.

2. coordinate of the last block to modify in X -direction;

Default: Nx .

3. coordinate of the first block to modify in Y -direction;

Default: 1.

4. coordinate of the last block to modify in Y -direction;

Default: Ny .

5. coordinate of the first block to modify in Z -direction;

Default: 1.

6. coordinate of the last block to modify in Z -direction;

Default: Nz .

7. modification type: MODI (see 14.4.47) or REPL (see 14.4.56).

Default: MODI (see 14.4.47).

In the following line should be specified:

1. if the keyword MODI (see 14.4.47) is used:

• value to add (add );

Default: 0.
• multiplier (mult );
Default: 1.
• minimal value (min);
Default: 0.

14.4.52. T_X / T_Y / T_Z (TX / TY / TZ, T-X / T-Y / T-Z) 2522
Keywords for formats tN, MO 19.1

• maximal value (max )

Default: 1020 ..

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.56) is used:

• new values for blocks, which coordinates are specified above.

This keyword has an E1/E3 compatible analogue TRANX (see 12.2.50), TRANY
(see 12.2.51), TRANZ (see 12.2.52).
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.47). They are will increase in 2 times.

14.4.52. T_X / T_Y / T_Z (TX / TY / TZ, T-X / T-Y / T-Z) 2523
Keywords for formats tN, MO 19.1

14.4.53. VARI

Data x tN E1 E3 IM GE ST x MO
format
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
parameters should be specified:

1. size of ith 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.53. VARI 2524

Keywords for formats tN, MO 19.1

14.4.54. NNC

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

The keyword is used to specify non-neighbour connections. The following parameters

should be specified:

• in one line with the keyword:

1. MULT [additional parameter] – values are recognized as transmissibility values;

2. MORE / ECLI – use MO units (METRIC: md − m; FIELD: md − f t ) or E1/E3
units (METRIC: rm3 · cp/bar ; FIELD: rb · cp/psi);
Default: ECLI.
3. ONPD vp [additional parameter] – don’t use these connections while the pressure
difference across them don’t exceeds specified value vp.

• in the following line:

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.

The data should be terminated with a slash /.

This keyword has an E1/E3 compatible analogue NNC (see 12.2.54).

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.54. NNC 2525

Keywords for formats tN, MO 19.1

14.4.55. NTG / NTOG

Data x tN E1 E3 IM GE ST x MO
format
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 E1/E3 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.55. NTG / NTOG 2526

Keywords for formats tN, MO 19.1

14.4.56. REPL

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

The keyword is used to modify array values. The following parameters should be specified:

• in one line with the keyword:

1. first coordinate of modifying block in X -direction;

Default: 1.
2. last coordinate of modifying block in X -direction;
Default: Nx .
3. first coordinate of modifying block in Y -direction;
Default: 1.
4. last coordinate of modifying block in Y -direction;
Default: Ny .
5. first coordinate of modifying block in Z -direction;
Default: 1.
6. last coordinate of modifying block in Z -direction;
Default: Nz .

• in the following line:

1. new values of modifying array;

Example
SWL
REPL 71 73 101 103 154 184
279*0.38/
In the example SWL (see 14.4.63) values are changed. New value of this parameter (0.38)
is assigned to specified blocks.

14.4.56. REPL 2527

Keywords for formats tN, MO 19.1

14.4.57. SGCR

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

The keyword specifies critical gas saturation in each cell for end point scaling.
The following parameters should be specified:

1. critical gas saturation for each cell.

Default: corresponding to the keyword KRGO (see 14.3.4).

The number of entered values must be equal to the number of grid blocks.

This keyword has an E1/E3 compatible analogue SGCR (see 12.6.30).

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.57. SGCR 2528

Keywords for formats tN, MO 19.1

14.4.58. SGL

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

This keyword defines connate gas saturation for grid blocks, used for saturation end point
scaling.
The following parameters should be specified:

1. connate gas saturation for each grid block.

Default: corresponding to the keyword KRGO (see 14.3.4).

The number of entered values must be equal to the number of grid blocks.

This keyword has an E1/E3 compatible analogue SGL (see 12.6.28).

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
the grid and to 0.45 for last 50 blocks.

14.4.58. SGL 2529

Keywords for formats tN, MO 19.1

14.4.59. SGU

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

This keyword defines maximal gas saturation for grid blocks, used for saturation end point
scaling.
The following parameters should be specified:

1. maximal gas saturation for each grid block.

Default: corresponding to the keyword KRGO (see 14.3.4).

The number of entered values must be equal to the number of grid blocks.

This keyword has an E1/E3 compatible analogue SGU (see 12.6.34).

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
the grid and to 0.85 for last 50 blocks.

14.4.59. SGU 2530

Keywords for formats tN, MO 19.1

14.4.60. SOGCr

Data x tN E1 E3 IM GE ST x MO
format
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.
The following parameters should be specified:

1. critical oil-to-gas saturation for each grid block.

Default: corresponding to the keyword KRGO (see 14.3.4).

The number of entered values must be equal to the number of grid blocks.

This keyword has an E1/E3 compatible analogue SOGCR (see 12.6.32).

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.60. SOGCr 2531

Keywords for formats tN, MO 19.1

14.4.61. SOWCr

Data x tN E1 E3 IM GE ST x MO
format
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.
The following parameters should be specified:

1. critical oil-to-water saturation for each grid block.

Default: corresponding to the keyword KRGO (see 14.3.4).

The number of entered values must be equal to the number of grid blocks.

This keyword has an E1/E3 compatible analogue SOWCR (see 12.6.31).

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.61. SOWCr 2532

Keywords for formats tN, MO 19.1

14.4.62. SWU

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

This keyword defines maximal water saturation for grid blocks, used for saturation end
point scaling.
The following parameters should be specified:

1. maximal water saturation for each grid block.

Default: corresponding to the keyword KRWO (see 14.3.3).

The number of entered values must be equal to the number of grid blocks.

This keyword has an E1/E3 compatible analogue SWU (see 12.6.33).

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.62. SWU 2533

Keywords for formats tN, MO 19.1

14.4.63. SWL

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

This keyword defines minimal water saturation for grid blocks, used for saturation end
point scaling.
The following parameters should be specified:

1. minimal water saturation for each grid block.

Default: corresponding to the keyword KRWO (see 14.3.3).

The number of entered values must be equal to the number of grid blocks.

This keyword has an E1/E3 compatible analogue SWL (see 12.6.26).

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.63. SWL 2534

Keywords for formats tN, MO 19.1

14.4.64. SWCR

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

This keyword defines critical water saturation for grid blocks, used for saturation end point
scaling.
The following parameters should be specified:

1. critical water saturation for each grid block.

Default: corresponding to the keyword KRWO (see 14.3.3).

The number of entered values must be equal to the number of grid blocks.

This keyword has an E1/E3 compatible analogue SWCR (see 12.6.29).

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.64. SWCR 2535

Keywords for formats tN, MO 19.1

14.4.65. XKRG

Data x tN E1 E3 IM GE ST x MO
format
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.
Default: 1 for each grid block.

The number of entering values should be equal to the number of grid blocks.

This keyword has an E1/E3 compatible analogue KRG (see 12.6.60).

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.65. XKRG 2536

Keywords for formats tN, MO 19.1

14.4.66. XKRO

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

The keyword sets scaling multipliers for the relative permeability values of oil at the
maximum 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: 1 for each grid block.

The number of entering values should be equal to the number of grid blocks.

This keyword has an E1/E3 compatible analogue KRO (see 12.6.58).

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

This example defines scaling multipliers for 20 grid blocks.

14.4.66. XKRO 2537

Keywords for formats tN, MO 19.1

14.4.67. XKRW

Data x tN E1 E3 IM GE ST x MO
format
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: 1 for each grid block.

The number of entering values should be equal to the number of grid blocks.

This keyword has an E1/E3 compatible analogue KRW (see 12.6.59).

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

This example defines scaling multipliers for 20 grid blocks.

14.4.67. XKRW 2538

Keywords for formats tN, MO 19.1

14.4.68. XPCG

Data x tN E1 E3 IM GE ST x MO
format
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). The
following parameters should be specified:

1. multipliers for the capillary pressure values for each grid block.
Default: 1 for each grid block.

The number of entering values should be equal to the number of grid blocks.

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

This example defines scaling multipliers for 20 grid blocks.

14.4.68. XPCG 2539

Keywords for formats tN, MO 19.1

14.4.69. XPCW

Data x tN E1 E3 IM GE ST x MO
format
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).
The following parameters should be specified:

1. multipliers for the capillary pressure values for each grid block.
Default: 1 for each grid block.

The number of entering values should be equal to the number of grid blocks.

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

This example defines scaling multipliers for 20 grid blocks.

14.4.69. XPCW 2540

Keywords for formats tN, MO 19.1

14.4.70. YKRW

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

This keyword is a full analog of the keyword KRWR (see 12.6.59) which is used by E1/E3.

14.4.70. YKRW 2541

Keywords for formats tN, MO 19.1

14.4.71. ZCORn

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
x GRID INIT RECU

The keyword sets z-coordinate values of block tops, i.e. their depth values. The following
parameters should be specified:

• depth values (must be specified 8 · Nx · Ny · Nz numbers) (METRIC: m, FIELD: f t ).

This keyword has an E1/E3 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.71. ZCORn 2542

Keywords for formats tN, MO 19.1

14.4.72. ZVAR

Data x tN E1 E3 IM GE ST x MO
format
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.72)
should be used with the name of data array. The following parameters should be specified:

1. values of a parameter for each layer.

Default: 0.

Example
SWL
ZVAR
43*0.375
In the example SWL (see 14.4.63) values in 43 layers of the model are equal to 0.375.

14.4.72. ZVAR 2543

Keywords for formats tN, MO 19.1

14.4.73. TSUM

Data x tN E1 E3 IM GE ST x MO
format
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).
The following parameters should be specified:
• in the same line with the keyword:
1. x -coordinate of the first cell;
Default: 1.
2. x -coordinate of the last cell;
Default: Nx .
3. y-coordinate of the first cell;
Default: 1.
4. y-coordinate of the last cell;
Default: Ny .
5. z-coordinate of the first cell;
Default: 1.
6. z-coordinate of the last cell;
Default: Nz .
• in the following line:
1. multiplier of initial value;
Default: 1.
2. maximal value. All ratio values which exceed this value will be reduced to this
maximal value.
Default: 1020 .

Example
TSUM 4* 7 7
1* 0.06
In the example the keyword TSUM (see 14.4.73) 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.73. TSUM 2544

Keywords for formats tN, MO 19.1

14.5. INIT Data Section

14.5.1. INIT

Data x tN E1 E3 IM GE ST x MO
format
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. INIT Data Section 2545

Keywords for formats tN, MO 19.1

14.5.2. EQUI

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID x INIT RECU

This keyword specifies properties of each equilibration region which are used in calcula-
tion of initial conditions. The following parameters should be specified:

1. depth (METRIC: m, FIELD: f t );

2. pressure at this depth (METRIC: bar , FIELD: psi);

3. depth of gas-oil contact (METRIC: m, FIELD: f t );

Default: depth of top cell of reservoir.

4. capillary pressure at depth of gas-oil contact (METRIC: bar , FIELD: psi);

Default: 0.

5. depth of water-oil contact (METRIC: m, FIELD: f t );

Default: depth of bottom cell of reservoir.

6. capillary pressure at depth of water-oil contact (METRIC: bar , FIELD: psi).

Default: 0.

This keyword has an E1/E3 compatible analogue EQUIL (see 12.16.2).

Example
EQUI
2330 237 2* 2320.8 0
2330 237 2* 2335.8 0

14.5.2. EQUI 2546

Keywords for formats tN, MO 19.1

14.5.3. CONS (INIT)

Data x tN E1 E3 IM GE ST x MO
format
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
parameters should be specified:

– in one line with the keyword:

1. [additional parameter] number of equilibration region for which data is spec-
ified;
– 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
parameters should be specified:

– in one line with the keyword:

1. [additional parameter] number of equilibration region for which data is spec-
ified;
Default: all regions.
– 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;
Default: Swc .

14.5.3. CONS (INIT) 2547

Keywords for formats tN, MO 19.1

6. 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.

Default: the mole values of initial composition: all values are 0.

Example
UNIT METR
...
INIT EQUI
...
CONS 1
87 282 /
In the example properties for EOS-system are specified. Initial temperature is 87 ◦ C,

initial saturation pressure is 282 bars.

14.5.3. CONS (INIT) 2548

Keywords for formats tN, MO 19.1

14.5.4. GOCX

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID x INIT RECU

The keyword can be used only if option EQUI (see 14.5.2) 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.4. GOCX 2549

Keywords for formats tN, MO 19.1

14.5.5. GOCY

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID x INIT RECU

The keyword can be used only if option EQUI (see 14.5.2) 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.5. GOCY 2550

Keywords for formats tN, MO 19.1

14.5.6. PBVD

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID x INIT RECU

The keyword should be used with the option EQUI (see 14.5.2). 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.7).
The following parameters should be specified:

• in one line with the keyword:

1. number of the region, for which data is specifying.

• on the next line the table with two columns is specifying:

1. depth (METRIC: m, FIELD: f t );

2. oil bubble point pressure at this depth (METRIC: barsa, FIELD: psia). The data
should be terminated with a slash /.

Default: if a number of region is absent, then data will be applied to the whole grid.

This keyword has an E1/E3 compatible analogue PBVD (see 12.16.8).

Example
PBVD
2000 250
2500 310
3000 350
/
In this example the data for one equilibration region is specified.

14.5.6. PBVD 2551

Keywords for formats tN, MO 19.1

14.5.7. RSVD

Data x tN E1 E3 IM GE ST x MO
format
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.2). This keyword is alternative to the keyword PBVD (see 14.5.6). The
following parameters should be specified:

• in one line with the keyword:

1. number of equilibration region to which data applies.

• in the next line the table with two columns is specifying:

1. depth (METRIC: m, FIELD: f t );

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: if a number of region is absent, then data will be applied to the whole grid.
This keyword has an E1/E3 compatible analogue RSVD (see 12.16.7).
Example
RSVD
2000 0.06
2500 0.068
3000 0.0735
/
In this example the data for one equilibration region is specified.

14.5.7. RSVD 2552

Keywords for formats tN, MO 19.1

14.5.8. RVVD

Data x tN E1 E3 IM GE ST x MO
format
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.2). The following parameters should be specified:

• in one line with the keyword:

1. number of equilibration region to which data is applied.

• on the next line the table with two columns is specifying:

1. depth (METRIC: m, FIELD: f t );

2. vaporized oil concentration value at this depth (METRIC: sm3 /sm3 , FIELD:
Msc f /stb). The data should be terminated with a slash /.

Default: if a number of region is absent, then data will be applied to the whole grid.
This keyword has an E1/E3 compatible analogue RVVD (see 12.16.9).
Example
RVVD
2000 0.00060
2500 0.00068
3000 0.000735
/
In this example the data for one equilibration region is specified.

14.5.8. RVVD 2553

Keywords for formats tN, MO 19.1

14.5.9. PCSH

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID x INIT RECU

The keyword sets options for capillary pressure values shift to stabilize solution when
option EQUI (see 14.5.2) is used.

The following parameters should be specified:

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 de-
fined by EQUI (see 14.5.2);
– 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.

Example
PCSH FULL

14.5.9. PCSH 2554

Keywords for formats tN, MO 19.1

14.5.10. SEPA

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID x INIT x RECU

The keyword sets separator properties. The following parameters should be specified:

• in one line with the keyword:

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:

1.1. temperature of the separator stage;
1.2. pressure of the separator stage;
1.3. [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.
1.4. [additional parameter] destination of the vapor of the stage. This parameter
has the same possible values as parameter (c).

This keyword has an E1/E3 compatible analogue SEPCOND (see 12.19.156).

Example
SEPA ALL EOS ZFAC
90 815
80 65
60 14.7

14.5.10. SEPA 2555

Keywords for formats tN, MO 19.1

14.5.11. AQCO

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID x INIT RECU

The keyword is used to specify blocks to which aquifer will be connected. The following
parameters should be specified:

1. aquifer name (it is specified via the keyword AQCT, see 14.5.12);

2. i-coordinate of the first cell to connect aquifer;

Default: 1.

3. i-coordinate of the last cell to connect aquifer;

Default: Nx .

4. j -coordinate of the first cell to connect aquifer;

Default: 1.

5. j -coordinate of the last cell to connect aquifer;

Default: Ny .

6. k -coordinate of the first cell to connect aquifer;

Default: 1.

7. k -coordinate of the last cell to connect aquifer;

Default: Nz .

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: all possible faces (i.e. ones, which has no neighbor active cells).

This keyword has an E1/E3 compatible analogue AQUANCON (see 12.17.11).

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.5.11. AQCO 2556

Keywords for formats tN, MO 19.1

14.5.12. AQCT

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID x 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.5.11). The following
parameters should be specified:

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);

Default: initial reservoir pressure.

10. water viscosity (cP);

11. [additional parameter] water pressure table index. IGNORED, this is a MO compati-
bility field;

12. [additional parameter] index of influence function table AQUT (see 14.5.13), which
specifies pressure dependence on time.
Default: 0.

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;

14.5.12. AQCT 2557

Keywords for formats tN, MO 19.1

This keyword has an E1/E3 compatible analogue AQUCT (see 12.17.9).

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.5.12. AQCT 2558

Keywords for formats tN, MO 19.1

14.5.13. AQUT

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID x INIT RECU

This keyword defines an influence function tables for Carter-Tracy aquifers.

The use of the defined table can be set via 12-th parameter of AQCT (see 14.5.12) key-
word. In this case AQUT (see 14.5.13) must be entered before AQCT (see 14.5.12).

The table should be entered on the lines below the keyword. The data entry must be
terminated with slash /.
One table row should contain the following parameters:

1. dimensionless time (positive and increasing down the column),

2. corresponding dimensionless pressure (positive).

This keyword has an E1/E3 compatible analogue AQUTAB (see 12.17.10).

Example
AQUT
0.012 0.167
0.045 0.223
0.100 0.300
0.170 0.380
0.200 0.450
0.270 0.480
0.300 0.500
0.400 0.580
0.500 0.620
0.600 0.680
0.700 0.730
/

14.5.13. AQUT 2559

Keywords for formats tN, MO 19.1

14.5.14. AQFE

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID x 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.5.11). The following
parameters should be specified:

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 E1/E3 compatible analogue AQUFETP (see 12.17.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.5.14. AQFE 2560

Keywords for formats tN, MO 19.1

14.5.15. AQUW

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID x 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.
• Default: YES.

It is allowed to use ON and OFF instead of YES and NO correspondingly.

The data should be terminated with a slash /.

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.5.15. AQUW 2561

Keywords for formats tN, MO 19.1

14.5.16. AQWO

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID x INIT RECU

The keyword sets option of index productivity calculation of analytical aquifer. The fol-
lowing parameters should be specified:

1. analytical aquifer index productivity calculation option:

• EVEN – index productivity is set to 1;

• AREA – index productivity is set to aquifer connection area.
• Default: EVEN.

The keyword AQUGP (see 12.17.15) which is used by tNavigator is analogous to this one.
Example
AQWO AREA

14.5.16. AQWO 2562

Keywords for formats tN, MO 19.1

14.5.17. RHAQ

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID x INIT RECU

This keyword specifies initial hydrocarbon in aqueous phase (as a gas/water ratio).
It should be use with keyword SOLU (see 14.2.32).
This keyword has an E1/E3-compatible analogue RSW (see 12.16.56).

14.5.17. RHAQ 2563

Keywords for formats tN, MO 19.1

14.6. RECUrrent Data Section

14.6.1. RECU

Data x tN E1 E3 IM GE ST x MO
format
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. RECUrrent Data Section 2564

Keywords for formats tN, MO 19.1

14.6.2. RATE

Data x tN E1 E3 IM GE ST x MO
format
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.16.64).

Example
RATE 1 MONT

In the example record of graphs with period one time per month is configured.

14.6.2. RATE 2565

Keywords for formats tN, MO 19.1

14.6.3. EFILe

Data x tN E1 E3 IM GE ST x MO
format
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 E1/E3-compatible analogue INCLUDE (see 12.1.80).

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 con-
nections 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 2566

Keywords for formats tN, MO 19.1

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 2567

Keywords for formats tN, MO 19.1

14.6.4. TFIL

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID INIT x RECU

This keyword specifies the name of file, from which well trajectories data will be read.
The following parameters should be specified:

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:

Example of this file format

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:

Example of this file format

track_name:branch_number
X Y Z MD

14.6.4. TFIL 2568

Keywords for formats tN, MO 19.1

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 2569

Keywords for formats tN, MO 19.1

14.6.5. ETAB

Data x tN E1 E3 IM GE ST x MO
format
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 /.

Alternative way of data specification.

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 including
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 inde-
pendently. It is specified in the description of the given keywords.

Example
EFORm WELL 'DD.MM.YYYY' MDL MDU RAD SKIN MULT
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).
Supported subkeywords of ETAB section:

14.6.5. ETAB 2570

Keywords for formats tN, MO 19.1

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:

Keyword Short description

SHUT (see 14.6.29) Shut well
STOP (see 14.6.30) Stop well
OPEN (see 14.6.38) 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 14.6.39) Set reference depth
PREX (see 14.6.21) Set external radius
XFLO (see 14.6.40) Allow or deny well crossflow

Pressure targets:

Keyword Short description

BHPT (see 14.6.41) Set BHP target
THPT (see 14.6.42) Set THP target
DRAW (see 14.6.54) Set drawdown target

Well production targets:

Keyword Short description

OPT (see 14.6.43) Set oil production target
GPT (see 14.6.43) Set gas production target
WPT (see 14.6.43) Set water production target
LPT (see 14.6.43) Set liquid production target
VPT (see 14.6.43) Set voidage production target

14.6.5. ETAB 2571

Keywords for formats tN, MO 19.1

Injection targets:

Keyword Short description

OIT (see 14.6.44) Set oil injection target
GIT (see 14.6.44) Set gas injection target
WIT (see 14.6.44) Set water injection target

Historical targets:

Keyword Short description

HOIL (see 14.6.31) Historical oil rate
HGAS (see 14.6.31) Historical gas rate
HWAT (see 14.6.31) Historical water rate
HLIQ (see 14.6.31) Historical liquid rate
HBHP (see 14.6.31) Historical BHP
HTHP (see 14.6.31) Historical THP
HWEF (see 14.6.31) Historical well efficiency factor

Other settings:

Keyword Short description

WEF (see 14.6.47) Well efficiency factor
LIFTETAB (see 14.6.45) Well lift rate
WALQ (see 14.6.46) Set an artificial lift value for a well
STRE (see 14.6.48) Specify an injection composition
CWAG (see 14.6.60) Set continuous injection of water and gas
TEMP (see 14.6.77) Injection fluid temperature
WWAG (see 14.6.26) Set well water and gas injection
WFRA (see 14.6.27) Set well fracture
WFRP (see 14.6.28) Set well fracture (It is recommended to use it instead of WFRA)
TRAC (see 14.6.73) Tracer injection

14.6.5. ETAB 2572

Keywords for formats tN, MO 19.1

Group production target:

Keyword Short description

GOPT (see 14.6.49) Set group oil production target
GGPT (see 14.6.49) Set group gas production target
GWPT (see 14.6.49) Set group water production target
GLPT (see 14.6.49) Set group liquid production target

Group injection target:

Keyword Short description

GGIT (see 14.6.50) Set group gas injection target
GWIT (see 14.6.50) Set group water injection target

Calculation:

Keyword Short description

RATE (see 14.6.2) Save graphs to disk

Group recycling targets:

Keyword Short description

RECY (see 14.6.56) Set recycle operation between two well groups
GGRT (see 14.6.59) Set group gas recycle target
GWRT (see 14.6.59) Set group water recycle target
VREP (see 14.6.55) Set up voidage replacement coefficient
GVRT (see 14.6.63) Settings of voidage replacement

Well and group limits:

Keyword Short description

PLIM (see 14.6.64) Set well production limit
ILIM (see 14.6.65) Set well injection limit

14.6.5. ETAB 2573

Keywords for formats tN, MO 19.1

Limit types:

Keyword Short description

OIL (description: FLOW, see 14.6.33) Oil rate
GAS (description: FLOW, see 14.6.33) Gas rate
WAT (description: FLOW, see 14.6.33) Water rate
LIQ (description: FLOW, see 14.6.33) Liquid rate
BHP (see 14.6.36) BHP value
THP (see 14.6.34) THP value
GOR (description: RATI, see 14.6.35) Gas-oil rate ratio
OGR (description: RATI, see 14.6.35) Oil-gas rate ratio
WCT (description: RATI, see 14.6.35) Watercut value
WOR (description: RATI, see 14.6.35) Water-oil rate ratio
WGR (description: RATI, see 14.6.35) Water-gas rate ratio

Other options:

Keyword Short description

HOURS (see 14.6.51) Time accuracy of event

14.6.5. ETAB 2574

Keywords for formats tN, MO 19.1

14.6.6. TTAB

Data x tN E1 E3 IM GE ST x MO
format
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 2575

Keywords for formats tN, MO 19.1

14.6.7. ENDE

Data x tN E1 E3 IM GE ST x MO
format
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 2576

Keywords for formats tN, MO 19.1

14.6.8. ENDT

Data x tN E1 E3 IM GE ST x MO
format
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 2577

Keywords for formats tN, MO 19.1

14.6.9. HFILe

Data x tN E1 E3 IM GE ST x MO
format
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 E1/E3-compatible analogue INCLUDE (see 12.1.80).

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 2578

Keywords for formats tN, MO 19.1

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 2579

Keywords for formats tN, MO 19.1

14.6.10. HTAB

Data x tN E1 E3 IM GE ST x MO
format
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 /.

Alternative way of data specification.

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 including
file. The end of included file is regarded as the end of data.

Example
HFORm WELL 'DD.MM.YYYY' QOIL QLIQ QWATr WEF BHP
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 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.10. HTAB 2580

Keywords for formats tN, MO 19.1

14.6.11. ENDH

Data x tN E1 E3 IM GE ST x MO
format
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 2581

Keywords for formats tN, MO 19.1

14.6.12. EFORm

Data x tN E1 E3 IM GE ST x MO
format
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 pa-
rameter] 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
EFORm WELL 'DD.MM.YYYY' MDL MDU RAD SKIN MULT
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 2582

Keywords for formats tN, MO 19.1

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 2583

Keywords for formats tN, MO 19.1

14.6.13. HFORm

Data x tN E1 E3 IM GE ST x MO
format
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: ksm3 /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 2584

Keywords for formats tN, MO 19.1

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
HFORm WELL 'DD.MM.YYYY' QOIL QLIQ QWATr WEF BHP
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 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.13. HFORm 2585

Keywords for formats tN, MO 19.1

14.6.14. EUNIts

Data x tN E1 E3 IM GE ST x MO
format
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
EFORm WELL 'DD.MM.YYYY' MDL MDU RAD SKIN MULT
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 2586

Keywords for formats tN, MO 19.1

14.6.15. HUNIts

Data x tN E1 E3 IM GE ST x MO
format
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).
The following parameters should be specified:

1. units for liquid rate – METRIC: sm3 /day (or ksm3 /day), FIELD: stb/day (or
Mstb/day);
Default: METRIC: sm3 /day, FIELD: stb/day.

2. units for gas rate – METRIC: sm3 /day (or ksm3 /day), FIELD: sc f /day or
(Msc f /day);
Default: METRIC: ksm3 /day, FIELD: Msc f /day.

3. units for liquid total – METRIC: ksm3 (or Msm3 ), FIELD: Mstb (or MMstb);
Default: METRIC: ksm3 , FIELD: Mstb.

4. units for gas total – METRIC: ksm3 (or Msm3 ), FIELD: Msc f (or MMsc f );
Default: METRIC: Msm3 , FIELD: MMsc f .

5. units for pressure – METRIC: bara (or barg), FIELD: psia (or psig).
Default: METRIC: bara, 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 2587

Keywords for formats tN, MO 19.1

14.6.16. PERF

Data x tN E1 E3 IM GE ST x MO
format
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 parame-
ter] 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 2588

Keywords for formats tN, MO 19.1

13. BRANCH [additional parameter] – branch number which will be perforated (see key-
word BRAN, see 14.6.72).

The keyword is analogous to an E1/E3 keyword COMPDAT (see 12.19.6).

Formulas used to calculate parameters of this keyword for MO and E1/E3 are presented
in the section 5.6.2 Connection transmissibility calculation (CF and Kh). Furthermore, the
formula used to calculate connection factor for MO models is defined by the keyword ETUNe
(see 14.1.16).
Example
EFORm WELL 'DD.MM.YYYY' MDL MDU RAD SKIN MULT
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 2589

Keywords for formats tN, MO 19.1

14.6.17. SQUEeze

Data x tN E1 E3 IM GE ST x MO
format
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).

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 parame-
ter] 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 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 E1/E3 keyword COMPDAT (see 12.19.6).
Example
EFORm WELL 'DD.MM.YYYY' MDL MDU RAD SKIN MULT
ETAB
6 01.12.1990 SQUE 1405.0 1527.0
P3 01.01.2012 SQUE 1 20 ZONE
ENDE
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):

14.6.17. SQUEeze 2590

Keywords for formats tN, MO 19.1

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 2591

Keywords for formats tN, MO 19.1

14.6.18. PROD

Data x tN E1 E3 IM GE ST x MO
format
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 E1/E3 compatible analogue WCONPROD (see 12.19.42).

Example
W_1 01.02.2002 PROD
W_1 well status will be changed to ”production” at 01.02.2002.

14.6.18. PROD 2592

Keywords for formats tN, MO 19.1

14.6.19. INJE

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID INIT x RECU

The keyword changes well status to ”injection”. The following parameters should be spec-
ified:

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 INJE which defines event.

This keyword has an E1/E3 compatible analogue WCONPROD (see 12.19.42).

Example
W_1 01.08.2006 INJE
W_1 well status will be changed to ”injection” at 01.08.2006.

14.6.19. INJE 2593

Keywords for formats tN, MO 19.1

14.6.20. LTAB

Data x tN E1 E3 IM GE ST x MO
format
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).

Specified parameters have to be matched with format specified by the keyword EFORm
(see 14.6.12).

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 LTAB which defines event.

4. table name. If 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 2594

Keywords for formats tN, MO 19.1

14.6.21. PREX

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID INIT x RECU

The keyword sets well external radius. It should be used only in table ETAB (see 14.6.5)
or after the keyword WELL (see 14.6.23). The following parameters should be specified:

1. well external radius (re ) (METRIC: m, FIELD: f t );

Default: 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 2595

Keywords for formats tN, MO 19.1

14.6.22. P-RE

Data x tN E1 E3 IM GE ST x MO
format
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 2596

Keywords for formats tN, MO 19.1

14.6.23. WELL

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID INIT x RECU

The keyword defines well and sets parameters of it control mode. The following parame-
ters should be specified:

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.32) - tubing head
pressure.

14.6.23. WELL 2597

Keywords for formats tN, MO 19.1

8. AND – is using to set injection of 2 fluids (WWAG, see 14.6.26). 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 2598

Keywords for formats tN, MO 19.1

14.6.24. LIFT

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID INIT x RECU

This keyword allows to specify a lift gas injection for a well specified by the keyword
WELL (see 14.6.23). LIFT can be used only after the keyword WELL (see 14.6.23) is specified
The keyword is followed by the data:

1. Name of the injected fluid or table name for the downhole pump. Only GAS is possible
for the fluid;

2. Rate of lift gas injection (required parameter if injected fluid is specified in the 1-st
parameter)

3. Turn lift on or off (optional parameter if injected fluid is specified in the 1-st parameter):

• OFF – lift gas injection is off;

• ON – lift gas injection is on.

The lift fluid rate is added to the flowing fluid stream for lift calculations only and is not
taken into account in calculations of the produced fluid rates.
Example
WELL P1
LIFT GAS 20

14.6.24. LIFT 2599

Keywords for formats tN, MO 19.1

14.6.25. WCOR

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID INIT x RECU

This keyword is used for correction of well positions locate in the corner or edge of the
model’s grid. If this option is not activated it is assumed that wells are located at the center of
the grid cell. If this option is activated a well is shifted to the corner or edge of the model’s
grid. Thus, the connection factor CF is calculated assuming the well is in the corner or edge
of model’s grid. Such correction is useful when a five spot pattern is applied
This keyword should be followed by keyword WELL (see 14.6.23).

• YES (ON) – option of correction of well positions turns on;

• No (OFF) – option of correction of well positions turns off.

Default: YES (ON) – option of correction of well positions turns on.

Example
WCOR OFF /
In this example the option of correction of well positions turns off.

14.6.25. WCOR 2600

Keywords for formats tN, MO 19.1

14.6.26. WWAG

Data x tN E1 E3 IM GE ST x MO
format
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 14.6.23). The following
parameters should be specified:

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.19.52), with is used in tNavigator.

Example
WWAG 30311 31 30
In the example the keyword WWAG specifies periods of gas and water injection for well
30311, which are equal to 31 and 30 days correspondingly.

14.6.26. WWAG 2601

Keywords for formats tN, MO 19.1

14.6.27. WFRA

Data x tN E1 E3 IM GE ST x MO
format
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.28) instead of WFRA. The keyword WFRP (see 14.6.28) is prepared to use in
MO models.This keyword is analogous to the keywords WFRACP (see 12.19.145), WFRAC
(see 12.19.143) COMPFRAC (see 12.19.148).

The following parameters should be specified (that ones which noted as [additional pa-
rameter] 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
EFORm. For example, DD.MM.YYYY);

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);

11. Fracture time constant (days);

14.6.27. WFRA 2602

Keywords for formats tN, MO 19.1

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.27. WFRA 2603

Keywords for formats tN, MO 19.1

14.6.28. WFRP

Data x tN E1 E3 IM GE ST MO
format
INPU FLUI RELA
Section
GRID INIT x RECU

The keyword is used for specifying hydraulic fracture.

The description of the matematical model of hydraulic fracture in tNavigator is in the

section Modified well model (5.7).

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 MO models.This keyword is analogous to the keywords

WFRACP (see 12.19.145), WFRAC (see 12.19.143) COMPFRAC (see 12.19.148).

The following parameters should be specified (that ones which noted as [additional pa-
rameter] 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
EFORm. For example, DD.MM.YYYY);
3. The keyword WFRP which specifies event;
4. i1 – first connection coordinate in X direction (coordinates of connection of well frac-
tures 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 frac-
tures to blocks should be specified by parameters 4-9 or depths should be specified by
parameters 10-11);
6. k1 – first connection coordinate in Z direction (coordinates of connection of well frac-
tures to blocks should be specified by parameters 4-9 or depths should be specified by
parameters 10-11);
7. 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
(coordinates of connection of well fractures to blocks should be specified by parameters
4-9 or depths should be specified by parameters 10-11);

14.6.28. WFRP 2604

Keywords for formats tN, MO 19.1

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 (is set in MD, METRIC: m, FIELD: f t ) (coordinates of connection
of well fractures to blocks should be specified by parameters 4-9 or depths should be
specified by parameters 10-11);

11. fracture upper depth (is set in MD, METRIC: m, FIELD: f t ) (coordinates of connection
of well fractures to blocks should be specified by parameters 4-9 or depths should be
specified by parameters 10-11);

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.19.145).
Note 1: If the fracture direction (azimuth angle) doesn’t correspond to this logic in
graphical interface check please if the keyword MAPAXES (see 12.2.67) is specified or
the visualization option Flip vertically is used.

13. Zenith angle (from 0 ◦ to 90 ◦ );

Default: 0 ◦ .

14. 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);

15. 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);

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.28. WFRP 2605

Keywords for formats tN, MO 19.1

• flow function name (the dependence between fracture permeability and phase flow
or time). 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);
• number of days (is case if the next parameter is – TIME). Dependence of perme-
ability versus time is set via the the following formula:
D−T
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.
Default: not defined; there is no dependence from flow.

21.• 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);

22. 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 multiplier
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;
Default: 1.

23. X1-coordinate of bounding box (the fracture shouldn’t be outside this box) (number of
layer in X direction should be specified);
Default: 1.

24. Y1-coordinate of bounding box (the fracture shouldn’t be outside this box) (number of
layer in Y direction should be specified);
Default: 1.

25. Z1-coordinate of bounding box (the fracture shouldn’t be outside this box) (number of
layer in Z direction should be specified);
Default: 1.

26. X2-coordinate of bounding box (the fracture shouldn’t be outside this box) (number of
layer in X direction should be specified);
Default: NX (see 12.1.28).

14.6.28. WFRP 2606

Keywords for formats tN, MO 19.1

27. Y2-coordinate of bounding box (the fracture shouldn’t be outside this box) (number of
layer in Y direction should be specified);
Default: NY (see 12.1.28).

28. Z2-coordinate of bounding box (the fracture shouldn’t be outside this box) (number of
layer in Z direction should be specified);
Default: NZ (see 12.1.28).

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.28. WFRP 2607

Keywords for formats tN, MO 19.1

14.6.29. SHUT

Data x tN E1 E3 IM GE ST x MO
format
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).

The following parameters should be specified:

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 specifying event;

2. shut well date (date format should correspond to the format specified in EFORm. For
example, DD.MM.YYYY);

3. the keyword SHUT.

The keyword has an E1/E3-compatible analogue WELOPEN (see 12.19.128).

Example
EFORm WELL 'DD.MM.YYYY' MDL MDU RAD SKIN MULT
ETAB
6 01.12.1990 SHUT
ENDE

14.6.29. SHUT 2608

Keywords for formats tN, MO 19.1

14.6.30. STOP

Data x tN E1 E3 IM GE ST x MO
format
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 EFIL (see 14.6.3).

The following parameters should be specified:

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 specifying event;

2. shut well date (date format should correspond to the format specified in EFORm. For
example, DD.MM.YYYY);

3. the keyword STOP.

The keyword has an E1/E3-compatible analogue WELOPEN (see 12.19.128).

Example
EFORm WELL 'DD.MM.YYYY' MDL MDU RAD SKIN MULT
ETAB
6 01.12.1990 STOP
ENDE

14.6.30. STOP 2609

Keywords for formats tN, MO 19.1

14.6.31. HOIL / HGAS / HWAT / HLIQ / HBHP / HTHP / HWEF

Data x tN E1 E3 IM GE ST x MO
format
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 EFIL (see 14.6.3).

• HOIL – historical oil rate target;

• HGAS – historical gas rate target;

• HWAT – historical water rate target;

• HLIQ – historical liquid rate target;

• HBHP – historical bottom hole pressure value target BHP (see 14.6.36);

• HTHP – historical tubing head pressure value target THP (see 14.6.34);

• 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.19.43), which is used
by E1/E3.
Example
ETAB
607 01.11.1999 HWAT HWEF
607 01.12.1999 HWAT OFF HGAS
In the example the keywords HWAT (see 14.6.31) and HWEF (see 14.6.31) 01.11.1999
specify targets, corresponding to these keywords, for well 607. 01.12.1999 limiting by histor-
ical water rate target is stopped and by historical gas target is set.

14.6.31. HOIL / HGAS / HWAT / HLIQ / HBHP / HTHP / HWEF 2610

Keywords for formats tN, MO 19.1

14.6.32. TUBI

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID INIT x RECU

The keyword indicates an input of tubing head pressure table. The following parameters
should be specified:

1. table name;

2. reference depth for values of bottom hole pressures, which are specified in the table
(METRIC: m; FIELD: f t );
Default: value of depth, which defined by the keyword DATUm (see 14.4.5).

3. format of input table:

• PACK – for all values of RATI (see 14.6.35) one array of BHP (see 14.6.36) values
will be inputed;
• LONG – subkeyword BHP (see 14.6.36) will be specified for each ratio value
specified by the keyword RATI (see 14.6.35).
• Default: PACK.

Also after the keyword TUBI one or several keywords, which define values of variables
in the table, should be specified: FLOW (see 14.6.33), THP (see 14.6.34), RATI (see 14.6.35)
and BHP (see 14.6.36).

The data should be terminated with a slash /.

14.6.32. TUBI 2611

Keywords for formats tN, MO 19.1

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.32) 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.33). 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.32. TUBI 2612

Keywords for formats tN, MO 19.1

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.36) values.

14.6.32. TUBI 2613

Keywords for formats tN, MO 19.1

14.6.33. FLOW

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID INIT x RECU

The keyword specifies fluid rates for THP table (TUBI, see 14.6.32). The keyword FLOW
should be used after the keyword TUBI (see 14.6.32). The following parameters should be
specified:
• in one line with the keyword:
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).
– Default: OIL.
• on the next line:
1. rate values. This values must be increasing. The data should be terminated with a
slash /.

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 /

In the example 4 values of gas rate are specified.

14.6.33. FLOW 2614

Keywords for formats tN, MO 19.1

14.6.34. THP

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID INIT x RECU

The keyword specifies values of tubing head pressure for the keyword TUBI (see 14.6.32).
The keyword THP should be used after the keyword TUBI (see 14.6.32). The following pa-
rameters should be specified:

1. values of THP (METRIC: bar , FIELD: psi). The data should be terminated with a
slash /.

Default: If subkeyword THP (see 14.6.34) is not specified, then the pressure value, which
was specified at WELL (see 14.6.23), is considered as the only value of THP.
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 /

In the example one value of THP is specified. It is equal to 15 bar .

14.6.34. THP 2615

Keywords for formats tN, MO 19.1

14.6.35. RATI

Data x tN E1 E3 IM GE ST x MO
format
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.32). The keyword RATI should be used only after the keywords TUBI (see 14.6.32),
FLOW (see 14.6.33) and THP (see 14.6.34). The following parameters should be specified:
• in one line with the keyword:
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
...
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 /

In the example ratio type WGR is used.

14.6.35. RATI 2616

Keywords for formats tN, MO 19.1

14.6.36. BHP

Data x tN E1 E3 IM GE ST x MO
format
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.32) and all of its subkeywords (FLOW (see 14.6.33), THP
(see 14.6.34) and RATI, see 14.6.35).

The following parameters should be specified:

1. type of ith ratio;

2. value of ith 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.35). Each line of the table should be ended by /.
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 /

In the example BHP tables are specified by the keyword BHP (see 14.6.36). These tables
are specified for each ratio value (RATI, see 14.6.35). The number of columns of each table is
equal to the number of values of parameter FLOW (see 14.6.33). The number of lines is equal
to the number of values of parameter THP (see 14.6.34).

14.6.36. BHP 2617

Keywords for formats tN, MO 19.1

14.6.37. ALQ

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID INIT x RECU

This keyword specifies artificial lift quantities for a tubing head pressure table defined by
the keyword TUBI (see 14.6.32). ALQ can be used only after the keyword TUBI (see 14.6.32)
is specified and after the following keywords FLOW (see 14.6.33), THP (see 14.6.34) and
RATI (see 14.6.35), but before BHP (see 14.6.36).
On the same line after the ALQ an optional parameter GRAT can be specified. In this case
the artificial lift quantity is gas rate. On the next line artificial lift values are specified. Values
may be spread over more than one line. The data should be terminated with Code/. If GRAT
is specified then the following units are used: (METRIC: ksm3 /day; FIELD: Mscf/day).
An artificial lift quantity can be any variable affecting the lift performance of the well.
The ALQ value for a well can be specified using the event WALQ (see 14.6.46) in the section
RECU.
This keyword has an E1/E3 compatible analogue 6 parameter of the keyword VFPPROD
(see 12.19.66).
Example
TUBI TAB1 1505 PROD LONG
...
ALQ GRAT
0 10 20 /

In this example the keyword ALQ specifies 3 artificial lift values for the table TAB1 given
by the keyword TUBI (see 14.6.32). Since GRAT is specified ALQ set gas rates: 0, 10 and 20
(METRIC: ksm3 /day; FIELD: Mscf/day).

14.6.37. ALQ 2618

Keywords for formats tN, MO 19.1

14.6.38. OPEN (RECU)

Data x tN E1 E3 IM GE ST x MO
format
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 EFIL (see 14.6.3) file to specify well event.

The following parameters should be specified:

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
EFORm (see 14.6.12). For example, DD.MM.YYYY);

3. the keyword OPEN.

This keyword has an E1/E3 compatible analogue WELOPEN (see 12.19.128).

Example
EFORm WELL 'DD.MM.YYYY' MDL MDU RAD SKIN MULT
ETAB
6 01.12.1990 OPEN
ENDE
In the example by the keyword OPEN well 6 is opened on 01.12.1990.

14.6.38. OPEN (RECU) 2619

Keywords for formats tN, MO 19.1

14.6.39. DREF

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID INIT x RECU

The keyword specifies a reference depth for well’s bottom hole pressure. This keyword
should be used inside ETAB (see 14.6.5) table or inside EFIL (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.

The following parameters should be specified:

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.19.3)
used by E1/E3.
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.39. DREF 2620

Keywords for formats tN, MO 19.1

14.6.40. XFLO

Data x tN E1 E3 IM GE ST x MO
format
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 EFIL (see 14.6.3) file to specify well event.
The following parameters should be specified:

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 12.19.3) used by E1/E3.
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.40. XFLO 2621

Keywords for formats tN, MO 19.1

14.6.41. BHPT

Data x tN E1 E3 IM GE ST x MO
format
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 EFIL (see 14.6.3) file to specify well event.
The following parameters should be specified:

1. pressure value (METRIC: bar , FIELD: psi).

This keyword is analogous to the 9-th parameter of the keyword WCONPROD

(see 12.19.42) used by E1/E3.
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.41. BHPT 2622

Keywords for formats tN, MO 19.1

14.6.42. THPT

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID INIT x RECU

The keyword sets target for the value of tubing head pressure. This keyword should be
used inside ETAB (see 14.6.5) table or inside EFIL (see 14.6.3) file to specify well event.
The following parameters should be specified:

1. pressure value (METRIC: bar , FIELD: psi).

This keyword is analogous to the 10-th parameter of the keyword WCONPROD

(see 12.19.42) used by E1/E3.
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.42. THPT 2623

Keywords for formats tN, MO 19.1

14.6.43. OPT / WPT / GPT / LPT / VPT

Data x tN E1 E3 IM GE ST x MO
format
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 EFIL (see 14.6.3) file to specify well event.
The following parameters should be specified:

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.19.42), which is used by E1/E3.
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.43. OPT / WPT / GPT / LPT / VPT 2624

Keywords for formats tN, MO 19.1

14.6.44. OIT / GIT / WIT

Data x tN E1 E3 IM GE ST x MO
format
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
EFIL (see 14.6.3) file to specify well event.
The following parameters should be specified:

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 12.19.44) used by E1/E3.
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.44. OIT / GIT / WIT 2625

Keywords for formats tN, MO 19.1

14.6.45. LIFT

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID INIT x RECU

The keyword specifies well lift rate. This keyword should be used inside ETAB (see 14.6.5)
table or inside EFIL (see 14.6.3) file to specify well event.
The following parameters should be specified:

1. lift gas rate (METRIC: sm3 /day, FIELD: Msc f /day).

This keyword has an E1/E3 compatible analogue 12 parameter of the keyword WCON-
PROD (see 12.19.42).
Example
ETAB
...
P-1 01.04.2014 LIFT 1000
In this example on date 01.04.2014 lift gas rate equal to 1000 is set for the well P-1.

14.6.45. LIFT 2626

Keywords for formats tN, MO 19.1

14.6.46. WALQ

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID INIT x RECU

This keyword specifies artificial lift quantity for a well. WALQ is active if well has a
tubing table for which an ALQ variable is specified (see TUBI, see 14.6.32).
The keyword is followed by the parameters:

1. Well artificial lift value;

2. Optional parameters:

• HOURS – allows to add the extra time in hours to the time of a well event.

The units of WALQ should match those used by keyword ALQ (see 14.6.37) when speci-
fying the tubing table.
This keyword has an E1/E3 compatible analogue 12 parameter of the keyword WCON-
PROD (see 12.19.42).
Example
ETAB
P1
...
01/Jan/2002 WALQ 2
In this example the artificial lift value for the well P1 is set equal to 2 at 01/Jan/2002.

14.6.46. WALQ 2627

Keywords for formats tN, MO 19.1

14.6.47. WEF

Data x tN E1 E3 IM GE ST x MO
format
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 EFIL (see 14.6.3) file to specify well event.
The following parameters should be specified:

1. well efficiency factor (a number between 0 and 1).

This keyword has an E1/E3 compatible analogue WEFAC (see 12.19.83).

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.47. WEF 2628

Keywords for formats tN, MO 19.1

14.6.48. STRE

Data x tN E1 E3 IM GE ST x MO
format
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 EFIL (see 14.6.3) file to specify well event.
The following parameters should be specified:

1. component to inject. Use the keyword SCMP (see 14.1.10) to specify several compo-
nents to inject.

This keyword has an E1/E3 compatible analogue WELLSTRE (see 12.19.184).

Example
T1 09.06.2021 STRE H2S
In the example the well T1 is injecting H2S component.

14.6.48. STRE 2629

Keywords for formats tN, MO 19.1

14.6.49. GOPT / GGPT / GWPT / GLPT

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID INIT x RECU

These keywords set targets for well production groups for oil, gas, water and liquid rates
correspondingly. These keywords should be used inside ETAB (see 14.6.5) table or inside EFIL
(see 14.6.3) file to specify well event.
The following parameters should be specified:

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.19.86) used by E1/E3.
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.49. GOPT / GGPT / GWPT / GLPT 2630

Keywords for formats tN, MO 19.1

14.6.50. GGIT / GWIT

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID INIT x RECU

These keywords set targets for well injection groups gas and water rates correspondingly.
These keywords should be used inside ETAB (see 14.6.5) table or inside EFIL (see 14.6.3) file
to specify well event.
The following parameters should be specified:

1. group to which targets are set;

2. date at which targets start operating;

3. subkeyword GGIT / GWIT;

4. injection rate value. Units:

• if GWIT is specified – METRIC: sm3 /day, FIELD: stb/day;

• if GGIT is specified – METRIC: sm3 /day, FIELD: Msc f /day.

These keywords are analogous to the keyword GCONINJE (see 12.19.95) which is used
by E1/E3.
Example
ETAB
ALLProd 01.01.2025 GGIT 1124.91781 /
ALLProd 01.01.2026 GGIT 1172.32877 /
In the example 2 events are set for group ALLProd. On 01.01.2025 group target for gas
rate which is equal to 1124.91781 sm3 /day is set. On 01.01.2026 group target for gas rate
which is equal to 1172.32877 sm3 /day is set.

14.6.50. GGIT / GWIT 2631

Keywords for formats tN, MO 19.1

14.6.51. HOURS

Data x tN E1 E3 IM GE ST x MO
format
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).
The following parameters should be specified:

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.51. HOURS 2632

Keywords for formats tN, MO 19.1

14.6.52. DATE / READ / TIME

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID INIT x RECU

The keyword specifies the time and simulator will read recurrent data until respective date.
The following parameters should be specified:

1. the time to be simulated:

• the number of days/months/years;

• date in one of two formats:
– DD MMM YYYY;
– MMM DD YYYY.
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.52. DATE / READ / TIME 2633

Keywords for formats tN, MO 19.1

14.6.53. GROU

Data x tN E1 E3 IM GE ST x MO
format
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);
Default: 1.

4. well names list.

This keyword has an E1/E3 compatible analogue GRUPTREE (see 12.19.100).

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.53. GROU 2634

Keywords for formats tN, MO 19.1

14.6.54. DRAW

Data x tN E1 E3 IM GE ST x MO
format
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 EFIL (see 14.6.3) file to specify well event.
The following parameters should be specified:

1. drawdown value (METRIC: bar , FIELD: psi).

This keyword has an E1/E3 compatible analogue WELDRAW (see 12.19.123).

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.54);

• bottom hole pressure target value is equal to 50 bars (via the keyword BHPT,
see 14.6.41);

• well historical efficiency factor value is used as a target (via the keyword HWEF,
see 14.6.31).

14.6.54. DRAW 2635

Keywords for formats tN, MO 19.1

14.6.55. VREP

Data x tN E1 E3 IM GE ST x MO
format
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 EFIL (see 14.6.3) file to specify well event.
The following parameters should be specified:

1. group name which contains injecting wells;

Default: ALL.

2. group name which contains producing wells;

Default: ALL.

3. voidage replacement coefficient.

Default: 1.

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.

This keyword has an E1/E3 compatible analogue GCONINJE (see 12.19.95).

Example
GR-I 01.01.2014 VREP GR-P 1.75
In the example the keyword VREP sets voidage replacement coefficient. Value of compen-
sating injection fluid rate will be greater than producing rate 1.75 times.

14.6.55. VREP 2636

Keywords for formats tN, MO 19.1

14.6.56. RECY

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID INIT x RECU

The keyword sets recycle operation between two well groups. This keyword should be
used inside ETAB (see 14.6.5) table or inside EFIL (see 14.6.3) file to specify well event.
The following parameters should be specified:

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.

Notice that it can be possible to specify makeup and sales rates for recycle operation using
keywords MAKE (see 14.6.57) and SALE (see 14.6.58), respectively.
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.56. RECY 2637

Keywords for formats tN, MO 19.1

14.6.57. MAKE

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID INIT x RECU

This keyword specifies the amount of makeup gas required in a recycle operation. The
makeup gas is an additional gas that can be injected. In this case the injection rate can exceed
the production rate minus the sales rate. Using the SALE (see 14.6.58) keyword it is possible
to specify the amount of gas produced from a well that will be excluded from recycling.
MAKE is a sub-keyword of the RECY (see 14.6.56) keyword and must be used only after it.
MAKE is followed by two parameters: the first parameter is required and the second one
is optional.

1. Makeup rate for current group;

2. Format (optional):

• RATE – makeup rate is defined as a rate;

• FRAC – makeup rate is defined as a fraction.

Example
MAKE 100 RATE

14.6.57. MAKE 2638

Keywords for formats tN, MO 19.1

14.6.58. SALE

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID INIT x RECU

This keyword specifies amount of gas produced from a well that will be removed (e.g., to
be sold) from recycle operation. SALE is a sub-keyword of the RECY (see 14.6.56) keyword
and must be used only after it. Makeup gas can be injected before a recycle operation using
MAKE (see 14.6.57) keyword.
SALE is followed by two parameters: the first parameter is required and the second one is
optional.

1. Sales rate for current group;

2. Format (optional):

• RATE – sales rate is defined as a rate. By default RATE is used;

• FRAC – sales rate is defined as a fraction.

This keyword controls the recycling and remove (sales) for a given sub-rate or fraction of
the production. An amount of gas defined by SALE keyword is subtracted from production
of the producer group specified by RECY (see 14.6.56) keyword. If for the recycling requires
less than available amount of the remaining gas the extra amount of gas will be added to sales
gas total.
Example
SALE 10 RATE

14.6.58. SALE 2639

Keywords for formats tN, MO 19.1

14.6.59. GGRT / GWRT

Data x tN E1 E3 IM GE ST x MO
format
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 EFIL (see 14.6.3)
file to specify well event.
The following parameters should be specified:

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: RESV.

This keyword has an E1/E3 compatible analogue GCONINJE (see 12.19.95).

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.59. GGRT / GWRT 2640

Keywords for formats tN, MO 19.1

14.6.60. CWAG

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID INIT x RECU

This keyword specifies a well event, that’s why it should be used inside ETAB (see 14.6.5)
table or inside EFIL (see 14.6.3) file.
The keyword sets continuous simultaneous water and gas injection. The following param-
eters should be specified:

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.19.44) used by E1/E3.
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.60. CWAG 2641

Keywords for formats tN, MO 19.1

14.6.61. KMOD

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID INIT x RECU

The keyword is used to change cells permeability values during calculation. The following
parameters should be specified:

• in one line with the keyword:

1. X -coordinate of the first cell to change permeability;

Default: 1.
2. X -coordinate of the last cell to change permeability;
Default: Nx .
3. Y -coordinate of the first cell to change permeability;
Default: 1.
4. Y -coordinate of the last cell to change permeability;
Default: Ny .
5. Z -coordinate of the first cell to change permeability;
Default: 1.
6. Z -coordinate of the last cell to change permeability;
Default: Nz .
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).

Example
KMOD 32 38 84 88 1 6 SCALAR
10
In the example via the keyword KMOD (see 14.6.61) the values of cells permeability will
be multiplied by 10.

14.6.61. KMOD 2642

Keywords for formats tN, MO 19.1

14.6.62. PARE

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID INIT x RECU

The keyword is used to specify parent well group for a well group. The following param-
eters should be specified:

1. name of the group which will be assigned to a parent group;

2. name of the parent group.

Default: 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.62. PARE 2643

Keywords for formats tN, MO 19.1

14.6.63. GVRT

Data x tN E1 E3 IM GE ST x MO
format
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 EFIL (see 14.6.3)
file to specify well event.

The following parameters should be specified:

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.63. GVRT 2644

Keywords for formats tN, MO 19.1

14.6.64. PLIM

Data x tN E1 E3 IM GE ST x MO
format
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 EFIL (see 14.6.3) file.

This keyword sets well lower limits.

The following parameters should be specified:

1. limit type:

• OIL – oil rate (METRIC: sm3 /day; FIELD: stb/day);

• GAS – gas rate (METRIC: sm3 /day; FIELD: Msc f /day);
• WAT – water rate (METRIC: sm3 /day; FIELD: stb/day);
• RESV – reservoir volume rate (METRIC: rm3 /day; FIELD: rb/day);
• LIQ – liquid rate (METRIC: sm3 /day; FIELD: stb/day);
• BHP – bottom hole pressure (METRIC: barsa, FIELD: psi);
• THP – top hole pressure (METRIC: barsa, FIELD: psi);
• 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 );
• WOR – water-oil ratio (METRIC: sm3 /sm3 ; FIELD: stb/stb);
• GWR – gas-water ratio (METRIC: ksm3 /sm3 ; FIELD: Msc f /stb).

2. limit value;

3. action to well if limit will be exceeded:

• SHUT – shut well;

• WORK TOP – shut the topmost perforation;
• WORK BOT – shut the bottommost perforation;
• WORK WORS – shut the worst offending perforation;
• STOP – stop run.

14.6.64. PLIM 2645

Keywords for formats tN, MO 19.1

This keyword has an E1/E3 compatible analogue WECONX (see 12.19.75).

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.64. PLIM 2646

Keywords for formats tN, MO 19.1

14.6.65. ILIM

Data x tN E1 E3 IM GE ST x MO
format
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 EFIL (see 14.6.3) file.

This keyword sets injector lower limits.

The following parameters should be specified:

1. limit type:

• WAT – water rate (METRIC: sm3 ; FIELD: stb);

• GAS – gas rate (METRIC: sm3 ; FIELD: stb).

2. limit value;

3. action to well when the predicted value falls below the limit value:

• SHUT MIN – shut well.

Example
W1 01.02.2018 ILIM GAS 10 SHUT MIN /
In the example limit on the injector W1 is set. Limit will be active since 01.02.2018. The
injector will bu shut when rate falls below 10 ksm3 /day.

14.6.65. ILIM 2647

Keywords for formats tN, MO 19.1

14.6.66. GLIM

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID INIT x RECU

This keyword specifies group production limits. The keyword is followed by 5 parameters:
3 parameters are required, 2 parameters are optional. All parameters are specified on the same
line with the keyword.
The following parameters should be specified:

1. Name of group of production wells under control;

2. Limit type:

• OIL – oil production target;

• GAS – gas production target;
• WAT – water production target;
• RESV – reservoir volume production target;
• LIQ – liquid production target;
• GOR – gas-oil ratio;
• OGR – oil-gas ratio;
• WCT – water cut;
• WOR – water-oil ratio;
• GWR – gas-water ratio;
• WGR – water-gas ratio;
• GLR – gas-liquid ratio;
• LGR – liquid-gas ratio.

3. Group limit value;

4. Optional parameter 1:

• MIN – minimum limit;

• MAX – maximum limit;
• HOLD – target. It can be applied to rate limits (e.g., OIL, GAS etc.) and can not
applied to ratios (e.g., GOR, WOR etc.).

5. Optional parameter 2:

14.6.66. GLIM 2648

Keywords for formats tN, MO 19.1

• STIM – production wells in a group will be activated if minimum rate limit or a

group ratio is violated;
• WORK – a workover operation performed on the group of wells:
– WRKW – workover the worst well in the group;
– WRKS – shut the worst well the in group;
– WRKA – workover all the wells;
Default: WRKA.
• DRIL – a production well (from a group) belonging to the drilling queue will be
drilled to reach minimum rate limit in case of violation of minimum rate limit;
• GRED – redefine one or more wells in the group in case of limit is violated;
• SHUT – all wells in the group will be shut when limit violation occurs;
• STOP – the simulation will be terminated when limit violation occurs (only for
MIN and MAX).

Only one type of the limit can be specified (e.g., OIL). If a new type of the limit is specified
then previous types are skipped.
There is no significant difference between MAX/MIN and HOLD limits. MIN and MAX
limits specify events at which actions execute. HOLD defines continuous adjustment of the
group to reach a rate target.
A well can be included into the drilling queue if it is included both in the group and in
the group ”DRIL”. The well maximum rate and pressure targets are specified as usual, but the
well will not be used until it is used in the action DRIL.
This keyword has a tNavigator analog GECONX (see 12.19.76).

Example
GLIM ML OIL 650 MAX SHUT /

In this example the group ML will be shut when oil production rate exceeds the maximum
value 650.

14.6.66. GLIM 2649

Keywords for formats tN, MO 19.1

14.6.67. CIJK

Data x tN E1 E3 IM GE ST x MO
format
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 EFIL (see 14.6.3) file.

The keyword sets coordinates of well perforations. The data should be terminated with a
slash /.
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 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 );

Default: 0.5 f t .

9. [additional parameter] multiplier of transmissibility coefficient;

Default: 1.

10. [additional parameter] skin-factor;

Default: 0.

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 );

14.6.67. CIJK 2650

Keywords for formats tN, MO 19.1

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.67. CIJK 2651

Keywords for formats tN, MO 19.1

14.6.68. ARRAy

Data x tN E1 E3 IM GE ST x MO
format
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.
The following parameters should be specified:

• in the line with the keyword:

1. time intervals unit:

– DAYS – day;
– MONT – month;
– YEAR – year;
– DATE – steps are specified in full date format.
– Default: DATE.
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 /.

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.68. ARRAy 2652

Keywords for formats tN, MO 19.1

14.6.69. FREQ

Data x tN E1 E3 IM GE ST x MO
format
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.69) always follows the keyword
RATE (see 14.6.2).
The following parameters should be specified:

1. a multiple for frequency of data output to monitor.

Default: 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.69. FREQ 2653

Keywords for formats tN, MO 19.1

14.6.70. DELTa

Data x tN E1 E3 IM GE ST x MO
format
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 MO compatibility field.

14.6.70. DELTa 2654

Keywords for formats tN, MO 19.1

14.6.71. COMP

Data x tN E1 E3 IM GE ST x MO
format
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 14.6.23) and should be specified after it.

The following parameters should be specified:

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;
Default: 6 inches.
5. skin-factor;
Default: 0.
6. transmissibility multiplier;
Default: 1.
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.
• Default: FRAC.
This keyword has a tNavigator analog COMPDATMD (see 12.19.10).

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.71. COMP 2655

Keywords for formats tN, MO 19.1

14.6.72. BRANch

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID INIT x RECU

The subkeyword is optional for keyword PERF (see 14.6.16), which defines well perfora-
tion event. BRAN (see 14.6.72) 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.19.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

EFORm WELL 'DD.MM.YYYY' MDL MDU RAD SKIN MULT

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.72. BRANch 2656

Keywords for formats tN, MO 19.1

14.6.73. TRAC (RECU)

Data x tN E1 E3 IM GE ST x MO
format
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 EFIL (see 14.6.3) file.
The keyword sets the beginning of tracer injection.
The possibility to inject several passive tracers in one well is available.

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.73. TRAC (RECU) 2657

Keywords for formats tN, MO 19.1

14.6.74. WGPP

Data x tN E1 E3 IM GE ST x MO
format
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
parameters should be specified:

1. well name. Only one well name can be specified.

Example
WGPP PROD1

14.6.74. WGPP 2658

Keywords for formats tN, MO 19.1

14.6.75. WMPG

Data x tN E1 E3 IM GE ST x MO
format
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
parameters should be specified:

1. well name. Only one well name can be specified.

Example
WMPG PROD1

14.6.75. WMPG 2659

Keywords for formats tN, MO 19.1

14.6.76. WRG

Data x tN E1 E3 IM GE ST x MO
format
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:

1. well name. Only one well name can be specified.

Example
WRG PROD1

14.6.76. WRG 2660

Keywords for formats tN, MO 19.1

14.6.77. TEMP (RECU)

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID INIT x RECU

The keyword sets temperature of fluid to be injected by the well. This keyword can be
used only with the keyword WELL (see 14.6.23) and should be specified after it.

The following parameters should be specified:

1. temperature of fluid to be injected (METRIC: ◦ C, FIELD: ◦ F)

Default: if the keyword is not specified, fluid will be injected at 15 ◦ C or 60 ◦ F.

Example
WELL 232 INJE HLIQ PMIN=110 QOIL=100 HWEF
TEMP 150
In the example well 232 injects fluid at 150 ◦ F.

14.6.77. TEMP (RECU) 2661

Keywords for formats tN, MO 19.1

14.6.78. TEST

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID INIT x RECU

The keyword sets the period of shut wells testing for opening. The following parameters
should be specified:

1. periodicity of test performing;

Default: 3 month.

2. [additional parameter] units for parameter 1:

• DAYS – day;
• MONT – month;
• YEAR – year.
• Default: DAYS.

This keyword has an E1/E3 compatible analogue WTEST (see 12.19.183).

Example
TEST 1 YEAR
In the example periodicity of test performing is 1 year.

14.6.78. TEST 2662

 19.1

14.6.79. STMO

Data x tN E1 E3 IM GE ST x MO
format
INPU FLUI RELA
Section
GRID INIT x RECU

The keyword modifies saturation regions of grid blocks of a box during model run. The
following parameters should be specified:

• in the line with the keyword:

1. lower coordinate of the box (along X -direction);

Default: 1.
2. upper coordinate of the box (along X -direction);
Default: Nx .
3. lower coordinate of the box (along Y -direction);
Default: 1.
4. upper coordinate of the box (along Y -direction);
Default: Ny .
5. lower coordinate of the box (along Z -direction);
Default: 1.
6. upper coordinate of the box (along Z -direction);
Default: Nz .
7. [additional parameter] SCALAR – if this subkeyword is specified, then one num-
ber is set in the next line, which defines the number of saturation region of box
blocks.

• in the next line:

1. saturation region number of blocks in the specified box. If subkeyword SCALAR

is specified, then the number of saturation region of box blocks is set.

The data should be terminated with a slash /.

Example
STMO 4* 2 2 SCALAR
2 /
In the example all blocks of the 2-nd layer in Z direction will be assigned to the 2-nd
saturation region.

14.6.79. STMO 2663

15. Keyword definitions index formats E1, E3
A ASPDEPO . . . . . . . . . . . . . . . . . . . . . . . . . 1132
ACF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1193
ACFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1195
ACTDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . 465
ACTION . . . . . . . . . . . . . . . . . . . . . . . . . . 1821
ACTIONG . . . . . . . . . . . . . . . . . . . . . . . . .1823
ACTIONR . . . . . . . . . . . . . . . . . . . . . . . . . 1826
ACTIONW . . . . . . . . . . . . . . . . . . . . . . . . 1828
ACTIONX . . . . . . . . . . . . . . . . . . . . . . . . .1831
ACTNUM . . . . . . . . . . . . . . . . . . . . . . . . . . 623
ADD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
ADDREG . . . . . . . . . . . . . . . . . . . . . . . . . . 812
ADDZCORN . . . . . . . . . . . . . . . . . . . . . . . 593
ADSALNOD . . . . . . . . . . . . . . . . . . . . . . 1042
AIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
AIMFRAC . . . . . . . . . . . . . . . . . . . . . . . . . . 544
AIMPVI . . . . . . . . . . . . . . . . . . . . . . . . . . . 1996
ALKADS . . . . . . . . . . . . . . . . . . . . . . . . . . 1110
ALKALINE . . . . . . . . . . . . . . . . . . . . . . . . 490
ALKROCK . . . . . . . . . . . . . . . . . . . . . . . . 1111
ALPOLADS . . . . . . . . . . . . . . . . . . . . . . . 1109
ALSURFAD . . . . . . . . . . . . . . . . . . . . . . . 1108
ALSURFST . . . . . . . . . . . . . . . . . . . . . . . 1107
AMALGAM . . . . . . . . . . . . . . . . . . . . . . . . 724
API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
APIGROUP. . . . . . . . . . . . . . . . . . . . . . . . .909
APIVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1373
AQANCONL . . . . . . . . . . . . . . . . . . . . . . 1457
AQANTRC . . . . . . . . . . . . . . . . . . . . . . . . 1451
AQSTREAW . . . . . . . . . . . . . . . . . . . . . . 1450
AQUANCON . . . . . . . . . . . . . . . . . . . . . . 1455
AQUCHWAT . . . . . . . . . . . . . . . . . . . . . . 1442
AQUCON . . . . . . . . . . . . . . . . . . . . . . . . . 1461
AQUCT . . . . . . . . . . . . . . . . . . . . . . . . . . . 1452
AQUDIMS . . . . . . . . . . . . . . . . . . . . . . . . 1439
AQUFET . . . . . . . . . . . . . . . . . . . . . . . . . . 1444
AQUFETP . . . . . . . . . . . . . . . . . . . . . . . . .1448
AQUFLUX . . . . . . . . . . . . . . . . . . . . . . . . 1441
AQUNUM . . . . . . . . . . . . . . . . . . . . . . . . .1459
AQUTAB . . . . . . . . . . . . . . . . . . . . . . . . . 1454
2664
ASPFLRT . . . . . . . . . . . . . . . . . . . . . . . . . 1129
ASPHALTE . . . . . . . . . . . . . . . . . . . . . . . . 505
ASPLCRT . . . . . . . . . . . . . . . . . . . . . . . . . 1130
ASPP1P . . . . . . . . . . . . . . . . . . . . . . . . . . . 1125
ASPP2P . . . . . . . . . . . . . . . . . . . . . . . . . . . 1127
ASPPW2D . . . . . . . . . . . . . . . . . . . . . . . . 1128
ASPREWG . . . . . . . . . . . . . . . . . . . . . . . . 1126
ASPVISO . . . . . . . . . . . . . . . . . . . . . . . . . 1131
B
BDENSITY. . . . . . . . . . . . . . . . . . . . . . . .1046
BIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1196
BICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1198
BIGMODEL . . . . . . . . . . . . . . . . . . . . . . . . 562
BIOTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
BLACKOIL . . . . . . . . . . . . . . . . . . . . . . . . 450
BOX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 778
BRANPROP . . . . . . . . . . . . . . . . . . . . . . . 1712
BRINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
C
CALTRAC . . . . . . . . . . . . . . . . . . . . . . . . 1997
CALVAL . . . . . . . . . . . . . . . . . . . . . . . . . . 1339
CALVALR. . . . . . . . . . . . . . . . . . . . . . . . .1340
CARFIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713
CART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
CATYPE . . . . . . . . . . . . . . . . . . . . . . . . . . 1133
CBMOPTS . . . . . . . . . . . . . . . . . . . . . . . . . 575
CCTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . 1241
CCTYPES . . . . . . . . . . . . . . . . . . . . . . . . . 1242
CECON . . . . . . . . . . . . . . . . . . . . . . . . . . . 1668
CGDTYPE . . . . . . . . . . . . . . . . . . . . . . . . 1235
CGVTYPE . . . . . . . . . . . . . . . . . . . . . . . . 1236
CNAMES . . . . . . . . . . . . . . . . . . . . . . . . . 1150
CO2SOL . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
COAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
COALNUM . . . . . . . . . . . . . . . . . . . . . . . . 838
COARSEN . . . . . . . . . . . . . . . . . . . . . . . . . 725
CODTYPE . . . . . . . . . . . . . . . . . . . . . . . . 1237
COMPDAT . . . . . . . . . . . . . . . . . . . . . . . . 1499

COMPDATL. . . . . . . . . . . . . . . . . . . . . . .1502
COMPDATM . . . . . . . . . . . . . . . . . . . . . . 1505
COMPINJK . . . . . . . . . . . . . . . . . . . . . . . 1566
COMPLMPL . . . . . . . . . . . . . . . . . . . . . . 1562
COMPLUMP . . . . . . . . . . . . . . . . . . . . . . 1560
COMPMBIL . . . . . . . . . . . . . . . . . . . . . . . 1875
COMPMOBI . . . . . . . . . . . . . . . . . . . . . . 1874
COMPOFF . . . . . . . . . . . . . . . . . . . . . . . . 1727
COMPORD. . . . . . . . . . . . . . . . . . . . . . . .1564
COMPRP . . . . . . . . . . . . . . . . . . . . . . . . . . 1580
COMPS . . . . . . . . . . . . . . . . . . . . . . . . . . . 1148
COMPSEGL . . . . . . . . . . . . . . . . . . . . . . . 1559
COMPSEGS . . . . . . . . . . . . . . . . . . . . . . . 1556
COMPVD . . . . . . . . . . . . . . . . . . . . . . . . . 1163
COMPW . . . . . . . . . . . . . . . . . . . . . . . . . . 1149
COORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
COORDSYS . . . . . . . . . . . . . . . . . . . . . . . . 645
COPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
COPYBOX . . . . . . . . . . . . . . . . . . . . . . . . . 808
COPYREG . . . . . . . . . . . . . . . . . . . . . . . . . 809
COVTYPE . . . . . . . . . . . . . . . . . . . . . . . . 1238
CREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1283
CREFW . . . . . . . . . . . . . . . . . . . . . . . . . . . 1284
CSKIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1989
CVCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . 1767
CVTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . 1239
CVTYPES . . . . . . . . . . . . . . . . . . . . . . . . . 1240
D DRSDT . . . . . . . . . . . . . . . . . . . . . . . . . . . 1735
DATES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1748
DATUM . . . . . . . . . . . . . . . . . . . . . . . . . . . 1405
DATUMR . . . . . . . . . . . . . . . . . . . . . . . . . 1406
DATUMRX. . . . . . . . . . . . . . . . . . . . . . . .1407
DCQDEFN . . . . . . . . . . . . . . . . . . . . . . . . 1903
DELAYACT . . . . . . . . . . . . . . . . . . . . . . . 1837
DENSITY . . . . . . . . . . . . . . . . . . . . . . . . . . 907
DEPTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820
DETAILMF . . . . . . . . . . . . . . . . . . . . . . . . 1151
DETAILVD . . . . . . . . . . . . . . . . . . . . . . . . 1153
DGRDT . . . . . . . . . . . . . . . . . . . . . . . . . . . 1711
DIFFC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 912
DIFFCBM . . . . . . . . . . . . . . . . . . . . . . . . . 1123
DIFFCGAS . . . . . . . . . . . . . . . . . . . . . . . . 1217
DIFFCGO . . . . . . . . . . . . . . . . . . . . . . . . . 1219
19.1
DIFFCOAL . . . . . . . . . . . . . . . . . . . . . . . . 1116
DIFFCOG . . . . . . . . . . . . . . . . . . . . . . . . . 1220
DIFFCOIL. . . . . . . . . . . . . . . . . . . . . . . . .1218
DIFFMMF . . . . . . . . . . . . . . . . . . . . . . . . . . 733
DIFFMX . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
DIFFMX- . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
DIFFMY . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
DIFFMY- . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
DIFFMZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
DIFFMZ- . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
DIFFUSE . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
DIFFX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
DIFFY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
DIFFZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
DIMENS . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
DISGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
DNGL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1231
DOMAINS . . . . . . . . . . . . . . . . . . . . . . . . . 641
DPCDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
DPGRID . . . . . . . . . . . . . . . . . . . . . . . . . . . 677
DPNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676
DRAINAGE . . . . . . . . . . . . . . . . . . . . . . . 1008
DREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1279
DREFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1281
DREFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1280
DREFW . . . . . . . . . . . . . . . . . . . . . . . . . . . 1191
DREFWS . . . . . . . . . . . . . . . . . . . . . . . . . . 1192
DRILPRI . . . . . . . . . . . . . . . . . . . . . . . . . . 1934
DRVDT . . . . . . . . . . . . . . . . . . . . . . . . . . . 1740
DUALPERM . . . . . . . . . . . . . . . . . . . . . . . 524
DUALPORO. . . . . . . . . . . . . . . . . . . . . . . .523
DUMPFLUX . . . . . . . . . . . . . . . . . . . . . . . 639
DX / DY / DZ . . . . . . . . . . . . . . . . . . . . . . 584
DXV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
DYV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
DZMATRIX . . . . . . . . . . . . . . . . . . . . . . . . 689
DZMTRX . . . . . . . . . . . . . . . . . . . . . . . . . . 688
DZMTRXV . . . . . . . . . . . . . . . . . . . . . . . . . 690
DZNET . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
DZV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
E
ECHO / NOECHO . . . . . . . . . . . . . . . . . . 545
2665

EDIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 770
EDITNNC . . . . . . . . . . . . . . . . . . . . . . . . . . 654
EDITNNCR . . . . . . . . . . . . . . . . . . . . . . . . 656
EHYSTR . . . . . . . . . . . . . . . . . . . . . . . . . . 1003
EHYSTRR . . . . . . . . . . . . . . . . . . . . . . . . 1006
END . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
ENDACTIO / ENDACTION . . . . . . . . 1839
ENDBOX . . . . . . . . . . . . . . . . . . . . . . . . . . 779
ENDFIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
ENDNUM . . . . . . . . . . . . . . . . . . . . . . . . . . 840
ENDSCALE . . . . . . . . . . . . . . . . . . . . . . . . 579
ENDSKIP . . . . . . . . . . . . . . . . . . . . . . . . . 1933
ENKRVC . . . . . . . . . . . . . . . . . . . . . . . . . . 1212
ENKRVD . . . . . . . . . . . . . . . . . . . . . . . . . . . 972
ENKRVT . . . . . . . . . . . . . . . . . . . . . . . . . . 1332
ENPCVC . . . . . . . . . . . . . . . . . . . . . . . . . . 1214
ENPCVD . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
ENPCVT . . . . . . . . . . . . . . . . . . . . . . . . . . 1333
ENPTVC . . . . . . . . . . . . . . . . . . . . . . . . . . 1215
ENPTVD . . . . . . . . . . . . . . . . . . . . . . . . . . . 970
ENPTVT . . . . . . . . . . . . . . . . . . . . . . . . . . 1330
EOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1155
EOSNUM . . . . . . . . . . . . . . . . . . . . . . . . . . 843
EOSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1156
EPSCOMP . . . . . . . . . . . . . . . . . . . . . . . . 1211
EQLDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . 464
EQLDKVCR . . . . . . . . . . . . . . . . . . . . . . 1317
EQLDREAC . . . . . . . . . . . . . . . . . . . . . . . 1315
EQLNUM . . . . . . . . . . . . . . . . . . . . . . . . . . 831
EQLOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . 534
EQUALREG . . . . . . . . . . . . . . . . . . . . . . . . 810
EQUALS . . . . . . . . . . . . . . . . . . . . . . . . . . . 813
EQUIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1343
ESSNODE . . . . . . . . . . . . . . . . . . . . . . . . .1043
F GCONPRI . . . . . . . . . . . . . . . . . . . . . . . . . 1685
FACTLI . . . . . . . . . . . . . . . . . . . . . . . . . . . 1204
FAULTDIM. . . . . . . . . . . . . . . . . . . . . . . . .477
FAULTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
FBHPDEF . . . . . . . . . . . . . . . . . . . . . . . . . 1582
FIELD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
FIELDSEP . . . . . . . . . . . . . . . . . . . . . . . . 1380
FIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833
FIPNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . 832
19.1
FIPOWG . . . . . . . . . . . . . . . . . . . . . . . . . . . 835
FIPSEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1382
FLUXNUM . . . . . . . . . . . . . . . . . . . . . . . . . 841
FLUXREG / FLUXTYPE . . . . . . . . . . . . 640
FMTIN/ FMTSAVE . . . . . . . . . . . . . . . . . 567
FOAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
FOAMADS . . . . . . . . . . . . . . . . . . . . . . . . 1134
FOAMDCYO . . . . . . . . . . . . . . . . . . . . . . 1138
FOAMDCYW . . . . . . . . . . . . . . . . . . . . . 1137
FOAMMOB . . . . . . . . . . . . . . . . . . . . . . . 1139
FOAMMOBP . . . . . . . . . . . . . . . . . . . . . . 1140
FOAMMOBS . . . . . . . . . . . . . . . . . . . . . . 1141
FOAMOPTS . . . . . . . . . . . . . . . . . . . . . . . 1135
FOAMROCK . . . . . . . . . . . . . . . . . . . . . . 1136
FORMOPTS . . . . . . . . . . . . . . . . . . . . . . . . 536
FULLIMP . . . . . . . . . . . . . . . . . . . . . . . . . . 547
G
GADVANCE . . . . . . . . . . . . . . . . . . . . . . 1884
GAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
GASBEGIN . . . . . . . . . . . . . . . . . . . . . . . 1905
GASCCMP . . . . . . . . . . . . . . . . . . . . . . . . 1422
GASCONC . . . . . . . . . . . . . . . . . . . . . . . . 1420
GASEND . . . . . . . . . . . . . . . . . . . . . . . . . . 1907
GASFCOMP. . . . . . . . . . . . . . . . . . . . . . .1912
GASFDECR . . . . . . . . . . . . . . . . . . . . . . . 1911
GASFIELD . . . . . . . . . . . . . . . . . . . . . . . . . 539
GASFTARG . . . . . . . . . . . . . . . . . . . . . . . 1910
GASMONTH . . . . . . . . . . . . . . . . . . . . . . 1908
GASPERIO . . . . . . . . . . . . . . . . . . . . . . . . 1900
GASSATC . . . . . . . . . . . . . . . . . . . . . . . . . 1421
GASVISCF . . . . . . . . . . . . . . . . . . . . . . . . 1301
GASVISCT . . . . . . . . . . . . . . . . . . . . . . . . 1300
GASYEAR . . . . . . . . . . . . . . . . . . . . . . . . 1897
GCONINJE . . . . . . . . . . . . . . . . . . . . . . . . 1701
GCONPROD . . . . . . . . . . . . . . . . . . . . . . 1676
GCONSALE . . . . . . . . . . . . . . . . . . . . . . . 1886
GCONSUMP . . . . . . . . . . . . . . . . . . . . . . 1704
GCONTOL . . . . . . . . . . . . . . . . . . . . . . . . 1947
GCUTBACK . . . . . . . . . . . . . . . . . . . . . . 1625
GDCQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1895
GDCQECON . . . . . . . . . . . . . . . . . . . . . . 1904
GDFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
2666

GDRILPOT. . . . . . . . . . . . . . . . . . . . . . . .1940
GECON . . . . . . . . . . . . . . . . . . . . . . . . . . . 1742
GEFAC . . . . . . . . . . . . . . . . . . . . . . . . . . . 1674
GEODIMS . . . . . . . . . . . . . . . . . . . . . . . . . . 541
GEOMECH . . . . . . . . . . . . . . . . . . . . . . . . . 540
GINJGAS . . . . . . . . . . . . . . . . . . . . . . . . . 1882
GLIFTLIM . . . . . . . . . . . . . . . . . . . . . . . . 1954
GLIFTOPT . . . . . . . . . . . . . . . . . . . . . . . . 1955
GMDISBC . . . . . . . . . . . . . . . . . . . . . . . . 2000
GMPSTBC . . . . . . . . . . . . . . . . . . . . . . . . 2002
GNETDP . . . . . . . . . . . . . . . . . . . . . . . . . . 1720
GNETINJE . . . . . . . . . . . . . . . . . . . . . . . . 1722
GNETPUMP. . . . . . . . . . . . . . . . . . . . . . .1732
GPMAINT . . . . . . . . . . . . . . . . . . . . . . . . 1688
GPMAINT3 . . . . . . . . . . . . . . . . . . . . . . . 1691
GPTABLE . . . . . . . . . . . . . . . . . . . . . . . . . 1384
GPTABLE3 . . . . . . . . . . . . . . . . . . . . . . . . 1388
GPTABLEN . . . . . . . . . . . . . . . . . . . . . . . 1386
GPTDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . 470
GRAVDR . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
GRAVDRM . . . . . . . . . . . . . . . . . . . . . . . . . 527
GRAVITY . . . . . . . . . . . . . . . . . . . . . . . . . . 908
GRID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
GRIDFILE . . . . . . . . . . . . . . . . . . . . . . . . . . 727
GRIDOPTS . . . . . . . . . . . . . . . . . . . . . . . . . 535
GRIDUNIT . . . . . . . . . . . . . . . . . . . . . . . . . 672
GRUPFUEL . . . . . . . . . . . . . . . . . . . . . . . 1888
GRUPINJE . . . . . . . . . . . . . . . . . . . . . . . . 1607
GRUPLIM . . . . . . . . . . . . . . . . . . . . . . . . .1744
GRUPMAST . . . . . . . . . . . . . . . . . . . . . . 1985
GRUPNET . . . . . . . . . . . . . . . . . . . . . . . . 1733
GRUPPROD . . . . . . . . . . . . . . . . . . . . . . . 1968
GRUPRIG . . . . . . . . . . . . . . . . . . . . . . . . . 1943
GRUPSALE . . . . . . . . . . . . . . . . . . . . . . . 1885
GRUPSLAV . . . . . . . . . . . . . . . . . . . . . . . 1987
GRUPTARG . . . . . . . . . . . . . . . . . . . . . . . 1638
GRUPTREE . . . . . . . . . . . . . . . . . . . . . . . 1710
GSATCOMP . . . . . . . . . . . . . . . . . . . . . . . 1709
GSATINJE . . . . . . . . . . . . . . . . . . . . . . . . 1707
GSATPROD . . . . . . . . . . . . . . . . . . . . . . . 1705
GSEPCOND . . . . . . . . . . . . . . . . . . . . . . . 1817
GSWINGF . . . . . . . . . . . . . . . . . . . . . . . . 1893
GUIDERAT . . . . . . . . . . . . . . . . . . . . . . . 1680
19.1
H
H2SSOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
HEATCR . . . . . . . . . . . . . . . . . . . . . . . . . . 1253
HEATCRT . . . . . . . . . . . . . . . . . . . . . . . . . 1254
HEATDIMS . . . . . . . . . . . . . . . . . . . . . . . . 479
HEATER . . . . . . . . . . . . . . . . . . . . . . . . . . 1868
HEATERL . . . . . . . . . . . . . . . . . . . . . . . . . 1869
HEATTX . . . . . . . . . . . . . . . . . . . . . . . . . . . 708
HEATTY . . . . . . . . . . . . . . . . . . . . . . . . . . . 709
HEATTZ . . . . . . . . . . . . . . . . . . . . . . . . . . . 710
HEATVAP . . . . . . . . . . . . . . . . . . . . . . . . . 1257
HEATVAPE . . . . . . . . . . . . . . . . . . . . . . . 1258
HEATVAPS . . . . . . . . . . . . . . . . . . . . . . . 1326
HMMLCTAQ . . . . . . . . . . . . . . . . . . . . . . 1467
HMMLFTAQ . . . . . . . . . . . . . . . . . . . . . . 1468
HMMLTPX / HMMLTPY / HMMLTPZ /
HMMLTPXY . . . . . . . . . . . . . . . . 611
HMMROCKT. . . . . . . . . . . . . . . . . . . . . . .895
HMMULTX / HMMULTY / HMMULTZ /
HMMLTXY / HMMULTPV . . 612
HMMULTX- / HMMULTY- /
HMMULTZ- . . . . . . . . . . . . . . . . 614
HMRREF . . . . . . . . . . . . . . . . . . . . . . . . . . . 896
HWELLS . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
HXFIN / HYFIN / HZFIN . . . . . . . . . . . 723
I
IKRG, IKRGR, IKRW, IKRWR, IKRO,
IKRORW, IKRORG . . . . . . . . . 996
IMBNUM . . . . . . . . . . . . . . . . . . . . . . . . . . 828
IMBNUMMF . . . . . . . . . . . . . . . . . . . . . . . 848
IMPES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
IMPLICIT . . . . . . . . . . . . . . . . . . . . . . . . . . 522
IMPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
INCLUDE . . . . . . . . . . . . . . . . . . . . . . . . . . 519
INIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
IPCW, IPCG . . . . . . . . . . . . . . . . . . . . . . . . 999
ISGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
ISGL, ISGCR, ISGU, ISWL, ISWLPC,
ISWCR, ISWU, ISOGCR,
ISOWCR . . . . . . . . . . . . . . . . . . . 968
ISOLNUM . . . . . . . . . . . . . . . . . . . . . . . . . . 642
2667

J LSOWCR . . . . . . . . . . . . . . . . . . . . . . . . . . 986
JALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
JFUNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667
JFUNCR . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
K LTOSIGMA . . . . . . . . . . . . . . . . . . . . . . . . 680
KRG, KRGR . . . . . . . . . . . . . . . . . . . . . . . .995
KRNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
KRNUMMF . . . . . . . . . . . . . . . . . . . . . . . . 847
KRO, KRORW, KRORG. . . . . . . . . . . . .993
KRW, KRWR . . . . . . . . . . . . . . . . . . . . . . . 994
KVALUES . . . . . . . . . . . . . . . . . . . . . . . . . . 516
KVCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1245
KVCRS . . . . . . . . . . . . . . . . . . . . . . . . . . . 1247
KVTABLE . . . . . . . . . . . . . . . . . . . . . . . . 1170
KVTABTn . . . . . . . . . . . . . . . . . . . . . . . . . 1249
KVTEMP . . . . . . . . . . . . . . . . . . . . . . . . . 1248
KVWI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1252
L METRIC . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
LAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
LANGMEXT . . . . . . . . . . . . . . . . . . . . . . 1121
LANGMPL . . . . . . . . . . . . . . . . . . . . . . . . 1118
LANGMUIR . . . . . . . . . . . . . . . . . . . . . . . 1117
LANGMULT . . . . . . . . . . . . . . . . . . . . . . 1119
LBCCOEF . . . . . . . . . . . . . . . . . . . . . . . . .1201
LBCCOEFR . . . . . . . . . . . . . . . . . . . . . . . 1202
LGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
LGRCOPY . . . . . . . . . . . . . . . . . . . . . . . . . 560
LGRLOCK / LGRFREE . . . . . . . . . . . . 1766
LGROFF . . . . . . . . . . . . . . . . . . . . . . . . . . 1999
LGRON . . . . . . . . . . . . . . . . . . . . . . . . . . . 1998
LICENSES . . . . . . . . . . . . . . . . . . . . . . . . . 565
LIFTOPT . . . . . . . . . . . . . . . . . . . . . . . . . . 1953
LILIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1205
LKRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 990
LKRORG . . . . . . . . . . . . . . . . . . . . . . . . . . . 992
LKRORW . . . . . . . . . . . . . . . . . . . . . . . . . . 991
LKRW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988
LKRWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989
LOWSALT . . . . . . . . . . . . . . . . . . . . . . . . . 501
LPCW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 984
LSALTFNC . . . . . . . . . . . . . . . . . . . . . . . 1048
LSOGCR . . . . . . . . . . . . . . . . . . . . . . . . . . . 985
19.1
LSWCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 987
LSWL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 981
LSWLPC . . . . . . . . . . . . . . . . . . . . . . . . . . . 982
LSWU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983
LUMPDIMS . . . . . . . . . . . . . . . . . . . . . . . 1157
LUMPING . . . . . . . . . . . . . . . . . . . . . . . . 1158
LWSLTNUM / LSNUM . . . . . . . . . . . . . 827
LX / LY / LZ . . . . . . . . . . . . . . . . . . . . . . . 675
M
MAPAXES . . . . . . . . . . . . . . . . . . . . . . . . . 673
MAPUNITS . . . . . . . . . . . . . . . . . . . . . . . . 674
MATCORR . . . . . . . . . . . . . . . . . . . . . . . . 1759
MAXTRANZ . . . . . . . . . . . . . . . . . . . . . . . 651
MAXVALUE . . . . . . . . . . . . . . . . . . . . . . . 814
MEMORY . . . . . . . . . . . . . . . . . . . . . . . . . . 566
MESSAGE / MESSAGES / MSGFILE552
MIDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590
MINDZNET . . . . . . . . . . . . . . . . . . . . . . . . 628
MINPORV . . . . . . . . . . . . . . . . . . . . . . . . . . 626
MINPV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
MINPVV . . . . . . . . . . . . . . . . . . . . . . . . . . . 627
MINROCKV. . . . . . . . . . . . . . . . . . . . . . . .630
MINRV . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
MINVALUE . . . . . . . . . . . . . . . . . . . . . . . . 815
MISCEXP . . . . . . . . . . . . . . . . . . . . . . . . . 1025
MISCIBLE . . . . . . . . . . . . . . . . . . . . . . . . . 507
MISCNUM . . . . . . . . . . . . . . . . . . . . . . . . . 830
MISCSTR . . . . . . . . . . . . . . . . . . . . . . . . . 1022
MISCSTRP . . . . . . . . . . . . . . . . . . . . . . . . 1023
MISCSTRR. . . . . . . . . . . . . . . . . . . . . . . .1024
MLANG. . . . . . . . . . . . . . . . . . . . . . . . . . .1120
MONITOR/ NOMONITO . . . . . . . . . . . . 569
MSFN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1028
MULTFLT . . . . . . . . . . . . . . . . . . . . . . . . . . 635
MULTIN/ MULTSAVE . . . . . . . . . . . . . . 568
MULTIPLY . . . . . . . . . . . . . . . . . . . . . . . . . 801
MULTIREG . . . . . . . . . . . . . . . . . . . . . . . . 802
MULTMF . . . . . . . . . . . . . . . . . . . . . . . . . . 687
MULTNUM . . . . . . . . . . . . . . . . . . . . . . . . 845
MULTOUT . . . . . . . . . . . . . . . . . . . . . . . . . 443
2668

MULTOUTS . . . . . . . . . . . . . . . . . . . . . . . . 444
MULTPV . . . . . . . . . . . . . . . . . . . . . . . . . . . 621
MULTREGP . . . . . . . . . . . . . . . . . . . . . . . . 803
MULTREGT . . . . . . . . . . . . . . . . . . . . . . . . 691
MULTSIG . . . . . . . . . . . . . . . . . . . . . . . . . 1780
MULTSIGV . . . . . . . . . . . . . . . . . . . . . . . 1781
MULTX . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
MULTX- . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
MULTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
MULTY-. . . . . . . . . . . . . . . . . . . . . . . . . . . .605
MULTZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
MULTZ-. . . . . . . . . . . . . . . . . . . . . . . . . . . .609
MW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1184
MWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1186
MWW . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1187
MWWS . . . . . . . . . . . . . . . . . . . . . . . . . . . 1188
N PARACHOR . . . . . . . . . . . . . . . . . . . . . . . 1026
NCOMPS . . . . . . . . . . . . . . . . . . . . . . . . . 1230
NCONSUMP . . . . . . . . . . . . . . . . . . . . . . 1719
NEI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1169
NETBALAN. . . . . . . . . . . . . . . . . . . . . . .1760
NETCOMPA . . . . . . . . . . . . . . . . . . . . . . 1724
NETWORK . . . . . . . . . . . . . . . . . . . . . . . . .531
NEWTRAN . . . . . . . . . . . . . . . . . . . . . . . . .596
NEXTSTEP . . . . . . . . . . . . . . . . . . . . . . . 1752
NGASREM . . . . . . . . . . . . . . . . . . . . . . . . 1729
NNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
NNCGEN . . . . . . . . . . . . . . . . . . . . . . . . . . 658
NODEPROP . . . . . . . . . . . . . . . . . . . . . . . 1714
NODPCDT . . . . . . . . . . . . . . . . . . . . . . . . . 577
NODPPM . . . . . . . . . . . . . . . . . . . . . . . . . . 530
NOMIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
NONNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
NOSIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
NPROCX / NPROCKY . . . . . . . . . . . . . . 551
NSTACK . . . . . . . . . . . . . . . . . . . . . . . . . . 1765
NTG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
NUMRES . . . . . . . . . . . . . . . . . . . . . . . . . . 515
NUPCOL . . . . . . . . . . . . . . . . . . . . . . . . . . 1945
NWATREM. . . . . . . . . . . . . . . . . . . . . . . .1728
NXFIN / NYFIN / NZFIN . . . . . . . . . . . 722
19.1
O
OIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
OILAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . 1374
OILVINDX . . . . . . . . . . . . . . . . . . . . . . . . 1297
OILVISCC . . . . . . . . . . . . . . . . . . . . . . . . 1294
OILVISCT . . . . . . . . . . . . . . . . . . . . . . . . . 1292
OLDTRAN . . . . . . . . . . . . . . . . . . . . . . . . . 595
OMEGAA / OMEGAB . . . . . . . . . . . . . 1199
OMEGAAS / OMEGABS . . . . . . . . . . 1200
OPERATE . . . . . . . . . . . . . . . . . . . . . . . . . . 816
OPERATER . . . . . . . . . . . . . . . . . . . . . . . . 818
OPERNUM . . . . . . . . . . . . . . . . . . . . . . . . . 844
OPTIONS . . . . . . . . . . . . . . . . . . . . . . . . . 1958
OPTIONS3 . . . . . . . . . . . . . . . . . . . . . . . . 1961
OUTSOL . . . . . . . . . . . . . . . . . . . . . . . . . . 1356
OVERBURD . . . . . . . . . . . . . . . . . . . . . . . 906
P
PARALLEL / PARAOPTS . . . . . . . . . . . 550
PATHS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
PBUB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1398
PBVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1358
PCG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998
PCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1174
PCRITS . . . . . . . . . . . . . . . . . . . . . . . . . . . 1176
PCW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997
PDEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1404
PDVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1360
PEDERSEN . . . . . . . . . . . . . . . . . . . . . . . 1226
PEDTUNE . . . . . . . . . . . . . . . . . . . . . . . . 1227
PEDTUNER . . . . . . . . . . . . . . . . . . . . . . . 1229
PERMAVE . . . . . . . . . . . . . . . . . . . . . . . . . 632
PERMMF . . . . . . . . . . . . . . . . . . . . . . . . . . 598
PERMSTAB . . . . . . . . . . . . . . . . . . . . . . . . 897
PERMX / PERMY / PERMZ . . . . . . . . . 597
PETOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . 549
PICOND . . . . . . . . . . . . . . . . . . . . . . . . . . 1914
PIMTDIMS . . . . . . . . . . . . . . . . . . . . . . . . . 471
PIMULTAB . . . . . . . . . . . . . . . . . . . . . . . .1579
PINCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
PINCHNUM . . . . . . . . . . . . . . . . . . . . . . . . 666
PINCHOUT . . . . . . . . . . . . . . . . . . . . . . . . 663
PINCHREG. . . . . . . . . . . . . . . . . . . . . . . . .664
2669

PINCHXY . . . . . . . . . . . . . . . . . . . . . . . . . . 662
PLMIXNUM. . . . . . . . . . . . . . . . . . . . . . . .728
PLMIXPAR . . . . . . . . . . . . . . . . . . . . . . . 1094
PLYADS . . . . . . . . . . . . . . . . . . . . . . . . . . 1090
PLYADSS . . . . . . . . . . . . . . . . . . . . . . . . . 1091
PLYKRRF . . . . . . . . . . . . . . . . . . . . . . . . . 1096
PLYMAX . . . . . . . . . . . . . . . . . . . . . . . . . 1093
PLYROCK . . . . . . . . . . . . . . . . . . . . . . . . 1095
PLYSHEAR . . . . . . . . . . . . . . . . . . . . . . . 1097
PLYSHLOG . . . . . . . . . . . . . . . . . . . . . . . 1099
PLYVISC. . . . . . . . . . . . . . . . . . . . . . . . . .1089
PLYVISCS . . . . . . . . . . . . . . . . . . . . . . . . 1044
PLYVISCT . . . . . . . . . . . . . . . . . . . . . . . . 1102
PLYVSCST . . . . . . . . . . . . . . . . . . . . . . . . 1104
PMANUM . . . . . . . . . . . . . . . . . . . . . . . . . . 839
PMISC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1027
POISSONR . . . . . . . . . . . . . . . . . . . . . . . . . 743
POLYMER . . . . . . . . . . . . . . . . . . . . . . . . . 489
PORO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616
PORV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
PPCWMAX . . . . . . . . . . . . . . . . . . . . . . . 1002
PRCORR . . . . . . . . . . . . . . . . . . . . . . . . . . 1206
PREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1273
PREFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1275
PREFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1274
PREFW . . . . . . . . . . . . . . . . . . . . . . . . . . . 1189
PREFWS . . . . . . . . . . . . . . . . . . . . . . . . . . 1190
PRESSURE. . . . . . . . . . . . . . . . . . . . . . . .1363
PRIORITY . . . . . . . . . . . . . . . . . . . . . . . . 1695
PROPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854
PRORDER . . . . . . . . . . . . . . . . . . . . . . . . 1951
PRVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1365
PSEUPRES . . . . . . . . . . . . . . . . . . . . . . . . 1978
PSPLITX/ PSPLITY/ PSPLITZ . . . . . . . 570
PVCDO . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
PVCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 864
PVDG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
PVDO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
PVTG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 868
PVTNUM . . . . . . . . . . . . . . . . . . . . . . . . . . 823
PVTO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859
PVTW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 862
PVTWSALT . . . . . . . . . . . . . . . . . . . . . . . 1047
19.1
PVZG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 870
Q
QDRILL . . . . . . . . . . . . . . . . . . . . . . . . . . 1939
R
REACACT . . . . . . . . . . . . . . . . . . . . . . . . 1303
REACCORD . . . . . . . . . . . . . . . . . . . . . . 1304
REACENTH . . . . . . . . . . . . . . . . . . . . . . . 1314
REACLIMS . . . . . . . . . . . . . . . . . . . . . . . 1305
REACPHA . . . . . . . . . . . . . . . . . . . . . . . . 1311
REACPORD . . . . . . . . . . . . . . . . . . . . . . . 1308
REACRATE . . . . . . . . . . . . . . . . . . . . . . . 1302
REACSORD . . . . . . . . . . . . . . . . . . . . . . . 1313
REACTION . . . . . . . . . . . . . . . . . . . . . . . . 493
RECOVERY . . . . . . . . . . . . . . . . . . . . . . . 1390
REFINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716
REGDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . 466
REGIONS . . . . . . . . . . . . . . . . . . . . . . . . . . 822
RESORB . . . . . . . . . . . . . . . . . . . . . . . . . . 1124
RESTART . . . . . . . . . . . . . . . . . . . . . . . . . 1346
RESVNUM . . . . . . . . . . . . . . . . . . . . . . . . . 644
RKTRMDIR . . . . . . . . . . . . . . . . . . . . . . . . 884
ROCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 882
ROCKCOMP . . . . . . . . . . . . . . . . . . . . . . . 472
ROCKCON . . . . . . . . . . . . . . . . . . . . . . . . . 694
ROCKDEN . . . . . . . . . . . . . . . . . . . . . . . . . 729
ROCKDIMS . . . . . . . . . . . . . . . . . . . . . . . . 474
ROCKNUM . . . . . . . . . . . . . . . . . . . . . . . . 837
ROCKOPTS . . . . . . . . . . . . . . . . . . . . . . . . 904
ROCKPAMA . . . . . . . . . . . . . . . . . . . . . . . 887
ROCKPROP . . . . . . . . . . . . . . . . . . . . . . . . 693
ROCKTAB . . . . . . . . . . . . . . . . . . . . . . . . . 889
ROCKTABH . . . . . . . . . . . . . . . . . . . . . . . . 891
ROCKTSIG. . . . . . . . . . . . . . . . . . . . . . . . .885
ROCKV . . . . . . . . . . . . . . . . . . . . . . . . . . . 1334
ROMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1428
RPTGRID/ RPTGRIDL . . . . . . . . . . . . . . 741
RPTHMD/ RPTHMG/ RPTHMW . . . . 571
RPTISOL/ RPTPROPS/ RPTREGS/
RPTRUNSP/ RPTSCHED/
RPTSMRY/ RPTSOL . . . . . . . . 572
RPTONLY . . . . . . . . . . . . . . . . . . . . . . . . . 1485
RPTONLYO . . . . . . . . . . . . . . . . . . . . . . . 1486
2670

RPTRST . . . . . . . . . . . . . . . . . . . . . . . . . . 1351
RS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1400
RSCONST . . . . . . . . . . . . . . . . . . . . . . . . . . 876
RSCONSTT . . . . . . . . . . . . . . . . . . . . . . . . 877
RSVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1357
RSW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1425
RSWVD . . . . . . . . . . . . . . . . . . . . . . . . . . . 1233
RTEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . 1159
RTEMPA . . . . . . . . . . . . . . . . . . . . . . . . . . 1395
RTEMPVD . . . . . . . . . . . . . . . . . . . . . . . . 1396
RUNSPEC . . . . . . . . . . . . . . . . . . . . . . . . . . 409
RV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1402
RVCONST . . . . . . . . . . . . . . . . . . . . . . . . . 879
RVCONSTT . . . . . . . . . . . . . . . . . . . . . . . . 880
RVVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1359
S
SALT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1415
SALTNODE . . . . . . . . . . . . . . . . . . . . . . . 1041
SALTVD . . . . . . . . . . . . . . . . . . . . . . . . . . 1416
SATNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . 824
SATOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . 513
SCALECRS . . . . . . . . . . . . . . . . . . . . . . . . 958
SCALELIM. . . . . . . . . . . . . . . . . . . . . . . . .969
SCDATAB . . . . . . . . . . . . . . . . . . . . . . . . . 1975
SCDPDIMS. . . . . . . . . . . . . . . . . . . . . . . . .559
SCDPTAB . . . . . . . . . . . . . . . . . . . . . . . . . 1973
SCDPTRAC . . . . . . . . . . . . . . . . . . . . . . . 1974
SCHEDULE . . . . . . . . . . . . . . . . . . . . . . . 1490
SCREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1268
SDENSITY . . . . . . . . . . . . . . . . . . . . . . . . 1030
SDREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1266
SEPARATE / RUNSUM . . . . . . . . . . . . 1487
SEPCOND . . . . . . . . . . . . . . . . . . . . . . . . 1818
SEPVALS . . . . . . . . . . . . . . . . . . . . . . . . . 1815
SFOAM . . . . . . . . . . . . . . . . . . . . . . . . . . . 1426
SGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1368
SGCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963
SGCWMIS . . . . . . . . . . . . . . . . . . . . . . . . 1031
SGFN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 942
SGL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 961
SGOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 917
SGU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 967
SGWFN . . . . . . . . . . . . . . . . . . . . . . . . . . . . 946
19.1
SHRATE . . . . . . . . . . . . . . . . . . . . . . . . . . 1101
SIGMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
SIGMAGD . . . . . . . . . . . . . . . . . . . . . . . . . 681
SIGMAGDV . . . . . . . . . . . . . . . . . . . . . . . . 683
SIGMATH . . . . . . . . . . . . . . . . . . . . . . . . . . 686
SIGMAV . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
SKIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1925
SKIP100 . . . . . . . . . . . . . . . . . . . . . . . . . . 1927
SKIP300 . . . . . . . . . . . . . . . . . . . . . . . . . . 1928
SKIPREST . . . . . . . . . . . . . . . . . . . . . . . . 1926
SKIPSTAB . . . . . . . . . . . . . . . . . . . . . . . . . 564
SKRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1087
SKRORW . . . . . . . . . . . . . . . . . . . . . . . . . 1088
SKRW . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1085
SKRWR . . . . . . . . . . . . . . . . . . . . . . . . . . . 1086
SLAVES . . . . . . . . . . . . . . . . . . . . . . . . . . 1984
SLGOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 936
SMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1375
SOCRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1071
SOF2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938
SOF3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 944
SOGCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 965
SOIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1370
SOILR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1427
SOLID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
SOLIDADS . . . . . . . . . . . . . . . . . . . . . . . . 1146
SOLIDMMC . . . . . . . . . . . . . . . . . . . . . . . 1144
SOLIDMMS . . . . . . . . . . . . . . . . . . . . . . . 1145
SOLUBILI . . . . . . . . . . . . . . . . . . . . . . . . 1232
SOLUTION . . . . . . . . . . . . . . . . . . . . . . . 1342
SOLVDIRS . . . . . . . . . . . . . . . . . . . . . . . . . 643
SOMGAS . . . . . . . . . . . . . . . . . . . . . . . . . . 950
SOMWAT . . . . . . . . . . . . . . . . . . . . . . . . . . 948
SOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1142
SOROPTS . . . . . . . . . . . . . . . . . . . . . . . . . 1143
SORWMIS . . . . . . . . . . . . . . . . . . . . . . . . 1032
SOWCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 964
SPECGRID . . . . . . . . . . . . . . . . . . . . . . . . . 711
SPECHA . . . . . . . . . . . . . . . . . . . . . . . . . . 1318
SPECHB . . . . . . . . . . . . . . . . . . . . . . . . . . 1319
SPECHEAT. . . . . . . . . . . . . . . . . . . . . . . .1338
SPECHG . . . . . . . . . . . . . . . . . . . . . . . . . . 1322
SPECHH . . . . . . . . . . . . . . . . . . . . . . . . . . 1323
2671

SPECHS . . . . . . . . . . . . . . . . . . . . . . . . . . 1327
SPECHT . . . . . . . . . . . . . . . . . . . . . . . . . . 1328
SPECROCK . . . . . . . . . . . . . . . . . . . . . . . 1337
SPOLY . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1419
SPREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1267
SSHIFT . . . . . . . . . . . . . . . . . . . . . . . . . . . 1207
SSHIFTS . . . . . . . . . . . . . . . . . . . . . . . . . . 1208
SSOLID . . . . . . . . . . . . . . . . . . . . . . . . . . . 1372
SSOWCR . . . . . . . . . . . . . . . . . . . . . . . . . 1084
SSWCR . . . . . . . . . . . . . . . . . . . . . . . . . . . 1082
SSWL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1081
SSWU . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1083
START . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
STCOND . . . . . . . . . . . . . . . . . . . . . . . . . . 1160
STHERMX1 . . . . . . . . . . . . . . . . . . . . . . . 1264
STOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1034
STONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 955
STONE1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 953
STONE2 . . . . . . . . . . . . . . . . . . . . . . . . . . . 954
STONEPAR . . . . . . . . . . . . . . . . . . . . . . . . 956
STOPROD . . . . . . . . . . . . . . . . . . . . . . . . 1309
STOREAC . . . . . . . . . . . . . . . . . . . . . . . . 1310
STOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035
STREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1269
STVP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1112
SUMMARY . . . . . . . . . . . . . . . . . . . . . . . 1469
SURF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1418
SURFACT . . . . . . . . . . . . . . . . . . . . . . . . . . 487
SURFACTW . . . . . . . . . . . . . . . . . . . . . . . . 488
SURFADDW . . . . . . . . . . . . . . . . . . . . . . 1077
SURFADS . . . . . . . . . . . . . . . . . . . . . . . . . 1072
SURFCAPD . . . . . . . . . . . . . . . . . . . . . . . 1075
SURFNUM . . . . . . . . . . . . . . . . . . . . . . . . . 825
SURFROCK . . . . . . . . . . . . . . . . . . . . . . . 1076
SURFST . . . . . . . . . . . . . . . . . . . . . . . . . . 1073
SURFSTES . . . . . . . . . . . . . . . . . . . . . . . . 1079
SURFVISC . . . . . . . . . . . . . . . . . . . . . . . . 1074
SURFWNUM . . . . . . . . . . . . . . . . . . . . . . . 826
SWAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1366
SWATINIT . . . . . . . . . . . . . . . . . . . . . . . . 1000
SWCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 962
SWFN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 940
SWINGFAC . . . . . . . . . . . . . . . . . . . . . . . 1891
19.1
SWL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 959
SWLPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 960
SWOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914
SWU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 966
T
TABDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . 462
TBLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1408
TCBDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . 485
TCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1171
TCRITS . . . . . . . . . . . . . . . . . . . . . . . . . . . 1173
TEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502
TEMPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1394
TEMPNODE . . . . . . . . . . . . . . . . . . . . . . 1106
TEMPVD . . . . . . . . . . . . . . . . . . . . . . . . . 1329
THANALB . . . . . . . . . . . . . . . . . . . . . . . . 1244
THCGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . 698
THCOIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
THCONMF . . . . . . . . . . . . . . . . . . . . . . . . . 685
THCONR . . . . . . . . . . . . . . . . . . . . . . . . . 1259
THCONSF . . . . . . . . . . . . . . . . . . . . . . . . 1260
THCROCK . . . . . . . . . . . . . . . . . . . . . . . . . 706
THCSOLID . . . . . . . . . . . . . . . . . . . . . . . . . 704
THCWATER . . . . . . . . . . . . . . . . . . . . . . . . 702
THERMAL . . . . . . . . . . . . . . . . . . . . . . . . . 492
THERMEX1 . . . . . . . . . . . . . . . . . . . . . . . 1270
THPRES . . . . . . . . . . . . . . . . . . . . . . . . . . 1361
THPRESFT . . . . . . . . . . . . . . . . . . . . . . . . . 637
THSVC . . . . . . . . . . . . . . . . . . . . . . . . . . . 1335
THWVC . . . . . . . . . . . . . . . . . . . . . . . . . . 1336
TIGHTENP / TSCRIT . . . . . . . . . . . . . . 1763
TITLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
TLMIXPAR . . . . . . . . . . . . . . . . . . . . . . . 1033
TNUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1410
TOLCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . 952
TOPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
TRACER . . . . . . . . . . . . . . . . . . . . . . . . . . 1050
TRACERS . . . . . . . . . . . . . . . . . . . . . . . . . . 486
TRACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
TRACKREG . . . . . . . . . . . . . . . . . . . . . . . . 853
TRADS . . . . . . . . . . . . . . . . . . . . . . . . . . . 1059
TRANGE . . . . . . . . . . . . . . . . . . . . . . . . . . 1972
TRANX . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
TRANY . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
2672

TRANZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
TRDCY . . . . . . . . . . . . . . . . . . . . . . . . . . . 1058
TREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1276
TREFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1278
TREFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1277
TRROCK . . . . . . . . . . . . . . . . . . . . . . . . . . . 898
TSTEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1751
TUNING / TUNINGDP / TUNINGL /
TUNINGS . . . . . . . . . . . . . . . . . 1762
TVDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1412
TZONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 957
U WBHGLR . . . . . . . . . . . . . . . . . . . . . . . . . 1627
UDADIMS . . . . . . . . . . . . . . . . . . . . . . . . . 483
UDQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1840
UDQDIMS . . . . . . . . . . . . . . . . . . . . . . . . . 480
UDQPARAM . . . . . . . . . . . . . . . . . . . . . . . 482
UDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1846
UDTDIMS . . . . . . . . . . . . . . . . . . . . . . . . . . 484
UNIFIN/ UNIFSAVE . . . . . . . . . . . . . . . . 573
UNIFOUT . . . . . . . . . . . . . . . . . . . . . . . . . . 441
UNIFOUTS . . . . . . . . . . . . . . . . . . . . . . . . . 442
USEFLUX . . . . . . . . . . . . . . . . . . . . . . . . . . 638
V WDRILRES . . . . . . . . . . . . . . . . . . . . . . . 1941
VAPOIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
VAPPARS . . . . . . . . . . . . . . . . . . . . . . . . . 1736
VCOMPACT . . . . . . . . . . . . . . . . . . . . . . 1203
VCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1177
VCRITS . . . . . . . . . . . . . . . . . . . . . . . . . . . 1179
VCRITVIS . . . . . . . . . . . . . . . . . . . . . . . . 1180
VDKRG . . . . . . . . . . . . . . . . . . . . . . . . . . . 1221
VDKRGC . . . . . . . . . . . . . . . . . . . . . . . . . 1223
VDKRO . . . . . . . . . . . . . . . . . . . . . . . . . . . 1224
VELDEP . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
VFPCHECK . . . . . . . . . . . . . . . . . . . . . . . 1648
VFPCHK . . . . . . . . . . . . . . . . . . . . . . . . . . 1647
VFPIDIMS . . . . . . . . . . . . . . . . . . . . . . . . . 468
VFPINJ . . . . . . . . . . . . . . . . . . . . . . . . . . . 1640
VFPPDIMS . . . . . . . . . . . . . . . . . . . . . . . . . 469
VFPPROD . . . . . . . . . . . . . . . . . . . . . . . . .1643
VFPTABL . . . . . . . . . . . . . . . . . . . . . . . . . 1649
VISCD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
VISCREF . . . . . . . . . . . . . . . . . . . . . . . . . 1290
19.1
VREFW . . . . . . . . . . . . . . . . . . . . . . . . . . . 1282
W
WAGHALT . . . . . . . . . . . . . . . . . . . . . . . . 1115
WAGHYSTR . . . . . . . . . . . . . . . . . . . . . . 1113
WALKALIN . . . . . . . . . . . . . . . . . . . . . . . 1860
WARN / NOWARN / NOWARNEP . . . 553
WATDENT . . . . . . . . . . . . . . . . . . . . . . . . 1243
WATER . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
WATERTAB . . . . . . . . . . . . . . . . . . . . . . . 1161
WATVISCT. . . . . . . . . . . . . . . . . . . . . . . .1291
WAVAILIM . . . . . . . . . . . . . . . . . . . . . . . . 1890
WCONHIST . . . . . . . . . . . . . . . . . . . . . . . 1589
WCONINJ . . . . . . . . . . . . . . . . . . . . . . . . .1596
WCONINJE . . . . . . . . . . . . . . . . . . . . . . . 1592
WCONINJH . . . . . . . . . . . . . . . . . . . . . . . 1600
WCONINJP . . . . . . . . . . . . . . . . . . . . . . . 1598
WCONPROD . . . . . . . . . . . . . . . . . . . . . . 1585
WCUTBACK . . . . . . . . . . . . . . . . . . . . . . 1620
WCYCLE . . . . . . . . . . . . . . . . . . . . . . . . . 1610
WDFAC . . . . . . . . . . . . . . . . . . . . . . . . . . . 1854
WDFACCOR . . . . . . . . . . . . . . . . . . . . . . 1855
WDRILPRI . . . . . . . . . . . . . . . . . . . . . . . . 1936
WDRILTIM . . . . . . . . . . . . . . . . . . . . . . . 1938
WECON . . . . . . . . . . . . . . . . . . . . . . . . . . 1657
WECONCMF . . . . . . . . . . . . . . . . . . . . . . 1665
WECONINJ . . . . . . . . . . . . . . . . . . . . . . . 1670
WEFAC . . . . . . . . . . . . . . . . . . . . . . . . . . . 1673
WELCNTL . . . . . . . . . . . . . . . . . . . . . . . . 1636
WELDRAW . . . . . . . . . . . . . . . . . . . . . . . 1745
WELLCOMP . . . . . . . . . . . . . . . . . . . . . . 1970
WELLDIMS . . . . . . . . . . . . . . . . . . . . . . . . 475
WELLGR . . . . . . . . . . . . . . . . . . . . . . . . . 1982
WELLINJE . . . . . . . . . . . . . . . . . . . . . . . . 1603
WELLLIM . . . . . . . . . . . . . . . . . . . . . . . . 1667
WELLOPEN. . . . . . . . . . . . . . . . . . . . . . .1758
WELLOPTS . . . . . . . . . . . . . . . . . . . . . . . 1946
WELLPROD . . . . . . . . . . . . . . . . . . . . . . 1965
WELLSHUT. . . . . . . . . . . . . . . . . . . . . . .1753
WELLSPEC . . . . . . . . . . . . . . . . . . . . . . . 1498
WELLSTRE . . . . . . . . . . . . . . . . . . . . . . . 1872
WELLSTRW . . . . . . . . . . . . . . . . . . . . . . 1873
2673

WELLTARG . . . . . . . . . . . . . . . . . . . . . . . 1635
WELLTCB . . . . . . . . . . . . . . . . . . . . . . . . 1655
WELLTCBT . . . . . . . . . . . . . . . . . . . . . . . 1656
WELLWAG . . . . . . . . . . . . . . . . . . . . . . . 1612
WELOPEN . . . . . . . . . . . . . . . . . . . . . . . . 1754
WELOPENL. . . . . . . . . . . . . . . . . . . . . . .1756
WELPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1639
WELPRI . . . . . . . . . . . . . . . . . . . . . . . . . . 1697
WELSEGS . . . . . . . . . . . . . . . . . . . . . . . . 1513
WELSOMIN. . . . . . . . . . . . . . . . . . . . . . .1491
WELSPECL . . . . . . . . . . . . . . . . . . . . . . . 1495
WELSPECS . . . . . . . . . . . . . . . . . . . . . . . 1492
WELTARG . . . . . . . . . . . . . . . . . . . . . . . . 1632
WFOAM . . . . . . . . . . . . . . . . . . . . . . . . . . 1990
WFRICSEG / WFRICSGL . . . . . . . . . . 1554
WFRICTN . . . . . . . . . . . . . . . . . . . . . . . . . 1549
WFRICTNL . . . . . . . . . . . . . . . . . . . . . . . 1552
WGASPROD . . . . . . . . . . . . . . . . . . . . . . 1909
WGORPEN. . . . . . . . . . . . . . . . . . . . . . . .1666
WGRUPCON . . . . . . . . . . . . . . . . . . . . . . 1699
WH2NUM . . . . . . . . . . . . . . . . . . . . . . . . . . 849
WH3NUM . . . . . . . . . . . . . . . . . . . . . . . . . . 850
WHISTCTL . . . . . . . . . . . . . . . . . . . . . . . 1619
WHTEMP . . . . . . . . . . . . . . . . . . . . . . . . . 1864
WI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1285
WINJGAS . . . . . . . . . . . . . . . . . . . . . . . . . 1880
WINJMIX . . . . . . . . . . . . . . . . . . . . . . . . . 1876
WINJMULT . . . . . . . . . . . . . . . . . . . . . . . 1583
WINJORD . . . . . . . . . . . . . . . . . . . . . . . . .1878
WINJTEMP . . . . . . . . . . . . . . . . . . . . . . . 1865
WINJW . . . . . . . . . . . . . . . . . . . . . . . . . . . 1867
WINJWAT . . . . . . . . . . . . . . . . . . . . . . . . . 1866
WLIFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1948
WLIFTOPT . . . . . . . . . . . . . . . . . . . . . . . . 1956
WLIMTOL . . . . . . . . . . . . . . . . . . . . . . . . 1814
WLIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1568
WLISTDYN . . . . . . . . . . . . . . . . . . . . . . . 1570
WMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1429
WMFVD . . . . . . . . . . . . . . . . . . . . . . . . . . 1286
WNAMES . . . . . . . . . . . . . . . . . . . . . . . . . 1287
WNETDP . . . . . . . . . . . . . . . . . . . . . . . . . 1964
WORKLIM . . . . . . . . . . . . . . . . . . . . . . . . 1942
WORKTHP. . . . . . . . . . . . . . . . . . . . . . . .1675
19.1
WPAVE . . . . . . . . . . . . . . . . . . . . . . . . . . . 1916
WPAVEDEP . . . . . . . . . . . . . . . . . . . . . . . 1921
WPIMULT . . . . . . . . . . . . . . . . . . . . . . . . 1572
WPIMULTL . . . . . . . . . . . . . . . . . . . . . . . 1575
WPITAB . . . . . . . . . . . . . . . . . . . . . . . . . . 1578
WPOLYMER . . . . . . . . . . . . . . . . . . . . . . 1861
WREGROUP . . . . . . . . . . . . . . . . . . . . . . 1683
WRFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1922
WRFTPLT . . . . . . . . . . . . . . . . . . . . . . . . . 1923
WSALT . . . . . . . . . . . . . . . . . . . . . . . . . . . 1862
WSCTAB . . . . . . . . . . . . . . . . . . . . . . . . . 1976
WSEGAICD . . . . . . . . . . . . . . . . . . . . . . . 1524
WSEGDFPA . . . . . . . . . . . . . . . . . . . . . . . 1541
WSEGDIMS . . . . . . . . . . . . . . . . . . . . . . . . 478
WSEGEXSS . . . . . . . . . . . . . . . . . . . . . . . 1534
WSEGFLIM . . . . . . . . . . . . . . . . . . . . . . . 1536
WSEGFMOD . . . . . . . . . . . . . . . . . . . . . . 1538
WSEGINIT . . . . . . . . . . . . . . . . . . . . . . . . 1517
WSEGITER . . . . . . . . . . . . . . . . . . . . . . . 1761
WSEGLINK . . . . . . . . . . . . . . . . . . . . . . . 1518
WSEGPULL . . . . . . . . . . . . . . . . . . . . . . . 1546
WSEGSEP . . . . . . . . . . . . . . . . . . . . . . . . 1544
WSEGSICD . . . . . . . . . . . . . . . . . . . . . . . 1528
WSEGTABL . . . . . . . . . . . . . . . . . . . . . . . 1520
WSEGVALV. . . . . . . . . . . . . . . . . . . . . . .1522
WSEPCOND . . . . . . . . . . . . . . . . . . . . . . 1820
WSURFACT . . . . . . . . . . . . . . . . . . . . . . . 1859
WTADD . . . . . . . . . . . . . . . . . . . . . . . . . . 1631
WTAKEGAS . . . . . . . . . . . . . . . . . . . . . . 1889
WTEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . 1863
WTEST . . . . . . . . . . . . . . . . . . . . . . . . . . . 1870
WTMULT . . . . . . . . . . . . . . . . . . . . . . . . . 1629
WTRACER . . . . . . . . . . . . . . . . . . . . . . . . 1858
WVFPDP . . . . . . . . . . . . . . . . . . . . . . . . . . 1913
WVFPEXP . . . . . . . . . . . . . . . . . . . . . . . . 1650
X
XMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1376
XMFVP . . . . . . . . . . . . . . . . . . . . . . . . . . . 1165
Y
YMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1377
YMFVP . . . . . . . . . . . . . . . . . . . . . . . . . . . 1166
YOUNGMOD . . . . . . . . . . . . . . . . . . . . . . 742
2674
 19.1

Z ZFACTOR . . . . . . . . . . . . . . . . . . . . . . . . . 1288
ZCORN . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592 ZI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1162
ZCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1181 ZIPPY2 . . . . . . . . . . . . . . . . . . . . . . . . . . . 1764
ZCRITS . . . . . . . . . . . . . . . . . . . . . . . . . . . 1182 ZMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1378
ZCRITVIS . . . . . . . . . . . . . . . . . . . . . . . . . 1183 ZMFVD . . . . . . . . . . . . . . . . . . . . . . . . . . . 1167
ZFACT1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 1289

2675
16. Keyword definitions index formats IM, ST, GE
A BVISC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2177
AC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2198
ADGCSTC . . . . . . . . . . . . . . . . . . . . . . . . 2281
ADGMAXC . . . . . . . . . . . . . . . . . . . . . . . 2280
ALTER . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2360
ALTER-HIST . . . . . . . . . . . . . . . . . . . . . . 2361
ALTERCP . . . . . . . . . . . . . . . . . . . . . . . . . 2401
API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2304
APIGRAD . . . . . . . . . . . . . . . . . . . . . . . . . 2125
APIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2305
AQFUNC . . . . . . . . . . . . . . . . . . . . . . . . . 2040
AQLEAK . . . . . . . . . . . . . . . . . . . . . . . . . 2035
AQMETHOD . . . . . . . . . . . . . . . . . . . . . . 2036
AQPROP . . . . . . . . . . . . . . . . . . . . . . . . . . 2038
AQUEOUS-DENSITY . . . . . . . . . . . . . 2121
AQUIFER . . . . . . . . . . . . . . . . . . . . . . . . . 2039
AQVISC . . . . . . . . . . . . . . . . . . . . . . . . . . 2037
AVG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2183
AVISC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2176
B CPRPOR . . . . . . . . . . . . . . . . . . . . . . . . . . 2046
BG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2011
BHPDEPTH . . . . . . . . . . . . . . . . . . . . . . . 2332
BIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2196
BKRGCW . . . . . . . . . . . . . . . . . . . . . . . . . 2248
BKROCW . . . . . . . . . . . . . . . . . . . . . . . . . 2250
BKRWIRO . . . . . . . . . . . . . . . . . . . . . . . . 2246
BLOCKGROUP . . . . . . . . . . . . . . . . . . . 2024
BOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2190
BOTAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . 2127
BPCGMAX. . . . . . . . . . . . . . . . . . . . . . . .2252
BPCWMAX . . . . . . . . . . . . . . . . . . . . . . . 2254
BSGCON . . . . . . . . . . . . . . . . . . . . . . . . . . 2236
BSGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2238
BSOIRG . . . . . . . . . . . . . . . . . . . . . . . . . . 2240
BSOIRW . . . . . . . . . . . . . . . . . . . . . . . . . . 2234
BSORG . . . . . . . . . . . . . . . . . . . . . . . . . . . 2244
BSORW . . . . . . . . . . . . . . . . . . . . . . . . . . . 2242
BSWCRIT . . . . . . . . . . . . . . . . . . . . . . . . . 2232
BSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2230
BVG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2184
2676
BWI / CW / REFPW / CVW / VWI . 2131
C
CCPOR . . . . . . . . . . . . . . . . . . . . . . . . . . . 2047
CMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2185
CO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2189
COAL-DIF-COMP . . . . . . . . . . . . . . . . . 2282
COAL-DIF-TIME . . . . . . . . . . . . . . . . . . 2283
COMPNAME . . . . . . . . . . . . . . . . . . . . . . 2134
CON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2008
CONC_SLD . . . . . . . . . . . . . . . . . . . . . . . 2308
COORD . . . . . . . . . . . . . . . . . . . . . . . . . . . 2023
CORNERS . . . . . . . . . . . . . . . . . . . . . . . . 2042
COT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2188
CP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2141
CPG1 / CPG2 / CPG3 / CPG4 . . . . . . . 2153
CPL1 / CPL2 / CPL3 / CPL4 . . . . . . . . 2152
CPOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2081
CPORPD . . . . . . . . . . . . . . . . . . . . . . . . . . 2099
CPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2144
CPTPOR . . . . . . . . . . . . . . . . . . . . . . . . . . 2084
CRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2112
CROCKTAB . . . . . . . . . . . . . . . . . . . . . . . 2048
CROCKTABH . . . . . . . . . . . . . . . . . . . . . 2049
CROCKTYPE . . . . . . . . . . . . . . . . . . . . . 2045
CT1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2142
CT2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2143
CTPOR . . . . . . . . . . . . . . . . . . . . . . . . . . . 2083
CTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2044
CVO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2191
D
DAMP-PCOW-TROIL . . . . . . . . . . . . . . 2278
DATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2324
DATUMDEPTH . . . . . . . . . . . . . . . . . . . 2291
DENSITY . . . . . . . . . . . . . . . . . . . . . . . . . 2120
DENSTR-MIX . . . . . . . . . . . . . . . . . . . . . 2379
DEPLETION . . . . . . . . . . . . . . . . . . . . . . 2053
DEPTH . . . . . . . . . . . . . . . . . . . . . . . . . . . 2062

DGOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2298
DI / DJ / DK . . . . . . . . . . . . . . . . . . . . . . . 2021
DIFFUSION . . . . . . . . . . . . . . . . . . . . . . . 2210
DIFLIB. . . . . . . . . . . . . . . . . . . . . . . . . . . .2117
DIFRAC / DJFRAC / DKFRAC . . . . . 2027
DILATION . . . . . . . . . . . . . . . . . . . . . . . . 2102
DRILLQ . . . . . . . . . . . . . . . . . . . . . . . . . . 2351
DTOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2063
DUALPERM . . . . . . . . . . . . . . . . . . . . . . 2041
DUALPOR . . . . . . . . . . . . . . . . . . . . . . . . 2025
DWOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2297
E HVR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2155
EACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2161
EACT_TAB . . . . . . . . . . . . . . . . . . . . . . . 2162
EGUST / BGUST / ZGUST . . . . . . . . . 2119
EOSSET . . . . . . . . . . . . . . . . . . . . . . . . . . 2194
EOSTYPE . . . . . . . . . . . . . . . . . . . . . . . . . 2195
EPSPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2255
EPSPCG . . . . . . . . . . . . . . . . . . . . . . . . . . 2256
EQUALSI . . . . . . . . . . . . . . . . . . . . . . . . . 2013
EV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2156
F
FILENAMES . . . . . . . . . . . . . . . . . . . . . . 2018
FORMINFRAC . . . . . . . . . . . . . . . . . . . . 2059
FRACTURE . . . . . . . . . . . . . . . . . . . . . . . 2007
FREQFAC . . . . . . . . . . . . . . . . . . . . . . . . . 2159
FREQFACP . . . . . . . . . . . . . . . . . . . . . . . 2160
FRFRAC . . . . . . . . . . . . . . . . . . . . . . . . . . 2058
FZ / NFZ . . . . . . . . . . . . . . . . . . . . . . . . . . 2012
G
GASD-ZCOEF . . . . . . . . . . . . . . . . . . . . . 2186
GASLIQKV . . . . . . . . . . . . . . . . . . . . . . . 2187
GASZONE . . . . . . . . . . . . . . . . . . . . . . . . 2292
GCONI . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2373
GCONM . . . . . . . . . . . . . . . . . . . . . . . . . . 2376
GCONP . . . . . . . . . . . . . . . . . . . . . . . . . . . 2371
GEOMETRY . . . . . . . . . . . . . . . . . . . . . . 2333
GLCONTROL . . . . . . . . . . . . . . . . . . . . . 2391
GLIFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2389
GLOPT . . . . . . . . . . . . . . . . . . . . . . . . . . . 2390
GPRODGROUP . . . . . . . . . . . . . . . . . . . 2375
GRAVITY . . . . . . . . . . . . . . . . . . . . . . . . . 2123
19.1
GRID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2020
GROUP . . . . . . . . . . . . . . . . . . . . . . . . . . . 2326
H
HCFLAG . . . . . . . . . . . . . . . . . . . . . . . . . . 2110
HEATR . . . . . . . . . . . . . . . . . . . . . . . . . . . 2395
HLOSSPROP . . . . . . . . . . . . . . . . . . . . . . 2098
HLOSST . . . . . . . . . . . . . . . . . . . . . . . . . . 2096
HLOSSTDIFF . . . . . . . . . . . . . . . . . . . . . 2097
HTWELL / HTWRATE / HTWRATEPL /
HTWTEMP / HTWI . . . . . . . . 2400
HVAPR . . . . . . . . . . . . . . . . . . . . . . . . . . . 2154
HYS_KRG . . . . . . . . . . . . . . . . . . . . . . . . 2271
HYS_KRO . . . . . . . . . . . . . . . . . . . . . . . . 2268
HYS_LEVEL . . . . . . . . . . . . . . . . . . . . . . 2275
HYS_PCOG . . . . . . . . . . . . . . . . . . . . . . . 2274
HYS_PCOW. . . . . . . . . . . . . . . . . . . . . . .2273
HYSKRG . . . . . . . . . . . . . . . . . . . . . . . . . 2264
HYSKRO . . . . . . . . . . . . . . . . . . . . . . . . . 2259
HYSKROG . . . . . . . . . . . . . . . . . . . . . . . . 2267
HYSKROW . . . . . . . . . . . . . . . . . . . . . . . 2265
HYSKRW . . . . . . . . . . . . . . . . . . . . . . . . . 2262
I
IDEALGAS . . . . . . . . . . . . . . . . . . . . . . . 2193
IJK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2010
INCLUDE . . . . . . . . . . . . . . . . . . . . . . . . . 2019
INCOMP . . . . . . . . . . . . . . . . . . . . . . . . . . 2209
INITIAL . . . . . . . . . . . . . . . . . . . . . . . . . . 2284
INITREGION . . . . . . . . . . . . . . . . . . . . . . 2293
INJECTOR . . . . . . . . . . . . . . . . . . . . . . . . 2331
INTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . 2294
INUNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . 2015
ISECTOR / SECTORNAMES . . . . . . . 2061
ISOTHERMAL . . . . . . . . . . . . . . . . . . . . 2317
IVAR / JVAR / KVAR . . . . . . . . . . . . . . 2009
J
JFUNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2222
K
K_SURF . . . . . . . . . . . . . . . . . . . . . . . . . . 2104
KRGCW . . . . . . . . . . . . . . . . . . . . . . . . . . 2247
KROCW . . . . . . . . . . . . . . . . . . . . . . . . . . 2249
2677

KROGCG . . . . . . . . . . . . . . . . . . . . . . . . . 2215
KROIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2214
KRPERF . . . . . . . . . . . . . . . . . . . . . . . . . . 2344
KRTEMTAB . . . . . . . . . . . . . . . . . . . . . . . 2227
KRTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . 2226
KRWIRO . . . . . . . . . . . . . . . . . . . . . . . . . . 2245
KV1 / KV2 / KV3 / KV4 / KV5 . . . . . 2151
KVTABLE . . . . . . . . . . . . . . . . . . . . . . . . 2150
KVTABLIM . . . . . . . . . . . . . . . . . . . . . . . 2149
L PINJW . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2399
LAYER-CTRL . . . . . . . . . . . . . . . . . . . . . 2392
LAYERXYZ . . . . . . . . . . . . . . . . . . . . . . . 2342
M
MASSDEN . . . . . . . . . . . . . . . . . . . . . . . . 2140
MATRIX . . . . . . . . . . . . . . . . . . . . . . . . . . 2006
MAXTEMP . . . . . . . . . . . . . . . . . . . . . . . 2319
MFRAC_GAS . . . . . . . . . . . . . . . . . . . . . 2310
MFRAC_OIL . . . . . . . . . . . . . . . . . . . . . . 2309
MINTEMP . . . . . . . . . . . . . . . . . . . . . . . . 2318
MIXVC . . . . . . . . . . . . . . . . . . . . . . . . . . . 2175
MODEL . . . . . . . . . . . . . . . . . . . . . . . . . . . 2107
MODELSHUT . . . . . . . . . . . . . . . . . . . . . 2352
MOLDEN . . . . . . . . . . . . . . . . . . . . . . . . . 2139
MOLVOL . . . . . . . . . . . . . . . . . . . . . . . . . 2106
MONITOR . . . . . . . . . . . . . . . . . . . . . . . . 2363
N PTUBE1 . . . . . . . . . . . . . . . . . . . . . . . . . . 2383
NC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2109
NETGROSS . . . . . . . . . . . . . . . . . . . . . . . 2031
NETPAY . . . . . . . . . . . . . . . . . . . . . . . . . . 2034
NULL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2028
NUMERICAL . . . . . . . . . . . . . . . . . . . . . 2315
O PVTCOND . . . . . . . . . . . . . . . . . . . . . . . . 2115
O2PP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2169
OMEGA / OMEGB . . . . . . . . . . . . . . . . 2199
ON-TIME . . . . . . . . . . . . . . . . . . . . . . . . . 2354
OPERATE . . . . . . . . . . . . . . . . . . . . . . . . . 2355
OPERATE-HIST . . . . . . . . . . . . . . . . . . . 2358
P REFDEPTH . . . . . . . . . . . . . . . . . . . . . . . 2296
PADSORP . . . . . . . . . . . . . . . . . . . . . . . . . 2204
PB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2290
19.1
PBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2311
PCGEND . . . . . . . . . . . . . . . . . . . . . . . . . . 2251
PCHOR . . . . . . . . . . . . . . . . . . . . . . . . . . . 2197
PCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2145
PCWEND . . . . . . . . . . . . . . . . . . . . . . . . . 2253
PERF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2335
PERFV . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2339
PERMI / PERMJ / PERMK . . . . . . . . . 2030
PHWELLBORE . . . . . . . . . . . . . . . . . . . 2387
PINCHOUTARRAY . . . . . . . . . . . . . . . . 2032
PLANT-TABLE . . . . . . . . . . . . . . . . . . . . 2381
PLNRFRAC . . . . . . . . . . . . . . . . . . . . . . . 2071
PLNRFRAC_TEMPLATE . . . . . . . . . . 2068
PMIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2206
POR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2029
PORFORM . . . . . . . . . . . . . . . . . . . . . . . . 2101
PORMAX . . . . . . . . . . . . . . . . . . . . . . . . . 2100
PPERM . . . . . . . . . . . . . . . . . . . . . . . . . . . 2205
PREFCONC . . . . . . . . . . . . . . . . . . . . . . . 2207
PRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2306
PRODUCER . . . . . . . . . . . . . . . . . . . . . . . 2330
PRPOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2079
PRSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2135
PSURF . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2137
PTHRESHI / PTHRESHJ / PTHRESHK
2279
PTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2133
PVC3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2111
PVCUTOFF . . . . . . . . . . . . . . . . . . . . . . . 2064
PVISC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2208
PVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2113
PVTAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . 2124
PWELLBORE . . . . . . . . . . . . . . . . . . . . . 2386
Q
QUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2398
R
REFINE . . . . . . . . . . . . . . . . . . . . . . . . . . . 2065
REFPRES . . . . . . . . . . . . . . . . . . . . . . . . . 2295
2678

RELAX . . . . . . . . . . . . . . . . . . . . . . . . . . . 2320
RENTH . . . . . . . . . . . . . . . . . . . . . . . . . . . 2163
RESDATE . . . . . . . . . . . . . . . . . . . . . . . . . 2017
RESTART . . . . . . . . . . . . . . . . . . . . . . . . . 2016
RHOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2132
ROCKCP . . . . . . . . . . . . . . . . . . . . . . . . . . 2078
ROCKFLUID . . . . . . . . . . . . . . . . . . . . . . 2212
ROCKTYPE . . . . . . . . . . . . . . . . . . . . . . . 2075
RORDER . . . . . . . . . . . . . . . . . . . . . . . . . . 2164
RPHASE . . . . . . . . . . . . . . . . . . . . . . . . . . 2165
RPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2213
RTEMLOWR . . . . . . . . . . . . . . . . . . . . . . 2167
RTEMUPR . . . . . . . . . . . . . . . . . . . . . . . . 2166
RTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2225
RUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2322
RXCRITCON . . . . . . . . . . . . . . . . . . . . . . 2168
RXEQBAK . . . . . . . . . . . . . . . . . . . . . . . . 2093
RXEQBASE . . . . . . . . . . . . . . . . . . . . . . . 2095
RXEQFOR . . . . . . . . . . . . . . . . . . . . . . . . 2091
S TEMR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2136
SALINITY . . . . . . . . . . . . . . . . . . . . . . . . 2122
SAT_ADJUST . . . . . . . . . . . . . . . . . . . . . 2303
SCONNECT . . . . . . . . . . . . . . . . . . . . . . . 2067
SECTORARRAY . . . . . . . . . . . . . . . . . . 2060
SEPARATOR . . . . . . . . . . . . . . . . . . . . . . 2312
SETPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2346
SG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2301
SGCON . . . . . . . . . . . . . . . . . . . . . . . . . . . 2235
SGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2237
SGT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2220
SHAPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2026
SHUTIN / OPEN . . . . . . . . . . . . . . . . . . 2349
SLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2218
SO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2300
SOIRG . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2239
SOIRW . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2233
SOLID_CP . . . . . . . . . . . . . . . . . . . . . . . . 2148
SOLID_DEN . . . . . . . . . . . . . . . . . . . . . . 2147
SOLVER / PNTHRDS . . . . . . . . . . . . . . 2321
SONEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . 2289
SORG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2243
SORM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2276
SORMAX . . . . . . . . . . . . . . . . . . . . . . . . . 2261
19.1
SORW . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2241
SRFTNG . . . . . . . . . . . . . . . . . . . . . . . . . . 2224
SRFTNW . . . . . . . . . . . . . . . . . . . . . . . . . . 2223
STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2323
STOPROD . . . . . . . . . . . . . . . . . . . . . . . . 2158
STOREAC . . . . . . . . . . . . . . . . . . . . . . . . 2157
SURFLASH . . . . . . . . . . . . . . . . . . . . . . . 2105
SW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2302
SWCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . 2231
SWINIT . . . . . . . . . . . . . . . . . . . . . . . . . . . 2287
SWNEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . 2288
SWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2229
SWT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2216
SWTI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2257
T
TARGET . . . . . . . . . . . . . . . . . . . . . . . . . . 2365
TCRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2146
TEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2307
TFORM . . . . . . . . . . . . . . . . . . . . . . . . . . . 2316
THCONG . . . . . . . . . . . . . . . . . . . . . . . . . 2088
THCONMIX. . . . . . . . . . . . . . . . . . . . . . .2090
THCONO . . . . . . . . . . . . . . . . . . . . . . . . . 2087
THCONR . . . . . . . . . . . . . . . . . . . . . . . . . 2085
THCONS . . . . . . . . . . . . . . . . . . . . . . . . . . 2089
THCONW . . . . . . . . . . . . . . . . . . . . . . . . . 2086
THTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . 2077
TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2325
TINJW . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2397
TITLE1 / TITLE2 / TITLE3 . . . . . . . . 2014
TMPSET . . . . . . . . . . . . . . . . . . . . . . . . . . 2394
TRANLI / TRANLJ / TRANLK . . . . . 2055
TRANSF . . . . . . . . . . . . . . . . . . . . . . . . . . 2057
TRANSI / TRANSJ / TRANSK . . . . . 2054
TRANSMULT . . . . . . . . . . . . . . . . . . . . . 2056
TREFVS . . . . . . . . . . . . . . . . . . . . . . . . . . 2202
TRIGGER . . . . . . . . . . . . . . . . . . . . . . . . . 2402
TSURF . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2138
U
UHTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2396
USER_INPUT . . . . . . . . . . . . . . . . . . . . . 2286
2679

V VSMIXFUNC . . . . . . . . . . . . . . . . . . . . . 2182
VAMOD . . . . . . . . . . . . . . . . . . . . . . . . . . 2072
VATYPE . . . . . . . . . . . . . . . . . . . . . . . . . . 2074
VERTICAL . . . . . . . . . . . . . . . . . . . . . . . . 2285
VGUST . . . . . . . . . . . . . . . . . . . . . . . . . . . 2203
VISCOEFF . . . . . . . . . . . . . . . . . . . . . . . . 2174
VISCOR . . . . . . . . . . . . . . . . . . . . . . . . . . 2172
VISCTABLE . . . . . . . . . . . . . . . . . . . . . . 2178
VISCTYPE . . . . . . . . . . . . . . . . . . . . . . . . 2171
VISVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2173
VOLMOD . . . . . . . . . . . . . . . . . . . . . . . . . 2033
VOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2192
VOTAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . 2129
VSHIF1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 2201
VSHIFT . . . . . . . . . . . . . . . . . . . . . . . . . . . 2200
VSMIXCOMP . . . . . . . . . . . . . . . . . . . . . 2180
VSMIXENDP . . . . . . . . . . . . . . . . . . . . . 2181
19.1
VSTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . 2170
W
WELGEO . . . . . . . . . . . . . . . . . . . . . . . . . 2348
WELL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2329
WELSEP . . . . . . . . . . . . . . . . . . . . . . . . . . 2378
WLISTSHUT / WELISTOPEN . . . . . . 2350
WOC_SW . . . . . . . . . . . . . . . . . . . . . . . . . 2299
WTINCR . . . . . . . . . . . . . . . . . . . . . . . . . . 2367
WTMULT . . . . . . . . . . . . . . . . . . . . . . . . . 2369
X
XFLOW-MODEL . . . . . . . . . . . . . . . . . . 2353
Z
ZCORN . . . . . . . . . . . . . . . . . . . . . . . . . . . 2022
2680
17. Keyword definitions index format tN

A ENPCTRC . . . . . . . . . . . . . . . . . . . . . . . . . . 977
ACTIONC . . . . . . . . . . . . . . . . . . . . . . . . . 1849 ENPCTRCM . . . . . . . . . . . . . . . . . . . . . . . . 980
AIMCTRL . . . . . . . . . . . . . . . . . . . . . . . . . . 429 ENPKTRC . . . . . . . . . . . . . . . . . . . . . . . . . . 976
APILIM . . . . . . . . . . . . . . . . . . . . . . . . . . . 1980 ENPKTRCM. . . . . . . . . . . . . . . . . . . . . . . .979
AQUGP . . . . . . . . . . . . . . . . . . . . . . . . . . . 1464 ENPTRC . . . . . . . . . . . . . . . . . . . . . . . . . . . 974
AQUOPTS . . . . . . . . . . . . . . . . . . . . . . . . 1446 ENPTRCM . . . . . . . . . . . . . . . . . . . . . . . . . 978
ARITHMETIC . . . . . . . . . . . . . . . . . . . . . . 771
ARR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 780 F
AUTOSAVE . . . . . . . . . . . . . . . . . . . . . . . 1981 FIPPATT . . . . . . . . . . . . . . . . . . . . . . . . . . . 836
FLASHCTRL . . . . . . . . . . . . . . . . . . . . . . . 430
B FLOWFNAMES . . . . . . . . . . . . . . . . . . . 1068
BG_xxx . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712 FLOWFTAB . . . . . . . . . . . . . . . . . . . . . . . 1069
BLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787 FLOWFUNC . . . . . . . . . . . . . . . . . . . . . . 1065
FRACTURE_ARITHMETIC . . . . . . . . . 764
C FRACTURE_PATH . . . . . . . . . . . . . . . . . 749
CARFINBG . . . . . . . . . . . . . . . . . . . . . . . . 715 FRACTURE_PLANE . . . . . . . . . . . . . . . . 751
COHESION . . . . . . . . . . . . . . . . . . . . . . . . 902 FRACTURE_STAGE . . . . . . . . . . . . . . . 1801
COMPDATMD . . . . . . . . . . . . . . . . . . . . 1508 FRACTURE_TEMPLATE . . . . . . . . . . . 752
COMPENSATION . . . . . . . . . . . . . . . . . 1741 FRACTURE_WELL . . . . . . . . . . . . . . . . . 762
COMPFRAC . . . . . . . . . . . . . . . . . . . . . . 1802
COMPFRACL . . . . . . . . . . . . . . . . . . . . . 1805 G
COMPVAL . . . . . . . . . . . . . . . . . . . . . . . . 1962 GECONX . . . . . . . . . . . . . . . . . . . . . . . . . 1663
COMPVALL . . . . . . . . . . . . . . . . . . . . . . . 1963 GWRATMUL . . . . . . . . . . . . . . . . . . . . . . 1979
COREYGO . . . . . . . . . . . . . . . . . . . . . . . . . 921
COREYGOMOD . . . . . . . . . . . . . . . . . . . . 926 H
COREYWG . . . . . . . . . . . . . . . . . . . . . . . . 923 HEATTCR. . . . . . . . . . . . . . . . . . . . . . . . .1255
COREYWO . . . . . . . . . . . . . . . . . . . . . . . . 919 HYSTKRW / HYSTKROW / HYSTKRG
COREYWOMOD . . . . . . . . . . . . . . . . . . . 925 / HYSTKROG . . . . . . . . . . . . . 1009
CORNERS . . . . . . . . . . . . . . . . . . . . . . . . . 745 HYSTKRWR / HYSTKROWR /
CYLINDER . . . . . . . . . . . . . . . . . . . . . . . . 789 HYSTKRGR / HYSTKROGR
1012
D HYSTOPTS . . . . . . . . . . . . . . . . . . . . . . . 1019
DEACDEPT . . . . . . . . . . . . . . . . . . . . . . . . 748 HYSTOPTSR . . . . . . . . . . . . . . . . . . . . . . 1021
DEFINES . . . . . . . . . . . . . . . . . . . . . . . . . . . 451 HYSTPCW / HYSTPCG . . . . . . . . . . . . 1015
DENSTRMIX . . . . . . . . . . . . . . . . . . . . . 1391 HYSTPCWR / HYSTPCGR. . . . . . . . .1017
DRSDTVP . . . . . . . . . . . . . . . . . . . . . . . . 1738
DRSDTVPE . . . . . . . . . . . . . . . . . . . . . . . 1739 I
IF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784
E IF-THEN-ELSE-ENDIF . . . . . . . . . . . . . 785
ECDATES . . . . . . . . . . . . . . . . . . . . . . . . . . 556 IMPORT_NETWORK . . . . . . . . . . . . . . . 438
ECINIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555 IMPORT_PROJECT . . . . . . . . . . . . . . . . . 439
ECVAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557 IMPORT_WELL . . . . . . . . . . . . . . . . . . . . 437

2681
 19.1

INNERWIDTH . . . . . . . . . . . . . . . . . . . . . 719 ROCKCONT . . . . . . . . . . . . . . . . . . . . . . . 696

INTERPOLATE . . . . . . . . . . . . . . . . . . . . . 792 ROCKSALT . . . . . . . . . . . . . . . . . . . . . . . 1414
ROCKSTRE . . . . . . . . . . . . . . . . . . . . . . . . 901
J ROCKT . . . . . . . . . . . . . . . . . . . . . . . . . . . 1261
JFPERM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671 RPTMAPD/RPTGRAPHD . . . . . . . . . . 1433
RPTMAPL/RPTGRAPHL . . . . . . . . . . 1437
K
RPTMAPS . . . . . . . . . . . . . . . . . . . . . . . . 1423
KRSMOOTH . . . . . . . . . . . . . . . . . . . . . . 1036
RPTMAPT/RPTGRAPHT . . . . . . . . . . 1435
KVTABLIM . . . . . . . . . . . . . . . . . . . . . . . 1250
RPTRSTD . . . . . . . . . . . . . . . . . . . . . . . . . 1430
L RPTRSTL . . . . . . . . . . . . . . . . . . . . . . . . . 1432
LANGUAGE . . . . . . . . . . . . . . . . . . . . . . . 449 RPTRSTT . . . . . . . . . . . . . . . . . . . . . . . . . 1431
LETGO . . . . . . . . . . . . . . . . . . . . . . . . . . . . 930 RUNCTRL . . . . . . . . . . . . . . . . . . . . . . . . 1768
LETWG . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933
LETWO . . . . . . . . . . . . . . . . . . . . . . . . . . . . 927 S
LINEAR_ISOPERM . . . . . . . . . . . . . . . 1037 SALTPROP . . . . . . . . . . . . . . . . . . . . . . . . 1039
SALTTRM . . . . . . . . . . . . . . . . . . . . . . . . 1040
M SEPDEN . . . . . . . . . . . . . . . . . . . . . . . . . . 1392
MINPVR . . . . . . . . . . . . . . . . . . . . . . . . . . . 629 SKIPOFF . . . . . . . . . . . . . . . . . . . . . . . . . . 1930
SKIPON . . . . . . . . . . . . . . . . . . . . . . . . . . . 1932
N SKIPTNAV . . . . . . . . . . . . . . . . . . . . . . . . 1929
NEFLASH . . . . . . . . . . . . . . . . . . . . . . . . . . 432 SPECHC . . . . . . . . . . . . . . . . . . . . . . . . . . 1320
NETCHOKE. . . . . . . . . . . . . . . . . . . . . . .1717 SPECHD . . . . . . . . . . . . . . . . . . . . . . . . . . 1321
NFLOWFTB. . . . . . . . . . . . . . . . . . . . . . .1067 SPECHI . . . . . . . . . . . . . . . . . . . . . . . . . . . 1324
NOILREM . . . . . . . . . . . . . . . . . . . . . . . . 1731 SPECHJ . . . . . . . . . . . . . . . . . . . . . . . . . . . 1325
NPROPANTS . . . . . . . . . . . . . . . . . . . . . . 1061 SRSALT . . . . . . . . . . . . . . . . . . . . . . . . . . 1417
STANDG . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
O
STANDO . . . . . . . . . . . . . . . . . . . . . . . . . . . 874
OILVINDT . . . . . . . . . . . . . . . . . . . . . . . . 1298
STHERMX2 . . . . . . . . . . . . . . . . . . . . . . . 1265
OPEN_BASE_MODEL . . . . . . . . . . . . . . 460
STORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 790
OVPG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 872
SURFDW . . . . . . . . . . . . . . . . . . . . . . . . . 1078
P SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . 791
PHASEID . . . . . . . . . . . . . . . . . . . . . . . . . . 434
PREDEFINES . . . . . . . . . . . . . . . . . . . . . . 459 T
PROPANTNAMES . . . . . . . . . . . . . . . . . 1062 TEMPR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
PROPANTTABLE . . . . . . . . . . . . . . . . . 1063 TFORM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
PVTGEN . . . . . . . . . . . . . . . . . . . . . . . . . . . 574 THCONMIX. . . . . . . . . . . . . . . . . . . . . . .1263
PVTOPTS . . . . . . . . . . . . . . . . . . . . . . . . . . 910 THERMEX2 . . . . . . . . . . . . . . . . . . . . . . . 1271
THERMEX3 . . . . . . . . . . . . . . . . . . . . . . . 1272
R THETA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903
REACCONC . . . . . . . . . . . . . . . . . . . . . . 1307 TNAVCTRL . . . . . . . . . . . . . . . . . . . . . . . . 420
REPORTFILE / REPORTSCREEN . . . 411 TRACERM . . . . . . . . . . . . . . . . . . . . . . . . 1051
RESTARTDATE . . . . . . . . . . . . . . . . . . . 1349 TRACEROPTS . . . . . . . . . . . . . . . . . . . . 1052
RFD_WFRAC . . . . . . . . . . . . . . . . . . . . . . 542 TREFVS . . . . . . . . . . . . . . . . . . . . . . . . . . 1210
ROCKAXES . . . . . . . . . . . . . . . . . . . . . . . . 900 TRMMULTC . . . . . . . . . . . . . . . . . . . . . . 1054

2682

TRMMULTT . . . . . . . . . . . . . . . . . . . . . . 1056
TRMTEMP . . . . . . . . . . . . . . . . . . . . . . . . 1057
V WFRACL . . . . . . . . . . . . . . . . . . . . . . . . . 1785
VDEF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
VFPCORR . . . . . . . . . . . . . . . . . . . . . . . . 1652
VISCNUM . . . . . . . . . . . . . . . . . . . . . . . . . 842
VISGRID . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
VSHIF1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 1209
W WPIFUNC. . . . . . . . . . . . . . . . . . . . . . . . .1808
WBHZONE . . . . . . . . . . . . . . . . . . . . . . . 1812
WCUTBACKX . . . . . . . . . . . . . . . . . . . . 1623
WDFACCORL . . . . . . . . . . . . . . . . . . . . . 1857
WECONINJX . . . . . . . . . . . . . . . . . . . . . 1671
WECONX . . . . . . . . . . . . . . . . . . . . . . . . . 1661
WELLBRANCH . . . . . . . . . . . . . . . . . . . 1994
WELLDATA . . . . . . . . . . . . . . . . . . . . . . . 1992
19.1
WELLINCL . . . . . . . . . . . . . . . . . . . . . . . 1991
WELLTRACK . . . . . . . . . . . . . . . . . . . . . 1506
WFRAC . . . . . . . . . . . . . . . . . . . . . . . . . . . 1782
WFRACP . . . . . . . . . . . . . . . . . . . . . . . . . 1788
WFRACPL . . . . . . . . . . . . . . . . . . . . . . . . 1797
WFRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2604
WLOGCALC . . . . . . . . . . . . . . . . . . . . . . 2004
WORK/IWORK . . . . . . . . . . . . . . . . . . . . . 783
WSEGCNTL . . . . . . . . . . . . . . . . . . . . . . 1977
WSKFUNC . . . . . . . . . . . . . . . . . . . . . . . . 1810
WTEMPDEF . . . . . . . . . . . . . . . . . . . . . . 1397
WWAG . . . . . . . . . . . . . . . . . . . . . . . . . . . 1614
Z
ZONES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851
2683
18. Keyword definitions index format MO
A E
ACTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2482
ALQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2618
AQCD . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2486
AQCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2556
AQCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2557
AQFE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2560
AQUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2559
AQUW . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2561
AQWO . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2562
ARRAy. . . . . . . . . . . . . . . . . . . . . . . . . . . .2652
B ETUNe . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2423
BASIc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2430
BHP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2617
BHPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2622
BRANch . . . . . . . . . . . . . . . . . . . . . . . . . . 2656
C
CIJK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2650
CNAMe . . . . . . . . . . . . . . . . . . . . . . . . . . . 2414
COMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2655
CONS (GRID) . . . . . . . . . . . . . . . . . . . . . 2487
CONS (INIT) . . . . . . . . . . . . . . . . . . . . . . 2547
COORd . . . . . . . . . . . . . . . . . . . . . . . . . . . 2483
CROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2480
CWAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2641
D FPVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2494
DATE / READ / TIME . . . . . . . . . . . . . 2633
DATUm . . . . . . . . . . . . . . . . . . . . . . . . . . . 2471
DEFI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2488
DELTa . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2654
DEPTh / ZGRI . . . . . . . . . . . . . . . . . . . . . 2474
DPORo . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2418
DPSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2489
DRAW . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2635
DREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2620
DWPW . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2421
DZMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2496
2684
EFILe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2566
EFORm . . . . . . . . . . . . . . . . . . . . . . . . . . . 2582
ENDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2576
ENDH . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2581
ENDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2577
EPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2419
EPSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2420
EQUA . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2441
EQUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2546
EQUI / EQLN . . . . . . . . . . . . . . . . . . . . . 2497
ETAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2570
EUNIts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2586
F
F(DE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2443
F(PO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2498
FAUL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2499
FCRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2501
FEQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2504
FIPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2484
FKPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2493
FKX / FKY / FKZ . . . . . . . . . . . . . . . . . 2502
FLOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2614
FLUId . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2428
FMLX / FMLY / FMLZ . . . . . . . . . . . . 2503
FMUL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2500
FPOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2505
FREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2506
FREQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2653
FSAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2490
FSWA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2491
FSWL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2492
G
GGIT / GWIT . . . . . . . . . . . . . . . . . . . . . 2631
GGRT / GWRT . . . . . . . . . . . . . . . . . . . . 2640
GLIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2648
GOCX . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2549

GOCY . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2550
GOPT / GGPT / GWPT / GLPT . . . . . 2630
GPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2424
GPVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2433
GRID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2467
GROU . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2634
GVRT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2644
GVVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2456
H MPGP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2425
HFILe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2578
HFORm . . . . . . . . . . . . . . . . . . . . . . . . . . . 2584
HOIL / HGAS / HWAT / HLIQ / HBHP /
HTHP / HWEF . . . . . . . . . . . . . 2610
HORI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2469
HOURS . . . . . . . . . . . . . . . . . . . . . . . . . . . 2632
HTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2580
HUNIts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2587
I O
IDATe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2412
IEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2507
ILIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2647
IMPLicit . . . . . . . . . . . . . . . . . . . . . . . . . . 2415
INCLude . . . . . . . . . . . . . . . . . . . . . . . . . . 2416
INIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2545
INJE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2593
INPUt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2408
INTE (FLUID) . . . . . . . . . . . . . . . . . . . . . 2444
INTE (GRID) . . . . . . . . . . . . . . . . . . . . . . 2508
K P
K_X / K_Y / K_Z (KX / KY / KZ,
PERMX / PERMY / PERMZ)
2479
KMOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2642
KPTA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2510
KRGO . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2465
KRWO . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2464
KVPX / KVPY / KVPZ . . . . . . . . . . . . 2439
KVSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2438
L PRINt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2410
LAYE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2511
LEVJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2512
19.1
LGRD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2513
LIFT . . . . . . . . . . . . . . . . . . . . . . . . 2599, 2626
LTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2594
M
MAKE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2638
MINDznet . . . . . . . . . . . . . . . . . . . . . . . . . 2514
MINPv . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2477
MODI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2515
MULX / MULY / MULZ (MX / MY /
MZ, M_X / M_Y / M_Z, M-X /
M-Y / M-Z, MULTX / MULTY /
MULTZ) . . . . . . . . . . . . . . . . . . . 2517
N
NNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2525
NTG / NTOG . . . . . . . . . . . . . . . . . . . . . . 2526
OIT / GIT / WIT . . . . . . . . . . . . . . . . . . . 2625
OMGA . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2435
OMGB . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2436
OPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2422
OPEN (RECU) . . . . . . . . . . . . . . . . . . . . . 2619
OPT / WPT / GPT / LPT / VPT . . . . . 2624
OPVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2434
OPVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2432
OVPG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2458
OVVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2455
P-RE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2596
PARE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2643
PBVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2551
PCSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2554
PERF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2588
PINCh . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2518
PLIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2645
POROsity . . . . . . . . . . . . . . . . . . . . . . . . . 2476
PORV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2519
PREX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2595
PROD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2592
PROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2445
2685

PVOL / RVOL / PVR . . . . . . . . . . . . . . 2520
PVTNum . . . . . . . . . . . . . . . . . . . . . . . . . . 2495
R THCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2451
RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2565
RATI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2616
RECU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2564
RECY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2637
REFE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2481
RELA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2462
REPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2527
RG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2426
RHAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2563
RSVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2552
RVVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2553
S TUBI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2611
SALE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2639
SATNum / ROCK . . . . . . . . . . . . . . . . . . 2485
SCMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2417
SDATe . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2413
SDEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2440
SEPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2555
SGCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2528
SGL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2529
SGU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2530
SHUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2608
SIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2470
SOGCr . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2531
SOLU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2459
SOWCr . . . . . . . . . . . . . . . . . . . . . . . . . . . 2532
SQUEeze . . . . . . . . . . . . . . . . . . . . . . . . . . 2590
STMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2663
STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2609
STRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2629
SWCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2535
SWL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2534
SWU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2533
T WFRA . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2602
T_X / T_Y / T_Z (TX / TY / TZ, T-X /
T-Y / T-Z). . . . . . . . . . . . . . . . . .2522
TEMP (RECU) . . . . . . . . . . . . . . . . . . . . 2661
TEMPerature (FLUI) . . . . . . . . . . . . . . . 2431
TEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2662
19.1
TFIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2568
TFUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2466
THCG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2452
THCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2454
THCW . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2453
THER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2427
THICkness . . . . . . . . . . . . . . . . . . . . . . . . 2475
THP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2615
THPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2623
TITLe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2409
TRAC (FLUI) . . . . . . . . . . . . . . . . . . . . . 2446
TRAC (RECU) . . . . . . . . . . . . . . . . . . . . 2657
TSUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2544
TTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2575
U
UGAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2448
UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2411
UOIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2447
UROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2450
UWAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2449
V
VARI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2524
VCOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2442
VCVI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2460
VERT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2468
VOLU . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2437
VREP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2636
W
WALQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2627
WATR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2429
WCOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2600
WEF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2628
WELL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2597
WETT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2463
WGPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2658
WMPG . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2659
WRG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2660
WVVT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2457
WWAG . . . . . . . . . . . . . . . . . . . . . . . . . . . 2601
2686
 19.1

X Y
X-DIrection . . . . . . . . . . . . . . . . . . . . . . . . 2472 Y-DIrection . . . . . . . . . . . . . . . . . . . . . . . . 2473
XFLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2621 YKRW . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2541
XKRG . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2536
XKRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2537 Z
XKRW . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2538 ZCOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2461
XPCG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2539 ZCORn . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2542
XPCW . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2540 ZVAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2543

2687
 19.1

19. 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, pp. 214–218, 1970.

[4] Stone, H. L., Estimation of Three-Phase Relative Permeability and Residual Oil Data.
Can.Pet.Tech., Vol 12, pp. 53–61, 1973.

[5] Carter, R. D., Tracy, G. W., An Improved Method for Calculating Water Influx. Trans AIME
(JPT), 219, pp. 58–60, 1960.

[6] Fetkovich, M. J., A Simplified Approach to Water Influx Calculations - Finite Aquifer Systems.
JPT, pp. 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] Tarek Ahmed, Equations of State and PVT Analysis: Applications for Improved Reservoir Mod-
eling, Gulf Publishing Company, Houston, Texas, 2007.

[10] Tarek Ahmed, Hydrocarbon phase behavior, Gulf Pub. Co., 1989.

[11] Economides, Michael J. Unified Fracture Design. Orsa Press, Alvin, Texas, 2002.

[12] Khalid Aziz, George W. Govier, Pressure Drop In Wells Producing Oil And Gas. Journal of
Canadian Petroleum Technology, volume 11, July 1972.

[13] J. Orkiszewski, Predicting Two-Phase Pressure Drops in Vertical Pipe. Journal of Petroleum Tech-
nology, volume 19, June 1967.

[14] Alton R. Hagedorn, Kermit E. Brown, Experimental Study of Pressure Gradients Occurring Dur-
ing Continuous Two-Phase Flow in Small Diameter vertical Conduits. Journal of Petroleum Tech-
nology, volume 17, April 1965.

[15] D.H. Beggs, J.P. Brill, A Study of Two-Phase Flow in Inclined Pipes. Journal of Petroleum
Technology, volume 25, May 1973.

[16] 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.

[17] Nicholas Petalas, A Mechanistic Model for Stabilized Multiphase Flow in Pipes. Stanford Uni-
versity, 1997.

[18] http://www.fekete.ca/SAN/WebHelp/Piper/WebHelp/c-te-pressure.htm, Gray correlation section.

19. References 2688

 19.1

[19] M.J. King, Mark Mansfield, Flow Simulation of Geologic Models. SPE Reservoir Eval. & Eng.,
Vol. 2, No. 4, August 1999.

[20] Perry’s Chemical Engineers’ Handbook, pp. 2-306.

[21] 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.

[22] L.E.Baker, SPE / DOE 17369.

[23] Fayers and Matthews, SPEJ April 1984, pp. 224-232.

[24] Carl L. Yaws, Thermophysical properties of chemicals and hydrocarbons, Elsevier, 2014.

[25] Karen Schou Pedersen, Peter L. Christensen, Phase Behavior of Petroleum Reservoir Fluids,
Taylor & Francis Group, 2006. (pp. 197–206).

[26] Bean, Buckingham, Murphy, Discharge coefficients of squared edged orifices for measuring the
flow of air, US Bureau of Standards, RP 49, 1929.

[27] Todd, M., Longstaff, W., The Development, Testing and Application of a Numerical Simulator for
Predicting Miscible Flood Performance, SPE 3484, Journal of Canadian Petroleum Technology
(1972) 24, No. 7, 874-882.

[28] Coats, K. H., An Equation of State Compositional Model, paper SPE 8284, Society for Petroleum
Engineers Journal (1980) 20, 363-376; also presented at the SPE 54th Annual Technical Confer-
ence and Exhibition, Las Vegas, Nevada, USA (September 23-26, 1979).

[29] Killough, J. E. Reservoir Simulation with History-dependent Saturation Functions, paper SPE
5106, Society of Petroleum Engineers Journal (1976).

[30] Claus P. Rasmussen, Kristian Krejbjerg, Michael L. Michelsen, Kersti E. Bjurstrom Increasing
the Computational Speed of Flash Calculations with Applications for Compositional, Transient
Simulations, SPE Reservoir Evaluation and Engineering (2006).

[31] Zuber, N. and Findlay, J. A. Average Volumetric Concentration in Two-Phase Flow Systems,
Transactions of ASME, Ser. C, Journal of Heat Transfer (1965) 87, No. 4, 453-468.

[32] Hasan, A. R. and Kabir, C. S. A Simplified Model for Oil/Water Flow in Vertical and Deviated
Wellbores, SPE 54131, SPE Production & Facilities (1999) 14 No. 1, 56–62.

[33] Payne, G.A., Experimantal Evaluation of Two- Phase Pressure Loss Correlations for Inclined
Pipe, M.S. Thesis, The University of Tulsa, 1975.

[34] Sonnad, J. R., Goudar, C. T., Explicit Reformulation of the Colebrook-White Equation for Tur-
bulent Flow Friction Factor Calculation, Ind. Eng. Chem. Res., 2007, 46, 2593-2600.

[35] K. Yu. Bogachev, E. V. Piskovskiy, and G. G. Piatsky, A Method for the Coupled Solution of the
Filtration Problem and the System of Elasticity Equations, Numerical Methods and Programming
(Vychislitelnye Metody i Programmirovanie). [in Russian], 2017, 18, 221-226.

[36] V. V. Belousov, Structural Geology Mosk. Gos. Univ., Moscow, 1986.

19. References 2689

 19.1

[37] Chang, Y-B, Coats B. K., and Nolen, J. S., A Compositional Model for CO2 Floods Including
CO2 Solubility in Water. SPE 35164, SPE Reservoir Evaluation and Engineering, 1998 1 No. 2,
155-160.

[38] Brusilovskiy K.I., Phase transitions at oil and gas development. M.: ”Graal” [in Russian], 2002,
575 p.

[39] Michelsen, M.L., The isothermal flash problem. Part II. Phase-split calculation. Fluid phase equi-
libria, 1982, 9, p.21–40.

[40] Michelsen, M.L., The isothermal flash problem. Part I. Stability. Fluid phase equilibria, 1982, 9,
p.1–19.

[41] Rachford, H. H. J. D. Rice, Procedure for Use of Electrical Digital Computers in Calculating
Flash Vaporization Hydrocarbon Equilibrium. JPT, 1952, p.19.

[42] Li, Y.-K., L.X. Nghiem, Phase Equilibria of Oil, Gas and Water/Brine Mistures from a Cubic
Equation of State and Henry’s Law. Canadian J. of Chemical Engineering., 1986, 64 (3), pp.
486–496.

[43] Allen M. Rowe Jr., and James C. S. Chou, Pressure-Volume-Temperature-Concentration Relation

of Aqueous NaCl Solutions. Journal of Chemical and Engineering Data., 1970, Vol. 15, No. 1,
pp. 61-65.

[44] Ejiogu, G. C., Fiori, M., High-Pressure Saturated-Steam Correlations. Journal of Petroleum Tech-
nology., 1987, 39 (12), pp. 1585–1590.

[45] Indrupskiy I.M., Lobanova O.A., Zubov V.R., Non-equilibrium phase behavior of hydrocarbons in
compositional simulations and upscaling. Computational Geosciences, 2017, 21(5), P. 1173-1188.

[46] Whitson, Curtis and L. Michelsen, Michael, The Negative Flash. Fluid Phase Equilibria, 1989,
51-71 p.

19. References 2690

 Rock Flow Dynamics

Phone: +1 713-337-4450
Fax: +1 713-337-4454
Address: 2200 Post Oak Boulevard, STE 1260, Houston, TX 77056
E-mail: tnavigator@rfdyn.com
Web: http://rfdyn.com

To locate the office nearest to you, please visit https://rfdyn.com/contact/

© Rock Flow Dynamics. All rights reserved. 15.03.2019