Release notes 2019.

5
Copyright Notice

Copyright © 2019 Schlumberger. All rights reserved.

This work contains the confidential and proprietary trade secrets of Schlumberger and may not be copied or stored in an information retrieval
system, transferred, used, distributed, translated or retransmitted in any form or by any means, electronic or mechanical, in whole or in part,
without the express written permission of the copyright owner.

Trademarks and Service Marks

Schlumberger, the Schlumberger logotype, and other words or symbols used to identify the products and services described herein are either
trademarks, trade names or service marks of Schlumberger and its licensors, or are the property of their respective owners. These marks may not
be copied, imitated or used, in whole or in part, without the express prior written permission of Schlumberger. In addition, covers, page headers,
custom graphics, icons, and other design elements may be service marks, trademarks, and/or trade dress of Schlumberger, and may not be
copied, imitated, or used, in whole or in part, without the express prior written permission of Schlumberger. Other company, product, and service
names are the properties of their respective owners.
Petrel® is a mark of Schlumberger.
An asterisk (*) is used throughout this document to designate other marks of Schlumberger.

Security Notice
The software described herein is configured to operate with at least the minimum specifications set out by Schlumberger. You are advised that
such minimum specifications are merely recommendations and not intended to be limiting to configurations that may be used to operate the
software. Similarly, you are advised that the software should be operated in a secure environment whether such software is operated across a
network, on a single system and/or on a plurality of systems. It is up to you to configure and maintain your networks and/or system(s) in a secure
manner. If you have further questions as to recommendations regarding recommended specifications or security, please feel free to contact your
local Schlumberger representative.
 TABLE OF CONTENTS

OVERVIEW
Distribution............................................................................................................................................................................................................. 2

REQUIREMENTS
System requirements............................................................................................................................................................................................3
Operating systems..........................................................................................................................................................................................3
Studio database system requirements..............................................................................................................................................................3
Licensing requirements........................................................................................................................................................................................4
Project compatibility.............................................................................................................................................................................................4

NEW FEATURES AND ENHANCEMENTS

Geology................................................................................................................................................................................................................... 5
Well section window..................................................................................................................................................................................... 5
GPM.........................................................................................................................................................................................................................5
Usability............................................................................................................................................................................................................5
GPM 2D............................................................................................................................................................................................................ 5

KNOWN ISSUES
Geophysics.............................................................................................................................................................................................................7
General.............................................................................................................................................................................................................7
Seismic Well Tie..............................................................................................................................................................................................7
Geology................................................................................................................................................................................................................... 7
General.............................................................................................................................................................................................................7
Well Section Window.................................................................................................................................................................................... 7
Reservoir and Production Engineering..............................................................................................................................................................8
Simulation........................................................................................................................................................................................................ 8
Structural Modeling............................................................................................................................................................................................10
Structural Framework Modeling................................................................................................................................................................10
Gridding..........................................................................................................................................................................................................11
Property Population..................................................................................................................................................................................... 11
Geomechanics.....................................................................................................................................................................................................11
Reservoir Geomechanics............................................................................................................................................................................11
Reservoir Modeling.............................................................................................................................................................................................11
Exploration Geology............................................................................................................................................................................................12
Petroleum Systems Modeling.................................................................................................................................................................... 12
Petroleum Systems Quick Look..................................................................................................................................................................12
Play Chance Mapping..................................................................................................................................................................................12
GPM.......................................................................................................................................................................................................................13
Shale......................................................................................................................................................................................................................13
Geosteering................................................................................................................................................................................................... 13
Studio.................................................................................................................................................................................................................... 13
Guru....................................................................................................................................................................................................................... 13
Foundation............................................................................................................................................................................................................14
Profiles .......................................................................................................................................................................................................... 14
Printing........................................................................................................................................................................................................... 14
Mapping......................................................................................................................................................................................................... 14
Core....................................................................................................................................................................................................................... 14

SUPPORT INFORMATION
User assistance...................................................................................................................................................................................................15
Contact Schlumberger....................................................................................................................................................................................... 15

i
RELEASE NOTES 2019.5

Overview

Finding, characterizing, and exploiting new and existing reservoirs is increasingly complex. To overcome these
challenges, we must continually improve and innovate the way we work. With the Petrel E&P Software Platform,
Schlumberger revolutionized the oil and gas industry by bringing disciplines together with best-in-class science in an
unparalleled productivity environment.
Our commitment to Petrel resulted in dramatic strides forward in the way we develop and deliver a software platform, and
with the Petrel 2019 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.
With this Petrel E&P Software 2019.5 minor release, Schlumberger continues its commitment to improve and innovate the
way you work. Petrel allows multi-domain experts to co-create a shared earth model that can be continuously updated as
new information is acquired. These release notes contain short descriptors for the most significant enhancements, fixed
issues, and known limitations, as well as system requirements and recommendations.

Distribution
The Petrel 2019 release is available by download using the appropriate links on the Software Integrated Solutions (SIS)
Support Portal. A user account is required on the portal. If you do not already have a user account, you can register to
access the portal at https://www.software.slb.com/support.
The full set of Petrel 2019 documentation, and documentation for any prior Petrel release, can be downloaded from the
Software Integrated Solutions (SIS) Support Portal.

2
 REQUIREMENTS

Requirements

This section contains Petrel system requirements, Studio* database requirements, licensing requirements, and project
compatibility.

System requirements
For more information on the Petrel system requirements, operating systems, and hardware selections, please refer to the
Installation Guide.

Minimum Preferred

Processor Quad-core processor (best with a fast clock Dual 4 to 8 core processor (best with a fast
speed and high cache) clock speed and high cache)

Memory 16 GB RAM (32+ GB recommended) 64 GB RAM

Display The quality of the viewing experience increases with the size and number of monitors

Graphics desktop NVIDIA® Quadro® P4000 or NVIDIA Quadro NVIDIA Quadro P6000 or P5000
P2000

Graphics mobile NVIDIA Quadro P3000 or NVIDIA Quadro M2200 NVIDIA Quadro P5000 or P4000

Primary storage Fast rotational speed HDD (10K, 15K RPM) or PCIe based Flash or SSD
SSD

Secondary storage Optional SSD or Fast rotational speed HDD (10K, 15K)

• The Petrel interface is optimized for horizontal resolutions from 1280 and higher and for vertical resolutions from 1024
and higher.
• Support for VR (virtual reality) has been removed from Petrel 2017 onward.
• Windows 10 updates - Microsoft® supports semi-annual update channel (includes .NET®) - future Petrel versions will
be supported on the current channel update at the Petrel release date.
• Schlumberger continually tests the latest hardware available from major suppliers. In an attempt to minimize
unexpected problems and costs, Schlumberger often uses branded solutions such as those offered by HP®, Dell®,
Lenovo®, Intel®, and NVIDIA.

Operating systems
Microsoft Windows 10 Professional or Enterprise Edition (64-bit)
Microsoft Windows 7 with SP1 Professional or Enterprise Edition (64-bit)

Studio database system requirements

Oracle databases

Minimum Preferred

Operating system Red Hat® Enterprise Linux® 7.2 (64-bit) Red Hat Enterprise Linux 7.3 (64-bit), CentOS 7.3
(Kwin, WindowingManager)

Processor x64 dual quad-core processor x64 dual six-core processor

Memory 32 GB 64 GB or greater

Other required software Oracle® Database Enterprise Edition 12.2.0.1 (64-bit)

System requirements 3
RELEASE NOTES 2019.5

Microsoft SQL server databases

Minimum Preferred

Operating system Windows Server® 2012 R2 Standard (64-bit) Windows Server 2016 (64-bit)

Processor x64 quad-core processor x64 quad-core processor

Memory 32 GB 64 GB or greater

Other required software SQL Server 2016 SP1 Standard Edition

Licensing requirements
Petrel 2019 requires the 2017 version of the Schlumberger Licensing Tool.
• Petrel 2019 will not work against a Schlumberger 2015 or earlier License Server. You must use a Schlumberger 2017
License Server.
• All older versions of Petrel will continue to work against the 2017 License Server.
• The 2017 Licensing Tool is available from the Licensing folder on the Petrel DVD.
A Petrel dongle and a valid license are required to run this release. Petrel licenses incorporate two important dates: the
maintenance expiry date and the license expiry date. You can verify the validity of your license, as follows:

FEATURE Petrel_01220255_MAAAdLyku/aUAslbsis<yyyy.mm> <d-mmm-yyyy>.<#>

Where:
• <yyyy.mm> is the maintenance expiry year and month
• <d-mmm-yyyy> is the license expiry day, month, year
• <#> is the number of licenses

Project compatibility
The Petrel platform preserves the value of your historical data. Projects saved in all earlier Petrel versions will load
directly into Petrel 2019 without any need for data migration. However, note that projects saved with Petrel 2019 will not
be backwards compatible (e.g. cannot be opened) with earlier versions.

4
 NEW FEATURES AND ENHANCEMENTS

New features and enhancements

The following content contains descriptions of new features and behavioral changes in this release, organized by domain.

Geology
Well section window
Empty well section templates folder: Fixed an issue where the Petrel system templates folder under the Well section
templates folder was empty when creating a new project in Petrel 2019.3 or Petrel 2019.4.

GPM
There are many improvements to the existing GPM functionalities and usability. These changes are expressed as new
controls in the existing process and as a complete reorganization of the tabs and subtabs. In addition, a new GPM 2D
mode is now available, which enables you to easily and quickly build GPM models as 2D cross-sections. Such 2D models
are used to rapidly test and validate different geologic scenarios thereby providing additional support to workflows such
as well correlation, seismic interpretation and prediction of the rock distribution, reservoir connectivity and potential
stratigraphic traps.

Usability
• New user interface: All the dialog boxes have been updated to make the user experience smoother and more intuitive.
The Run sedimentary simulation dialog box has been reorganized into three main tabs: General, Geological processes,
and History. In the Geological processes tab, all the intermediate folders (tectonic, point source, areal source) have
been removed and the process events are now managed, using tables, under each specific process.
• Context menu: You can now access processing and conversion options for GPM software model results from the
context menu. Some of the previous context menu options have been replaced and new options have been added.
• Data management: GPM results were previously stored in the Petrel project .dat folder and also created as an .hdf5
file. Simulation results are now only created as .hdf5 files and are no longer stored in the Petrel project .dat folder.
Therefore, the simulation result objects visible in the Input pane are now only links to the corresponding .hdf5 files,
similar to the way in which seismic data is managed in Petrel.
• Algorithm changes: Changes were made to the Wave and Steady flow algorithms to improve the performance of both
the simulation and results.

GPM 2D
GPM 2D is a complete forward stratigraphic modeling solution based on the same technology as GPM 3D. It enables the
simulation of sedimentary deposition through time and is based on processes such as growth, erosion, transport, and
deposition of clastic and carbonate sediments in a user-defined 2D cross-section.
It can be used to predict stratigraphic architecture and lithology variations and estimate porosity and permeability in a 2D
section.
Using GPM 2D, it is very fast and easy to build a model and to quickly run multiple iterations. Therefore, you can use this
tool to have a quick look at and get an overview of possible sedimentology and stratigraphy scenarios.
Because GPM 2D runs in a 2D section and is aimed at achieving very fast simulations, some more elaborate GPM
geological processes are not available, such as steady flow, unsteady flow, and wave action. These geological processes
are available in GPM 3D for more complex simulations.
GPM 2D simulation results include:
• An understanding of the effect of the main controls of the sedimentary processes in your sedimentary system.
• The distribution of sediment types and rock properties along the 2D section.

Geology 5
RELEASE NOTES 2019.5

• An understanding of the possible sedimentary architectures and their implications for well correlation, seismic
interpretation, reservoir connectivity, and the potential for stratigraphic traps.
• A definition of the stratigraphic controls such as sea level variations, synsedimentary tectonics, compaction, and
sediment supply required as inputs for the more elaborate GPM 3D models.

6
 KNOWN ISSUES

Known issues

The following content summarizes known issues and limitations organized by domain.

Geophysics
General
• Mesh probes:
• There may be an error when converting a mesh probe made from multi-z data into a seismic cube. This is best
checked by playing converted timeslices through the original multi-z data to check that the conversion is correct.
• There will be an error when extracting geobodies from a volume mesh probe made from seismic horizons or
surfaces that have holes in them.
• Horizon probes: Horizon probes use an on-demand view. This is not cached when the project is saved. Therefore, on
reopening a project that contains a horizon probe, the surface or horizon must be resampled the first time the probe is
displayed. For large surfaces, this can take a considerable amount of time. You may wish to close the window that
shows the probe before you save the project, or press Ctrl when opening the project (this opens the project with no
windows open).
• Meshes: You cannot create an editable mesh from 3D interpretation data if there are gaps between interpreted points,
for example if you have interpreted on a cube with an increment greater than the survey increment. You can resolve
this by either interpolating the data or converting to a surface.

Seismic Well Tie

Depth seismic calibration study:
• If a well is transferred from Studio, the active DDR in the project is reset to the DDR that was active for this well when
it was transferred to the Studio repository. In this case, after the transfer, you must activate the required DDR log.
• A depth seismic calibration study with only bulk shift applied created prior Petrel 2019.2 has incorrect depth
correction values when the project is upgraded.
Workaround: Open the Seismic well tie Tool Palette, select bulk shift, remove it and then apply the same bulk shift but
with the opposite sign.
• A depth seismic calibration study created in Petrel 2019.4 with bulk shift or bulk shift plus manual corrections is not
supported by earlier Petrel 2019 versions.
• Deleted depth correction attributes re-generate each time a new depth seismic calibration study is created.

Geology
General
Contour lines disassociated from a surface: In some cases, when a surface is rotated, the contour lines can be
disassociated from the surface after running a workflow. This issue is currently under investigation.
A potential workaround to resolve this issue is to save the project with a different name.

Well Section Window

• Style tab for depogrid properties: Style tab edits for depogrid properties are not preserved if the project is opened in
2018.1. Default settings apply in Petrel 2018.1 and the Style tab is not available.
• Custom templates in the Well Section Window: Surfaces cannot be displayed in the Well Section Window when using
custom templates inside the Well Section Window.

Geophysics 7
RELEASE NOTES 2019.5

Reservoir and Production Engineering

Simulation
• User edits with FM Strategy: If you have created User Edits for Field management strategy prior to Petrel 2018.1 and
they contain nodes related to region mapping, they must be updated to match the new node names.

Old (pre-2018.1) New (2018.1 and later)

RockMechanics ROCK_MECHANICS

DrainageSaturationFunction DRAINAGE_SATURATION_FUNCTION

DrainageSaturationNonDarcyFlows NONDARCY_FLOWMODEL_DEFINITION

ImbibitionSaturationFunction IMBIBITION_SATURATION_FUNCTION

Adsorption ADSORPTION_MODEL

MiscibilitySaturationFunction MISCIBLE_SATURATION_FUNCTION

LowSaltSaturationFunction LOW_SALT_SATURATION_FUNCTION

RelPermHysteresis REL_PERM_HYSTERESIS

CapPressureHysteresis CAP_PRESSURE_HYSTERESIS

RelPermCapNumber REL_PERM_CAP_NUMBER

FluidPVTModel FLUID_PVT_MODEL

FluidEOSModel FLUID_EOS_MODEL

EqulibriumEQLModel EQULIBRIUM_EQL_MODEL

EqulibriumPVTModel EQULIBRIUM_PVT_MODEL

EqulibriumEOSModel EQULIBRIUM_EOS_MODEL

• EOR Surfactant workflows: In INTERSECT 2019.1 and later, the surfactant workflow is compatible with black oil
simulation with oil, water, and gas defined.
Dual porosity, compositional, API tracking simulation, and J-function are not supported with surfactant. Refer to
INTERSECT Technical Description for a detailed compatibility list.
• Initial conditions process for depogrid: The Initial conditions process is not supported for depogrids in this release.
• Depogrid INTERSECT cases do not support PINCH: INTERSECT does not currently support the generation of
connections across pinched-out layers (PINCH keyword in ECLIPSE) for unstructured grids such as depogrids. Pre-
release testing suggests that the material impact on the simulation is limited when realistic property distributions are
used.
In a structured grid, pinched-out layers either represent layers of zero-thickness cells or represent cells that have
been made inactive because their overall cell thickness or pore volume is less than the specified threshold value. The
presence of a layer of inactive cells would normally prevent flow from crossing between the active cells immediately
above and below. So, you can turn on the option within the simulator to automatically generate non-neighbor
connections that allow fluid to flow between these active cells.
However, in a depogrid you cannot have cells of zero thickness. In addition, we tested the impact on the simulated
reservoir flows across cells made inactive with pore volume cut-off values on a selection of synthetic and client
models that contained the thin layers and flat erosions. While you can create flow barriers in synthetic examples with
constant reservoir properties, when representative property distributions were used, unrealistically large pore volume
cut-off values were required to see a material flow barrier.
• Case conversion – Convert to INTERSECT Field Management cases: The ability to convert a simulation case to a Field
Management case is an additional option that has been added to the Case Conversion dialog box. It enables you to

8
 KNOWN ISSUES

convert cases that use INTERSECT Development Strategies to cases that use INTERSECT Field Management
strategies. This is a pre-commercial feature, and has some limitations in this release. It can convert many cases, but
you may encounter some problems.
Most types of cases can be inserted in the Input case field. Select the type of case that you want to convert the input
case to. Where check boxes are disabled, there is no supported conversion to that case type. The selected case
types determine the new cases that result. Petrel may generate intermediate cases during conversion, but unless
these case types were explicitly requested they are deleted before conversion finishes.
Here are some hints to help you overcome the issues you may encounter:
Many cases convert without problems – if conversion errors occur, error messages appear and the case types that
you selected may not be created. You can still achieve the conversion you want by isolating the problems, making
changes to cases, and re-running the conversions.
To do this, run the conversions in stages. For example, if you are starting with an ‘imported’ case (an ECLIPSE deck
managed by a Petrel case), and you want to convert this to an INTERSECT Field Management case, Petrel does the
following conversion stages in sequence, for a single use of the Convert Case dialog box:
1. Conversion of the ‘imported’ case to a ‘modeled’ ECLIPSE case (this was called Convert to Petrel case in Petrel
2017).
2. Conversion of the ‘modeled’ ECLIPSE case to an INTERSECT Development Strategy case.
3. Conversion of the INTERSECT Development Strategy case to an INTERSECT Field Management case.
Instead, do each of these three conversions separately, using the Case Convertor dialog box each time. After each
conversion, try to export and run the case that was just created.
If you see errors at any stage, or simulation results that do not match, then try to resolve these issues first (by either
modifying the input or output case).
Where there are problems with conversion (2), it can be helpful to run the INTERSECT Migrator directly on the
exported ECLIPSE case (outside Petrel) to check if the same problems are seen.
Conversion (1) can create ECLIPSE ‘user keywords’ in the converted case, these are a common cause of conversion
problems.
Conversion (2) can create INTERSECT user edits in the converted case, these should be the INTERSECT ‘equivalent’ of
the user keywords in (1).
Conversion (3) can also create INTERSECT user edits in the converted case. These should mostly be the same as the
user edits in (2) but with some different IXF node names, caused by different naming formats between DS (ECLIPSE
format) and FM (full Petrel entity names). It may be possible to correct some types of error by editing the generated
user keywords or user edits.
Some known limitations in this release:
• Type (2) or (3) conversions are not supported for:
• Restart cases
• Cases containing Initial Condition Sets
• Cases with grids that cannot be reasonably accurately represented in Petrel EGRID format.
• Type (2) conversions for cases containing user keywords are not supported for:
• Initialization cases (in other words, no Development Strategy).
• Cases with user keywords affecting grid geometry.
• Type (3) conversions are not supported for cases that have Development Strategy schedule keyword rules
containing COMPSEG(S/L).

Reservoir and Production Engineering 9

RELEASE NOTES 2019.5

Structural Modeling
Structural Framework Modeling
• Fault modeling – Running converted fault frameworks: Previous (pre-2018) structural frameworks must be converted
to new domain objects and rerun. Fault modeling parameters are converted as they are, but for some cases are used
differently, for example the fault smoothing parameter.
• Fault modeling – 2018/2019/2020 versus previous versions: Framework faults modeled with previous versions may
differ from faults modeled with the new fault framework modeling algorithm, even though the same parameters have
been used. Any derived output from fault modeling is also expected to change. To minimize such differences, the
pre-2018.1 framework fault can be converted into points and assigned as input to the new fault model.
• Fault modeling – Modeling while interpreting: Fault modeling while interpreting is not yet enabled on the new
framework faults.
• Fault modeling – Fault extrapolation distance: Depending on the fault shape and dip variations, the extrapolation
distance might not be isotropic.
• Fault modeling – Fault truncation editing: Fault patches can only be truncated when the corresponding intersection
line entirely disconnects the fault patch. A truncation rule specified in the Framework fault modeling process which
cannot be applied will not be automatically set to none. In other words, the fault relationship table will be inconsistent
with the Framework faults.
• Model construction – Filtering of stratigraphic model input data: The filtering of stratigraphic model input data could
be performed for selected faults at specific distances in the horizon modeling process prior to Petrel 2018.1. This is
now handled by filtering attribute generation in the Horizon clean-up process and attribute consumption in the Model
construction process. Bulk fault filtering (one value for all faults but for selected input) is still possible in the Model
construction process.
• Model construction – Incorrect dip-trend extrapolation along faults and at model boundary: Without enough data to
constrain horizons close to faults and the model boundary, those horizons can present an incorrect shape, for
example in narrow fault blocks where the input data has been filtered. The editing of filtering parameters (edit
attribute, reduce bulk filtering) and manual addition of new unfiltered data can reduce these effects.
• Model construction – Model faults versus Framework faults: Model faults resulting from the Model construction step
are re-meshed versions of the framework faults. Depending on the change in mesh resolution, model faults may have
a different shape and no longer explicitly match the fault tops used in fault modeling.
• Model construction – Spikes or bubbles in non-refined horizons: Non-refined horizons extracted from the stratigraphic
can in some cases present spikes or bubbles. These artifacts can often be related to inconsistent stratigraphic input
data (very noisy interpretation, omitted faults, competing data, and other anomalies). Such inconsistencies are not
necessarily present in the input data corresponding to the horizon where those artefacts are observed. These
inconsistencies may be derived from any other input data for the affected conformable sequence.
• Model refinement – Degradation of refined versus non-refined horizons: Where the non-refined horizons (from the
Model construction process) are far away from the corresponding input data, issues can occur during the refinement
of those horizons. In a setting where one or more refined horizons are snapping to the input data, but intermediate
horizons do not have any input data to snap to (for example, well-based horizons), refined horizons may cross even
when the Enforce consistent zone thickness option is activated. Where the horizon input data contains uninterpreted
areas, models will snap to the data where interpretation is present and not in those areas where no interpretation has
been generated. This scenario may also result in horizon irregularities.
• Model refinement – Keep only blocks: The Keep only blocks with input data option in the Model construction process
is not compatible with the Depospace calculation process and with the Structural gridding process when using the
stratigraphic layering type.
• Depospace calculation – Overlapping zones or gaps in depospace: Unbalanced structural models due to inconsistent
fault/horizon cut-off lines can result in overlapping areas or gaps in depospace view. Overlaps can be seen in the
mesh view of the zones.
• Depospace calculation – Optimization: Depospace performance optimization per conformable sequence (pre-2018.1)
is currently not compatible with the underlying stratigraphic function structure and depogrid, and has therefore been
disabled.
• Depospace calculation – Geodesic distances: The current depospace calculation uses a vertical mapping step to
flatten the conformable horizons, and consequently geodetic distances may not be preserved in certain cases.

10
 KNOWN ISSUES

• Depospace calculation – Isolated fault blocks: Zones identified as isolated fault blocks are not handled in Depospace.
To remove isolated fault blocks, at least one data point must be added into each block.
• Operations – Convert horizon to surface: The conversion of model horizons to surfaces has been removed.

Gridding
• Depogrids in multi-sequence models: For depogrids built from structural models including non-conformable horizons
(erosion, base, or discontinuity), small gaps or interpenetrations may be observed locally between grid cells across
the unconformity. These may create small-scale localized artifacts. The impact on downstream property modeling,
volume computation, and reservoir simulation has been assessed as low.
• Depogrids with a lateral resolution different from the parent structural model: It is recommended to build a depogrid at
a similar lateral resolution to the parent (refined) structural model. Issues may be observed when those resolutions
significantly differ. In particular, small-scale localized mismatches between the depogrid horizons and the structural
model horizons may be observed when the grid resolution is finer.
• Depogrid layering issues in certain cases of high aspect ratio cells: The distribution of the layers within a zone may
not strictly be proportional in certain cases of grid cells with a high aspect ratio. The extreme case is self-intersecting
cells that may locally be observed around faults or well tops.

Property Population
Depogrid support workflows: The following property modeling processes/methods/options are not available for
depogrids:
• Zone correction option in Well log upscaling.
• Multi-point simulation with patterns object method for discrete properties.
• Create variograms from properties in Settings.
• More tab for continuous properties.
• User-defined object for 3D depogrid properties data type.
• Store and populate the contact option in the Contacts process.

Geomechanics
Reservoir Geomechanics
• VISAGE INTERSECT coupling
• The pore volume updating of the fracture model can be unstable for large pore volume changes causing
convergence issues in the INTERSECT simulation. In this case, you are advised to turn off the pore volume
updating of the fracture model.
• This release does not support the remote transfer of coupled VISAGE/INTERSECT cases.
• Quick MEM: Does not support LGRs.
• Mud weight predictor: Does not support LGRs.
• Geomechanical grids: LGRs are not supported for grids that contain bad cells.
• Creep: Including creep in the geomechanical simulation can significantly increase the simulation runtime, especially
when choosing Power law creep or Visco-plastic shear stress removal for initialization with a low creep tolerance
and long time period.

Reservoir Modeling
• General folder in MIPS folder: If a 2019.2 project that contains general folders inside the Facies or Petrophysical MIPS
folders is opened in Petrel 2019.1, the folders are not valid. Make sure that all MIP objects are stored outside of
general folders if you intend to save the project in 2019.1. If not, the MIP objects will be corrupted when the project is
saved in 2019.1.
• Data analysis settings in MIP objects: Currently only single variogram structures and global facies fractions are
captured in MIP from data analysis. Proportion, probability, and transformation curves are not stored in MIP.

Geomechanics 11
RELEASE NOTES 2019.5

• MIP object unit dependency with RPT: It is not possible to transfer MIP objects between projects if the XY and Z units
if the Working and Background projects are not the same.
• Uncertainty and optimization - Trend modeling: 2D discrete Trend modeling process is not restored in the Uncertainty
and optimization process when its output is used as input in a process defined in a case. Only discrete 3D trend
modeling is listed in the Uncertainty and optimization workflow. 2D trend models can be added to the workflow
through Edit workflow in Unceratinty and optimization process.

Exploration Geology
Petroleum Systems Modeling
• 2D extraction from 3D model: When you display a property, and show the default or more cell boundaries (horizons
and vertical lines), and then turn on a different property, the cell boundary lines are no longer visible.
Workaround: Rotate the model to make them reappear.
• Import 3D input model from PetroMod to Petrel: Take care when importing models that contain layers which were
completely deposited and eroded because the number of sublayers (at present day) does not match the number of
created horizons.
Workaround: The top horizon of a layer, which was completely deposited and eroded, must be assigned manually in
the Create 3D model process after importing the model. Note that the naming convention of that horizon differs
between Petrel and PetroMod.
• Extract and export 2D interpretation from seismic lines: Extract and export 2D interpretation from seismic lines does
not support cropped lines. Workarounds:
• Use the uncropped line for the extraction and export.
• Convert the cropped line to 2D seismic (right-click on the line, then select Convert to 2D seismic in the shortcut
menu) and right-click the resulting 2D seismic line to access Extract and export to PetroMod.
• Create 3D model Map-based mixing: Map-based mixing does not work for models that contain erosion events when
facies are assigned from the table. If lithology mixing ratios are defined from grid properties and erosion is to be
modeled at the same time, the simulator reports that some elements have no lithological information. This is because
the mixing ratio property is not defined for the missing elements (due to erosion).
Workaround:
1. Export the model to PetroMod.
2. Convert cube data to maps.
3. Fill in any undefined values using the map editing tools in PetroBuilder 3D.
4. Simulate the model.

Petroleum Systems Quick Look

Petroleum Systems Quick Look lithologies not available to petroleum systems modeling outside of PSQL: Petroleum
Systems Quick Look (PSQL) lithologies are generated by default in a main folder. Note that lithologies located in main
lithology folders are not merged with PetroMod. Therefore, the simulator does not have access to them, and they cannot
be assigned in a Facies definition table in PetroMod or in Petrel.
Workaround: If you want to use PSQL lithologies for petroleum systems modeling outside of PSQL, you must copy them to
a sub- folder.

Play Chance Mapping

Play Chance Mapping Coordinate reference system (CRS) conversion possible with wrong results: If you work with Play
Chance Mapping (PCM) in the Reference project tool, after a coordinate reference system (CRS) conversion the resulting
surface may be distorted or have a rotation angle. The reason is that the master grid may no longer be orthogonal, which
is mandatory for PCM to work properly.
Workaround: Specify the master grid after the CRS conversion and run PCM again.

12
 KNOWN ISSUES

GPM
If the GPM simulation name given during the Run sedimentary simulation process includes a special character (space,
underscore, hyphen, and so on), the resulting GPM input object retains the complete GPM simulation name but the name
of the resulting GPM result object does not include any special characters (for example, GPM_3D_Model will become
GPM3DModel).
Workaround: Do not use special characters in GPM simulation models.

Shale
Geosteering
• Curve shifting in vertical and horizontal tracks: Curve shifts in vertical and horizontal tracks disappear when you close
a project. You must re-apply the shift when you re-open the project.
• Artifacts created when editing a well top: Sometimes, when editing a well top (dragging it sideways) in the horizontal
track of the Curtain Section Window, some artifacts are displayed. These artifacts are only visual.

Studio
• Project data table delete functionality: When deleting a microseismic folder and the associated data and geopolygons
in the Project data table, if the Search dialog box is open, or if it was opened and then closed, you may receive an
error message. As a workaround, avoid opening the Search dialog box when deleting this data type, or delete objects
from the Input pane.
• Studio database upgrade of SRD information: During upgrade, time-indexed data are tagged with the original seismic
reference datum (SRD) of the object. This is important for subsequent use in multi-SRD workflows. An issue exists
where seismic logs (time-indexed synthetics, logs extracted from time-indexed seismic cubes) are not given an
original SRD tag. This means that, on transfer to a Petrel project, they will assume the SRD of the Petrel project. This
may not be correct and can lead to erroneous interpretation.
Workaround: If you know the correct SRD of the object, set this manually in the Petrel SRD manager and then for the
data shifted in conjunction with other log data.
• Transfer of seismic logs sampled in depth from Petrel to Studio: The SRD definition for the seismic log is not
transferred. This will potentially cause the same issue as mentioned above if the log is subsequently moved from
Studio to another Petrel project.

Guru
• Quality Reporting Screen Capture workstep does not support georeferenced images: When using the Screen Capture
workstep within a workflow, if the option to output the image as a georeferenced image is selected, an image will be
created in the Input pane. However, this image is not spatially referenced as required by georeferenced images.
Workaround: Spatial information can be entered manually in the Settings dialog box of the georeferenced image.
• Any comments added to Guru pages in previous versions are not retained: If you added comments to any Guru pages
in previous versions of Petrel, these are not retained in 2019.
• Quality Reporting Add to reference list does not support horizons from a 3D grid: When using the Add to reference list
workstep in a workflow, if 3D grid horizons are added to that reference list then any operation that is run on that
reference list will not recognize them (a message appears saying the reference list is empty).
Workaround: Use the For all icons in workstep to loop through all horizons within a 3D grid or provide the horizons
manually to the Set reference list workstep.
• Custom company logos are not retained if a page is repackaged: If a new page is created in the Guru Editor and
packaged with a new company logo, if the page is packaged a second time all the information is retained except the
company logo (it will revert to the Schlumberger logo).
Workaround: Add the company logo during each packaging process.
• Blank guided workflow window opens if two Petrel instances are open: If there are two instances of Petrel open,
accessing Guru or running a guided workflow will result in a blank Guru window opening.

GPM 13
RELEASE NOTES 2019.5

Workaround: Close one instance of Petrel and Guru will function correctly.

Foundation
Profiles
• Tools repeated in search: Multiple tools exist for some functions, such as creating windows and opening dialog boxes,
and some tool names therefore appear more than once. This is an area of active development.
• Tools missing from search: Some tools, such as drop-down menus, may not appear in the search results in the Profile
editor dialog box.

Printing
No CGM output: If you have a map window active and you print in CGM format, no CGM file is generated. Workaround:
Click Advanced Settings , then select Save debug output to disk.

Mapping
Geopolygons do not display in the correct position in the map viewport when using large-sized plot windows: When using
a plot window with a large size and two or more map viewports are displayed at the bottom and top right, if you visualize a
geopolygon with the corresponding polygon counterpart for reference, the geopolygon will shift position when you
reduce the zoom display.

Core
Live collaboration: The Live collaboration feature has the following limitations:
• The list of supported data when creating a collaboration session and searching for objects can be incomplete.
Supported objects that are missing from the list can be directly added to the session using the blue arrow.
• It is not possible to delete an active collaboration session. You can only delete your own session if nobody else has
joined.
• It is possible to specify collaboration administrative rights to users in the collaboration.config file so that they can
delete any non-active session. Note: User names are case-sensitive.
• It is not possible to join a session that contains a seismic horizon with only read-only access to the folder where the
Petrel project is stored.
• When performing fault interpretation through a live collaboration session, where user 'A' is interpreting a fault and
user 'B' is interacting with the same fault and has it set as active, if user 'B' moves the active fault from its original
folder, this causes the Petrel session to crash for user 'A'.

14
 SUPPORT INFORMATION

Support information

User assistance
The full set of Petrel 2019 documentation, and documentation for any prior Petrel release, can be downloaded from the
Software Integrated Solutions (SIS) Support Portal.

Contact Schlumberger
Schlumberger has sales and support offices around the world. For Technical Support information for Software Integrated
Solutions (SIS) software:
• Schlumberger Support Portal: https://www.software.slb.com/support/
• Customer Care Center email: customercarecenter@slb.com
• Support Contact Details: https://www.software.slb.com/support/contact-details. Select your country to view support
phone numbers. If your country is not listed, select the nearest location

Core 15