OFM 2007.2 Fundamentals

(1)

Schlum

berger Public

OilField Manager 2007

Fundamentals

Workflow/Solutions Training

Schlumberger Information Solutions

January, 2008

(2)

Schlum

berger Public

Copyright Notice

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, Suite100, Houston, TX 77056-2722.

Disclaimer

Use of this product is governed by the License Agreement. 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

*Mark of Schlumberger. Certain other products and product names are trademarks or registered trademarks of their respective companies or organizations.

(3)

OilField Manager 2007 Fundamentals i

Schlum

berger Public

About this Manual...1

Learning Objectives...1

What You Will Need ...1

What to Expect ...2

Course Conventions...2

Icons...4

Module 1

OFM Basics...7

Lesson 1 OFM Database ...7

OFM Data Tables ...8

Standard Data Tables...8

Exercise 1 Exploring Other Data Tables ...12

OFM Defined Data Tables ...12

Exercise 2 Studying OFM Defined Data Tables ...13

The OFM Defined Table Manager ...13

Lesson 2 OFM Workspace...14

About Shared Workspace / My Workspace...15

Creating a Shared Workspace...15

Creating a New My Workspace that is Linked to the Shared Workspace...20

Linking an Existing OFM Project Workspace to a Shared Workspace ...22

Creating a Standalone Snapshot of a My Workspace and its Shared Workspace ...24

Creating a Copy of the Shared Workspace...27

(Optional) Migrating an OFM 2004 Database to OFM 2007...29

Exercise 3 Opening an OFM Workspace...30

Exercise 4 Changing the Database ...30

Exercise 5 Changing the Well Symbol Size ...31

Exercise 6 Changing the Database in a Workspace ...32

Exercise 7 Reversing the Changes ...32

Review Questions ...32

Summary ...32

Module 2

Project Creation...35

Prerequisites...35

(4)

Schlum

berger Public

Lesson 3 OFM Table Types...35

Lesson 4 Project Creation ...37

Lesson 5 OFM Loadable ASCII Flat File Formats...38

Viewing the (ASCII) Text Load Files ...39

Analyzing Data Files...43

Study Other Text Format Files ...46

Exercise 8 Creating a Project from ASCII Text Files ...46

Exercise 9 Creating Files and New Workspace...50

Exercise 10 Using Batch Loading (optional) ...50

Exercise 11 Creating a Workspace From PI/Dwights Production Files ...51

Exercise 12 Loading PI/Dwights Production File ...56

Exercise 13 Loading PI/Diwghts 298 Production File ...56

Exercise 14 Creating a Workspace from an Existing Access Database...56

Exercise 15 Associating Tables to the Project ...59

Exercise 16 Associating Group Level Tables to the Project...73

Exercise 17 Associating the Available Tables...76

Exercise 18 Linking to an Access Database ...77

Lesson 6 Project Creation – Linking to an Excel Spreadsheet ...83

Exercise 19 Creating an OFM Project from an External Excel Spreadsheet...84

Exercise 20 Associating Additional Tables to the OFM Project...88

Exercise 21 Advanced Topic: Linking to an ODBC Data Source (Optional)...89

Exercise 22 Linking to SQL Server...96

Summary ...96

Module 3

Project Administration...99

Lesson 7 Changing the Layout ...99

Opening Panes ...99

Hiding/Showing Panes ...100

Docking Panes/Disabling Auto Hide ...100

Floating/Docking Panes ...100

Positioning Panes ...100

Detaching Tabs from Panes...101

Editing the Database ...101

Editing OFM Units...103

Multipliers ...104

(5)

OilField Manager 2007 Fundamentals iii

Schlum

berger Public

Editing Project Structure...105

Editing Schema Table ...105

Editing Categories ...112

Summary ...114

Module 4

Basemap Customization ...117

Prerequisites...117

Lesson 8 Map Association Data...117

Editing Map Association Data...117

Exercise 23 ...117

Exercise 24 Moving the Legend (Optional) ...119

Lesson 9 The Map Display...119

Exercise 25 Modifying Well Symbols...120

Exercise 26 Displaying the Well Names on the Basemap...121

Modifying Map Limits...123

Exercise 27 Adding Map Headers ...124

Changing the Map Scale...129

Exercise 28 Adding Map Annotations...129

Exercise 29 Displaying Deviation Information ...134

Exercise 30 Zooming & Panning ...135

Exercise 31 Using Irregular Zoom ...136

Using Track Cursor...136

Using Workbook Mode...136

Exercise 32 Creating New Annotations...137

Exercise 33 Editing Annotations ...138

Summary ...142

Module 5

Filtering ...145

Lesson 10 Filter by Completion...146

Exercise 34 Filtering by Completion ...146

Lesson 11 Filter by Table Data ...150

Exercise 35 Filtering by Table Data...151

Question ...152

(6)

Schlum

berger Public

Exercise 36 Filtering by Category...153

Question ...154

Lesson 13 Filter by Match ...154

Exercise 37 Filtering by Match...155

Lesson 14 Filter by Query ...157

Exercise 38 Filtering by Query...157

Additional Filtering Options...162

Lesson 15 Invert Filter ...163

Exercise 39 Using the Invert Filter ...163

Lesson 16 Filter by DCA Data...163

Exercise 40 Filtering by DCA Data ...163

Exercise 41 Flagging Items...163

Exercise 42 Saving Filters...165

Lesson 17 Project Filter...169

Exercise 43 Using the Project Filter...169

Summary ...173

Module 6

Project Variables ...177

Lesson 18 Types of Variables...177

Lesson 19 Calculated Variables...178

Exercise 44 Editing Calculated Variables...179

Exercise 45 Adding Calculated Fields ...183

Question...183

Lesson 20 Calculated Variables...183

Exercise 46 Adding Ratio Variable ...184

Exercise 47 Using Cumulative Variable ...185

Exercise 48 Creating Calculated Variables ...187

Exercise 49 Creating Date/Event Variables ...187

Exercise 50 Creating a Calculated Variable...188

Exercise 51 (Dynamic) Computing Variables...188

Exercise 52 Creating a Variable ...189

Exercise 53 Plotting Variables Versus Date...189

Question...189

Exercise 54 Creating Text Display Variables ...189

Lesson 21 Calculated Fields ...194

(7)

OilField Manager 2007 Fundamentals v

Schlum

berger Public

Exercise 56 Creating Text Display Variables ...198

Summary ...198

Module 7

Plotting ...201

Lesson 22 Basics of Plotting ...201

Exercise 57 Creating a Graph with One Y-Axis ...202

Exercise 58 Modifying Graph Properties...204

Exercise 59 Creating a Graph with Two Y-Axes...211

Exercise 60 Creating a Plot with Multiple Graphs ...213

Lesson 23 Charts...215

Exercise 61 Creating Bar Charts ...215

Lesson 24 Save a Plot...218

Exercise 62 Using Plot Lock and Graph Blow Up Options...218

Exercise 63 Creating a Stacked Plot on Entities...220

Lesson 25 Stacked Plot on Variables ...223

Exercise 64 Creating a Stacked Plot on Variables...223

Lesson 26 Sum/Average/% Contribution Types ...226

Exercise 65 Using Sum/Average/% Contribution Types ...226

Lesson 27 Plot Overlay ...230

Exercise 66 Creating Plot Overlay...230

Lesson 28 Plot Annotations...232

Exercise 67 Using Plot Annotations...233

Lesson 29 Plot-Related Tools/Utilities ...235

Viewing XY Coordinates with Corresponding Points On the Plot...235

Plot Legends with Scroll Bars...236

Compute Line ...236

Creating a Plot with Three Graphs...240

Summary ...241

Module 8

Reporting ...243

Prerequisites...243

Lesson 30 OFM Reports ...243

Rules ...243

(8)

Schlum

berger Public

Exercise 68 Creating a Monthly Report...244

Exercise 69 Reporting Calculated Variables...247

Lesson 32 Daily Report ...247

Exercise 70 Creating a Daily Report...247

Question...248

Exercise 71 Using a Daily Frequency Calculated Variable ...248

Lesson 33 Sporadic Report...249

Exercise 72 Creating a Sporadic Report ...249

Lesson 34 Format a Report ...251

Exercise 73 Formatting a Report ...252

Lesson 35 Additional Report Tools ...260

Using Additional Formatting/Processing Features ...261

Exercise 74 Creating Maximum Monthly Oil Production ...262

Other Report Tools ...263

Creating a Table from the Report...265

Exercise 75 Exporting to Microsoft Excel ...268

Exercise 76 Exporting Data from the Report Module to Text Files ...270

Summary ...271

Module 9

Exporting...273

Lesson 36 Export Database Tables...273

Exercise 77 Exporting Database Tables ...274

Lesson 37 Export Variables to Table ...276

Lesson 38 Export Text Load Files ...276

Exporting Table Definitions...276

Exporting Table Data...277

Exporting Calculated Variables ...277

Scheduling (Eclipse) Exports ...278

Exporting DCA Data ...279

Summary ...280

Module 10

OFM Tools and Settings...283

Lesson 39 Project Settings...283

(9)

OilField Manager 2007 Fundamentals vii Schlum berger Public Group ...284 DCA...284 Units ...285

Exercise 78 Grouping Data by Date ...285

Date Display...287

Multiply By Factor ...287

Lesson 40 Data Normalization ...288

Exercise 79 Using Data Normalization ...289

Lesson 41 Data Register...291

Exercise 80 Creating a Variable to Represent the Average Monthly Oil and Creating a Data Register...292

(10)

(11)

OilField Manager 2007 Fundamentals 1

Schlum

berger Public

About this Manual

OilField Manager (OFM) is a powerful surveillance software

application that is widely used by professionals in the oil industry. It provides an array of tools for managing and analyzing

production data.

An 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 provides enough knowledge to perform basic functionalities that OFM supports.

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 terms database, workspace, and

project encompass both the database and workspace.

Learning Objectives

At the completion of this training, you will be able to: • Create an OFM project.

• Analyze project data using the various OFM modules. • Describe the design of the OFM tables (including keys). • Explain the DOs and DON’Ts of specific types of OFM tables. • Create an OFM workspace.

• Create a standalone OFM project or one that is linked to an

external data source or a combination of both.

What You Will Need

In this workflow, you will need the following hardware and applications in order to perform the workflow:

• OFM properly installed and licensed • Training datasets

(12)

Schlum

berger Public

What to Expect

In each module within this training material, you will encounter the following:

• Overview of the module

• Prerequisites to the module (if necessary) • Learning objectives

• A workflow component

• Lesson(s), which explain about a subject or an activity in the workflow

• Procedure(s), which show the sequence of steps needed to perform a task

• Exercises, which allow you to practice a task by using the steps in the procedure with a data set

• Summary of the module • Questions about the module • Scenario-based exercises

You will also encounter notes, tips and best practices.

Course Conventions

The instructions for the procedures and exercises in this manual are written using the following conventions.

Characters typed in Bold Represents references to dialog box names and application areas or commands to be performed. For example, “Open the Open Asset

Model dialog box.”

Used to denote keyboard

commands. For example, “Type a name and press Enter.”

Identifies the name of Schlumberger software applications, such as “Petrel” or “GeoFrame.”

Identifies the first use of important terms or concepts. For example, “Stacking of data…”

Characters inside <> triangle brackets

Indicate values that the user must supply. "sqlplus

<username>/<password> ", usually with a sentence that defines the values.

Characters typed in italics Represent file names or directories. "... edit the file lease.dat and..." Represent lists and option areas in

NOTE: Some of the

conventions used in this manual indicate the information to enter, but are not part of the information For example: Quotation marks and information between brackets indicate the information you should enter. Do not include the quotation marks or brackets when you type your information.

(13)

Schlum

berger Public

a window, such as “Attributes” list or “Select Options” area.

Characters typed in fixed-width

Represent code, sql, and other literal text that the user sees or types. For example: “sqlplus <username>/<password> ".

Instructions to make menu selections are also written using bold text and an arrow indicating the selection sequence, as shown below:

1. Click File > Save (the Save Asset Model File dialog box

opens.) OR

Click the Save Model toolbar button. An “OR” is used to identify an alternate procedure.

(14)

Schlum

berger Public

Icons

Throughout this manual, you will find icons in the margin

representing various kinds of information. These icons serve as at-a-glance reminders of their associated text. See below for

descriptions of what each icon means.

Prerequisites

This icon identifies any prerequisites that are required for the course, or for individual modules.

Learning Objectives

This icon identifies any learning objectives set out for the course, or for the current module.

What you will need

This icon indicates any applications, hardware, datasets, or other material required for the course.

Procedures

This icon identifies the steps required to perform a given task.

Exercise

This icon indicates that it’s your turn to practice the procedure.

Review Questions

This icon identifies the review questions at the end of each module.

Tips

This icon points you to a tip that will make your work

Notes

This icon indicates that the following information is particularly important.

Best Practices

This icon indicates the best way to perform a given task when different options are available.

Lessons

This icon identifies a lesson, which covers a particular topic.

Questions

This icon identifies the questions at the end of each lesson.

Warnings

This icon indicates when you need to proceed with extreme caution.

(15)

Schlum

berger Public

(16)

Schlum

berger Public

(17)

Schlum

berger Public

Module 1 OFM Basics

This section 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 and workspace so that you can correctly create your OFM projects.

Learning Objectives

At the completion of this module, you will be able to: • Describe the OFM data tables

• Use the OFM Defined Table Manager

• Create a Shared Workspace

• Link a new Workspace to the Shared Workspace • Link an existing My Workspace to a Shared Workspace • Create a copy of a Shared Workspace.

Lesson 1 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

There are two types of data tables in an OFM project: • Standard Data Tables that have no prefix

• OFM Defined Data Tables that have OFM_Data_ as a prefix Previous versions of OFM also had OFM Defined System Data tables that had _OFM_SYS_ as a prefix. In OFM 2007 all the information that was stored in the OFM Defined System Data tables is now stored in the *.OFM workspace file.

(18)

Schlum

berger Public

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.

Standard Data Tables

A standard data table is any table that does not have the

OFM_DATA_ prefix. The table must have a primary key and may

contain constraint and indexing information. Each field in the table will have designated data types, i.e., date/time, number, or text and size, i.e., long integer, double precision for number field, or 20 spaces wide for text field. Assigning the correct data types and sizes will insure no unexpected loss of data from truncation or rounding at load time. For example, a table to store time-independent data is shown in the following image.

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.

NOTE: There are only two

types of tables in OFM 2007, OFM-defined database tables having the prefix OFM_DATA_ and standard database data tables. Previous versions of OFM had tables containing the prefix _OFM_SYS_. All the information that was stored in those tables is now stored in the *.OFM workspace file.

NOTE: Standard Data

Tables are tables that do not have the OFM_DATA_ prefix.

(19)

Schlum

berger Public

In the image below, the HEADERID table is the master table for the OFM project, as indicated by the key icon to the left of the table name.

The UNIQUEID field is a field within the HEADERID table of type text that has a size of 20 and is designated as the primary key field in the HEADERID table, as indicated by the key icon to the left of the field name in the OFM Representation box and in the Attr column in the Available Fields box.

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:

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.

NOTE: Not all field

properties are displayed by

OFM in the Available Fields

section. To view any additional field properties open the table in Access in

Design view and select the

field. The additional properties will be defined on the General tab.

(20)

Schlum

berger Public

In the following image other field types can be seen in the

HEADERID table. For example, the YCOOR field is of type

Double, UPPERPERF is of field type Single, and

COMPLETIONDATE is of field type Date/Time.

When the field is a number, assigning the appropriate field type will save space in the database.

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.

To create a project OFM requires that a table be designated as the master table and that a field in the master table be designated as the primary key for the project. In the previous images the

HEADERID table is the master table and the UNIQUEID field is

the primary key. The master table contains static data about the primary key. The primary key is usually the completion name and the table would contain static data like the completions XY coordinate, alias, completion date, total depth, etc.

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. Now take a look at a monthly frequency table.

(21)

Schlum

berger Public

An OFM project can consist of many table types. Some table types contain more than one keyed field. For example, a monthly or daily table, which is date dependent, would have two keys: the primary key and a date/time key. In the following image a monthly table is highlighted.

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

(22)

Schlum

berger Public

UNIQUEID field in the HEADERID table. In this illustrative

database, there is a table that contains such valuable information. The relationship between them could be established as shown below.

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 Exploring Other Data Tables

Explore the DAILYPROD, TEST and CHOKE tables in the

Demo2007.mdb database.

• How many keys are there in the CHOKE table? • Which key is the primary key?

The instructor will explain why the CHOKE table is a special type of table in OFM.

OFM Defined Data Tables

The other type of table in OFM is the OFM-defined data table. It stores data that is either loaded, input or a result of OFM analyses. One type of OFM-defined data table has the prefix

OFM_DATA_DCA_ and decline curve analysis data generated in

the OFM decline curve analysis module. These tables are automatically created when the project is created and will not contain any data unless a forecast has been saved or merged from another workspace. The names of these tables, as defined by OFM, cannot be changed.

Some additional OFM defined data tables are

OFM_DATA_Deviation, OFM_DATA_Fault,

OFM_DATA_FILTER, OFM_DATA_Log, OFM_DATA_Marker,

etc. It is not recommended that the names of these tables be changed as it could prevent OFM from being able to access the

NOTE: You do not have to

physically make the joins between the tables.

NOTE: There is a special

type of data table named *_Adjustments in the Access database. These tables store prior cumulative production for the respective date-dependent tables. For example, open the

Demo2007.mdb database with Access, the

MONTHLYPROD table will

have an adjustments table named

MONTHLYPROD_Adjustm ents. The instructor will

explain why this special table type may be needed.

(23)

Schlum

berger Public

data. Even though OFM-defined data tables are basically data tables, the data that are stored in them can be sensitive to changes; therefore, it is not recommended that the data be manipulated manually.

Exercise 2 Studying OFM Defined Data

Tables

Using Microsoft Access, open the Demo2007.mdb database and study the OFM-defined data tables.

The OFM Defined Table Manager

The Database\Schema Tables… option is now used to only edit standard data tables. The Database\OFM Defined Tables… option has been added to manage all of the OFM-defined data tables. OFM-defined data tables are tables with the OFM_DATA_ prefix. They consist of Decline Analysis, Deviation, Fault, Log, Marker, Pattern, PIPESIM, PVT, and Wellbore Diagram tables. OFM-defined data tables now can be switched between Shared Workspace and My Workspace. If the OFM-defined data table is pointing to Shared Workspace then it is read-only. The OFM-defined data table has been converted to an entity based sporadic table.

NOTE: The Log table (i.e., OFM_DATA_LOG) stores

binary data object (i.e., BLOB). Therefore, the data (trace values) cannot be edited in this table.

NOTE: Refer to Lesson 2

for more information on My Workspace and Shared Workspace concepts.

(24)

Schlum

berger Public

Lesson 2 OFM Workspace

The following eight system tables were removed from the Access database: • _OFM_SYS_Configuration • _OFM_SYS_DateRange • _OFM_SYS_FieldProp • _OFM_SYS_Multipliers • _OFM_SYS_Parser • _OFM_SYS_TableInfo • _OFM_SYS_TableMap • _OFM_SYS_Units.

The first step taken was to extract all the information stored in the

_OFM_SYS_Configuration table and put it in a HTML file with

the suffix *.OFM. When any version of OFM 2007 is used to open a *.mdb project created with OFM 2004 or earlier, a XML file with the suffix *.OFM is created and the information from all eight tables with the prefix _OFM_SYS_ is written to this file not just the

_OFM_SYS_Configuration table. This *.OFM file is referred to as

the OFM workspace file. The _OFM_SYS_Configuration table is not deleted from the Access database and can be used to restore the *.OFM workspace file to the configuration it had when the project was converted if the *.OFM workspace file should ever become corrupt, however, any changes to the project

configuration that occur after the project is converted are stored only to the *.OFM workspace file; the _OFM_SYS_Configuration table becomes obsolete.

The second step was to remove the remaining seven tables having the prefix _OFM_SYS_, i.e., System tables, from the Access database. This step occurred in OFM 2007. When any project created in a previous version of OFM is opened with OFM

2007, the information that originally resided in the eight system

tables is written to the OFM 2007 *.OFM workspace file. If the project was created in OFM 2004 or earlier, then the information is taken from all eight system tables. If a project was created with

OFM 2005 or upgraded to OFM 2005, then the information is

taken from the OFM 2005 *.OFM workspace and all the system tables except the _OFM_SYS_Configuration table, which would only exist if the project had be upgraded to OFM 2005 and would not exist if the project was created with OFM 2005. The system files in any project created in a previous version of OFM become obsolete when upgraded to OFM 2007.

NOTE: There are three

types of OFM-defined tables which have the prefixes _OFM_SYS_, OFM_DATA_ and OFM_DATA_DCA_.

NOTE: If the project was a

OFM2007 project and had an existing *.OFM workspace the default setting in OFM 2007 is to backup the *.OFM workspace file and is recommended. If the project was a *.mdb project created with OFM 2004 or earlier then the backup message will not display and all the information in the eight system tables will be written to the OFM 2007 *.OFM workspace file.

(25)

Schlum

berger Public

About Shared Workspace / My Workspace

In OilField Manager 2007 (OFM 2007) the Private Database functionality has been replaced with the functionality to create workspaces. There are two types of workspaces – Shared Workspace and My Workspace.

When a workspace is a standalone workspace or a workspace linked to a data source the items in the workspace will be referenced using the word My. The main folder in the Analysis pane will be My Analysis, the main folder in the Calculated

Variables window will be My Calculated Variables, the main folder

in the Categories window will be My Categories, the main folder in the Units window will be My Units, etc. When the word My is used, that means that the items can be edited.

When a workspace is linked to another workspace, the items in the workspace will be categorized as either My or Shared. Any items that are categorized under the word Shared will not be editable from within that linked workspace.

Creating a Shared Workspace

A Shared Workspace can be a standalone workspace or a linked workspace. A typical Shared Workspace can be a workspace linked to a company database or a standalone project created using ASCII files. The primary benefit of a Shared Workspace is the ability to share a project with multiple users while restricting those users from modifying shared files. The functionality to create a shared workspace is the same as with OFM 2005 or OFM 2004, using linked tables or ASCII files. The only difference is once the workspace is created the items in the Shared Workspace will be referenced using the word My, as in My Analysis, My Calculated Variables, My Categories, etc. If you link to the Shared

Workspace using the Link to a Shared Workspace File: functionality, you will see the same items referenced using the word Shared; the items in the users linked workspace just created will be referenced using the word My. You will be able to add, edit or delete any of the items referenced as My, but will not be able to add, edit or delete any of the items referenced as Shared. In your training data set is an Access database named Company

Data Source.mdb. The following workflow will create a Shared

Workspace that is linked to the Company Data Source.mdb file. The Shared Workspace will then be linked to, illustrating how a user would access the Shared Workspace using the Shared Workspace / My Workspace concept. In this example the external data source is an Access database but it could be any external data source, Oracle, SQL, Excel, etc.

NOTE: In OFM 2007.1 the

word Team was used. It was replaced in OFM 2007.2 with the word Shared.

NOTE: The procedure

which follows would be performed by a nominated Owner of the Shared Workspace, typically a Team Leader or some other responsible person in the organization.

(26)

Schlum

berger Public

1. Launch OFM 2007.

2. Select File > New Workspace. The New OFM Workspace

window displays.

3. Click the browse button to the right of the Workspace File field. The New Workspace window displays.

4. In the File Name field, type Shared Workspace and click OK.

(27)

Schlum

berger Public

You are returned to the New OFM Workspace window. A default name using the same prefix as the Workspace File name displays in the Database File field.

5. Locate the section named How do you want to define your

(28)

Schlum

berger Public

6. Click OK. The Edit Schema Tables window displays.

7. Select the HeaderID table and right-click. A shortcut menu

(29)

Schlum

berger Public

8. Select Delete.

9. Click Add Link Tables. The Open window displays.

10. Select Company Data Source.mdb and click Open. The

Select Table(s) to Link window displays.

11. Click Select All to map all the tables to the project using the same workflow as in OFM 2004 or OFM 2005. The Shared

Workspace.mdb database and Shared Workspace.OFM

workspace file represent a workspace that is to be shared by multiple users. The users would access the Shared

Workspace using the Link to a Shared Workspace File functionality. This functionality will be illustrated next but first let’s add some output to the Shared Workspace.OFM workspace file making note that everything created or currently referenced in this workspace uses the word My, as can be seen in the Analysis pane where the folder is named

My Analysis.

12. Select Analysis > Bubble Map. The Open Bubble Map window displays. Create a bubble map and from the Analysis pane rename the bubble map Shared_Bubble_Map.

13. Select Analysis > Report. The Edit Report window displays. Create a report and from the Analysis pane rename the report

Shared_Report.

14. Select Database > Calculated Variables. The Calculated Variables window displays. Create a calculated variable name

Shared_CV.

NOTE: All the analysis

items created are placed in folders that are referenced using the word My. That means that anyone with access to the Shared Workspace.OFM workspace file can potentially open the workspace file and add, edit, or delete any of the items in the workspace. To prevent unauthorized users from accessing the shared workspace, it needs to be secured from those users.

(30)

Schlum

berger Public

Creating a New My Workspace that is Linked to

the Shared Workspace

The Shared Workspace enables you to share the workspace, but prevents you from being able to add, edit, or delete items in the workspace. We are now going to simulate how a team member would create a new personal workspace, and how he will link to the Shared Workspace created during the previous exercise in order to share all of its items.

1. To create My Workspace open OFM 2007.

window displays.

3. Click the browse button to the right of the Workspace File field. The New OFM Workspace window displays.

4. In the File Name field, type My Workspace and click OK.

You are returned to the New OFM Workspace window. A default name using the same prefix as the Workspace File name is displayed in the Database File field.

5. Locate the How do you want to define your project?

section, select the Link to a Shared Workspace File option, and click the browse button to the right of the text field. The

Open window displays.

6. Select the Shared Workspace.OFM workspace file created in

the previous exercise and click Open. You are returned to the

New OFM Workspace window. Click OK.

The My Workspace is created. Note the Analysis pane now has a My Analysis folder and a Shared Analysis folder. Expand the Shared_Analysis folder, Shared_Report, and Shared_Bubble_Map.

7. Select the Shared_Report or Shared_Bubble_Map under the

Shared Analysis folder. You will not be able to edit, add, or

delete the items; you only can copy them from the

Shared_Analysis folder to the My Analysis folder.

8. Right-click on the Shared_Report and select Save As New

Node. The report is copied to the My Analysis folder.

(31)

Schlum

berger Public

10. Right-click on the Shared_Bubble_Map and select Save As New Node. The bubble map can be copied to the My

Analysis folder. Rename the bubble map My_Bubble_Map.

11. Select Database > Calculated Variables. There is a My

Calculated Variables folder and a Shared Calculated Variables

folder.

12. Expand the Shared Calculated Variables folder. The

Shared_CV variable previously created is available.

13. Select Company_CV and right-click. Note that the only selection for you is to copy the calculated variable. Add, edit, or delete options are not available.

(32)

Schlum

berger Public

15. Click OK. Enter My_CV as the name for the new calculated variable. The variable is listed below the My Calculated

Variables folder.

16. Close the Calculated Variables window.

It is important to review and note that previously a workspace was created that was to be shared to other users. Upon opening that workspace directly you will see the word My on all the items because it is a standalone project that was created with ASCII files or is linked to an external data source. When you create a My Workspace that is linked to that Shared Workspace will see

Shared on all the items in the workspace previously created and My on all the items created in the My Workspace just created.

The items are labeled as My or Shared depending on from which workspace they are being viewed.

Linking an Existing OFM Project Workspace to

a Shared Workspace

There will be times when you may wish to migrate a pre-existing

OFM 2005 project, complete with your pre-existing (standalone)

associated My Workspace, to OFM 2007. In the previous exercises you were creating new Workspaces. Here, however, you will retain an existing Workspace, but make use of the new Shared Workspace feature in OFM 2007. To do this, use the

Database > Shared Workspace facility.

To link an existing workspace to a Shared Workspace:

1. Open the Demo2007 project as a standalone user: Select File > Open Workspace. Navigate to the My Workspace file you

created in the previous exercise.

2. The project opens, with the Analysis pane indicating that only one Workspace, My Workspace, exists. This is the situation that would have existed when you were an OFM 2005 user.

(33)

Schlum

berger Public

3. Select Database > Shared Workspace. The Shared Workspace form opens.

Now navigate to the Workspace file, which will represent the Shared Workspace to which you wish to Link.

4. Click Add.

5. Navigate to Shared Workspace.OFM and click Open.

6. OFM offers you the option to rename this Shared Workspace. (Remember, you may choose one of several Workspace files to be the current Shared Workspace.)

7. If you wish to accept the default, click OK.

8. You then return to the Shared Workspace form, which displays the list of available Shared Workspaces. Check the

(34)

Schlum

berger Public

box next to the one that you wish to make the current active

Shared Workspace and click OK.

At this point, OFM issues a message:

9. Once you are satisfied, click OK.

Your OFM session should now display an Analysis pane with two Workspaces: your pre-existing Workspace (My

Workspace) and the newly linked Shared Workspace (Shared Workspace).

Creating a Standalone Snapshot of a My

Workspace and its Shared Workspace

This feature enables you to combine My Workspace and any Shared Workspace that it is connected to into a single My

Workspace that will contain all the items and data from an original My Workspace and the Shared Workspace that it was connected to, including linked tables. All the items in the Standalone

Snapshot will be referenced with the word My and can be edited.

IMPORTANT: OFM is

about to perform the linking process. Any Table, Calculated Variable, Category, Unit or Multiplier in YOUR My Workspace that has the same name as one in the Shared Workspace will be considered to be a

duplicate and will be removed from My

Workspace. You should consider this before performing the link process. If you suspect that any such element (e.g., a personal calculated variable) may suffer from this duplication removal, rename it before you start the link process to ensure that your calculated variable survives.

(35)

Schlum

berger Public

1. To create a Standalone Snapshot, select Database >

Workspace Snapshot. The Workspace Snapshot window

displays.

2. Click the browse button to the right of the Workspace File list field.

3. The Open window displays.

4. Type Snapshot in the File name list field and click Open.

(36)

Schlum

berger Public

6. Open the newly created workspace Snapshot.OFM. In the Analysis pane the Share_Report, the

Shared_Bubble_Map, the My_Report, and the

My_Bubble_Map have been combined into a single My Analysis folder, as shown below.

7. Select Database > Calculated Variables. Both the

Shared_CV and the My_CV will have been combined into just a single My Calculated Variables folder, as shown below.

8. Close the Snapshot.OFM workspace.

NOTE: All the items in the

Snapshot.OFM workspace can be edited by the user. The snapshot could be sent to a co-worker, a partner company who shares interest in the project or to Schlumberger support for troubleshooting purposes.

(37)

Schlum

berger Public

Creating a Copy of the Shared Workspace

This option enables you to generate a copy of the Shared

Workspace. This feature is useful when you need to work but will not have access to the Shared Workspace. You can make a copy of the Shared Workspace and take it with you to perform your work then reconnect to the original Shared Workspace later time. 1. To create a copy of the Shared Workspace that the My

Workspace is linked to open the My Workspace.OFM file. Select Database > Workspace Snapshot. The Workspace

Snapshot window displays.

2. Click the browse button to the right of the Workspace File list field. The Open window displays.

3. Enter Copy of Shared Workspace as the file name and click Open.

4. Select the Create a copy option, as shown below, and click OK.

5. Click OK. Close the My Workspace.OFM file and open the Copy of Shared Workspace.OFM file.

(38)

Schlum

berger Public

The data and information will be the same as the original

Shared Workspace.OFM file up until the date the snapshot

(39)

Schlum

berger Public

(Optional) Migrating an OFM 2004 Database to

OFM 2007

The procedure below provides detailed instructions on how to migrate an OFM 2004 database to OFM 2007.

1. Select File > Open Workspace. The Open OFM Workspace

window displays.

2. From the Files of type list field, select OFM2004 Projects

(*.mdb).

3. Navigate to the location of the *.mdb file you want to load.

4. Select the file name and click Open.

5. A confirmation dialog displays enabling you to confirm that you wish to convert the OFM project.

6. Click Yes. A second confirmation dialog displays prompting

you to confirm if you wish to use the HEADERID as the OFM master table.

(40)

Schlum

berger Public

Exercise 3 Opening an OFM Workspace

To open an OFM workspace:

1. From the File menu select Open Workspace. The Open OFM Workspace window displays.

2. Select the name of the file you wish to load and click Open. The basemap loads in the OFM main window.

Exercise 4 Changing the Database

In this exercise you will re-attach the workspace to a new project (database), while still retaining the properties contained in the workspace file.

1. From the Database menu select Change Database. The Open dialog displays.

2. Navigate to the location of the desired database, select the file and click Open. The basemap displays.

(41)

Schlum

berger Public

Exercise 5 Changing the Well Symbol Size

In this exercise you will modify the well symbol size. Change the well symbol size to 1.5.

1. Select Edit > Map >Symbols. The Well Symbols dialog

displays.

2. Locate the Size section and change the Value to 1.5.

3. Click OK. NOTE: If you need

clarifications, please do not hesitate to ask your instructor.

(42)

Schlum

berger Public

Exercise 6 Changing the Database in a

Workspace

In this exercise you will change the database in a workspace. 1. Select the Base Map1 from the Analysis pane. From the

Database menu, select Change.

2. Locate the Training directory and go to Buildit2. Select Waterflood.mdb. Click Open.

3. Notice how the size of the well symbols has been adopted from the settings saved in the workspace file.

Exercise 7 Reversing the Changes

1. Change the database back to Demo2007.mdb. 2. Resize the well symbol from 1.5 back to 1.

Review Questions

• What are the names of the data tables used in OFM and what is the purpose of each one?

• What is the purpose of the OFM Defined Table Manager? • What is the benefit of using a Shared Workspace?

• Why would you want to link My Workspace to the Shared Workspace?

• When is it useful to create a copy of a Shared Workspace?

Summary

In this module, you:

• Familiarized yourself with the OFM database and OFM-defined data tables

• Reviewed the OFM workspace

• Learned the basics about the Shared Workspace and My Workspace concepts

• Created a Workspace Snapshot

NOTE: Notice that the

basemap header, well symbols, and the plot template are on the workspace level, independent of the database. This is the advantage of having created a workspace that pulls data from various identically designed databases.

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. The next section demonstrates such functionalities.

(43)

Schlum

berger Public

• Copied a Shared Workspace

• Migrated an OFM 2004 database into OFM 2007.

In the next module, you will learn how to create and associate data with OFM projects.

(44)

Schlum

berger Public

(45)

Schlum

berger Public

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

Data cannot be lost or changed by specifying incorrect tables. If a project table does not match the data source the data will simply not load or will not be viewable but nothing will happen to the data.

Prerequisites

Before getting to the actual data populating exercises, it would be useful to understand the OFM data table types and specifications.

Learning Objectives

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.

Lesson 3 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 the table structures in order to correctly construct the project will save you time and also guarantee the normal behavior and data integrity of your created project.

(46)

Schlum

berger Public

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) HOUR MINUTE SECOND 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.

(47)

Schlum

berger Public

Table Type Number of Keys

Key Types Key Data Types Comments 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. 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. MARKER 2 Entity Name Text Entity key MUST be Wellbore. Name key is the marker name.

Lesson 4 Project Creation

An OFM project can be defined/created using a variety of methods:

• Creating it directly from an Access database • Using a template

• Designing it interactively using linked tables

• Creating it from a data source like ASCII Flat Files, OFM3 Project Database or PI/Dwights

• Linking to a shared workspace file.

In the next section you will define/create a project using ASCII Flat Files, PI/Dwights DMP2 Production files, an Access database, and Linked Tables.

(48)

Schlum

berger Public

Lesson 5 OFM Loadable ASCII Flat

File Formats

In this section, you will learn the formats of OFM loadable ASCII Flat 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.

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

TIP: Most of the time, each

data file contains information from 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 into the project at the same time.

(49)

Schlum

berger Public

We have constantly used the terms definition file and data file. Not all the tables in OFM require table definitions before load time. These are tables that do not require table definitions before load time:

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

Viewing the (ASCII) Text Load Files

OFM 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, you will study the characteristics of some important table definition and data files in the Demo (usually located in the \\…\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.

3. The Open Window displays, 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.

(50)

Schlum

berger Public

6. Click Open. The definition file displays, as shown below

(partial file only):

Notes:

• The row beginning with the *Tablename keyword defines the table name, table type and indicates that it will be the master table. The file format is space delimited so whatever text lies between the next two spaces,

consecutive spaces are treated as one, will be the name of the table, followed by the table type and the master table designation.

• In this example HEADERID is the table name and it is a static table and most importantly it is the master table. A project can have as many static tables as desired, but there can only be one 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.

(51)

Schlum

berger Public

• Project Settings keywords may appear in the definition file. *DateLabel is one of them, denoting the displayed DATE name for the project. For 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.

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.

(52)

Schlum

berger Public

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.

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

(53)

Schlum

berger Public

Analyzing Data Files

The procedures below will assist you in analyzing static data, monthly data, daily data, hourly data and sporadic data.

Static Data

To begin analyzing static data follow the instructions below. 1. Launch any text editor.

2. From the File menu select Open and navigate to the Demo Key Data.XY file located in the Text Load Files directory.

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 parses data into the

corresponding fields, based on the order they appear on that variable identifier's line.

Monthly Data

To begin analyzing monthly data, follow the instructions below. 1. From the open text editor select Open.

(54)

Schlum

berger Public

Notice the *KeyName line. This tells OFM which entity the next data section will be loaded into (until the next instance of *KeyName).

3. Scroll down to see the rest of the file.

Daily Data

To begin analyzing daily data follow the instructions below. 1. From the open text editor select Open.

2. Navigate to the Demo Daily Prod.dly file and view the data.

Hourly Data

To begin analyzing hourly data follow the instructions below. 1. Export the Hourly data to notepad.

2. Select Database > Export > Selected Text Load File(s) > Table Data. The Table to Export window displays.

(55)

Schlum

berger Public

3. Select HourlyProd and click OK. The Save As dialog

displays.

4. Navigate to the desired save location and click Save. 5. Open the HourlyProd.hly file and view the data.

Sporadic Data

1. From the open text editor select Open.

2. Navigate to the Demo Sporadic Test Data.tst file and view the data.

(56)

Schlum

berger Public

The Sort Category table is a non-defined table. The table definition is specified at the beginning of the file, between the *Define and the *End_Define keywords.

In OFM 2007 (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 a text field, from a static table can be used as a category. Refer to the Editing Sort Categories section for additional information.

There are additional text load files provided with the Demo project. With the help of the instructor, you are encouraged to become familiar with those files, especially the typical format of each file/table.

Study Other Text Format Files

Continue to study the other text file formats in the \…\Text Load

Files\ directory.

Exercise 8 Creating a 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.

(57)

Schlum

berger Public

window displays.

3. Click the browse button to the right of the Workspace File field. The New OFM Workspace window displays.

4. Navigate to the desired location you want to store your workspace file.

(58)

Schlum

berger Public

6. Select Create it from the data source specified below and

browse to the location of the file (*.OFM).

7. Click OK. The OFM Data Loader window displays.

OFM 2007.2 Fundamentals

OilField Manager 2007

Fundamentals

Workflow/Solutions Training

Schlumberger Information Solutions

January, 2008

Copyright Notice

Disclaimer

Trademark Information

Table of Contents

About this Manual...1

Module 1

OFM Basics...7

Module 2

Project Creation...35

Module 3

Project Administration...99

Module 4

Basemap Customization ...117

Module 5

Filtering ...145

Module 6

Project Variables ...177

Module 7

Plotting ...201

Module 8

Reporting ...243

Module 9

Exporting...273

Module 10

OFM Tools and Settings...283

About this Manual

Learning Objectives

What You Will Need

What to Expect

Course Conventions

Icons

Module 1 OFM Basics

Learning Objectives

Lesson 1 OFM Database

OFM Data Tables

Standard Data Tables

Exercise 1 Exploring Other Data Tables

OFM Defined Data Tables

Exercise 2 Studying OFM Defined Data

Tables

The OFM Defined Table Manager

Lesson 2 OFM Workspace

About Shared Workspace / My Workspace

Creating a Shared Workspace

Creating a New My Workspace that is Linked to

the Shared Workspace

Linking an Existing OFM Project Workspace to

a Shared Workspace

Creating a Standalone Snapshot of a My

Workspace and its Shared Workspace

Creating a Copy of the Shared Workspace

(Optional) Migrating an OFM 2004 Database to

OFM 2007

Exercise 3 Opening an OFM Workspace

Exercise 4 Changing the Database

Exercise 5 Changing the Well Symbol Size

Exercise 6 Changing the Database in a

Workspace

Exercise 7 Reversing the Changes

Review Questions

Summary

Module 2 Project Creation

Prerequisites

Learning Objectives

Lesson 3 OFM Table Types

Lesson 4 Project Creation

Lesson 5 OFM Loadable ASCII Flat

File Formats

Viewing the (ASCII) Text Load Files

TIPS – NUMERIC SIZE

TIPS - Reserved Keywords

Analyzing Data Files

Static Data

Monthly Data