tNavUserGuideDesignerEnglish PDF

18.
Geology & Model Designer

User Guide
Rock Flow Dynamics
March 2018
18.1
Copyright Notice
Rock Flow Dynamics r (RFD), 2004–2018. 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
18.1
Press to open tNavigator Library

Press to open User Manual
Contents
1. Introduction 12
2. Designer project 14
2.1. Designer project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.2. Top menu. Document. View. Files Reports. Queue . . . . . . . . . . . . . . 15
2.3. Import Data from Rescue File . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.4. Top panel buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.5. Left Panel Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.6. Report Panel – Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3. Cases 23
3.1. Creating different variants of a model . . . . . . . . . . . . . . . . . . . . . 24
3.2. Visualization option of Information tab . . . . . . . . . . . . . . . . . . . . 24
4. Geometry Objects. Calculations 26

4.1. Calculations panel buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5. Wells 27
5.1. Create Log by Trajectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.2. Import. Well Trajectories . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.2.1. Import. WELLTRACK Format . . . . . . . . . . . . . . . . . . . . . . 28
5.2.2. Import. Well Path/Deviation Text Format . . . . . . . . . . . . . . . . 30
5.2.3. Import. LAS Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.2.4. Import. GWTD Format . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.2.5. Import. Landmark OWX Format . . . . . . . . . . . . . . . . . . . . . 35
5.2.6. Import. MoReS Format . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.2.7. Import. Vertical Wells Format . . . . . . . . . . . . . . . . . . . . . . . 39
5.3. Trajectory construction methods . . . . . . . . . . . . . . . . . . . . . . . . 40
5.4. Import. Well Heads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
5.5. Transformations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.6. Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6. Markers 44
6.1. Import. Markers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.1.1. Text Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.1.2. Landmark OWX Format . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.2. Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.3. Calculator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
CONTENTS 3
18.1
6.4. Build Marker by Horizon . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

6.5. Build Marker by Logs Correlation . . . . . . . . . . . . . . . . . . . . . . . 46
7. Wells Attributes 49
7.1. Calculator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
7.2. Average Log Between Markers . . . . . . . . . . . . . . . . . . . . . . . . 49
8. Logs 52
8.1. Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
8.1.1. Production Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
8.1.2. LAS Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
8.1.3. RFT Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
8.1.4. Landmark OWX Format . . . . . . . . . . . . . . . . . . . . . . . . . 57
8.2. Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
8.3. Calculator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
8.4. Logs Calculation. Upscale Log to Grid . . . . . . . . . . . . . . . . . . . . 58
8.5. Logs Calculation. Create Log by Property . . . . . . . . . . . . . . . . . . . 58
8.6. Logs Calculation. Remove Equals . . . . . . . . . . . . . . . . . . . . . . . 59
8.7. Logs Calculation. Generate synthetic . . . . . . . . . . . . . . . . . . . . . 60
8.8. Logs Setting. Remove Equals . . . . . . . . . . . . . . . . . . . . . . . . . 61
8.9. Logs Setting. Resample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
8.10. Logs Setting. Remove Spikes . . . . . . . . . . . . . . . . . . . . . . . . . 64
8.11. Logs Setting. Block/Unblock . . . . . . . . . . . . . . . . . . . . . . . . . . 65
9. Comment Logs 66
9.1. Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
9.2. Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
10. Core Sample Images 68

10.1. Load Core Sample Images . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
11. Horizons 69
11.1. Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
11.1.1. Import. CPS Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
11.1.2. Import. Horizon ASCII Format . . . . . . . . . . . . . . . . . . . . . . 71
11.1.3. Import. Surfer 6 GRD (Bin) Format . . . . . . . . . . . . . . . . . . . 72
11.1.4. Import. Surfer 7 GRD (Bin) Format . . . . . . . . . . . . . . . . . . . 73
11.1.5. Import. Z-Map Plus Format . . . . . . . . . . . . . . . . . . . . . . . . 73
11.1.6. Import. GXF-3 Format . . . . . . . . . . . . . . . . . . . . . . . . . . 75
11.2. Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
11.2.1. Export All Horizons to Horizon Format (ASCII). . . . . . . . . . . . . 78
11.2.2. Export Horizon to Horizon Format (ASCII). . . . . . . . . . . . . . . . 78
11.3. Calculator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
11.4. Crop Horizon by Polygon . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
CONTENTS 4
18.1
11.5. Interpolation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
11.5.1. Horizons: IDW Method . . . . . . . . . . . . . . . . . . . . . . . . . . 80
11.5.2. Horizons: Kriging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
11.5.3. Horizons: SGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
11.5.4. Horizons: Least Squares method . . . . . . . . . . . . . . . . . . . . . 84
11.5.5. Horizons: Least Squares interpolation (by Point Set) . . . . . . . . . . 86
11.6. Horizons Adjustment to Markers . . . . . . . . . . . . . . . . . . . . . . . . 88
11.6.1. IDW method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
11.6.2. Least Squares method . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
11.7.1. Rotate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
11.7.2. Translate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
11.7.3. Smooth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
11.7.4. Pull Up Horizon to Marker . . . . . . . . . . . . . . . . . . . . . . . . 91
11.8. Auxiliary Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
11.8.1. Create Horizon by Pointset . . . . . . . . . . . . . . . . . . . . . . . . 91
11.8.2. Create Horizon by Seismic Horizon . . . . . . . . . . . . . . . . . . . 92
12. 2D-Maps 93
12.1. Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
12.2. Calculator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
12.3. Voronoi Regions 2D Map by Markers . . . . . . . . . . . . . . . . . . . . . 95
12.4. Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
12.5. Interpolation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
12.5.1. 2D Maps: IDW Method . . . . . . . . . . . . . . . . . . . . . . . . . . 96
12.5.2. 2D Maps: Kriging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
12.5.3. 2D Maps: SGS Method . . . . . . . . . . . . . . . . . . . . . . . . . . 99
12.5.4. 2D Maps: Least Squares method . . . . . . . . . . . . . . . . . . . . . 100
12.6. 2D Map Adjustment to Wells Attributes . . . . . . . . . . . . . . . . . . . . 102
12.6.1. IDW method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
12.7.1. Rotate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
12.7.2. Translate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
12.8.1. 2D Map by Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
12.8.2. Azimut Map by Polygons . . . . . . . . . . . . . . . . . . . . . . . . . 106
13. Seismic 108

13.1. Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
CONTENTS 5
18.1
14. Seismic Horizons 110

14.1. Create a new seismic horizon . . . . . . . . . . . . . . . . . . . . . . . . . 110
14.2. Seismic Interpretation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
14.3. Autotracking parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
14.4. Line and Projection display . . . . . . . . . . . . . . . . . . . . . . . . . . 112
14.5. 3D Correlation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
15. Polygons 114

15.1. Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
15.1.1. Single Polygon File (Text file) . . . . . . . . . . . . . . . . . . . . . . 114
15.1.2. From .bln files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
15.1.3. TKS Polygons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
15.1.4. Polygon lines (ASCII) . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
15.1.5. CPS-3 lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
15.1.6. Import Polygons from Shapefile . . . . . . . . . . . . . . . . . . . . . 116
15.2. Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
15.3. Polygons Union . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
15.4. Polygons by Point Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
15.5. Set Polygon Z-Coordinates by Depth . . . . . . . . . . . . . . . . . . . . . 118
15.6. Set Polygon Z-Coordinates by Horizon . . . . . . . . . . . . . . . . . . . . 118
15.7. Transform Polygon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
16. Aquifers 120

16.1. Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
16.2. Aquifer Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
16.2.1. Carter-Tracy Aquifer Settings . . . . . . . . . . . . . . . . . . . . . . . 121
16.2.2. Fetkovich Aquifer Settings . . . . . . . . . . . . . . . . . . . . . . . . 121
16.2.3. Constant Head/Pressure Water Aquifer Settings . . . . . . . . . . . . . 121
17. Faults 122

17.1. Fault Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
17.2. Fault Editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
17.3. Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
17.3.1. From Curves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
17.3.2. Landmark Fault 3D Format . . . . . . . . . . . . . . . . . . . . . . . . 126
17.3.3. Surfer .Bln Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
17.3.4. Surfer 7 GRD Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
17.4. Smooth Fault Surface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
17.5. Ruled Fault by Curves 2D . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
17.6. Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
17.6.1. Export Fault as Curve Set . . . . . . . . . . . . . . . . . . . . . . . . . 131
17.7. Auxialiary Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
17.7.1. Create Fault by Seismic Fault . . . . . . . . . . . . . . . . . . . . . . . 131
CONTENTS 6
18.1
18. Faulted Horizons 133

18.1. Horizon by Marker and Faults (Least-Squares) . . . . . . . . . . . . . . . . 133
18.2. Horizon by Point Set and Faults (Least-Squares) . . . . . . . . . . . . . . . 134
19. Point Sets 136

19.1. Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
19.1.1. XYZ format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
19.1.2. Point set lines (ASCII) . . . . . . . . . . . . . . . . . . . . . . . . . . 137
19.1.3. CPS-3 lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
19.1.4. Import Pointsets from Shapefile . . . . . . . . . . . . . . . . . . . . . 138
19.2. Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
19.2.1. Export all PointSets in XYZ format . . . . . . . . . . . . . . . . . . . 138
19.2.2. Export all PointSet in XYZ format . . . . . . . . . . . . . . . . . . . . 138
19.3. Create Point Set by Horizon . . . . . . . . . . . . . . . . . . . . . . . . . . 139
19.4. Create Point Set by Seismic Horizon . . . . . . . . . . . . . . . . . . . . . 139
19.5. Create Point Set as Wells and Horizon Intersection . . . . . . . . . . . . . . 139
19.6. Create Point Set by Marker . . . . . . . . . . . . . . . . . . . . . . . . . . 140
19.7. Clear Point Set Near Faults . . . . . . . . . . . . . . . . . . . . . . . . . . 140
19.8. Create a Point Set by Grid Layer . . . . . . . . . . . . . . . . . . . . . . . 140
19.9. Pointsets Union . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
19.10.Shift Point Set by Vector . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
20. Tables 142

20.1. Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
20.2. Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
20.3. Create Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
21. 3D-Grids. Model grids 143

21.1. Import. Load Grid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
21.2. Create Simple Grid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
21.3. Create Simple LGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
21.4. Create LGRs by Wells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
21.5. Create LGRs by Filter Property . . . . . . . . . . . . . . . . . . . . . . . . 147
21.6. Remove LGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
21.7. Create Grid by Horizons . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
21.8. Create Grid by Horizon and Faults . . . . . . . . . . . . . . . . . . . . . . 150
21.9. Create Grid by Point Sets&Faults . . . . . . . . . . . . . . . . . . . . . . . 154
21.10.Transformations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
21.10.1. Edit Grid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
21.10.2. Translate & Rotate Grid . . . . . . . . . . . . . . . . . . . . . . . . . 157
21.10.3. Cut Grid 3D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
21.10.4. Update Grid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
21.11.Add Geological K to Grid 3D . . . . . . . . . . . . . . . . . . . . . . . . . 158
21.12.Import Existing Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
CONTENTS 7
18.1
21.13.Calculate Grid Geometry Properties . . . . . . . . . . . . . . . . . . . . . . 159

21.14.Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
21.14.1. Export. Corner Point format . . . . . . . . . . . . . . . . . . . . . . . 160
21.14.2. Export. All Maps to GRID_ECL . . . . . . . . . . . . . . . . . . . . . 160
22. Grid Properties 161

22.1. Import. GRID_ECL (ASCII) . . . . . . . . . . . . . . . . . . . . . . . . . . 161
22.2. Calculator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
22.3. Interpolation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
22.3.1. Interpolation: Trivial interpolation . . . . . . . . . . . . . . . . . . . . 162
22.3.2. Interpolation: Multilayer IDW method . . . . . . . . . . . . . . . . . . 162
22.3.3. Interpolation: Multilayer Kriging . . . . . . . . . . . . . . . . . . . . . 163
22.3.4. Interpolation: Multilayer SGS . . . . . . . . . . . . . . . . . . . . . . . 165
22.3.5. Interpolation: Kriging 3D . . . . . . . . . . . . . . . . . . . . . . . . . 166
22.3.6. Interpolation: SGS 3D . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
22.4. Facies Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
22.4.1. Facies Analysis and Discrete properties modeling: Trivial interpolation 169
22.4.2. Facies Analysis and Discrete properties modeling: Multilayer IDW
method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
22.4.3. Facies Analysis and Discrete properties modeling: Multilayer Kriging 170
22.4.4. Facies Analysis and Discrete properties modeling: Multilayer SGS . . 171
22.4.5. Facies Analysis and Discrete properties modeling: Kriging 3D . . . . 173
22.4.6. Facies Analysis and Discrete properties modeling: SGS 3D . . . . . . 174
22.5.1. Calculate Geometrical Volume . . . . . . . . . . . . . . . . . . . . . . 176
22.5.2. Calculate Pore Volume . . . . . . . . . . . . . . . . . . . . . . . . . . 177
22.5.3. Calculate Volumetric Properties . . . . . . . . . . . . . . . . . . . . . . 177
22.5.4. Connected Components . . . . . . . . . . . . . . . . . . . . . . . . . . 181
22.5.5. Grid & Faults Intersection Property . . . . . . . . . . . . . . . . . . . 182
22.5.6. 3D Voronoi Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
22.5.7. Multilayer Voronoi Regions . . . . . . . . . . . . . . . . . . . . . . . . 182
22.5.8. Calculate Cut by Polygon . . . . . . . . . . . . . . . . . . . . . . . . . 183
22.5.9. Calculate Cut by Wells . . . . . . . . . . . . . . . . . . . . . . . . . . 183
22.5.10. Create Property by Zones . . . . . . . . . . . . . . . . . . . . . . . . . 183
22.5.11. Edit Property Inside Polygon . . . . . . . . . . . . . . . . . . . . . . . 183
22.5.12. Calculate Property by VPC and 2D Map . . . . . . . . . . . . . . . . . 184
22.5.13. Property by Well Log Distribution (experimental) . . . . . . . . . . . . 184
22.5.14. Assign between surfaces . . . . . . . . . . . . . . . . . . . . . . . . . 185
22.6. Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
22.7. Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
22.8. User Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
22.9. Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
CONTENTS 8
18.1
23. Blocked Wells 193

23.1. Select a log template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
23.2. Blocked Wells Computation . . . . . . . . . . . . . . . . . . . . . . . . . . 194
24. Contacts 199

24.1. Create Contact by Horizon . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
25. Fluid Properties 199

25.1. General Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
25.2. Property Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
26. Wells Data. Tables 202

26.1. Well Production Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
26.1.1. History table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
26.1.2. History – FHF Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
26.1.3. Grouped by wells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
26.2. Well Structure Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
26.2.1. Events – One Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
26.2.2. Events – Grouped by wells . . . . . . . . . . . . . . . . . . . . . . . . 211
26.2.3. Events – Landmark OWX format . . . . . . . . . . . . . . . . . . . . . 212
27. Wells Data. Strategies. Rules. Global 213

27.1. Time steps, rules and strategies buttons . . . . . . . . . . . . . . . . . . . . 214
27.2. Right Panel Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
27.3. Wells Data. Global Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
27.3.1. Input Wells Trajectories . . . . . . . . . . . . . . . . . . . . . . . . . . 216
27.3.2. Input VFP tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
27.3.3. Input Well Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
27.3.4. Gas Lift Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
28. Wells Data. Rules. Wells 218

28.1. Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
28.1.1. Create Historical Well Controls by Table . . . . . . . . . . . . . . . . . 218
28.1.2. Create Forecast Well Controls by Table . . . . . . . . . . . . . . . . . 221
28.1.3. Reset Well Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
28.1.4. Well Efficiency Factor . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
28.1.5. Drawdown Limit for Well . . . . . . . . . . . . . . . . . . . . . . . . . 226
28.1.6. Well Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
28.1.7. Well Production Limits (Forecast) . . . . . . . . . . . . . . . . . . . . 227
28.1.8. Well Injection Limits (Forecast) . . . . . . . . . . . . . . . . . . . . . 228
28.2. VFP tables for wells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
28.2.1. Assign VFP Tables to Production wells . . . . . . . . . . . . . . . . . 229
28.2.2. Assign VFP Tables to Injection wells . . . . . . . . . . . . . . . . . . 229
28.3. Economical Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
CONTENTS 9
18.1
28.3.1. Economic Limits for Production Well . . . . . . . . . . . . . . . . . . 231

28.3.2. Economic Limits for Injection Well . . . . . . . . . . . . . . . . . . . 231
28.4. ASP Flooding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
28.4.1. Surfactant Concentration . . . . . . . . . . . . . . . . . . . . . . . . . 232
28.4.2. Polymer Concentration . . . . . . . . . . . . . . . . . . . . . . . . . . 232
28.4.3. Alkaline Concentration . . . . . . . . . . . . . . . . . . . . . . . . . . 232
28.5. Thermal properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
28.5.1. Thermal Properties of Injected Fluid . . . . . . . . . . . . . . . . . . . 233
28.6. Brine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
28.6.1. Salt Concentration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
28.7. Other well rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
28.7.1. Well Specification Parameters . . . . . . . . . . . . . . . . . . . . . . 234
29. Wells Data. Rules. Groups 236

29.1. Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
29.1.1. Group Production Controls . . . . . . . . . . . . . . . . . . . . . . . . 236
29.1.2. Group Injection Controls . . . . . . . . . . . . . . . . . . . . . . . . . 237
29.1.3. Group Efficiency Factor . . . . . . . . . . . . . . . . . . . . . . . . . . 238
29.2. Economical limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
29.2.1. Economic Limits for Production Group . . . . . . . . . . . . . . . . . 239
29.3. Other group rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
29.3.1. Gas Lift Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
29.3.2. Create Group Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . 240
30. Wells Data. Rules. Other 243

30.1. User Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
30.2. Comment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
30.3. Wells and Groups Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
31. Other data 245

31.1. Variograms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
31.1.1. Variogram models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
31.1.2. Variogram Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . 246
31.2. Interpolation methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
31.2.2. Trivial interpolation method . . . . . . . . . . . . . . . . . . . . . . . . 262
31.2.3. Multilayer IDW method . . . . . . . . . . . . . . . . . . . . . . . . . . 263
31.2.4. Kriging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
31.2.5. Sequential Gaussian Simulation (SGS) method . . . . . . . . . . . . . 266
32. Graphs 267

32.1. Graph calculator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
32.1.1. Importing libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
32.1.2. Usage examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
CONTENTS 10
18.1
33. References 278
CONTENTS 11
18.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
analysis 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 paral-
lel numerical 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 the following modules are described:
• Geology Designer – building static model from scratch.
• Model Designer – pre-processor to build dynamic model.
Modules Geology Designer, Model Designer are fully integrated with simulation engine
(Black Oil simulator, Compositional simulator, Thermal simulator).
Geology Designer, Model Designer allow to:
• Create static model from scratch using initial data;
• Load rescue files of the static model and edit data; create a dynamic model based on
existing geological model;
1. Introduction 12
18.1
• Load existing model in the tNavigator, E1, E3, IM, ST, GE, MO formats and edit grid
locally, edit properties and keywords;
• Load well trajectory, seismic surfaces, markers, faults, LOG data;
• Interpret seismic horizons;
• Perform well correlation;
• Build horizons and a model grid using different interpolation algorithms;
• Run workflows;
• Build PVT tables using compositional properties and match with measurement data
(PVT Designer is described in the document tNavPVTDesignerGuide);
• Create phase relative permeabilities;
• Create lifting tables (VFP) using correlations and match with measurement data;
• Load wells events and historical data;
• Define rules for wells (well control mode, economic limits, group controls and other);
• Work in one graphical interface with static and dynamic data;
• Calculate the designed dynamic model visualizing results on 2D, 3D and graphs.
tNavigator User Manual contains the description of physical model, mathematical model
and the keywords that can be used in dynamic model.
1. Introduction 13
18.1
2. Designer project
See the training course 9.1 How to Use Geology to learn how to create a geological (and a
dynamic further) model from scratch using initial geological data
2.1. Designer project

The graphical interface is composed of:
• The Top menu (Document. View. Files. Reports. Queue);
• Top Panel Buttons;
• The Options Panel (Cases, Geometry Objects, Fluid Properties, Wells Data, Others,
Graphs);
• There are three working panels: a tree of corresponding objects (at the left), a visual-
ization properties panel and a list of calculations which are available for the object. It
is possible to activate only the panels you need for work using buttons placed at the
left (Left panel buttons);
• The Visualization panel (2D, 3D, Wells Table, Well Section, Histogram, VPC, Cross-
plot, Seismic, Geosteering);
• The Right panel buttons;
• Log Panel at the bottom of the project window.
The required option can be chosen by left clicking on the corresponding button. For most
part of the options, selecting an option brings up an additional sub-options panel near the
main option panel. On the right panel, the corresponding data are visualized for viewing and
editing.
2. Designer project 14
18.1
Figure 1. Designer project window.
2.2. Top menu. Document. View. Files Reports. Queue

1. Menu Document.
• Save. Save current project.

• Import data from RESCUE file.
The dynamic model will be built from the RESCUE files. Grid, model porosity
property, permeabilities, trajectories of wells can be loaded and a creation of the
dynamic model can be continued based on these data (cf. Import a Rescue file).
An example of this approach can be found in the training tutorial 9.3 How To
Load Rescue And Create Model.
• Import data from Existing model. Indicating the existing model *.data file its
2.2. Top menu. Document. View. Files Reports. Queue 15

18.1
grid, properties, phase relative permeabilities, PVT, wells data and other proper-
ties will be loaded. The geological project will be created based on the loaded
model. Further, the model can be modified. It is possible to make a local grid
editing, change properties, add an aquifer, do a local grid refinement, etc. After
all necessary modifications the modified model can be saved.
• Open Model.
Open a created dynamic model.
• Export Model. The created model will be saved in tNavigator format. The
definition and detailed description of this format are given in the User Manual
section tNavigator format.
• Export Model in E1/E3 Format. The created model will be saved in one
of these formats. E1 is the black oil model, E3 is the compositional model.
• Stop. Stop calculation of the model.
• Close model. Close the created model.
• Settings.
Coordinate System.
– Coordinate System. Using the button Select the Coordinate Reference Sys-
tem, the coordinate reference can be set for the entire project. The coordinate
system can be found by its EPSG code (European Petroleum Survey Group).
A detailed information about each coordinate system is available, including
the name, the EPSG code, the type of coordinates (projected or geographic),
the information and the data source and the information about the datum
(ellipsoid and origin of the coordinate system).
– Datum. Displays the datum associated to the chosen coordinate system once
it is set. Note that it is possible to import objects which are not in the same
coordinate system as the one which is set for the entire project (see the
options in calculations panel)
Output Units. The units indicted by the user (METRIC / FIELD / LAB) will be
used for the project graphical interface and for the saved model as well.
2. Menu View.
• New View. Create Designer new window for the current project.
• Hide all. Hide all additionally opened windows.
• Show all. Show all additionally opened windows.
• Close all additional views. Close all additionally opened Designer project win-
dows.
Comment. If there are additionally opened Designer windows it is possible to switch
between them using the View menu.

18.1
3. Menu Files. Project files are available for viewing here.
4. files Reports.
See training tutorial 1.3 How To Import Export Data Reports
Some of above mentioned menu elements can be found on top panel buttons.

18.1
2.3. Import Data from Rescue File

This dialog, accessible from the Document menu allows to load a model from a rescue file.
The following parameters have to be set:
• Rescue File Name. Complete path to the rescue file. The path can be changed by the
ellipsis button;
• Grid coordinates Measure Units. Set the units for XY and Z;
• Length Measure Units. Set the length measure units for XY units and Z units;
• Grid and Properties. Contains the following parameters:
– Apply ACTNUM to Grid. Tick or untick the box to use or not ACTNUM cube
(if present) in the project (cf. the keyword ACTNUM, see 12.2.29). The cube will
be loaded as region and will be displayed in the category Regions in Geometry
Objects. If no ACTNUM cube is available and the option is activated, the rescue
file is loaded, but a message is displayed in the message panel indicating that no
ACTNUM is available;
– Use. Tick or untick the box to import or not the properties;
– Input Name. Name of the property in the model;
– Name in Designer. Name of the property which will be displayed in Designer
interface. The field can be changed by double clicking on it;
– Quantity. Set the equivalent quantity of the properties. The proper quantity can
be chosen from the list by double clicking on the field;
– System. Set the system of the properties from SI, METRIC, LAB, FIELD.
• Wellbores. Contains the following parameters:
– Load Wellbores. Import the wellbores if the box is ticked;

– Append To Existing. Add the imported wellbores to the existing ones;
– Add Point with Zero MD. Continue the well trajectories to the nearest point at
XY plane if the top trajectory point is visually below this plane. ;
– Use. Tick or untick the box to import or not the wellbores;
– Input Names. Name of the wellbore in the model;
– Name in Designer. Name of the wellbore which will be displayed in Designer
interface. The field can be changed by double clicking on it;
• Faults. Contains the following parameters:
– Load Faults. Allows to load the faults as separate geometry objects. After the
loading, the faults will appear under Faults in the objects tree.
2.3. Import Data from Rescue File 18

18.1
– Use. Tick or untick the box to import or not the fault;

– Input Names. Name of the fault in the model;
– Name in Designer. Name of the fault which will be displayed in Designer inter-
face. The field can be changed by double clicking on it;
– Find and Replace in Faults Column. Allows to edit the name of the faults in
Designer Interface:
∗ Reduce to 8 symbols. Reduce the fault names in Designer to 8 symbols. If
Change Left Part of Word is checked, the 8 first symbols of the name are
left. If not, the 8 last are left;
∗ Find What Replace With. Allows to edit the name of the faults in the
interface. The symbols which are entered in the field Find What are replaced
by the one entered in Replace with when the button Replace is pressed.
These operations can be undone using the button undo.
• Horizons. Contains the following parameters:
– Load as Horizons.Allows to load the horizons which are present in the model.
The horizons will appear under Horizons in Geometry Objects;
– Load as Faulted Horizons. Allows to load the horizons which are present in the
model as faulted horizons. After the loading, the horizons will appear in Geometry
Objects below faulted horizons;
– Use. Tick or untick the box to import or not the horizons;
– Input Names. Name of the horizon in the model;
– Name in Designer. Name of the horizon which will be displayed in Designer
interface. The field can be changed by double clicking on it
2.3. Import Data from Rescue File 19

18.1
2.4. Top panel buttons

The description of buttons Create new view, Hide All additional views, Show
all views, Save, Open model and Stop see section Top menu. Document. View.
Files. Reports.
• Reload Graphs.
• Open Time Step Editor. Time step editor will be opened (figure 2):
– Add Steps.
Step Length. Time step length: One step, Year, Month, Week, Day. Initial
date. Initial date of the time interval. Final date. Final date of the time interval.
In accordance with defined settings the list of dates will be formed. The number
of steps fitted inside a given time interval will be added.
One step means that time step length is equal to the whole time interval. For any
length of time interval one time step will be always added.
– Remove Step. Remove the time step.
– Add Steps from History and Event Tables. Time steps will be defined
automatically after loading wells data and/or history. Any date can be defined as
initial or final by right-clicking on the date and selecting in dialogue Defined as
initial or final.
Figure 2. Time steps editor – adding a time step.
2.4. Top panel buttons 20

18.1
2.5. Left Panel Buttons

• Show the list of visualization methods and the tree of corresponding objects.
Clicking on the button brings up the panel of available options and corresponding
objects. Clicking on the button again hides the panel.
• Show Settings. Clicking on the button brings up the visualization properties panel.
This panel gathers the main visualization settings for all the objects. Clicking on the
button again hides the panel.
• Show list of calculations of the selected object. Clicking on the button brings up
list of available Calculations for the selected object, e.g. loading object data, creating
object from scratch or based on another available object or exporting the available
object.
Detailed information about the object can be found in the section corresponding to the
object.
2.5. Left Panel Buttons 21

18.1
2.6. Report Panel – Log

This panel is situated in the bottom part of the project window and shows all the information
about current processes, e.g. loading objects, running computations and etc.
By default all messages will be displayed (button Messages, bottom panel). Clicking
on the button Warnings and Errors (on the bottom panel) will display warnings and
errors. Clicking on the button Errors (on the bottom panel) will display only errors.
Figure 3. Report Panel.
2.6. Report Panel – Log 22

18.1
3. Cases
Definitions tab contains general settings of the designed model. Depends on selected def-
initions different options are available in the project. Therefore, it is necessary to define
desirable options (e.g. fluid properties, existing models, initialization, etc.) in the Definitions
tab.
Furthermore, it is possible to create different variants of a model see section Creating

different variants of a model. Model variants can have different grids and properties.
• Grid Properties.
– Use Minimal Pore Volume (see the keyword MINPV, see 12.2.30) or Use Min-
imal Pore Volumes Map (see the keyword MINPVV, see 12.2.32).
– Generate Connections Across. Connections will be generated between non-
neighbor cells using the keyword PINCH (see 12.2.56).
• Fluid Properties.
– Phase. Select designed model phases: Water, Oil and/or Gas.

– Model Type. Select model type: Black Oil or Compositional.
– Hysteresis Allows use different saturation functions for drainage and imbibition
processes. For more details see the section in User Manual. Hysteresis. Hysteresis
options can be modified by clicking on the ellipsis button (corresponds to the
keyword EHYSTR, see 12.6.51).
• PVT property.
In the case of Black Oil model type:
– Vaporized Oil.
– Dissolved Gas.
In the case of Compositional model type:
– PVT properties. It is necessary to define standard temperature and pressure using

the keywords STCOND (see 12.14.11).
• Initialization.
– Equilibrium (the keyword EQUIL (see 12.16.2) is used) or Nonequilibrium

(initial water, oil, etc. saturations should be defined using keywords SWAT
(see 12.16.12), SOIL (see 12.16.14), etc.).
– Initialize SWAT for Capillary Pressure Scaling. (the keyword SWATINIT,
see 12.6.49).
3. Cases 23
18.1
– Threshold Pressures. If the option is selected the keyword THPRES (see 12.16.9)
will be created defining a threshold pressure between equilibrium regions.
The detailed description of hydrodynamic model initialization options is given in the

UserManual section Initial conditions.
• Miscellaneous.
– Allow Long Names. If the option is not activated, the models containing certain
objects (wells, faults, LGRs) with names longer than 8 characters will be not
saved.
For more details about the name length limitation in tNavigator see the option
LONGNAMES of the keyword TNAVCTRL (see 12.1.4).
3.1. Creating different variants of a model

In one project different variants of a model can be created. Different variants can have
different grids, properties. Different variants of a model can be further calculated and obtained
graphs can be compared in Graphs.
Right clicking on the model name brings up a dialogue:
• Set Current. The selected model variant becomes current allowing to modify it.
• Duplicate. All data will be copied (grid, properties, wells data, etc.)
• Delete. Option is available only for model variants which are not current.
• Create Forecast. Option is available only if model calculation is running and at least
one step has been done.
3.2. Visualization option of Information tab

Data indicated below can be shown only when a dynamic model is open.
Open model.
• Information. Information tab contains general information about loaded model:
– Model title (TITLE, see 12.1.2);

– Start simulation date (START, see 12.1.15);
– Language;
– Model type;
– Collector type (single porosity, dual porosity);
3.1. Creating different variants of a model 24

18.1
– Model dimension NX, NY, NZ (block number in X, Y, Z directions) (DIMENS,

see 12.1.25);
– The number of grid blocks, the number of active grid blocks;
– Wells number, transit well number, well group, number of perforation intervals,
maximum number of perforation intervals per well;
– Information about presence in model Alkaline, Surfactant, Polymer, Salt and Trac-
ers. (On / Off).
• Keywords. Contains list of keywords sorted by sections and their parameters except
those involved in section SCHEDULE.
• Variables. List of model variables using for assisted history matching.
3.2. Visualization option of Information tab 25

18.1
4. Geometry Objects. Calculations

Geometry objects tab contains all objects, such as Wells, Markers, Horizons, Logs, Grids
and etc. to create geological model from scratch starting from initial data.
In this section the tab Calculations for all objects is described. Data import and export,
creating grid and variograms, interpolations and other operations with all objects are consid-
ered as calculations. In order to calculate any object click on the button (Show list of
calculations for the selected object) on the left of panel. Define settings for calculating the
object and click on the button Apply at the bottom of the Calculations panel.
4.1. Calculations panel buttons

• Apply. Load the file selected by user (e.g. with well trajectories) or execute a command
(e.g. saving the well trajectory file).
• Clear State Undo all changes.
• Autoupdate. If the button Autoupdate is being pressed, after defining the calculation
rule, the property will be recalculated when the parameters included in the rule change.
By default the button Autoupdate is not pressed.
• Close. Close the calculation panel.
• Actual State. Show the dialogue used for calculating the current object. Parameters
used for the calculation will be activated.
4. Geometry Objects. Calculations 26

18.1
5. Wells
To work with wells in Calculations panel the following possibilities are available:
• Create Log by Trajectory;
• Import. Well Trajectories;
• Import. Well Heads;
• Transformations. Translate Well Trajectories;
• Export. Well Trajectories.
5.1. Create Log by Trajectory

• Create DLS. Trajectory curvature log DLS (Dogleg severity) will be created.
• Create Azimuth. Azimuth log AZIM will be created. Here, the azimuth is an angle
between tangential to the trajectory vector and X axis.
• Create Inclinometry. Inclinometry log INCL will be created. Here, the inclinometry
is an angle between tangential to the trajectory vector and Z axis.
• Method of Calculation DLS:
– first. The following formula is used:

100
DLS = arccos(sin I1 sin I2 (sin A1 sin A2 + cos A1 cos A2 + cos I1 cos I2 ))
∆MD
– second. The following formula is used:
s
A2 − A1 2 I2 − I1 2

200
DLS = arcsin sin I1 sin I2 sin + sin
∆MD 2 2
– third. The following formula is used:

s 2
100 2
I1 + I2
(I2 − I1 ) + sin (A2 − A1 )
∆MD 2
DLS is calculated for each line segment of polygonal chain defining well trajectory. In
these formulae:
– ∆MD (METRIC: m, FIELD: f t ) is the difference between MD values taken at

top and bottom points of line segment.
– I1 , I2 are the inclinometry angle values taken at top and bottom points of line
segment, respectively.
5. Wells 27
18.1
– A1 , A2 are the azimuth angle values taken at top and bottom points of line seg-
ment, respectively.
• Well Filter. Allow to select wells to which the calculation will be applied. If a filter is
not activated a calculation will be applied to all wells.
5.2. Import. Well Trajectories

Well trajectories can be load using the following formats:
• Import. WELLTRACK Format;
• Well Path/Deviation Text Format;
• LAS Format;
• GWTD Format;
• Landmark OWX Format;
• MoReS format.
• Vertical Wells
Supported formats of imported well trajectory files are listed below:
5.2.1. Import. WELLTRACK Format

There are two types of WELLTRACK format:
1. For each well the separate table is created. Several well trajectories can be contained
in a file. A well name is specified using the keyword ”welltrack” followed by a well
name. A colon and a wellbore number may be added after a well name.
Trajectory data reading starts when the first number occurred.
Columns are the following:
1.1. X (METRIC: m, FIELD: f t ).

1.2. Y (METRIC: m, FIELD: f t ).
1.3. Z (METRIC: m, FIELD: f t ).
1.4. MD (Measured Depth) (METRIC: m, FIELD: f t ).
A columns order and Z axis orientation can be indicated when loading the files. A well
table is terminated by a comma or a slash /.
5.2. Import. Well Trajectories 28

18.1
Example
welltrack Well_P82
50133.99849282 57365.78811816 3335.08379542 3331.36235500
50131.05636316 57365.30935266 3350.53042953 3346.51853724
50129.97016088 57365.15669689 3356.13983138 3352.01963798
50128.40792386 57364.95680241 3364.20096452 3359.92539399
............................................................;
2. All wells are defined by one table. Columns are:
2.1. Well name.

2.2. X (METRIC: m, FIELD: f t ).
2.3. Y (METRIC: m, FIELD: f t ).
2.4. Z (METRIC: m, FIELD: f t ).
2.5. MD (Measured Depth) (METRIC: m, FIELD: f t ).
Example
Well_P82 50133.99849282 57365.78811816 3335.08379542
3331.36235500
Well_P82 50131.05636316 57365.30935266 3350.53042953
3346.51853724
Well_P82 50129.97016088 57365.15669689 3356.13983138
3352.01963798
................................................ .....
Well_V350 50626.37190988 59306.20715875 3476.42938629
3477.48641053
Well_V350 50625.29074100 59306.09947473 3489.80035778
3490.90156557
Well_V350 50624.10952261 59306.00296529 3504.01549917
3505.16623325
.....................................................
The following fields and options of Wells Import dialog, common for all the formats, can
be set for this format as well:
• Reload All. Delete earlier loaded trajectories and load new ones. If this option is not
activated loaded trajectories will be added to available ones.
• File Names. Show full paths of files containing information about the objects in the
format indicated above.
• Add Rows. Add file with trajectory.
5.2.1. Import. WELLTRACK Format 29

18.1
• Remove Rows. Delete selected file.
• Add Point with Zero MD. Continue well trajectories to the nearest point at XY plane
if the top trajectory point is visually below this plane.
• Invert Z-coordinate (For all formats except Well Path/Deviation and MoReS ones).
It is recommended to activate this option if the loaded trajectories were generated by
the third-party software which has the opposite direction of Z axis. Here Z is directed
downward.
• Use OEM encoding. This field is recommended to activate if the loaded file is the old
encoding file (e.g. DOS encoding).
• Well Filter. Define the wells filter name in which loaded wells will be selected.
• Length Units XY (except LAS and MoReS formats). Choose Units System for X
and Y axes. Available units are METRIC, FIELD, LAB. If option Not specified is
activated, units are defined by default in Document. Settings menu.
• Length Units Z (except LAS and MoReS formats). Choose Units System for Z axis.
Available units are METRIC, FIELD, LAB. If option Not specified is activated, units
are defined by default in Document. Settings menu.
• Apply. Load trajectories of wells from chosen files using activated options.
Additional options can be used:
• Use keywords. Select the format for loading well data. If this option is activated the
first alternative with the keyword ”welltrack” is used, otherwise the second one will be
applied.
5.2.2. Import. Well Path/Deviation Text Format

A file should contain an information about a trajectory for one well. Lines starting from ”#”
symbol are comments. In dialogue there is a possibility to define a line from which the table
will be read.
5.2.2. Import. Well Path/Deviation Text Format 30

18.1
downward.
• Input Data Type. This option is used to indicate the type of columns which are
available in the data which will be input. The exact name of the columns can be
modified later in the preview window.
– MD X Y Z. (METRIC: m, FIELD: f t )
– MD DX DY TVD (METRIC: m, FIELD: f t ) where DX, DY are shifts with
respect to the well head, respectively).
– MD INCL AZM (where INCL (inclinometry) is the angle between the cur-
rent direction and the vertical; AZIM (azimuth) is the angle in clockwise direc-
tion between the north direction and its projection onto a horizontal plane). MD
(METRIC: m, FIELD: f t ).
• Method (available only for MD INCL AZM input data type). Well trajectory con-
struction method based on MD, INCL and AZM data should be chosen. The detailed
description of each method is given in the section Trajectory construction methods.
– Tangential.
– Balanced Tangential.
– Average Angle.
– Radius of Curvature.
– Minimum Curvature.
5.2.2. Import. Well Path/Deviation Text Format 31

18.1
• Preview:
– Delimiter. Define a symbol separating table columns (e.g. tab or space symbols).
– Comment. Define a comment symbol. Comments start with the determined sym-
bol and all text following the symbol will be ignored.
– Skip lines. Skip defined number of lines starting from the file beginning.
– Table of trajectories. Names of columns correspond to the format. Names of
columns can be rearranged. Moreover, in the table additional options are aviable:
∗ Skip. Ignore a data column.
∗ Skip line. Ignore all row data to the right.
Example
# WELL TRACE
# WELL NAME: 1336
# WELL HEAD X-COORDINATE: 9005.36000000
# WELL HEAD Y-COORDINATE: 25888.28000000
# WELL KB: 187.71000000
# WELL TYPE: UNDEFINED
# MD AND TVD ARE REFERENCED (=0) AT KB AND INCREASE DOWNWARDS
# ANGLES ARE GIVEN IN DEGREES
#==================================================
MD X Y Z TVD DX DY AZIM INCL DLS
#==================================================
5.0000000000 9005.3600000 25888.280000 182.71000000
5.0000000000 0.0000000000 0.0000000000 14.000000000
0.2500000000 0.0000000000
50.000000000 9005.4075011 25888.470517 137.71042837
49.999571632 0.0475011024 0.1905165158 14.000000000
0.2500000000 0.0000000000
80.000000000 9005.4550020 25888.661032 107.71109472
79.998905285 0.0950019787 0.3810321248 14.000000000
0.5000000000 0.2500000000
......................................................
5.2.3. Import. LAS Format

This is a standard LAS Format for well trajectory (and log curve). To get the detailed
description of the format follow the link.
5.2.3. Import. LAS Format 32

18.1
downward.
• MD, X, Y, Z (METRIC: m, FIELD: f t ) (where X, Y, Z are well coordinates).
• MD, DX, DY, TVD (METRIC: m, FIELD: f t ) (where DX, DY are shifts with
respect to the well head).
• MD, INCL, AZIM (where INCL (inclinometry) is an angle between the current di-
rection and vertical; AZIM (azimuth) is an angle in clockwise direction between north
direction and its projection onto a horizontal plane).
The Measured depth MD (METRIC: m, FIELD: f t ) is always present in a file.

The accordance between column names and their content can be set in this dialog box.
5.2.3. Import. LAS Format 33

18.1
5.2.4. Import. GWTD Format

The file can contain several well trajectories. The well name is specified using the keywords
”Well name” or ”Wellname”, or ”Well” followed by a colon symbol and the well name. A
comment can follow after that (name columns in the example above). The trajectory data
reading starts when the first number occurred.
The following types of column names can be set:
1. MD (Measured Depth) (METRIC: m, FIELD: f t ).
2. X (METRIC: m, FIELD: f t ).
3. Y (METRIC: m, FIELD: f t ).
4. Z (METRIC: m, FIELD: f t ).
The order and Z axis orientation can be chosen when loading.
downward.
5.2.4. Import. GWTD Format 34

18.1
Preview. Trajectories table. The column names are in agreement with the format but can
can be rearranged. Moreover, in the table additional options are available:
• Skip. Ignore a data column.
• Skip line. Ignore all row data to the right.
Example
Well name : P82
MD in Entry point
3335.08379542 50133.99849282 57365.78811816 -3331.36235500
3350.53042953 50131.05636316 57365.30935266 -3346.51853724
3356.13983138 50129.97016088 57365.15669689 -3352.01963798
3364.20096452 50128.40792386 57364.95680241 -3359.92539399
5.2.5. Import. Landmark OWX Format

Each row starts from keywords except the header followed by data. Each keyword has several
parameters. The parameter position in the row is strictly determined (i.e. parameter typing
starts from and end up in the particular position in the row).
Possible keywords are:
• WELL, 2WELL, 3WELL, etc., define different well attributes;
• PICK, 2PICK, etc., define different marker features;
• WPERF, 2WPERF, etc., define different perforation data;
• LOG1, LOG2, etc., define different log curve features;
• PLG1, PLG2, etc., define different trajectory features.
Thus, well trajectories, logs, markers, events can be determined in one file.
Wells are identified by the first parameter UWI of the keyword WELL (it exists in PLG1
and LOG1 as well).
5.2.5. Import. Landmark OWX Format 35

18.1
Example
Project : my project
Depth Mode : MD
Depth Unit : feet
Distance Unit : feet
Date : 01 Aug 2016
WELL 11111111111111 well-a

2WELL Company LTD well-a 01-11 20 01-Aug-2000 0 0
3WELL 2453895.209 480864.110 40.64190000 -
103.86439000 2453895.209 480864.110
4WELL KB 4714.000 6423.000
5WELL
ELEV KB 4714.000
PICK Mrk-11
2PICK 6344.625 6344.625 -1630.625 42
PICK Mrk-12
2PICK 6151.875 6151.875 -1437.875 1
COMP 1 01-Jun-2000
2COMP N 0.00
WPERF 1 1 6259.000 6288.000
2WPERF0.00 0.00 0.000 0.000 0.000
LOG1 UWI: 11111111111111 Depth:
LOG2 Common: well-a
LOG3 Curve: XXD Run #: Units: API: 10 220 10 01
LOG4 Measr. Depth TVD Depth Log Value Null Value: -999.990
LOG5 6140.000 6140.000 3.534
LOG5 6141.000 6141.000 3.530
LOG5 6142.000 6142.000 3.486
PLG1 UWI: wel1
PLG2 Common: well1 Method: 5
PLG3 Measr. Depth TVD Depth TVDSS Depth X-Offset Y-Offset
PLG4 0.000 0.000 0.000 0.000
PLG4 5380.300 5365.752 -100.797 -26.337
PLG4 5386.090 5371.524 -100.965 -26.764
5.2.5. Import. Landmark OWX Format 36

18.1
downward.
5.2.6. Import. MoReS Format

The standard load file syntax of MoReS simulator for defining well trajectories is supported.
5.2.6. Import. MoReS Format 37

18.1
downward.
5.2.6. Import. MoReS Format 38

18.1
5.2.7. Import. Vertical Wells Format

The file can contain several well trajectories. The file must contain 4 columns: the well name,
X and Y coordinates and the depth of the last trajectory point (as MD, KB, or TVDSS).
The following types of column names can be set:
1. MD (Measured Depth) (METRIC: m, FIELD: f t ).
2. TVDSS (True Vertical Depth Subsea) (METRIC: m, FIELD: f t ).
3. KB (Kelly Bushing) (METRIC: m, FIELD: f t ).
4. X (METRIC: m, FIELD: f t ).
5. Y (METRIC: m, FIELD: f t ).
The order and Z axis orientation can be chosen when loading.
downward.
5.2.7. Import. Vertical Wells Format 39

18.1
Preview. Trajectories table. The column names are in agreement with the format but can
5.3. Trajectory construction methods

The trajectory construction is based on the calculation of coordinate increments of the well
trajectory line segment using the inclinometry and azimuth angles. I1 , A1 denote inclinom-
etry and azimuth for top segment point, receptively and I2 , A2 for bottom segment point,
receptively. The following trajectory construction methods can be implemented:
1. Tangential:
• ∆Z = ∆MD · cos(I1 )
• ∆X = ∆MD · sin(I1 ) cos(A1 )
• ∆Y = ∆MD · sin(I1 ) sin(A1 )
2. Balanced Tangential:
• ∆Z = 12 ∆MD · (cos(I1 ) + cos(I2 ))

• ∆X = 12 ∆MD · (sin(I1 ) · cos(A1 ) + sin(I2 ) · cos(A2 ))
• ∆Y = 21 ∆MD · (sin(I1 ) · sin(A1 ) + sin(I2 ) · sin(A2 ))
3. Averaged Angle:
• ∆Z = ∆MD · cos( 21 (I1 + I2 ))

• ∆X = ∆MD · sin( 21 (I1 + I2 )) · cos( 12 (A1 + A2 ))
• ∆Y = ∆MD · sin( 12 (I1 + I2 )) · sin( 12 (A1 + A2 ))
4. Radius of Curvature:
• ∆Z = ∆MD · sin(I2I2)−sin(I
−I1
1)
• ∆X = ∆MD · (cos(I1 )−cos(I2 ))(sin(A2 )−sin(A1 ))

(A −A )(I −I )
2 1 2 1
(cos(I1 )−cos(I2 ))(cos(A1 )−cos(A2 ))
• ∆Y = ∆MD · (A2 −A1 )(I2 −I1 )
5.3. Trajectory construction methods 40

18.1
Here, an angel measured unit is radian. If an angle is measured in degrees the right
side of the first expression should be multiplied by 180
π , while second and third ones
180 180
by π · π .
5. Minimum Curvature:
• ∆Z = 21 ∆MD · (cos(I1 ) + cos(I2 )) · RF

• ∆X = 12 ∆MD · (sin(I1 ) cos(A1 ) + sin(I2 ) cos(A2 )) · RF
• ∆Y = 12 ∆MD · (sin(I1 ) sin(A1 ) + sin(I2 ) sin(A2 )) · RF,
where:
• RF = 2 tan(DL/2)
DL ,
• DL = arccos(cos(I2 − I1 ) − sin(I1 ) · sin(I2 ) · (1 − cos(A2 − A1 )))
5.3. Trajectory construction methods 41

18.1
5.4. Import. Well Heads

• Reload all. Delete already loaded well heads and reload new ones. If this option is not
activated the loaded well heads will be added to available ones.
• File Names. Show full paths of files containing information about well heads in the
format indicated below.
• Add Rows. Add file.
• Remove Rows. Delete file from the list.
• Delimiter. Define a symbol separating table columns (e.g. tab or space symbols).
• Comment. Define a comment symbol. Comments start with the determined symbol.
All comment text following the symbol will be ignored.
• Skip line. Ingnore, i.e. do not load, defined number of lines from the begining of the
file.
The well head format is defined below:
• Well is the well name;
• X, Y (METRIC: m, FIELD: f t ) X and Y are well head coordinates, respectively;
• KB is the actual elevation above mean sea level (altitude).
Other parameters are further defined:
• Length Units XY. Choose units of length for X axis and Y axis. Available units are
METRIC, FIELD, LAB. If option Not specified is activated, units are defined by
default in Document. Settings menu.
• Length Units Z. Choose units of length for Z axis. Available units are METRIC,
FIELD, LAB. If option Not specified is activated, units are defined by default in
Document. Settings menu.
Example
T-6032 13540732.400 7549405.300 -41.3500
T-6055 13538781.600 7546669.100 -30.7200
T-6066 13534483.400 7543596.400 -30.6700
T-6074 13536838.600 7544463.200 -29.8600
T-5058 13529758.200 7539880.500 -37.1400
5.4. Import. Well Heads 42

18.1
5.5. Transformations
1. Translate Wells Trajectories.
• Well Filter. Allow to select wells trajectories, which will be shifted. If filter is
not activated all wells trajectories will be shifted.
• Shift Vector. (METRIC: m, FIELD: f t ) All trajectory’s points of selected well
will be shifted by a specified number of units in each direction.
5.6. Export
To export a well trajectory in all formats the following options should be defined:
• File name. Define a file name to save well trajectories.
• Well Filter. Allow to export only selected wells trajectories. If a filter is not activated
all wells trajectories will be exported.
• Length Units XY (except LAS and MoReS formats). Choose units of length for X
axis and Y axis. Available units are METRIC, FIELD, LAB. If option Not specified is
• Length Units Z (except LAS and MoReS formats). Choose units of length for Z axis.
Trajectories can be saved in the following formats:
1. GWTD Format.
2. WELLTRACK Format.
3. Well Path/Deviation Format.
4. Well Inclinometry Format.
5. LAS.
The description of different formats and examples of how to use them are given in the
section Import. Well Trajectory.
5.5. Transformations 43
18.1
6. Markers
In Calculations menu to work with Markers the following options are available:
• Import. Markers;
• Export. Text Format;
• Calculator;
• Build Marker by Horizon;
• Build Marker by Logs Correlation.
6.1. Import. Markers

Two types of formats can be imported in this section:
• Text Format;
The import is possible only if well trajectories are loaded.
6.1.1. Text Format

The following options, which are common to all the formats can be set:
• File Names. Show full paths of files containing information about markers.
• Preview. Displays the file which will be imported.
• Input/Depth Units. Define units (METRIC, FIELD, LAB), in which input data will
be loaded. Available units are METRIC, FIELD, LAB. If option Not specified is
For this format, delimiter type, and skip lines options can be set:
6. Markers 44
18.1
file.
The marker table is shown below. Column names correspond to the format. Column names
Table contains:
• Well name;
• Marker name;
• Marker Measured Depth (METRIC: m, FIELD: f t ).
Example
1314 CII_top 1349.79
1314 CII_bottom 1363.23
273 CV_bottom 1555.86
273 CIV_bottom 1553.41
272G_PS CII_bottom 1629.06
272G_PS CII_top 1606.81
6.1.2. Landmark OWX Format

OWX format is the universal format. In this type of file an information about trajectories,
markers, attributes, logs can be defined. The format description is given here. The following
options, which are common to all the formats can be set:
• File Names. Show full paths of files containing information about markers.
• Preview. Displays the file which will be imported.
• Input/Depth Units. Define units (METRIC, FIELD, LAB), in which input data will
be loaded. Available units are METRIC, FIELD, LAB. If option Not specified is
6.1.2. Landmark OWX Format 45

18.1
6.2. Export
Markers are exported in the same format as imported. In the field File name it is necessary
to define the full path of the file and its format, which will be used to export all markers of
the model.
6.3. Calculator
This section contains the tools used to generate a new horizon by mathematical calculations.
• Result Type. Shows the type of object which will be created.
• Result Object. Shows the resulting name of the generated object.
• Formula. Used to write the formula which will define the object to generate.
• Assistant fields. Gathers the objects and the options that can be used in the formula: a
list of objects which can be used for the computation, a list of available operators and
and a list of mathematical functions. Double-click on it to display the exact syntax.
6.4. Build Marker by Horizon

The markers which are generated using this command are defined as intersection points
between well trajectories and a chosen horizon.
• Result Marker. Name of created marker.
• Well Filter. Select wells trajectories used in the calculation. If a well filter is not
selected all trajectories will be used.
• Horizon. Define the horizon, which will be used for building the markers.
6.5. Build Marker by Logs Correlation

The algorithm automatically calculates a well marker depth using an estimation of well log
curves correlation with source well curves in the vicinity of the source well marker position.
The algorithm allows to find the best correlation of well log curves. Moreover, wells are
included in the algorithm process in parallel way. For each well, except source wells, an
attempt to calculate a marker depth is done. This means that the well marker position is
searched in the vicinity of which a well log curve has the form ”similar” to a form of source
well log curve. The size of neighborhood region (i.e. a depth region) in the vicinity of marker
position is defined in Window. A level of ”similarity” of the log curve form in the defined
depth region is estimated by calculating a correlation coefficient using the following formula:
R
Fk,i (zi + x)Fk, j (z j + x)dx
ck (zi , z j ) = qR qR ,
2 (z + x)dx
Fk,i Fk,2 j (z j + x)dx
i
where:
6.2. Export 46
18.1
• Fk,i (z) is the log curve k value of i well at the depth z.
• ck (zi , z j ) is the correlation coefficient for log curve k in the vicinity of the depth zi of
well i and in the vicinity of the depth z j of well j , respectively.
For each well, except source wells, the depth corresponding to the maximum correlation
coefficient is searched in the depth region (defined in Searching Window) in the vicinity
of source marker position. If the correlation coefficient is higher than the threshold value
(Correlation Threshold) then the similarity level is considered to be sufficient enough and
the marker is set at the depth which is the middle of the depth range defined in (Window).
If the marker depth is set for the well then the well is considered to be a source one and the
algorithm process starts again.
In case of several log curves are defined in the Comparison Rule table (see below) the
correlation coefficients are averaged with weights indicated in the table.
(c1 · w1 + ... + cn · wn )
,
(w1 + ... + wn )
where ci are correlation coefficients, wi are weights.
In graphical interface the following parameters can be set:
• Result Marker. Created marker name.
• Result Wells. Wells selected for the building markers algorithm.
• Source Marker. The source marker used for the algorithm. The algorithm searches
target wells log curve regions similar to the log curve region near the source marker.
• Source Wells. Source wells used for the algorithm. Source markers are defined on
source wells. Generally speaking marker can be defined on any well, but only few of
them can be selected as the source one.
• Comparison Rule. Columns:
– Use. Use the defined log curve for building markers.

– Log. Markers will be built on the selected log curve.
– Window. The comparison window is defined by the length of the depth (SSTVD)
range in which the part of selected log curve is set. Other wells log curves will
be compared with the part of selected log curve. The marker depth is the middle
value of the depth range.
– Weight. Weight wi means importance of the i log curve.
– Add Rows. Add a log curve.
– Remove Rows. Delete a log curve.
Options:
6.5. Build Marker by Logs Correlation 47

18.1
• Searching Window. (METRIC: m, FIELD: f t ) The depth range in the vicinity of

maker position of the source well. The marker depth will be searched for any well,
except source wells, in this depth range.
• Correlation Threshold. If the correlation coefficient value is higher than the threshold
value then the similarity is considered to be sufficient to set a marker at the depth
found by the algorithm.
• Nearest Wells Count. Extend the algorithm (i.e. setting markers) to wells, which are
the nearest to source wells.
• Neighborhood Radius. (METRIC: m, FIELD: f t ) The algorithm selects wells lo-

cated from source wells not further than defined distance.
• Hard Mode. Define additional limitation on the maximum correlation coefficients

selection in order to increase the calculation accuracy. Consider correlation coefficients,
higher than threshold value, for wells located within the defined radius are set on unit
interval. The hard mode equals 0,5 means that the coefficients placed at low part of
the interval (from 0 to 0,5) will be discarded. The hard mode equals 1 means that the
well with the highest correlation coefficient will be chosen.
6.5. Build Marker by Logs Correlation 48

18.1
7. Wells Attributes
Well Attribute is the well numerical characteristic. For each calculated characteristic a 2D
Map is available.
For example, the interpolation method residual for constructing a horizon based on markers
can be calculated as an attribute (cf. 11.5).
7.1. Calculator
7.2. Average Log Between Markers

The result of this calculation is the average value of selected well logging data.
• Output:
• Well Attribute. Attribute name obtained by calculation.
• Source Data:
– Well Log. Well log data used to calculate the average log value.
– Top Well Marker. Top well marker is a top boundary of log curve used for the
average value calculation.
– Bottom Well Marker. Bottom well marker is the bottom boundary of log curve
used for the average value calculation. Well log curve is averaged from top to
bottom markers.
– Well Filter. Allow to select wells to which the calculation will be applied. If a
filter is not activated a calculation will be applied to all wells.
• Parameters:
– Well Log Type. Discrete or continuous. Values of Log curve can be discretely
distributed along well’s depth. This means a well can be subdivided by segments
of arbitrary length, along which a Log’s value is constant.
7. Wells Attributes 49
18.1
– Scale Type. (METRIC: m, FIELD: f t ) MD or SSTVD.

• Averaging Parameters:
• Averaging Type. A method of calculation of well attribute is defined here. For Discrete
well log type the following methods are available:
– Most of. Frequently occurred value.
– Median. Median is the value separating the higher half of a data sample from the
lower half.
– Minimum. Minimum value.
– Maximum. Maximum value.
– Arithmetic. Arithmetic average of values.
– Fraction. The ratio of Thickness (see below) to the length of the log curve,
which is distance from top marker to bottom marker.
– Percentage. The ratio of Thickness (see below) to the length of the log curve,
which is distance from top marker to bottom marker in terms of percentage.
– Thickness. The sum of lengths of Log’s segments, in which the Log’s value
coincide with value defined in the Facies Code.
• The averaging methods available for continuous log curve are:
– Arithmetic. Arithmetic average is calculated as:
Ra
f (x)dx
b
|b − a|
– Harmonic. Harmonic average is calculated as:
|b − a|
Rb dx
f (x)
a
– Geometric. Geometric average is calculated as:

Rb
ln f (x)dx
a
e |b−a|
– RMS. RMS is computed as:

v  2
u
u Rb b
u f 2 (x)dx  R f (x)dx 
u
ua −a
 
|b − |b −

a| a|
u
t  
7.2. Average Log Between Markers 50

18.1
– Minimum. Minimum value.

– Maximum. Maximum value.
– Integrate. Integral can be calculated using the formula:
Zb
f (x)dx
a
• Cut by Log. Initial log curve values will be ignored on the intervals where the log
curve values are imposed to be zero.
• Cut by Values. Well log data are limited by the following values:
– Min Value. Minimum value.

– Max Value. Maximum value.
• Cut Behaviour. Filter:
– Ignore values. If well log curve values are not in the range (i.e. from Min Value
to Max Value) defined above then we suppose that log data are not defined at
all.
– Cut values. Cut well log data higher than the defined maximum and lower than
the defined minimum. Log data value higher than the defined maximum will be
decreased to the maximum, while log data values lower than defined minimum
will be increased to the minimum.
7.2. Average Log Between Markers 51

18.1
8. Logs
In Calculations menu to work with well logs the following possibilities are available:
• Import;
• Export;
• Calculator;
• Logs Calculation. Upscale Log to Grid;
• Logs Calculation. Create Log by Property;
• Logs Calculation. Remove Equals;
• Logs Calculation. Generate synthetic.
Other options are also available by right mouse button click on a log curve in Geometry
Objects/Settings:
• Logs Setting. Remove Equals;
• Logs Setting. Resample;
• Logs Setting. Remove Spikes;
• Logs Setting. Block/Unblock.
8.1. Import
Files can be loaded in the following formats:
• LAS Format;
• RFT Format;
• Production Log.
8. Logs 52
18.1
8.1.1. Production Log

Production logs are logs of any property, which are defined by intervals. Each defined
interval admits only one log value. A production log file must contain a well name column,
two columns defining the interval for which the data is available and a column with data
values.
Example
Well Top Bot NTG Phit_Core Sg

3 1717.9 1729.9 0.7 0.23 0.87
3 1730 1749.9 0.6 0.25 0.81
3 1760 1765.9 0.4 0.19 0.7
4 1739.6 1787.3 0.8 0.21 0.81
• File Names. Complete path to the loaded file;
• Add Rows.
• Remove Rows.
• Log Name. Name of the logs which are contained in the file.
file.
• The names of the columns can be set: "Well", "Top" and "Bottom" are present by
default in the list. The log names appear after their definition in the Log Name field
(cf. figure 4).
8.1.2. LAS Format

LAS Format is standard format for well log data. For the detailed description of LAS format
follow the link.
Brief description: file consists of several sections. Each section starts from symbol ’∼’.
The main file sections are:
• ∼Well. Well attributes list.
8.1.1. Production Log 53

18.1
Figure 4. Import a production log calculation. The log names become available in the list
of column names after their definition in the Log Names field.
• ∼Curve. Well log curves list. Each line describes one log curve. Well log curves
are presented in the table of the section ∼Ascii. Well log data are defined in the
corresponding table column. Depth or time should be written in the first line of the
section. This is the curve argument. The line format is the following: from the beginning
to the first dot the log name should be written; from the first dot to the last colon the
measured unit is defined.
• ∼Ascii. The table shown below contains the well log data. The columns order corre-
sponds to the row order in the section ∼Curve.
8.1.2. LAS Format 54

18.1
Example
# LAS format log file
# Project units are specified as depth units
#============================================================
∼Version information
VERS. 2.0:
WRAP. NO:
#============================================================
∼Well
STRT .m 1117.8000000 :
STOP .m 1613.6000000 :
STEP .m 0.20000000 :
NULL . -999.250000 :
WELL. 273 : WELL
FLD. : FIELD
DATE. Thursday, November 29 2012 13:40:49 : DATE
UWI. : UNIQUE WELL ID
#============================================================
∼Curve
DEPT .m : DEPTH
IKP .mS/m : IKP
GK .gAPI : GK
NGK .m3/m3 : NGK
DTP . : DTP
BK .ohm.m : BK
Zones . : Zones
GKcut . : GKcut
Agk . : Agk
∼Parameter
#============================================================
∼Ascii
1117.8000000 1117.8000488 -999.250000 -999.250000 0.2099999934
-999.250000 -999.250000 -999.250000 -999.250000
1118.0000000 1118.0000000 -999.250000 -999.250000 0.2099999934
-999.250000 -999.250000 -999.250000 -999.250000
1118.2000000 1118.1999512 -999.250000 -999.250000 0.2099999934
-999.250000 -999.250000 -999.250000 -999.250000
.................................................
To load files it is necessary to define the following parameters:
• Las File Names. Show full paths of files containing information about well logs data
in LAS Format.
• Add Rows. Add a file.
8.1.2. LAS Format 55

18.1
• Remove Rows. Delete a file from the list.
• Preview. Number of Lines. Number of file lines shown in the Preview window.
• Merge logs with equal names. If this option is activated new well logs data and
already loaded logs data will be merged by equal names.
If new loaded log data coincide with existed ones in terms of measured depth log data
from new loaded files with the same depth replace earlier loaded log data.
• Well Filter. Define well filter name. Data will be loaded for wells selected using a
filter.
8.1.3. RFT Format

RFT (MDT) format file contains the table with the following columns:
• Well name;
• Measured depth (MD);
• Measured pressure data in RFT (MDT) format;
• Date.
Load dialogue allows to choose columns for which data from above mentioned file will
be loaded.
Example
SN-71H1 2511.0 271.33 29.03.2009
SN-71H1 2515.0 271.72 29.03.2009
SN-71H1 2524.0 271.88 29.03.2009
SN-71H1 2537.2 272.78 29.03.2009
SN-81 2517.4 266.55 08.02.2013
SN-81 2517.7 266.57 08.02.2013
SN-81 2523.3 266.89 08.02.2013
SN-82HI 2517.2 264.57 21.03.2013
SN-82HI 2518.9 265.08 21.03.2013
SN-82HI 2523.6 264.97 21.03.2013
SN-82HI 2525.3 265.01 21.03.2013
SN-82HI 2526.8 265.02 21.03.2013
To load a file it is necessary to define the following parameters:
• File Names. Show the full paths of files containing information about measured pres-
sure data in RFT (MDT) format.
8.1.3. RFT Format 56

18.1
• Remove Rows. Delete a chosen file from the list.
file.
• Date Format. Choose available date format or define arbitrary one.
• Input Units. Choose units system for input data (e.g. METRIC, FIELD, LAB). Avail-
able units are METRIC, FIELD, LAB. If option Not specified is activated, units are
defined by default in Document. Settings menu.
The import file format is defined in the table:
• Well – Well Name;
• Date – Date;
• Depth – Measured depth (MD);
• Pressure – Measured pressure data in RFT (MDT) format.
8.1.4. Landmark OWX Format

Landmark OWX Format is a universal format. In the Landmark OWX format file an infor-
mation about well trajectories, markers, events, logs can be defined. To get the description
of this format follow the link.
8.2. Export
• LAS Format.
– Output Folder. Define a folder name for saving files of log corves.
– Input Units.
8.3. Calculator
8.1.4. Landmark OWX Format 57

18.1
8.4. Logs Calculation. Upscale Log to Grid

Upscaling well log on a grid is the averaging log well data process. A depth scale is
increased and becomes equal to a block size along Z. Further, in each block a well log curve
is smoothed using the following formula:
n
v(mdk )(mdk − mdk−1 )
∑ ,
k=1 mdn − md0
where:
• k is a well log depth index. In a block k varies from 1 to n.
• md 0 , md n are depth of top and bottom block faces, respectively.
• md k is the k -th depth.
• v(md k ) is the log curve value at the depth md k .

User settings:
• Source Log. Choose an available log curve.
• Result Log. Define the calculated log curve name.
8.5. Logs Calculation. Create Log by Property

Log curve values are calculated based on properties defined in blocks and intersected by a
well trajectory. Log depth is considered to be equal to the top point of intersection between
block and curve. The curve value is equal to the property value in this block.
User settings:
• Property. Choose available 3D property;
• Result Log Step. Set the type of object which will be used to define the step of the
computed log:
– Use Grid Step. The step of the grid will be affected as sampling step for the
computed log (one point per grid block).
– Set Log Step. The data sampling of the computed log is defined manually in the
field Log Step.
8.4. Logs Calculation. Upscale Log to Grid 58

18.1
– Use Sample Log Step. The computed log will present data points at the same
locations as a sample log defined in the field Sample Log.
• Log Step. Set the step (in distance units of the project) which will be used to sample
the data in the computed log.
• Sample Log. Define the log which will be used to define the sampling of the data in
the computed log. The computed log will present data points at the same locations as
a sample log. This field is active only if the option Use Sample Log Step is chosen
from the list in Result Log Step field.
• Result Log. Define the name of the computed log.
8.6. Logs Calculation. Remove Equals

This setting allows to remove equal values from a log curve. If the input log presents a series
of depth points with the same values, only the first point of each series will be preserved in
the output log (cf. figure 5).
Figure 5. Example of an input (Litho) and an output (Remove Equals Results) log for
Remove Equals calculations. The example is done with a discrete type of log, the values
which are not removed are highlighted.
8.6. Logs Calculation. Remove Equals 59

18.1
• Well Filter. Define a well filter name. The calculation will be performed for the wells
selected in the filter;
• Well Selector. Define a well selector name. The calculation will be performed for the
wells selected by the selector;
• Source Log. Choose an available log curve;
• Result Log. Define the calculated log curve name.
8.7. Logs Calculation. Generate synthetic

This computation allows to generate a synthetic velocity curve, synthetic acoustic impedance,
reflection coefficient and interval velocity curves to compare it with the seismic data. The
match can be improved by changing the wavelet parameters.
• Density Log. Choose the density log from the list;
• Sonic Log. Choose the sonic log from the list;
• Time Depth Relation Log. Choose the time-depth log from the list;
• Time Depth Relation Log type. Choose the log type from the list (one way or two
way time);
• Synthetic log. Set the name of the resulting log.
• Well Filter. Set the well filter from the list. The calculation will be performed for the
wells selected in the filter;
• Algorithm. Set the model for the seismic wavelet:
– Ricker. A zero-phase wavelet model which corresponds to the second derivative

of the Gaussian function;
• Length. Length of the displayed window in ms;
• Central frequency. Set the central frequency of the wavelet in Hz;
• Apply. Generates a synthetic seismic, an acoustic impedance, a reflectivity coefficient

and an interval velocity curve.
8.7. Logs Calculation. Generate synthetic 60

18.1
8.8. Logs Setting. Remove Equals
i This setting is available by right mouse button click on a log curve in

Geometry Objects → Settings.
This setting allows to remove equal values from a log curve. If the input log presents
a series of depth points with the same values, only the first point of each series will be
preserved in the output log (see figure 5).
8.9. Logs Setting. Resample

This setting allows to resample the log data according to the interval which is set in the
field Interval. The resampling method depends on the type of the curve:
• Discrete curves. If in Object Settings, the palette of the curve is a discrete one,
the data is assumed to be piecewise constant. Resampled points will present the same
values as the nearest data point to the top (cf. figure 6);
• Continuous curves. If in Object Settings, the palette of the curve is a continuous

one, the values assigned to resampled data points will correspond to linear interpolation
between the two nearest data points (cf. figure 7).
8.8. Logs Setting. Remove Equals 61

18.1
Well Track
Data Point
Same values of resampled

Resampled values
points for all the interval
between two data points
Data Point
Data Point
Figure 6. Discrete data resampling. The data series is assumed to be piecewise constant.
Resampled points will present the same values as the nearest data point to the top.
8.9. Logs Setting. Resample 62

18.1
Log values
Linear interpolation between

the nearest data points
Resampled points
Data points
Depth
Figure 7. Continuous data resampling. The resampled data series is assumed to be piecewise
linear, interpolating between the two original data points.
8.9. Logs Setting. Resample 63

18.1
8.10. Logs Setting. Remove Spikes

This setting allows to remove isolated data points which are likely to be outliers (located
in large intervals without data, etc.; cf. figure 8).
Figure 8. A) Log curve before spike removal. Some isolated points located in intervals
without data are present. B) Log curve after spike removal. Isolated points ("spikes") were
removed.
8.10. Logs Setting. Remove Spikes 64

18.1
8.11. Logs Setting. Block/Unblock

This setting allows to assume that a log curve is piecewise constant if Block option is
selected. A discrete type of interpolation between the data points is used in this case. If
Unblock Log option is selected, the log is assumed to be continuous between the data points
and a linear interpolation is used.
The interpolation type set in Settings is used for the curve display and also for the property
modeling. (cf. figure 9).
Figure 9. A) Continuous log curve, block log option ticked. The curve is assumed to
be continuous by intervals B) Continuous log curve, unblock log option ticked. A linear
interpolation is used between the points
8.11. Logs Setting. Block/Unblock 65

18.1
9. Comment Logs
In Calculations menu to work with comment logs the following possibilities are available:
• Import;
• Export.
Note that this type of logs cannot be used as input data in Calculator, but can be modified in
Well Table Tab and in Well Section Tab.
9.1. Import
The files can only be loaded in text format.
Example
Well Top MD Bot MD Comment
29 1720 1731 gas: 5000 m3 water: 2m3
11 1732 1779 gas: 1000 m3 water: 0,5 m3
2 1731 1745 gas: 15000 m3 water: 10m3
2 1762 1773 gas: 5000 m3 water: 3m3
7 1672 1698 gas: 7000 m3 water: 1m3
7 1717 1742 gas: 5000 m3 water: 2m3
20 1695 1710 gas: 1000 m3 water: 1m3
.................................................
To load the files it is necessary to define the following parameters:
• File Names. Show full paths of files containing information about comment logs data
in text Format.
file.
• Merge logs with equal names. If this option is activated new comment logs and
already loaded comment logs will be merged by equal names.
If the new loaded comment log data coincide with existed ones in terms of measured
depth log data from new loaded files with the same depth replace earlier loaded log
data.
9. Comment Logs 66
18.1
• Well Filter. Define the well filter name. Data will be loaded for wells selected using
the filter.
9.2. Export
Comment logs can only be exported in text format. To export the file,the following parameters
must be specified:
• Output folder. Choose the folder in which the file will be exported.
• Well Filter. Define the well filter name. Data will be exported for wells selected in the
filter.
9.2. Export 67
18.1
10. Core Sample Images

Core sample images can be uploaded and visualized in Well Section. The following file
format can be loaded:
• BMP (Windows Bitmap)
• GIF (Graphic Interchange Format)
• JPG (Joint Photographic Experts Group)
• JPEG (Joint Photographic Experts Group)
• PNG (Portable Network Graphics)
• PBM (Portable Bitmap)
• PGM (Portable Graymap)
• PPM (Portable Pixmap)
• XBM (X11 Bitmap)
• XPM (X11 Pixmap)
In Calculations, the following options are available:
• Load Core Sample Images;
10.1. Load Core Sample Images

This calculation allows to import a core sample image. To import an image, it is necessary
to build a text file containing the following information:
the well name, the top depth of the image (measured depth), the bottom depth, the
complete path to the image.
Each created file generates one item (object) under Core Sample Images in Geometry
Objects.
The following parameters have to be defined:
• File Name. Complete path to the text file containing the information about the loaded
files;
• Core Sample Images List. Name of the loaded object in Designer project. Each object
can contain several images;
10. Core Sample Images 68

18.1
file.
• Column names can be changed according to the data indicated in the text file.
• Well Filter. Define the well filter name. Data will be loaded for wells selected using
the filter.
• Length Units. Choose units system for input data (e.g. METRIC, FIELD, LAB).
11. Horizons
In Calculations menu to work with horizons the following possibilities are available:
• Import;
• Export;
• Calculator;
• Crop Horizon by Polygon;
• Interpolation;
• Horizons Adjustment to Markers;
• Transformations;
• Auxiliary Calculations.
11.1. Import
Horizons can be loaded in the following formats:
• CPS Format;
• Import. Horizon ASCII Format;
• Surfer 6 GRD (Bin) Format;
• Surfer 7 GRD (Bin) Format;
• Z-Map Plus Format;
• GXF-3 Format.
11. Horizons 69
18.1
11.1.1. Import. CPS Format

The file is composed of a header describing a grid, NOVALUE marker and a list of horizon
values defined in grid points. The header line with the name FSASCI defines:
1. NOVALUE marker which is the fifth element of the FSASCI line.
Comment. All elements of the FSASCI line are ignored except the fifth element. The
line with the name FSATTR is totally ignored.
The line with the name FSLIMI sets bounds for each axis:
1. Minimum of X (METRIC: m, FIELD: f t ).
2. Maximum of X (METRIC: m, FIELD: f t ).
3. Minimum of Y (METRIC: m, FIELD: f t ).
4. Maximum of Y (METRIC: m, FIELD: f t ).
Comment. Fifth and sixth elements of line with the name FSLIMI are ignored.
The number of grid nodes in X and Y directions, respectively, are indicated in the line
with the name FSNROW. The step length in X and Y directions, respectively, is pointed out
in the line with the name FSXINC. The data array starts from symbol ”->” followed by the
horizon name.
Example
FSASCI 0 1 ''Computed'' 0 999999.0 0
FSATTR 0 0
FSLIMI 37150.000000 42400.000000 14950.000000 19250.000000
448.54349 3685.0830
FSNROW 106 87
FSXINC 50.00000 50.00000
->Default
1210.440552 1210.597656 1210.755615 1210.914551 1211.074463
1211.235474
1211.397339 1211.560181 1211.723877 1211.888184 1212.053101
1212.218750
1212.384888 1212.551880 1212.719482 1212.888184 1213.057861
1213.228638
.....................................
• File Name. Show full paths of files containing an information about a horizon.
11.1.1. Import. CPS Format 70

18.1
• Invert Z-coordinates. It is recommended to activate this option if the loaded trajecto-

ries were generated by the third-party software which has the opposite direction of Z
axis. Here Z axis is directed downward.
• Input Units. Choose units system (e.g. METRIC, FIELD, LAB). Available units are
• NOVALUE. Special marker (equals 99999 by default) is used to indicate that a horizon
value does not exist in the data table.
11.1.2. Import. Horizon ASCII Format

The file is composed of a header and of an array of values. The header describes a grid. The
first line of the header defines the following parameters:
1. Unused parameter.
2. The number of grid nodes in Y direction.
3. Grid step in X (METRIC: m, FIELD: f t ).
4. Grid step in Y (METRIC: m, FIELD: f t ).
In the second line of the header the following parameters are defined:
1. Minimum of X (METRIC: m, FIELD: f t ).
2. Maximum of X (METRIC: m, FIELD: f t ).
3. Minimum of Y (METRIC: m, FIELD: f t ).
4. Maximum of Y (METRIC: m, FIELD: f t ).
The third line of the header defines:
1. Number of grid nodes in the X direction.
2. Rotation angle from the X axis in the counterclockwise direction.
Comment. Third and forth parameters in the third line are ignored.
NOVALUE marker is denotes by 99999.0000. An absence of a horizon value in the data
table is marked by the special number 99999.0000. Number values in the array are listed one
by one. The array starts after the line of 7 zeros. Values are listed by rows from bottom to
top.
11.1.2. Import. Horizon ASCII Format 71

18.1
Example
-996 87 50.000000 50.000000
37150.000000 42400.000000 14950.000000 19250.000000
106 0.000000 37150.000000 14950.000000
0 0 0 0 0 0 0
1210.440552 1210.597656 1210.755615 1210.914551 1211.074463
1211.235474
1211.397339 1211.560181 1211.723877 1211.888184 1212.053101
1212.218750
1212.384888 1212.551880 1212.719482 1212.888184 1213.057861
1213.228638

11.1.3. Import. Surfer 6 GRD (Bin) Format

It is a binary file format.
11.1.3. Import. Surfer 6 GRD (Bin) Format 72

18.1

11.1.4. Import. Surfer 7 GRD (Bin) Format

It is a binary file format. The following options, which are common to all the formats can
be set:

11.1.5. Import. Z-Map Plus Format

The symbol ”!” is a comment symbol. The header starts from the first symbol ”@”. The
second symbol ”@” marks the header end and the beginning of the data array/table. In the
table all columns have the same width. The column width is defined in the header. The
symbol position from which the first column starts in each table row is defined in the header
as well. Thus, it is not necessary to use the data delimiter in the table. Moreover, there is a
possibility to load a file without using table parameters by defining a special parameter in
the load dialogue.
The columns number is independent from grid counts in X or Y directions. The table is
defined as one dimensional data array. Therefore, the two dimensional array of grid nodes is
converted to one dimensional array using a column order, i.e. the first column of grid array
11.1.4. Import. Surfer 7 GRD (Bin) Format 73

18.1
followed by the second one etc. In particular, the first column corresponds to the column
with minimum I. All columns start from the top, i.e. from the node with maximum J.
The grid size (counts number), boundaries, NOVALUE marker are defined in the header.
There are four lines in the header. Each row consists of several fields. Each field is separated
by comma. The first line contains:
1. File Name.
2. Word GRID.
3. The number of columns in the table.
The second line contains:
1. Column width in the table.
2. NOVALUE marker.
3. String is similar to NOVALUE marker (can be replaced by space).
4. The number of digits after the decimal point (use when all values are integers in
order to keep the space).
5. Symbol number in each line of the table which begins the first column.
The third row contains:
1. Counts number along Y.
2. Counts number along X.
3. Minimum X coordinate. (METRIC: m, FIELD: f t )
4. Maximum X coordinate. (METRIC: m, FIELD: f t )
5. Minimum Y coordinate. (METRIC: m, FIELD: f t )
6. Maximum Y coordinate. (METRIC: m, FIELD: f t )
The forth line contains:
11.1.5. Import. Z-Map Plus Format 74

18.1
Example
! Landmark Zmap grid file name: my_file.dat
! Created/converted by Xxx Xxx, XXX Inc.
@ my_file.dat, GRID, 4
20, 1.0E+30, , 7, 1
208, 435, -630000.0000, 672000.0000, 2000000.0000,
2621000.0000,
0.0000, 0.0000, 0.0000,
@
45.5158691 70.0117188 78.3193359 78.5185547
92.6440430 96.5151367 97.1289063 103.1782227
110.9963379 120.7421875 137.1284180 162.2819824
191.4841309 218.0258789 228.3671875 204.8771973
150.1228027 82.9328613 30.0051270 7.5603027
This format has Advanced settings.
• Ignore table structure. First and fifth parameters of the header second line are ignored.
Then the table data are separated by space and start from the first line symbol.
• Grid nodes enumeration:
– Listed by. The method of ”scattering” the table values across the grid nodes. Two
methods are available: ”scattering” by Columns and Rows.
– Start node. The grid node starting from which the table values will be scattered
across the grid nodes. There are four approaches: Top left, Bottom left, Top
right, Bottom right.
11.1.6. Import. GXF-3 Format

The grid is described by the set of keywords. Each keyword starts with # symbol. The data
corresponding to the keyword are given in one or several lines (depends on the keyword)
following the line with this keyword. Other lines will be ignored up to the next keyword.
Thus, even if there is no a symbol comment comments can exist in the file.
The minimal list of keywords must include the following keywords:
• #POINTS – counts number in X direction.
• #ROWS – counts number in Y direction.
• #GRID – array of grid values.

11.1.6. Import. GXF-3 Format 75

18.1

Other parameters are optional:

To define the grid it is necessary to describe the grid rectangle. Parameters have default
values. The rectangle is set using the following keywords:
• #PTSEPARATION – step size along X coordinate (is 1 by default).
• #RWSEPARATION – step size along Y coordinate (is 1 by default).
• #XORIGIN – X coordinate of the left bottom corner of the grid (is 0 by default).
• #YORIGIN – Y coordinate of the left bottom corner of the grid (is 0 by default).
• #ROTATION – rotation angle of the rectangle side along the X axis in the counter-
clockwise direction in degrees (is 0 by default).
• #DUMMY – NOVALUE marker (not defined by default).
• #SENSE – defines the method of converting a two dimensional array into one dimen-
sional.
The array can be compressed using base-90 method. Compression parameters are defined
by the keyword #GTYPE.
11.1.6. Import. GXF-3 Format 76

18.1
Example
===========================================
This is a comment area which is ignored by GXF readers.
===========================================
#POINTS
6
#ROWS
4
#PTSEPARATION
12.5
#RWSEPARATION
12.5
#XORIGIN
1750000.0
#YORIGIN
4250.0
#ROTATION
0.0
#UNIT_LENGTH
''ftUS'', 0.3048006096012
#MAP_PROJECTION
''NAD27 / Ohio North''
''NAD27'',6378206.4, 0.082271854, 0
''Lambert Conic Conformal (2SP) '', 40.4333333333, 41.7,
39.6666666667,
82.5, 609601.22
#MAP_DATUM_TRANSFORM
''NAD27 to WGS 84 (6)'', -8, 159, 175, 0, 0, 0, 1
#GRID
0 1 2 3 4 5
10 11 12 13 14 15
20 21 22 23 24 25
30 31 32 33 34 35
11.2. Export
Export a horizon to a file. There are two possibilities defining in Export to save horizons:
• Export All Horizons to Horizon Format (ASCII).
• Export Horizon to Horizon Format (ASCII).
Choosing the first option allows to save all available horizons and the second one allows to
save the selected horizon.
11.2. Export 77
18.1
11.2.1. Export All Horizons to Horizon Format (ASCII).

• Output Folder. Define the folder name where all horizons will be saved.
• Default Value. Special value indicating that the horizon in not defined in this place.
• Input Units. Define units (METRIC, FIELD, LAB) in which data will be saved.
11.2.2. Export Horizon to Horizon Format (ASCII).

• File Name. Define the folder/file name in which a horizon will be saved.
• Horizon. Define a horizon name for saving.
• Default Value.
• Input Units. Define units (METRIC, FIELD, LAB) in which input data will be saved.
11.3. Calculator
This section contains the tools used to generate a new object by mathematical calculations.
• Grid Properties. Gathers all the parameters which will define the plane grid.
• Angle, degree. Angle of rotation of the plane grid.
• Min. X/Y, m. Minimum X or Y coordinate in meters.
• Length along X/Y, m. Field used to set the minimum length of the plane which will
be generated.
• Step along X/Y, m. Field used to set the distance between the plane grid points along
X or Y axis.
• Autodetect by. Chose an object in the list if you want to use its size as dimensions
for the plane which will be generated. It is recommended to set this option for shifting
horizons.
• Autodetect. Autodetects the size of the object selected in the field Autodetect by.
Fills automatically the Grid Properties fields.
• The white field situated below Autodetect option is used to write the formula which
will define the plane to generate.
• Assistant fields. Gathers the objects and the options that can be used in the formula
11.2.1. Export All Horizons to Horizon Format (ASCII). 78

18.1
• Operators. List of the operators which can be used to compose the formula in the white
field situated below the Autodetect button.The exact syntax is displayed by clicking on
it.
• Functions. List of the mathematical functions which can be used to compose the
formula in the white field situated below the Autodetect button.The exact syntax is
displayed by clicking on it.
• Geometry. List of geometry variables and index which can be used to compose the
• The field with the object list can be used to integrate the objects to the computation.
Double-click on it to display the exact syntax.
11.4. Crop Horizon by Polygon

An initial horizon will be cut with the Polygon boundaries.
• Output. Result Horizon. Define the name of resulting horizon.
• Source Data:
– Input Horizon. Select a horizon for modification.

– Polygon. Choose the existed polygon as a boundary of a new horizon.
11.5. Interpolation
In the Designer for horizons the following interpolation methods are implemented:
• IDW;
• Kriging;
• SGS;
• Least Squares;
• Least Squares (by Point Set).
11.4. Crop Horizon by Polygon 79

18.1
11.5.1. Horizons: IDW Method

In this section a specification on implementation of the interpolation method to edit the object
is given. A general description of the method, formulas and details of the use of multipliers
and coefficients, mentioned in this section, are given in the section Multilayer Inverse Dis-
tance Weighting (IDW) method.
To interpolate a horizon the following parameters should be defined:
• Output. Horizon. Name of the resulting horizon.
• Residual. The residual map between an intersection point of the created horizon with
the well and the marker corresponding to the well. The map is shown in the Well
attributes list.
• Source data:
– Well Marker (except Least Squares interpolation (by Point Set)). Choose an
available marker for interpolation of its values.
– Well Filter. Use only markers corresponding to wells defined in the filter.
– Trend Horizon. Based on the horizon trend a new horizon will be built. Let’s the
function T (x, y) denotes a trend horizon, (xi , yi , zi ) are the coordinates of each
marker. Denoting D(x, y) as a function obtained by interpolation of ”residual”
between the marker and the trend, i.e. the values zi − T (xi , yi ) defined in (xi , yi )
are interpolated. Thus, the new horizon is the result of adding the function D(x, y)
to the trend function T (x, y): D(x, y) + T (x, y).
• Grid Properties:
– Angle, degrees. Rotation angle of the new coordinate system with respect to the
old one. In the new system a horizon will be built. See below the description of
Autodetect option.
– Min. X. Minimum X coordinate in the new coordinate system (METRIC: m,
FIELD: f t ).
– Length along X. Horizon’s length along X axis (METRIC: m, FIELD: f t ).
– Step along X. Grid step size in the X direction (METRIC: m, FIELD: f t ).
– Min. Y. Minimum Y coordinate in the new coordinate system (METRIC: m,
FIELD: f t ).
– Length along Y. Horizon length along Y axis (METRIC: m, FIELD: f t ).
– Step along Y. Grid step size in the Y direction (METRIC: m, FIELD: f t ).
• XY Margin. (METRIC: m, FIELD: f t ) See below the description of Autodetect

option.
11.5.1. Horizons: IDW Method 80

18.1
• Use Perforations. See below the description of Autodetect option. Notice that this
option is not available for Least Squares interpolation (by Point Set).
for the plane which will be generated.
• Autodetect. Automatic detection of horizon boundaries. Using maximum and minimum

X and Y coordinates of wells and horizon’s boundaries (if the option Trend Horizon
is activated) a minimum square rectangle is built and rotated by defined angle with
respect to the X axis. The obtained rectangle contains all markers and trend. Further,
the rectangle extends to the value defined by XY Margin in each direction, i.e. the
value is added to maximum coordinates and subtracted from minimum coordinates.
If the option Use Perforations is available and activated then for building a rectangle
the perforation intervals of wells will be only taken into account.
• Other Parameters. Power Parameter. This parameter is used in the formula of the
Multilayer IDW method.
11.5.2. Horizons: Kriging

and coefficients, mentioned in this section, are given in the section Kriging.
attributes list.
• Source data:
11.5.2. Horizons: Kriging 81

18.1
Autodetect option.
FIELD: f t ).
FIELD: f t ).

option.

Other Parameters define a specific of interpolation method:
• Kriging Type. Define a type of Kriging, which will be used to interpolate a horizon.
– Simple.
– Ordinary.
– Universal.
• Variogramm. It is possible to choose available variogram for interpolation. If there is

no variogram it is necessary to create it. To do this Go To Variogram Properties. Use
tab Others to define variogram’s parameters.
11.5.2. Horizons: Kriging 82

18.1
11.5.3. Horizons: SGS

is given. A general description of the method, formulas and details of the use of multipli-
ers and coefficients, mentioned in this section, are given in the section Sequential Gaussian
Simulation (SGS) method.
attributes list.
• Source data:
Autodetect option.
FIELD: f t ).
FIELD: f t ).

option.
11.5.3. Horizons: SGS 83

18.1


• Kriging Radius. (METRIC: m, FIELD: f t )
• Kriging Points.
• Random number.
11.5.4. Horizons: Least Squares method

ers and coefficients, mentioned in this section, are given in the section Least Squares method.
attributes list.
• Source data:
11.5.4. Horizons: Least Squares method 84

18.1
Autodetect option.
FIELD: f t ).
FIELD: f t ).

option.

A smoothness of interpolated horizon can be improved by varying coefficients in the

range [0.01, 100] (see formula of LSM).
• Coefficients:
11.5.4. Horizons: Least Squares method 85

18.1
– First Derivative.
– Second Derivative.
• Advanced settings. If this check-box is checked additional option Grid refinement

will be available. The choice of this option allows to improve an accuracy of horizon’s
interpolation, however, increases a computational time. An interpolation is carried out
Refinement Steps number of times. At initial interpolation step the number of points
in X and Y directions is defined:
– Start Count of Points by X.

– Start Count of Points by Y.
At the first interpolation step it is recommended to use a rough grid, i.e. the number of
points in X and Y directions should be minimal. At each iteration the number of points
in X and Y directions increases in such way that after defined number of iterations
(steps) the final number of points becomes equal to the number of horizon’s points.
11.5.5. Horizons: Least Squares interpolation (by Point Set)

attributes list.
• Source data:
Autodetect option.
11.5.5. Horizons: Least Squares interpolation (by Point Set) 86

18.1

FIELD: f t ).
FIELD: f t ).

option.

• Source data:
– Point Set. Each point has its (x, y, z) coordinates. The points are similar to the
markers, but they are not connected with any well. Therefore, there is no possi-
bilities to choose a well filter. As for the rest this option is the same as described
in the Least Squares method.

will be available. The choice of this option allows to improve an accuracy of horizon’s

11.5.5. Horizons: Least Squares interpolation (by Point Set) 87

18.1
(steps) the final number of points becomes equal to the number of horizon’s points.
Comment. If the point set (Point Set) defines grid nodes then it is recommended to use
the option Create Horizon by Pointset.
11.6. Horizons Adjustment to Markers

In some cases the built horizon does not pass through markers. In such case you can try
to eliminate residuals. The procedure of building the new horizon is similar to the building
horizon based on the trend horizon: values zi − T (xi , yi ) defined in (xi , yi ) are interpolated,
where T (x, y) is a trend function and (xi , yi , zi ) are marker coordinates. Finally, the trend
horizon will be shifted by obtained values.
Two correction methods are available:
• IDW method;
• Least Squares Method.
11.6.1. IDW method

and coefficients, mentioned in this section, are given in the section Multilayer IDW method.
To adjust a horizon the following parameters should be defined:
• Output Horizon. Name of resulting horizon.
the well and the marker corresponding to the well. The map is shown in the list Well
attributes.
• Source data:
– Input Horizon.
– Well Marker. Choose available marker for interpolation of its values.
– Well Filter.
11.6. Horizons Adjustment to Markers 88

18.1
11.6.2. Least Squares method

To adjust a horizon the following parameters should be defined:

the well and the marker corresponding to the well. The map is shown in the list Well
attributes.
• Source data:
– Input Horizon.
– Well Marker. Choose available marker for interpolation of its values.
– Well Filter.
Coefficients providing a smoothness of adjusted horizon are defined (see formula of
LSM) and varied in the range [0.01, 100].
• Coefficients:
• Discrepancies elimination:
– Iterations.
– Coefficient. At each iteration of algorithm the derivative coefficients are modified
by multiplying by this coefficient.
11.7.1. Rotate
It is possible to rotate a horizon by defined angle around the point.
• Output. Horizon. Choose a modifying horizon.
• Point (the horizon will be rotated around this point):
– X. (METRIC: m, FIELD: f t )
– Y. (METRIC: m, FIELD: f t )
• Angle, degrees. Horizon rotation angle.
11.6.2. Least Squares method 89

18.1
11.7.2. Translate
All horizon points are shifted in the same direction by the same distance.
• Output. Horizon. Choose a modifying horizon.
• Shift vector:
– X. Shift all horizon points in the X direction by the defined number of units of
length (METRIC: m, FIELD: f t ).
– Y. Shift all horizon points in the Y direction by the defined number of units of
length (METRIC: m, FIELD: f t ).
11.7.3. Smooth
The algorithm allows to smooth a selected horizon surface. If a rectangle is defined as:
X0 6 x 6 X1 ,Y0 6 y 6 Y1
and the regular grid is defined on the rectangle as:
pi j , i = 1, . . . , N, j = 1, . . . , M.
Let H is a horizon function defined on the two dimensional grid pi j and hi j is the
horizon value in the grid node pi j .
• Input Horizon. Smoothing horizon name.
• Method:
– Moving average. Smoothed horizon H̃ is defined on the same grid with the
following values:
h
h̃i j = ∑ Nklkl .
|p −p |<R ij kl
Here Nkl is a grid nodes number located within the circle of the radius R (dialogue
parameter) with the center at the point pi j , i.e. Nkl = ∑ 1
|pi j −pkl |<R
– Splines. First, the coarse grid with step in x , y directions equal to the radius
(dialogue parameter) is constructed. Then, the horizon H1 is defined on the coarse
grid based on H values defined on the coarse grid nodes. The smoothed horizon
H̃ is calculated using the bicubic spline interpolation based on H1 values defined
on coarse grid nodes.
• Radius. (METRIC: m, FIELD: f t )
11.7.2. Translate 90
18.1
11.7.4. Pull Up Horizon to Marker

The algorithm allows to modify a horizon locally by pulling it to the selected marker.
• Result Horizon. Name of resulting horizon.
• Source Horizon. Name of source horizon.
• Well Marker. Selected marker name which the horizon is pulled to.
• Well Filter. Use markers corresponding to the wells selected in the filter.
• Radius of Changing. (METRIC: m, FIELD: f t ) Modify a horizon within the defined

radius of the circle with the center at the marker projection point on the source horizon.
• Pulling Type:
1. Simple Pulling. Horizon points in the vicinity of the pulling point (i.e. the point
of the marker projection on the source horizon) is pulled to the marker by distance
calculated as:
√
(2d 3 − 3d 2 + 1)h p,
where:
– d is the distance from the horizon’s point to the nearest marker point divided
by the radius (Radius of Changing). If the distance d is larger than the
radius then the horizon’s point will be excluded from the algorithm.
– h is the nearest to the horizon point marker depth.
– p is Power parameter defined in graphical interface. It determines the
obtained horizon curvature in the area bounded by radius.
2. IDW Interpolation.
– Power parameter. This parameter is used in the formula of the Multilayer
IDW method.
3. Least Squares Interpolation. The list of parameters is common for described
above.
11.8. Auxiliary Calculations

11.8.1. Create Horizon by Pointset
If the point set (Point Set) defines grid nodes then it is recommended to use this option.
• Output. Horizon. Name of resulting horizon.
• Source Data. Point Set. Set of points which will be used to build the horizon.
11.7.4. Pull Up Horizon to Marker 91

18.1
11.8.2. Create Horizon by Seismic Horizon

This option allows to convert a surface in time (seismic horizon) into a surface in depth,
using check-shot data. The following parameters must be specified:
• Output. Horizon. Name of resulting horizon.
• Log. Check-shot log which will be used to build the horizon.
• Log Type. Define the log type (one way ot two-way time).
• Well Filter. Selection of the well filter containing all the wells with check-shot data
which will be used in the computation.
• Seismic. Selection of the seismic data used for the picking.
• Seismic Horizon. Selection of the seismic horizon which will be converted in depth.
The object has to be a 3D correlated horizon (not picked lines).
11.8.2. Create Horizon by Seismic Horizon 92

18.1
12. 2D-Maps
In 2D Maps menu to work with maps the following possibilities are available:
• Import;
• Calculator;
• Voronoi Regions 2D Map by Markers;
• Export;
• Interpolation;
• 2D Map Adjustment to Wells Attributes;
• Auxiliary Calculations (calculations 2D Map by Property and Azimut Map by Poly-

gons).
12.1. Import
2D Maps can be loaded in the following formats:
• Format:
– CPS Format;
– 2D map ASCII Format;
– GRD Format.
Formats with the same names for horizons and 2D Maps are identical. Descriptions of
corresponding formats and file examples are presented in the section Horizons.Import.
• File Name. Show full paths of files containing an information about a 2D Map.
• NOVALUE. Special marker (equals 99999 by default) is used to indicate that a 2D

Map value does not exist in the data table.
12. 2D-Maps 93
18.1
12.2. Calculator
This section contains the tools used to generate a new object by mathematical calculations.
• Grid Properties. Gathers all the parameters which will define the plane grid.
• Angle, degree. Angle of rotation of the plane grid.
• Min. X/Y, m. Minimum X or Y coordinate in meters.
• Length along X/Y, m. Field used to set the minimum length of the plane which will
be generated.
• Step along X/Y, m. Field used to set the distance between the plane grid points along
X or Y axis.
for the plane which will be generated. It is recommended to set this option for shifting
horizons.
• Autodetect. Autodetects the size of the object selected in the field Autodetect by.
Fills automatically the Grid Properties fields.
• The white field situated below Autodetect option is used to write the formula which
will define the plane to generate.
• Assistant fields. Gathers the objects and the options that can be used in the formula
• Operators. List of the operators which can be used to compose the formula in the white
field situated below the Autodetect button.The exact syntax is displayed by clicking on
it.
• Functions. List of the mathematical functions which can be used to compose the
• Geometry. List of geometry variables and index which can be used to compose the
• The field with the object list can be used to integrate the objects to the computation.
Double-click on it to display the exact syntax.
12.2. Calculator 94
18.1
12.3. Voronoi Regions 2D Map by Markers

Voronoi Regions is the domain decomposition approach. The map is decomposed to regions
(according to the selected initial points number) in such way that the boundary between two
neighboring regions is perpendicular to the line connecting initial points (domain centers)
and crosses this line in the middle.
As initial points wells (their projections on the 2D map) can be used (e.g. to estimate
resources in the well area (well resources in the Voronoi region), or well drainage regions).
The description of this option for the dynamic model see in the training tutorial 4.6 How To
Use Voronoi Diagrams.
In this calculation as initial points markers are used (regions are built based on marker
depths). Based on marker projections on the plane the Voronoi Regions 2D Map is built.
This map can be used to create a horizon without an interpolation
• Output. 2D Map. Name of resulting Voronoi Regions 2D Map.
• Source Data:
– Marker. Marker based on which the Voronoi Regions 2D Map will be built.
– Well Filter. Use markers corresponding to the wells selected in the filter.
• Dimensions:
– Count of Points by X. Grid nodes number in the X direction.

– Count of Points by Y. Grid nodes number in the Y direction.
• Bounds:
– Minimal X Coordiante. Minimum X coordinate of the map (METRIC: m,

FIELD: f t ).
– Maximal X Coordiante. Maximum X coordinate of the map (METRIC: m,
FIELD: f t ).
– Minimal Y Coordiante. Minimum Y coordinate of the map (METRIC: m,
FIELD: f t ).
– Maximal Y Coordiante. Maximum Y coordinate of the map (METRIC: m,
FIELD: f t ).
• Autodetect. Automatic detection of map boundaries. Based on maximum and minimum

X and Y coordinates of marker projections, respectively, the minimum square rectangle
is built with its sides parallel to the OX and OY axes and containing marker projections.
• Use Radius. Maximum radius of one region (METRIC: m, FIELD: f t ).
12.3. Voronoi Regions 2D Map by Markers 95

18.1
12.4. Export
Export of 2D Map into the file.
• 2D Map ASCII Format.
• File Name. File name for the 2D map export.
• 2D Map. 2D map which will be exported.
• Default Value. Special number marker is used to indicate that a map value does not
exist in the data table.
12.5. Interpolation
In the Designer for 2D Maps the following interpolation methods are implemented:
• 2D Maps: IDW Method;
• 2D Maps: Kriging;
• 2D Maps: SGS Method;
• 2D Maps: Least Squares method.
12.5.1. 2D Maps: IDW Method

To interpolate a 2D Map the following parameters should be defined:

• Output:
– 2D Map. Name of resulting map.

– Residual. The residual map between an intersection point of the created 2D Map
with the well and the marker corresponding to the well. The map is shown in the
list Wells Attributes.
• Source Data:
– Well Attribute. Choose available attribute for an interpolation of its values.

12.4. Export 96
18.1
– Trend 2D Map. Based on the trend map a new 2D Map will be built. Denoting
T (x, y) as a trend map function and (xi , yi , zi ) as the coordinates of attribute the
”residual” between attribute and trend, i.e. values zi − T (xi , yi ) defined in (xi , yi ),
are interpolated and D(x, y) function is obtained. Thus, the new map is the result
of adding D(x, y) function to the trend function T (x, y), i.e D(x, y) + T (x, y).
– Angle, degrees. Rotation angle of the new coordinate system with respect ot the
old one. In the new system a 2D map will be built. See below the description of
Autodetect option.
FIELD: f t ).
– Length along X. Horizon length along X axis (METRIC: m, FIELD: f t ).
FIELD: f t ).
option.
• Use Perforations. See below the description of Autodetect option.
• Autodetect. Automatic detection of 2D Map boundaries. Using maximum and mini-
mum X and Y coordinates of the well and the 2D Map boundaries (if the option Trend
2D Map is activated) a minimum square rectangle is built and rotated by defined angle
with respect to the X axis. The obtained rectangle contains all markers and the trend.
Further, the rectangle extends to the value defined by XY Margin in each direction, i.e.
the value is added to maximum coordinates and subtracted from minimum coordinates.
If option Use Perforations is activated then building a rectangle wells perforation
intervals will be only taken into account.
12.5.2. 2D Maps: Kriging

To interpolate a Map the following parameters should be defined:
12.5.2. 2D Maps: Kriging 97

18.1
• Output:
• Source Data:
Autodetect option.
FIELD: f t ).
FIELD: f t ).
option.
12.5.2. 2D Maps: Kriging 98

18.1

• Kriging Type. Define a type of Kriging, which will be used to interpolate a 2D Map.
– Simple.
– Ordinary.
– Universal.

12.5.3. 2D Maps: SGS Method

Simulation (SGS) method.
To interpolate a 2D Map the following parameters should be defined:
• Output:

• Source Data:

Autodetect option.
FIELD: f t ).
12.5.3. 2D Maps: SGS Method 99

18.1

FIELD: f t ).

option.


• Kriging Radius. (METRIC: m, FIELD: f t )
• Kriging Points.
• Random number.
12.5.4. 2D Maps: Least Squares method

To interpolate a Map the following parameters should be defined:
• Output:
12.5.4. 2D Maps: Least Squares method 100

18.1
• Source Data:
Autodetect option.
FIELD: f t ).
FIELD: f t ).
option.
A smoothness of interpolated 2D Map’s values can be improved by varying Coefficients

in the range [0.01, 100] (see formula of LSM):
12.5.4. 2D Maps: Least Squares method 101

18.1
• Coefficients:

will be available. The choice of this option allows to improve an accuracy of 2D Map’s

(steps) the final number of points becomes equal to the number of 2D Map’s points.
12.6. 2D Map Adjustment to Wells Attributes

Two methods are available:
• IDW;
• Least Squares.
12.6.1. IDW method

To adjust a Map the following parameters should be defined:
• Output:
– Output. 2D Map. Resulting Map.

– Residual. The residual map. The map will be available in the section Wells
Attributes.
• Source data:
– Input. 2D Map. Initial Map.

– Well Attribute. Well attribute map.
12.6. 2D Map Adjustment to Wells Attributes 102

18.1

To adjust a 2D Map the following parameters should be defined:
• Output:
– Output. 2D Map. Resulting 2D Map.

– Residual. The residual 2D Map. The map will be available in the section Wells
Attributes.
• Initial data:
– Input. 2D Map. Initial Map.

– Well Attribute. Map of well attribute.
Coefficients providing a smoothness of adjusted Map are defined (see formula of LSM)
and varied in the range [0.01, 100].
• Coefficients:
• Discrepancies elimination:
– Iterations.
– Coefficient. At each algorithm iteration derivative coefficients are modified by
multiplying by this coefficient.

18.1
12.7.1. Rotate
A rotation of the 2D map by the specified angle around the defined point.
• Output. 2D Map. Choose modified map.
• Point around which the map will be rotated:
– X. (METRIC: m, FIELD: f t )
– Y. (METRIC: m, FIELD: f t )
• Angle, degrees. Rotation angle of 2D map.
12.7.2. Translate
All map points are shifted in the same direction by the same distance.
• Output. 2D Map. Choose modified map.
• Shift vector:
– X. Shift all map points in the X direction by the defined number of units of length
– Y. Shift all map points in the Y direction by the defined number of units of length

12.8.1. 2D Map by Property
The calculation is created the 2D Map based on the selected property.
• 2D Map. Name of 2D Map for the calculation.
• Method.Method, which is used to build 2D Map . If type Continuous is chosen in

Property Type (defined below), the following methods are available:
– Average. Consider a vertical line coming from the two dimensional grid node.
Blocks i crossing by the line and satisfying the filter condition (which will be
defined below) are considered. Based on the property values c(i) and blocks
height height(i) the map value at the grid node is calculated as:
∑ c(i) · height(i)
M= .
∑ height(i)

18.1
– Volume-height. Consider a vertical line coming from the two dimensional grid
node. Blocks i = 1, ... crossing by the line and satisfying the filter condition
(defined below) are considered. Based on the property’s values c(i), blocks’
height height(i) and volumes volume(i) the 2D Map value M at the grid node is
calculated as:
c(i) · height(i)
M=∑ .
volume(i)
– Net. Based on the same data as for the Average method the value of 2D Map M
at the grid node is calculated as:
M = ∑ c(i) · height(i).
– Sum. Based on the same data as for the Average method the value of 2D Map
M at the grid node is calculated as:
M = ∑ c(i)
If type Discrete is chosen:

– Average. Consider a vertical line coming from the two dimensional grid node.
Blocks i crossing by the line and satisfying the filter condition (which will be
defined below) are considered. Based on the property values c(i) and blocks
height height(i) the 2D Map value M at the grid node is calculated as:
∑ c(i) · height(i)
M= .
∑ height(i)
– Top. Consider a vertical line coming from the two dimensional grid node. The
set of, intervals which are the line intersection with the 3D grid, is calculated. All
intervals, which are not the result of line intersection with blocks, do not satisfy
the filter condition and a facies value in them equals to the defined value, are
skipped. The minimum boundary of the top interval is supposed to be a 2D map
value at the specified grid node.
– Bottom. Consider a vertical line coming from the two dimensional grid node. The
set of intervals, which are the line intersection with the 3D grid, is calculated. All
intervals, which are not the result of line intersection with blocks, do not satisfy
the filter condition and a facies value in them equals to the defined value, are
skipped. The maximum boundary of the top interval is supposed to be a 2D map
value at the specified grid node.
– Thickness. Consider a vertical line coming from the two dimensional grid node.
The set of intervals, which are the line intersection with the 3D grid, is calculated.
All intervals which are not the result of line intersection with blocks, do not satisfy
the filter condition and a facies value in them equals to defined value are skipped.
The sum of intervals length is supposed to be a 2D map value at the specified
grid node.
12.8.1. 2D Map by Property 105

18.1
– Proportion. Consider a vertical line coming from the two dimensional grid node.
The set of intervals, which are the line intersection with the 3D grid, is calculated.
All intervals, which are not the result of line intersection with blocks, do not
satisfy the filter condition, are skipped. The sum of intervals length is calculated.
Further, all intervals, which are not the result of line intersection with blocks, a
facies value in them equals to defined value, are skipped. The sum of intervals
length is calculated. The ratio between second and first sum is considered to be a
value of 2D Map at the specified grid node.
• Smooth result. If the check-box is checked the 2D Map will be smoothed. The map
value in each node is averaged using values at neighboring nodes.
• User Cut. 2D map will be built based on the block satisfying to the defined filter.
• Property. Choose property which will be used to build 2D Map.
• Property Type. Property’s types are:
– Continuous. Any numerical values can be used for Property.

– Discrete. Integers can be used for Property.
12.8.2. Azimut Map by Polygons

This calculation allows to create a map representing azimuts, using polygons and a value of
dominant azimut (used as a trend). First, the tangent to the curves is computed for each point
and then, the azimuts of these tangents are interpolated. The azimut is defined as the angle
between the direction and the Y axis. This map can be used for facies modeling, using the
methods Facies Analysis and Discrete properties modeling: Kriging 3D and Facies Analysis
and Discrete properties modeling: SGS 3D.
• Output. 2D-Map. Name of the resulting map;
• Normalize result. The result is normalized in order to obtain angles inferior to 360;
• Source Data. This field is used to indicate the polygons which will be used for the
computation. A polygon can be selected from the list of available polygons by double
clicking on the white field under Polygon. The use of the polygon for the computation
has to be confirmed by cheking the box Use;
• Dominant Azimut, degrees. Value of the dominant azimut in degrees. The azimut is
the angle between Y axis and the direction;
• Set Grid 2D Properties.
• 2D Grid: parameters for the 2D grid. The settings can be detected automatically using
the option Autodetect by (see below).
12.8.2. Azimut Map by Polygons 106

18.1
◦ Angle, degrees. Rotation angle of the new coordinate system with respect to the
old one. Corresponds to the angle between the X axis and the border of the
constructed grid. In order to set an automatic value computed from an object, the
icon on the right has to represent a closed padlock. See below the description of
Autodetect option.
◦ Min. X. Minimum X coordinate of the grid in the new coordinate system (METRIC:
m, FIELD: f t ).
◦ Length along X. Grid length along X axis (METRIC: m, FIELD: f t ).
◦ Step along X. Grid step size in the X direction (METRIC: m, FIELD: f t ).
◦ Min. Y. Minimum Y coordinate of the grid in the new coordinate system (METRIC:
m, FIELD: f t ).
◦ Length along Y. Grid length along Y axis (METRIC: m, FIELD: f t ).
◦ Step along Y. Grid step size in Y direction (METRIC: m, FIELD: f t ).
◦ Autodetect by. Selection of the object which size will be used to compute the grid
(for automatic definition);
◦ XY Margin. (METRIC: m, FIELD: f t ) See below the description of Autodetect
option.
◦ Autodetect. Automatic detection of boundaries for the 2D grid, using the object
defined in Autodetect by field. Maximum and minimum coordinates (X, Y) are
detected. The minimum rectangle rotated by the defined Angle with respect to the
OX axis and enclosing the object with given XY Margin is built.
12.8.2. Azimut Map by Polygons 107

18.1
13. Seismic
In Calculations menu to work with seismic the following possibilities are available:
• Import.
For more information about working with seismic data, see the training course How to
do seismic interpretation
13.1. Import
The seismic can only be loaded in SEG-Y format.
• Name. Define the name of the loaded seismic.
• File Name. Full path to the seismic file.
• Preview:
– Binary header. Preview of the binary header of the loaded Seg-y containing the
descriptor and the value columns.
– Text header. Preview of the text header containing the text information about the
data.
– Trace header. Preview of the trace header containing information about the seis-
mic record.
• Type:
– Type. Selection of the type of data (2D or 3D).

– Start Inline. Number of the first inline.
– Last Inline. Number of the last incline.
– Start Crossline. Number of the first crossline.
– Last Crossline. Number of the last crossline.
• Geometry:
– Angle. Setting of the angle of the seismic.

– Min X. Minimum X coordinate of the seismic line or cube.
– Min Y. Minimum Y coordinate of the seismic line or cube.
– Length X. Length of the seismic line or cube along X axis.
– Length Y. Length of the seismic line or cube along Y axis.
– Reverse Crosslines. Reverse the direction of increasing crossline numbers, cf.
Fig.10
13. Seismic 108

18.1
Figure 10. A - loaded seismic without the Reverse Crossline option. B - loaded seismic.
Reverse Crossline option is activated. The same inline is displayed.
– Reverse Inline. Reverse the direction of increasing inline numbers.
• Processing:
– Inline position in the header. Setting of the inline position.

– Crossline position in the header. Setting of the crossline position.
– Inline Position Length. Setting of the inline position length in the header.
– Crossline Position Length. Setting of the crossline position length in the header.
– X Position in Header. Setting of X position in the header.
– Y Position in Header. Setting of Y position in the header.
– X Position Length. Setting of X position length in the header.
– Y Position Length. Setting of Y position length in the header.
– Autodetect. Autodetection of Geometry, Processing and Type parameters from
the data.
13.1. Import 109

18.1
14. Seismic Horizons

In Seismic tab, to work with seismic horizons, the following possibilities are available:
• Create a new seismic horizon;
• Interprete Seismic Horizons.
In Settings tab, to work with seismic horizons, the following possibilities are available:
• Autotracking Parameters;
• Line and projection display.
In Calculations menu, to work with the following possibilities are available:
• 3D Correlation.
14.1. Create a new seismic horizon

In seismic tab, the button Create New Seismic Horizon allows to add a new empty
seismic horizon to the geometry objects hierarchy below Seismic.
14.2. Seismic Interpretation

In Interprete Seismic Horizons dialog, the following options are available:
• Seismic Horizon. Selection of the seismic horizon which will be edited;
• Manual Interpretation. Allows to interpret manually a seismic horizon. Left

mouse button click allows to select the points on the seismic in seismic tab, double
left click can be used to finish the selection and the right mouse button click allows to
delete the selection;
• Guided Autotracking. Allows to interpret a seismic horizon by seeds picking.

The left button allows to select the seeds, the double click propagates the picking to
the reflector between the seeds, according to the Autotracking Parameters which are
set;
• Seeded 2D Autotracking. For this method, the selection of one point on the
reflector (by double left clicking) fits automatically the picking to the part of the
reflector which has similar phase parameters as the seed, according to the Autotracking
Parameters which are set;
• 3D Autotracking. This method allows to create a horizon in time from the

picking. Picked seeds in 2D are interpolated to 3D by double clicking, according to the
Autotracking Parameters which are set;
14. Seismic Horizons 110

18.1
• Eraser Tool. Erases the parts of the picking which are selected by left mouse
click. This tool deletes only the points in 2D, whatever the method;
• Undo Button. Undo the last steps performed;
• Redo Button. Redo the last steps performed.
14.3. Autotracking parameters

To compute Seismic Horizons by semi-automatic methods, the following parameters are
available:
• Signal Feature. Selection of the type of reflector which is interpreted: peak (positive
reflection coefficient), trough (negative reflection coefficient) or peaks and troughs.
• Seed Confidence. If this option is activated, values calculated by autotracking will

be constrained by amplitudes. Seed Confidence specifies the minimum value for the
seismic amplitude, as a percentage of the seed points values. Minimum and maximum
values for the amplitude are determined for the entire field. For instance, if the seed
confidence value is 30% and maximum and minimum values area 120 and -120,
autotracked values will not be outside [-120;-36 ∪ 36;120], where 120 and -120
correspond to minimum and maximum possible amplitudes and 36 corresponds to 30%
of 120, see Figure 11.
Figure 11. Seed confidence definition, example for seed confidence value of 30%, auto-
tracked values will not be outside the blue rectangles
• Window Confidence. Represents the vertical degree of freedom for the autotracking.
The less is this value, the less calculated values are varying from the seed value, see
Figure 12.
14.3. Autotracking parameters 111

18.1
Figure 12. Window Confidence definition, example for a window confidence value of 20 ms.
Seeds are represented in blues. Autotracked values cannot be outside the limits represented
in dashed lines and located at 10 ms upwards and 10 ms downwards
• Use Wavelet tracking. If this option is activated, the calculated values by autotracking
will be constrained by the wavelet.The wavelet tracking method compares traces around
the selected point (within the correlation window). The picking will be propagated to
a neighboring trace if the original trace and the neighboring one have a correlation
coefficient value which equals to at least the value set as Correlation Quality.
If no options (Seed Confidence or Wavelet tracking) is used, the picking is propagated

without constraints to all the neighboring peaks or troughs in 2D or 3D.
14.4. Line and Projection display

For each Seismic Horizon, the following parameters can be set in Settings panel:
• Line Width. Setting of the line width in mm.
• Line Color. Setting of the color for each object.
• Line Style. Setting of the style.
• Show Projection. If this option is selected, the projection of already interpreted lines
will be visible.
• Projection Line Width. Setting of the projection line width in mm.
• Projection Color. Setting of the color for the projection.
• Projection Line Style. Setting of the projection line style.
14.4. Line and Projection display 112

18.1
14.5. 3D Correlation
This option is accessible from Calculations menu and allow to convert line picking into a
surface in time. The following parameters must be specified:
• Seismic. Selection of the seismic which was interpreted.
• Seismic Horizon. Selection of the picking which will be converted.
• Seismic Horizon 3D. Name of the 3D seismic horizon which will be created.
• Autotracking Parameters. Selection of the methods which will be used to compute

the seismic horizon. See Autotracking Parameters for more details.
• Load SEG-Y in Memory. If this option is activated, the entire SEG-Y file is loaded
in the memory.
14.5. 3D Correlation 113

18.1
15. Polygons
In Calculations menu to work with polygons the following possibilities are available:
• Import;
• Export;
• Polygons Union;
• Polygons by Point Set;
• Set Polygon Z-Coordinates by Depth;
• Set Polygon Z-Coordinates by Horizon;
• Transform Polygon.
15.1. Import
Polygons can be loaded in the following formats:
• Single Polygon File (Text file);
• From .bln files;
• TKS Polygons;
• Polygon lines (ASCII);
• CPS-3 lines;
• Import Polygons from Shapefile.
15.1.1. Single Polygon File (Text file)

The text file should contain 3 columns: X coordinate, Y coordinate and Z coordinate.
Example
9534534.880176 4999851.081244 0.000000
9534518.919362 5000070.985790 0.000000
9534905.525740 4999987.634873 0.000000
9534905.525740 4999773.050599 0.000000
9534768.972111 4999679.059141 0.000000
• Polygon. Define the name of the loaded polygon.
15. Polygons 114

18.1
• File. The full path to file containing the file, which defines the polygon.
• Preview:
– Number of Lines. Number of lines shown in the Preview window.

– Input Units. Choose a system of units (METRIC, FIELD, LAB).
• Polygon Is Closed. If the check-box of this option is checked then the loaded polygon
will be shown in closed form.
15.1.2. From .bln files

• Name Prefix.
• Remove Rows. Remove a file from the list.
The file format is coincide with the format described for faults.
15.1.3. TKS Polygons

Format description.
The file consists of a header and description of polygons. The header consists of two
parts. Among other thing the number of polygons is defined in the header’s first part. The
number of polygons is followed by keyword Count. The header first part is terminated by
keyword Next ID.
In the header’s second part two lines are used to define main parameters for each polygon.
The polygon name is defined in the first line. The polygon number is defined in the second
line (in this line the second number is not used).
The header is followed by polygons data (in the order listed in the header). The first line
contains parameters for visualization and is not used. The polygon point number is defined
in the second line. Further, points coordinates are given; each point is defined by X and Y
coordinates. The space is a delimiter.
15.1.2. From .bln files 115

18.1
Example
40 File Definition Type
1 Version 7.0
3 Count
43 Next ID
Polygon A
40,107
Polygon B
41,1
Polygon C
42,1
25 0 3 6 5 7257866.000000 21041.038499 1.000000
5
8774.000000 15604.000000 7753.000000 14963.000000 6793.000000
14260.000000 6129.000000 14149.000000 5539.000000 13486.000000
0 0 3 58 1 11468610.000000 14615.461954 1.000000
6
19308.000000 7482.000000 18348.000000 4752.000000 21666.000000
4824.000000 22332.000000 8070.000000 22260.000000 9552.000000
19308.000000 7482.000000
12 0 3 50 0 16117524.000000 16296.022271 1.000000
6
1074.000000 3792.000000 3732.000000 -198.000000 5430.000000
2760.000000 5946.000000 4380.000000 2994.000000 6078.000000
1074.000000 3792.000000
0
0
15.1.4. Polygon lines (ASCII)

The description of the format is given in the section from Curves (a format type to import
faults).
15.1.5. CPS-3 lines

The description of the format is given in the section from Curves (a format type to import
faults).
15.1.6. Import Polygons from Shapefile

Polygons can also be loaded from Shapefiles.
The shapefile format is a geospatial vector data format. A shapefile contains a main file,
an index file, and a dBASE table. The main file is a description of the object geometry and
15.1.4. Polygon lines (ASCII) 116

18.1
contains a list of vertices. The index file provides a positional index of the object geometry,
while the dBASE table is a list of the object attributes.
The following parameters have to be specified:
• File Name. Complete path to the .shp file;

• Name prefix. Name of the loaded object in Designer;
• Add Rows. Add a file;
• Remove Rows. Remove a file. The removed file will not be loaded;
• Ignore index file. This option can be used to force the visualization of the object in
case of corrupted index files;
• Select Coordinate Reference System. These field is active when a coordinate system
is set for the entire project and allows to set a coordinate system (CRS) for the file,
which can differ from the project CRS. To change the file CRS, select a CRS from the
list available by clicking on the ellipsis button. The project CRS can be modified, as
described in the section 2.2.
15.2. Export
Saving polygons into a file. By default, all the exported polygons have Z coordinates equal
to 0.
1. Text File.
• File Name. The full path to file, in which the polygon will be exported.
• Curve. Name of the curve to be saved.
2. Export all curves.
• Output Folder. The full path to file, in which all curves will be saved.
15.3. Polygons Union

• Result Polygon. Name of the resulting polygon. All points inside the polygon will be
included in the union.
• United Polygons. Set of united polygons.
– Use. If the check-box is not checked then, a selected polygon will not be included
in the union.
– Polygon. Selection of the polygon name which will be included in the union.
– Add Rows. Add the file with polygon parameters.
– Remove Rows. Delete the chosen file from the list.
15.2. Export 117

18.1
15.4. Polygons by Point Set

This option in Calculations window allows to generate a polygon using point sets as input
data. The polygon will be generated as a convex envelop of a chosen point set.
• Result Polygon. Name of the resulting polygon.
• Point Set. Selection of the point set which will be used to create the polygon.
• Margin. First to create the polygon by pointset the convex envelop of point set is
created, then this margin is added to the envelop from all sides (in meters).
15.5. Set Polygon Z-Coordinates by Depth

This calculation allows to add a Z coordinate value to the polygons by indicating a constant
depth. All the nodes of the polygons will present the same depth.
• Polygon. Select the polygon from the list;
• Depth. Indicate the polygon depth.
15.6. Set Polygon Z-Coordinates by Horizon

This calculation allows to add a Z coordinate value to the polygons by projecting the polygon
on an existing horizon. Each polygon node will present a Z coordinate value according to
the depth and the geometry of the horizon.
• Add Nodes With Step. This option is used to add nodes on the polygon. The points
will be added to the polygon according to the step which will be indicated in this field
(in project units). It is recommended to use this option if the polygon contains few
points, otherwise the polygon will not follow the horizon curvature;
• Polygon. Select the polygon from the list;
• Horizon. Select the horizon on which the polygon will be projected;
• Default Depth. Indicate the depth which will be assigned to the polygon in the areas
where the horizon is not defined.
15.7. Transform Polygon

This calculation allows to rotate, scale and translate a polygon. The following options are
available:
• Result Polygon. Enter the name of the resulting polygon;
15.4. Polygons by Point Set 118

18.1
• Source Polygon. Select the source polygon;
• Transformation Type. Select the transformation which will be applied to the polygon.
The following transformations are available:
– Shift. All the points of the polygon will be shifted according to the translation
vector which is set in the fields X and Y;
– Rotate. All the points of the polygon will be rotated in the trigonometric direction
according to the rotation which will be defined in the fields Center X, Y and in
Angle. The angle is measured from the Y axis;
– Scale. The polygon will be scaled according to the scale coefficient which is en-
tered in the field Scale coefficient and the center specified by X and Y coordinates
entered in the fields Center X and Center Y.
15.7. Transform Polygon 119

18.1
16. Aquifers
In Calculations menu to work with aquifers the following possibilities are available:
16.1. Create
Calculate an aquifer by polygon.
• Aquifer. Name of the created aquifer.
• Direction. Choose the direction of aquifer’s connections to blocks.
• User Cut. Aquifer will be created only in blocks satisfying to the defined filter. The
filter can be created using the tab User Maps of model Grid menu (Geometry Objects
tab).
• Polygon. Polygon based on which an aquifer will be calculated. Blocks included in the
aquifer should satisfy the following conditions:
– if part of block face is in the polygon.

– including blocks in the aquifer depends on above mentioned option Direction.
For example, if the check box I+ is checked then including in the aquifer blocks
are satisfied to above condition and ”visible” from the side placed at I = Ni , i.e.
the boundary with the maximum grid coordinate I .
Saving a dynamic model the connected aquifer is saved using keywords AQUAN-
CON (see 12.17.11), AQUGP (see 12.17.14). Aquifer Settings are saved using keywords
AQUANCON (see 12.17.11) and AQUCT (see 12.17.9) (Carter-Tracy model) or AQUFETP
(see 12.17.6) (Fetkovich model), AQUCHWAT (see 12.17.3) depending on the aquifer type.
16.2. Aquifer Settings

After creating aquifer its properties should be defined. Aquifer Settings dialogue is available
in the context menu of created aquifers by right clicking on the selected aquifer.
At the left part of the dialogue a list of aquifers (Aquifer Name) and their types (Aquifer
Type) is available. Three types of aquifer can be set: Fetkovich, Carter-Tracy and Constant
Head/Pressure Water. The aquifer’s type can be chosen in this list. At the right part main
settings can be defined. For all the aquifer types some settings are common and listed below:
• Aquifer influx coefficient. See the description of the 9-th parameter of the keyword
AQUANCON (see 12.17.11).
• Use Default. If this option is activated then the aquifer influx coefficient is equal to
default value, 0.
16. Aquifers 120

18.1
• Aquifer influx multiplier. See the description of the 10-th parameter of the keyword
AQUANCON (see 12.17.11).
• Allow connections from faces connected with active blocks. See the description of
the 11-th parameter of the keyword AQUANCON (see 12.17.11).
16.2.1. Carter-Tracy Aquifer Settings

All settings correspond to 2-13 parameters of the keyword AQUCT (see 12.17.9).
16.2.2. Fetkovich Aquifer Settings

All settings correspond to 2-9 parameters of the keyword AQUFETP (see 12.17.6).
16.2.3. Constant Head/Pressure Water Aquifer Settings

All settings correspond to 2-6 parameters of the keyword AQUCHWAT (see 12.17.3).
16.2.1. Carter-Tracy Aquifer Settings 121

18.1
17. Faults
In Calculations menu to work with faults the following possibilities are available:
• Import;
• Smooth Fault Surface;
• Ruled Fault by Curves 2D;
• Export.
• Auxiliary Calculations.
The following possibilities are available to set fault parameters and to edit faults:
• Fault Settings;
• Fault Editing.
17.1. Fault Settings

The following Faults Settings are available by right mouse button click on Faults in Ge-
ometry Objects:
• Fault. List of the faults which are present in the project;
• Transm. Mult. Transmissibility multiplier value for each fault. Second parameter of
the keyword MULTFLT (see 12.2.39) which will be added to the model. This field can
be edited from the interface by double clicking on it;
• Diffus. Mult. Diffusivity multiplier value for each fault. Corresponds to the third
parameter of the keyword MULTFLT (see 12.2.39) which will be added to the model.
This field can be edited from the interface bu double clicking on it;
• Threshold Pres. Threshold pressure value for each fault. Corresponds to the second
parameter of the keyword THPRESFT (see 12.2.40) which will be added to the model.
This field can be edited from the interface by double clicking on it;
• Fault Renaming Allows to edit fault names in Designer Interface:
– Reduce to 8 symbols. Reduce the name of the fault in Designer to 8 symbols. If

Change Left Part of Word is checked, the 8 first symbols of the name are left. If
not, the 8 last are left.
– Find What Replace With. Allows to edit the name of the faults in the interface.
The symbols which are entered in the field Find What are replaced by the one
entered in Replace with when the button Replace is pressed. These operations
can be undone using the button undo.
17. Faults 122

18.1
17.2. Fault Editing

The Fault Edit menu is available in 3D view and the Edit Fault button is situated on the
right panel ( ). To edit the fault, select the proper fault in the Fault list, click on a node,
select one of the modes and drag the node in 3D. The following options are available in the
dialog:
• Fault. Select the fault to edit from the list of displayed faults. Only the selected fault
can be edited;
• Control Size. Set the size of the sphere which indicates the node to be edited. This
parameter is a visualization tool and has no influence on the editing result;
• Do Not Use Fixed Control Size. If this option is activated, the yellow sphere indicating
the edited node will be displayed with a fixed size remaining the same while you zoom
in or out and which will be regulated by the Control Size parameter. This option is a
display tool and has no influence on the fault editing;
• Apply Changes When the Mouse is Released. This option is active for the Per-
pendicular to Fault and With Arbitrary Direction options. It allows to apply the
changes are applied only when the mouse is released. If the option is not activated, the
changes apply automatically once the node is dragged in space;
• Move the Whole Stick. Allows to edit a whole fault stick. If this option is not
activated, only the selected node and potentially the nodes situated in the action radius
(if the option Use Action Radius is activated) will be affected;
• Type of Control Move. Selection of the editing mode. The following editing modes
are available.
– Along Stick. Allows to move the nodes along a fault stick;

– Along Fault Surface. Allows to move the nodes along the fault surface. Modifies
only the nodes coordinates and do not affect the global geometry of the fault;
– Perpendicular to Fault. Moves a node perpendicularly to the fault surface. The
direction is indicated by a stick;
– With Arbitrary Direction. Moves a node in any chosen direction. The direction
is indicated by a stick.
• Use Action Radius. If this option is used, the editing will be applied to all the nodes
situated in the indicated radius around the edited node (marked by the yellow sphere).
17.3. Import
The following import parameters are available:
• from Curves;
17.2. Fault Editing 123

18.1
• from Landmark Fault 3D;
• From Surfer .Bln files;
• From Surfer 7 GRD.
For first and second formats a fault surface is defined by set of simple polygonal chains
in the three dimensional space. Corresponding points of neighbouring polygonal chains are
connected by lines. The loaded file contains points coordinates (x, y, z). For the third and
fourth formats a set of polygons, representing the hangingwall and footwall of the fault for
each horizon is defined in the loaded file. Corresponding points of polygons are connected
by sticks, which is a set of vertical lines representing the slope of the faults.
For all import format type common parameters are the following:
• Preview. Number of Lines. Number of loaded file lines shown in the Preview window.
• Select Coordinate Reference System:
– Project CRS. Project coordinate system. It is defined in the menu Settings.

– File CRS. Data coordinate system in the loaded file.
• Invert Z -coordinates. It is recommended to activate this option if loaded trajectories

were generated by the third-party software which has the opposite direction of Z axis.
Here Z axis is directed downward.
17.3.1. From Curves

• Automatically reoder sticks. Automatic ordering of loaded curves. Ordering is done
in the following way:
1. Sticks are numbered in the order of their appearance in the loaded file. The
average depth z0 of points defining a stick.
2. The surface Z = z0 is created. Intersection points of the fault with this surface are
found. Each point corresponds to its stick.
3. The line, which approximates points set in the best way, is constructed.
4. Points projections on the obtained line are built. Projection points are numbered
and sticks are renumbered: stick number is assigned to the number of points
corresponding to a stick.
17.3.1. From Curves 124

18.1
• Automatically reoder stick points.
Format description. The file contains several curves. Each curve is described by points
set. Each point has its coordinates (x, y, z). Initially, the first curve points are followed by the
second curve points etc.
Two file formats are supported:
1. From Curves. Curves are separated from each other by lines ”999.000000 999.000000
999.000000”.
Example
462371.578491 5937306.051758 1665.394653
462390.957214 5937310.997803 1697.219849
462701.016907 5937390.136719 2228.605469
462739.774384 5937400.029053 2305.924805
999.000000 999.000000 999.000000
462374.560120 5937573.822510 1446.748535
462381.576111 5937581.040771 1504.181274
462393.749268 5937598.266602 1657.436157
462608.282715 5937656.375488 2323.370361
999.000000 999.000000 999.000000
462692.342529 5937181.511230 2067.374023
462711.721252 5937186.457031 2101.812012
462769.857468 5937201.295898 2212.541504
462808.614914 5937211.188477 2287.954590
999.000000 999.000000 999.000000
2. CPS-3. The beginning of the curve is defined by the line which starts from symbol
”->”.
17.3.1. From Curves 125

18.1
Example
FFASCI 0 1 ''LINES'' 0 1e+10
FFATTR 0 1
->1
-1168.400000 1062.000000 -735.000000
-1171.680952 1065.452381 -740.571429
-1174.961905 1068.904762 -746.142857
-1181.523810 1075.809524 -757.285714
-1184.804762 1079.261905 -762.857143
-1191.366667 1086.166667 -774.000000
-1194.647619 1089.619048 -779.571429
-1201.209524 1096.523810 -790.714286
->2
-3550.600000 -853.000000 -839.000000
-3566.855556 -835.861111 -862.222222
-3583.111111 -818.722222 -885.444444
-3599.366667 -801.583333 -908.666667
-3615.622222 -784.444444 -931.888889
-3631.877778 -767.305556 -955.111111
17.3.2. Landmark Fault 3D Format

• XY Units. Choose units system for X and Y axes. Available units are METRIC, FIELD,
LAB. If option Not specified is activated, units are defined by default in Document.
Settings menu.
• Z Units. Choose units system for Z axis. Available units are METRIC, FIELD, LAB.
If option Not specified is activated, units are defined by default in Document. Settings
menu.
Format description. The file contains a table consisted of twelve columns. Each column
has a fixed width. Each data column has a particular purpose. The detailed description of all
parameters is given in the table shown below.
The file defines a set of faults. Each fault is defined by the set of curves. Each curve is
defined by the set of points. Each table line describes one point. For each point the following
parameters should be defined: its coordinates, its position in curve (first, intermediate, last),
fault name, XY units and Z units (depth and time). It should be noticed that curve points are
listed in a table one by one, i.e. the first point is followed by intermediate points and the last
point.
Column Column width Content Data type

1 12 X Real
17.3.2. Landmark Fault 3D Format 126

18.1
2 12 Y Real
3 12 Z (depth) Real
4 3 Colour Integer (1-64)
5 2 Fault type Integer (is not used)
6 2 Point type Integer (1 is the beginning
of the curve point, 2 is in-
termediate point, 3 is the
curve last point)
7 50 Fault name Line
8 5 Interpreter Line (is not used)
9 12 Depth type Line (TIME/DEPTH)
10 14 Survey Line (is not used)
11 20 XY Units Line (METERS/FEET)
12 6 Z Units Line (ms/seconds or ME-
TERS/FEET depends on
depth type)
17.3.2. Landmark Fault 3D Format 127

18.1
Example
448460.997 486599.560 6198.600 41 1 1Fault1 GEO DEPTH Sooner3D
FEET FEET
2448460.997 486599.560 6503.600 41 1 3Fault1 GEO DEPTH
Sooner3D FEET FEET
2450294.620 484225.149 6196.400 41 1 1Fault1 GEO DEPTH
Sooner3D FEET FEET
2450394.610 484226.558 6432.400 41 1 2Fault1 GEO DEPTH
Sooner3D FEET FEET
2450394.610 484226.558 6499.400 41 1 3Fault1 GEO DEPTH
Sooner3D FEET FEET
2451726.875 481945.095 6195.400 41 1 1Fault1 GEO DEPTH
Sooner3D FEET FEET
2451726.875 481945.095 6398.400 41 1 2Fault1 GEO DEPTH
Sooner3D FEET FEET
2451825.457 482046.494 6498.300 41 1 3Fault1 GEO DEPTH
Sooner3D FEET FEET
2452469.058 478955.252 6206.000 41 1 1Fault1 GEO DEPTH
Sooner3D FEET FEET
2452469.058 478955.252 6403.700 41 1 2Fault1 GEO DEPTH
Sooner3D FEET FEET
17.3.3. Surfer .Bln Format

• Name Prefix.
• Top. (METRIC: m, FIELD: f t )
• Bottom. (METRIC: m, FIELD: f t )
Format description. The file contains set of polygons. A polygon is described by the
set of polygon’s corners – points. The number of points is defined in the separate line before
polygon’s points. It is possible to have two numbers in the line, the first one is the number
of points. The second number is ignored. Thus, the file structure is the following:
• a line, which defines the number of points in the set;
• the above line is followed by lines contained coordinates of points in the set.
Points are defined by their coordinates. Each point coordinates are written in the separate
line and separated by commas.
Each points set in the file describes a curve. Faults are vertical surfaces. Each fault is
defined by vertical lines passing through points of the corresponding curve. Then, faults are
cut at the top by the value defined in Top, and at the bottom by the value in Bottom.
17.3.3. Surfer .Bln Format 128

18.1
Example
4,0
17856.63489,6658.68163,0
17861.12519,6658.372,0
17875.46317,6649.609481,0
17880,6648.635638786964,0
8,0
17750,6622.511664327508,0
17751.68145,6622.511664,0
17759.38253,6622.511665,0
17768.69632,6622.074379,0
17775.94934,6620.203068,0
17786.25336,6618.328153,0
17795.78362,6617.355725,0
17857.69565,6615.201342,0
3,0
17754.75112259643,6700,0
17754.85626,6699.875191,0
17759.6023,6698.34022,0
17.3.4. Surfer 7 GRD Format

• Top. (METRIC: m, FIELD: f t )
• Bottom. (METRIC: m, FIELD: f t )
Binary file format.
17.4. Smooth Fault Surface

• Input Surface. Name of the surface which will be smoothed.
• Smoothed Surface. Smoothed surface name.
• Smoothing Algorithm:
◦ Splines. Lines connected neighbouring points of top and bottom fault boundaries are
smoothed using cubic splines. First, lines connected x coordinates of initial points
are smoothed, the same procedure is repeated for lines connected y coordinates
of points and then z coordinates. Number of points adding to a line is defined by
parameter Subdivision.
◦ Moving Average. A stick points position is smoothed as following: for each sticks
node the neighbouring radius r is calculated. r is a product of the value defined
in Radius for Moving Average with boundary length. All points placed in the
17.3.4. Surfer 7 GRD Format 129

18.1
circle of radius r with the center at the stick node are averaged, i.e. average
values of their coordinates are calculated. The point with averaged coordinates is
the result of smoothing in this stick node.
• Extend Surface Vertically:
◦ Top. Last top stick line is continued up to intersection with the surface Z = z0 ,
where z0 is the parameter value in this field.
◦ Bottom. Last bottom stick line is continued up to intersection with the surface
Z = z0 , where z0 is the parameter value in this field.
17.5. Ruled Fault by Curves 2D

A ruled fault is created between top and bottom curves placed at defined depths. Then
visualized part of the fault is cut by top depth and bottom depth.
• Result Fault. Name of the resulting fault.
• Sticks. Number of sticks formed a curve.
• Top Depth. Top depth which will be used to cut a visualized fault part (METRIC: m,
FIELD: f t ).
• Bottom Depth. Bottom depth which will be used to cut a visualized fault part (METRIC:
m, FIELD: f t ).
• Top Curve Depth. (METRIC: m, FIELD: f t )
• Bottom Curve Depth. (METRIC: m, FIELD: f t )
• Top Curve. Curve name bounded the fault at the top.
• Bottom Curve. Curve name bounded the fault at the bottom.
17.6. Export
This option allows to save the files which contain faults. The faults are exported to the format
From Curves.
17.5. Ruled Fault by Curves 2D 130

18.1
Figure 13. Ruled Fault by Curves 2D. Top and bottom curves.
17.6.1. Export Fault as Curve Set

1. Export Fault Surfaces.
• Output Folder. Define a folder name in which all Horizons will be saved.
• Fault Surface. Define a name of exported fault surface.
• Input Units. Define the units (METRIC, FIELD, LAB) in which data will be
saved. Available units are METRIC, FIELD, LAB. If option Not specified is
17.7. Auxialiary Calculations

17.7.1. Create Fault by Seismic Fault
This option allows to convert a fault picking in time (seismic fault) into a surface in depth,
using check-shot data. The following parameters must be specified:
• Output. Result Fault. Name of resulting fault.
• Time-Depth Relation Log. Check-shot log which will be used to build the fault.
• Time-Depth Relation Log Type. Define the log type (one way ot two-way time).
17.6.1. Export Fault as Curve Set 131

18.1
• Well Filter. Selection of the well filter containing all the wells with check-shot data
which will be used in the computation.
• Seismic. Selection of the seismic data used for the picking.
• Seismic Fault. Selection of the seismic fault which will be converted in depth.
17.7.1. Create Fault by Seismic Fault 132

18.1
18. Faulted Horizons

Faulted horizons are produced in the process of building the grid with faults. Faulted horizons
are built based on markers and faults or set of points and faults. In contrast to horizons, which
are functions of depth, i.e. H = H(X,Y ), faulted horizons are multivalued functions, i.e. one
coordinate (X,Y ) is associated with set of depths H1 , H2 , ...: H(X,Y ) = H1 , H(X,Y ) = H2 , ....
In Calculations faulted horizons can be interpolated.
18.1. Horizon by Marker and Faults (Least-Squares)

To construct faulted horizons defined markers and faults are used. If the option Use Perfo-
rations (see below) is activated markers located on well perforated intervals are taken into
construction. Generally, a faulted horizon is defined on an arbitrary 2D grid. The faulted
horizon can be interpolated using Least-Squares method on a regular 2D grid in the XOY
plane. For an interpolation it might be required to define a trend horizon (e.g. from seismic
data).
• Source data:
– Well Marker.
– Well Filter.
– Trend Horizon.
• Dimensions:
– Count of Points by X.
– Count of Points by Y.
• Bounds:
Horizon’s boundaries can be detected by user explicitly or automatically calculated
using Autodetect. (see below).
Explicit definition:
– Minimal X Coordinate. (METRIC: m, FIELD: f t )

– Maximal X Coordinate. (METRIC: m, FIELD: f t )
– Minimal Y Coordinate. (METRIC: m, FIELD: f t )
– Maximal Y Coordinate. (METRIC: m, FIELD: f t )
• XY Margin. (METRIC: m, FIELD: f t ) Option description see below in Autodetect.
• Use Perforations. Option description see below in Autodetect.
18. Faulted Horizons 133

18.1
• Autodetect. Automatic detection of horizon boundaries. A minimum square rectangle

rotated by the defined angle with respect to the OX axis is built based on a set of
markers on the XOY surface. Rectangle’s boundaries are defined by maximum and
minimum coordinates of markers. Further, the rectangle is extended by XY Margin
value in each direction (i.e. the value is added to maximum coordinates and sub-
tracted from minimum ones). If option Use Perforations. is activated then to construct
the rectangle only markers located within well’s perforated intervals are taken into
calculation.
The smoothness of the interpolated horizon can be improved by varying Coefficients
in the range [0.01, 100] (see formula of LSM).
• Coefficients:
If check-box Advanced settings is checked additional option Grid refinement will be

available. The choice of this option allows to improve an accuracy of horizon’s interpolation,
however, increases a computational time. An interpolation is carried out Refinement Steps
number of times. At initial interpolation step the number of points in X and Y directions is
defined:
• Start Count of Points by X.
• Start Count of Points by Y.
At the first interpolation step it is recommended to use a rough grid, i.e. the number of points
in X and Y directions should be minimal. At each iteration the number of points in X and
Y directions increases in such way that after defined number of iterations (steps) the final
number of points becomes equal to the number of horizon’s points.
18.2. Horizon by Point Set and Faults (Least-Squares)

A faulted horizon is produced in the process of creation of Grid by Point Sets&Faults. To
construct a faulted horizon defined set of points and faults are used. Generally, a faulted
horizon is defined on an arbitrary 2D grid. A faulted horizon can be interpolated using Least-
Squares method on a regular 2D grid in the XOY surface. For an interpolation it might be
required to define a trend horizon (e.g. from seismic data).
• Source data:
◦ Point Set.
◦ Trend Horizon.
18.2. Horizon by Point Set and Faults (Least-Squares) 134

18.1
• Dimensions:
– Count of Points by X.
– Count of Points by Y.
• Bounds:
Horizon’s boundaries can be detected by user explicitly or automatically calculated
using Autodetect. (see below).
– Minimal X Coordinate. (METRIC: m, FIELD: f t )

– Maximal X Coordinate. (METRIC: m, FIELD: f t )
– Minimal Y Coordinate. (METRIC: m, FIELD: f t )
– Maximal Y Coordinate. (METRIC: m, FIELD: f t )
• XY Margin, m. Option description see below in Autodetect.
• Autodetect. Automatic detection of horizon boundaries. A minimum square rectangle

rotated by the defined angle with respect to the OX axis is built based on a set of points
in the XOY surface. Rectangle’s boundaries are defined by maximum and minimum
coordinates of points. Further, the rectangle is extended by XY Margin value in each
direction (i.e. the value is added to maximum coordinates and subtracted from minimum
ones).
A smoothness of interpolated horizon can be improved by varying Coefficients in the
range [0.01, 100] (see formula of LSM).
• Coefficients:
If check-box Advanced settings is checked additional option Grid refinement will be

available. The choice of this option allows to improve an accuracy of horizon’s interpolation,
however, increases a computational time. An interpolation is carried out Refinement Steps
number of times. At initial interpolation step the number of points in X and Y directions is
defined:
• Start Count of Points by X.
• Start Count of Points by Y.

At the first interpolation step it is recommended to use a rough grid, i.e. the number of points
in X and Y directions should be minimal. At each iteration the number of points in X and
Y directions increases in such way that after defined number of iterations (steps) the final
number of points becomes equal to the number of horizon’s points.
18.2. Horizon by Point Set and Faults (Least-Squares) 135

18.1
19. Point Sets

In Calculations menu to work with point sets the following possibilities are available:
• Import;
• Export;
• Create Point Set by Horizon;
• Create Point Set by Seismic Horizon;
• Create Point Set as Wells and Horizon Intersection;
• Create Point Set by Marker;
• Clear Point Set Near Faults;
• Create a Point Set by Grid Layer;
• Pointsets Union;
• Shift Point Set by Vector.
19.1. Import
A point set can be loaded in the following formats:
• XYZ format;
• Point set lines (ASCII);
• CPS-3 lines;
• Import Pointsets from Shapefile.
19.1.1. XYZ format

In the loaded file point’s coordinates (x, y, z) in the three dimensional space are defined.
• Add Rows. Add files with a set of points.
• Comment. Define a comment symbol. Comments start with the determined symbol
and all text following the symbol will be ignored.
• Skip lines. Skip defined number of lines starting from the beginning of the file.
19. Point Sets 136

18.1

• XY Units. Choose units system for X and Y axes. Available units are METRIC, FIELD,
LAB. If option Not specified is activated, units are defined by default in Document.
Settings menu.
• Z Units. Choose units system forZ axis. Available units are METRIC, FIELD, LAB.
If option Not specified is activated, units are defined by default in Document. Settings
menu.
Example
420467.295654 7246003.404053 2487.228271
420467.295654 7246053.668579 2480.297363
420467.295654 7246103.933105 2473.079834
420517.610107 7246103.933105 2468.294922
420467.295654 7246154.197632 2465.580322
420517.610107 7246154.197632 2460.757812
420416.981201 7246204.462280 2463.250244
19.1.2. Point set lines (ASCII)

The description of the format is given in the section From Curves (a format type to import
Faults).
Parameters to import a point set are:
• Remove Rows. Remove a file from the list.
• Number of Lines.
• One Point Set per file. In each file there is one point set.
• Invert Z coordinate. It is recommended to activate this option if loaded trajectories

were generated by the third-party software which has the opposite direction of Z axis.
Here Z axis is directed downward.
• Input Units. Choose a system of units (METRIC, FIELD, LAB).
19.1.3. CPS-3 lines

The description of the format is given in the section From Curves (a format type to import
Faults). Parameters to import a point set in the format coincide with ones for Point set lines
(ASCII).
19.1.2. Point set lines (ASCII) 137

18.1
19.1.4. Import Pointsets from Shapefile

Point sets can also be loaded from Shapefiles.
The shapefile format is a geospatial vector data format. A shapefile contains a main file,
an index file and a dBASE table. The main file is a description of the object geometry and
contains a list of vertices. The index file provides a positional index of the object geometry,
while the dBASE table is a list of the object attributes.
The following parameters have to be specified:
• File Name. Complete path to the .shp file;
• Name prefix. Name of the loaded object in Designer;
• Add Rows. Add a file;
• Remove Rows. Remove a file. The removed file will not be loaded;
• Ignore index file. This option can be used to force the visualization of the object in
case of corrupted index files ;
• Select Coordinate Reference System. These field is active when a coordinate system
is set for the entire project and allows to set a coordinate system (CRS) for the file,
which can differ from the project CRS. To change the file CRS, select a CRS from the
list available by clicking on the ellipsis button. The project CRS can be modified, as
described in the section 2.2.
19.2. Export
A point set can be exported using the following ways:
• Export all PointSets in XYZ format;
• Export all PointSet in XYZ format.
19.2.1. Export all PointSets in XYZ format

• Output Folder. Define a folder name in which all Point Sets will be saved.
• Output Units. Choose a system of units (METRIC, FIELD, LAB).
19.2.2. Export all PointSet in XYZ format

• File Name. Name of the file, in which the selected point set will be saved.
• PointSet. Name of the exporting point set.
• Output Units. Choose a system of units (METRIC, FIELD, LAB).
19.1.4. Import Pointsets from Shapefile 138

18.1
19.3. Create Point Set by Horizon

Horizon points satisfying the filter condition defined below will be included in the set of
points.
• Point Set. Name of the creating set.
• Horizon. Horizon used to create a set of points.
• Thinning coefficient. Allows to decrease a number of horizon’s points in order to

accelerate the grid construction process. Thinning coefficient c varies in the range:
0 < c ≤ 1. The number of horizon’s points is multiplied by the coefficient. The rest of
the points are distributed on the grid with uniform step.
• Distances From Faults. Table with the following columns:
– Use. Use or not use fault for the nodes filtration.

– Fault. Fault name.
– Distance. Grid nodes placed at the defined distance from the fault or closer are
excluded from the set of points.
• Gradient Threshold (angle in degrees). Grid nodes, in which an inclination angle

between a horizon and XOY surface is higher than the threshold value, are excluded
from the set of points. The inclination angle varies from 0 ◦ to 90 ◦ .
19.4. Create Point Set by Seismic Horizon

This computation allows to create a point set using a seismic horizon. The points will be
located at the horizon nodes.
• Point Set. Name of the created point set;
• Seismic. Name of the interpreted seismic;
• Seismic Horizon. Name of the seismic horizon which will be used for the computation.
19.5. Create Point Set as Wells and Horizon Intersection

Horizon intersection points with well trajectories will be included in creating set of points.
• Point Set. Name of the creating set of points.
• Well Filter. Horizon intersection with wells satisfied to defined filter will be calculated.
• Horizon. Horizon used to create a point set.
19.3. Create Point Set by Horizon 139

18.1
19.6. Create Point Set by Marker

A set of points will be coincide with selected well markers.
• Point Set. Name of the creating point set.
• Well Marker. Marker used to create a point set.
• Well Filter. Markers for wells satisfied to the filter will be selected.
• Z Shift. (METRIC: m, FIELD: f t ) All points shift in the direction of Z- coordinate
increase.
19.7. Clear Point Set Near Faults

The calculation allows to exclude points satisfied to conditions below from a set of points.
• Result Point Set. Name of the point set after cleaning.
• Result Horizon. Horizon obtained by interpolation of the initial set of points. An
interpolation is carried out using LSM with default settings.
• Result Gradient 2D Map. Gradient 2D map is calculated in order to use a gradient
filter (parameter Gradient Threshold see below). In order to see this map in the 2D
Map list this option should be activated.
• Source Point Set. Set of points for modification.
• Band Width. (METRIC: m, FIELD: f t ) Grid nodes placed at the defined distance
from the fault or closer are excluded from the set of points.
• Gradient Threshold (angle in degrees). Grid nodes, in which an inclination angle
between a horizon and XOY surface is higher than the threshold value, are excluded
from the set of points. An inclination angle varies from 0 ◦ to 90 ◦ .
19.8. Create a Point Set by Grid Layer

This option allows to create a point set along a chosen grid layer.
• Result Point Set. Name of the point set which will be created.
• Layer. Selection of the layer along which the point set will be calculated.
• Use Top Points of Block. If this option is selected, the point set will pass through the
top of the blocks, if not, it will pass through the bottom.
• Distance From Faults. Allows to take the faults into account. When this option is
activated, a field with the fault list appears. The faults for which the column Use is
ticked will be taken into account. The distance set in the field Distance will work as a
margin: only the points situated beyond that distance will be a part of the point set.
19.6. Create Point Set by Marker 140

18.1
19.9. Pointsets Union

This calculation allows to obtain a point set by union of several points sets.
• Result Point Set. Set the resulting point set.
• Add Rows. Add point sets for the union (a point set has to be chosen from the list
available by double click on the row).
• Remove Rows. Remove point sets.
• Apply. Create a point set from the union defined above.
19.10. Shift Point Set by Vector

This computation allows to translate a point set by a vector.
• Result Point Set. Name of the resulting point set;
• Initial Point Set. Name of the point set which has to be translated;
• X Shift, m. Shift length along X;
• Y Shift, m. Shift length along Y;
• Z Shift, m. Shift length along Z;
19.9. Pointsets Union 141

18.1
20. Tables
In this section, Tables are presented. These objects, corresponding to report tables can be
visualized in the tab Table. Available calculations allows to load, export and create a report
table for volumetric properties (presented in 22.5.1) which have to be created beforehand.
The following Calculations are available:
• Export;
• Load Tables;
• Create Table.
20.1. Export
This calculation allows to export a created table in text format.
• File Name. complete path of the exported file;
• Table. Name of the exported table in the project;
• Field Delimiter. Selection of the columns delimiter type from the list containing Tab;
All Spaces, Comma, Semicolon delimiters. If another type of delimiter is needed, the
option Other Delimiter has to be ticked and the delimiter has to be entered in the
field.
Note that if the exported table has to be imported in a tNavigator

! project, the type of delimiter has to be chosen from the list of available
delimiters.
20.2. Import
Report tables can be imported to Geology Designer projects in text formats. The field delim-
iter has to be one of the following: Comma, Tab, Space, Semicolon. The following options
are available:
• Table File Names. List of imported tables. To add a new table, the option Add Rows
has to be used;
• Preview. Preview of each imported table. The number of displayed lines is given by
the number of lines;
• Field Delimiter. Selection of the field delimiter of the file.
20. Tables 142

18.1
20.3. Create Tables

This calculation allows to create a report table by region. In order to generate a report, first,
the volumetric properties have to be computed. Volume computations are presented in the
section 22.5.1
• Table. Name of the table in the project;
• Property. The property for which the report will be generated has to be selected from
the list available by double clicking on the white field;
• Statistic type. Selection of the statistic value which will be computed for each property.
The proper type has to be selected from the list available by double clicking on the
white field.
– Sum. Calculates the sum of all the values;

– Max. Allows to display the maximum value of the property;
– Min. Allows to display the minimum value of the property;
– Mean. Calculates the arithmetic mean;
– Entries. Displays the number of entries for each region (number of blocks);
– RMS. Calculates the root mean square of the property;
– Weighted Mean. Calculates the weighted mean of the property. The property
corresponding to the weights has to be selected in Weights.
• Regions. Region for which the report will be generated. The proper region has to be
selected from the list.
• Weights. Selection of the property corresponding to the weights which are used for the
Weighted Mean calculation.
21. 3D-Grids. Model grids

In this section the possibilities to work with a 3D grid are described. The description of
possibilities to work with properties is given in the section Properties. Depending on the
structure, Corner Point (ZCORN, see 12.2.9) or CORNERS (see 12.2.117) grid will be gen-
erated. ZCORN (see 12.2.9) format will be used for simple geometries, while CORNERS
(see 12.2.117) format will be generated when structural faults are present. The grid will be
exported in the proper format if the entire model is exported.
• Import. Load Grid;
• Create Simple Grid;
• Create Simple LGR;
20.3. Create Tables 143

18.1
• Create LGRs by Wells;
• Create LGRs by Filter Property;
• Remove LGR;
• Create Grid by Horizons;
• Create Grid by Horizon and Faults;
• Create Grid by Point Sets&Faults;
• Add Geological K to Grid 3D;
• Import Existing Model;
• Calculate Grid Geometry Properties;
• Export.
21.1. Import. Load Grid

• File Name. Name of the file with a grid (e.g. in the format .GRDECL). A model *.data
file can be used if a grid file is defined in the model file using the keyword INCLUDE
(see 12.1.76) with a parameter – grid model file.
• Preview. Number of Lines. Number of lines shown in the Preview window.
• Use ACTNUM from file. Use the keyword ACTNUM (see 12.2.29) specifications.
• Ignore MAPAXES. If this option is activated specifications defined by the keyword

MAPAXES (see 12.2.65) will be ignored when reading a grid file.
• Input Units. Choose a system of units (e.g. METRIC, FIELD, LAB).
21.2. Create Simple Grid

The calculation allows to create a grid between the top and the bottom of the reservoir. The
construction is based on the set of well trajectories points on XOY plane. If the option Use
Perforations (see below) is activated, the points located on perforated intervals are taken
into account for the construction.
• Dimensions:
– Count of Blocks by X;
– Count of Blocks by Y;
21.1. Import. Load Grid 144

18.1
– Count of Blocks by Z.
• Top. Top bound of the reservoir along Z axis (METRIC: m, FIELD: f t ).
• Bottom. Bottom bound of reservoir along Z axis (METRIC: m, FIELD: f t ).
• Bounds: 2D grid’s boundaries can be detected by user explicitly or automatically cal-

culated using Autodetect (see below).
– Minimal X Coordinate. (METRIC: m, FIELD: f t ).

– Maximal X Coordinate. (METRIC: m, FIELD: f t ).
– Minimal Y Coordinate. (METRIC: m, FIELD: f t ).
– Maximal Y Coordinate. (METRIC: m, FIELD: f t ).
• XY Margin. (METRIC: m, FIELD: f t ) A description of the option see below in

Autodetect.
• Use Perforations. A description of the option see below in Autodetect.
• Autodetect. An automatic detection of 2D grid boundaries. A minimum square rect-

angle rotated by the defined angle with respect to the OX axis is built based on a
set of wells trajectories points on the XOY plane. Rectangle’s boundaries are defined
by maximum and minimum coordinates of trajectories points. Further, the rectangle is
extended by XY Margin value in each direction (i.e. the value is added to maximum
coordinates and subtracted from minimum ones). If option Use Perforations is acti-
vated then to construct the rectangle only wells trajectories points located within well’s
perforated intervals are taken into calculation. If trajectories of wells are not loaded
then extension starts from the coordinate origin.
21.3. Create Simple LGR

The calculation allows to create a local grid refinement (LGR) for the defined box of blocks.
• LGR name. Name of the creating grid refinement.
• Box of grid indices (vertices coordinates of the refinement region):
– Lower I. Coordinate of the first refining block in X direction.

– Upper I. Coordinate of the last refining block in X direction.
– Lower J. Coordinate of the first refining block in Y direction.
– Upper J. Coordinate of the last refining block in Y direction.
– Lower K. Coordinate of the first refining block in Z direction.
21.3. Create Simple LGR 145

18.1
– Upper K. Coordinate of the last refining block in Z direction.

• Refinement:
– NXFIN. The number of parts in which each block will be refined in X direction;
– NYFIN. The number of parts in which each block will be refined in Y direction;
– NZFIN. The number of parts in which each block will be refined in Z direction.
– Logarithmic Refinement Rate. Sets the refinement spacing. This value must be
a positive real number (cf. figure 14).
Figure 14. Examples of LGRs with different logarithmic rates. The refinement spacing
increases with the logarithmic refinement rate (the value can be superior to 1).
– Enable Logarithmic Refinement Along I. Create a logarithmic refinement along

I axis.
– Refinement Center Along I. Set the center of the refinement along I. Corre-
sponds to a I index. By default, it is set as the center of the defined box.
– Enable Logarithmic Refinement Along J. Create a logarithmic refinement along
J axis.
– Refinement Center Along J. Corresponds to a J index. By default, it is set as
the center of the defined box.
– Enable Logarithmic Refinement Along K. Create a logarithmic refinement
along K axis.
– Refinement Center Along K. Corresponds to a K index. By default, it is set as
the center of the defined box.
When exporting, the keywords LGR (see 12.1.84), REFINE (see 12.2.95), CARFIN
(see 12.2.94), NXFIN / NYFIN / NZFIN (see 12.2.97), HXFIN / HYFIN / HZFIN
(see 12.2.98) are saved.
21.3. Create Simple LGR 146

18.1
21.4. Create LGRs by Wells

The calculation allows to create a local grid refinement (LGR) in the vicinity of selected
wells. Blocks intersected by well trajectory or blocks with perforations can be refined as
well.
• Well Filter. Create LGR in the vicinity of wells selected by the filter.
• Boxes parameters.
– Minimum Indent From Well. LGR will be done in all blocks located from the
block with a well no further than the defined distance. A block is used as a unit
of distance.
– Maximum Box Size. Allows to create a cubic box around a well block of a
given maximum size defined in terms of blocks number. The refinement will be
performed in the blocks of the created box.
It is recommended to implement a box when a local refinement in the vicinity
of horizontal wells is applied. This parameter allows to decrease the number of
blocks around a well for the local refinement.
• Refinement options:
– NXFIN. The number of parts in which each block will be refined in the X
direction;
– NYFIN. The number of parts in which each block will be refined in the Y
direction;
– NZFIN. The number of parts in which each block will be refined in the Z
direction.
• Refine in Perforations Only. Implement a grid refinement with parameters defined

above only for the well’s blocks with perforation.
• Remove All of Existing LGR Near Wells. Remove the created LGR in the vicinity
of the well before creating a new one.
When exporting a model keywords LGR (see 12.1.84), REFINE (see 12.2.95), CARFIN
(see 12.2.94) and NXFIN / NYFIN / NZFIN (see 12.2.97) are saved.
21.5. Create LGRs by Filter Property

This calculation allows to create an LGR in the blocks which satisfy the condition set by the
property which is selected from the list Filter Property, the operator and the number entered
in the field. The following fields have also to be set:
• LGR Name Prefix: prefix of the created LGRs. A number will be automatically
generated;
21.4. Create LGRs by Wells 147

18.1
• Refinement.
– NXFIN. The number of parts in which each block will be refined in the X
direction;
– NYFIN. The number of parts in which each block will be refined in the Y
direction;
– NZFIN. The number of parts in which each block will be refined in the Z
direction.
21.6. Remove LGR

All created LGR are shown in the list below. To remove a created refinement (LGR) it is
necessary to tick the check box near the selected LGR and press the button Apply situated
on the panel below.
21.7. Create Grid by Horizons

The calculation allows to construct a grid between defined horizons, e.g. between bottom and
top of reservoir. If several horizons are available the grid can be defined with different Par-
tition Type for each reservoir located between selected horizons. To add/remove a horizon
Add Rows/Remove Rows buttons are used.
The grid is constructed in the region, which is an intersection of horizons with the 2D
grid. In addition, a polygon boundary, defining a licensed area for example, can be taken into
account.
• Horizon. Define the horizons that encompass the grid and separate it into the regions. To
add more horizons, press Add Rows or double-click in the empty field. Horizons are
selected from the list available, and have to be arranged from top to bottom. For each
horizon, the following parameters must be set:
◦ Zone. Zones can be created by using regions located between the first horizon
(top horizon) and the last one (base horizon). Each zone has its unique number.
Several regions can be included in one zone. The created zone can be edited in the
tab Zones by right-clicking on zone_id and selecting Edit option. Corresponding
nodes of top and bottom horizons, defined in 2D grid nodes located with Step
along X and Step along Y (see below), are connected with each other. Then, the
partition is done in the Z direction.
◦ Partition Type. Three types of partition are available:
– Proportional (counts). In this case the distance between top and base horizons
is partitioned by user defined number of counts. The number of counts is
defined in the Counts/Step field.
21.6. Remove LGR 148

18.1
– Along Top (step). In this case the grid block faces of each following layer is
constructed in such way that top and bottom faces are parallel to the Top
Horizon. The grid step size in Z direction is defined by Counts/Step. A step
length is measured in meters.
– Along Bottom (step). In this case the grid block faces of each following layer
is constructed in such way that top and bottom faces are parallel to the Base
◦ Counts/Step. See description of Partition Type option.
◦ Horizon Type. In order to accurately manage the contacts between the horizons,
the proper type of horizon has to be chosen from the following list, available by
right-mouse button click on the field (cf. Fig. 15):
Figure 15. Conformable, Discontinuous, Erosional and Basement types of horizons.
– Conformable. Use for conformable deposits. The horizon will cut all lower
horizons it intersects, except the Basement;
– Discontinuous. Use for unconformable deposits. All the horizons lying upon
and below will be truncated, including the basement;
– Erosional. The horizon will cut all lower horizons it intersects, including the
basement
– Basement. Use for horizons defining the basement top. It will cut all upper
horizons it intersects;
• Polygon. This option allows to use a polygon as boundary for the grid;
21.7. Create Grid by Horizons 149

18.1
Autodetect option.
m, FIELD: f t ).
m, FIELD: f t ).
◦ Autodetect by. Selection of the object which size will be used to compute the grid
(for automatic definition);
option.
• Treat Blocks of Zero Volume as Active. Zero volume blocks may affect interpolation
results and are not included in the dynamic model.
21.8. Create Grid by Horizon and Faults

The calculation allows to construct a grid based on defined horizons and faults. In addition,
as a result of grid construction faulted horizons are created. If several horizons are available
the grid can be defined with different Partition Type in Z direction for each reservoirs located
between selected horizons. To add/remove horizons Add Rows/Remove Rows buttons can
be used. The grid is constructed in the region, which is an intersection of horizons with a
2D grid. In addition, a polygon boundary, defined a licensed area, can be taken into account.
Horizons, faults and 2D-grid parameters are defined below.
• Horizon.
Horizons have to be defined from top to bottom by selecting it from the list available
by double clicking on the field;
◦ Zone. Zones can be created by using regions located between the first horizon (top)
and the last one (base). Each zone has its unique number. Several regions can
be included in one zone. The created zone can be edited in the tab Zones by
right-clicking on zone_id and selecting Edit option. Corresponding nodes of top
and bottom horizons, defined in 2D grid nodes located with Step along X and
21.8. Create Grid by Horizon and Faults 150

18.1
Step along Y (see below), are connected with each others. Then, the partition is
done in the Z direction.
– Proportional (counts). In this case the distance between the surfaces passing
through the top and base horizons is partitioned by the number of counts
defined by the user. The number of counts is defined in the Counts/Step
field.
◦ Horizon Type. In order to accurately manage the contacts between the horizons,
the proper horizon type has to be chosen from the following dropdown list (cf.
Fig. 15):
– Conformable. Use for conformable deposits. The horizon will cut all lower
horizons it intersects, except the Basement;
– Discontinuous. Use for unconformable deposits. All the horizons lying upon
– Erosional. The horizon will cut all lower horizons it intersects, including the
basement
– Basement. Use for horizons defining the basement top. It will cut all upper
horizons it intersects;
• Faults:
◦ Use. Specifies the faults which are used for the computation;
◦ Faults. Fault name;
◦ Structural. If this option is checked then the grid blocks edges will be parallel to
the fault surface, otherwise a stair step geometry will be used and the grid blocks
edges will be parallel to the coordinate axes;
◦ Distance. Exclude from the set of points points located at the defined distance from
a fault or closer;
◦ Linearity Level. This value describes the linearity of the faults. 100% linearity
level corresponds to a completely linear fault. This value can be used to reduce
the computation time by approximating the faults as linear segments;

18.1
• Segments Property.
Selection of the property which will carry the information about the fault compartments.
A discrete code will be assigned to each fault block, cf. figure 16);
Figure 16. Example of fault compartments property. A code (1, 2 or 3) is assigned to each
compartment.
• Polygon.
This option allows to use a polygon as boundary for the grid;
• 2D Grid Border Using.

This option allows to manage the grid border geometry. In the case of structural faults,
the grid blocks will be oriented along the fault, so 3 options can be used in order to
define the border:
◦ Use With Grid Structure. Changes the orientation of grid blocks in order to obtain
a vertical boundary;
◦ Cut Grid. Cuts the grid vertically at the defined boundary following the grid blocks;
◦ Do Not Use. Option allows to generate a boundary along the grid blocks, parallel
to the faults, cf. figure 17).
• 2D Grid:
parameters for the 2D grid. The settings can be detected automatically using the option
Autodetect by (see below).

18.1
Cut Grid Use With Grid Structure Do Not Use

(Structural Fault) (Structural Fault) (Structural Fault)
Figure 17. Example of grid borders for the options Cut Grid (A), Use With Grid Structure
(B), Do Not Use (C). Structural type is assigned to all the faults. The grid border is circled
by red dashed lines.
Autodetect option.
m, FIELD: f t ).
m, FIELD: f t ).
◦ Autodetect by. Selection of the object which will define the size of the grid (for
automatic definition);
option.

18.1
21.9. Create Grid by Point Sets&Faults

This calculation allows to build a grid based on defined sets of points and faults. In addition,
as a result of grid construction faulted horizons based on markers and faults are created.
The grid is constructed based on the set of points defined on XOY plane. If several sets of
points are available, different Partition Type in Z direction can be used for each reservoir
located between surfaces built on selected sets of points. To add/remove a set of points Add
Rows/Remove Rows buttons can be used. The grid is defined as the intersection of surfaces
defined by point sets with the 2D grid. In addition, a polygon can be set as a boundary for
the grid (corresponding to a licensed area for example).
• Point Set. Point Sets have to be defined from top to bottom by selecting it from the list
available by double clicking on the field;
◦ Zone. Zones can be created by using regions located between the first point set
(top) and the last one (base). Each zone has its unique number. Several regions
can be included in one zone. The created zone can be edited in the tab Zones by
right-clicking on zone_id and selecting Edit option. Corresponding nodes of top
and bottom point sets, defined in 2D grid nodes located with Step along X and
Step along Y (see below), are connected with each other. Then, the partition is
done in the Z direction.
– Proportional (counts). In this case the distance between the surfaces passing
through the top and base point sets is partitioned by the number of counts
defined by the user. The number of counts is defined in the Counts/Step
field.
◦ Point Set Type. In order to accurately manage the contacts between the point sets,
the proper point set type has to be chosen from the following dropdown list (cf.
Fig. 15):
– Conformable. Use for conformable deposits. The point set will cut all lower
point sets it intersects, except the Basement;
– Discontinuous. Use for unconformable deposits. All the point sets lying upon
21.9. Create Grid by Point Sets&Faults 154

18.1
– Erosional. The horizon will cut all lower point sets it intersects, including the
basement
– Basement. Use for point sets defining the basement top. It will cut all upper
point sets it intersects;
• Faults:
◦ Use. Specifies the faults which are used for the computation;
◦ Faults. Fault name;
◦ Structural. If this option is checked then the grid blocks edges will be parallel to
the fault surface, otherwise a stair step geometry will be used and the grid blocks
edges will be parallel to the coordinate axes;
◦ Linearity Level. This value describes the linearity of the faults. 100% linearity
level corresponds to a completely linear fault. This value can be used to reduce
the computation time by approximating the faults as linear segments;
• Segments Property. Selection of the property which will carry the information about the
fault compartments. A discrete code will be assigned to each fault block, cf. figure 16);
• Polygon. This option allows to use a polygon as boundary for the grid;
• 2D Grid Border Using. This option allows to manage the grid border geometry. In the
case of structural faults, the grid blocks will be oriented along the fault, so 3 options
can be used in order to define the border:
◦ Use With Grid Structure. Changes the orientation of grid blocks in order to obtain
a vertical boundary;
◦ Cut Grid. Cuts the grid vertically at the defined boundary following the grid blocks;
◦ Do Not Use. Option allows to generate a boundary along the grid blocks, parallel
to the faults, cf. figure 17).
Autodetect option.
m, FIELD: f t ).
21.9. Create Grid by Point Sets&Faults 155

18.1
m, FIELD: f t ).
◦ Autodetect by. Selection of the object which will define the size of the grid (for
automatic definition);
option.
In Transformations the following possibilities are available to work with 3D grids:
• Edit Grid;
• Translate & Rotate Grid;
• Cut Grid 3D;
• Update Grid.
21.10.1. Edit Grid

This option allows to pull a grid to the selected space point (attraction point). The projection
of attraction point on a grid is a grid pulling point.
The following parameters should be defined:
• Fill Point by mouse click. Set the X, Y and Z coordinate of the chosen point by
clicking on it on the 3D model.
• Point x. X-coordinate of the attraction point (METRIC: m, FIELD: f t ).
• Point y. Y-coordinate of the attraction point (METRIC: m, FIELD: f t ).
• Point z. Z-coordinate of the attraction point (METRIC: m, FIELD: f t ).
• Radius of Editing. (METRIC: m, FIELD: f t ) Grid points, located within the circle
of defined radius with center in the projection of attraction point on the grid, will be
pulled to the attraction point as well.
• Number of Layers. Number of layers which will be pulled to the attraction point.

18.1
• Pulling Type. Proportional, Parallel. The pulling height of the top layer points to the
attraction point is calculated using above mentioned formula. Other points of below
layers (the number of editing layers is defined by parameter Number of Layers) are
pulled by the same height using Parallel way or Proportional way. The last way means
that the distance between top and bottom points of column of blocks with the same
(x, y) coordinates (boundaries of such columns are called pillars) will be subdivided
by Z-layers in the same proportion as before editing.
21.10.2. Translate & Rotate Grid

• Rotation:
– Angle, degrees.
– Center X. X-coordinate of the point around which the grid is rotated (METRIC:
m, FIELD: f t ).
– Center Y. Y-coordinate of the point around which the grid is rotated (METRIC:
m, FIELD: f t ).
• Shift Vector. All grid points will be shifted by defined number of meters in each
direction. In order to shift the grid in the opposite direction along any axis the negative
values should be defined.
– X. Shift of grid points in the X direction by the defined number of units of length
– Y. Shift of grid points in the Y direction by the defined number of units of length
– Z. Shift of grid points in the Z direction by the defined number of units of length
• Invert I-index. After transformation the grid block index [i, j ] is changed to [ni − i +
1, j ].
• Invert J-index. After transformation the grid block index [i, j ] is changed to [i, n j −
j + 1].
21.10.3. Cut Grid 3D

Grid is cut by selected indices.
Indices Cut Box:
• Start/End I/J/K. 6 coordinates of the box are new grid boundaries.
• User Cut. For automatic calculation of the new grid boundaries blocks, in which
selected property is not zero, are used.
• Autodetect. Coordinates of the new grid boundaries are calculated automatically based
on active blocks. The minimum size parallelepiped containing all active blocks is built.
21.10.2. Translate & Rotate Grid 157

18.1
21.10.4. Update Grid

This calculation allows to update a grid locally based on selected markers and defined editing
radius.
• Markers:
– Marker. Name of loaded/created marker.

– Layer. ijk-layer which will be pulled to the selected marker.
• Mutable sections filter. Marker of wells selected by the filter are included in the
updating.
• Unused wells filter. Select wells around which their regions will be not edited.
• Max Radius of Changes. (METRIC: m, FIELD: f t ) To create the radius of changes

Voronoi Regions are built in order to define places, where the grid is updated and
where the grid is not updated.
• Power parameter. (METRIC: m, FIELD: f t ) Marker ”pulling” procedure is done us-

ing the Multilayer IDW method. This parameter is used in the formula of the Multilayer
IDW method.
21.11. Add Geological K to Grid 3D

This operation allows to display the index of the geological layer. When the model presents
faults, two cells from the same layer which are cut by a fault have the same layer index
value, but do not have the same k index. The k value for cells cut by faults is superior to the
last layer number (cf. figure 18). This operation allows as well:
• To compute a property by zones defined by the geological K;
• To obtain the number of geological layers when displaying the grid information;
• To set the IJK-filter according to the geological layers;
• To use the geological K number for computations in the calculator: ’K’ will correspond
to the geological number.
To use this option, an existing geological K cube containing the information about the ge-
ological index of the cells must be available (can be loaded with a Rescue file). To visualize
the geological number, use the information tooltip: click on the button tooltip situated on
the right panel or move the cursor holding the shift button. The geological layer index will
appear as a tip once the cursor will be moved on the model.

• Operation. Set or Clear the geological K;
21.10.4. Update Grid 158

18.1
Figure 18. Cells with the same geological K are highlighted in green. These cells presents
a true K value superior to the last layer number (10 in the illustrated case). For this cell,
the geological K calculation will show a value of 0, which corresponds to the geological
layer number.
• Geological K Property. Set the property containing the information about the geolog-
ical layer index.
21.12. Import Existing Model

The grid will be exported in Z-Corner format, i.e. using the keywords COORD (see 12.2.8),
ZCORN (see 12.2.9).
• File Name. Full path to the model file defining a grid. It is possible to define a grid
file (e.g. in the .GRDECL format), or the model *.data file, in which the grid file is
included in the model using the keyword INCLUDE (see 12.1.76).
• Add Zero Point As Well Head. Trajectories of wells are extended to the nearest point
on the XY surface if the top trajectory point is located visually below this surface.
• Input Syntax. A format of the input model (E1, IM, MO).
21.13. Calculate Grid Geometry Properties

This calculation allows to calculate geometry properties: block sizes along X, Y and Z, the
depth of the center and the top of each block.
21.12. Import Existing Model 159

18.1
• Calculate Block Sizes (DX): A new property name can be entered or an already
created property can be selected from the list. The calculated property gives the size of
each block along X;
• Calculate Block Sizes (DY): A new property name can be entered or an already
each block along Y;
• Calculate Block Sizes (DZ): A new property name can be entered or an already
each block along Z;
• Calculate Depth: A new property name can be entered or an already created property
can be selected from the list. The calculated property gives the depth of each block
center;
• Calculate Tops: A new property name can be entered or an already created property
can be selected from the list. The calculated property gives the mean of the four Z
coordinates of block tops.
21.14. Export
21.14.1. Export. Corner Point format
A grid will be exported in the Corner Point format, i.e. using keywords COORD (see 12.2.8),
ZCORN (see 12.2.9).
• File Name. Full path to the saving file.
• Output Units. Define a system of units of the exporting model: (METRIC, FIELD,
LAB).
21.14.2. Export. All Maps to GRID_ECL

Export all maps to GRID_ECL format.
• Output Folder. Full path to the output folder.
• N/A. Special number value (99999 by default) indicating that the property value is not
defined in this place.
• Output Units. Define a system of units of the exporting model: (METRIC, FIELD,
LAB).
21.14. Export 160

18.1
22. Grid Properties

In this section the possibilities to work with properties are described. The description of possi-
bilities to work with 3D grids is given in the section 3D-Grids. Model grids. In Calculations
menu to work with properties the following possibilities are available:
• Import. GRID_ECL (ASCII);
• Calculator;
• Interpolation;
• Facies Analysis;
• Auxiliary Calculations;
• Export;
• Regions;
• User Maps;
• Zones;
• Blocked Wells.
22.1. Import. GRID_ECL (ASCII)

• File Name. Full path to the file with a map.
• Preview. Number of Lines. Number of lines shown in the Preview window.
• Map. Select a loaded map name.
22.2. Calculator
22. Grid Properties 161

18.1
22.3. Interpolation
The following interpolations and stochastical simulations methods are available for Geology
Designer module for continuous properties:
• Interpolation: Multilayer IDW method;
• Interpolation: Multilayer Kriging;
• Interpolation: Multilayer SGS;
• Interpolation: SGS 3D;
• Interpolation: Kriging 3D;
• Interpolation: Trivial interpolation.
22.3.1. Interpolation: Trivial interpolation

In this section a specification on implementation of the interpolation method to edit the
object is given. A general description of the method, formulas and details of the use of
multipliers and coefficients, mentioned in this section, are given in the section Multilayer
trivial interpolation method.
To interpolate a property the following parameters should be defined:
• Well Filter. An interpolation is carried out based on wells selected in the filter.
• Well Log. Choose a well log based on which a property is interpolated.
• Interpolate Log. If the check-box is checked, in case of the lack of log curve data for
some intervals of well’s trajectory, first, the log curve will be interpolated over these
intervals.
• Default Value. If input data for an interpolation of a layer do not exist the absent layer
data are assigned by the default value.
• Property. Choose a property name for which data are interpolated.
22.3.2. Interpolation: Multilayer IDW method

• Property. Property name for which data are interpolated.
22.3. Interpolation 162

18.1
• Cut by Log Bounds. Each log curve has its minimum and maximum. If this option
is activated, the interpolated values higher than the maximum and lower than the
minimum, are replaced by maximum and minimum log curve values, respectively.
• Filter. If this option is activated the following parameters have to be set:
- Cut. The interpolation is carried out only in the blocks which satisfy the condition
which is set. Select the property from the list and set the condition using the
operator and entering the value in the field. An interpolation between the filtered
area values and values in the area outside of the filter is performed, which leads
to a smoother transition.
• Trend. If this option is activated, additional parameters have to be set. If Trend Type is
- Arbitrary Property, then the option Trend Type allows to choose an available
property as a trend. This means that instead of an interpolation of initial data taken
from log curves the differences between values of log curves and trend’s values
are interpolated. Further, property values of the trend are added to the obtained
results.
- VPC, then the property is built based on the VPC and the 2D Map, which is
used as a trend for the interpolation. If Trend Property is not selected then the
property is built based on VPC. The resulting property (trend) is not saved during
the calculation. The interpolation process is described in details in the section
Auxiliary Calculations. Property by Well Log Distribution (experimental).
• Well Filter. The interpolation is performed only for the wells selected in the filter.
• Well Log. Choose the well log for the computation.
• Interpolate Log. If this option is activated, in case of the lack of data for some intervals,
first, the log curve will be interpolated over these intervals.
• Empty Layer Value. Allows to assign a constant value for layers without data.
• Power Parameter. This parameter is used in the formula of the Multilayer IDW method.
22.3.3. Interpolation: Multilayer Kriging

22.3.3. Interpolation: Multilayer Kriging 163

18.1
results.
A variogram has to be chosen for the computation. If there is no available variogram in

the project, it is necessary to create it. To compute a variogram, the option Go To Variogram
Properties can be used. This option is a shortcut to the tab Others which allows to manage
the variogram parameters.
Define a type of Kriging, which will be used to interpolate the property:
• Simple.
• Ordinary.
• Universal.
22.3.3. Interpolation: Multilayer Kriging 164

18.1
22.3.4. Interpolation: Multilayer SGS

Simulation method.
results.
22.3.4. Interpolation: Multilayer SGS 165

18.1
• Variogram. A variogram has to be chosen for the computation. If there is no available

variogram in the project, it is necessary to create it. To compute a variogram, the option
Go To Variogram Properties can be used. This option is a shortcut to the tab Others
which allows to manage the variogram parameters.
• Adjust to Source Distribution. This option is active if Trend (see above) is not chosen
for interpolation. If the check-box is checked then the distribution of the selected Well
Log is taken into account for the SGS interpolation.
• Kriging Radius. (METRIC: m, FIELD: f t )If the Kriging radius is set to 0, it

is considered that the radius is not constrained and the nearest points are taken
into account according to the Kriging Points value which is set.
• Kriging Points.
• Random number.
22.3.5. Interpolation: Kriging 3D

• Space Type. selection of the space used for the interpolation. IJK space allows to inter-
polate along geological layers, (cf. figure 19);
results.
- VPC, then the property is built based on VPC and 2D Map, which is used as
a trend for interpolation. If Trend Property is not selected then the property is
built based on VPC. The resulting property (trend) is not saved during the calcu-
lation. The interpolation process is described in details in the section Auxiliary
Calculations. Property by Well Log Distribution (experimental).
22.3.5. Interpolation: Kriging 3D 166

18.1
operator and entering the value in the field;
• Adjust to Source Distribution. This option is active if the Trend (see above) is not
chosen for interpolation. If the check-box is checked then distribution of the selected
Well Log is taken into account for the SGS interpolation.
• Global Mean. Setting of the global mean for the distribution (the data is assumed to be
stationary).
22.3.6. Interpolation: SGS 3D

Simulation method.

• Space Type. Selection of the space used for the interpolation. IJK space allows to
interpolate along geological layers, (cf. figure 19);
• Trend. If this option is activated, additional parameters have to be set. If Trend Type
is
results.
22.3.6. Interpolation: SGS 3D 167

18.1
- VPC, then the property is built based on VPC and 2D Map, which is used as
a trend for interpolation. If Trend Property is not selected then the property is
built based on VPC. The resulting property (trend) is not saved during the calcu-
lation. The interpolation process is described in details in the section Auxiliary
Calculations. Property by Well Log Distribution (experimental).
• Interpolate Log. If this option is activated, in case of the lack of data for some
intervals, first, the log curve will be interpolated over these intervals.

• Global Mean. Setting of the global mean for the distribution (the data is assumed to
be stationary);
• Kriging Radius. If the Kriging radius is set to 0, it is considered that the radius is
not constrained and the nearest points are taken into account according to the Kriging
Points value which is set. (METRIC: m, FIELD: f t )
• Kriging Points.
• Random number.
22.4. Facies Analysis

For all the methods presented here, a template has to be associated to the facies log (Select
a log template). To perform facies modeling (discrete properties modeling) the following
options are available:
• Facies Analysis and Discrete properties modeling: Trivial interpolation;
• Facies Analysis and Discrete properties modeling: Multilayer IDW method;
• Facies Analysis and Discrete properties modeling: Multilayer Kriging;
• Facies Analysis and Discrete properties modeling: Multilayer SGS;
22.4. Facies Analysis 168

18.1
• Facies Analysis and Discrete properties modeling: Kriging 3D;

• Facies Analysis and Discrete properties modeling: SGS 3D.
22.4.1. Facies Analysis and Discrete properties modeling: Trivial interpolation

multipliers and coefficients, mentioned in this section, are given in the section Multilayer
trivial interpolation method.
At the end of the computation, a lithology template has to be assigned to the property in
order to visualize the facies categories (Select a log template). To interpolate a property the
following parameters should be defined:
• Well Filter. An interpolation is carried out based on wells selected in the filter.
• Well Log. Choose a well log based on which a property is interpolated.
• Interpolate Log. If the check-box is checked, in case of the lack of log curve data for
some intervals of the well trajectory, first, the log curve will be interpolated over these
intervals.
• Default Value. If input data for an interpolation of a layer do not exist the absent layer
data are assigned by the default value.
• Property. Enter a name or select an existing result property.
22.4.2. Facies Analysis and Discrete properties modeling: Multilayer IDW method
order to visualize the facies categories (Select a log template). To build the property the
22.4.1. Facies Analysis and Discrete properties modeling: Trivial interpolation 169
18.1
results.
• Power Parameter. This parameter is used in the formula of the Multilayer IDW method.
22.4.3. Facies Analysis and Discrete properties modeling: Multilayer Kriging

order to visualize the facies categories (Select a log template). To interpolate the property the
22.4.3. Facies Analysis and Discrete properties modeling: Multilayer Kriging 170
18.1
results.
• Variogram. It is necessary to choose an available variogram for each facies. If there is no
variogram it is necessary to create it. The tab Others can be used to define variogram
parameters.
• Kriging type. Define a type of Kriging which will be used to interpolate a property:
• Simple.
• Ordinary.
• Universal.
22.4.4. Facies Analysis and Discrete properties modeling: Multilayer SGS

and coefficients, mentioned in this section, are given in the section Sequential Gaussian
Simulation method.
order to visualize the facies categories (Select a log template). To interpolate a property the
22.4.4. Facies Analysis and Discrete properties modeling: Multilayer SGS 171
18.1
results.
• Variogram. It is possible to choose available variogram for interpolation. If there is no

variogram it is necessary to create it. To do this Go To Variogram Properties. Use
• Kriging Radius. (METRIC: m, FIELD: f t )If the Kriging radius is set to 0, it is con-
sidered that the radius is not constrained and the nearest points are taken into account
according to the Kriging Points value which is set.
• Kriging Points.
• Random number.
22.4.4. Facies Analysis and Discrete properties modeling: Multilayer SGS 172
18.1
22.4.5. Facies Analysis and Discrete properties modeling: Kriging 3D

For this method, a blocked wells property has to be computed first (21). It is also important
to assign a discrete template to the log in order to be able to select the facies categories for
the computation (Select a log template).
Parameters of this method being common for other interpolation methods are described
in the section 22.3.
multipliers and coefficients, mentioned in this section, are given in the section Kriging.
• Interpolate in LGR. The activation of this option allows to take LGRs into account for
the interpolation. The interpolation is performed within LGR blocks. If this option is
not activated, the interpolation is performed as if the LGRs were not created;
• Space Type. Selection of the space used for the interpolation. IJK space allows to inter-
◦ Cut. The interpolation is carried out only in the blocks which satisfy the condition
• Blocked Wells Log. Selection of the blocked wells log for the interpolation. See
23. Blocked Wells for working with blocked wells.
• Facies (list). Define the facies which will be used to interpolate the property. If the box
Use is checked in the list of facies, the corresponding facies will be included to the
computation. The list is displayed only if a discrete template was assigned to the facies
well log before the computation of the blocked wells (23.1).
All the following parameters have to be set for each facies. First, click
! on a facies in the list, then set the parameters and click on a second
facies to set all the parameters again. Note that a variogram has to be
set for each facies.
◦ Property, the property has to be chosen from the list. This means that instead of an
interpolation of initial data taken from log curves the differences between values
of log curves and trend’s values are interpolated. Further, property values of the
trend are added to the obtained results.
22.4.5. Facies Analysis and Discrete properties modeling: Kriging 3D 173

18.1
◦ VPC, then the property is built based on the VPC.

◦ 2D Map, then the property is built based on the selected 2D Map. The interpolation
process is described in details in the section Auxiliary Calculations →Property
by Well Log Distribution (experimental).
• Facies Fraction. Method which will be used to compute the facies proportion for each
facies. Note that a facies has to be selected from the list.
◦ Blocked Wells log. The proportion set is the one which is computed from the
blocked wells log;
◦ Well Log. The proportion set is the one computed from raw data log;
◦ Trend Property. The proportion set is the one computed from the trend property;
◦ Manual. The proportion is set manually. The value has to be entered in the field;
◦ No adjustement. The proportion is not set.

parameters.
• Azimuth Map 2D. The kriging is performed according to the azimuth given by the loaded
2D map (optionally).
22.4.6. Facies Analysis and Discrete properties modeling: SGS 3D

and coefficients, mentioned in this section, are given in the section Sequential Gaussian
Simulation method.
For this method, a blocked wells property has to be computed first (21). It is also important
to assign a discrete template to the log in order to be able to select the facies categories for
the computation (Select a log template). To interpolate a property the following parameters
should be defined:
• Interpolate in LGR. The activation of this option allows to take LGRs into account for
the interpolation. The interpolation is performed within LGR blocks. If this option is
not activated, the interpolation is performed as if the LGRs were not created;
• Space Type. Selection of the space used for the interpolation. IJK space allows to inter-
22.4.6. Facies Analysis and Discrete properties modeling: SGS 3D 174

18.1
◦ Cut. The interpolation is carried out only in the blocks which satisfy the condition
• Blocked Wells Log. Selection of the blocked wells log for the interpolation. See
23. Blocked Wells for working with blocked wells.
• Facies (list). Define the facies which will be used to interpolate the property. If the box
Use is checked in the list of facies, the corresponding facies will be included to the
computation. The list is displayed only if a discrete template was assigned to the facies
well log before the computation of the blocked wells (23.1).
All the following parameters have to be set for each facies. First, click
! on a facies in the list, then set the parameters and click on a second
facies to set all the parameters again. Note that a variogram has to be
set for each facies.
◦ Property, the property has to be chosen from the list. This means that instead of an
interpolation of initial data taken from log curves the differences between values
of log curves and trend’s values are interpolated. Further, property values of the
trend are added to the obtained results.
◦ VPC, then the property is built based on the VPC.
◦ 2D Map, then the property is built based on the selected 2D Map. The interpolation
process is described in details in the section Auxiliary Calculations →Property
by Well Log Distribution (experimental).
• Facies Fraction. Method which will be used to compute the facies proportion for each
facies. Note that a facies has to be selected from the list.
◦ Blocked Wells log. The proportion set is the one which is computed from the
blocked wells log;
◦ Well Log. The proportion set is the one computed from raw data log;
◦ Trend Property. The proportion set is the one computed from the trend property;
◦ Manual. The proportion is set manually. The value has to be entered in the field;
◦ No adjustement. The proportion is not set.

parameters.
22.4.6. Facies Analysis and Discrete properties modeling: SGS 3D 175

18.1
• Azimuth Map 2D. The kriging is performed according to the azimuth given by the loaded
2D map (optionally).
• Kriging Radius. (METRIC: m, FIELD: f t )If the Kriging radius is set to 0, it is con-
sidered that the radius is not constrained and the nearest points are taken into account
according to the Kriging Points value which is set.
• Kriging Points.
• Random number.

For auxiliary calculations it is recommended to create User Maps, since the interpolation
results are written into the selected map.
• Calculate Geometrical Volume;
• Calculate Pore Volume;
• Calculate Volumetric Properties;
• Connected Components;
• Grid & Faults Intersection Property;
• 3D Voronoi Regions;
• Multilayer Voronoi Regions;
• Calculate Cut by Polygon;
• Calculate Cut by Wells;
• Create Property by Zones;
• Edit Property Inside Polygon;
• Calculate Property by VPC and 2D Map;
• Property by Well Log Distribution (experimental);
• Assign between surfaces.
22.5.1. Calculate Geometrical Volume

This calculation allows to compute the volume of each cell (see figure 20 for more details
about the calculated properties).
• Output. Result Property.
A grid for storing the computed property has to be chosen from the list.
22.5. Auxiliary Calculations 176

18.1
22.5.2. Calculate Pore Volume

This calculation allows to compute the pore volume (corresponding to the product of the
net volume and the porosity) for each cell. The following parameters have to be set (see
figure 20 for more details about the calculated properties):
• Source Data.
◦ Porosity. The porosity property has to be chosen from the list;

◦ ACTNUM. If the ACTNUM (see 12.2.29) property is available, it can be set by this
option;
◦ NTG. If the Net-to-Gross property is computed, it can be set to be taken into
account for the pore volume estimation;
◦ MULTPV. If the pore volume multiplier property (corresponds to the keyword
MULTPV, see 12.2.28) is available, it can be set to be taken into account for the
pore volume estimation. This property can be created via by right mouse button
click on Properties.
• Output.
◦ Result Property. A grid for storing the computed property has to be chosen from
the list.
22.5.3. Calculate Volumetric Properties

This calculation allows to compute the volume of hydrocarbon in the reservoir. This compu-
tation provides a static measure of oil and gas in place. For more details about the calculated
properties, see figure 20.
The formulas used for these computations are presented in the following table:
Calculated Property Formula

Net Volume Vnet = Vrock · NG
Pore Volume Vpore = Vnet · φ
HCPV HCPV = Vpore · (1 − Sw )
STOIIP ST OIIP = HCPVoil . B1O
Associated Gas Associated Gas = ST OIIP · RS
GIIP GIIP = HCPVgas · B1g
Associated Liquid Associated Liquid = GIIP · Rv
Recoverable Oil Recoverableoil = (ST OIIP + Associated Liquid) · Recovery Factoro
Recoverable Gas Recoverablegas = (GIIP + Associated Gas) · Recovery Factorg
22.5.3. Calculate Volumetric Properties 177

18.1
Direction of
interpolation for
IJK space type
Direction of
interpolation for
XYZ space type
Figure 19. IJK and XYZ directions of interpolation. IJK space allows to interpolate along
geological layers.
Geometrical Net volume Pore volume

volume
Reservoir HCPV
×N/G Reservoir
×POR × Oil saturation
conditions STOIIP
Non-reservoir
or GIIP
layers /Bo , Bg
Reservoir
Non-reservoir
layers
Reservoir
Figure 20. Volume computation for fluid-in-place. The Geometrical volume contains both
reservoir and non-reservoir layers. The Net Volume contains only reservoir rocks (it cor-
responds to the product between the Geometrical Volume and the Net to Gross). The Pore
Volume corresponds to the pore space (it is defined as the Net Volume multiplied by the
porosity). The HCPV (Hydrocarbon Pore Volume) corresponds to the volume of hydrocar-
bons obtained without taking into account the formation volume factor. The STOIIP and
GIIP corresponds to the volumes of hydrocarbon in place in reservoir conditions.

18.1
The variables used for the computation are defined below:
Variable Definition
Vnet Net Volume
Vrock Geometrical Volume
HCPV Hydrocarbon pore volume
STOIIP Stock Tank Oil Initially In Place
GIIP Gas Initially In Place
Rs Gas Oil Ratio
Rv Liquid Gas Ratio
Bo Oil Formation Volume Factor
Bg Gas Formation Volume Factor
As inputs, the following parameters have to be set :
• Source Data.
◦ General.
– NTG. The net-to-gross property has to be selected from the list;

– Porosity. The porosity property has to be selected for the computation.
◦ Contacts.
– Gas-Oil Contact. Select the Gas-Oil contact which will be taken into account
for the computation (see Contacts to create a contact). When both GOC and
gas saturation are defined, the computation is predominantly performed using
the contact;
– Oil-Water Contact. Select the Oil-Water contact which will be taken into ac-
count for the computation (see Contacts to create a contact). When both WOC
and oil saturation are defined, the computation is predominantly performed
using the contact.
◦ Saturations.
– Saturations of Water. The property containing water saturation values has to

be chosen from the list;
– Saturation of Oil. The property containing oil saturation values has to be
chosen from the list;

18.1
– Saturation of Gas. The property containing gas saturation values has to be

chosen from the list.
◦ Oil.
– FVF for Oil (BO). The property containing Formation Volume Factor values
has to be chosen from the list;
– RS. The property containing dissolved GOR values has to be chosen from the
list;
– Oil Recovery Factor. The property containing Oil Recovery Factor values has
to be chosen from the list;
– Oil Density. The property containing Oil Density values has to be chosen from
the list;
◦ Gas.
– FVF for Gas (BG). The property containing the Formation Volume Factor
values has to be chosen from the list;
– RV. The property containing volatilized oil/gas ratio values has to be chosen
from the list;
– Gas Recovery Factor. The property containing Gas Recovery Factor values
has to be chosen from the list;
– Gas Density. The property containing Gas Density values has to be chosen
from the list;
• Output.
All output properties are optional.
◦ Geometrical Volume. This option allows to compute a cube corresponding to the

Geometrical Volume (i.e. the rock volume, keyword ROCKV, see 12.15.88) and
store it as a property in the project. An empty property to store the computation
result has to be selected from the list.
◦ Net Volume. This option allows to compute a cube corresponding to the Net Vol-
ume (i.e. the reservoir volume) and store it as a property in the project. An empty
property to store the computation result has to be selected from the list.
◦ Pore Volume. This option allows to compute a cube corresponding to the Pore
Volume (i.e. the product of the net volume by the porosity) and store it as a
property in the project. An empty property to store the computation result has to
be selected from the list.
◦ HCPV. Hydrocarbon pore volume. This option allows to compute a cube corre-
sponding to the HCPV (i.e. the product of the pore volume by the oil or gas
saturation) and store it as a property in the project. An empty property to store
the computation result has to be selected from the list.

18.1
◦ Oil.
– STOIIP. Stock Tank Oil Initially in Place. This option has to be selected in
order to compute a cube corresponding to the STOIIP. An empty property to
store the computation result has to be selected from the list.
– STOIIP (Mass). Mass of Stock Tank Oil Originally in Place. This option
has to be selected in order to compute a cube corresponding to the mass of
STOOIP. An empty property to store the computation result has to be selected
from the list.
– Associated Gas. This option has to be selected in order to compute a cube cor-
responding to the Associated Gas. An empty property to store the computation
– Recoverable Oil. This option has to be selected in order to compute a cube
corresponding to the Recoverable Oil. An empty property to store the com-
putation result has to be selected from the list.
– Recoverable Oil (Mass). This option has to be selected in order to compute
a cube corresponding to the mass of Recoverable Oil. An empty property to
◦ Gas.
– GIIP. Gas Initially in Place. This option has to be selected in order to compute
a cube corresponding to the GIIP. The property which will contain the values
has to be selected from the list.
– GIIP (Mass). Mass of Gas Initially in Place.
– Associated Oil. This option has to be selected in order to compute a cube cor-
responding to the Associated Oil. An empty property to store the computation
– Recoverable Gas. This option has to be selected in order to compute a cube
corresponding to the Recoverable Gas. An empty property to store the com-
putation result has to be selected from the list.
– Recoverable Gas (Mass). This option has to be selected in order to compute
a cube corresponding to the mass of Recoverable Gas. An empty property to
22.5.4. Connected Components

The calculation allows to build connected components. A connected component is a part of
the model, where blocks are connected via faces or edges. This means that all blocks of one
connected component can be continuously bypassed along block edges. ”Bypass” from one
component to another is not possible.
A connected component is a part of the model; blocks through which the flow is possible.
Blocks links can be geometrical (the case if blocks have the intersection of a nonzero area)
or special, such as PINCH (see 12.2.56) or NNC (see 12.2.50).
22.5.4. Connected Components 181

18.1
• Output:
– Result Map. Property name in which the calculation result is written.
• Source Data:
– Cut. Choose ACTNUM property.

– Iteration Property. The map of distances from the randomly selected block at
the beginning of calculation to other blocks. The distance is measured in blocks
using the following rule: the distance from a block to the neighbouring block is
equal to one. This map allows to identify blocks connecting two parts of the grid.
It can be useful if we suppose that the model has several connected components,
but the result of calculation is different.
22.5.5. Grid & Faults Intersection Property

An integer number is assigned to all blocks, in which a fault intersects with a grid. The
calculation is done for all available faults. Thus, the values of blocks, in which F1 fault
intersects with a grid, are equal to 1, for F2 fault the values of blocks are 2 etc.
• Output. Result Property. Name of the grid that the calculation will be saved into.
22.5.6. 3D Voronoi Regions

The difference of 3D Voronoi Regions from Multilayer ones is to that the distance from a
well to blocks is calculated in all three directions. A horizontal well passes through several
blocks, hence the distance from a block to a well is a minimum distance from the block to
one of the well’s blocks.
• Property. Map name in which the calculation result is written.
• Well Filter. Use for Voronoi regions construction wells selected by filter.
• Use Radius. (METRIC: m, FIELD: f t ) By default each block is included in one of

Voronoi regions. If this option is activated and the radius is defined then the blocks
located outside of the circle of this radius are not included in Voronoi regions.
22.5.7. Multilayer Voronoi Regions

Multilayer Voronoi Regions are built in each grid layer independent from other layers. If
a well passes through the block with coordinates (x1 , y1 , z1 ), but does not pass through the
block (x1 , y1 , z2 ), then in the layer corresponding to the z1 coordinate the Voronoi region is
built, but in the layer corresponding to the z2 coordinate the Voronoi region is not built. See
the description of 3D Voronoi Regions.
• Output:
22.5.5. Grid & Faults Intersection Property 182

18.1
– Result Property. Map name in which the calculation result (Voronoi Regions
map) is written.
• Source Data:
– Well Filter.
– Use Radius. (METRIC: m, FIELD: f t )
22.5.8. Calculate Cut by Polygon

• Output. Result Property. Name of the resulting property.
• Source Data. Polygon. Select a polygon, which will be used for calculation of the
property. The values of blocks inside the polygon are assigneded to 1, the values of
other blocks are assigneded to 0.
22.5.9. Calculate Cut by Wells

• Output:
– Reuslt Property. Name of the resulting property.
• Source Data:
– Well Filter. Use for calculation only wells selected by the filter.
– Radius. (METRIC: m, FIELD: f t ) All blocks located in the circle of defined
radius with the center in the well are assigned with 1.
22.5.10. Create Property by Zones

• Result Property. Name of the resulting property.
• Zone. Create a map based on the defined zone. Using Zones it is possible to create
an arbitrary subregion in the grid and assign it with an arbitrary value. Moreover, the
property in this region is replaced by the defined value. The property in blocks, which
is not used for creation of zone, is equal to zero. The detailed description of zone
creation is given in the section Zones.
22.5.11. Edit Property Inside Polygon

• Property. Name of the resulting property.
• Polygon. Select a polygon inside which the blocks value are edited.
• Stored Value. Blocks inside a polygon is assigned with the define value.
22.5.8. Calculate Cut by Polygon 183

18.1
22.5.12. Calculate Property by VPC and 2D Map

The calculation allows to extrapolate VPC data on property using 2D Map selected in Map
2D as a trend. Thus, it is necessary to calculate a value in each block of 3D grid (i, j, k),
where i = 1, .., Nx , j = 1, .., Ny , k = 1, .., Nk , using known values of 2D Map defined at points
(i, j) and Nk values of VPC. Further VPC values are normalized on the unit interval [0,1].
Then, values of property in the k -th layer is calculated as a map’s values at points (i, j)
multiplied by k -th value of VPC. If 2D Map is not selected, then to all property’s value in
the k -th layer are assigned the k -th value of VPC.
• Well Log. Choose a well log based on which the property will be interpolated.
• Well Filter. Interpolation will be carried out based on wells selected by the filter.
• 2D Map. If the check-box is checked then the VPC is normalized and used as co-
efficient for property’s values in the corresponding k layer. Otherwise, all property’s
values in the k -th layer are imposed to be equal to VPC values for the k -th layer.
• Discrete Interpolation. The maximum log value in this block is assign with a block
value.
• Interpolate Log. If the check-box is checked, in case of the lack of log curve data in
some intervals, first, the log curve will be interpolated over these intervals.
22.5.13. Property by Well Log Distribution (experimental)

The calculation allows to compute, for example, permeability based on porosity. In tNavigator
Core Data, poro and perm are stored in log curves. For each log curve values of porosity
is subdivided by intervals of length defined in Step of Base Data. For each interval a
permeability distribution is defined based on the constructed histogram. The process of
creation of histogram is the following: a range of values of porosity in the selected interval
is subdivided to create subrange; for each subrange the number of values of premiability is
counted. Finally, to calculate permeability by porosity, for each porosity value the permability
value is selected randomly based on the permeability distribution in the interval of porosity’s
values, to which considered porosity value belongs.
• Result Property. Property, in which a result for interpolation will be saved.
• Base Log. Define a Log based on which interpolation has been carried out.
• Base Property. Define a property based on which interpolation has been carried out.
• Step of Base Data. Define a length of interval using which a base log curve will be
partitioned.
• Log for Result. Define a Log based on which a result property will be built.
22.5.12. Calculate Property by VPC and 2D Map 184

18.1
22.5.14. Assign between surfaces

This calculation is assigned value to blocks located between horizons. Tuning settings:
• Top. If this check-box is not checked then a top grid layer is consider as a top boundary.
Otherwise, it is necessary to define the following parameters:
– What to Use. Use as a top boundary one of the following objects: Horizon or
Depth (METRIC: m, FIELD: f t ) .
– Top boundary value: Horizon or Depth (METRIC: m, FIELD: f t ) depends on
the above selected object.
• Bottom. If this check-box is not checked then a bottom grid layer is consider as a
bottom boundary. Otherwise, it is necessary to define the following parameters:
– What to Use. Use as a top boundary one of the following objects: Horizon or
Depth (METRIC: m, FIELD: f t ) .
– Bottom boundary value: Horizon or Depth (METRIC: m, FIELD: f t ) depends
on the selected above object.
• Polygon. Property’s boundaries in X and Y directions are defined by polygon’s bound-

aries.
• Value inside. Define blocks values inside the area. There are three possibilities to do
this:
– Value. Assign an arbitrary value to blocks. This value is defined below.

– Do not change. Do not change current value assigned to blocks.
– Undefined. Do not assign any value to blocks.
• Value outside. Define blocks values outside the area. There are three possibilities to
do this:
– Value. Assign an arbitrary value to blocks. This value is defined below.

– Do not change. Do not change current value assigned to blocks.
– Undefined. Do not assign any value to blocks.
22.5.14. Assign between surfaces 185

18.1
22.6. Export
The Export function is available for all the geometry objects and is accessible from Calcula-
tions window.
1. Save 3D.
File type: Array of the property values (tNavigator format).
File format – .txt.
Data description: values of parameter are written to the file for all grid blocks. The
coordinates of blocks ascending by X, Y, Z. The following parameters have to be set:
• Property. Indicates the property which will be exported;

• File Name. Full path to the folder in which the property will be exported;
• Export as Integer. Allows to import the property as an integer;
• Keyword. Specify the keyword corresponding to the exported property;
• Inactive Block Placeholder – a number which specifies that property value in
respective block is absent;
• Separate Layers by Comment – each layer in the file will be headed by its
number;
• Units. Specify the units of the property.
Example of this file format

--Map: Depth
--Time step: 0
Depth
-- Layer 1 --
+2.748260e+003 +2.742420e+003 +2.742420e+003 +2.737400e+003
+2.737400e+003 +2.733930e+003 +2.733930e+003 0 0 0 0 0
0 0 0 0 0 0
2. Save 3D as ACTNUM
File type: the array of active (corresponding 1 value) and inactive blocks (correspond-
ing 0 value) is saved.
File format – .inc.
Data description: values 1 and 0 are written to the file for all grid blocks. The coordi-
nates of blocks ascending by X, Y, Z. The following parameters have to be set:
• Property. Indicates the property which will be exported.

• File Name. Full path to the folder in which the property will be exported.
22.6. Export 186

18.1
• Separate Layers by Comment – each layer in the file will be headed by its
number.
Syntax corresponds to the keyword ACTNUM (see 12.2.29).

-- Map: Map
-- Time step: 0
ACTNUM
-- Layer 1 --
+0 +0 +0 +0 +0 +0
+0 +0 0 0 0 0
0 0 0 0 +0 +1
+1 +1 +1 0 0 0
+1 +1 +1 +1 +1
+1 +1 +1 +1 +1 +1
3. Save 3D to .grd
File type: Binary file.
File format – .grd.

• Keyword. Specify the keyword corresponding to the exported property;
• Title. Title of the property which will appear in the header of the file;
respective block is absent.
4. Save 3D to Wellpics
Based on Cut. Export data for blocks which satisfy a user cut condition. The cut can
be selected from the list and the condition has to be set using the = and 6= signs.
Well Filter. Export data for wells satisfying the well filter.
Export Value:
• Values Along Well. All property values along well are exported. If the field
Get Value From Property (below in the dialog) is active then the value of the
respective function of these numbers is calculated and exported;
• First Intersection Point Value. The block value of the first connection is ex-
ported. If the field Get Value from Property (below in the dialog) is active, then
the value of the respective 2D map is exported, according to the option which is
chosen.
22.6. Export 187

18.1
Get Value From Property. If the option is activated, the value of the root mean
square, the minimum, the maximum, the average, or the sum of the respective 2D map
is exported according to the Export Value type.
Units. Specify the units of the property.
File type: IJK data.

File format – no format is specified.
Data description: Text file with the following data: well name, IJK coordinates of block
with connection, value of parameter in this block.
’102’ 1 4 1 0.175400
’102’ 1 4 2 0.175400
’102’ 1 4 3 0.175400
’103’ 7 4 1 0.176300
’103’ 7 4 2 0.176300
’103’ 7 4 3 0.176300
File type: Block center data.

File format – no format is specified.
Data description: Text file with the following data: well name, XYZ (meters) of center
of block with connection, value of parameter in this block.
’102’ 0.000000 300.000000 2735.030000 0.175400
’102’ 0.000000 300.000000 2740.030000 0.175400
’102’ 0.000000 300.000000 2745.030000 0.175400
’103’ 600.000000 300.000000 2719.000000 0.176300
’103’ 600.000000 300.000000 2724.000000 0.176300
’103’ 600.000000 300.000000 2729.000000 0.176300
5. Save 3D to .xyz
File type: Save a 3D property in .xyz format.
File format – .xyz.
Data description: Layer index (optional) X coordinate of the block (meters), Y coordi-
nate of the block (meters), Z coordinate of the block (meters), value of the parameter
in this block.
22.6. Export 188

18.1

40 9534151.489700 4999493.969697 363.339050 0.000000
39 9534151.489700 4999493.969697 362.683533 1.000000
38 9534151.489700 4999493.969697 362.028011 0.000000
37 9534151.489700 4999493.969697 361.372494 0.000000
36 9534151.489700 4999493.969697 360.716980 1.000000
35 9534151.489700 4999493.969697 360.061462 0.000000
34 9534151.489700 4999493.969697 359.405945 0.000000
33 9534151.489700 4999493.969697 358.750427 1.000000

• Write Layer Index. If this option is activated, the layer index will be written in
the exported file, as shown in the example;
6. Save 2D to Surfer .grd

File format – .grd.
Data description: Text file for the program Surfer.
DSAA
40 65
-50 3950
-50 6450
30.2647 564.92
+57.4933 +58.4596 +59.4258 +60.392 +61.3583 +62.4282
+65.0649 +69.8945 +75.5536 +81.2801 +87.2017 +94.5382
+110.626 +124.216 +126.598 +123.544 +120.511 +117.151
+108.631 +98.4625 +87.8773 +79.3242 +73.3193 +67.9514

• Layer Index. Indicate the index layer which will be exported;
• Units. Specify the units of the property;
22.6. Export 189

18.1
7. Save 2D to .xyz
File type: XY data. Save 2D map in .xyz format.
Data description: X coordinate of the block (meters), Y coordinate of the block (me-
ters), value of the parameter in this block.
0.000000e+000 0.000000e+000 5.749330e+001
1.000000e+002 0.000000e+000 5.845960e+001
2.000000e+002 0.000000e+000 5.942580e+001
3.000000e+002 0.000000e+000 6.039200e+001
4.000000e+002 0.000000e+000 6.135830e+001
5.000000e+002 0.000000e+000 6.242820e+001
6.000000e+002 0.000000e+000 6.506490e+001
File type: IJ data. Save 2D map in .xyz format.

Data description: block numbers along X, Y axes, value of the parameter in this block.
1 1 5.749330e+001
2 1 5.845960e+001
3 1 5.942580e+001
4 1 6.039200e+001
5 1 6.135830e+001
6 1 6.242820e+001
7 1 6.506490e+001
8 1 6.989450e+001

• Layer Index. Indicate the index layer which will be exported;
• Format. Specify the type of format for the export (X Y or i j.);
8. Save 2D to .cps (CPS-3 ASCII)

File format – .cps.
Data description: To save a 2D property in this format one can specify the number of
22.6. Export 190

18.1
values along the axes X and Y, ascending or descending order of blocks on the axes.
The resulting data array can be transposed (reflected relatively to the main diagonal).
FSASCI 0 1 COMPUTED 0 1.000000e+030
FSATTR 0 0
FSLIMI -33.3333 3933.3333 -33.3333 6433.3333 30.2647 564.9200
FSNROW 195 120
FSXINC 33.333333 33.333333
-> generated by tNavigator
259.6710000 259.6710000 259.6710000 267.4820000 267.4820000
267.4820000 271.0630000 271.0630000 271.0630000 271.8970000
271.8970000 271.8970000 271.9130000 271.9130000 271.9130000
271.7910000 271.7910000 271.7910000 271.6340000 271.6340000
22.7. Regions
Allows to define regions in the model. The following options are available by right mouse
button click:
• Add regions. Selection of the type of regions which will be created. Each model of
regions can be edited in Calculations window or with the brush tool available in 2D.
• Create FIP Regions. Allows to create a FIP region.
• Erase. Erases all the regions.
22.8. User Maps

The properties created by users can be used as inputs and outputs for auxiliary calculations,
used for computations in calculator, or exported.
22.9. Zones
Use to create a map based on the defined zone (see Create Map by Zones)
To define a zone right click on zone_id and choose Edit in the drop-down menu. In the
appeared table define the following parameters:
• Use. Use or not selected zone.
• Name. Name of zone.
• Value. Arbitrary integer number.
• I1. Beginning of the selected range along X axis.
22.7. Regions 191

18.1
• I2. End of the selected range along X axis.
• J1. Beginning of the selected range along Y axis.
• J2. End of the selected range along Y axis.
• K1. Beginning of the selected range along Z axis.
• K2. End of the selected range along Z axis.
All blocks included in the defined region are assigned to selected value. Other blocks present
zero values.
22.9. Zones 192

18.1
23. Blocked Wells

Blocked Wells are created as grid objects and are available in Geometry Objects. It can be
visualized in 3D, Well Section, and Histograms tabs. Blocked Wells option allows to assign
log data points to the grid in the blocks situated along the well path. Reservoir grids have
cells that are generally at a much coarser resolution than that at which well data is sampled.
So, well data should first be upscaled to the resolution of the reservoir grid block. The data
that intersects the grid can be scaled up to the grid resolution by blocking the values into the
grid and then calculating statistics for those values. During the interpolation these "blocked"
values along the wells will be used in order to populate the entire grid.
23.1. Select a log template

In order to compute blocked wells, the log template has to be set (to indicate if the property
is a continuous or a discrete one). The template editor is available by right mouse button
click on the log curve and selecting Object Setting. A template can be selected from the list
of available templates. It is possible to edit a template or to create a new one by clicking
on the ellipsis button. A new template can be added by clicking on the Add New Template
button, corresponding to the green "+" icon. The new template appears in the list and can be
modified in the field Info and Palette in the right part of the List of Templates window. In
Info, the following parameters can be set:
• Name. A new name can be entered;
• Type. Selection of the template type: Discrete or Continuous;
• Numeric Precision.
• Units.
In Palette tab, the palette can be edited. For a discrete palette, the code, the name and the
color of the categories can be set by double clicking on the white fields. For a continuous
palette, different options are available by right mouse button click on the palette:
• Set Predefined Palette. Select a predefined color set;
• Add Color. Adds a user color to the palette at the exact place where you clicked;
• Change Color. Changes the selected color in the palette;
• Remove Color. Removes the selected color in the palette;
• Edit Palette. Allows to drag the categories boundaries;
• Edit Colors Simultaneously. Allows to drag all the boundaries at the same time. To
activate this option, the option Edit Palette has to be active;
• Logarithmic Palette.
23. Blocked Wells 193

18.1
• Inverted Color. Inverts the color scale;

• Discrete Palette Mode. If this option is activated, the property will be displayed as a
discrete one, according to the discretization degree which has to be set in the Settings
panel (Grid Settings. Palette. Discretization Degree.)
23.2. Blocked Wells Computation

When the log template is properly defined (see Select a log template for more details), the
following parameters have to be set:
• BlockedWells. Blocked property name;
• Well Filter. Well filter setting. If a well filter is selected, the computation will be
performed only for the wells present in the well filter;
• Source Log. Raw data used for the computation;
• Averaging type. If a grid block contains several data points, a unique value is assigned
to the entire block using one of the following methods, depending on the type of data
(discrete or continuous) which is used:
– Arithmetic. The value assigned to the entire block is the arithmetic mean of the
data point values situated within the grid block;
– Minimum. The value assigned to the entire block is the minimum value of the
– Maximum. The value assigned to the entire block is the maximum value of the
– Median. The value assigned to the entire block is the median of the data point
values situated within the grid block;
– Mid Point. The value assigned to the entire block is the value of the data point
which is the nearest to the cell center;
– RMS. The value assigned to the entire block is the root mean square of the data
point values situated within the grid block;
– Geometric. The value assigned to the entire block is the geometric mean of the
– Harmonic. The value assigned to the entire block is the harmonic mean of the
– Most of. This blocking method is present only for the discrete data logs. The
most frequent value among all data points within the grid block will be assigned
to the entire grid block.
• Treat log. Indicates the method used to fill the cells with no values. 2 methods are
available:
23.2. Blocked Wells Computation 194

18.1
– As points. No values will be attributed to the grid blocks without data points;
– As lines. Depending on the type of data, a value will be assigned to each grid
block. If the data is discrete, the measurement is valid in the interval between 2
data points, so the cells situated in the upper half of the interval between 2 data
points will present the same values as the lowest value of the upper grid block,
while the cells situated in the lower half of the interval will present the same
values as the upper value of the lower grid block (cf. figure 21.
Well path
Value assigned by
Treat log the blocking method
as lines
Grid blocks Value of the upper
along the well and lower blocks
Treat log as points
Figure 21. Definition of blocked wells with logs treated as lines and as points for discrete
data. The measurement is valid in the interval between 2 data points, so all the cells between
2 data points will present the same values as the upper and lower grid block values if the
logs are defined as lines, while the grid blocks without values will have no values if the
logs are defines as points.
If the data is a continuous one, the upper half of the interval between 2 data
points grid blocks will present the same values as the maximum value present
in the upper grid block,while the cells situated in the lower half of the interval
will present the same values as the maximum value of the lower grid block (cf.
figure 22);
• Min. number of points in block. Minimum number of data points which should be
within a grid block to be taken into account for the computation. If the number of data
points is inferior to the number set, the data points are ignored.
• Use Bias. This option can be used to compute continuous blocked data using already
existing discrete blocked data. This can be used to avoid bias in continuous blocked
data when an averaging method is used, (cf. figure 23 and figure 24). The continuous
blocked data is computed using the blocked discrete data as a reference;

18.1
Well path
Treat log
Value assigned by
as intervals the blocking method
Grid blocks
Value of the upper
along the well and lower data points
Treat log as points
Figure 22. Definition of blocked wells with logs treated as lines and as points for continuous
data. The measurement is valid in the interval between 2 data points, so all the cells between
2 data points will present the same values as the upper grid block if the logs are defined
as lines, while the grid blocks without values will have no values if the logs are defines as
points.

18.1
Blocked data: porosity (in red)

Method: geometric, with lithol-
ogy as bias
Raw Data: porosity. Result: reservoir porosity val-
Blocked data: lithology
The geometric mean is ues coherent with preponderant
Method: Most of (reser-
Raw Data: lithology represented in red lithology
voir facies is preponderant)
Figure 23. Use of bias for blocked wells computation. The first track represents the raw
lithology data, the second one is the blocked lithology data where the method most of is
used. The last track represents the results obtained for blocked porosity computation using
the lithology as bias. Porosity values are coherent with the preponderant lithology.

18.1
Blocked data: lithology Raw Data: lithology Blocked porosity Blocked porosity Raw Data: porosity
Method: Most of (reservoir data with blocked data without bias
facies is preponderant) lithology as bias Method: arithmetic
No porosity value is
assigned to the block,
Facies 2 is assigned because there is no
to this block porosity data for facies 2
in this block
Figure 24. Computation of blocked well data using bias: porosity data presented in the
track 3 is computed using the blocked lithology data represented in the first track. The last
block will present no values, because it should take the porosity value corresponding to the
facies 2 according to the blocked data, and there is no porosity data for facies 2 in this
block.

18.1
24. Contacts
Contacts are created as grid objects, available in Geometry Objects. They can be visualized
in 3D and can be used to generate volumetric properties (see Calculate Volumetric Properties)
as Gas-Oil contact or Oil-Water contact. The following Calculations are available:
• Create Contact by Horizon.
24.1. Create Contact by Horizon

This calculation allows to compute a contact using a horizon. The following parameters have
to be set:
• Horizon. Select the horizon which will be used to compute the contact;
• Contact. Enter a name for the generated contact or select an existing one.
25. Fluid Properties

This section deals with setting up the properties of oil, gas, water and rock in order to create
a dynamic model.
25.1. General Overview

To set up a property for a region:
• Specify model type (see Cases).
• Specify the property as a table or import it.
• Create the region(s) to apply the property to.
• Map the created tables to regions.
25.2. Property Tables

On the left panel under Fliud Properties, there are multiple second-level tabs associated
with various properties. The most important ones are already present by default. The rest
can be added with the More Properties button below. Upon hovering over a tab, a pop-up
message is displayed containing the related keywords.
Once a property is selected, it is possible to create an arbitrary number of tables with this
property in either of the two ways:
• On the Settings tab (if it is closed, press Settings to open) add new tables using
button below and fill in the values by hand or via correlations available for this
particular property.
24. Contacts 199

18.1
• Press Import on the right panel to import the table from an external source.
The complete list of tabs/properties together with the corresponding keywords includes:
Tab Keywords
Displayed by default:
Rock ROCK (see 12.5.17)
Relative Permeability RP
Equilibrium EQUIL (see 12.16.2)
PVT PVT (see 13.5.9)
Hidden by default:
Thermal Group including the following:
Oil viscosity vs Temperature OILVISCT (see 12.15.54)
Oil viscosity vs Temperature (Compositional) OILVISCT (see 12.15.54)
Initial Reservoir Temperature vs Depth RTEMPVD (see 12.16.30)
Fluid Specific Heat SPECHEAT (see 12.15.92)
Rock Specific Heat SPECROCK (see 12.15.91)
Temperature Nodes for Polymer Solution Viscos- TEMPNODE (see 12.8.29)
ity
Reference Conditions for Viscosity VISCREF (see 12.15.52)
Water Viscosity vs Temperature WATVISCT (see 12.15.53)
Alkaline Group including the following:
Alkaline Adsorption Functions ALKADS (see 12.8.33)
Alkaline-Rock Properties ALKROCK (see 12.8.34)
Polymer Absorption Mult. vs Alk. Concentration ALPOLADS (see 12.8.32)
Surfactant Absorption Mult. vs Alk. Concentra- ALSURFAD (see 12.8.31)
tion
Water/Oil Surface Tension vs Alk. Concentration ALSURFST (see 12.8.30)
Polymer Todd–Longstaff Mixing Parameter PLMIXPAR (see 12.8.21)
Polymer Adsorption Functions PLYADS (see 12.8.18)
Polymer/Salt Concentrations for Mixing Calcu- PLYMAX (see 12.8.20)
lation
Polymer-Rock Properties PLYROCK (see 12.8.22)
Polymer Shear Thinning/Thickening Data PLYSHEAR (see 12.8.24)
25.2. Property Tables 200

18.1
Tab Keywords
Polymer Solution Viscosity Function PLYVISC (see 12.8.17)
Salt Concentration Nodes for Polymer Solution SALTNODE (see 12.7.6)
Viscosity
Surfactant Group including the following:
Adsorbed Surfactant Conc. vs Fractional Satura- SURFADDW (see 12.8.14)
tion Functions
Surfactant Adsorption Functions SURFADS (see 12.8.9)
Surfactant Capillary De-Saturation Functions SURFCAPD (see 12.8.12)
RP Calculation Coefficient vs Surf.Concentration SURFDW (see 12.8.15)
Rock Properties for the Surfactant Model SURFROCK (see 12.8.13)
Water/Oil Surface Tension vs Surf. Conc. SURFST (see 12.8.10)
Surfactant Solution Viscosity Function SURFVISC (see 12.8.11)
Salt Group including the following:
Brine Surface Density BDENSITY (see 12.7.10)
Low-Salt Weighing Factors vs Salt Conc. LSALTFNC (see 12.7.17)
Salt Properties SALTPROP (see 12.7.4)
Permeability vs Dissolved Salt SALTTRM (see 12.7.5)
Salt Concentration vs. Depth for Equilibration SALTVD (see 12.16.44)
Rock Table ROCKTAB (see 12.5.19)
Component Data
Standard Conditions STCOND (see 12.14.11)
Reservoir Temperature RTEMP (see 12.14.10)
25.2. Property Tables 201

18.1
26. Wells Data. Tables

The tab Wells Data contains the following options:
• Well Production Tables;
• Well Structure Tables;
• Rules;
• Schedule (the keywords of SCHEDULE section that are generated via Rules);
• VFP tables. VFP tables can be built in tNavigator module – VFP Designer.
26.1. Well Production Tables

Well production data can be loaded in the following formats:
• History – One Table;
• History – Grouped by Wells;
• History – Field History File format;
• History – MoRes format.
26.1.1. History table

File type: Prod. history table.
Data description: well name; date; oil rate; water rate; gas rate; liquid rate; gas injection;
water injection; THP; BHP; well efficiency factor; polymer injection, enthalpy and other
parameters.
Columns that are in the file should be selected in the drop-down menu. Order of boxes can
be changed (in accordance with the data in the file).
Example 1. How loaded historical data is used.

--Well Date WOPRH WWPRH WWIR
WELL15 01.10.2014 19.6224 130.378 0
WELL15 01.11.2014 19.1517 130.848 0
WELL15 01.12.2014 18.7443 131.256 0
In this example we load historical data for WELL15: oil rate (column WOPRH), water
rate (column WWPRH) and water injection rate (column WWIR).
Loading the data in this format we consider that the well works in the following way:
26. Wells Data. Tables 202

18.1
• Oil rate 19.6224 sm3 /day and Water rate 130.378 sm3 /day, from 01.10.2014 to
01.11.2014;
• Oil rate 19.1517 sm3 /day and Water rate 130.848 sm3 /day, from 01.11.2014 to
01.12.2014;
• Oil rate 18.7443 sm3 /day and Water rate 131.256 sm3 /day, from the date 01.12.2014.
Two scenarios are possible:
• If the last date in the model is 01.12.2014, then the rates from the last line are
not taken into consideration in cumulative production calculation. Oil cumulative
production from 01.10.2014 is calculated as 19.6224 ∗ 31 + 19.1517 ∗ 30 (only Octo-
ber+November). To take December into account add the last date 01.01.2015 to
the model (DATES, see 12.19.117).
• If the last date in the model is 01.01.2015, then the rates from the last line are
taken into consideration in cumulative production calculation. Oil cumulative pro-
duction from 01.10.2014 is calculated as 19.6224 ∗ 31 + 19.1517 ∗ 30 + 18.7443 ∗ 31
(October+November+December).
Note. In graphical interface on the Graphs tab in the table on the right rates are visualized
with date shift, see the picture 25.
26.1.1. History table 203

18.1
Figure 25. Load historical data
Example 2. Additional Settings.

--Well Date WOPRH WWPRH WWIR
WELL15 01.06.2014 26.2376 123.341 0
WELL15 01.07.2014 24.5654 0
WELL15 01.09.2014 20.1092 129.891 0
• Replace missing values with zero. If this option is used, the parameters for the well
that are missing in the file on the specific date will be replaced with zeros. In the
example above for the date 01.07.2014 water rate (column WWPRH) of the WELL15
is considered as zero. If this option is not used then water rate at this date is equal to
the value from previous time step (01.06.2014).
• Data Filter. If Data Filter is used, then historical data will be loaded only in the
specified time period, including the First Date and the Last Date.
• WEFac Units. If well efficiency factor is set in Days then it is divided by number of
days in a month to convert to Relative.
• Time Units. If Month time units are used then day rates are calculated as:
monthrate
monthdays ∗W EFAC

18.1
where:
– monthrate – month rate;

– monthdays – number of days in a month;
– W EFAC – well efficiency factor.

18.1
26.1.2. History – FHF Format

File type: Prod. and Pressure history.
File format – .fhf.
Data description: date; gas rate; oil rate; water rate; BHP.

2013 12 10
’4600 Production and Pressure’
2011 12 10
’YYYY/MM/DD’
4
’Oil Rate SC’ ’Gas Rate SC’ ’Water Rate SC’ ’Well BHP’
’bbl/day’ ’ft3/day’ ’bbl/day’ ’psi’
’E1’
2011/12/10 0 0 0 10362
2011/12/17 2999 4512234 0 10068
2011/12/18 8411 8117802 0 9694
2011/12/19 5140 3468024 0 9965
2011/12/20 2812 4490000 0 10148
2011/12/21 2825 4248000 0 10156
2011/12/22 2758 4358000 0 10154
2011/12/23 1261 1872542 0 10171
2011/12/26 2439 2163277 0 10197

2011/12/27 2471 3970000 0 10181
2011/12/28 2490 4180000 0 10174
2011/12/29 1676 2924000 0 10156
2011/12/30 4390 6100000 0 10011
2011/12/31 3032 5982000 0 10042
2012/01/01 6827 14256000 0 9776
2012/01/02 4547 8027000 0 9684
26.1.3. Grouped by wells

The beginning of the file contains the keywords which describe the data. It is followed by
history tables for each well. The keywords begin with the symbol*.
26.1.2. History – FHF Format 206

18.1
Special keywords:
• *READON – the part of the file included in the interval between this keyword and the
keyword *READOFF is not read.
• *READOFF – see above.
Units:
• *METRIC;
• *FIELD.
Units for concrete quantities:
• *MSTB – quantity of liquid measured in STB (is used only with *FIELD );
• *MMSCF – volume of gas measured in thousands of MSCF (is used only with *FIELD
);
• *MSM3 – all volumes are measured in 1000 sm 3 (is used only with *METRIC);
• *MSM3GAS – volume of gas measured in 1000 sm 3 (is used only with *METRIC);
• *MSM3LIQUID – volume of liquid measured in 1000 sm 3 (is used only with *MET-
RIC).
Interval of time for which the data is available in the tables:
• *DAILY – daily rate;
• *MONTHLY – monthly rate;
• *YEARLY – annual rate.
Other keywords:
• *CUMULATIVE – indicates that the tables contain cumulative quantities instead of

rates (injection/production spead). During the loading these quantities are converted
into rates.
• *KEYLENGTH – defines the number of first signs of the keyword which are used for
recognizing it.
• *MISSING_VALUE – defines the value which will replace the missing one during the
import.
One of the following keywords can be used to define the well and to indicate the
beginning of the history table for this well. It is followed by the name of the well and the
history table itself (corresponding to the well).
26.1.3. Grouped by wells 207

18.1
• *WELL;
• *KEYLABEL;
• *UNIQUEUD;
• *NAME;
• *WELLNAME;
• *KEYNAME.
The following keywords are used to describe the format of the tables. Each of these
keywords represents a column with the corresponding type of data which is present in the
table.
Date Format. Several methods can be used to define the dates:
1. One column *DATE – date related to the historical data.
2. Detailed Data. Instead of a single column, one or more columns can be used from the
following list:
• *DAY – day (day of the month);

• *MONTH – month;
• *YEAR – year;
• *HOUR – hours;
• *MINUTE – minutes;
• *SECOND – seconds.
3. Date in a particular format. The year and the month have to be set. The day is
optional, but can be indicated. The corresponding fields are defined as follows: YY or
YYYY (if the year is defined by 4 numbers), MM, DD. For example:
• *YY.MM.DD,
• *YYYY.MM.DD,
• *DD/MM/YYYY,
• *YYYYMMDD,
Then the keyword *DAYS is used to define the number of days in the month during
which the production has occurred.
Definition of history data. Keywords defining the production history data for the corre-
sponding dates:
• *OIL – oil rate;
• *GAS – gas rate;

18.1
• *WATER – water rate;
• *WINJ – water injection rate;
• *GINJ – gas injection rate;
• *BHP – bottom hole pressure;
• *THP – tubing head pressure.
Example
*METRIC
*Daily
*Date *Oil *Gas *Water
*Name SN-17H1
01.04.2009 22.32 124000.00 0.00
01.05.2009 25.31 140600.00 0.00
01.06.2009 36.36 202000.00 0.00
01.07.2009 32.94 183000.00 0.00
01.08.2009 19.26 107000.00 0.00
*Name SN-22H1
01.10.2012 200 200000 0.22
01.11.2012 170 170000 0.22
01.12.2012 166.16 150000 0.26
01.01.2013 188.85 130000 0.22
..............................

18.1
26.2. Well Structure Tables

The following formats are available for the import of the well structure:
• Events – One Table;
• Events – Grouped by Wells;
• Events – Landmark OWX format;
• Events – MoRes format.
26.2.1. Events – One Table

File type: Events – Table.
Data description: well name; branch, date; event; layer; lower depth; upper depth; radius;
diameter; skin; multiplier.
Columns that are in the file should be selected in the drop-down menu. Order of boxes can
be changed (in accordance with the data in the file).
Possible events:
• perf – open connections in all grid blocks where the trajectory intersects grid. Lower
depth and upper depth should be specified;
• sque – shut connections in all grid blocks where the trajectory intersects grid. Lower
depth and upper depth should be specified;
• plug – open connections in all grid blocks where the trajectory intersects grid. Upper
depth should be specified, lower depth is calculated as the end of the trajectory;
• bare – shut connections in all grid blocks where the trajectory intersects grid. Upper
depth should be specified, lower depth is calculated as the end of the trajectory.
Example 1.

WELL1 1.7.1997 perforation 3354.8 3358.8 0.2 -3
WELL1 1.7.1997 perforation 3383 3390.6 0.2 -3
Example 2.
Load perforations for multilateral wells. For the main well branch (first row) the default ranch
number is used 1∗; the next branch is set via number – 1. For each branch we set depth
26.2. Well Structure Tables 210

18.1
for perforated interval. Please choose branch for the corresponding column in the graphical
interface.

’WU20’ 01.07.2012 1* 1440 1473 PERF 0.16
’WU20’ 01.07.2012 1 1430 2150 PERF 0.16
Additional Settings.
• Replace missing values with zero. If this option is used, the parameters for the well
that are missing in the file on the specific date will be replaced with zeros.
• Data Filter. If Data Filter is used, then historical data will be loaded only in the
specified time period, including the First Date and the Last Date.
26.2.2. Events – Grouped by wells

Specify Units explicitly. The keyword UNITS is used with one of its parameters:
• FIELD;
• METRIC;
• LAB.
If some of the quantities are measured in one units and some others in other units it is
necessary to add one of the following lines (in addition to the one described above):
• UNITS DEPTH – to indicate the depth units;
• UNITS PRESSURE – to indicate the pressure units;
• UNITS DIAMETER – to indicate the diameter units.
See the example below.

Well identification and definition of the beginning of the corresponding table. One
of the following keywords can be used:
• WELLNAME;
• NAME;
• KEYNAME;
• UNIQUEID;
• KEYLABEL;
• WELL.
26.2.2. Events – Grouped by wells 211

18.1
The table of events and corresponding dates follows.

Example
UNITS METRIC
UNITS DEPTH FIELD
WELLNAME 'SN-18H1'
06/29/1986 Squeeze 7758 7770
06/16/1986 Perforation 7551.33 7591.83
01/21/2009 Perforation 7581.06 7621.56
WELLNAME 'SN-21H1'
01/12/1988 Perforation 7728 7758
01/25/2009 Perforation 7530 7545
In this example the events for 2 wells are defined. All the units except for the depth are
measured in the METRIC system. The units of depth are measured in the FIELD system.
26.2.3. Events – Landmark OWX format

OWX format is a universal format. For these kind of files, the information about trajectories,
markers, events and logs can be loaded. A description of this format can be found here.
26.2.3. Events – Landmark OWX format 212

18.1
27. Wells Data. Strategies. Rules. Global

Strategies tab is used to define the rules for each step. Keywords are automatically generated
for each rule and will be written into the Schedule section when dynamic model is exported.
Switching to the Schedule tab all generated keywords can be seen. Added steps are displayed
as a list on the left under Wells Data. The rules are displayed under each step. Each rule can
be edited on the right under Strategies. Two sets of buttons allow to manage the time steps
and the keywords (cf. Fig. 26).
Figure 26. Model Designer interface for Strategies tab. A) List of defined strategies and
corresponding time steps and rules (global and affected to a particular time step). B) Editing
area for the rules. This area is displayed by clicking on a rule in the area A). C) Set of
buttons used to manage rules. D) Set of buttons which allows to manage the loaded keywords
and to define a well filter.
Four categories of rules can be added:
• Global Rules;
• Wells;
• Groups;
• Other.
27. Wells Data. Strategies. Rules. Global 213

18.1
Moreover, several strategies can be created. A strategy corresponds to a set of rules and
time steps. A unique strategy for each model has to be selected during the dynamic model
creation step.
27.1. Time steps, rules and strategies buttons

Under the list of rules and time steps in Strategies Tab, the following buttons are available:
• Add New Rule. The rule is added for the selected time step or as a Global Rule.
The rule has to be selected from the list. A new rule can also be added by right mouse
button click on a time step;
• Duplicate Rule. A rule can also be duplicated by right mouse button click on a
time step. After that rule can be moved holding left mouse button to another time step;
• Remove Rules. Removes the selected rules from the list;
• Time Step Editor.

The time steps can also be added using the button Add Steps which is available by
right mouse button click on the white field under Global Rules, on the panel A (cf.
Fig. 26) and in the menu Time Step Editor situated in the Top Panel Buttons.
– Add Steps.
Step Length. Time step length: One step, Year, Six Months, Three Months,
Month, Week, Day;
– Remove Steps. A rule can also be removed by right mouse button click on
a time step;
– Add Steps from History and Event Tables. Time steps will be defined
automatically after loading wells data and/or history.
• Remove Steps. A rule can also be removed by right mouse button click on a time
step;
• Verify Rules. The button is used to check correctness of created rules. In case
of a rule is not correct the following warning will appear on log–panel (located at the
bottom part of project window) or/and in a log–file:
Some problems are found in schedule rules. May be not all rules are applied correctly
due to contradictory or insufficient input data. Press button ’Verify rules on ’Strategies’
tab to see all warnings.
Information about problem for particular rule does not appear automatically on log–
panel. Therefore, to see detailed information about a problem press this button or select
the option Verify Rules from the menu which is available by right mouse button click
on the panel A (cf. Fig. 26).
27.1. Time steps, rules and strategies buttons 214

18.1
For example, if for well ”32” both oil rate and water injection are specified in well
production table, then the following warning will appear on the log–panel:
Warning: contradictory historical events for well ”32” are found on 01.05.2014.
By right mouse button click on the white field under Wells Data, the following options
can also be set (cf. Fig. 27):
Figure 27. Menu accessible by RMB on the field under Well Data in Model Designer. This
menu gathers rules, time steps, and strategies managment options.
• Hide Steps Without Rules. If this option is ticked, only the steps with rules will be
displayed;
• Add new strategy. Allows to add a new strategy. The new strategy will be added
to the list of strategies. The corresponding steps and rules will also be displayed and
could be edited;
• Duplicate Strategy. Allows to duplicate a strategy. The copy can be modified inde-
pendently;
• Remove Strategies. Allows to remove a strategy.
27.2. Right Panel Buttons

On the right panel, the following buttons are available:
• Import Keywords.
– Load Well Controls from MoRes format. Standard MoReS format is supported.
27.2. Right Panel Buttons 215

18.1
∗ Add Rows. Add a file;

∗ Remove Rows. Delete a file from the list;
∗ Preview. Number of Lines. Number of the file lines shown in the Preview
window;
∗ Well History. Set the production table which will be used. The production
table has to be chosen from the list;
∗ Clear Tables. Clears the tables which are already present in the project and
replaces it by a default table.
– Load User Keywords from E1/E3 formats. Standard E1/E3 schedule keywords
are supported.
∗ Select file for load. Browse to find the file to load;
∗ Choose starting date for Load Schedule. Indicate the starting date for the
loaded schedule.
• Well Filter. Set the current well filter. All the rules and the list of keywords in Wells
Data tab will be displayed only for the wells selected in the filter.
27.3. Wells Data. Global Rules

Global rules are general well specifications (e.g., structure, trajectories and VFP tables).
Other rules should be specified for selected dates.
27.3.1. Input Wells Trajectories

Adds the keyword WELSPECS (see 12.19.3) and WELLTRACK (see 12.19.9) to the Schedule.
The following options are available:
• Wells. Set the wells to which the rule will be applied.
– Well: selection of a particular well from the list of wells.

– Wells from filter: the rule will be applied only to the wells selected in the filter.
– All Wells: the rule will be applied to all the wells present in the project.
27.3.2. Input VFP tables

Adds the keyword VFPPROD (see 12.19.62) or VFPINJ (see 12.19.61) to the Schedule, if a
VFP table is added via the VFP designer tab.
27.3.3. Input Well Structure

Adds the keyword COMPDATMD (see 12.19.10) and COMPORD (see 12.19.30) to the Sched-
ule. The following options are available:
27.3. Wells Data. Global Rules 216

18.1

• Well Structure. Choose a table from the list of well events tables.
It is possible when we have several events tables, for example: historical table, data
for 2017 and data for forecast:
– To load or create a new table go to the Table tab;

– If several tables are loaded, you should create several Input Well Structure rules
in order to assign different tables to different rules;
– In order to apply a rule to new loaded events you need to right-click any of the
Input Well Structure rules and press Duplicate. Select the created copy of the
rule and from the drop–down menu select new table as shown in the figure 28.
Figure 28. Specifying events for global rules.
27.3.4. Gas Lift Optimization

Adds the keyword LIFTOPT (see 12.19.229) to the Schedule. The following parameters
should be specified:
• Increment size for lift gas injection rate;
• Min. economic gradient of improvement in oil production rate for increase in lift gas
injection rate by one;
• Min. interval between gas lift optimizations.
27.3.4. Gas Lift Optimization 217

18.1
28. Wells Data. Rules. Wells

28.1. Control
28.1.1. Create Historical Well Controls by Table
Allows to add the keywords WCONHIST (see 12.19.41) or WCONINJH (see 12.19.45) and
optionally the keywords WEFAC (see 12.19.76), WALKALIN (see 12.19.164), WPOLYMER
(see 12.19.165), WSALT (see 12.19.166) and WSURFACT (see 12.19.163) to the Schedule
section. The following parameters have to be set:
• Well History. Set the production table which will be used. The production table has to
• Wells Type. Set the type of wells which will be affected by the rule:
– Detect by Rate. The type of the well (injector of producer) will be detected by
its rate. This is very useful in case if the well is switched from production to
injection. Its type is detected automatically. For the injectors, all the parameters
set in Water Injectors and Gas Injectors will be set, while for the producers, the
parameters set in Producers tab will be used.
– Producers. Adds the keyword WCONHIST (see 12.19.41) to the Schedule section.
Only the tab Producers will be active and the keyword will be added only for
producers;
– Injectors. Adds the keyword WCONINJH (see 12.19.45) and optionally the
keywords WALKALIN (see 12.19.164), WPOLYMER (see 12.19.165), WSALT
(see 12.19.166) and WSURFACT (see 12.19.163) to the Schedule section. Only
the tabs Water and Gas Injectors will be active and the keyword will be added
only to injectors;
– Water Injectors. Adds the keyword WCONINJH (see 12.19.45) for water injectors
only. The parameter ’WATER’ will be added to the keyword. Only the tab Water
Injectors will be active to set the parameters;
– Gas Injectors. Adds the keyword WCONINJH (see 12.19.45) with ’GAS’ as
second parameter. Only the tab Gas Injectors will be active;
– Detect by BHP. If historical value of BHP is less than the indicated threshold
value, then the well is considered as producer; else – injector.
• Producers. Settings for producer wells (production limits). This tab is active only if
the chosen wells type is Producers. The following options can be set:
28. Wells Data. Rules. Wells 218

18.1
– Well Status. Sets the second parameter of the WCONHIST (see 12.19.41) key-
word: OPEN, SHUT or STOP.
– Control Mode. Sets the third parameter of WCONHIST (see 12.19.41) keyword.
The parameter ORAT, WRAT, LRAT, RESV, BHP, THP or GRUP will be added.
– Set the constraints:
The constraint value can be specified as following:
∗ Historical Value. The value will be taken from the historical value in Table
tab.
∗ Value. The value entered in the field will be taken as upper limit.
The following constraints can be selected:
∗ Oil Rate. Setting of the oil rate target or upper limit.
∗ Water Rate. Setting of water rate target or upper limit.
∗ Gas Rate. Setting of gas rate target or upper limit.
∗ Liquid Rate. Setting of liquid rate target or upper limit.
∗ Reservoir Liquid Rate. Setting of Reservoir fluid volume rate target or
upper limit.
∗ Bottom Hole Pressure. Setting of bottom hole pressure target or upper limit.
∗ Tubing Head Pressure. Setting of tubing head pressure target or upper limit.
• Water Injectors. Settings for water injectors wells. This tab is active only if the chosen
wells type is Injectors, Water Injection. The following options can be set:
– Water Injection Limits.

∗ Well Status. Sets the third parameter of WCONINJE (see 12.19.42) keyword:
OPEN, SHUT or STOP. Corresponds to the well working mode.
∗ Control Mode. Sets the fourth parameter of WCONINJE (see 12.19.42) key-
word. The parameter RATE, RESV, BHP or GRUP will be added.
The limit value can be specified as following:
· Historical Value. The value will be taken from the historical value in
Table tab;
· Value. The value entered in the field will be taken as upper limit.
The following limits can be selected:
· Injection Rate. Setting of water rate target or upper limit.
· Reservoir Injection Rate. Setting of Reservoir injection rate target or
upper limit.
· Bottom Hole Pressure. Setting of bottom hole pressure target or upper
limit.
· Tubing Head Pressure. Setting of tubing head pressure target or upper
limit.
28.1.1. Create Historical Well Controls by Table 219

18.1
∗ Thermal Properties of Injected Fluid. The keyword WINJTEMP

(see 12.19.169) is added. The parameters of the keyword are specified in
the fields:
· Steam Quality. Specifies the second parameter of the keyword WIN-
JTEMP (see 12.19.169) corresponding to the steam quality of the injected
fluid.
· Steam Temperature. Specifies the third parameter of the keyword WIN-
JTEMP (see 12.19.169) corresponding to the temperature of the injected
fluid.
· Pressure. Specifies the fourth parameter of the keyword WINJTEMP
(see 12.19.169) corresponding to the pressure of the injected fluid.
· Enthalpy. Specifies the fifth parameter of the keyword WINJTEMP
(see 12.19.169) corresponding to the specific enthalpy of the injected
fluid.
– Enhanced Oil Recovery.
∗ ASP Flooding
· Polymer Concentration. This option adds the keyword WPOLYMER
(see 12.19.165) to the schedule section. The value of the concentration
can be taken from the loaded table or can be specified in the field Value
(the proper option has to be ticked).
· Alkaline Concentration. This option adds the keyword WALKALIN
(see 12.19.164) to the schedule section. The value of the concentra-
tion can be taken from the loaded table or can be specified in the field
Value (the proper option has to be ticked).
· Surfactant Concentration. This option adds the keyword WSURFACT
∗ Brine
· Salt Concentration. This option adds the keyword WSALT (see 12.19.166)
to the schedule section. The value of the concentration can be taken from
the loaded table or can be specified in the field Value (the proper option
has to be ticked).
• Gas Injectors. Settings of the parameters for the keyword WCONINJE (see 12.19.42)
for gas injectors wells. This tab is active only if the chosen wells type is Injectors,
Gas Injection. The following options can be set:
– Gas Injection Limits.

28.1.1. Create Historical Well Controls by Table 220

18.1

· Historical Value. The value will be taken from the historical value in
Table tab.
· Value. The value entered in the field will be taken as upper limit.
upper limit.
limit.
limit.
– Thermal Properties of Injected Fluid. The keyword WINJTEMP (see 12.19.169)
is added. The parameters of the keyword are specified in the fields:
∗ Steam Quality. Specifies the second parameter of the keyword WINJTEMP
(see 12.19.169) corresponding to the steam quality of the injected fluid.
∗ Steam Temperature. Specifies the third parameter of the keyword WIN-
fluid.
∗ Pressure. Specifies the fourth parameter of the keyword WINJTEMP
∗ Enthalpy. Specifies the fifth parameter of the keyword WINJTEMP
(see 12.19.169) corresponding to the specific enthalpy of the injected fluid.
• Economic limits. Set the Well Efficiency Factor. The keyword WEFAC (see 12.19.76)
will be added to the Schedule section. The limit value can be specified as following:
– Historical Value. The value will be taken from the historical value in Table tab;
– Value. Specify the value of efficiency factor.
28.1.2. Create Forecast Well Controls by Table

Allows to add the keywords WCONPROD (see 12.19.40) or WCONINJE (see 12.19.42)
and optionally the keywords WEFAC (see 12.19.76), WALKALIN (see 12.19.164), WPOLY-
MER (see 12.19.165), WSALT (see 12.19.166), WINJTEMP (see 12.19.169) and WSURFACT
(see 12.19.163) to the Schedule section. The following parameters have to be set:
28.1.2. Create Forecast Well Controls by Table 221

18.1
• Well History. Set the production table which will be used. The production table has to
• Wells Type. Set the type of wells which will be affected by the rule:
– Detect by Rate. The type of the well (injector of producer) will be detected by
its rate. This is very useful in case if the well is switched from production to
injection. Its type is detected automatically. For the injectors, all the parameters
set in Water Injectors and Gas Injectors will be set, while for the producers, the
parameters set in Producers tab will be used.
– Producers. Adds the keyword WCONPROD (see 12.19.40) to the Schedule sec-
tion. Only the tab Producers will be active and the keyword will be added only
for producers;
– Injectors. Adds the keyword WCONINJE (see 12.19.42) and optionally the
keywords WALKALIN (see 12.19.164), WPOLYMER (see 12.19.165), WSALT
(see 12.19.166) and WSURFACT (see 12.19.163) to the Schedule section. Only
the tabs Water and Gas Injectors will be active and the keyword will be added
only to injectors;
– Water Injectors. Adds the keyword WCONINJE (see 12.19.42) for water injectors
only. The parameter ’WATER’ will be added to the keyword. Only the tab Water
Injectors will be active to set the parameters;
– Gas Injectors. Adds the keyword WCONINJE (see 12.19.42) with ’GAS’ as
second parameter. Only the tab Gas Injectors will be active;
– Detect by BHP. Only the wells which BHP value is higher than the indicated
threshold will be affected by the rule.
• Producers. Settings for producer wells (production limits). This tab is active only if
the chosen wells type is Producers. The following options can be set:
– Well Status. Sets the second parameter of WCONPROD (see 12.19.40) keyword:
OPEN, SHUT or STOP.
– Control Mode. Sets the third parameter of WCONPROD (see 12.19.40) keyword.
The parameter ORAT, WRAT, LRAT, RESV, BHP, THP or GRUP will be added.
– Set the constraints:
The constraint value can be specified as following:
∗ From Table. The value is taken from the production table loaded in Table
tab
∗ Value. The value entered in the field will be taken as upper limit
The following constraints can be selected:

18.1
∗ Oil Rate. Setting of the oil rate target or upper limit.

∗ Water Rate. Setting of water rate target or upper limit.
∗ Gas Rate. Setting of gas rate target or upper limit.
∗ Liquid Rate. Setting of liquid rate target or upper limit.
∗ Reservoir Liquid Rate. Setting of Reservoir fluid volume rate target or
upper limit.
∗ Bottom Hole Pressure. Setting of bottom hole pressure target or upper limit.
∗ Tubing Head Pressure. Setting of tubing head pressure target or upper limit.
• Water Injectors. Settings for water injectors wells. This tab is active only if the chosen
wells type is Injectors, Water Injection. The following options can be set:
– Water Injection Limits.

· From Table. The value is taken from the production table loaded in
Table tab
· Value. The value entered in the field will be taken as upper limit
upper limit.
limit.
limit.
∗ Thermal Properties of Injected Fluid. The keyword WINJTEMP
(see 12.19.169) is added. The parameters of the keyword are specified in
the fields:
· Steam Quality. Specifies the second parameter of the keyword WIN-
JTEMP (see 12.19.169) corresponding to the steam quality of the injected
fluid.
· Steam Temperature. Specifies the third parameter of the keyword WIN-
fluid.
· Pressure. Specifies the fourth parameter of the keyword WINJTEMP

18.1
· Enthalpy. Specifies the fifth parameter of the keyword WINJTEMP

(see 12.19.169) corresponding to the specific enthalpy of the injected
fluid.
– Enhanced Oil Recovery.
∗ ASP Flooding
· Polymer Concentration. This option adds the keyword WPOLYMER
· Alkaline Concentration. This option adds the keyword WALKALIN
(see 12.19.164) to the schedule section. The value of the concentra-
tion can be taken from the loaded table or can be specified in the field
Value (the proper option has to be ticked).
· Surfactant Concentration. This option adds the keyword WSURFACT
∗ Brine
· Salt Concentration. This option adds the keyword WSALT (see 12.19.166)
to the schedule section. The value of the concentration can be taken from
the loaded table or can be specified in the field Value (the proper option
has to be ticked).
• Gas Injectors. Settings of the parameters for the keyword WCONINJE (see 12.19.42)
for gas injectors wells. This tab is active only if the chosen wells type is Injectors,
Gas Injection. The following options can be set:
– Gas Injection Limits.
· From Table. The value is taken from the production table loaded in
Table tab
· Value. The value entered in the field will be taken as upper limit
upper limit.
limit.

18.1

limit.
– Thermal Properties of Injected Fluid. The keyword WINJTEMP (see 12.19.169)
is added. The parameters of the keyword are specified in the fields:
∗ Steam Quality. Specifies the second parameter of the keyword WINJTEMP
(see 12.19.169) corresponding to the steam quality of the injected fluid.
∗ Steam Temperature. Specifies the third parameter of the keyword WIN-
fluid.
∗ Pressure. Specifies the fourth parameter of the keyword WINJTEMP
∗ Enthalpy. Specifies the fifth parameter of the keyword WINJTEMP
(see 12.19.169) corresponding to the specific enthalpy of the injected fluid.
• Economic limits. Set the Well Efficiency Factor. The keyword WEFAC (see 12.19.76)
will be added to the Schedule section. The limit value can be specified as following:
– From Table. The value is taken from the production table loaded in Table tab;
– Value. Specify the value of efficiency factor.
28.1.3. Reset Well Target

This rule changes the limit of the selected wells. The keyword WELTARG (see 12.19.57) is
added to the Schedule section.

• Limit Type. Definition of the control or constraint quantity to be changed. Can be

chosen from the list:
– Oil Rate;
– Water Rate;
– Gas Rate;
– Liquid Rate;
– Reservoir Liquid Rate;
– Bottom Hole Pressure;
– Tubing Head Pressure;
28.1.3. Reset Well Target 225

18.1
– Artificial lift quantity;

– Guide Rate;
– Wet Gas Rate;
– and other.
• Value. New value of the quantity to be changed.
28.1.4. Well Efficiency Factor

This rule adds the keyword WEFAC (see 12.19.76) to the Schedule section. The value of the
well efficiency factor has to be entered in the field.

• Well Efficiency Factor. Specify the value of efficiency factor.
28.1.5. Drawdown Limit for Well

Set a control by drawdown for the well. The keyword WELDRAW (see 12.19.116) will be
added to the schedule.

• Maximum drawdown. Set the maximum allowable drawdown value for the concerned
wells;
• Phase. Select the phase (Liquid or Gas) for the rate limit;
• Limit Type. Select the type of limit for the drawdown:
– Avg. the drawdown will be set as the PI-weighted average of the drawdowns
within the grid blocks containing the connections;
– Max. the drawdown will be set as the maximum drawdown within the grid blocks
containing the connections.
28.1.4. Well Efficiency Factor 226

18.1
28.1.6. Well Status

The keyword WELOPEN (see 12.19.119) is added to the Schedule section. The keyword
shuts or reopens wells.

• Well Status. SHUT, OPEN or STOP. Specifies the well status (2nd parameter of the
keyword).
28.1.7. Well Production Limits (Forecast)

This rule adds the keyword WCONPROD (see 12.19.40) to the schedule section and is used
to define the limit for production wells in the case of a forecast. The following parameters
can be set:

• Well Status. Sets the second parameter of WCONPROD (see 12.19.40) keyword:
OPEN, SHUT or STOP. Corresponds to the well working mode;
• Control Mode. Sets the third parameter of WCONPROD (see 12.19.40) keyword:
LRAT, ORAT, WRAT, RESV, BHP, THP or GRUP will be added;
• Oil Rate. Setting of oil rate target or upper limit. The value entered in the field will
be taken as upper limit;
• Water Rate. Setting of water rate target or upper limit. The value entered in the field
will be taken as upper limit;
• Gas Rate. Setting of gas rate target or upper limit. The value entered in the field will
be taken as upper limit;
• Liquid Rate. Setting of liquid rate target or upper limit. The value entered in the field
• Reservoir liquid Rate. Setting of the liquid rate target is reservoir conditions or upper
limit. The value entered in the field will be taken as upper limit;
28.1.6. Well Status 227

18.1
• Bottom Hole Pressure. Setting of bottom hole pressure target or upper limit. The
value entered in the field will be taken as upper limit;
• Tubing Head Pressure. Setting of tubing head pressure target or upper limit. The
• VFP Table. Set the VFP table which will used for the forecast.
28.1.8. Well Injection Limits (Forecast)

This rule adds the keyword WCONINJE (see 12.19.42) to the schedule section and is used to
define the limit for injection wells in the case of a forecast. The following parameters can be
set:

• Well Status. Sets the third parameter of WCONINJE (see 12.19.42) keyword: OPEN,
SHUT or STOP. Corresponds to the well working mode;
• Inj. Fluid. Set the second parameter of WCONINJE (see 12.19.42) keyword: Water,
Gas or Oil;
• Control Mode. Set the forth parameter of WCONINJE (see 12.19.42) keyword: RATE,
RESV, BHP or GRUP will be added;
• Injection Rate. Setting of water rate target or upper limit. The value entered in the
field will be taken as upper limit;
• Reservoir Injection Rate. Setting of the injection rate target in reservoir conditions or
upper limit. The value entered in the field will be taken as upper limit;
• Bottom Hole Pressure. Setting of bottom hole pressure target or upper limit. The
• Tubing Head Pressure. Setting of tubing head pressure target or upper limit. The
• VFP Table. Set the VFP table which will used for the forecast.
28.1.8. Well Injection Limits (Forecast) 228

18.1
28.2. VFP tables for wells

28.2.1. Assign VFP Tables to Production wells
Allows to assign a loaded VFP table to a production well. For each added row, the well
and the corresponding VFP table have to chosen from the lists available by double clicking
on the fields Well and VFP Table. The relation between the VFP table and the wells will
be indicated when the control of the well will be specified, as a parameter of the keywords
WCONPROD (see 12.19.40) or WCONHIST (see 12.19.41).
• Add Row. Add a table-well tie in.
• Remove Rows.
• Add Wells to Table. Add wells to the table: 3 options are available by clicking on the
arrow.
– All Wells. Add all the wells for the tie in of VFP tables;
– Current well filter. Add the wells corresponding to the current well filter;
– Well Filter. List of the different existing well filters which can be used.
• Load Table. Load a VFP table.
– Import File Format:

∗ Wells → VFP Table Name;
∗ Wells → VFP Table number.
– Add Rows. Add a file;
– Remove Rows. Remove a file.
28.2.2. Assign VFP Tables to Injection wells

Allows to assign a loaded VFP table to a well. For each added row, the well and the
corresponding VFP table have to be chosen from the lists available by double clicking on
the fields Well and VFP Table. The relation between the VFP table and the wells will
be indicated when the control of the well is specified, as a parameter of the keywords
WCONINJH (see 12.19.45) or WCONINJE (see 12.19.42).
• Add Row. Add a table-well tie in.
• Remove Rows.
• Add Wells to Table. Add wells to the table: 3 options are available by clicking on the
arrow.
– All Wells. Add all the wells for the tie in of VFP tables;
– Current Well Filter. Add the wells corresponding to the current well filter;
28.2. VFP tables for wells 229

18.1
– Well Filter. List of the different existing well filters which can be used.
• Load Table. Load a VFP table.

∗ Wells → VFP Table Name;
∗ Wells → VFP Table number.
– Add Rows. Add a file;
– Remove Rows. Remove a file.
28.2.2. Assign VFP Tables to Injection wells 230

18.1
28.3. Economical Limits

28.3.1. Economic Limits for Production Well
Setting of the economics for production wells. Adds the keyword WECON (see 12.19.68) to
the schedule. The following parameters have to be set:
• Limit Type:
– Minimum Oil Production Rate. Set the limit for the oil production rate;
– Minimum Gas Production Rate. Set the limit for the gas production rate;
– Maximum Water Cut. Set the limit for the water cut;
– Maximum Gas-Oil Ratio. Set the limit for the gas-oil ratio;
– Maximum Water-Gas Ratio. Set the limit for the water-gas ratio;
– Maximum Gas-Liquid Ratio. Set the limit for the gas-liquid ratio;
– Minimum Liquid Production Rate. Set the limit for the liquid production rate;
• Workover. Set the procedure for the wells on exceeding watercut, gas-oil ratio, water-
gas ratio or GLR limit. The following workover actions are possible:
– NONE: do nothing;
– CON: shut the worst offending perforation;
– WELL: shut in or step the well (9th parameter of WELSPECS, see 12.19.3);
– CON+: shut the worst offending perforation and below.
28.3.2. Economic Limits for Injection Well

Setting of the economics for injection wells. Adds the keyword WECONINJ (see 12.19.74)
to the schedule. The following parameters have to be set:
• Minimum Water Injection Rate. Set the minimum allowable injection rate. The well
will be shut if the rate of the well is inferior to this limit.
28.3. Economical Limits 231

18.1
28.4. ASP Flooding

28.4.1. Surfactant Concentration
This rule adds the keyword WSURFACT (see 12.19.163) to the schedule section. The fol-
lowing parameters have to be set:

• Concentration. Set the concentration of surfactant in the injection stream. Corresponds

to the second parameter of the keyword.
28.4.2. Polymer Concentration

This rule adds the keyword WPOLYMER (see 12.19.165) to the schedule section. The fol-
lowing parameters have to be set:

• Concentration. Set the concentration of polymer in the injection stream. Corresponds

28.4.3. Alkaline Concentration

Adds the keyword WALKALIN (see 12.19.164) to the schedule. The following parameters
have to be set:

• Concentration. Set the concentration of alkaline in the injection steam. Corresponds

28.4. ASP Flooding 232

18.1
28.5. Thermal properties

28.5.1. Thermal Properties of Injected Fluid
The keyword WINJTEMP (see 12.19.169) is added to the Schedule section. The parameters
of the keyword are specified in the fields:
• Steam Quality. Specifies the second parameter of the keyword WINJTEMP

(see 12.19.169) corresponding to the steam quality of the injected fluid;
• Steam Temperature. Specifies the third parameter of the keyword WINJTEMP

(see 12.19.169) corresponding to the temperature of the injected fluid;
• Pressure. Specifies the fourth parameter of the keyword WINJTEMP (see 12.19.169)
corresponding to the pressure of the injected fluid;
• Enthalpy. Specifies the fifth parameter of the keyword WINJTEMP (see 12.19.169)
corresponding to the specific enthalpy of the injected fluid.
28.6. Brine
28.6.1. Salt Concentration
This rule adds the keyword WSALT (see 12.19.166) to the schedule section. The following
parameters have to be set:

• Concentration. Set the concentration of salt in the injection stream. Corresponds to

the second parameter of the keyword.
28.5. Thermal properties 233

18.1
28.7. Other well rules

28.7.1. Well Specification Parameters
This rule adds the keyword WELSPECS (see 12.19.3) to the schedule section which will
introduce a new well. The parameters of the keyword have to be specified:
• Well. Select the name of the well in the list (available by double clicking on the field
Well);
• Reference depth. (METRIC: m, FIELD: f t ) Enter the reference depth of the well.
Recommended location: first perforated interval depth;
• Preferred phase. Select the phase from WATER, OIL, GAS or LIQUID. This data is
used to determine the worst offending well or connection for closure when a group
production rate limit is exceeding GCONPROD (see 12.19.79) (7-th parameter);
• Drainage radius. (METRIC: m, FIELD: f t ) Specify the drainage radius. If 0 is indi-

cated, the pressure equivalent radius of the grid blocks containing the well connections
is used. The productivity index equals 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 potential flow rate of the well 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);
• Inflow flag. Setting of the flag of the special inflow equation used to model the
flow of gas between the completed grid blocks and the well completions: STD, NO(the
standard inflow equations will be used or not), R_G, YES (Russell–Goodrich equation),
P_P (dry gas pseudopressure equation, should not be used for gas condensate), GPP
(generalized pseudopressure equation), LPP, QUAD (available by double clicking on
the white field);
• Shut-in-flag. Selection of the proper shut-in-flag from the list available by double
clicking on the white field;
• Crossflow flag. Selection the proper Crossflow flag from the list available by double
clicking on the white field:
– YES – crossflow is allowed in the well;

– NO – crossflow is not allowed in the well (connection is a oneway valve, which
prevents reverse drawdown flow).
• PVT region. The PVT region can be entered in the white field;
• Density calculation type. Type of density calculations for the wellbore hydrostatic
head (SEG – segmented model of density calculations. The mixture density in the
wellbore is calculated in each segment between two connections, and depends on the
28.7. Other well rules 234

18.1
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);
• FIP region. Number of FIP region, that will be used in the calculations of the well
rate in reservoir conditions.
The following buttons can also be used:
• Add Row. Adds a line corresponding to a well;
• Remove Rows.
• Add Wells to Table. The following options can be selected (the list is available by
clicking on the arrow): all wells (adds all the wells to the list), current well filter
(adds the wells from the current well filter), well filter(adds wells from the chosen well
filter);
• Load table. Can be used to load a table in text format containing columns with
parameters and well names.
28.7.1. Well Specification Parameters 235

18.1
29. Wells Data. Rules. Groups

29.1. Control
29.1.1. Group Production Controls
This rule specifies the production controls for groups. This rule adds the keyword GCON-
PROD (see 12.19.79) to the schedule section. The following parameters can be set:
• Groups. Set the groups to which the rule will be applied.
– Group: selection of a particular group from the list of groups.

– Groups from filter: the rule will be applied only to the groups selected in the
filter.
– All groups: the rule will be applied to all the groups present in the project.
• Limit type
– Oil Rate. Setting of oil rate target or upper limit. The value entered in the field
– Water Rate. Setting of water rate target or upper limit. The value entered in the
– Gas Rate. Setting of gas rate target or upper limit. The value entered in the field
– Liquid Rate. Setting of liquid rate target or upper limit. The value entered in the
– Res. Vol. Rate. Setting of the reservoir volume rate target or upper limit. The
value entered in the field will be taken as upper limit.
• Workover Action Description.
– No limit;
– NONE: do nothing;
– CON: shut the worst offending perforation;
– CON+: shut the worst offending perforation and below;
– WELL: shut in the worst offending well;
– RATE: group production rate is equal the violated upper limit;
• Respond to a Higher Level Group Target.
29. Wells Data. Rules. Groups 236

18.1
29.1.2. Group Injection Controls

This rule specifies the injection controls for groups. The keyword GCONINJE (see 12.19.88)
is added to the schedule section. The following parameters have to be set:

filter.
• Inj. Fluid. Set the second parameter of GCONINJE (see 12.19.88) keyword: Water,
Gas or Oil;
• Control Mode. Set the third parameter of GCONINJE (see 12.19.88) keyword:
– NONE – no immediate control;

– RATE – injection rate control;
– RESV – reservoir volume injection rate (total reservoir volume injection rate of
the group meets the parameter 5 of keyword GCONINJE, see 12.19.88);
– REIN – group injection will be equal to group production of the same phase multi-
plied by reinjection fraction specified in parameter 6 of GCONINJE (see 12.19.88);
– VREP – group injection in reservoir conditions will be equal to group production
in reservoir conditions multiplied by voidage replacement fraction specified in
parameter 7 of GCONINJE (see 12.19.88).
• Injection Rate. Setting of water rate target or upper limit. The value entered in the
• Res. Vol. Inj. Rate. Setting of the reservoir volume injection rate target in reservoir
conditions or upper limit. The value entered in the field will be taken as upper limit;
• Reinjection Fraction. Setting of reinjection fraction target or upper limit.
– Reinjection Group. Select a group with specified reinjection fraction limit.
• Voidage Replacement Fraction. Setting of voidage replacement target or upper limit;
– Voidage Replacement Group. Select a group with specified voidage replacement

limit.
• Respond to a Higher Level Group Target.
29.1.2. Group Injection Controls 237

18.1
29.1.3. Group Efficiency Factor

This rule specifies the efficiency factor for groups. The keyword GEFAC (see 12.19.77) is
added to the schedule section. The following parameters have to be set:

filter.
• Group Efficiency Factor. Corresponds to the first parameter of GLIFTOPT

(see 12.19.231). Group efficiency factor (part of time for which the group is work-
ing. If the group does not work for 15% of time, its efficiency factor should be
0.85).
29.1.3. Group Efficiency Factor 238

18.1
29.2. Economical limits

29.2.1. Economic Limits for Production Group
Setting of the economics for groups. Adds the keyword GECON (see 12.19.114) to the
schedule. The following parameters have to be set:

filter.
• Minimum Oil Production Rate. Set the limit for the oil production rate;
• Minimum Gas Production Rate. Set the limit for the gas production rate;
• Minimum Water Cut. Set the limit for the water cut;
• Maximum Gas-Oil Ratio. Set the limit for the gas-oil ratio;
• Maximum Water-Gas Ratio. Set the limit for the water-gas ratio;
• Workover. Set the procedure for the groups on exceeding watercut, gas-oil ratio, water-
gas ratio or GLR limit. NONE: do nothing, CON: shut the worst offending perforation,
CON+: shut the worst offending perforation and below.
29.2. Economical limits 239

18.1
29.3. Other group rules

29.3.1. Gas Lift Optimization
This rule specifies the group lift gas limits for gas lift optimization option. The keyword
GLIFTOPT (see 12.19.231) is added to the schedule section. The following parameters have
to be set:

filter.
• Maximum total gas rate. Corresponds to the third parameter of GLIFTOPT

(see 12.19.231). The lift gas supply for the group is equal to the sum of the lift
gas injection rates of its wells or groups, multiplied by their efficiency factors;
• Maximum lift gas supply limit. Corresponds to the second parameter of GLIFTOPT
(see 12.19.231). The lift gas supply for the group is equal to the sum of the lift gas plus
the gas produced from the formation for its well or group, multiplied by the efficiency
factor of the well or groups.
29.3.2. Create Group Hierarchy

This rule defines the well groups and the groups hierarchy. Adds the keyword GRUP-
TREE (see 12.19.93) to the schedule. The keyword WELSPECS (see 12.19.3) is also added
specifying the group for each well affected by the rule.
To work with groups the following buttons are available (on the panel C, see figure 29):
• Add Group. To add a sub–group to the selected group left–click on the group
(on panel B, see figure 29) and then press on this button. In order to change the group
position in a hierarchy left–click on the selected group and then drag–and–drop it;
• Remove Group. Removes the selected group;
• Load Hierarchy from File. Pressing this button calls the dialog:

∗ Well → Group;
∗ Group → Well;
∗ Group → Parent Group.
– Reload All. Can be used to erase all the previously defined groups and replace it
by the loaded groups;
29.3. Other group rules 240

18.1
Figure 29. Model Designer interface for Rules tab, Add a group hierarchy rule. A) List of
all the wells or of the wells defined in the well filter (if activated by using the right panel
button. B) List of existing groups. C) Set of buttons which allows to add new groups, remove
groups or load groups from files.
– Add Row. Add a file;

– Remove Row. Remove a file.
To define a group, the group has to be added (C area on Fig. 29) and selected on the
middle panel (B on Fig. 29). Then, the proper wells have to be selected on the right panel.
Import File Format:
File type: Well – Group.
Data description: well name; group to which this well belongs.
’WELL1’ ’SAT-1’
29.3.2. Create Group Hierarchy 241

18.1
File type: Group – Wells.

Data description: group name; wells which belong to this group.
’GRUP1’ ’PROD1’ ’PROD2’ ’PROD8’ ’PROD9’
’GRUP2’ ’INJ1’ ’INJ2’ ’INJ3’ ’INJ4’ ’INJ5’
’GRUP3’ ’WPR1’ ’WPR9’ ’WPR17’
’GRUP4’ ’WELSEGM3’
File type: Group – Parent Group.
Data description: group name; parent group name.
’GRUP1’ ’GRUP4’
29.3.2. Create Group Hierarchy 242

18.1
30. Wells Data. Rules. Other

30.1. User Keywords
• User Keywords. This rule allows to add E1/E3 and tNavigator format keywords. The
following options are available:
– Add keyword. Allows to add a new keyword;

∗ Text. This option allows to enter keyword parameters manually in the field
situated below the description of the keyword (parameters order has to be
respected) (see Fig. 31);
∗ Table. This option allows to fill keyword parameters using a predefined table
(only E1/E3 and tNavigator formats, see Fig. 30);
∗ Keyword. Selection of the keyword which has to be added. The list shows
all the keywords which are available.
Figure 30. User keyword in tabular format.
Figure 31. User keyword in text format.
– Edit Keywords. Allows to edit the selected keyword;

– Duplicate Keywords. Allows to duplicate the selected keyword;
30. Wells Data. Rules. Other 243

18.1
– Remove Keywords.Allows to remove the selected keyword.
• User Keywords (GE format). This rule allows to add GE format keywords.
• User Keywords (IM format). This rule allows to add IM format keywords.
• User Keywords (ST format). This rule allows to add ST format keywords.
30.2. Comment
Allows to add a text comment to the schedule section. The comment will appear in the
Schedule tab as an EDITOR_TEXT operation.
30.3. Wells and Groups Filter

This rule allows to create a Wells and Groups Filter that works the following way:
• Wells and Groups Filter is set on a specific time step. Starting from this time step all
rules are applied only for selected wells and groups (not to all wells available in the
project).
• In case if on the further step a new rule Wells and Groups Filter is set, then the
previous one stops working and only new rule works.
• When dynamic model is exported the keywords are written to Schedule section to
each date according to the filters that are used for wells and groups (and not for all
wells available in the project). Schedule section can be checked in advance in the tab
Schedule.
The rule Wells and Groups Filter can be created via existing filters (added before using
button on the right panel ) or new filters.
Please note that the rule Wells and Groups Filter is different from the button on the right
panel . Button on the right panel is used for visualization only. Wells that are available
in the project are visualized (or not visualized) on 2D, 3D, Graphs and Tables according to
the selection.
30.2. Comment 244

18.1
31. Other data

31.1. Variograms
31.1.1. Variogram models
Variograms are key tools in classical geostatistic, which are applied for analysis and mod-
elling of space correlation [9]. Further, the approach of variograms construction is briefly
outlined. Physical intuition suggests that values at two points, placed close to each other, are
close because these values are generated under similar physical conditions (have the same
”geological environment”). On the contrary, at long distance the conditions are different and
greater variations are to be expected. The value variability with the distance can be quantified
with the variogram cloud. Variograms are important tools for trend, cyclicity, geometric and
zonal anisotropy detection.
Let’s consider known values of f at N sample points {xi }, i = 1, ..., N , for which a
variogram will be constructed. All possible pairs of available points xi , x j , where 1 6 i <
j 6 N , are considered. For each pair the distance ρ = |xi − x j | and square of the difference
between values at these points v = ( fi − f j )2 are computed. The obtained set of points on a
plane (ρ, v) is called a variogram cloud.
A variogram cloud can display anisotropy (i.e. shows different behaviours along the
different directions). This is frequent in 3D cases, where vertical variability is rarely of
the same nature as horizontal variability (layer media). The main anisotropy directions are
often suspected from geological knowledge, and a variogram cloud is calculated along these
directions.
Depending on the function v(ρ) which is used to construct the curve that approximates
the cloud, the following variogram models are implemented:
Model type Formula

ρ

Exponential v(ρ) = c 1 − e − a

c 3ρ − ρ 3 ,


2a 2a3 if ρ < a;
Spherical v(ρ) =


c, if ρ > a

2

− ρ2
Gaussian v(ρ) = c 1 − e a
3 7ρ 5 3ρ 7

Cubic v(ρ) = c 7 ρa − 35ρ
4a3
+ 2a5
− 4a7

Nugget effect v(ρ) = c 1 − ρa sin ρa
Power law v(ρ) = cρ a
Cauchy v(ρ) = c log ρ
31. Other data 245

18.1
2
De-Vijs v(ρ) = c ρ 2ρ+a2
The output of a variogram computation is a plot where X-axis represents the distances
between wells (data points) split into the number of intervals assigned by the user. All well
pairs are considered and distances between them (i.e. the distances between wells in the same
layer) are computed. For each pair of wells the difference between corresponding values of
the selected property is computed. The Y-axis displays the squared difference of the selected
property values.
In case of the large number of wells, the point of variogram’s cloud (as shown by a
cross in the interface) represents a group of pairs of well, rather than a single pair. The wells
are grouped by distance between the wells and the variogram’s point displays the average
X-axis and Y-axis values. The red curve is created depending on the selected model type of
variogram.
It is very important to choose the proper variogram model, since the experimental points
themselves are not used in property computations.
A 2D variogram can also be computed for anisotropic models. The algorithm is the
same as for 1D plots: first, the model is discretized along X and Y in order to create a
variogram grid. If several data points are located in the same grid cell, an average value is
computed for the entire cell. So obtained data points are compared as for 1D plot and the
square of the difference between values at these points are computed and filled in the grid
(in tNavigator colors represent variogram values). This 2D plot allows to detect the main
anisotropy direction. The same can be performed in the case of spatial anisotropy for the XZ
plane (cf. figure 32).
31.1.2. Variogram Calculations

The following calculations are available:
• Build Isotropic Variogram by Markers;
• Build Isotropic Variogram by Logs;
• Build Anisotropic Variogram by Markers;
• Build Anisotropic Variogram by Logs;
• Build Isotropic Variogram by Blocked Wells;
• Build Anisotropic Variogram by Blocked Wells.

Build Isotropic Variogram by Markers
This calculation allows to create an isotropic variogram using well markers. The markers
depth will be considered. The following parameters have to be set:
• Variogram Name. Output name of the computed variogram;
31.1.2. Variogram Calculations 246

18.1
Figure 32. A) Display of a 2D variogram and of the main and orthogonal directions. The 2D
grid is defined by the number of X and Y intervals and the colors correspond to variogram
values, blue colors represent the minimum data variation, while the red ones, display the
maximum anisotropy. The main variogram azimuth has to be set along the minimum data
variation. B) Display of a 1D variogram computed along the main direction. The number of
points is given by the number of intervals

18.1
• Well Marker. Set the well markers which will be used to compute the variogram;
• Well Filter. The variogram will be computed only for the wells selected in the filter;
• Variogram Model Type. Selection of the variogram type (cf. Variogram model type
description);
• Correlation Radius. Distance between the data points. The wells separated by distances
exceeding the assigned radius are excluded from the variogram construction. If the
distance between wells is within the radius the wells are included in the variogram
computation;
• Number of Intervals. Number of lags (corresponds to the number of points of the vari-
ogram) (see Fig. 33).
Figure 33. Plot representing the XY plan. The direction of computation is defined by
its azimuth, the points which are taken into account are defined by the tolerance, the
discretization is represented by the number of intervals. The points which are taken into
account are then ploted on the 1D variogram
In variogram tabs, the following parameters can be set:
• Range. Starting point of the near-straight-line section of the curve. Corresponds to the
point where the curve has reached 95% of the sill. The value can be entered in the
corresponding field or the cursor can be moved to fit the experimental variogram curve
to the points;

18.1
• Sill. Height of the near-straight-line section of the curve. The value can be entered in the
to the points;
• Nugget Effect. Value of the variogram at the origin. The nugget effect can be due to
measurement errors or to variations at microscales (inferior to the sampling distances).
The value can be entered in the corresponding field or the cursor can be moved to fit
the experimental variogram curve to the points.
Build Isotropic Variogram by Logs

This calculation allows to create an isotropic variogram using well logs. Logs values will
be considered. The following parameters have to be set:
• Well Log. Set the well logs which will be used to compute the variogram (raw data);
• Well Filter. Well filter setting. If a well filter is selected, the computation will be per-
formed only for the wells present in the well filter;
• User Cut. The variogram will be computed only for the points situated in the selected
area. Only the points situated in the selected blocks will be taken into account. To select
an area, the property or the region has to be selected from the list and the condition
has to be set with the operator (the proper operator has to be selected from the list)
and the corresponding value (which has to be entered in the corresponding field). This
option can be particularly useful when a Net-To-Gross property is defined: a variogram
containing only reservoir data can be computed using the condition NTG = 1;
description);
• Correlation Radius. Distance between the data points. Points separated by distances
distance between the points is within the radius the points are included in the variogram
computation;
ogram, see Fig. 33);
to the points;

18.1
to the points;
Build Anisotropic Variogram by Markers
This calculation allows to create an anisotropic variogram using well markers. The mark-
ers depth will be considered. In the case of anisoptropic variograms, first, a 2D variogram
is computed. Then, classical 1D variograms are calculated and the plot is displayed. The
following parameters have to be set (see Fig. 33):
• Well Marker. Set the well markers which will be used to compute the variogram;
• Well Filter. The variogram will be computed only for the wells selected in the filter;
description);
• Anisotropy. Selection of the anisotropy type (Plane or Spatial). If the anisotropy is a plane
one, the vertical variogram will not be computed.
• 2D Variograms. Parameters which concern the 2D variogram (along X and Y axis) which
will be computed. The following settings are available:
◦ Same Parameters for All Axes. This option allows to set the same parameters
along X and Y axis;
◦ X Correlation Radius. Distance between the wells (data points). Points separated
by distances exceeding the assigned radius are excluded from the 2D variogram
construction. If the distance between the data points is within the radius, the points
are included in the variogram computation;
◦ Number of X Intervals. Discretization intervals number along X axis. If the model
contains a high number of wells, it is recommended to increase the number of
intervals;
◦ Y Correlation Radius.
◦ Number of Y Intervals.
◦ Z Correlation Radius.
◦ Number of Z Intervals.
• Directional Variograms.

18.1
◦ Same Parameters for All Directions. This option allows to set the same parame-
ters along the main, the orthogonal and the vertical direction;
◦ Main Direction. Correlation Radius. Distance between the data points. Points
separated by distances exceeding the assigned radius are excluded from the var-
iogram construction. If the distance between the data points is within the radius,
the points are included in the variogram computation;
◦ Main Direction. Number of Intervals. Discretization intervals number along the
direction of computation;
◦ Main Direction. Tolerance. Deviation angle from the direction of computation
defining the area within which the points are taken into account for the computa-
tion;
◦ Normal Direction. Correlation Radius. Distance between data points. Points sep-
arated by distances exceeding the assigned radius are excluded from the variogram
◦ Normal Direction. Number of Intervals. Discretization intervals number along
the direction of computation;
◦ Normal Direction. Tolerance. Deviation angle from the direction of computa-
tion defining the area within which the points are taken into account for the
computation;
◦ Vertical Direction. Correlation Radius. Distance between data points. Points sep-
◦ Vertical Direction. Number of Intervals. Discretization intervals number along
◦ Vertical Direction. Tolerance. Deviation angle from the direction of computa-
computation;
to the points;
to the points;

18.1
For anisotropic variograms the following additional parameters are computed (see Fig.
33):
• Azimuth. Sets the azimuth of the main anisotropy direction (angle between the direction
and X axis). This estimation can be based on the result obtained by 2D variogram
computation. The azimuth has to be chosen in order to accurately characterize the
variability;
• Dip. Sets the dip for the vertical variogram computation;
• Range Main. Starting point of the near-straight-line section of the curve displaying the
variogram build along the main direction (given by the azimuth). Corresponds to the
to the points;
• Range Normal. Starting point of the near-straight-line section of the curve displaying the
variogram build along the normal direction (orthogonal to the main one). Corresponds
to the point where the curve has reached 95% of the sill. The value can be entered in
the corresponding field or the cursor can be moved to fit the experimental variogram
curve to the points;
• Range Vertical. Starting point of the near-straight-line section of the curve displaying the
variogram build along the vertical direction. Corresponds to the point where the curve
has reached 95% of the sill. The value can be entered in the corresponding field or the
cursor can be moved to fit the experimental variogram curve to the points.
Build Anisotropic Variogram by Logs

This calculation allows to create an anisotropic variogram using well logs. Logs values
will be considered. The following parameters have to be set (see Fig.33):
• Well Log. Set the well logs which will be used to compute the variogram (raw data);

18.1
containing only reservoir data can be computed using the condition NTG = 1;;
description);
along X and Y axis;
intervals;
tion;

18.1

computation;
computation;
to the points;
to the points;
For anisotropic variograms the following additional parameters are computed:
variability;
to the points;

18.1
Build Isotropic Variogram by Blocked Wells

This calculation allows to create an isotropic variogram using blocked data. Blocked
values will be considered. In order to compute the variograms for blocked wells, the template
of the log curve and the blocked wells property has to be set.
The following parameters have to be set (see Fig.33):
• Blocked Wells Log. Set the blocked well logs which will be used to compute the vari-
ogram;
containing only reservoir data can be computed using the condition NTG = 1;
• Filter by Layers. If this option allows to compute the variogram by layers. So the pairs
of points used for the computation will lay within the same layer;
• Facies. Available for discrete properties. List of available categories (facies types). To
select a category for the computation, the box in front of it has to be checked. Please
note that in order to properly compute blocked wells and variograms by blocked wells,
the log template has to be properly set (Select a log template). If the template is not
set, the facies categories will not be available for the computation. Note also that this
computation will allow to create as many variograms as used facies;
description);

18.1
• Correlation Radius. Distance between the data points. Points separated by distances
distance between the points is within the radius, the points are included in the variogram
computation;
ogram, see Fig. 33);
Build Anisotropic Variogram by Blocked Wells

This calculation allows to create an anisotropic variogram using blocked data. Blocked
values will be considered. The following parameters have to be set (see Fig.33):
• Blocked Wells Log. Set the blocked well logs which will be used to compute the vari-
ogram;
• User Cut. The variogram will be computed only for the cells situated in the selected area.
Only the the selected blocks will be taken into account. To select an area, the property
or the region has to be selected from the list and the condition has to be set with the
operator (the proper operator has to be selected from the list) and the corresponding
value (which has to be entered in the corresponding field). This option can be partic-
ularly useful when a Net-To-Gross property is defined: a variogram containing only
reservoir data can be computed using the condition NTG = 1;;
• Filter by Layers. If this option allows to compute the variogram by layers. So the pairs
of points used for the computation will lay within the same layer;
• Facies. Available for discrete properties. List of available categories (facies types). To
select a category for the computation, the box in front of it has to be checked. Please
note that in order to properly compute blocked wells and variograms by blocked wells,
the log template has to be properly set (see Select a log template). If the template is
not set, the facies categories will not be available for the computation. Note also that
this computation will allow to create as many variograms as used facies;
description);
description);

18.1
along X and Y axis;
intervals;
tion;
computation;

18.1
computation;
to the points;
to the points;
For anisotropic variograms the following additional parameters are computed:
variability;
to the points;

18.1

18.1
31.2. Interpolation methods

Interpolation is the process of applying values (e.g. porosity, permeability, uncertainty etc.)
assigned to certain points to entire domain. In tNavigator interpolation is used:
• in graphical interface of hydrodynamics to edit grid properties, User Maps, User Cuts
via Property Editing.
• in Geology Designer and Model Designer to interpolate 2D Maps, horizons and prop-
erties.
tNavigator supports the following interpolation methods:
• Deterministic method:
- Least Squares method;

- Trivial interpolation method;
- Multilayer IDW method.
• Geostatistical method:
- Kriging;
- Sequential Gaussian Simulation (SGS) method.
In this section a general description of methods is given.

There are a large number of interpolation methods. The most popular of deterministic methods
is the Least-Squares method (see [5], [8]).
In tNavigator there are two possibilities of this method’s implementation:
• Multilayer Least Squares method;
• 3D Least Squares method.
In the first case, the three-dimensional interpolation problem is converted to the two-
dimensional one, i.e. an interpolation is carried out for each grid’s layer independently.
General description of the method. Let’s consider a grid, consisting of arbitrary shaped
non-crossing polyhedrons (blocks) {b} defined by 8 peaks. Some of polyhedron’s peaks may
coincide. For each block’s peak the space coordinates (cx , cy , cz ) are defined. Let’s N values
of function F defined at arbitrary points {x} are known: Fi = F(xi ), i = 1, ..., N . If a block
bi contains a point xi , then the value Fi = F(bi ) is defined in the block. Generally speaking
a distribution of points do not coincide with grid’s blocks. In this case the values F(xi ) are
interpolated to grid’s blocks. Further, for the sake of simplicity, let’s suppose that values
of function F are defined in grid’s blocks, i.e. Fi = F(bi ). In addition to a set of blocks
{b}, a grid contains a set of links between blocks links. linked(bk ) denotes a set of blocks
31.2. Interpolation methods 260

18.1
connected with a block bk , li j denotes a link between bi and b j blocks. A non oriented
direction of link between blocks Axis(li j ) = (x(li j ), y(li j ), z(li j )) is defined by faces, which
are mutal for the blocks. An orientation of the link between blocks is defined by the function
Dir(li j ) (i.e. x+ , x− , y+ , y− , z+ , z− ). hx (bi ), hy (bi ) and hz (bi ) are the distance between mass
centers of bi block’s faces along Ox , Oy and Oz, respectively.
Based on the limited set of function values the function f ∗ , minimizing a least mean
square error of approximation calculated at the points {x}, can be defined as:
N
f ∗ = ∑ (Fi − f (xi ))2 + αR1 ( f ) + β R2 ( f ),
i=1
where R1 ( f ) and R2 ( f ) are correction functions, α and β are coefficients, which defines an
impact level of correction functions and varies in the range [0.01, 100]. Correction functions
limit a variability of approximation values and allow to obtain smoother solutions. First and
second derivatives of function f can be chosen as correction functions. R1 ( f ) and R2 ( f )
are computed by summation over neighboring blocks (i, j):
R1 ( f ) = ∑ w2i j ( f (bi ) − f (b j ))2 ,

l(bi ,b j )∈links
N 2

2
R2 ( f ) = ∑ ∑ wik f (bk ) − f (bi ) − wk j f (b j ) − f (bk ) / hAxis(lik ) (bk )
k=1 bi ,b j ∈linked(xk )
Dir(lik )=Dir(lki )
where wi j is the weight coefficient, which can be defined differently, li j = l(bi , b j ) is a link
between bi and b j blocks, linked(bk ) are set of blocks linked with a block bk , hAxis (bi )
is the distance between mass centers of bi block’s faces, quasi-orthogonal to directions
Axis = (x, y, z).
Depends on the chosen grid’s geometry coefficients wi j can be defined as:
• If wi j = 1/hi j (where hi j is the distance between mass centers of adjoining blocks),

then R1 is a sum of square of finite-difference approximations of f derivatives along
directions Axis = (x, y, z). R2 is a sum of square of approximations of second deriva-
tives .
• If wi j = 1 the grid’s geometry does not take into account.
• If wi j = Ti j , where Ti j is transmissibility of link li j , then R1 is computed by integration

of (∇ f ,~n) over adjoining face of bi and b j blocks, where ~n is the unit vector normal
to the face directed to bi block. In case of rectangular grid Ti j is the ratio of square of
adjoining face of bi and b j blocks to the distance between their mass centers.

18.1
31.2.2. Trivial interpolation method

In the trivial interpolation method to each grid’s block bi , i = 1, ..., M , in which a function
f value is not defined, a constant value C is assigned: f (bi ) = C . By default C = 0. The
assignment is carried out by layers independently.
With this method, only the cells situated along the wells will be affected by a value
different from 0. If the input data are logs, an arithmetical mean (in the case of continuous
property) or the most frequent value (in the case of discrete property) will be affected to the
cells with several data points.
31.2.2. Trivial interpolation method 262

18.1
31.2.3. Multilayer IDW method

Method of Inverse Distance Weighting (IDW) is a deterministic interpolation method. IDW
method is based on the idea that objects placed in the vicinity are more similar to each
other then objects placed far from each other. To interpolate a value in arbitrary space point
IDW method uses known values defined in the points neighbouring to this point. At the
same time, the values in the points placed closer to the interpolated point have a stronger
impact on the forecast value, then values in the remoted points. Thus, each point affects the
forecast value only locally, and the impact decreases with increase of distance. This means
that points placed close to the interpolated point have larger weights. Point’s weight decreases
as a function of distance. Therefore, method is called as inverse Distance Weighting method.
In case of three–dimensional interpolation is carried out a dimension can be decreased to
two–dimension by implementing the IDW interpolation to each two–dimensional layer of
three–dimensional grid.
Let’s N values of arbitrary function f are known and defined at grid’s points xi : fi =
f (xi ). The interpolated value of the function f at a space point x∗ is calculated by using the
function’s values fi at the points xi (interpolation nodes), i = 1, ..., N :
N
 ∑ ωi (x∗ ) fi
, if d(x∗ , xi ) > 0 for each i;
 i=1

 N
∗ ∗
f (x ) = ∑ ωi (x )
 i=1


fi , if d(x, xi ) = 0 for an arbitrary i;

where ωi = d(x∗1,xi ) p are weights corresponding to data points, d(x∗ , xi ) is the distance between
x∗ and xi , p is a power parameter.
31.2.3. Multilayer IDW method 263

18.1
31.2.4. Kriging
Kriging is a general linear regression method using statistical parameters to find optimal es-
timations in terms of minimum mean square deviation when constructing surfaces, properties
and User Maps ([7, 6, 9]). The method is based on the principle of undisturb average value.
This means that all values taken together should have a correct average value. A global
undisturbness is formally provided by increase of low values and decrease of high values. To
calculate unknown value of variable at a space point the Kriging method uses a variogram,
a configuration of space data and values at the points in the vicinity of the selected point.
A construction of variograms allows user to match a quantitative model with an available
structure of space data.
In tNavigator there are two possibilities of Kriging implementation:
• Multilayer Kriging;
• 3D Kriging.
In case of Multilayer Kriging method is used, an interpolation is carried out independently

for each grid’s layer, i.e. a three–dimensional interpolation problem is converted to a two–
dimensional one.
The following Kriging’s methods are supported:
• Simple Kriging;
• Ordinary Kriging;
• Universal Kriging.
General description of the method Let’s N values of function f are known and defined
at points (blocks) xi of grid G: fi = f (xi ). A function value is assumed to be constant inside
a block. A grid is a set of arbitrary shaped non-crossing polyhedrons (blocks) defined by 8
peaks. Some of polyhedron’s peaks may coincide. For each block’s peak the space coordinates
(cx , cy , cz ) are defined. The aim of interpolation is to construct an interpolation function fb,
which is a good approximation of unknown function f : fb(x) ≈ f (x) for each x ∈ G.
At a space point x∗ the Kriging interpolation is linear combination of known values of
the function defined at the points x :
N
fb(x∗ ) = ∑ wk (x∗) f (xk )
k=1
Summation is carried out for known function values defined at corresponding points with
coefficients wk . wk coefficients are calculated by solving the system of linear equations.
Notice that to calculate wk coefficients f1 , ..., fN values do not use. Instead, positions of
points x1 , ..., xN and a model of probability process (variogram) are used.
It is supposed that a function f is a random function. Hence, fi = f (xi ) are random
values. Then, their linear combination is a random value as well. wk coefficients are calcu-
lated in such way that a mathematical expectation of random variable fˆ(x∗ ) is equal to a
31.2.4. Kriging 264

18.1
mathematical expectation of value of random function f (x) at this point, and dispersion of
their difference is minimal:
M( fb(x)) = M( f (x)), D( fb(x) − f (x)) → min.
31.2.4. Kriging 265

18.1
31.2.5. Sequential Gaussian Simulation (SGS) method

Sequential Gaussian Simulation method is similar to the Kriging. To get more details see
[6, 9].
In tNavigator there are two possibilities of implementation of this method:
• Multilayer SGS;
• 3D SGS.
Multilayer SGS method is carried out independently for each grid’s layer, i.e. a three–
dimensional interpolation problem is converted to a two–dimensional one.
General description of the method. Let’s define a grid G composed of arbitrary shaped
non-crossing polyhedrons (blocks) {b} defined by 8 peaks. Some of polyhedron’s peaks may
coincide. For each block’s peak the space coordinates (cx , cy , cz ) are defined.
Let’s consider known values of function f at N sample points xi of grid G: fi = f (xi ),
i = 1, ..., N . A function value fi is assumed to be constant inside a block.
A process of variogram construction for this method coincide with construction in method
Kriging.
In contrast to Kriging method, for the SGS method the result of interpolation at point x∗
is a linear combination of defined number of points Nk (where Nk is the number of kriging
points) selected in the region limited by Kriging Radius.
A summation is carried using known values of function f defined at points xi :
Nk
fb(x∗ ) = ∑ wi (x∗ ) f (xi )
i=1
wi coefficients are calculated by solving a system of linear equations.
31.2.5. Sequential Gaussian Simulation (SGS) method 266

18.1
32. Graphs
Designer contains advanced tools to work with graphs, including:
• making fast selection of graphs to view;
• showing several sets of graphs in one view;
• building graphs of sums or average values for selected objects;
• setting graph preferences (color, thickness, names, fonts and so on);
• exporting and importing graph templates from one model to another.
For the detailed information see the training tutorial 1.7 Graph templates.
The Graph calculator button on the right panel allows the creation of custom graphs
(see 32.1. Graph calculator).
32. Graphs 267

18.1
32.1. Graph calculator

Graph calculator allows the arbitrary combination of existing parameters and data series of the
model using mathematical functions, numerical differentiation and/or integration, conditional
operators, cycles, and other means of Python programming language.
Graph calculator is also available in the Advanced History Matching GUI, where it allows
using the calculated graphs as target function for optimization, and also in the simulator GUI.
Figure 34. Graph calculator
Text editor of the graph calculator window allows entering of arbitrary code in Python.
Importing standard libraries using import <name> is possible (see also Importing libraries).
Python console output is directed to the window below and can be used for debug purposes.
Once the script has been executed, the resulting graph appears in the list of User graphs
of the template (see figure 35) and can be selected for display individually or in combination
with other graphs. Its dimension can be selected arbitrarily in the Units field. Whether it
will appear for Field, Well, or Connection object is determined by its type, which in turn is
determined by its declaration (see below graph function under Global functions) or by the
type of the graph(s) it was derived from. Inconsistency in those may lead to an error in the
script.
A script is saved at the moment of successful execution. If you walk away to another
script or close the Graph calculator window before that, the changes may be lost. Scripts are
32.1. Graph calculator 268

18.1
Figure 35. User graphs
permanently saved within the project when it is closed, but are not included in the exported
graph templates.
The name of the variable used in the last assignment operator in the code is interpreted as
the name of the custom graph which is created or modified as the result of script execution.
By changing the name of that variable you may effectively create a copy of an existing script.
The code may include predefined objects (field, wells, groups, connections and FIP
regions). For treating these objects, the following properties and functions are defined and
accessible on the right panel:
• Add well function

Well object has the following accessible properties and functions:
◦ .name is a property containing the name of the well.

Usage example: s1 = w1.name
Code fragments presented here and below are merely illustrations

! of syntax. They are not self-sufficient and not intended to work if
copied-and-pasted to the calculator "as is". For the ready-to-use
examples see Usage examples.
◦ .connections is a property which is an iterator object containing the well’s connec-
tions.
Usage example: for c in w1.connections: hdo somethingi

18.1
◦ .is_producer() (no arguments) returns an object that casts to boolean True if the
well is a producer, and to False otherwise.
Usage example: if w1.is_producer(): hdo somethingi
◦ .is_opened() (no arguments) returns an object that casts to boolean True if the well
is open, and to False otherwise.
Usage example: if w1.is_opened(): hdo somethingi
• Add group function

Group object represents a group of wells and has the following accessible properties:
◦ .name is a property containing the name of this group.

Usage example: s1 = g1.name
◦ .wells is a property which is an iterator object containing the wells of this group.
Usage example: for w in g1.wells: hdo somethingi
Iterator is a structure that provides an interface for traversing a

collection of elements one by one (for ... in ...). Can be transformed
i to an array which allows direct access to any element by number:
wells = [*g1.wells()]
w = wells[5]
◦ .parent_group is a property containing the parent group of this group.
Usage example: g2 = g1.parent_group
◦ .child_groups is a property which is an iterator object containing the child groups
of this group.
Usage example: for g in g1.child_groups: hdo somethingi
• Add model function

Model object has the following accessible property:
◦ .name is a property containing the model name (relevant when the results of multi-
ple model calculations are loaded).
Usage example: s1 = m1.name
• Add timestep functions

Timestep object represents an individual step in the time line of the model, and has the
following accessible properties and functions:
◦ .name is a property containing the calendar representation of this time step object
according to the template (selected from the dropdown list in the Date format
field below).
Usage example: s1 = t1.name
◦ .to_datetime() (no arguments) returns the Python datetime object corresponding to
this time step. The object has standard Python properties and methods. Usage
example:

18.1
dt1 = t1.to_datetime()
if dt1.year > 2014: hdo somethingi
• Add graph function

Graph object represents a graph which may be either one of the standard graphs or
derived via calculations. The ultimate result of script execution is also an object of this
type. A graph has the following accessible functions:
◦ .fix(model='',object='',date='') returns the value of the specified graph for the

given model, object, and date. All arguments are optional. If some of them are
missing, the function returns an object containing the values of the graph for all
possible values of the missing argument(s).
Usage example:
graph2 = graph1.fix(date='01.01.2013')
returns a graph object containing only one value at all times, namely the value of
the original graph on 01.01.2013. If the original graph was referring to wells, so
will be the result.
◦ max,min,avg,sum(models='',objects='',dates='') retrieve a subset of values for the
given models, objects, and dates (all arguments may include multiple values in a
form of comma-separated lists), and then return the minimum, maximum, aver-
age, or sum of the resulting array. All arguments are optional. If some of them
are missing, the functions return an object containing the values of minimum,
maximum, average, or sum over all specified argument(s) for all possible values
of the missing argument(s).
Usage examples:
graph2 = graph1.min(dates='01.01.2013,01.01.2014,01.01.2015')
returns a graph object containing only one value at all times, namely the min-
imum among the values of the original graph on 01.01.2013, 01.01.2014, and
01.01.2015.
graph2 = graph1.avg(objects='WELL31, WELL32, WELL33')
returns a graph containing averaged values of the original graph for the wells
WELL31, WELL32, and WELL33.
◦ .aggregate_by_time_interval(interval='',type='') takes the array of values of the
original graph over the specified interval (possible values: month, year) and
derives a new graph where all steps within the interval have the same value
calculated according to the specified type:
– avg: average value;
– min: minimum value;
– max: maximum value;
– last: last value;
– sum: sum of values;
– total: difference between the last and first values.

18.1
Usage example:
w1 = wopr.aggregate_by_time_interval(interval = 'year', type = 'avg')
returns a graph which is piecewise constant over one-year intervals, and the value
on each interval is the average of the original graph (wopr, that is, oil rate) over
that interval.
◦ .to_list() (no arguments) returns an array of values of the graph. This function
only works for one-dimensional graphs, otherwise it throws an error. To make a
graph one-dimensional, that is, dependent on time only, you have to exclude the
dependence on the model and the well, either specifying these explicitly via .fix(),
or by finding the value of .min(), .max(), etc. over them all. Usage example:
x=fopr.fix(model='BRUGGE_VAR_1').to_list()
returns an array of the field oil rate values for all time steps.
• Add global function

General purpose functions, including:
◦ exp(number), ln(number) are mathematical functions.

Usage examples:
t = ln(y)
x = exp(r)
◦ diff(series) performs numeric differentiation of the time series, that is, return the
series of differences of successive values.
Usage example: graph2 = diff(graph1)
In this example we are calculating oil totals per time step from oil totals:
465, 1165, 2188, 3418, 4968 . . . → 465, 700, 1023, 1230, 1550 . . .
◦ diff_t(series) is the same as diff, only the results are divided by the time step length
in days. Usage example: graph2 = diff_t(graph1)
In this example we are calculating oil rates from oil totals. Let the time steps
represent months and have the duration of 31, 28, 31, 30, 31... days. Then:
465, 1165, 2188, 3418, 4968 . . . → 15, 25, 33, 41, 50 . . .
◦ cum_sum(series) performs numeric integration of the time series, that is, returns
the series of sums.
Usage example: graph3 = cum_sum(graph1)
In this example we are calculating oil totals from oil totals per time step:
465, 700, 1023, 1230, 1550 . . . → 465, 1165, 2188, 3418, 4968 . . .
◦ cum_sum_t(series) is the same as cum_sum, only the increments are multiplied by

the time step length in days.
Usage example: graph3 = cum_sum_t(graph1)

18.1
In this example we are calculating oil totals from oil rates. Let the time steps
represent months and have the duration of 31, 28, 31, 30, 31... days. Then:
15, 25, 33, 41, 50 . . . → 465, 1165, 2188, 3418, 4968 . . .
◦ if_then_else(condition,option_if_true,option_if_false) is the conditional operator

that works on array variables element-wise.
Usage example: graph1 = if_then_else(wopr > 10, 1, 0)
◦ get_well_by_name(name) returns a well by its name.
Usage example: w1 = get_well_by_name('prod122')
◦ get_group_by_name(name) returns a group by its name.
Usage example: g1 = get_group_by_name('group21')
◦ get_all_wells() (no arguments) returns an iterator object containing all wells.
Usage example: for w in get_all_wells: hdo somethingi
◦ get_all_groups() (no arguments) returns an iterator object containing all groups.
Usage example: for g in get_all_groups: hdo somethingi
◦ get_all_models() (no arguments) returns an iterator object containing all models
(relevant when the results of multiple model calculations are loaded).
Usage example: for m in get_all_models: hdo somethingi
◦ get_all_timesteps() (no arguments) returns the iterator object containing all time
steps.
Usage example: for t in get_all_timesteps: hdo somethingi
◦ create_table_vs_time(array) returns a graph containing a piecewise linear approx-
imation of the given time series. The series must be represented by an array of
two-element tuples (date,value).
Usage example:
oil_price_list = []
oil_price_list.append(('01.01.2011',107.5))
oil_price_list.append(('01.01.2014', 96.3))
oil_price = create_table_vs_time(oil_price_list)
Here we build a graph of oil prices. For maximum clarity, the array is prepared
by adding elements one by one.
◦ get_wells_by_mask(mask) returns an iterator object containing wells that match
the given name mask. The mask may contain wildcards: ? means any character,
* means any number of characters (including zero).
Usage example: for w in get_wells_by_mask('prod1*'): hdo somethingi
◦ get_wells_by_filter(filter_name) returns an iterator object containing wells that are
included in the given well filter. The filter must be created beforehand using

18.1
Well Filter .
Usage example: for w in get_wells_by_filter('first'): hdo somethingi
◦ shift_t(original_series,shift,default_value) returns the original graph shifted by the
specified number of time steps. The empty positions are padded with the specified
default value.
Usage example: graph2 = shift_t(graph1,3,10)
In this example we shift the historic records of oil rate which were mistakenly
assigned to the wrong time. The series is shifted 3 steps to the right, and the
starting positions are filled with the first known value of oil rate (10).
10, 12, 19, 24, 30, 33, 31, 27, 25 . . . −→ 10, 10, 10, 10, 12, 19, 24, 30, 33 . . .
| {z } | {z }
graph1 shift_t(graph1,3,10)
◦ get_project_folder() (no arguments) returns the full path to the folder containing
the current model, which you might need in order to write something to a file.
Usage example: path = get_project_folder()
◦ get_project_file_name() (no arguments) returns the file name of the current model
without an extension.
Usage example: fn = get_project_file_name()
◦ graph(type='',default_value='') initializes a graph of the given type (field, well,
group, conn for connections, or fip for FIP regions) and fills it with the given
default values.
Usage example: tmp = graph(type='field', default_value=1)
Lower right section contains the list of mnemonics (same as in the keyword SUMMARY,
see 12.18.1). Their meaning is explained in the pop-up messages. Mnemonics are grouped
by type (field, group, well, etc.); types are selected in the lower left field. Each mnemonic
contains an array of values for all time steps. If it is applicable to wells or groups, then for
each time step it contains an array of values for all wells or groups. It is possible to retrieve
values of mnemonics per object: for example, wopr[w1] returns oil rate for the well w1.
Mnemonics can be used directly in the code and are interpreted as graph objects. Arith-
metical operators and mathematical functions apply to them element-wise and return objects
of the same type.
If the model contains any variables created by the keyword UDQ (see 12.19.151), those
can be used by putting their names in the code. They are also interpreted as graph objects.
! Note that other custom graphs, including those defined in the same template,
are not accessible from the code by their names.
32.1.1. Importing libraries

Python has a considerable body of libraries for data processing, including sophisticated
mathematical methods, export to Excel and other common formats, etc. All this can be
accessed from the graph calculator.
32.1.1. Importing libraries 274

18.1
Standard Python libraries can be imported as is:

import datetime
To import custom or third-party libraries, do the following:
1. Install Python 3.6.4 or later for all users.
2. If you intend to use Win32 API:
2.1. Install pywin32 package.

2.2. Run the following command:
hPython installation f olderi\Scripts\pywin32_postinstall.py -install
3. In that instance of Python, install the libraries you intend to use.
4. In tNavigator main window, go to Settings → Options → Paths.
5. Change the following parameters:
5.1. Under Use External Python3.dll select the path to Python3.dll from the new
instance of Python.
5.2. Under Path to Python Modules select the path to imported Python modules.
32.1.2. Usage examples

Example 1
Suppose we want to see what portion of the well’s oil rate comes from the layers with
70 6 k < 100.
This is possible in the simulator or Model Designer GUI, where the graph
! calculator has access to the data on individual connections, but not in the
AHM GUI.
The script proceeds as follows:
1. Initialize a temporary data structure (tmp) of the appropriate type (graph in the Well
context) and fill it with 0;
2. Iterate over all connections:
• If the connection is located in the desired area,

– add its oil rate value to that of the corresponding well in the temporary
structure;
3. Return the temporary array divided by the array of total oil rate values for the wells
(the division of graphs is applied element-wise, that is, a sum over connections of any
well is divided by the rate of the same well).
32.1.2. Usage examples 275

18.1
Example
tmp = graph(type='well', default_value=0)
for c in get_all_connections():
if c.k in range(70,100):
tmp[c.well] += copr[c]
wopr_layer2 = tmp/wopr
! Pay attention to the spaces at the beginning of the lines. They are essential
to Python syntax, and are easily lost during copying-and-pasting.
Example 2
Suppose we want to calculate the average oil rate over a certain subset of wells (those
with names starting with 'WELL3') and compare it with the historic data, which are stored in
a file elsewhere. The deviation will then be used as an objective function for matching. The
script proceeds as follows:
1. Obtain an iterator over the required subset of wells, transform it to the list of names,
and join them into a comma-separated string;
2. Pass the resulting string to avg function and obtain the desired average (obs).
3. Locate the file input.txt in the model folder and open it for reading.
4. Transform the array of file lines into the array of tuples (date,value).
5. Build the interpolation graph from the data in the file (hist).
6. Build the graph of squared deviation.
Example
s=','.join ([x.name for x in get_wells_by_mask ('3*')])
obs = wopr.avg (objects = s)
inpf = open(get_project_folder()+'/input.txt', 'r')
arr = [ (line.split()[0],float(line.split()[1])) for line in inpf ]
hist = create_table_vs_time(arr)
fuobj = (obs - hist)**2
Example 3
Suppose we have the graphs of historic bottom hole pressure measured only at some
points; the rest is filled with 0. We want to interpolate those for the entire time range. The
script proceeds as follows:
1. Initialize a temporary data structure (tmp) of the appropriate type (graph in the Well
context) and fill it with 0;

18.1
2. Iterate over all models and all wells:
• Retrieve the BHP data for the given well;

• Create an empty array to store the actual BHP measurements (observed);
• Iterate over all time steps:
– If the BHP at this time step is greater than 0,
– we append it to the array;
• If the array contains at least 2 elements,
• we create an interpolated graph from it and put it in the temporary structure;
3. Return the temporary structure.
Example
tmp = graph (type = 'well', default_value = 0)
for m in get_all_models():
for w in get_all_wells():
current = wbhph[m,w]
observed = []
for t in get_all_timesteps():
if current[t] > 0:
observed.append ((t.name, current[t]))
if len (observed) >= 2:
tmp[m,w] = create_table_vs_time(observed)
interpolated_wbhph = tmp

18.1
33. References
[1] Tarek Ahmed, Equations of State and PVT Analysis: Applications for Improved Reservoir Mod-
eling, Gulf Publishing Company, Houston, Texas, 2007.
[2] Tarek Ahmed, Working Guide to Vapor-liquid Phase Equilibria Calculations, Elsevier, 2010.
[3] Pedersen, K. S., Christensen, P. L., Phase behavior of petroleum reservoir fluids, Taylor &
Francis Group, Boca Raton, USA, 2007.
[4] Hassan S. Naji, Characterizing Pure and Undefined Petroleum Components, IJET-IJENS, Vol:10
No:02, 2010, pp 28–48.
[5] N.S. Bahvalov, N.P. Zhidkov, G.M. Kobelkov, Numerical methods, M. «Nauka», 1987 [in rus-
sian]
[6] Clayton V. Deutsch, Geostatistical Reservoir Modeling, Oxford University Press, 2002
[7] A. Bardossy Introduction to Geostatistics University of Stuttgart
[8] S. D. Conte, Carl de Boor Elementary Numerical Analysis McGraw-Hill Book Company, 1980.
[9] J-P Chiles, P. Delfinder Geostatistics Modeling Spatial Uncertainty Wiley & Sons, Canada, 1999.
33. References 278

tNavUserGuideDesignerEnglish PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

tNavUserGuideDesignerEnglish PDF

Hochgeladen von

Copyright:

Verfügbare Formate

18.

Geology & Model Designer

Rock Flow Dynamics

Press to open tNavigator Library

4. Geometry Objects. Calculations 26

6.4. Build Marker by Horizon . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

10. Core Sample Images 68

13. Seismic 108

14. Seismic Horizons 110

15. Polygons 114

16. Aquifers 120

17. Faults 122

18. Faulted Horizons 133

19. Point Sets 136

20. Tables 142

21. 3D-Grids. Model grids 143

21.13.Calculate Grid Geometry Properties . . . . . . . . . . . . . . . . . . . . . . 159

22. Grid Properties 161

23. Blocked Wells 193

24. Contacts 199

25. Fluid Properties 199

26. Wells Data. Tables 202

27. Wells Data. Strategies. Rules. Global 213

28. Wells Data. Rules. Wells 218

28.3.1. Economic Limits for Production Well . . . . . . . . . . . . . . . . . . 231

29. Wells Data. Rules. Groups 236

30. Wells Data. Rules. Other 243

31. Other data 245

32. Graphs 267

33. References 278

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

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

• Graphical User Interface.

The list of tNavigator documentation is available in tNavigator Library.

In this document the following modules are described:

• Geology Designer – building static model from scratch.

• Model Designer – pre-processor to build dynamic model.

Geology Designer, Model Designer allow to:

• Create static model from scratch using initial data;

• Load well trajectory, seismic surfaces, markers, faults, LOG data;

• Interpret seismic horizons;

• Perform well correlation;

• Build horizons and a model grid using different interpolation algorithms;

• Create phase relative permeabilities;

• Load wells events and historical data;

• Work in one graphical interface with static and dynamic data;

2.1. Designer project

• The Top menu (Document. View. Files. Reports. Queue);

• Top Panel Buttons;

• The Right panel buttons;

• Log Panel at the bottom of the project window.

Figure 1. Designer project window.

2.2. Top menu. Document. View. Files Reports. Queue

• Save. Save current project.

2.2. Top menu. Document. View. Files Reports. Queue 15

2.2. Top menu. Document. View. Files Reports. Queue 16

3. Menu Files. Project files are available for viewing here.

2.2. Top menu. Document. View. Files Reports. Queue 17

2.3. Import Data from Rescue File

• Grid coordinates Measure Units. Set the units for XY and Z;