Petrel 2020-1 Release Notes PDF

Release notes 2020.
1
Copyright Notice
Copyright © 2020 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............................................................................................................................................................................................................. 3
REQUIREMENTS
System requirements............................................................................................................................................................................................4
Operating systems..........................................................................................................................................................................................4
Studio database system requirements..............................................................................................................................................................4
Licensing requirements........................................................................................................................................................................................5
Project compatibility.............................................................................................................................................................................................5
DELFI Petrotechnical Suite system requirements........................................................................................................................................... 5
Operating system............................................................................................................................................................................................5
Browser............................................................................................................................................................................................................5
Graphics processing unit (GPU)...................................................................................................................................................................5
Remote visualization...................................................................................................................................................................................... 6
Display..............................................................................................................................................................................................................6
Network connectivity.....................................................................................................................................................................................6
Allowed traffic.................................................................................................................................................................................................6
NEW FEATURES AND ENHANCEMENTS

Geophysics.............................................................................................................................................................................................................7
General.............................................................................................................................................................................................................7
Seismic Well Tie .............................................................................................................................................................................................7
Quantitative Interpretation............................................................................................................................................................................8
Enriched workflows in the DELFI Petrotechnical Suite........................................................................................................................... 9
Geology................................................................................................................................................................................................................... 9
General.............................................................................................................................................................................................................9
Wells................................................................................................................................................................................................................. 9
Well section window..................................................................................................................................................................................... 9
Petrosys map window................................................................................................................................................................................... 9
Reservoir and Production Engineering............................................................................................................................................................10
General...........................................................................................................................................................................................................10
Structural Modeling............................................................................................................................................................................................10
Structural Framework Modeling................................................................................................................................................................10
Fracture Modeling........................................................................................................................................................................................11
Gridding..........................................................................................................................................................................................................11
Geomechanics.....................................................................................................................................................................................................11
General...........................................................................................................................................................................................................11
Reservoir Modeling.............................................................................................................................................................................................12
General...........................................................................................................................................................................................................12
Workflow Editor ........................................................................................................................................................................................... 12
Train Estimation Model................................................................................................................................................................................12
Studio.................................................................................................................................................................................................................... 12
Guru....................................................................................................................................................................................................................... 13
Guru Content Manager................................................................................................................................................................................13
Foundation............................................................................................................................................................................................................13
Annotate Note...............................................................................................................................................................................................13
Floating Widgets...........................................................................................................................................................................................13
Improved workflow to define the project CRS.........................................................................................................................................13
Polygons and Points Attribute Spreadsheet............................................................................................................................................13
Position Groups in Viewports and Windows........................................................................................................................................... 13
Reference Project Tool................................................................................................................................................................................ 14
Windows Usability........................................................................................................................................................................................14
Workflow Editor............................................................................................................................................................................................ 14
Zoom in a 3D Window..................................................................................................................................................................................14
i
TABLE OF CONTENTS
Enriched workflows in the DELFI Petrotechnical Suite......................................................................................................................... 14

Licensing........................................................................................................................................................................................................14
KNOWN ISSUES
Geophysics...........................................................................................................................................................................................................16
General...........................................................................................................................................................................................................16
Seismic Well Tie............................................................................................................................................................................................16
Geology................................................................................................................................................................................................................. 16
General...........................................................................................................................................................................................................16
Well Section Window.................................................................................................................................................................................. 16
Reservoir and Production Engineering............................................................................................................................................................17
Simulation...................................................................................................................................................................................................... 17
Structural Modeling............................................................................................................................................................................................19
Structural framework modeling................................................................................................................................................................. 19
Gridding..........................................................................................................................................................................................................20
Fracture modeling........................................................................................................................................................................................ 20
Enriched workflows in the DEFLI Petrotechnical Suite......................................................................................................................... 20
Geomechanics.....................................................................................................................................................................................................20
Reservoir Geomechanics............................................................................................................................................................................20
Reservoir Modeling.............................................................................................................................................................................................21
Property Population..................................................................................................................................................................................... 21
Exploration Geology............................................................................................................................................................................................21
Petroleum Systems Modeling.................................................................................................................................................................... 21
Petroleum Systems Quick Look..................................................................................................................................................................22
Play Chance Mapping..................................................................................................................................................................................22
Studio.................................................................................................................................................................................................................... 22
Guru....................................................................................................................................................................................................................... 22
Foundation............................................................................................................................................................................................................23
Profiles .......................................................................................................................................................................................................... 23
Mapping......................................................................................................................................................................................................... 23
Function Window Scaling........................................................................................................................................................................... 23
Color Tables................................................................................................................................................................................................... 23
Printers...........................................................................................................................................................................................................23
Core....................................................................................................................................................................................................................... 23
SUPPORT INFORMATION
User assistance...................................................................................................................................................................................................24
Contact Schlumberger....................................................................................................................................................................................... 24
ii
OVERVIEW
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 2020 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 2020.1 major 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 2020 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 2020 documentation, and documentation for any prior Petrel release, can be downloaded from the
Software Integrated Solutions (SIS) Support Portal.
3
RELEASE NOTES 2020.1
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)
Studio database system requirements

Oracle databases
Recommended
Operating system Red Hat® Enterprise Linux® 7.5 (64-bit), CentOS 7.5 (Kwin Windowing Manager)
Processor x64 processor (dual six-core) (x64 processor [dual quad-core] minimum)
Memory 64 GB or greater (32 GB minimum)
Other required software
Oracle Database Enterprise Edition 18c (64-bit)
4
REQUIREMENTS
Microsoft SQL Server databases
Recommended
Operating system Windows Server 2016 (64-bit)
Processor x64 processor (dual quad-core) (x64 processor [quad-core] minimum)
Memory 64 GB (32 GB minimum)
Other required software
SQL Server 2016 SP1 Standard Edition (64-bit)
Licensing requirements
Petrel 2020 requires the 2020.1 (recommended) or 2017 version of the Schlumberger Licensing Tool.
• Petrel 2020 will not work with an older License Server.
• All older versions of Petrel will continue to work against the 2017 or 2020.1 License Server.
• The 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 2020 without any need for data migration. However, note that projects saved with Petrel 2020 will not
be backwards compatible (e.g. cannot be opened) with earlier versions.
DELFI Petrotechnical Suite system requirements

Operating system
Microsoft Windows 10
Browser
Google Chrome™
Graphics processing unit (GPU)

• GPU capable of H.264 decoding for TGX use
• Minimum driver version for Intel® HD devices: xx.xx.xx.4352
Licensing requirements 5
Remote visualization
• Schlumberger RemoteApp Launcher (requires Microsoft .NET Framework 4.6.1)
• Mechdyne TGX™ 1.10.7 client (64 bit)
Display
• Capable of a working 1920 x 1080 resolution
• Support 4K resolution and multiple displays
Network connectivity
Workflow type Bandwidth Ping
Basic visualization At least 10 Mbps 140 ms or lower
High-end visualization At least 25 Mbps 50 ms or lower
Suitable bandwidth for multiple users at peak loads must be available (for example, 50–100 Mbps aggregate bandwidth
for 10 users, depending on workflows).
Allowed traffic
HTTPS to:
• https://delfi.slb.com/
• https://platforms.delfi.slb.com/
• https://*.platforms.delfi.slb.com/ (file management URL)
Remote visualization on:
• RDP: Outbound Ports 42967, 42968/TCP and UDP
• TGX: Outbound Port Range 40001-40017/TCP and UDP
• Domain suffix: platforms.cloud.slb-ds.com
The IP address/subnet is at the discretion of the cloud provider and cannot be predefined. The user machine connects to
a randomly generated hostname, such as:
• 5750b66bd0ca6234216b4cd6a1.dev.slbcloud.com on 42967 using RDP
• 5750b66bd0ca6234216b4cd6a1.dev.slbcloud.com on 40001-17 using TGX
6
New features and enhancements
The following content contains descriptions of new features and behavioral changes in this release, organized by domain.
Geophysics
General
• Restrict interpretation: You can now display 3D interpretation on a time slice in restrict mode.
• Restrict mode: Fixed an issue with cursor tracking where the cursor was incorrectly snapping to seismic
interpretations that were not visible at that moment due to being in Restrict mode.
• Seismic folder: Fixed an issue where the performance of Petrel (for example, scrolling of the Input pane) was
impacted by having the seismic folder expanded in the input tree.
• Search with Studio: Fixed an issue where loading 2D seismic lines to a Petrel project in silent mode did not create the
2D intersection plane, preventing the line from being displayed.
• Geobody interpretation: Fixed an issue where an error message appeared when new voxels were added to an active
geobody.
• Simple domain conversion: Support for the conversion of 2D interpretation data has been added. Fixed an issue where
Upper layer velocity was not editable for 2D seismic lines. Fixed an issue, in projects where the SRD was not 0, where
a conversion produced incorrect results.
• Strata Mesh: Improved the usability of the mesh control dialogue.
• Mesh probes: Fixed a rendering issue when probes were displayed in Depth effect mode.
• Flatten on horizon: Enabled the option to flatten an entire horizon by right-clicking when working with composite lines
between surveys in the Interpretation window.
• Virtual cropped volumes: Volume min and max amplitudes are now saved correctly when the project is saved.
• ZGY Operations: A Reset button has been added in the Amplitude sub-tab on the Operations tab in the Settings dialog
box to reset the minimum and maximum amplitude to the values contained within the ZGY file.
• Prestack Seismic: Improved performance when displaying gather locations and attributes in the 2D window.
• SEG-Y 2D toolbox: Various bug fixes.
• Fixed an issue where the troubleshooting option to release all licenses, when an inactivity period is exceeded,
caused the SEG-Y 2D toolbox to hang.
• Fixed an issue introduced in 2018.1 which impacted the performance of SEG-Y-2D toolbox.
• Fixed an issue in Match with existing lines, where string replacement did not work when automatch was used.
• Fixed an issue in Navigation merge where the SP/CDP relationship differed between the SEG-Y file listing and Line
segments.
• Fixed an issue in the detection of duplicate coordinates.
• Fixed an issue with the Seismic plot display.
• SRD manager: Fixed an issue where the Individual replacement velocity calculated from checkshots was incorrect if
the checkshots were edited to include additional points.
• Log conditioning: Fixed an issue where it was not possible select logs after saving and reopening a project.
• Workflows: The following worksteps have been added to seismic operations:
• Create virtual cropped 3D volume
• Create vintage
• Get vintage
• Assign vintage
• Remove used vintages
Seismic Well Tie

• Depth seismic calibrated to user-defined points: Two depth seismic calibration studies are available under the
Seismic well tie process:
Geophysics 7
• The Depth seismic calibration study has been renamed as the Depth seismic calibrated to well tops study.
• The Depth seismic calibrated to user-defined points study is a new option which enables you to create new
alignment points after the study has been generated. All alignment points are recorded and stored inside the
study.
• Fixed the warning in the Seismic well tie dialog box for the Depth seismic calibration study when the domain of the
input seismic is defined incorrectly.
• Fixed the issue where depth seismic disappears or is shifted up in the study window after it is calibrated to well
tops. This occurred if the depth seismic started below the seismic datum.
• Fixed the issue for the Depth calibration seismic study where some depth correction values in the well tops got
incorrect values during project upgrade.
• Integrated seismic well tie: Fixed the issue where it was not possible to change the TDR after deleting a track from the
well section template.
• Sonic calibration: Fixed an issue where the incorrect interval velocities were generated above the top of the sonic log.
This occurred when changing the Checkshot threshold depth option from Just above shallowest checkshot to Only
use checkshots and back.
Quantitative Interpretation
• QI crossplots: Fixed an issue where Petrel read the memory available for cross-plotting from the system's graphics
card instead of the main graphics card.
• Simultaneous inversion: Fixed an issue where Russian characters in a file name prevented successful execution.
• Rock physics: Fixed an issue in Fluid substitution where temperature unit conversions were applied incorrectly.
• Rock physics models crossplot: Fixed an exception that occurred when attempting to update and then order the
polygon values. The facility to order the values has been removed.
• AVO Anisotropy: Fixed a crash that occurred when trying to make a working interval when no wells existed in the
project.
• Seismic data conditioning:
• Intercept and gradient calculation is only applicable to partial angle stacks. Offset gathers or offset partial stacks
must be converted to angle stacks before applying this operation.
• Amplitude balancing calculation is now available for pre-stack gathers. Each gather is balanced to a reference
sub-stack defined by the near and far offset or angle range.
• Time shift estimation calculation is available when using offset pre-stack data when stacked using the offset to
angle calculation or angle pre-stack data stacked using the average stack calculation.
• Band pass filter calculation is now available for pre-stack gathers. Each trace in the gather has an Ormsby band
pass filter applied.
• Bulk time shift calculation is now available for pre-stack data. Seven time shift values can be entered as either a
value or a horizon property and the shift values are interpolated across the gather traces to avoid edge effects.
• Zero phase calculation is now available for pre-stack data. A wavelet is applied to all traces in the gather.
• Spectral balancing calculation is available for pre-stack data or partial angle stacks. Each gather is balanced to a
reference sub-stack defined by the near and far offset or angle range.
• Phase balancing calculation is available for pre-stack data or partial angle stacks. Each gather is phase balanced
to a reference sub-stack defined by the near and far offset or angle range.
• Arithmetic operation calculation is available for pre-stack data or partial angle stacks. Seven values can be
entered as either a value or a horizon property. The values are interpolated across the gather traces to avoid edge
effects.
• Phase rotation calculation is available for pre-stack data or partial angle stacks. Seven angle rotation values can
be entered as either a value or a horizon property. The values are interpolated across the gather traces to avoid
edge effects.
• Gather flattening calculation is available for pre-stack data or partial angle stacks. Each trace is shifted to a
reference sub-stack defined by the near and far offset or angle range.
• Output tab has been modified to improve usability.
8
• Relevant details on inputs and parameters are now written to the object history.
• The horizon settings from a crop calculation are now automatically propagated to subsequent calculations as they
are added to a seismic data conditioning session.
• Broadband wavelet estimation: Allows a wavelet to be estimated directly from seismic using frequency matching. The
wavelet is then 'colored' using a reflectivity series at a selected well.
Enriched workflows in the DELFI Petrotechnical Suite

• DELFI Data Ecosystem: It is now possible to read and write ZGY data to and from the DELFI Data Ecosystem at read
rates of up to 8 GB/s which provides greatly improved performance for all seismic workflows. ZGY data stored in the
DELFI Data Ecosystem can also be utilized in other DELFI workflows such as Assisted seismic interpretation.
• Assisted seismic interpretation: Machine learning now provides two distinct models to enable fault prediction from 3D
seismic data. The output is a fault prediction cube that describes fault locations. An extraction algorithm can be run
on a fault prediction cube to automatically extract and segment the faults.
Geology
General
General performance improvement when printing Petrel windows to metafiles (PDF, CGM, EMF).
Wells
• Quick access to open a filtered well tops spreadsheet: In a 2D window, 3D window, Map window, and Well section
window, you can now open a well tops spreadsheet filtered by the well tops of the selected well. To access the
functionality, you only need to right-click in either a well or in a displayed well top. The functionality is also available
through the Input pane by right-clicking either in a well or in a well filter.
• Saved search for well tops attributes: You can now create saved searches by using well tops attributes as a search
criteria.
• Well Data Browser: Well Data Browser provides a user-friendly interface for easy browsing and analyzing well data in
a Petrel project such as well summary, point well data, top/zones, deviations, completions and productions. It provides
tables and graphics/charts to support data mining, analysis and reporting.
• Well optimizer: Given a set of targets, the well optimizer enables you to create well trajectories and platform locations
while minimizing the total cost of a drilling project.
• Select a symbol and color for multiple wells: You can now select a symbol and a color for multiple wells from the Well
Manager.
• Corridor X-section: You can add or update wells in a cross section by drawing a corridor (polyline with a radius) in a
2D window. The corridor X-section can be moved and rotated in a 2D window to automatically update a cross section.
It is available in the Input pane and can be shared through RPT and Studio.
• Bulk edit well top attribute 'Used by geo mod': You can now edit in bulk the well top attribute Used by geo mod in a 2D
window or 3D window using a brush or a bounding box.
Well section window

Performance improvement in Well section window: General performance improvements in the Well section window when
moving, reducing, maximizing, or restoring a window with many wells displayed. Performance improvement when
displaying logs with high density data with color fill.
Petrosys map window

The Petrosys map window now supports the creation of bubble maps for wells and well tops attributes. Additionally, the
Petrosys map window has improved support for international characters throughout.
Geology 9
Reservoir and Production Engineering

General
• Underperforming wells identification: Workover candidate analysis enables you to quickly identify underperforming
wells in your field so that you can plan remedial action and maximize the production from your existing wells. This is
accomplished by cross-plotting reservoir quality, derived from well logs, and historical production performance. You
can quickly recognize outliers, that is, wells which are producing less than expected based on their reservoir quality.
In addition to analysis on the well-level, you can use completion-level production data when you have multiple
producing intervals flowing into a single wellbore and therefore you can plan targeted remedial actions for each
producing interval.
• Coal seam gas simulation using INTERSECT: You can now use Petrel for high-fidelity modeling of your coal seam gas
assets, taking full advantage of the robust physics and performance of INTERSECT. Incorporate time-dependent
adsorption in your INTERSECT simulation cases which is critical for accurately capturing gas desorption from the
surface of the coal to the porous media. To use this functionality, you must have INTERSECT 2020.1 or later.
INTERSECT Connector 2020.1 or later must also be active.
• Well properties table in Field Management: You can now view and edit the properties of all the wells in the Field
Management process in the form of a table. This includes properties such as well status, productivity index, VFP
tables, and so on. Right-click Wells in Field Management to access the Well properties table. Use the column selector
to display only relevant properties.
• RFT/PLT simulation logs for depogrid: You can now incorporate insights from downhole dynamic data into your
depogrid simulation models by generating simulated RFT/PLT logs. You can calibrate the simulated logs against the
measured RFTs or PLTs during history match to increase the reliability of your models.
• Flexible units in the Advanced completions optimization dialog box: You can now use customized units in the
Advanced completions optimization dialog box.
• Simplified flow scaling for inflow control devices: Flow scaling for inflow control devices has been simplified and
generalized for simulators and devices. Use the Physical valves equivalent device property in the Completions
manager to make a single device in simulation represent multiple real devices in parallel, for both ECLIPSE and
INTERSECT simulations.
• Support for RESQML v2 import and export: The RESQML v2 plug-in was onboarded in Petrel 2019 and now installs with
Petrel. This plug-in enables the import and export of structured (corner-point) grids and static properties in RESQML
v2 explicit format. From Petrel 2020 onwards, only RESQML V2 (and RESCUE V37) will be supported and the RESQML
V1 export/import option will be removed.
Structural Modeling
Structural Framework Modeling
• Consumption of air-interpretation input data in Model Construction: An option has been added to support 'air
interpretation' input data in the structural modeling engine. Air interpretation data are interpretation points located
above erosional or discontinuous horizons. Adding such points to the computation enables you to better control the
background stratigraphic function, particularly at horizon-erosion contacts.
• Improved performance of Model construction: The algorithms used in the Model construction process have been
improved to optimize their performance. This performance improvement affects all models, however the degree of
change is highly model dependent. Models with a large input dataset (enhanced data filtering), large number of fault-
fault or horizon-fault intersections (enhanced contact extraction) or multiple sequences will see the most significant
reduction in runtime. For multi-sequence models, activating the 'air-interpretation' option will also improve the
performance of the construction process. Structural models computed in Petrel 2020.1 are expected to show slight
variations from those computed in previous releases, particularly in sparse data areas. These changes are related to
the algorithmic changes to enhance performance and are expected to be more consistent with interpreted structures.
• Improved consistency of the Depospace geometrical flattening method: In some cases, inconsistent rotation of the
structural models in depospace was observed. This rotation was relative to the geospace representation. This is now
fixed in Petrel 2020.1.
10
Fracture Modeling
• Implicit fracture modeling support for depogrids: The modeling of naturally fractured reservoirs using depogrids has
been enabled in 2020.1. This complements the existing dual-porosity, dual-permeability simulation workflows available
on depogrids using INTERSECT. The Fracture network and Scale up fracture properties fracture modeling processes
are currently supported. The Fracture density and Generate fracture driver processes are not active for this grid type.
NOTE: Only implicit fracture modeling is enabled on depogrids in Petrel 2020.1. DFN modeling remains available
on pillar grids and stairstepped grids.
• Improved 'ODA corrected' fracture property upscaling method: The ODA correction has been modified in Petrel 2020.
Previously it was only valid for certain ranges of extended connectivity index, eCl, and length, L. With eCI lower than
~26-27 and L lower than ~0.7, it was noticed in some specific cases that upscaled permeability would decrease as the
eCI connectivity increases due to the fracture network generating values of eCI,L outside the expected range. This is
now fixed.
Gridding
Depogrid layering enhancements: Algorithmic enhancements have been made to the Depogrid creation process to
improve the grid layering proportionality. These changes reduce the number of self-intersecting cells. This enhancement
can be observed in certain model configurations, particularly those with very high aspect ratio cells.
Geomechanics
General
• Discontinuity modeling: The Discontinuity modeling process now provides improved usability to facilitate inserting
multiple faults and fracture networks and to change selections without re-mapping everything. The process now also
enables you to set discrete filter properties, which significantly accelerates the mapping process, and to define fault
and fracture properties using 3D grid properties and DFN attributes.
• Define geomechanics simulation case: The Define geomechanics simulation case process now enables you to submit
VISAGE simulations using hybrid parallelization. In other words, you can define the number of MPI tasks and
additionally the number of more memory-efficient OMP threads for each MPI task. The new undersubscription option
now enables you to specify the number of processors available on remote server queues and then reserve full
compute nodes while using only a subset of processors for the simulation, which is typically required due to the
memory demand of large simulations. When exporting large simulation with more than 100 million elements or when
more than 8 million elements are distributed on a single MPI task, a new VISAGE version is automatically called that is
able to handle such large models.
• On Demand Reservoir Simulation: VISAGE 2020.1 is now available through On Demand Reservoir Simulation in the
DELFI environment for initialization and 1-way coupled simulations.
• 2-way coupling: The permeability updating in 2-way coupled simulations with single permeability reservoir simulations
has been improved. A new method enables you to use the cubic law directly and you can also define the assume split
of matrix and fracture permeability in the model.
• Mud weight prediction: The mud weight prediction process now enables you to calculate advanced collapse results
considering a Depth of Damage or Failure arc at the borehole wall. The Stassi d’Alia failure criterion is added and you
can select the unit of results. In addition, the well section window templates for results are improved and
automatically updated for advanced collapse results.
• Material modeling: The new implicit power law creep material model for salt was enhanced and now enables you to
use primary and secondary creep in combination in a single material definition.
Geomechanics 11
Reservoir Modeling
General
Convert property to points: You can now convert properties to points, with attributes that represent the property values.
This feature is available in the context menu of an object, on the Operations tab in the Settings dialog box for an object,
and in the Workflow editor.
Workflow Editor
Insert quality assurance map: An option to insert a quality assurance map is available in the Workflow editor. You can find
commands for inserting maps in the Insert quality assurance map folder under Processes.
Train Estimation Model

Output neural net classification probabilities to variables: When using neural net as the method for facies modeling in the
Workflow editor, the resulting classification probabilities can be assigned directly to variables. Select the Output
probabilities checkbox to enable Open variables table.
Studio
• Data footprint improvement: The following data types are now supported in the Studio database to enhance user
workflow collaboration:
• Editable triangle mesh (Geophysics)
• Triangle mesh (Structural Framework)
• Corridor x-section (Geological Interpretation) polyline can be transferred and stored in Studio, in the data table
(Shape tab under Corridor x-section tab).
• Find indexing configuration upgrade: You can import an existing data environment in the Studio manager's Shared
indexing configuration settings dialog box. This removes the manual editing of configuration files before an upgrade.
• Point well data merge: An Admin, Super Admin, Repository Admin, and Petrel Super User can now merge point well
data from different well entries in the Global data app. You can select two or more entries and click Merge to merge a
source into a target.
• Global well logs data merge: A newly merged global well log in the Global data app now correctly reassigns a source
to target well log and updates the path attribute in the Data table. Well logs merged in prior releases are not affected.
• Seismic logs SRD info: Seismic logs upgraded from Studio 2017 through 2018/2019 to 2020 shows a blank SRD record,
but the transfer from Petrel to the Studio repository has the SRD information updated.
• Find filter based on relative object extent: Geoscientists can now search for objects based on the relative size of the
extent of the object. This can be useful for workflows, such as finding surface objects that are relevant to the project
area (that is, filter out objects that cover a large area), finding objects of a specific size, QA control, such as finding
large or small objects, or to see if the size of the objects in a search result varies (by looking at the histogram), and
finding objects of roughly the same size. The filter is located under the Geometry group and has a slider with a
histogram display of the relative object size. The numeric value in the filter is only a relative value, but it is roughly the
length of the diagonal across the extent in kilometers.
• Securely store and prompt user basic authentication details: You can now add items that require basic authentication
(username and password) to a custom webmap gallery config file without having to put the username and password
in the configuration file. If the item is a ESRI portal, you are prompted for a username and password when the
webmap gallery dialog box is opened. If the item is a specific map service, you are prompted when adding that
service to the project.
• 2D line shape storage: 2D lines saved in Petrel 2020 are now stored as multiLineString (and not in a
GeometryCollectionWrapper), which means they can now be mapped correctly in tools such as ArcGIS server.
12
Guru
Guru Content Manager
Projects download functionality removed: Within Guru Content Manager, the functionality to download projects from the
cloud has been removed.
Workaround: Projects from across all versions of Petrel are available on the Software Download Center for download. For
more information on this change, see the Guru Content Manager Release Notes.
Foundation
Annotate Note
Annotate Note enhancements: The Annotate Note's interactivity and functionality have improved and you can now
preserve your note's position and your display status choices. These settings are saved and recovered when you reopen
the project.
Floating Widgets
• Properties of floating widgets persist: Petrel now saves the position, size, and settings for the widely used floating
widgets, which include:
• Tool palette: Position and gear settings.
• Inspector: Position, size, and gear settings (with the exception of 'Window', because this is project specific).
• Players: Position and gear settings.
• Visual filters: Position, size, and gear settings.
Your choices for these tools are saved before the Petrel session is closed. When you start a new Petrel session and
select any of the last used tools, they are positioned on the last place they were left on any monitor, together with the
size and specific settings, whenever applicable.
Properties are saved locally in your machine and they do not depend on a specific project, so you can recover the
saved properties every time when using Petrel, which enables a personalized user experience.
• Selection of floating widgets persists: Petrel now saves the selection of tools for the applicable floating widgets,
which include:
• Tool palette: tool group selection.
• Players: players selection.
Your selections for these widgets are saved when you save the project. When you reopen the project in a new or
existing Petrel session, the last used selection of tools is restored, which improves usability, workflow continuity, and
creates a personalized experience.
Improved workflow to define the project CRS

When you create a new Petrel project, the box to define the spatial context now appears when the project is created.
This is to organize the workflow to create a new project, and prevent the box appearing unexpectedly. If Petrel is
completely initialized, it now appears immediately when you click New project.
Polygons and Points Attribute Spreadsheet

Polygons and points attribute spreadsheet improvements: In the polygons and points attributes spreadsheet, you can now
perform a multi-selection of cells belonging to a single column and select on or off. This is applicable for Show and
boolean attributes.
Position Groups in Viewports and Windows

Position group new linking functionality: In selected viewports and windows you can synchronize the position to a
specific group, so that panning and zooming the display in the active viewport or window has the same effect in the other
Guru 13
linked viewports or windows of the same type. The functionality is similar to the camera link for a 3D window, but with no
restriction on the amount of focused areas or positions you can create. Works for Map, Interpretation and Intersection
viewports and their related windows.
Access this functionality from the windows toolbar and contextual window's Map tab under the Linking group.
The options to create new position groups, link and unlink all the active viewports, and delete unused groups, are
available through the Link to position group icons.
Reference Project Tool

Surface attributes unit conversion when using the Reference project tool: Fixed an issue that caused data inconsistency
when using the Reference project tool and transferring surfaces and their attributes. If there was a unit mismatch
between working and background projects, the surface attribute's children would not be considered for unit conversion,
just the parent surface was.
Windows Usability
Link to visual group access: Usability improvement with the implementation of the Link to visual group configuration
settings, which you can access by right-clicking a window in the Input pane.
Workflow Editor
• Collapse and expand sections: You can now collapse and expand IF statements. You can also use tools to collapse all
and expand all.
• Read expression from output sheet : When using the Read output sheet workstep, it is now possible for Petrel to read
and understand expressions in the specified cell and then consume and combine the expression with other
expressions in the Workflow editor. With this implementation, you can read expressions such as "10*$var" from the
output sheet, and later make use of the expression in a calculator, for example, or replace the "$var" value with
another value.
Zoom in a 3D Window
Removed the artificial rotation when using target zoom in a 3D window: Updated and improved behavior when you use
the target zoom on an area of interest in a 3D window. When you use the orthographic camera and the zoom to target
tool, the display does not unexpectedly rotate when the camera moves towards the area of interest. This scenario
impacts special cases when you visualize seismic or general intersections.
Enriched workflows in the DELFI Petrotechnical Suite

• Managing Petrel Projects in the Petrotechnical Suite: With Petrel 2020.1, Petrel projects are automatically managed in
the cloud. When saving a Petrel project, it is submitted to the cloud and registered in the Project Explorer. Every
subsequent incremental save creates a new, immutable version of the project with meta information that is visible in
the Project Explorer. Projects are accessible from anywhere through the Project Explorer as the single user interface.
• Project Explorer: The Project Explorer is available from within Petrel or as a standalone webpage outside Petrel. It
provides access to all Petrel projects for the selected data partition. The Project Explorer lists all versions for each
project with additional meta information such as screenshots, frame of reference, or inspection of the data tree. Users
can open the Petrel project from within Petrel or through the web version of the Project Explorer. A comprehensive
guide through the features is available within the Project Explorer.
• Sharing Petrel projects: Through a copyable web link Petrel projects can be shared with other users. If multiple users
work on the same project no data is lost or overwritten because every save creates a new immutable version.
Notifications are sent to update others on newer project versions as they become available and data can be easily
transferred between projects through the Reference Project Tool.
Licensing
Schlumberger Licensing Tool: Petrel 2020.1 contains Schlumberger Licensing Tool 2020.1
(SchlumbergerLicensingTool_2020.1.exe). All SLB products are advised to upgrade to this release of the Schlumberger
14
Licensing Tool as it contains critical security and stability updates. The Schlumberger Licensing Tool contains the SIS
License Server 2020.1 which is compatible with prior versions of SIS license files and software versions.
Foundation 15
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.
• Restrict mode: Restrict on timeslices is limited to the active timeslice. Changing the active timeslice requires restrict
mode to be switched off and on, or the timeslice to be moved to update the display.
Seismic Well Tie

Depth seismic calibration study:
• A Depth seismic calibration study with only bulk shift applied created prior to Petrel 2019.2 contains incorrect depth
correction values when the project is upgraded.
Workaround: Open the Seismic well tie Tool Palette, check bulk shift, remove it and apply the same bulk shift but with
the opposite sign.
• To get the bulk shift value added in the Well tops spreadsheet (depth correction value) after the project upgrade for all
depth seismic calibration studies created prior to version 2019.4, you must check that the Align points option is applied
on the Seismic Well Tie Editing Tool Palette.
• If the Auto save all option in the Output tab is used to create a DDR log, the Set as active DDR button is not active. To
make it active, click the save icon.
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.
• Well Data loader - user defined well attributes: User attributes loaded with the Well data loader are assumed to be in
SI unit in the source file. This can lead to data being converted incorrectly during the import process. Until the issue is
fixed, you must manually convert user attributes to SI units in the source file.
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.
16
KNOWN ISSUES
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
Reservoir and Production Engineering 17

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).
18
KNOWN ISSUES
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 Construction – Known issues related to air-interpretation: When the air-interpretation option is enabled in the
Model Construction process, inconsistent stratigraphic relationships may be observed in some rare cases where
unconformities are completely eroded. Where this occurs, it is recommended to add control points to constrain the
stratigraphy. Also, some artifacts on horizon surfaces may be observed along the horizon-erosion contacts. In such
cases, it is recommended to deactivate the Allow large thickness variation option.
• 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.
Structural Modeling 19
• 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.
• 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 in the grid (close to faults or unconformities).
Fracture modeling
Implicit fracture property in depogrids - Visualization artifacts: For depogrids, an issue has been observed that occurs in
certain cases when displaying properties of an implicit fracture network. This may exhibit as holes in the property. These
values are defined and the hole is a visualization artifact. The property value can be interrogated using the Inspector tool
and this will not impact the reservoir simulation.
Enriched workflows in the DEFLI Petrotechnical Suite

Fracture modeling: The Oda and Oda corrected methods are available for Discrete Fracture Networks. The Flow based
method is not available on Petrel PTS.
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.
20
KNOWN ISSUES
Reservoir Modeling
• 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.
• 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.
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.
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.
Reservoir Modeling 21
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.
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.
• Transfer of seismic logs sampled in depth from Petrel to Studio: The SRD definitions for the seismogram logs are not
populated during the upgrade to 2020. They assume the SRD of the receiving project, and can be subsequently
reassigned. When sent back to Studio, the SRD information is correctly retained.
• Updating merged point well data attribute: When the attribute data from a source point well data is merged into a
target, the source is deleted, and the link between the source point well data attribute and the target is lost. Any
updates made against the source point well data attributes are not preserved in Studio. You must delete the source
point well data in a Petrel project before a transfer from Studio.
• Well top synchronization status during spatial filtering: When the Studio Transfer Tool has active window spatial
filtering enabled, wells within the project that are outside of the current filter area will have their well top collections
incorrectly appear as 'New – no counterpart' in the transfer tool. Turning off the spatial filter will correctly resolve the
synchronization filter.
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,
running a guided workflow will result in a blank Guru window opening.
22
KNOWN ISSUES
Workaround: Close one instance of Petrel and run the guided workflow.
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.
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.
Function Window Scaling

The display of a function line in a Function window shifts when you use extreme zoom and the proximity to points defined
the function. This is a product of the current minimum scaling limitation.
Color Tables
Specific surface display updates (contour lines off and solid display set to specified) can cause the color table's
histogram to disappear when opening and displaying an object in a new black window. The workaround is to switch off
and on the histogram by right-clicking the top of the color table display.
Printers
Unsupported printers: The printer HP Designjet 1055CM (model number: C6075A/system requirements: Windows 9x;
Windows 3x; Windows NT) is not supported. When printing a plot window, clicking Properties in the Petrel printing dialog
box results in an unhandled exception which causes Petrel to fail and close. This affects all versions of Petrel from 2017
onward. As stated in its systems requirements, the printer does not support the operating systems in which Petrel is
certified (Windows 10 Professional or Enterprise Edition (64-bit)). The printer also causes issues with other applications.
Workaround: Uninstall the printer's driver and report the issue to HP.
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.
• Live collaboration and its workflows are not currently supported in the DELFI Petrotechnical Suite.
Foundation 23
Support information
User assistance
The full set of Petrel 2020 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
24

Petrel 2020-1 Release Notes PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Petrel 2020-1 Release Notes PDF

Uploaded by

Copyright:

Available Formats

Release notes 2020.

Copyright © 2020 Schlumberger. All rights reserved.

Trademarks and Service Marks

NEW FEATURES AND ENHANCEMENTS

Enriched workflows in the DELFI Petrotechnical Suite......................................................................................................................... 14

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

Studio database system requirements

Memory 64 GB or greater (32 GB minimum)

Other required software

Oracle Database Enterprise Edition 18c (64-bit)

Microsoft SQL Server databases

Operating system Windows Server 2016 (64-bit)

Processor x64 processor (dual quad-core) (x64 processor [quad-core] minimum)

Memory 64 GB (32 GB minimum)

Other required software

SQL Server 2016 SP1 Standard Edition (64-bit)

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

DELFI Petrotechnical Suite system requirements

Graphics processing unit (GPU)

Basic visualization At least 10 Mbps 140 ms or lower

High-end visualization At least 25 Mbps 50 ms or lower

New features and enhancements

Seismic Well Tie

Enriched workflows in the DELFI Petrotechnical Suite

Well section window

Petrosys map window

Reservoir and Production Engineering

Train Estimation Model

Improved workflow to define the project CRS

Polygons and Points Attribute Spreadsheet

Position Groups in Viewports and Windows

Reference Project Tool

Enriched workflows in the DELFI Petrotechnical Suite

Seismic Well Tie

Well Section Window

Reservoir and Production Engineering

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

Reservoir and Production Engineering 17

Enriched workflows in the DEFLI Petrotechnical Suite

Petroleum Systems Quick Look

Play Chance Mapping

Function Window Scaling

You might also like