Petrel E&P Software Platform 2014: Release Notes
Petrel E&P Software Platform 2014: Release Notes
Petrel E&P Software Platform 2014: Release Notes
RELEASE NOTES
Schlumberger Public
Copyright © 2015 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.
These Release Notes contain short descriptors for the most significant enhancements, fixed issues, and known
limitations, as well as system requirements and recommendations. The full set of Petrel 2014 documentation, and
documentation for any prior Petrel release, can be downloaded from the Software Integrated Solutions (SIS)
Support Portal.
The Petrel platform architecture tracks and audits beta testing, ensuring that the broad range of capabilities is
consistently and comprehensively tested. For 2014, this has involved more than 70 oil and gas companies across
the spectrum of major, independent, and national oil companies, as well as internal resources. In total, we have
recorded more than 30 person-years of testing on the 2014 beta releases.
Further information about the above mentioned updates and improvements can be found in the following sections
and, where appropriate, in more detail in the companion document, Petrel E&P Software Platform 2014 What’s
New Guide. Complete documentation for this release, and all prior Petrel releases, is available from the Software
Integrated Solutions (SIS) Support Portal.
General
Feature Short Description
Resolving potential project unit Projects created earlier than 2014 may have inconsistent horizontal
inconsistencies XY and Distance template units. From 2014.6 on, the inconsistency
will be detected, reported, and rectified. In such cases, a warning is
raised, a detailed written to the message log and an entry is added to
the project history. The project may still contain corrupted data,
which may have to be reloaded or recomputed.
User Experience
Affected Feature Issue or Limitation
Inspector shortcut key The Ctrl+Shift+Spacebar shortcut key for showing/hiding the
Inspector does not work when sharing your screen with other users
using Microsoft Lync™.
Using Petrel with Windows non- Running Microsoft Windows with non-Aero themes when using
Aero themes Petrel 2014 may have cosmetic implications for the rendering of the
outer Petrel application border. It is recommended running Windows
with the Aero theme when using Petrel 2014.
Geophysics: General
Affected Feature Issue or Limitation
Geobody Box probes In certain situations, the box probe performs at lower resolution than
expected. This issue has been observed for cubes in seismic surveys
having rotation angles relative to North, in degrees other than 0,
90,180, and 270. A fix in OpenInventor is being worked on for an
upcoming release.
Workaround:
• Use horizon probes if possible, as they are not affected by this
issue.
• When extracting geobodies from box probes, toggle on “extract in
full resolution” option to ensure maximum extraction quality,
independent of probe display resolution.
Geology: General
Affected Feature Issue or Limitation
Surface contouring The Enhanced surface contouring method, which is now the default,
may render slowly if there are many thousands of contour lines, and
in some cases may lead to a crash. This is more likely to happen
when displaying property maps.
Workaround: Change the contour method from Enhanced to Classic
before displaying the surface.
Delete the invalid logs, and then recreate the logs in the current
Geology: Fractures
Affected Feature Issue or Limitation
Stress based driver (NFP) Fold-related fractures: NFP computes stresses induced by faulting.
Therefore, when no faults are present in the sub surface or if it is
known that the observed small-scale natural fractures are not
mechanically related to the fault network, you cannot use NFP.
Fracture related folding, for instance, cannot be used in NFP
simulations.
Fold-related fractures
Basically, Li, Lj and Lk are the dimensions along each cell axis of the
blocks of material, making up the matrix volume (i.e. the blocks
between fractures). They can also be seen as the distance between
Reservoir Engineering
Affected Feature Issue or Limitation
RESQML models exported from RESQML models created by any version of Petrel from 2012.2 to
Petrel versions 2012.2 to 2013.3 2013.3 that include an HDF5 component will not be imported
and which include a HDF5 correctly by Petrel.
component cannot be re- This issue is caused by a fault in the binary format written to the
imported. HDF5 models by the offending versions. The same fault may affect
import into other software that supports the RESQML standard.
Note: Models that do not include an HDF5 file are unaffected.
The solution depends on the version of Petrel used to create the
RESQML model:
• Models created with any version from 2012.2 to 2012.8 should
be recreated using Petrel 2012.1.
• Models created with any version from 2013.1 to 2013.3 should
be recreated using Petrel 2013.4 or later.
Converting a simple proposed A simple proposed well is created with Well path design by
well to an advanced plan manually digitizing the design points. When converting a simple
proposed well to an advanced plan, the design points will be
converted into Station points in the advanced plan.
• If you click Go to surface or add any curve section to the top in
Well path designer, for the Station points, only MD, INCL and
AZIM values will remain unchanged during calculation, but X, Y,
Z and TVD will be recalculated.
• If the last point of the simple well (TD) is above MSL, the
conversion will fail due to TVD and MD being referenced to MSL
instead of to Kelly Bushing (KB).
Workaround: Edit settings for the proposed well by changing from
Associating a side track to a well When assigning a branch to a main well during the sidetrack creation
workflow, the trajectory of the main well (parent) and the branch
(sidetrack) must be within 1m. Otherwise the assignment will fail.
Well path creation with non S-3D The system automatically converts any non S-section (profile) into an
profile S-3D profile when you click on that section in a 3D window and in
well path design Pick/Dragger mode. The conversion will display in
the Well path designer spreadsheet as empty rows. Those rows will
be filled up when modified with the dragger.
Workaround: Click the Undo button and return to the Well path
designer.
Plan grid convergence values In the 2012.1 release, if a project was set up with mixed units, the
grid convergence for the plan might be calculated incorrectly. This
issue was fixed in the 2012.2 release. However, if a project is saved
with the 2012.1 version and is opened with any newer version, an
incorrect grid convergence will occur.
Workaround: To correct this, you must trigger a plan recalculation by
editing the plan (with Well path designer, dragger or Inspector) in a
3D window.
Relief well path template In the Relief well path template, if a sidetrack wellbore is selected as
the target well, the relief well location cannot be calculated based on
the actual well head location of the target well. Therefore, the
calculated relief well path might not meet your design criteria.
Workaround: Manually combine the survey data of the parent well
and the sidetrack well into a new well and use the new well as the
target well to design the relief well.
Showing EOU and VOU • Displaying a lot of EOU or VOU might cause performance issues.
Workaround: To avoid performance issues, you can hide the EOU
or VOU display by toggling off the Show EOU or Show VOU
button, or you can display only the VOU, without EOU.
• When EOU and VOU are displayed at the same time, the shape
of the EOU might not be correctly visualized.
Workaround: To correctly visualize them together, you need to
toggle on the Orthogonal camera mode on the 3D window
toolbar.
Showing No-go zone • The 3D No-go space is visualized by connecting all the No-go
zone cross sections from wellhead to TD. As a limitation of this
algorithm, the No-go zone beyond the offset well TD cross
section cannot be visualized although there is some extended
trajectory uncertainty.
• The No-go zone only gives you a view of collision hit. On the No-
go zone boundary, there might be small calculation bias
compared to the Anti-collision result. The actual collision risk
level must be confirmed using the Anti-collision scan.
Production: General
Affected Feature Issue or Limitation
Well Section Window Production charts may be positioned incorrectly in a Well Section
Window.
Workaround: In a Well Section Window, you must display a
production chart in the MD domain for the chart to be positioned
correctly.
OFM Data Connector – Import When you use the OFM Data Connector to import well trajectories
and completions from OFM, the gas lift valve in OFM is imported to
Petrel as an Inline FCV.
OFM Data Connector – Forecast OFM Data Connector cannot import the gas, oil, and water phase
Import units for forecast data in the OFM project. The following conversions
are used:
• For an OFM forecast case saved using English units: Gas =
SCF/D, Oil = STB/D, and Water = STB/D
• For an OFM forecast case saved using metric units: Gas = Sm3/d,
Oil = Sm3/d, and Water = Sm3/d
Technology: Licensing
Affected Feature Issue or Limitation
Plug-ins When using plug-ins licensed on the PluginClass, the
UseFastPackageDialog parameter in the PetrelConfiguration file
should be set to False. Otherwise, these plug-ins may not be visible
in the license selection UI.
Project Compatibility
The Petrel platform preserves the value of your historical data. Projects saved in all earlier Petrel versions will load
directly into Petrel 2014 without any need for data migration. However, note that projects saved with Petrel 2014
will not be backwards compatible (e.g., cannot be opened) with earlier versions.
Licensing
License files issued after 2012 are valid for use with new releases of Petrel, so long as the license expiry and
maintenance expiry dates have not passed, as explained below. However, licenses issued prior to Petrel 2012 need
to be updated.
Petrel licenses now incorporate two important dates, the maintenance expiry date and the license expiry date. You
can verify the validity of your license, as follows:
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
The license is valid to run Petrel up to the license expiry date; it allows you to run any Petrel version that is
released before the maintenance expiry date. All license inquiries should be made to your SIS account manager,
but note that you will normally be contacted by Schlumberger before your maintenance expires.
Note: It is recommended running Microsoft Windows with the Aero theme when using Petrel 2014.
Minimum Recommended
Microsoft® Windows® 7 (64-bit, SP1) Microsoft Windows 7 Professional, Enterprise, or
Ultimate Edition (64-bit, SP1)
Quad-core processor (best with fast clock speed and Dual quad-core or hex-core processor (best with fast
large cache) clock speed and large cache)
16 GB RAM memory 64 GB RAM memory
* Petrel will run on 4K (display devices or content having horizontal resolution on the order of 4,000 pixels).
However, it is recommended to use the DPI setting of 100% or 125%. By running Petrel on 4K display devices, you
may experience visual artifacts regarding labels, icons, and font sizes. We are working towards increasing Petrel's
compatibility with 4K through future releases of Petrel.
Note: The Petrel 2014 interface is optimized for horizontal resolutions from 1280 and higher and for vertical
resolutions from 1024 and higher.