Handout OFM Fund-Int Trisakti-FIN2

OFM One Day
Workshop
Trisakti University
Ni Ketut S. Jyotir
Software Integrated Solutions (SIS)

Schlumberger Jakarta, Indonesia
13 April 2016
Copyright Notice
2004-2014 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, 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
Software application marks used in this publication, unless otherwise indicated,
are trademarks of Schlumberger. Certain other products and product names
are trademarks or registered trademarks of their respective companies or
organizations.
An asterisk (*) is used throughout this document to designate a mark of
Schlumberger.
Table of Contents
About this Manual

Learning Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What You Will Need . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What to Expect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Course Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
2
2
3
4
5
Module 1: Introduction to the Training

Lesson 1: Tour of a Working OFM Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
The Walkthrough Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Walkthrough Project Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Module 2: Groups and Filters

Learning Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Lesson 1: Ad-Hoc Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Exercise 1: Opening an Existing Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Exercise 2: Changing the Color of Grouped Wells . . . . . . . . . . . . . . . . . . . . 15
Lesson 2: Filter by Map Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Exercise 1: Filtering by Zoom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Exercise 2: Using Irregular Zoom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Lesson 3: Filter by Completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Exercise 1: Filtering by Completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Procedure 1: Enabling the Auto-Zoom Option . . . . . . . . . . . . . . . . . . . . . . . 22
Lesson 4: Well Lists and Filter Archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Exercise 1: Saving an Ad-hoc Grouping as an OFM Well List . . . . . . . . . . 24
Exercise 2: Filtering by a Well List from a Text File . . . . . . . . . . . . . . . . . . . 25
Procedure 1: Saving Filters as an External Well List Text File . . . . . . . . . . 27
Scatter Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Filter Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Procedure 2: Saving a Filter Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Lesson 5: Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Procedure 1: Enabling Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Exercise 1: Filtering using the Filter by Category Option . . . . . . . . . . . . . . . 33
Question . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
OilField Manager Fundamentals Using Oil and Waterflood Production Examples, Version 2012
Lesson 6: Completion Data Grouped in the Navigation Pane . . . . . . . . . . . . . . 36

Exercise 1: Stepping by Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Quality Control Checks for Project Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Exercise 2: Checking Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Lesson 7: Filter by Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Exercise 1: Filtering by Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Lesson 8: Filter by Match . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Exercise 1: Filtering by Match . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Lesson 9: Filter by Table Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Exercise 1: Filtering by Table Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Question . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Exercise 2: Identifying Non-Producing Completions . . . . . . . . . . . . . . . . . . 55
Exercise 3: Finding the Last Database Date . . . . . . . . . . . . . . . . . . . . . . . . 56
Exercise 4: Identifying Low Rate Completions . . . . . . . . . . . . . . . . . . . . . . . 57
Lesson 10: Project Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Exercise 1: Using the Project Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Exercise 2: Using Multiple Project Filters . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Module 3: Project Variables

Lesson 1: Project Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Lesson 2: Calculated Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
System Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Exercise 1: Creating a Calculated Variable Representing the Gas-Oil
Ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Exercise 2: Preventing Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Production Rate Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Exercise 3: Creating a (Monthly) Calendar Day Average Oil Rate
Calculated Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Exercise 4: Creating a Cumulative Calculated Variable . . . . . . . . . . . . . . . 77
Exercise 5: Using Calculated Variables to Find Single Values . . . . . . . . . . 79
Exercise 6: Displaying the Results of Calculated Variable Creation . . . . . . 82
Question . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Exercise 7: Creating Text Display Variables . . . . . . . . . . . . . . . . . . . . . . . . 85
Exercise 8: Displaying Text Display Variables on a Plot Header . . . . . . . . . 86
Exercise 9: Loading Additional Project Calculated Variables . . . . . . . . . . . . 88
ii
Module 4: Plots
Lesson 1: Basics of Plotting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Exercise 1: Creating a Graph with One Y-Axis . . . . . . . . . . . . . . . . . . . . . . 94
Exercise 2: Modifying Graph Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Exercise 3: Inserting an Image in the Plot Header . . . . . . . . . . . . . . . . . . . 100
Exercise 4: Adding Curves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Exercise 5: Changing the Size or Location of Your Plot . . . . . . . . . . . . . . 103
Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Exercise 6: Creating a Graph with Two Y-Axes . . . . . . . . . . . . . . . . . . . . . 106
Exercise 7: Creating a Plot with Multiple Graphs . . . . . . . . . . . . . . . . . . . . 107
Procedure 1: Viewing a Graph up Close . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Exercise 8: Using the Solutions Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Lesson 2: Plots Comparing Multiple Entities . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Exercise 1: Creating a Plot Comparing Multiple Completions . . . . . . . . . . 116
Exercise 2: Using Stacked, Sum, Average,
and % Contribution Plot Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Exercise 3: Creating a Plot Comparing Multiple Groups . . . . . . . . . . . . . . 124
Lesson 3: Plot Annotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Exercise 1: Adding a Table to the Project . . . . . . . . . . . . . . . . . . . . . . . . . 130
Exercise 2: Preparing a Plot to Annotate . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Lesson 4: Plot-Related Tools and Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Exercise 1: Viewing X-Y Data Pairs with Corresponding Points on the
Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Exercise 2: Analyzing Information using the Compute Line Feature . . . . . 141
Question . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Exercise 3: Adding a Group Average to the Plot . . . . . . . . . . . . . . . . . . . . 146
Procedure 1: Saving the Setup of a Plot . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Lesson 5: Water Production Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Exercise 1: Importing Calculated Variables for Creating the Chan Plot . . . 150
Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Module 5: Reports
Learning Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Lesson 1: Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
iii
Lesson 2: OFM Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Report Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Exercise 1: Creating a Time-Dependent Report . . . . . . . . . . . . . . . . . . . . 159
Waterflood Performance Analysis Using Reports . . . . . . . . . . . . . . . . . . . 162
Exercise 2: Reporting Waterflood Performance . . . . . . . . . . . . . . . . . . . . . 164
Lesson 3: Report Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Exercise 1: Formatting a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Exercise 2: Setting Date and Sort Options . . . . . . . . . . . . . . . . . . . . . . . . . 171
Exercise 3: Including Ad-Hoc Calculations in a Report . . . . . . . . . . . . . . . 178
Exercise 4: Generating a Summary Report . . . . . . . . . . . . . . . . . . . . . . . . 181
Exercise 5: Using the Report Gallery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Exercise 6: Applying the Gallery Option for a Summary By Item
Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Lesson 4: Save and Export Options for Reports . . . . . . . . . . . . . . . . . . . . . . 191
Procedure 1: Saving the Setup of Your Report . . . . . . . . . . . . . . . . . . . . . 192
Procedure 2: Saving the Results of Your Report to a Text or CSV File . . . 193
Procedure 3: Exporting to Microsoft Excel . . . . . . . . . . . . . . . . . . . . . . . . 194
Exercise 1: Exporting a Report to an Access Table . . . . . . . . . . . . . . . . . . 197
Lesson 5: Data Visualization Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Exercise 1: Sending a Report to a Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Exercise 2: Sending a Plot to a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Module 6: Simple OFM Forecasting

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Lesson 1: Forecast Set Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Exercise 1: Identifying Completions of Interest . . . . . . . . . . . . . . .. . . . . . . 208
Forecast Variable Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Exercise 2: Creating the Calculated Cumulative Oil Variable for
Forecasting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Exercise 3: Setting Up a Forecast Association . . . . . . . . . . . . . . . . . . . . . . 211
Lesson 2: Forecast Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Historical Regression (History Match) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Upper and Lower Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Exercise 1: Setting a Lower Limit Line . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Exercise 2: Setting an Upper Limit Line . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Exercise 3: Excluding Data Points with a Range Limit . . . . . . . . . . . . . . . . 217
Exercise 4: Toggling Working Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
iv
OilField Manager Fundamentals Using Oil andWaterflood Production Examples, Version 2012
The Variable Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

Exercise 5: Using a Calculated Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Exercise 6: Digitizing Data Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Lesson 3: History Match Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Fit Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Procedure 1: Finding the Best Exponential Fit . . . . . . . . . . . . . . . . . . . . . . 224
Procedure 2: Constraining the b Value to a Range . . . . . . . . . . . . . . . . . . . 224
Procedure 3: Initiating Manual Fit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Future Performance Forecasting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Procedure 4: Viewing Historical Regression Attributes . . . . . . . . . . . . . . . 227
Procedure 5: Viewing Forecast Attributes . . . . . . . . . . . . . . . . . . . . . . . . . 228
Edit Scenario Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Exercise 1: Single Entity (Individual) Forecast Settings . . . . . . . . . . . . . . 231
Saved Forecast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Procedure 6: Recalling a Saved Forecast or Working Forecast . . . . . . . . . 238
The Forecast Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Exercise 2: Controlling the Curve to Display . . . . . . . . . . . . . . . . . . . . . . . 239
Exercise 3: Controlling Graphic Attributes . . . . . . . . . . . . . . . . . . . . . . . . 241
Exercise 4: Editing Forecast Graph Headers . . . . . . . . . . . . . . . . . . . . . . 242
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Module 7: Additional Forecasting Features

Lesson 1: Gas and Water Phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Exercise 1: Switching Between Gas and Water Phases . . . . . . . . . . . . . . 247
Exercise 2: Forecasting with User-Defined Phases . . . . . . . . . . . . . . . . . . 250
Lesson 2: Additional Scenario Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Exercise 1: Configuring a Two-Schedule Forecast . . . . . . . . . . . . . . . . . . 253
Start and End Time Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Reserve Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Procedure 1: Adding Default Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Exercise 2: Creating a Forecast with User-Defined Parameters . . . . . . . . 258
Lesson 3: Re-Initializing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Exercise 1: Simulating the Effect of Rate Acceleration . . . . . . . . . . . . . . 261
Lesson 4: Group Forecasting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Exercise 1: Forecasting Group Oil . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Procedure 1: Forecasting Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Lesson 5: Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Procedure 1: Setting Up a Default Base Case . . . . . . . . . . . . . . . . . . . . . . . 269
Procedure 2: Creating a New Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Procedure 3: Reassigning the Current Case . . . . . . . . . . . . . . . . . . . . . . . 270
Procedure 4: Changing the Order of the Display . . . . . . . . . . . . . . . . . . . . . 271
Compare Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Exercise 1: Creating New Futures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Procedure 5: Comparing Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Lesson 6: Ratio Forecast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Exercise 1: Creating a Water Cut Forecast . . . . . . . . . . . . . . . . . . . . . . . . 276
Other Fluid Cuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Lesson 7: Calculated Forecast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Procedure 1: Creating a Calculated Forecast . . . . . . . . . . . . . . . . . . . . . . . 280
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
vi
OilField Manager Fundamentals Using Oil andWaterflood Production Examples, Version 2012
Schlumberger
About this Manual
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 subtopics and keywords. You also can take
advantage of award-winning Schlumberger Information Solutions
support offered to all SIS customers.
The training provides participants with as much hands-on
experience as possible. To minimize the repetition of terminology,
you are encouraged to use the help file. This training material
provides sufficient information for you to be able to perform the
basic functionality supported by OFM.
Advanced training with OFM is addressed in other courses, which
you can take after completing this course.
NOTE: Unless it is specifically stated, the word application
refers to OFM and the terms database, workspace, and
project encompass both the database and the
workspace.
Learning Objectives
After completing this training, you will know how to:
navigate an existing OFM project
set up the base map
filter to the completions of interest using a variety of

techniques
define calculated variables
analyze project data using the OFM modules of plotting and

reporting
export data and other text files for use in this or another OFM
project.
About this Manual
Schlumberger
What You Will Need

In this training you will need the following software:
OFM, properly installed and licensed
Training data sets.
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 (if applicable)
Lessons, explaining a subject or an activity in the workflow
Procedures, showing the 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
Scenario-based exercises
Questions about the module
Summary of the module.
You will also encounter notes, tips, and best practices.
About this Manual
Schlumberger
Course Conventions
Content in this manual uses the following conventions.
Characters in Bold
Represent references to dialog box names,

application areas, or commands to be
performed.
For example, "Open the Open Asset Model
dialog."
Denote keyboard commands. For example,
"Type a name and press Enter."
Identify the name of Schlumberger software
applications, such as ECLIPSE* or Petrel*.
Fixed-width
Indicate variable values that the user must

supply, such as <username> and
<password>.
Characters in italics
Represent file names or directories, such as

"... edit the file sample.dat and..."
characters inside <>

triangle brackets
Represent option areas in a window, such as

the Experiments area.
Identify the first use of important terms or
concepts.
For example, "compositional simulation" or
safe mode operation.
Characters in
fixed-width
Represent code, data, and other literal text

you see or type.
For example, enter 0.7323.
NOTE: Text you must enter is indicated in a fixed-width font or a

fixed-width font inside triangle brackets. Do not include
the brackets when you enter the required information.
Instructions to make menu selections are also written using bold
text and an arrow indicating the selection sequence, as shown:
1. Click File menu > Save. (The Save Asset Model File dialog
box opens.)
OR
Click Save Model
An OR is used to identify an alternate procedure.
Schlumberger
About this Manual
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.
Schlumberger
About this Manual
Summary
In this introduction, we:
defined the learning objectives
outlined what tools you will need for this training
discussed what you will encounter within this material.
Schlumberger
About this Manual
NOTES
Introduction to the Training
Schlumberger
Module 1 Introduction to the

Training
In this class, you will be exposed to many features of OFM in a
way that closely matches the way in which you are likely to use
the application. The manual leads you through the features
following a path that corresponds with normal workflow
processes.
Lesson 1
Tour of a Working OFM Project
Over the course of this training, you will be exposed to many

features and capabilities of the OFM application.
While these processes are vital in preparing a project for
subsequent analyses, they can be difficult to understand (and
even boring) when you cannot see the end product for which the
application is renowned.
With this very real concern in mind, it is worthwhile to start your
OFM learning experience with a tour of a fully populated working
OFM project.
The Walkthrough Project

Your instructor will provide a copy of the OFM project you will use
for this session. Notice that it is not intended as a learning
exercise, but rather for familiarization with a project.
Your instructor will open the project and guide you through the
features you will explore later. You are welcome to follow along
with your own copy of the project, but it is important to remember
that your primary role right now is to watch what can be done with
OFM. Do not ask How did you do that? at this time. There will be
many opportunities for explanations.
Schlumberger
Your instructor will perform these tasks:

1. Launch OFM.
2. Open the Walkthrough project found at \OFM 2012 Oil
Fundamentals\A Walkthrough Project\Walkthrough
2012.ofm.
3. Open the base map.
Arrange panes, stacked left and right.
Modify the grid and frame attributes.
Show deviation surveys, with completions at surface and
then bottomhole location.
Use the Zoom features to explore the base map.
4. Examine data in these tables.
Master table (HEADERID)
Monthly Production (MONTHLYPROD).
5. View the definitions of one or two simple calculated
variables, such as Oil.CalDay and Water.Cut.
6. Perform simple analyses.
a. Open a plot and a report from the Analysis pane.
b. Choose individual completions for the plot or report.
c. Use the filter and group completions for the plot or report.
d. Observe the use of the Navigation bar for higher level
aggregation, such as Reservoir.
e. Create a multiple curves plot for Cumulative Oil.
7. Work with units by changing the display units to Metric. (On
the Workspace tab, click Options.)
Hopefully, this quick look at a working OFM project will have given
you a taste for the kinds of simple analyses that are achievable.
The balance of the training shows you how to create these results
quickly and efficiently in any OFM project.
Schlumberger
Walkthrough Project Components

The Walkthrough project and all other OFM projects are
comprised of two components: the database and the workspace.
The database is often an Access database but it also can be an
Oracle or SQL Server database. It contains the data structures
(tables) and the data itself.
The .ofm file is what we call the workspace. It contains everything
else that has been saved in the project, including properties of the
variables (such as units and plot color), templates for plotting and
reporting, well lists, and calculated variables. In other words, it
contains all of the configuration information about the project.
The primary method of introducing the features of OFM will be by
completing and analyzing an OFM project. Features will be
introduced and explored as they are required. In this way, the
value of the application will be illustrated as a tool for managing
your own analytical workflows, as opposed to showing you
buttons to push without truly learning the features.
It is important to recognize that the exercises you will work
through are simply examples. As you will quickly discover, OFM
can be configured to perform an unlimited variety of tasks that
easily can be adapted to any of your specific workflows.
Project Configuration: OFM Workspace and Base Map Customization
Schlumberger
NOTES
10
Schlumberger
Groups and Filters
Module 2 Groups and Filters

Grouping and filtering are two separate (but related) functions
critical to the OFM problem-solving process.
Grouping is a process in which all of the completions in the current
filter are combined together and one set of results is presented at
the group level. The data are summed or averaged, depending on
settings applied in the Edit Schema Tables dialog. Plots and
reports automatically respond and display the result of the
aggregation process.
The hierarchy of an OFM project is captured through the creation
of categories. In this way, OFM understands, for example, which
completions belong to Zone V and which completions belong to
Flow Station SE. Categories are a special form of grouping and
are described in more detail in Lesson 5.
When using visualization tools, such as plots and reports, you can
quickly display a visualization of the performance of a Category
(Zone or reservoir) because OFM knows which completion data
must be aggregated to produce the visualization. This will become
clearer when discussing plots and reports.
Filtering is a technique used to reduce the list of completions to a
more manageable and workable selection. In practice, an OFM
project can contain many thousands of completions but you might
be interested in (or responsible for) only a subset of the full
project.
11
Groups and Filters
Schlumberger
The concept of filtering in OFM has proven to be very useful, as

good filter criteria can optimize the time to perform analysis, help
guarantee correct results, and maximize productivity. The OFM
Filter pane is shown in Figure 6.
The Filter pane offers many tools for effectively creating and
saving filters. The application of filters is temporary and does not
survive into the next OFM session; however, many of the filtering
techniques can be saved for use again later.
The exception to this rule is the Project filter, which remains
permanently in effect until you disable it. This filter can be
extremely useful if you are responsible for a subset of completions
because your OFM project will always show only that subset.
12
Groups and Filters
Schlumberger
Learning Objectives
In this module, you will learn how to create a project filter and
perform ad-hoc filtering and grouping in many ways.
map techniques
completion
well lists and archives
categories
OFM queries
match
table data.
Lesson 1
Ad-Hoc Groups
You can group together completions in the current filter in three

ways.
On the Home tab, in the Select well group, click the Group
button.
On the toolbar above the Filter pane, click the Group button.
On the Filter pane, click the Group button.
Several indicators let you know the completions have been

grouped.
The Navigation toolbar at the top of the OFM main window

that normally displays a completion identifier now shows a
group name.
The completions on the base map change color and display

in pink.
If you have a plot or a report open when you group the

completions, the group results are automatically displayed
instead of the results for an individual completion.
To ungroup completions, choose one completion from the

Navigation toolbar or the Navigation pane. The completions on
the base map will no longer display in pink.
13
Schlumberger
Groups and Filters
The lessons and exercises that follow introduce you to a variety of

methods for reducing the number of completions in a project to the
subset you wish to work with, either on a temporary or semipermanent basis.
Exercise 1
Opening an Existing Plot
The results of various filtering techniques are easiest to see if you

open a plot.
1. Locate the Analysis pane.
2. Double-click the plot node PD Rates.
Notice that the base map is still open behind the plot window.
The plot is blank because no entities have been selected.
3. Locate the Navigation pane.
14
Groups and Filters
Schlumberger
4. Click on one of the completion names. The plot will change

to show the data for that completion.
5. Click on a different completion name.

NOTE: The fact that the plot changes completely to display
the data for the selected entity is one of the most
flexible features of OFM. Thus, the PD Rates plot
node is a template rather than a saved plot
containing data for a specific entity.
Exercise 2
Changing the Color of Grouped

Wells
There can be occasions when grouped wells are difficult to

distinguish from non-grouped wells. Gas wells, for example,
where the symbol is typically red, might not be easy to identify. In
this exercise, you change the color of grouped wells on the base
map so that they are easier to see.
1. On the Workspace tab, click Options.
2. In the Options window, click the Maps tab.
15
Schlumberger
Groups and Filters
3. Change the setting Color of grouped wells on the base map to

Cyan and click OK.
4. Save the workspace.
Lesson 2
Filter by Map Techniques
A highly visual and interactive way of screening out unwanted

completions is to use the base map itself. There are two ways you
can zoom to selectively view details on the base map: Filter by
Zoom and Irregular Zoom.
16
Groups and Filters
Schlumberger
Exercise 1
Filtering by Zoom
When you zoom into the base map, OFM automatically creates a
filter containing the completions visible on the map.
1. Choose the base map.
2. On the Format tab, in the Zoom group, click Zoom Area
3. Use the mouse to drag an area on the map and release the
mouse button.
There are two things of note.
A filter named Current Zoom has been created in the Filter
pane.
The Navigation pane now indicates the reduced list of
completions.
TIP: The Zoom Area button allows you to filter using the
map. The Zoom In button magnifies only the map; it
does not filter. It is used much less frequently than
Zoom Area.
4. On the Home tab, in the Select Well group, click Group.
Notice that the well symbols on the map turn cyan in color.
17
Groups and Filters
Schlumberger
5. Choose the PD Rates plot. Notice that the heading and

legend both indicate a name for the ad-hoc group.
WARNING: ALL subsequent work in OFM will apply only to

these completions until you clear or modify the filter
on this list.
To clear the filter, click Clear Filter
on the
Home tab, in the Select Well group, or on the Filter
pane toolbar.
18
Groups and Filters
Schlumberger
Exercise 2
Using Irregular Zoom
The Zoom Area technique works well if you are interested in

completions within one geographic area that fit nicely into a
square or rectangle. However, sometimes they do not. The
Irregular Zoom option allows you to zoom in on a specific area of
the base map using an irregular polygon.
1. On the Format tab, in the Zoom group, click Irregular Zoom.
The cursor shows an irregular shape at its base.
2. Choose the area of interest on the base map by repeatedly
clicking with the left mouse button to draw a polygon.
OFM automatically joins the points.
3. When the polygon is virtually complete, right-click and select
Done from the shortcut menu.
You are zoomed in on the selected area and filtered to those
completions.
4. To zoom out, click Zoom To Fit.
Lesson 3
Filter by Completion
There could be occasions when you need to work on many

completions that have nothing in common. For example, there
could be an area on the map where completions are not located
near each other so they cannot be chosen from a map zoom or
there could be project data that are not shared, such as the
reservoir or business unit.
Completions could be provided to you in the form of a list of well
names. In this situation, the Filter by Completion option is
probably the only way of creating the subset you need.
19
Schlumberger
Groups and Filters
Exercise 1
Filtering by Completion
You have been provided a list of wells that could be candidates for
remedial activity and you have been asked to look at them.
1. In the Filter pane, click Filter By Completion
The Filter By Completion window displays.

TIP: Click Clear to remove any previous selections or click
Select All to highlight all completions. Clicking the
column headers automatically sorts the well entities.
TIP: By default, the Filter by Completions dialog displays
two columns in one screen: the Completions column,
which is fixed, and a second column that is not fixed.
It defaults to show the Alias of each completion but you
can select an alternate static variable, such as Zone.
20
Groups and Filters
Schlumberger
2. While holding down the Ctrl key, use the mouse to choose
these completions.
HOGL3_1029
HOGL9_0632
HOGLA-0232
HOGL3_1129
HOGL7_0232
HOGLA_1529
HOGL732
3. Click OK.
The Filter by Completions dialog closes and the base map
displays.
Note that, in the Navigation pane, you are now restricted to

only the seven selected (filtered) completions. All others are
temporarily screened out.
21
Schlumberger
Groups and Filters
Procedure 1 Enabling the Auto-Zoom Option

The base map does not automatically adjust to display the
selected wells but you can change this.
1. On the Workspace tab, click Options.
2. On the Options window, click the Maps tab.
3. Check the box for Auto zoom map around selected wells.
4. Click OK.
The Options window closes.
5. On the Home tab, in the Select well group, click Group.
22
Groups and Filters
Schlumberger
6. Choose the PD Rates plot.

Notice that the plot reflects the grouping. The heading and
the legend both display a name for the ad-hoc group.
Lesson 4
Well Lists and Filter Archives
In the Lesson 3, you selected completions of interest from a list.

For future analysis of these completions, it would be timeconsuming and inconvenient to have to use the Filter by
Completion technique each time. The solution is to save the
filtered list.
Filtered lists can be saved in two ways, either as an ad-hoc
grouping or as a well list from a text file.
In these exercises and procedures, you will look at saving the
filtered list as a Well List and explore alternative ways of saving a
filter list.
23
Schlumberger
Groups and Filters
Exercise 1
Saving an Ad-hoc Grouping as an

OFM Well List
1. From the Filter pane, click Well List.

2. Right-click and select Add.
3. Click Set From Current Filter.
This causes the completions in the current filter to be listed in
the Edit Well List dialog.
4. Click OK.
5. Enter the name Possible Workovers to replace the
default name Well List1.
6. Clear the filter by clicking Clear Filter.
24
Groups and Filters
Schlumberger
7. To reactivate the well list, from the Filter pane, under Well
List, select the checkbox beside the list Possible Workovers.
The project is filtered to the same seven completions.
Exercise 2
Filtering by a Well List from a Text

File
Consider this variation on the scenario in Exercise 1. Instead of

selecting specific completions one by one, suppose you have a
text file that contains the list of completions. For example,
someone in the field has emailed you a list of completions that
have problems with missing data.
NOTE: The completion identifiers must match those being used
as the key identifier in your OFM project.
25
Schlumberger
Groups and Filters
The text file shown in Figure 7 can be found at \OFM 2012 Oil
Fundamentals\D Filtering and Grouping\Missing data.txt.
Figure 7
Sample file: Missing data.txt
1. In OFM, from the Filter pane, click Well List.

2. Right-click and select Open.
3. Navigate to and choose the text file.
The new well list appears in the Filter pane as Missing
data1.
Like the previous well list, this well list can be reused any
time by selecting its checkbox.
4. Open plot PD Rates.
26
Schlumberger
Groups and Filters
5. Scroll through the completions and observe the lack of late

time data.
Procedure 1 Saving Filters as an External Well

List Text File
An external well list stores the list of completions that meet the
filter criteria to a text file. Just as you opened the well list text file of
completions with missing data in the Exercise 2, any new well list
text file you create using this method could be opened in this or
another OFM project that contains the same completions.
1. From the top of the Filter pane, select Save > To Well List.
The Well List dialog displays.
2. Enter the desired name in the File Name field and click Save.
27
Groups and Filters
Schlumberger
Scatter Sets
A scatter set organizes the completions either by category or filter
name and is used by the Scatter Plot module. This activity is
discussed in the OFM Intermediate course.
Filter Archive
A filter archive is similar to a well list, but it is more flexible and
powerful. If your filter is the result of many steps, including
querying and nested instructions, it is useful to save the procedure
(steps) itself. Filter Archive helps you achieve that goal.
Another useful feature of the Filter Archive approach is that
recalling the list re-runs the queries that were used to create it.
The query might return a different result (list) each time you run it
and sometimes this is desirable.
For example, you might wish to know if a list of low oil producers is
growing over time. Re-activating the filter lets you know if this is
true.
You will also find later, in Module 5, that filter archives also are
useful when plotting.
28
Schlumberger
Groups and Filters
Procedure 2 Saving a Filter Archive

A Filter Archive allows you to save your query steps and reuse
them. This is especially useful if your query procedure has many
steps.
1. After applying the filter, click the drop-down arrow to the right
of the Save Filter icon and select To Archive.
The Add Filter Archive dialog displays.
29
Schlumberger
Groups and Filters
2. Enter a name in the Filter Archive Name field and click OK.
3. View the Filter Archive pane by clicking the tab behind the
Filter pane.
NOTE: To apply the archived filter criteria, double-click on
the archive or right-click on the archive and select
Load from the shortcut menu.
30
Groups and Filters
Schlumberger
Lesson 5
Categories
Categories are one of the most useful methods for both filtering
and grouping.
To work with the hierarchy in your project (completions, wellbores,
reservoirs, fields, and platforms) you will use the concept of OFM
Categories. Each completion is associated, or mapped, to its
corresponding entry at the higher level in the hierarchy, such as
Completion X5 is in Reservoir A.
After these mappings are made, OFM knows that to display a plot
of oil production for Reservoir A, for example, it should aggregate
all the individual oil production volumes for each completion
associated to Reservoir A.
Mapping information is stored in static tables; any text field in any
static table can be used to define a Category. You will find that
most of these properties are found in the Sc table in the Provo
East project.
NOTE: Sc is an old abbreviation for the legacy term Sort
Category.
In your projects, you can hold Category information in any number
of static tables.
31
Schlumberger
Groups and Filters
Procedure 1 Enabling Categories

1. On the Setup tab, in the Workspace Managers group, click
Categories.
The Categories window displays.
The full list (on the right) represents every text field in every
static table in the project. Note the existing enabled
(checked) categories. Each enabled (checked) category is
also listed on the left.
2. Enable the Geometry option by selecting its checkbox. Note
that it, too, now displays on the left, confirming that it is now
an OFM category.
Clearing (unchecking) a box in the Category Name column
disables it.
WARNING: There is an option on this dialog to use numeric
columns from your tables as Categories. Use
the Show All Fields (text and numeric) checkbox
option with caution; it can cause round-off errors
for non-text fields.
32
Groups and Filters
Schlumberger
3. If you wish to finish at this time and save your changes, click
OK.
Exercise 1
Filtering using the Filter by

Category Option
Although Categories are primarily designed for the purpose of

aggregating data, they contain valuable information that also can
be used to filter your project.
1. Clear the filter.
2. On the Filter pane, expand Category and expand Flow Station.
3. Choose TB0532.
The base map and the Navigation pane show 13
completions have been mapped to this Flow Station.
33
Schlumberger
Groups and Filters
4. Choose completions that are mapped to either Flow Station

TB0532 or TB0539 by selecting both options.
5. The base map and Navigation pane now show 82
completions, which means that Flow Station TB0539
contains 69 completions.
Confirm this by clearing the Flow Station TB0539 option.
6. Expand Zone and notice that, although all entries are listed,
three are in bold.
This is because your filtered completions (only those in Flow
Station TB0532) also are mapped only to Zones II, III, and
IVA. In other words, none of the completions in your filter are
in Zone IC or IVB.
7. Choose Zone III (current total now 10 completions).
34
Schlumberger
Groups and Filters
8. Group the wells and choose the PD Rates plot.

Notice that the heading and legend both indicate an
appropriate name for the ad-hoc group.
Question
In Step 7, what would happen if you checked Zone IC instead of
III?
35
Schlumberger
Groups and Filters
Lesson 6
Completion Data Grouped in

the Navigation Pane
In the Lesson 5, you used Category information for filtering. While

this is a useful feature, Categories are primarily used for stepping
up and down through the project hierarchy. (The old name for the
Navigation pane was the Step pane.) In other words, the
Navigation pane can be set to automatically group the completion
data one category at a time.
For example, if you were interested in only one specific flow
station, you could filter by category to that flow station and group
the completions.
On the other hand, if you were interested in seeing graphs of the
total production for each flow station, one after another, it would
be more convenient to change the Step in the Navigation pane to
Flow Station.
This allows you to scroll from one flow station to the next, seeing
the total production rates for each without having to filter, group,
and clear the filter between each Flow Station.
Exercise 1
Stepping by Category

2. Locate the Navigation pane and notice the drop-down list at
the top. The default level is Completions.
3. From the drop-down list at the top of the Navigation pane,
choose Zone.
36
Schlumberger
Groups and Filters
Note that, instead of listing completions, the Navigation

pane now lists Zones and indicates there are five Zones.
Beside each zone is a number, advising you how many
completions are currently mapped to that zone.
4. Choose the PD Rates plot.
37
Schlumberger
Groups and Filters
5. Choose Zone IVA.

Observe how the plot now automatically aggregates all the
data for completions in Zone IVA and displays the result.
6. Choose another zone from the list and watch the plot
automatically update.
Observe, also, that the name of the entity whose data you
are plotting appears in the Navigation toolbar as well as in
the header at the top of the plot.
7. Return to the Navigation pane and choose Flow_Station.
38
Schlumberger
Groups and Filters
8. Choose Flow Station TB0539.
9. Explore the other levels (categories) and their effect on the

plot.
An important point to note here is that this is all happening in
the same plot. The plot has been configured to display only three
variables.
You choose the entity to be evaluated: Completion, Wellbore,
Zone, or Flow Station. The choice is not controlled by the design
of the plot. As a result, the plot is universal in scope.
Compare this to an Excel spreadsheet. To monitor this project,
you most likely would need one chart per completion (87) plus one
for each Category entry (14) for a total of 101 Excel charts.
39
Schlumberger
Groups and Filters
Quality Control Checks for Project Data

The categories you have dealt with so far can become a useful
tool for quality control. It is important that every completion be
mapped to its correct category values. If this is not done, you run
the risk of viewing incorrect data and possibly making a bad
decision based on this data.
For example, if some completions are not mapped to their Flow
Stations and you perform an analysis of Flow Station production
to make a decision on surface facility sizing, you could be
underestimating the production rates.
Exercise 2
Checking Quality
1. On the Navigation pane, change the step back to the default

value of Completions.
2. On the Filter pane, expand Category, then select Pool.
A possible error in mapping might be evident here based on
the category labeled <N/A>.
3. Enable the checkbox beside the <N/A> value of Pool.
4. On the Navigation pane, observe that four completions are
mapped to the Pool labeled <N/A>.
This actually means that these completions have not been
mapped to ANY Pool. At this time, you do not know if this is
important or not.
40
Schlumberger
Groups and Filters
Check to see if these completions have a production history

and will, therefore, contribute to the analysis of the project.
5. Determine if the completion has had production in one of two

ways.
Choose the plot PD Rates and click the completion name.
Use the Table Data filter option on the Filter pane to find out
if it has data in the PRD table.
41
Groups and Filters
Schlumberger
6. Because all the completions show data on the plot and are
included in the PRD Table Data filter, they are active.
However, they have not been mapped to a Pool so there is
an error in category mapping.
42
Schlumberger
Groups and Filters
To correct this error:

a. On the Setup tab, in the Tables group, click Data Grid.
The Select OFM Table to Edit window displays.
b. In this project, the information mapping each completion
to its corresponding Pool is in the table named Sc.
Select the Sc table and enable the Edit all records
checkbox.
c. Scroll to the right to view the Pool column. Notice that the
cells are blank.
d. Place your cursor in the blank cell and enter BLM A.
e. Repeat Step d for the other completions with missing
information in this column.
f. Click any cell in a different row to save the change to the
database.
NOTE: You do not have enough time to comprehensively QC
the entire project but this procedure is a good start in
using the application to find errors in the raw data.
43
Schlumberger
Groups and Filters
7. While you have the Sc table open, scroll through it and look
for any other blank cells, which could indicate mapping
errors. (There should be no errors.)
8. Close the Sc table.
Lesson 7
Filter by Query
You have performed several filtering techniques that deal with the
static properties or attributes of your entities, such as by category.
You also have seen the power of using dynamic data to create
calculated categories. As you know, the most important data are
production data, which change over time.
To create ad-hoc filters using dynamic data, use the Filter by
Query option. Unlike calculated categories, this does not require
that custom calculated variables exist beforehand.
For example, it would be very useful to know which completions
have had the highest production rates throughout their lives. You
will use a query to select the completions that have produced PD
(producing day) oil rates of higher than 100 b/d at least once in
their production history. The table variable that you will query is
PRD.PDOil.
BEST PRACTICE: When referring to a table variable, OFM
adopts the naming convention of
tablename.columname. In this instance, the
table name is PRD and the column name is
PDOil. (OFM is not case-sensitive.)
44
Schlumberger
Groups and Filters
Exercise 1
Filtering by Query
Filter by Query allows you to create an ad-hoc filter for dynamic

data.
1. Clear the current filter.
2. From the Filter pane, right-click on OFM Query.
A shortcut menu displays.
3. Select Add.
The OFM Query window displays.
45
Groups and Filters
Schlumberger
4. Click Edit.
The Create Query window displays.
5. In the text window, enter PRD.PDOil > 100.

TIP: You can enter the expression or you can quickly select
the variables you need for the expression by choosing
them from the list prompted by the Project Variables
button (the default listing view).
This listing contains table variables, together with any
Calculated Variables that were created in the project.
To use any one of these, either double-click on an item
or highlight it and click Add.
46
Schlumberger
Groups and Filters
6. Click OK to return to the OFM Query window.

The filter query statement displays next to the Edit button.
7. Because you wish to see the completions that have

produced more than 100 b/d at least one time, leave the
default value of 1 in the time(s) box and click OK.
8. OFM automatically assigns a name to the new query (Ofm
Query1).
Change this name to Best Oil Rate and press Enter.
NOTE: Next to the query name, the checkbox is selected.
OFM automatically applies the filter. The base map
appears with 64 completions.
47
Groups and Filters
Schlumberger

Many of these wells probably had high rates shortly after
completion, but you are searching only for those that had
high rates later in the project, so you must add a time
limitation to your query.
11. Access the OFM Query window again by right clicking Best
Oil Rate and selecting Edit.
12. In the OFM Query dialog, click Edit and then extend the
expression to read:
PRD.PDOil > 100 & Date >= 20040101
BEST PRACTICE: Note the OFM convention for dates
YYYYMMDD.
NOTE: In the above statement, the AND operation told OFM
to apply the filter only to monthly PD oil rate records
from January 1st, 2004, ignoring all records before
that date.
Without this extra date criterion, the query asks for
the oil rate to be greater than 100 b/d anytime in the
well's life, which could have been decades ago.
13. Click OK.
You are returned to the OFM Query window.
14. Click OK to save the query.
15. The OFM Query window closes.
17. Select the checkbox to the left of the query Best Oil Rate.
You should see 55 completions returned, meaning that these
completions had a PD oil rate of at least 100 b/d in their
producing history since January 2004.
18. Edit the query again.
19. Enter 3 in the time(s) text field so that at least two instances
of the criteria are met.
48
Schlumberger
Groups and Filters
20. Select the Consecutively checkbox.
21. Click OK to save the query.

The OFM Query window closes.
23. Select the checkbox to the left of the query Best Oil Rate.
You should see 42 completions returned, meaning that
although 55 completions had rates higher than 100 b/d, only
42 were able to sustain that rate for more than three months.
24. Right-click on Best Oil Rate and select Edit.
25. Now you will extend the query to check for gas production.
Here, you are searching for completions that have high oil
and low gas production, with PD gas rates of less than 50
Mcf/d.
Append this line to the end of the previous query statement:
& PRD.PDgas < 50000
WARNING: When querying, the values that you enter as
your criteria are expressed in the base units,
ignoring multipliers.
For oil rates, this is usually not an issue but
when dealing with gas rates, a normal
convention is to display in units of Mcf/d. The
base units are cf/d, so you must query in cf/d.
49
Groups and Filters
Schlumberger
26. Run the query again. Only 22 completions return.

28. Review the PD Rates plot for the 22 completions.
In spite of the fact that these completions have had the
highest rates, notice that less than half them are still
producing as of the final project date (January, 2009).
In terms of short-term rates, they have been the best
producers but, in terms of total production and dependable
operation, they have not.
TIP: Rewriting the expression with parentheses will return
the same result. However, by adding parentheses, the
query statement is more readable and manageable.
(PRD.PDOil > 100) & (Date >= 20040101) &
(PRD.PDgas < 50000)
The order of precedence is very important in any type
of query language. Parentheses ensure that the query
is evaluated in the order you specify and helps avoid
unnecessary errors. It is a good idea that you develop
the habit of adding parentheses.
NOTE: OFM supports nested filtering (or stage filtering),
which means you can apply your current filter on the
previously filtered list.
For example, you could first filter by category Zone,
then filter by a query similar to this one to find highest
producing wells within a specific zone. This operation
cannot involve Clear Filter.
50
Schlumberger
Groups and Filters
Lesson 8
Filter by Match
OFM provides a Filter by Match option. This enables you to

search for the list of desired completions by name instead of using
the Filter by Completion option. The match can be performed by
completion name or alias name.
Exercise 1
Filtering by Match
Use Filter by Match to search for completions by name.

2. In the Filter pane, right-click on Match.
3. Select Add.
The Match dialog displays.
4. In the Completion Key Match field, enter PVE* and click OK.
(This option is not case sensitive.)
TIP: The asterisk (*) wildcard cannot be used as a prefix (for
example, *A). Instead, you can use the (?) wildcard.
For example, ???601 would find all completions with
601 starting in the 4th position of their names.
The Match dialog closes and you are returned to the OFM
main window. The filter does not run immediately. OFM first
offers you the opportunity to give this filter a name, as it will
be saved for future recall.
51
Groups and Filters
Schlumberger
5. Change the name to PVE and press Enter.

Notice that there is a check mark next to PVE in the Filter
pane, because OFM automatically applies this filter. The map
displays 13 completions that satisfy the filter criteria.
Lesson 9
Filter by Table Data
It is often useful to screen out completions that have no data to

display, such as in a plot or report. (This avoids wasting paper by
printing empty plots). To achieve this, use the Filter by Table Data
option.
For example, in the process of becoming familiar with the fields
included in the OFM project, it is important to know if there is any
pressure data, how many completions have these data, and which
completions they are.
Not only is this useful in terms of understanding the project data, it
also can be very convenient. Suppose you are working on an
analysis of pressure data. You would waste a lot of time trying to
scroll through potentially hundreds of completions, looking for
those that have pressure data if you did not have the ability to filter
by table data.
52
Schlumberger
Groups and Filters
Exercise 1
Filtering by Table Data
Filtering by Table Data allows you to choose completions that

contain data in the pressure table.
1. Clear the filter from Lesson 10, Exercise 1 by clicking Clear
Filter
2. Expand Table Data located in the Filter pane.
53
Groups and Filters
Schlumberger
3. Choose the PRS table from the list of tables.

The base map returns all completions with pressure data.
NOTE: The label at the top of the Filter pane shows that 9
completions meet the filter criteria.
NOTE: This process works in the Provo East project
because the pressure data are stored in a table
separate from the production data (PRD).
If you were working with a project having the
pressure data stored in the PRD table, you would
need a query to come up with these results.
5. Choose completions with production data by selecting the
PRD table.
A list of 85 completions that meet this filter criterion is
returned.
7. Choose INJ from the table list. Five completions display.
9. Choose both PRD and INJ tables from the list.
The filter is applied and only the completions that have
records in both tables are displayed on the base map.
Three completions meet the criteria. Although there are five
injection wells in this project, three of them seem to have had
a production history prior to conversion to injection.
Question
What can you say about the two completions that appeared in the
INJ table filter, but that did not appear in this final combined filter?
54
Schlumberger
Groups and Filters
Exercise 2
Identifying Non-Producing
Completions
You now have the skills necessary to identify non-producing

completions that could be considered for reactivation. It would be
beneficial to include only completions that have produced in the
past and exclude completions that have been abandoned.
1. Clear the filter from Exercise 1.
2. Filter by Table Data PRD to ensure that the completions
have produced previously.
3. Filter by Category Current Water: Not Producing to identify
completions that were not producing on the last database
date.
The result is 37 completions.
4. Save these in a filter archive.
a. Click the drop-down arrow to the right of the Save Filter
icon and select To Archive.
The Add Filter Archive dialog displays.
b. In the Filter Archive Name field, enter the name:
Reactivation Candidates.
c. Click OK.
d. Clear the filter.
e. Test the Filter Archive by clicking the Filter Archive tab
behind the Filter pane and double-clicking the archive
name.
55
Groups and Filters
Schlumberger
Exercise 3
Finding the Last Database Date
In Exercise 2 you identified non-producing completions that could

possibly be reactivated after some sort of intervention. This
exercise shows you how to determine the date of the latest
database.
1. On the Setup tab, in the Tables group, click Data Grid.
The Select OFM Table to Edit dialog displays.
2. Choose PRD.
3. Enable the Edit all records checkbox and click OK.
The entire table for all completions displays.
4. Double-click the Date heading to sort the table by Date,

ascending.
56
Schlumberger
Groups and Filters
5. Double-click the Date heading again to sort the table by

Date, descending.
You can see that the last date of the project database is
January 2009.
6. Close the PRD table view.
Exercise 4
Identifying Low Rate Completions
In this exercise, you will identify those producing completions with

low gas rates of less than 30 Mcf/d as of the last project date.
These completions might be considered for workovers. A query
will be the easiest approach.
1. From the Filter pane, right-click on OFM Query.
2. Select Add.
The OFM Query window displays.
3. Click Edit.
57
Groups and Filters
Schlumberger
4. In the text window, enter: (PRD.PDOil < 5) & (Date =

20090101).
NOTE: Remember that query criteria values are expressed
in the base units, ignoring multipliers.
5. Click OK to return to the OFM Query window.
6. Click OK.
7. OFM automatically assigns a name to the new query (Ofm
Query1). Change this name to Low Rates and press Enter.
8. The query runs and filters to a list of 17 completions. Review
the completion and production history of these wells to
determine if any of them are workover candidates.
9. As in Exercise 2, save the filter to a Filter Archive, naming it
Low Rates.
Lesson 10
Project Filter
OFM has many smart-loading algorithms to accelerate opening a

project. The time it takes to open a project depends on the size of
your project. It will take longer to open a 10,000-well project than a
100-well project. The problem can be worse if you are working on
a network project and the network is somewhat slow.
OFM provides a partial solution by pre-filtering the completions.
Applying this type of filtering (named Project Filter) to your project
will cause it to read only the applicable list of completions, saving
load time from reading the excluded wells.
A Project Filter also is very useful in these situations.
Suppose the OFM project was built to include all completions

in the field but you are assigned to only the wells flowing to
the two southern flow stations. It would be much more
convenient for you if the project opens with those
completions already filtered.
Perhaps you are working on an analysis of only the VK 1

pool completions for the coming week. It would be much
more convenient if the project opens pre-filtered to those
completions.
58
Groups and Filters
Schlumberger
Exercise 1
Using the Project Filter
Limit the project to completions that belong to the BLM B pool.

1. Clear all filters.
2. Locate Project Filters in the Filter pane.
3. Right-click Project Filters.

59
Schlumberger
Groups and Filters
4. Select Add from the shortcut menu.

The Edit Project Filter window displays.
5. Pool information is stored in the Sc table. At the top of the

dialog box, select OFM Table: Sc
6. From the drop-down list for Fields, choose Pool.
7. From the drop-down list for Operator, choose = (equal).
8. To avoid having to remember the exact spelling of the
different values of Pool, click Find Field Values. This will
populate the Values drop-down list.
9. From the drop-down list for Values, choose BLM B.
60
Schlumberger
Groups and Filters
10. Click Add to Where.

This causes the following expression to appear in the Where
Clause section of the dialog:
Pool = 'BLM B'.
11. Click OK.

The Edit Project Filter dialog closes.
61
Schlumberger
Groups and Filters
12. OFM gives the new project filter a default name. Change the
name to BLM B and press Enter.
13. Save the workspace

14. Select the checkbox to the left of the newly created project
filter BLM B.
NOTE: In this instance, 62 completions meet the criteria. At
this point, if you were to close the OFM workspace,
upon opening it, the project filter would still be
applied and only 62 completions would display on the
base map.
15. From the Home tab, in the Select well group, click Clear
Filter.
The filter does not change, indicating the semi-permanent
nature of a project filter, unlike all the previous filtering
techniques covered in this module.
62
Groups and Filters
Schlumberger
16. Clear the checkmark to the left of the project filter and click
Yes.
The base map shows all 87 completions.
Exercise 2
Using Multiple Project Filters
From time to time, you might need to work on a different subset of

the main project. OFM supports multiple project filters.
For example, you might wish to conduct analyses on the
shallower wells in the field to determine whether they have lower
water production.
WARNING: Only one project filter can be active at any time.
1. From the Filter pane, right-click Project Filters.
2. Select Add from the shortcut menu.
The Edit Project Filter window displays.
3. In the OFM Table list field, keep the default selection of XY.
4. From the Fields list, choose TDEPTH.
5. Click Add to Where.
6. In the Where Clause section of the dialog, add to the
expression so that it reads:
TDEPTH < 3200.
7. Click OK.
The Edit Project Filter window closes.
8. Enter the name Shallow Wells for the new filter name and
press Enter.
10. Select the checkbox to the left of the newly created project
filter.
The base map displays 24 completions whose total depth is
less than 3,200 feet.
63
Schlumberger
Groups and Filters
WARNING: Applying a Clear Filter action while a Project

Filter is in place causes the completion list to
regress to the result created by the Project
Filter. In other words, a Project Filter constraint
cannot be cleared by a Clear Filter action.
NOTE: This example shows the importance of
understanding your data. The TDepth value in the XY
table is a measured depth (MD) value. In this project,
where most wells are vertical, the project filter you
just created works effectively to determine the
shallower wells.
However, if more of the wellbores were deviated, it
would be important to query based on some true
vertical depth (TVD) value instead.
11. At the top of the Navigation pane, change the step to Zone.
Notice that all of the shallow completions are in zones III,
IVA, and IVB. You can conclude that these are the shallowest
of the five zones.
12. Clear the checkbox next to the project filter to disable it
before progressing to the next section.
13. Change the step on the Navigation pane back to
Completions.
Review Questions
64
What is the purpose of the Irregular Zoom option?
How is filtering different from grouping?
Why is Filtering by Table Data useful?
What data can you best access when you filter by Query?
In what three forms can a filter be saved?
When the project is updated with new data, will you have to
rebuild the calculated categories? Why?
What does a Project Filter do that other filter types do not?
Why is it good practice to ensure that all completions are fully

mapped to their respective categories?
Schlumberger
Groups and Filters
Summary
In this module, you learned about:
performing ad-hoc filtering by:

map techniques
completion
well list
categories based on text fields
areal, vintage and calculated categories
using step functionality
OFM query
table data
match.
visualizing dynamic data on the base map
project filtering
This is what you learned about the Provo East oil field:
All wells are in one of two pools. Most of the completions are
in the BLM B pool.
More than half of the wells are completed in zone III.
Production began in the 1980s. There has been ongoing infill

drilling through the years since, particularly in the 1990s.
Nearly half the wells started production in that decade.
Only a quarter of the completions were able to sustain high

oil rates for more than two months.
There were 17 non-producing completions as of the last

database date that could be considered for reactivation.
65
Groups and Filters
Schlumberger
NOTES
66
Project Variables
Schlumberger
Module 3 Project Variables

There are many ways to classify OFM variables (also called
project variables), depending on how you wish to use them.
Based on the type of table to which the variables belong or from
which they were created, you could have monthly, daily, and
sporadic variables.
Based on the type of data, you could have date, numeric or
alphanumeric (text) variables. Each variable classification can be
put to use in your OFM project.
Learning Objectives
After completing this module, you will know how to:
create and edit calculated variables
create and use calculated fields
understand the ways in which the variables differ when used

in specific types of calculations
Lesson 1
Project Variables
There are three forms of project variables: input (table) variables,

calculated variables, and calculated fields.
Input
Variable
This is the simplest form of a variable. Input

variables are columns in physical tables with
physically loaded data. In other words, if you
open the table in MS Access or in OFM, you will
see editable data. You can think of these as raw
data stored in the table.
Input variables do not change value unless the
data are corrected; every time a request is made
to an input variable on a specific entity and a
specific date, you get the same resulting data
value.
In its Access database, OFM stores both the
design and the data of the input variable.
67
Project Variables
Schlumberger
Calculated
Variables
These are derived variables. OFM saves only the

definition of a calculated variable, not its physical
resulting value. The value of a calculated
variable can change from time to time,
particularly when the project data are updated.
For example, each time a retrieval request is
made for a calculated variable such as peak gas
rate, you could get a different resulting value
because new data have been added recently to
the database. The advantage of this variable
type is that you always get the most up-to-date
result and you never worry about project storage
capacity.
Calculated variables are constructed in the same
way you build expressions in an Excel
spreadsheet, but they are vastly more efficient
than Excel.
For example, to calculate water cut for 20 wells
daily over 5 years requires 36,500 independent
calculations in an Excel spreadsheet. OFM
requires only one.
Calculated
Fields
These are a unique variable type in OFM. There

are occasions when neither input nor calculated
variables are sufficient to address the type of
calculation being considered. With the existence
of Calculated Fields, those problems can be
resolved.
Calculated fields are used in OFM projects in a
relatively small number of instances. Calculated
variables, on the other hand, are significantly
more flexible and powerful and, consequently,
are widely used.
68
Project Variables
Schlumberger
Lesson 2
Calculated Variables
Most projects contain production volumes of oil, gas, and water.

Of crucial importance are derived parameters, such as water cut,
cumulative gas, and gas-liquid ratio. It should be possible to
calculate these directly from the input variables (raw data) and
OFM provides this capability through calculated variables.
In simple terms, calculated variables are variables created from
expressions built using any other variables. Other variables can
be input variables, calculated fields, or other calculated variables.
There are virtually no limitations on how many calculated
variables you can have in your project. There is also no limit to the
complexity of calculated variables, subject to the criterion that the
expression must be able to be resolved.
WARNING: When naming calculated variables, the only valid
characters are letters, numbers, underscores, and
periods. Names such as Cum_Gas and Gas.Cum
are fine. Names such as Cum Gas or
#_Gas_Wells are not allowed.
System Functions
Building expressions eventually demands that specific complex
functionality is made available, such as the ability of an
expression to cumulate values. These functionalities, with predefined behaviors, are provided in OFM through a collection of
utilities known as the system functions.
If you are comfortable with using functions in an Excel
spreadsheet formula, you will very quickly adapt to the concept of
OFM system functions. The logic behind the two is very similar.
With more than 230 predefined system functions in OFM,
calculated variables are one of the strongest functionalities of
OFM. In this training, you will learn how to create a few of the
most commonly used calculated variables. Consult the OFM Help
topic System functions list of all for a list and description of all
system functions.
69
Project Variables
Schlumberger
Exercise 1
Creating a Calculated Variable

Representing the Gas-Oil Ratio
One of the simplest illustrations of a variable created by a

combination of other variables is a simple ratio calculation.
1. On the Setup tab, in the Variable Managers group, click
Calculated Variable Editor.
The Variable Editor window displays with the list of
variables filtered to show only calculated variables.
You can see that many Calculated Variables already exist for
this project; feel free to examine them. For the time being,
however, continue with the exercise to understand how they
were created.
2. Click Add Calculated Variable.

The Edit Calculated Variable window displays.
70
Schlumberger
Project Variables
3. In the text field at the top of the dialog, enter Prd.Gas/

Prd.Oil
OR
a. Choose the variables by highlighting them in the displayed
Project Variables list and clicking Add or by doubleclicking the item.
b. Enter the division symbol or choose it from the keypad on
the right side of the dialog.
TIP: Using spaces between elements in an expression is
permissible: it makes the formula easier to read and
OFM will accept it.
Do not click OK yet. There is more work to do.
71
Project Variables
Schlumberger
Exercise 2
Preventing Errors
You have defined the expression that will return a Gas-Oil ratio,
but there is a potential problem.
What if, in one particular month, there is water production but zero
gas production or the gas production value is missing? This
expression will cause a divide-by-zero type of error, which is not
desirable. You need a way to protect your expression from this
eventuality.
The obvious way of avoiding a divide-by-zero error is to introduce
a condition into the expression. This is a nice way of introducing
OFM system functions.
1. Click System Functions.
The parameter list changes to show the collection of
prepared system functions available to all OFM projects.
2. Scroll through the list and locate the system function named
If.
3. In the upper text entry area, place the cursor at the beginning
of the expression and double-click on the If function to bring
it into the expression creation area.
4. Edit the expression to read as follows:
@If(Prd.Oil=0,@Null(), Prd.Gas/Prd.Oil)
If the condition (monthly gas volume value is zero) is TRUE,
the expression returns a Null value, meaning it returns
nothing. (It does NOT return zero.)
If the condition is FALSE (monthly gas volume value is not
zero), the expression proceeds to perform the calculation.
TIP: A system function must be preceded by (@)in an
expression.
NOTE: The @Null() result is itself a system function and
requires no arguments.
You are now protected against the possibility of the Divide by
zero error.
72
Schlumberger
Project Variables
5. Click OK.
The Edit Calculated Variable window closes and the
variable displays in the Variable Editor window. By default,
the name of the new calculated variable is NewItem.
6. In the Name column for the NewItem calculated variable,
enter GOR.
OFM automatically assigns the same name for the Display
Name.
NOTE: Display Name has been included in the design of the
application but as yet it is not being used.
7. Leave the User and Class fields unspecified.
8. At the top, click Math.
OFM displays columns for math information.
9. In the cell for the Output Multiplier, choose M.
Because the desired display units for GOR will be thousands
of cubic feet per barrel or thousand cubic meters per
standard cubic meter, the M multiplier is required.
73
Project Variables
Schlumberger
NOTE: Output Multipliers are your personal choice for

display purposes. If you prefer to see this variable
displayed by default in cf/b, leave the Multiplier at 1.
10. At the top, click Math again to hide the math columns.
11. Click Units to display the units columns.
12. In the cell for Units, choose cf/bbl ==> scm/m3.
At this time, the essential work is done. You also can use this
dialog to assign visualization attributes to the calculated
variable, which comes into play when you display its result in
a plot or report.
13. At the top, click Units again to hide the units columns.
14. Click Plot to show the plot columns.
15. Set these parameters:
Curve Name = Gas Oil Ratio
Curve Line Color = Red
Curve Line Type = Solid
Curve Line Width = 3.
16. At the top, click Plot again to hide the plot columns.
17. Click Report to show the report columns.
Report Width = 8
Report Width Decimals = 3
Report Heading 1 = Gas
Report Heading 2 = Oil
Report Heading 3 = Ratio.
74
Schlumberger
Project Variables
TIP: Do not enter units in the Headings. OFM will provide

them when the report displays. Remember: You might
wish to change from metric to field in the report.
Entering m3 here will confuse your readers.
19. Click OK.
The new calculated variable is now in the project and is
immediately available to all modules.
Production Rate Calculations

When analyzing production data, you seldom deal directly with
monthly volumes; instead, you concentrate on rates. There are
two common types of rate calculations.
A Calendar day (CD) rate is defined as the monthly volume
divided by the number of days in the month. A Producing day (PD)
rate is the same monthly volume but, this time, it is divided by the
number of days on production.
This second definition is considered the rate at which the
completion was flowing - when it was flowing. This can be a more
representative number, depending on the situation.
You already have the gas producing day rate variable
(Prd.PDGAS); what you need is the calendar day rate, which you
will name Gas.CalDay, using the expression:
Gas.CalDay = Prd.Gas/@dom(Date)
This variable introduces a new system function @dom(). This
function returns the correct number of days in any calendar
month. For example, in January, it will return 31 and in June it will
return 30. It requires an argument, which is the Date variable.
Compare this with a spreadsheet-style approach, which most
likely would use a formula of 365 days/12 months = 30.417 as an
average month length.
WARNING: Never do this because it is always wrong!
75
Project Variables
Schlumberger
Exercise 3
Creating a (Monthly) Calendar Day

Average Oil Rate Calculated
Variable
Use the Average Oil Rate Calculated Variable to create a

production rate variable based on the actual number of days in the
month.
The Variable Editor window displays.
3. Enter the expression, either by entering the string or by
choosing any portion of it from the Project Variables or
System Functions lists:
Prd.Oil/@dom(Date)
4. Click OK.
The Edit Calculated Variable window closes and the
variable displays in the Variable Editor window. By default,
the name of the new calculated variable is NewItem.
5. In the Name column for the NewItem calculated variable,
enter Oil.CalDay.
OFM automatically assigns the same name for the Display
Name.
NOTE: Display Name has been included in the design of the
application but as yet it is not being used.
6. Leave the User and Class fields unspecified.
7. At the top, click Units to display the units columns.
8. In the cell for Units, choose bbl/d ==> m3/d.
9. At the top, click Units again to hide the units columns.
10. Click Plot to show the plot columns.
76
Project Variables
Schlumberger

Curve Name = CD Oil Rate
Curve Line Color = Dark Green
12. At the top, click Plot again to hide the plot columns.
13. Click Report to show the report columns.
Report Width = 7
Report Heading 1 = CD
Report Heading 3 = Rate.
15. Click OK.
The new calculated variable is now in the project and is
immediately available to all modules. You will use this
variable later in this module.
Exercise 4
Creating a Cumulative Calculated

Variable
Cumulative production volumes are always of interest. To create

cumulatives, OFM provides a system function named
@CumInput(). This function calculates the running sum of the
variable inside the parentheses (the argument), including prior
cumulatives (precums).
Your instructor will provide a more detailed explanation of the
concept and use of precums in OFM.
77
Project Variables
Schlumberger
3. In the text field at the top of the dialog, enter

@CumInput(Prd.Oil)
OR
Click System Function to locate the Cuminput system
function.
NOTE: The @CumInput () function can take only input
variables (i.e., table data) as an argument. It cannot
accept calculated variables. If your argument is a
calculated variable, there are alternatives: use
@RSum () or @CRSum ().
These system functions also calculate cumulatives,
but they do not take previous volumes (precums) into
account and they can be reset to zero by a condition.
For example, track total production against an annual
target. The total would reset when the year portion of
the date changes
4. Click OK.
The Edit Calculated Variable window closes and you are
returned to the Variable Editor window.
5. In the Name field, enter CumOil.
6. Leave the User and Class empty for this exercise.
7. At the top, click Math.
8. Choose M for Output Multiplier.
9. At the top, click Units.
10. Choose bbl ==>m3 for Units.
11. At the top, click Report.
Report Width = 7
Report Heading 1 = Cumulative
Report Heading 3 = Volume.
13. At the top, click Plot.
14. In the Curve Name field, enter Cumulative Oil.
78
Project Variables
Schlumberger
15. Assign these attributes and click OK:

Curve Line Color = Dark Green
The CumOil calculated variable has been added to the project
and can be found in any variable list.
This calculated variable illustrates an important point. Do not store
data for cumulative volumes in your project for two reasons.
They are redundant and duplications can cause problems.

For example, you would like a report or plot of the total
cumulative gas for the entire field but, when completions are
shut in, their cumulatives drop out of the total.
OFM stores only the expression and its attributes. It

recreates the data set on demand, which helps keep your
project database light.
Exercise 5
Using Calculated Variables to Find

Single Values
It is time-consuming to scroll through all the records of a

completion or group to find a specific record, such as the peak
production rate. This is especially true when the maximum
production value varies from well to well and happens at different
times.
Fortunately, OFM has system functions that can resolve such a
concern. Here, you create a calculated variable that returns the
peak CD gas production rate for each completion. You will use the
@TMax() system function.
The Edit Calculated Variables window displays.
79
Project Variables
Schlumberger
3. In the text field at the top of the window, enter

@Tmax(Oil.CalDay, Oil.CalDay > 0).
This expression illustrates two new points.
The definition of a new calculated variable can contain
another (existing) calculated variable.
The @TMax() system function requires a condition as its
second argument. A suitable choice here is that the
expression will evaluate only if the monthly oil production is
non-zero.
BEST PRACTICE: Many OFM system functions demand
conditional arguments. However,
sometimes you do not want or need
to apply a condition.Remember that the
condition will be evaluated against a
logical True or False.
A trick, therefore, to ensure that the
conditional argument is effectively
ignored is to enter 1. (This always
evaluates to True.)
4. Click OK.
The Edit Calculated Variables window closes and you are
returned to the Variable Editor window.
5. Enter MaxCDOil in the Name.
6. Click Units and choose bbl/d ==> m3/d from the Units cell.
7. Click Report.
Report Heading 1 = Peak
on Report Heading 2 = CD Oil
Report Heading 3 = Rate.
9. Click Plot.
10. Enter Peak CD Oil Rate in the Curve Name cell.
80
Schlumberger
Project Variables
11. Choose these curve attributes and click OK:

Curve Line Color = Magenta
Curve Line Type = None
Curve Point Type = Filled Star
Curve Point Size = 6.
81
Project Variables
Schlumberger
Exercise 6
Displaying the Results of

Calculated Variable Creation
You will now display in the PD Rates plot the results of some of
the work you completed in the last three exercises.
In this exercise, you will add the CD oil rate and peak CD oil rate
variables to the plot.
1. Select the PD Rates plot.
2. Double-click the plot.
The Edit Plot dialog displays.
3. Click Add Curve.

4. From the Variable drop-down list, choose Oil.CalDay.
5. Click Add Curve.
6. From the Variable drop-down list, choose MaxCDOil.
82
Schlumberger
Project Variables
7. Do not make changes to the Category or Name columns.

Click OK.
8. Choose completion HOGL1232.
Notice how the peak oil rate value is returned every month
but it correctly coincides with the peak value on the plot of
the CD Oil Rate in late 1993.
83
Project Variables
Schlumberger
9. Group all of the Provo East completions.

Notice that the total oil rate of the field declined, then
increased again multiple times. What you do not know yet is
how many completions contributed to the total rate
throughout the field history. You will investigate this further in
Module 5.
Question
You plotted the calendar day oil rate curve and the producing day
oil rate curve. They seem to coincide very well. But look at the
spike in PD rate in 2004. The CD rate does NOT spike.
Why could this be? Why is the producing day rate so different
from the calendar day rate?
84
Project Variables
Schlumberger
Exercise 7
Creating Text Display Variables
There will be times when you might wish to display values on a

report or plot, or in the headers and footers of other modules.
Numeric variables can be displayed in their original format but
they do not display well because all you get is the unlabeled
number.
You might wish to create calculated variables to convert the
outputs to text and display them better with attributes such as
names, units, and multipliers. Now you will create two text display
calculated variables, the first of which uses the @FmtName()
system function.
3. In the text field at the top of the dialog, enter this expression.
@FmtName(CumOil, @Last(CumOil))
This system function returns a text string comprised of four
parts.
The last (current) value of cumulative oil production
(based on monthly records)
Three attributes for the CumOil variable: plot name, unit,
and multiplier. These are the attributes you provided when
you created the CumOil calculated variable.
4. Click OK to close the Edit Calculated Variable window.
You are returned to the Variable Editor window.
5. Name this new variable HdrCumOil.
Because this variable is used for retrieving the last value of
CumOil, it will use the variable attributes of CumOil for
display. Do not worry about assigning attributes for it (not
even the field Width).
You will create the second text variable. This will be a slightly
more expanded description of the name of the operator of
the completion.
85
Project Variables
Schlumberger
7. In the text field at the top of the dialog, enter this expression:
Operator: + Sc.Operator
NOTE: Be sure to include the quotes and the space
character after the colon (:); otherwise, the appended
string will not be aligned properly.
This variable returns a text string comprised of the phrase
Operator: together with the (dynamic) name of the operator
associated with this completion, taken from the Sc table.
8. Click OK to close the Edit Calculated Variable window.
You are returned to the Variable Editor window.
9. Name this new variable HdrOperator and click OK.
Exercise 8
Displaying Text Display Variables

on a Plot Header
The two new header variables are now available to use as

headers on the PD Rates plot.
1. Select the PD Rates plot.
2. Select the completion HOGL1232.
3. Double-click the header at the top of the plot that displays the
completion name.
The Header dialog displays.
4. Click Add.
5. Click Assist.
6. Enter HdrCumOil or select it from the list of project variables
and click OK.
86
Schlumberger
Project Variables
7. Repeat Step 4 through Step 6 and enter or select

HdrOperator and click OK.
TIP: Include only one text variable per header line.

8. Click OK. Move the headers to your preferred locations.
9. Choose a completion.
87
Project Variables
Schlumberger
10. Group all the completions.

TIP: When a text header shows a result of <Ambiguous>, it
means that the completions included in the group do
not all have the same value for that text variable.
Therefore, no single result can be displayed.
Exercise 9
Loading Additional Project

Calculated Variables
You created many Calculated Variables in this training. Clearly, a

working OFM project will require many more, depending on the
needs of the project.
Similar to how you might work with in your own projects, the Provo
East project contains many prebuilt Calculated Variables. View
them through the Calculated Variable Editor as you did before
and observe the flexibility with which Calculated Variables can be
constructed.
Note how one Calculated Variable can include reference to
another.It is important to remember that OFM does not store the
results of Calculated Variables. They are evaluated in memory onthe-fly.
As a result, your project data stores do not need to absorb the
results. The idea is to keep only the raw data (for example, oil,
gas, and water volumes) in your databases and let OFM do all the
calculations locally.
88
Schlumberger
Project Variables
Calculated Variables are all fully defined in the workspace (.ofm)

file. However, it is possible to reload them via text files. The full set
of project Calculated Variables is available in the file
\OFM 2012 Oil Fundamentals\E Project Variables\
Provo East.par.
1. On the Setup tab, in the Import/Export group, click Import >
Data Loader.
2. Click Clear All to clear any existing selections.
3. Navigate to the folder \OFM 2012 Oil Fundamentals\
E Project Variables.
4. Double-click Provo East.par to enter it into the Files to Load
area.
5. Click Load.
Feel free to explore the various definitions using the Calculated
Variable Editor (Figure 8), with the goal of identifying where they
might be relevant to your projects.
TIP: Double-click the Name heading in the Calculated Variable

Editor to sort the calculated variables alphabetically.
89
Project Variables
Schlumberger
Review Questions
What is the difference between a calculated variable and an

Excel spreadsheet-style formula for calendar day rates?
How do conditional system functions, such as @if(),

improve the handling of calculated variables?
How do text display variables improve your presentations?
Summary
creating and editing calculated variables
Based on the comparison of the calendar day and producing

day rates for the field, there is not a great deal of downtime.
However, there is a spike in the data during 2004 that might
be explainable because of significantly reduced production
time.
The total oil rate of the field has declined, then increased
again multiple times. What you do not know yet is how many
completions contributed to the total rate throughout the field
history.
The total oil production rate for the field is approximately 300
b/d
Peak calendar day production rate for the field occurred in

1992.
90
Schlumberger
Project Variables
NOTES
91
Plots
Schlumberger
NOTES
92
Plots
Schlumberger
Module 4 Plots
Plotting is one of the most commonly used processes in OFM
because it is easy to use, effective, and capable of providing many
solutions for analysis of production data.
Learning Objectives
create a graph with one or two Y-axes
create a plot with multiple graphs
create a plot using the OFM catalog
use the Graph Blow Up option
create multiple completion plots and multiple group plots
use sum/average/% contribution plot types
add a new table for well events
use plot annotations
use plot-related tools/utilities
use a water production diagnostic plot.
Lesson 1
Basics of Plotting
An OFM plot is made up of one or more graphs. OFM supports as

many as six graphs in one plot window and each graph can have
as many as six vertical (Y) axes but it can have only one
horizontal (X) axis. Each Y-axis can display multiple variables.
You must follow these rules when plotting your results.
All project variables, except for text variables, can be plotted.

Project variables consist of input variables, calculated
variables, and calculated fields.
Text variables cannot be plotted but they can be used as plot

headers (titles).
93
Plots
Schlumberger
The terms plot and graph are often used interchangeably,

especially when there is one graph in the window, but they
cannot be identical. Graph is the visual representation of the
data, while plot is the housing of the graphs.
Exercise 1
Creating a Graph with One Y-Axis
This exercise shows you how to create a basic graph in OFM.

1. On the Home tab, in the Launch analysis group, click Plot.
The Edit Plot window displays.
2. In the X-axis section of the window, accept the default Date
from the Variable list field and 1 for the Multiplier.
3. Click in the Variables column and choose CD.Oil.Rate from
the list of predefined variables. This variable is defined the
same as the Oil.CalDay calculated variable you created in
Module 4.
4. Click OK.
OFM generates the plot.
94
Plots
Schlumberger
6. Notice that the new plot appears in the Analysis pane and
has been given the name Plot1.
Rename this plot to Production Plot.
Exercise 2
Modifying Graph Properties
A plot is composed of many elements. OFM allows you to modify

every aspect of the display of the plot.
1. On the graph, click on the green curve of oil rate.
The curve is highlighted and the curve properties are
displayed in the Properties pane.
2. Use the vertical scroll bar to locate the Curve Attributes
section of the Properties pane.
95
Plots
Schlumberger
3. Select a thicker Line Width.
4. Click on the X-axis line of the graph.

NOTE: The general rule for modifying properties is to click
directly on the part of the plot you wish to change,
such as the X-axis. The Properties pane adjusts to
offer you the editing tools you need to work on that
part.
5. Locate the Font property displayed at the bottom of the
Properties pane.
96
Schlumberger
Plots
6. Click the button with the three dots to the right of Font.
The Font window displays.
7. Change the Size to 12 and click OK.

The Font window closes and the size of the text displayed on
the X-axis updates.
8. Click on the Y-axis line of the graph.
9. Scroll the Properties pane until you find the Scale section.
Note that the Y-Axis Scale Type is Linear. (This is the default
behavior.)
10. Change the Scale Type to Logarithmic.
11. Locate the Font property displayed at the bottom of the
Properties pane.
12. Click the button with the three dots to the right of Font.
97
Plots
Schlumberger
13. Change the Size to 12 and click OK.

The Font window closes and the size of the text displayed on
the X-axis updates.

15. On the Format tab, in the Edit group, click Header.
The Header window displays.
16. Click Add.
A blank row is inserted in the Header window.
98
Schlumberger
Plots
17. Enter @Name()in the Edit Header window and click OK.
The Edit Header window closes.
TIP: The system function @Name() is very useful in OFM. It
automatically returns the name of the selected entity,
whether the entity is a completion, a wellbore, or a
user-defined group.
18. Click Font.

19. Set these properties and click OK:
Font Style = Bold
Size = 16
Color = Blue.
The Font window closes and you return to the Header
window.
99
Plots
Schlumberger
20. Click OK to close the Headers dialog. Observe the effect of

your changes.
Exercise 3
Inserting an Image in the Plot

Header
Optionally, you can insert an image, such as a company logo, in

the plot header. For this exercise, you will insert the Schlumberger
logo, located in the file \OFM 2012 Oil Fundamentals \C Provo
East Configuration\SLB-logo.jpg.
2. Click Add in the Header dialog. A new row is inserted.
3. Click Assist to display the Edit Header dialog.
4. Enter the system function @image and the full path and name
of Schlumberger logo file.
For example:
@image(D:\Documents\OFM 2012 Oil
Fundamentals\C Provo East Configuration\SLBlogo.jpg).
TIP: Copy and paste the path for the .jpg file from Windows
Explorer. Be sure to include the name of the file and
enclose the whole phrase in double quotes. There is a
128 character limit for the expression. If necessary,
copy the .jpg file to a folder with a shorter path.
5. Click Font.
6. Select Font Size 24. (You might need to work with this
number for images you choose for your project.)
100
Plots
Schlumberger
7. Click OK to close the Header dialog.

The image displays on the plot.

The header can be saved to a separate file for re-use on this
or another plot later.
10. Click Save As.
11. Navigate to a convenient folder and save the file with the
name My Header. It will have a file extension of *.gh.
Re-use the saved header with the Open option in the Header
dialog.
Exercise 4
Adding Curves
Curves can be added to a plot at any time to enhance analysis.

1. Double-click on the plot.
2. Click Add Curve.
One row is inserted in the variables section of the dialog.
3. Choose CD.Prod.Water.Rate for the variable of the newly
inserted row.
4. Click OK.
The Edit Plot window closes and the data are displayed on
the plot.
5. Click on the CD.Prod.Water.Rate curve on the plot.
The properties display in the Properties pane.
101
Plots
Schlumberger
6. Under Curve Attributes, assign these attributes to the curve:

Line Color = Dark Blue
Point Type = None.
7. (Optional): If you have multiple curves and wish them to

share some of the same properties, you can assign those
properties by choosing All Curves from Curves setting of the
Properties pane.
For example, if all curves share the same Type, Width, Point,
and Fill properties, you can choose All Curves and change
those properties only once.
102
Plots
Schlumberger
Alternatively, you can hold down the Shift key, click two or
more curves directly on the plot, and change the attributes of
only those curves simultaneously.
Exercise 5
Changing the Size or Location of

Your Plot
When a plot is created, the graphs are placed in default positions

within the window. You are free to change their position and resize
them any way you like.
1. Click anywhere in a blank area inside a graph, but not on a
curve. Anchor points at the corners indicate the plot is
selected.
2. Right-click and select Move/Resize from the shortcut menu.
The cursor changes to a four arrow-headed cross.
3. Choose one of the anchor points and resize the plot.
103
Plots
Schlumberger
4. Right-click and select Done.

Observe that your plot now adopts the placement that you
specified.
104
Schlumberger
Plots
6. The graph was moved manually to its new position. If you

need to fine-tune the exact placement of the graph, use the
Properties pane.
a. Select the X-axis on the plot. Selection handles appear
indicating that the axis has been selected.
b. In the Properties pane, adjust the Axis Origin settings for
the X-axis. To understand the settings, review the
diagram.
NOTE: These fine tune settings apply ONLY to the X-axis. To
fine tune the Y-axis, select it from the graph and
repeat the principle of these steps.
Questions
These questions are for discussion and review.
Why is the OFM approach to plotting superior to a

spreadsheet method?
When a plot is opened and data are displayed, what happens

to the data if a different completion is selected?
Where is the information stored that describes how you wish

to view this plot?
Does the Production Plot node on the Analysis pane hold

the plot data?
105
Plots
Schlumberger
Exercise 6
Creating a Graph with Two Y-Axes
As indicated earlier, any plot can be enhanced at any time.

1. Double-click on the plot.
The Edit Plot dialog displays.
2. Locate the Y-Axis section at the right side of the window and
choose Number of Axes = 2.
3. In the same area of the dialog, make sure Current Axis =
Y-AXIS 2.
4. In the Variable Selection area, add a cumulative oil variable
(Cum.Oil.Prod).
5. Click OK.
The Edit Plot window closes and the graph displays.
106
Plots
Schlumberger
Exercise 7
Creating a Plot with Multiple

Graphs
Creating a graph with multiple curves, such as the one in this

exercise, will help you understand production trends over time.
2. Locate the Graph section at the right side of the window.
3. Change the Number of Graphs to 4.
4. An OFM message dialog displays prompting you to overlap
graphs. Click Yes.
NOTE: If there are fewer than four graphs on the plot, the
default setting is Overlap, meaning lined up vertically.
If there are more than four graphs on the plot, the No
Overlap option is automatic.
For example, six graphs would be positioned with
three graphs lined up vertically on the left side and
three on the right.
5. Set the Current Graph to Graph 2.
6. Add Cum.Water.Prod from the Variables list.
7. Change the Current Graph to Graph 3.
8. Set Number of Axes = 2.
9. Choose Water.Gas.Ratio for the first X-axis variable.
107
Plots
Schlumberger
10. Choose Cum.Water.Gas.Ratio for the second Y-axis

variable.
11. Switch the Current Graph to Graph 4.

12. Choose Cnt.Gas.Well for the X-axis.
13. Click OK.
The Edit Plot window closes.
14. Group all of the Provo West completions.
15. Adjust the legend positions and the Scale Types of the
Y-axes to improve the appearance.
Notice that when the number of graphs changes, the header
is reset to default font sizes and positions.
17. Click Open.
18. Navigate to and select the My header.gh file that you saved
previously.
19. Click Open, then click OK.
108
Schlumberger
Plots
You observed in a previous module that the decline of total

oil production rate of Provo East seems to be increasing.
This graph helps you to understand that behavior.
The variable Active.Oil.Producers on the fourth graph
indicates that since about 2002, more and more wells have
gone offline.
21. Open the Calculated Variable Editor to review the definition
of Active.Oil.Producers. It uses a new system function.
Active.Oil.Producers = @CountInput(prd.oil)
The system function @CountInput() returns the number of
completions that contribute data to the table field (Prd.oil) at
each time step (month). The result is, therefore, a time
dependent number.
109
Plots
Schlumberger
Procedure 1 Viewing a Graph up Close

When a plot contains multiple graphs, it might not be possible to
see detail very clearly. OFM provides the option to view individual
graphs up close.
1. Click one of the four graphs.
2. On the Format tab, in the Display group, click Blow Up.
The selected graph displays in full scale.
3. Click Blow Up again to return the plot to its original state.
4. Close the Production plot.
Exercise 8
Using the Solutions Catalog
OFM installs with an assortment of useful plots and reports in its

Solutions Catalog. The Catalog is possible because every OFM
project has an internal listing (the Data Dictionary) of more than
1,000 commonly used terms, such as Daily Oil Production. Items
in the Catalog (plots, reports, maps) have been built using these
universally standard terms.
To make use of the Catalog (for example, a plot of Daily Oil
Production vs. Time), OFM needs to know only the name of the
variable in your project that corresponds to the Dictionary entry
named Daily Oil Production.
You now will create a plot similar to the one you built in
Exercise 7. This time, you will take it directly from the Catalog.
1. Clear the previously applied filter.
2. On the Home tab, in the Launch analysis group, click
Catalog.
3. In the Type Ahead filter box, enter oil
4. Scroll down the list to the item labeled Oil Well Summary
Performance.
110
Schlumberger
Plots
5. Highlight the row.

An example of the output of this plot appears in the lower
window as shown in the figure.
You will add this plot directly to your project but two things
prevent it. The Add button is disabled and a
confirmation
symbol indicates that OFM does not have
all the information it needs to create the plot.
111
Plots
Schlumberger
Specifically, the variables needed to create these plots have

not yet been mapped to their corresponding Data Dictionary
entries. The Details tab in this dialog tells you which
variables have been mapped and which have not.
112
Schlumberger
Plots
6. Click Map to Dictionary at the bottom left corner of the

window.
The full list of variables in the Data Dictionary dialog are
those necessary to create the plot from the catalog.
113
Plots
Schlumberger
7. Choose the appropriate project variables, as shown in the

figure.
NOTE: Some items in your variable list are grayed out. This
means that they have already been mapped to a
Data Dictionary variable. This illustrates an important
feature: only one project variable can be mapped to a
Data Dictionary variable at any time.
You can change the mapping at any time but there
can be only one association between a Data
Dictionary item and a project variable.
8. Click OK to return to the Catalog window.
Note that the yellow warning triangle icon has been replaced
by a green check mark. The plot is ready to be used.
9. Click Add to add this plot to your Analysis pane.
10. Click Close to clear the Catalog dialog.
114
Schlumberger
Plots
11. Observe your Analysis pane.

The Catalog solution is now in your workspace.
12. Group all the completions in Provo East.
You are free to change any aspects of this plot as desired.

This plot is now in your workspace. Your changes will have
no effect on the Catalog item.
115
Plots
Schlumberger

BEST PRACTICE: Explore the Catalog. It contains over 100
items, many of which are useful for
general oil and gas operations. Some
are specific to particular operations,
such as pattern flooding or SAGD.
The principle of obtaining ANY item from
the Catalog is exactly the same as the
exercise you just completed: map the
necessary variables and select the
Catalog item that you want.
A very common question has been, Can I add to the Catalog? The
answer is yes. Follow this thread in the online Help for details of
how to expand it to accommodate your own analyses: Home >
OFM > Catalogs > Creating New Catalog Items.
Lesson 2
Plots Comparing Multiple

Entities
Up to now, you displayed the performance of one completion or

one group at a time. However, at some point, you will want to
compare multiple completions or multiple groups at the same
time. OFM offers this capability.
Exercise 1
Creating a Plot Comparing

Multiple Completions
In this exercise, you will compare the producing day oil rate of all
the completions in the project flowing to Flow Station TB0532,
using a technique where you choose one variable and display that
variable for all entities (completions) in your current filter.
2. In the Filter pane:
a. Select Category > Flow_Station.
b. Check the box marked TB0532.
c. Select Table Data > PRD.
There should now be 13 completions in the current filter.
116
Schlumberger
Plots

4. Click Add Multiple Curves.
The Add Multiple Curves dialog is displayed.
5. Leave Category set to Completion and choose the Variable =
Cum.Oil.Prod.
117
Plots
Schlumberger
6. Click OK to accept the selections.

The Edit Plot dialog shows 13 curves, representing
cumulative oil for each of the 13 completions in your filter.
118
Schlumberger
Plots
7. Click OK.
The plot displays.
Each completions curve is displayed independently, automatically

set to different colors. It is clear that completion PVE2_0131 has
been the best producer to this Flow Station with a cumulative
production of just over 160 Mbbl.
In addition, four of the completions have produced less than 40
Mbbl. Completion PVE3_0831 displays an interesting story: rapid
accumulation early in its history and a sudden slowing down in
1993. This well clearly needs to be investigated further.
There are several alternate ways to display this plot.
119
Plots
Schlumberger
Exercise 2
Using Stacked, Sum, Average,

and % Contribution Plot Types
This exercise shows you different ways to display a plot of multiple

completions.
1. On the Format tab, in the Display group, click Stacked
This style of plot provides a good understanding of how

much volume each completion has contributed to the total
cumulative for the Flow Station.
120
Plots
Schlumberger
2. On the Format tab, in the Display group, click Sum
The Sum plot displays.
The single curve sums the individual cum oil curves for all 13
completions. It is essentially the upper profile of the stacked
plot.
Observe that the curve does not increase continuously, so it
does not accurately represent the total cum gas for the Flow
Station. This is due to the production of several of the
completions ending early and thus their values dropped out
of both the stacked and this summed plot.
WARNING: Although the button looks similar, summing the
curves on a plot is very different than grouping
the completions. Summing the curves will sum
all curves on the same axis, even if they
represent oil and water for a single entity.
121
Plots
Schlumberger
3. Click Average
The average cumulative gas for each active completion

displays.
Why does this curve have a higher number of
discontinuities? Does this curve have a physical meaning?
122
Plots
Schlumberger
4. Click Percent
Observe the new Y-axis scale.
5. Rename the plot node on the Analysis pane to Compare

TB0532 Cum Oil.
Questions
These questions are for discussion and review.
If this were a plot comparing oil rates instead of cum Oil,

would the sum, average, and % contribution style plots have
more meaning?
Would a header of @Name() be relevant for this plot?
If you were to clear the filter would the plot change? What if
you were to filter to a different Flow Station?
123
Plots
Schlumberger
Exercise 3
Creating a Plot Comparing Multiple

Groups
In Exercise 2, you compared individual completions on a plot. A

similar technique can be used to compare entities at any grouping
levels based on either Categories or Filter Archives.
Because there are multiple zones in this project, you will compare
the performance of each zone. However, there are a different
number of completions in each of the zones, so a comparison of
total gas rate per zone will not be meaningful.
Instead, it will be more meaningful to remove the well count from
the analysis by comparing the average gas rate per completion.
3. Enter active in the Type ahead filter box at the top of the
window.
4. Locate the calculated variable Active.Oil.Producers and
double-click its name to review the definition.
This calculated variable counts how many completions in a
group produce oil each month.
5. Click Cancel and repeat for CD.Oil.Rate.per.Active.Well.
This calculated variable divides the total CD oil rate for each
month by the number of active oil producers. This is more
representative than simply dividing by the number of
completions in the group.
6. Click Cancel.
8. Click Add Multiple Curves.
The Add Multiple Curves dialog is displayed.
9. Set Category to Zone.
124
Schlumberger
Plots
10. Choose the variable CD.Oil.Rate.per.Active.Well and click

OK.
The Edit Plot dialog shows five curves, representing the

average gas rate for each of the five zones.
125
Plots
Schlumberger
NOTE: On any plot created using the Add Multiple Curves

button, the entities in the Name column are
essentially hard-coded into the plot template. The
normal behavior is for these columns to vary
dynamically with the entity selected. (You will usually
see Current in this column, indicating that the choice
of entity will depend on your choice in the Filter or
Navigation pane.)
Clearing or changing the filter has no effect on the
plot results; only a Project Filter changes or limits the
data displayed on the plot.
11. At the top right, change Number of Graphs to 2.
12. Set Current Graph = Graph 2.
13. Repeat the Add Multiple Curves procedure (Step 8 through
Step 12).
14. Choose Category Zone and Variable Cum.Gas.oil.Ratio.
126
Schlumberger
Plots
15. Click OK and display the plot.

It is obvious from the plot that, apart from a spike in 1992 oil
rate, all five zones have performed equally well. Also, for
most of the zones, cumulative GOR has peaked slightly
before the peak in oil rate.
16. Click the Y-axis of the first graph.

17. On the Properties pane, set the Scale Type to Logarithmic.
18. Repeat Step 16 and Step 17 for the second graph.
19. Press the Shift key and click on the yellow curves on both
graphs to select them.
20. On the Properties pane, set the Line Color to a more visible
color, such as Magenta.
22. Click Add.
23. Enter Provo East Zone Comparison. Be sure to
include the double-quotes.
127
Plots
Schlumberger
24. Click Font and set the Size to 16.

25. Click OK twice.
26. On the Analysis pane rename the plot node to Compare

Zones.
27. Save the workspace and close the plot.
128
Plots
Schlumberger
Lesson 3
Plot Annotations
In OFM, plot annotations can be displayed on a graph. This allows

you, for example, to display a comment on a curve to help explain
a particular change in the performance of a completion.
Annotations can come from any time-dependent table. The Provo
East project does not have an appropriate table in which to store
well events, so we must create one. This means you must edit the
Schema (database structure) of the project.
You have been introduced to the Edit Schema Tables dialog
during the process of creating the Provo East project. Here, you
investigate how to use it to:
add a new table to the project
add data columns (fields) to the table
define the default attributes of the new fields.
129
Plots
Schlumberger
Exercise 1
Adding a Table to the Project
Use the table you add to the project to store well events.
1. On the Setup tab, in the Tables group, click Schema.
The Edit Schema Tables dialog displays.
NOTE: The level of the tree selected in the OFM
Representation section of the dialog determines what
information will be displayed on the right side of the
Edit Schema Tables dialog.
If the top level of the project is selected, only the
Tables tab displays. You must select a table to
display the Table and Fields tabs for that table.
2. Locate the OFM Representation section on the left side of

the window.
3. Click the data source (Provo East.accdb) and right-click.
130
Plots
Schlumberger
4. Click Add.
The Edit Schema Table dialog displays a NewItem table in
the OFM Representation section of the window.
5. Replace the default table name NewItem with Events.
OFM assumes that the table is of a monthly type and creates
the default fields UID and Date.
WARNING: Never use spaces in table names or field
names. Letters, numbers, and underscores are
the only valid characters.
6. Events can occur anytime throughout the month. Change the
Table Type to Sporadic on the right side under OFM
Definition.
7. Click the Fields tab.

8. Enter Type in the Add New Field text box.
9. In the drop-down box to the right of the variable name,
choose Text.
131
Plots
Schlumberger
10. To the right of Text, enter 20 for the field size.
11. Click Add.

The new variable/field Type is added into the table.
132
Plots
Schlumberger
12. Repeat Step 11, this time adding TopDepth and BotDepth
variables and setting them to a variable type of Double.
The newly added fields are displayed in the Available Fields
section of the dialog.
NOTE: Any field can be disabled by clearing the box next to
its name. This prevents the field from displaying in
any subsequent OFM operation, such as a list of
plotting variables. It does not delete the field from the
database.
Select the box at any time in the project to enable the
field.
Setting detailed attributes for the variables you have just created
(for example, units and plot settings) is outside the scope of this
course.
133
Plots
Schlumberger
Exercise 2
Preparing a Plot to Annotate
This exercise allows you to practice many of the plot options

related to annotations.
2. From the Filter pane, choose the Well List Possible
Workovers that you saved in Module 3.
4. Select Y-axis variable PRD.PdOil and click OK.
5. On the Analysis pane, rename the plot node from Plot1 to
PD Oil Annotated.
6. Choose completion HOGL2-1029.
7. On the Setup tab, in the Tables group, click Data Grid.
8. Open the Events table with the Edit all records checkbox
cleared.
9. For completion HOGL2-1029, make the entries shown in the
figure.
NOTE: When entering date values into a data table in OFM,

the format you use should match the regional
settings in your Control panel. So the first date, for
example, could be interpreted as October 12 or 10
December.
10. Click in the next blank line of the table grid to commit the
changes to the database.
11. Close the grid view.
12. Choose completion HOGL2-1029 from the Navigation
toolbar.
13. Click the PD oil curve.
134
Plots
Schlumberger
14. In the Properties pane, set the Curve Event to Events.Type.
135
Plots
Schlumberger
15. Observe the effect.

A new legend lists all the entries in the Events table for this
completion. Each entry is numbered.
Observe the X-axis. Small numbers 1, 2 and 3 appear along
the X-axis, indicating the date corresponding to the
numbered event. This is the default behavior.
136
Plots
Schlumberger
16. (Optional) Place the annotations directly over the curve itself.
In the Properties pane, locate the Event Display Type option
and choose On Curve.
NOTE: If no curve data exists for a given date or range of

dates, no event in that date range will display on the
plot using the On Curve method.
137
Plots
Schlumberger
17. Rotate the annotations.

a. In the Properties pane, select Curve Properties >
Event > Font.
The Font dialog allows the label to be oriented.
b. Set an Angle value of 90 (degrees).
138
Plots
Schlumberger
c. Set a size of 12 and click OK. Observe the effect on the

plot.
Lesson 4
Plot-Related Tools and

Utilities
There are many peripheral options related to plotting. Trace

features allow for tracking data values and the Plot toolbar
provides a way to quickly toggle plot types, such as switching
between Regular and Stacked plots.
Exercise 1
Viewing X-Y Data Pairs with

Corresponding Points on the Plot
For the purpose of data quality control, individual data points can
be viewed as XY data pairs and points simultaneously.
1. Choose the PD Oil Annotate plot you created in Lesson 4,
Exercise 2.
2. Choose completion HOGL2_1029.
139
Plots
Schlumberger
3. Click the PD oil rate curve on the plot.

4. Right-click and select Show XY Pairs.
The window in the figure displays.
5. Scroll up and down the X-Y Pair data window.

While moving the cursor, observe that cross hairs on the plot
move to match the position of your cursor in the XY data pair
list.
6. Clear the Show Visible Points Only checkbox.
NOTE: The minimum, maximum, and average values of the
selected variable are calculated and displayed.
140
Plots
Schlumberger
Exercise 2
Analyzing Information using the

Compute Line Feature
Compute Line provides a quick means to analyze information.

2. Choose the PD Oil Annotate plot you used in Exercise 1.
3. Click on the Y-axis.
4. In the Properties pane, set the Scale Type to Logarithmic.
5. From the Filter pane, filter by Category > Vintage 10 > 2000 2010.
6. Choose completion HOGL4-1529.
7. On the Format tab, in the Utilities group, click Compute
Line.
141
Plots
Schlumberger
8. Click on the plot and drag a line on the curve that visually fits
the data between mid-2001 and mid-2008.
142
Plots
Schlumberger
9. On the Format tab, in the Utilities group, take these actions.

a. Click Lock Line to prevent the line from disappearing in
the next step.
b. Click Trace/line Attributes.
The Trace Attributes window displays.
c. In the Trace Line Attributes section of the window, set

these values:
Set the Color to Blue.
Set the Width to 4.
143
Plots
Schlumberger
d. Click OK.
The Compute Line changes color and width.
144
Plots
Schlumberger
10. In the Navigation pane, choose completion HOGL8_0232.
NOTE: Bear in mind that, as the producing ranges of the

wells are different, the Compute Line might not
always show on the graph if the ends of the locked
line lie outside the plot range for the new completion.
Question
What can you say about the performance of HOGL8_0232 as it
compares to HOGL4-1529?
145
Plots
Schlumberger
Exercise 3
Adding a Group Average to the Plot
The previous technique allowed you to compare the trends of

many completions. It often can be helpful to compare individual
completions to the average for a group.
Here, you will create the calculated variable for average PD Oil
rate per active well and add that variable to the plot for the
appropriate Vintage 10 grouping.
2. Click Add Curve.
3. Set the variable CD.Oil.Rate.Per.Active.Well.
4. In the Category column, choose Vintage 10.
5. In the Name column, choose 2000_2010 and click OK.
146
Plots
Schlumberger
One graph now shows data for three independent entities: the
currently chosen completion (HOGL8_0232), the locked reference
(HOGL4_1529), and the average for the Vintage grouping 200
2010.
This is an example of how the technique can be used with any
category or with any Filter Archive to combine any entity or
grouping you wish onto any plot.
147
Plots
Schlumberger
Procedure 1 Saving the Setup of a Plot

As you have seen, a plot is only a template. It does not contain the
data being displayed, it merely describes how the data should be
displayed.
Every time you make a change to a plot (such as curve color or
axis scale), the modifications are captured in the plot node in the
Analysis pane. The Analysis pane itself is part of the project .ofm
file; when the workspace is saved, all the changes to the plot are
saved.
The portion of the .ofm file containing the plot details can be
exported. This is useful if you wish to share specifically the one
plot with a colleague.
1. Highlight the plot item on the pane. (The plot does not need
to be open.)
2. Right-click and select Export The Node.
148
Plots
Schlumberger
3. Save the file to a suitable location. OFM appends a *.Node

extension.
4. To import the Node into another OFM project, highlight My
Analysis in that projects Analysis pane.
5. Right-click and select Import The Node.
6. Navigate to the relevant .Node file and import it.

The plot displays in your Analysis pane.
149
Plots
Schlumberger
Lesson 5
Water Production Diagnostics
In Module 3, you used an OFM query to identify completions that

were producing at low oil rates as of the last project date. Here,
you will investigate the water production of the low oil rates to
determine if water coning or water breakthrough could be causing
the production problems.
A common technique for investigating water-oil ratio in oil wells,
often referred to as the Chan plot, is based on SPE paper 30775,
Water Control Diagnostic Plots. The technique involves plotting
the water-oil ratio and the first derivative of the water-oil ratio on a
log scale versus a log X-axis of cum producing days.
The relative shapes of curves fitted to both the ratio and the first
derivative can give some idea of the reason for the water
production.
Exercise 1
Importing Calculated Variables for

Creating the Chan Plot
The calculated variables for creating the Chan plot, along with the
plot template itself, are included in the files for this course. You will
first load the file containing the calculated variables, then you will
open the supplied graph template.
While Calculated Variables are routinely stored in the project
workspace file, they also can be saved externally. This legacy
method is named a parser file. It is a text file containing the
definition of each Calculated Variable, together with its associated
attributes (curve color and report settings).
In this case, given the relative complexity of the relevant
Calculated Variables, you will make use of this method. (You are
encouraged to look at the file and see how they were created.)
1. On the Setup tab, in the Import/Export group, select
Import > Data Loader.
2. Click Clear All to clear any existing list in the Files to Load
field.
3. Navigate to the folder: \OFM 2012 Oil Fundamentals\
F Plotting and Reporting.
150
Plots
Schlumberger
4. Double-click WOR Chan Variables.par to add it to the Files to

Load field.
5. Click Load.
A message reminds you how to stop loading data.
6. On the message, click OK.
8. In the Analysis pane, click the My Analysis folder.
9. Right-click and select Import the Node.
10. If necessary, navigate to the \F Plotting folder.
11. Choose CHAN WOR PLOT.NODE and click Open.
A new plot node appears on the Analysis pane named
Chan Plot Water-Oil Ratio.
12. Double-click the Chan Plot node to open it.

13. Filter to the Low Rates group by either enabling the OFM
Query from the Filter pane or double-clicking the filter
archive from the Filter Archive pane.
151
Plots
Schlumberger
The blue line and points represent the water-oil ratio. The red
line and points represent the first derivative of the water-oil
ratio. The relative shapes of the fit curves are typical of a
water coning situation.
After the cone is established, it stabilized, causing the watergas ratio to flatten out. With the ratio stabilizing, the first
derivative decreases as a result. This completion should be
investigated to determine if water could be coning.
152
Plots
Schlumberger
This time the relative shapes of the fit curves are typical of a
near wellbore breakthrough situation. When the water breaks
through, it does not stabilize; instead, it gets increasingly
worse.
With the ratio increasing so sharply, the first derivative also
increases sharply as a result. This completion should be
investigated to determine if water has broken through.
WARNING: The Chan plot is not definitive proof of specific
water problems. It suggests a possible reason
that should be investigated further using
supplemental data.
In particular, you have seen that this Provo East
project has some data problems, so be cautious
in drawing conclusions.
153
Plots
Schlumberger
Review Questions
In what ways is the OFM plotting solution superior to an

Excel spreadsheet style of approach?
How would you create a plot with 3 curves: curve 1

representing a completion, curve 2 the wellbore for that
completion, and curve 3 the zone which that completion
belongs to?
How would you add a curve to that plot to show another

specific zone?
How would you add the name of the current entity as a title
(header) on a plot?
Summary
creating a graph on one or two Y-axes
creating a plot with multiple graphs
using the graph Blow up option
plotting a single curve for many entities
sum, average, and percent control plots
using plot annotations
using plot-related tools and utilities.
The number of producing wells has fallen steadily towards

the end of the project.
Water production rate for the field overall has been relatively
flat since about 2000.
Gas Oil ratio for the field has only stabilized around 2007.
The largest producer flowing to Flow Station TB0532 has

contributed more than 160 Mbbl.
All five reservoir zones appear to be contributing equally to

overall production.
The cause of water production appears to differ from well to

well. There is no unique mechanism at play.
154
Plots
Schlumberger
NOTES
155
Plots
Schlumberger
NOTES
156
Reports
Schlumberger
Module 5 Reports
As an analytical tool, OFM is tailored for specific needs. There are
more than 230 system functions and an environment for writing
macro-like tasks.
The OFM report function has proven to be a powerful and
effective tool for outputting information, processing and
manipulating data, and testing customized variables. Unlike
plotting, it is not necessary for the fields displayed in the report to
be pre-constructed variables.
Learning Objectives
create a time-based (monthly) report
format a report
create a summary report
use additional report tools
export data to Microsoft Excel
convert a report to a plot.
Lesson 1
Rules
There are specific rules by which the OFM Report module

operates:
Static data can be retrieved at any time because they are

unchanged with time.
Monthly, daily, and sporadic data are all date-based but they
represent different concepts. Try not to include them in the
same report.
This also holds true for hour-, minute-, and second-based
data.
157
Reports
Schlumberger
A null data point is a missing data point.

Do not replace a null with a zero (0). This practice can be
dangerous in subsequent calculations.
WARNING: Zero is a real value. Null means that data are
missing. They are not the same.
For example, a missing oil volume replaced by a zero will
result in a 100% water cut calculation result. Similarly, a
GOR will appear to be infinitely high. Be careful with this
option.
If any variable in an arithmetic calculation is null or a variable

evaluates to null, the entire result of the calculation is null
(i.e., null + 2 = null).
Ad-hoc calculations can be included in reports and can be

assigned a name for the report.
For example, this column in a report
, (Prd.Oil + Prd.Water)/Prd.Gas LGR,
creates a column named LGR containing values equal to
liquid volume divided by gas volume.
Lesson 2
OFM Reports
The OFM report module is primarily used for retrieving datedependent data. (Depth-dependent data, such as log information,
are output to the Log Report module.) You can design and
customize the output and a user-friendly editor includes many
useful tools.
Reports can be configured to write automatically to many formats.
When the report updates, the external format also updates.
Report Variables
All OFM variables can be reported. The variables can be
accessed from the Project Variables list in the Edit Report
window.
158
Reports
Schlumberger
Exercise 1
Creating a Time-Dependent
Report
In this exercise, you create simple reports to output a combination

of monthly and static data.
1. Clear any previously applied filter.
Report.
The Edit Report window displays.
3. In the Select text box area, enter these variables:
Date, Prd.Oil, CD.Oil.Rate, Cum.Oil.Prod
There are two ways of entering this information.
Manually enter it, ensuring the variables are separated by
commas. If you have the Autofill variables and functions
checkbox enabled, OFM will try to predict your selection. You
might find it more efficient to switch this feature off.
OR
a. Use the drop-down list to find the variables you wish to

use.
b. Double click it or highlight it and click Add.
4. Click Project Variables to access the list of variables.
159
Reports
Schlumberger
5. Click System Functions to access system functions.

TIP: If you find an item from either list and double-click it,
OFM adds a comma after the last variable to separate it
from the newly added variable.
6. Click OK.
OFM generates the report and displays it in the OFM main
window. All of the variables are in monthly frequency.
160
Schlumberger
Reports
7. Choose Completion AVI2_0532.
8. On the Navigation pane, scroll through several completions

to see how the data are refreshed.
Sometimes, you will see a completion that does not have
monthly data. When this occurs, an empty report displays.
10. Double-click the report.
11. Add these parameters to the Select text field (remembering
to add the separating comma):
Sc.Flow_Station, Gas.Oil.Ratio
161
Reports
Schlumberger
12. Click OK.

The modified report displays.
BEST PRACTICE: As with plots, a report displays results
for any entity you choose: completion,
wellbore, Category, or group.
Any step change on the Navigation
pane or ad-hoc groupings is reflected
immediately in the report.
13. In the Analysis pane, rename the Report1 node to

Historical Production Report.
Waterflood Performance Analysis Using Reports

The Provo East project is a waterflood operation. Production from
a total of 82 producing wells is supported by five water injection
wells. While this is not a conventional pattern flood, you can still
evaluate the performance of the field as a whole. Pattern analysis
will be introduced in the OFM Intermediate course.
162
Schlumberger
Reports
There are four key waterflood performance indicators that you will
track using OFM:
Voidage (Reservoir Fluid Production minus Reservoir Water

Injection)
Cumulative Voidage
Voidage Replacement Ratio (VRR; Reservoir Water Injection

divided by Reservoir Fluid Production
Cumulative Voidage Replacement Ratio.
NOTE: All of these expressions MUST be evaluated in terms of

reservoir volumes, not surface measured volumes. In
your project surface, volumes (such as Prd.Oil) are
converted using a single constant Formation Volume
Factor value.
A more rigorous calculation will demand the introduction
of PVT into OFM but that is outside the scope of this
course. PVT is introduced in the OFM Intermediate
course.
In your project, you already have some very important Calculated
Variables that form the basis of our calculations.
Reservoir.Oil.Prod = Prd.Oil * FVF.Oil
FVF.Oil = 1.15
Reservoir.Water.Prod = Prd.Water * FVF.Water
FVF.Water = 1.02
Reservoir.Water.Inj = @nz(Inj.Water) *
FVF.Water
NOTE: Water injection did not commence until 1992; data for
this period is Null. This affects voidage calculations, so a
system function @nz() is introduced to convert the Null
values for reservoir volumes to zero.
Strictly speaking, you also should include gas terms in these
expressions, but keep the process simple for now.
163
Reports
Schlumberger
Exercise 2
Reporting Waterflood Performance
1. Define the four indicators as new Calculated Variables.

Voidage = (Reservoir.Oil.Prod +
Reservoir.Water.Prod) - Reservoir.Water.Inj
Cumulative.Voidage =
@RSum(Reservoir.Oil.Prod +
Reservoir.Water.Prod) @RSum(Reservoir.Water.Inj)
VRR = Reservoir.Water.Inj /
(Reservoir.Oil.Prod + Reservoir.Water.Prod)
Cumulative.VRR = @RSum(Reservoir.Water.Inj)
/ @RSum(Reservoir.Oil.Prod +
Reservoir.Water.Prod)
2. Create a new report. Enter this text in the Text entry area and
click OK.
@Name(), Date, Prd.Oil, Reservoir.Oil.Prod,
Prd.Water, Reservoir.Water.Prod, Inj.Water,
Reservoir.Water.Inj, Voidage,
Cumulative.Voidage, VRR, Cumulative.VRR
3. From the Navigation pane, choose Category = Field and
select Provo-East.
164
Schlumberger
Reports
Observe several features.

Production began in 1980 but injection support did not
begin for another 12 years. Voidage in this period continues
to climb, reaching a cumulative value of around 10 MMb in
1992.
Within a few years of starting injection in 1992, VRR
reaches approximately 1, suggesting that monthly volumes
of withdrawals are being matched by monthly volumes
injected.
However, the earlier production period means that only
about 70% of total withdrawals have been replaced
(Cumulative VRR) by 1992.
By the end of the data set, in 2009, Cumulative VRR has
still not exceeded 0.8. The long-term target value should
be 1. This field looks like it needs to increase its water
injection.
4. Rename this report Waterflood Summary.
5. Save your workspace.
This exercise provides a brief introduction in the use of OFM,
specifically in a waterflood operation. Several key performance
indicators also were introduced.
A more comprehensive treatment of the subject of waterflood
(pattern creation, allocation factors, and pattern maps) is outside
the scope of this course, but will be explored in other courses
dedicated to the subject.
165
Reports
Schlumberger
Lesson 3
Report Format
A sensible report is more useful when it is easier to read. OFM

provides a set of features that enable you to narrow the date
range, apply sort criteria, display subtotals, and enhance the
quality of the report output.
Exercise 1
Formatting a Report
1. Re-open the Historical Production report.

2. Use your mouse to change the column widths by dragging
their edges.
3. Highlight any cell in the column of data.
4. At the top of the Properties pane, change the Date Format
to MMM-YY. Observe the result on the report.
5. Click anywhere in the Flow Station column.

6. In the Properties pane, under Column Attributes, change
Justification to Center.
7. Click anywhere in the Monthly Oil Volume column.
166
Schlumberger
Reports
8. In the Properties pane, under Variable, change Multiplier to

M.
167
Reports
Schlumberger
Observe the changes.
168
Schlumberger
Reports

The Header / Footer window displays.
169
Reports
Schlumberger
10. Enter these variables and align all headings to the left:
@FmtDate(@today(), Mmm-dd-yyyy)
"Current " + Hdr.Cumgas
Hdr.PoolZone.
TIP: You can edit, delete, or add more headers. Footers

function in the same manner as headers, the only
difference is the location of the data displayed. Footers
are displayed at the base of the report, as opposed to
headers, which are displayed at the top of reports.
170
Reports
Schlumberger
11. Click OK to display the report.
Exercise 2
Setting Date and Sort Options
The default sort order is by date and the default date range is the
full history of the completion. Both of these setting can be
changed. Here, you will sort by CD oil rate in order to identify the
date and value of the peak oil rate.
1. On the Format tab, in the Edit group, click Date & Sort.
The Edit Report Attributes window displays.
2. Click the Sort tab.
3. From the First list field, choose CD.Oil.Rate.
171
Reports
Schlumberger
4. Select the checkbox next to Descending.
5. Click OK.
The report displays with peak gas rate displayed at the top of
the report.
172
Schlumberger
Reports
For completion HOGL1032, this tells you that the peak rate
occurred in June, 1982 and its value was just over 65 b/d.
(As you can see, there are many ways in OFM of finding the
same information!)
6. On the Format tab, in the Edit group, click Date & Sort
again.
7. Click the Sort tab.
8. Click Clear to remove the sort criterion and allow the report
to return to a date order.
9. Click the Set Date tab.
TIP: From the Set Date tab, you can display records of
interest based on date criteria. You can report data at a
specific date, at the last date of the entity, at all
available dates, or within a specific date range.
10. To determine the available date range (monthly and daily) of

the project, locate the Database Date Range section of the
dialog and click Find Monthly Database Date Range.
11. Under the Options section of the window, choose Range.
12. In the Starting field, choose 1/1/2007.
173
Reports
Schlumberger
13. In the Ending field, choose 12/31/2008.
174
Schlumberger
Reports

Observe that it now displays data only for 2007 and 2008.
Regardless of the length of the date range being displayed in

the report, it shows continuous rows with no breaks. For
readability it would be easier if there were visible breaks, for
example at the end of each year.
15. In the bottom of the Properties pane, set the Break property
to Annually.
Observe on the report that there is now a blank line at the
end of 2007.
16. Highlight a cell anywhere in the Monthly Oil Volume column.
175
Reports
Schlumberger
17. In the Properties pane, change the Subtotal property to

SUM.
18. Click anywhere in the Oil Rate (CD) column. In the

Properties pane, set the Subtotal to AVERAGE.
176
Schlumberger
Reports
19. Choose other columns in the report and set Subtotals

appropriately.
Note that Sums and Averages display on different lines. This
will help if you wish to copy the data, for example, over to a
spreadsheet.
177
Reports
Schlumberger
Exercise 3
Including Ad-Hoc Calculations in a

Report
As described in the rules in Lesson 1, you can include ad-hoc

calculations in a report. This is an extremely powerful feature. In
some cases, you might need a calculated column only for a
specific report, based on an idea you wish to test.
In other cases, you might plan a calculated variable for multiple
purposes and using the report to test your logic before finalizing
the definition of the calculated variable.
Another example might be where an existing, but very complex,
Calculated Variable does not return a result. By rebuilding the
Calculated Variable piece by piece in a report, it is possible to
determine where the Calculated Variable has broken, or where
there could be invalid data.
In this example, suppose that your company acquired this field at
the end of 2007. You are interested in knowing how much gas
each well has produced since that time.
1. Double-click the report.
2. After the Gas.Oil.Ratio variable, add a comma and enter this
expression.
@Rsum(prd.oil, date > 20071231) CumOil2008
NOTE: The @Rsum() system function calculates a running
sum of a variable, with an optional condition. In this
case, the date must be greater than 01/01/2007.
Adding the name CumOil2008 after the calculation
causes OFM to name the new column with that
name.
178
Schlumberger
Reports
3. Click OK.
The revised report complete with the new column displays.
As expected, the new column result shows zero value until

the start of 2008, then it starts to calculate a cumulative oil
figure.
179
Reports
Schlumberger
4. In the Column Properties section of the Properties pane,

improve the appearance of the column heading by splitting it
among three rows.
180
Reports
Schlumberger
Exercise 4
Generating a Summary Report
A frequently used type of report is referred to as a Summary

Report. This is typically a report displaying one line per completion
showing the last value, which is also most likely the current value.
This is a two-part process.
Report.
3. In the Select text box, enter this expression:
@Name(), Date, CD.Oil.Rate, MaxCDOil,
Cum.Oil.Prod
NOTE: MaxCDOil was the calculated variable that you
created in Module 4. It uses the @Tmax function to
calculate the peak oil rate for the completion.
4. Click OK.
5. On the Analysis pane, rename the report node from Report1
to Summary Report.
181
Reports
Schlumberger
7. Choose completion AVI2-0532.
8. Restrict the report to one line (representing the most recently

recorded data).
On the Format tab, in the Edit group, click Date &Sort.
9. Choose the At Last Date option and click OK.
This provides a nice summary of the single completion, but

you do not want to scroll through each completion and see
the summary one completion at a time.
182
Reports
Schlumberger
10. On the Format tab, in the Display group, click Summary By

Item.
The result is a concise overview of all completions in the
current filter and represents a very useful form of quick-look
performance summary.
WARNING: Observe the line for HOGL2_0232. It is dated
1994, while most of the other completions are
dated 2009.
Remember that each line is based on the date of
the last recorded data for the entity. This is not
always the same as the most current date, so be
very careful in using features, such as Subtotal.
It would have no meaning to SUM the CD oil
rate column.
An alternative that allows a subtotal to make
sense is the At Date option set to a specific date
of January, 2009.
The report can be changed very easily to become a

summary by zone.
183
Reports
Schlumberger
11. On the Navigation pane, change the step to Zone.
Any change of the step will immediately reflect on the report.

NOTE: The Summary by Item button is a toggle. When
turned on, it stays on until you turn it off.
Notice that the @Name() header is less relevant
when used on summary reports. A better header for
this report would be something like "Oil Summary
by " + @CategoryName( ).
12. Change the step back to Completions.
13. Double-click the report. At the end of the report parameters,
enter a comma, then enter Sc.Zone.
14. Click OK.
15. On the Format tab, in the Edit group, click Date &Sort.
184
Schlumberger
Reports
16. On the Sort tab, sort first by Sc.Zone, then by

CD.Gas.Rate.Max descending.
17. Click anywhere in the Zone column.
185
Reports
Schlumberger
18. On the Properties pane, in the Column Attributes section,

set these options:
Break when this column changes to Yes
Hide Duplicates to Yes.
19. Observe the Zone column.

Now your table has been (very quickly) reconfigured to show
production by zone and the completions in each zone are
ordered according to their peak production.
20. Relabel the report in the Analysis pane to Best
Producers by Zone.
186
Reports
Schlumberger
Exercise 5
Using the Report Gallery
Galleries are small collections of frequently used layouts for plots,

reports, and maps. In this exercise, you will explore how they are
used in the context of reports.
1. Beneath the Report icon on the Home tab, click the small
drop-down arrow.
This opens up a collection of six pre-prepared report formats.

Note that Galleries do not contain content (variables for
plotting or reporting are not pre-entered). They contain only
layout formatting.
187
Reports
Schlumberger
2. Click the icon with the Y/2 label (representing a report

breaking twice per year).
A standard Edit Report dialog displays.
188
Schlumberger
Reports
3. Enter Date, PRD.Oil and click OK.

Observe that OFM has prepared a semi-annual report,
complete with a descriptive title.
4. Explore the corresponding Gallery entries for plots.
189
Reports
Schlumberger
Exercise 6
Applying the Gallery Option for a

Summary By Item Report
The Summary By Item report that you created earlier now can be
replicated much more quickly using the Gallery.
1. From the Home tab, in the Launch Analysis section, click the
drop-down arrow below Report and choose the Summary
By Item Gallery option.
2. In the text entry area, enter this expression.

@Name(), Date, CD.Oil.Rate, MaxCDOil,
Cum.Oil.Prod
190
Reports
Schlumberger
3. Click OK.
We just achieved the same result as the 10-step preceding

exercise, but you did it in only four steps.
Lesson 4
Save and Export Options for

Reports
Every report has two components, the setup (design) and the
output (result). There are many formats to which report results can
be saved or exported, including Excel spreadsheets and tables
within the Access database.
OFM allows you to create a new Access database table in your
project, populated with data directly from the report. Here are
sample scenarios where this might be a valuable feature.
Scenario 1
The project contains thousands of completions and you wish to
carry out analysis using several complex calculated variables.
Due to the large volume of data and complex data processing, the
performance could be slower than you like.
You could save a summary report of the KPIs for each completion
to a new table and use that table to carry out further analyses with
very quick response.
191
Reports
Schlumberger
Scenario 2
You need to pass Events data to your Petrel model. For this
export to run, OFM requires that all data exist in the same
sporadic table. Normally, you would not have a need for such
diverse kinds of information to be stored in the same place.
By creating a report that gathers all these parameters together
and sends the resulting report to a table, the events information
can be successfully exported to Petrel.
Scenario 3
The field has informed you they discovered a problem with the
water meter into the central processing facility. Starting from
January, 2008, the correct water volumes should have been 50
percent higher than the reported values.
You would like to view and carry out analyses with a table of
corrected values without deleting the original data. One possible
solution is to report the adjusted production information and create
a new table that will hold new data.
Procedure 1 Saving the Setup of Your Report

You can save the setup of a report in two ways.
Save the current workspace.
OR
Export a report node from the Analysis pane. A NODE file can
include a plot format, a report format, or a folder containing
multiple formats. To save a NODE file, right-click the node and
select Export The Node. Reuse this node in this project or
another project.
1. Click a folder in the Analysis pane or highlight the Analysis
root folder.
2. Right-click and select Import The Node.
192
Schlumberger
Reports
Procedure 2 Saving the Results of Your Report

to a Text or CSV File
You can save the report as a text file or as a comma-separate
value file. A rich text format is not available.
1. Open the report and choose the desired entity (completion or
group).
2. On the Format tab, in the Utilities group, click Save
Analysis > Save File.
OFM also gives you the option of formatting output text files in
special formats. These files can be loaded to OFM, provided you
have previously defined the field names.
193
Reports
Schlumberger
Procedure 3 Exporting to Microsoft Excel

Exporting a report to Excel can be a very useful option, particularly
if you either want to check the logic of a new calculated variable or
do conditional formatting on the report results.
1. Select the Summary Report with the View Summary by Item
option still activated.
2. On the Format tab, in the Edit group, click Excel.
The Excel dialog displays.
NOTE: In the Columns section of the dialog, the default
header names to be exported are the OFM names.
194
Schlumberger
Reports
3. Select the checkboxes for these options.

Automatically update Excel when the report is updated
Include Excel column names above report
Include units for OFM columns above report.
4. Highlight the column names listed below Excel Column
Name and rename them as desired.
The entries under OFM Column cannot be edited. They were

used to create the report, not the spreadsheet.
195
Reports
Schlumberger
5. Click Close and Update.

The data are exported and displayed in an Excel worksheet.
WARNING: Be aware of the nature of this worksheet. If the

data in the OFM project is updated, the
worksheet will not be updated unless the report
is reopened.
Also, be cautious of the option Automatically
update Excel when the report is updated. If your
purpose is to create a conditionally formatted
report of a specific completion using Excel, be
aware that the worksheet will completely change
every time you choose a different completion or
group in OFM.
196
Reports
Schlumberger
TIP: Depending on your purpose for putting the report

contents into Excel, there is a simpler method. You can
click the top left corner of the report in OFM, copy
(Ctrl-C) and paste it (Ctrl-V) into Excel.
This method duplicates the column headings, breaks,
and subtotals from the OFM report to Excel, which the
export method does not.
Exercise 1
Exporting a Report to an Access

Table
This exercise creates a report for Scenario 3 that adjusts monthly

water production values and stores the adjusted monthly
production in a new OFM table.
1. On the Home tab, in the Launch analysis group, click Report.
The Edit Report dialog displays.
2. In the Select section of the dialog, enter this expression.
@Name(), Date, Prd.Hours, Prd.Oil, Prd.Water,
@If(Date >= 20080101, Prd.Water*1.05,
Prd.Water)
Note that the original uncorrected water volume figure
(Prd.Water) is included to illustrate the scenario.
197
Reports
Schlumberger
4. In the Navigation pane, choose the AVI2_0532 completion.
Observe how all the Prd.Water values have been increased

by 5 percent from January 2008 onwards. This is exactly
what you want.
5. On the Format tab, in the Display group, click Summary by
Item.
The report now displays the full history of every completion in
the project.
198
Schlumberger
Reports
6. On the Format tab, in the Edit group, click Access.

The Access window displays.
7. In the Table Name field, enter AdjustedMonthly.
8. Highlight Field1 located in the Access Fields column.
9. Rename Field1 to UID and press Enter.
10. Highlight UID and click Key.
This sets the UID field as the first primary key of the new
table.
11. Highlight Date and click Key.
This sets the Date as the second primary key of the new
table.
12. Change the other three field names to Hours, Oil,
Water and Adjusted_Water.
199
Reports
Schlumberger
13. Click Close and Update.

A message dialog displays prompting you to confirm creating
the Access table.
14. Click Yes.

OFM writes to the table, then the dialog closes and you are
returned to the report.
15. On the Analysis pane, change the report name from
Report1 to Water Correction.
16. On the Setup tab, in the Tables group, click Schema.
The Edit Schema Tables window displays.
17. Select the Show All Tables checkbox at the bottom right of
the window.
18. Check the Adjusted Monthly table from the list of Available
Tables. A message dialog displays prompting you to confirm
your decision.
200
Schlumberger
Reports
19. Click Yes.

20. For the AdjustedMonthly table, choose Table Type = Monthly.
OFM recognizes the mapping between the corresponding
key variables due to their names.
21. Click Yes in the confirmation dialog.

OFM successfully included the table into this project for your
use. You now have a data table containing your corrected
production volumes, independent of the original volumes.
201
Reports
Schlumberger
22. Click OK.

TIP: The option Automatically update Access when the
report is updated was not selected. If you made that
choice, updating will occur only when this report is reopened. Refreshing the report will refresh the
AdjustedMonthly table.
23. (Optional) Before proceeding, go through the remainder of
the Schema setup for the new table and check settings such
as units and multipliers.
Lesson 5
Data Visualization Options
As you have seen, sometimes it is better to visualize data using a

plot, and other times it is preferable to see the actual values on a
report. OFM provides the flexibility to move back and forth
between these two views of your data by allowing you to send a
report to a plot, and vice versa.
Exercise 1
Sending a Report to a Plot
1. Choose the Water Correction report that you created in the

Lesson 4, Exercise 1.
2. Choose completion AVI2_0532.
3. If Summary by Item is still enabled on the Format tab, click
that button again to turn off the feature.
202
Schlumberger
Reports
4. On the Format tab, in the Utilities group, click Send to Plot.
203
Reports
Schlumberger
5. A plot is created containing the data from the report. Observe

the two Prd. Water curves, indicating the uncorrected and
corrected values.
Exercise 2
Sending a Plot to a Report
A common form of surveillance is a table with one completion per

column. This can be done in the Report module itself but the
process is very laborious. Instead, a much faster way is to create
the multiple entity results in a plot then send that plot to a report.
1. On the Analysis pane, double-click the Compare TB0532
Cum Oil plot that you created in Module 5.
This plot was created using the Add Multiple Curves feature
and it has the curves for each zone hard-coded onto it.
204
Schlumberger
Reports
2. On the Format tab, in the Utilities group, click Send to

Report.
Observe that the report now has one column for each
completion.
3. Name this report Well by Well Summary.
4. Save your workspace.
Review Questions
Why should you filter to your completions of interest before

creating a Summary by Item report?
Why would you want to create a table from a report?
Why might you not want to automatically update a report?
Summary
creating a time-based report
introducing simple key concepts of waterflood surveillance

into a report
formatting a report
using additional reporting tools
introducing the Gallery feature
exporting report data to Microsoft Excel
exporting reports back to the project as a new table
sending reports to plots and plots to reports.
205
Reports
Schlumberger
NOTES
206
Schlumberger
Simple OFM Forecasting
Module 6 Simple OFM Forecasting

The Forecast module in OFM offers four major techniques:
Empirical, Fetkovitch, Locke&Sawyer, and Analytical Transient
solutions. The last three of these are type curve technique
that bring additional understanding of the well's current and future
performance. In practice, however, they are used infrequently and
will notbe covered in this training.
The majority of forecast analysis is done using simple Empirical
techniques. The Physical are well understood and it is often the
preferred method by which organizations estimate their official
reserves.
Prerequisites
To successfully complete this training, you must have knowledge
of these aspects of OFM:
Creating filters
Grouping completions
Working with categories
Performing calculations with System functions
Using calculated variables and calculated fields
Generating OFM plots and reports
Learning Objectives
Work with this empirical forecasting techniques.

Exponential, Hyperbolic, and Harmonic decline
Setup a forecast scenario
Work with different kind of limits
Change history match settings
Perform a manual match
Edit forecast graphs.
207
Schlumberger
Lesson 1
Forecast Set Up
A specific analysis requires preparatory work before beginning the

process. In addition to selecting the completions to work on, you
must ensure that default settings for your subsequent analyses
are effective and save you as much time as possible
Exercise 1
Identifying Completions of Interest
One of the first tasks in performing forecast activity in OFM is

assessing which completions to work with. Bear in mind that you
will perform a group forecast at some stage, so now would be a
good time to identify which completions will be grouped.
Restrict yourself to a short list of the best oil producers in the
Provo project - producers that have made more than 25,000 bbl
of oil.
To identify completions of interest:
1. Start OFM and open the Provo project.
Clear the current filter.
2. From the Filter pane, create an OFM Query filter with the
expression
.
@last(Cum.Oil.Prod)>25000
.
208
Schlumberger
3. Name the query Best Oil.

4. Activate the filter by checking the box next to the new name.
As the Filter pane indicates, there are 8 completions which meet

the criterion you set. This will be your working dataset for the next
few exercises.
Forecast Variables Setup

Before OFM can perform a forecast, you must prepare the
variables you will need. You will forecast oil rates, so you will be
asked to provide two variables - daily oil rate and cumulative oil.
TIP: The second variable is needed if you wish to switch to a
rate cum analysis.
OFM requires a source of daily oil rate data. In the Provo project,
you do not have raw daily data, so you will create similar data
using a calculated equivalent.
OFM performs its forecast calculations on a monthly basis, so a
single value for the oil rate will be required for each month. This
requirements also allows you to calculate a daily equivalent from
monthly data.
209
Schlumberger
There are two ways you can define the daily equivalent:
Calendar day average rate that is equal to the volume

produced, divided by the number of calendar days in the
month.
Producing day average rate that is the volume produced,

divided by the number of days on production).
The preferred method is the producing day average rate. Because

of the way in which a group average is calculated, this must be
accomplished using a calculated field. In this instance, the
expression for the calculated field is
IIF(HOURS <> 0, OIL*24/HOURS, NULL)

NOTE : Remember to set the Grouping option to Sum when
creating this variable.
For reference, the corresponding calendar day average would be
a calculated variable with the definition:
PRD.OIL / @dom(Date)
TIP: 'Days on production' data may not always be available, but
it is always possible to calculate a calendar day average.
Exercise 2
Creating the Calculated Cumulative

Oil Variable for Forecasting
When forecasting oil, you must set the cumulative variable in

thousands of bbl (or thousands of m 3 if metric). If the project Unit
Multiplier Style is set to Field, then set M; if the styleis set to
Metric, then set K. You set the style by selecting Workspace >
.
Options > Units.
1. Find the calculated variable for cumulative. oil using the
Calculated Variable editor
2. Select the Math tab.
3. Set Output Multiplier = M

4. Klik OK to save changes.
.
210
Schlumberger
Exercise 3
Setting Up a Forecast Association
Begin the first phase of the forecasting process by selecting the

variables to use in your forecast session. This is done interactively
in an OFM forecast dialog.
1. Select Forecast form the Home tab.
2. If this is the first time you have used the forecast module, you
are prompted to set up the forecast variables. Click Yes.
If you are not prompted, then continue with step 3.
3. Click Edit.
4. Make the selections, as shown in the figure, to set up an oil
forecast.
NOTE: OFM confirms the M output multiplier (arrow) which
you provided. If this is not the same as the multiplier
in the label to the left (Cum Oil, Mbbl), exit the dialog
and modify the multiplier in either the calculated
variable or the calculated field.
211
Schlumberger
4. Click OK to save your changes and exit the dialog.

5. Choose the first completion HOGL1032. A forecast window
displays.
Lesson 2
Forecast Analysis
Now that the preparatory work is complete, you can begin the
actual analysis. You will do that by determining which region of the
historical data can be considered representative for the purposes
of predicting future performance.
Procedure 1 Determining a Representative

Region
1. Remove data points that do not belong to the representative
region.
2. Configure the rate and time at which your forecast is to begin.
3. Determine which factors will control the end of the forecast.
212
Schlumberger
Historical Regression (History Match)

You should see several things in the window after completing the
previous exercise:
OFM graphed your selected rate variable (ProducingDay Oil

Rate) against time on a semi-log basis. This is the default
display setting.
All historical data are plotted. The data points are represented
by red dots, and are connected by light green lines.
A straight line fit (match) has automatically been made

through all of the historical data points.
A forecast has been proposed, based on the automatic

match and the default settings for the forecast.
Results of the proposed forecast display in a legend.
All of these things happen automatically according to default

settings but they can all be controlled.
You will create a match (fit) to the historical data. Remember that
the match will control the forecast, so time spent in this phase will
be rewarded with better quality results.
OFM provides several tools for ensuring that your match is made
using data points considered representative of the past
performance of the completion. By extension, this is considered
representative of its future performance.
For completion HOGL1032, there are observations you can make
that will determine how to proceed.
The region from 1980 to 1991 exhibits a very clean straight

line on this plot, which is indicative of exponential decline.
However, it is no longer representative because work was
done in this well during the 1990s, which invalidates the
earlier data for inclusion in the analysis.
Abnormally high data values during 2004 are not

representative, and may even be erroneous.
The region from 2000 to 2007, while noisy, is considered to

be the most representative for forecasting purposes.
For all these reasons, you need a way of excluding the

unrepresentative data from your analysis. You do this using the
Limits feature, which has six options. You will explore four of
them.
213
Schlumberger
Upper and Lower Limits

Upper and lower limits perform similar tasks but in opposite
directions. Together, they eliminate large regions of data by
scribing a partition (dividing line) through the plot. Any data point
on the wrong side of the line is excluded.
Exercise 1
Setting a Lower Limit Line
1. Right-click on the graph and select Limits > Lower.

2. Using the left mouse button, digitize a series of points on the
graph. These are shown in the figure with arrows.
Your goal is to define a line that represents the lowest values
you are willing to accept. In other words, a lower limit line is
placed below the data points you wish to preserve, but above
the points you wish to eliminate. This line will eliminate data
prior to 1992.
3. Notice how the line also cuts off the anomalously low point at.
the end of 2006.
After clicking the last point, right-click again and select Done.
214
Schlumberger
The entire region up to mid-1991 has been excluded, along with

the single data point at the end of 2006. OFM automatically
rematches the remaining points and updates the results legend.
TIP: When a Lower Limit line is confirmed, OFM removes all
data points below the line but it also eliminates all data
points beyond the ends of the line.
The figure illustrates an alternaltive, faster way to eliminate
every data point before mid-2000 and after 2009, as well
as the spike at the end of 2006.
215
Schlumberger
Exercise 2
Setting an Upper Limit Line
This same principle can be applied to the Upper Limit.

1. Right-click on the graph and select Limits > Upper.
2. Using the left mouse button, digitize a series of points on the
graph, as shown in the figure, to eliminate from the analysis
the spike and possibly erroneous values in 2004.
Your goal is to define a line which represents the highest
values you are willing to accept. An upper limit line is placed
above the data points we wish to preserve, but below the
points you wish to eliminate.
3. After clicking the last point, right-click and select Done.

The bad data points have been removed from the analysis.
The fit recalculates and the results are updated.
216
Schlumberger
Exercise 3
Excluding Data Points with Range

Limit
This feature works by excluding data points outside a range of

either the X-axis (date values), the Y-axis (oil-rate) values, or both.
1. Right-click on the graph and select Limits > Range.
2. Set the values shown in the figure and click OK. All data prior
to 2001 has been removed
NOTE : Remember that data points are being removed only
from the analysis; the data are not affected.
3. Using the Zoom tool, focus in on the newly reduced area.
217
Schlumberger
Exercise 4
Toggling Working Points
This tool works like an eraser, allowing you to selectively remove

individual points by wiping their selection (active status) off the
screen.
1. From the Format tab, click the Erase pint icon.
2. On the graph, click and wipe the cursor across the popints you
wish to remove.
The data point symbol changes as you erase the data point.
Use this feature to remove some of the outlier points - points
that abnormally high or low.
. to
3. When you are finished, click the Erase Points icon again
apply the changes.
218
Schlumberger
The Variable Option

There will be occasions when you will wish to remove data points
from an analysis for reason that are not evident from the garph.
For example, you might wish to remove all points acquired during
choked flow periods or where the flowing pressure was unstable.
You also could have a very large data set and wish to remove
outliers quickly and automatically. The variable option allows you
to achieve these aims.
In pronciple, you choose a project variable (table variable,
Calculated Variable, user function) that return a True or False
(one or zero).
OFM evaluates this variable at every time step (month). If the
variable return True (or 1), the corresponding data point for that
month are included in the analysis. If the variable return False (or
zero), the corresponding data point for that month are excluded
from the analysis.
Exercise 5
Using a Calculated Variable
We will eliminate any data point where tha water cut is in excess
of 99%.
WARNING: So far, all your changes to the data are temporary.
Working with a calculated variable reset the data
set to its original extent. To prevent this, temporarily
save the forecast.
1. Click on Save Forecast on the Format tab. This will preserve
your changes.
2. Create a new Calculated Variable with this definition:
.
@if(Water.cut>0.9, 0,1).
If the water cut exceeds 0.99, this variable return 0 (False).
otherwise it return 1 (True).
3. Name this variable WC99.
4. On the graph, right-click and Select Limits > Variable.
5. Check the Use Variable box and choose the new Calculated
Variable.
219
Schlumberger
6. Click OK.
7. Observe the revised analysis. Notice how almost every data

point after mid-2004 has been removed.
You could decide that if the value of oil rate on any date is within
10 percent of the previous monthly value, the point is considered
valid. If not, the point is considered bad.
This is corresponding Calculated Variable definition that
matches that statement.
Test = @if(@abs((prd.pdoil@previous(prd.pdoil))/@previous(prd.pdoil))<
0.1, 1,0)
220
Schlumberger
Exercise 6
Digitizing Data Points
This is the last of data reduction options. It lies outside the limits
collection because it does not deal with limiting data; instead, it
deals with replacing it.
There could be occasions when you either do not wish to use the
data provided (it is unreliable, poor quality, or too noisy) or you
could have insufficient data to begin (the well has only just started
producing). You might wishto construct your own data.
For this exercise, you will begin by using the feature in a way that
allows all data points to be restored.
1. Right-click and select Limits > Reset to restore All data points.
2. On the graph, right-click and select Digitize.
3. Click on a series of points you wish to use instead of the
.
existing data points. A suggested set is highlighted in the
figure.
221
Schlumberger
4. Right-click on the graph and select Done.

.
OFM ignores all the data and fits a match through your
points.
You have been introduced to several limit capabilities and you are
free to use them in any order you wish. You do not have to use
all of them and, in many instances, a single limit option could
achieve everything you need.
222
Schlumberger
Lesson 3
History Match Settings
Up to now, all fitting was accomplished automatically, based on

selected data points. In this section, you explore how these
activities can be controlled.
The settings which control the primary shape of the fit are located
on the Properties pane. Take a moment to note the default
settings, as shown in Figure below.
Fit Type
The Fit Type is set at Best Fit, which allows OFM to decide if the
best statistical fit through the included data points is exponential,
hyperbolic or harmonic. In some circumstances, you may wish to
allow OFM to determine the fit this way.
For example, it may be that exponential decline is predominant in
your own project. For this completion, you may wish to force OFM
to find the best exponential fit through the data.
223
Schlumberger
Procedure 1
Finding the Best Exponential Fit
1. Choose the setting Fit Type.

2. In the drop-down list that displays, choose Exponential .
While you continue to work on this completion, OFM will
determine the best straight line through the semi-log plot,
which is the definition of exponential decline.
3. Confirm the fit by looking the result legend. The Arps b value
is zero, conforming an exponential decline fit.
3. (Optional) Force OFM to always find the best harmonic fit by

choosing Harmonic from the Fit Type property list.
4. Confirm the fit by noting the results legend, where the b value
should be 1.
Procedure 2
Constraining the b Value to a

Range
The Arps b value is an important parameter in decline analysis. In

OFM the value is automatically calculated when you conduct
history matches. This is visible in the Properties pane, where the
History Match b Value Method is set at Optimize.
There are occasions when you have more detailed knowledge of
the performance of the wells in your project.
224
Schlumberger
For example, you might know that b value typically range from
0.2 to 0.4 or you could be reasonably confident of assuming the
b values is 0.3. For both of these situation, you can adapt your
OFM forecast.
1. Set Fit Type to Best Fit.
2. Set Method to Range. A new property element is displayed.
3. Enter the minimum and maximum values, for example 0.2

and 0.4, respectively. OFM will not allow the subsequently
calculated value to fall outside this range.
To constrain the value to a single number, Set Method = User
A new property element is displayed.
4. Enter the single figure you wish to use, for example 0.3. OFM
will find the best fit through your data, subject to a fixed b
value of 0.3
Procedure 3
Initiating Manual Fit
When OFM performs a match to your data, it is a statistical fit

through a series of x-y data pairs; no actual petroleum engineering
analysis is occurring. You could decide that the statistical fit is
good but that an engineering eye could improve it. OFM allows you
to do this by means of the Manual Fit feature.
225
Schlumberger
On the graph, notice the control points on the plot. These are the
two blue dots at the ends of the line.
1. Click and drag the: upper blue control point and take a note of
several things.
The upper control point is moveable.
The control point drags the fit line.
The lower control point remains fixed.
The forecast moves with the fit.
The results legend updates continuously.
2. Release the mouse button. Note that the entry for History
Match Method on the Properties pane has changed to
Manual.
WARNING: When Method is set to Manual, it will remain
Manual until you change it back to Auto on the
Properties pane.
226
Schlumberger
Using this feature, you can place the fit anywhere you like on
the screen. The forecast and the calculated results reflect your
changes, so be prepared to justify your action. Your fit is now a
personal judgment and is no longer supported by the calculations
NOTE: In this example, there are two control points because
two points are sufficient to define straight line
exponential decline. If your existing fit was hyperbolic,
a third central control point would also display,
allowing you to control the curvature of the line.
Notice also that, although the harmonic fit is also a
curve, its curvature is defined by b = 1. As a result,
the curvature of a Harmonic fit cannot be manually
modified.
Future Performance Forecasting

Now that you have fully applied the limits and fitting options to
build the history match, you are ready to begin forecasting the
performance of the completion. Each time you choose an entity to
forecast, such as a completion, OFM applies a series of default
attributes to the analysis.
Procedure 4
Viewing Historical Regression

Attributes
1. Right-click on the forecast graph and click Scenario

Manager
2. In the The Scenario Manager dialog, click Edit
3. In the Edit Scenario: Default Scenario dialog, click the
Historical Regression tab.
4. Observe that the default analysis is a Rate-Time analysis.
Observe also that the analysis Method is set to a default of
Best Method.
5. (Optional) choose any of the other options as the default
method.
TIP: If wells in your OFM projects typically exhibit, for
example, exponential decline, you may wish to set
Method = Exponential as the default. This will save
you time later, as no manual adjustment is needed.
227
Schlumberger
6. Where appropriate, the Hyperbolic selection allows you to

set a specific (known) b value as the default.
7. Observe that you also
can preset minimum and / or maximum
:
b values.
Procedure 5
Viewing Forecast Attributes
To view and modify default forecast attributes:

1. Click the Forecast tab.
The starting flow rate for a new forecast is set to be equal in
value to the last historical data point. This appears as Start
Rate = Last Historical Rate. There will be occasions
however when the last data point is not a representative point.
It is preferable to consider the forecast to be an extension or
continuation of the fitted history match.
2. Set Start Rate to From Fit.
228
Schlumberger
3. Click OK to return to the Scenario Manager dialog.

4. Click Apply to save the changes. A confirmation dialog
displays prompting you to confirm.
5. Click Yes to apply these settings to the current case.
6. Click Close to close the dialog and return to the graph.
7. Observe the change in the behavior of the fit and forecast;
they appear as one single line or curve.
NOTE: All entities without a saved forecast will adopt this
and the other default setting. Any entity with a saved
forecast will display the attributes of the saved
forecast and not the default.
229
Schlumberger
Working Forecast
Phase
Case Name
b
Di
qi
ti
te
Final Rate
Cum. Prod.
Cum. Date
Reserves
Reserves Date
EUR
Forecast Ended By
DB Forecast Date
Reserve Type
Producing Day Oil Rate
Parameters
: Oil
: Case1
:0
: 0.0117753 M.n.
: 0.809686
: 01/31/2009
: 01/31/2019
: 0.197119
: 50.3675 M
: 12/31/2008
: 1.5834 M
: 01/31/2019
: 51.9509 M
: Time
: Not Saved
: None
0.5
0.2
1998 99 2000 01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
Date
230
Schlumberger
Edit Scenario Dialog

This window has five sections.
Schedules
A period in time during which the remaining

settings apply.
A forecast can be made up of as many as 20
schedules, each with its own settings.
Start settings
Controls the position of the first point on the

forecast profile.
Limits
Controls how the forecast will end.
Decline
parameters
Allows you to disconnect the forecast from the

history match by applying your own values for
the type and decline rate.
Advanced
settings
Additional control options
You will not investigate every permutation in this dialog, but you
will work through a few common options. (Refer to the online Help
for full details.)
Exercise 1
Single Entity (Individual) Forecast

Setting
You have now modified the default settings for all entities you will
work with; you will now explore controlling the forecast of each
entity individually. You will modify individual entity forecast
settings.
1. Choose completion HOGL1032 and double-click on the
forecast graph. The Edit Scenario dialog displays.
2. Create a 5-year forecast for this one entity, subject to two
additional constraints.
- Operational economic limit of 0.5 bopd
- Reserves estomate
231
Schlumberger
3. Use the information in the table to specify values for

Schedule #1.
Start Time
Months from End = 0
Start Rate
From Fit
Reserve Type
Proven-Developed
End Time
Months from Start = 60
End Rate
0.5
NOTE: Months from End means months from the end of the
project, not just the entity in question. OFM looks for
the last date for which there is production from any
entity. This will be 'time zero' for all forecasts.
NOTE: The Proven Developed setting is a label with no effect
on the analysis. Is useful as a future filtering criterion
4. Click OK.
5. Observe the effect.
According to the results legend, the forecast ended ('te') on
January 31, 2014, when the time limit of 60 months was
reached. This is confirmed on the legend by Forecast Ended
by = Time
Also Observe that the volume produced by the forecast
(Reserves) is 6.032 Mbbl.
NOTE: Depending on how you limited your data, your results
could be slightly different to these but the principles
are the same.
232
Schlumberger
6. Double-click on the graph to display the Edit Scenario

dialog.
7. In the Schedule Reserves area, enter 5 and click OK .
Observe that the forecast has ended sooner (October, 2012)
and the final flow rate (Final Rate) is 2.62 bopd. The forecast
ended because of Schedule Reserves; the reserves figure is
given as 4.95 Mbbl.
NOTE: This is the closest OFM could get to the 5 Mbbl limit
without exceeding it.
233
Schlumberger
TIP: Observe that, in addition to being able to enter data into

The Schedule Reserves and End Rate boxes, the boxes
are also drop-down lists. You can choose any project
variable to represent your parameters.
For example, if you have a table listing all the calculated
economic limits for each completion, you can choose the
table as the source of the Schedule Reserves value.
OFM will look up the appropriate value from the table
and provide it to the forecast analysis.
234
Schlumberger
8. Edit the scenario again, this time setting End Rate = 3 bbl/d
9. Click OK and observe that the forecast ended because you

reached the Rate limit before either the time or reserves limit
was reached. The volume recovered (reserves) is reduced to
4.18 Mbbl.
235
Schlumberger
Save Forecast
Assume the forecast for this completion is acceptable. Save the
forecast to the project by selecting Save Forecast from the
Format tab.
Your forecast for this entity is now committed to the OFM project
and you will see three changes to your OFM session.
The red working forecast profile on the graph is now

superimposed with a series of light blue symbols, indicating
the profile which is now in the project database.
You can continue editing the working (red) forecast but the
blue line will remain fixed until you overwrite it by saving the
display.
236
Schlumberger
The results legend indicates that today was the last date on
which a forecast was saved for this entity.
The Forecasts pane now shows an Oil forecast was saved

for completion HOGL1032 under Case1. (Cases are
discussed later in the training.)
NOTE: Although you have worked specifically with oil

production data, the same processes are used when
forecasting gas or water. The only difference is your
choice of the appropriate variables (rate and
cumulative, respectively).
237
Schlumberger
Procedure 6
Recalling a Saved Forecast or

Working Forecast
There is one more feature worth mentioning now that you have a
saved forecast: recalling the data used to create the saved
forecast.
1. Click View.
2. Toggle OFF the Working Forecast Mode checkbox on the
Layout tab.
.
You can now see

data points used in the history match
the match itself
the subsequent forecast, including the relevant legend.
3. Toggle ON the checkbox to restore the working forecast.
238
Schlumberger
The Forecast Graph

Before proceeding, consider improvng the appearance of the
forecast graph. There are two areas you can influence: curve on
the plot and graph headers (titles).
Just as the analysis of a forecast is set by defaults, the display of
a forecast window is set with defaults. You can control two
aspects of the display:
which curves are display
the graphic attributes of the curves on display
Exercise 2
Controlling the Curve to Display
1. Right-click on the graph

, and select the Graph option from
the menu.
The Edit Plot window in the Forecast module is similar to
the Edit Plot window in Plot module.
The curves are all grayed out. This means you cannot modify
their definition but you can disable them them by clearing the box
next to the appropriate curve.
239
Schlumberger
2. Clear the Selected Historical (Line 5) and click OK. The

result is shown in the figure. The red dots have been
removed.
3. Reverse the change before proceeding.

The forecast plot is a special plot, but it is still an OFM plot.
You have the ability to add curves, add axes, more graphs
and other details just as in a conventional plot.
4. Right-click on the graph
, and select the Graph option from
the menu.
5. Click Add Curve
6. Choose the Water.Cut calculated variable and click OK.
240
Schlumberger
7. Observe the new curve. This can be a useful 'visual aid' for
forecasting.
For example, display another curve as a guide to assessing
where the wellhead pressure could be unstable. In this case,
you might wish to remove the data points in that region.
Exercise 3
Controlling Graphic Attributes
Select or Right-click
1. On the Layout tab, select Enable Curve
.
.
on the graph and select Enable Curve Select.
2. Click on any curve to choose it.
3. Use the Properties pane to alter the color of the curve, the
thickness of the line, and other attributes.
241
Schlumberger
Exercise 4
Editing Forecast Graph Header
You can introduce headers on a forecast graph in the same way

as for a conventional OFM plot.
To edit forecast headers:
1. Locate the Headers section of the Properties pane.
2. Click Setup to open a conventional Headers dialog.
242
Schlumberger
3. Click Add. A new row is inserted into the Headers window.

4. Click Assist. The Edit Header window displays.
5. Enter "Forecast "+@Name().
Note the space after the word 'Forecast.'
6. Click OK. The Edit Header window closes and you are
returned to the Headers window.
7. Click the Font button and apply the following settings:
Style = Bold Italic
Size = 14
Color = Red
8. Click OK to return to the Headers dialog.
9. Add another header that reports todays date. The definition is
@fmtdate(@today(), "Mmmm dd yyyy")
243
Schlumberger
10. Click the Font button and apply the following settings:
Style = Bold
Size = 12
The Headers window should resemble the figure.
11. Click OK. The Headers window closes and the graph displays
with the new titles.
244
Schlumberger
12. Observe the Analysis pane. When you began working on this
forecast, a new node displayed named Forecast1. Now that
the graph looks reasonably complete, you may wish to
rename the node, for example, Semilog ,Oil v Time so that
its format can be recalled.
NOTE: The Forecast nodes that display in the Analysis pane
store information about how you like to view the
analysis session. They do NOT contain the forecast
results.
This node represents a simple and quick pass through a forecast
analysis for one completion in OFM. Your filter is comprised of
eight completions and, as you progress through the others, you
will explore additional capabilities.
245
Schlumberger
12. Before proceeding, remove the water.cut curve.

a. Right-click on the plot and select Graph.
b. Delete or disable water.cut curve.
Review Questions
What are Working Forecast and Database Forecast?
Is it possible to delete a Working Forecast?
What is the physical meaning of the b factor in a Forecast

curve?
Is the Decline Curve Anaysis dependent on the size and

shape of the reservoir or the actual drive-mechanism?
Decline Anaysis is based on the implicit assumption that the

factors that governed performance in the past will continue to
govern performance in the foreseeable future. True or False?
The reserves estimate from a rate time forecast will always

be the same as the estimate from a rate cum forecast. True
or False?
Summary
246
setting up a forecast session in OFM
controlling the history matching and forecasting sections
extracting result from your analysis.
Additional Forecasting Features
Schlumberger
Module 7 Additional Forecasting

Features
Up to this point, you have created a complete but relatively simple
forecast that introduced you to a few of the more common
forecasting utilities. In this lesson, you will explore these utilities
in more detail and use the remaining completions in your filter as
candidates.
Learning Objectives
work with additional phases
create your own phases
work with schedule and cases
Lesson 1
Gas and Water Phases
Your work so far has been based on oil forecasting. You will now
briefly learn how to work with the other two primary phases; gas
an water. In addition, you will learn how to create your own
primary phase for forecasting in OFM.
Exercise 1
Switching Between Gas and Water

Phases
OFM has the default ability to allow you to switch easily from oil to
each of the other conventional primary phases.
1. Double-click on the forecast graph to display the Current
Scenario dialog.
2. In the Phase / Analysis section, click Gas.
247
Schlumberger
3. Observe that the three variables necessary to proceed with

the analysis have changed.
Set these parameters:
Time (Date) = Date
Cum Gas, MMcf = Cum.Gas.Prod
Gas Rate, Mcf/d = Prd.PDGas
NOTE: The variables for cum gas and gas rate must be set
with Output Multipliers MM and M, respectively. When
you choose these variables, OFM displays their
multipliers next to the selection as confirmation that
they are correct. If they do not match, you must stop
the process and correct the discrepancy.
5. Make these changes and click OK.
Start rate = From Fit
End Rate = 0.1 Mcf/d
248
Schlumberger
6. Observe the effect. With a small number of changes, you can

now work exclusively with gas production data.
7. Assuming the fit and forecast are acceptable, save the
forecast.
.
The Forecasts pane changes to indicate this completion was
saved as a gas forecast, under Case1.

Scenario dialog.
9. In the Phase / Analysis section, click Water.
the analysis have changed.
Time (Date) = Date
Cum Water, Mbbl = Cum.Water.Prod
Water Rate, bbl/d = Prd.PDWater
NOTE: As before, the variable for cum water must be set
with Output Multiplier M. If it does not, you must stop
the process and correct the discrepancy.
12. Make the following changes and click OK.
End Rate = 0.1 bbl/d
249
Schlumberger
13. Make no changes to the graph but save the forecast.

The Forecasts pane changes to indicate this completion was
saved as a water forecast, under Case1.
Exercise 2
Forecasting with User-Defined

Phases
OFM support the concept of user-defined primary pahses. This

means you can add project-specific phases and use the range of
functionality to create forecasts of the new phases.
Scenario: Completion HOGL432 has condensate data, and you
would like to forecast it.
1. Verify that variables for Cumulative Condensate
(Cum.Condensate.Prod) and Producing Day Condensate
Rate (Prd.Pdcond) are available.
If not, the source table variable for both is Prd.Cond. Use the
corresponding calculated variables for cumulative oil and
producing day oil rate asaguide.
2. Select Phase Setup from the Format tab.
.
3. In the new dialog, click Add.
4. In the Name box, type Condensate and click OK.
250
Schlumberger
5. Leave the phase Type set as Liquid.
6. Click OK again to save your changes and exit the dialog.

7. Choose completion HOGL432
.
Scenario dialog.
9. In the Phase / Analysis section, click the new entry
Condensate.
the analysis now reflect condensate values.
Time (Date) = Date
Cum Condensate, Mbbl = Cum.Condensate.Prod
Condensate Rate, bbl/d = Prd.PDCond
NOTE: As before, the variable for cum condensate must be
set with Output Multiplier M. If it does not, you must
stop the process and correct the discrepancy.
12. In the Condensate Schedules area, click Add to create a
new schedule.
13. Make these changes and click OK.
Start Time = Last Historical Date
End Rate = 0.1 bbl/d
251
Schlumberger
14. Apply data reduction operations to give a meaningful

prediction.
13. Save the forecast.

The Forecasts pane changes to indicate this new completion
also has a saved condensate forecast under Case1.
252
Schlumberger
Lesson 2
Additional Scenario Settings
The future performance of any entity may be influenced by of a

series of events.
For example, a well could be a subjected to a workover in a years
time. Two years later all wells could be shut in for a field
maintenance program.
OFM allows you to acknowledge these known events by building
the forecast from a sequence of time periods. Individual time
periods are represented by OFM through Schedules. A Schedules
is a time period during which a set of assumptions will apply.
Exercise 1
Configuring a Two-Schedule
Forecast
Scenario: Completion HOGL1132 is not performing well and,

since mid-2007, decline has accelerated. An untapped sand was
identified in the wells in this area and a perforation program will
begin in January 2011. Early results indicate this new sand can
support an additional 20 bbl/d at the HOGL1132 location.
Completion HOGL1132 is to be included in the perforation
program. It is, therefore, reasonable to conclude that the future of
this completion will be in two distinct parts.
The period leading up to the perforation activity, during
which it will decline as normal.
The period following the workover, when you anticipate it will
begin flowing at a rate 20 bbl/d higher than the rate
immediately before the work.
Finally, because this represents incremental production, it is
anticipated that new decline will be parallel to the previous decline.
This is a good example of the need for a multiple schedule
forecast.
1. Choose completion HOGL1132
TIP: You might wish to clear your filte and reselect the Best
Oil OFM query filter.
2. Switch to Phase = Oil.
253
Schlumberger
3. Apply a Range Limit to the data by excluding all data prior to

July 1, 2007.
4. Double-click on the graph to display the Current Scenario
dialog.
6. The settings on the page are for Schedule 1. You will allow
the completion to decline until the date of the perforation job,
so set these parameters:
Start Rate = From Fit
End Time = Date (20110101)
End Rate = 0.01 (This will ensure that rate does not
constrain the schedule)
7. Return to the top of the dialog where you can enter the
second schedule. This will model the effect of the perforation.
8. In the Oil Schedules section, click Add to create Schedule 2.
In this instance the Start Time setting of Month From End
will mean from the end of Schedule 1, so the default value of
zero is correct.
9. Start Rate defaults to Previous, which is the rate at which
Schedule 1 finished. This is not what you want.
The effect of the work is configured by entering 20 b/d
for the Start Rate = Change
. By Parameter.
10. Click OK and observe the effect. OFM has honored the
increase in productivity in January 2011, as a result of the
perforation.
254
Schlumberger
Observe also that the decline shape following the perforation

job is the same as the shape prior to the job.
Start and End Time Controls

The Forecast tab offers many additional controls over how your
forecasts begin and end. Most of these controls are selfexplanatory and can be quickly demonstrated in the working
forecast. More comprehensive details are available in the online
Help.
255
Schlumberger
Start Time Controls

Date
A specific date, in YYYYMMDD format
Months from
End
A specific number of months after the last

historical date in the database for ALL
completions in the project. This allows
forecasts for multiple completions to begin on
the same date.
Last Historical
Date
Date of the last historical data point for the

current completion or group, regardless if it is
included in the fit.
From Historical The date of the last historical data point

included in the fitted history match for the
current completion or group.
Start Rate Controls

Previous
Starts the forecast at the final rate from the

previous schedule.
(Not intended for the first schedule.)
From Historical The rate of the last historical data point

included in the fitted history match for the
current completion or group.
256
Last Historical
Starts the forecast from the last historical

production rate, regardless if it is included in
the fit.
Value
Begins the forecast schedule at a specific

value.
Change By
Changes the default starting rate by the given

rate.
Change By
Percent
Changes the default starting rate by the given

percentage.
From Fit
Calculates the starting rate at the specified

start time using the fit equation.
Last Fit Rate
Calculates the starting rate at the specified

last historical date using the fit equation.
Schlumberger
Shut in
Indicates that production is to be stopped for

the duration of the schedule.
The result is a gap in the graph, indicating
there will be no production during the time
period. The graph line resumes at the end of
shut in period.
Reserve Type
By default, the list of entries available to you is consistent with
SPE standard nomenclature for reserves estimation.
As indicated earlier, the choice you make here has no effect on
on the analysis or the results generated. However,
forecast is saved, this information is also saved. It can be used in
the System Function module for tasks such as filtering criterion
(@DCAReserveType())
Another example might be in the preparation od a report of proven,
probable and possible reserves.
OFM support the idea of allowing you to edit the list of default
entries and to add your own.
Procedure 1
Adding Default Entries
1. Exit the current Scenarion dialog.

2. Select Reserve Type Setup from the Format tab.
3. In the Reserve Type Setup dialog, delete an any entry
. by
highlighting it and clicking Delete.
4. Add a new entry by clicking Add and entering the new name.
257
Schlumberger
5. Click OK and the new name appears on the list.

6. Click OK to save your changes.
7. Double-click on a forecast graph and click the Forecast tab
8. Observe the new entry.
Exercise 2
Creating a Forecast with UserDefined Parameters
There could be occasions when, evenif you have a satisfactory

history match, you might wish to create a forecast with setting
different from history match values.
For example, your match could show it to be hyperbolic, but, for a
conservative forecast, you might wish the forecast to be
expressed as an exponential decline.
1. Choose completion HOGL2_1029
2. Use any technique you wish to exclude all data points prior to
the spike in production in the middle of 2005.
auto fit through this data seems to be hyperbolic (b = 0.586).
NOTE: The auto fit through these data seems to be
hyperbolic (b= 0.575)
258
Schlumberger
3. A hyperbolic forecast may prove overly optimistic for this

well. Other wells in the area tend to exhibit exponential
declines of approximately 2 percent per month.
To recognize this, make changes to the Forecast tab, as
shown in the figure.
4. Clear the checkmark next to the Reinitialize box and click OK.
5. Observe the effect. The future trend for this completion is a
straight line exponential, despite the historical regression
match being hyperbolic.
259
Schlumberger
260
Schlumberger
Lesson 3
Re-Initializing
Earlier in the training you modeled the effect of adding a new

producing layer the well. In terms of reservoir recovery, this action
has the effect of adding incremental reserves. The new line adds
a wedge of new production on top of the base profile.
There will be occasions, however, when the activity is aimed at
returning the well to its original conditions as a way of accelerating
the recovery of existing reserves.
Exercise 1
Simulating the Effect of Rate

Acceleration
Your completion will be subjected to work designed to return the

well to its original conditions. This will accelerate the process of
recovery of reserves. For simplicity, you will use only a single
Schedule forecast and assume the work is done at the end of the
data set.
The default fit through this data set is hyperbolic. Which serves
well for the purposes of illustrating the feature.
2. In the Forecast tab, change the End Rate to Value = 0.5 bbl/d.
3. Save the forecast without changes.
NOTE: The estimated reserves areat 15.372 Mbbl and they
willbe recovered in January, 2019.
4. Make these changes to the Forecast tab:
Start Rate = Value = 12 bbl/d (The result of the stimulation
work, performed today)
Schedule reserves = 15.372.
5. Select the box named Reinitialize and click OK to observe
the effect of this change.
261
Schlumberger
6. Save your new forecast.
Observe that the forecast is not an extension of the fit; it is a copy

of the production history repositioned to start at 12 bbl/d. The
shape could look a little different, but that is the effect of shifting
the copy on a logarithmic scale.
The reserves are recovered over a shorter time period,
approximately 2.5 years sooner.
This is the effect of the Reinitialize feature; you are simulating the
return to initial conditions by replicating the original history.
WARNING: OFM is not a reservoir simulator. The results
generated by this feature should be considered no
more than engineering estimates.
262
Schlumberger
Lesson 4
Group Forecasting
Up to now, you have neem concerned with forecasting individual

completion. Soon, you will need to forecast entities at higher levels
in the project, such as fault compartements, reservoirs, and fields.
These are alla examples, of group forecasts.
A Group is a single entity, just like a completion is a single entity.
The only difference is that a group is composed of completions.
In OFM, the concept is no more complex than what you have
already learned but there are one or two new aspects you should
understand.
To explore the concept of group forecasts, return to the Best Oil
collection of completions.
Exercise 1
Forecasting Oil Group
This exercise is equivalent to completing Task 2 of the Provo

project forecasting workflow.
2. Load the Best Oil filter from the OFM Query section of the
Filter pane.
3. This filter contains eight completions. To create a group

to create a group representing the aggregated (summed)
performance of all eight, click Group
on the Filter pane.
263
Schlumberger
The entry in the main entity selector toolbar shows that OFM
is now working with an 'object' that is a group named
Completions Selected (8).
You can proceed to forecast this new object.

4. If a forecast window is not already open, open one (Analysis
> Forecast).
5. The graph displays a default fit and forecast for the new
object (group).
From this point forward, you use exactly the same tools and
techniques as we did for the individual completion forecasts.
You are already fully familiar with these techniques, so they
will not be repeated here. Your grouping should look like the
display in the figure.
264
Schlumberger
6. Apply a single data reduction filter and set the following

range limit on Date:
Minimum = 19940101
Maximum = 20021231
7. Observe the revised fit and forecast.
.
8. Enter a forecast End Rate limit of 20 bbl/d
Observe that the forecast ends in early 2017, and a reserve
estimate of 111.285 Mbbl is calculated.
10. In the Edit Group Forecast dialog, this group is an ad-hoc
collection.
To save the forecast, provide
.
a name for it. In this instance,
name it Best Oil Group and click OK.
265
Schlumberger
10. Inspect the Forecasts pane where a new entity is displays.

OFM recognizes this entity has a saved oil forecast under
Case1.
The task of creating a single group oil rate forecast forthe best oil
producers is now completed.
Exercise 2
Forecasting Group Gas

2. Apply the Best Gas filter. (Gas completions which have
produced more than 25 MMcf.)
3. Group the resulting eight completions.
4. Choose the Gas phase for analysis.
5. The aggregated performance is rather erratic, with no single
candidate to draw your fit through.
This may be an instance for a manual fit but, in the end, it is
up to you.
6. Apply your historical fit, and create a forecast.
7. Save the forecast as Best Gas Group.
8. Confirm that the new group forecast entity is captured in the
Forecasts pane.
266
Schlumberger
Procedure 1
Forecasting Categories
You created group forecasts by aggregating completions from a

filters. Categories also represent groups of completions. Category
data forecast follows the same procedure as you have seen for
groups. The only difference is in the way you load the objects
2. From the Navigation pane, choose Zone .
3. From the resulting list, choose ZONE III.

4. Observe from the titte of the graphand the legend that the
object you are working with reoresents the total oil rate of all
completions mapped to Zone III.
5. (Optional) Use all the tools to fitting and forecasting you have
used so far.
4. Observe from the behaviour of the Forecast Pane. You now
have a saved oil forecast for zone III under case 1.
The task of forecasting the performance of Zone III is now
complete.
267
Schlumberger
Lesson 5
Cases
Saving a forecast under a case name has been mentioned

numerous times. In OFM forecasting, cases have a special role
to play.
For example, you might wish to create and save for future
comparison several forecasts for one well.
The first case could represent your base case; do nothing

and allow thewell to decline as normal.
A second forecast for the same well couls assume a more

optimistic future than the base case projection.
A third one could assume the opposite, the future profile is

more pessimistic than the base case projection.
A fourth situation could assume that a workover will be

performed in this well and that an increase in production rate
is anticipated.
A fifth possibility might assume that the workover will be

delayed by a year.
Each of these forecasts is a valid analysis but, if you overwrite the

old analysis each time, all the old work is lost and you cannot
perform the comparison.
To navigate through this problem, OFM uses the concept of
cases. All of these scenarios can be captured independently in
OFM by saving them under different cases.
TIP: Think of a case as a folder containing a collection of
forecasts that all follow the same set of assumptions, such
as workover delayed by one year. It makes logical sense to
keep all the forecasts that adopt the same rules in the same
place. This is only a suggestion, but cases are a
This is only a suggestion, but cases are a good method of
organizing your forecasts in a way that make sense to you.
268
Schlumberger
With this additional layer of information, working with forecast

cases introduces another dimension to your ability to differentiate
exactly which results set you wish to work with. When identifying a
forecast to analyze, you can recall the entity and phase as well as
specific assumptions, such as the case name.
Take a look at how OFM embeds case information in your work.
The circled regions are active (current) case names with

information confirmed in two locations; the Current Case entry
on the Forecasts pane and the results legend.
A tree structure is prominent on the Forecasts pane that identifies
the status of each case in the project. The active case name also
appears in the tittle tab for the current Forecast graph.
There is no excuse for not knowing which is thecurrent case!
Procedure 1
Setting Up a Default Base Case
Your first OFM forecast session defaults to Case1. All the work
you have done so far has been under Case1. Assume that all your
existing work is a base case. You might wish to rename the default
case.
1. Right-click on the Case1 node on the tree structure.
2. Select Rename.
3. Rename it Base Case. and Press Enter to save the changes.
4. Observe now that all the entries with circle in the diagram above
have been renamed.
269
Schlumberger
Procedure 2
Creating a New Case
Think back to the possible situations in which you might wish to

forecast for any well. Your first task is to create new nodes or
folders in your tree, representing the new cases.
1. Click the New Case Icon on the Forecast pane.
2. Enter the name Optimistic
3. (Optional) Enter a userid and Comment. The comment field
allows you to describe in detail the reason for creating this
case.
4. Click OK. Observe the following:
The new case node appears on the tree.
It is automatically assigned the new active (current) case.
The blue line on the graph for the current entity does not
display because it is not associated with saved forecast
under this new case name.
5. Create an additional case named Pesimistic
Procedure 3
Reassigning the Current Case
At any time, the current case (also termed the active case) could
be assigned using the Current Case dialog at the top of the
Forecast pane.
1. Open the drop-down list and choose the relevant case.

TIP: Forecasts are normally saved to the current case.
2. Make Base Case the active case.
270
Schlumberger
Procedure 4 Changing the Order of the Display

In a tree format, the Forecasts pane shows information regarding
the forecasting work you have saved in this project. Observe how
the tree is organized.
While this could be a useful way of organizing the data, it becomes

difficult to use when attempting to answer a question such as,
Which cases contain saved gas forecasts for well X?
OFM support the means to answer the question by allowing you
to re-organize the tree.
1. On the Forecasts pane toolbar, click the drop-down arrow on
the Change Order icon.
2. Select Entity > Phase > Case
3. Observe the new behavior of the pane tree.
Among other thing, it shows that, for the BestOil group of
completions, an oil forecast has been saved to only the Base
Case.
271
Schlumberger
Compare Cases
One of the primary roles of a petroleum engineer is to evaluate the
effect of alternative courses of action for a well or group of wells. A
vital tool in this analysis is the comparison of the projected future
of the well under each of the possible alternatives. This requires
creating forecasts, and comparing them for each possibility.
Exercise 1
Creating New Future
To illustrate OFMs capability in this respect, create new futures

for a well.
2. Open a new forecast window.
3. Confirm Phases is set
. to Oil and the Current Case is Base
Case.
4. Confirm that the graph displays an existing saved forecast
(light blue line).
272
Schlumberger
5. Set the Current Case to Optimistic. OFM should display an

unedited dataset, representing the fact that no saved
forecast exists for this well in this case.
Use the tools that you have already learned about to create a
forecast for this completion that represents an optimistic
future.
6. Save the forecast. The Forecasts pane should now indicate
a saved oil forecast.
7. Set the Current Case to Pessimistic.

Because you made no changes for the Optimistic case, the
new case will initially follow the same profile.
8. Double-click on the graph to edit the forecast settings.
9. Set Start Rate = Last Historical Rate
.
10. Manually adjust the match profile to indicate
a high rate of
decline.
11. Click OK.
13. Save the new forecast
Again, the tree on the Forecasts pane should update to

reflect that there are now three saved oil forecasts for this
completion.
273
Schlumberger
Procedure 5 Comparing Cases

1. On the Layout tab, select Display Cases
2. In the Display Multiple Cases dialog, select the show
additional cases on the graph checkbox.
3. Select (check) the three items on the list and click OK.
274
Schlumberger
NOTE: At any time, there can only be one active (current)

case. This is evident on the graph in two places - the
active case displays a working forecast (red dotted
line), and the new legend shows the attributes of the
non-active cases.
TIP: Even though you are in a comparison 'mode' of display,
you may continue working as normal. You may choose
to switch the active case, and return to an earlier
forecast to make adjustments.
The task of preparing and comparing new oil forecast for
completion HOGL1032 (a base do nothing forecast, together
with optimistic and pessimistic predictions) is now complete.
275
Schlumberger
Lesson 6
Ratio Forecasts
All the forecasting work you have done to this point has been
time-based. There are other, equally valid methods of forecasting.
The most commonlyused alternative method is the Ratio forecast.
Ratio forecast operate on the basis that there is a well
understood, and moderately predictable, relationship between the
parameter under investigation (a water/oil ratio, for example) and
recovered volumes (production) of oil or gas. This type of
forecasting uses cumulative production as the basis for
predictions.
Exercise 1
Creating a Water-Cut Forecast
To begin, you will work with Water Cut versus Cumulative Oil
analysis as an introduction to the concept of Ratio forecasting in
OFM
1. Open the Current Scenario dialog.
2. In the Flow Model dialog, choose the settings shown in the
figure.
TIP: Note the unit multipliers.
3. Click OK to accept the changes.
276
Schlumberger
4. Choose completion HOGL1132 and

. the forecsat dispalys.
Classical water-cut development typically follows an S shape.

As cuts increase to higher values, the curve tends to roll over,
causing the subsequent projection to be much flatter.
In this completion, you can see that the roll over is well
estlabished. This means that your historical match should be
restricted to the near-end region of the data.
5. Select Limits > Range (or any option you wish).
6. Enter these parameters:
Min = 380 Mbbl
Max = 400 Mbbl.
By default, an OFM water-cut forecast ends at 95%. In your

completion, the current (last) data point is already 99.5%, so
there is currently no forecast.
277
Schlumberger
TIP: To create a forecast, you must reset the end value. For
now, assume it is possible to produce this completion to
99.9% water cut.
7. In the Properties pane, make these selection:
Select Forecast > Start WCUT Option > From Fit.

Select Forecast > End WCUT Option > Value.
8. Enter 99.9 for the End WCUT.

9. Zoom into the area of interest to see the effect. You might
need to adjust scale minimum, maximum, and scale type
(Linear) to be able to see the short forecast.
7. The legend shows thattoif the completion

. produced to a 99.9%
water cut, the completion would recover an additional 13.19
Mbbl of oil.
278
Schlumberger
Other Fluid Cuts

Exercise 1 can be used for any of these fluid cut analysis in OFM:
GOR - (Gas oil Ratio)
WOR - (Water Oil Ratio)
NOTE: For WOR analysis, the default END value is 10 times

the START value.
OCUT - (Oil Cut)
TIP: While the definitions of water cut and water oil ratio are
co-dependent, their forecast limits can be independent,
for differing reasons. Typically, wellbore hydraulics (lift
capacity) govern the water-cut limit, while surface
process design could provide a water-oil ratio limit.
Lesson 7
Calculated Forecast
In this reason, you will learn how to combine the result of a Ratio
forecast with a Primary Phase forecast to create a new phase
forecast, the Calculated Forecast.
This is very common question among OFM users:
I have saved an oil vs. time forecast, andI have saved a
water cut vs. cum oil forecast. I need to generate a fluid
forecast for this well. How do I combine these mutually
independent profiles to obtain a water vs. time forecast?
In this scenario, oil and water-cut data could be readily available,
but water data are not. For example, oil rates were measured
directly, while water cut was the result of wellhead sampling.
Another scenario could be one in which water data are available,
but they are considered to be unreliable.
In these situations, obtaining a water forecast might require a
series of external manual calculations involving lookup tables,
interpolations, and other sources. An expert user could know how
to achieve the same result in OFM,but it would not be intuitive for
a casual user.
279
Schlumberger
TIP: This method of water forecasting requires an obscure from

of a System Function.
Procedure 1
Creating a Calculated Forecast
The Calculated Forecast is designed to directly answe the

question posed in the first scenario. The feature is being
introduced in the training at this time because of the most common
way to using it would not be possible until a Ratio analysis is
completed.
1. Ensure completion HOGL1132 is selected.
2. Verify in the In the Forecast pane that you have saved Oil and
Water-Cut forecasts for this completion.
3. Right click on the forecast graph and select Scenario to display
the Edit Scenario dialog.
4. Generate a calculated Water forecast.
a. Choose Phase = Water
b. Ensure that these variables are set:
Time (Date) = Date
Cum Water, Mbbl = Cum.Water.Prod*
Water Rate, bbl/d = Prd.PDWater*.
TIP: * You might need to create these variables first. It is best to

use the corresponding oil variables Cum.Oil.Prod and
Prd.PDOil as guides for the definitions.
280
Schlumberger
c. Click the Calculated tab.
281
Schlumberger
Because your selected phase is Water, this dialog provides

several options for calculating a water forecast.
The WATER phase is not Calculated from other phase:

This is the default option. The forecast is done using water
production data.
The WATER phase is calculated from ...: You select how

you want the water phase calculated.
Forecast Phase and
Ratio Forecast
Oil is the only usable primary

phase; Ratio forecast are based
on cum oil.
For calculated water, the available
ratio options are WCUT, WOR,
and OCUT. OFM calculates the
water rate versus time from
these two sources.
Forexcast Phase
multiplied by
constant
You supply a constant value. This

is used to directly convert Oil
forecast values to Water forecast
values.
Forecast Phase
multiplied by
variable
A variable is chosen from the

standard project variable list. The
variable must evaluate at future
dates; the calculated result is in
the future.
Calculated from
Variable
Choose a project variable to

represent the water forecast.
5. In this example, select Forecast Phase and Ratio Forecast.

6. Set the phase to OIL and the Ratio to WCUT.
7. Click OK to accept the choices and perform the calculation.
282
Schlumberger

Several features of the display in the figure are note worthy.
The Calculated forecast is independent of the historical

regression, if any exists.
Decline result, such as b and Di, do not display on the

legend because they are not involved in the process.
The forecast Ended by setting in the legend reads
Calculated, confirmation of the process.
Because the oil forecast was across two Schedules (preand post-workover), the water forecast has a corresponding
two Schedule profile.
283
Schlumberger
Review Questions
When might it make sense to maintain more than just the

Default scenario?
In which cirmumtances might adate limitbe applied to a forecast?
How would you use the result of a Water-Cut analysis to

improve an Oil forecast?
Summary
setting up a forecast scenario and working with the results
editing a graph
changing the fit type
working with multi-schedule forecast and performing a

manual match.
working with phases
performing group forecasting
working with cases and extracting forecast results
performing a Ratio analysis and creating a calculated

forecast
284
using automated calculated variables and reports.

Handout OFM Fund-Int Trisakti-FIN2

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Handout OFM Fund-Int Trisakti-FIN2

Hochgeladen von

Copyright:

Verfügbare Formate

OFM One Day

Software Integrated Solutions (SIS)

About this Manual

Module 1: Introduction to the Training

Module 2: Groups and Filters

Lesson 6: Completion Data Grouped in the Navigation Pane . . . . . . . . . . . . . . 36

Module 3: Project Variables

Lesson 2: OFM Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Module 6: Simple OFM Forecasting

The Variable Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

Module 7: Additional Forecasting Features

Lesson 5: Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

About this Manual

About this Manual

navigate an existing OFM project

set up the base map

filter to the completions of interest using a variety of

define calculated variables

analyze project data using the OFM modules of plotting and

About this Manual

What You Will Need

OFM, properly installed and licensed

Training data sets.

Overview of the module

Prerequisites to the module (if necessary)

A workflow component (if applicable)

Lessons, explaining a subject or an activity in the workflow

Procedures, showing the steps needed to perform a task

Exercises, which allow you to practice a task by using the

Questions about the module

Summary of the module.

You will also encounter notes, tips, and best practices.

About this Manual

Represent references to dialog box names,

Indicate variable values that the user must

Represent file names or directories, such as

characters inside <>

Represent option areas in a window, such as

Represent code, data, and other literal text

NOTE: Text you must enter is indicated in a fixed-width font or a

An OR is used to identify an alternate procedure.

About this Manual

About this Manual

defined the learning objectives

outlined what tools you will need for this training

discussed what you will encounter within this material.

About this Manual

Introduction to the Training

Module 1 Introduction to the

Tour of a Working OFM Project

Over the course of this training, you will be exposed to many

The Walkthrough Project

Introduction to the Training

Your instructor will perform these tasks:

Introduction to the Training

Walkthrough Project Components

Project Configuration: OFM Workspace and Base Map Customization

Groups and Filters

Module 2 Groups and Filters

Groups and Filters

The concept of filtering in OFM has proven to be very useful, as

Groups and Filters

well lists and archives

You can group together completions in the current filter in three