Release Notes for OFM™ 2007.

3
Copyright 2008 Schlumberger. All rights reserved.
No part of this manual may be reproduced, stored in a retrieval system, or translated in any form or by any means,
electronic or mechanical, including photocopying and recording, without the prior written permission of Schlumberger
Information Solutions, 5599 San Felipe, Suite 1700, Houston, TX 77056-2722, USA.
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

Introduction
OilField Manager™ (OFM™) 2007.3 is a full install release and supersedes all previous versions
of OFM. This release corrects a number of defects discovered in OFM 2007.2 and earlier
commercial releases. A summary of changes can be found below.

Warning:
The workspace file (*.OFM) created by OFM 2007.3 is not backward compatible with OFM 2005.
All OFM 2005 workspaces will automatically be converted to OFM 2007.3 formats. Users will be
prompted upon opening their OFM 2005 workspaces to allow OFM 2007.3 to automatically create
a back-up copy of the 2005 workspace files.

Workspaces created by OFM 2007.2 are fully compatible with OFM 2007.3.

Summary of Changes in OFM 2007.3

OFM 2007.3 corrects a number of defects in OFM 2007.2. These are detailed functionally in the
sections that follow.

Workspaces
• Fixed a problem which caused pre-existing Nodes to be deleted when changes were not
to be saved.
• Allow a user’s “My Workspace” tables to take precedence over the same table in a
Shared Workspace, reversing the existing conflict resolution.

Calculated Variables
• Fixed problem caused by deletion of a Calculated Variable used in a plot header.

Decline Curve Analysis

• Allowed a forecast to be prepared for a completion with no production history.
• Fixed problem occurring where DCA module crashed when Step = Wellbore and graph
contains multiple curves.

Exporting
• Fixed problem of OFM writing to limited number of columns in an Excel spreadsheet.
• Fixed problem writing date / time data to an Access table.
• Fixed problem when creating Snapshot of a project which contains a Query. Query is
converted to a table. Any filed in the query which had a zero field length would cause the
Snapshot copy process to fail.
Filtering
• Fixed problem of using “Group By” option when creating an OFM query filter.

General
• Fixed problem when a SQL query was forced to handle just one entity.
• Fixed problem relating to recalling data for a completion for which there is no category
mapping.
• Fixed problem of trying to load data to a Wellbore or Category level table.
• Corrected issue arising when foreign key is composed of two keys.
• Corrected a fault when a project migrated from OFM 2005 used a Date Label different
from “Date”.
• Corrected fault which arose when migrating Calculated Variables using the System
Function @groupdata() from OFM 2005 to OFM 2007.

Dwights Loader
• Fixed problem where loader was not loading Category data.

Patterns
• Fixed problem in Pattern module where data could not be edited at well level.
• Fixed problem of Multiply By Factor option not working correctly.
• Fixed problem arising when stepping by Pattern, filtering to a reduced number of
Patterns, then attempting to group the data.

Plots
• Fixed problem when using “Add Multiple Curves” option while "Display Alias as
Completion Identifier" is turned on.
• Fixed problem highlighted by attempting to plot large data sets. Existing default plot data
frequency option causes plot to be slow to generate.

Reports
• Fixed problem which occurred when a Report displayed both Date and Time, and a
WHERE clause was used.
• Fixed problem caused by use of @fiteq and @fitr2 System Functions in a Report.
• Fixed problem of Report not breaking correctly when displaying daily data and requesting
a monthly break, while a WHERE clause is in effect.

System Functions
• The @CountInput() System Function has now been extended to (optionally) allow the
user to return information relating to how many entities in any particular Step Category
were contributing to the table variable. The new syntax is as follows:

@countinput(input variable, [“Type”])

where

Input Variable Table variables only (not Calculated Variables)

Type Name of any project Step Category, including “Completion” and
“Wellbore”

Type “Completion” will return the same value as the original form of the System Function
if the frequency of the data is set to default. An example when this argument will return a
different value is when doing a report of monthly data and the report frequency is set to
annually for a single completion. @CountInput(Monthlyprod.oil) will return 12 but
 @CountInput(Monthlyprod.oil, “Completion”) in this instance would return 1. This allows
a user to find the number of completions that contributed over a given time interval.

Type “Wellbore” or Category Name will return the number of items that contributed over a
given time interval.

June 2008