Petrel 2013 5 Whats New
Petrel 2013 5 Whats New
Petrel 2013 5 Whats New
Our commitment to Petrel resulted in dramatic strides forward in the way we develop and deliver a software
platform, and with the Petrel 2013 Platform and Update releases, we continue to deliver on our promise of better
integration, deep science, and productivity. Today we support an engineering team unrivalled in size and expertise,
empowered by the Ocean software development framework. More than ever before, we are positioned to help you
develop critical insights into reservoirs throughout the oilfield lifecycle.
This document is updated for the 2013.5 release. The following sections are organized, as far as possible, by
discipline. Within each section you will find the New Features and any significant behavioral changes listed,
Refer to the companion documents, Petrel E&P Software Platform 2013 Release Notes and Petrel 2013 Installation
Guide, for information on licensing and system requirements.
Documentation for all prior Petrel releases is available from the Schlumberger Information Solutions (SIS) Support
Portal.
Volume Based Modeling (VBM) technology revolves around the concept of ’implicit modeling’*. The main idea
The process for creating such models is conceptually simple: first, a fully unstructured faulted 3D mesh is built from
a watertight representation of the fault network, then a volume attribute representing the stratigraphic age of the
formations is interpolated on this mesh, once this calculation is completed, iso-surfaces of the attribute which
correspond to the location of the original input data points are extracted as horizons in the Structural framework
and a zone model is computed; this yields a volume representation of geological layers.
Input Data Create background Compute background Extract horizons from Build zone model
volume model stratigraphy property volume
Figure 2. Volume Based Modeling (VBM) examples of compressional and extensional models
Extensional**
Compressional
** Physical (sandbox) models courtesy Fault Dynamics Research Group, Royal Holloway University of London.
*** Seismic data supplied by Geosciences Australia
** Physical (sandbox) models courtesy Fault Dynamics Research Group, Royal Holloway University of London.
*** Seismic data supplied by Geosciences Australia
H1
H2
H3
As all of the horizons are contained within a single 'conformable sequence', the geometry of each final horizon is
constrained by all input horizons, without the need for using isochore or isopach modelling.
A B
Structural Framework QC Manager is a tool designed to identify algorithmic and intersection failures in the Fault
framework model of the Structural framework. The new tool presents all of the identified error information that is
associated with each problem (reported by Fault Validation and/or Horizon Modeling) and presents them in a
user friendly spreadsheet format.
The Fault validation process can be found by using the right mouse button menu on the Faults folder of Structural
framework in model tree (or directly on a fault in the 3D window).
There is now quick access to all operations on faults (structural framework and pillar grid), seismic horizon
interpretations, surfaces and points from the right-hand mouse button. This functionality is available from within
3D windows and from the data objects in the Input and Models panes.
Isochore gradient
2013.4
Seismic Smart Folders
You can now dynamically display the seismic data listing in your project based on a range of attributes, including
In the example below, the Input pane on the left shows a typical tree structure as the project is populated with an
increasing number of seismic datasets. Data is typically received and loaded grouped by surveys and vintages. The
Favorites pane on the right shows the same inventory of seismic datasets sorted in a user-preferred hierarchy. This
tree structure is dynamic and responds to your selected preference of attributes and their sorting order. A full
listing and explanation of the available attributes is described in the online help. In the example below, the same
2D lines are now listed by line geometry names, with available vintages grouped below them.
2013.3
Surface attributes: resample option
There is now an option to resample the input seismic trace prior to surface attribute computation to mitigate
artifacts arising from the discrete nature of seismic, particularly in areas of dipping seismic reflectors.
A new tab, “Resample parameters”, is available for the following five attributes: RMS, Average Magnitude, Mean
Amplitude, Positive to Negative ratio, and Average energy.
As an example, setting input seismic to be resampled at “4x” will create 4 times the number of original sample
points within the specified time window of interest, prior to computing the surface attribute. These resampled data
points are regularly distributed within the time window.
This resample option will be extended to the full range of attributes in future releases.
The Interval velocity maps option now is available from the Velocity Modeling process.
A new icon called “Select a single point” was presented in the 2013.1 release, but no shortcut key was assigned to
it. In this release, it can be accessed via the shortcut key Shift + E.
2013.2
Multi-Z Interpretation
You can now create a Multi-Z interpretation object, which can handle Multi-Z interpretation values. The Multi-Z
interpretation workflow is part of the Seismic interpretation process. Interpretation is done on 2D lines, inlines,
crosslines, random lines in 3D window or a traditional 2D interpretation window. Multi-Z interpretation can be
created and stored in an Interpretation folder in the Input tab.
Normals are represented by vectors on each Multi-Z interpretation point showing the direction of an object
(inwards, outwards). “QC normals” option is the part of the data QC and can be used for checking the normals
consistency. The following example represents a top salt interpretation, where the normals are inconsistent in the
central portion of the points set. Red points show that a Multi-Z interpretation has the normals downwards when
they should be upwards.
The Multi-Z interpretation is a manual process. However, a user can snap a secondary Multi-Z interpretation to the
primary one while interpreting. The ability to snap helps to avoid vertical mismatches at the crossing point of the
same Multi-Z interpretation interpreted, e.g., on INL and XLN.
The following example represents the same Multi-Z interpretation that is interpreted on INL and XLN. The higher
Final Multi-Z interpretation can be used to create a triangle mesh. Schlumberger Private – Customer Use
There are three modes available, depending on the resolution of a Multi-Z interpretation. A new triangle mesh will
be created and stored in a Triangle Meshes folder in the Input tab.
A “multi z values” triangle mesh created from “multi z values” interpretation, as well as a “single z value” triangle
mesh can be integrated within a Structural Framework using the WesternGeco Seismic Velocity Modeling plug-in.
This enables to build velocity models to be consumed by imaging workflows.
Figure 21. Triangle meshes (Data courtesy of WesternGeco Multi Client services)
The Interval velocity maps option now is available from the Settings for an output Velocity model, Operations
tab/Velocity conversion folder/Interval velocity maps.
Seismic Reconstruction – 2D
Unconformity handling
The seismic reconstruction 2D process now allows you to define the geological type of horizons in order to handle
unconformities such as erosional surfaces, resulting in chrono-stratigraphic displays of seismic sections.
The geo-mechanically based seismic reconstruction 2D process now allows you to define the geological type of the
input horizons/surfaces through the stratigraphy column in the Reconstruction 2D process or in the settings of an
existing reconstruction model. The types of horizons/surfaces that can be defined are Conformable, Erosional,
Discontinuous and Base.
The compression process for ZGY cubes only requires one parameter as an input: the Signal to Quantization Noise
Ratio (SQNR, with dB unit). The “Noise” mentioned here is not the one contained within the original seismic
volume (cf. acquisition/processing noise), but the one that would be introduced by the compression algorithm itself.
A high SQNR implies low compression factor, and vice versa. A relationship between the latter and the
compression factor can be estimated from within the dialog of the process (see the following information).
The function (cf. compression factor = f(SQNR)) is unique per seismic cube and is sensitive to the nature of the
seismic signal (e.g., whether you have a large amount of heterogeneity in the signal/amplitude/wavelet, or
whether the reflectors are homogeneous. Seismic volumes with high information content will compress less well
than volumes with lower information content, given the same SQNR setting.
You then need to adjust the compression process based on the workflow (e.g., Structural Interpretation vs.
Quantitative Interpretation).
This new option is located under the Options tab in the Sonic Calibration and Integrated seismic well tie studies.
By default, the system suggests an order based on the number of knee points divided by 2. However, you can
manually set it (1≤order≤20).
Compared with the existing options (Linear and Cubic), Polynomial fit creates a smoother correction curve, so the
Calibrated Sonic and the output Interval Velocity present a “gentle“ transition.
The character of seismic data varies as time increases, with deeper data generally having lower frequencies and
amplitudes. It may be useful to use different wavelets over different time ranges (gates) to generate a synthetic.
With time varying wavelet, the interpreter can use various existing wavelets and taper types to create a time
varying wavelet.
New functionality can be accessed in the Input tab of the Synthetic Generation and Integrated Seismic Well Tie
studies:
In the time varying wavelet dialog, you have to specify time ranges or time intervals over which a series of
was modified”:
2. Start/end times (in ms) for each individual gate (time ranges) over which individual wavelets will generate
the synthetic. Minimum time interval is 4 ms and gaps between time ranges are not allowed.
3. Taper: Taper types supported are:
a. Trapezoidal
b. Cosine
c. Cosine squared
d. Hanning
e. Hamming
f. Blackmann
g. Papoulis
All the wavelets are re-sampled to the same sample rate of the one with the lowest sample interval.
Synthetic seismogram is generated using the highest resolution.
Wavelet average is a new option on the wavelet toolbox. In the parameters area, you are requested to select, as
input, a list of wavelets to be used for the average calculation.
You can use Analytical, Deterministic, and Statistical wavelets for the average calculation.
The input wavelets can have any sample interval between 1-16 ms and lengths up to 8 seconds.
The wavelet average method will automatically compute and plot the result just after the first wavelet is selected
as input. It is displayed in dark blue. When all inputs are removed, no wavelet is plotted.
In order to allow you full control of the log manipulations, additional parameters have been added to the interface
of Log Conditioning > draw to show the start and end depth interval and the value under modification during the
manipulations.
2013.1
SEG-Y 2D Toolbox
The SEG-Y 2D Toolbox is intended to be used with 2D SEG-Y files that cannot be loaded correctly using Petrel’s
standard SEG-Y import tools.
A major focus is in handling of 2D navigation data. The SEG-Y 2D Toolbox will work with navigation data from
multiple sources, including:
• Amplitude – Prioritizes picks of higher extrema for early expansion, leaving lower extrema picks to
expand later.
• Proximity – Prioritizes picks with shortest expansion paths over picks with longer expansion paths.
• Amplitude&Proximity – Corresponds to a priority combining the first two methods.
The default value is Amplitude&Proximity, which offers both high quality growth and influence of close
proximity to seed points.
Figure 32. The trace-window dynamically updates to indicate the reflector dipping along the inline
Wavelet Correlation
• Seed trace – Calculates the cross-correlation value with waveform from seed trace
• Adjacent parent – Calculates the cross-correlation value with waveform from adjacent parent trace
Cross correlation with Seed trace has a quality range from 0 to 1.0, while cross correlation with Adjacent parent
trace has, as previously, a smaller range from 0.75 to 1.0. In the following case, the waveform of adjacent parent
trace would have drifted from the original seed trace with increasing distance.
3D Snap
A new 3D Snap button was introduced. Previously it was necessary to set several parameters to perform 3D
interpretation snapping. Now you can set the Max. vertical delta search window parameter, the desired
seedpoint collection under Seed/Locking, and click 3D Snap to snap the horizon interpretation.
Seeds/Locking
The Seeds and Locking mechanisms have been combined into a common GUI, and restrictions for the data-types
and tracking mechanisms supported by each mode was clarified.
For more information on smaller updates and details on tracking algorithms, refer to the dialog tooltips and online
help.
Meta data works for both 3D and 2D seismic data. You can manually specify parameters applied for seismic data
during the processing.
Figure 35. Meta data tab
Composite Lines
Figure 39. Automatic creation of a joined Composite Line for lines that don’t intersect
Chained Expressions
Chained expressions introduce great improvements to the calculator, especially in combination with the spatial
operator. You can now use calculator output as input to a new expression. This opens possibilities to quickly
calculate self-composed attributes like spatial smoothing, curvature, and many more.
Multi-Threaded
The seismic calculator has been parallelized and now supports multi-threading for increased performance. Multi-
core workstations can experience a speed-up by a factor of 10 or more in certain scenarios.
Inspector Updates
Increased Horizon and Fault-Interpretation Support
You can now manipulate style settings for seismic horizon interpretation objects in the Inspector. Horizon
tracking parameters can also be set directly by the Inspector. The same features are supported for fault
interpretation objects.
Figure 42. Extracted geobody Petrel 2011 (left), and extracted geobody Petrel 2012.5 (right)
Medium NVIDIA Quadro K4000 or NVIDIA Quadro 6000-series (Fermi) Desktop edition
Illumination techniques empower the interpreter to focus on particular structural elements by utilizing different
light sources at different elevations and azimuths. Depending on the information to be obtained or filtered, the
structurally oriented directional light sources are capable of clearly enhancing or suppressing information extracted
from the seismic subsurface response or gridded topographical expressions.
Typical Usage
The Light Tool can be used in several different scenarios. Here are some examples of data where adding colored
light enhances visualization:
Figure 44. Lighting applied to a regular 3D seismic amplitude cube. Two lights have been added,
green to highlight the layers and red from the side to enhance the vertical faults.
3D Edge Enhancement improves edge detection by comparing and summing the values of the surrounding pixels
along a plane on the edge-detected cube. After this, the mean of the values is displayed on the output cube. This
process is repeated for each pixel, for all directions and angles for the planes. The resulting cube would enhance
the larger and planar features, while smaller features such as noise are smoothed away.
The parameters set for this attribute include the manipulation of the horizontal and vertical radii, in addition to the
strike and dip ranges and the maximum and minimum values. The radii are used to calculate the total size of the
filter through: (2 × 𝑟) + 1
The larger the radii selected, the more compute time is necessary. However, by limiting the dip and strike ranges, it
will take less time to compute. Strike is computed from the Inline direction. The computation of dip and strike
angles assumes an isotropic sampling rate where the intervals between pixels are the same in all three
dimensions. The strike and dip angels also limit the rotation of the plane.
Figure 48. Effects of minimum and maximum strike. Left: 158, 180. Middle: 103,134. Right: 62, 87
Four parameters need to be defined after constructing GLCM: the quantization level of the image (levels), the size
of the moving window (lateral and vertical), the direction and distance of voxel pairs (split), and the statistics used
as a texture attribute (algorithm).
The parameters are divided into five main categories that directly relate to the required factors mentioned above.
The Algorithm parameter selects the desired algorithm to calculate the statistic, based on the co-occurrence
matrix. The upper- and lower-amplitude limits should be defined by you, as these differ for different datasets. The
Levels parameter controls the levels of quantization in the definition of the co-occurrence matrix. The actual
numbers of levels is set at 2𝑛 where n is the selected parameter in the 8-bit grey scale. For the direction and
distance of voxel pairs, the Split parameter is used. It is dependent on the size of the moving window, which is
controlled by the Lateral-&-vertical window parameter, where the half-window size is defined to calculate the
co-occurrence matrix.
• Co-blocking: The algorithm uses as a reference a log and blocks the others taking in consideration the
same depth position for the blocks.
• Draw: Replaces log values with values interpolated between start and end depth selected.
Track Manager can be accessed in Seismic Well Tie Process > Track Manager.
Seismic Track
Seismic track allows the visualization of seismic sections in the Well Section Window. Use this track to display
Inline, Xline or 2D seismic sections available in the project. In this environment, the visualization of seismic and its
attributes can be fully adapted to your preferences (position, number of traces displayed and other settings).
Seismic track can be added by going to Well Section Template > Settings > Add Track > Seismic (SWT).
• Trace Options: You can now select where data correlation will start. The options provided are: Match
Seismic traces (to that used in the seismic track), User-defined traces or Single trace (average seismic
trace defined by a radius around the well).
• Phase Mistie: This new option calculates not only the level of correlation considering time shifts in the
synthetic, but also in the wavelet’s phase.
The wavelet is rotated 360 degrees (with a 1 degree step) and at each rotation, the correlation between
synthetic and seismic is calculated. Final output of this process is the optimum phase rotation to be applied
to the wavelet when the maximum correlation between synthetic and seismic was found.
RC Modeling can be accessed during the Synthetic Generation Process and allows the user to select/unselect RC
areas or individual coefficients and see the results as a partial synthetic.
Each component (positive and negative) is the result of the convolution of the active wavelet with a reflection
coefficient. The partial synthetic trace is the sum of the positive and negative components.
This process permits you to better understand how those coefficients impact the synthetic response, as well as
giving the ability to filter problematic areas from your synthetic.
Wavelet Toolbox
Allows you to invert polarity for Analytical wavelets. This option is shown under Parameters for Analytical
wavelets in the Wavelet Toolbox.
Extraction windows in the reflectivity and the seismic for deterministic wavelets can now be visually
adjusted directly in Well Section Window by using the slide bars. This option gives more flexibility and
control to get the correct time frame to extract wavelets.
Figure 54. Local legends for a 3D window, as stored in the Windows pane
The use of Pre-Stack Depth Migration (PSDM) seismic data has become popular in recent years. With Depth
Seismic Calibration, we are proposing a new tool that, by the generation of synthetic seismograms, the interpreter
2013.3
Backward compatible projects
We have addressed a compatibility issue between 2013.2 and 2013.1 that may have occurred when using
Checkshot loader
When importing checkshot data exported from GeoFrame, where the file contains a header, units can now be reset
and user-specified units can also be stored for use in the next import activity.
2013.2
Multiple LAS Importer
Time series logs introduced in the 2013.1 release were created by a manual workflow: after importing regular logs
and inserting and editing the time step attribute in the log attributes spreadsheet, you could then create individual
time steps from global time series log operations tab. In the 2013.2 release, a new LAS importer allows you to
simultaneously import both regular and time series logs in the same GUI.
The LAS importer now handles simultaneous import of time series and regular logs. This reduces time spent
creating time series logs with the manual workflow implemented in the 2013.1 release. The manual workflow,
On the Data tab of the new LAS importer dialog, you can switch on Automatic matching to import only regular
logs, or you can select the Specified option to import both time series and regular logs for matched (property
template based on log name) and unmatched (property template based on unit) sections.
See the online help topic, “Importing and Converting Multiple LAS Files” for the detailed procedure.
Copy zone option allows you to copy a zone over to the next column along with the bounding events. It requires an
empty interval on the destination column where the zone is being copied.
2013.1
Several enhancements were made to Stratigraphic charts and labeling, and there is now a new process for volume
calculations based on gridded surfaces. This release also delivers several client requests related to data
management of well objects. If you work with thousands of wells—for example in a shale gas portfolio—you can
now classify well attributes by color. You can also view and manipulate many more geology objects directly from
the Inspector window and see those changes reflected dynamically in your display window.
Reporting
The Map-based volume calculation process outputs the results in the volumetrics spreadsheet in different
formats. The case is also saved in the Cases tab, where you can access the reporting options by right-clicking on
the case.
Workflow Editor
The Map-based volume calculation process is fully supported in the Workflow editor. You can use variables
and object variables to automate the workflows for map-based volume calculations. A number of other commands
provide functionality for extraction of volumes from saved map-based volume calculation cases.
Two formats from StrataBugs are now supported: .xml and .dex. You can also import Petrel 2012 stratigraphic
charts using the format put in place specifically for those charts.
Spreadsheet
Display
With the new display style, you have more control over the look of the chart. You can access the controls for
display settings by double-clicking columns in the tree and clicking the Style tab. See Figure 54.
Figure 59. Adding or deleting events and zones and editing well age and type
Background
If this feature is switched on, the label will be filled with a solid color. You can modify the color source as well as
the transparency.
Inspector now supports quick viewing and updating for these object types:
• Fault model
• Skeleton
• Horizons
• Fluid contact
• Well tops
• Well logs
• Well trace
• Point well data
• Checkshots
For example, the Inspector displays information for the well trace of regular and producing wells (not newly
designed wells), well logs, well tops, point well data, and checkshots when these are visualized in a 2D or 3D
window. You can view general information and statistics, modify style settings, and launch the spreadsheet
without accessing the object data tree. See the online help topic “Inspector Windows” for descriptions of the
generic and object-specific Inspector tabs.
Figure 60. Fault Model Inspector (left) and Skeleton Inspector (right)
To import well data in latitude/longitude, you must set the coordinate reference of the project. Once imported, well
header data is stored in the Well attributes subfolder under the main Wells folder. These ASCII files contain
attributes displayed in columns in the well head import dialog. Petrel creates several default attribute columns, but
you can add an unlimited number of custom attributes. An attribute can be one of these types: Boolean, string,
continuous, discrete, or date.
For more details on how to import and edit well headers with latitude/longitude coordinates, see the Core online
help topic, “Importing Well Headers.” For directions on exporting latitude/longitude, see “Exporting Well Headers.”
Time-Series Logs
Time-series logs allow production engineers to create, visualize, and evaluate repeat logs recorded in days or
hours, with a maximum of 20 repeats. The logs help identify critical reservoir intervals that return poor quality data,
thereby isolating potential candidates for reservoir analysis.
Petrel time-series logs were added to supplement point well data used in repeat formation tester workflows for
reservoir engineering. In the Input pane, a time-series log icon is marked with a log template icon overlayed with a
clock symbol, for example for a well section time-series log.
Whenever there are changes in global well logs used in creating time-series logs, either by import of new logs or
after modifying a resistivity log using the calculator, the local time-step log must be updated to reflect those
changes.
Time-step objects can be visualized in 2D, 3D, Map, Well section, and Intersection windows. The global time
player is used to play through the different time steps. To visualize and play through time steps in an Intersection
window, first create and activate the vertical well intersection or general intersection plane. Playing through the
time-step logs helps to identify logs with wrong data samples. You can selectively delete the interval or reload the
log data after editing the extraneous sample points. This could aid in the isolation of reservoir intervals with poor
data quality and the selection of the best reservoir interval for analysis.
1. Open the Settings dialog for a cross section template and insert a new track on the Well section
template tab.
4. Play the first, current, or last track using the time-step drop-down menu and the time player.
The log spreadsheet uses icons and special features to manage log data. The spreadsheet updates dynamically, as
you edit wells and well log names in the Input pane. The arrangement of attribute columns in the spreadsheet
always corresponds to their order in the Log attributes subfolder. To open the spreadsheet, right-click this
subfolder and click Log attributes spreadsheet.
Well log attributes and logs are synced using the Reference Project Tool. Log values for all log attributes
common to the two projects are copied. Values for matching log attributes in the target project are
overwritten. If there is a modification to log attributes, the transfer dialog window indicates which well log is
newer. Copying log attributes and well logs in copy mode will not change the well logs in the RPT transfer window
until data is synced. The copy mode provides a canvas from which to compare modified data against the original.
In addition to filtering on wells and surfaces, you can filter user interpretations. Under the main Well Tops folder,
the Interpreter filter subfolder captures the interpretations using the IDs assigned automatically when anyone
creates or edits well tops. If you are importing well tops from outside Petrel, the interpreter ID can be created
during import or added later to the Well Top spreadsheet. In this spreadsheet you can create, edit, copy, paste, and
rename interpreter IDs.
For more details and procedures, see the Geology online help for “Filtering Well Tops.”
Two workflows for generating logs using THL as depth are implemented in this release:
• Generating a log using THL as the geometrical variable
• Generating a THL log from a well top continuous attribute
By calculating the THL point for the corresponding MD, you can generate a log for the entire length of a well in the
vertical, deviated, and horizontal sections. During geosteering this is important in the horizontal section of the well,
where data manipulation using true vertical depth is a problem because of repeat depths. To create a THL log for
the entire well path without repeated depth:
1. Right-click the Global well logs folder and click Calculator. If you launch the calculator by right-clicking a
specific well log, calculations will only affect the local log.
A log created from a well top attribute at zone level, with THL as depth scale, gives the calculated thickness per
zone and the corresponding MD. During geosteering, this provides information about the thickness of the reservoir
interval in the horizontal section. Wells are more easily positioned to maintain the well path in the horizontal
section.
For more details, see the Geology online help topic, “Creating THL Logs from a Well Top Attribute.”
Well Usability
Coloring by Attributes
Data managers working with unconventional wells and shale gas extraction frequently perform classification
workflows. When thousands of wells are involved, coloring wells by attributes before visualizing in 2D, 3D, and
Map windows vastly improves identification and interpretation.
Fig 25 highlights the main settings. See the Geology online help topic, “Coloring Wells by Attributes” for how to
assign colors, add the information to the Well manager spreadsheet, and display the wells by color in a Map
window.
Launch the calculator by right-clicking one of these folders and clicking Calculator:
• From the Global well log folder - Creates a calculated log for all wells in the project, provided the logs
being sampled exist in the well.
• From a local log in the well tree - Creates a calculated log in the selected well.
For more details, see the Geology online help topic, “Specifying Log Calculator Folders.”
In addition, pattern display in a Well section window was improved. There is now better tiling with almost no
mismatching joins.
2013.1
Enhanced Cross Sections Object
Creating X-sections
When you create an X-section, a new object will be created in the Input tree in the Cross sections folder. The X-
section settings will manage the well hinges that define the X-section geometry in the Definition tab. Therefore,
you will no longer need to go to the Well Section Window (WSW) settings dialog box to reorder, delete, or add
new well hinges to the X-section. Also, the Well section template will be set from the same dialog box. Only
domain and scale will be handled from the WSW as a result of the decoupling of the Cross sections and the WSW.
Figure 72. X-section settings (left) and Well section settings (right)
By default, a Well Section Window will be created once the cross section geometry is defined. However,
this setting can be changed by turning off the option from the Well Correlation process dialog box.
Any X-section can be displayed in any Well Section Window, and the template will be tied to the object not to the
window.
Acquiring the right acreage and drilling the best prospects are the two main investments impacting exploration
success. Understanding key risk factors is crucial in making these investment decisions. The Exploration Geology
module provides workflows to support these decisions for regional and prospect-level evaluation—from early
phase exploration to appraisal.
Since the results are linked to data and interpretations, there is easy reference to the input geology, rapid updates
with new information, and consistency across evaluations.
The module additionally enables you to gain a contextual understanding of the burial history, source rock
maturation, hydrocarbon expulsion potential and changes to properties over time in the reservoir and overburden
through 1D Petroleum Systems Modeling, using the same simulation algorithms as used in the petroleum systems
modeling software PetroMod. The 3D geocellular model for full dynamic forward modeling of geological processes
in PetroMod software can also be constructed on the Petrel platform. Post-simulation results—transferred to the
Petrel platform—enable further, contextual understanding of source rock maturation and hydrocarbon flow-path
migration processes.
Compatibility between Exploration Geology (plug-in until version 2013.1, module version 2013.2), Petrel, and
PetroMod software:
Petrel 2012 Petrel 2013.1 Petrel 2013.2 PetroMod 2012 PetroMod 2013
The notion “facies”, as it is used in PetroMod, has a different meaning than that of a purely sedimentary (or
tectonic, geochemical, etc.) facies. In PetroMod, the term "facies" includes both lithology and source rock property
information on TOC content and distribution, kerogen type and petroleum generation kinetics. In the PetroMod
simulator, a source rock can only be assigned when a kinetic reaction has been defined for a facies and positive
You can add the lithologies in the Define facies table process via a drop-down menu. This drop-down menu is
now linked to the Petrel templates, not to the PetroMod lithologies via active link.
All standard PetroMod lithologies are now part of the Petrel templates. If you modify or create new lithologies in
the PetroMod Lithology Editor, you need to merge the PetroMod lithologies with the Petrel lithologies. Your user-
defined lithologies will then become part of the Petrel database. Once they have been merged, you do not need the
link to the PetroMod project anymore. Currently, you can only edit the lithologies view their settings in the
PetroMod Lithology Editor. Please refer to the PetroMod Lithology Editor User Guide for more information.
Caution: Each time you change the user-defined lithologies in PetroMod, you need to merge the PetroMod
lithologies again to update the Petrel lithology database. The Petrel lithology database is not an active link to the
PetroMod lithology database.
Separation of “Ages and facies table” into chrono-stratigraphic column and facies
definition table
Ages, facies, and default lithologies have been defined and assigned within Petrel and transferred to the PetroMod
“Ages and facies table”. This process has been split: You can now create a chrono-stratigraphic column, define the
facies in the facies definition table an d connect the data in the Make 1D or Make 3D petroleum systems model
process.
Petroleum systems processes enable construction of 3D geocellular models in Petrel prior to export to PetroMod
petroleum systems modeling software for dynamic forward modeling of geological processes in sedimentary basins
over geological time spans. To utilize the Petrel model in PetroMod, it needs ages, and the facies data need to be
refined with geothermal, paleo-geometry, etc. data.
When running the upscaling with zone correction ON, the input well log is internally translated and re-scaled so
that the correct data is upscaled in each zone, according to the interpreted stratigraphy and even if the model is not
properly tied at the well. (The original input log remains untouched.)
Performing a variogram analysis that fits your data can now be achieved quickly and easily with only a few mouse
clicks. Also, large datasets can be analyzed in a few minutes, thanks to the new data decimation feature.
Petrophysical modeling
Property Modeling with Nested Variogram
The use of nested variogram from data analysis is enabled in all modeling processes:
• Trend modeling (discrete)
• Facies modeling
• Petrophysical modeling
It is only possible to create a nested variogram in the Data analysis process, and then to use it in any of the
processes mentioned above. Nested variogram parameters are also available as read-only in the Modeling Input
Parameters editor for discrete property.
An object variable can be inserted in the With 3D grid command and must refer to 3D grids. The workflow will
then run only on the referenced grids. To run a workflow with multiple grids, the specified grid and the reference
grids must follow these constraints:
• Zone structures must be identical for all grids
• When used in the workflow, property names and contact sets must be unique
For more details, see the utilities section of the online help and the Workflow editor topic, “Using object
variables.”
In combination with the 3D grid uncertainty developments, the enhanced reference list allows building a whole
new range of uncertainty workflows based on discrete scenarios instead of random realizations.
In the following simple example, the same petrophysical model is run four times in a loop with four different
variogram scenarios.
Alternatively, parameters can still be changed in the Facies modeling dialog by double-clicking Facies
modeling or the property name. For more details, see the Modeling online help topic, “Modeling Input Parameters
Editor.”
Object Modeling
Body Shape Enhancements
The Fan lobe (formerly Deltaic/alluvial fan) and Oxbow lake body shapes in Object modeling have been modified to
offer more flexibility.
It is now possible to select the radial profile geometry of the Fan lobe from among the same four options used by
Ellipse shape: Sharp edges, Rounded, Rounded base, and Rounded top.
In addition the Tapering parameter has been added, to allow the lobe to thin longitudinally.
An additional the Channel width parameter allows you to modify the width of the channel independently of the
dimensions of the abandoned meander.
Reporting Enhancements
The output messages for object modeling have been clarified and improved to include detailed result fraction and
geometry statistics per body. This information is now also stored in the Comments tab of the property and
updated every time the property is re-run.
A new workflow editor command (Operations\Model extraction\Output part of grid inside polygon) allows
automating the operation for multiple polygons.
For more details, see the Core online help topic, “Operations tab (Individual Properties).”
NOTE: Parameter changes that are not saved or not run in the previously active grid will be lost.
When any modeling processes are open, you can now also:
• Copy a grid
• Delete a grid
• Copy properties of the active grid
• Delete properties of the active grid
For more details, see the online help topic, “General Information on Property Modeling.”
Geomechanical method
Geomechanically-based driver for constraining fracture modeling in Petrel
This module brings a new geomechanically-based driver for constraining the existing create fracture network
The process for generating such a driver is conceptually simple: first, you need a faults model coming from a
structural framework and fracture data (associated with wells for this release), and, secondly you need to run a
forward modeling using a tectonic stress (imposed or inverted).
Figure 80. Fault framework, fracture data and generated discrete fracture network
Figure 81. Rose diagrams or Fracture data and computed fractures on the WSW
Figure 82. Vector of joint strike and associated discrete fractures network
The created discrete fracture network will follow this fracture density map and the fracture orientation trend as
illustrated in Figure 81.
Figure 83. Computed and calibrated Fracture density and Discrete fracture network
Figure 85. Computed fracture strike and corresponding DFN using classical approach
Set 1
Set 2
Geomechanically-based approach
Assuming that the observed fractures develop during one tectonic event around active faults, there could be only
one set of fractures for this tectonic event, even though the combined rose diagram displays two orientations. The
corresponding fracture network (see Figure 84) created from the perturbed stress field is very different from the one
using the classical fracture analysis approach.
Figure 86. Computed fracture strike and corresponding DFN using geomechanical approach
Set 1
Set 1
2013.1
Well Plan Inspector
(*) Minimum curvature algorithm: Between two neighbor points the curve follows a circular ARC.
When importing Surveys from WITSML files, you also have the options to select the MD and TVD elevation
reference:
• Kelly bushing (KB)
• Mean sea level (MSL)
• Other: type the offset distance to the MSL
3. Click Open to see the Well matching dialog box and remove or change the automatic mapping.
• Wells in file: This column lists all the wells in the risk WITSML file.
• Project wells: This column is to be filled with the matching wells in the Petrel project.
If the wells in the WITSML file have the same names as the wells in the Petrel project Wells folder, the
wells with the same names will be mapped automatically, although you can change this.
Well Deliverability
Petrel Projects with TUFFP Flow Correlations
Because the TUFFP Unified 2-phase v2007.1 flow correlation is no longer supported by Petrel and PIPESIM, you will
receive a warning message if you try to open a Petrel project that was saved with a TUFFP Unified 2-phase v2007.1
flow correlation. In 2013.3, the TUFFP Unified 2-phase v2007.1 flow correlation is replaced with a default flow
correlation.
2013.2
New Production Analytics
The Petrel combined core license enables new features including abilities to manually back allocate, visualize
completion level data in the well section window, and generate grid and bubble maps of production data.
Use the Petrel Split set manager to back allocate the wellbore production to the completion levels by splitting well
level observed data sets into completion intervals called split sets. One of the most important daily practices for
the Reservoir and Production Engineer is allocating the produced volumes back to the reservoir. This practice is
fundamental for many reasons: Material balance, Injection efficiency and Voidage Replacement Ratios
calculations. This practice is sometimes complicated, especially when you are producing from many reservoirs or
layers within the same wellbore. To that end, we are introducing the Split set and the Split set manager into Petrel.
You can manually enter completion level factors for the entire completion or by phase. You can then apply this split
set to a well level observed data set to create a derived completion level data set and use this for visualization.
The streamlined UI for the OFM Data Connector allows the user to map to different data levels for well information
and production histories. You can now map to the completion level or to the traditional well level. The UI is
responsive to well selections and provides a wizard type format to assist the user in mapping OFM completions to
Petrel completions.
As in OFM, you can explain anomalies in production plots with explanations from well notes. For example, as
shown in the screenshot, you will see markers where events have taken place in the lifetime of the well that will
give you context for a well’s behavior. The OFM Data Connector UI has been modified to allow the mapping of the
notes table from OFM.
The default reference depth value, the shallowest completion not squeezed, takes into account the entire well
model as it is configured by the user and all downhole tools within the well model are enabled for sensitivity
purposes.
If the reference depth is modified by the user, the well is treated as a modified well model where the model ends
at the modified depth value and only the downhole completions tools down to the modified reference depth are
displayed for sensitivity purposes.
The IPR model compares the bottom-hole flowing pressure of a well with its production rate. Combined with
NODAL* analysis techniques, the IPR helps to determine the optimal production scheme (most efficient flow
rate), design production equipment, and simulate artificial-lift systems.
In the IPR Model Manager you can derive the IPR model based on well test data, to better represent well
performance. The values corresponding to well test data are plotted along with the IPR curve, so you can check the
quality of the IPR curve. The closer the data points are to the curve, the better the model is.
Click OK to apply the action to this specific duplicated risk. Click OK for all to apply you selection to all
duplicated risks.
In previous releases, setting Well connection factor options (on the Define simulation case process, Strategies
tab) to "Use default calculation in simulator", in addition to using the default values for the transmissibility factor
(COMPAT item 8) and effective Kh (COMPAT item 10), the default skin factor (COMPAT item 11) from the
simulator was used.
When using this option in Petrel 2013.5, the default values for transmissibility factor and effective Kh are used, but
In previous releases, when using partial export on a case having a development strategy using a non-default start
date (that is, not 01 JAN 1980), the START keyword in the RUNSPEC section was incorrectly exported as 01 JAN
1980. This behavior is corrected in Petrel 2013.5.
In order for a partial export to correctly export the entered START date, you should first carry out a full export of
the incorrectly-exported case. The partial export relies on information exported during a full export, and without re-
exporting the START information, will still be exported incorrectly.
From Petrel 2013.3 onwards, multiple realization cases exported outside either the Workflow editor or
Uncertainty and Optimization process no longer include the MULTREAL keyword, and will not use a Multiple
Realization license in ECLIPSE. If you want to run multiple cases that are all associated with each other in a
"multiple realization" relationship, you must export the cases from either the Uncertainty and Optimization
process or Workflow editor.
From Petrel 2013.2 we make use of a new keyword item added to the WSEGVALV keyword in ECLIPSE 2013.1. The
new item is at position 10 of WSEGVALV and allows the maximum cross sectional area of the device to be
specified. This allows a valve to be partially open when first introduced to the simulation as the simulator now
knows the current open area (item 4) and the fully open area (new item 10). WSEGVALV item 10 is only available in
ECLIPSE 2013.1 or later; if you want to use an earlier version of ECLIPSE with Petrel 2013.3, you must explicitly
specify the ECLIPSE version on the Advanced tab of the Define Simulation Case process.
2013.2
Changes to INTERSECT Support in Petrel
When you install Petrel 2013.2, you have the choice between installing the connector to INTERSECT 2012.2 or
INTERSECT 2013.1. The connector is that part of Petrel that creates Field Management strategies and exports
INTERSECT simulation cases. The default choice is to install the connector to INTERSECT 2013.1, the newest
release of INTERSECT. You can later change the connector by using the Modify option in the Petrel E&P Platform
installer.
The INTERSECT 2013.1 connector provides an enhanced Field Management feature that allow the import of a Field
Management strategy into Petrel, and the export of a strategy for review and use in an INTERSECT simulation run.
In addition to the existing supported completion types, the Field management process can now be used to create a
strategy utilizing the new sliding sleeve devices in multi-segment wells.
In addition, in your INTERSECT simulation cases you can now include the new INTERSECT 2013.1 functionality,
which was previously only available for ECLIPSE cases.
• You can use two-phase black oil fluid models
• You can specify the use of the Forcheimer equation for non-Darcy flow using the check box option on the
Function tab of Define Simulation Case dialog. This is relevant for non-laminar flow regimes, for example, in
high flow areas around fractured wells
The WSEGVALV keyword generates pressure drops due to both the constriction and friction within the device. The
frictional component is generated using a pipe diameter and cross sectional area as specified on the WSEGVALV
keyword (items 6 and 8). These items were left at their default values. Under these circumstances, ECLIPSE uses
the diameter and cross sectional area of the segment defined in WELSEGS, where the diameter and cross sectional
area set to those of the constriction. Any calculated frictional pressure drop was therefore artificially too big;
especially when the constriction was particularly small.
This calculation error has been resolved by specifying the pipe attributes directly on WSEGVALV as either the inner
Certain completion design operations make use of a device attribute called ‘physical valves equivalent’. This
attribute allows a single device to represent any number of physical valves on export to the simulator and is
defined by scaling the simulator keyword attributes for that device by the number of physical devices it is
representing.
In previous versions, not all keyword items (in particular 'maximum cross sectional area' on WSEGVALV and
'segment cross sectional area' and 'diameter' on WELSEGS) were scaled correctly, potentially resulting in the
current cross sectional area in WSEGVALV being larger than maximum specified. This difference would cause the
simulator to fail with an error, and has been resolved by this change.
For existing projects with non-midnight time steps, the time steps will now be assumed to be at midnight. In Petrel
2012 there was already a problem with non-midnight time steps for summary results, so this workflow was already
problematic. These issues have been resolved in Petrel 2013 for newly created projects.
If you have an existing project with non-midnight time steps that you would like to open in Petrel 2013 without
losing time information, delete the RSSPEC file from the relevant simulation case directory and it will be
regenerated with both date and time information. This is not done automatically because some information (that is
not used by Petrel) is lost during the regeneration process.
Change of Default Number of Rows in Capillary Pressure Tables in Make Rock Physics
In previous versions of Petrel, by default the capillary pressure table contained twice as many rows as the relative
permeability table. The number of table entries should generally be set to the same value for capillary pressure and
relative permeabilities in order for the combined table exported to simulators to match the tables seen in Petrel.
When Make rock physics is opened and Create new used, the auto-populated default values enter the same
value into both the relative permeability table entries and the capillary pressure table entries fields. After this, you
can independently change the values and thereby revert to the 2008.1–2012.1 behavior if required.
Performance Improvements
Numerous targeted performance improvements have been made to Petrel Reservoir Engineering, as follows. The
The following operations are faster for models with many cells:
• Loading simulation results (especially with a .GRID file over the network).
• Picking a cell in a 3D window to view the cell information in the status bar.
The following operations are faster for models with many wells:
• Displaying summary vectors using the Results charting and analysis process.
• Displaying all wells in a 3D window with simulation results present.
• Switching between 3D windows with simulation results present.
The following operations are faster for models with many LGRs:
• Displaying LGRs in a 3D window with simulation results present.
• Updating the LGR stepping toolbar when displaying a property for the first time.
The following operations are faster for cases with many 3D report steps:
Documentation
Following on from the 2012.1 restructuring of the reservoir engineering sections of the online manual, the following
areas have been refreshed in 2013:
• Wells & completions
• Uncertainty & optimization
The Y value is chosen from a simulation case and the X value is chosen from the observed data set. Any
points on the X=Y line are exact matches. For points below the line, the observed quantity is larger than
the simulated quantity. For points above the line, the observed quantity is smaller.
The options, which depend on the picking mode selected, are listed below.
Option Produces
Don't split Only one chart.
Source One chart for each selected source.
Case One chart for each selected case.
Property A chart for each selected property.
Primary identifier A chart for each selected primary identifier (for example, well)
Quantity A chart for each quantity that the selected properties have. For example,
"Cumulatives", "Limits", and "Rates" will each produce a different chart.
Well Player
The Well player buttons appear on the plotting toolbar when it is possible to move between identifiers in a chart.
You can move between identifiers when data for just one primary identifier, probably a well, is plotted. Identifiers
which have no data are excluded. Suppose you have three wells, P1, P2 and P3 and your chart is showing data for
P1. Clicking the Move forwards ... button displays data for P2; clicking it again shows data for P3.
The Well player is only available for the following picking modes:
• Data vs. time.
• Data vs. time (additive).
• Scatter by time.
Case Player
You can change the selected source for a single chart, or the sources for all the charts in a study. You can change
sources independently of each other.
The Inspector is available for all charts, but operates differently depending on the chart's picking mode. The
Inspector collapses data into the most suitable form for display.
General Mode
This is the standard General mode, where the Inspector displays data for the closest point to the cursor location,
that is, for one primary identifier.
For charts that do not have a Crosshairs mode (Scatter by time, Scatter by identifier, and Simulation vs. observed),
this is the default mode.
After you enable Continuous mode, you do not need to click on the chart; the Inspector is updated as you move
your mouse over the chart. This works with crosshairs enabled or disabled, and across all plotting modes.
Date/Time Format
The format of the date/time displayed is set by the chart theme. In most cases this might be “auto” which results
in the generic MM/DD/YYYY HH:MM style display of time. If you want a more specific date/time format, you must
change it in the chart theme settings.
The imported data appears in the Input pane, stored in a folder called Device control data under Global
completions in the Wells folder.
Example Format
WellDef "P9" {
MDUnit=ft
SlidingSleeve { -- Optional section
ValveType "SSD" -- Optional, determines type of device to build, SSD by default
-- Name StartMD EndMD
“SSDA” 5640 6000
"SSDB" 6000 6400
"SSDC" 6400 6950
}
SlidingSleeveStatus {
DATE 1-Feb-2000
-- Name FractionOpen
"SSDA" 1.0
"SSDB" 1.0
Format Requirements
If you choose not to build the completion from the file contents, each well's completion (including all SSDs and/or
AFCVs) must have been defined in Petrel before the file is imported. Petrel uses the well and device names in the
file to identify each completion device and associate the device 'status' data with it.
When mapping the file contents to an existing Petrel completion, if a well and device name pair cannot be matched
to a Petrel completion device, Petrel writes an error message to the log window.
The WellDef, SlidingSleeve and SlidingSleeveStatus sections must be scoped with curly brackets '{ }'. If
names contain spaces they must be within quotes, otherwise quotes are optional.
MDUnit
The Measured Depth (MD) unit, either “m” (the default) or “ft”. If this is omitted from a WellDef
section, the previously encountered MDUnit value (if there is one) in the file is used.
• Each line in the SlidingSleeve section defines both the well MD interval that flows through a
device (StartMD to EndMD) and the location of the device (at StartMD).
• A sliding sleeve device with default parameters is placed at every StartMD in the section. A default
tubing string is added, extending to the most upstream EndMD within the section.
• A packer is placed at every StartMD and EndMD depth.
• The well is cased to the most downstream packer.
• Well intervals must not overlap each other.
ValveType (optional)
By default the completion is built with SSDs. To build another type of controllable device, change this
value. Currently the only supported device types are SSD and AFCV.
Comments
All text on a line that follows two dashes '--' is treated as comments.
Wells
Drop in a well or folder of wells from the strategy tree. For this rule to work correctly, all wells with sliding sleeve
control should be segmented using Define well segmentation and the segmentation set used when building the
simulation case.
The calculation method is selected from the Well connection factor options field on the Strategies tab of the
Define simulation case process. The options offered are:
• Calculate using E300 method (Petrel default) - the net-to-gross value is used as a multiplier on the Z
component of the well penetration vector through a cell.
• Calculate using E100 method - the net-to-gross value is used as a multiplier on the Z component of the well
penetration vector through a cell and as a multiplier on the height of the block.
• Calculate using scaled permeabilities - the net-to-gross value is used as a multiplier on the X and Y direction
permeabilities.
• Use default calculation in simulator - Petrel does not calculate and export values for the following data. It sets
the values in the simulation input files to the simulator default code, for example '1*' for ECLIPSE.
Transmissibility factor for the connection.
KH.
Skin.
Pressure equivalent radius.
• Look up from grid property – the connection factor is looked up directly from the specified input grid property.
Connection factors for wells within an unstructured grid are always calculated using the Scaled permeabilities
option. In a case where structured grids contain unstructured LGRs, any connection factors calculated for the LGRs
use the Scaled permeabilities option.
When the Use default calculation in simulator option is chosen, the well bore diameter is not set to the default
because the ECLIPSE 100 default value is undefined
For cells connected to one or more wells, the corresponding well connection property is displayed. For any other
cells, no property is shown. In cases where more than one well is connected to a single cell, only one value is
displayed.
To obtain the required data from the simulator, select Grid properties in the Define simulation case process
Results tab, 3D simulation results sub-tab.
Like other dynamic 3D simulation results, these properties can change with time step, for example if a connection
is squeezed. If a well connection is completely shut, no CF or Kh property for that connection is shown.
NOTE: Existing projects are not automatically upgraded to include these dynamic results. If you wish to
load ECLIPSE results for an existing project, reload the simulation results for a case.
The Make rock physics process is used to make changes to functions that are generated from correlations, for
example to change the Corey coefficients of a relative permeability function or the exponent b of the J-function
correlation J = a.eb.Swat. Unless the Use correlation or Use J-function options have been ticked for that part of
an existing saturation function, Petrel does not change it. In this way you can within the same Petrel saturation
function, use relative permeability and capillary pressure / J function functions that are created by Petrel from
correlations and defined by entering the tables directly in the spreadsheet view
This is valuable when for example you wish to run uncertainty on your relative curves generated by Petrel from
correlations, but have fixed capillary pressure functions defined in tables that you do not wish to be changed.
On Upgrade
The current 2008.1- 2012.1 behavior is conserved by default. On upgrade, if you open Make rock physics on an
existing saturation subject, populate the relative permeability, table entries field with the existing tables entries
value (N), and populate the capillary pressure table entries fields with 2N.
When Make rock physics is opened and Create new used, the auto-populated default values enter the same
value into both the relative permeability table entries and the capillary pressure table entries fields. After this, you
can independently change the values and thereby revert to the 2008.1- 2012.1 behavior if required.
NOTE: PATHS keywords are not generated in exported data sets, but can be added as user keywords.
There is a new field and checkbox Use non-Darcy flow (Drainage relative permeabilities only) in the
Functions tab of the Define simulation case process that enables you to select this option and enter the
Forchheimer parameter β. Units are entered in atma.s .g (known as Forchheimer units). Petrel exports the more
2 -1
The default precision for most templates is two or four decimal places. This works well for many, but not all, cases.
Examples of where more precision is required include the following:
• For unconventional fields, a higher precision and use of significant figures is required to represent
nanoDarcy permeabilities.
• For some simulation cases, the rock physics functions require higher precision to correctly simulate multi-
phase flow within the reservoir.
NOTE: Not all numbers in a simulation case are controlled by the template. See Templates used by ECLIPSE
keywords for the details of which templates map to which ECLIPSE keyword item in the ECLIPSE file format
and ECLIPSE simulation case exporter.
For example, for unconventional fields where permeability magnitudes are of the order of nanoDarcies, the default
four decimal places would result in zero values being shown and exported. When importing an existing ECLIPSE
case, it can be critical to preserve the full precision of the original keyword arguments when converting these to
Petrel subjects and then exporting the converted case. Examples are the values within the relative permeability
tables where the step from zero to "not quite zero" is critical for controlling the phase mobility and hence simulated
breakthrough behavior.
Grid Templates
The numeric precision of some Grid keyword items is controlled by templates. The table below shows which
template controls the numeric precision of each Grid keyword item. All other Grid properties use the
template assigned to grid property.
NOTE: Where no item is specified, the template applies to all items in the keyword.
Fluids Templates
The numeric precision of the following keyword items is controlled by the templates shown.
The numeric precision of some wells and completions keyword items is controlled by templates. The table below
shows which template controls the numeric precision of each keyword item.
Field Management
Drag and Drop Modes in the Field Management Dialog
Petrel 2013 introduces two drag and drop modes in the Field management dialog. You can:
• Drag from the Toolbox onto the Strategy pane. This is the same as right-clicking the node and selecting
New and a child node. When you start to drag an item from the Toolbox, nodes that you can drop it into
turn green. If a node which the item can be dropped into is currently hidden (as its parent node has
collapsed children), hovering the mouse over the parent node highlighted in green causes that node to
expand.
• Drag and drop between nodes in the Strategy pane. When a node is dragged from one parent node to
another, if it can be dropped into a property on that node, the node expands showing the list of properties
that the node can be dropped into. This is the same as selecting the target node, and then using the drop
control for the property on the Properties pane.
To exit drop mode, click Drop mode active. From this point, entities can no longer be dropped in. To reactivate
drop mode, just click in the Entity list field again.
• Cancel drop mode after drop - drop mode ends once an entity has been dropped using the blue arrow.
• Alter background color in drop mode - changes the background color of the Strategy pane when in
drop mode.
• In the Constraints field, enter the name of an expression in the format "Expression('<Expression
name>')". For example, for an expression named "New Expression 2", you would enter:
Expression('New Expression 2').
• Click Switch to expression reference adjacent to the field to replace the text with the expression
itself.
1. In the Strategy pane, right-click Regions then select New and Create 3D property region. A New
Region List entry is created.
2. Select the New Region List entry. In the Properties panel, drop the 3D property to use into the Grid
region property field. A region is created for each region defined in the 3D grid property. The region list
is named to match the selected 3D property.
• Always show advanced fields – Select this if you want the Advanced pane to be expanded whenever
a node is selected in the tree. Otherwise, the Advanced pane is only expanded if it was expanded for the
last selected node.
• Cancel drop mode after drop – If selected drop mode ends once an entity has been blue arrow
dropped.
• Alter background color in drop mode – Changes the background color of the tree panel when in drop
mode.
• Show hidden nodes & fields – Select to show hidden items.
• Show programmatic nodes & fields – Select to show these items.
• Show partner nodes & fields – Select to show partner items.
• Switch to IX World tree view – Click to show the tree in INTERSECT format.
The FMOptions element has three attributes, shown on the left of the table. Their effect is shown in the body of
the table (y makes the UI item visible).
Effect
Show partner Show hidden Show programmatic Switch to IX
nodes & fields nodes and nodes & fields World tree view
fields (button)
Attribute PartnerEnabled y
FMSchemaViewEnabled y
Note these INTERSECT 2012.2 features are supported in the Petrel 2012.3 update release and later updates of
Petrel 2012
NOTE: Fault threshold pressure is not supported for stair step faults.
2013.3
Studio Database Compatibility
Petrel Version
2012.3 + YES NO NO NO
2013.1 NO YES YES YES
2013.2 NO YES YES YES
2013.3 NO YES YES YES
Users can set a filter to be used as a synchronization filter limiting what data will be synchronized between the
Studio Database and the users’ Petrel project.
Original CRS
Studio stores the Original CRS information and it can be retrieved from the Database to Petrel. The value of the
Find
Saved Selection
You can now share a list of data items via email or a shared disk with other users. This facilitates a central team or
a specific data administrator to load data on someone’s behalf. It also allows certain data sources to be visible to
users while allowing control over how the data is loaded. It is also now possible to import data items using a
previously saved list.
2013.1
User Interface
The Petrel 2013 release brings several enhancements to the general user interface: a unified help center, updated
window scheme and icons, and changes in the way the data tree synchronizes with actions in the display window.
This behavioral change results in reduced interaction with the data tree. For example, if grid A and grid B are
displayed in the 3D window and you want to set the Property player direction:
• In Petrel 2012, you must make the appropriate grid active in the Model tab.
• In Petrel 2013, selecting the property in the 3D window automatically makes it active, and the Property
player is immediately available for that property.
Large cultural data sets consisting of thousands of polygons could cause severe performance issues in previous
Petrel releases. These are now solved by using graphic card hardware to display the data in the Petrel 3D or 2D
window.
These improvements allow you to continue working interactively in 2D and 3D windows while handling larger and
more datasets without compromising fidelity or accuracy.
The following list summarizes the keyboard and mouse actions you now use to edit points and polygons:
• Select points –Click a point. To add or remove points from the selection, hold down Shift and click.
Selected points can be dragged in the 3D window, deleted, or acted upon by operations in the Process
actions toolbar.
• Select polyline – Click the line between points to select all points in the line.
• Select bounding box – Click the background to initiate a bounding box selection. To add or remove
points from the selection, hold down Shift and click.
• Deselect all points – Click the background to deselect all points.
• Add points to an existing polygon – With at least one point already selected, hold down Ctrl and click
System Enhancements
Refer to the Petrel 2013 Installation Guide for more information about the following improvements.
Startup Optimization
Petrel 2013 introduces a Startup Optimization setting which is enabled with the Petrel installer.
Startup optimization is switched on by default. After Petrel has been installed and the system is idle, Ngen starts
to create native images and stores them on the local PC. This will only take a couple of minutes, depending on the
system load. The whole process is invisible to users, and the system controls when to create the native images and
when to use them.
Once the native images are created, they are used every time Petrel is launched and this improves startup
performance significantly. For further information please read the relevant section of the Petrel 2013 Installation
Guide.
Installation Progress
Petrel 2013 introduces a progress bar for the installation procedure, informing you about progress and status on
every installation step. In addition, a progress bar is shown when launching Petrel indicating the current task
Memory Monitoring
Physical RAM memory utilization is further increased with Petrel 2013. Many operations use the CPU and persist in
the machine’s physical memory (RAM). It is therefore useful to be informed about the utilization level of the
memory buffer, because the overall Petrel performance is affected when operating at memory-size limits.
Petrel 2013 introduces a monitor gauge in the lower-right menu bar. It measures current usage of physical RAM
memory. When usage reaches 90%, the monitor turns red to indicate that you should show caution when executing
further memory-intensive tasks. Petrel will not abort, but performance gradually degrades when consistently
operating > 90% memory usage. A gauge tooltip provides detailed information on the memory usage. Clicking the
RAM gauge is a shortcut to launching Tools>>Free memory from the main menu.
Version Identifier
Petrel projects stored on disks identify themselves through the name, extension, and Petrel icon. However, it is
often useful to know which Petrel version was used the last time the project was saved. Previously you needed to
open the project to discover this information. Petrel 2013 introduces a version identifier in Windows Explorer.
Once selected, the Petrel version displays in Explorer, as illustrated in the following example. The File Version
identifies Petrel projects from Petrel 2011 or later. From Petrel 2013 forward, minor versions (2013.x) are also
exposed.
When importing data into Petrel, you choose the CRS that your data refers to by using the CRS selector. The
catalog choices are typically provided and maintained by your geodetic department using the Coordinate System
Manager in Studio* Manager.
Other data connectors or CRS definitions (for example, from OpenSpirit* Petrel Adaptor or Joint Ventures and
Partners), create data in Petrel with original CRS references to the external data sources. In this case, the new CRS
definitions entering your Petrel project may not be listed in the Petrel CRS catalogs.
CRS matching is complex. For data loaders and transfers, it is generally better to leave the CRS definitions as close
as possible to the original CRS and avoid matching. In the long run, however, it is not desirable to keep multiple,
synonymous CRS definitions in parallel. This is particularly undesirable in the Studio environment, where a CRS
must be present in the reference tables prior to data transfer.
Over time, human error may introduce undesirable CRS naming conventions, e.g., as the result of a typo in a name.
The CRS definitions then become replicated inside multiple Petrel projects. Corrections in the CRS catalogs address
the problem only for new projects and newly-loaded data. Existing projects continue to refer to the old, misnamed
CRS definition.
Any Petrel user can submit a CRS consolidation request, which is then approved by a geodetic expert. This is a
four-step process:
1. In the data context of a Petrel project, users propose a new CRS definition for existing data. This is done
by selecting a CRS from the catalog. The proposals are gathered in a separate proposed CRS replacement
table. Once a set of replacements are proposed, the geodetic expert is notified about the proposals, for
example by email with attached proposed CRS replacements.
2. The geodetic expert reviews the proposed CRS replacements and validates them. The validated
replacement pairs are compiled into the approved replacement table, which is a separate data file. The
file format is xml, which can be edited by text editors or in Microsoft® Excel. The geodetic expert should
also review the description of the reason for the replacement, because the rational will appear in the data
history.
Details:
• Catalog handling
o The <Petrel.exe-path>\xml\ CoordinateCatalogConfiguration.xml contains the definition of the
catalog location on disk/network as well as where the user and enterprise catalogs of previous
versions are expected.
o The <Petrel.exe-path>\xml\ESRI10AddOnsCatalog.ctl contains the new CRSs and transformations
known to the new ESRI 10.1 engine; the content is merged into the CRS enterprise catalog on
upgrade.
o Old Petrel projects and catalogs are updated when first loaded to Petrel 2013
ESRI corrections are managed via upgrade files. These files contain the instructions
how to preserve the previous engine behavior. The upgrade files are deployed in:
<Petrel.exe-path>\EsriCatalog\upgrade\CatalogUpgrade9.3.0.txt contains the
replacement instructions for project upgrades from Petrel 2010 to 2011/2012.
<Petrel.exe-path>\EsriCatalog\upgrade\CatalogUpgrade10.0.txt contains the instructions
for upgrade from Petrel 2011/2012 to Petrel 2013.