Fundamentals
Training and Exercise Guide
Version 2005.1
Schlumberger Information Solutions May 11, 2005
© 2005 Schlumberger. All rights reserved.
No part of this manual may be reproduced, stored in a retrieval system, or translated in any form or by any means, electronic or mechanical, including photocopying and recording, without the prior written permission of Schlumberger Information Solutions, 5599 San Felipe, Suite 1700, Houston, TX 77056-2722.
Disclaimer
The License Agreement governs use of this product. Schlumberger makes no warranties, express, implied, or statutory, with respect to the product described herein and disclaims without limitation any warranties of merchantability or fitness for a particular purpose. Schlumberger reserves the right to revise the information in this manual at any time without notice.
Trademark Information
GeoFrame™, StratLog™, WellPix™, WellEdit™, WellSketch™, and CPS- 3™ are trademarks of Schlumberger. Certain other products and product names are trademarks or registered trademarks of their respective companies or organizations.
Preface ...iv
Chapter 1
OFM Basics ... 1
Learning Objectives ... 1
What You Will Need... 1
What to Expect... 1
OFM Database... 2
OFM Workspace... 7
Chapter 2
Project Creation... 11
Learning Objectives ... 11
OFM Table Types ... 11
OFM Project Creation ... 13
OFM Loadable Text File Formats ... 13
Static Data ... 19
Monthly Data ... 19
Daily Data ... 20
Sporadic Data... 20
From an Existing Access Database ... 30
Chapter 3
Project Administration... 67
Project Panes... 67
Learning Objectives ... 67
Changing the Layout... 67
Editing the Database... 70
OFM Units ... 71
Multipliers ... 72
PVT Data... 73
Editing Project Structure ... 73
Editing Schema Table... 73
Editing Categories... 78
Chapter 4
Basemap Customization... 80
Learning Objectives... 80
Map Association Data ... 80
Map Display ... 83
Map Annotations... 90
Displaying Deviation Information... 94
Irregular Zoom ... 96
Create New Annotations ... 97
Edit Annotations... 98
Chapter 5
Filtering...103
Learning Objectives... 104
Filter by Completion... 104
Filter by Table Data ... 108
Filter by Category ... 109 Filter by Match ... 111 Filter by Query ... 113 Others ... 119 Well List ... 122 Scatter Set... 122 Filter Archive ... 122 Step... 124 Project Filter... 124
Chapter 6
Project Variables ...130
Learning Objectives... 131 Calculated Field ... 131 Calculated Variables... 135 Ratio Variable... 135
Chapter 7
Plotting ...155
Plotting Basics ... 155 Learning Objectives... 155Creating a Graph with One Y-Axis... 156
Creating a Graph with Two Y-Axes ... 164
Using Plot Lock and Graph Blow Up Options...171
Creating Stacked Plot Entities ...174
Creating Stacked Plot on Variables...176
Using Sum/Average/% Contribution Types ...179
Creating Plot Overlay...184
Using Plot Annotations ...186
Using Plot-Related Tools/Utilities ...190
Chapter 8
Reporting... 197
Prerequisites ...197
Learning Objectives ...197
Using OFM Report...197
Reporting Variables ...199
Formatting a Report...205
Additional Report Tools ...210
Chapter 9
Exporting ... 223
Learning Objectives ...223
Exporting Database Tables ...223
Exporting Variables to Table ...224
Exporting Text Load Files...225
Chapter 10 OFM Tools and Settings ... 229
Learning Objectives ...229
Project Settings ...229
Grouping Data by Date ...232
Data Normalization ...235
Data Register ...238
OilField Manager (OFM) is a powerful surveillance software application that has been widely used by professionals in the oil industry. It provides an array of tools for managing and analyzing production data.
OFM installation set includes a revised and updated (online) help file, structured by subtopic(s) and keyword(s). Users can also utilize the award-winning support that Schlumberger Information Solutions offers to all Schlumberger Information Solutions customers.
The focus will be on providing participants with as much hands-on experience as possible. To reduce the repeated usage of terminology, participants are encouraged to use the help file. This training material should give enough knowledge to perform basic functionalities that OFM supports.
Note: Advanced training with OFM is addressed in other courses, which can
be taken upon completion of this course. A few things regarding terminology:
• If not specifically stated, the word “application” refers to OFM. • If not specifically stated, the word “database” refers to the OFM
Chapter 1 OFM Basics
This section of the tutorial addresses the overall structure of the OFM
database and workspace. Its sole purpose is to help you understand the basic architecture of the OFM database so that you can correctly create your OFM projects.
Learning Objectives
In this module, you will successfully learn how to perform the following procedures:
• Analyze OFM data tables
• Describe the design of the OFM tables (including keys) • Explain the DOs and DON’Ts of specific types of OFM tables • Create OFM workspace
• Create or attach OFM database to a workspace
What You Will Need
Besides having OFM properly installed and licensed, it is
recommended that you have Microsoft Access installed so you can view the OFM database. For more information, please consult the Online Help and the Reference Guide.
What to Expect
In this training, you will encounter the following: • Overview of the OFM database
• Prerequisites to the module (if necessary) • Learning objectives
• Lesson(s)
• Summary of the module • Questions about the module • Scenario-based exercises • Notes and best practice
OFM Database
OFM can be viewed as having two integrated layers - database and application. Basically, the database layer handles the data part; and the application controls the user interface, as well as the processing
data/information per request. OFM database is Microsoft Access-based. All data/information are stored in tables (and sometimes views). Therefore, OFM database has all the characteristics of a relational database, including
constraints, keys, and indices. There are three main classes (types) of tables in an OFM database:
• Data Table
• System and Configuration Table • OFM-Managed Table
OFM Data Tables
As the name suggests, these tables contain data. Most of the tables must have at least one key (primary key) and may contain constraint and indexing information. Each table has two or more fields, which have designated data types (i.e. date/time, number, or text) and size (i.e. long integer, double precision for number field, or 20 space wide for text field). By assigning the correct data types and sizes, you can assure no unexpected loss of data (in case of truncating, rounding-off) at load time. OFM data tables are not named with either the “_OFM_SYS” or the “OFM_DATA_” prefixes. For example, a table to store time-independent data may resemble the image pictured below.
In the above example, the UNIQUEID field is a text field that is 20 characters wide. In addition, it is designated as the primary key field in this HEADERID table (indicated by the key icon in the left). Also, as it is the primary key of the table (and later you will know that it is the master key of the OFM project) it carries additional properties (seen in the lower section, General tab). Please reference Relational Database concepts for further information.
There are many fields in this table that are number (numeric) fields. For example, if you select the XCOOR field from the list, you would see the following:
In the above example, the XCOOR field is a number field, with double
precision and no decimal place assigned in display. Also, it is not indexed and can accept a null value.
By design, OFM requires the designation of a “MASTER” table, which
normally stores static well information such as “Well Alias”, “Well Coordinates”, etc… The primary key of this master table is the main (MASTER) key of the whole OFM project. HEADERID table in the above example is a master table. Many other data tables may contain more than one keyed field. For example, a date-dependent table must have at least two keys, one is the “entity” key (similar to the UNIQUEID key); the other is the “date” key. Let’s take a look at a “monthly” frequency table:
As seen above, this MONTHLYPROD table has two keys. The UNIQUEID key joins this MONTHLYPROD table to the HEADERID table, in a relational manner. However, the primary “entity” key of one table does not have to be identical to the primary “entity” key (master key) of the OFM project. As long as a relationship (join) can be established between the two tables (normally via an intermediate field – could be a foreign key), there is no violation in the design of the OFM database. For example, if you have a table like this:
This can be joined to the HEADERID table as long as there exists a way to relate Reservoir (in this RES_PROD table) to the UNIQUEID field in the HEADERID table. In this illustrative database, there is a table that contains such valuable information.
Note: You do not have to physically make the joins between the tables. At
project creation time, OFM can generate all the necessary joins to ensure the data integrity.The data tables store data that have got loaded into the project. Please take a look at a few data tables to experiment.
Exercise 1
Explore Other Data Tables
Explore the other data tables in the Demo200x.mdb, at least the
DAILYPROD, the TEST, the CHOKE tables. How many keys are there in the CHOKE table? Which key is the (primary) “entity” key?
Your instructor will explain why the CHOKE table is a special type of table in OFM.
There is a special type of data table named “XXX_Adjustments”; these tables store “pre-cum” (or prior cumulative production) data for the respective date-dependent tables (with the “XXX” name). Your instructor will explain why this special table type is needed.
OFM System and Configuration Tables
OFM system and configuration tables are preceded with the “_OFM_SYS” prefix. Their names cannot be changed at all. They are automatically created when the OFM project is created. These tables store specific information such as calculated variable definition, user function definition, interface
customization information, project configuration information, etc… There are eight (8) such tables in any OFM database, namely:
• _OFM_SYS_Configuration (for configuration information) • _OFM_SYS_DateRange (for User’s Date Range)
• _OFM_SYS_Multipliers (User’s Multipliers)
• _OFM_SYS_Parser (Calculated Variables and User Functions) • _OFM_SYS_TableInfo (Table information)
• _OFM_SYS_TableMap (Table Mapping/Map Association Schema) • _OFM_SYS_Units (User’s Units)
These tables contain critical information for OFM to function normally. Therefore, it is strongly advised that you do not tamper with these tables as any inappropriate modifications to these tables may cause OFM not to launch and run properly.
Exercise 2
Exercise 3
OFM System and Configuration Tables
In Microsoft Access, open and study the OFM system and configuration tables. DO NOT make any changes!Your instructor can explain more about the usage of these tables.
OFM Managed Tables
The other tables in an OFM database (preceded by the OFM_DATA_ prefix) are classified as OFM-managed tables; they all store data (either loaded/input data or the results of OFM analyses), as the name suggests.
One set of these tables stores DCA (Decline Curve Analysis, or Forecast) related information. These tables are also automatically created at the project creation time. Yet they may not contain any data until a forecast task has been performed in the project. The names of these tables cannot be changed. The other set of the tables contains Log, Deviation Survey, Wellbore
Schematics, and Marker information, among others. Some of their table names can be changed. However, it is also recommended that you keep these names to guarantee the normal behavior of the program/project. Even though these tables basically are data tables, the data that got stored in most of these tables are very sensitive to changes. Therefore, it is strongly advised that you do not change the data in these tables unless you are very confident with the program, the data, and definitely with your decision.
Studying Managed Tables
In Microsoft Access, open and study the OFM managed tables.Note: The Log table (i.e. OFM_DATA_LOG) stores binary data object (i.e.
BLOB). Therefore, there is absolutely no change to the data value (trace value) in this table.OFM Workspace
OFM project consists of two parts: the project workspace and the project database.
At project creation time, both the project workspace and the project database can be created. Then data must be loaded into the project.
If the project database has already existed, only the project workspace needs to be created. Then the database will be associated (attached) to it.
The following exercises demonstrate the steps to create a new project workspace, associate a database to that workspace, and change the database in a workspace.
Creating Workspace
1. From the File menu select New Workspace.
2. Click the “browse” icon to the right of the Workspace File text box and specify a directory (folder) for the new OFM project.
3. Enter the desired name in the File Name box and click OK.
Changing Database
Click on the “browse” icon to the right of the Database
1. Click the “browse” icon to the right of the Database File text box. 2. Locate the Program Directory (if you installed OFM to C:\ProgramFiles\OFM 2005\, then that is the Program Directory), then go to Sample Databases>Demo Database and select the Demo2005.mdb from the list. Click OK. The New OFM Workspace window displays:
3. Leave the rest unchanged and click OK. The OFM project (workspace) has been created and basemap displays.
Change the Well Symbol Size
Change the well symbol size to 1.5 (from Edit>Map>Symbols). If you need clarifications, please do not hesitate to ask your instructor.
Changing the Database in a Workspace
1. Select the Base Map1 from the Analysis pane. From the Database menu, select Change.
2. Locate the Program Directory, then go to Sample Databases>Pilot Waterflood Sample and select the Pilot Waterflood Bfield.mdb.
3. Click Open. The basemap of the Pilot Waterflood Bfield database displays.
4. Select the Plot1 node from the Analysis pane. Group the data, and the plot displays.
Note: Notice that the basemap header, well symbols, and the plot template
are on the workspace level, independent on the database. This is the advantage of having created a workspace that pulls data from various identically designed databases.Exercise 4
Delete the Plot1 Node
Change the database back to Demo2005.mdb. Delete the Plot1 node and resize the well symbol from 1.5 back to 1.
Note: If you choose to create a brand new database at project creation time,
you will have to populate the data in the next steps (after Step 5). OFM supports various methods of “loading” data to the OFM project, such as using the Data Loader or using the Linked Tables method. The next module demonstrates such functionalities.Chapter 2 Project Creation
In this module, we will cover the most common ways to create and get data into an OFM project. The structure of the project should be carefully designed before actually launching the first creation step.
Before getting to the actual data populating exercises, it would be useful to understand the OFM data table types and specifications. In this module you will learn to:
• Analyze table types
• Populate project with ASCII data files (OFM formats) • Populate project with ASCII data files (PI/Dwights formats) • Link the project with data from external ODBC sources
Note: Specifying incorrect table types when loading and/or linking data may
result in losing or changing data.Learning Objectives
In this module, you will successfully learn how to perform the following procedures within this workflow:
• Design your OFM tables
• Load OFM formatted data to a project
• Load selected PI/Dwights formatted data to a project
• Create OFM project from an existing Microsoft Access database • Link OFM projects to external data source using the Linked Tables
method
OFM Table Types
OFM data are stored in Microsoft Access tables, which follow relational
database design concepts. In addition, OFM tables have their own constraints and properties understanding their structures to correctly construct the project will not only save you time, but also guarantee the normal behavior and data integrity of your created project.
The following summary table provides information about the most commonly used OFM tables:
Table Type Number of
Keys Key Types Key Data Types Comments
MASTER 1 -
Completion Entity MUST also be of STATIC type. The master (entity) key (also called completion) is preferably Text (String)
STATIC 1 Entity The key could be either
completion or foreign key
DAILY 2 Entity
Date Date
At most 1 record per day per entity.
MONTHLY 2 Entity
Date Date
At most 1 record per month per entity (day value is not considered)
SPORADIC 2 Entity
Prm. Key Num/Date
At most 1 record per day per entity SPORADIC DUALKEY 3 Entity Prm. Key Sec. Key Num/Date Num
Intra-day records per entity are allowed LOG 3 Entity Name Date Text Date
Entity key MUST be
“Wellbore”. Name key is the “trace name”
MARKER 2 Entity
Name Text
Entity key MUST be “Wellbore”.
Name key is the marker name
FAULT 2 Entity
Name Text
Entity key MUST be “Wellbore”.
Name key is the fault name
DEVIATION 2 Entity
Depth Num
Entity key MUST be “Wellbore”.
NOTES 2 Entity
Date Date
The entity key could be of any level PATTERN 4 PatternSet PatternName Date Entity Text Text Date Completion LOOKUP 2 Entity Prm. Key Num
The entity key could be of any level. Fields in lookup table MUST all be numeric. XREF (cross
reference) 1 Entity The entity key could be of any level
WBD
(wellbore diagram)
This OFM table corresponds to 4 separate tables in Access, each one has different key requirement. For more information, please reference the OFM_DATA_WBD_XXX tables in Microsoft Access
OFM Project Creation
An OFM project can be created from a variety of methods:
• Directly built from its original Access database (in this case, OFM will create the system tables needed). The Access database in this case is called the native database.
• Linked to any ODBC compliant database using the Linked Table(s) method or ODBC (Open Database Connectivity).
• Built from a reasonable list of widely used templates and specially formatted data sources such as PI/Dwights dmp2 production files. • Designed interactively via a step-by-step procedure, giving users the
customization capability.
• Created using its most conventional method, ASCII flat files. In this module, you will learn the ASCII flat files, the PI/Dwights dmp2 production files, the “native” Access, and the Linked Tables ways of creating OFM project.
OFM Loadable Text File Formats
In this section, you will learn the formats of OFM loadable text (ASCII) files for various table types. You will then create a new OFM project from the text files (provided in the installed program directory).
You MUST load the definition file and the (master) key data file (in that order) first. Most of the ASCII data files do not have to be loaded into your OFM project in order. Load the table definition file (for one or many tables) before loading the data files for those tables. If you choose to create the tables interactively (without using the definition files), they MUST exist before the data files can be loaded. This is also true if you want to load data into a group table (different entity key than the key in the master table), as you must define that group entity before OFM can load the data. For example, if you want to load production data at the reservoir level into a table called “RES_PROD”, the reservoir entity has to be associated (as a sort category, a foreign key, a wellbore, etc) before load time. The table definition for that table also has to be created beforehand.
Tips:
• Most of the time, each data file contains information of only one table. • Multiple data files can be loaded into one table (appending).
• One definition file can hold information of one or more tables. • Multiple files (definition and data) can be loaded to the project at the
same time.
OFM automatically recognizes the table types if the text load files have some specific extensions. If the data files don’t have the commonly used extensions
that OFM expects, they will be treated as typical data files, and will be parsed into the specified tables. Here are some commonly used file extensions:
• *.def – table definition file • *.xy – master (key) data • *.srt – sort category data • *.dly – daily frequency data • *.prd – monthly frequency data • *.tst – test (sporadic) data • *.lku – lookup data
• *.xrf – cross-reference data
• *.par – parser (i.e. calculated variable) data • *.dev – deviation data
• *.not – note (i.e. plot annotation) data • *.flt – fault data
• *.log – log (trace) data • *.mrk – marker data
• *.wbd – wellbore diagram data • *.pat – pattern data
• *.ano – map annotation data
We have constantly used the terms “definition file” and “data file”. Not all the tables in OFM require table definitions before load time. Those tables are called “non-defined” tables, in contrast to “defined” tables. They are:
• Deviation table • Fault table
• Marker table Sort category (filter) table • Pattern table
• Wellbore diagram table • Parser table*
*Parser table is not a typical table in many ways, even though parser information does get stored in a table.
Note: Sometimes, map annotations files are regarded as “non-defined”.
However, there is no particular table for this type of information.Viewing the (ASCII) Text Load Files
Definition FileOFM does expect the text files to follow certain file formats so that it can read and write the data to the database correctly. The files have to contain keywords to designate/separate all information stored in the files. A
comprehensive list of all keywords can be searched from the on-line help file provided with the application. In this procedure, we will study the
characteristics of some important table definition and data files in the “Demo” project (usually located in \\…\Sample Databases\Demo Database\Text Load Files\ directory, where \\…\ denotes your installed OFM program directory)
1. Launch a text editor such as Notepad or WordPad. (If you have already associated the application with the file extension, you can open the file directly from Windows Explorer).
2. Select File>Open from the menu.
3. In the Open Window, select All Files or All Documents from the Files of Type drop-down list.
4. Locate the \Sample Databases\Demo Database\Text Load Files\ from your program directory.
5. Select Demo Definitions File.def.
6. Click Open. and the definition file displays as shown below (partial file only):
Notes:
• The *Tablename keyword marks the first instance beginning of the table definition. The file format is space separated; therefore whatever text between the two spaces (consecutive spaces are treated as one) follows this keyword will be the name of the table.
• The next word denotes the table type. In this case, the HEADERID table is a static table. More importantly it is the master table. A project can have as many static tables as desired, but there is only one master table. The next word specifies that HEADERID is a master table.
• In the fields/variables section, each field is assigned a data type, text or numeric (with size). As many other PC applications, OFM has several precision specific numeric types such as INT2, FLOAT, DOUBLE, etc …
• In the definition file, the field’s attributes can be assigned, identified by the keywords such as *pn for Plot Name, *pa for Plot Attribute, *u for Unit, and *mu for Multiplier. These attribute keywords can be searched from the help file.
example, a Spanish speaking user can select to use FECHA for date; the user has to insert *DateLabel FECHA at the top of this definition file. Another Project Settings keyword you may see quite often is *Metric, which alerts OFM to treat the project as in Metric unit system. • The static master table must be the very first table defined in the
primary definition file (there may be many multiple definition files). • If the table name, variable name, or even the attribute contains two or
more words and has space(s) between them (or non-ASCII characters), they should be enclosed in quotes (for instance, “MY WELL”) for OFM to treat it properly.
• Comment lines have to be started with either comment identifiers “//” or “/*”. These lines are just descriptive information and will be ignored by OFM at load time. All texts are case-insensitive.
Let us now take a look at the definition of the monthly production table named MONTHLYPROD. Scroll down the file and locate the line “*TABLENAME MONTHLYPROD Monthly”. Notice the structure of the definition file.
In this case, MONTHLYPROD is the name of a MONTHLY table, which has fields like DAYS (an int4 type), OIL (a float type), and more…
Continue to scroll up and down the definition file to study other tables, their fields and attributes. Notice the CHOKE and the RES_PROD tables. The CHOKE table is a DUALKEY SPORADIC table. Therefore, the *DUALKEY keyword is required after the *Tablename line.
Likewise, RES_PROD is a GROUP level table. OFM needs to know at which level its data are associated to. Thus, the word GROUP is required, followed by the group name. In this case, it is RESERVOIR (a Sort Category).
TIPS – NUMERIC SIZE:
• Numeric Type Value Ranges: • INT1: -128 to 127
• INT2: -32,768 to 32,767
• INT4: -2,147,483,648 to 2,147,483,647 • UINT1: 0 to 255 (unsigned int1)
• UINT2: 0 to 65,535 (unsigned int2)
• UINT4: 0 to 4,294,967,295 (unsigned int4)
• FLOAT: occupies 4 bytes, 7 decimal places, and values of approximately -3.4E-38 to 3.4E38.
• DOUBLE: occupies 8 bytes, 19 decimal places, and values of approximately -1.7E-308 to 1.7E308.
• Knowing the appropriate range of your variable data and assigning the proper size to the variable may help you save memory and improve performance.
TIPS - Reserved Keywords
There are reserved keywords that may be used in the text load files. They have special meanings to OFM and cannot be reused as variable names. The following table is a list of the most commonly used reserved keywords:
*DateLabel *KeyLength *ReadOff
*Day *KeyLimit *Skip
*DD *KeyName *TableName
*DDMMYY *Metric *TVD
*Define *MM *XDelt
*Depth *MMYYDD *YDelt
*End_Define *Month *Year
*EOF *Null *YYMM
*End_Format *Quiet *YYMMDD
Data Files
Static Data
1. On a text editor, open the Demo Key Data.xy file (in the Text Load Files directory).
2. Study the file (please scroll to the right to see all field data). The variable identifiers exist before the data section, right below the *tablename line. OFM will parse data into the corresponding fields, based on the order they appear on that variable identifiers line.
Monthly Data
1. On a text editor, open the Demo Monthly Prod Data.prd file.
2. Notice the *KeyName line. This tells OFM which entity the next data section will be loaded into (until the next instance of *KeyName). Scroll down to see the rest of the file.
Daily Data
Open the Demo Daily Prod.dly file and view the data.
Sporadic Data
Open the Demo Sporadic Test Data.tst file and view the data.
Note: Sort Category table is a “non-defined” table. Its table definition is
specified at the beginning of the file, enclosing between the *Define and theIn OFM 2005 (as well as in any versions after 2002), it is not mandatory to physically have a Sort Category table in the OFM project. Any field (preferably text field) from a static table can be used as a category. Further discussion on this will be given in the “Editing Sort Categories” section.
There are more text load files provided with the Demo project (as well as other projects in the Sample Databases directory). With the help of the instructors, class participants are encouraged to get familiarized with those files, especially the typical format of each file/table.
Exercise 5
Study Other Text Format Files
Continue to study the other text file formats in the “\…\Text Load Files\” directory.
Creating Project from ASCII Text Files
In this section, you will learn to create a new project with text files provided in the Demo “Text Load Files” directory.
1. Start OFM.
2. Select File>New Workspace.
3. In the New OFM Workspace window, select the directory where you want you workspace and database files to be in, enter the desired workspace name, and select Create it from the data source specified below.
4. Make sure that ASCII Flat Files is selected at the Data Source select list. 5. Select either Access 97 or Access 2000 to create your OFM Access
database (if you have Access 2000 installed in your computer and you are creating an Access 97 OFM database, you will be able to open the OFM database in Access but cannot make changes to its design. On the other hand if you have Access 97 installed and are creating an Access 2000 database, you will not be able to view the database). Ignore the Prompt for Project Filter … for now and leave it unchecked.
6. Click OK.
7. In the OFM Data Loader window, locate the \\…\Text Load Files directory to display it in the Look in list.
8. Add the following files to the Files to Load field, in this order, by either double-clicking the file, or highlight and click Add.
• Demo Definitions File.def • Demo Key Data.xy
• Demo Monthly Prod Data.prd • Demo Daily Prod Data.dly • Demo Sporadic Test Data.tst
• Demo Calculated Variables Data.par • Demo Deviation Data.dev
• Demo Basemap Anno Data.ano • Demo Lease Info Data.xrf • Demo Pressure Lookup Data.lku • Demo DualKey Choke Data.dat
9. When a file is added to the Files to Load list, OFM recognizes the extension and reflects the correct types in the Data Types list. If the load files do not follow the OFM naming convention, associate the appropriate data types for the files. Otherwise, the result may be incorrect.
10. Leave all other choices unchanged, and click Load to display the Basemap.
Note: If there is error(s) encountered during the loading, OFM will display a
red error icon on the status bar (i.e. bottom right corner). Click on it and the error(s) will display. You can use the right-mouse menu to select and copy the error messages to a text editor to view/save.Exercise 6
Create Files and New Workspace
Create the one definition file, one key data file, one monthly production file, and one daily production file for a simple four-well project. Create a new workspace and load the files to the project.
Using Batch Loading (optional)
Before proceeding to the next exercise, check your OFM installation directory for the *.bdl and the *.bpf files. If you do not have these files, ask your instructor to get a sample copy.
There are two types of batch data loading in OFM, via the Data Loader. One is used for loading multiple files to create a project, the other loading multiple
files to create multiple projects. The former batch file should have the *.bdl (e.g. Batch Data Loading) extension, and the latter should have the *.bpf (e.g. Batch Project File). This exercise demonstrates how to use the first feature.
1. Open the *.bdl (for example, Batch Data Load File.bdl) file that you have (or your instructor provides) in a text editor (WordPad or Notepad). 2. Edit (if needed) to verify the path/directory of the text files is correct. In this
case, it would be \\…\…\Text Load File\ and then the full file names (again, \\…\ denotes the program directory).
3. Verify that the definition and key data files are the first two files in the list. 4. Repeat steps 1- 7 of the Creating Project from ASCII Text Files exercise. 5. Locate the Batch Data Load File.bdl file and click Add. OFM will read the
file and deposit place the correct specified files into the Files to Load list (in the specified order).
6. Click Load to load the files as you did in the previous exercise.
7. The format of the *.bpf is very much the same as the format of the *.bdl file, except for each project, there is a line specifying the project name and directory. For example, a project named DemoData in the D:\Temp directory would be specified as: *Project “D:\Temp\DemoData.mdb”. The project keyword line is followed by those lines (data files) seen in a *.bdl file. A different project is identified by a new *project line, then its own data files. To execute this batch loading procedure, from the File menu (no workspace opened), select Batch Load and select desired file to load. Again, verify the path and file names are correct to guarantee correct loading of data. Do not forget to close the workspace for the next exercise!
PI/Dwights Text Format
OFM provides a direct method to load certain PI/Dwights production files (i.e. dmp2, 298 fixed format) to create OFM projects. The following exercise demonstrates how to create an OFM project from the dmp2 production files. 1. Create a new workspace, assign the desired workspace name (please
refer to step 1 – 3 in the previous exercise – Creating Project from ASCII Text Files).
3. Click OK. Locate the \\…\Sample Databases\PI Dwights Sample Files\ directory and select a file from the list of available files (i.e.
wcr_dmp2.dp2). Proceed to the next step.
4. Toggle on the Prod ID (Entity ID) (40 characters) button. If you do not want to keep the temporary load files, make sure the Delete Temporary Load Files option is checked.
5. Select the wells you want to load into the OFM project. You can choose to load all wells to the database.
Note: If you want to create a Xref (cross-reference) table at this time, you can
do so. Click the corresponding button and specify the file name in the next dialog.6. Click Next. It is recommended that you do not make changes (unless you know exactly the data) to guarantee the database integrity. In this step, you can specify the fields to be used as Sort Categories. Select the displayed fields to view their descriptions. Then select Next.
7. This step allows you to select which well test items to be included. Make the selection and click Next.
8. This last step gives you the option to select which monthly production data items to be included. Make the selection and click Finish.
9. With proper editions, your basemap should look like the following: (do not display the well name otherwise the basemap may look crowded).
30.0 30.0 37.5 37.5 45.0 45.0 52.5 52.5 60.0 60.0 67.5 67.5 - 152.0 - 152.0 -144.0 -144.0 -136.0 -136.0 -128.0 -128.0 -120.0 -120.0 -112.0 -112.0 OIL GA S
Exercise 7
Exercise 8
Load PI/Dwights Production File
Create a new workspace and load another PI/Dwights production dmp2 file to the database.
Load PI/Diwghts 298 Production File
Create a new workspace and load a PI/Dwights 298 production file to the database.Do not forget to close the workspace for the next exercise!
From an Existing Access Database
If an Access database has a structure that is compliant to the OFM database model, OFM can open it and converts it to an OFM database (by creating proper system and configuration tables in the opened Access database). If you want to open a generic Access database (which does not necessarily comply with the OFM database model) in OFM, OFM would certainly try to open it. However, the program cannot ensure the normal behavior of the database and/or the project.
Note: Once the original Access database has been opened (and converted to
an OFM database), it is primarily used by OFM. In this case, it is so-called a “native” database. The use of native database reduces the storage space but does not offer good recovery schema in case of database corruption.
In the following class exercise, you are going to create an OFM
project/database from an existing Access database. For the training purpose, a simplified version of the Demo database will be used. You can either obtain that Access database from your instructor or create your own database that only has the data tables (not the OFM system and configuration tables) by deleting the appropriate tables from you Demo database. Please do not forget to make a copy of the Demo database before proceeding with this exercise. Your generic Access database may look like the following:
Note: Also, make two (2) copies of this stripped-down Access database for
use in the next session.
1. Start OFM. From the File menu, select New Workspace. Click on the “browse” button to the right of the Workspace File text box and select the directory where you want your workspace file to be located. Enter a workspace name, i.e. demo_native, and click OK.
2. Click on the “browse” button to the right of the Database File text box and locate the directory where your original (generic) Access database is located. Select the desired “*.mdb” file.
3. Click OK.
5. At the prompt, select Yes to confirm that you want to make this Access database an OFM project.
6. Click Yes (remember this Access database is the stripped-down version of the Demo database). The Edit Schema Tables displays.
7. Select the master (primary) key for this project in Table Key(s). In this case, it is UNIQUEID (which should have been selected for Field1). Click OK to proceed. The basemap displays.
Note: If your project has composite key, you can specify the key by
appropriate concatenation of the keys, with appropriate delimiter(s). Up to three keys can be combined to create the composite key field (denoted by
Field1, Field2, and Field3 in the Table Key(s) group box). Also, you may
have to customize a few things (i.e. map association, map properties, etc…) to get the basemap displayed properly as desired.
At this time, only the HeaderID table has been associated to the OFM project. The next step is to associate other Access tables to the OFM project. This is done from the Schema Tables.
8. Select Database>Schema Tables. The Edit Schema Tables displays, with all the tables available for OFM use.
9. Let us first map a STATIC table to the project. Scroll down the window and select SortCategory (by checking the box in front of the table name) from the list of available tables. The dialog refreshes for you to give
specifications to SortCategory table.
10. Select Static from the Table Type box. OFM will prompt you for confirming if you want to join the (SortCategory.)UniqueID field to the (HeaderID.)UniqueID field. As this is correct, click Yes. The following window displays.
Note: If you want to not use any of the available fields in this table, select the Fields tab and uncheck the undesired field(s).
11. From the left pane of the Edit Schema window (so-called the OFM Representation pane), select the Demo2005_native node to get to the project level as shown below.
Note: You can view an OFM database as if it has three hierarchical levels –
add/remove table(s) from the project level, and add/remove field(s) from the table level.
12. Select the MONTHLYPROD from the list of Available Tables. Since this is a monthly frequency table, select Monthly from the Table Type drop down list. OFM reads the table structure and suggests the following:
13. As the suggestions are correct, click Yes (select No if any of the choices is incorrect).
14. Click on the Fields tab to view the field information. You can un-associate the field(s) from here. You can also add more field(s) to this table.
15. Click the Demo2005_native node from the left pane again. When the list of available tables displays, select DAILYPROD.
16. Select Daily from the drop-down list for Table Type. As OFM suggests map (Dailyprod.)UniqueID to (HeaderID.)UniqueID and
(Dailyprod).Date to Date, click Yes.
17. Select the Demo2005_native node from the left pane again. When the list of available tables displays, select TEST.
18. Select Sporadic from the Table Type select list. OFM suggests the following:
20. Since the “entity” key of the TEST table (UniqueID) matches the project master (primary) key, the Key Type should be set at Completion (please refer to Module 1 for OFM Database discussion), similar to what you have seen for Static, Monthly, and Daily tables. Make sure the secondary sporadic key in this TEST table is set at DATE.
21. Click on the Demo2005_native node again. Check CHOKE from the list of Available Tables. Since this table contains intra-day information, select Sporadic DualKey from the Table Type drop down list. Click Yes when OFM suggests the entity key association.
22. Make sure the two secondary sporadic keys are DATE and INDEX (in that order). Select the Demo2005_native node again. Check the
VALUE_DATA from the list.
23. Select Lookup from the Table Type drop-down list.
Note: Entity is just a generic term used specifically in Lookup and Xref
tables. It could represent many different things including completion, lease, reservoir, etc…
25. Select the Demo2005_native node. From the list of available tables, select LEASE_DATA. Select Xref from the Table Type drop-down list. Make sure the Cross Reference Key is set to LEASE.
384000 384000 386000 386000 388000 388000 390000 390000 392000 392000 394000 394000 1665000 1665000 1668000 1668000 1671000 1671000 1674000 1674000 1677000 1677000 1680000 1680000
Note: If you want to display the well type legend on the basemap, you will
have to go to Edit>Map>Association to specify the well type field (i.e. SortCategory.WellType) in the Well Type – Table field.
Now, we are going to associate a group level table to the OFM project. We had to exit the Schema Tables window so the “Foreign” key or “Category” key is registered to the project for use. In this next exercise, we are going to map in a monthly frequency table that has a RESERVOIR key.
27. From the Database menu, select Schema Tables. Select the Demo2005_native node. From the list of available tables, select RES_PROD. Select Monthly from the Table Type select list.
28. OFM cannot find the correct key in this table to match the
(HeaderID.)UniqueID key, select No (even though the Date key is correctly matched). OFM will remind you to manually associate two keys for this table (from the bottom, above the OK and Cancel buttons).
29. As the key of this table is RESERVOIR (which is not a “completion”-type key), drop down the Key Type list and select Foreign.
30. Click No. From the drop-down list of Foreign field, UNCHECK the HeaderID.Alias field. Scroll down the list and CHECK the
SortCategory.RESERVOIR field.
Note: You MUST uncheck the HeaderID.Alias field before checking the
SortCategory.RESERVOIR field to make this work properly.
31. Now that OFM has correctly guessed the key associations, click Yes to accept the suggestions.
Exercise 9
Exercise 10
Exercise 11
Associate the Available Tables
Associate the rest of the available tables to the OFM project. (Hint: FINANCIAL is a Lookup table, MONTHLYGASINJ is a Monthly table, and Sand is a Static table).Un-Associate the RES_PROD Table
(Optional) Un-associate the RES_PROD table, exit the Schema Tables window. Then go back to the Edit Schema Tables and re-associate the RES_PROD table. This time, use the CATEGORY key type instead of the FOREIGN key type. (Hint: You have to activate the RESERVOIR key before it is available as a CATEGORY-type key).Associate Deviation Table
Associate a Deviation table to the OFM project.Do not forget to close the workspace for the next exercise!
Linking to an Access Database
Considering that most of the generic Access databases are not created and maintained exactly the way OFM databases are designed, coupling with the practice of keeping the original Access databases separate from the OFM project databases, OFM provides a dynamic method of linking the OFM database to the Access data source called Linked Tables method. In this Linked Tables method, there are two separate Access databases – one of the original data (i.e. the source) and the other containing the linked information along with system/configuration tables.
The Linked Tables method can be used to connect to any ODBC- (Open Database Connectivity) compliant data sources such as SQL Server, Oracle, or Microsoft Access, Microsoft Excel, etc… Its advantage is that the users always have a “clean” copy of the data. It reduces the risk of corrupting the original database. The trivial disadvantage of this method is the maintenance of two separate databases. In addition, each time the user requests data from the OFM project, the program has to resolve the links and goes to the source database to get data. This may add more time for data processing (especially when the source database is not located in the local hard drive and/or the source database is Oracle/SQL Server based), but at the same time guarantee the user always gets the most up-to-date version of the data. OFM provides built-in algorithm to connect to Microsoft Access. In this session, you will learn to create an OFM project linking to data from an external Access database. We are going to use the copy of the file Demo Access database that was in the previous exercise.
1. Start OFM. From the File menu, select New Workspace. Click on the “browse” button to the right of the Workspace File text box and select the directory where you want your workspace file to be located. Enter a workspace name, i.e. demo_link_Access, and click OK.
2. Leave the Database File name unchanged. Toggle on the Design it interactively button.
4. Select the HeaderID table in the OFM Representation pane. Right mouse click and select Delete from the menu options.
Note: OFM always suggests the default OFM database structure, with the
Master Table being HeaderID and the Master Key being UniqueID. Generic databases normally do not follow this model. For demonstration purpose, we are going to simulate the generic case steps even though the data source already has this model.
5. Click on the Add Link Tables button.
6. Locate the directory where your Microsoft Access source database is located from the Look in select box. Select the database as shown below.
7. Make sure the Files of type box shows Microsoft Access (*.mdb). Click Open.
8. The first table to link to the OFM project MUST BE the “master” table. In the source Access database, that table is the HEADERID. Select that table from the list and click OK.
9. Select the HEADERID table (check the box). OFM recognizes this table structure and suggests the key association.
10. Since the mapping suggestion is correct, you do not have to take any action. Select the demo_link_Access node from the left pane.
11. Click on Add Link Tables. Again, select the directory, the database, and make sure the Microsoft Access is selected as in steps 6 and 7. Click Open.
12. From the Select Table(s) to Link dialog, click Select All. Notice that the HEADERID table is available for linking. You do not need to link the HEADERID table again. Therefore, while holding the Control key (Ctrl), click on the HEADERID table to unselect it.
Notes:
• In step 7 of this exercise, you can select all tables (i.e. Select All). Then you MUST select the HEADERID table first (from the Available Tables list) to map into the project. Remember, the MASTER table MUST be mapped first.
• One source table can be linked as many times as you want (i.e. one source table is used to create many OFM project tables).
• Data from different external data sources can be linked to in a single OFM project.
13. Click OK. The selected tables have been made available to the OFM project.
14. Repeat steps 8 – 31 in the previous exercise (Project Creation – From an Existing Access Database).
Do not forget to close the workspace for the next exercise!
Project Creation – Linking to an Excel Spreadsheet
Microsoft Excel has been used widely in the Oil and Gas industry to temporarily store data (before loading to long-term data managementapplications and/or analytical applications), as it is very easy to use. However, Excel is free formatted, which is error-prone for a relational database based application like OFM.
With all that being considered, OFM supports linking to Excel to get the data, via the Linked Tables method. However, to ensure the link between OFM and Excel works correctly, there are a few Rules of Thumb (in addition to the table key information) to consider:
• The Worksheet Name will be used as the Table Name • The first row on the worksheet is reserved for Field Names
• Each worksheet can only store data for one OFM table. No merging of worksheets allowed.
• Data on the worksheet must be continuous. No empty row(s) should exist in between data sections.
• No extra formats on the data columns (i.e. comments, merged cells, etc…)
• Data in the same column must be of identical data type (i.e. number, text, date/time) and should be of the same format.
• No embedded graphs allowed on the linked worksheet. In other words, KEEP IT SIMPLE!
In this next exercise, you are going to create an OFM project with data from an external Excel spreadsheet. Built-in Excel linking setup procedure is used; and the data source is the stripped-down version of the Demo Access database. Please obtain the Excel file from your instructor or create one for this training exercise. The Excel spreadsheet structure looks similar to the following:
(Example: Worksheets and their names in the Excel file)
(Example: Static table information)
(Example: Monthly table information)
1. Launch OFM. Create a new workspace. Locate the directory where you want to put the workspace file and the database file.
2. Make sure Design it interactively is selected. Click OK. 3. Select the HeaderID table and delete it.
4. Click the Add Link Tables button.
5. Select the directory where the source Excel file is located. Select the desired file. From the Files of type drop-down list, select Microsoft Excel (*.xls).
6. Click Open.
8. Select the Master table from the list.
9. OFM recognizes the table structure and suggests the key association. As it is correct, do not change anything. Select the demo_link_Excel node from the OFM Representation pane.
Notes:
• Once you are connected to the external data source, the procedure to map/associate the external tables to the OFM project is the same regardless of the data source type.
• You can rename a table in OFM, once the table has been mapped. Many external tables have long names, which you may consider changing. The external table names are still unaltered; only the OFM table names change. Tip: Right mouse click on the table (on the left pane) and select Rename from the menu, the program should give you access to changing table names.
• The “master” table can only be renamed when it has just been mapped to the project. After that, it cannot be changed. The other table names can be changed at any time unless the tables (and their children fields) are referenced by other tables/fields.
It has been left as an exercise to associate all other Excel tables to the project now that they have already been made available for use.
Exercise 12 Associate Other Tables to the Project
Associate the other tables to the project. Please refer to the previous two sessions for procedure. (Hint: There are one static table, one monthly table, one daily table, one sporadic table, one dualkey sporadic table, and one monthly foreign key table).Do not forget to close the workspace for the next exercise!
Advanced Topic: Linking to an ODBC Data Source
(optional)
This session is designed to illustrate the Linked Tables method using ODBC driver setup. Usually, your ODBC data sources are not local. Connecting to such data sources requires a network connection and a driver – the DSN (Data Source Name). For training purposes, you are going to use a Microsoft SQL Server database as the ODBC data source. This SQL Server database is the upsized version of the Demo database (from Access).
The simplified Demo Access database is used in this session. For further information about how to upsize your Access database to SQL Server, please consult with your instructor.
Note: You can create the DSN prior to starting OFM, or you can create it
during the project creation session.
1. Launch OFM. Create a new workspace and a new database file in the desired directory. Select Design it interactively.
2. Click OK. Select the HeaderID table and delete it. Click the Add Link Tables button.
3. From the Files of type drop-down list, select ODBC Database(). The Select Data Source appears.
4. (You are recommended to create a Machine Data Source DSN) Select the Machine Data Source tab, and click New. The Create New Data Source dialog displays.
5. Toggle on the System Data Source and click Next.
6. Since the data source is Microsoft SQL Server, select the SQL Server from the driver list.
7. Click Finish. The Create a New Data Source to SQL Server window displays.
8. Specify your desired Data Source Name (Name) and give a Description (optional). The select the host Server name from the list of SQL Server you can connect to.
Note: You can connect to the SQL Server database using the (Windows NT)
network login ID or specifying server authentication login name and password. For more information, please consult with your instructor.
10. Click Next. Select the default database (where your source database is located) and provide other information as needed.
12. Click Finish. The summary page displays. You can test the connection by clicking the Test Data Source.
If the connection to the data source is good, you will get the following message:
15. Click OK.
17. With the desired DSN being highlighted (as shown above), click OK to conclude the DSN setup procedure. The Tables dialog appears:
18. Considering that you are only connecting to a small set of tables, you can leave everything on this dialog at default. If you are linking to a rather large data source (i.e. Oracle database or SQL Server database), you would want to narrow down the list by specifying a “filter” criterion (i.e. Owner, Table only, or specific Table(s), etc…) Click OK to continue. 19. The Select Source Tables dialog appears.
20. Select the appropriate tables to link to the OFM project (i.e. HeaderID, Monthlyprod, etc…). Once the tables are made available to OFM (in the list of Available Tables), the steps to associate those tables to the project are straightforward, as in the previous exercises.
Exercise 13 Linking to SQL Server
Chapter 3 Project Administration
Project Panes
The most significant change to OFM 2005 is the Graphical User Interface (GUI). The GUI has been completely redesigned. These interface
improvements reduce the number of menu selections and provide a more intuitive experience for the end user. This redesign of the GUI will enable users to quickly access and leverage the core functionality and features within the OFM environment. Accessibility through much of the functionality OFM provides is achieved through the use of project panes.
Learning Objectives
In this module, you will successfully learn how to perform the following procedures within this workflow:
• Changing the layout • Working with panes
• Edit completions, wellbores, patterns • Understanding units, multipliers, PVT data • Editing table schema
• Editing categories
Changing the Layout
The Layout menu command enables you to organize the display with
predefined layouts. The table below lists the available layouts and provides a brief description of each. Select View>Layout to access this predefined layout.
Hiding/Showing Panes
Panes that are open but not displayed in the main OFM window are displayed as a tab on an open pane. Placing the mouse over the tab shows the hidden pane. The image below shows the results when you mouse-over the tab of a hidden pane.
Note: The horizontal pin located in the upper-right corner of the pane indicates
that the pane is not docked. Moving the mouse away from the pane, results in the pane being hidden.
Docking Panes/Disabling Auto Hide
To dock panes or disable the Auto Hide feature, click the horizontal pin in the upper-right corner of the pane you want to dock. This action docks the pane in the OFM main window. The image pictured below shows the results when you pin a pane to the main window.
Note: Clicking the pin again turns the Auto Hide feature On.
Floating/Docking Panes
Select the pane you want to move, drag it to the desired location, and release the mouse. The image below shows the results of a floating pane.
Note: To dock the pane, double-click in the header of the pane. The pane is
restored to its original location.
Positioning Panes
Panes can be moved to any location within the OFM main window. To reposition a pane, select the pane and drag it to the desired location. An outline of the pane is displayed showing where the pane will be relocated. Panes can be repositioned within another pane, displayed as a tabbed page of another pane, or as a docked pane within the OFM main window.
Opening Panes
Panes can be opened from the View menu. Opened panes have a checkmark displayed to the left of them in the view menu indicating that the pane is opened.
Detaching Tabs from Panes
With the new OFM graphic user interface, you can detach tabs from panes that can float or sit in front of the OFM main window or dock along either side of the main window. Detached tabs can also be combined with other docked panes.
1. Select the tab and drag the pane to the desired location.
Note: The detached tab is indicated by a dashed line.
Editing the Database
The OFM Database menu command is accessible from all analysis modes. It is important to note that all changes made will impact the database. Use these options with caution.
• Completion – displays the Delete/Rename dialog. This dialog enables you to remove or rename UNIQUEIDs (well names) from the database.
• Wellbore – displays the Delete/Rename dialog. This dialog enables you to delete or rename Wellbores from the database.
• Patterns – patterns are groups of wells. The portion that each individual well contributes to the group varies with time and is
calculated by applying a factor to the individual well data. Selecting the Patterns menu command displays the Edit Patterns dialog. This dialog contains a list of pattern data to select one or more patterns to display on the base map.
OFM Units
The Edit OFM Units dialog enables you to add or edit units of measurement to your project. This is useful when converting currency or when defining units required by the project not included in the OFM database.
1. Select Database>Units. The Edit OFM Units dialog displays.
Notes: The Edit OFM Unit dialog is displayed when you click the Add or Edit
2. Enter a value in the Metric, English, and Conversion fields or modify the values currently displayed.
3. Click OK.
Multipliers
The Edit OFM Multipliers dialog enables you to create, edit, or delete unit multipliers for variables. The OFM multiplier functionality is useful for converting existing data, creating conversion factors, or defining multipliers that are not included in the OFM database.
1. Select Database>Multipliers. The Edit OFM Multipliers dialog displays.
Notes: The Edit OFM Multiplier dialog is displayed when you click the Add
2. Enter a value in the Field, Metric, Scientific, and Conversion fields or modify the values currently displayed.
3. Click OK.
PVT Data
PVT Data is edited from the PVT Entity Name dialog. The PVT Entity Name dialog contains a Select One section, which lists entities such as wells, reservoirs, fields or surveys, for example. PVT data for the selected entity or item can be edited and stored in a database that is automatically accessed and used when calculations that require PVT data for the entity are performed. The PVT Entity Name dialog also enables you to add an entity, delete an entity or rename an entity in the Select One list. Predefined PVT table data for one entity can by copied to another (New) entity.
Editing Project Structure
There are two parts of an OFM project, the design (structure) and the data. This topic demonstrates how to edit a project in both the design and the data. A typical OFM project has many tables and each table has many
fields/variables. OFM does enable users to interactively add/delete/rename tables, fields, as well as change the project settings/associations regarding its structure.
Editing Schema Table
The Edit Schema Tables dialog enables you to create tables in Access and locate and recognize those tables in OFM. Tables can be defined in either Access or OFM. Operations, such as editing, deleting, and adding tables and fields can be performed from the Edit Schema Tables dialog. At the project level, the dialog consists of the OFM Representation section and the Tables tabbed page.
