Importing, Exporting, and Linking

Importing, Exporting, and Linking

Copyright Notice

Copyright © 2017 Schlumberger. All rights reserved.

This work contains the confidential and proprietary trade secrets of Schlumberger and may not be copied or stored in an
information retrieval system, transferred, used, distributed, translated or retransmitted in any form or by any means,
electronic or mechanical, in whole or in part, without the express written permission of the copyright owner.

Trademarks & Service Marks

Schlumberger, the Schlumberger logotype, and other words or symbols used to identify Schlumberger, the Schlumberger
logotype, and other words or symbols used to identify the products and services described herein are either trademarks,
trade names or service marks of Schlumberger and its licensors, or are the property of their respective owners. These
marks may not be copied, imitated or used, in whole or in part, without the express prior written permission of
Schlumberger. In addition, covers, page headers, custom graphics, icons, and other design elements may be service
marks, trademarks, and/or trade dress of Schlumberger, and may not be copied, imitated, or used, in whole or in part,
without the express prior written permission of Schlumberger. Other company, product, and service names are the
properties of their respective owners.

OFM® is a mark of Schlumberger.

An asterisk (*) is used throughout this document to designate other marks of Schlumberger.

Security Notice

The software described herein is configured to operate with at least the minimum specifications set out by Schlumberger.
You are advised that such minimum specifications are merely recommendations and not intended to be limiting to
configurations that may be used to operate the software. Similarly, you are advised that the software should be operated
in a secure environment whether such software is operated across a network, on a single system and/or on a plurality of
systems. It is up to you to configure and maintain your networks and/or system(s) in a secure manner. If you have
further questions as to recommendations regarding recommended specifications or security, please feel free to contact
your local Schlumberger representative.

1 of 164
Importing, Exporting, and Linking

Definitions for File Extensions

The following table lists file extensions related to your OFM projects. These extensions are the OFM defaults
used when opening or saving project data. The table lists the syntax and file types and gives a brief
description of each. Follow the links for details about each of the file types.

Extension File Type Description See Also

.ano Map Annotation ASCII files containing information such as n Map Annotation
rivers or lease and state lines. You can add Data Guidelines
these to the base map to improve the
n Importing Data
presentation.
into New or
Existing Projects

n Performing Sweep
Calculations:
Saving
streamlines, flood
lines, and pattern
boundaries

n Viewing and
Changing
Wellbore Diagram
Symbols
.bpf Batch Project File ASCII file used for scheduled batch updates n Exporting Project
of project data. This is an advanced feature. Text Load Files

n Copying Forecasts
in Cases
.bub Bubble Map A template file for bubble maps. n Importing and
Exporting
Analyses and
Nodes
.cnl Contour This contour file is similar to the .cnt file, n About Map
except that it contains the necessary Annotations
parameters for color, line type, width, and
other features.
.cnt CPS-3 Contour This file display contour data in black and n About Map
white, with solid contour lines and numbers. Annotations
.cs Color Scale A non-ASCII file that can: n Changing the
Colors on
n Set the appearance of the color scale
Analytical Maps
legend on a bubble, grid, or contour map

n Customize the color palette

2 of 164
Importing, Exporting, and Linking

You can save this file in one map and open it

in another.
.dat Table Data ASCII files that contain data for loading to n Exporting Project
data tables. The *Tablename keyword Text Load Files
within the file identifies the correct table
n Exporting Project
into which the data will be loaded.
Table Data
.dca Decline Curve Analysis ASCII file containing the monthly forecast n Importing Data
Forecast data for one or more entities. into New or
Existing Projects

n Copying Forecasts
in Cases
.def Definition When loaded, this ASCII file creates the n Definition File
structure of one or more tables in the Guidelines
database.
n Exporting Project
OFM requires a project definition file when Table Definitions
you create a new project from ASCII files. At
n Exporting Project
any time, you can use a smaller definition
Text Load Files
file to add new tables to the project.
n Importing Data
into New or
Existing Projects
.dev Deviation Data ASCII file containing deviation data for n Deviation Data
loading to the OFM project. Guidelines

OFM uses deviation data for: n Importing Data

into New or
n Calculating measured depth versus true
Existing Projects
vertical depth
n Exporting Project
n Displaying wells on the base map and in
Text Load Files
mapper files at the surface, bottomhole,
or a selected point along the deviation n Exporting Project
survey Table Data

.dly Daily Data ASCII file containing date-dependent data n Daily Data
(such as daily tests) recorded daily. Guidelines

This is an optional file extension. The same n Importing Data

file could also have a file extension such as into New or
.dat or .txt as long as the *Tablename Existing Projects
keyword within the file identifies the correct
n Exporting Project
table.
Text Load Files

n Exporting Project
Table Data
.flt Fault Data ASCII file containing fault data. Fault data n Fault Data
includes information about the fault Guidelines

3 of 164
Importing, Exporting, and Linking

attributes (such as depth and throw). n Importing Data

into New or
Use fault data files to load:
Existing Projects
n Geological fault data
n Exporting Project
n Time-variant fault data Text Load Files

n Multiple sets of fault data n Exporting Project

Table Data
You can export this file from an OFM project,
and import it into a project.
.ga Grid Area Files ASCII file that defines a grid area used to n Defining the Grid
limit the extent of a grid map or contour Area
map.
n Calculating the
You can create and save this file from an Grid Area
OFM grid map, and you can open it and
apply it to another grid map.
.gcp Grid Control Point File containing control points added to grid n Adding Artificial
and contour maps. You can open this file in Data Points to the
other grid and contour maps and in surface Map
maps.
.gh Graph Header A template file that describes the header for n Saving and
maps and forecasts. This may include: Loading Header
Files on the Base
n Text title
Map
n Calculated variables or formulas
n Adding Project
n Entity name Variables and
System Function
n Current date
for Database
You can create and save this file from an Information Text
OFM plot, and you can open and apply it to Boxes
another plot.
.grd Grid A template file for a grid, surface, or contour n Saving a Forecast
map; or forecast. It is required for grid map to a Different Case
arithmetic.
n Creating Grid
You can save this file from a grid map in one Arithmetic
OFM project and open it in another project Calculations
to grid the same variable with the same
n Importing and
settings.
Exporting
Analyses and
Nodes
.grf Graph A template file for a plot or forecast. n Saving and
Applying Forecast
You can save this file in one OFM project and
Formats
open it in another project to plot the same

4 of 164
Importing, Exporting, and Linking

variables with the same settings. This is one n Importing and

of the ways to share plot formats between Exporting
projects. Analyses and
Nodes
.hly Hourly Data ASCII file containing date-dependent data n Exporting Project
recorded hourly. Text Load Files

n Exporting Project
Table Data
.il Info Line Template file for customized information n Adding Custom
displayed on the Well Info pane. This may Information to
include: the Well Info Pane

n Calculated variables showing the latest n Saving and

values of rates Loading a Well
Annotations File
n Cumulative volumes

n Ratios

You can create and save this file in one OFM

project and open it in another project.
.ini Setup File n Exporting the
Project Variables
to a Table
.inj Injection Data ASCII file typically containing date- n Importing Data
dependent monthly injection data. into New or
Existing Projects
This is an optional file extension. The same
file could also have a file extension such as
.dat or .txt as long as the *Tablename
keyword within the file identifies the correct
table.
.las LAS Log Format Industry-standard ASCII file containing log
data. You cannot load this file into OFM.

To convert an LAS file to a format that you

can load into OFM, use the LAS to OFM
utility. This utility is in the OFMPlus directory
(installed with OFM).
.lgv Log File A template file for single well log displays. n Importing and
Exporting
Analyses and
Nodes
.lku Lookup Data ASCII file containing lookup table data. n Lookup Data
Guidelines
This is an optional file extension. The same
file could also have a file extension such as n Importing Data
.dat or .txt as long as the *Tablename into New or

5 of 164
Importing, Exporting, and Linking

keyword within the file identifies the correct Existing Projects

table.
n Exporting Project
Lookup data can: Text Load Files

n Change over time, and be used as a n Exporting Project

reference (such as tax rates or oil price) Table Data

n Change with other values, like pressure

(such as PVT data)

Lookup tables store the values of properties

that do not have to be related to a
completion.
.loc Location File containing the location of the bubbles n Moving Bubbles or
on a bubble map, or the plots on a map XY Plots and Saving
plot. Their Location
.log Trace data Depth-dependent data that records a value n Importing Data
at each depth interval for each trace and into New or
each wellbore. Existing Projects

n Exporting Project
Text Load Files

n Exporting Project
Table Data
.mdb Microsoft Access Database which holds some or all of your n Overview of
project data. Workspaces
.min Minute Data ASCII file containing date-dependent data n Exporting Project
recorded by the minute. Text Load Files

n Exporting Project
Table Data
.mrk Marker Data ASCII file containing marker data. n Marker Data
Guidelines
n Marker names are user-defined, depth-
dependent data that record a value at a n Importing Data
given depth, for each wellbore. Examples into New or
of this data are formation tops and fluid Existing Projects
levels. n Exporting Project
n You can use marker data to load Text Load Files
geological data. n Exporting Project
Table Data
You can export this file from an OFM project,
and import it into a project.
.mwl Multi-Well Log A template file for multi-well log displays. n Importing and
Exporting
Analyses and
Nodes

6 of 164
Importing, Exporting, and Linking

.ofm OFM Workspace A text file in XML format, which stores the n Overview of
attributes of all your analyses. This file Workspaces
contains no data; it only contains
information about how you want to view
the data.
.par Parser Data ASCII file containing user-defined, n Parser File
calculated variables that use equations to Guidelines
perform calculations on input variables or
n Exporting Project
other calculated variables.
Calculated
This file can be exported from, or imported Variables
into, an OFM project.
n Exporting Project
Text Load Files

n Importing Data
into New or
Existing Projects
.pat Pattern Data ASCII file containing waterflood pattern n Importing Data
configurations. into New or
Existing Projects
The data includes:
n Exporting Project
n Pattern set name
Table Data
n Pattern names
n Performing Sweep
n Wells belonging to each pattern Calculations:
Exporting
n Allocation factors
patterns
n Start dates, if applicable
n Pattern Tutorial:
This file can be exported from, or imported To Create
into, an OFM project. Patterns From an
ASCII File
.prd Monthly Production ASCII file typically containing date- n Importing Data
dependent monthly production data. into New or
Existing Projects
This is an optional file extension. The same
file could also have a file extension such as n Exporting Project
.dat or .txt as long as the *Tablename Text Load Files
keyword within the file identifies the correct
n Exporting Project
table.
Table Data
You can export this file from an OFM project,
and import it into a project.
.pvt PVT Data Non-ASCII file containing PVT correlation n Sharing PVT
data. Entities

You can open and save this file on the PVT

Data window.

7 of 164
Importing, Exporting, and Linking

.qry Query You can use this file when filtering with an n Filtering with an
OFM query. OFM Query
.rh Report Header A template file that describes the header for n Working with
reports. This may include: Report Headers
and Footers
n Text title

n Calculated variables or formulas

n Entity name

n Current date

You can create and save this file from an

OFM report, and open and apply it to
another report.
.rpt Report A template file for a report. n Creating and
Using Report
You can save this file in one OFM project and
Templates
open it in another project to report the
same variables with the same settings. This
is one of the ways to share report formats
between projects.

Reports can contain:

n Calculated variables

n Input data taken directly from a database

n Calculations defined interactively

.sec Second Data ASCII file containing date-dependent data n Exporting Project
recorded by the second. Text Load Files

n Exporting Project
Table Data
.set Scatter Plot Set ASCII file containing one or more sets of n Creating Scatter
completions and the characteristics for the Plot Sets
set.

OFM uses these files when color-coding

completions or other entities in scatter
plots. You can create them:

n Outside of OFM

n Interactively within the Scatter Plots

module

n Saved from the Filter pane

.spf Scatter Plot A template file for scatter plots. n Importing and
Exporting

8 of 164
Importing, Exporting, and Linking

Analyses and
Nodes
.srt Sort Data ASCII file that defines: n Importing Data
into New or
n Entity-dependent data
Existing Projects
n Sort categories in OFM (such as the
operator, field name, and PVT region)

You can use sort categories to create

subsets of data in any meaningful group for
analysis.

This is an optional file extension. The same

file could also have a file extension such as
.dat or .txt as long as the *Tablename
keyword within the file identifies the correct
table.

You can export this file from an OFM project,

and import it into a project.
.sym Well Symbols ASCII file that defines the color and symbol n Editing Well
used to represent completions on the base Symbols
map.
n Importing Data
Usually the symbols show well type or into New or
status. However, you can use other data to Existing Projects
dictate symbols by setting the base map's
map association.

You can save this file from the base map of

one OFM project and open it in another
project.
.wbd Wellbore Diagram There are two different types of files with n Importing Data
this extension. into New or
and
Existing Projects
Wellbore Diagram:
Wellbore Data
A template file for a wellbore diagram
display.

You can save this file from one OFM project

and open it in another project to create the
diagram for a different set of wells using the
same display format.

Wellbore Data:

ASCII file containing wellbore data for

loading to the OFM project. This data can
include descriptions of:

9 of 164
Importing, Exporting, and Linking

n Casing and tubing strings

n Perfs

n Other equipment in the wellbore

.wbt Wellbore Diagram A template file for wellbore diagrams. n Importing and
Template Exporting
Analyses and
Nodes

n Using and Saving

Wellbore Diagram
Templates
.xrf Cross-Reference Data ASCII file containing data for loading to a n Cross-Reference
cross-reference table in an OFM project. Data Guidelines

You can export this file from an OFM project, n Exporting Project
and import it into a project. Text Load Files
.xsc Cross-Section Template file for a cross-section display. It is n Importing and
wellbore specific. That is, the template Exporting
includes the wellbore selection used to Analyses and
create it. Nodes

You can save this file from an existing cross-

section display in an OFM project and reopen
it in the same project.
.xy Keydata ASCII file for loading data to the master n Exporting Project
table. Each record in this file describes a Table Data
unique entity (usually a completion) in the
n Exporting Project
OFM project.
Text Load Files

n Importing Data
into New or
Existing Projects

10 of 164
Importing, Exporting, and Linking

About Loading Data into Projects

You can create an OFM project using ASCII data files, Dwights PCD information, or PI98 fixed format files.

After you create a definition file and data files for your project, you can add new data to your project's
database:

n Data

n PI/Dwights production files

n FrontSim bundle and allocation information

OFM adds new data to the existing database and updates any data that has changed. OFM updates the
database based on date, name, and input variables.

Note: If you created the database in a version earlier than OFM 3.1 and used any template other than
Production Analyst, you cannot update the database using Petroleum Information/Dwights LLC data. You
must create a new database in a temporary directory using the updated data, and save the temporary load
files. Then, delete the new database and use the temporary load files to update the existing database. If
you plan to use Petroleum Information/Dwights LLC data to update a database, you can never delete a
field originally specified in the template.

The process is the same as for a new project, except the definition file is no longer needed and only ASCII
files containing the new or modified data are selected and loaded.

Note: To prevent overwriting or corrupting existing data, do not reload previously-loaded definition files.

Related Topics
About Linking to External Data

11 of 164
Importing, Exporting, and Linking

Importing Data into New or Existing Projects

You can load defined and non-defined data into new and existing projects, such as the file types listed in
the following table.

You can load this type See this topic for

of data... guidelines...
Guidelines for Loading
Daily data (.dly)
Daily Data
Definition (.def)
Guidelines for Loading
Deviation data (.dev)
Deviation Data
Guidelines for Loading
Fault data (.flt)
Fault Data
Forecast (.dca)
Hourly (.hly)
Injection data (.inj)
KeyData (.xy)
Guidelines for Loading
Lookup data (.lku)
Lookup Data
Guidelines for Loading
Map annotations (.ano)
Annotation Data
Guidelines for Loading
Marker data (.mrk)
Marker Data
Minute (.min)
Guidelines for Loading
Monthly production (.prd)
Monthly Data
Parser data (.par) Parser File Guidelines
Guidelines for Loading
Pattern data (.pat)
Pattern Data
Second (.sec)
Sort data (.srt)
Guidelines for Loading
Trace data (.log)
Trace Data
Wellbore diagram and Guidelines for Loading
wellbore data (.wbd) Wellbore Diagram Data
Guidelines for Loading
Well symbols (.sym)
Well Symbols

1. On the Setup tab, in the Import/Export group, select Import > Data Loader.
The OFM Data Loader window opens.

12 of 164
Importing, Exporting, and Linking

2. From the file list, select the files with the data you want to import into your project.

3. Click Add.
The file location displays in the Files to Load section. If the file has an extension that OFM
recognizes, the Data Type field automatically displays the type of data in the file you selected. If the
file has an extension that OFM does not recognize, the Data Type field displays DATA by default.

4. Select the Show Results check box.

5. Click Load.
The OFM Data Loader window closes.

You can now view your data on the base map.

Related Tutorials and Examples

Patterns: To Create Patterns From an ASCII File

Displaying Formation or Reservoir Thickness and Structure: Getting Started

Using .Las Log Data: Loading the Log and Definition Files into the OFM Project

Related Topics
Overview of OFM Data

Exporting Project Text Load Files

13 of 164
Importing, Exporting, and Linking

Loading PI/Dwights Production Files

You can import PI/Dwights (DMP2 or 298) production files into new and existing projects.

1. On the Setup tab, in the Import/Export group, select Import > PI/Dwights DMP2 Loader or
PI/Dwights 298 File Loader.
The PI/Dwights Production File Loader window opens.

2. Select the PI/Dwights file and then click Open.

The PI/D Import wizard opens. The wizard has five panels.

3. On the Selecting well name convention panel, select the following and then click Next.

a. How you want OFM to create your well names.

n We recommend selecting Prod ID (for DMP2 files) or PI/D Unique Identifier (for 298 files),
because you will have unique well names for all cases.

n To use a previously saved cross-reference file, select Cross-reference table and then click
Browse to select the .xrf file.

b. Whether to delete the temporary load files.

n OFM produces the temporary load files. Do not delete them if you want to see the contents of
the temporary load files, or if you will use them to create other projects.

4. On the Selecting wells panel:

n If you want to create a cross-reference table now, click Create X-ref. On the Save As window,
enter the name of your new cross-reference table and click Save.

n Select the wells you want to import and click Next.

5. On the Selecting sort categories panel, choose the fields you want to use as sort categories. If
you need to view more information about any of the sort categories listed, select the item or click
Details. When you have selected the sort categories, click Next.

6. On the Selecting well test data panel, select the test data you want to import. If you need to view
more information about any of the listed test data, select the item and click Details. When you have
selected the test data, click Next.

7. On the Selecting monthly data panel, select the monthly data you want to include. If you need to
view more information about the monthly data, click Details. When you have selected the test data,
click Finish to load the data.

Related Topics
Defining a Workspace from PI/Dwights Production Files

14 of 164
Importing, Exporting, and Linking

Loading FrontSim Bundle and Allocation

Information
Follow these steps to load files containing the FrontSim bundle and allocation information.

1. On the Setup tab, in the Import/Export group, select Import > FrontSim Patterns.

2. Select the FrontSim allocation (.txt) file and then click Open.
The Import Patterns From FrontSim window opens.

3. In the Import Which Bundles (Patterns) section, select Injector Centered, Producer
Centered, or Both.
FrontSim exports both Injector Centered and Producer Centered patterns to the allocation file.

4. Select the pattern type (or both) to import to OFM.

5. In the OFM Pattern Settings section, enter the OFM pattern Set Name.

6. Enter the desired date in the Date of First Time Step field.
This date corresponds to the first time step found in the FrontSim file. Each following time step
causes the date to increase by the number of days read from the file.

7. FrontSim reports wells as sequential numbers. Click the FrontSim Wellname field and select the
OFM name.
This action associates this field with a field in the Master XY table. When loading, OFM will translate
the FrontSim well name (number) to an OFM unique well identifier using the associated field.

8. In the Injectant Loss field, enter the desired numeric value. This number is used to reduce the
total amount of injectant produced by the production wells in the pattern.

Note: Selecting the Display Import Status Messages check box causes import status messages to
appear on the status window. By default, OFM selects this check box.

9. Click Load.

15 of 164
Importing, Exporting, and Linking

Saving and Loading a Well Symbols File

Follow these steps to save well symbols as a symbol (.sym) file, and load it in another project.

1. With the base map displayed, on the Format tab, in the Edit group, click Symbols.

2. Save or load the file:

n To save: Click Save File, enter a name for your file, and then click Save.

n To load: Click Get File, select the symbol (.sym) file, and then click Open.

3. Click OK.

Related Topics
Guidelines for Loading Well Symbols

16 of 164
Importing, Exporting, and Linking

About Exporting Data

You can export the data used in your OFM project from the Setup tab:

n Save calculated variables as a parser (.par) file

n Save project table definitions as a definition (.def) file

n Export project table data: The key (.xy) file, user-defined tables such as monthly production (.prd) or
pattern (.pat) files, and OFM-defined tables such as OFM_DATA_Marker

n Copy project tables from one OFM database to another

n Export project data and then automatically open the new project after it is created

n Export calculations to another data source as a setup (.ini) file

n Export data to Eclipse or Petrel, such as production/injection data, deviation surveys, and well event
data

17 of 164
Importing, Exporting, and Linking

Exporting Project Calculated Variables

When you export calculated variables, you create a parser file. This text file contains the expression and
attributes of each calculated variable that you export.

Export calculated variables if you wish to:

n Save the variables independently from your workspace

n Import them into other OFM workspaces

n Create a standard set of calculations for use by others in their workspaces

1. On the Setup tab, in the Import/Export group, select Export > Selected Text Load File(s) >
Calculated Variables.
The Export Calculated Variables window opens.

2. Click the browse (...) button to the right of the File field.

3. Enter a File name, select a location to store the saved file, and then click OK.

4. (Optional) If you have assigned user or class attributes to your calculated variables, you may filter
the exported variables by user and/or class. Select the User and Class from the lists.

5. Click OK.
OFM saves the calculated files in a parser (.par) file.

Related Topics
Parser File Guidelines

Importing Data into New or Existing Projects

Related Keyword
*Parser (Parser) Keyword

18 of 164
Importing, Exporting, and Linking

Exporting Project Table Definitions

Follow these steps to save OFM project definition files.

1. On the Setup tab, in the Import/Export group, select Export > Selected Text Load File(s) >
Table Definitions.

2. Enter the table definitions File Name and select a location to store the definition (.def) file.

3. Click Save.
OFM saves the table definitions in a definition (.def) file.

Related Topics
About the Project Definition (project.def) File

Definition File Guidelines

19 of 164
Importing, Exporting, and Linking

Exporting Project Tables

Follow these steps to copy project tables from one OFM database to another.

1. On the Setup tab, in the Import/Export group, select Export > Selected Database Tables.
The Table Data window opens.

2. In the OFM Table(s) to Copy From section, select the tables you want to copy.

3. In the Database to Copy Table(s) To section:

a. Click Select.

b. Select the database (.mdb) file and then click OK.

4. Click OK.

20 of 164
Importing, Exporting, and Linking

Exporting Project Text Load Files

Follow these steps to export project data. If you wish, you can automatically create a new project with the
exported files.

1. On the Setup tab, in the Import/Export group, select Export > All Text Load Files.
The Export Project Files window opens.

2. Enter a name for your project load files, and click Browse to select a new location.

3. To use the exported data to create a new project, select Use exported data to create a new
project.

4. Click OK.
OFM exports the data into text files in the folder you selected. If you selected Use exported data
to create a new project, OFM creates the new project and opens it.

21 of 164
Importing, Exporting, and Linking

Exporting Project Table Data

Follow these steps to export the keydata (.xy) file, user-defined tables such as monthly production (.prd) or
pattern (.pat) files, and OFM-defined tables such as OFM_DATA_Marker.

1. On the Setup tab, in the Import/Export group, select Export > Selected Text Load File(s)
Table Data.
The Table to Export window opens.

2. Select the name of the table you want to export and click OK.

3. Enter the table name in the File Name field, select a location to store the file, and then click Save.

22 of 164
Importing, Exporting, and Linking

Exporting the Project Variables to a Table

Follow these steps to export calculations to another data source.

To Export to a Setup File

1. On the Setup tab, in the Import/Export group, select Export > Export Variables to Table.
The Table Export Wizard opens.

2. Select Setup a new export and then click Next.

3. Select a Target Table from the list field.

4. For each Column in Target Table, map an OFM Variable.

5. Click Next.

n (Optional) The Begin Stored Procedure field enables you to prepare the data.

n (Optional) The End Stored Procedure field enables you to decide what happens to the data
after it is exported.

6. Click Next.

7. To set up another table to export, click Yes and then repeat the steps above. To continue, click No.

8. Click Save Setup.

9. Enter a name for the setup (.ini) file and then click Save.

10. Click Finish.

To Open a Saved Setup File

1. On the Setup tab, in the Import/Export group, select Export > Export Variables to Table.
The Table Export Wizard displays.

2. Select Open a saved setup and click File.

3. Select the setup (.ini) file and then click Open.

4. Make any needed changes or click Finish.

23 of 164
Importing, Exporting, and Linking

Exporting to Petrel or Eclipse

You can export production/injection data, deviation surveys, and well event data to Eclipse or Petrel. The
exported ASCII files have a format suitable for direct import into Schedule. Schedule is a separate module
that loads data into Eclipse.

1. On the Setup tab, in the Import/Export group, select Export > Selected Text Load File(s) >
To Petrel or Eclipse.
The Export to Petrel or Eclipse window opens.

2. On the Setup tab:

a. To use the well alias for the well name, select Use Well Alias for Well Name.

b. Click Output File Prefix, enter a name for the export file, and then click Save.
A list of output file names display on the Setup tab. By default, OFM selects all the choices.

c. Select the items you want to export. You must clear either the monthly or the daily selections.

Note: OFM selects all the choices by default. Clear any you do not want to export. Do not select both
monthly and daily options. One option type overwrites the other because they are stored in the same file
(.vol).

3. On the Well Position & Trajectory tab:

a. On the X Loc and Y Loc fields, select the correct variables to associate with the X- and Y-axis.

b. In the Coordinate Units section, select a unit of measure or specify a different unit of measure
by selecting the Other radio button.

4. On the Monthly Production tab, select the correct variables to associate with producing Days, Oil
Volume, Gas Volume, and the Water Volume injection rate.

5. On the Monthly Injection tab, select the correct variables to associate with the Gas Injection
and Water Injection days and rate.

6. On the Daily Production tab, select the correct variables to associate with Hours On (producing
days), and for oil, gas, and water volume.

7. On the Daily Injection tab, select the correct variables to associate with Gas Injection and
Water Injection days and rate.

8. On the Events tab, select the correct variables to associate with the well date.

9. Click OK.

Related Topics
Exporting Wellbore Diagram Data to Petrel

24 of 164
Importing, Exporting, and Linking

Exporting Wellbore Diagram Data to Petrel

If your project has wellbore diagrams, you can export the information about well casing and tubing,
packers, chokes, and inflow control devices to Petrel or Eclipse. The file you save is a tubing (.tub) file. This
is an ASCII file that has the information for the wellbore diagrams you have created (per wellbore).

Note: Not all well equipment that can be contained in an OFM workspace can be exported to Petrel. Export
is limited to well casing and tubing, packers, chokes, and inflow control devices. In addition, well equipment
contained in an OFM workspace may not conform to the Petrel well model. If this happens, when you
import the .tub file into Petrel then Petrel rejects the exported equipment that does not conform to the
Petrel well model.

n Casing definition:

n The top depth point of the casing

n Internal diameter and roughness, starting at the measured depth

n Bottom measured depth for the casing

n Tubing definition:

n Top depth of the tubing

n Internal diameter and roughness

n External diameter and roughness

n Measured depth where the tubing stops

n Packer location (measured depth)

n Inflow valve location (measured depth)

1. On the Navigation pane, select Wellbores.

2. On the Setup tab, in the Import/Export group, click Export > Well Configurations to Petrel.

3. Enter a name for the tubing (.tub) file and then click Save.

To import the tubing (.tub) file into Petrel, view the Petrel online help and search for importing well tubing
data.

Related Topics
Overview of Wellbore Diagrams

Exporting to Petrel or Eclipse

25 of 164
Importing, Exporting, and Linking

About Linking to External Data

You can link to one or more data sources. The data sources may or may not be on your computer. The OFM
Home data source stores saved forecasts, log data, deviation surveys, and more.

You also can link to other applications.

26 of 164
Importing, Exporting, and Linking

The Edit Schema Tables Window

You can use the Edit Schema Tables window to change your project's structure:

n For data sources: Add and remove data sources

n For tables in data sources: Add and remove tables, enable and disable them, and set attributes
such as table type and date ranges

n For the fields in tables: Add and remove fields; enable and disable them; and set attributes such
as math options, units of measurement, and how the data displays in plots and reports

The Edit Schema Tables window has two parts:

n OFM Representation pane on the left lists all the enabled tables and fields.

n Tabs on the right provide information about the item you selected in the OFM Representation
pane. The tabs vary depending on your selection.

Note: The level you select in the tree on the OFM Representation pane controls the information that will
display on the right side of the Edit Schema Tables window.

The following table defines the icons, used in the OFM Representation pane, and the tabs that display
when you select different items.

Icons Actions You Can Take Tabs that Display Actions You Can Take
on the Pane When You Select the on the Tab
Icon
Workspace None Tables: Lists all tables None
(your tables and shared
This is the top level of
tables) in the project
your project.
My Workspace or Add a table Tables: Lists the tables Link to databases and
Shared Workspace in the your personal spreadsheets
workspace, or in the
This is the top level of the
shared workspace
workspace. Inside the
workspace are all the
enabled tables.
Home Data Source Change the home data Tables: Lists the tables Enable and disable tables
source in the database or
Each workspace can have
spreadsheet.
only one home source. Limit the number of
entities to display for a If you select the check
Database or
SQL query box, OFM automatically
Spreadsheet
loads the tables when you
Data sources for your open your project.
project, which are not the

27 of 164
Importing, Exporting, and Linking

home data source.

Master Table Add a calculated field Master: Displays the n Change the table type,
table name, table keys, key type, and cross-
Every OFM project must and key delimiters reference key
have a master table. This
table stores static well n View keys and

information. delimiters

Fields: Displays a list of Add fields to the table

fields in the table.

If you select the check

box, OFM automatically
loads the fields when you
open your project.
Table n Add a calculated field Table: Displays the table Change the table type,
name, type, and key type key type, and cross-
Inside the table are all the n Rename a table
reference key
enabled fields. n Delete a table
Fields: Displays a list of n Add fields to the table
fields in the table.
n Enable and disable
If you select the check fields in the table
box, OFM automatically
loads the fields when you
open your project.
Date Range: Displays if Set date ranges for tables
the table has a date range with time-dependent
data
Primary Key Field n Add a field Field: Displays the table, View field source and

Field field names, variable type variables

n Add a calculated field
and size
The tabs that display n Rename a field
Units: Displays Change the units of
when you select a field
n Delete a field selections for units of measurement for the
depend on the type of
measurement field label
data the field contains.
Math: Displays math Set all math options for
Calculated Field options, such as carrying the field
forward, multipliers,
grouping by sum or

28 of 164
Importing, Exporting, and Linking

average, and using data

attributes when
importing data

Report: Displays Format the field data in

formatting choices for reports
your reports, including
width, text justification
on the page, use of upper
and lower-case letters,
and headings
Plot: Displays the name Format the field data in
of your curve, and how plots
you want the curve line
to display.

29 of 164
Importing, Exporting, and Linking

Linking to a Data Source

You can link to any of the following types of data sources:

n Microsoft® Excel spreadsheet

n Microsoft Access® database

n Microsoft OLE DB data sources

n Microsoft SQL Server® database

n Oracle® database

1. On the Setup tab, in the Tables group, click Schema.

The Edit Schema Tables window opens.

2. On the OFM Representation pane, right-click My Workspace and then click Add.
The Data Source window opens.

3. Enter the Name you want to give the database.

If the data is in Access:

a. Select Microsoft Access Database File in the Type field.

b. Click Browse in the File field and select the file you want to use.

If the data is in Excel:

a. Select Microsoft Excel File in the Type field.

b. Click Browse in the File field and select the file you want to use.

If the data is in an OLEDB data source:

a. Select Microsoft OLEDB Data Source in the Type field.

A dialog box opens, confirming your selection. When you link to OLEDB sources, you must have
an understanding of the provider.

b. Click Yes.
The Data Link Properties window opens.

c. Enter information about the provider, and then click OK.

Note: If this data source requires a password, OFM does not store the password. You will enter the
password every time you access the data source.

If the data is in SQL Server:

30 of 164
Importing, Exporting, and Linking

a. Select Microsoft SQL Server in the Type field.

b. Click Browse in the Server field.

The Server field populates with a list of available servers.

c. Select the correct server.

d. Click Browse in the Database field.

The Database field populates with a list of available databases.

e. Select the correct database.

If the data is in Oracle:

a. Select Oracle Database in the Type field.

b. Click Browse in the TNS field and select the TNS you want to use.

c. In the Log On section, select a method for authentication (gaining permission to access the
database).

4. Click Test Connection to make sure OFM can connect to the data source with the information you
entered.

5. Click OK to close the Data Source window.

The Tables tab on the Edit Schema Tables window lists the tables in your data source. The table
is available, but is not enabled.

6. For each table you want to enable:

a. Select the check box to the left of one of the tables.

The Add an Existing Table to the Project dialog confirms that you want to enable the table.

b. Click Yes.

c. On the Table tab, in the OFM Definition group, select a table type (the type of data in the
table).
The Auto-associate Fields dialog lists the fields OFM identified as the key associations.

d. If the key associations are correct, click Yes. If they are not correct, click No and select a
different table type on the Table tab.

7. Repeat the steps to link to more data sources, if needed.

Related Topics
The Edit Schema Tables Window

Defining SQL Settings

Spreadsheet Guidelines

31 of 164
Importing, Exporting, and Linking

Linking to Other Applications

About Using OFM Expressions as Arguments
<OFM>@loadname()</OFM>

OFM evaluates all text between the OFM tags. The tags and expression will be replaced by the result, as
calculated by OFM. OFM expressions can be combined with static text.

Note: When you use this feature, include leading and trailing spaces as needed. These instructions are run
via a command line, and so you must use the proper syntax.

1. On the Analysis pane, right-click My Analysis and then select New > Linked Application.
The Link Application window opens.

2. On the Target field, enter a target or click Browse and then select the application or file associated
with the application.

3. (Optional) On the Arguments field, enter command-line arguments. These can include static text
and OFM expressions that can be evaluated at runtime.

4. Click OK.
OFM displays the link on the Analysis pane. By default, the name is Exe App.

5. To rename the link:

a. On the Analysis pane, right-click the link and then click Rename.

b. Type a new name and then press Enter.

3. To use the link, on the Analysis pane, double-click the link.

4. To change an existing link:

a. On the Analysis pane, click the link.

The Property pane displays the target and arguments.

b. Make changes on the Target or Arguments fields.

Examples
n Linking to a search engine

In this example, the expression adds a link to do a search for the current lease. If the target is an
http address, then OFM removes all white space from the command and arguments.

Target: http://www.google.com

Argument: >/OFM<sc.lease>OFM<q=&/search?hl=en

n Linking to open the project database

32 of 164
Importing, Exporting, and Linking

In this example, the expression adds a link to open the current project database using Microsoft
Access. Double quotes are placed on either side of the OFM expression, since the return value of
@ProjectPath() may contains spaces in the path, which Access would misinterpret as multiple
command line arguments.

Target: D:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE

Argument: "<OFM>@ProjectPath()</OFM>"

n Linking to a spreadsheet

In this example, the expression adds a link to an Excel worksheet.

Target: D:\My Project\My Worksheet.xls

n Linking to send an email

In this example, the expression adds a link to send your manager an email about the well you are
examining in OFM. If the target is mailto, then OFM removes all white space from the command
and arguments.

Target: mailto:[email protected]?subject=

Argument:  About well: <OFM>@name()</OFM>

Related Topics
Adding Comments and Viewing Properties for Analyses

33 of 164
Importing, Exporting, and Linking

Spreadsheet Guidelines
If you have issues linking to spreadsheets, it is usually because of spreadsheet formatting. Follow these
guidelines to make sure the link works correctly:

n Worksheet names: Name the worksheet with the name you want OFM to use for your table. The
worksheet name is the default name for the table in OFM.

n Row 1: Use the first row of the worksheet to name your columns. These will be the field names in
OFM.

n Do not use spaces in the column names. For example, if a column in your worksheet is for oil
volumes, name the column Oil_Volume.

n Do not put units of measurement in the column names. OFM does not interpret units of
measurement based on the name; units are determined within the workspace. For example, do
not name a column Oil_Volume_m3.

n Row 2: The cells in this row may have numbers or text. For columns that hold numbers, the cells in
Row 2 must have numeric data. For columns that hold text, the cells in Row 2 can be blank. If data is
missing in any numeric cell on this row, enter the OFM default null value in it. The default null value
is -99999.

n Empty rows: Do not have any empty rows. You can have cells with no data (in any row except Row
2), but you cannot have a row in which all rows are empty. OFM interprets an empty row as the end
of the data.

n Type of data in worksheets: Keep similar data on the same worksheet. Each worksheet in your
spreadsheet creates a separate table in OFM. You cannot merge worksheets. For example, if you
have data for two wells in two different worksheets, OFM will create two tables.

n Type of data in columns: Do not mix data types in a single column. Every column should have
one (and only one) type of data. For example do not have numbers, text, and dates or times in a
single column. Do not have "N/A" (text) in a column of numbers.

n Formatting, comments, and merged cells: Do not format any of your cells. Excel passes
formatting information to OFM as data.

n Embedded graphs: Do not have graphs embedded in your worksheet.

34 of 164
Importing, Exporting, and Linking

Overview of OFM Data

OFM uses relational databases to analyze and display data. Databases store data in linked tables. The tables
look similar to spreadsheets in Microsoft® Excel.

Types of Data
In OFM projects, all data can be categorized into one of three categories. There are three types of data in
OFM projects:

n User-defined: With this data, you must set up a table in the definition file or through the Edit
Schema Tables window, with associated keyword variables, units, and attributes.

n OFM-defined: Data that do not require a table to be set up in the definition file, and are created by
OFM. To manage the OFM-defined tables, use the OFM Defined Table Manager.

n Reference: Data that OFM references. You do not load this data, but you can change it. For
example, reference data include units of measurement, equations for data conversion, and
multipliers.

OFM-Defined Data Tables

Warning: Do not change the name or structure of these tables.

These tables have the prefix OFM_Data_. OFM stores defined data in a definition file that associates
keynames, variables, and variable attributes to each table. You must define this data before loading it.

Examples of OFM-defined data tables are:

n Tables with an OFM_DATA_DCA_ prefix. These tables hold decline curve analysis data, which OFM
produces in the forecasts module.

n OFM_DATA_Deviation

n OFM_DATA_Fault

n OFM_DATA_Log

n OFM_DATA_Marker

n OFM_DATA_

n OFM_DATA_PATTERN

n Tables with an OFM_DATA_WBD prefix. These tables hold wellbore diagram data.

35 of 164
Importing, Exporting, and Linking

Managing OFM-Defined Tables

To manage the OFM-defined tables, use the OFM Defined Table Manager.

OFM-defined tables are tables starting with _OFM_DATA_. They consist of decline analysis, deviation, fault,
log, marker, pattern, PVT, and wellbore diagram tables. For these tables, you can switch between a Shared
Workspace and My Workspace.

n If you point to an OFM-defined table in a Shared Workspace, then it is read-only in My Workspace.

n If you have a Shared Workspace, but you point to an OFM-defined table in My Workspace, then you
can read and write to the table. Use the Edit Schema Tables window to make changes to the OFM-
defined tables in My Workspace.

n If you have a standalone OFM project, you can make changes to your project's OFM-defined tables.

1. On the Setup tab, in the Tables group, click OFM-Defined.

2. Select My Workspace or the Shared Workspace for each of the OFM-defined tables.

3. Click OK.

Related Topics
Overview of OFM Data

Overview of Workspaces

36 of 164
Importing, Exporting, and Linking

Overview of OFM-Defined Data Types

Data is OFM-defined if OFM makes a special use of the data. Although you can load this data into OFM,
usually OFM can populate this data itself when you use special data editors or through analyses. For
example, you can create wellbore diagram data with the editors in the wellbore diagram analysis. You can
create forecast data in the forecast analysis.

For this type of data... If you load it... Or you can create the data
when you are...
Deviation data n Use this file extension: .dev Working with Faults

Depth-dependent data that shows n Follow the guidelines for loading

the deviation in a wellbore from deviation data
the surface location
Fault data n Use this file extension: .flt

Data on the depth and throw fault n Follow the guidelines for loading
attributes fault data
Marker data n Use this file extension: .mrk Working with Markers

Depth-dependent data recording a n Follow the guidelines for loading

value at a given depth, for each marker data
wellbore (such as formation tops
and fluid levels)
Pattern data n Use this file extension: .pat Creating Patterns

Data used to identify a group of n Follow the guidelines for loading

entities that form a relationship, pattern data
and the extent to which they
relate
Wellbore data n Use this file extension: .wbd Creating Wellbore Diagrams

Wellbore diagram data which list n Follow the guidelines for loading
equipment downhole, and events wellbore data
such as treatments
Forecast data n Use this file extension: .dca

Inputs to, and results from, OFM

forecast analyses
PVT data n Use this file extension: .pvt Creating or Changing PVT Entities

PVT configurations for the

workspace and/or various entities
in the workspace

Related Topics

37 of 164
Importing, Exporting, and Linking

Exporting Project Table Data

38 of 164
Importing, Exporting, and Linking

Entering and Changing Table Data

You can add and change the data in your tables. To do so, you first select the table you want to modify. The
table opens, and you can use the tools on the Format tab to make your changes.

1. Select a table to edit:

a. The completions that display in the table you select will be the ones in the current filter. Filter to
the completions you want to see.

b. On the Setup tab, in the Tables group, click Data Grid.

The Select OFM Table to Edit window opens.

c. Select a table from the list.

d. If the number of records in the table exceeds the limit you identified on the Edit Schema
Tables window, and you want to display all the records, select Edit all records.

e. Click OK.

f. If the number of records in the table exceeds the limit you defined, and you did not select the
Edit all records check box, a message displays. If you want the table to display all the records,
click No on the message. If you want the table to display select records, click Yes on the
message and then select the specific records.

2. To change data, click in the cell and then enter the new information.

3. To add a row of data to the table:

a. On the Format tab, in the Display group, click Last Record to move to the last row.

b. On the last row type the new information.

4. The Unique ID is always the first column, but OFM hides it. To show it, hover your mouse over the
first column line in the header row (the line to the left of the name of the first column). When the
cursor changes to show two arrows, double-click.

5. To find a specific record:

a. On the Format tab, in the Edit group, click Find.

b. Type the word you want to find and then click Find Next.

c. If you want to find each instance of that word with the Find window closed, close the window.
On the Format tab, in the Edit group, click Find Next.

5. To find a specific word and replace it with a different word:

a. On the Format tab, in the Edit group, click Replace.

b. Enter the word you want to find, and the word you want to replace it with, and then click
Replace or Replace All.

39 of 164
Importing, Exporting, and Linking

6. To navigate through the list, on the Format tab, in the Display group, click First Record,
Previous Record, Next Record, or Last Record.

7. To sort the data:

a. Click in the column by which you want to sort.

b. On the Format tab, in the Display group, click Sort to sort alphabetically (A-Z).

c. To reverse it (sort alphabetically Z-A), click Sort again.

8. To change the font and font size for all the text in the table, on the Format tab, in the Edit group,
click Font.

9. To make the display larger or smaller, on the Format tab, in the Zoom group, click Zoom In, Zoom
Out, or Zoom To Fit.

10. To resize the columns:

a. On the column header, drag the line that marks the column edge.

b. To change the column widths to the default sizes, on the Format tab, in the Display group,
click Default Column Widths.

11. To change the query that OFM used:

a. On the Format tab, in the Utilities group, click Advanced Query.

b. Enter a new SQL query and then click OK.

12. You can save the table of data as a text (.txt) file. On the Format tab, in the Utilities group, click
Save As File.

13. If you want to open another table:

a. On the Format tab, in the Utilities group, click Open.

b. Select the table you want to open and then click OK.

14. When you are finished, close the tab.

Related Tutorials and Examples

Well Deliverability Analysis: To View Test Data

Flow After Flow Test: To Enter Test Data

PVT: To Create a PVT Entity for Each Fluid

PVT: To Map Completions to their PVT Entity

Patterns: To Edit Patterns

Creating Plots for Waterflooding: Adding Stock Tank Oil Initially in Place to the Workspace

40 of 164
Importing, Exporting, and Linking

Related Topics
Mapping Completions to PVT Entities

41 of 164
Importing, Exporting, and Linking

Guidelines for Loading Cross-Reference

Data
Cross-reference data relates a key field to one or more other fields. The key field can refer to the completion
name, wellbore name, a category value, or any other entity name. The other fields may be either text or
numeric.

Cross-reference tables are similar to Lookup tables. OFM can access numeric or alpha contents of a multi-
column table if you define it as a cross-reference table. You can tie both cross-reference and lookup tables
to a variable other than the primary key. Cross-reference tables require two parameters; lookup tables
provide a value based on one parameter.

Use of Data
Use cross-reference data when you want a simple way to get back a numeric or string value for a
completion, wellbore, category value, or other key which OFM can create at runtime.

Example: You would like to assign some properties to leases. You can create a cross-reference table
named LEASEDATA that looks like this:

Lease Size CumOil

BERRINGER BIG 1.2e7
HENDERSON SMALL 2000

Within OFM, you could get back the size of the lease for a specified completion using this: @xrefalpha(
sc.lease, LEASEDATA.Size )

See the descriptions of tasks (below) for more details.

Tasks
You can perform the following tasks:

n Edit the data interactively or use an ASCII file to load them

n Define the table names, variable names, and attributes of cross-reference data

n Use the following system functions to access cross-reference data:

@XrefValue (expression,XRefTable.keyword)

@XrefAlpha (expression,XRefTable.keyword)

Where:

n Expression is either numeric or alpha and is selected from the first column of the table.

n Keyword identifies the column that XRefValue (a numeric value) or XRefAlpha (an alpha string)
will reference in the same row of the table as the expression.

42 of 164
Importing, Exporting, and Linking

Guidelines
This is an example of an ASCII cross-reference data file that you could load into OFM:

*tablename pat XRef

pattern string 10

parea float

stooip double

*pattern *parea *stooip

3503 81.09 9999783.30
3512 79.14 9270101.05
3524 93.90 10009775.09
3537 65.00 6915005.99
3541 79.25 9824745.00

Key Types
n Entity: Name of the entity, at any level

Reserved Keywords
*TableName: Required

43 of 164
Importing, Exporting, and Linking

Guidelines for Loading Daily Data

Date-dependent data may be recorded daily. In this case, a daily table is most suitable.

Use of Data
Daily data tables contain data such as:

n Flow rates and pressures recorded every day

n Offshore data, such as daily weather and sea conditions

Tasks
You can perform the following tasks:

n Edit the data interactively or use an ASCII file to load the daily data.

n Define the table names, variable names, and attributes of daily data.

n OFM assumes a value of null for any date skipped in the data file. Use the data range keyword *DA to
specify a default value for skipped data. Use a sporadic table when many data values are missing.

Guidelines
n You define the table names and variables.

n Data is date-dependent. You can edit it interactively, and you can load it at the entity level.

n You can load pre-cumulative values or adjustments to cumulatives by using zeros for the day in the
date.

n You can use the *DA (Data Attributes) keyword to specify another default value for skipped data. By
default, OFM assumes a value of null for data on any date skipped in the data file.

n *Data is the keyword in a batch data load file.

n The *Date column is implied. Do not define it in the definition file.

Key Types
n Entity: Name of the entity

n Date: Daily date

Reserved Keywords
n *Tablename: Required

n *Date: Required

44 of 164
Importing, Exporting, and Linking

n *KeyName: Required unless you specify the name of the entity key field, and you specify the entity
key name in every row of data supplied. This keyword requires a unique entity name followed by all
data associated with it.

n *Metric: Must appear above *Tablename to signal that the data is recorded in metric units

n *Null n: Where n is the null user-defined value, and where it appears before *Tablename. OFM
automatically interprets any non-alpha or numeric character as null (such as *, #, $).

n *Skip

45 of 164
Importing, Exporting, and Linking

Guidelines for Loading Deviation Data

Deviation data is OFM-defined data that shows deviation in a wellbore from the surface location along the
depth of the well.

Use of Data
OFM uses deviation data for calculating measured depth versus true vertical depth and for displaying wells
on maps at the surface, bottomhole, or at points along the deviation survey.

The data begins with the surface location at zero from the values loaded to the X- and Y- coordinates in the
Master static table.

Tasks
You can edit the data interactively or load the deviation data if it is in an ASCII file.

Guidelines
Deviation data is loaded to the wellbore level. The following is a portion of an example ASCII load file:

*TableName Dev

*Md *TVD *XDelt *YDelt

// ft ft None None

*KeyName "GREEN_14"

0. 0. 0. 0.

0.000000 0.000000 0.000000 0.000000

7450.000000 7445.000000 -138.000000 -122.000000

8253.000000 8243.000000 -223.679993 -134.539993

9560.000000 9468.000000 -613.000000 -296.720001

11130.000000 10730.000000 -1507.589966 -554.229980

12773.000000 11762.000000 -2755.870117 -765.919983

*KeyName "GREEN_17"

0. 0. 0. 0.

0.000000 0.000000 0.000000 0.000000

8000.000000 7995.000000 -110.000000 -107.000000

8991.000000 8971.000000 -67.000000 8.000000

9606.000000 9531.000000 43.000000 234.000000

10053.000000 9921.000000 155.000000 421.000000

46 of 164
Importing, Exporting, and Linking

11302.000000 11046.000000 600.000000 1021.000000

Key Types
n Entity: Name of the wellbore

n Depth: Measured depth

Reserved Keywords
Keywords for deviation data are unique and must be used exactly as they appear. OFM recognizes absolute
deviation coordinates. For this type of file, replace *XDelt and *YDelt with *XCoord and *YCoord.

n *Depth: Required

n *XCoord (Absolute X-coordinate): Required unless you use *XDelt

n *YCoord (Absolute X-coordinate): Required unless you use *YDelt

n *XDelt (Relative from surface): Required unless you use *XCoord

n *YDelt (Relative from surface): Required unless you use *YCoord

n *TVD (Reference depths relative to sea level): Required

n *KeyName: Required

n *Metric

n *KeyLength

Related Topics
Using Well Deviation Data

Adding Deviation Views (to wellbore diagrams)

47 of 164
Importing, Exporting, and Linking

Guidelines for Loading Fault Data

Fault data is OFM-defined data that contains information about the fault attributes, such as depth and
throw. After you load the ASCII data file, OFM stores the fault data in the project database.

Use of Data
Use fault data files to load geological fault data, time-variant fault data, and multiple sets of fault data.

Tasks
You can edit the data interactively or use an ASCII file to load the fault data.

Guidelines
n A project can have a maximum of 30 fault names.

n When entering key names, use the entire key name including the completion identifier.

n *.Flt is the keyword in a batch data load file, and it is the recommended file extension.

This is a portion of an example fault ASCII load file:

*TableName Fault

*Name *Depth *Throw *Azimuth *Type

*KeyName "BLUE_14"

"AA" 5500.000000 50.000000 15.000000 "unknown"

"BB" 6000.000000 100.000000 15.000000 "unknown"

*KeyName "BLUE_17"

"AA" 5500.000000 50.000000 15.000000 "unknown"

"BB" 6000.000000 100.000000 15.000000 "unknown"

Key Types
n Keyname: Name of the wellbore

n Name: Name of the fault, as a text string

Reserved Keywords
n *Keyname: Required; the name of the wellbore containing faults

n *Name: Required; the column containing the fault name

n *Depth: Required; the depth at which the fault occurs

48 of 164
Importing, Exporting, and Linking

n *Throw: Required; length of the fault

n *Azimuth: For information only; not used by OFM in fault display

n *Type: For information only; not used by OFM in fault display

n *Metric

49 of 164
Importing, Exporting, and Linking

Guidelines for Loading Lookup Data

Lookup data is user-defined data that allows dependent values to be obtained from an independent value
on an entity basis. With lookup tables, you can interpolate between known values.

Use of Data
The following are examples of values you can add to lookup tables:

n Compressibilities

n Date-dependent

n Depth-dependent

n Formation volume factors

n Oil and gas prices

n Pressure profiles

n Relative permeability data

n Viscosities

Tasks
You can perform the following tasks:

n Edit the data interactively or use an ASCII file to load the lookup data

n Define the table names, variable names, and attributes

Guidelines
This is a portion of an example lookup ASCII load file that would allow oil prices to be retrieved by date:

*TableName PRICES

*DATE *OIL

*Keyname BERRINGER

19500101 20.000000

19600101 25.000000

19700101 30.000000

19800101 35.000000

19900101 40.000000

19990101 50.000000

*Keyname TRAMMEL

50 of 164
Importing, Exporting, and Linking

19500101 20.500000

19550101 22.500000

19600101 25.500000

19700101 30.500000

19800101 35.500000

19900101 40.500000

19990101 45.500000

This is a portion of an example lookup ASCII load file that would allow a value to be retrieved based on
pressure:

*TABLENAME Value_data

*Pressure *P_value

*keyname BERRINGER

1000 200

2000 400

3000 600

4000 800

*keyname TRAMMEL

1000 500

2000 600

3000 700

Key Types
n Keyname: Name of the entity

n Primary Key: Numeric value

Reserved Keywords
n *Tablename: Required

n *KeyName: Required; this keyword can be an entity, a category, or a wellbore

n *Date: Required for date-dependent data

51 of 164
Importing, Exporting, and Linking

Guidelines for Loading Annotation Data

Map annotation data contains information (such as lease and state lines) you add to the base map to
improve presentation. OFM reads the file and displays the map annotation when it draws the base map.
OFM also uses annotation data to draw well symbols and the symbols on wellbore diagrams.

Use of Data
Create map annotations, well symbols, and the symbols on wellbore diagram sketches with ASCII
annotation files that have draw commands and modifiers.

Tasks
You can edit the data interactively or load an ASCII file with map annotation data.

Guidelines
If your base map appears with a concentration of data in two corners, it is because of well spots and map
annotation coordinates of different systems or an extreme range of differences between them.

Note: OFM can also display CPS contour files as map annotations.

The following table defines the draw commands used to create annotation data.

Draw Command Description

Modifiers
Map
MAP x1 y1 x2 y2 Map

Places an invisible boundary around the points (x1,y1) and (x2,y2) to define the
initial display area for the base map.

Note: The Map command must be the first command in a file.

M x1 y1 Move

Positions the pen without drawing to point (x1,y1).

Line
D x1 y1 Draw

Draws a line segment from the current position to the point (x1,y1).
L x1 y1 x2 y2 Line

Draws a line from point (x1,y1) to point (x2,y2).

LW n Line Width

Defines all lines after this command as n standard line-widths thick. This command
persists until the next Line Width command. The default is 1 standard line width.

52 of 164
Importing, Exporting, and Linking

LT n Line Type

Defines all the line styles that follow as the type represented by the code n, until the
next Line Type command. The available line types are:

n 1: Solid

n 2: Long dashed

n 3: Dotted

n 4: Dashed dotted

n 5: Medium dashed
Point
P x1 y1 Point

Creates a point at (x1,y1).

PT n Point Type

Defines all points that follow as the type represented by n until the next Point Type
command, where n=1 through 34.
PS Point Size

Defines all points that follow with the size defined by n until the next Point Size
command.
Shapes
B x1 y1 x2 y2 Box

Creates a box using point (x1,y1) as the lower-left corner and point (x2,y2) as the
upper-right corner.
ARC x1 y1 D S E Arc

Draws an arc or circle from the starting position (S) to the ending position (E) with a
radius (D), and the center at (x1,y1) where S and E are in degrees and D is in map
units.

To draw a circle, start at 0 and end at 360.

>MMCLVL Polyline

Defines all polylines that follow as the polyline represented by the string, until the
next >MMCLVL string when it begins drawing a new polyline. Each line following the
string must be in the following format:

xCoordinate yCoordinate zValue. ny

Other text on the line is ignored.

Text
T x1 y1 Text String

Creates a string of alphanumeric characters defined by a string of text at point

(x1,y1). The maximum string length is 60 characters. Use the underscore character
for spaces.

53 of 164
Importing, Exporting, and Linking

Fn Font

Selects a font type for text strings that follow. The available fonts are:

n 0: Standard (default)

n 2: Times New Roman

n 3: Times New Roman, bold face

Sn Text Size

Defines the font size in points. By default this is 6 point font size.
TH n Text Height

Assigns a number n in map units for the text height.

An Text Angle

Assigns an angle (in degrees above or below a horizontal line) to the text strings that
follow. For example, 90 makes the text vertical.
Jn Text Justification

Justifies the text strings in relation to the set of coordinates in the Text String
command. The available values are:

n 0: Left

n 1: Center

n 2: Right
Color and Fill
Cn Color

Defines all line colors and text that follow as the color represented by the code
number n, until the next Color command. Colors available are:

n 0: White

n 1: Black

n 2: Red

n 3: Green

n 4: Blue

n 5: Yellow

n 6: Magenta

n 7: Cyan
OC n Outline Color

Defines all fill outline colors and text that follow as the color represented by the code
number n, until encountering another Outline Color command. Colors available are:

n 0: White

54 of 164
Importing, Exporting, and Linking

n 1: Black

n 2: Red

n 3: Green

n 4: Blue

n 5: Yellow

n 6: Magenta

n 7: Cyan
Li n Fill

Defines a solid fill for polygons that follow. Defines all fill patterns that follow as the
color represented by the code number n, until encountering another Fill command.
Patterns available are:

n 0: Hollow

n 1: Solid

n 2: Hatch

n 3: Pattern

Related Examples
Adding New Well Symbols

Related Topics
Adding Map Annotations by Importing a CPS File

Changing OFM's Default Colors

55 of 164
Importing, Exporting, and Linking

Guidelines for Loading Marker Data

Marker data is OFM-defined data that is depth-dependent data, recording a value at a given depth for each
wellbore (such as formation tops and fluid levels).

Use of Data
Markers describe known geological features, such as formation tops. Once defined, you can show cross-
sections that align well logs to common markers. You can define intervals between a top and bottom
marker so that you can display lithological regions. You can create log reports to show average properties
between markers.

Tasks
You can edit the data interactively or use an ASCII file to load the marker data.

Guidelines
n The keyname must be matched to the wellbore name.

n *Depth is required.

Key Types
n Keyname: Name of the wellbore

n Name: Name of the marker

n Depth: Depth of the marker

Reserved Keywords
n *Depth: Required

n *KeyName: Required

n *Name: Required

n *Date

n *Picker

n *Metric

n *Null

56 of 164
Importing, Exporting, and Linking

Guidelines for Loading Monthly Data

Monthly data is user-defined data. It is date-dependent data, such as monthly production volumes. It has
no more than one record for each month, for each entity.

Use of Data
Monthly data may consist of the following information:

n Number of days on production

n Gas, oil, and water production

n Gas and water injection

n Pressure data

Tasks
You can perform the following tasks:

n Edit the data interactively or use an ASCII file to load the monthly data

n Define the table names, variable names, and attributes

n Specify when in the month OFM should plot and report data (such as at the beginning, middle, or end
of the month)

Guidelines
n The Date field is added automatically for monthly tables, and is not defined in the definition file.

n You can use the *DA (Data Attributes) keyword to specify another default value for skipped data. By
default, OFM assumes a value of null for data on any date skipped in the data file.

Key Types
n Entity: Name of the entity

n Date: A date describing the year and month for the data

Reserved Keywords
n *Tablename: Required

n *Date: Required

57 of 164
Importing, Exporting, and Linking

n *KeyName: Required unless you specify the name of the entity key field, and you specify the entity
key name in every row of data supplied. This keyword requires a unique entity name followed by all
data associated with it.

n *Metric: Must appear above *Tablename, to signal that the data is recorded in metric units.

n *Null n: Where n is the null user-defined value, and where it appears before *Tablename. OFM
automatically interprets any non-alpha or numeric character as null (such as *, #, $).

n *Skip

58 of 164
Importing, Exporting, and Linking

Guidelines for Loading Pattern Data

Pattern data is OFM-defined data that defines the relationships of certain producing wells with other
injection wells in a field (such as water injection, CO2 injection, and steam injection). Over time, a
response is experienced in the producing wells as a result of the fluid injected into the corresponding
injection wells.

Use of Data
Pattern data consists of well names with allocation factors for assigning a fraction of either injected volume
to a group of producing wells or the other way around, which assigns a percentage of production to a group
of injectors. Many types of patterns exist for evaluation, such as:

n Injecting water to carry oil through the rock pore space or produce the combined oil and water out of
another well

n Steam injection to the center of a group of producers that produce the heated, less viscous oil from
the perimeter wells

A typical five-spot pattern consists of four injectors in a square around a single producer.

Tasks
You can edit the data interactively or use an ASCII file to load the pattern data.

Guidelines
n Predefined definitions of variables assigned to pattern data are *KeyName, *Factor, and *Loss. By
including *Date, you can specify changes in pattern allocation factors over time.

Note: Use the *loss keyword to adjust the produced fluids for any loss of injected volumes in the reservoir.

n You can adjust time-dependent patterns up to 20 times.

n Pattern names can have no more than 20 characters.

n You can specify four different sets of patterns for each database.

n *Pattern is the keyword in a batch data load file.

n OFM applies allocation factors to any input variable that has the "multiply by factor" math property
assigned.

Key Types
n PatternSet: Name of the pattern set, as a string

n PatternName: Name of the pattern, as a text string

59 of 164
Importing, Exporting, and Linking

n Date: Date

n Well: Name of the completion

Reserved Keywords
n *set: Required; pattern set name

n *well: Required; well name

n *factor: Required; pattern allocation factor

n *loss: Used to adjust the produced fluids for any loss of injected volumes in the reservoir

Related Tutorials
Patterns: To Create Patterns Interactively

Patterns: To Create Patterns From an ASCII File

Related Topics
Performing Sweep Calculations

60 of 164
Importing, Exporting, and Linking

Guidelines for Loading Sporadic Data

Sporadic data is user-defined data. It is unevenly distributed, time-dependent data. Unlike daily and
monthly data, the sequence in sporadic data is not continuous.

Use of Data
Sporadic tables could include the following information:

n Well-flow test data

n Buildup data

n Drawdown data

n Interference test data

Tasks
You can perform the following tasks:

n Edit the data interactively or load the sporadic data if it is in an ASCII file

n Define the table names, variable names, and attributes

Guidelines
n You must define primary and secondary (if used) keywords in the definition file.

n Usually, *Date is a primary keyword. A primary key is required and may be (for example) *Date or
*Depth.

n If a secondary keyword is necessary, include the *Dualkey keyword at the top of the sporadic data
file, below the table name and above both the primary and secondary keywords.

n *Data is the keyword in a batch data load file.

Key Types
n Entity: Name of the entity

n Primary Key: Numeric value or date

n Secondary Key: Numeric value

Reserved Keywords
n *TableName: Required

n *KeyName: Required

61 of 164
Importing, Exporting, and Linking

n *Metric

n *Null

n *Skip

62 of 164
Importing, Exporting, and Linking

Guidelines for Loading Static Data

Static data is user-defined data. This data has well information that does not change with time. For
example, static data can be:

n Location

n Completion date

n Initial pressure

n Total depth

n Perforations

n Porosity

n Initial rate and pressure

n Drilling cost

Use of Data
Use static data for:

n Any data that does not change with time

n Well location, total depth, and API number

n Porosity

n Initial reservoir pressure

n Water-saturation values

n X- and Y-coordinates

Tasks
You can perform the following tasks:

n Edit the data interactively or use an ASCII file to load the static data

n Define the table names, variable names, and attributes

Guidelines
n The first keyword of this table identifies the primary key used for the table.

n The words GROUP <category> must follow the table name in the definition file if static data applies
to a level other than completion. For example, a static table for wellbore-level data is defined like
this:
*TableName hello Static Group Wellbore

63 of 164
Importing, Exporting, and Linking

Key Types
n Entity: Name of the completion or foreign key

Reserved Keywords
n *Tablename: Required

n *Null

n *Metric

n *Skip

64 of 164
Importing, Exporting, and Linking

Guidelines for Loading Trace Data

Traces are data that contain well logs.

Use of Data
An example of trace data is information gathered from open-hole and cased-hole logging surveys.

Tasks
You can use an ASCII file to load trace data.

Caution: When you load .log files, OFM overwrites previously loaded files if they use the same well name
and trace name, even if the intervals or depth ranges are different.

Guidelines: Trace Data

*TableName Log trace should be used, followed by a name and variable type for every well log.

Guidelines: ASCII Data

n Depth values should be positive values measured from the reference depth.

n To time-stamp logs, use the *Date keyword.

n *KeyName is the identifier used to identify the wellbore containing the well logs.

n You should use scientific notation or standard numbers for all log values.

n You cannot interactively edit log data. You must change data by loading a new ASCII file.

n Enter an asterisk or null value for missing log values at depths.

Key Types
n Entity: Name of the entity

n Name: Name of the trace, as a text string

n Date: Date

Reserved Keywords
n *Tablename: Required

n *KeyName: Required

n *Depth: Required

n *Metric

65 of 164
Importing, Exporting, and Linking

n *Null

n *Date

n *Start

n *End

n *Inc

n *Skip

Related Examples
Using .Las Log Data

Related Topics
Overview of Well Log Displays

66 of 164
Importing, Exporting, and Linking

Guidelines for Loading Well Symbols

This is a data file that specifies the list of well symbols and their attributes. Well symbols display locations
on the base map.

Tasks
You can load this data.

Guidelines
n The first column of data contains the "short name" for the well symbol.

n The second column contains the "long name" for the symbol.

n The third column specifies the number of the symbol annotation file used to draw the symbol.
Symbol annotation files are in the OFM Symbols directory.

n The fourth column specifies the color of the well symbol.

This is an example of a well symbol file:

*clear

CINJ Carbon_Dioxide_Injector 18 1

CO2PRD Carbon_Dioxide_Producer 19 1

SCYCL Cyclic_Steam 28 1

DISCV Discovery_Well 32 1

DRY Dry_Hole 2 1

GINJ Gas_Injector 73 2

GAS Gas_Producer 5 2

GEOTH Geothermal_Producer 30 1

*eof

Reserved Keywords
n *clear: Resets the current set of well symbols

n *EOF: Tells OFM to stop reading the file

Related Examples

67 of 164
Importing, Exporting, and Linking

Adding New Well Symbols

68 of 164
Importing, Exporting, and Linking

Guidelines for Loading Wellbore Diagram

Data
Wellbore data contains historical equipment configurations, and a description of stimulated, troubled, and
cored intervals.

Use of Data
OFM uses the data in:

n The wellbore diagram module: To display wellbore configurations

n The well log display and log cross section modules: To present wellbore diagrams and cross sections,
and to indicate perforated intervals on log traces

Tasks
You can create wellbore diagrams in the Wellbore Diagram module, or use ASCII files to load them with the
Data Loader.

Key Types
n Wellbore

n Data

There are many keywords that describe wellbore information, tubular descriptions, equipment,
completions, and layout of the diagram.

69 of 164
Importing, Exporting, and Linking

Overview of Keywords
There are three categories of keywords in the OFM-defined data tables:

n General

n Time

n Wellbore

Many keywords are used in input files to control the import of data. Keywords apply to a single data file, and
forward from the point in the file where they appear. Keywords applicable to a table should appear after the
*Tablename keyword. In the context of reading ASCII files, OFM uses keywords to control input and define
the attributes of data and variables.

Time Keywords
OFM expects dates specified as yyyymmdd (for example, it expects 20101231 for December 31, 2010).
When data is used in another format, or split into two or more columns, the time keywords provide a
method to input dates.

As OFM has no special data type for time, a time value (such as 2100 for 9:00 PM) must be entered and
must be consistent with the data type specified in the definition file.

70 of 164
Importing, Exporting, and Linking

Overview of General Keywords

This Does this...
keyword...
*DA Data Attributes

Controls data attributes

*Data Data File

Denotes a file containing user-defined data to be

loaded as part of a batch load file
*Date Date

Denotes a column that contains a date

*DateLabel Date Label

Changes the label that OFM displays by default, and

expects the keyword for the date in monthly and
daily tables
*Depth Depth

Specifies the measured depth in the wellbore

*DualKey Dual Key

In sporadic data load files, indicates a dual-date load

level
*End End Depth

Specifies the maximum depth for which log data is

loaded
*End_ End Format
Format
Defines the end of the format block (which starts
with the *Format keyword)
*EOF End of File

Indicates the end of the file

*Factor Factor

Specifies the fraction of well production/injection

allocated to a pattern
*Format Format

Defines the beginning of the format block (which

ends with the *End_Format keyword)
*Inc Increment

Defines the increment of footage at which trace data

is recorded

71 of 164
Importing, Exporting, and Linking

*KeyLength Key Length

Sets the maximum number of characters that OFM

reads in a keyword, and then that number is used to
match with defined and reserved keywords
*KeyName Key Name

Designates a value of the master key

*Loadby Method of Loading

Provides an additional method for loading data to a

level other than the completion level
*Loss Loss

Specifies a loss factor

*MA Aggregation Options

Defines the way that data is grouped for more than

one well, and allows you to use pattern or other
factors to apply to values as they are read from the
data source
*Map Map Association

In a definition file, denotes the variables to be

mapped to various OFM association types
*Metric Metric

Specifies that data following this keyword is in metric

units rather than English or scientific units
*MU Multiplier

Indicates that the input data is a specified multiple of

the unit type, and specifies the multiple of the unit
type to use for output
*Null Null

Specifies a number to consider as null (instead of no

value or zero)
*PA Plot Attributes

Specifies the plot attributes for a variable

*Parser Parser

Denotes a file containing calculated variable data to

be loaded as part of a batch load file
*Pattern Pattern

Denotes the pattern for which the data that follows

is loaded
*PN Plot Name

72 of 164
Importing, Exporting, and Linking

Denotes the name of the variable when displayed as

a plot curve
*ReadOff Suspend Reading

Instructs the data loader to ignore lines until the end

of the file or until the *ReadOn keyword is
encountered
*Readon Resume Reading

Instructs the data loader to resume reading the data

in the file, after reading has been suspended by the
*ReadOff keyword
*RF Report Format

Specifies the report width, number of decimal places,

and text justification of a loaded variable
*RH Report Header

Sets the first, second, and third rows of a report

header name for a loaded variable
*Set Pattern Set

Denotes the pattern set for which the data that

follows is loaded
*Skip Skip Data

Identifies a column of data to be ignored

*Start Minimum Depth for Loading Log Data

Specifies the minimum depth for which log data will

be loaded
*Subsea Subsea Units

Specifies that depth data in the depth data in the file

is in subsea units
*Tablename Table Name

Denotes the name of a table to be mapped to OFM,

specified in a definition file
*Throw Fault Throw

Denotes the length of the fault throw

*Trace Log Trace Table Type

Denotes that a specified table contains log traces

*TVD True Vertical Depth

Denotes the column that contains TVD values in a

deviation data file
*U Units

Denotes the English and metric unit identifier for a

73 of 164
Importing, Exporting, and Linking

variable specification in a definition file

*Xdelt X Direction Deviation

Denotes the column which contains the length of

deviation in the X direction, at a specified depth, in a
deviation data file
*Ydelt Y Direction Deviation

Denotes the column which contains the length of

deviation in the Y direction, at a specified depth in a
deviation file

74 of 164
Importing, Exporting, and Linking

*DA (Data Attributes) Keyword

Description This keyword controls data attributes used during data loading. It is
used in a table definition (.def) load file for a project variable.
Syntax *da [min valid value] [max valid value] [default value]
Example In this example, data loading is specified that the valid data load range
is from 5 to 500, with a default value of -99999:

*da 5 500 -99999

Related Topics

Overview of OFM Data

75 of 164
Importing, Exporting, and Linking

*Data (Data File) Keyword

Description This keyword denotes a file containing user-defined data to be loaded
as part of a batch load file.
Syntax *data [data file name]
Example In this example batch load file, the *data keyword is used twice, to
indicate that two data files are to be loaded:

*Project c:\vers21\duson\data\duson.ofm

*Definition c:\vers21\duson\data\duson.def

*keydata c:\vers21\duson\data\duson0.xy

*data c:\vers21\duson\data\duson1.dat

*data c:\vers21\duson\data\duson2.dat

*sort c:\vers21\duson\data\duson3.srt

*parser c:\vers21\duson\data\duson3.par

76 of 164
Importing, Exporting, and Linking

*Date (Date) Keyword

This keyword denotes a column in a text load file that contains a
date.
Descriptio Note: The variable DATE is a default variable in OFM which is not
n related to the @date system function. The @date system function
returns the system date from the computer or network operating
system.
Syntax *date
This example shows how a date column is specified in a text load file:
*TableName MONTHLYPROD

*Date&#9;*DAYS&#9;*OIL&#9;*GAS&#9;*WATER&#9;*PRESSURE&#9;*STATUS&#
9;

*KeyName "BLUE_1:Ge_6"
Example
19991201 8 1440.000000 38.000000 44.000000 -99999.000000 ""

20000101 31 6061.000000 75.000000 0.000000 -99999.000000 ""

20000201 29 5152.000000 156.000000 0.000000 -

77 of 164
Importing, Exporting, and Linking

*DateLabel (Date Label) Keyword

This keyword changes the label that OFM displays by default, and
Description expects the keyword for the date in monthly and daily tables. This
keyword is used in definition files.
Syntax *DateLabel string
In this example, OFM is told to expect the keyword *Lapse instead of
Example *Date in monthly and daily tables:

*DateLabel lapse

78 of 164
Importing, Exporting, and Linking

*Depth (Depth) Keyword

Description This keyword is required. It specifies the measured depth in the
wellbore. The keyword is always positive.
Syntax *Depth numeric
Example In this example, the *Depth keyword is used to tell OFM the column
in which the fault depth is located:

*Name *Depth *throw

*KeyName B-2

Fault_A 5000 100

*KeyName B-5

Fault_A 5476 200

*KeyName B-14

Fault_A 5446 300

Fault_B 5800 50

Related Examples
Displaying Formation or Reservoir Thickness and Structure: Getting Started

Related Topics
Guidelines for Loading Cross-Reference Data

Guidelines for Loading Fault Data

Guidelines for Loading Lookup Data

Guidelines for Loading Marker Data

Guidelines for Loading Sporadic Data

Guidelines for Loading Trace Data

79 of 164
Importing, Exporting, and Linking

*DualKey (Dual Key) Keyword

Description This keyword is used only in a sporadic data load file, to indicate a
dual-data load level. It indicates that data is recorded by date and time
with a *Date keyword being the primary filter and a *Time variable
being the secondary filter. The secondary filter must be the second
variable of the sporadic table in the definition file followed by oil, gas,
or water.

Note: This keyword must appear on the line directly following

*TableName.
Syntax *DualKey
Example In this example, the *Time data is recorded as hours past 12:00
midnight (that is, 3:00 A.M. is represented as 3 and 3:00 P.M. is
represented as 15). By using a *DualKey keyword in the data load file,
two values can be loaded per date per variable.

*Tablename altday

*DualKey

*Date *Time *ALP

*KeyName 42072313750000

19891231 12 37

80 of 164
Importing, Exporting, and Linking

*End (End Depth) Keyword

Description This keyword specifies the maximum depth for which log data will be
loaded. Do not load values after this depth.

Note: This keyword is used with *Start and *Inc.

Syntax *End
Example In this example, log data will be loaded for depths between 5300 feet
and 5850 feet in depth:

*Tablename LOG

*Compress

*KeyName 0-31

*Start 5300

*End 5850

*Inc 1

Related Topics
Guidelines for Loading Trace Data

81 of 164
Importing, Exporting, and Linking

*End_Format (End Format) Keyword

Description This keyword provides fixed field input:

n It defines the end of the format block in data tables with a fixed
format.

n Variables within the format block begin with an asterisk (*) and
include the beginning and ending column definition number.
Syntax *Format

*End_Format
Example In this example, the well name will be within columns 1-20, the data
will be within columns 21-28, and the days will be within columns 29-
35 in the load file:

*Format

*Well 1 20

*Date 21 28

*Days 29 35

*End_Format

82 of 164
Importing, Exporting, and Linking

*EOF (End of File) Keyword

Description This keyword indicates end-of-file. Data in the file after this keyword is
not read.
Syntax *EOF
Example In this example, data after 19961111 is ignored:

*TableName DAILYPROD

*DATE *OIL *GAS *WATER

*KeyName "BLUE_1:He_0"

19961100 40.000000 32.000000 284.000000

19961110 73.000000 90.000000 980.000000

19961111 76.000000 94.000000 1004.000000

*eof

19961112 75.000000 93.000000 999.000000

19961113 75.000000 93.000000 999.000000

19961114 75.000000 93.000000 963.000000

19961115 73.000000 90.000000 999.000000

83 of 164
Importing, Exporting, and Linking

*Factor (Factor) Keyword

Description This keyword is required. It specifies the fraction of well
production/injection allocated to a pattern.
Syntax *factor [allocation fraction]
Example In this example, 50% of the flow from injector OFM_01 is allocated to
pattern 501:

*Well *Factor

*Pattern 501

OFM_01 0.5

Related Topics
Guidelines for Loading Pattern Data

*Loss (Loss) Keyword

84 of 164
Importing, Exporting, and Linking

*Format (Format) Keyword

Description This keyword provides fixed field input. It defines the beginning of the
format block in data tables with a fixed format. Variables within the
format block begin with an asterisk (*) and include the beginning and
ending column definition number.
Syntax *Format

* End_Format
Example In this example, the well name will be within columns 1-20, date will
be within columns 21-28, and days will be within columns 29-35 in
the load file:

*Format

*Well 1 20

*Date 21 28

*Days 29 35

* End_Format

85 of 164
Importing, Exporting, and Linking

*Inc (Increment) Keyword

Description This keyword defines the increment of footage at which the trace data
is recorded:

Depth Depth
100 100
101.3 100.5
101.9 101
101.4 101.5
Syntax *Inc numeric
Example In this example, OFM is instructed to round log depth values to the
nearest increment of 0.5:

*Inc 1

Related Topics
Guidelines for Loading Trace Data

86 of 164
Importing, Exporting, and Linking

*KeyLength (Key Length) Keyword

Description This keyword sets the maximum number of characters that OFM
reads in a keyword, then uses this number to match with defined and
reserved keywords. Without this specification, OFM normally reads all
characters in a keyword.
Syntax *KeyLength numeric
Example In this example, four is the maximum number of characters that OFM
reads in a keyword:

*KeyLength 4

Note: If the keywords *Skipperf and *Skipco2 are provided to OFM,

only the characters contained in "Skip" are recognized to match with
defined and reserved keywords.

Related Topics
Guidelines for Loading Deviation Data

87 of 164
Importing, Exporting, and Linking

*KeyName (Key Name) Keyword

Description This keyword designates a value of the master key.

n Keys the values of the primary keyword in the master static

definition table.

n The primary keyword in the Master static definition table is the

master key.
Syntax *KeyName keys
Example This example identifies well names or primary keywords within a
production table:

*KeyName SLB_1

and

*KeyName SLB_2

88 of 164
Importing, Exporting, and Linking

*Loadby (Method for Loading Data)

Keyword
Description This keyword provides an additional method for loading data to a level
other than the completion level in OFM. The following tables are
supported by *Loadby:

n Static

n Monthly

n Daily

n Sporadic

Data may be loaded to a given level, as specified by an OFM sort

category. Load completion-level data to a separate table.
Syntax *loadby categoryname
Example This is an example:

*Loadby *flowstation

*TableName MeasuredProduction

*date *oil *gas *water

*KeyName FS-1

89 of 164
Importing, Exporting, and Linking

*Loss (Loss) Keyword

Description This keyword is optional. It specifies a loss factor used to modify
*Factor, to account for fluid losses or downhole allocations. The
allocation factor is the product of *Factor and (1- *Loss).

Note: The keyword is always a fraction.

Syntax *Loss
Example In this example, 20% of the flow from injector OFM_01 is being "lost"
and thus only 40% of its flow is going into pattern 501.

*Well *Factor *Loss

*Pattern 501

OFM_01 0.5 0.2

Related Topics
Guidelines for Loading Pattern Data

90 of 164
Importing, Exporting, and Linking

*MA (Aggregation Options) Keyword

Description This keyword defines the way that data is grouped for more than one
well. It also allows you to use pattern or other factors to apply to
values as they are read from the data source.

When grouping values for more than one well, the default is to sum
the values. Average_type allows you to specify an averaging method.

Note: When grouping values for more than one well, the default is to
sum values. By using this keyword, it is possible to specify an
averaging method instead.
Syntax *MA use_factor averaging_method

Where

use_factor is a Boolean:

0: No

1: Yes

(Use a pattern or other factor to apply to values as they are read from
the data source.)

averaging_method is:

0: None

1: Arithmetic

2: Geometric

3: Harmonic
Example In this example, when filtering by patterns, pressure is arithmetically
averaged rather than summed. Also, pattern allocation factors are not
applied.

Pressure FLOAT *MA 0 1

91 of 164
Importing, Exporting, and Linking

*Map (Map Association) Keyword

Description This keyword is in a definition file to denote the variables to be
mapped to various OFM association types.
Syntax *MAP "association type" "table name" "field name"

Where

Association type is one of the following:

n Well Type Exp

n Well Type Table

n Well Type Sort

n Wellbore

n Alias

n Object Type

n X Coordinate

n Y Coordinate

n Reference Depth

n Completion Depth

n Bottom Depth

n Project

n PVT Name

n Well Label
Example In this example, seven associations are defined:

*Map "Well Type Table" "Sc" "WELLTYPE"

*Map "Wellbore" "HEADERID" "WELLBORE"

*Map "Alias" "HEADERID" "ALIAS"

*Map "X Coordinate" "HEADERID" "XCOOR"

*Map "Y Coordinate" "HEADERID" "YCOOR"

*Map "Reference Depth" "HEADERID" "KBELEVATION"

*Map "Bottom Depth" "HEADERID" "TOTALDEPTH"

92 of 164
Importing, Exporting, and Linking

*Metric (Metric) Keyword

Description This keyword is optional. The keyword specifies that data following
this keyword is in metric units rather than English or scientific units.

It is inserted on the second line of the .def file when your data is
measured in metric units. If your data is measured in English units,
then this keyword should not be inserted. It must appear before any
data in a non-defined data file or before *Tablename in a defined data
file.

Note: The internal calculations in OFM are performed in English units.

Syntax *Metric

93 of 164
Importing, Exporting, and Linking

*MU (Multiplier) Keyword

Description This keyword indicates that the input data is a specified multiple of the
unit type, and it specifies the multiple of the unit type to use for
output.

Note: The multiplier can be any prefix assigned in the Multiplier table.
Syntax *MU inputunit outputunit
Example In this example, the input data for gas measurements are in MMscf,
and the output unit are MMMscf:

Gas DOUBLE *U scf *MU MM MMM

94 of 164
Importing, Exporting, and Linking

*Null (Null) Keyword

Description This keyword specifies a number for the data loader to consider a
value of null as opposed to having no value or zero. The default is -
99999. This function applies only to variables defined as a float or
double.
Syntax *Null (numeric)
Example In this example, a value in the load file of -9999.25 will be interpreted
as a null value:

*Null 9999.25

95 of 164
Importing, Exporting, and Linking

*PA (Plot Attributes) Keyword

Description This keyword specifies the plot attributes for a variable. It sets line
color, line type, and point type using the values or words (no spaces)
from the following table.

Code Line Colors Line Type Point Type

0 White None None
1 Black Solid Circle
2 Red Dotted Up triangle
3 Green Dashed Down triangle
4 Blue Dash-dot Square
5 Yellow Star
6 Magenta Diamond
7 Cyan Plus
8 Minus
9 Vertical bar
10 Slash
11 Backslash
12 Hourglass

Point size ranges from 1 to 20. You can mix names and code values in
the description of *PA. For example, both of the following are
equivalent:

n *PA 4 dotted 1 4

n *PA blue 2 circle 4

Syntax *PA linecolor
Example In this example, plots of days would use a blue-dotted line with 4-
point circles:

Days FLOAT *PA 4 2 1 4

Or

Days FLOAT *PA blue dotted circle 4

96 of 164
Importing, Exporting, and Linking

*Parser (Parser) Keyword

Description This keyword denotes a file containing calculated variable data to be
loaded as part of a batch load file.
Syntax *parser [data file name]
Example In this example batch load file, the *parser keyword is used to indicate
the file in which calculated variables are contained:

*Project c:\vers21\duson\data\duson.ofm

*Definition c:\vers21\duson\data\duson.def

*keydata c:\vers21\duson\data\duson0.xy

*sort c:\vers21\duson\data\duson3.srt

*parser c:\vers21\duson\data\duson3.par

Related Topics
Exporting Project Calculated Variables

97 of 164
Importing, Exporting, and Linking

*Pattern (Pattern) Keyword

Description This keyword denotes the pattern for which the data that follows is
loaded.
Syntax *Pattern [pattern name]
Example In this example, the *pattern instructs the data loader to load data for
pattern 502:

*set "inverted_five_spot"

*WELL *factor *loss

*pattern 502

*date 199301

495:B 0.25 0

496:B 0.25 0

502WI:B 1 0

500:B 0.25 0

98 of 164
Importing, Exporting, and Linking

*PN (Plot Name) Keyword

Description This keyword denotes the name of the variable when displayed as a
plot curve.
Example In this example, the variable dailyprod.oil will display as “Daily Oil
Production” in plots:

*TableName DAILYPROD Daily

&#9;OIL&#9;Float

&#9;&#9;*pn "Daily Oil Production"

99 of 164
Importing, Exporting, and Linking

*ReadOff (Suspend Reading) Keyword

Description This keyword instructs the data loader to ignore lines until the end of
the file or until the *ReadOn (Resume Reading) keyword is
encountered.
Example In this example, the gas variable is ignored when defining the table
DAILYPROD:

*TableName DAILYPROD Daily

OIL Float

*rh "Daily" "Oil" "Production"

*rf 10 0 "Right"

*pn "Daily Oil Production"

*pa "Green" "Solid" "None" 4

*u "bbl/d" "m3/d"

*ma "Yes" "None"

*READOFF

GAS Double

*rh "Daily" "Gas" "Production"

*rf 10 0 "Right"

*pn "Daily Gas Production"

*pa "Red" "Solid" "None" 4

*u "cf/d" "scm/d"

*mu "M" "M"

*ma "Yes" "None"

*READON

WATER Float

*rh "Daily" "Water" "Production"

*rf 10 0 "Right"

*pn "Daily Water Production"

*pa "Blue" "Solid" "None" 4

*u "bbl/d" "m3/d"

*ma "Yes" "None"

100 of 164
Importing, Exporting, and Linking

*Readon (Resume Reading) Keyword

Description This keyword instructs the data loader to resume reading the
data in the file, after reading has been suspended by the
*ReadOff (Suspend Reading) keyword.
Example In this example, the gas variable is ignored when defining the
table DAILYPROD:

*TableName DAILYPROD Daily

&#9;OIL&#9;Float

&#9;&#9;*rh "Daily" "Oil" "Production"

&#9;&#9;*rf 10 0 "Right"

&#9;&#9;*pn "Daily Oil Production"

&#9;&#9;*pa "Green" "Solid" "None" 4

&#9;&#9;*u "bbl/d" "m3/d"

&#9;&#9;*ma "Yes" "None"

*READOFF

&#9;GAS&#9;Double

&#9;&#9;*rh "Daily" "Gas" "Production"

&#9;&#9;*rf 10 0 "Right"

&#9;&#9;*pn "Daily Gas Production"

&#9;&#9;*pa "Red" "Solid" "None" 4

&#9;&#9;*u "cf/d" "scm/d"

&#9;&#9;*mu "M" "M"

&#9;&#9;*ma "Yes" "None"

*READON

&#9;WATER&#9;Float

&#9;&#9;*rh "Daily" "Water" "Production"

&#9;&#9;*rf 10 0 "Right"

&#9;&#9;*pn "Daily Water Production"

&#9;&#9;*pa "Blue" "Solid" "None" 4

&#9;&#9;*u "bbl/d" "m3/d"

&#9;&#9;*ma "Yes" "None"

101 of 164
Importing, Exporting, and Linking

*RF (Report Format) Keyword

Description This keyword specifies the report width, number of decimal places,
and text justification of a loaded variable.
Example In this example, the variable dailyprod.oil will be displayed in reports
with a width of 10, will have no decimal places, and the text will be
right justified.

*TableName DAILYPROD Daily

&#9;OIL&#9;Float

&#9;&#9;*rh "Daily" "Oil" "Production"

&#9;&#9;*rf 10 0 "Right"

&#9;&#9;*pn "Daily Oil Production"

&#9;&#9;*pa "Green" "Solid" "None" 4

102 of 164
Importing, Exporting, and Linking

*RH (Report Header) Keyword

Description This keyword sets the first, second, and third rows of a report header
name for a loaded variable.
Example In this example, the *rh line instructs OFM to display the column
header for dailyprod.oil as "Daily/Oil/Production":

*TableName DAILYPROD Daily

&#9;OIL&#9;Float

&#9;&#9;*rh "Daily" "Oil" "Production"

&#9;&#9;*rf 10 0 "Right"

&#9;&#9;*pn "Daily Oil Production"

&#9;&#9;*pa "Green" "Solid" "None"

103 of 164
Importing, Exporting, and Linking

*Set (Pattern Set) Keyword

Description This keyword denotes the pattern set for which the data that follows
is loaded.
Example In this example, pattern data will be loaded into a pattern set named
"inverted five spot":

*label PATTERN

*set "inverted_five_spot"

*WELL *factor *loss

*pattern 502

*date 199301

495:B 0.25 0

496:B 0.25 0

502WI:B 1 0

500:B 0.25 0

501:B 0.25 0

*pattern 503

*date 199301

496:B 0.25 0

104 of 164
Importing, Exporting, and Linking

*Skip (Skip Data) Keyword

Description This keyword identifies a column of data to be ignored when loading a
file.
Syntax *Skip
Example In this example, the third column of data is ignored (so, Hobbs is not
read):

*Oil *Water *Skip *Gas

150 6648 HOBBS 6788

105 of 164
Importing, Exporting, and Linking

*Start (Minimum Depth for Loading Log

Data) Keyword
Description This keyword specifies the minimum depth for which log data will be
loaded. Do not load values before this depth.

Note: This keyword is used with *End and *Inc.

Syntax *Start
Example In this example, log data will be loaded for depths between 5300 feet
and 5850 feet in depth:

*Tablename LOG

*Compress

*KeyName 0-31

*Start 5300

*End 5850

*Inc 1

106 of 164
Importing, Exporting, and Linking

*Subsea (Subsea Units) Keyword

Description This keyword specifies that depth data in the file is in subsea units.
Syntax *Subsea
Example In this example, depths are indicated to be in subsea depth:

*TableName OFM_DATA_LOG

*DEPTH *ILD

*SUBSEA

*KeyName "BLUE_1"

*DATE 19000101

  5151.000000 0.426800

  5152.000000 0.502400

  5153.000000 0.611200

  5154.000000 0.624200

  5155.000000 0.599000

  5156.000000 0.547900

  5157.000000 0.510000

  5158.000000 0.771400

  5159.000000 1.381300

107 of 164
Importing, Exporting, and Linking

*Tablename (Table Name) Keyword

Description This keyword denotes the name of a table to be mapped to OFM,
specified in a definition file.
Syntax *tablename [tablename] [tabletype]
Example In this example, the *tablename keyword tells OFM to create a table
map to a daily table called DAILYPROD:

*TableName DAILYPROD Daily

OIL Float

*rh "Daily" "Oil" "Production"

*rf 10 0 "Right"

*pn "Daily Oil Production"

*pa "Green" "Solid" "None" 4

*u "bbl/d" "m3/d"

*ma "Yes" "None"

Related Examples
Displaying Formation or Reservoir Thickness and Structure: Getting Started

108 of 164
Importing, Exporting, and Linking

*Throw (Fault Throw) Keyword

Description This keyword denotes the length of the fault throw, for a fault loaded
via the data loader.
Example In this example, fault "AA" is denoted to have a throw of 50:

*TableName Fault

*Name *Depth *Throw *Azimuth *Type

*KeyName "BLUE_14"

"AA" 5500.000000 50.000000 15.000000 "unknown"

109 of 164
Importing, Exporting, and Linking

*Trace (Log Trace Table Type) Keyword

Description This keyword denotes that a specified table contains log traces.
Example In this example, the OFM_DATA_LOG table is identified as the log
trace table:

*TableName OFM_DATA_LOG Trace

DEPTH Float

*rh "" "LOG" "DEPTH"

*rf 10 1 "Right"

*pn "LOG.DEPTH"

*pa "Red" "Solid" "None" 4

*ma "Yes" "None"

ACOUSTIC Float

*rh "" "LOG" "ACOUSTIC"

*rf 10 1 "Right"

*pn "LOG.ACOUSTIC"

*pa "Green" "Solid" "None" 4

*ma "Yes" "None"

110 of 164
Importing, Exporting, and Linking

*TVD (True Vertical Depth) Keyword

Description This keyword denotes the column that contains true vertical
depth values in a deviation data file.
Example In this example, the second column contains true vertical
depth values:

*TableName Dev

*Md *TVD *XDelt *YDelt

*KeyName "GREEN_14"

0. 0. 0. 0.

0.000000 0.000000 0.000000 0.000000

7450.000000 7445.000000 -138.000000 -122.000000

8253.000000 8243.000000 -223.679993 -134.539993

9560.000000 9468.000000 -613.000000 -296.720001

11130.000000 10730.000000 -1507.589966 -554.229980

12773.000000 11762.000000 -2755.870117 -765.919983

111 of 164
Importing, Exporting, and Linking

*U (Units) Keyword
Description This keyword denotes the English and metric unit identifier for
a variable specification in a definition file.
Example In this example, the *u keyword denotes that the English units
for monthlygas.volume are bbl and the metric units are m3:

Name MONTHLYGASINJ Monthly

VOLUME Float

*rh "Monthly" "Gas" "Injected"

*rf 10 0 "Right"

*pn "Monthly Gas Injected"

*pa "Red" "Solid" "None" 4 0 "None"

*u "bbl" "m3"

*ma "Yes" "None"

112 of 164
Importing, Exporting, and Linking

*Xdelt (X Direction Deviation) Keyword

Description This keyword denotes the column that contains the length of
deviation in the X direction, at a specified depth, in a deviation
data file.
Example In this example, the third column contains X deviation values:

*TableName Dev

*Md *TVD *XDelt *YDelt

*KeyName "GREEN_14"

0. 0. 0. 0.

0.000000 0.000000 0.000000 0.000000

7450.000000 7445.000000 -138.000000 -122.000000

8253.000000 8243.000000 -223.679993 -134.539993

9560.000000 9468.000000 -613.000000 -296.720001

11130.000000 10730.000000 -1507.589966 -554.229980

12773.000000 11762.000000 -2755.870117 -765.919983

113 of 164
Importing, Exporting, and Linking

*Ydelt (Y Direction Deviation) Keyword

Description This keyword denotes the column that contains the length of
deviation in the Y direction, at a specified depth in a deviation
data file.
Example In this example, the fourth column contains Y deviation values:

*TableName Dev

*Md *TVD *XDelt *YDelt

*KeyName "GREEN_14"

0. 0. 0. 0.

0.000000 0.000000 0.000000 0.000000

7450.000000 7445.000000 -138.000000 -122.000000

8253.000000 8243.000000 -223.679993 -134.539993

9560.000000 9468.000000 -613.000000 -296.720001

11130.000000 10730.000000 -1507.589966 -554.229980

12773.000000 11762.000000 -2755.870117 -765.919983

114 of 164
Importing, Exporting, and Linking

Overview of Time Keywords

This keyword... Does this...
*dd Day Column

Specifies the column containing the day

*ddmmyy Day-Month-Year

Specifies that date values are in Day-Month-Year

order
*mm Month Column

Specifies the column containing the month

*mmyydd Month-Day-Year

Specifies that date values are in Month-Day-Year

order
*yy Year Column

Specifies the column containing the year

*yymm Year-Month

Specifies that date values are in Year-Month order

*yymmdd Year-Month-Day

Specifies that date values are in Year-Month-Day

order

115 of 164
Importing, Exporting, and Linking

*dd (Day Column) Keyword

Description This keyword specifies the column containing the day in text load files.
Example In this example, the day value is located in the third column:

*TableName MONTHLYPROD

*YY *MM *DD *DAYS *GAS *OIL *PRESSURE *STATUS *WATER

*KeyName "BLUE_1:Ge_6"

1999 12 01 8 38.000000 1440.000000 -99999.000000 ""

44.000000

2000 01 01 31 75.000000 6061.000000 -99999.000000 ""

0.000000

2000 02 01 29 156.000000 5152.000000 -99999.000000 ""

0.000000

2000 03 01 31 74.000000 5347.000000 -99999.000000 ""

0.000000

2000 04 01 30 113.000000 4642.000000 -99999.000000 ""

0.000000

2000 05 01 31 87.000000 5264.000000 -99999.000000 ""

0.000000

2000 06 01 30 35.000000 5247.000000 -99999.000000 ""

0.000000

116 of 164
Importing, Exporting, and Linking

*ddmmyy (Day-Month-Year) Keyword

Description This keyword specifies that date values in the text load file are in Day-
Month-Year order.
Example In this example, *ddmmyy specifies that date values are in Day-
Month-Year order:

*TableName MONTHLYPROD

*ddmmyy *DAYS *GAS *OIL *PRESSURE *STATUS *WATER

*KeyName "BLUE_1:Ge_6"

01012010 8 38.000000 1440.000000 -99999.000000 ""

44.000000

01022010 31 75.000000 6061.000000 -99999.000000 ""

0.000000

01032010 29 156.000000 5152.000000 -99999.000000 ""

0.000000

01042010 31 74.000000 5347.000000 -99999.000000 ""

0.000000

01052010 30 113.000000 4642.000000 -99999.000000 ""

0.000000

01062010 31 87.000000 5264.000000 -99999.000000 ""

0.000000

01072010 30 35.000000 5247.000000 -99999.000000 ""

0.000000

117 of 164
Importing, Exporting, and Linking

*mm (Month Column) Keyword

Description This keyword specifies the column containing the month in text load
files.
Example In this example, the month value is located in the second column:

*TableName MONTHLYPROD

*YY *MM *DD *DAYS *GAS *OIL *PRESSURE *STATUS *WATER

*KeyName "BLUE_1:Ge_6"

1999 12 01 8 38.000000 1440.000000 -99999.000000 ""

44.000000

2000 01 01 31 75.000000 6061.000000 -99999.000000 ""

0.000000

2000 02 01 29 156.000000 5152.000000 -99999.000000 ""

0.000000

2000 03 01 31 74.000000 5347.000000 -99999.000000 ""

0.000000

2000 04 01 30 113.000000 4642.000000 -99999.000000 ""

0.000000

2000 05 01 31 87.000000 5264.000000 -99999.000000 ""

0.000000

2000 06 01 30 35.000000 5247.000000 -99999.000000 ""

0.000000

118 of 164
Importing, Exporting, and Linking

*mmyydd (Month-Day-Year) Keyword

Description This keyword specifies that date values in the text load file are in
Month-Day-Year order.
Example In this example, *mmddyy specifies that date values are in Month-
Day-Year order:

*TableName MONTHLYPROD

*mmddyy *DAYS *GAS *OIL *PRESSURE *STATUS *WATER

*KeyName "BLUE_1:Ge_6"

01012010 8 38.000000 1440.000000 -99999.000000 ""

44.000000

02012010 31 75.000000 6061.000000 -99999.000000 ""

0.000000

03012010 29 156.000000 5152.000000 -99999.000000 ""

0.000000

04012010 31 74.000000 5347.000000 -99999.000000 ""

0.000000

05012010 30 113.000000 4642.000000 -99999.000000 ""

0.000000

119 of 164
Importing, Exporting, and Linking

*yy (Year Column) Keyword

Description This keyword specifies the column containing the year in text load
files.
Example In this example, the year value is located in the first column:

*TableName MONTHLYPROD

*YY *MM *DD *DAYS *GAS *OIL *PRESSURE *STATUS *WATER

*KeyName "BLUE_1:Ge_6"

1999 12 01 8 38.000000 1440.000000 -99999.000000 ""

44.000000

2000 01 01 31 75.000000 6061.000000 -99999.000000 ""

0.000000

2000 02 01 29 156.000000 5152.000000 -99999.000000 ""

0.000000

2000 03 01 31 74.000000 5347.000000 -99999.000000 ""

0.000000

2000 04 01 30 113.000000 4642.000000 -99999.000000 ""

0.000000

2000 05 01 31 87.000000 5264.000000 -99999.000000 ""

0.000000

2000 06 01 30 35.000000 5247.000000 -99999.000000 ""

0.000000

120 of 164
Importing, Exporting, and Linking

*yymm (Year-Month) Keyword

Description This keyword specifies that date values in the text load file are in Year-
Month order.
Example In this example, *yymm specifies that date values are in Year-Month
order:

*TableName MONTHLYPROD

*yymm *DAYS *GAS *OIL *PRESSURE *STATUS *WATER

*KeyName "BLUE_1:Ge_6"

201001 8 38.000000 1440.000000 -99999.000000 "" 44.000000

201002 31 75.000000 6061.000000 -99999.000000 "" 0.000000

201003 29 156.000000 5152.000000 -99999.000000 ""

0.000000

201004 31 74.000000 5347.000000 -99999.000000 "" 0.000000

201005 30 113.000000 4642.000000 -99999.000000 ""

0.000000

121 of 164
Importing, Exporting, and Linking

*yymmdd (Year-Month-Day) Keyword

Description This keyword specifies that date values in the text load file are in Year-
Month-Day order.
Example In this example, *yymmdd specifies that date values are in Year-
Month-Day order:

*TableName MONTHLYPROD

*YYMMDD *DAYS *GAS *OIL *PRESSURE *STATUS *WATER

*KeyName "BLUE_1:Ge_6"

19991201 8 38.000000 1440.000000 -99999.000000 ""

44.000000

20000101 31 75.000000 6061.000000 -99999.000000 ""

0.000000

20000201 29 156.000000 5152.000000 -99999.000000 ""

0.000000

20000301 31 74.000000 5347.000000 -99999.000000 ""

0.000000

20000401 30 113.000000 4642.000000 -99999.000000 ""

0.000000

20000501 31 87.000000 5264.000000 -99999.000000 ""

0.000000

20000601 30 35.000000 5247.000000 -99999.000000 ""

0.000000

122 of 164
Importing, Exporting, and Linking

*Day (Day) Keyword

Description This keyword is obsolete. It specified the column containing the day in
old, Production Analyst text load files.
Example In this example, the day field is located in the third column:

*year *month *day *dayson *oil *gas *water *press

*name BLUE_1:He_0

2007 01 01 23 0 30063 0 4000

2007 02 01 28 0 32568 0 4000

2007 03 01 31 0 89825 0 4000

2007 04 01 30 0 103560 0 4000

2007 05 01 31 626 104547 0 4000

2007 06 01 30 2010 104340 0 4000

2007 07 01 31 2067 106454 0 4000

123 of 164
Importing, Exporting, and Linking

*Month (Month) Keyword

Description This keyword is obsolete. It specified the column containing the
month in old, Production Analyst text load files.
Example In this example, the month field is located in the second
column:

*year *month *day *dayson *oil *gas *water *press

*name BLUE_1:He_0

2007 01 01 23 0 30063 0 4000

2007 02 01 28 0 32568 0 4000

2007 03 01 31 0 89825 0 4000

2007 04 01 30 0 103560 0 4000

2007 05 01 31 626 104547 0 4000

2007 06 01 30 2010 104340 0 4000

2007 07 01 31 2067 106454 0 4000

124 of 164
Importing, Exporting, and Linking

*Year (Year) Keyword

Description This keyword is obsolete. It specified the column containing the
year in old, Production Analyst text load files.
Example In this example, the year field is located in the third column:

*year *month *day *dayson *oil *gas *water *press

*name BLUE_1:He_0

2007 01 01 23 0 30063 0 4000

2007 02 01 28 0 32568 0 4000

2007 03 01 31 0 89825 0 4000

2007 04 01 30 0 103560 0 4000

2007 05 01 31 626 104547 0 4000

2007 06 01 30 2010 104340 0 4000

2007 07 01 31 2067 106454 0 4000

125 of 164
Importing, Exporting, and Linking

Files Required for Building an OFM

Workspace from ASCII Files
Creating a workspace from ASCII files is one of the ways to define a workspace. OFM requires the following
files when you build workspaces from ASCII files.

Required OFM Workspace Files

File Type Example File Name Description

Definition project.def Creates the table structure in the
new OFM database. When you use
a definition file to create the initial
workspace, OFM automatically
loads it before loading any other
file.
Parser project.par Creates the calculated variables
required in the OFM workspace.
These typically include rate,
cumulative, and ratio calculations.
Data Files project.xy Provide the data to populate the
tables in the database.
project.prd

126 of 164
Importing, Exporting, and Linking

About the Project Definition (project.def)

File
The project definition file is one of the files required when creating an OFM project from ASCII files. It
creates the data tables. OFM automatically loads this file before it loads any other file. The project definition
file does the following:

n Describes the database structure (tables and columns)

n Defines the numeric precision and text limits for data

n Assigns units and multipliers to each column

n Assigns attributes for displaying data (such as units, color of plot curves, and plot and report names)

n Defines how OFM should combine data in each column when grouping completions (sum or average)

n Identifies categories

Note: There are many different definition files (files with a .def extension) that install with OFM. This help
topic is about one specific definition file: the project definition file (project.def).

How the File is Created

You create the project definition file by exporting it from an existing OFM project. You can then change it,
as needed.

Actions You Can Take

You can open the definition file with a text editor, such as Notepad.

127 of 164
Importing, Exporting, and Linking

Definition File Guidelines

Use the following guidelines for definition files:

n File extension: The file extension must be .def for OFM to recognize the file as a definition file.

n Comments: Type // or /* before comments inside the file. OFM ignores comment lines that you
mark this way.

n Case sensitivity: Nothing in the definition file is case sensitive.

n Master table: Make sure the first table in the definition file is a static data table as well as the
master table.

n Make sure the master table has a unique entity identifier (a primary key).

n Make sure the unique identifier is the first variable in the master table, and that it has a string
data type.

n Table names

n Each table in your project must have a unique name. The *Tablename keyword sets the table
name and identifies the table type (such as monthly, daily, lookup, and so on).

n Make sure the data files you prepare for loading use the same table name and column names
you identify in the definition file.

n Column names: Column names must follow these rules:

n One table cannot have more than one column with the same name in it. You can use the same
name in a different table. For example, a table named MonthlyProd and a table named DailyProd
each can have a column named Oil.

n Column names can include uppercase and lowercase letters, numbers, and underscores. You
cannot have spaces in column names.

n Loading: You can create all project tables loading one large definition file, or you may split them
among several small definition files with different tables in each file. After loading the definition file,
use the Edit Schema Tables window to change the table structures interactively.

128 of 164
Importing, Exporting, and Linking

About the Parser (project.par) File

A parser file is one of the files required when creating an OFM project from ASCII files. It creates the
calculated variables required in the OFM workspace. These usually include rate, cumulative, and ratio
calculations.

The parser file does the following:

n Defines the name of each calculated variable and its formula

n Assigns units and multipliers to each calculated variable

n Assigns attributes for displaying data (such as units, color of plot curves, and plot and report names)

How the File is Created

You create the parser file by exporting it from an existing OFM project. You can then change it as needed.

Actions You Can Take

You can open the parser file with a text editor, such as Notepad.

129 of 164
Importing, Exporting, and Linking

Parser File Guidelines

Use the following guidelines for parser files:

n File extension: The file extension must be .par for OFM to recognize the file as a parser file.

n Comments: Type // or /* before comments inside the file. OFM ignores comment lines that you
mark this way.

n Case sensitivity: Nothing in the parser file is case sensitive.

n Calculated variable names: Names can include uppercase and lowercase letters, numbers,
underscores, and periods. You cannot have spaces in calculated variable names.

n Loading: Follow these rules for loading parser files:

n You can create all project calculated variables by loading one larger parser file, or you may split
them among several small parser files with different calculated variables in each file. After
loading the parser file, you can make changes either interactively in the OFM workspace or by
changing and reloading the parser file.

n You can load parser files at any time during project creation, as long as you have loaded first the
project definition.

130 of 164
Importing, Exporting, and Linking

Overview of Data Examples

The help system has tutorials, samples, and examples. You can use these to understand and learn OFM
features.

n Tutorials focus on explaining a single type of analysis.

n Samples use one of the illustrative databases to show a specific feature or concept.

n Examples use more than one feature or type of analysis to show a potential workflow.

For this... Use this...

Tutorials for a good Patterns
understanding of importing
data
Examples that show loading Using .Las Log Data
and entering data as part of a
Displaying Formation or Reservoir Thickness and Structure
workflow
Calculating Pressure from P/Z and Production Data

131 of 164
Importing, Exporting, and Linking

Tutorial: Patterns
You can configure waterflood patterns by assigning completions to a pattern and allocating production and
injection volumes from those completions. Typical pattern configurations look like these:

You must use your judgment and knowledge of the reservoir to assign a realistic fraction of each
completion's production or injection to the block of reservoir beneath the pattern. When you do this, you
can compare performance, surveillance, and the optimization of operations at the pattern level,
considering both injection and production.

In this tutorial, you will:

n Open the waterflood sample project

n Create patterns interactively: Each pattern has several completions. In this section, you select the
completions for each pattern individually.

n Edit patterns: After you create patterns, you can change the pattern allocation factors or dates. In
this section, you edit the patterns that you created. There are two ways to change the pattern data.
You can change one pattern at a time, or you can change the pattern data with all sets and all
patterns visible.

n Confirm the pattern allocation factors: No single well should have allocation factors summing to
more than one. In this section, you create a report to confirm this.

n Choose variables affected by pattern allocation factors: In this section, you choose which variables
are affected by pattern allocation factors, and which are not. The factors should only affect volumes.
Pressures, depths, porosities, choke sizes, hours on production, or any other non-volume variable
should not be affected.

n View pattern results one at a time: In this section, you use patterns and see the effect of the pattern
allocation factors that you supplied. You can use patterns by filtering or by stepping though (on the
Navigation pane). You can see the results most easily in plots or reports. You will create a report
that shows the results of pattern allocation factors.

132 of 164
Importing, Exporting, and Linking

n Compare multiple patterns on a plot: In this section, you create a plot that compares multiple
patterns, applying pattern allocation factors.

n Create patterns from an ASCII file: If you have determined the allocation factors already and it is
available in a document or spreadsheet, you can reformat the data and load it into OFM. The pattern
data can be static or dynamic. For dynamic patterns, the allocation factors may change over time as
injectors are created and terminated. You can remove wells from a pattern as new patterns are
created. In this section, you add patterns to the project by loading a formatted data file. They will be
the same patterns that you created interactively.

Opening the Waterflood Sample Project

Open the Bfield sample workspace. It is in the OFM installation folder, at ...Sample
Workspaces\Pilot Waterflood Sample\Pilot Waterflood BField.ofm.

Creating Patterns Interactively

Each pattern has several completions. In this section, you select the completions for each pattern
individually.

Note: Before you start, you may want to print a large map of your area and manually draw the pattern
outlines on that map. This helps organize your work when you configure the patterns interactively in OFM.

1. On the Format tab, in the Zoom group, click Zoom Area.

2. On the base map, drag a frame around the pattern waterflood area in the north (marked with blue
symbols).

With this waterflood, you could create patterns with a regular layout or in an inverted layout. You
will set up regular patterns.

Regular layout: Inverted layout:

3. On the Property pane, under Well Name Properties, change the Well Name to Alias Name.

4. On the base map, press Ctrl and click wells 491, 492, 495, 498, and 502.

5. Release the Ctrl key.

The Edit Patterns window opens.

133 of 164
Importing, Exporting, and Linking

n The left pane lists patterns. OFM lists the pattern you created with a default name (P-0). The
date (1900-01-01) is the default starting date for the pattern.

n The right pane lists the five wells you selected.

n The Current Pattern Set field at the bottom of the window displays the current pattern
(inverted_five_spot). Because two pattern sets have already been configured for this project,
the pattern you created is in the current pattern. You will change the pattern in the next section
of the tutorial.

6. Click OK to close the Edit Patterns window.

7. On the base map, press Ctrl and select another five wells to create another pattern.

8. Release the Ctrl key.

The Edit Patterns window opens. OFM lists the pattern you created with a default name (P-1) and
the default starting date for the pattern. The wells you selected are listed on the right pane.

9. Click OK to close the Edit Patterns window.

Editing Patterns
After you create patterns, you can change the pattern allocation factors or dates. In this section, you edit
the patterns that you created. There are two ways to change the pattern data. You can change one
pattern at a time, or you can change the pattern data with all sets and all patterns visible.

1. First, view how you can change the pattern data, one pattern at a time:

a. On the Setup tab, in the Workspace Managers group, click Patterns.

The Edit Patterns window opens. Notice that you can navigate to the pattern you want to edit,
by expanding the pattern folder in the left pane.

b. Click OK to close the Edit Patterns window.

2. Now you will change the pattern data with all sets and all patterns visible. On the Setup tab, in the
Tables group, click Data Grid.
The Select OFM Table to Edit window opens.

3. Select the Pattern table and then click OK.

The contents of the Pattern table display, showing all patterns configured in both pattern sets.

4. Scroll to the bottom of the table and find the records for the patterns you created. They are part of
the inverted_five_spot pattern set, and the pattern name is P-0 and P-1.

5. Highlight all records that are not the patterns you created. Ensure the entire rows are highlighted.
Press Delete.
Only the P-0 and P-1 patterns remain.

6. Change the PatternSet names from inverted_five_spot to Tutorial.

7. Change the PatternNames. A common naming convention is to name the pattern after the center

134 of 164
Importing, Exporting, and Linking

well. Name the first pattern you created (with the default name P-0) P-495.

8. Note the other table columns:

n Date: This is the effective start date of the pattern allocation factors. This does not have to be
the first date of production or injection. The default date (January 1900) means the allocation
factors are in effect from the beginning of the waterflood, and usually can be left unchanged.

n Factor: This is the allocation factor the specific well's rates and volumes to the specific pattern.
For example, an allocation factor of 0.5 implies that 50% of its injection is supporting a different
pattern.

n Loss: This is the injectant loss factor. For example, a loss of 0.2 implies that 20% of water
injected is being lost to non-pay zones or outside the pattern area.

The effective factor is the Factor value minus the Loss value. So, instead of setting a Loss, you
can choose to set a lower Factor.

9. Since no single well should be allocated more than 100%, a simple way to set geometric allocation
factors is to sort the table by well. Double-click the Well column heading to sort the table.

10. For each well, do the following:

n If the well only appears one time, leave the Factor value as 1.

n If the well appears two times, change the Factor value for each to 0.5.

n If the well appears three times, change the Factor value for each to 0.33

Make sure to click on a different record after making a change, to save the change.

11. When you finish, close the Pattern table.

Confirming the Pattern Allocation Factors

No single well should have allocation factors summing to more than one. In this section, you create a
report to confirm this.

1. On the Home tab, in the Launch analysis group, click Report.

The Edit Report window opens.

2. In the Select box, enter the following: @PatCurSet( ), @PatWell( ), @PatName( ), @PatDate(
), @PatFact( ), @PatLoss( )

3. Click OK.
A report opens. It lists the pattern set name, well, pattern name, date, factor, and loss.

4. On the report, click in the @PatWell() column.

5. On the Property pane, under Columns, change the Break when this column changes field to
Yes.

6. On the report, click in the @PatFact() column.

135 of 164
Importing, Exporting, and Linking

7. On the Property pane, under Columns, change the Subtotal field to SUM.

8. On the report, check the sum values to make sure that none of them are larger than 1.00.

Choosing Variables Affected by Pattern Allocation Factors

In this section, you choose which variables are affected by pattern allocation factors, and which are not.
The factors should only affect volumes. Pressures, depths, porosities, choke sizes, hours on production, or
any other non-volume variable should not be affected.

1. On the Setup tab, in the Tables group, click Schema.

The Edit Schema Tables window opens. In this project, only the PRD and WIN tables store
volumes.

2. Make sure the OIL, GAS, and WATER variables in the PRD table are set for Multiply by Factor because
these store volumes.

a. On the left pane, expand the PRD table and then click the OIL variable.

b. On the right, view the Math tab.

c. In the Grouping Options section, make sure Multiply by Factor is selected.

d. On the PRD table, select the GAS variable.

e. On the Math tab, make sure Multiply by Factor is selected.

f. On the PRD table, select the WATER variable.

g. On the Math tab, make sure Multiply by Factor is selected.

3. Make sure the ACTIVE, DAYS, and PRESS variables in the PRD table are not set for Multiply by Factor:

a. On the left pane, in the PRD table, click the ACTIVE variable.

b. On the Math tab, in the Grouping Options section, make sure the Multiply by Factor check
box is clear.

c. On the PRD table, select the DAYS variable.

d. On the Math tab, make sure the Multiply by Factor check box is clear.

e. On the PRD table, select the PRESS variable.

f. On the Math tab, make sure the check box is clear.

4. On the left pane, expand the WIN table and make sure that the variables that store volumes are set
to Multiply by Factor. Make sure that all other variables are not set to Multiply by Factor.

5. Make sure that all numeric variables in the MASTER, PVT, and RESPROP tables are not set to
Multiply by Factor.

6. Click OK to save your changes and close the Edit Schema Tables window.

136 of 164
Importing, Exporting, and Linking

Viewing Pattern Results One at a Time

In this section, you use patterns and see the effect of the pattern allocation factors that you supplied. You
can use patterns by filtering or by stepping though (on the Navigation pane). You can see the results
most easily in plots or reports. You will create a report that shows the results of pattern allocation factors.

1. On the Home tab, in the Launch analysis group, click Report.

The Edit Report window opens.

2. In the Select box, enter the following: Date, Win.Winj

3. Click OK.
A report opens. An empty report opens with columns for the date and water injection.

4. On the Format tab, in the Edit group, click Date & Sort.
The Edit Report Attributes window opens.

5. Select At Last Date and then click OK.

6. Use patterns for filtering:

a. On the Filter pane, click Clear Filter (  ).

b. On the Filter pane, expand Category, then Patterns, then Tutorial.

c. Under Tutorial, select the check box to the left of the first pattern (this was the P-0 pattern,
which you may have renamed P-495).

d. Click Group (  ) to view the total pattern results.

The report populates with one row.

7. Compare the difference with and without pattern use:

a. On the Filter pane, click Clear Filter (    ).

b. View the base map.

c. On the Format tab, in the Zoom group, click Zoom Area and then drag across the map around
the pattern waterflood area in the north.

d. On the Filter pane, click Group (  ).

e. View the report.

The report populates with one row. The water injection value represents the unallocated total of
all five wells, so it is a larger value than before.

8. Step by patterns:

a. On the Filter pane, click Clear Filter (    ).

b. On the Navigation pane, on the field at the top, change the step to PATTERN: Tutorial.

c. On the Navigation pane, select the first pattern listed.

This automatically groups the values for the first pattern, with allocation factors applied.

137 of 164
Importing, Exporting, and Linking

Comparing Multiple Patterns on a Plot

In this section, you create a plot that compares multiple patterns, applying pattern allocation factors.

1. On the Home tab, in the Launch analysis group, click Plot.

The Edit Plot window opens.

2. Below the main area of the window, click the Add Multiple Curves button.
The Add Multiple Curves window opens.

3. On the Category field, select Tutorial.

4. On the Variable field, select Win.Winj.

5. Click OK to close Add Multiple Curves window.

6. On the Edit Plot window, click OK to create the plot.

Creating Patterns from an ASCII File

If you have determined the allocation factors already and it is in a document or spreadsheet, you can
reformat the data and load it into OFM. The pattern data can be static or dynamic. For dynamic patterns,
the allocation factors may change over time as injectors are created and terminated. You can remove wells
from a pattern as new patterns are created. In this section, you add patterns to the project by loading a
formatted data file. They will be the same patterns that you created interactively.

1. Open Notepad or a similar text editor.

2. In a new text file, enter the following:

*Label Pattern

*WELL *Factor *Loss

*Set Tutorial

*Pattern "P-0"

*Date 19000101

"491WI:B" 1.000000 0.000000

"492WI:B" 0.500000 0.000000

"495:B" 1.000000 0.000000

"498WI:B" 1.000000 0.000000

"502WI:B" 0.500000 0.000000

*Pattern "P-1"

*Date 19000101

"492WI:B" 0.500000 0.000000

"493WI:B" 0.500000 0.000000

138 of 164
Importing, Exporting, and Linking

"496:B" 1.000000 0.000000

"502WI:B" 0.500000 0.000000

"503WI:B" 0.500000 0.000000

*Pattern "P-2"

*Date 19000101

"493WI:B" 0.500000 0.000000

"494WI:B" 1.000000 0.000000

"497:B" 1.000000 0.000000

"503WI:B" 0.500000 0.000000

"507WI:B" 1.000000 0.000000

3. Notice the following lines:

n The fourth line (*Pattern "P-0") is the pattern name.

n The third line (*Set Tutorial) is the Pattern Set name.

n The fifth line (*Date 19000101) is the effective date.

n The sixth line ("491WI:B" 1.000000 0.000000) is the wellname, factor, and loss. To remove a
well from a pattern at a specific date, change either the pattern allocation factor to zero, or set
the loss factor to 1.0.

4. Save the file with a .pat file extension and then close the text editor.

5. In OFM, on the Setup tab, in the Import/Export group, click Import > Data Loader.
The OFM Data Loader opens.

6. In the upper section, double-click the pattern (.pat) file you created.
The Files to Load section lists the file.

7. Click Load.
A warning message confirms your choice.

8. On the warning message, click OK.

The new patterns are loaded into your project. On the Navigation pane, OFM lists them with the
other patterns. OFM also lists them on the Edit Patterns window. (To see this window, on the
Setup tab, in the Workspace Managers group, click Patterns.)

139 of 164
Importing, Exporting, and Linking

Example: Using .Las Log Data

If you have a log ASCII standard (.las) file with log data, you can convert it to a .log file and then import the
.log file into your OFM project. The LAS to OFM tool converts the file for you.

In this example, you will:

n Get started, by making a copy of a sample .las file, setting Microsoft Excel to run macros, reviewing
the log data in the Demo database, and reviewing the log data you will import from the .las file.

n Create a log and a definition file with the LAS to OFM tool.

n Load the files into the Demo workspace.

n View the imported log data in a single well log display.

Getting Started
1. Make a copy of the sample .las file. It is in the OFM installation folder, at
...OfmPlus\Samples\Sample.las.

2. The Excel file that changes your .las file to a .log file uses a macro. You must have macros enabled in
Microsoft Excel:

a. In Excel, click the Office button in the upper-left corner and then click Excel Options.

b. In the Trust Center section, click Trust Center Settings.

The Trust Center window opens.

c. In the Macro Settings section, select Enable all macros and then click OK.

3. Review the log data in the Demo project:

a. Open the Demo workspace. It is in the OFM installation folder, at ...Sample Workspaces\Demo
Workspace\demo.ofm.

b. On the Setup tab, in the Tables group, click OFM-Defined.

c. Click Logs.

d. Note that the Logs window lists 16 traces. The first one is Acoustic, and the last one is TPhi.

4. Click OK to close the window.

5. View the log data in the .las file that you will import into the OFM project:

a. In Notepad, open the copy of the sample.las file.

b. Note the ~C section:

~C

DEPT.F 00 000 00 00: 1 DEPTH CURVE

DT.US/F 00 000 00 00: 2 SONIC TRAVEL TIME

140 of 164
Importing, Exporting, and Linking

RHOB.G/C3 42 350 02 00: 3 DENSITY-BULK DENSITY

NPHI.V/V 42 890 00 00: 4 POROSITY -NEUTRON

RXO.OHMM 07 220 01 00: 5 RESISTIVITY -RXO

SFLU.OHMM 07 222 01 00: 6 RESISTIVITY -SHALLOW

ILM.OHMM 07 120 44 00: 7 RESISTIVITY -MEDIUM

ILD.OHMM 07 120 46 00: 8 RESISTIVITY -DEEP

SP.MV 07 010 01 00: 9 SPON. POTENTIAL

GR.GAPI 42 310 01 00: 10 GAMMA RAY

CALI.IN 42 280 01 00: 11 CALIPER

DRHO.G/C3 42 356 01 00: 12 DELTA-RHO

EATT.DB/M 00 000 00 00: 13 EPT ATTENUATION

TPL.NS/M 00 000 00 00: 14 TP -EPT

PEF.B/E 42 358 01 00: 15 PHOTOELECTRIC FACTOR

FPHI.V/V 00 000 00 00: 16 POROSITY -NML FFI

The log traces you will import into the OFM project are DT, RHOB, NPHI, RXO, ILM, CALI,
DRHO, EATT, TPL, PEF, and FPHI. The demo project already has SFLU, ILD, SP, and GR.

c. Close the .las file.

Creating Log and Definition Files with the Tool

1. Open the LAS to OFM file, at ...OfmPlus\LAS to OFM.xls.

2. Click the Click to convert LAS log format (*.as) to OilField Manager log format (*.log)
button.

3. In the Input window, enter the version of Excel that you are using and then click OK.

4. Select the Sample.las file you copied.

5. In the Input window, enter the Wellbore ID you will use and then click OK: Red_9

6. Save the file to your computer with this name: LAStoLOG.log

7. In the Input window, type y and then click OK.

You type y (yes) if the .las file has traces in it that are not currently defined in the project. When
you type y, the LAS to OFM tool creates a definition (.def) file based on the converted curves that
you load into the project.

8. Save the file to your computer with this name: LAStoLOG.def

141 of 164
Importing, Exporting, and Linking

Loading the Log and Definition Files into the OFM Project
1. Return to the Demo project in OFM. On the Setup tab, in the Import/Export group, click Import
> Data Loader.

2. Double-click the LAStoLOG.def and LAStoLOG.log files to move them to the Files to Load
section.

3. Click Load.

4. On the Setup tab, in the Tables group, click OFM-Defined.

5. Click Logs.

6. Note that the Logs window now lists 27 traces. The imported traces are listed after TPhi. They start
with DT and end with FPHI.

7. Click OK to close the window.

8. Click OK to close the OFM Defined Table Manager.

Viewing the Log Data in a Single Well Log Display

1. On the Home tab, in the Launch analysis group, click Well Log.

2. On the Set Depth Range window, accept the default range. Click OK.
A blank log template for your single well log display opens.

The template has two tracks. A depth track (which shows the depth scale in the units of
measurement for the workspace) separates the two tracks. By default, each track can hold two
traces, which you add to the tracks. The trace name displays at the top of each track. To the left of
the trace name is the minimum trace value. To the right of the trace name is the maximum trace
value.

3. Double-click the top Trace Name for the left track.

The Log Trace Attributes window opens.

4. Make these selections and then click OK:

n Log: ILM

n Color: Green

5. Double-click the bottom Trace Name for the left track.

6. Make these selections and then click OK:

n Log: RHOB

n Color: Red

7. On the Navigation pane, select the Red_9 wellbore.

142 of 164
Importing, Exporting, and Linking

Example: Displaying Formation or Reservoir

Thickness and Structure
OFM can create effective isopach maps. In this example, you will:

1. Add a new table with depth and height data.

2. Create a contour map showing thickness.

3. Create a grid map showing thickness.

4. Create a contour map showing a pseudo top or bottom of the structure.

5. Display the thickness map on the base map.

Adding a New Table with Depth and Height Data

1. Open the Demo workspace. It is in the OFM installation folder, at ...Sample Workspaces\Demo
Workspace\demo.ofm.

2. You need a table and field to hold thickness data. Create the table:

a. On the Setup tab, in the Tables group, click Schema.

The Edit Schema Tables window opens.

b. Right-click the Demo data source and click Add.

c. Type Iso for the table name and then press Enter.
By default, OFM adds UniqueID and Date as the primary key fields, and the table is defined to
hold monthly data with a Completion key type.

d. On the Table tab, change the Table Type to Static.

e. OFM asks if you want to keep the Date field. Click No.

f. On the Fields tab, in the Add New Field field, enter Depth and then click Add.

g. In the Add New Field field, enter H and then click Add.
The Demo data source now has an Iso table. The primary key field is UniqueID. It has two other
fields: Depth and H.

h. On the OFM Representation pane, select the Depth field.

i. On the Units tab, select ft ==>m.

j. On the OFM Representation pane, select the H field.

k. On the Units tab, select ft ==>m.

l. Click OK to save your changes and close the window.

3. Add data to the new table:

143 of 164
Importing, Exporting, and Linking

a. Open Notepad.

b. Paste the following into a new file:

*TableName Iso
*UniqueID *Depth *H
"Blue_12:Li_1C" 6647 0
"Blue_3:Li_1C" 6440 0
"Blue_7:Li_1C" 6440 10
"Green_15:Li_1C" 6500 0
"Green_3:Li_1C" 6500 0
"Green_5:Li_1C" 6441 40
"Orange_16:Li_1C" 6460 10
"Orange_24:Cl_3" 6470 20
"Purple_1:Cl_3" 6494 0
"Red_13:Cl_3" 6495 0
"Red_4:Cl_3" 64980 0

c. Save the file with this name: Iso.dat

d. On the Setup tab, in the Import/Export group, click Import > Data Loader.

e. Double-click the Iso.dat file to move it to the Files to Load section, and then click Load.

Creating a Contour Map Showing Thickness

1. On the Filter pane, expand Table Data and then select the new Iso table to show only the
completions with data in that table.

2. On the Home tab, in the Launch analysis group, click Contour.

3. On the list of Project variables, double-click Iso.H to move it to the Selected variables list.

4. Click Finish.
The contour map displays the thickness.

5. Improve the appearance of the contour map:

a. On the Properties pane, under Properties, in the GRID section make these selections:

Number of Neighbors: 2

Maximum Grid Size: 14

Search Radius: 304801

b. On the Properties pane, under Properties, in the 2D section make these selections:

Show: Yes

Decimal Places: 0

Distance Between Labels: 10

144 of 164
Importing, Exporting, and Linking

c. On the Properties pane, under Grids and Limits, change Grid Type to None.

6. On the Analysis pane, right-click the contour map and then click Rename.

7. Type this for the new name and then press Enter: Net Sand Thickness - Contour Map

Creating a Grid Map Showing Thickness

1. On the Analysis pane, right-click the contour map and then click Clone Map As > Grid Map.
OFM creates a new grid map displaying the same variable as the contour map.

2. On the Properties pane, under Variable Properties, change Exclude out of range to Yes.

3. On the Properties pane, under Grids and Limits, change Grid Type to Frame.

145 of 164
Importing, Exporting, and Linking

4. On the Analysis pane, right-click the grid map and then click Rename.

5. Type this for the new name and then press Enter: Net Sand Thickness - Grid Map

Creating a Contour Map Showing a Pseudo Top or Bottom of the

Structure
1. On the Analysis pane, right-click Net Sand Thickness - Contour Map and then click Save As
New Node.
OFM makes a copy of the map.

2. On the Analysis pane, right-click the copy and then click Rename.

3. Type this for the new name and then press Enter: Pseudo Structure

4. With the Pseudo Structure map open, on the Format tab, in the Edit group, click Variables.

5. Remove the Iso.H variable from the Selected variables list, and double-click Iso.Depth to add it
to the Selected variables list.

6. Click Finish.

146 of 164
Importing, Exporting, and Linking

Displaying the Thickness Map on the Base Map

1. Close the Pseudo Structure map and open the Net Sand Thickness - Contour Map.

2. On the Format tab, in the Utilities group, click Save Analysis > Save As.

3. Change the Save as type to Annotation Files and then save the file with this name:
NetSandThickness.ano

4. View the base map.

5. On the Format tab, in the Display group, click Annotations.

The Map Annotations window opens.

6. Click Add.
The Data Loader opens.

7. Double-click the NetSandThickness.ano file to move it to the Files list, and then click Load.

8. On the Map Annotations window, click OK.

The thickness map you originally created as a contour map displays as an annotation on the base
map.

147 of 164
Importing, Exporting, and Linking

Example: Calculating Pressure from P/Z and

Production Data
This example shows how to use user functions in OFM. Among other things, you can use user functions to
execute iterative calculations. In this example, you execute iterative calculations to create a continuous
stream of pressure data, using a combination of sporadic pressures, production data, and a P/Z line. To do
this, you will:

1. Add sporadic pressure data to the monthly production table.

2. Create a user function to calculate the pressure that corresponds to the P/Z line at any given time.

3. Create two calculated variables:

n Fitted P/Z value

n Calculated pressure from a fitted P/Z curve

4. Create a plot to compare reservoir pressure to the fitted pressure.

Adding Sporadic Pressure Data

1. Open the Demo workspace. It is in the OFM installation folder, at ...Sample Workspaces\Demo
Workspace\demo.ofm.

2. In this workspace pressure data is stored in the MonthlyProd table. The table has a field for pressure
data, but does not have data. Add pressure data:

a. On the Setup tab, in the Tables group, click Data Grid.

The Select OFM Table to Edit window opens.

b. Select the MonthlyProd table and then click OK.

c. On the Navigation pane, select the Blue_1:Ge_6 completion.

d. In the Pressure column, add the following pressure data:

For this date... Enter this pressure...

12/1/1999 5000
1/1/2000 4789
2/1/2000 4234
3/1/2000 4123
4/1/2000 3900
5/1/2000 3876
6/1/2000 3768

e. Close the data grid to save your entries.

148 of 164
Importing, Exporting, and Linking

Creating a User Function to Calculate the Pressure

Corresponding to Any Point on a P/Z Line
1. On the Setup tab, in the Variable Managers group, click User Functions.
The User Functions window opens.

2. In the top field, enter the name of your new user function: Pcalc

3. Click Add.
The Edit User Function window opens. The name of the user function displays in the text field at
the top of the window.

4. This user function will take one input, which is a parameter that represents a P/Z value. It also will
create five temporary variables for the calculation. So, the first lines are this:

Pcalc(PZ)
num Zold, Znew, Pnew, DeltaZ, loops;

5. You then set the initial values. The next two lines are:

DeltaZ=1;
Zold=1;
loops=0;

6. The calculation has a loop. On the next lines, set the exit criteria for the loop:

while(DeltaZ > 0.001 & loops < 50)

7. At the end of one loop pass, a variable increments by 1. The next lines are:

{
loops=loops+1;

8. Inside the loop, the following takes place:

a. Pressure (P) is calculated at a Z value of 1.

b. The Z value is re-evaluated at this pressure.

c. The new Z value is used to re-calculate P (in step a).

d. These steps are repeated until the re-evaluated value of Z has not changed the value of Z by
more than 0.001. In other words, the function has converged, and it outputs its result, which is
the current value of P.

To do this, the next lines of the user function are:

Pnew=PZ*Zold;

Znew=@PvtZ(Pnew);

DeltaZ = @abs(Zold-Znew);

149 of 164
Importing, Exporting, and Linking

Zold=Znew;
}

Pcalc= Pnew;

9. Double-check your user function. It should be:

Pcalc(PZ)

num Zold, Znew, Pnew, DeltaZ, loops;

DeltaZ=1;

Zold=1;

loops=0;

while(DeltaZ > 0.001 & loops < 50)

loops=loops+1;

Pnew=PZ*Zold;

Znew=@PVTZ(Pnew);

DeltaZ = @abs(Zold-Znew);

Zold=Znew;

Pcalc= Pnew;

10. Click OK.

11. On the Edit User Function window, click Close.

Finding the P/Z Value

1. On the Setup tab, in the Variable Managers group, click Calculated Variable Editor.
The Variable Editor opens with a list of all calculated variables.

2. Click Add Calculated Variable.

The calculated variable will use the @Fit system function, which fits a polynomial of n order
through the data. When you use this system function, you identify:

n The X-axis parameter for the dataset being fitted (in this case, cv.cumgas)

n The Y-axis parameter for the dataset being fitted (in this case, cv.pz)

n A true/false condition that excludes a value if the condition is false (in this case, you exclude a
value if cv.pz is greater than 0)

n The X-axis parameter for the output fitted curve (in this case, cv.cumgas)

n An option (in this case, the order of the fitted polynomial, which is 1 linear)

150 of 164
Importing, Exporting, and Linking

In this workspace, PZ is already defined as a calculated variable.

3. Double-click the items in the System Functions and Project Variables lists to add this equation
to the text box at the top of the window: @Fit( Gas.cum, pz, pz>0, Gas.cum,"Deg 1 linear")

4. Click OK.
The new variable displays on the list of variables. By default, OFM names it NewItem.

5. Type this new name for the calculated variable and then press Enter: Fit.PZ

6. Set plot attributes for the new calculated variable:

a. At the top of the window, click Define to hide the definition columns, and click Plot to show the
plot attribute columns.

b. On the row for the new Fit.PZ calculated variable, for Curve Name select Fit P/Z.

7. Set report attributes for the new calculated variable:

a. At the top of the window, click Plot to hide the plot attribute columns and click Report to show
the report columns.

b. On the row for Fit.PZ, make these selections:

Report Heading 1: Fitted

Report Heading 2: Pressure

Report Heading 3: from P/Z

8. Set unit attributes for the new calculated variable:

a. At the top of the window, click Report to hide those columns and click Units to show the units
columns.

b. On the row for Fit.PZ, for Units select psig ==> bar.

c. You need to use this calculated variable in the next calculated variable you will create. It is not
available until you save your changes. Click OK to save your changes and close the Variable
Editor.

Calculating the Pressure from a Fitted P/Z Curve

1. Reopen the Variable Editor: On the Setup tab, in the Variable Managers group, click
Calculated Variable Editor.

2. Click Add Calculated Variable.

3. The calculated variable will use the user function you created with the Fit.Pz calculated variable you
created. Double-click the items in the User Functions and Project Variables lists to add this
equation to the text box at the top of the window: #PCalc(FIT.PZ)

4. Click OK.

151 of 164
Importing, Exporting, and Linking

5. Type this for the name of the calculated variable and then press Enter: Fit.Press_PZ

6. Set plot attributes for the new calculated variable:

a. Click Define to hide the definition columns and click Plot to show the plot attribute columns.

b. On the row for Fit.Press_PZ, make these selections:

Curve Name: Fitted Pressure from P/Z

Curve Line Color: Red

7. Click OK to save the calculated variable and close the window.

Comparing the Reservoir Pressure to the Fitted Pressure from

the Fitted P/Z Curve
1. On the Navigation pane, select the BLUE_1:Ge_6 completion.

2. On the Home tab, in the Launch analysis group, click Plot.

The Edit Plot window opens.

3. You will create a plot with two graphs. In the Graph section, set the Number of Graphs to 2.

4. Make selections for the first graph:

a. In the Graph section, for the Current Graph select Graph 1.

b. For the X-Axis Variable, select Gas.Cum.

c. In the curve section, select the Fit.PZ variable, Current category, and BLUE_1:Ge_6 name.

d. Click Add Curve.

e. For the second curve, select the PZ variable, Current category, and BLUE_1:Ge_6 name.

5. Make selections for the second graph:

a. In the Graph section, change the Current Graph to Graph 2.

b. For the X-Axis Variable, select Date.

c. In the curve section, select the Fit.Press_PZ variable, the Current category, and the BLUE_
1:Ge_6 name.

d. Click Add Curve.

e. For the second curve, select the Monthlyprod.Pressure variable, the Current category, and
the BLUE_1:Ge_6 name.

f. Click OK.

6. Change the scale type for the top graph:

152 of 164
Importing, Exporting, and Linking

a. On the top graph, click the X-axis.

b. On the Properties pane, under Axis, change the Scale Type to Linear.

153 of 164
Importing, Exporting, and Linking

@Fit (Fit) System Function

Description This system function fits a polynomial of order n through the data,
using the least squares method. It can be used across tables and n can
equal up to 12 degrees.
Syntax @Fit (value1, value2, value3, value4, option)
Where Argument Type Required Description
Numeric The X-axis parameter for the
value1 Yes
or date dataset being fitted
The Y-axis parameter for the
value2 Numeric Yes
dataset being fitted
Condition; any value evaluating as
value3 True/False Yes
False will be excluded from the fit
Numeric The X-axis parameter for the output
value4 Yes
or date fitted curve
n Date: Use if the input X-axis
parameter represents date

n Xlog: Use if the curve is to be

fitted to the logarithm of X

n Ylog: Use if the curve is to be

fitted to the logarithm of Y

n deg: Order, n, of fitted

polynomial, where n should not
exceed 12

option Several Yes n min val: If any resulting fitted

value is less than val, then
function returns a Null

n max val: If any resulting fitted

value is greater than val, then
function returns a Null

n opt: Finds the best value for n

(between 1 and 12)

n abs val: Fit the curve. Exclude

the point if abs (resulting data) >
val, then refit the curve
Example In this example, the function returns an array of points evaluating the
fourth degree polynomial fit to monthly oil production, subject to the
constraint that values below 500 are not reported:

@fit(Date, Prd.oil, Prd.oil>0, Date, "Date deg 4 min 500")

154 of 164
Importing, Exporting, and Linking

Related Examples
Calculating Pressure from P/Z and Production Data: Finding the P/Z Value

Creating a Water Breakthrough Diagnostic (Chan) Plot: Fitting the WOR Derivative

Creating a Water Breakthrough Diagnostic (Chan) Plot: Fitting the WOR

Fitting a Polynomial Curve Through Plot Data and Displaying Its Equation: Fitting a Polynomial Curve

155 of 164
Importing, Exporting, and Linking

@Reg (Value in a Data Register) System

Function
Description This system function recalls a value (for a variable used to represent
parameter Y) stored in the specified Data Register and interpolates
missing values.
Syntax @Reg (regn#, value, "option")
Where Argument Type Required Description
regn# Numeric Yes Data Register number (1-40)
Variable representing the X
value Numeric Yes parameter used when creating the
Data Register
n xlog: Performs lookup along X-axis

n ylog: Performs lookup along Y-axis

n linear: Performs linear

interpolation

n lag: Performs lookup Lagrange

interpolation

"option" String No n deg: Specifies degree of Lagrange

polynomial

n step up: Performs lookup

returning upward value

n step down: Performs lookup

returning lower value

n in: Value must exist within range.

Do not extrapolate.
Example In this example, Data Register 5 was previously created to store a
variable (Y), representing bottomhole pressure against Date (X). The
example will return the values of bottomhole pressure, and linearly
interpolate across missing values.

@Reg (5, Date, "date linear")

156 of 164
Importing, Exporting, and Linking

@PvtBo (Oil Formation Volume Factor)

System Function
Description This system function calculates the time-dependent oil formation
volume factor at a specified time-dependent pressure.
Syntax @PvtBo (value)
Where Argument Type Required Description
value Numeric Yes Pressure value
Example In this example, the system function returns a time-dependent oil
formation volume factor based on time-dependent pressure data:

@pvtBo(Prd.Pressure)

Related Tutorials
PVT: To Use PVT System Functions

157 of 164
Importing, Exporting, and Linking

@PvtBg (Gas Formation Volume Factor at a

Pressure) System Function
Description This system function calculates the gas formation volume factor at a
specified pressure.
Syntax @PvtBg (value)
Where Argument Type Required Description
value Numeric Yes Pressure value
Example In this example, the system function returns a time-dependent gas
formation volume factor based on time-dependent pressure data:

@PvtBg(Prd.Pressure)

158 of 164
Importing, Exporting, and Linking

@PvtBw (Water Formation Volume Factor at

a Pressure) System Function
Description This system function calculates the time-dependent water formation
volume factor at a specified time-dependent pressure.
Syntax @PvtBw (value)
Where Argument Type Required Description
value Numeric Yes Pressure value
Example In this example, the system function returns a time-dependent water
formation volume factor based on time-dependent pressure data:

@pvtBw(Prd.Pressure)

159 of 164
Importing, Exporting, and Linking

@PvtRs (Calculate the Solution Gas-Oil

Ratio at a Pressure) System Function
Description This system function calculates the solution gas-oil ratio (GOR) at a
specified pressure, based on the previously selected oil correlation.
Syntax @PvtRs (value)
Where Argument Type Required Description
value Numeric Yes Pressure value
Example In this example, the system function returns time-dependent solution
gas oil ratio based on time-dependent pressure data:

@PvtRs (Prd.Pressure)

160 of 164
Importing, Exporting, and Linking

@Lookup (Lookup) System Function

Description This system function searches or interpolates the lookup table for a
specific value of a specified variable. It offers a lookup capability, and
allows for interpolation between recorded values.

Note: Interpolation requires that the range to be interpolated must

be in strict ascending order.
Syntax @Lookup (output_variable, keyname, input_value, option)
Where Argument Type Required Description
output_ The result you wish to extract from
Numeric Yes
variable the lookup table
The entity for which your lookup table
keyname Text Yes
has been populated with data
The value of the independent variable
input_
Numeric Yes for which you require the lookup
value
result
option Text Yes See Options list, below
Options Combinations of options are permitted, where applicable (for example,
"date deg4 in" specifies a 4th order polynomial interpolation of time
dependent lookup data, prohibiting extrapolation outside the range of
existing data).

n date: Used when input_value refers to a date.

n xlog: For interpolation, specifies that the x axis scale is logarithmic.

n ylog: For interpolation, specifies that the y axis scale is logarithmic.

n linear: Performs linear interpolation between known values of

data.

n lag: Performs Lagrange interpolation.

n deg: Specifies degree of the Lagrange polynomial (for example,

"deg3").

n step up: No interpolation; function returns the previous value of

output_variable.

n step down: No interpolation; function returns the next value of

output_variable.

n in: Value must exist within range; do not extrapolate.

Example 1 In this example, the function returns the oil price from the Cost table,
for the entity Sand1 at the corresponding date:

@Lookup (cost.oilprice, "sand1", date, "Date")

161 of 164
Importing, Exporting, and Linking

Example 2 In this example, the function returns the formation volume factor
(FVF) from the Fluid_Data table, for the Reservoir to which the
currently loaded completion belongs, at a pressure value provided by
Prd.Pressure, allowing linear interpolation at pressure values for which
the fluid data does not exist in the table. Note there is no time
dependency for the lookup table data in this example.

@Lookup (Fluid_Data.FVF, “Sc.Reservoir”, Prd.Pressure,

“lin”)

162 of 164