Petrel 2011.1 What's New

Petrel*
Version 2011.1
Schlumberger Public
Whats New in Petrel 2011.1 Guide
Copyright Notice
Copyright 1998 - 2011 Schlumberger. All rights reserved.
No part of this document 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 100, 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.
*Mark of Schlumberger. Certain other products and product names are trademarks or
registered trademarks of their respective companies or organizations.
Schlumberger Public
Trademark Information
Contents
Welcome to Petrel 2011 ............................................................ 12
Disciplines Working Together ............................................................................. 12
Access to the Best Science .................................................................................. 13
Increased Workflow Productivity ....................................................................... 14
General Functionality ................................................................ 16

Studio Favorites .................................................................................................. 16
Arrangement of Windows ................................................................................... 17
Window Auto Focus ............................................................................................ 19
Clean Project History .......................................................................................... 20
Geophysics ................................................................................ 21
Interpretation ..................................................................................................... 21
Seismic Interpretation Toolbar .....................................................................................21
Restrict Mode .............................................................................................................23
Autotracking - Quality Control Grids .............................................................................24
Seismic Interpretation Process Settings ........................................................................25
Polygon Tracking ........................................................................................................25
Polygon Selection .......................................................................................................26
Manual Interpretation on Time Slices ...........................................................................26
Fault Intersection Cuts ................................................................................................26
Interpretation Filtering ................................................................................................27
Fault Autotracking ......................................................................................................27
Window Auto Focus ....................................................................................................29
Linked Interpretation Windows ....................................................................................29
Crossing Intersection Filters ........................................................................................29
Select Orthogonal Intersection .....................................................................................30
Vintages .............................................................................................................. 31
Seismic Flattening .............................................................................................. 32
Schlumberger Public
Message Log ....................................................................................................... 18
Miscellaneous ..................................................................................................... 35
2D Survey Geometries ................................................................................................35
External Seismic Files..................................................................................................36
Limiting File-Writing Locations .....................................................................................37
2D External Files ........................................................................................................39
Intersection Plane Step via Mouse Scroll Wheel .............................................................39
Volume Attributes ............................................................................................... 39
AVO Attributes ...........................................................................................................39
Nested Virtual Attributes .............................................................................................40
Volume Attribute Computation by Folder and Vintage ....................................................40
Realized Volume Attribute File Locations .......................................................................41
Seismic Well Tie .................................................................................................. 41
Additional Tracks ........................................................................................................41
Computation of Aki-Richards Angle Dependent Reflectivity .............................................42
Taper Extraction Windows ...........................................................................................42
Geology ..................................................................................... 44
Well Section Window .......................................................................................... 44
Well Section Window Display Template ........................................................................44
Display Template Usability...........................................................................................49
Ghost and Marker Drop Functionality............................................................................52
Well Section Window Fence .........................................................................................53
Well Section Window Display Manipulation....................................................................53
Data Displays and Flexibility ........................................................................................54
Shortcut Keys .............................................................................................................56
Well Data Performance ....................................................................................... 58
Well Zoom and Highlight: 2D and 3D Windows .................................................. 59
Well Projection on Intersections ........................................................................ 61
Multiple/Missing Projections .........................................................................................61
Incomplete Projections................................................................................................63
User Interface ............................................................................................................63
Project Upgrade .........................................................................................................66
Local Model Update for Structure ....................................................................... 66
How to Perform a Local Model Update of the Structure ..................................................67
Define Fluid Contacts .......................................................................................... 70
Schlumberger Public
Seismic Wavelet ASCII Export/Import...........................................................................42
How to Define Fluid Contacts Using Regions .................................................................70

Store and Populate Fluid Contacts ...................................................................... 72
How to Populate Fluid Contacts in an Updated Grid .......................................................72
Convert Contacts to Surfaces and Points ............................................................ 74
Automatic Polygon Generation around Targets .................................................. 74
Polygon Attribute Calculator............................................................................... 76
Polygon Display .................................................................................................. 76
Polygon Editing ................................................................................................... 78
Well Picking for Well Section .............................................................................. 78
Filtering of Templates in Calculators .................................................................. 78
Workflow Editor Commands ............................................................................... 80
Define 3D Properties and Well Influence Radius in Volume Calculation ............................80
Well Top Attribute Recalculations .................................................................................81
Well Repositioning ......................................................................................................82
Get and Set Well Attribute Values ................................................................................84
Inclination and Azimuth on Well Log .................................................................. 86
Handling of Empty Well Logs .............................................................................. 87
DLIS Loader ........................................................................................................ 87
2D Volumetrics ................................................................................................... 88
Function Viewport Display .................................................................................. 89
Time Stratigraphy Template ............................................................................... 90
Handling of Zero Line .......................................................................................... 91
Juxtaposition Report for Discrete Properties ...................................................... 93
Modeling .................................................................................... 94
Local Model Update............................................................................................. 94
Petrophysical Modeling Distribution Tab ............................................................ 95
Data Analysis for Continuous Properties ............................................................ 96
Data Analysis for Discrete Properties ................................................................. 97
Object Modeling Output Properties .................................................................... 99
Variable Azimuth Property Definition for Geometric Bodies and Fluvial Channels
.......................................................................................................................... 101
Honoring Priority Settings for Object Modeling ................................................ 101
Servo-System for Sequential Indicator Simulation ........................................... 103
Volumetrics Calculation and Reporting Per Contact Regions ........................... 104
Schlumberger Public
Make Log Process ............................................................................................... 84
Usability ............................................................................................................ 105
Structural Framework ............................................................. 106

Structural Gridding ........................................................................................... 106
Setup Tab ................................................................................................................ 107
Geometry Tab .......................................................................................................... 108
Faults Tab................................................................................................................ 109
Structural Gridding Workflows ......................................................................... 110
Zone Control ............................................................................................................ 110
Reservoir Intervals ................................................................................................... 111
Layer Guides ............................................................................................................ 112
Combining Regions ................................................................................................... 113
Assessing Zone Cell Number ...................................................................................... 114
Structural Framework Fault Properties ............................................................ 115
Dip and Dip Direction ................................................................................................ 115
Seismic Extraction onto Faults ................................................................................... 115
2D Fault Plane Maps ................................................................................................. 116
Productivity and Usability ................................................................................. 116
Fault Patch Removal Tool .......................................................................................... 116
Intersection Colorfill.................................................................................................. 118
Streamlined Input Data Handling During MWI ............................................................. 118
Context-Sensitive Menu Update ................................................................................. 119
Display Single Fault Input Data .................................................................................. 120
Recalculate Changed Faults ....................................................................................... 120
Delete Fault or Horizon ............................................................................................. 121
Context Menu Process Synchronization ....................................................................... 122
Reservoir Engineering ............................................................. 123

Import and Export Formats: Advance Notice for 2012.1 .................................. 123
INTERSECT Environment .................................................................................. 124
Define Simulation Case ............................................................................................. 124
Make Local Grids ...................................................................................................... 125
Make Development Strategies.................................................................................... 126
Initialization of Simulations.............................................................................. 126
Define Simulation Case: Initialization by Enumeration for Thermal and Compositional .... 126
Make Fluids: Mixed Hydrostatic Equilibration Option for Thermal .................................. 126
Schlumberger Public
Zonal Juxtapositions ................................................................................................. 116
Fine Scale Equilibration ............................................................................................. 127

Conversion of ECLIPSE Data Input Files ........................................................... 127
RUNSPEC Section Export ........................................................................................... 127
Case Conversion Key Points: Best Practices................................................................. 128
How to Perform a Case Conversion and Quality Check ................................................. 129
User Defined Rules in Development Strategies ................................................ 132
How to Create a User Defined Rule ............................................................................ 132
How to Add a User Defined Rule to the Development Strategy ..................................... 135
How to Share User Defined Rules between Projects ..................................................... 135
How to Convert a Schedule Keyword Rule into a User Defined Rule .............................. 135
Examples of User Defined Rules Containing Multiple Keywords ..................................... 136
History Matching Tools ..................................................................................... 138
Grid Property Modification Process ............................................................................. 138
Using the Grid Property Modification Process .............................................................. 140
Uncertainty and Optimization Dialog........................................................................... 145
Simulation vs. Observed Data Plot ............................................................................. 157
Visualization of End Point Scaled Saturation Curves: End Point Scaling Probe. 159
EPS Settings ............................................................................................................ 160
Visualization and Quality Control of Vertical Flow Performance Tables ........... 161
Display and Quality Check Option Panel...................................................................... 162
Plot Panel ................................................................................................................ 165
VFP Table ................................................................................................................ 165
Simulation Results Analysis .............................................................................. 165
Line-Plotting Workflows............................................................................................. 165
Standard Summary Plotting Workflows ....................................................................... 166
Example Plotting Workflow ........................................................................................ 166
Drop-in Enabled Workflows ....................................................................................... 167
Autogenerated Workflows ......................................................................................... 168
Dual Porosity Simulation Results View ........................................................................ 169
Visualize Production and Injection Allocation Data from Streamlines ............................. 171
Solution Probe.......................................................................................................... 171
Summary Data in the Histogram Window ................................................................... 172
Well Section Window Enhancements .......................................................................... 173
Miscellaneous ........................................................................................................... 175
Schlumberger Public
History Match Objective Function ............................................................................... 147
Aquifers ............................................................................................................ 176

Thermal Fluids, K-Values .................................................................................. 176
Gridding Enhancements .................................................................................... 177
Upscaling Algorithms ................................................................................................ 177
Global Coarsening Utility ........................................................................................... 178
Well Engineering ............................................................................................... 180
Completions ............................................................................................................. 180
Well Placement ........................................................................................................ 183
Simulation Data File Management .................................................................... 188
Relinking the Simulation Folder .................................................................................. 188
Relink to the Simulation Data Folder for Unmanaged Cases .......................................... 188
Simulation Case Export ..................................................................................... 189
Disk Space Usage and Export Time Reduction ............................................................. 189
Precision of Values in Exported Keywords ................................................................... 192
Mixed-Vendor Workflows ........................................................................................... 192
Summary File Format ................................................................................................ 195
Requesting Summary Data ........................................................................................ 195
Conversion-Related Work Steps in Petrel .................................................................... 195
Plotting Plots and Graphs .......................................................................................... 196
Studio ...................................................................................... 198

Studio Annotate ................................................................................................ 198
How to Use Studio Annotate ...................................................................................... 199
Studio Find ........................................................................................................ 201
How to Configure Studio Find .................................................................................... 202
How to Use Studio Find ............................................................................................. 203
Data Environment Manager .............................................................................. 205
Studio Knowledge Database ............................................................................. 208
Additional Data Coverage .......................................................................................... 208
Performance and Scalability....................................................................................... 209
Data Collaboration (Multi-User Workflows) .................................................................. 210
Data Lifecycle Management ....................................................................................... 211
Data Management and Consolidation ......................................................................... 211
Security ................................................................................................................... 213
Licensing ................................................................................................................. 214
Schlumberger Public
Simulation Summary Results Loading .............................................................. 195
Structural and Fault Analysis ................................................... 215

Structural Framework Fault Tools .................................................................... 215
Dip and Dip Direction ................................................................................................ 215
Zonal Juxtapositions ................................................................................................. 216
Stairstep Fault Tools ......................................................................................... 217
Constant Transmissibility Multipliers ........................................................................... 217
Grid Property Extraction ............................................................................................ 217
Juxtaposition Mapping .............................................................................................. 218
Juxtaposition Windows .............................................................................................. 218
Pillar Faults Tools.............................................................................................. 219
Throw and Displacement Profiles ............................................................................... 219
Throw and Displacement Gradients ............................................................................ 219
Throw Consistency ................................................................................................... 220
Dip and Throw Calculations using Average Interval Velocities for TWT Data .................. 220
Cross-Fault Thickness Change ................................................................................... 220
Distance to Failure .................................................................................................... 221
Hydrocarbon Column Height Prediction Enhancement .................................................. 221
Fault Permeability Predictor ....................................................................................... 222
Fault Thickness Predictor .......................................................................................... 222
Potential Flow Indicators and TM Calculations ............................................................. 222
General Fault Tools ........................................................................................... 223
Fault Properties to Points .......................................................................................... 223
Juxtaposition Mapping .............................................................................................. 224
Fault Property Calculations ........................................................................................ 224
Juxtaposition Windows .............................................................................................. 225
Fault Property Import and Export ............................................................................... 225
Fault Property Identifier ............................................................................................ 226
Fault Tool Usability ................................................................................................... 226
Fault Surface Model Analysis ............................................................................ 227
Schlumberger Public
Throw and Displacement Cumulative Frequency Profiles .............................................. 219
Seismic Horizon Interpretation, Point, and Surface Data ................................. 227

Quick-Look Surface ................................................................................................... 227
Edge Detection......................................................................................................... 228
Automatic Boundary Polygon ..................................................................................... 228
Anomaly Identification .............................................................................................. 228
Influential Data ........................................................................................................ 229
Clipping Surfaces ...................................................................................................... 229
Grid Geometry Calculations .............................................................................. 229
Edge Detection......................................................................................................... 229
Curvature ................................................................................................................ 229
Seismic Horizon Ghosting ................................................................................. 230
Surface Truncation Modeling ............................................................................ 230
Point Attribute Filter ......................................................................................... 230
Operations in the Workflow Manager ............................................................... 231
Function Modifier Operation ............................................................................. 231
Structural and Fault Analysis Process ............................................................... 232
Usability .................................................................................................................. 232
Full Incorporation of Uncertainty in Workflows ............................................................ 233
Fault Seal Scenario Creator .............................................................................. 233
Petroleum Systems Quick Look ............................................... 235

Reservoir Properties: Porosity Property ........................................................... 235
Top Seal Properties: Top Seal Capillary Entry Pressure .................................... 235
Top Seal Properties: Density Property .............................................................. 236
Top Seal Properties: Hydrocarbon Column Height Property ............................. 236
User-Defined Lithologies .................................................................................. 237
Workflow Editor ................................................................................................ 237
Hydrocarbon Generation: Open or Closed System ............................................ 237
Pepper Generation to Expulsion Look-up Tables .............................................. 237
Net-to-Gross Ratio ............................................................................................ 238
Water Saturation .............................................................................................. 238
PVT Calculation for Injection Polygons and Points ........................................... 238
Final Accumulation Closure Polygons ............................................................... 238
Accumulation Information ................................................................................ 239
Map Output ....................................................................................................... 239
10
Schlumberger Public
Fault Modifier Process ...................................................................................... 231
Reset Button ..................................................................................................... 239

Potential Spill.................................................................................................... 239
Direction on Flow Paths .................................................................................... 239
Geological Time in PSQL ................................................................................... 239
Ocean Plug-in Manager ........................................................... 240

Release Distribution ......................................................................................... 240
Plug-ins Section ................................................................................................ 240
Store Section .................................................................................................... 242
Corporate Section ............................................................................................. 243
Security Section ................................................................................................ 244
System Requirements.............................................................. 246

Studio Knowledge Database Server Requirements........................................... 247
Schlumberger Public
11
Welcome to Petrel 2011

The Petrel* E&P platform is about disciplines working together in a collaborative environment
with access to the best science, either from within the application or through plug-ins created
on the Ocean* software development framework. The flexibility of the Petrel software increases
you and your teams productivity and enables you to take and deliver more confident decisions
about your prospect.
In the Petrel 2011 release we put specific focus on productivity. This is reflected in new
functionality, such as a new geophysical tool bar; scalable management of seismic, well, and
simulation data; and interactive, in-context searches using Studio Find.
Let us introduce you to some of the new workflows and functionality.
Disciplines Working Together
Flexible Well Section Window Petrel

softwares 3D window strengththe ability to
view and interact with all types of datahas
been extended to the 2D well section window,
to support well correlation and cross section
workflows. Standard 2D well data can be
displayed together with seismic fences, grid
model objects, and dynamic information, using
customizable templates which can be shared
across the organization.
The well section window shows well log data against

a backdrop of seismic data and a porosity model.
Stair-Stepped Grid Option Petrel 2010

software introduced Modeling While
Interpreting (MWI). MWI enabled you to
validate the seismic interpretation while
building the structural model, which resulted in
a robust and sealed structural framework. With
the new structural gridding option in 2011, the
most complex faulted fields can be correctly
modeled. The stair-stepped grid handles all
fault types in a way that is optimal for property
population and fluid flow simulation.
12
Structural framework building starts from the first

interpretation step, generating a robust and sealed
framework.
Depending on complexity, you can chose the most

appropriate type of grid; pillar, partial stair-step, or
stair-step.
Schlumberger Public
Three improvements address general

collaboration:
Faster history matching though manipulation of all facets of the model, from seismic to
simulation You can now work directly on problem areas and run new scenarios to better
match production history data by utilizing uncertainty tools (to evaluate and understand
parameter sensitivity), local model updates, and definition and analysis of history matching
objective functions.
Access to the Best Science

Using the latest advances in modeling, every task returns a more accurate picture of your data:
local model updates that you need. New workflows

include structural model updates around wells and
extended options for the selection of the cells
requiring property updates, particularly useful with
new horizontal wells. In this way it is possible to
preserve the history match performed on existing
wells, when new data is introduced to update the
model.
Greater Spatial Accuracy With Petrel 2011

software, you will experience a step change in
accuracy. A new, patent-pending method is used to
position and visualize the data accurately when
moving or merging data. This means that a well will
be accurately positioned and correctly visualized in
a 3D seismic volume, and well data can be correctly
mapped to seismic eventsno more distortions.
Property Modeling Advances Advances have been

made to the way Petrel software honors target
fractions for multi-point facies simulation and
indicator simulation. A servo system tracks the
sequential simulation, to ensure that the modeled
facies fractions do not differ too much from the
target values, and takes corrective action if
divergence occurs. In situations where it is difficult
to honor object geometry, you can now chose
which parameter to relax to best match
expectations.
The Power of INTERSECT* - The reservoir
engineering environment in Petrel 2011 software

supports the next generation reservoir simulator
INTERSECT. INTERSECT is designed to handle
large and complex fields, using excellent
performance and scalability on multiprocessor and
multi-core hardware and novel numerical
techniques for non-uniform and unstructured data.
13
This example shows the impact of

converting seismic and point data, for
example well target (shown in yellow)
in standard systems (right image) with
an error of 30-50 meters and Petrel
2011 (left image).
INTERSECT provides better flow

prediction because it allows better
representation of geological details
increased details with local refinements
and unstructured gridsand fluid flows.
Schlumberger Public
As-Needed Local Model Updates Perform only the
Increased Workflow Productivity

Petrel 2011.1 software enriches individual, domain-specific workflows in several ways:
Enhanced Geophysicists Tool Box New and

improved interpretation and usability tools give
you increased speed and accuracy. The new
tools include restrict mode for fault and horizons,
3D seismic flattening, new automatic fault
picker, and a new tracking method (polygon
tracker) specifically designed for detailed
interpretation.
Streamlined Daily Tasks To help you get your
Interactive, In Context, Data Search Results

Google reinvented the way we search, find, and
use information. With the new Studio Find
functionality, Petrel software offers a similar
refreshing and efficient way to search seamlessly
across Petrel projects and reference projects as
well as the Studio Knowledge Database, with
information extracted in context and displayed
on web map services integrated into the native
Petrel 2D and 3D canvases. The Studio Find
interface offers a combination of filters, such as
polygons, name strings, geographic location,
colors, data type, and dates to quickly identify
data of interest and transfer data into the
current project.
14
Similar to a Google engine, the Find tool lets you

interactively search, find, and transfer data
results to your Petrel project.
The annotation tool is used to notify the team of

an analogy to the geological feature that has
been incorporated into this model.
Schlumberger Public
day-to-day interpretation done more efficiently,

we performed a number of usability studies to
understand mouse movements, interactions, and
navigation. This resulted in a concerted effort to
implement many large and small usability
improvements, such as tabbed windows, tear
menus, and a Studio Favorites panel in which to
collect your frequently used objects and
processes.
The Studio Favorites panel lets you collect

short-cuts, such as objects and processes.
Scalable Management of Large Numbers of

Wells Optimization of the Petrel Core permits
handling of a much larger number of wells
within the project. Studio lets you appraise
100,000s of wells across multiple projects and
bring wells into the working project as needed.
Together these developments make Petrel
software capable of handling large regional
scale well data sets, making it the perfect choice
for well interpretation workflows.
Collaboration of Knowledge and Data With the
This example shows two local model updates.

Before (left) there is no match between model
and the new markers and facies log. After
(right) the model matches the new well data.
Schlumberger Public
new Studio Annotate tool, you can share

important unstructured information about your
work and save it for future reference. You can
attach images, URLs, or simple text notes to
projects and objects. You can exchange ideas,
point out problems, highlight features, or add
any other specific information about the study
area for current or future team members.
Enhanced ECLIPSE* Data Input File Integration

The Petrel 2011 software provides enhanced
capabilities for reading and converting existing
ECLIPSE data input files into Petrel projects,
thereby enabling the full suite of Petrel
workflows and reservoir model updates.
Rapid Simulation Results Analysis To help you

get your daily analysis of simulations done more
efficiently, Petrel 2011 software offers one-click
access to standard plots and one-click update of
these plots to new wells of cases, providing
rapid screening and comparison of your results.
It also uses a new faster-loading summary
format.
15
Local model update preserves field history

matching and performs model updates only
where needed.
General Functionality
This section describes new functionality that affects multiple domains.
Studio Favorites
A new, customizable Favorites pane allows you to build a shortcut list to frequently used
objects. Any Petrel item can be inserted into the Favorites panedata, processes, or windows.
To insert an item, simply drag and drop it into the Favorites pane.
Items in the Favorites pane operate just as they would from their home pane, so they can be
organized into folders and rearranged to any logically desired hierarchy. More than one shortcut
can exist for any one item.
Schlumberger Public
16
Arrangement of Windows
Windows can now be structured into groups and tabs. This allows you to quickly navigate
between windows and also to organize your work area by related topics. All windows are now
mutually non-overlapping, and tiles can be re-sized by dragging splitter bars. There is also a
new option to tile all selected windows automatically. When you resize the Petrel application, all
windows are now automatically resized at the same time.
Schlumberger Public
17
Message Log
The Message log is now dockable and part of the windows arrangement. It is docked by
default, but it can be set as a floating pane, as in previous Petrel software versions.
Schlumberger Public
18
Window Auto Focus

A new Window auto focus option allows you to activate displayed windows by hovering the
mouse over them. A small delay prevents unintended activation. This option is available from the
Tools menu system settings, under the Effects tab.
Schlumberger Public
19
Clean Project History

The project history can now be easily cleaned, to preserve user anonymity. This option is available
from the Project menu settings under the Misc settings 1 tab. Once you run the Clean project
history option, all history of all objects in the project are deleted permanently.
Schlumberger Public
20
Geophysics
This section describes new functionality for Petrel 2011.1 geophysics.
Interpretation
There are many usability improvements to seismic interpretation tools, including new ways to
select, track, process, and filter.
Seismic Interpretation Toolbar

To provide access to commonly used tools, the Seismic Interpretation toolbar has been
developed for the 3D, 2D, and interpretation windows. This toolbar is turned on and off via the
View menu in the main Petrel toolbar.
Active seismic object - Lists the active seismic object.
Color scale Displays the color table of the active section and allows the user to
compress, rotate, or alter opacity (via RMB).
Flip color table Flips the color bar.
Reset color table Resets changes made to the color bar.
Active property template Shows the property template of the active section and allows
you to change property templates.
Toggle opacity on all visible seismic planes Toggles opacity in 3D and 2D windows.
Active fault/horizon interpretation Lists in a dropdown menu the content of the

current active interpretation folder. Selecting a horizon or fault makes it active.
Toggle wiggle and bitmap Toggles between VI/VA/VAVI displays in the interpretation
window.
Create new fault/horizon Adds this option to the current active interpretation folder.
Toggle on/off all interpretation objects Hides or displays all seismic horizons, faults,
and surfaces.
Selected vintage Lists the vintages available for the current intersection. A new vintage
can be selected.
21
Schlumberger Public
The Seismic Interpretation toolbar provides access to common actions and tools, reducing the
time spent searching for data in the Input pane and navigating to the settings dialogues. The
toolbar can be customized to display your desired subset of tools, from among these choices:
Apply selected vintage to visible seismic planes Applies the selected vintage to all
visible intersections.
Reset visible seismic planes to original vintage Resets the vintage of visible
intersections to the vintage belonging to the displayed intersection.
You can control the specific tools that are displayed, and their order, by selecting the
Customize icon
. This opens the Customize seismic interpretation toolbar dialog box:
Schlumberger Public
22
Restrict Mode
It is often advisable, while interpreting in the 3D window, to show only horizons and faults
where they intersect displayed seismic sections. This is enabled in the Seismic horizon
settings under the Style tab by selecting the Restrict mode checkbox.
While in the Seismic Interpretation process, the Restrict Active icon
and the Restrict All
To avoid confusion, if an object is displayed in either the 3D or 2D window and the Restrict
mode option is checked, the phrase Restrict mode is displayed in the upper right corner of
the window. The following images show fault data displayed in normal and restricted mode.
While in restrict mode, select and delete operations will only apply to restricted data.
Fault data shown in Conventional Mode (left) and Restricted Mode (right).
23
Schlumberger Public
icon
can be used to restrict just the active horizon or fault or restrict all horizons and
faults. You can also use shortcut keys R or SHIFT and R, respectively.
Autotracking - Quality Control Grids

During 3D autotracking, three additional output grids are created: Confidence, Amplitude, and
Distance. These attributes can be used to control quality on the tracked results and are typically
used in conjunction with the Filtering dialog.
Confidence Represents the overall confidence number used in the autotracking

algorithm. This will be heavily biased by the seismic amplitude, the wavelet tracker
being switched on, and the correlation quality.
Amplitude Shows the seismic amplitude for the tracked samples.
Distance Shows the relative distance from the original seed point.
Schlumberger Public
Quality control attributes displayed from an autotracked seismic horizon.
24
Seismic Interpretation Process Settings

To allow more control of display options, several additions were added to the process settings
for seismic interpretation.
Active horizon color When selected, overrides the color of the active horizon when
viewed in the interpretation window or when in restrict mode in a 3D window.
Active fault color When selected, overrides the color of the active fault when viewed
in the interpretation window or when in restrict mode in a 3D window.
Horizon rubberband Controls display style for the rubberband used during guided
autotracking and manual interpretation.
Fault rubberband When selected, improves performance in the 3D window,

especially when interpreting faults on seismic horizons.
Selection color Allows you to correct for conflicts between the default color and the
color table used to display the active seismic horizon. It is used during horizon editing,
for example with parent and child point identification.
Polygon Tracking
3D autotracking can be limited to a user-defined polygon by selecting the Polygon Tracking
icon
. A polygon can then be drawn in the 3D or 2D window, and data will only be tracked
within the polygon extent.
25
Schlumberger Public
Polygon Selection
Data selection can be limited by polygon using the Polygon Selection icon
Seismic Interpretation toolbar.
found on the
Manual Interpretation on Time Slices

Interpretation on time slices in the 3D and 2D window is supported for 3D autotracking and
manual interpretation.
Fault Intersection Cuts

In the interpretation window, fault intersection cuts are displayed (as a cross) to indicate where
a fault stick intersects a seismic intersection, as shown in the following image. Right-click the
intersection cut to activate the fault.
Schlumberger Public
26
Interpretation Filtering
The new Filtering tab in the Settings dialog for Seismic Horizons allows you to interactively
filter a horizon based on opacity controls. The tab displays the histogram of user-selected
attributes chosen from those available for the horizon. Using the left and right mouse buttons,
areas of the histogram can be interactively filtered from the display.
To apply this filter and permanently blank the associated bins in all the attribute grids
associated with this horizon, press the Run filter button.
To apply the changes and output the results to a new seismic horizon, toggle on the
Apply to New icon
A typical case for applying such a filter would be for data based on the 3D autotracker. An
example of use with the Distance attribute is shown in the following image.
Schlumberger Public
Fault Autotracking
Fault autotracking enables rapid interpretation of fault sticks based on seed sticks and userdefined tracking criteria. It can be performed by selecting track in the Autotracking tab or by
right-clicking a fault and selecting Track faults. A seismic volume must be active to apply fault
autotracking. Two tracking methods exist:
Voxel correlation Based on the minimum cross correlation value across the fault.
This method is used for tracking on seismic volumes showing continuity on either side of
the fault pane, for example on conventional seismic volumes.
27
Maximum value Based on the maximum average value on the fault plane. This
method is used for seismic volumes which highlight faulting, such as Variance or Ant
volumes.
If you select the Choose method automatically checkbox, then either the Voxel correlation
method or the Maximum value method will be chosen, based on the template of the active
seismic cube.
Schlumberger Public
An initial fault direction is determined based on the seed points used, which defaults to all
interpreted segments. If you have interpreted fault sticks on a combination of inlines,
crosslines, and time slices, the tracker may not be able to compute the initial fault direction and
no tracking will be performed. In such cases the selection paint brush can be used to
interactively select the seeds to be used in the tracking process, for example those on inlines.
After tracking, an attribute is stored with the fault to highlight the points used as seed points
and the points computed by the tracker.
Undo will only remove the last fault segment tracked. To remove a large number of fault
segments, you should highlight them using the selection paintbrush and then delete them.
Fault autotracking can be used in conjunction with Fault framework modeling.
28
Window Auto Focus

In the System settings dialog under the Effects tab, you can now activate window auto
focus. This allows you to change the active window by hovering the mouse pointer over the
preferred window. This is an effective setup, for example, if you are interpreting in the
interpretation window while doing quality control in the 3D window. The adjustable hovering
delay parameter for window auto focus is stated in milliseconds and reflects the time the mouse
must be stationary to trigger the window activation.
Linked Interpretation Windows

The coordinate group of several interpretation windows can be linked using the Camera
Linking icon
. When windows are linked, they will zoom and scroll together. The process
must be activated in both linked windows.
Crossing Intersection Filters
29
Schlumberger Public
You can now control the crossing intersections that are displayed at the top of the
interpretation window by filtering them based on vintages or surveys. This simplifies data
selection.
The New Window Interpretation icon

has been added to the Window Tools toolbar to
provide easy access to the Settings dialogue where this is controlled.
In addition, when selecting a crossing seismic line, the new line is positioned to maintain the
same horizontal intersection point with the previous line. In Petrel 2010 software, the
intersection point was centered in the window. The following image shows the result of setting
filters for displayed intersections.
Select Orthogonal Intersection

In the interpretation window you can select an intersection that is orthogonal to the currently
displayed inline, xline, or random line.
For random lines, clicking and dragging the mouse horizontally causes the random line to
rotate. This can be particularly useful when interpreting faults or salt bodies.
NOTE: For smooth rotation of the random line, it is best to pre-fetch the seismic
data to the seismic cache.
30
Schlumberger Public
Crossing line intersections filtered to show only those from the chosen survey.
Vintages
Vintages of seismic lines and volumes are data-sharing the same line and survey geometry, but
they contain different trace data. They may be created during loading or from generation of
Volume attributes.
Selecting a seismic intersection highlights the vintage it belongs to in the Input pane. The
Seismic Interpretation toolbar will also show this same vintage. In addition, the Input pane and
toolbar will show which other vintages are available for this intersection and allow them to be
selected.
In the 3D window the selected vintage can be applied to all visible seismic planes using the
Apply Vintage icon
on the Seismic Interpretation toolbar. Reset the intersection to its
original vintage using the Reset Vintage icon
. You can scroll through all available vintage
selections for an intersection using the Previous Vintage

and Next Vintage
or by using the SHIFT and UP or SHIFT and DOWN key combinations.
icons
Interpretation icon
found in the Window Tools toolbar.
During selection of seismic data in the 2D window, the selection of inlines, crosslines, and 2D
lines will follow the active vintage in the Input pane.
When an intersection is displayed and the display vintage is different from the parent of the
intersection (for example, the cube vintage for 3D seismic data), the name of the intersection is
changed to append the vintage being displayed.
A typical usage of vintages and vintage selection is shown in the following image. Here we
displayed two camera-linked 3D windows showing the same 3D intersections. In one window
the vintage has been changed to show a different attribute volume. We can now easily compare
the two volumes; they will zoom and rotate together and, using the manipulate plane to move
the intersection, the intersection in both windows will move.
31
Schlumberger Public
Crossing lines, visible as triangles along the top of the interpretation window, can be filtered by
vintage. Use the Settings dialog for the interpretation window or the New Window
Seismic Flattening
A virtual flattened volume can be created in one of two ways:
Right-click a 3D seismic volume surface and select

the Flatten active seismic volume option. This creates both a virtual flattened
volume and a Flattening surfaces folder. The folder contains the surface used to
flatten and unflatten interpretation objects. Flattening is based on the midpoint of the
surface.
Right-click a 3D seismic volume and select the Insert

flattened volume option. This creates a virtual flattened volume underneath the 3D
volume. As a flattening surface has not yet been specified, you must go to the Settings
dialog of the virtual flattened volume to determine how the volume should be flattened.
A separate tab, available in the Settings dialog for a virtual flattened volume, controls the
flattening of other Petrel objects. The tab content displays the surface the volume is flattened
on as well as the calculated shift surface. A list of objects to be converted in flattened space is
displayed. Other objects can be added to the list.
32
Schlumberger Public
Flattening is accomplished by shifting seismic trace data based on a given surface. This results
in a virtual flattened volume (which can be realized to a ZGY file) and a folder containing a
surface that is used to flatten and unflatten other Petrel objects (seismic horizons and faults,
surfaces, and points).
Schlumberger Public
To flatten the objects, select the Flatten button. This applies the computed shift to the objects,
flattening them. If an object has been flattened, it appears with a different icon in the Data
pane. The flattening dialogue also allows you to add a new horizon or fault directly into the
dialogue. This is required if you want to start interpreting on a flattened volume and you want
the Petrel software to understand that this is being done in the flattened domain.
NOTE: If you realize a virtual flattened volume to a ZGY file, it will not maintain the
Settings tab for flattening. You must keep the virtual volume if you want to
flatten and unflatten data, or do so manually using the relevant operation and the
shift surface computed during the flattening process.
If the surface used to flatten the data has changed, you can re-run the flattening process by
selecting the Re-flatten button. This will unflatten the objects and then re-flatten the data,
based on the changed surface.
33
If you want to change the domain of an object without performing a shift to the data, select the
item in the list and toggle its state using the toggle icon
. A typical use case would be when
working with a point set that has been created from a geobody extracted from flattened seismic
data. In such a case the point set would represent flattened data, but the dialogue would not
understand this. Using the toggle icon allows you to tag the point set as flattened and makes it
possible to unflatten it.
34
Schlumberger Public
(Above) Data in unflattened space. (Below) Seismic and interpretation

objects flattened on the pink horizon.
(Above) A geobody extracted from a flattened volume. (Below) The geobody object
converted back to unflattened space as a point set.
Schlumberger Public
Miscellaneous
2D Survey Geometries
The Settings dialogue for a 2D seismic survey contains a Geometry tab which lists the line
geometries for lines within a survey. Line geometries represent the navigation data, and it is to
the line geometry data that seismic interpretation data is linked.
Bulk seismic data does not need to exist in a project in order for the project to contain 2D
interpretation data. If only 2D interpretation data is selected when moving data via the
Reference Project Tool (RPT), then only the interpretation data and survey line geometries will
35
be copied to the new project. If required, you can generate dummy lines from the Geometry
tab to view the data in the interpretation window. Or you can select the bulk seismic data in
RPT to continue interpreting on the lines.
Schlumberger Public
External Seismic Files

The Seismic tab on the main Petrel System settings dialogue allows you to specify a default
location in which to write external seismic files. If this checkbox is selected, 2D and 3D seismic
files will be written to your specified location when created during the Realize data and
Volume attribute operations. The output file will also have a system generated file name.
This enables you to generate files without having to specify the output location and file name
each time.
You can still override the above settings (if allowed to do so) in the respective dialogues for the
Realize data and Volume attribute generation.
36
To make data management of seismic files easier, some special characters can be included in
the output directory name:
%p Includes the project name.

%s Includes the survey name.
%u Includes the user name.
These characters will be decoded during the generation of the seismic file to include additional
folders in the output path, as shown in the following example.
NOTE: The setting for the file location supports relative paths. This is important if
files are being written to network drives.
Limiting File-Writing Locations

It is possible to limit the options available for where users can write files to. This is done by
editing the Petrel Global configuration file. Typically this is done by the Petrel site administrator.
The following code is an example of the programming modification:
37
Schlumberger Public
On Realizing a 2D line, the data is output to a directory structure that contains the user,
project, and survey name, as shown in the next example.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<Configuration>
<SystemSettings>
<UseSpecifiedZGYFileLocation Value="True"/>
<InsistOnZGYFileLocation Value="7"/>
<ZGYFileLocation Value="D:\NotBackedUp\PETREL"/>
</SystemSettings>
</Configuration>
The setting <InsistOnZGYFileLocation Value="n"/> further limits what you can do.
This setting can only be set by manually editing the configuration file. The n value can be one
of the feature numbers shown in the following list. The number is actually a bitmap and can be
thought of as the sum of the desired options (codes 1, 2, or 4).
1: In Tools->System Settings->Seismic, the toggle is grayed out. If checked, users
can still change the folder but it cannot be set to be empty.
2: In Tools->System Settings->Seismic, it is not possible to change the ZGY folder.

It is still possible to toggle the use of this folder on or off.
3: Both 1 and 2, so neither setting can be changed. Note that this only controls the
default. Each time users actually Realize data, there will be a dialog that allows them to
change the default
4: In the Realize dialogs, if the Use folder check box in system settings is on, it will not
be possible for users to toggle off the output file, nor will it be possible to specify an
empty file name. It will still be possible to go the other way, that is, if the toggle in
system settings is unchecked, then it will be possible to specify an output file when
Realizing data. By itself this is only a minor nuisance, since users can close the dialog,
uncheck the toggle in system settings, and re-open the dialog again.
5: Turns on options 1 and 4. This forces users to Realize data to an external folder.
6: Turns on options 2 and 4.
7: Turns on all the options. Users are forced to Realize data to an external folder. It is
still possible to use a folder different from the default, but this will need to be specified
on every Realize. The default is locked.
With the most restrictive setting selected (7), users cannot generate seismic files inside the
project .ptd folder (files are created as external files), nor can they change the default seismic
directory set in the System setting. They could specify a different external folder, but this would
have to be done on every operation. This has been allowed to enable someone to work if the
disk specified by the site administrator is full.
NOTE: This also applies to both ZGY files and 2d SEGY files. The names in the
configuration file suggest it only impacts ZGY data, but this is incorrect.
38
Schlumberger Public
2D External Files
2D seismic files are written as SEGY files. This makes data management tasks easier and allows
sharing of bulk files between users. You have the option to select Integer 8-bit, Integer16-bit,
or Floating 32-bit output formats.
It is not recommended to use .raw files in Petrel projects (internal Petrel files generated with
Petrel software before 2011.1), since 2D SEGY files provide similar performance and have the
advantage of being stored outside the .ptd folder. This allows sharing of bulk data between
users, reduces the size of the .ptd folder, and greatly improves performance when working with
the Reference Project Tool or Petrel Database.
In Petrel 2011.1 software, 2D .raw files will still function as before, with new data being written
as SEGY files. There is no automatic upgrade of .raw files to SEGY files. This can be done
manually via the Survey Manager or via a Petrel workflow.
Intersection Plane Step via Mouse Scroll Wheel
Volume Attributes
AVO Attributes
The following post stack AVO attributes have been added to the Volume attributes process.
They require you to have access to a Multitrace attributes license feature.
AVO
AVO
AVO
AVO
AVO
AVO
Attributes
Fluid Angle
Fluid Strength
Linear Correlation Coefficient
Polarization Angle
Strength
39
Schlumberger Public
While performing horizon or fault interpretation in the 3D window, the mouse scroll wheel can
be used to step the active intersection plane forwards or backwards based on the current plane
intersection step.
Nested Virtual Attributes

Virtual volume attributes can be nested. In such cases, changing the parameters of one of the
attributes will cause subsequent attributes to be updated. The following image shows an
example of such nesting. In this example the user generated a virtual structural smooth
volume, which was used as input to make a virtual variance volume. Changing the parameters
for the structural smooth volume caused both volumes to be updated.
The Volume attributes dialogue allows you to specify a folder and vintage as input to the
attribute computation. This is particularly useful when you want to compute the attribute on an
entire 2D seismic survey.
40
Schlumberger Public
Volume Attribute Computation by Folder and Vintage
Realized Volume Attribute File Locations

3D and 2D realized attributes will honor the external Seismic file setting dialogue found
under System settings on the Seismic tab. If set, the files will be written to this location and
automatically named. Additionally, 2D data will be stored as SEGY files. This enhances sharing
of 2D seismic data between multiple users.
Seismic Well Tie

Additional Tracks
41
Schlumberger Public
It is now possible to include additional tracks in the Sonic calibration and Wavelet
extraction windows to display additional indexes and interval velocity logs. The following
image shows a TWT time index in addition to a TVD depth index and a velocity track. The
velocity track shows input and output velocities based on changes to the time depth curve and
can be used to quality-check the sonic calibration process and any additional stretching and
squeezing of the time-depth relationship.
Computation of Aki-Richards Angle Dependent Reflectivity

If shear sonic data is available, angle stack synthetics can be created using the Aki-Richards PP
method. Selection of the method and angle is made in the Input tabs.
Taper Extraction Windows
Seismic Wavelet ASCII Export/Import
On ASCII Export
Time of first sample The internal time of first sample is written to the ASCII file in
the WAVELET-TFS field.
Example For a 128ms wavelet sampled at 4ms, the WAVELET-TFS is -64. In previous
versions this defaulted to 0.
On ASCII Import
Time of first sample If the WAVELET-TFS field is found in the wavelet header, it will
be used as the time of the first sample. If it is not found, it will be set so the center of
the wavelet is at 0.
Sample rate If the SAMPLE-RATE field is found in the wavelet header, it will be used
as the wavelet sample rate. If it is not found, it will be computed by
(last time-first time)/(number of samples 1).
Wavelet name If WAVELET-NAME is found in the header, this will be used; if not, a
default wavelet name will be assigned.
Wavelet comments If WAVELET-DESC is found in the header, this will be used. This
can be multi-line.
The following image shows an example wavelet file:
42
Schlumberger Public
To obtain a more stable extracted wavelet, a taper can now be applied to the ends of the
windows used in the extraction process.
Schlumberger Public
43
Geology
This section describes new functionality specific to Petrel 2011.1 geology.
Well Section Window

The strength of a Petrel 3D windowthe ability to view and interact with all types of datahas
been extended to the 2D Well section window to support well correlation and cross section
workflows. Standard 2D well data can be displayed together with seismic fences, grid model
objects, and simulation results, using customizable templates.
Well Section Window Display Template
In the Well section window, the well data tracks and their supported data types continue to
be the main backdrop for several correlation workflows. However, the Petrel 2011.1 release also
includes new functionality to geometrically display seismic, grid properties, simulation
properties, and 3D geometry between the separate well data tracks.
The same display template editor user interface introduced with the Petrel 2010 software has
been expanded to accommodate the new data displays.
44
Schlumberger Public
In the Petrel 2011.1 release, the well section can be built by adding tracks and template objects
from the Input tab by right-clicking the object or by using the Template settings window.
Some of the objects can be added to the template and some to the background. Objects that
can be added to the background include 3D grid geometry and property, seismic, and
simulation properties.
The display template editor has been broken down into three main sections:
Borehole tracks,
Borehole markers,
Background.
Data Tracks
The following table lists the different data tracks and their respective data types that can be
displayed in the Well section window. Global well logs and grid properties can be added to
the display template directly, by turning them on in the Petrel Input tab or Model tab in data
panes. These items can also be added to the display template by right-clicking the item in the
data pane and choosing the option for adding to the template. The grid properties have a
choice for adding them to the data track or to the background. The check box in the data pane
will represent the data tracks population.
Associated Data Type Options
Completion Track
Completion equipment
Index Track
Depth domains
Track
Log curves (discrete and continuous), grid property,

points attribute, seismic log, 2D log, simulation grid
results, bitmap log, simulation log
Tadpole Track
Tadpole
Comment Track
Comment logs
Summation Track
Volume log curves that contain the units, with values in

fractions or %
Polar Frequency Plot Track
Polar frequency plot (rose plot or points display)
45
Schlumberger Public
Data Track
In the Display template editor, each track type shows all data types that can be added to
that track. The following image shows the data object options for Tracks:
Schlumberger Public
Borehole Markers
The Borehole markers section allows you to add well tops, surface group, contacts, and pillar
grid horizons to the Display template editor. Each marker group added to the display
template will be able to have individual style settings.
46
In addition to adding these objects from inside the Template editor, these items can be
added to the display template by checking their object in the Input tab or Models tab in the
data pane.
Schlumberger Public
Background
Objects that can be added to the background include 3D grid geometry and property, seismic,
and simulation properties. A vertical fence is created between each well. The fence is aligned to
either the borehole trajectory wells bottom, middle, or top, or to a specified well top. These
objects can be displayed in their appropriate index of either SSTVD or TWT.
47
Schlumberger Public
48
Display Template Usability
Template Editor
In Petrel 2010s Well section window, in the Display template editor, you had limited
ability to add tracks or data objects to the template. You could only access tracks or data
objects using the Add new Object button in the top left corner of the Template editor. In
Petrel the 2011 release, this has been improved to allow you to right-click any data track to add
more tracks below that one. Also, you can right-click any data track to choose the specific data
objects to add to that track.
The Global well logs can also be selected in the Input tabs data pane, then dragged and
dropped into the open template editors appropriate data track.
49
Schlumberger Public
Additionally, several items can be added directly to the template, and global well logs and grid
properties can be added to the display template directly by turning them on in the Petrel Input
tab or Model tab in data panes. These items can also be added to the display template by
right-clicking the item in the data pane and choosing the option for adding to the template. The
grid properties can either be added to the data track or to the background. The check box in
the data pane will represent the data tracks population.
Schlumberger Public
Choosing Data Candidates for the Template Editor Data Objects

When adding data items to the Template editor, the editor now allows you to type in a filter
for the data template you want to display. In addition, the list of candidates can be amended to
include or not include the data with the chosen templates measurements.
Once the candidates are listed, the list can be used as a preference system for the wells
display. The data at the top of the list is given top priority, while the data at the bottom of the
list is given lowest priority. The data candidates can be moved up and down the list using the
blue arrows keys to the left of the candidate list.
50
Schlumberger Public
51
Ghost and Marker Drop Functionality

The ghost curve functionality has been expanded. Once the ghost curve process has been
enabled, you can now use it as either a single- or multiple-marker drop functionality:
If you choose a single marker, you can immediately drag and drop that marker to a new
well.
If you choose an interval across several markers, the ghost section interval is created and
can be moved over to another well. In multiple-marker mode, once you move the ghost
interval to another well, the well top depths can be adjusted before dropping them into the
new well.
Ghost curves can be created in any index domain, but only one ghost curve can exist at a time.
To choose a ghost interval for horizontal wells, the well must be displayed in MD index or have
split panels enabled.
Schlumberger Public
52
Well Section Window Fence

The well section fence is a vertical intersection between wells. Petrel software automatically
creates a well section fence when you add wells to the Well section window display. The
fences created from the Well section window will be stored in the Input pane in an
automatically created Cross sections folder. The cross sections are named X, with the
corresponding window name in brackets. This cross section can later be selected to display in a
2D, 3D, map, intersection, or interpretation window.
The settings in the cross section have the option for you to align the vertical fence to a wells
top, middle, or bottom, or to a specified well top. You can also choose to have the fence pass
through the bottom of the wells as a second tie point for each fence section. Petrel software will
connect the fence sections to create the shortest possible route though the hinge points.
Well Section Window Display Manipulation

To improve navigation in the Well section window display, new functions were added or
relocated to the Window Tool toolbar.
New features: 1D scale, Equalize scales.

Relocated features: View entire well, View entire wells.
The Window Tool toolbar buttons pictured above are described below:
Percentage Zoom Factor Represents the % of display shown when using magnify
zoom, fit to width, or fit to height modes.
Magnify Zoom Allows you to draw a rubberband box in the well section window
viewport to magnify this section of the display.
53
Schlumberger Public
A well section fence is tied to the wells in the Well section window, so if you change the
order of wells, the fence will respond. The well order displayed, and therefore fence path
displayed, can be updated in the Well section window settings, on the Definition tab.
Fit to Width Adjusts all displayed wells to the width of the well section window
viewport. The well scale in this mode is the true hardcopy scale.
Fit to Height Adjusts the initial full well interval to the height of the well section
window viewport. The well scale in this mode is the true hardcopy scale.
Fit Dynamic Mode Dynamically adjusts all displayed wells horizontally and vertically
in the well section window viewport. The well scale computed is based on a fixed
vertical DPI and is not a true hardcopy scale.
Show Plot Size Area When in true percentage hardcopy display mode (except
Dynamic mode), allows you to visualize the plot area size based on the chosen plot size
input.
1D Scaling When enabled, allows you to select a vertical section of a well. The well
automatically vertically scales to that zone. This lets you quickly visualize the zone of
interest.
Equalize Scales Automatically makes equal all the displayed wells vertical scales. It
uses the average of all vertical scales displayed.
View Entire Well Visualizes the entire interval of the active well. This option was
relocated to this toolbar.
View Entire Wells Visualizes the intervals of all displayed wells. This option was
relocated to this toolbar.
Data Displays and Flexibility
Tadpole Display
The tadpole displays user interface has been updated to improve intuitive data set up. The
tadpole data can now be colored when a discrete attribute dip classification is added to the data
set. The different dip classifications can also have separate tadpole shapes assigned to them.
While tadpole colors are driven by the dip classification discrete property template, both this
color choice and the tadpole shape can be chosen in the tadpole data object display in
Template editor of the Well section window.
Polar Frequency Plot Display

In the Petrel 2011.1 release, the polar frequency plot data object replaced the rose plot data
object. The dip data can now be plotted as a rose plot display or as points. The user interface
has been updated to improve intuitive data set up. The data can now be colored when a
discrete attribute of dip classification is added to the data set.
54
Schlumberger Public
Polar frequency plots can now be added in fixed intervals, or plots can be added between
specified well tops. Plots can now also be viewed above the top-most well top and below the
bottom-most well top.
You also have control over the circumferential and radial grid and labels.
Schlumberger Public
Summation Track
The summation track was expanded to allow more data types to be added. Data with units that
are dimensionless (%, v/v, or pu) can now be added to the summation track. The volumes will
not normalize, but they will be limited to display only cumulative volumes between 1 and 0. The
volume ordering was modeled after ELAN and Techlog.
Once the volumes have been added as summation track candidates, the color fills can
automatically be generated from a button added to the Definition tab.
55
All keyboard shortcut keys were updated for the Well section window. Several new shortcut
keys were added to improve efficiency in workflows. When the Well section window is
active, the following keyboard shortcuts can be used:
A Paint discrete log class. While this mode is active, choose SHIFT and left-click to
toggle flood mode on and off, and use CTRL and left click to toggle pick-up class
mode on and off.
C Create or edit the curve fill. While this mode is active, move the mouse pointer over
the curve fill and press the DELETE key to remove the curve fill.
E Create or edit well tops. While this mode is active, press the DELETE key to delete
the active marker.
F Insert a new fault surface.
G Create a ghost curve.
SHIFT and G Drop tops from a ghost.
H Insert a new horizon.
I Create or edit image control points mode.
56
Schlumberger Public
Shortcut Keys
K Create new comments track.
L Flood discrete log class. While this mode is active, the following key modifiers should
apply: SHIFT and left-click to toggle paint mode on and off, CTRL and left-click to
toggle pick up class mode on and off.
O Insert another new surface.
Q Set equal scales.
R Create or edit comments.
S Set 1D scale.
T Show template settings.
W Show window settings.
Y Flatten on active well top. Right-click the context menu from well top horizon.
SHIFT and Y Toggle synch scrolling OFF.
CTRL and Y Redo well top edit.
Z Activate the Zoom or the Magnify tool.
CTRL and Z Undo well top edit.
Up arrow key Scroll upwards in the active well.
SHIFT and Up arrow key Refine scroll up.
CTRL and Up arrow key Activate horizon above (in well top editing mode).
Down arrow key Scroll downwards in the active well.
SHIFT and Down arrow key Refine scroll down.
CTRL and Down arrow key Activate horizon below (in well top editing mode).
Plus key Stretch well scale (go to smaller value vertical scale).
SHIFT and Plus key Refine stretching of vertical well scale.
Minus key Squeeze well scale (go to larger value vertical scale).
SHIFT and Minus key Refine squeeze of vertical well scale.
Page Down Scroll one page downward in the active well.
Page Up Scroll one page upward in the active well.
Home Scroll to the uppermost part of the well.
End Scroll to the lowermost part of the well.
57
Schlumberger Public
Well Data Performance

In the Petrel 2011.1 release, the performance on wells has been improved for many individual
actions. Projects with many wells and well logs will see significantly faster behavior when
applying certain steps. In general, Petrel will now work faster when opening a project, moving
wells, or copying wells via the Reference Project Tool. But other functionalities, such as the well
log calculator or up-scaling of well logs, have been improved as well. Working with saved
searches will show significant improvements.
For selected processes, the individual improvements can be seen in the following chart. The
numbers are maximum factors compared to Petrel release 2010.2 and can vary for individual
projects.
Performance Improvements for Selected Processes on Wells

(Factor Compared to 2010.2)
1000
Schlumberger Public
100
10
1
The size of the project (number of wells) influences the performance for individual actions.
When moving wells, the improvement increases with increasing number of wells, as illustrated
in the following table.
58
Perfomance Improvements when Moving Wells

(Saved Search Applied)
35
Factor compared to 2010.2
30
25
20
15
10
5
0
50 Wells
100 Wells
200 Wells
500 Wells
1000 Wells
In the presence of many wells, a well can now easily be detected in the 2D and 3D windows
using the new Zoom and highlight option. This function is available from both the Input
pane and the Well Manager.
From the Input pane Activate the well you want to detect, then right-click the well and
select Zoom and highlight. The well blinks for a few seconds in your active window. See
the following images.
From the Well Manager Open the Well manager, and then select the well you want to
detect and click the Highlight icon. The well blinks a few seconds in your active window.
See the following images.
59
Schlumberger Public
Well Zoom and Highlight: 2D and 3D Windows
On this page, how to select well zoom and highlight

from the Input pane.
Schlumberger Public
60
How to select well zoom and highlight from the Well Manager.
In Petrel 2011.1, the display of well data on intersection planes has been significantly improved.
It includes projections on general intersections; on seismic sections and well section fences;
and in 3D, intersection, and interpretation windows.
Multiple/Missing Projections
Before Petrel 2011.1, well trajectories and related data were projected orthogonally, according
to the distance limit specified in the intersection settings. In some cases, wells were projected
several times or were not projected at all. See the following example, where d is the distance
limit. This example shows a map view of three vertical wells projected onto an arbitrary
intersection.
61
Schlumberger Public
Well Projection on Intersections
From now on, it is possible to specify projection direction for each well, if necessary. You can
specify the projection direction either by azimuth value (from North) or by manually adjusting
the direction in the 2D or 3D window. The previous projection method is preserved and is now
called Orthogonal.
Another important change is that new methods (Along azimuth and Manual) will project
wells only once, and on the closest intersection fence in the selected direction. See the
following example of an azimuth-defined projection.
Well 2 is projected along a direction specified by azimuth angle . For Well 3, there is no
intersection fence located closer than the distance limit d along the specified direction. In such
cases, Petrel will search for a suitable intersection fence in the opposite direction, as shown in
62
Schlumberger Public
From Well 1, in the above example, it is not possible to drop a perpendicular to any fence
located closer than d, therefore well 1 was not projected. At the same time Well 2 was
projected twice, since perpendiculars can be dropped to two nearby intersection fences. Only
Well 3 was projected correctly once.
the example. Notice also that even though there are two suitable intersection fences for Well 3,
its projection is shown only once on the closest fence.
Incomplete Projections
Before Petrel 2011.1, the distance limit was applied to each point of the well trace
independently. Sometimes only part or several parts of the trajectory were projected. The
following example shows a map view of a deviated well partially projected on the intersection.
You may still use the previous way of projecting by deactivating the Display entire well trace
option in the intersection settings. Refer to the following "User Interface" section.
User Interface
Most settings and controls for well projection are grouped in the new Well projection tab
under General Intersection settings.
63
Schlumberger Public
This issue was addressed in the Petrel 2011.1 release. A new option now allows you to force
the projection of the entire trajectory, if the distance between the fence and the well is smaller
than the specified distance limit for at least one trajectory point, as illustrated in the next
example.
By default, all wells are projected using the method selected as the default:
Orthogonal Use this check box to specify that an orthogonal projection method be
applied to all wells on the current intersection. An orthogonal projection does not have any
additional user settings.
Along azimuth Use this check box to specify that the projection method for all wells on
the current intersection should be along the azimuth.
Display entire well trace Use this check box to activate the forced projection of the
entire well trace. Refer to the details in the preceding section on Incomplete Projections.
Schlumberger Public
The lower left portion of the General Intersection setting dialog lists only the wells projected
on the intersection. To be projected, a well must be selected on the plane and be closer to the
intersection than the distance limit.
It is possible to specify different settings for a particular well by first selecting it from the well
list and then deactivating the Use default check box. You can then specify the projection
method to be applied to that well only.
64
When using the Along azimuth method, you will need to specify a projection angle, as shown
in the following example.
If you want to set the projection direction manually for a well, select Manual from the
projection type pull-down menu. In your 2D or 3D window, you will then be able to see the
polygon which defines the projection direction for that particular well. Polygons are shown only
for wells visualized in the active window.
65
Schlumberger Public
You may edit direction polygons like any other polygon in Petrel. Remember to activate the
Make Edit Polygons process. It is possible to adjust only one floating point of the polygons.
Another anchor point will always be tied to the well. Notice the direction polygons for wells C1
and C7 in the following image.
You can switch off direction polygons by deactivating the Keep direction polygons visible
check box.
Distance limit in the Input settings tab

All settings shown on the Well projection tab.
Project Upgrade
If a project saved in a previous Petrel version has different distance limits for different windows,
nothing will change when you first open the project. However, the distance limit will be
synchronized after you press the Apply or Ok button in the intersection settings.
Local Model Update for Structure

A new Local model update process allows for local updates to the structure of a 3D grid
model in a specific area. This is noteworthy for cases where new local data is introduced to a
large model (for example with a newly drilled well), when history matching has already been
performed for the rest of the region and you do not want to redo all the previous work.
The process will adjust horizons and layers of the 3D model according to the new structural
data, while still preserving all 3D properties in all cells. For each zone, once the horizons are
adjusted, all the layers are updated automatically and proportionally using the new thickness of
the zone. The user has full control over which horizons need to be updated.
66
Schlumberger Public
There is also an important change in the handling of intersection settings related to the
projection of well data. Before Petrel release 2011.1, intersection planes had independent
settings for each window. Now some settings are synchronized so that it is possible to set up
well projection in 2D and 3D views. For example, manually adjust the projection direction and
apply it to intersection or interpretation windows. The following settings can be synchronized:
The area to update can be defined by a closed polygon or several closed polygons grouped into
one polygon object. Only the cells inside the polygon wall will be updated when the process is
run; all cells outside the polygon will remain unchanged. The most common situation is to draw
a polygon around a newly drilled well or newly interpreted well data. Any of the following input
data can be used solely or in combination to guide the update process: well tops, points,
polygons, surfaces, and horizon interpretations.
To assess the uncertainty of the local structural update, this process can also be included in the
Uncertainty workflows.
How to Perform a Local Model Update of the Structure

The following example demonstrates a typical local model update of the structure.
Scenario: You have built a complete 3D model with the usual 3D properties, and the history
match has been performed on all the current wells for the model. A new well has been
drilled, and you need to update your model according to the new data.
2. In the Regions field, activate the Use polygon(s) checkbox and use the blue arrow to
drop in the closed polygon inside which you want to update the model. In this example,
it would be a closed polygon around the new well. A saved search can also be provided
to use only the tops from filtered wells during the horizons recalculation. See the
following image.
67
Schlumberger Public
1. Open the Local Model Update process to update the structure of the 3D model.
68
Schlumberger Public
3. Select all the horizons you wish to update by selecting Yes in the Calculate column and
inserting your new data (Input or Well tops). More tabs and options will appear on the
window, depending on your specific input data. Set all the modeling parameters for the
region that you wish to update and run the process so that the structure inside the
polygon is updated.
Before update
After update
Before update
After update
performed only on
specified horizons
After update with

proportional adjustment of
intermediate horizons
4. It is also recommended that you update your property model using the Local model
update for properties, in case your new well contains facies or petrophysical information.
69
Schlumberger Public
If no data are available during the update of some intermediate horizons, they will be
automatically adjusted proportionally using the thickness between the other horizons.
Define Fluid Contacts

The Petrel 2011.1 release introduces a new way of defining fluid contacts: by regions. A new
tool helps you create regions using any discrete property, for example by using segments or
zones properties. They can also be modified by being merged or defined by polygons or other
properties. You can find this new option on the new Make Regions Property tab when
activating the Make contacts process. New options are also available in the Make Contacts
tab. This new interactive fluid contacts definition enables you to create custom regions and
define different contact levels for each one. There are no restrictions to the shape, extension, or
number of regions.
How to Define Fluid Contacts Using Regions

The following example demonstrates how to create fluid contacts using regions.
Scenario: You have just finished building your 3D grid, and now you want to define the
different fluid contacts within your 3D grid. Your model is highly compartmentalized, and
fluid contact levels are different within each compartment.
Region based contact
Regions property
2. Since your contact regions are related to the grid segments, first create a Segment
index property using the Geometrical modeling process. Open the Make contacts
process to define your fluid contacts. Under the Make regions property tab, select the
Segments property. You can modify the regions property to reflect the different fluid
70
Schlumberger Public
1. First, create your contact regions property and then define your fluid contacts within
your regions.
contacts existing in your grid, by merging several segments having identical fluid
contacts or by creating new segments using polygons or other relevant properties.
71
Schlumberger Public
3. Under the Make contacts tab, you will now define your fluid contacts within each
contact region. Toggle on the Use region property check box and select your contact
regions property. Complete the fluid contact table for each contact and run the process.
Your fluid contacts are defined as specified for each region.
Store and Populate Fluid Contacts

A second functionality concerning fluid contacts allows you to quickly save and populate
contacts information. This is of great interest when a 3D grid containing many segments is
updated with a new fault and the segments modified accordingly. Using the Make contacts
process, fluid contacts information can be saved into the Input pane. Saved contacts can then
be used to quickly populate any grid using the Make contacts process settings.
For each region or segment of the 3D grid, one contact point is created at the center of the
region or segment. In case the region or segment presents a non-convex geometry, the contact
point will be located arbitrarily within the region or segment. The following attributes are
attached to each contact point: X, Y, Depth, Contact Depth, Region Name, and Region Code.
How to Populate Fluid Contacts in an Updated Grid

The following example demonstrates how to populate fluid contacts in an updated grid using
the Store and Populate functions.
1. Before updating your 3D grid, open the Make contacts process to save your fluid
contact information. Use the Store button to create a point set in the Input pane for
each of your fluid contacts.
NOTE: To create a fluid contact point set, the spreadsheet has to be properly populated.
2. Update your 3D grid according to your new interpretation data. A new segment is
created in your model.
3. To update the fluid contact information in your updated grid, again open the Make
contacts process. For each fluid contact, drop the previously saved fluid contact point
set using the blue arrow button. Then click the Populate button to update your fluid
contacts.
4. Check your fluid contacts. Three results can happen during the Populate step for each
region or segment:
Only one point is found: The contact value for this region or segment will be
correctly set.
No point is found: The contact value will not be modified for this region or
segment.
More than one point is found: The contact value will be set to the first point of
the point spreadsheet located in this region or segment.
72
Schlumberger Public
Scenario: You had previously built a complex 3D model with many segments and populated
it with different fluid contacts for each segment. A new interpretation has been made, and
you incorporated a new fault in your model. You also want to update the fluid contacts.
Schlumberger Public
73
Convert Contacts to Surfaces and Points

It is now possible to convert fluid contacts to surfaces and points. If you right-click a specific
fluid contact defined within your 3D grid, a contextual menu offers to convert your contact to
points or surfaces. Those surfaces and points are created in the Input pane. Different options
are available to create surfaces and points by segments.
Schlumberger Public
Automatic Polygon Generation around Targets

This new functionality enables you to create polygons with multiple pre-defined shapes (circles
and rectangles) around several objects. This option is available through the new Shapes tab of
the Make/edit polygons process. Wells, well tops, and points can be used as input data. A
closed polygon is generated around each data object. All the created polygons are then merged
into a single set, which is the final output. You have full control over the geometrical
parameters of the polygons through their shape, the number of points per polygon generated,
and other size parameters depending on their depth value and shape (radius for a circle or
width, thickness, and rotation for a rectangle). This functionality is also available in the Process
Manager.
74
75
Schlumberger Public
In the following illustration, polygons were created around wells using a circular shape with 16
points and a radius dependant on a continuous well attribute surface (it could also be any
discrete attribute or surface).
Polygon Attribute Calculator

The Calculator for the Polygon attribute is now enabled. It supports geometrical functions such
as area and length. To enable access to this calculator, you must first create a new polygon
attribute. After that the calculator will be available by right-clicking Attributes.
Schlumberger Public
Polygon Display
Color and pattern filling as well as labeling are now available for polygons in 2D and 3D
windows, similar to what is available in the Map window. This display enhancement is
particularly useful in exploration studies when you want to select and identify quickly and
efficiently the data for interpretation. This also facilitates working in a multi-windows
environment. Also, when clicking inside a filled polygon, the polygon information will be
displayed in the status bar. Imported or created attributes can be used for filling polygons with
colors and patterns.
76
77
Schlumberger Public
Continuous, discrete, and Boolean attributes can be used for directly defining fill colors. All
settings are defined in the Style tab of the Settings dialog for the polygon. You need to select
the As attribute color type and then select the attribute from the list on the right. Discrete
attributes can also define the pattern filling.
Polygon Editing
The polygon editing functionality has been enhanced to allow editing only on the active
polygon. In case many polygons are displayed in a window, this prevents accidentally editing
polygons other than the one activated.
Well Picking for Well Section

While creating a Well section, you can pick on well symbols or well tops in 2D and 3D windows.
This enhancement is particular useful for picking vertical wells displayed in a top view, when in
the presence of many wells.
Schlumberger Public
Filtering of Templates in Calculators

To help you find the correct template when using the Calculator, a template filter has been
introduced for all calculators using templates. When using the Filter templates textbox, the
template list displayed when selecting a new template will be automatically filtered. The
template list will only include templates containing the string of characters you typed in. The
filter is not case sensitive.
78
In the following illustrations, templates have been filtered using the perm string (to find
permeability templates) and the poro string (to find only templates related to porosity).
Schlumberger Public
79
Several new commands and options were added to the Workflow editor:
Define 3D properties and well influence radius in Volume Calculation,
Recalculate the well top attribute,
Reposition wells in any direction,
Get and set well attributes values.
Define 3D Properties and Well Influence Radius in Volume Calculation

The handling of the general variable has been improved in the Workflow manager. Drop
fields are now available in the Volume calculation process, so that new 3D properties can be
created in the calculator, accessed by the Output variable, and renamed and used later. This
enhancement allows workflows to be easily shared between multiple projects, which improves
asset team work and collaboration.
In a workflow, to use a reference variable in the Volume calculation process, first toggle off
the Constant property for the specific property and then toggle on Use variable. A blue
arrow button appears, allowing you to drop any variable into the property field.
80
Schlumberger Public
Workflow Editor Commands
Well top attributes can now be recalculated in a workflow using the Update well tops
attribute operation under Points with well attribute operations. The input parameter is
the well top attribute to update.
In case input well data are modified (well tops, well logs), this operation allows automatic
updating of reservoir maps and models very quickly.
The workflow operation automatically applies all the settings used when the well tops attribute
was previously updated, using the Attribute operations tab of the Settings interface.
81
Schlumberger Public
Well Top Attribute Recalculations
The new workflow Translate well operation (under Well operations) allows repositioning of
a well in any direction. This feature is particularly useful for optimization and well placement
workflows. The input parameters are the well and the X, Y, and Z values used to translate the
well.
In the following example workflow, first a copy of the given well is created and then the copy is
repositioned in the 3D space according to a randomly picked vector.
82
Schlumberger Public
Well Repositioning
Schlumberger Public
83
Get and Set Well Attribute Values

Two new workflow operations are available to get and set well attributes for an individual well
or a group of wells: Get well attribute and Set well attribute under Wells attribute
operations. The input parameters are the well (or group of wells), a well attribute, and an
answer or value. These operations are useful for optimization workflows.
Two enhancements have been introduced in the Make log process. First, deviated wells are
correctly supported as data projection is performed in the TVD domain. An option for working
with only one set of well tops is also provided. These two improvements are useful in scenarios
where you are geosteering a horizontal well to provide real-time information while drilling based
on surrounding wells.
To interpolate log values from other logs, bring up the well settings. Then you will be able to
create such a log under the Make logs tab and the From other logs sub-tab.
84
Schlumberger Public
Make Log Process
Schlumberger Public
85
Inclination and azimuth information is now available in the well logs calculator. They are both
found in the geometrical functions group. Using the calculator, you can create inclination and
azimuth logs.
This information can be especially useful during completion design and log interpretation, to
quickly assess the spatial position and orientation of a given well.
Since this new functionality is present in the calculator, it can easily be integrated into the
Process Manager.
86
Schlumberger Public
Inclination and Azimuth on Well Log
The following improvements have been introduced regarding Global well logs deletion, to
facilitate well data management:
A right-mouse option called Delete empty global well logs in the Global well logs
folder and its sub-folder allows you to delete manually empty logs. Information
regarding global well logs deletion is also recorded in the Message Log pane.
No automatic deletion of empty global well logs is ever performed, especially when
opening a project, importing logs, and when the Delete content option is performed
on the Global well logs folder and its sub-folder.
DLIS Loader
The DLIS loader has been improved two ways: different data frames are now imported
correctly, and the loader does not force log resampling.
87
Schlumberger Public
Handling of Empty Well Logs
2D Volumetrics
The performance of 2D volumetrics and polygon area computation has been significantly
improved by multi-threading the algorithm. The expected speedup should be linearly
proportional to the number of cores. This will make a significant difference for multi-realizations
and map-based volumetric workflows in exploration context. The following two images compare
volumetric calculation times between the Petrel 2010.2 and 2011.1 releases.
Schlumberger Public
In Petrel 2010.2, 2D volumetrics calculation took 28.35 seconds.
88
Function Viewport Display

The background color and transparency of function viewports can now be fully controlled. This
display enhancement is very useful when displaying function viewports on top of a map to
easily see the different plots.
The Function Viewport display can be modified in the Settings tab of the Function viewport,
under the Background section.
89
Schlumberger Public
In Petrel 2011.1, 2D volumetrics calculation took 13.59 seconds.
Time Stratigraphy Template
90
Schlumberger Public
The Time Stratigraphy template (located in the Discrete Property Templates folder) has
been updated to follow the conventions and exact colors of the International Stratigraphic Chart
2009 from the International Commission on Stratigraphy (IUGS). The new template is organized
hierarchically by Eon, Era, Period, Epoch, and Stage levels, and the official age boundaries are
stored within the template codes. In projects created in previous versions, the old Time
Stratigraphy template is preserved as a new Legacy Time Stratigraphy template.
The handling of the zero contour line has been improved in 2D, 3D, and Map windows.
In the following example, the zero contour line of a horizon is displayed in bold on a Map
window, and colored dots show the depth of the horizon.
91
Schlumberger Public
Handling of Zero Line
Schlumberger Public
92
Juxtaposition Report for Discrete Properties

A juxtaposition report between two discrete properties can now be created for analysis purpose
and tracking history. For example, this can be used to analyze and track the creation of contact
regions. This functionality is also available as an operation in the Workflow editor under
Property operations. To run a juxtaposition report, bring up your primary grid property
settings and select Create juxtaposition report under the Property operations of the
Operations tab. You can then select your secondary property and run the process.
Schlumberger Public
93
Modeling
This section describes new functionality affecting modeling.
Local Model Update

The Local model update functionality for facies and petrophysical modeling, introduced in Petrel
2010.1, has been significantly enhanced in Petrel 2011.1. It is now possible to update an
existing model from within a polygon or set of polygons, from within a discrete property region,
and from within a user-defined radius around a well or a group of wells.
94
Schlumberger Public
The different options can be used together or independently. If Use union is selected, all cells
defined in the different options will be updated (as shown in the following figure). If Use
intersection is selected, only the cells that exist in all defined regions simultaneously will be
updated. Refer to the Local Model Update (Facies modeling) and Local Model Update
(Petrophysical modeling) topics of the online help manual for more details.
Petrophysical Modeling Distribution Tab

The Distribution tab for the two Gaussian simulation algorithms has been modified to improve
the logic of the different options:
The Is logarithmic check box, present at the top of the tab in previous versions, has been
removed.
A Lognormal distribution option has been added for modeling logarithmic properties as a
lognormal function. The mean and standard deviation are now specified directly in the
original data space, not in log transformed space. Pressing the Estimate button computes
the mean and standard of the best fit lognormal function from the upscaled data.
The Beta distribution option now uses the mean and standard deviation instead of
alpha and beta to compute the beta function. This change is intended to make it easier for
you to vary slightly the shape and mode of a pre-defined target beta distribution function.
In an uncertainty workflow, variables can be used for the mean and standard. The
Estimate button causes the mean and standard deviation to be computed from the
upscaled data. For more flexibility with the beta function, use the new Beta distribution
transformation from the Data Analysis process.
The General distribution option will now automatically detect if the specified function is
logarithmic and will transform the data to logarithmic domain prior to modeling. The phrase
(Is logarithmic) will be displayed underneath the drop box if the logarithmic X-axis is
toggled on in the settings for the function.
95
Schlumberger Public
On project upgrade from previous versions, Is logarithmic combined with Normal

distribution will be converted to the equivalent lognormal distribution. Refer to the
Distribution Tab subsection in the Sequential Gaussian Simulation (SGS) topic of the online
help manual for more details.
For unconditional modeling (when no upscaled data is present), the default distribution will now
be Normal for most properties and Lognormal for typical logarithmic properties such as
permeability. The minimum and maximum of the output range will be set according to the
current minimum and maximum of the associated template, and the mean and standard will be
estimated so that min = mean 4*std and max = mean + 4*std. These defaults can be edited
manually.
Data Analysis for Continuous Properties

Two new transformations have been added to the Data Analysis process pane for continuous
properties:
General distribution transformation Used to specify the target distribution based on
a user-defined function. The transformation assumes that the upscaled data follows the
given distribution function and builds a transformation table between the function and a
Gaussian (normal) distribution. The transformation brings more flexibility than the general
distribution option in petrophysical modeling, as it gives the ability to stretch or squeeze the
function over a user-defined range and to apply other transformations to the data
beforehand.
Beta distribution transformation Used to specify a beta function as target

distribution. The transformation assumes that the upscaled data follows a beta distribution
function and builds a transformation table between the beta function and a Gaussian
(normal) distribution. The transformation brings more flexibility than the Beta distribution
96
Schlumberger Public
option in petrophysical modeling, as it gives the ability to define the beta function either by
the alpha and beta parameters or by the mean and standard. It also enables you to stretch
or squeeze the function over a user-defined range and to apply other transformations to the
data beforehand.
NOTE: These transformations should always be the last transformations performed

on your data, after truncations of input data or removal of spatial trends. The
Beta distribution and General distribution transformations are alternatives to
the Normal score transformation, and only one of the three can be used at a
time.
Please refer to the Beta Distribution and General Distribution topics of the online help
manual for more details.
Data Analysis for Discrete Properties

The Probability tab in the Data Analysis process allows you to analyze the relationship
between facies and the values of a continuous property, typically a seismic attribute resampled
into the 3D model. Facies probability curves can be edited interactively over the range of values
of the seismic property. These curves can then be used as soft constraints for facies modeling
algorithms.
By default the range of secondary property shown on the X-axis is only taken from the values of
the property within the upscaled cells of the modeled facies property. In previous versions of
Petrel this meant that it was not possible to specify facies probabilities for the full range of
property values (unless it had been fully sampled within the upscaled cells). In Petrel 2011.1 an
97
Schlumberger Public
After the modeling has taken place, the data is back-transformed to the target distribution, and
the final 3D grid distribution will then match the user-defined beta function/general distribution,
provided the specified variogram ranges are not too large.
Extend range button

has been added to the interface. When the button is pressed, the
probability curves (for the facies present in the upscaled cells or for any additional facies) can
be adjusted over the full secondary attribute range. Refer to the Probability tab (Data
analysis) topic of the online help manual for more details.
Schlumberger Public
Facies probability curves based on the values of the re-sampled seismic AI in the upscaled cells (above), or the full secondary
property range with the Extend range function on (below). A third facies (HiQ Sand) not present in the upscaled cells has been
added and assigned high probability for the low AI value range.
98
Object Modeling Output Properties

Additional output properties can be generated from the Other output tab of the Object
modeling method in Facies modeling. These properties are mainly used for filtering, for postprocessing of existing facies models, and as input for advanced trend options in Petrophysical
modeling.
New options are available for the directional trend. You can specify if the property should
be generated only inside the bodies or extrapolated from the bodies to the whole model.
Another new (non-exclusive) option is to choose if the direction should be calculated along
the main axis (as in previous versions) or outwards normal-to-border (in which case
opposite borders of the object will get values at 180 degrees to each other). This is
illustrated in the following two figures.
99
Schlumberger Public
In Petrel 2011.1, these outputs have been significantly enhanced and expanded:
There is a new Distance from object property. This generates a property whose value
represents the distance to the bodys edge (negative values inside the body). You can
specify if the distance should be absolute or relative to the bodys half width. This is
illustrated in the following two figures.
There is a new Object curvature property. This will produce a property whose values
show the curvature of the border of the nearest object. The curvature of the object's border
is calculated as the inverse of the radius of curvature of the border, and made negative
when the object is concave (such as the inside of a meander or the concave part of an
oxbow lake). There are two options for the radius of curvature: in real distance units or
relative to the object's half width. This is illustrated in the following two figures.
These three new properties can be combined, post-processed in the property calculator, and
used for advanced conditional facies modeling with the existing source objects. Refer to the
Other output tab (Object modeling) and Modeling fluvial facies with crevasse splays topics
of the online help manual for more details and workflow examples.
100
Schlumberger Public
Variable Azimuth Property Definition for Geometric

Bodies and Fluvial Channels
In Object modeling, the azimuth of single facies geometric bodies and fluvial channels (not
available for adaptive channels) can now be defined by a 3D property.
When running object modeling, the density and complexity of the well data might make it
difficult to achieve a complete well tie or achieve the expected target fractions with the
requested object geometry. In Petrel 2011.1, new honoring priority settings have been
introduced to help you achieve the desired result in case of conflicts.
Out of the three main criteriawell tie (Hard data), target fractions match (Facies
Proportion), and requested object geometry (Geometry)you can choose to relax one, thus
increasing the likelihood of achieving the other two. The Honoring priority settings will have
an effect on the result only if a conflict exists between criteria. Otherwise the result will be
identical, regardless of what option is chosen.
101
Schlumberger Public
Honoring Priority Settings for Object Modeling
The Honoring priority settings are located in the Settings tab for Object Modeling. If Object
dependent is selected, they are grayed out and individual settings appear at the bottom of
each individual objects Settings sub-tab.
In the following example, an adaptive channel model is run (Upscaled channel/levee fraction:
68%, specified channel fraction: 20%). The upscaled cells for well A1 are 100% levee facies.
The specified channel thickness is much thinner than the zone.
Honoring Priorities: Example with Hard Data selected.
If the highest flexibility is assigned to the Facies proportion honority priority, additional
bodies matching the specified geometry are inserted so that the whole interval is tied. However,
the resulting fraction is increased to 27%, as shown in the following example.
102
Schlumberger Public
If the highest flexibility is assigned to the Hard data honoring priority, bodies matching the
specified geometry are inserted and the result fraction is close to the target fraction (22%).
However, only 66% of the levee intervals are matched. In the following example, only three
bodies intersect well A1, and the bottom part of the interval is not tied (grey cells are undefined in the Bodies property).
Honoring Priorities: Example with Facies Proportion selected.
Finally, if the highest flexibility is assigned to the Geometry, bodies smaller than the specified
geometry are inserted, the result fraction is close to the target fraction (22%), and all levee and
channel intervals are matched.
Schlumberger Public
Honoring Priorities: Example with Geometry selected.
Refer to the Probability tab (Data analysis) topic of the online help manual for more details.
Servo-System for Sequential Indicator Simulation

The Sequential Indicator Simulation (SIS) algorithm has been re-implemented in C++. This new
implementation, as well as the original GSLIB Fortran code, is available in Facies modeling.
Both versions are very similar. However the C++ version is slightly faster and benefits from a
new expert Target fraction honoring setting. This setting drives a servo-system similar to
the one already implemented in Multi-Point Facies Simulation.
103
During the simulation, the algorithm will attempt to match

the specified target fractions for all facies.
In some cases, however, the other modeling constraints
(dense well control, long variogram ranges) will prevent the
algorithm from achieving the target fractions. When this
happens you can increase the value of the Target fraction
honoring parameter in the Expert tab. The servo-system
will then slightly tweak the algorithm to ensure that the
desired fraction is matched.
Volumetrics Calculation and Reporting Per Contact

Regions
Items selected in the list will be used in the report. To modify the reporting order, select one of
the criteria and move it up or down using the blue arrows.
104
Schlumberger Public
If the fluid contacts have been defined by a region property (refer to Define Fluid Contacts in
the Geology section of this guide), the Volume calculation process will compute separate subvolumes for each region. In the Volumetrics report settings, a new Contact regions reporting
level has been added to the list to be able to output these volumes. The Report detail and
order interface has been modified to improve usability.
Usability
There are two minor usability enhancements in Petrel 2011.1:
A template filter has been introduced in the Property calculator, making it easier to select
the appropriate template when creating a new property. As you begin entering the template
name, the drop-down list will show only the relevant templates.
When I- or J-filters are active, the Get limits from selected button will extract the
minimum and maximum X and Y of the selected object (most objects from the Input or
Models tab) and adjust the I and J minimum and maximum indexes to fit the corners of
the smallest topological rectangle containing the object.
105
Schlumberger Public
Structural Framework
The section summarizes Structural Framework functionality new to Petrel 2011.1.
Structural Gridding
Petrel 2011.1 introduces a new structural gridding process that enables you to directly construct
corner point grids from the Petrel structural framework without needing to use pillar gridding
workflows. The process is located under the corner point gridding process group.
There is some overlap in the creation of fully stair-stepped grids, since workflows introduced in
Petrel 2010.1 coexist with the new structural gridding workflows. Stair-step grids created using
the new structural gridding process will cause all of the included faults to be stair-stepped; the
new process does not allow creation of a partially stair-stepped grid, though this can still be
accomplished using the old workflows.
Grid results in Petrel 2011.1 are identical to 2010.1, but achieved through a single process.
106
Schlumberger Public
The new structural gridding process allows the construction of stair-stepped corner point grids.
The process automatically adopts the active structural framework as the input to the corner
point grid and applies the geometry and the defined zones. However, these may be altered to
suit the purpose of the grid.
Three tabs are used in the gridding process: Setup, Geometry, and Faults.
Setup Tab
The Setup tab controls the followings details of the new geocellular grid:
Type of grid being created (currently only stair-stepped is available),
Whether reverse faulting is needed,
Use of vertical-interval or zonation scheme,
Fine layers within the specified zones.
Schlumberger Public
107
General Settings
Create Grid Type Currently limited to stair-step corner-point grids.
Allow Reverse Faulting Allows stair-stepped grids, with reverse faults, to have
subsequent corner-point grid layers correctly modeled. This new layering is also correct for
facies and petrophysical modeling processes, allowing these geocellular grids to be used for
property modeling.
You can choose to combine or omit zones that were modeled in the structural framework. They
may also choose to reapply well top correction if they alter the I-J geometry (covered in the
Geometry tab). This allows construction of thin intervals within a much larger shared-earth
model, or it can be used to concatenate zones together for reservoir engineering purposes.
Region Boundary
This allows the merging of explicit region blocks (which are separated by faults) above and
below a specific horizon. When enabled, the regions above the horizon are given separate
indices from the regions below it.
Zone Layering
This controls the fine layering scheme within each of the zones specified by the vertical interval
section. Each zone may have different layering.
Geometry Tab
The Geometry tab allows you to modify the geometry of the output geocellular grid. By default
the geometry of the input structural framework is adopted as the geometry for the output
geocellular grid. Depending on the ultimate use of the geocellular grid (reservoir simulation or
fine scale property modeling) the input I-J cellular geometry may be unsuitable.
The tab allows you to alter these variables:
108
Schlumberger Public
Vertical Interval
I-J cell size,

Grid rotation,
Area of interest (by using a polygon).
The Statistics table reports an estimation of the total I-J columns in the output grid, to assist
reservoir engineering workflows. These will be refined further, depending on the independent
layering schemes used for each grid zone.
Schlumberger Public
Faults Tab
This tab allows you to omit or include faults from the structural framework in the output
geocellular grid. All faults are included, by default.
109
Structural Gridding Workflows

Zone Control
The structural gridding process allows you to omit particular horizons from the new geocellular
grid. Removing horizons will alter the zone hierarchy, since zones are defined as the interval
between horizons.
This workflow is useful for concatenating or omitting zones that are not reservoir from a
structural framework. This workflow is also targeted at generating a reservoir grid from a
structural framework where overburden or aquifer structure has been modeled.
Schlumberger Public
Geocellular zones as a result of all horizons being used in the grid construction.
110
Horizon H3 is omitted from the vertical interval panel which results in only two zones being constructed.
The structural gridding process can be used to construct a reservoir interval from a much larger
structural framework, by defining the horizons in the vertical layering panel.
111
Schlumberger Public
Reservoir Intervals
Layer Guides
The following image sequence describes how layer guides are applied.
By default the gridding process has not layered this

region well, so we use the layer guide to help enforce
better layering.
Use the make/edit surface or make/edit polygons to

create a dataset where the layering is good for the top
of a given layer.
Use this point set in the structural gridding

process
The layering in the previously bad region is now

improved; it has been guided by the points.
NOTE: This will affect other areas of the grid.
Quality check all regions and zones and, if
required, add further guiding data.
112
Schlumberger Public
Add points where you believe the layering should be

in the bad region. Points in any layer guide object are
treated differently, depending on their location:
- Points that are vertically between two horizons in
the structural framework are used to indicate which
layer is being referred to.
- Points that are vertically between a horizon and a
fault will be used to guide layering.
- Points that are vertically between two faults are
ignored.
Combining Regions
Region properties are created by default for each grid zone. These are useful for understanding
grid segmentation and potential sector modeling tasks. The region boundary option, which
separates grid regions, is toggled on by default in the structural gridding process.
113
Schlumberger Public
You may wish to combine zone regions together. This feature is activated or deactivated during
grid construction.
In this framework (shown in vertical crosssection), a fault is affecting horizons 2 and 3,

but horizon 1 is un-faulted.
If horizon 2 is not required as a region

boundary, then the entire model is considered
to be a single region, because the fault does
not intersect horizon 1.
Assessing Zone Cell Number

Statistics in the Geometry tab give an approximation of the I-J columns, based on the defined
geometry of the new corner-point grid.
114
Schlumberger Public
If horizon 2 is a region boundary, then the

lower zone (between horizons 2 and 3) is
separately split into regions from the upper
zone (between horizons 1 and 2).
The lower zone is separated into two regions,
since it is entirely split by the fault, and the
upper zone has its own, single region.
As a result, multiplying the number of layers by the number of columns in the new corner-point
grid will give a good estimation of the number of cells in each zone.
Structural Framework Fault Properties

Dip and Dip Direction
Seismic Extraction onto Faults

Seismic attribute data can now be
extracted onto the structural framework
faults to assist seismic interpretation. The
process extracts a texture map of the
extracted seismic onto each structural
framework fault.
NOTE: Seismic horizon interpretation cannot be carried out on this texture map,
however seismic fault interpretation objects and points or polylines may be used.
The seismic data can be extracted at a range of resolutions, from course to full seismic
resolution, and either on the fault or offset from the fault (offset into the hanging wall and the
footwall).
A series of difference calculations can be performed to compare the seismic at different offset
distances from the faults. This operation provides a powerful visualization technique to check
the accuracy of fault and horizon pick locations.
115
Schlumberger Public
Dip and dip direction attributes can now be

computed on TVD (depth) and TWT (two-waytime) structural framework faults. For two-waytime datasets, the user can specify an average
interval velocity to estimate the true fault dips.
Zonal Juxtapositions
Once a structural framework zone model has
been calculated, the areas defining the different
zonal juxtaposition types occurring along the
faults can now be mapped. This displays a
stratigraphic juxtaposition attribute along
structural framework faults, enabling early
identification of barriers to flow.
2D Fault Plane Maps

2D fault plane maps that help in defining trap locations can now be generated while conducting
initial seismic interpretations.
Schlumberger Public
Productivity and Usability

Fault Patch Removal Tool
The fault patch removal tool allows interactive removal of unwanted or incorrect fault patches
from the structural framework. The tool is accessed from the Fault framework modeling
process, with the Magic Wand icon now being available on the Functional toolbar.
To remove an unwanted fault patch, select the new tool and manipulate the 3D view to
visualize the piece of unwanted fault. Click the wand on the unwanted fault, and fault rules will
be updated, causing a recalculation of the fault relationship.
116
To remove or undo this, reset the fault relationship using the context sensitive menu or the
Edit Relationships tab in the Fault framework modeling process.
Schlumberger Public
117
Intersection Colorfill
Structural framework zone colorfill has now been added to the General Intersection and
Intersection windows.
Schlumberger Public
Streamlined Input Data Handling During MWI

Fault input data handling has now been updated during the Modeling While Interpreting
(MWI) process. Altering input data in the active MWI interpretation folder will automatically
update the active structural framework, depending on whether you drag data in or out:
Dragging new fault data into the active folder adds framework fault.
Dragging fault data out of the active folder deletes framework fault.
118
Context-Sensitive Menu Update

The right mouse button Context Sensitive menu has been updated to provide more user
control.
Schlumberger Public
Petrel 2010
Petrel 2011
119
Display Single Fault Input Data

The Show/hide input data option will display the input data for an individual structural
framework fault, as opposed to displaying all input data items.
For non-MWI workflows, if you recalculate changed faults, all structural framework faults which
had alterations to their input data will be updated.
120
Schlumberger Public
Recalculate Changed Faults
Delete Fault or Horizon
121
Schlumberger Public
You now have context-sensitive menu control of fault and horizon deletion from the active
structural framework, which also updates the input data rows in the relevant structural
framework processes.
Context Menu Process Synchronization

Changes to the structural framework using the right mouse button Context Sensitive menu
now correctly synchronizes with the relevant structural framework processes:
Deleting faults or horizons updates the input data rows in the processes and the Fault
Relationship table.
Altering fault extrapolation distances updates the Fault framework modeling process.
Toggling the relationship verification updates the Verified column in the Fault
Relationship table.
Swapping fault truncations and swapping major and minor fault relationships
automatically updates the Fault Relationship table.
Schlumberger Public
122
Reservoir Engineering
This section summarizes whats new in reservoir engineering in Petrel 2011.1. These are the
essential improvements:
Support of the INTERSECT environment, for faster simulations on more complex,

heterogeneous, and bigger models;
Improved productivity to help you do more in less time;
Additional and improved functionality to increase your ability to prepare, quality check,
history match, and analyze your reservoir and simulation data.
Import and Export Formats: Advance Notice for

2012.1
Schlumbergers commitment to openness can be seen in the adoption of open industry

standards for model exchange and through the promotion of access to Petrel for third parties
via the Ocean* software development framework. For model exchange with third party
simulators and modeling vendors such as CMG, Roxar, and Landmark, we support the use of
the open industry standard RESCUE format (and its successor, RESQML) and provide the ability
for third parties to create Ocean plug-ins for direct import and export of proprietary formats.
Beginning with the Petrel 2011.1 release, all SIS simulators support the GSG format. For 2012.1
we shall provide a GSG-RESQML conversion utility to provide an open route for third parties to
read and write GSG files. We shall make the ECLIPSE keyword import and export format more
flexible, allowing properties whose names are not ECLIPSE properties keywords to be imported
in this file formatthe main difference between the current ECLIPSE and CMG properties
format. ECLIPSE has deprecated the use of OPF for the last several releases.
Therefore beginning with the Petrel 2012.1 release, the following formats will be removed
(retired) from Petrel:
123
Schlumberger Public
The Petrel 2011.1 release supports a large number of alternative formats for the export of grid
geometry and properties for use by simulators. The multitude of formats poses a significant
maintenance challenge, particularly for multi-vendor workflows.
Import and Export

CMG grid (ASCII) (*.*)
VIP fault data (ASCII)(*.*)
VIP grid (ASCII) (*.*)
CMG properties (ASCII) (*.*)
VIP properties (ASCII) (*.*)
VIP properties Init/Restart (ASCII) (*.*)
VIP Well Connection Data (*.*)
VIP Well Completion Data (*.*)
Open RMS format (binary) (*.*)
Export
OPF (Petrel will continue to read existing OPF files)
Petrel 2011.1 is the last release to support the above listed formats.
INTERSECT Environment
Define Simulation Case

When you select INTERSECT as your simulator in the Process dialog, an additional tab
becomes available in the Define Simulation Case process. This dialog contains reporting and
tuning control. GSG is the only grid format option for exporting simulations to INTERSECT.
INTERSECT simulations require the transmissibility and pore volumes to be provided by Petrel.
124
Schlumberger Public
You can define, run, and analyze black oil, compositional, and thermal INTERSECT simulations
from Petrel 2011.1 using the same processes that you use for ECLIPSE or FRONTSIM.
Make Local Grids

An unstructured Generation method has been added to the Make Local Grids process,
allowing the creation of local grids with polyhedral cells following the path of the wellbore. If
the well path remains in the same I-J column for its length, then an unstructured radial grid is
created, with rings of cells around the well. If the well path is horizontal or deviated, the
unstructured cells form cells paralleling the well path along its length.
Unstructured radial grid created from a well

path with the same I-J column on the length.
Unstructured grid created from a

horizontal or deviated well path
125
Schlumberger Public
In general all the existing thermal functionality in Petrel software is available for INTERSECT
simulations with the 2011.1 release. This includes the thermal multi-segmented well
functionality, thermal fluids, thermal boundary conditions, export of thermal conductivities as
part of the transmissibility and pore volume calculations, and thermal results import and
analysis.
Options to control the size and number of cells for the unstructured local grids are described in
the tool tips.
NOTE: Simulation using unstructured local grids is only supported by the INTERSECT
simulator. Properties on unstructured local grids can be defined by either inheritance
from the host global cell or by upscaling from another grid using the cell-center method
only.
Make Development Strategies

INTERESECT 2011.1 has a flexible and powerful Field Management function. Using Petrel
2011.1 you can use Make Development Strategies to define the dynamic control on the
reservoir. There are some INTERSECT specific rules in Make Development Strategies, and these
are identified in the online help manual and the validation messages within the Make
Development Strategies process. When a development strategy is exported as part of an
INTERSECT case, it is converted to a file of Field Management commands. However to access
the full Field Management functionality, the editor must be used to edit the field management
file directly. Refer to the INTERSECT and Field Management manuals for further details.
The Petrel 2011.1 release offers improved support for compositional and thermal workflows
using both the ECLIPSE Thermal or INTERSECT simulators.
Define Simulation Case: Initialization by Enumeration for Thermal and

Compositional
Initialization by enumeration is possible though not fully supported. In the Grid tab:
Supply all the following grid properties: PRESSURE, TEMPERATURE, SWAT, and SGAS;
Supply either RS, or PBUB and RV, or PDEW.
To complete initialization by enumeration, you still need to specify the initial compositional
variation with depth by adding user keywords to the simulation case (ZMFVD and COMPVD, or
XMF and YMF).
Make Fluids: Mixed Hydrostatic Equilibration Option for Thermal

The Mixed initialization option calculates the pressure gradient internally (assuming an oil
leg) and expects the saturation arrays to be specified by the user. This feature has been
introduced to help simplify the modeling of isolated gas pockets in very viscous oil reservoirs,
where the gas pockets are deduced from seismic maps or log data. This initialization will
126
Schlumberger Public
Initialization of Simulations
produce a "hydrostatic" pressure gradient with the formation in vertical communication, where
the gas is expected to remain trapped due to the very low mobility of the surrounding oil.
This initialization option has been implemented in ECLIPSE Thermal 2011.1, and Petrel 2011.1
supports the mixed hydrostatic equilibrium. The option can be accessed under the Initial
Conditions tab of the Make Fluids process and is not available for simulations using earlier
versions of ECLIPSE. Refer to the ECLIPSE Technical manual under the "Initializing the Study"
chapter for further details on the ECLIPSE keywords used for Mixed Hydrostatic Equilibrium
initialization.
Fine Scale Equilibration

This option is available for use with ECLIPSE, ECLIPSE Compositional, and INTERSECT
simulation cases. When the Initialize by equilibration option is selected, then two columns
will be added to the table in which you activate the fine scale equilibration option and set the
related controls (number of levels and the tilted cell option). The ECLIPSE and INTERSECT
manuals provides further details on these initialization options.
Schlumberger Public
Conversion of ECLIPSE Data Input Files

RUNSPEC Section Export
The Petrel 2011.1 release now generates the RUNSPEC section from all the keywords exported
to the case. Prior to this Petrel would update the RUNSPEC section from the model in the
project, which meant that user keywords were ignored and caused a potentially inconsistent
RUNSPEC to be exported.
RUNSPEC is generated three ways:
As part of the Convert to Petrel case option,

When the user presses the Generate RUNSPEC button on the keyword editor,
When a case is exported.
127
NOTE: This process will not update user keywords in the RUNSPEC, that is, keywords
without a generated tag. Exceptions to this are the DIMENS keyword (calculated from the
grid in Petrel) and WELLDIMS (calculated from the wells and completions).
Case Conversion Key Points: Best Practices

Petrel 2011 offers major improvements to the case conversion of imported ECLIPSE data input
files.
Transparency In the Petrel 2011.1 release, the case conversion process was made more
transparent. Petrel outputs a Convert to Petrel case messages window, which provides
the conversion status of each single keyword of the ECLIPSE data input file. Keywords can
be set to:
Additional Supported Keywords These additional keywords are fully converted in Petrel
2011:
GRUPTREE
WELSPECS
COMPDAT
WLIST
Development Strategy It is now possible to convert the schedule section of an ECLIPSE

data input file into a development strategy.
If the data input file has only history data, a history development strategy is created.
If the data input file has only prediction data, a prediction development strategy is
created.
If the data file has both history and prediction data, Petrel will create both a history and
a prediction development strategy.
Vertical Flow Performance (VFP) Tables If an imported ECLIPSE data input file has VFP
tables, Petrel will convert them and add them to the Input pane. They also appear as
Schedule keyword rules in the development strategy. They can be quality checked after the
case conversion using the VFP manager.
Dual Porosity Models Dual porosity models are can be converted to Petrel cases in Petrel
2011. However, the NODPPM keyword does not get converted because there is currently no
specific process in Petrel to build a dual-porosity model. Dual-porosity models are created
using the Define simulation case process.
128
Schlumberger Public
Ignored
Converted
Not converted
Partially converted
Unsupported Keywords All keywords not supported by the user interface will be either
preserved as user keywords (for keywords from RUNSPEC, GRID, EDIT, PROPS,
SOLUTION, REGIONS, and SUMMARY) or converted to a Schedule keyword rule for each
date within an outline development strategy created by the conversion process (for
keywords from the Schedule section).
The converted case must always be reviewed to ensure that the quality of the model is
preserved. The following points must also be taken into account:
Aquifers are not converted in the Petrel 2011.1 release. Whether a model has one or
several aquifers, all the keywords pertaining to them will be preserved as user
keywords.
The API option is not currently supported by the case conversion.
The EOR (enhanced oil recovery) options (for example Brine, Chemical reactions,
Polymer flooding) are not supported by case conversion in the Petrel 2011.1 release.
Advanced ECLIPSE options such as Gas field operations, Gas plants and NGL, and
Independent reservoir are not supported for the case conversion in the Petrel
2011.1 release.
1. Import the data file by right-clicking anywhere in the Cases pane.

2. Save the project.
3. Right click the imported case and select the Convert to Petrel case option. The Guided
schedule section conversion window opens.
Three conversion options are available:
129
Schlumberger Public
How to Perform a Case Conversion and Quality Check
Automated This conversion type can be selected when well names in Petrel match
those in the ECLIPSE data file or when completions are to be extracted from the
COMPDAT keywords. If history and prediction data are in the same file, Petrel selects
the first WCONPROD encountered as the end of the history and the start of the
prediction phase.
Guided This conversion type can be selected when well names in Petrel are different
than those in the ECLIPSE data file. The names in Petrel can be mapped to those in the
data file. If well completions have already been imported as a separate .vol file,
completions do not need to be extracted from the COMPDAT keywords; therefore you
must deselect the Extract completions from keywords option. The guided
conversion type is also used to specify the date at which prediction data start. This is
particularly useful when prediction starts with a keyword other than WCONPROD.
No conversion of the SCHEDULE section.
4. Select your conversation option and click OK. A new window opens to display information
on the conversion status of each keyword.
Schlumberger Public
Converted Keywords whose items are fully converted.
Partially converted Keywords for which only some items are converted.
Ignored Keywords that are not necessary to create the Petrel case, for example
ECLIPSE data input file section names.
Not converted Keywords that are not supported by the user interface. They are
preserved as user keywords.
130
A new case is added to the Cases pane. A Fluids folder, a Rock Physics Functions
folder, and a Development Strategies folder are added to the Input pane. If historical
and prediction data are in the same file, Petrel software will produce two development
strategies, one for history and one for prediction. An example of the folder structure is
shown in the following image.
131
Schlumberger Public
5. All unsupported keywords from the Schedule section of an ECLIPSE data file are preserved
as Schedule keyword rules in an outline development strategy. This development strategy
can generally be exported as part of the Petrel simulation case and run in ECLIPSE as is.
However you can choose to further complete the conversion process by editing the outline
development strategies to replace some or all of the content of the Schedule rules with
equivalent Petrel rules or new User Defined Rules.
6. Quality check the case conversion. It is essential to compare results from the converted
case to those of the original one to identify the remaining manual steps needed to complete
each individual case conversion. For example, check that the oil in place calculated by the
original and the converted cases match each other.
User Defined Rules in Development Strategies

User Defined Rules (UDRs) in the Petrel 2011.1 release are an extension of the Schedule
Keyword Rules introduced in Petrel 2010. They offer more flexibility and can be fully
parameterized. They can be shared and re-used between projects through use of the Reference
Project Tool. The Schedule keyword rule remains available.
Development strategies that contain UDRs or Schedule keyword rules cannot be used in
INTERSECT simulation cases.
A library of prebuilt UDRs for single and multiple keywords have been added to the Petrel demo
data project, for you to re-use or adapt.
How to Create a User Defined Rule

In this example we build a UDR similar to the existing Petrel Well WAG injection control rule
and discuss some details of the rule canvas. For simplicity, the example rule is composed of
only the WELLWAG keyword, which contains 14 items. Refer to Examples of User Defined
Rules Containing Multiple Keywords for more information.
Step 1: UDR Creation

1. Open the Make development strategy process and click Add new rule. The Add rules
dialog opens.
2. Click the Advanced button to create or edit UDRs.
3. Select the Create New radio button and enter a name for the rule.
4. On the Implementation tab, enter the keywords that comprise this rule. You can type or
paste the text (the radio button above the tab switches to Edit Existing). Items that are
parameterized must be entered with a dollar sign ($) in front of them. The names of the
parameter can be changed later, so at this point you can name them or just number them,
132
Schlumberger Public
ECLIPSE users should not confuse UDRs with the ECLIPSE keywords UDQ and UDT. The latter
provides the ability to parameterize certain keyword arguments using reporting automatic
triggered actions (ACTIONX, W, G, and R) and dynamic grid operators OPERATE(R). On the
other hand, UDRs are rules that allow easier implementation of existing operation modeling that
is built into ECLIPSE
as you prefer. You could cut and paste the keyword text from, for example, the ECLIPSE
online manual and then add a dollar sign ($) in front of the arguments you want to
parameterize.
5. Click the Generate parameters button. Parameters appear in the lower half of the
window when the keyword and items are generated. Petrel attempts to set suitable types
and ranges for parameterized items using its knowledge of the keyword syntax. The
selected type will determine the valid parameter values and ranges. For instance, if the
selected type is Boolean, the parameter value will be either Yes or No.
133
Schlumberger Public
NOTE: The parameter type for a well name defaults to String. This should be
selected manually as Wells and should be shared between all keywords within
the UDR so that the Petrel software can substitute the appropriate well names
when you export your development strategy containing this rule. In the example
below, the parameter name was changed from 1 to the more meaningful Well
name.
Step 2: UDR Settings

After creating the UDR, you now complete the UDR definition using the Definition tab. Though
most of these steps are optional, doing them greatly improves the ease of re-use and
robustness of the UDR by you and by other projects within the company.
1. Document your rule by filling in the Description field and assigning it to the appropriate
rule Category.
3. Add documentation and validity checks to each parameter in your rule. Select a row in the
parameter tables and click Show Settings. For each parameter, set the description of that
parameter. Petrel will, where possible, pre-populate the defaults and ranges and check
whether the argument is optional, based on the ECLIPSE keyword syntax. Review the autopopulated values and, if applicable, set unit, range, and default values.
134
Schlumberger Public
2. Add validation checks to your rule by selecting the appropriate Simulators and Strategy
type options.
How to Add a User Defined Rule to the Development Strategy

The created UDR is located in the User Defined Rules folder. If no category has been set, the
rule appears in the General folder. To add the UDR to the Development strategy, select the
rule and click the Add rule button in the same way as you do for Petrel (SLB) rules.
How to Share User Defined Rules between Projects
How to Convert a Schedule Keyword Rule into a User Defined Rule

1. Create a new, empty UDR.
a. Open the Make development strategy process and click the Open Add rules
button.
b. In the Add Rules dialog, click the Advanced tab.
c. Select Create new rule radio button, and enter a name for the new rule.
2. In the Make development strategy dialog, select the Schedule keyword rule, then cut
and paste the keywords of interest from the text box on the right into the implementation
box of the UDR.
3. Select which items to parameterized and add dollar signs in front of them.
4. Click the Generate parameters button.
135
Schlumberger Public
Once created, UDRs are stored in the Input pane in the Development strategies folder.
They can be copied between projects with the same project unit system, using the Reference
Project Tool.
5. Set the appropriate parameter types.

6. Edit or modify the settings, as necessary, and click the Apply button.
Schlumberger Public
Examples of User Defined Rules Containing Multiple Keywords

UDRs that contain multiple keywords are more useful and flexible. They can be created in a way
similar to single keyword UDRs. We may never have a complete set of UDRs, but with the right
advice and examples, it should be possible for engineers to build their own sets. Below are
some valid examples from the library of pre-defined UDRs supplied with the Petrel demo
project.
136
Example1: Well Economic Limit with Plug Option

Equivalent ECLIPSE keywords WECON and WPLUG
NOTE: The $Wname parameter is used twice in this example.
Schlumberger Public
WECON
$Wname $ORATmin $GRATmin
$WCTmax $GORmax 1* $WkOv $EndSim
4* $GLRmax $LRATmin $MaxTemp /
/
WPLUG
$Wname $TopPlugLength
$BtmPlugLength $PlugType /
/
Example 2: Advance Injection Gas (for E300 only)

Rule combines two keywords WELLSTRE and GADVANCE
NOTE: Specify the advance gas name and composition as String.
WELLSTRE
$StreamName $StreamComposition
/
/
GADVANCE
$Group $StreamName
$AdvGasRate /
/
137
Example 3: Alkaline-Surfactant-Polymer Injection Control (for E100 only)
Schlumberger Public
History Matching Tools

Grid Property Modification Process
A new Grid property modification process allows you to modify the properties specified in a
simulation case during case export, leaving the data saved in the Petrel project unaffected. This
new feature provides a simple and more user-friendly alternative to the property calculator and
is particularly convenient for use within Uncertainty and Optimization workflows.
There are two basic steps to add grid property modification to your history-matching workflow:
1. Create and add sets of property modifiers to the Input pane using the Grid property
modification process.
138
2. Include these sets in simulation cases, to affect the desired modifications in the data input
file.
Optionally you can vary the definition of the set within Uncertainty and Optimization workflows,
to generate multiple realizations of the grid properties.
To be able to work effectively with grid property modification, it is essential to understand these
building blocks for defining modifiers:
Property modifier sets

Property modifiers
Operations
Filters
Property Modifier Sets
Property Modifiers
Property modifiers have two components:
One or more operations defining modifications to the properties included in a simulation

case;
Optionally, one or more generic filters defining the subset of cells to be modified.
Operations
Operations define the modifications that will be applied to cells affected by their parent
modifier. To allow property modifier sets to be portable to different cases, grids, and simulators,
operations are defined in terms of a set of generic simulator keywords that correspond to
properties specified on the Grid tab of the Define simulation case dialog. The details of how
to manage the operations within a property modifier are described in the next section.
139
Schlumberger Public
Property modifier sets are containers for property modifiers that allow a combination of
modifications for easy inclusion in simulation cases. Any property modifier set contained in a
project can be found under the Property modifiers folder in the Input pane. Sets are defined
using the new Grid property modification process dialog, which can be found under
Simulation in the Process pane. Once defined and stored in the pane, sets can be added to
simulation cases via the Grid tab of the Define simulation case process.
Filters
To allow grid property modification to be restricted to a subset of the grid cells, one or more
generic filters can be added to a modifier. To determine whether a property modifier should be
applied to a grid cell, Petrel evaluates the TRUE/FALSE value. If all the modifier's filters evaluate
to true, the modifier's operations will be applied to the cell, otherwise the cell will be ignored.
Use the 3D window to determine whether a modifier will affect the correct cells. Start by
clearing all visualizations from the window and disabling all filters. Next, choose a property to
visualize that is defined (has a value) at every cell in the whole grid; this is essential for
avoiding ambiguity about why cells are not displayed. Once your property is displayed, switch
on all the filters you have added to your modifier, making sure that no additional filters are
enabled. Once you have done this, the window will display only the cells that will be modified.
Instructions for how to use generic filters are provided in the Basics section of the online help
manual. The following section describes how to add or remove filters to and from a property
modifier set.
The Grid property modification process dialog, shown below, allows you to create and edit
property modifier sets and preview their effect on a simulation case. The Grid property
modification process is located under Simulation in the Processes pane.
The upper section of this dialog allows you to choose between creating a new set and editing
an existing set in the project. To create a new set, select the Create new check box and enter
a name for the new set. To edit an existing set, select the Edit existing check box and select
the desired set from the drop-down menu.
140
Schlumberger Public
Using the Grid Property Modification Process
Schlumberger Public
The two tabs in the lower section of the dialog allow you to define the modifier set and preview
the effect of the modifier set on a given case. You can preview the effect of the grid property
modifier on a particular simulation case by using the blue-arrow Simulation case drop site to
select the case. Dropping a simulation case here activates two features of the dialog:
Filter keywords Check box located to the right of the Simulation case drop site.
Used to toggle keyword filtering on and off. When toggled on, the keywords in the dropdown menus on the Operations tab of the Define property modifier tab are filtered
in accordance with keyword mapping rules (see the following section) applied to the
dropped case. When you enable the Filter keywords option, you are guided towards a
property modifier set definition that is compatible with the dropped case.
141
Create modified properties Button located on the Preview modification results

tab. Allows you to preview the modifications that result from applying the current dialog
settings to the dropped case.
Below these controls is the main tab group containing the Define property modifier set and
Preview modification results tabs.
Mapping Keywords within Simulation Cases

When a property modifier set is applied to a simulation case, the Petrel software looks inside
the case for grid tab properties corresponding to the keywords referenced within the property
modifier set. The following search rules apply:
Any disabled property modifiers or operations are ignored.
For each keyword referenced in the property modifier set, the case must define a 3D
property.
For each keyword appearing on the left-hand side of an operation, the case must define
a 3D property that is not used again in that case. For example, you may not drop the
same Permeability property as both PERMX and PERMY if you intend to modify either of
those properties with a property modifier set.
If the case does not satisfy the above requirements for the property modifier set it includes,
modification will be aborted. For dual porosity cases, the rules are independently applied twice,
once for the matrix property modifier set with respect to the matrix properties and again for the
fracture property modifier set with respect to the fracture properties.
Defining a Property Modifier Set

The Define property modifier set tab uses tables to present the modifiers within the set and
the operations within the modifiers.
The usual buttons
above each table are used to add, delete, or
reorder items within the table. Entries in both the modifier and operations tables can be
temporarily disabled by clearing the check box in the leftmost column. Disabled modifiers and
operations will be ignored when the containing property modifier set is applied to a case.
142
Schlumberger Public
The property modifiers within the set being edited are displayed in the modifiers table in the top
half of the tab.
To transfer property modifiers between sets, either copy and paste or drag and drop them into
the Input pane.
The operations within a property modifier are edited on the Operations tab. To edit a
modifier, you must first select it in the modifiers table.
Schlumberger Public
The controls that appear to the right of the operations table allow the currently selected
operation (highlighted in light blue) to be edited:
Formula Drop-down menu for selecting from a list of available property modification
operations.
Y Drop-down menu for selecting the generic keyword that appears on the left-hand
side of the operation. If you select the Filter keywords check box, the drop-down will
contain only the keywords which satisfy keyword mapping rule 3, with respect to the
case in the Simulation case drop site.
143
X Drop-down menu for selecting the generic keyword that appears on the right-hand
side of the operation. If you select the Filter keywords check box, the drop-down will
contain only the keywords which satisfy keyword mapping rule 2, with respect to the
case in the Simulation case drop site.
a Text box for editing the first scalar parameter in the operation, if present. When the
dialog is launched from within the Workflow editor or from the Uncertainty and
Optimization process, this text box will accept named variables.
b Text box for editing the second scalar parameter in the operation, if present. When
the dialog is launched from within the Workflow editor or from the Uncertainty and
Optimization process, this text box will accept named variables.
The filters within a modifier are managed on the Filters tab. To manage the filters within a
modifier, you must first select the modifier in the modifiers table in the upper part of the dialog.
NOTE: Because the filters within a property modifier set are combined into a single filter
using a logical AND operation (see filters above), the order of the filters in this table has
no significance.
Including Property Modifier Sets in Simulation Cases

To prepare a simulation case for export-time property modification, a property modifier set is
dropped onto the Grid tab of the Define simulation case process dialog.
For single porosity cases, the Grid tab of the Define simulation case will accept a single
property modifier set. For dual porosity cases, the Grid tab of Define simulation case will
allow one property modifier set to be dropped as the modifier for matrix properties and allow a
second set to be dropped as the modifier for fracture properties.
144
Schlumberger Public
The buttons in the top left of the tab allow filters to be added and removed. To add a filter to a
property modifier, find and select it in the Input pane and then click the Add filter button. To
remove a filter from a property modifier, select it in the filters table and click the Delete
selected filter button.
When a case containing a property modifier set is exported, Petrel will attempt to calculate
modified versions of the case's properties as specified by the property modifier set. The
modified versions are then written to the data input file in place of the originals, leaving the
data in the project unaffected.
If any of the keywords referenced within the set cannot be mapped to properties within the
case according to the keyword mapping rules, modification will be aborted and the export will
proceed with the unmodified properties.
Uncertainty and Optimization Dialog

The Uncertainty and optimization dialog received several small but useful enhancements to
dialog, variable setting, sampling control, and failed case handling.
Dialog
The Pr (process) column indicates the source for each process variable. Double-clicking a
process icon in this column displays the process dialog in which the variable originated. Note
that user variables have no icon in this column.
145
Schlumberger Public
To conserve space, the Variables display on the base case panel is now truncated. Hover the
mouse pointer over a truncated command variable listing to reveal the full list of command
variables.
Variable Setting
You choose the variable names, but for clarity and future maintenance we recommend using
descriptive variable names. Some processes support automatic naming, as indicated by the
salmon pink background color of input fields, as shown in the following image.
Schlumberger Public
Petrel chooses clear, identifiable, and unique names derived by concatenating process,
component, and quantity names. Automatic naming is selected by hovering the mouse pointer
over a colored input field, right-clicking, and selecting the Auto variable option.
146
This yields a new variable that is added to the Variables table.
Sampling Control
Failed Case Handling

In the Petrel 2010.1 release, a failed case meant no results. With 2011.1, a failed case means
an incomplete run. This means incomplete runs are not included in the statistical results.
Therefore processes that depend on simulation, such as the define objective and optimization
algorithm, are not skewed by incomplete runs. This provides more reliable results.
In Petrel 2010.1, an uncertainty and optimization run failure meant that cases were moved to
the failed runs folder and lost their context, including the variables. In 2011.1 there is no
separate folder, so the context and variables are never lost.
History Match Objective Function

The aim of the new history matching objective function is to compare numerical simulation
results with real data observed in the field, and optionally adjust various properties and
parameters entering the simulation, to reduce the mismatch between the two sources of data.
The Define objective function process facilitates a straightforward setup and tuning of the
history mismatch computations, based on reservoir production data such as well flow rates and
pressures.
147
Schlumberger Public
The Petrel 2011.1 release introduces a new, simple, equal spaced sampler. This is most useful
in sensitivity studies. The SEED values may be set from the Uncertainty and optimization
process, for any process that involves internal Monte Carlo sampling as part of the Petrel
process. Control over the SEED variable value means that uncertainty and optimization
workflows that include such a process can be made reproducible, that is, they will give the
same sets of results when rerun.
Once you select the History matching objective type in the Define objective function
dialog, five tabs appears, as shown in the following image.
Data Mapping Tab
To define the data mapping, you first drop in an observed data set from the Input pane into
the Observed data field. The Data Mapping table is instantly filled with rows of observed
quantities obtained from the set and the corresponding simulation quantities found in the base
case. Depending on the base case settings, some simulation quantities may be unavailable and
hence their entries in the Data Mapping table stay empty. By filling in the table you can pair
each observed quantity with any valid simulation quantity of user's choice, either by filling in
empty fields or replacing the default simulation quantities. Select the Use checkbox in each row
to define which pairs to use in the objective function. A valid simulation quantity is a quantity
from the Dynamic results data of the Results pane that has been computed for the specified
base case and is of the same measurement (for example, a pressure or oil production rate) as
the corresponding observed quantity.
Certain data appearing in the observed data set are not directly imported from an external file;
instead they are computed by the Petrel software from other observed quantities. For example,
Phase-flow ratios such as water cut or GOR, or group and field data computed by merging
contributions from their wells. By default these data do not appear in the Data Mapping table or
on the Production data tab. In order to include such data in the objective function
computation, you must select the Allow computed data checkbox.
148
Schlumberger Public
This tab contains the Data Mapping table in which you can pair up observed data with any
matching simulated data to define the mismatches to be calculated and used in the history
matching objective function.
Production Data Tab

Having properly set up the observed and simulation quantities on the Data mapping tab, you
can now use the Production data tab to assign weights and other options to each quantity
identifier pair, where identifier represents any well or group of wells, including Field. The tab
contains two data tables: the Summary table on the left and the Details table on the right. The
following data types appear in both tables:
Identifier name Name of a well or group of wells to be history matched.
Quantity name Observed quantity to be history matched against the simulation quantity
specified in the Data mapping tab.
Observed range Minimum and maximum observed values in the Unit-displayed units.
Mismatch range Minimum and maximum non-weighted history mismatch in the

Unit-displayed units.
Unit Measurement unit associated with the Observed range, Mismatch range, and
Measurement error.
Measurement error Estimate of the standard deviation of the observed data. Used to
normalize each history-mismatch contribution.
Identifier weight Non-negative coefficient controlling influence of the associated well or

group on the global history mismatch.
Quantity weight Non-negative coefficient controlling influence of the associated

quantity on the global history mismatch.
Time weight Non-negative function (defined in the Time weights tab) controlling the
influence of date and time on the global history mismatch.
Ignore zeros Option to skip observations with strictly zero values even though the
corresponding simulation values may be non-zero. Refer to Zero Observed Data Filtering
in the online help, which describes the numerical implications of activating this option.
149
Schlumberger Public
Summary Table
The Summary table rows and columns can be grouped, filtered, and ordered using the
Grouping and sorting bar and the filter drop-downs and column titles, in the same way as you
do in the Completion Manager. Use the SHIFT and CTRL keys to make multiple selections.
There are two additional selection modes which can be very useful in a grouped or filtered
view:
Select all visible rows Press the top-left cell of the Summary table to select all rows
(including rows under all collapsed groups) not filtered out by the current filters.
Select all rows in a group Press any group title cell to select all rows (including
rows under all collapsed subgroups) not filtered out by the current sub-filters.
No changes to data within a row are committed until you press the ENTER key or switch to
another row. To discard any changes made to a row before that, press the ESC key; the row
data are then reverted to their values before the editing mode.
If the Summary table shows no data, make sure that at least one row in the Data mapping
tab table has its Use checkbox selected and the Saved search option (described below) is not
filtering out all available identifiers.
The following screenshot shows the Summary table from the example above, after grouping
and sorting by Quantity name, filtering the second group to show identifier INJ only, and
swapping its first two columns:
150
Schlumberger Public
The Summary table, located on the left of the Production data tab, displays all
quantity-identifier pairs for which you selected Use in the Data mapping tab. Each row
represents a single quantity-identifier pair whose production data will be used in the history
mismatch computation.
The main role of the Summary table, though, is to facilitate multiple selections which can be
collectively edited in the Details table, described next.
Details Table
151
Schlumberger Public
The Details table, located on the right side of the Production data tab, displays data from all
rows currently selected in the Summary table. If more than one row is selected and values in
the corresponding cells differ between the rows, then the Details table shows a series of blue
hash marks (#####). A series of grey question marks (?????) indicate that the corresponding
cells are currently being edited in the Summary table.
Time Weights Tab

The Time Weight tab allows you to put more emphasis on certain simulation periods and
suppress the history-mismatch impact of other periods. The time weight is a function of date
and time, with dimensionless values equal to or greater than zero. Different time weights can
be applied to different quantity-identifier pairs in the Production data tab. The Time weights
tab provides a convenient tool for creating and editing time weights for history matching:
NOTE: Though you may edit the Default time weight function, we recommended you
create and edit another time weight.
The selected time weight is displayed graphically on the right side of the tab window. You can
select one or more points using the mouse and CTRL or SHIFT keys, and move them using the
mouse or keyboard.
After creating a new time weight function, remember to revisit the Production data tab and
select the weight for the quantity-identifier pairs that should involve the new function in their
history-mismatch contributions.
152
Schlumberger Public
All time weights are stored as individual icons in the Objective functions|Time weights
folder of the Input pane; they can be reused between Petrel projects via the Reference Project
Tool. All the defined time weights are listed in the left side of the tab window. The Default time
weight has a constant value of 1 and spans the years 1900 to 2100.
Output Options Tab

The output from the history matching objective function is controlled by the user settings made
in the Output options tab.
There are three forms of output from this process:
A set of mismatch vectors or dynamic results,

Well top attributes,
Partial objective functions.
History Mismatch Measure

The first important decision that the user must make is to choose the statistical measure which
collapses the entire history vector of individual mismatches d(T), weighted by time weight
w(T), at N observation times T into a single number m(I, Q) representing the history mismatch
for the given identifier I and quantity Q. The three currently supported measures are:
153
Schlumberger Public
Figure RE-1. The Output Options Tab
Average Arithmetic mean (related to the L1-norm of vector algebra).
RMS Root-mean-square or quadratic mean (related to the L2-norm of vector algebra).
Maximum Largest absolute value (related to the L-norm of vector algebra).
Signed (Optional) Extends the standard measure definitions by also capturing the
sign of vector d(T): as a sum of d for Average and RMS measures, and as a minimum
or maximum of d for Maximum. The signed measures sm(I, Q) are only available for
dynamic results and well top attributes, that is, case variables output by this process are
always based on the standard (unsigned) measures. One example where signed
measures might be preferable is the creation of surfaces based on the history-match
related well-top attributes described below.
Dynamic Results
The first form of output from the history matching objective function is stored in the
Results|Dynamic results data|History match quantities folder of the Results pane. Up
to three dynamic results may be output for each quantity-identifier pair:
Average, RMS or Maximum Time-independent value of the standard measure m(I,
Q) or the signed measure sm(I, Q) selected in this tab; it is always output.
Mismatch Time-dependent difference between the simulation results and observed;

output is optional.
Normalized mismatch Time-dependent mismatch D(T) divided by the measurement

error E; output is optional.
NOTE: Although the measure is constant in time, it is represented by a "dynamic

result" with two identical values at the start and end times of the simulation timeline.
This allows you to exploit various features available for the dynamic results, such as
bubble plot, summary calculator, or function plot spreadsheet, in order to compare
history mismatches in a number of ways.
The following screenshot demonstrates plotting of dynamic results generated by the Define
objective function process for the Output options tab settings described above.
154
Schlumberger Public
The History match quantities folder in the Results pane lists all computed mismatch
quantities derived from the observed quantities selected in the Data mapping tab and
corresponding to the settings described above for the Output options tab. Notice that the ...
mismatch quantities, computed as D(T), have associated units (psi and STB/d) and are plotted
as points by default. Whereas the ... mismatch RMS quantities, computed as m(I, Q), are
dimensionless (see the Normalized Quantity, [] title of the right Y-axis), and are plotted as lines
by default.
Well Top Attributes

The second form of output from this process is a set of history-match related well top
attributes. In the tab settings example above, the Assign to well tops checkbox is selected
and the Well tops 1 icon dropped into the corresponding dropsite. After running the process
for the objective function History match 1, the following four new attributes are appended to
Well tops 1 in the Input pane:
155
Schlumberger Public
While plotting history match results, make sure at least one History match data source and at
least one simulation case are active, along with the corresponding identifiers and History
match quantities.
History_match_1
History_match_1_OPR
History_match_1_PR
History_match_1_WPR
The History_match_1 attribute represents the global objective function, which is always output.
The other three attributes correspond to partial objective functions and are optional; to output
them select the Separate quantities checkbox on the Output options tab. Partial objective
functions as well top attributes support signed measures, unlike the other three kinds of
objective functions introduced in the next topic.
Partial Objective Functions

The last of the three forms of output from this process is a set of case variables generated by
the history matching objective function. A variable representing global objective functions is
always output, irrespective of the user settings. Variables representing partial objective
functions are output if you select the Separate quantities checkbox.
The global objective function is a combination of the history-mismatch contributions from all
identifiers and quantities appearing in the Production data tab. The partial objective functions
are computed separately for each quantity; the case variable names for these are derived by
appending a quantity symbol such as OPR, PR, or WPR. The quantity weights from the
Production data tab are only applied to the partial objective functions computation if the
Apply target weight option is turned on. This means that the sum of all the case variables
representing partial objective functions will only sum to the global objective function value if the
Apply target weight option is turned on.
156
Schlumberger Public
All well tops of the same well share the same value of every attribute output by this process.
The main idea behind outputting history mismatches as well top attributes is to enable
workflows that would (perhaps iteratively) adapt grid regions and properties to these spatially
defined mismatches in an a attempt to improve the overall history match of well production
data.
In the following example, the History match 1 and History match 2 objective functions have
their Separate quantities checkbox selected and deselected, respectively.
Simulation vs. Observed Data Plot
How to Use the Simulation versus

Observed Data Plot
1. Activate the Function window.
2. In the Results pane, select this type of plot by toggling on the Simulated vs. observed
option under the Views tree. The first observed data set in the Source data type tree will
be selected as X by default.
3. Select the result to display by selecting the appropriate item in the Dynamic results data
tree.
4. Select the set of wells by selecting them in the Identifier tree.
5. Select the simulation case or cases and the time step to display by selecting the simulation
case(s) in the Cases pane and selecting the required time step in time player. The cross
plot is displayed as shown below.
157
Schlumberger Public
The new Simulated vs. Observed data plots provide a

convenient way to visualize mismatch between actual
and simulated well production data such as oil, water,
and gas rates, or cumulative. The data are plotted as
a cross plot of simulated and observed data with one
point per well per time step in the Function window.
More than one case can be plotted simultaneously for
case comparison purposes.
To access the display settings of this plot, open the Settings Dialog for each simulation case
displayed. The color of the symbol is controlled by the case color on the Info tab, and the
Style tab contains options to control the style of the points.
Picking a point on the plot will display the name of the well in the status bar.
NOTE: When you use the Output dynamic data to output sheet button, only
the data for the current time step is copied to the output sheet.
Known Limitations:
You cannot export the data and chart of the Simulation vs. Observed Plot to Excel using
the new Export to Excel function.
You cannot autogenerate a workflow to reproduce the Simulation vs. Observed Plot
using the Reproduce summary data options listed under the Auto generate
workflow option in the Workflow editor.
158
Schlumberger Public
You can use the time player to visualize how the match evolves over time. The crossplot will
appear only when both observed and simulation data are available. If nothing appears on the
plot, then there may be no results for that time step.
Visualization of End Point Scaled Saturation

Curves: End Point Scaling Probe
End point scaling (EPS) is used to generate saturation function curves with different values for
critical points on the curve, known as the end points, from a small set of base input curves. The
different relative permeability and capillary pressure curves are derived by applying linear
transformations on these input curves using different end points. The scaled curves will then be
used in the simulation. End point scaling can be used for different purposes; it can be a way to
reduce the number of input saturation tables, if they can be transformed to a smaller number of
generic curves, and it can be used as part of history matching scaling simulated reservoir.
To activate the probe, select any process inside the simulation processes folder, and then select
the End point scaling probe button in the Property player toolbar. Pick a cell in the 3D
window to see the selected curves displayed in the probe dialog, shown in the following
example.
159
Schlumberger Public
The EPS probe is a post-processing tool that allows visualization of any end point scaled curve
used in a simulation for a cell picked from a 3D model. The end points and saturation function
tables need to be available in the simulation output. In the Petrel 2011.1 release, this tool is
only available for recent versions of the ECLIPSE simulators. By default only the scaled
quantities are reported in any INIT file generated. To display the actual end points used in the
simulation for each grid cell, the FILLEPS keyword must have been added to the ECLIPSE
input files.
EPS Settings
X-axis Choose one phase from Oil, Water, or Gas for the saturation axis.
Y-axis Choose one or more of the relative permeability (KR*) or capillary pressure (PC**)
curves. W stands for water, O stands for oil, and G stands for gas, so KRW is the
relative permeability to water and PCOW is the capillary pressure between the oil and water
phase.
Water: KRW, KRG, KROW, PCOW

Oil: KRW, KRG, KROW, KROG, PCOW, PCOG
Gas: KRW, KRG, KROG, PCOG
Scaling method Display the curves scaled using the same method as in the simulation.
Also explore the effect of choosing the alternative method by selecting that checkbox in the
probe.
o
KRW: The critical water saturation (SWCR) and maximum water saturation (SWU,
the largest water saturation in a water saturation function table).
KRG: The critical gas saturation (SGCR) and maximum gas saturation SGU.
KROW: The critical oil-in-water saturation (SOWCR) and (1.0-SWL-SGL), where SWL
and SGL are the connate water and gas saturations, respectively.
KROG: The critical oil-in-gas saturation (SOGCR) and (1.0-SWL-SGL), where SWL
and SGL are the connate water and gas saturations, respectively.
3 Points Preserves the relative permeabilities at three saturation nodes. The following
end points are used:
KRW: The critical water saturation, (1.0- critical oil-in-water saturation - connate gas
saturation), and the maximum water saturation.
KRG: The critical gas saturation, (1.0- critical oil-in-gas saturation - connate water
saturation), and the maximum gas saturation.
KROW: The critical oil-in-water saturation, (1.0- critical water saturation - connate
gas saturation), and (1.0 - connate water saturation - connate gas saturation)
KROG: The critical oil-in-gas saturation, (1.0- critical gas saturation - connate water
saturation), and (1.0 - connate water saturation - connate gas saturation).
In gas-water runs, the following end points are used if the second form of relative
permeability scaling is selected:
160
Schlumberger Public
2 Points (Default option for the ECLIPSE simulator.) Preserves relative permeabilities
at two saturation nodes, that is, the two end-points. The following end points are
assumed for each relative permeability phase:
KRW: critical water saturation, (1.0- critical gas saturation), and maximum water
saturation.
KRG: critical gas saturation, (1.0- critical water saturation), and maximum gas
saturation.
Curve Options and Directional Relative Permeabilities Select which types of curves
to display using the checkboxes in this section. Your simulation must contain the feature in
order to display the corresponding curves. For example, you need a simulation that is using
the dual porosity-dual permeability model in order to display matrix or fracture curves, and
you need a simulation with an X-directional relative permeably curve defined to be able to
display the X+ scaled curve.
Visualization and Quality Control of Vertical Flow

Performance Tables
The VFP Manager is accessible from the Input pane by right-clicking the VFP (Hydraulics
tables) folder, or a subfolder, or hydraulics table within it.
The VFP Manager window has three panels. The left panel contains settings for the current
display and quality check options. The central panel contains a plot of the currently selected
view of the selected table. The right panel contains a table of the plotted data values.
161
Schlumberger Public
Vertical Flow Performance (VFP) tables for wellbore hydraulics are used to model the pressure
drops between the bottom hole and tubing head as a function of the flow conditions of the
wellbore. This information is used by the simulators to calculate tubing head pressures, by
interpolating these tables at the current flow conditions of the well. The VFP Manager enables
the visualization and editing of the VFP table as a function of the many variables involved
(pressures, liquid rate, water fraction, gas-oil ratio, or artificial lift quantity). The user may also
perform a quality check on the VFP tables in the Petrel project, to identify non-physical or
inconsistent data which may cause problems in the simulator.
VFP Manager Display Settings
Interpolated variable description: The variable to plot on the Y-axis of the VFP plot. This can
be either:
BHP (the well bottom hole pressure) or

BHP-THP (the pressure drop between bottom hole and tubing head).
Primary variable description: The variable to plot on the X-axis of the VFP plot.
Family variable description: The variable that will be shown independently in a VFP plot.
Fixed variables: Fixed variable values. These define which variables should stay fixed when
the table is visualized, and at what values they should be fixed.
162
Schlumberger Public
Display and Quality Check Option Panel
The variable settings depend on which variable is defined in the data input file. The variables
are from the following classes:
Flow
Pressure
Gas fraction
Water fraction
Artificial lift (optional)
These are the options:
Flow
Gas Fraction
Artificial Lift
Compositional Models
wet gas volume rate
total molar volume rate
water to wet gas ratio
water moles to total moles
fraction
gas to oil ratio

mean molecular weight
gas to liquid ratio
oil to gas ratio
Lift gas injection rate: lift gas injection rate
Lift gas liquid ratio: lift gas to liquid ratio
Total gas liquid ratio: total (lift and produced) gas to liquid ratio
Pump Rating: pump rating
Compressor power: compressor power
Oil density: surface density of oil
Gas density: surface density of gas
Chock diameter: choke (or bean) diameter
Hydraulics device value: setting for a general, unspecified device
VFP Quality Control Tools

There are three quality control tools available in the VFP Manager:
Apply stability transform. The transformation examines whether there is an unstable low
flow section of any J shaped curves in a production table, and will replace this section with
a horizontal line at the minimum BHP value, from the lowest flow value to the flow value at
minimum BHP. Although the effect of this transformation is not physically realistic, users
often find it useful to run the simulator with a VFP table in which there are no unstable
curves.
163
Schlumberger Public
Water Fraction
Black Oil Models

oil volume rate
water volume rate
water volume rate
water to oil ratio
water cut
water to gas ratio
NOTE: Use the stabilization option with caution. It may give misleading results for
the simulator well model at low flow rates. Simulators may contain an option that
shuts in any wells that are operating in the stabilized region at the end of the time
step. This prevents the simulation of wells as operating to be continued when
physically they could not do so.
Check for crossing curves. This option allows you to check the selected VFP table for
pairs of curves of BHP vs. flow at different THP values (but the same WFr, GFr, and ALQ
values) that cross each other
Check for high pressures. This option triggers a scan of the selected VFP table for any
BHP values greater than +1.0e10 (denoting choked or supersonic flow if the tables have
been produced by the VFPi application) and less than -1.0e10 (denoting compositional fluid
property calculation failure flow if the tables have been produced by the VFPi application). A
pop-up dialog allows you to change these pressure values. We recommend that the
defaulted 1.0e10 pressures be changed to a value slightly above the maximum expected
reservoir pressure. This should prevent the well conditions from entering the supersonic
flow region without having a drastic effect on the well behavior around the highest
physically reasonable flow value points.
164
Schlumberger Public
Compare Two VFP Tables

An option for comparing two VFP tables may be useful when comparing tables before and after
a quality check transformation has been applied to a table. These should be the same types of
table (production or injection). Only the primary VFP table is editable, though the secondary
table is plotted.
Plot Panel
The central panel in which the VFP curves are plotted has a number of tools in a toolbar at the
top of the panel.
When the Viewing Mode tool is active, the mouse pointer will be displayed as a hand in
the Display window. This allows you to move the curve.
With the Zoom tool active, you can magnify and then zoom into the curve by dragging a
zoom box around the data of interest.
Use the Copy Bitmap tool to produce a bitmap image that is temporarily stored in the
Windows clipboard. This can be pasted, for example, into Microsoft Paint, PowerPoint, or
Word.
Use the View All tool to view the whole plot.
Use the Show/Hide Grid tool to view or hide the grid in the whole plot.
Use the Edit Points tool to select and edit individual points in the plot. Points are moved
vertically by clicking and dragging.
VFP Table
The VFP table contains the values of the active primary variable and the value of the family
variable at each interpolated variable. Each family variable point inside the table can be edited
manually. These changes will only be saved after clicking the Apply button.
Simulation Results Analysis

Line-Plotting Workflows
The ability to override the auto-line styling logic has been restored in Petrel 2011.1. For each
element of the line style, the user can choose whether to take the style from the auto logic, the
source, the identifier, or the vector. This can be combined with the ability to independently
select the auto show options for simulation, observed, and dev start data.
165
Schlumberger Public
Standard Summary Plotting Workflows

Petrel provides a library of standard summary plotting workflows. These workflows can be
accessed by right-clicking the Workflows pane and selecting the Add standard summary
plotting workflows option.
The set of standard plotting workflows provided can be extended and modified to create a
customized set of powerful plotting workflows.
Example Plotting Workflow

The following steps describe how to create a multiple viewport plot displaying production rates
for an arbitrary well in your project.
1. Right click in the Workflows pane and select the Add standard summary plotting
workflows option. The standard workflows folder will be added to the Workflow pane.
2. Right click a well of interest in the Results pane, and hover over the Drop into workflow
menu item to see all available identifier drop-in enabled workflows. Hover over folders to
see the available workflows inside.
166
Schlumberger Public
When you select this option, a folder of standard plotting workflows is added to the Workflow
pane of the current project. The standard plotting workflows are drop-in enabled (see the
example plotting workflow, below), and workflows use the new style of plotting commands
introduced in Petrel 2011.1, which automatically select the subjects on the relevant pane. As
such, they are available for execution when you right-click any source in the Cases or Results
panes or any identifier in the Results pane. It is possible to scroll down through cases or
identifiers in the pane to update the plot. The Visualization follows selection option must
be checked. This option is found from the Tools Menu, the System Settings option, and the
Effects tab.
3. Click to select the desired workflow. For this example we selected

Standard Workflows -> Well/group -> General->Production performance 4
ports. The corresponding workflow is executed, and the resulting plot is displayed in the
function window.
Schlumberger Public
Drop-in Enabled Workflows

Drop-in enabled workflows make it simple to drop different sources and identifiers (for example,
case and wells) into workflows and to enable simple execution of the workflow. This feature is
particularly useful when constructing plotting workflows within a project containing multiple
sources or identifiers.
In the Workflow editor, the Set summary source reference and Set summary identifier
reference commands are used to include particular sources or identifiers in a plotting
workflow. These commands have an additional Enable drop-in check box. When the Enable
drop-in option is checked for either the Set summary source reference or Set summary
identifier reference commands, the workflow becomes available for execution when you
right-click any source in the Cases pane (for sources) or the Results pane (for identifiers). The
Drop into workflow menu item is then displayed, and hovering over this menu item shows all
workflows that are drop-in enabled. Clicking a drop-in enabled workflow drops the selected
source or identifier into the workflow at all instances of the Set summary source reference
or Set summary identifier reference command, and the workflow is executed.
167
NOTE: This additional drop-in will only be performed if the Set summary
identifier reference command does not already contain an identifier. If no
identifier is active, then the first well in the Wells folder (in the Results pane) will
be used. Dropping an identifier into a workflow will have the additional effect of
dropping the active source into the workflow, but only if the Set summary
source reference command does not already contain a source. If no source is
active, then the first Case in the Cases pane will be used.
Autogenerated Workflows
These workflows reproduce the summary data in the active function window. The
Autogenerate workflow button in the Workflows editor has been simplified from five to
three choices. These workflows choices recreate any simulation summary data plotted in the
currently active function window. The three Petrel 2011 choices are summarized below:
168
Schlumberger Public
When a workflow contains both the Set summary source reference and the Set summary
identifier reference commands, and both have Enable drop-in set, the workflow will be
available when you right-click sources and identifiers. In this case, dropping a source into a
workflow will not only drop the selected source into the workflow at all instances of the Set
summary source reference command, but also have the additional effect of dropping the
active identifier into the workflow at all instances of the Set summary identifier reference
command.
In Petrel 2011, autogenerated workflows are simplified to three choices (above).

Five options were available in Petrel 2010 (below).
Reproduce the summary data in the active function window Opens a second
window in which you can control which elements of the plotted data are factored out into
workflow variables and whether to use the Set visible or Add summary line commands
to add the data to the plot. This option maintains the other 2010.1 autogenerated plotting
workflow options. This option also allows you to successfully create an automated plotting
workflow in the rare case that there are more variables required than the Petrel limit of 52,
which would mean that the following two workflow choices would not be possible.
Reproduce the summary data in the active function window: Add Summary data
line command Functions the same as the Petrel 2010.2 option labeled Reproduce all
summary data in the active function window: factor out all items.
Reproduce the summary data in the active function window: Set visible
command Creates workflows similar to the pre-canned workflows. You have less precise
control over the plots created using the Set visible command, since you are not adding
individual lines to the plot. But for many common plots, the resulting workflow is readily reapplied to new cases, wells, or summary vectors through the Petrel 2011.1 drop-in enabled
workflow commands described above.
Dual Porosity Simulation Results View

The Dual porosity simulation results view allows simultaneous plotting of matrix-fracture
3D simulation results. The display shows the matrix value in the centre of the cell face and the
fracture value as a surround. This sugar cube display is available for matrix-fracture 3D
simulation results displayed in the 3D window, the 2D window, and on an intersection plane
within the 3D window. It is not available in the intersection window itself, the map window, or
the inter-well background on the well section window.
169
Schlumberger Public
To display a dual porosity simulation result:

1. Open a 3D window.
2. In the Cases pane select a case, then on the Results pane select a matrix or fracture 3D
simulation result. Petrel detects the complementary result and displays both results as a
sugar cube plot.
It is also possible to disable the feature from the Simulation grid results folder.
1. In the Results pane, right-click the Simulation grid results folder.
2. Select Settings.
3. Deselect the Enable dual porosity plot option on the Style tab.
Schlumberger Public
170
Visualize Production and Injection Allocation Data from Streamlines

For FRONtSIM simulations, you can visualize the allocation attributes on streamlines and see
where the contributions have come from.
Schlumberger Public
Solution Probe
The multi-value probe has been extended in Petrel 2011.1 to offer a new graphical mode to
view time-plots of simulation results extracted from RESTART format files. To use the feature:
1. Drop dynamic 3D simulation results into the multi-value probe table.
2. Click the Show graphics probe button, which is located in the bottom right corner.
3. Select a cell in the 3D window. The system will plot values of the cell over time.
4. Select the Copy time probe check box and click the Copy to outputsheet button to see
the graphics probe values in an output sheet.
171
NOTE: Updating the plot may be slow the first time. This is because the system
must load all the required 3D simulation results for all the time steps. After the
data has been loaded, the next update will be faster.
Summary Data in the Histogram Window

When you select a single case, you get a different series plotted in the histogram window for
each property selected. For each series, results display for all the identifiers selected: for
example, selecting oil and gas production rates for all wells results in two series.
If multiple cases are selected, then these are further broken down into separate series. In the
example above, selecting two cases results in four series: oil and gas production rates for each
case. This allows for the comparison of different cases. This is different from Petrel 2010.1,
which merged the results of multiple cases into one data series.
172
Schlumberger Public
A basic tool set is available for interacting with the chart. This is found in the toolbar just above
the plot. The tools provide options for panning, zooming (select zoom or use the mouse
pointer wheel), picking (values display in the status bar of the main Petrel window), see all,
show grid, and copy bitmap to clipboard. This last option allows you to past the chart in
various other applications.
Finally, if you want to merge the results of multiple casesas in Petrel 2010.1then the cases
need to be placed in a case collection. A case collection will create a single series from all the
contained cases for each property. This allows you to display the distribution of the results
across many cases.
Well Section Window Enhancements
Simulation Log Display

In Petrel 2011.1, interactive display of simulated RFT and PLT logs in the well section window is
greatly improved. Many issues were resolved regarding display of simulation logs for different
cases. In particular, when you have multiple simulation cases with different well segmentation
setups, the segment PLT logs will be successfully and correctly displayed for each case.
Inter-Well Simulation Results Display
A new well section window allows you to visualize grid properties and 3D simulations results on
an inter-well intersection plane. This is good for visualizing water break-though and front or
plume movement between wells.
Use these steps to display a simulation property in the background:
1. Open a new well section window and click the Show Settings option. The Settings for
Well section template window opens.
2. Click the Background template object.
3. From the Add new object drop down menu, select the Simulation property object.
4. Adjust the settings to refine the display:
a. Set the template of the property.
b. Set the case to be used.
c. Delete any unnecessary properties.
173
Schlumberger Public
The fence display between wells in the Petrel 2011.1 well section window can display
simulation properties and results as well as seismic data and model structure. The display will
animate through time. This allows you, for example, to track fronts in 2D between injectorproducer pairs.
Schlumberger Public
5. Optional: In the Style tab, click the Show in the Grid lines option.
NOTE: Though optional, grid lines will not be displayed in the background if this is
left unchecked.
6. Click on wells in the Input pane. The selected property displays in the background.
7. Optional: Add a completions and a simulation track by editing the well section template
settings.
174
In the Petrel 2011.1 release, the behaviour for adding simulation logs which shared the same
template (such as gas rate and gas upstream rate) is consistent with other logs. By default,
when added to the well section window by ticking them, each log appears in a separate track.
You can move them into the same track or add additional logs to a track via the template
editor.
Miscellaneous
RESTART files larger than 2GB can be imported into both 32-bit and 64-bit versions of Petrel
2011.1.
In Petrel 2010.1, cumulative vectors (oil, gas, and water) displayed as bubble maps would
disappear through periods for which there was a gap in the reported production. In Petrel
2011.1 you can choose to extrapolate the cumulative values for these periods and therefore
keep the bubble maps displayed for all dates, including after the well has been shut. To use this
for a given cumulative summary vector, you need to turn on the new Extrapolate over
undefined values option for the individual cumulative summary vector in the dynamic results
data tree. To do this:
175
Schlumberger Public
Miscellaneous Behavioural Changes
1. On the Results pane, go to Results tree and open the Dynamic result data folder, then
the Cumulative folder.
2. Open the Settings dialog of the cumulative production vector of interest (double-click the
vector or right-click and use the context menu).
3. On the Style tab in the Advanced section, select the new Extrapolate over undefined
values option.
When a 3D simulation result displays, the property data for the specified time step loads into
memory. By default all loaded data is cached in memory so that the next time this time step is
displayed it will load faster. This can cause Petrel software to run out of memory when dealing
with very large result sets. This cache can be disabled by going to the Style tab in the
Simulation grid results folder and deselecting the Cache properties option.
Aquifers
Cells were inactive or had zero volume,

Cells had zero face area on the side of the aquifer connection (that is, the cells were
pinched out on the aquifer side).
Thermal Fluids, K-Values

For thermal simulations, correlations and tabular data are used to calculate fluid properties of
the liquid and vapor phases, including K-values, density, enthalpy, and viscosity. The Crookston
K-value correlation model can be used to create K-values for each hydrocarbon component for
both ECLIPSE and INTERSECT thermal simulations. In ECLIPSE the keywords are KVCR and
KVCRS. The model has 5 coefficients called A, B, C, D and E and relates the K-value to
pressure P and temperature T using the equation
K(P,T) = (A + B/P + C.P)e-D/(T-E)
In the Petrel 2010.1 release, the value input for D coefficient was interpreted by the Make
Fluids process and INTERSECT as an absolute temperature. This meant that the numerical
value was different when expressed in units of degree Centigrade and in degrees Kelvin, and so
the value exported to the simulator data files (in Kelvin) was different to the value (in
Centigrade) entered in the dialog. For example 200 deg C is exported as 473.1 K. However
users of ECLIPSE thermal through Petrel expected the D coefficient to be a temperature
difference. For a temperature difference, the numerical value is the same in degrees Centigrade
176
Schlumberger Public
Many changes were made to the aquifer process in Petrel 2011.1. These improve the set of
connections and improve handling of pinched out cells, undefined cells, faults, etc. This
changed the Petrel 2010 set of connections. Petrel 2011.1 removes connections that would be
present in 2010 for two reasons:
and degrees Kelvin. A difference in temperature of 20 deg C is a difference in temperature of

20 K.
Therefore in the Petrel 2011.1 release, the interpretation of the D coefficient provided in the
Petrel Make Fluids process dialog has been changed from an absolute temperature to a
temperature difference. Thus in Petrel 2011.1 the numerical value of the D coefficient exported
to the simulator data files (in Kelvin) is the same as the value (in deg C) entered in the dialog.
INTERSECT 2011.1 has also changed the interpretation of its input to be consistent with this.
Gridding Enhancements
Simulation faults that have been added to a grid can be deleted from the grid in Petrel 2011.1.
Upscaling Algorithms
Linear Boundary Condition

Linear boundary conditions are imposed by choosing a direction vector along the normal to a
surface that divides the grid block into two parts. This dividing surface is the arithmetic average
of the two opposing faces modeled as bilinear patches. This can be done three ways, leading to
three numerical experiments, one for each component of a diagonal permeability tensor. Details
of this method are provided in the online help manual.
The transmissibilities are calculated in the same way as in the ECLIPSE simulator, using the
NEWTRAN method.
Linear Boundary Condition: Adjoint Method

The adjoint method is very similar to the linear boundary condition method, but it has the
potential to be nearly three times faster. Only one flow-like simulation is performed rather than
177
Schlumberger Public
New flow-based upscaling algorithms from the Flogrid application were added to Petrel 2011.1.
These are accessed by choosing the Flow-based upscaling (advanced) option.
The advantage of using this method is that the flow simulation is more realistic and accurate in
a target cell. There are some limitations:
it is available only with the All Intersecting Cells sampling method,
skin cells are not supported,
NTG and porosity are not used.
the usual three. Details of this method are provided in the online help manual.
Linear Boundary Condition: Full Tensor
No Side-Flow Boundary Condition

No-side-flow boundary conditions impose a constant pressure on one face of the block and a
different constant pressure on the opposing face. The other four sides of the block are subject
to no-flow boundary conditions. There are three different ways of applying these boundary
conditions, providing three independent numerical experiments for the components of a
diagonal permeability tensor. This method is approximate unless the grid blocks are
rectangular. The transmissibilities on irregular grids are slightly different between this approach
and the NEWTRAN method used in the ECLIPSE simulator. More details of this method are
provided in the online help manual.
Global Coarsening Utility

The new Global coarsening process is located under the Utilities folder on the Processes
pane. It provides a simple method to generate a tartan grid. Such grids will have a refined area
in the polygon that represents the region of interest, surrounded by a coarsened region outside
the second boundary.
178
Schlumberger Public
The full tensor method is similar to the linear boundary condition method, but it allows all six
components of the permeability tensor to be extracted. This option cannot be chosen when
overwriting an existing tensor, as the number of components is already implied by the tensor
selected for overwrite.
How to Perform a Global Coarsening Run

1. Input a grid from the Models pane using the drop zone in the UI.
2. Drop coarsening and refining polygons into their respective drop zones. Ensure that the
coarse polygon completely encompasses the refine polygon.
4. Enter the coarsen and refine skip setting. The I coarsen and J coarsen options help the
algorithm skip the I and J pillars in the original grid. The I refine and J refine settings help
decide how many pillars need to be inserted in the original grid.
5. Click the Apply button. The resulting grid should display on the Models pane after the
algorithm executes and completes.
179
Schlumberger Public
3. The outer polygon is used to clip the boundary of the original grid to form a new one. The
plug-in can be used for clipping grid or for coarsen and refine operations.
Schlumberger Public
Well Engineering
Completions
Precision of Exported ECLIPSE Completion Keyword

Petrel 2011.1 exports COMPDAT Item 8 (the Transmissibility factor for the connection) in
scientific format, to maintain precision over the wide range of magnitude of values.
Extensions to Tubing File Format

The tubing description file provides information about the characteristics of well casing and
tubing as well as the locations of packers, chokes, and inflow control devices. The tubing file
format has been extended for Petrel 2011.1. The updated format is described in the online help
manual and includes examples and explanations of how the items are interpreted when
imported into Petrel. The following features are new to the Petrel 2011.1 release:
180
The format can specify completions attributes by identifying which equipment from the
Petrel equipment catalog should to be used, rather than providing explicit values in the file.
A BULLPLUG keyword has been introduced to represent sealing the end of tubing, for
example in a completion that uses ICDs to control inflow.
Suppressing Annular Segments

In unconsolidated formations, the material frequently collapses into the annulus. In Petrel
2011.1 you can now model this situation. For example in ICD type workflows you can do this by
suppressing annular segments for multi-segmented wells. This causes Petrel not to model flow
behind tubing, where flow passes through an inflow valve downstream. This can also be used
to reduce the number of segments in the well and so speed up the simulation.
Schlumberger Public
NOTE: With annular segments suppressed, all cell connections in the flowing
interval are connected directly to the inflow valve segment node. For the option to
work correctly, flow must pass through an inflow valve. The option will not work
correctly if, for example, the flow is allowed to loop around the end of the tubing.
Block the flow up the tubing by adding a bull plug to the tubing via the
Completions manager.
181
Individual Control of Displayed Items within a Well

In the new well section window, Petrel 2011.1 has re-enabled control over individual completion
items. As with Petrel 2009.2, it is possible to toggle individual completions on and off by
selecting the check box in front of each one. For Petrel 2011.1, however, you need to start by
toggling on the Global completions folder.
Known Limitations:
When a project is saved and reloaded, it does not remember the state. That is, all
equipment will be displayed according to the global completion.
If you uncheck equipment and then use the time player, the hidden equipment is shown but
the check box is not updated.
You cannot display all the completions of a specific well at once when selecting the
completions folder check box.
When refreshing, toggling the well folder on and off will not select all the completions
previously displayed.
Multiple Record Selection in Completion Manager

Multiple records can be selected from the navigation table using the CTRL and SHIFT keys;
the attributes that are common to all the selected records will be visible in the Details table.
Changing the value of attributes in the Details table will change the value of those attributes in
all selected records. If the common attribute has different values, it will be empty in the Details
table.
The common attributes in the Details table has different colors, depending on the selected
records:
WHITE The common attribute of all selected records are editable and have the same
value.
GREEN The common attribute of all selected records are editable but have different
values.
GREY The common attribute of one or more of the selected records are READ ONLY.
YELLOW The common attribute of all of the selected records are overridden.
WELL COLOR The color of the well name attribute of all the selected records. If they
have different colors, they will be GREY.
182
Schlumberger Public
Move Well
Move well is a new method in the Create wells tab in Well Path Design. Given a well or a
folder of wells, the Move well option will create a shifted well or wells. You specify the option
to shift the well in X, Y, and Z or by constraining surfaces as minimum input. The output is a
well translated using the inputs. If the input well has laterals, the whole unit of wells and
mother-bore get shifted using the provided inputs. After selecting the option to fix the main
well, only the well that has been dropped into the input drop-zone and its laterals will get
shifted holding the tie in point fixed.
Trajectory Constraints
The output well trajectories are constrained by a user defined DLS. The default fallback option
of this algorithm is a piecewise linear well, when DLS constraints fail to generate the desired
well.
183
Schlumberger Public
Well Placement
How to Make a Move Well Run

1. Open the Well path design process and select the Move well option.
2. Select either the Create new or Edit existing check box.
3. Drop a well or folder of wells.
4. As necessary, enter settings for the translation in X, Y, and Z or limit the surfaces.
5. In the DLS tab, specify the desired DLS constraints.
6. In the Create wells tab, click the Make run button.
7. View the shifted wells by selecting them from the Input pane in the specified output folder.
Schlumberger Public
184
Open the well path design process and select the Move well option, then select either the
Create new run or Edit existing option.
Shift Well
You can shift the well in X, Y, and Z directions. This means applying a constant translation
vector along X, Y, and Z for all the design points and trace points of the well.
185
Schlumberger Public
Move Well Settings
Limiting Surfaces
You can constrain well target points between two geometric surfaces, upper and lower. A
geometric surface is defined as:
A surface,
A constant.
If you specify the same geometric surface for the Upper and Lower options, the system will
snap the well to that surface. If the Upper and Lower surfaces are intersecting, or if Lower is
above Upper, then the system will swap surfaces.
Collision Detection
If this option is enabled, you must specify a well or well folder and a safety distance. The
system checks that the minimum distance between the created well and any specified well is
greater than the safety distance. If a collision is detected, a warning message is logged.
186
Schlumberger Public
You can check whether the created wells collide with existing wells. If the distance between two
wells is smaller than the specified safety distance, then these wells are colliding.
Fix Well Head

This option is used to fix the wellhead or the tie-in point of the input well while moving the
remaining trace points and design points with the shift operation. The option is disabled for a
folder input. The input well for the process acts as the agent for making the decision on the
option to fix the points. If the dropped well is a lateral, when you fix the well head the tie-in
point for the lateral is fixed and all parent wells and motherbore associated with the lateral are
ignored by the Move process. Only the input lateral and all laterals connected to it are moved.
When you enable the option with a motherbore as the input well, the well head remains fixed
and all other associated wells are moved using the well move algorithm.
Schlumberger Public
187
Simulation Data File Management

Relinking the Simulation Folder
You can now externally relocate the simulation case data and then reconnect to it from the
Petrel project. There are three components of a Petrel project that are, by default, located in
the same directory:
Project file - xxxx.pet

Project data folder - xxxx.ptd
Simulation data folder - xxxx.sim
Keeping these components together makes it easier to manage the simulation data. In some
circumstances, however, it may be more appropriate to store simulation data in a different
location. An example of this is when simulations will be run remotely on cluster and the case
files need to be accessible to both Petrel and the simulator program. To accommodate such a
configuration, Petrel 2011 allows you to override the default location for the .sim directory.
NOTE: You must reopen the project for the changes to take effect. Continuing to
make changes to the project without reopening may cause inconsistent data.
Each project must have a unique simulation data folder. Two projects cannot share the same
simulation data folder. If you attempt to link two projects to the same simulation data folder,
Petrel will display an error.
Relink to the Simulation Data Folder for Unmanaged Cases

When you are only using Petrel to load and visualize results for simulation or to run simulation
without converting to Petrel case, the location of the simulation data is not generally in the
simulation data folder for the project.
If the location of the data for such cases has changed, you need to relink the project to the
simulation case in the new location. This can be done by right-clicking the case on the Cases
pane and selecting Settings from the pop-up menu. The new location for the case .DATA file
can be specified on the Info tab.
188
Schlumberger Public
To separate a project's .sim directory from its .pet and .ptd directories, first create a new
directory in the desired location or move the existing simulation data folder there. Next, open
the project and specify the new Simulation data folder location in the Misc settings 1 tab
under the Project settings dialog. When you save the changes, the project will re-link to the
simulation data folder in the new location.
If you have the simulation results but do not have the .DATA file, you can create a blank .DATA
file in the folder where your results are and link to the .DATA file.
Schlumberger Public
Simulation Case Export

The Define Simulation Case process is used to create and export a full simulation case. For
large models the export can be time consuming, particularly if the Petrel project is stored on a
remote disk. There are now enhancements that significantly improve simulation export
performance. This is default behavior that does not require any user action and cannot be
turned off.
Disk Space Usage and Export Time Reduction
Output of Grid files in GRDECL Format when Re-Exporting a Case

Many users select the GRDECL file format, which is very large compared to other available
binary formats and should only be used if the workflow being performed requires it. In Petrel
2011.1, the performance of exporting the grid in GRDECL format is significantly improved when
re-exporting a case. The grid geometry and property files are now written out only if the grid
189
data relevant to the specific file have changed since the previous export. This applies to export
of a local as well as a remote disk.
Output of Case Files over a Network when Re-Exporting a Case

The time to export over the network is now reduced, approaching local export times if the case
is re-exported without changes. Otherwise network export time exceeds local export time by an
amount dependent on the volume of files that changed. ECLIPSE case files are now copied over
the network only if they changed since the previous export. However, this requires temporary
copies of files to be written to the cache folder on your local machine. This enhancement
benefits both export of a single case from the user interface and export of a case from within a
workflow.
NOTE: In very special cases the local caching can be turned off, although this is
not recommended. Refer to the Editing the Configuration File Simulator Settings
section in the online help manual for details.
In the Define Simulation Case process there is an advanced option on the Transmissibilities
tab for turning on and off the Calculate and export transmissibility and pore volumes
option. When turned on, the export time increases significantly. This was true even when reexporting the case with no change to the underlying model. In Petrel 2011.1 this recalculation is
avoided if the model remains unchanged from the previous case export. Similarly, aquifer
connections are not recalculated during re-export, if the relevant model data remain
unchanged.
File Sharing for Unmanaged Cases

Petrel 2010 introduced sharing of case files between cases created using the Uncertainty and
optimization process or alternatively the Workflow editor. Depending on the size and
complexity of the model, as well as the number and locations of modifications, the disk file size
savings can be very significant. As an example, if changes are made to the PROPS section alone
(for example, relative permeability curves), the rest of the simulation data are shared and huge
savings can be achieved. If the 3D grid, its properties, or its structure are modified, fewer
savings can be achieved, since these data typically represent a large proportion of the
simulation data.
Petrel 2011.1 allows you to import an external simulation deck and to use it in uncertainty and
optimization workflows without converting to a Petrel case. Now Petrel only exports the files
containing modified keywords associated with every realization and shares the rest of the deck
with the reference case. The deck file sharing capability is extended to cases where the user is
190
Schlumberger Public
Recalculations when Re-Exporting a Case
only using Petrel to load and visualize results for simulation or to run simulation without
converting to Petrel case.
Partial Export
The new Partial export tab in the Define Simulation Case process tab allows you to
override export settings and is intended for situations when many simulations are exported
(such as using the Workflow editor or Uncertainty and optimization process).
CAUTION: This option is only for advanced users. You must be fully aware of the
implication of turning off export of part or parts of the simulation case.
In the Uncertainty and optimization process, you must not turn off sections in which
variables are defined. These sections need to be re-exported, as each realization uses
different numerical values for these variables.
When using GSG or OPF grid format, the grid and properties options are linked, as they
are exported to a single file.
If you change the permeability of the model and turns off export of development
strategies then the well connection factors will not be updated.
The checkboxes in the Partial export tab are all checked by default, meaning that the full data
input file will be exported. Deselecting any checkbox will prevent the associated part of the
model from being exported. A warning will appear in the Advanced tab to remind you of this.
A confirmation dialog also appears when you press Export, and a message is written to the log
whenever a partial export is performed.
191
Schlumberger Public
Exporting simulation cases of large models can be very time consuming. Often you make
specific modifications to certain parts of the model that do not require the entire model to be
re-exported. To speed up simulation case export, you now have the option to manually exclude
the sections of the deck that do not need to be re-exported. You may choose to suppress reexport of specific elements in the simulation case (for example, grid and 3D properties) that
have not changed in the Petrel model since the previous export. Turning off items (for example,
grid, 3D properties, or development strategies) will mean that they will not be recalculated or
exported. Instead, the files from the previous export will remain unchanged. For multiple
realization workflows these files will be shared between multiple simulation cases.
Precision of Values in Exported Keywords

The precision of the values for data exported to keywords in simulator data files (that is, the
number of decimal places with which the numbers are written in the files) are in general
controlled by the precision of the template for that property. This is unchanged in the Petrel
2011.1 release. In particular this means that when an existing ECLIPSE data file is converted to
a Petrel case and re-exported, the exported keywords use the Petrel precision, not the original
precision in the original ECLIPSE data files.
In most cases the default export precision is sufficient. In some cases where there are very
small but non-zero values that have a critical influence on the simulation, for example end
points for saturation functions or permeabilities in tight formations, the default precision is
insufficient. In these cases you can go to the Templates pane and edit the settings of the
appropriate properties templates. On the Info tab of a template, change the Show numbers
with field to the required number of decimal places.
Mixed-Vendor Workflows
It is preferable to create (or convert) and then maintain the complete simulation model within
the Petrel software; the Petrel application has been designed as an integrated environment, and
the simulation workflows and data management work best and most productively when used in
that way.
The Petrel software is used, though, to add data to simulation data files that have been created
and are maintained outside of the Petrel environment.
The figure below shows the origins and axes that are the default for the XYZ coordinate axes
and the IJK grid cell numbering in Petrel and default for ECLIPSE, with corresponding settings
for the coordinate system origin. The orange settings are the default export settings in Petrel,
that is, they match the default ECLIPSE convention. The ECLIPSE IJK and XYZ axes and the
Petrel XYZ axes are all right-handed systems (recall Petrel has Z as elevation, not depth).
192
Schlumberger Public
For the Petrel 2011.1 release, the default export precision for PERM(XYZ) properties has been
changed from 2 to 4 decimal places. This allows you to better capture low but non-zero
permeability regions. This change in precision may return up to a 1% difference in simulation
results compared to Petrel 2010. To revert back to old behavior, you can edit the Permeability
templates in the petrophysical properties folder of templates.
Therefore for most users the export of simulator data files and keywords works in either the allin-Petrel or the Petrel-as-data-file-updater environment, and the following advanced import and
export setting options are not of direct interest.
Sometimes Petrel is used in a multi-vendor environment in which externally created simulator
data files may not share the default grid origin and grid cell traversal order conventions that
Petrel uses or that ECLIPSE uses. This can lead to issues with the IJK indices and XYZ
coordinates in the Petrel exported keywords not matching the original data files. The Petrel
2011.1 release offers increased flexibility for handling grid and property import coordinate
systems that can be used in these circumstances to support specific workflows. An example is
using Petrel to design and add a new multi-segmented well to an external simulation model
where the grid and existing grid-related data does not use the default ECLIPSE conventions.
Since Petrel calculates the connections and connection factors between the grid and the wells
during the export of a case using the Define Simulation Case process, you need to be able to
193
Schlumberger Public
Petrel software, by default, exports ECLIPSE simulation data files (from the model tree or from
the Define Simulation case process) using the ECLIPSE default XYZ coordinate system and the
ECLIPSE default IJK indexing convention. Petrel defaults to visualizing grid cell numbering in the
right-handed ECLIPSE convention (orange settings), so by default again you will see IJK indices
in the Petrel status bar reported as such.
export partial data files using the Define Simulation Case process with IJK and coordinate
values that match the rest of the external data files.
Export
There are two places where you can define the relationship of the IJK origin and grid cell
traversal order used by Petrel for how you want your data files exported to the simulator:
From the Eclipse export settings dialog accessed from the Project menu or the
export dialogs,
From the Export to simulator and visualization tab on the Settings dialog of a grid
(the orange-outlined tab in the figure above).
The settings on the Eclipse export settings dialog are used when exporting a grid and
properties from the Models tree using the Export menu and the ECLIPSE export formats.
In 2011.1, the settings on the Export to simulator and visualization tab on the Settings
dialog of a grid are now also used during the export of a case using that grid from the Define
Simulation Case process.
CAUTION: Exercise care when using this facility to change the exported
simulation case data files. It alters the I and J indexes of other keyword
information such as COMPDAT, FAULTS, and AQUCON. The traversal order
affects the order in which the grid property values are written within the grid
property keywords. If a partial case export is performed with the traversal order
set to J first, Petrel will check to see that certain processes such as Flux Boundary
on sector models are consistent with the new setting, and if not, Petrel will force a
recalculation of these items. However this level of self consistency checking is not
universal, and you are strongly advised to check the I and J parameters in all
keywords in the data input file you want to use.
Import
Petrel 2011.1 detects data files using a left-handed coordinate system, that is, files that are not
following the ECLIPSE default coordinate system. There are new advanced options on each of
the ECLIPSE keyword import dialogs that give you some control over how Petrel transforms the
194
Schlumberger Public
In 2010.1, the settings on the Export to simulator and visualization tab on the Settings
dialog of a grid were only used to control how the grid was displayed in Petrel; it did not affect
the export. This allowed you to import into Petrel the results files from simulation data files that
did not use the ECLIPSE defaults, and then see the expected grid. The Define Simulation Case
continued to export using the default ECLIPSE origin and traversal order.
grid XYZ coordinates and IJK coordinates on import. The appropriate choice will depend upon
the specific hybrid workflow that you are doing and the source of the original data files.
A new keyword, GDORIENT, written by ECLIPSE 2011.1, records the traversal order of
properties in IJK space, the Z-axis direction, and the grid handedness of the grid containing the
properties in the ECLIPSE file. Petrel 2011.1 can read this keyword and will issue warning
messages if it does not conform to the ECLIPSE conventions.
Simulation Summary Results Loading

Summary File Format
Requesting Summary Data

The recommended workflow is to make the conversion to the enhanced summary file format
part of the simulation submission job rather than via Petrel. For further information refer to the
Enhanced Summary File Format section of the online help manual.
Conversion-Related Work Steps in Petrel

When you load a Petrel project, including legacy projects, Petrel checks whether conversion is
needed. If so, the conversion process to the new file format is started in the background
without impeding Petrel itself. The names of individual cases being converted appear in red font
followed by (summary conversion being active...) as shown below.
195
Schlumberger Public
The simulator output for summary results in the form of *.(F)SMSPEC and *.A/Sxxx files reflects
the way the simulator solves the mathematical equations for increasing time. Accessing the
data for a particular summary vectorusually for plotting against timerequires the entire data
set. This access pattern is poorly supported by the simulator output mentioned above,
especially if the data is located on a network drive. In effect, accessing summary data often
results in high access times over network connections. This is the primary motivation behind the
introduction in Petrel 2011.1 of a new, enhanced file format for storing summary data.
Requesting summary data using this new file format will result in greatly increased access
speeds via network connections.
NOTE: You should not access summary data for a case during the conversion
process, in case the data is stored on a network location. Although possible, you
will not benefit from increased summary data performance until the end of the
conversion.
If you decide not to use the enhanced summary file format for a particular case, open its
settings dialog by right-clicking the case, activating the Results import tab, and deselect the
Use enhanced summary file format option. The checkbox location is shown in the following
figure.
If this option is greyed out, Petrel either hasn't found any summary data for this case, or the
option has been unchecked on the Results import tab on the case (see above).
You will notice several messages in the message log explaining the process.
Plotting Plots and Graphs

Thanks to the enhancements done in the summary file formats, importing data and plotting it in
Petrel 2011 is faster than in previous versions. The following two figures show the effect of the
optimization of the results loading and plotting algorithms in Petrel 2011.1
196
Schlumberger Public
Generally Petrel will make sure the enhanced summary file format is being used and updated.
However, you have the option to enforce conversion by right-clicking a simulation case, case
folder, or case collection. On the resulting pop-up menu, select the Convert summary data
into enhanced summary file format option.
20
18
16
14
12
10
8
6
4
2
0
Speed X
Up to 20X
6X
Speed
1X
Petrel 2010.1
Office
Petrel 2011.1
The figure above shows the speedups measured when loading simulation results over a network using the new summary file
formats in Petrel 2011.1. The actual speed you observe will depend upon the model and the network characteristics
40
Schlumberger Public
Speed X
Up to 40X
35
30
25
20
Speed
15
10
5
1X
3X
Petrel 2010.1
Office
Petrel 2011.1
The figure above shows the speedup measured when plotting simulation results from a shared disk using Petrel 2011.1. The
actual speed you observe will depend upon the amount of summary data you plot and the network characteristics.
197
Studio
For a discussion of the new, customizable Studio Favorites pane, see the General section of
this document.
Studio Annotate
Studio Annotate gives you a new and unique capability to enrich your project by adding content
in the context of workflows and data. Content and knowledge, in context, can be shared and
manipulated among team members through the Reference Project Tool (RPT). RPT-based
workflows provide a richer, more intuitive collaboration experience. Any type of file (sound,
document, PDF, video, etc.) or note (formatted text, embedded picture, hyperlink) can be
added.
198
Schlumberger Public
These are the primary features of Studio Annotate:

Link any type of file (sound, document, PDF, video etc.) to any object in Petrel through
identification of a spatial position (X, Y, Z in the current project CRS) on the Petrel
object.
Tag written notes (formatted text, embedded pictures) to any object in Petrel through
identification of a spatial position on the Petrel object.
Link hyperlinks to any object in Petrel through identification of a spatial position on the
Petrel object.
Turn on or off icon-based representations of files, notes, or hyperlinks on objects
represented in your 2D and 3D windows.
Open, edit, or save files or hyperlinks associated with objects in Petrel.
Preview available notes in 2D and 3D windows.
Manage (export, delete, etc.) and browse notes, files, and hyperlinks through the
convenient Annotate Manager or from the Petrel Input pane
Transfer notes and annotations between projects using the RPT, to share and expand
knowledge across the asset.
Figure S1. Example of an annotated Petrel project.
1. Display the Petrel object you want to annotate in a 2D or 3D window.

2. From the Annotate toolbar, choose what type of annotation you want added to the object:
file, note, or URL. In this example we choose to make a URL annotation.
3. Choose the spatial location on the object. A dialog appears asking for details of the URL,
note, or file you are attaching to the object. The dialog is different, depending on what you
are attaching. See figures S2 and S3.
Figure S2. Sample note editor dialog in Studio Annotate
199
Schlumberger Public
How to Use Studio Annotate
Figure S3. Sample URL attachment dialog in Studio Annotate
An Annotate object is appended to the Petrel Input pane, under the Annotate folder. In
addition, an icon is added to the current display to visually locate the new object. Notes also
include a preview mode (see Figure S1).
4. Use Annotate Manager
to perform the following tasks, as needed:
Turn on or off all Annotate objects in the 2D and 3D windows displayed.

Export, delete, or otherwise manage Annotate objects.
200
Schlumberger Public
Figure S4. Sample Studio Annotate folder
Studio Find
Studio Find provides a revolutionary new way to quickly and transparently browse Petrel data
throughout a company in a seamless and intuitive manner. Data can be smartly filtered to focus
on specific data and context of interest, and then imported for rapid project startup and project
knowledge. The learning curve for Studio Find is negligible, since it is similar to the latest Web
browsing techniques used by so many on a daily basis.
Studio Finds intuitive interface facilitates searching, viewing, filtering, and retrieving information
from any of the following three areas of Petrel, even if you dont know where specific
information is stored:
Reference projects and ordinary Petrel projects that exist on your local machine,
Reference projects and ordinary Petrel projects that exist anywhere within your
company intranet,
The Studio Knowledge Database.
Studio Find offers these key benefits:

Map layer integration into the 2D and 3D canvases to facilitate intuitive browsing of data
on GIS layers from any Web or ArcGIS map-based service.
Filter based groupings of search results according to the familiar Input pane structure,
by project or object.
Dynamic, interactive, and combinable filters (by keyword, datatype, project, template,
depths, date range, color, users, etc.).
Real time data refresh when filters are applied to search results.
Zooming and panning with or without map-based layers, resulting in increasing or
decreasing levels of graphical and object detail and attribute-based information.
Ability to load data returned from your search results directly into your local project.
201
Schlumberger Public
After finding the information you need, you can import it into your local project and continue
working. Studio Find integrates natively in Petrel with simple, intuitive, end-user interfaces and
provides easy, stand-alone administration tools for configuring and managing access to relevant
knowledge repositories.
How to Configure Studio Find

1. To search projects and update data available for search on your local machine, each project
must be opened and the Update search index option selected. Those projects are then
added or updated in your local search storage.
Figure S6. Update Studio Find search index
202
Schlumberger Public
Figure S5. Example of Studio Find
2. To search projects on network drives, publicly available locations, or database instances,

use the Search Settings dialog. This dialog provides the option to connect to a
configuration file that contains one or more data environments. Each data environment can
contain one or more Petrel or Petrel reference projects and a single database repository.
3. Use the Search Settings dialog to define what configuration file (specifying what data
environments you want to search across) to connect to. The configuration file can be
defined by an administrator in your organization using the Data Environment Manager.
Figure S7. Studio Find Search Settings dialog.
1. On the Search toolbar, click the Search button next to the search field. You can leave the
search field empty or specify criteria using specific keywords in the search text box.
Search panes, by default, display all data in the project if no keyword information is initially
supplied. The following search filters are available:
Keyword Find data by typing in a keyword, using * for wildcard.

Similarity Find data which has same properties as a selected item.
Datatypes Find data with a specific datatype.
Spatial Find data in a certain geographic area.
Template Find data according to a specific template.
Maximum Depth Find data with deepest depth in a given range.
Depth Find data with a given depth range.
Date Range Find data which has been modified in a certain date range.
Color Find data which has a specific color.
Projects Find data from a specific project.
Users Find data which has been modified by a specific user.
Sources Find data indexed in a specific index.
203
Schlumberger Public
How to Use Studio Find
Domain Find data indexed in a specific domain.

Well logs Find data with specified well log type.
Well type Find data with specified well type.
Spud date Find data with specified spud date.
Seismic survey Find data with specified seismic survey.
Seismic vintage Find data with specified seismic vintage.
Data maturity Find data with specified data maturity.
2. Search results can be shown by project or by individual objects. A maximum of 5,000 items
can be loaded at any time into your local project.
3. Load the returned search data into your project, as illustrated in the following figure.
4. To display an underlying map layer for Studio Find results, define a New map service.
This can be any ArcGIS or online-based Web service. Map layers and data relay increasing
or decreasing levels of attribute and graphic detail, based on zoom level. See Figure S8.
204
Schlumberger Public
When loading objects into your project, the RPT or Database tool load interface is displayed
for each source from which data is pulled.
Data Environment Manager

The Data Environment Manager is an administrator application launched outside of Petrel. It is
used by data managers to set up and define a data environment configuration, that is, a unified
transparent layer across which Petrel users can access all relevant data, regardless of how and
where it is stored. Users can transparently access multiple data environments simultaneously
through the Studio Find interface in Petrel. Each data environment may comprise one or more
Petrel projects and/or reference projects and a single database repository.
205
Schlumberger Public
Figure S8. Define a new map service in Studio Find.
Petrel projects and/or reference projects located on network or shared drives and
accessible by more than one person,
The Studio Knowledge Database repository.
These sources can be grouped together. Typically they represent an asset, field, lease, etc.
depending on the access requirements of the company.
The Data Environment Manager also provides an interface through which database
administration can be performed. A data environment can be backed up once the database is
installed in any particular environment.
The data environment configuration, once added to Studio Find as part of your native Petrel
install, allows you to find data across data environments or environments in the configuration
file. Refer to the Studio Find section, above, for more information. Data can subsequently be
viewed, filtered, and imported into your local project. (Permissions on Petrel projects and
databases would apply for importing data.)
You can customize the Data Environment Manager to facilitate the following scenarios. The
following table describes the display options.
206
Schlumberger Public
Typically a data environment will consist of the following sources:
Desired Setting
Menu Options
General Steps
Users access information

using Studio Find in
shared Petrel projects and
reference projects located
on network or shared
drives
Tools->Show
Find settings
Define what Petrel project or reference

project files are to be indexed, the location
of the index, and the configuration file in
which these settings are to be stored.
The link to this configuration file is sent to
users, and all users define this in their local
search settings (Tools->Search
settings...) so they are able to search
across all projects defined in this
configuration file.
Tools->Manage
schedule on this
system
Manage schedules (Daily, weekly etc.) for

updating the Studio Find index. The index
can contain one or more Petrel projects or
reference projects that users may search
across.
Users access information

using Studio Find from the
Studio Knowledge
Database
Tools->Show
Find settings
Manage database connections and the

definition of which Studio Knowledge
Database repository is to be indexed, the
location of the index, and the configuration
file in which these settings are to be
stored.
OR
The link to this configuration file is sent to

users, and each user defines this in their
local search settings (Tools->Search
settings) so they are able to search
across all projects defined in this
configuration file.
Tools->Show
Database
settings
OR
Tools->Manage
schedule on this
system
207
Manage schedules (daily, weekly etc.) for

updating the Studio Find index, which can
contain the database repository that you
want users to search across. A schedule
can only be configured on one machine at
a time for any given configuration file. To
configure on another machine, the
schedule has to be released from the
machine it was initially configured on.
Schlumberger Public
A schedule can only be configured on one

machine at a time for any given
configuration file. To configure on another
machine, the schedule has to be released
from the machine it was initially configured
on.
Desired Setting
Menu Options
General Steps
You want to create data

environments for backup
or restore (through the
Database Manager) and
manage database
connections available for
use in Studio Find.
Tools->Show
database
settings
Manage database connections and the

definition of what Petrel project or
reference project files or database
instances are to be backed up or available
for use in Studio Find.
NOTE: Backup functionality is not available
if Studio Knowledge Database is not
installed, since Backup is accessed through
the Database Manager. See the Data
Environment Manager online help for more
information.
Studio Knowledge Database
Additional Data Coverage

Data types that can be stored and exchanged using a database repository have been extended:
Well domain Global well logs, well logs subfolders, checkshot attributes, bitmap logs,
General Time log, comment logs, zone logs, synthetics and sonic logs, multi trace (2D) logs,
dynamic logs (for example, derived), completions data, observed data (production data),
point well data, point well data attributes.
Shapes - Points with attributes and polygons with attributes.
Seismic domain Horizon auto-tracking parameters.
General Property templates.
208
Schlumberger Public
The information in this section summarizes whats new in Studio Knowledge Database 2011.1.
For detailed information and workflows, refer to the Petrel 2011.1 Release Notes, Petrel 2011.1
Installation Guide, and the Studio Knowledge Database Server for Petrel 2011.1 Installation
Guide, available on the Petrel DVD and through the Support Portal, and to the Studio
Knowledge Database topics in the Petrel online help.
Studio Knowledge Database 2011 provides proven scalability and performance over large datacenter deployments with thousands of wells, terabytes of seismic data, and tens of concurrent
users.
Using the command line mode, data can be transferred in batch between Petrel projects
and Studio Knowledge Database. These transfers can also be automated; updates from a
corporate data store can easily be made available for the Petrel user community.
Coordinate conversion of grid data (surfaces, 3D seismic) is now supported in Petrel and in
Studio Knowledge Database.
Filtering capability and usability in Studio Knowledge Database were significantly improved.
Numerous attributes were made available to filter either in the Repository Data table or in a
saved filter. The filter management dialog and workflows were completely revamped and
made very intuitive. Creating saved filters is very similar to creating Outlook rules, and the
resulting filters read as a plain English sentence explaining the query that you have just
created.
209
Schlumberger Public
Performance and Scalability
Data Collaboration (Multi-User Workflows)
Find and browse for data using one of these tools:
Studio Find. Quickly search and see data that youre looking for in the context of you
Petrel canvas.
Repository Data table. Browse and filter the data in a spreadsheet and view all the
attributes you need.
Database tool. Open up a familiar RPT-style Database tool to browse for data in the
repository in a tree view.
Data selections work as a virtual shopping cart. Toggle on data you want to transfer and
keep browsing for more. The new log and other well data types are also added to the Well
data selector, so you can conveniently select well data for all the wells or for the wells you
selected for transfer.
Automatic database alerts and the integrated dashboard now let you know when updates of
interest are available.
The Timestamp Status and Comparison dialog lets you decide if you need a particular data
item. Use copy mode to retrieve a temporary copy of a repository data item to you project
and use the full capabilities of Petrel to compare.
Integrated Petrel right-click synchronization makes it very convenient to send and retrieve
seismic interpretation data directly from the Input pane or from your 3D, 2D, or
interpretation window.
Using quality attributes such as data status or confidence factor, you can add context to you
interpretations. This data tagging not only allows you to track data throughout its life cycle,
it also lets you signal your intention to other users. For example, you can mark data almost
complete (ready for review) or complete (final). The values of these attributes can be
customized, and enforcement rules can be applied.
Data lockinga concurrency control techniquelets you claim full temporary ownership of a
data item while youre working on it. Locked items cannot be updated in the repository by
other users; only the lock owner or a Petrel Super User can unlock or overwrite the data.
The data will, of course, still be readable by other users.
210
Schlumberger Public
Data Lifecycle Management

You can backup a data environment for migration, security, or contingency purposes using the
following tools:
Backup feature on the Repositories tab,

Command line mode for batch backup operations.
A snapshot is a way to preserve the data in a repository at any one moment in time. The
snapshot of the repository and all data items in it are read-only. All users assigned to the
snapshot repository are automatically downgraded to Petrel browsers.
Data Management and Consolidation

Data Environment Manager The Database Manager has grown into a versatile
management tool that lets you create a complete data environment for Petrel, where
reference projects and the database are managed as a single entity from a single
management utility. This allows backups to contain all the data of an asset team, whether
stored in the repository, in reference projects, or in external seismic data files.
Repository Data Table Completely re-designed, the Repository Data table has grown
into a fully-fledged data editor and browser, similar to the GeoFrame* Data Manager. The
Repository Data table allows quick query and direct edits in the database using familiar
spreadsheet views. You also have the option to retrieve the data to Petrel and visualize or
edit it. Using the Repository Data table and advanced filtering, you can quickly perform
common data management workflows such as deleting low quality or non-compliant data.
Well Matching In your Petrel data environment, if you load wells into projects
separately, each well has a unique GUID even though all wells are identical. Since these
identical wells have unique GUIDs, the Database tool will not recognize them as matching
counterparts. This could lead to multiple versions of the same well being sent to the
repository.
To help solve this problem, Studio Knowledge Database 2011.1 provides a well matching
feature. Administrators can choose matching rules (attributes other than the wells GUID)
and even enforce them.
211
Schlumberger Public
Petrel users use the Manage or Define matches dialog to establish the match and prevent
proliferation of duplicate wells in the repository. Established matches are saved with the
project.
Schlumberger Public
Avoiding duplicate global well logs Because the repository can store global well logs,
even empty ones, you can eliminate duplicated global well logs by retrieving the appropriate
global well log from the repository and assigning new log instances to it during data loading.
212
Security
Administrator Roles The Administrator role found in Petrel Database 2010.x was split
into two new database roles for Studio Knowledge Database 2011.1:
SuperAdmin Creates regular database users, Admins, or SuperAdmins.

Admin Creates regular database users only.
These roles allow more sophisticated access control to the database. Otherwise the two
roles have the same entitlements for database management. From now on these database
roles automatically assume a Petrel Super User (data management) role in all repositories
without having to assign themselves this repository role. Refer to the following table.
Custom Repository User Roles You can now match the role of a user in your asset
team with adequate data access privileges by assigning the desired access level to different
data types (read-only, read-write). For example, all geophisicist can be given read-write
access to seismic interpretation but read-only access to wells. These custom repository roles
can be added in addition to the built-in repository roles (Petrel Browser, Petrel User, Petrel
Super User). Of course a user can still have different roles in the different repositories.
Super
Admin
Admin
Assigned Repository Role
Petrel
Super
User
Petrel
Super
User
Petrel
Super
User
Petrel
User
Petrel
Browser
Custom
Create and manage database

Admin and SuperAdmin
accounts
Yes
No
No
No
No
No
Create and manage database

user accounts
Yes
Yes
No
No
No
No
Configure and manage the

database (repositories,
coordinate systems, etc.)
Yes
Yes
No
No
No
No
Assign users to repositories
Yes
Yes
No
No
No
No
Manage repository data
Yes
Yes
Yes
No
No
No
Access database features and

retrieve data
Yes
Yes
Yes
Yes
Yes
Yes*
Send data to the repository
Yes
Yes
Yes
Yes
No
Yes*
User
* Custom roles can have different entitlements for each data type.
213
Schlumberger Public
Database Role
Single Sign-on Single sign-on Windows authentication allows users to connect to the
Studio Knowledge Database using their Windows credentials, as opposed to providing a user
name and password again. Once the user has chosen to log in using Windows
authentication, the system remembers them and further logins take place automatically.
NOTE: This is a new optional feature that requires specific configuration of the
database server and installation of the Oracle client on your workstation. In addition
Active Directory must exist on your network, and your workstation must have
access to Active Directory.
Oracle RAC Support Studio Knowledge Database 2011.1 offers full support of Oracle
RAC to allow high availabilty.
Licensing
End user workflows such as collaboration, data browsing, and sharing are available with any
Petrel core license.
Data management workflows, such as direct edit and delete in the database, require the
Database repository manager license in addition to any Petrel Core modules, including the
Data and results viewer core.
Database management workflows do not require a license.
214
Schlumberger Public
Structural and Fault Analysis

Petrel 2011.1 brings new features and improvements in the following areas of structural and
fault analysis:
Structural framework fault tools
Stairstep fault tools
Pillar faults tools
General fault tools
Fault model surface analysis
Seismic horizon interpretation, point, and surface data
Grid geometry calculations
Seismic horizon ghosting
Surface truncation modeling
Point attribute filter
Operations in the Workflow manager
Function modifier operation
Fault modifier process
Structural and fault analysis process
Fault seal scenario creator
Structural Framework Fault Tools

Dip and Dip Direction
Dip and dip direction can be computed on depth and two-way-time faults in a structural
framework (directly from the initial seismic interpretation faults). For two-way-time datasets you
can specify an average interval velocity to estimate the true fault dips. This operation does not
require you to create a pillar grid.
215
Schlumberger Public

Seismic data can now be extracted onto
the faults during the initial seismic
interpretation. The seismic data can be
extracted at a range of resolutions, from
course to full seismic resolution, either
on the fault or offset from the fault
(offset into the hanging wall and the
footwall). A series of difference
calculations can be performed to
compare the seismic at different offset distances from the faults. This operation provides a
powerful visualization technique to check the accuracy of fault and horizon pick locations.
Zonal Juxtapositions
Schlumberger Public
Areas defining the different zonal

juxtaposition types that occur along the faults
can now be mapped at a very early stage in
the interpretation process. This operation
does not require a pillar grid to have been
created.
2D Fault Plane Maps

2D fault plane maps that help in defining trap locations can now be generated while conducting
initial seismic interpretations. This operation does not require a pillar grid to have been created.
216
Stairstep Fault Tools

Constant Transmissibility Multipliers
Constant transmissibility multipliers (TMs) can now be defined for stairstep faults within the
Structural and fault analysis process.
NOTE: K faces can be set to
sealing (TM = 0) while retaining
non-zero TMs on the I and J faces.

Schlumberger Public
Seismic data can now be extracted onto

stairstep faults. Different interpolation options
are available.
Grid Property Extraction

Any continuous grid property can now be
extracted onto the faults, and cross-fault
calculations can be performed.
217
Juxtaposition Mapping
Any discrete grid property can now be extracted onto the faults, and the discrete juxtaposition
types can be analyzed.
Juxtaposition Windows
218
Schlumberger Public
Juxtaposition windows can now be calculated for stairstep faults. You can choose to define
cross-fault juxtaposition windows based on elevation, zones, and fault properties as well as host
properties. Extended options are also available for the filtering logic that is applied.
Pillar Faults Tools

Throw and Displacement Profiles
Profiles of throw and displacement versus distance along the fault can be constructed for pillar
faults in grids. These are useful indicators of structural sense, fault growth, and linkage.
Throw and displacement gradients provide useful

quality checks on the grid construction and fault
linkages and can now be computed on pillar faults in
grids.
Throw and Displacement Cumulative Frequency Profiles

Throw and displacement cumulative
frequency profiles can give an indication
of mapping resolution and accuracy.
These can now be constructed for pillar
faults in grids. You can generate these per
fault or for all of the faults within the grid.
219
Schlumberger Public
Throw and Displacement Gradients
Throw Consistency
This new tool analyses the throw directions
across each pillar fault in a grid and identifies
areas where the throw sense reverses. This is a
powerful quality check tool for geological
models.
Dip and Throw Calculations using Average Interval Velocities for TWT Data
Schlumberger Public
Numerous calculations in two-way-time

(TWT) grids and models can now be
performed with a user-defined average
interval velocity.
Cross-Fault Thickness Change

Calculations of layer thickness change and
line length change against pillar faults in
grids can now be performed. This provides
useful quality checks on the geological
model or the grid geometry.
220
Distance to Failure
A MohrCoulomb failure criterion can now be
applied to assess the potential for failure on pillar
faults in grids, based on an applied far-field stress.

Seismic data can now be extracted onto pillar faults in grids. The seismic data can be extracted
either on the fault or offset from the fault (offset into the hanging wall and the footwall). A
series of difference calculations can be performed to compare the seismic at different offset
distances from the faults.
Schlumberger Public
Hydrocarbon Column Height Prediction Enhancement

The ability to use published fault clay to threshold pressure equations and in-situ pressure
functions has been added to the column height calculator. This extends the previous options
that were for mercury-air, core-derived relationships.
221
Fault Permeability Predictor

Numerous methods for predicting fault
permeability can now be applied on individual
pillar faults in grids. These are the methods
available in the Structural and fault analysis
process. User-defined input properties can also
be supplied.
Fault Thickness Predictor
Potential Flow Indicators and TM

Calculations
Transmissibility multipliers, effective cross-fault
transmissibilities, and effective cross-fault
permeabilities can now be computed as
independent operations on pillar faults in grids.
222
Schlumberger Public
Numerous methods for assigning fault

thicknesses can now be applied on individual
pillar faults in grids. These are the methods
available in the Structural and fault analysis
process. User-defined input properties can also
be supplied.
2D Fault Plane Maps

The ability to visualize sub-zones as well as main zones and individual layers is now available in
this operation, along with color-coding of the zonal polygons according to the zone they belong
to. More detailed 2D fault plane maps can now be created with these options.
Schlumberger Public
General Fault Tools

Fault Properties to Points
Fault properties can now be converted
to attributed point sets for stairstep or
pillar faults in grids. The conversion of
fault properties to points now
incorporates the fault name and the
K-layer juxtapositions. When averaging
properties along a fault, area weighting
options are now included. This
operation allows for the detailed
analysis of the fault data within or
outside Petrel.
223
Juxtaposition Mapping
The juxtaposition mapping of discrete grid properties can now be performed for stairstep or
pillar faults in grids. Subsets of discrete properties can now be used to map cross-fault
juxtapositions (for example, specific layers or individual facies types) along faults.
A significantly extended fault property calculator is

now available for properties of stairstep or pillar
faults in grids. The calculator allows mathematical
calculations to be applied to a single fault property
or between fault properties. An output template can
now be specified to eliminate problems with
combining different property templates in
calculations.
224
Schlumberger Public
Fault Property Calculations
Juxtaposition Windows
Juxtaposition windows can now be calculated
for stairstep or pillar faults in grids. You can
choose to define cross-fault juxtaposition
windows based on elevation, zones, and fault
properties as well as host properties. Extended
options are also available for the filtering logic
that is applied.
Schlumberger Public
Fault Property Import and Export

An ASCII fault property import and export option has been produced for stairstep or pillar faults
in grids. This allows the import and export of any fault properties from Petrel. It also allows new
properties to be created or edited outside Petrel and subsequently imported back into Petrel.
Example of the exported file format
225
Fault Property Identifier

Calculations based on absolute values, percentile locations, and absolute elevations can now be
carried out on any fault property for either stairstep or pillar faults in grids. Extractions can be
performed on a per-fault basis or for the entire fault network.
Fault operations can now be accessed from the main Faults folder as well as from the
individual faults settings tabs. This allows for more flexibility when applying operations to single
faults, specific collections of faults within a grid, or for all the faults in the grid.
226
Schlumberger Public
Fault Tool Usability
Fault Surface Model Analysis

A series of geometric tests are now available to assess the stability of pillar fault surfaces being
constructed. This allows more viable pillar faults to be produced, increases the speed with
which geomodels can be built, and improves the stability of the models produced.
Quick-Look Surface
Quick-look surface creation can now be performed in user-defined polygon areas for seismic
horizon interpretations and point sets.
227
Schlumberger Public
Seismic Horizon Interpretation, Point, and Surface

Data
Edge Detection
Edge detection can now be performed in user-defined polygon areas for seismic horizon
interpretations, point sets, and surfaces.
Automatic Boundary Polygon
Schlumberger Public
The automatic boundary polygon

operation now finds fault edges at a
user-defined topographic jump
tolerance in the data.
Anomaly Identification
Anomaly identification can now be
performed in user-defined polygon areas
for seismic horizon interpretations, point
sets, and surfaces.
228
Influential Data
Anomaly identification can now be
performed in user-defined polygon
areas for seismic horizon
interpretations, point sets, and
surfaces.
Clipping Surfaces
Surface clipping can now be performed for seismic horizon interpretations as well as point sets.
Grid Geometry Calculations

Edge Detection
Schlumberger Public
The edge detection operationpreviously

available on seismic horizon
interpretations, point sets, and surfaces
(2010.1 and 2010.2)has now been
extended to geocellular grids. This
operation can help to identify subtle faults
and folds in the grid. These may have a
relationship to fracture or fault densities
and so affect reservoir permeabilities and
porosities.
Curvature
The curvature of the grid can now be
computed. This can help to highlight zones
of more intense strain and hence
potentially elevated host permeabilities
due to fractures. This property can be
used as a potential control on the fracture
prediction process. It may also help to
identify subtle faults or folds that are
present within the grid (but not explicitly
modeled as a fault).
229
Seismic Horizon Ghosting

The ghosting of new seismic horizons can be performed based on three criteria:
Using an existing structural marker and a target pick,

Using a constant shift,
Using an isochore.
The following images show a ghosted seismic horizon using a structural marker and a weak,
partially picked target. The new ghosted seismic horizon has the general form of the structural
marker but is warped to pass through the target pick points. This allows robust structural
geometries to be developed through weak seismic events.
The ghosting of new surfaces that honor truncation limits can be performed in a variety of
ways. This can provided useful input into processes that control horizon construction. This
operation allows the rapid development of a series of surfaces that define continuous geological
interfaces through the region, in areas that have complex truncating architectures. This is often
a key input into generating robust, water-tight models in processes such as the Make
horizons process and the Horizon modeling process.
Point Attribute Filter

The point attribute filter now allows the visual and deletion filter to be applied to discrete
properties as well as continuous properties for point sets.
230
Schlumberger Public
Surface Truncation Modeling
Operations in the Workflow Manager

Approximately 50 operations have been made available in the Workflow manager and the
Optimization and uncertainty process. These operations fall under the following
categories:
Grid operations
Fault model operations
Fault operations
Pointset operations
Surface operations
Polyline operations
Horizon interpretation 3D operations
Function operations
Function Modifier Operation
Fault Modifier Process

Constant throw shifts can now be applied as well as percentage throw values. These throw
shifts are applied consistent with the general throw sense of the fault, and the user can specify
whether to allow local changes in throw sense. This process allows the throws on faults in pillar
grids (for grids with only pillar faults present) to be manipulated after the grid has been
constructed and populated. The process enables the impact of geometric uncertainty to be
assessed for both exploration and development cases.
231
Schlumberger Public
Function objects can be manipulated (reversed, shifted, and random-noise added). The
Function modifier operation can be used to modify the form of throw and displacement
profiles (for example, shifts and reversing for different faults) described above under the Pillar
Fault Tools section. It can also be used to modify the input into fault seal calculations and
other operations and processes that use function objects as input. For fault seal calculations,
the impact of uncertainty on predicted hydrocarbon column heights in explorationor on
permeabilities and transmissibility multipliers in productioncan be readily assessed with this
approach.
Usability
Fault folders are honored in the process dialog, allowing more effective management of the
different fault types. Sub-selections of faults can also be computed independently and
calculations re-run only for certain faults. Individual faults or folders of faults can be selected
and different sealing scenarios easily applied or removed from the calculation process.
232
Schlumberger Public
Structural and Fault Analysis Process
Full Incorporation of Uncertainty in Workflows

Throughout the Structural and fault analysis process dialog, $variables can be applied. All
aspects of the fault seal scenarios can be manipulated to develop integrated uncertainty
workflows. The fault seal scenario, the transmissibility scaling factor, and the threshold pressure
can all have variables assigned. These variables can be defined differently for each fault or can
be grouped for sets of faults.
Schlumberger Public
Fault Seal Scenario Creator

A new operation is available to make fault seal scenarios in the workflow. This allows
uncertainty and optimization to be applied throughout the fault seal process. The fault seal
scenario creator allows uncertainty to be applied at all stages of the transmissibility multiplier
prediction process.
233
Schlumberger Public
234
Petroleum Systems Quick Look

The information in this section summarizes whats new in Petroleum Systems Quick Look
(PSQL) 2011.1. For detailed information and workflows refer to the 2011.1 documentation
available on the Petrel DVD and on the Schlumberger Support Portal (under Petrel
Documentation):
Petroleum Systems Quick Look for Petrel User Guide

Petroleum Systems Quick Look for Petrel Release Notes
Petroleum Systems Quick Look for Petrel Installation Guide
Reservoir Properties: Porosity Property
A depth map that you input,
A lithology/facies type that you choose from a drop-down list

OR
A lithology/facies map that you input,
A current sea bed or topography depth map or constant value.
A simple sediment compaction trend is used to define the porosity, based on the lithology and
the burial depth of the surface, derived from a set of look-up tables which you can edit if
necessary.
After they have been created by the reservoir properties process and output to Petrels Input
pane, the resultant maps can be fully edited using standard Petrel functionality, to tie available
well data and reflect geological knowledge of the area. Where there are hard data points like
well data, the surface can be tied to these well data points either by including the well data in
the compaction trend or by using Petrels Make/Edit Surfaces process.
Top Seal Properties: Top Seal Capillary Entry

Pressure
There is now a new process for top seal capillary entry pressure map generation based on
porosity and compaction look-up tables. The new process allows you to generate a first pass
capillary entry pressure map based on the top seal depth map and a user-defined compaction
235
Schlumberger Public
There is now a new process for porosity map generation based on burial depth and compaction
look-up tables (default and user defined). The process allows you to generate a first-pass
porosity map for a reservoir based on the reservoir depth and a compaction trend. It can be
used to make play-scale porosity maps at early stages, when there is limited data. Input options
are:
trend. It can be used to make play scale seal capillary entry pressure maps at early stages,
when there is little data. Input options are:
A depth map that you input,
A lithology/facies type that you choose from a drop-down list

OR
A lithology/facies map that you input,
A current sea bed or topography depth map or constant value.
A simple burial depth compaction trend is used to first obtain the porosity followed by a
capillary pressure entry conversion based on the porosity, based on the lithology and the depth
of the surface. You can edit compaction trends and capillary entry pressure trends.
Top Seal Properties: Density Property

An option on the Seal Properties process allows you to create a density map from the
resultant porosity map using the following formula:
The grain density is defined as a standard density for the lithology, as chosen by you. The
water density can be entered in the options tab.
Top Seal Properties: Hydrocarbon Column Height

Property
The result of using PSQL output is a map of the maximum hydrocarbon column height, for both
vapor and liquid, which can be supported by the capillary entry pressure of the top seal.
At a certain buoyancy pressure the seal fails, resulting in a breakthrough of oil or gas. The
breakthrough pressure is determined by the column height of an accumulationthe taller the
column, the higher the pressure. The density of liquid, vapor, and water are also determining
factors on the pressure applied to the seal of a reservoir. Default lithology densities are used.
236
Schlumberger Public
After they have been created by the seal properties process and output to Petrels Input pane,
the resultant maps can be fully edited using standard Petrel functionality, to tie available well
data and reflect geological knowledge of the area. Where there are hard data points like well
data, the surface can be tied to these well data points by using Petrels Make/Edit Surfaces
process.
User-Defined Lithologies
You can enter a map of lithologies (Petrel facies map) into the Make reservoir properties
and Make seal properties processes.
You can create a discrete lithology attribute surface that uses a discrete lithology or facies
template. These attributes can be entered into the processes, and the table will be filled with
the values, as defined in the template. You can then select the relevant action for each facies
from a drop-down menu or by entering information using a blue arrow entry.
Workflow Editor
All new processes are accessed through the Workflow editor with the same look and feel as
other processes within the Petrel software.
In the Petrel 2010 release, the input was listed in rows and columns and did not resemble the
original process dialog. In the Petrel 2011.1 release the process looks the same whether
opened directly or opened by double-clicking the link in the Process manager.
The previous version of PSQL calculated secondary cracking as a closed source rock system; the
entire amount of generated oil was cracked into gas inside the source rock. The calculations in
PSQL represented one end of the spectrum (the closed system), the other end being an open
system in which all oil leaves the source rock immediately after primary generation and no
secondary cracking of oil into gas takes place.
PSQL 2011.1 allows you to choose the other end of the spectrumthe open system. The
default is the closed system, and you must go to the Expert tab to change the default.
Pepper Generation to Expulsion Look-up Tables

PSQL 2011.1 assumes a position between a closed system and an open system, as described
above about Hydrocarbon Generation, by taking hydrocarbon losses and adsorption into
account. For more information please refer to Andrew S. Pepper, Estimating the petroleum
expulsion behavior of source rocks: a novel quantitative approach, Geological Society, Special
Publications, London 1991, v.59, p.9-31. The amount of expulsion is determined by look-up
tables that list the expulsion during burial over set-depth intervals.
237
Schlumberger Public
Hydrocarbon Generation: Open or Closed System
Net-to-Gross Ratio
This is the ratio of the thickness of the effective reservoir rock within the reservoir unit to the
total (gross) thickness of the reservoir unit. Effective reservoir rock is that rock within the gross
reservoir unit with sufficient porosity and permeability to contribute to the production of
hydrocarbons. The net-to-gross ratio can be entered and taken into account for the resultant
volume. In PSQL, this can be entered as a net-to-gross ratio map or a uniform value. When a
uniform value is entered, you must be aware that this net-to-gross value will be applied to
every closure in the calculation of its hydrocarbon volume. Therefore the value should represent
an average value for each and every part of the PSQL model area.
Water Saturation
This refers to the fraction of irreducible water in the given pore space taken into account for the
resultant volume. In PSQL this can be entered as a water saturation map or as a uniform value.
When a uniform value is entered, you must be aware that this water saturation value will be
applied to every closure in the calculation of its hydrocarbon volume. Therefore the value
should represent an average value for each and every part of the PSQL model area.
PVT Calculation for Injection Polygons and Points

In PSQL 2010, PVT calculation was only performed when input surfaces of gas (vapor) and oil
(liquid) charge masses were used. PVT calculation in PSQL 2011 is also performed when using
point injections or area injections with polygons.
Final Accumulation Closure Polygons

In PSQL 2010, the output closure polygons were created at the depth of trap fill before seal
breakthrough. Depending on the input charge mass and the seal strength, this could be at trap
spill point. However, some of the vapor or liquid may have broken through the top seal and
drained some of the hydrocarbons from the accumulation, and these final, shallower closures
were not output. PSQL 2011 has an option for you to additionally output the final closure
polygons (after seal breakthrough).
238
Schlumberger Public
CAUTION: This represents a change from both 2009 and 2010 versions. Net-togross ratio and water saturation reduce the total volume. Re-running an existing
PSQL case may produce different results.
Accumulation Information
In PSQL 2010, the accumulation information found within the Petroleum systems folder was
not saved to the Petrel project and was lost when the project was re-opened. Now all the data
items are saved and can be re-used at a later date when the project is re-opened. All data
items can be transferred between projects using the Reference Project Tool (RPT).
Map Output
In PSQL 2010, the data output options from the PSQL process were a set of points and/or a set
of polygons for a variety of parameters. You had to create workflows to transform these into
surfaces. There is now an option to output surface attributes directly from the process for the
chosen parameters, using a default gridding algorithm.
Reset Button
There are a number of default parameters within PSQL which you can edit, and these now have
a Reset button that allows the original default settings to override your settings.
It is now possible to output the actual and potential spill points for each accumulation as a set
of points on the Input pane.
Direction on Flow Paths

There is now a direction indicator (color gradually changes from dark to light green or red) on
the liquid or vapor flow paths to show the direction of flow. Lighter colors are closest to the
accumulations.
Geological Time in PSQL

You can now incorporate an element of geological time within the generation process of PSQL
via a burial depth function. These functions can be imported or created in Petrel and dropped
into the process in a simple-to-use format. The geological time versus depth (or % depth),
allows you some control over the time element and time output options. This affects the
generation process and the generation of hydrocarbons over time.
239
Schlumberger Public
Potential Spill
Ocean Plug-in Manager
Release Distribution
Before the Petrel 2011.1 software release, the Ocean Plug-in Manager was delivered as a
plug-in from the Ocean Store, but starting with the 2011 release, the Ocean Plug-in Manager is
a fundamental part of Petrel and allows users to manage their plug-ins from the moment they
install the Petrel software.
Ocean Plug-in Manager updates are available from the Ocean Store (ocean.slb.com).
Plug-ins Section
The Plug-ins section contains all the features associated with plug-in management. The list of
all installed plug-ins is available in this section of the Ocean Plug-in Manager.
240
Schlumberger Public
The Ocean Plug-in Manager for Petrel* is a plug-in that allows you to manage, organize, and
update all your Petrel plug-ins. These are the new features delivered for the 2011 release:
Access to all installed plug-ins,
Ability to identify the plug-in status (loaded or not loaded),
Ability to disable or enable a plug-in,
Ability to deploy and install plug-ins outside the [PetrelHome] directory,
Access to the plug-ins available in the Ocean Store that are compatible with Petrel
2011.1 and the platform that the Petrel user is running (32-bit or 64-bit),
Access to plug-ins details from the Ocean Store in-context,
Access to company-proprietary plug-ins distributed from an internal network shared
drive,
Ability get the latest updates for the installed plug-ins and execute a plug-in update,
Access to the Petrel software security settings,
Ability to export a list of all installed plug-ins and Petrel environment details for support
or troubleshooting purposes.
241
Schlumberger Public
The following options are available:

Sort by: Allows you to sort the list of installed plug-ins by a list of predefined attributes.
# Plug-ins installed: Displays the number of installed plug-ins.
Plug-in details: Displays useful details about each plug-in. To view these details, click
the desired plug-in name.
More details from Ocean Store: Provides a learn more link in the plug-in details, as
long as the plug-in is available from the Ocean Store.
Plug-in active (loaded): Displays the plug-in title in bold when the plug-in does not
require a license or when you opt to load a plug-in and a license is already available.
Plug-in not active (not loaded): Displays the plug-in title in italics and grayed out
when you deselect a plug-in when starting the Petrel software or when a license for a
selected plug-in fails.
Plug-in enabled/disabled button: When disabled, prevents a plug-in from being
loaded, and the plug-in does not appear in the Petrel License Window. Enabling the
plug-in reverses the changes and allows the plug-in to load.
Plug-in update status: Indicates if the plug-in needs an update.
Plug-in update button: Launches an update. Only available when a newer version of
the installed plug-in is available from the Ocean Store or from the company internal
source of plug-ins. (See the Corporate Section, below.)
Plug-in uninstall button: Allows you to uninstall or remove a plug-in.
Export list: Allows you to export a list of all the plug-ins and details as a XML file. This
action only appears in the Plug-ins section.
Store Section
The Store section allows you to view the plug-ins available in the Ocean Store. Access to the
Ocean Store is available in this section.
Schlumberger Public
The Store section displays a list of those plug-ins available in the Ocean Store that are
compatible with the Petrel version currently installed. The following options are available from
this section:
Keyword search: Allows you to initiate the Ocean Store site search from the Ocean
Plug-in Manager.
242
Plug-in details: Displays useful details for each plug-in. To view the plug-in details,
click the desired plug-in name. Within the plug-in details, there is a link to the Ocean
Store to access more information.
Plug-in Manager updates: Indicates whether there is a newer version of the Ocean
Plug-in Manager available and if so provides a download link.
Launch Ocean Store: Provides a link to the full catalog of plug-ins in the Ocean Store.
Corporate Section
The Ocean Store (http://www.ocean.slb.com) is the designated website where scientists and
engineers can access and download plug-ins for use on the Petrel software platform. However,
companies that developed plug-ins for internal use are not accessible to you from the Ocean
Store.
The Ocean Plug-in Manager allows a System Administrator to configure an internal source of
plug-ins, such as network shared folders, to distribute and deploy plug-ins within the Petrel
environment.
Plug-in details: Displays useful details about the plug-in. To view these details, click
the plug-in name. Within the details is a link to the Ocean Store to access more
information.
Plug-in install button: Allows you to install the desired plug-in.
243
Schlumberger Public
The Corporate section allows you to view the plug-ins available in the defined internal source
of plug-ins. The following options are available in this section:
Schlumberger Public
Security Section
The Security section allows you to view and manage the plug-ins security settings. The
following options are available:
Security Level: Allows you to set the security level to Very High, High, Medium, or
Low.
Add/Remove Trusted Publisher(s): Allows you to add or remove a vendor to the
trusted publisher group, so that when the security level is set to High, those plug-ins
whose vendors are in the trusted publisher group can also be loaded.
244
Schlumberger Public
245
System Requirements
Before installing the Petrel 2011.1 software, ensure that your system meets the requirements
described in the following table. Refer to the Petrel 2011.1 Installation Guide for more details
about operating systems and hardware selections.
NOTE: Running the Petrel software with the Minimum Supported configuration is
not recommended. To use Studio, you must run the Petrel software with the
Minimum Recommended configuration.
Minimum Supported
Windows XP 32-bit Professional edition with SP3
Processor
Multi-core processor (best with a fast clock speed and high

cache)
Memory
4.0GB, DDR3 SDRAM
Display
No minimum requirement (the quality of the viewing

experience increases with the size of the monitor)
Graphics
NVIDIA mid-range graphics card
Primary Storage
SATA HDD 10K RPM
Secondary Storage
(optional)
500GB SATA HDD
Minimum Recommended
Operating System
Processor
Quad-core processor (best with a fast clock speed and high

cache)
Memory
8.0GB, DDR3 SDRAM
Display
Two 24-inch LCD monitors
Graphics
NVIDIA Quadro 4000
Primary Storage
Solid State Drive (SSD)
Secondary Storage
(optional)
500GB SATA HDD
Vista 64-bit Business or Ultimate editions

Windows XP 64-bit Professional edition with SP2
Preferred
Operating System
Windows 7 (64-bit) Professional or Ultimate editions
Processor
Dual quad or hex-core processor (best with a fast clock speed

and high cache)
Memory
48GB DDR3 SDRAM
246
Schlumberger Public
Operating System
Display
Two 24-inch or 30-inch LCD Monitors
Graphics
NVIDIA Quadro 6000
Primary Storage
SSD
Secondary Storage
(optional)
500GB SATA HDD
Other Required Software
Microsoft .NET Framework 3.5, SP1

Flexera FlexNet Publisher (for details, see the
Schlumberger Licensing Tool section on page 4-8 of the
Petrel Installation Guide)
Oracle client 11.2.0.2 for certain Database manager
workflows and single sign-on
Studio Knowledge Database Server Requirements
Minimum
Processor
Dual Six Core
Memory
16GB
Operating System
Red Hat Enterprise Linux 5.2 (64-bit)
Other Software
Oracle 10.2.0.5 (64-bit)

ArcSDE10 Direct Connect
Preferred
Processor
Quad-core processor (best with a fast clock speed

and high cache)
Memory
32GB
Operating System
Red Hat Enterprise Linux 5.2 (64-bit)
Other Software
Oracle 10.2.0.5 (64-bit)

ArcSDE10 Direct Connect
247
Schlumberger Public
NOTE: To use Studio, you must run the Petrel software with at least the Minimum
Recommended configuration described in the preceding table.

Petrel 2011.1 What&#39;s New

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Petrel 2011.1 What&#39;s New

Transféré par

Droits d'auteur :

Formats disponibles

Petrel*

Whats New in Petrel 2011.1 Guide

Whats New in Petrel 2011.1 Guide

General Functionality ................................................................ 16

Whats New in Petrel 2011.1 Guide

Message Log ....................................................................................................... 18

Whats New in Petrel 2011.1 Guide

Seismic Wavelet ASCII Export/Import...........................................................................42

How to Define Fluid Contacts Using Regions .................................................................70

Whats New in Petrel 2011.1 Guide

Make Log Process ............................................................................................... 84

Usability ............................................................................................................ 105

Structural Framework ............................................................. 106

Reservoir Engineering ............................................................. 123

Whats New in Petrel 2011.1 Guide

Zonal Juxtapositions ................................................................................................. 116

Fine Scale Equilibration ............................................................................................. 127

Whats New in Petrel 2011.1 Guide

History Match Objective Function ............................................................................... 147

Aquifers ............................................................................................................ 176

Studio ...................................................................................... 198

Whats New in Petrel 2011.1 Guide

Simulation Summary Results Loading .............................................................. 195

Structural and Fault Analysis ................................................... 215

Whats New in Petrel 2011.1 Guide

Throw and Displacement Cumulative Frequency Profiles .............................................. 219

Seismic Horizon Interpretation, Point, and Surface Data ................................. 227

Petroleum Systems Quick Look ............................................... 235

Whats New in Petrel 2011.1 Guide

Fault Modifier Process ...................................................................................... 231

Reset Button ..................................................................................................... 239

Ocean Plug-in Manager ........................................................... 240

System Requirements.............................................................. 246

Whats New in Petrel 2011.1 Guide

Welcome to Petrel 2011

Disciplines Working Together

Flexible Well Section Window Petrel

The well section window shows well log data against

Stair-Stepped Grid Option Petrel 2010

Whats New in Petrel 2011.1 Guide

Structural framework building starts from the first

Depending on complexity, you can chose the most

Three improvements address general

Access to the Best Science

local model updates that you need. New workflows

Greater Spatial Accuracy With Petrel 2011

Property Modeling Advances Advances have been

The Power of INTERSECT* - The reservoir

engineering environment in Petrel 2011 software

Whats New in Petrel 2011.1 Guide

This example shows the impact of

INTERSECT provides better flow

As-Needed Local Model Updates Perform only the

Increased Workflow Productivity

Enhanced Geophysicists Tool Box New and

Streamlined Daily Tasks To help you get your

Interactive, In Context, Data Search Results

Whats New in Petrel 2011.1 Guide

Similar to a Google engine, the Find tool lets you

The annotation tool is used to notify the team of

day-to-day interpretation done more efficiently,

The Studio Favorites panel lets you collect

Scalable Management of Large Numbers of

Collaboration of Knowledge and Data With the

Petrel 2011.1 What's New

Petrel 2011.1 What's New