2 Well Data Model

Contents

Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Wells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Sampling Styles (Interpolation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Set Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Set Constants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Set Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Well Header Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Audit Trail Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Reference Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Directional (Survey) Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Interval Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Log Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Log Versioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Log Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Parameter Size Limits and Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Database Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Geolog® 7 – Paradigm™ 2011 Well Data Model 2-1

With Epos® 4.1 Data Management
 Structure

The EPOS system is project oriented. Each project can be considered to consist of two parts, an application
directory and a well database. The application directory contains all files used or created by EPOS which
are not well databases (for example, contractor data files, plots, reports, layouts, etc.).
PROJECT
• Application Directory
• Well Database; basic components are:
— wells
— sets
 constants
 comments
 logs
A project can have any number of wells. A well contains a well header and any number of sets. The well
header is a special set which stores well constants and comments.
Sets are used to improve access and store different sampling rates. Sets contain groupings of related data.
They contain any number of constants, comments and logs. Each set has one reference log which defines
the reference domain and units for the logs in the set.
Fig. 1 provides a graphical representation:

Geolog® 7 – Paradigm™ 2011 Well Data Model 2-2

With Epos® 4.1 Data Management
 Project 1 Project 2 Project n
Project 1

Well 1 Well 2 Well n

Well 1

Set 1

Well Header Reference Wire Lith Core Tops Set n

Wire Set

Set Constants Set Comments Logs

Constant 1 Comment 1 Log 1

(Wireline) Logs

Reference log nphi rhob gr lld lls Log n

Fig. 1: Graphical representation of the well database

Geolog® 7 – Paradigm™ 2011 Well Data Model 2-3

With Epos® 4.1 Data Management
 Project

See the following sections for an in depth explanation of the Well Database components of a project, and
“Project Structure” on page 3-1 in the Environment documentation for detailed information on the
Application Directory.

Geolog® 7 – Paradigm™ 2011 Well Data Model 2-4

With Epos® 4.1 Data Management
 Wells

A well is created in a project when field data is loaded into the database. A well has a unique Primary Well
Identifier (PWI), such as well name or API number, which identifies it. A project you are working on can
have any number of wells, limited only by the amount of disk space available.

Geolog® 7 – Paradigm™ 2011 Well Data Model 2-5

With Epos® 4.1 Data Management
 Sets

Sets are groupings of related data and are named according to the kind of data they contain. There are
various naming conventions for sets and most are obvious. Wireline logs are stored in the Wire set,
lithological data in a set called Lith and so on.
• Each set has one reference log. This defines the reference domain and units for the logs in the
set. See "Reference Set" on page 2-10.
• A list of standard set names is provided in the file specs/setinfo.setinfo, which is site
configurable. This file also provides a priority or ordering for finding logs.

Sampling Styles (Interpolation)

A Set is determined by its interpolation (sampling).
The following is a description of the three sampling styles.
• Continuous
Connected data points at either regular (periodic) or irregular (aperiodic) spacing; interpolation
occurs between points.
— Periodic Data
Periodic logs can be grouped in any reasonable way, independent of the log sample rate; a
fast channel msfl can be stored together with other periodic logs, making the database
simpler from a data management perspective. The reference sampling is that of the finest
log in the set.
Sets extend in range automatically - for periodic sets, the range of the set is extended with
extra samples at the given sample rate extending to the new limits. When processing
periodic logs with different sampling rates, the finest sampling of the logs selected is used.
The range of data encompasses all the selected logs but no more.
— Aperiodic Data
See "Notes About Aperiodic Sets" on page 2-6.
• Tops
Constant data value between non-continuous points (aperiodic). See "Notes About Aperiodic
Sets" on page 2-6.
• Point
Random, unconnected data points (aperiodic). See "Notes About Aperiodic Sets" on page 2-6.

Notes About Aperiodic Sets

• Aperiodic sets have logs with identical sampling within the same domain.
• Sets extend in range automatically - for aperiodic sets, the set is modified to contain all the
sample points from the existing set together with those of the new logs.

Geolog® 7 – Paradigm™ 2011 Well Data Model 2-6

With Epos® 4.1 Data Management
Examples

Fig. 3 illustrates the three sampling styles.

Fig. 3 is a graphical representation of the sampling styles.
Fig. 4 highlights the differences between regular and irregular continuous.

Normal = continuous Histogram = tops Stick = point

Fig. 2: Sampling styles

Geolog® 7 – Paradigm™ 2011 Well Data Model 2-7

With Epos® 4.1 Data Management
 Irregular continuous and regular continuous are graphically the same Tops Point
(aperiodic) (aperiodic)

Fig. 3: Graphical examples of interpolation (sampling) styles - Fig. 4 shows the differences
between Continuous - irregular and regular sampling

Geolog® 7 – Paradigm™ 2011 Well Data Model 2-8

With Epos® 4.1 Data Management
 Data points every 0.1524 m Data points at random depths

Fig. 4: Continuous regular and irregular interval sampling.

Set Names
Identical names should not be used for both sets and expressions (e.g. functions, macros, curves, etc.).
Set names cannot be numerical. If numbers are used for the name, the letter "S" is appended to the
beginning of the name.

Set Constants
Set constants store set specific constant data (e.g. a well with multiple logging runs will have each run
stored in a different set with constants pertaining to the run). They have the following attributes:
• Name
• Type
• Value
• Units
• Comment

Geolog® 7 – Paradigm™ 2011 Well Data Model 2-9

With Epos® 4.1 Data Management
Type

Constants default to a type of "numeric" if they have an entry in the geolog<version>/specs/ loginfo
files (imperial.loginfo, metric.loginfo and mixed.loginfo) and that entry has a preferred unit
(on the basis that having a unit implies being a number). If these conditions are not met, the constant will
default to a type of "string".
The type also depends on how the constant is presented to the database. For instance, if a particular import
format presents a value as a "string" which the loginfo file indicates is a number, the database will attempt
to convert this to a number but if that fails, it will reset the type to "string".
Conversely, if the import format presents a value as a "number", then the database will set the type to
"numeric".

NOTE Caution is advised when importing data because many import formats do not have a data
type definition for a constant value, and there are cases where a value can look like a
number (e.g. API number or unique well ID) but should not be treated as a binary number.

Set Comments
Set comments store free format text and are set specific. They have the following attributes:
• Name
• Value

Well Header Set

The Well Header is a special set used for storing well related information. It contains well constants and
comments only, no logs.

Audit Trail Set

Any changes made to well database are recorded as Comments in the Audit Trail set – see “Audit Trail
Basics” on page 1-1 for more information.

Reference Set
A special set using the set name Reference may contain references from various domains to provide
translation between domains. The primary reference for the set is measured depth. The set is sampled at a
fairly coarse sample rate, such as one foot or half a meter and always starts at depth zero. When data is
loaded, the reference of this set automatically extends to cover the entire depth range of the well. This also
occurs via any action which extends the range of the well, e.g. evaluating new data.
The advantage of this set is that other sets only require one reference log, therefore references such as TVD
need not be duplicated in every set, preventing inconsistency and reducing work. References may be
duplicated in sets, if this is required, and set references will have precedence over those in the Reference set.

Geolog® 7 – Paradigm™ 2011 Well Data Model 2-10

With Epos® 4.1 Data Management
Features

• TVD and any other reference may extend from surface to below TD without having to extend
every log in the wireline set.
• Both periodic and aperiodic data can be interpolated or projected to any reference in the
Reference set provided the sets reference is present in the Reference set, making domain
translation clearer and simpler for the user.
• The depth range of the reference set is representative of the range of the well.

Directional (Survey) Set

A directional set contains raw deviation surveys. A deviation survey is used to calculate a wellpath in the
reference set.
The REFERENCE set is always considered to be TRUE NORTH, there are no set constants to indicate this.

NOTE There are no directional constants written into the WELL_HEADER.

Table 2-1: Mandatory Directional Set Constants

Constants Type Description
SURVEY_NAME Alpha Survey name.
CALC_METHOD Alpha Valid calculation methods are:
• Tangential
• Radius of Curvature
• Minimum Curvature
NORTH_REF Alpha Supported values are:
• True
• Grid
• Magnetic (Magnetic is not supported by OW)
Note: If NORTH_REF is not set the True is assumed.
Note: If NORTH_REF is set to Grid then at least the
EPOS_CRS must be set.
COORDINATE_SYS Alpha Set if NORTH_REF is set to Grid.
Third party original name.
GEODETIC_DATUM Alpha Set if NORTH_REF is set to Grid.
Third party original name.
MAP_PROJECTION Alpha Set if NORTH_REF is set to Grid.
Third party original name.
EPOS_CRS Alpha Set if NORTH_REF is set Grid.
Official Epos CS name.
CONV_FACTOR Double Set if NORTH_REF is Grid (not supported by OW).
CONV_ANGLE Double Set if NORTH_REF is Grid (not supported by OW).
MDEC Double Set if NORTH_REF is Magnetic (not supported by OW).

Geolog® 7 – Paradigm™ 2011 Well Data Model 2-11

With Epos® 4.1 Data Management
Interval Sets
Interval data is represented by aperiodic sets with a sampling style of “Tops”.
Each “Tops” set consists of a "Reference Set" on page 2-10 and an interval log. The interval log consists of
a sequence of interval names and the depths at which the intervals were entered from the reference set.
Intervals are referred to as “Tops” because the set is defined by assigning the interval name with the start
depth (or top) of that interval. The interval end is indicated by the start of the next interval or if the
intervals are not contiguous by an empty frame where the interval name is missing.
Interval names may be repeated in consecutive frames and they will be treated as a single interval. This
allows for the use of more than one interval log in a set (e.g. for hierarchical intervals).
Interval properties are delineated by the use of additional logs in the set. The properties are directly
associated with the appropriate interval by being defined at the same frame (reference depth) as the
interval it is associated with.

Geolog® 7 – Paradigm™ 2011 Well Data Model 2-12

With Epos® 4.1 Data Management
 Logs

Sets contain logs. The Wire set may contain Gamma Ray logs, Neutron Porosity logs etc. Each set has a
reference log. It defines the reference domain and units for logs in the set.

Log Names
Log names cannot be numerical. If numbers are used for the name, the letter "L" is appended to the
beginning of the name.

Log Versioning
Whenever a log is created, edited or modified, a new version of the log is created by appending a numeric
version number. <log>_1 is the original log version.
Version numbers are incremented by one to create a new log, for example, by curve editing while retaining
the original version. Referencing a log by name only, without a version, will access the latest version of the
log subject to log filtering. If multiple users are editing the same log, Geolog will save the edited logs as
different versions.

Log Priority
The file specs/setinfo.setinfo defines the order of priority of sets for finding logs. The order of priority
is:
• default set (when defined)
• setinfo set order
• latest version of a log
• alias order if the log is not present in the set
For example, a log to display is not in the default set, therefore find the log to display in the order defined
in setinfo.

Geolog® 7 – Paradigm™ 2011 Well Data Model 2-13

With Epos® 4.1 Data Management
 Parameter Size Limits and Naming Conventions

Table 2-2, "Parameter Size Limits and Naming Conventions" on page 2-14 defines the maximum length of
names for projects, wells, constants, etc and details the naming conventions for Project, Well and Constant
names.

Table 2-2: Parameter Size Limits and Naming Conventions

Item Max Length Naming Conventions
Project Name 64 Use only A-Z and/or a-z, 0-9 and underscore "_" characters in
a project name. Do not use spaces.
Note: Do not rename a project in the paradigm/projects
subdirectory.
Comment 72
Path 200
Well PWI 32 Use only A-Z, 0-9, underscore "_", dash "-" and forward slash
"/" characters in well names.
The following characters are invalid in a well name; space,
dot, parentheses, square brackets and single quotes — these
will be replaced by an underscore.
An exclamation mark will be presented as a forward slash.
Double quotes are ignored.
Note: Do not rename Wells in the paradigm/projects/
<project>/wells subdirectory.
Set Name 32
Log Name 32
Units 16
Userid 16
Comment 72
Text Value 72
Constant Name 32 The characters "-" and "/" are not supported in Constant
names. They will be replaced with an underscore "_".
Units 16
Comment 72
Text Value 72
Comment Name 32

Geolog® 7 – Paradigm™ 2011 Well Data Model 2-14

With Epos® 4.1 Data Management
 Data Types

The following data types can be used when defining data stored in the database. The range of values for
data types will depend on your workstation environment.

Table 2-3: Data Types

Data Type Description
REAL Float - 32 bit signed
DOUBLE Float - 64 bit signed
ALPHA Characters
INTEGER Integer- 32 bit signed
INT8 Integer - 8 bit signed
INT16 Integer - 16 bit signed
UINT8 Integer - 8 bit unsigned
UINT16 Integer - 16 bit unsigned
<type>*<size> Array type data

Geolog® 7 – Paradigm™ 2011 Well Data Model 2-15

With Epos® 4.1 Data Management
 Database Attributes

The following table lists the available attributes for projects, wells, sets and logs.

Table 2-4: Database Attributes

Type Attribute Description
PROJECT PROJECT Project name
PATH Project path
COMMENT Project comment
HOST Project host
TYPE Project type
DATASET Project dataset
OWNER Project owner
WELL WELL Well ID
DATE_MODIFIED Date/time modified
STATUS Status
PROJECT Project
INCLUDE_PROJECT Include project
SET SET Set name
LOG LOG Log name
NAME Log name
UNITS Log units
TYPE Log type
REPEAT Log data repeat
FRAMES Log frame count
COUNT Log non-missing count
START Log start of non-missing values
FINISH Log end of non-missing values
TOP Log reference top
BOTTOM Log reference bottom
SR Log reference sample rate
MIN Log minimum
MAX Log maximum
SUM Log sum of values
SUMSQR Log sum of values squared
SUMABS Log sum of absolute values
MEAN Log derived value - mean
STDDEV Log derived value - standard deviation
INCREASE Log increases monotonically
DECREASE Log decreases monotonically

Geolog® 7 – Paradigm™ 2011 Well Data Model 2-16

With Epos® 4.1 Data Management
 Table 2-4: Database Attributes
Type Attribute Description
Date Modified A date and time record of the last time the
log was modified.
When a well is copied from one project to
another, each logs date modified is copied
from the source project to the target
project.
Userid A record of which userid was used when
the log was last modified.
When a well is copied from one project to
another, the userid for each log is copied
from the source project to the target
project. Where userid fields are empty in
the source project, the userid used to
perform the copy will be used to populate
this field in the target project.
INTERPOLATION Log interpolation method
PROJECT Project log is from
COMMENT Log comment
SOURCE Log source
API_CODE API code
TOOL_ID Tool identifier
RUN_NO Run number
PASS_NO Pass number
LOGGED_DIRECTION Logging direction
CONTRACTOR Log contractor
KIND Log kind
AZIMUTH_TYPE Azimuth type

Geolog® 7 – Paradigm™ 2011 Well Data Model 2-17

With Epos® 4.1 Data Management
Index

A
audit trail
reserved set name 10

C
character limits
of names 13
comments
name, maximum length of 13
constants
comment, maximum length of 13
name, maximum length of 13
text value, maximum length of 13

D
data
types 14
Database
components 2
data types 14
interval set, description of 11
log versioning 12
project structure 2
reference set, description of 10
size limits for names 13
storage structure 2
well database diagram 2
well header set, description of 10
definition of
interpolation styles used in Geolog 6
sampling styles in Geolog 6
description of
interval set 11
reference set 10
well header set 10
wells in Geolog 5

I
interplolation styles used in Geolog 6

L
logs
comment, maximum length of 13
finding and order of priority of sets 12
name, maximum length of 13

Geolog® 7 – Paradigm™ 2011 Well Data Model 2-18

With Epos® 4.1 Data Management
 text value, maximum length of 13

N
names
length of 13

P
parameters
size limits for names 13
Project
comments, maximum length of 13
name, maximum length of 13
path, maximum length of 13
projects (Geolog working)
structure 2
PWI
name, maximum length of 13

R
reserved set names
audit trail 10
reference 10
well header 10

S
sampling styles, definition of Geolog 6
sets
interval, description of 11
name, maximum length of 13
order of priority of for finding logs 12
reference, description of 10
well header, description of 10
structure of
projects 2
well database 2

U
units
name, maximum length of 13
userid name, maximum length of 13

W
wells
database components 2
database diagram 2
description of Geolog 5
PWI, maximum length of 13

Geolog® 7 – Paradigm™ 2011 Well Data Model 2-19

With Epos® 4.1 Data Management