Petrel 2013 Installation Guide

Petrel 2013
Installation Guide
*Mark of Schlumberger
Schlumberger Private - Customer Use
Copyright © 1998–2013 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 & 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.
An asterisk * is used throughout this document to designate a mark of

Schlumberger.

iv Petrel Platform Installation Guide 2013.2 23 August 2013

Contents
1 Information Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Schlumberger Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

About Schlumberger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Typestyle Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Alert Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Contacting Schlumberger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Petrel 2013 Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Studio Deployment Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Studio Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Studio Deployment Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
3 System Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Additional Information: Operating Systems and Hardware Selections . . . . . . . . . . . . . . . . . . . . . 3-4
Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Memory (RAM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Graphics Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
6-DOF Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Recommended Tested Hardware Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Petrel Geophysics Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Network Storage Recommendation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
LiveQuest Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Dedicated Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Shared Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Thin-Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
4 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Contents v

Downloading the Installation Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Installing Petrel 2013 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Installing Petrel 2013 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Defining the License Server Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Selecting a Licensing Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Deploying Petrel On a Network Shared Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Deploying Petrel 2013.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Example caspol.exe Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Petrel Coordinate System Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Migrating 2010.1 or 2011.1 Catalog Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Re-Migrating 2010.1 Catalog Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Uninstalling Petrel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
5 Plug-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Plug-in Installation and Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Plug-in Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Plug-in Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Plug-in Manager Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Customizing the Plug-in Manager Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Deploying Plug-ins from a Network Shared Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Changing the Default [Plug-ins Home] Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Appendix A Troubleshooting and Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . A-1
What is the Petrel Startup Optimization Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

What is Ngen? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
How does it work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Can I run Ngen manually? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Petrel Issues and Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Setting License Package Names in the License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Global Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
Failure Messages When Opening Petrel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
0xc0150002 Error Message When Opening Petrel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7
Plug-in Issue and Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8
“Access Denied” During Plug-in Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8
System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
NVIDIA Optimus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
Windows Aero . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
vi Petrel Platform Installation Guide 2013.2

Hyper-threading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
Can I deploy the Petrel E&P Software Platform 2013 using PetrelPlatformInstaller.exe using the
command line? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
Can I deploy the Petrel E&P Software Platform 2013 without using PetrelPlatformInstaller.exe? A-9
Petrel Hints and Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
Deploying Petrel on a network shared disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
Several Users Running Petrel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
Search Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
Appendix B Advanced Printing System (APS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Appendix C Studio Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Third Party Software Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2

Single Sign On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Connecting to the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
Turning On the Remember Password Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4
Changing the Configuration for Custom Coordinate Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5
Appendix D Enhanced Summary File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D-1
How does it work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

Conversion-related worksteps in Petrel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Technical Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3
The Preferred Workflow for Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3
Stand-alone Enhanced Summary Converter Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-5
General Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-7
Best practice guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-7
Performance Consideration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-7
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-1
Contents vii

viii Petrel Platform Installation Guide 2013.2

1 Information Resources
In This Section
Schlumberger Product Documentation ......................................................... 1-2

Contacting Schlumberger ............................................................................ 1-3
Information Resources 1-1

Schlumberger Product Documentation
Schlumberger Product Documentation
About Schlumberger is the leading oilfield services provider, trusted to deliver superior
Schlumberger results and improved E&P performance for oil and gas companies around the world.
Through our well site operations and in our research and engineering facilities, we
develop products, services, and solutions that optimize customer performance in a
safe and environmentally sound manner.
Online Documentation is provided in the following electronic formats via the listed location:
Documentation
• Petrel* 2013 Installation Guide (Adobe® Acrobat® PDF file):
https://support.slb.com.
• Online help: Petrel > Help > Help Center
You can use Adobe® Reader to read the PDF file. Adobe Reader installation
programs for common operating systems are available as a free download from the
Adobe Web site at www.adobe.com.
Typestyle The following conventions are observed throughout this guide:

Conventions
• Bold text is used to designate file and folder names, dialog titles, names of
buttons, icons, and menus, and terms that are objects of a user selection.
• Italic text is used for word emphasis, defined terms, and manual titles.
• Monospace text (Courier) is used to show literal text as you would enter it, or
as it would appear onscreen.
Alert Statements The alerting statements are Notes, Cautions, and Warnings. These statements are
formatted in the following style:
• • • • • •
Note: Information that is incidental to the main text flow, or to an important
point or tip provided in addition to the previous statement or instruction.
• • • • • •
Caution: Advises of machine or data error that could occur should the user fail
to take or avoid a specified action.
• • • • • •
Warning: Requires immediate action by the user to prevent actual loss of data
or where an action is irreversible, or when physical damage to the
machine or devices is possible.
1-2 Petrel Platform Installation Guide 2013.2

Contacting Schlumberger
Technical Support Schlumberger has sales and support offices around the world. For information on
contacting Schlumberger, please refer to the information below.
For Technical Support for SIS software:
• Schlumberger Support Portal: https://support.slb.com
• Customer Care Center e-mail: customercarecenter@slb.com
• Phone Support:
- SIS Support (main)
http://www.slb.com/contact_us/technology/sis/sis_support.aspx
- Click here for Europe, Russia, and Africa Support
- Click here for Middle East and Asia Pacific Support
- Click here for North and South America Support
Information Resources 1-3


2 Overview
In This Chapter
Introduction ............................................................................................... 2-2

Petrel 2013 Distribution .............................................................................. 2-3
Licensing ................................................................................................... 2-4
Studio Deployment Overview....................................................................... 2-5
Overview 2-1

Introduction
Introduction
This guide explains how to install Petrel E&P Software Platform 2013. The following
topics are discussed:
• Installing on a workstation using a local license
• Installing on a workstation using a license on a central license server
This guide also explains the procedures required after installation:
• Defining your license server environment
• Selecting your license package
Additionally, this guide includes detailed information on deploying Petrel 2013 on a
network shared disk. See “Deploying Petrel On a Network Shared Disk” on page 4-8.
Audience This guide is useful for the following people:

• Petrel user who installs Petrel on your workstations
• System administrator who installs Petrel on a network shared disk, or creates and
distributes a global configuration file for Petrel

Petrel 2013 Distribution
Petrel 2013 Distribution

The Software Download Center distributes Petrel 2013: www.sdc.oilfield.slb.com
The Ocean Store provides Petrel plug-ins: www.ocean.slb.com
Petrel 2013 is supported on a 64-bit architecture. You can install Petrel on the
following type of workstation:
• Petrel 64-bit
- Microsoft® Windows® 7 SP1 (64-bit) Enterprise/Ultimate
Overview 2-3

Licensing
Licensing
To run Petrel 2013, you need a valid license for this release. The license can be
configured either locally on your computer or on a central license server.
Petrel 2013 uses a combination of FlexeraTM FlexNet Publisher® licensing and a
WIBU® CodeMeter® dongle to provide a secure licensing solution.
• • • • • •
Note: This version of Petrel requires a Petrel 2013 license file. Licenses for this
release are backward compatible with all previous release versions.
• • • • • •
Note: For information about licensing, please see Schlumberger Licensing User
Guide located in the Documentation folder containing your Petrel
Installation files. For example,
C:\Temp\Petrel2013InstallFiles\Documentation.

Studio Deployment Overview
Studio Overview The Studio E&P knowledge environment empowers a new level of usability and
productivity that supports an E&P organization’s quest to streamline and optimize its
workflow across the asset lifecycle, while also capturing vital knowledge to maximize
personal and team productivity. It features a powerful set of tools that allow
geoscientists and engineers to access, review, and use information, all of this in the
context of their workflows — providing three capabilities that increase productivity.
Find your information
Studio lets you easily search and find all available information across multiple data
sources in the context of your project and workflows. Using powerful search tools it
allows you to filter results based on specific criteria. These integrated workflows
provide greater awareness and access, thus the required data is always available at
your fingertips.
Collaborate with your team
Studio supports collaboration along multiple dimensions that let team members
publish interpretations and insights, sign up for notifications, utilize instant
messaging capabilities to easily connect and communicate with team members and
add virtual sticky notes to data. This provides greater context and understanding for
making better decisions.
Manage your knowledge
Studio provides a proven, scalable database — supported by industry standard
technology (Oracle® and Microsoft SQL Server®). Specifically designed to handle
E&P project data as well as the knowledge related to that data, all stored together in
context, users can obtain better retention and reuse of the generated knowledge.
Studio Deployment Deploying Studio in your environment enables data managers to define data
Overview environments comprising Petrel projects or databases across which users can
search, view, and filter to find data using Studio. The goal of this section is to help
you identify the best deployment option to enable rapid searching, viewing, filtering,
and loading information of interest. There are several deployment options:
• Search across local Petrel projects
This option enables users to search for, filter, and load data into their Petrel
environment from Petrel projects on their local machine. This capability is
Overview 2-5

available with every native Petrel 2013 installation. For more information, see the
Petrel online Help.
• Search across local Petrel projects and network data environments
This option enables users to search for, filter, and load data from Petrel projects
across the network for increased data awareness. This option requires
configuration of data environments using the Studio Manager. For more
information about setting up these data environments, see the relevant sections
in this installation guide, the Petrel Data Management training course materials,
and the Petrel online Help.
• Search across local Petrel projects, network data environments, and Studio
Databases
This option enables users to search for, filter, and load data in the Studio
Database for maximum scalability and data awareness. This option requires
deploying a Studio Database. A data manager configures the data environments
and Studio Database using the Studio Manager. For information on configuring
data environments and Studio Databases, see the relevant sections of this
installation guide and the Petrel online Help. For more information and assistance
with deploying a Studio Database, contact SIS Services.

3 System Environment
In This Chapter
System Requirements ................................................................................. 3-2

Additional Information: Operating Systems and Hardware Selections.............. 3-4
Recommended Tested Hardware Solutions ................................................... 3-9
Petrel Geophysics Recommendations ..........................................................3-10
Network Storage Recommendation .............................................................3-11
LiveQuest Solution.....................................................................................3-12
System Environment 3-1

System Requirements
System Requirements
The following table lists the minimum, recommended, and preferred system
requirements for Petrel 2013.2. The preferred system contains the minimum
requirements to efficiently support Geophysics workflows.
Table 3-1 Petrel 2013.2 System Requirements
Minimum System Recommendations
Operating system Microsoft Windows 7 SP1 - (64-bit)

Processor Quad-core processor (best with a fast clock
speed and high cache)
Memory 16 GB RAM
Display The quality of the viewing experience
increases with the size and number of
monitors
Graphics NVIDIA® Quadro® K2000 or NVIDIA Quadro®
K2000M for Mobile Workstation/Laptop
Primary storage Fast rotational speed HDD (10k, 15k Rotation
Per Minute(RPM).) or SSD
Secondary storage Optional
Preferred Hardware
Operating system Microsoft Windows 7 SP1 - (64-bit)
Enterprise or Ultimate editions
Processor Dual quad-core or hex-core processors (best
with a fast clock speed and high cache)
Memory 64 GB RAM
Display The quality of the viewing experience
increases with the size and number of
monitors
Graphics NVIDIA Quadro K5000
Primary storage Fast rotational speed HDD (10k, 15k) or
300 GB SSD
For better user experience, multiple high
speed disks is recommended.

System Requirements
Other Required Software
Microsoft .NET® Framework 4.0

Microsoft .NET® Framework 4.5*
*Everyone using PetrelPlatformInstaller.exe to
install 2013.2 will either have their existing
.NET Framework 4.0 automatically upgraded
to 4.5 or have a new installation of .NET
Framework 4.5 applied. For both cases, a
reboot is required. If you do NOT use
PetrelPlatformInstaller.exe to install Petrel
2013, Petrel 2013 can run on .NET Framework
4.0. However, Schlumberger recommends
upgrading to .NET Framework 4.5 as soon as
possible to avoid compatibility issues with
future Ocean plug-ins.
• • • • • •
Note: Schlumberger constantly 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.

Additional Information: Operating Systems and Hardware Selections
Operating Systems Petrel 2013.2 only runs on 64-bit. Schlumberger Information Solutions has retired
support for the Windows XP operating system and 32-bit platforms starting with the
Petrel 2013.2 release.
Table 3-2 lists the supported operating systems for these versions.
Table 3-2 Petrel 2013.2 Supported Operating Systems
Operating System Petrel 64-Bit

Windows 7 SP1 (64-bit) Yes
Processors Processor speed is important for the following types of tasks:

• Large calculation tasks such as volume size, seismic attribute generation, property
modeling, and upscaling
• Adding information to the graphics board
For general Petrel usage, you can use a processor that meets the minimum
recommendations. To achieve better performance, use the best available
configuration (see Table 3-1).
A number of modules in Petrel 2013.2 can effectively use multiple cores.
Table 3-3 Petrel Modules that effectively use multiple cores
Parallel and in the background Background

Geophysics
For more information, see “Petrel Geophysics Recommendations” on page 3-10.
Seismic read access of ZGY Prefetch to cache SEGY
Volume attribute computation Prefetch to cache RAW seismic
Prefetch to cache 3D seismic data
Local 3D horizon – read access for
Multiresolution computation for viz
• Horizons for seismic 3D
• Seismic 2D lines
Seismic 3D realization from any source
• ZGY
• SEGY
• RAW
Seismic 3D read access for 3D viz using
slice renderer
• SEGY
• RAW

Parallel and in the background Background

Seismic 3D export to OpenSpirit
Geology and Modeling
Data analysis - UI/dialog
Variogram calculation/update is multi-
threaded
Geometrical modeling, and Volumetrics
Facies and Petrophysical modeling
Surface volumetrics
If you want to run FrontSim or ECLIPSE on the same workstation as Petrel,

Schlumberger recommends the following:
• A multi-core processor
• Windows 7 SP1 64-bit
It is advisable to consider the speed of Quick Path Interconnect(QPI) or Front Side

Bus(FSB, old generations of Intel processor) when buying a multiple cores processor.
The transfer rates affect main memory transfers, which affects overall system
performance.
Petrel Modeling Several modeling algorithms in Petrel 2013.2 take advantage of multiple core
Recommendations processing. Increasing the number of processors improves the run time of these
algorithms. This current trend of converting algorithms to run in parallel will
continue based on algorithm run time.
Memory (RAM) To run Petrel efficiently, Schlumberger recommends at least 16GB of RAM. The total
system memory must be greater than the memory used by the application. This
ensures that your operating system has dedicated RAM so that you do not have to
use your page file (disk memory).
To estimate the size of your system, use the following guidelines:
• Small data sets (~1 GB): 16 GB of internal memory
• Medium-sized data sets (~5 GB): 16 to 32 GB of memory
• Large data sets (large 3D seismic volumes, regional seismic models, or
big simulation [ECLIPSE] runs): with 64 to 192 GB of RAM
Graphics Cards Table 3-5 lists the recommended tested graphics cards for Petrel 2013.2. Your
graphics card should meet the following requirements:
• Run pixel shader 2 or later
• Be OpenGL compatible
• Be CUDA enabled (for more information, see the CUDA GPUs page on the NVIDIA
site, at http://www.nvidia.com/object/cuda_gpus.html)

For a better visualization experience, use a high-end graphics card and a good
monitor (such as a 27 or 30-inch LCD monitor).
There are two graphics memory settings in Petrel:
• Under system settings, the graphics card memory
• The "render cache size"
The GPU memory used for Geobody interpretation is shared with the Seismic texture
cache. This can be set in the System Settings of Petrel. It’s recommended that you
set the increase the Seismic texture cache size working with Geobody workflows.
The value entered will automatically be truncated to 75% of the total GPU memory
available. The amount of memory (both physical memory and GPU memory) used by
Petrel can be monitored on the status bar in the lower right of the application frame.
As a rule, these two settings should never be larger than the available memory of
the installed graphics card.
The total allocated graphics memory for Petrel should not be 100% of the available
memory on the card. This allows graphics memory to be available for the OS and
other programs that may need it.
Depending on the workflow, there will be a variation on whether more memory
should be allocated to the geobodies process (when working with geobodies) or to
the system graphics settings (when performing volume visualization).
For geobody specific workflows (probe creation and manipulation), the memory
allocated to the geobodies process can be up to 80% of the available memory. See
Table 3-4. Note that there are only 100 MB for the Q5000, and 200 MB for the
Q6000 available as spare memory for OS functions and other programs (these
values will most likely differ from user to user). However, in this scenario, we are
assuming that no other programs are open that will require graphics memory. If
other programs are open that require graphics memory, these numbers will need to
be adjusted.
If volume rendering is also being done in conjunction with geobody probes (option
on the Volume visualization tab (only becomes active in a 3D window)), then you
would probably need to reduce this to ~70%, and allocate more to the graphics
memory setting under system settings.

If the average workflow will revolve around the creation of probes based on a 32GB
seismic volumes, then the Q6000 is the way to go, as it will also have the longest
lifespan for a user, rather than having to upgrade the graphics card again.
Table 3-4 Graphics Card Memory Specifications
Graphics Card Memory Geobody Render Cache

Card and Memory
Setting Site
Nvidia Quadro(R) K5000 / Up to 600 MB Up to 3 GB (~80%)
4GB
Nvidia Quadro(R) 6000 / Up to 800 MB Up to 5 GB (~80%)
6GB
Table 3-5 Petrel 2013.2 Recommended Tested Graphics Cards
Level Graphics Card Model Dedicated RAM

Workstation NVIDIA Quadro® 6000 6 GB
Ultra High End
NVIDIA Quadro K5000 4 GB
Workstation High End NVIDIA Quadro 5000 2.5 GB
NVIDIA Quadro K4000 4 GB
NVIDIA Quadro 4000 2 GB
Workstation Mid-Range NVIDIA Quadro K2000
NVIDIA Quadro 2000 1 GB
Mobile Workstation NVIDIA Quadro K5000M 4 GB

Ultra High End
NVIDIA Quadro 5010M 4 GB
High End
NVIDIA Quadro K3000M 2 GB
Mid-Range
NVIDIA Quadro K1000M 2 GB
Choosing the right graphics card optimizes Petrel visualization performance. Low-
end and high-end graphics cards perform substantially differently when using large
3D grids or when performing seismic volume rendering.

The performance of graphics cards depends on several factors outside of Petrel:

• Corporate operating system images
• Drivers
Schlumberger does not recommend integrated graphics cards without dedicated
RAM. These graphic cards reduce the amount of memory available for Petrel and the
operating system.
To achieve the best visualization user experience, run Petrel on a 64-bit system with
a high-end or ultra-high-end graphics card (for more information, see Table 3-5 on
page 3-7).
NVIDIA Tested The latest recommended and tested official driver from NVIDIA is 311.35 for both
Graphics Cards Workstations and Mobile Workstations. Schlumberger recommends upgrading to the
latest official drivers from your PC vendor's home page or directly from NVIDIA.
Testing has revealed that there are many critical fixes important to Petrel in NVIDIA
driver 296.88 and newer. Accordingly, 296.88 is our minimum required driver for
NVIDIA graphics cards.
• • • • • •
Note: NVIDIA SLI™ technology currently does not add any benefit to Petrel.
However, it might be helpful with large high-resolution monitors such as
30-inch LCD monitors.
6-DOF Devices The 3D window in Petrel 2013.2 supports a range of 6-degree-of-freedom (6-DOF)
devices from 3Dconnexion (www.3dconnexion.com), a Logitech® subsidiary. These
devices have six optical sensors, so you can simultaneously pan, zoom, and rotate
3D models or scenes in the 3D window. You can do this while using the mouse. The
devices are Plug and Play and are very intuitive. Their ergonomic design can help
prevent repetitive strain injuries by reducing the amount of traditional mouse usage.

Recommended Tested Hardware Solutions
Recommended Tested Hardware Solutions

Schlumberger regularly tests hardware from different vendors. Table 3-6 and Table
3-7 list some of the hardware used in the Petrel commercialization cycle. For
detailed information about the listed laptops and workstations, contact the
Schlumberger Information Solutions Services organization.
• • • • • •
suppliers. To minimize unexpected problems and costs, contact your
Schlumberger sales representative.
• • • • • •
Note: Most hardware vendors will have highly customizable options available for
each model of their workstations, it is advisable not referring to just the
model number when making the decision of hardware. It is advisable to
check detail of workstation system hardware configuration aligning with
Petrel system requirements. For example, A HP Z820 can have internal
components (CPU, Hard disk, GPU) that has lower specifications than
Z620.
Table 3-6 Tested Laptops for Petrel 2013.2
High-end Laptops Mid-end Laptops

• Dell M6700 • Dell M4700
• HP EliteBook 8770w • HP EliteBook 8570w
• Lenovo W530 • Lenovo W530
Table 3-7 Tested Workstations for Petrel 2013.2
High-end Workstations Mid-end Workstations

• Dell T7600 / T5600 • Dell T3600
• HP Z820 / Z620 • HP Z420
• Lenovo D30 / C30 • Lenovo S30
• • • • • •
Note: Although the listed hardware has been tested, Schlumberger cannot
certify it. Problems outside of Schlumberger control (such as driver
and BIOS bugs, and operating system limitations) may affect the
user experience.

Petrel Geophysics Recommendations
Petrel Geophysics Recommendations

If you use the Geophysics module to view large 2D lines and 3D surveys, and if you
use the volume rendering feature, Schlumberger recommends the following:
• A high-end graphics card with at least 4 GB memory
Table 3-8 Petrel Geophysics Graphics Card
Levels Graphic Card

High NVIDIA K5000-series and beyond (Kepler) Desktop edition
Medium NVIDIA Quadro 6000-series (Fermi) Desktop edition
Minimum NVIDIA Quadro 4000-series (Fermi) Desktop edition
• As much memory as your hardware and operating system permits, and at least 32
GB RAM
Schlumberger recommends that the sum of the graphics card memory setting plus
the geobody render cache should not exceed the total available graphics memory.
For better performance, use multiple of Serial Attached SCSI (SAS) 15K RPM or solid
state disk drives. Consider the following:
• Storage capacity (for example, 500 GB)
• Rotational speed (for example, 15K RPM)
Faster rotation speeds generally deliver faster performance.
• Interface (SATA or SAS)
SAS drives offer higher performance, especially with multiple disk configurations.
They also generally have a higher mean time between failure. SAS is a high-
performance point-to-point architecture in which all devices connect directly to
the storage controller.
Table 3-9 lists setup scenarios for Petrel Geophysics.
Table 3-9 Petrel Geophysics Setup Scenarios
Seismic
Operating Graphics Seismic
RAM Texture
System Card RAM Cache
Cache
Seismic Interpretation
64-bit 32 to 96 GB 1.5 to 4 GB 768 MB to Up to 180
system 3 GB GB,
(Windows 7 depending depending
SP1) on graphics on RAM
RAM
Seismic and Geobody Interpretation
64-bit 32 to 192 4 to 6 GB 2 to 4 GB Up to 180
system GB GB,
(Windows 7 depending
SP1) on RAM

Network Storage Recommendation
Network Storage Recommendation

Petrel projects and their respective data may be stored on a network drive on a
central file server. Often, access to these projects could become a performance issue
due to network congestion or as a result of using an inadequate Windows
network protocol.
To efficiently access project data stored on a network shared drive, use the Windows
SMB2 network protocol. This protocol is available only on Windows 7, Windows
Vista, and Windows Server 2008. The protocol is available by default. However, your
network storage system needs to be able to support it. Please contact your storage
provider for details.
The combination of the 64-bit Windows releases with the SMB2 protocol can
significantly enhance Reference Project workflows and access to Petrel data
in general.

LiveQuest Solution
LiveQuest Solution
In a central computing environment, you can use LiveQuest for remote access and
access to its collaboration features in Petrel 2013 application servers. LiveQuest has
a user-friendly interface that you can access from any computer connected to your
enterprise network.
LiveQuest uses a high-end thin-client technology to allow secure remote access to
Petrel 2013. Petrel has been thoroughly tested within LiveQuest in a LAN
environment, and has been found to perform well, including the Petrel Geophysics
workflows. Due to the nature of thin-client technology, visualization quality and
performance may be affected by network bandwidth and latency. Further
information and advice on deploying LiveQuest is available from SIS Services.
There are two models for deployment of Petrel on a LiveQuest environment:
• Dedicated Server
• Shared Server
• • • • • •
Note: A Dedicated Server is the only one supported for running Geophysics
workflows on Petrel 2013 through LiveQuest. A Shared Server is not
supported for running Geophysics workflows on Petrel 2013, however it is
suitable for running non-3D graphics intensive workflows on Petrel 2013,
through LiveQuest.
Dedicated Server A Dedicated Server is a system in where all the resources are allocated for one (1)
user at a time on its remote session.
This Server type deployment is the only one supported for running Geophysics
workflows on Petrel 2013, because it delivers the outstanding performance required
by the users.
Minimum The minimum hardware and software requirements for a dedicated server for Petrel
Requirements 2013 includes the following:
Table 3-10 Petrel 2013 Dedicated Server Requirements
Preferred Hardware
Operating system Windows 7 SP1 64-bit
Enterprise or Ultimate editions
Processor Dual quad-core or hex-core processors (best
with a fast clock speed and high cache)
Memory 64 GB RAM
Network 1 Gbps Network Adapter or higher
Graphics NVIDIA Quadro K5000

LiveQuest Solution
Primary storage Fast rotational speed HDD (10k, 15k) or

300 GB SSD
For better user experience, multiple high
speed disks is recommended.
LiveQuest ThinAnywhere Server for Windows version 2012.2 or higher
Recommended Tested Schlumberger regularly tests hardware from different vendors. Table 3-11 list some
Hardware Solutions of the hardware used in the LiveQuest commercialization cycle. For detailed
information about the listed systems, please contact the Schlumberger Information
Solutions Services organization.
• • • • • •
suppliers. To minimize unexpected problems and costs, contact your
Schlumberger sales representative.
Table 3-11 Systems for Petrel 2013 Dedicated Server
Systems
• HP Blade WS 460 Gen6 with the specs listed on Table 3-10 on page 3-12.
• • • • • •
Note: Although the listed hardware has been tested, Schlumberger cannot
certify it. Problems outside of Schlumberger control (such as driver and
BIOS bugs, and operating system limitations) may affect the user
experience.
Shared Server A Shared Server is a system in where all the resources are shared among multiple
users at a time on its remote sessions. This Server type deployment is not supported
for running Geophysics workflows on Petrel 2013 because it will not deliver the
outstanding performance required by users, however it is suitable for running non-
3D graphics intensive Petrel workflows.
When sizing a Shared Server for Petrel, the following two key requirements must be
taken into account:
• Number of remote concurrent users
• Data access requirements
• • • • • •
Note: A Shared Server for Petrel must be running on a physical machine and it
cannot be virtualized because Petrel is not supported on virtualized servers
at the moment.

LiveQuest Solution
Minimum The minimum hardware and software requirements for a Shared Server for Petrel
Requirements 2013 hosting up to two concurrent users including the following:
• 2 Intel hex-core processors
• 128 GB DDR3 SDRAM 1600 Mhz
• 1 NVIDIA Quadro K5000 or 6000
• 1 1 Gbps or higher network adapter
• Microsoft Windows Server 2008 R2 (64-bit)
• LiveQuest ThinAnywhere Windows RDP plug-in version 2012.2 or higher
• Microsoft Terminal Services/Remote Desktop Services configured in Remote
Applications mode
• • • • • •
Note: You also can use dual-port NICs on a teaming configuration for increased
network availability and performance.
Thin-Client A Thin-Client is a system that would be used by the users to remotely access the
applications provisioned through LiveQuest.
Minimum Requirements The minimum hardware and software requirements for a Thin-Client includes the
following:
• 1 Intel Core i5 or i7 (2nd Generation)
• 1 Gbps network adapter
• 6Gb of RAM
• Windows 7 / Red Hat Linux 5 up to 5.8

4 Installation
In This Chapter
Downloading the Installation Package .......................................................... 4-2

Installing Petrel 2013.................................................................................. 4-3
Defining the License Server Environment ..................................................... 4-4
Selecting a Licensing Package ..................................................................... 4-6
Deploying Petrel On a Network Shared Disk.................................................. 4-8
Petrel Coordinate System Manager .............................................................4-10
Uninstalling Petrel......................................................................................4-13
Installation 4-1

Downloading the Installation Package
Downloading the Installation Package

To install Petrel, you need the installation package. If you have a DVD, you can use
it. Otherwise, download Petrel from the Software Download Center.
• • • • • •
Note: If you are a new user of the Software Download Center, you must register
before you can download Petrel.
 To Download Petrel 2013 from the Software Download Center

1 Go to www.sdc.oilfield.slb.com.
2 Click SIS Software download center.
3 Log in to the site.
4 On the Welcome Message page, click Continue.
5 In the Product Group Name list (in the upper-left corner), click Petrel.
6 In the table of Petrel downloads, click the Download icon for the Petrel 2013
file you need. You can download a full .iso file, or you can download only the
Petrel version that you need.
You are ready to install Petrel 2013.

Installing Petrel 2013
Installing Petrel 2013

Petrel 2013 is a full installation with the following specifications:
• You can have prior Petrel versions installed on the same system.
• If you have a previous version and you want only Petrel 2013, then you must
uninstall the previous version (see “Uninstalling Petrel” on page 4-13).
• You must have at least 1.5 GB of free disk space to install Petrel.
• • • • • •
Note: If you will be installing a future version of Petrel that includes plug-ins
such as Production or Drilling, you will need to refer to the plug-in release
notes for an installation overview and steps on verifying the installation.
Installing Petrel
2013
 To Install Petrel 2013

1 Insert the DVD or navigate to the location where you downloaded the
installation files.
2 On the DVD browser, from the root folder, run PetrelPlatformInstaller.exe.
The Welcome panel displays.
3 On the Welcome panel, click Next.
4 On the License agreement panel, read the agreement, select I accept the
terms in the license agreement, and then click Next.
5 On the Destination Folder panel, accept the default folder, or click Change
to select the folder where you want to install Petrel, and then click Install.
• • • • • •
Note: You must install Petrel on a local drive (a drive that is locally installed on
your system). Deployment of the data environment on a network shared
disk is not supported
6 When the installation is finished, on the InstallShield Wizard Completed

panel click Finish.
Installation 4-3

Defining the License Server Environment
Before You Start You will need the following information:

• If you are getting your license from a server, the location where your Petrel
license is installed and configured (port and server name)
Get the location from your System or License Administrator.
• Name and location of your Petrel configuration file (PetrelConfiguration.xml)
Usually, this is
C:\Users\UserName\AppData\Roaming\Schlumberger\Petrel\2013.2\
PetrelConfiguration.xml.
• • • • • •
Note: If you are connecting to a license server and you have never run Petrel
2007, Petrel 2008, Petrel 2009.1, or Petrel 2009.1.1 on your workstation,
or if you are connecting to a new license server, you must define the
license server environment before starting Petrel 2013.2.
• • • • • •
Note: If you have already run a previous version of Petrel, and you are
connecting to the same license server, you can start Petrel 2013, as long
as the license server has a valid Petrel 2013 license.
 To Define the License Server Environment

1 Start Petrel with the following menu command:
Start > All Programs > Schlumberger > Petrel 2013 > Petrel 2013.1 (64-bit)
The first time that you launch Petrel 2013, a message warns that Petrel finds no
licenses.
• • • • • •
Note: This message only appears the first time you run Petrel. If it appears after
the first time you open Petrel, there is a problem in connecting to the
license server or finding the CodeMeter dongle.
2 On the message, click OK.

A message warns that you are about to change the license server
environment variables.
Petrel uses the following license server environment variables:
• SLBSLS_LICENSE_FILE: Other Schlumberger applications may use this
variable, too.
• LM_LICENSE_FILE: Other vendors may use this variable, which is the default
environment variable for FlexNet.

• • • • • •
Warning: If you click Yes, both license server environment variables will be
overwritten. If other applications are using these variables and you
overwrite them, then you may not be able to run the applications.
Only click Yes if you are sure that you want to overwrite the variables.
If you are unsure, contact your system administrator or
Schlumberger Support.
3 Click Yes.
The Define license server environment window opens.
4 Enter the following information:
a. On the License server environment variable field, select the address of
your local computer or of the central license server where your license
is stored.
The address must be in the following format:
port@servername
Where:
port is the port number where the license service is running (typically
27000). You can omit the port number if it is in the default range of 27000 to
27009 and if your workstation is on the same local network as the
license server.
servername is the host name or IP address of the system where the license
was installed and configured.
b. Select Use configuration file and then navigate to the location of your
Petrel configuration file.
c. Click OK.
The Select license package window opens.

You are ready to select your Petrel license package(s).
• • • • • •
Note: For information about verifying a license server, combining multiple
licenses, or monitoring license usage, see Schlumberger Licensing User
Guide.
Installation 4-5

Selecting a Licensing Package

If you defined your license server environment correctly, the Select license
package window opens when you open Petrel 2013. On this window, select the
Petrel license package you want to use.
 To Select a License Package

1 If you just defined your license server environment, the Select license
package window is open. If it is not, open Petrel: Double-click the Petrel icon
on your desktop, or select the following menu command:
Start > All Programs > Schlumberger > Petrel 2013 > Petrel 2013
This window has two panes:

• On the left: A list of the license packages that are available to you

• On the right: A list of modules in the license package selected on the

left pane
2 On the left pane:

a. Select the desired license package(s)
b. Select Favorite (to reduce the startup time when you open Petrel)
c. Click OK.
Petrel 2013 opens on your workstation. Every time you open Petrel, it will use
your Favorite license package automatically. As a result, Petrel will open faster
because you bypass the Select license package window. (If you need it in
the future, select Help > License packages).
If you have multiple Favorite packages, when you open Petrel the Favorites
window will open. This window shows a list of your Favorite license packages.
You select the Favorite license package you want to use.
You are ready to use Petrel.
• • • • • •
Note: For information about renaming the license packages or viewing a list of
Petrel users who use a license package, see Schlumberger Licensing User
Guide.
Installation 4-7

Deploying Petrel On a Network Shared Disk
Overview This section explains how a system administrator can deploy Petrel 2013.2 on a
network shared disk.
Deploying Petrel 2013.2 on a network shared disk offers the following advantages:
• Easy and efficient deployment of Petrel
• Single configuration file for all Petrel users
• Transparent configuration and installation of updates for all Petrel users
Deploying Petrel on a network shared disk reduces the management burden of
system administrators since they only needs to install, configure, and maintain Petrel
on one location.
Also, the system administrator can configure a single Petrel configuration file to
standardize license packages and specific Petrel settings for all Petrel users. For
detailed information, see Appendix A, “Global Configuration File,” on page A-5.
Since the Petrel 2013.2 configuration and installation of updates are transparent to
Petrel users, they can simply launch Petrel and begin working immediately.
Deploying Petrel Before beginning this procedure, you must be familiar with installing Petrel and
2013.2 already have access to a functional Petrel license. Refer to the following procedures
for details:
• “Installing Petrel 2013” on page 4-3
• • • • • •
Note: A system administrator should perform this procedure. Petrel users cannot
launch Petrel 2013.2 directly from the network path where the distribution
resides. Petrel users must map the network shared folder on their local
workstation.
1 From your workstation, install Petrel 2013.2.

2 Copy the entire installation folder where Petrel 2013.2 was installed (for
example, C:\Program Files\Schlumberger\Petrel 2013) from your local
workstation to a folder on the network shared disk (for example, P:\Global
Petrel\Petrel 2013).
On each workstation that you are going to run Petrel on, complete the following:
1 Go to the location on the shared disk where Petrel was copied and create a
shortcut for the Petrel executable. Place the shortcut on your desktop.
2 Install the following applications from the RuntimeEnvironment folder, located
on your Petrel Installation folder:
• dotnetfx45_full_x86_x64.exe
• NDP40-KB2468871-v2-x64.exe
• SDI_APS_Drivers.exe
• vcredist_x64.exe

• SQLSysClrTypes.msi (to connect to Studio database on SQL server)
3 Execute the command caspol.exe to configure the machine runtime security
policy. An example of a script you can modify for your use follows.
4 Launch Petrel 2013.2 from the shortcut you created.
5 Define the license server environment.
Example caspol.exe %windir%\Microsoft.NET\Framework64\v4.0.30319\caspol.exe -

Script quiet -machine -reset
%windir%\Microsoft.NET\Framework64\v4.0.30319\caspol.exe -
quiet -enterprise -reset
quiet -machine -addgroup 1 -url "file://
\\your.server.com\Global Petrel\Petrel2013\*" FullTrust -name
"Petrel_fulltrust" -description "Allow exe and dll from
directory on Network drive to run with full .NET trust,
necessary for calling native code."
quiet -enterprise -addgroup 1 -url "file://
\\your.server.com\Global Petrel\Petrel2013.2\*" FullTrust -
name "Petrel_fulltrust" -description "Allow exe and dll from
directory on Network drive to run with full .NET trust,
necessary for calling native code."
Modify '\\your.server.com\Global Petrel\Petrel2013.2\' for your own environment.
The execution of the caspol command will update system security at the machine
and enterprise policy level to allow .exe and .dll files on the shared folder to run
Petrel 2013.2 with full .NET trust.
Resetting the policies will remove any other policies that might have been
configured at the site. Use caution when you reset a policy.
Installation 4-9

Petrel Coordinate System Manager

During the installation of Petrel 2013, Petrel Coordinate System Manager is installed
for managing and customizing the Coordinate Reference System catalog used by
Petrel.
A geodetic expert can use Petrel Coordinate System Manager to manage and
customize the enterprise and extension catalogs used by Petrel. These catalogs
provide the coordinate reference systems that are available in Petrel in the
Coordinate reference system selection dialog box. A Petrel user uses the Coordinate
reference system selection dialog box to select the appropriate coordinate reference
system for their Petrel project.
Migrating 2010.1 If you used Petrel Coordinate System Manager 2010.1 or 2011.1 to customize the
or 2011.1 Catalog enterprise or extension catalog, you can migrate these catalogs to the 2013.2
Files catalogs. If you stored the 2011.1 enterprise or extension catalog in the default
location
%APPDATA%\Schlumberger\Petrel\CRSCatalogConfiguration\2011.1,
the software migrates the catalogs for you. If you stored the 2011.1 catalogs in
another location, for example on a shared network drive, or if you want to migrate
2010.1 catalogs, you must manually enter the catalog locations in the
CoordinateCatalogConfiguration.xml file before you open Petrel
Coordinate System Manager 2013.2 or the Coordinate reference system selection
dialog box in Petrel 2013.x.
If you opened Petrel Coordinate System Manager or the Coordinate reference
system selection dialog box in Petrel before migrating your 2010.1 custom catalog
files or 2011.1 custom catalog files stored on a network shared drive, follow the
procedure “Re-Migrating 2010.1 Catalog Files” on page 4-11.
• • • • • •
Note: Petrel Coordinate System Manager installed with Petrel 2012.x uses
2011.1 catalog files.
 To Migrate 2010.1 or 2011.1 Catalog Files

1 Navigate to the xml directory in your Petrel 2013.2 installation directory and
open the CoordinateCatalogConfiguration.xml file. For example: C:\Program
Files\Schlumberger\Petrel 2013.2\xml.
2 Locate the section  and update the
following default enterprise and extension catalog file locations. For example, if
you are migrating 2010.1 catalogs, enter the location of the 2010.1 catalog
files. If you are migrating 2011.1 catalog files that are stored on a network
shared drive, enter this location.
a. To update the enterprise catalog file location, update the following value with
catalog file location:
<Catalog name="CopyFromEnterpriseCatalog">
<value>%APPDATA%\Schlumberger\Petrel\CRSCatalogConfigurati
on\2011.1\CoordinateCatalogEnterprise.ctl</value>
</Catalog>

b. To update the extension catalog file location, update the following value with
the catalog file location:
<Catalog name="CopyFromUserdefinedExtensionCatalog">
on\2011.1\CoordinateCatalogExtensions.ctl</value>
</Catalog>
3 Save and close the configuration file.
4 Migrate the catalogs by performing one of the following actions:
• Launch Petrel Coordinate System Manager 2013.2.
• Launch Petrel 2013.x and open the Coordinate reference system selection
dialog box.
a. Click Project > Project settings.
b. In the Coordinates and units tab, click Select.
Re-Migrating Your 2010.1 catalog files are not automatically migrated to 2013.2. You must
2010.1 Catalog manually migrate them by modifying the
Files CoordinateCatalogConfiguration.xml file (see “Migrating 2010.1 or 2011.1
Catalog Files” on page 4-10). However, if you opened Petrel Coordinate System
Manager or the Coordinate reference system selection dialog box in Petrel before
you migrated your 2010.1 catalog files, you can use this procedure to re-migrate
your 2010.1 catalog files to 2013.2.
• • • • • •
Note: You can also use this re-migration procedure if you opened Petrel
Coordinate System Manager or the Coordinate reference system selection
dialog box before you modified the CoordinateCatalogConfiguration.xml
file with the location of your 2011.1 catalog files stored on a network
shared drive.
 To Re-migrate 2010.1 Catalog Files

1 Delete the default location for the 2013.2 catalog files:
%APPDATA%\Schlumberger\Petrel\CRSCatalogConfiguration\2013.2
2 Navigate to the xml directory in your Petrel 2013.2 installation directory and
open the CoordinateCatalogConfiguration.xml file. For example: C:\Program
Files\Schlumberger\Petrel 2013\xml
3 Locate the section  and update the
following default enterprise and extension catalog file locations.
a. To update the enterprise catalog file location, update the following value with
the location of your 2010.1 catalog file:
<Catalog name="CopyFromEnterpriseCatalog">
on\2011.1\CoordinateCatalogEnterprise.ctl</value>
</Catalog>
Installation 4-11

b. To update the extension catalog file location, update the following value with
the location of your 2010.1 catalog file:
<Catalog name="CopyFromUserdefinedExtensionCatalog">
<value>%APPDATA%\Schlumberger\Petrel\CRSCatalogConfigura
tion\2011.1\CoordinateCatalogExtensions.ctl</value>
</Catalog>
5 Migrate the catalogs by performing one of the following actions:
• Launch Petrel Coordinate System Manager 2013.2.
• Launch Petrel 2013.x and open the Coordinate reference system selection
dialog box.
a. Click Project > Project settings.
b. In the Coordinates and units tab, click Select.

Uninstalling Petrel
Uninstalling Petrel
You can uninstall Petrel from the Control Panel.
 To Uninstall Petrel from the Control Panel

1 Click Start > Settings > Add or Remove Programs.
2 On the list of currently installed programs, select the Petrel application, and
then click Remove.
Installation 4-13

Uninstalling Petrel

5 Plug-ins
In This Chapter
Overview ................................................................................................... 5-2

Plug-in Manager ......................................................................................... 5-3
Deploying Plug-ins from a Network Shared Folder ......................................... 5-5
Changing the Default [Plug-ins Home] Directory ........................................... 5-8
Plug-ins 5-1

Overview
Overview
With the Ocean Plug-in Manager, you can access, organize, and manage plug-ins
within Petrel. The plug-ins could come from a variety of sources:
• Distributed from the Ocean Store (www.ocean.slb.com)
• Developed internally within your company
• Developed as third-party plug-ins
The Ocean Plug-in Manager uses a Petrel plug-in installer package (.pip), allows you
to package and distribute plug-ins. You will not need to run an installer application
to install or uninstall a plug-in.
From the Ocean Plug-in Manager, you can access plug-ins from two locations:
• Plug-ins published in the Ocean Store
• Plug-ins from internal sources in your organization that are in network
share folders
This chapter describes how the system administrator can customize the deployment
of plug-ins and customize the Ocean Plug-in Manager interface to enable or
disable features.
Plug-in Installation Ocean* for Petrel is a public open API on top of Petrel that allows the development
and Uninstallation of plug-ins to expand the capabilities of Petrel or to integrate it within existing petro-
technical platforms and workflows.
Each plug-in comes with its own installer and targets a specific version of Petrel.
When a plug-in is installed, it registers itself to let Petrel know that it exists and how
it can be uninstalled. Similarly, if the plug-in is uninstalled, it will un-register itself
from Petrel.
If you uninstall Petrel, Petrel will check for plug-ins, and prompt you to uninstall the
registered plug-ins. Uninstalling all plug-ins is recommended if you uninstall Petrel.
Plug-in Licenses When you order a Petrel plug-in from the Ocean Store, full instructions for installing
and activating the plug-in license are included in the email sent to you. You also can
find the information on the Ocean Store’s Help page.

Plug-in Manager
Plug-in Manager
Plug-in Manager Ocean Plug-in Manager settings are stored in petrel.exe.config configuration file
Settings located in Petrel installation folder, for example:
C:\Program Files\Schlumberger\Petrel 2013\petrel.exe.config
• • • • • •
Note: Users should create a backup of this file before making changes to it.
Customizing the Follow these steps to customize the Plug-in Manager interface.
Plug-in Manager
Interface
 To Customize the Plug-in Manager Interface

1 If Petrel is open, close Petrel.
2 Open the petrel.exe.config file.
3 Find the <configSections> tag and add the following section inside it, if it is
not yet there:
<sectionGroup name="applicationSettings"
type="System.Configuration.ApplicationSettingsGroup,
System, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089">
<section
name="Slb.Ocean.Utilities.PetrelPluginManagerUiElements.Pr
operties.Settings"
type="System.Configuration.ClientSettingsSection, System,
Version=2.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089"
requirePermission="false"/>
</sectionGroup>
</sectionGroup>
This will enable configuration settings under separate
<applicationSettings> tag.
4 Inside <configuration> tag, on the same level with <configSections>
tag, add the following section, if it is not yet there:
<applicationSettings>
<Slb.Ocean.Utilities.PetrelPluginManagerUiElements.Propert
ies.Settings>
Plug-ins 5-3

Plug-in Manager
</
Slb.Ocean.Utilities.PetrelPluginManagerUiElements.Properti
es.Settings>
</applicationSettings>
5 Inside
<Slb.Ocean.Utilities.PetrelPluginManagerUiElements.Properties.Settings> tag
add the settings you would like to modify, following the format:
<setting name="SettingName" serializeAs="Type">
<value>Value</value>
</setting>
For example:
<setting name="StoreTabEnabled"
serializeAs="String">
<value>True</value>
</setting>
6 Following this format, you can change the following Plug-in Manager settings:
• StoreTabEnabled: Set as “True” if you want the Plug-in Manager’s Store
section enabled.
• SecurityTabEnabled: Set as “True” if you want the Plug-in Manager’s
Security section enabled and visible.
• CorporateTabEnabled: Set as “True” if you want the Plug-in Manager’s
Corporate section enabled and visible.
• InstallPluginButtonEnabled: Set as “True” if you want the Install Plug-
ins feature enabled in the Plug-in Manager. This feature is available only for
plug-ins packaged with a Petrel plug-in installer package (.pip file).
• UpdatePluginButtonEnabled: Set as “True” if you want the Update
Plug-in feature enabled from the Plug-in Manager.
• AddTrustedPublisherButtonEnabled: Set as “True” if you want the
Add Trusted Publisher feature enabled.
• RemoveTrustedPublisherButtonEnabled: Set as “True” if you want
the Remove Trusted Publisher feature enabled.
• ChangeSecurityLevelEnabled: Set as “True” if you want the Change
Security Level feature enabled.
7 Save the file.

Deploying Plug-ins from a Network Shared Folder

The Ocean Store is the designated website where scientists and engineers can
access and download plug-ins to use with Petrel. Plug-ins developed by other
companies for their internal use are not available in the Ocean Store.
The system administrator can use the Ocean Plug-in Manager to configure the
internal source of plug-ins (like network shared folders) to distribute and deploy
plug-ins within Petrel. These plug-ins are available in the Corporate section of the
Ocean Plug-in Manager.
• • • • • •
Note: The Ocean Plug-in Manager cannot browse plug-ins directly from the
network path where the plug-ins reside. Petrel users must map to the
network shared folder on their local workstation.
 To Enable Deployment of Plug-ins From a Remote Folder

2 Open the petrel.exe.config file.
3 Find the <configSections> tag and add the following section inside it, if it is
not yet there:
<section
name="Slb.Ocean.Utilities.PetrelPluginManagerUiElements.Pr
operties.Settings"
type="System.Configuration.ClientSettingsSection, System,
Version=2.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089"
requirePermission="false"/>
</sectionGroup>
This will enable configuration settings under separate
<applicationSettings> tag.
4 Inside <configuration> tag, on the same level with <configSections>
tag, add the following section, if it is not yet there:
<applicationSettings>
ies.Settings>
</
Slb.Ocean.Utilities.PetrelPluginManagerUiElements.Properti
es.Settings>
</applicationSettings>
Plug-ins 5-5

5 Inside
ies.Settings> tag, make sure that the following setting is present and set
to True:
<setting name="CorporateTabEnabled"
serializeAs="String">
<value>True</value>
</setting>
6 Inside
ies.Settings> tag, add the following section, if it is not yet there:
<setting name="LocalStoreDirectories" serializeAs="Xml">
<value>
<ArrayOfString xmlns:xsi="http://
www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/
XMLSchema"> />
</ArrayOfString>
</value>
</setting>
7 Inside <ArrayOfString> tag, add the folder locations where Ocean plug-ins
can be located.
You can add as many locations as you need. For example:
<string "H:\Corporate Plug-ins" </string>
<string "D:\My Developed Plug-ins"</string>
<string "I:\Asset Team Plug-ins"</string>
• • • • • •
Note: You can use this procedure to set a local folder (for example,
C:\my developed plug-ins) as the location of the plug-ins directory from
where you want to deploy the plug-ins.
8 Find <runtime> tag, add the following section inside it:

<loadFromRemoteSources enabled="true" />
• • • • • •
Note: More information about this setting is available in Microsoft knowledge
base article http://msdn.microsoft.com/en-us/library/
dd409252(VS.100).aspx
9 Save the file.

10 From a DOS shell, run the caspol command to configure the machine runtime
security policy. This command enables your system to trust the execution of
.exe and .dll files from a network shared folder.
a. Change to the following directory:
C:\Windows\Microsoft.NET\Framework \v2.0.50727
b. From this location, run caspol.exe as follows:
C:\Windows\Microsoft.NET\Framework\v2.0.50727>
caspol.exe -quiet -machine -addgroup 1 -url "file://
\\shared_disk\Global Petrel\Petrel 2013\*" FullTrust -
name "Petrel_fulltrust” -description
"Allow_exe_and_dll_to_run_with_full_.NET_trust"
You can copy the line above into a DOS shell, but make sure that you change
“file://\\....” to the location where you copied the Petrel distribution. This
location must be accessible at the time the caspol command is executed.
The caspol command updates your system security at the machine policy level.
The security policy updates are at:
• %WINDIR%\Microsoft.NET\Framework\version
directory\config\Security.config
• %WINDIR%\Microsoft.NET\Framework\version
directory\config\Security.config.cch
• • • • • •
Warning: Do not open these files if you are not familiar with them. Erroneous
changes to these files could make your system unstable.
11 Repeat step 10 for each network shared folder you want Ocean Plug-in
Manager to browse for plug-ins.
Plug-ins 5-7

Changing the Default [Plug-ins Home] Directory
Changing the Default [Plug-ins Home] Directory

Plug-ins usually are deployed or installed in a directory under [Petrel Home]
called \Extensions (for example, C:\Programs Files\Schlumberger\Petrel\
2013.2\Extensions). This folder is considered the default [Plug-ins Home]
directory.
 To Change the Default Location of the [Plug-ins Home] Directory

2 Open the PluginManagerSettings.xml file.
Find the <DefaultDirectory> tag. (for example, <DefaultDirectory
Name="Default" Location="C:\Program Files\Schlumberger\
Petrel 2013.2\Extensions\" />)
3 Enter the address for the new [Plug-ins Home] location (for example,
<DefaultDirectory Name="Default" Location="D:\My
Documents\ My Plug-ins\" />)
• • • • • •
Note: The user must have read/write access to the new [Plug-in Home]
directory.
• • • • • •
Note: The [Plug-in Home] directory may be located on a network shared folder.
The system administrator must execute the caspol.exe command to
configure the machine runtime security policy (see see “Deploying Plug-ins
from a Network Shared Folder” on page 5-5 for more details).
4 Save the file.
• • • • • •
Warning: Plug-ins using installers for deployment may be deployed under
[Petrel Home]\extensions. Only plug-ins deployed or installed
from the Plug-in Manager are guaranteed to be deployed
automatically in the customized [Plug-in Home].
• • • • • •
Note: There is a known issue when installing plug-ins into a restricted folder
structure. For more information, see “Plug-in Issue and Solution” on page
A-8.

A Troubleshooting and Frequently Asked
Questions
This appendix provides solutions to known issues, and provides useful Petrel tips.
Troubleshooting and Frequently Asked Questions A-1

What is the Petrel Startup Optimization Option
What is the Petrel Startup Optimization Option

The Startup Optimization setting runs a native image generator (Ngen) tool that
improves performance of managed applications. This is enabled by the installer by
default.
What is Ngen? Ngen is a Native image generator tool which improves performance of managed
applications. Ngen.exe creates native images, which are files containing compiled
processor-specific machine code, and installs them into the native image cache on
the local computer. The runtime can use native images from the cache instead of
using the just-in-time (JIT) compiler to compile the original assembly.
How does it work? Ngen compilation is on by default. After Petrel has been installed and the system is
idle Ngen starts to create native images and stores them in a hidden directory.
C:\Windows\assembly\NativeImages_v4.0.30319_64. The whole process is invisible
to the user and the system controls when to create the native images and when to
use them.
If you look you will find a lot of files in this directory. Some belong to Petrel
(identifiable through a SLB. Prefix) others belong to other applications. This is why
you should never delete this directory. The files are going to be removed when
Petrel is uninstalled.
Can I run Ngen Yes. In order to run Ngen manually open a Command prompt and cd to the Petrel
manually? installation directory. Usually that is: C:\Program Files\Schlumberger\Petrel 2013.
The run
ngenrun.bat install to install (this takes a couple of minutes)
ngenrun.bat uninstall to uninstall (also takes a couple of minutes)
While this tool has proven to significantly aid the start-up time of Petrel, each user
needs to evaluate their own case in conjunction with their IT staff, as there may be
certain scenarios where start-up optimization will need to be turned off.
A-2 Petrel Platform Installation Guide 2013.2

Petrel Issues and Solutions
Setting License You can customize a license package name on the Edit Package Licenses window
Package Names in in Petrel and distribute settings to other users with the global configuration file.
the License File When you do this, you must redistribute the settings every time a license
file changes.
A simpler process for setting company-wide license package names is to set the
names directly in the FlexNet license file. Then, the Petrel users set a flag to use the
package names in the license file.
 To Enable the Settings for a Single User

Set the flag in the PetrelConfiguration.xml file.
After you run Petrel for the first time, the location of this file will be:
• For Windows 7, the application data and settings folder is:
C:\Users\<username>\AppData\Roaming\Schlumberger\ Petrel\2013
• • • • • •
Note: You may need to enable viewing of hidden files in Folder Options.
 To Enable the Settings for Multiple Users

1 Apply the file on the machine level by storing the file in the following location:
• For Windows 7, the application data and settings folder is:
C:\Users\All Users\AppData\Roaming\Schlumberger\ Petrel\2013
2 To standardize the settings across the company, distribute the file to all
machines or deploy it as a global configuration file.
3 Setting the UsePackageNameInLicenseFile keyword to True in this file
will enable the following function:
<Configuration>
<SystemSettings>
<UsePackageNameInLicenseFile Value="True"/>
</SystemSettings>
</Configuration>
• • • • • •
Note: This file allows you to customize a series of settings. If you want to let
users customize some settings, these must be removed from the
configuration file if you are configuring it for multiple users.
 To Edit the License File

In the license file, add USER_INFO="Description/Name of Package" at the
end of the FEATURE line.
In the example below, the feature is named the Data and results viewer
license:

• When you start Petrel for the first time, Petrel will pick up these package
names from the license. When this setting is enabled, all your packages will be
selected as Favorites automatically.
You will not be able to edit the Package names or Favorite settings after you
enable the names from the license file.
• The second time you launch Petrel 2013, a short list of Favorites will appear,
instead of the initial Select license package window. This will speed up the
startup process, allowing you to choose the license from the list.
If you only selected one license package as a Favorite when you edited the license
file, Petrel opens automatically.
• • • • • •
Note: To open the Select license package window again, select Help >
License packages.

Global To standardize system settings in Petrel 2013 for multiple users, you can implement
Configuration File a global configuration file. Petrel stores the user system settings in the
PetrelConfiguration.xml file. The first time you run Petrel 2013 and exit, the file
is created in the following folder:
%APPDATA%\Schlumberger\Petrel\2013
- For Windows 7, the application data and settings folder is:
C:\Users\<username>\AppData\Roaming\Schlumberger\ Petrel\2013
The PetrelConfiguration.xml file contains the following information:
• Settings configured on the Select license package window, such as package
name and favorite package
• Settings configured using Tools > System Settings in Petrel
• • • • • •
Note: If changes are made to these settings, the changes are stored in the
PetrelConfiguration.xml file each time a user exits Petrel.
For more information, see System Settings in the Petrel online Help.
 To Create a Global Configuration File
• • • • • •
Note: This procedure is performed by the System or License Administrator.
1 Open Petrel.
2 Configure your license packages on the Select license package dialog box.
3 Configure your system settings in Petrel.
4 Close Petrel.
Your PetrelConfiguration.xml file is updated with the settings that you
selected, and it is ready to be distributed globally.
5 Copy the PetrelConfiguration.xml file to a shared disk drive that all users
can access, and set it to read only.
Remove the following lines from the global configuration file:
<UseGlobalSettingsFile Value="True"/>
<GlobalSettingsFile Value=""/>
6 To enable Petrel users to use the global configuration file, you need to set their
local configuration file to point to the global PetrelConfiguration.xml file.
Make a copy of the PetrelConfiguration.xml file created in Step 5, and
remove everything from the file except the following lines:
<?xml version="1.0" encoding="us-ascii" standalone="no" ?>
<Configuration>
<SystemSettings>
<UseGlobalSettingsFile Value="True"/>

<GlobalSettingsFile Value="E:\PetrelConfiguration.xml"/>
</SystemSettings>
</Configuration>
• • • • • •
Important: For the GlobalSettingsFile Value, replace
E:\PetrelConfiguration.xml with the path to the shared folder
where you place your global configuration file.
Copy the new PetrelConfiguration.xml file to the

%ALLUSERSPROFILE% folder on all Petrel user machines. Typically, you will
copy the new PetrelConfiguration.xml to the following default folder on
Windows 7:
C:\ProgramData\Schlumberger\Petrel\2013
When users start Petrel, Petrel will use the settings defined in the global
configuration file (PetrelConfiguration.xml). After completion of the first
Petrel run, a new PetrelConfiguration.xml file is created (if it doesn’t exist)
in the user data and settings location. This file is identical to the global
configuration file and its purpose is to allow users to personalize their own
petrel environment without modifying the settings for everyone in the global
configuration file.
Users can also select the global configuration file in the Define license server
environment window. See “Defining the License Server Environment” on page
4-4 for more information on selecting the global configuration file.
Failure Messages You may get the following error messages from the limited connection configuration
When Opening in the file server that is serving the Petrel network folder:
Petrel
• “The application failed to initialize properly.”
• “Required Petrel module failed.... Not enough server storage is available to
process this command.”
You must modify the server's IRPStackSize in the registry table. If the subkey is not
present, use Registry Editor to add it.
The IRPStackSize parameter specifies the number of stack locations in I/O request
packets (IRPs) that are used by a Windows Server 2003 and a Windows XP server.
You may have to increase this number for the following transports:
• Media access control (MAC) drivers
• File system drivers
Each stack uses 36 bytes of memory for each received buffer. This value is set in the
following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet \Services\LanmanServer\Parameters
The default value of the IRPStackSize parameter is 15. The range is from 11 (0xb in
hexadecimal) through 50 (0x32 in hexadecimal).
The Microsoft Support website has more information about this issue:

• Article 285089: “Description of the IRPStackSize parameter in Windows 2000, in

Windows XP, and in Windows Server 2003” (http://support.microsoft.com/kb/
285089)
• • • • • •
Warning: This should be done by IT engineers or system administrators. Do not
make any changes to the registry unless you are familiar with the
Registry Editor. If you make a mistake, it may harm your computer.
 To Add and Modify the IRPStackSize Subkey

1 Select Start > Run.
2 Type regedit, and then click OK.
3 Select the following subkey:
KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ LanmanServer\Parameters
4 Select Edit > New > DWORD Value.
5 Type IRPStackSize (this value is case sensitive) and then press ENTER.
6 Select Edit > Modify.
7 In the Data Value field, type the value that is appropriate for the network and
then click OK.
If the problem persists after you complete this procedure, increase the
IRPStackSize value more.
0xc0150002 Error You may get an 0xc0150002 error if all necessary components are not installed.
Message When
Make sure the following components are installed on the workstation:
Opening Petrel
• Visual C ++ libraries
• Microsoft .NET Framework 4.0
• Microsoft.VC80.MFC (64-bit), if the workstation is 64-bit

Plug-in Issue and Solution
Plug-in Issue and Solution
“Access Denied” If you try to install a plug-in into a restricted location on your computer, the Plug-in
During Plug-in Manager displays an “Access Denied” message.
Installation
Plug-ins are usually deployed or installed in the following directory:
[Petrel Home]\extensions
For example:
c:\Programs Files\Schlumberger\Petrel\2013.2\extensions
The [Petrel Home]\extensions directory is the default [Plug-ins Home]
directory. If you receive an “Access Denied” message while installing a plug-in, the
access to [Petrel Home] and/or [Plug-ins Home] is most likely restricted.
To allow the Plug-in Manager to install plug-ins, change the default
[Plug-ins Home] directory as described “Changing the Default [Plug-ins Home]
Directory” on page 5-8.

System Settings
System Settings
NVIDIA Optimus Turn this feature off as it causes Petrel to behave incorrectly.
 To Disable Optimus
1 Reboot the system.
2 Access the BIOS settings.
3 Go to the video section.
4 Disable Optimus.
5 Reboot the system.
To read more about NVIDIA’s Optimus Technology, please follow this link
http://www.nvidia.com/object/optimus_technology.html.
Windows Aero Prior to 2013, running Petrel in Windows Aero mode created unwanted visual
artifacts for certain operations. This is now fixed, and it is recommended to run
Petrel in Windows Aero mode.
Hyper-threading Hyper-threading can be safely turned on now for the vast majority of your Petrel
workflows. If in doubt, please check with your local Schlumberger SIS Services
team.
Can I deploy the PetrelPlatformInstaller.exe can take the following options

Petrel E&P
-DesktopShortcut=true/false
Software Platform
2013 using -QuickShortcut=true/false
PetrelPlatformInst
-PetrelOpt=true/false (Requires the .Net 4.5 to be installed, only available with the
aller.exe using the
silent option)
command line?
-Silent -Install
-Silent -Uninstall
-L logfile.txt
-InstallFolder="C:\MyCustomFolder"
Can I deploy the You can deploy the Petrel E&P Software Platform 2013 without using
Petrel E&P PetrelPlatformInstaller.exe as follows:
Software Platform
• First, ensure that you have all of the pre-requisites for the Petrel E&P Software
2013 without using
Platform 2013 installed:
PetrelPlatformInst
aller.exe? • .Net 4.5 (4.0 is also supported, however there is no startup optimization)
• Windows6.1-KB2533623-x64.msu

System Settings
• vcredist__2008_ATL_x86.exe
• SQLSysClrTypes.msi
• Then, install the Petrel E&P Software Platform 2013:
• Petrel 2013 (64-bit).msi
• Next, ALL other supplied MSIs must be installed. For this version, they are:
• Petrel 2013 Help.msi
• Petrel 2013 Manuals.msi
• Petrel 2013 SeismicWellTie.msi
• Petrel 2013 RDR.msi
• Petrel 2013 INTERSECT Connector.msi

Petrel Hints and Tips
Deploying Petrel on When deploying Petrel on a network shared disk, you have to run the DocIndexer in
a network shared order to get a search index. If not, a page will be shown stating this when you
disk attempt to run a search.
Several Users If there are several users running Petrel on the same computer, they will have to run
Running Petrel the DocIndexer tool individually (if they log on as individual users).
Search Index The documentation search index will only be removed for the user who installed
Petrel.
If an user have manually created a search index (stored in the %AppData%
location), this index will not be removed.
Additionally, this index will not be updated if the "install user" upgrades Petrel for
example, Petrel 2013.2.


B Advanced Printing System (APS)
Petrel uses SDITM Advanced Printing System (APS®) for the plotting engine. With
APS, Petrel provides native support for directly printing and exporting plot windows
to .cgm and .pdf formats.
APS’s integrated printing and plotting functionality provides the following:
• Improved options for page scaling (fitting to a page) and orientation (portrait
and landscape)
• Support for large printers, with a thumbnail display for easy print orientation
• Support for roll plotters without specifying custom page sizes
• New options to generate .cgm and .pdf files directly from the
Petrel Printing window
• Automatic detection and configuration of the printer setup from existing Windows
print drivers
• Ability to produce large print jobs without the limits of the standard Windows GDI
printing system
• • • • • •
Note: A large number of printers are supported. For a full list, go to
www.sdicgm.com.
Advanced Printing System (APS) B-1

Examples
Examples
In the following image, you can see that the width of the selected file exceeds the
width of the targeted media. Because the Panel check box is selected, the image
width value is orange. Orange indicates that the image requires paneling and that
Petrel will print multiple panels.
With the Panel check box cleared, the width value is red. In this case, Petrel prints
only what is fitted on the initial panel.
B-2 Petrel Platform Installation Guide 2013.2

Examples
On the Page Scaling field, you can select Width and then unlock the image. When
you do this, Petrel automatically scales the image width to the maximum width of
the media, while maintaining depth scale. This gives depth accuracy while allowing
the full width of the image to be displayed.
You can also specify scale values, which alters length and width dimensions by the
same percentage. If you need a specific width or height, you can enter that value
and APS will alter the other axis appropriately.
Advanced Printing System (APS) B-3

Examples
You also can export to a .cgm or .pdf file on the Petrel printing window.
B-4 Petrel Platform Installation Guide 2013.2

C Studio Database Configuration
Studio Database Configuration C-1

Third Party Software Configuration
Third Party Software Configuration
Single Sign On If you will use single sign-on, every Petrel end-user workstation must have the
following components installed:
• Oracle client 11.2.0.3
• Advanced Security Option (ASO)
Also, set the ORACLE_HOME variable on the Petrel client machine, or modify the
Petrel.exe.config file to use the Oracle client.
 To Modify the Petrel.exe.config

1 On the Petrel user’s workstation, open the Petrel.exe.config file in a text
editor.
2 Change the following line:
Change this... To this...

<addname=”DllPath” <addname=”DllPath” value=”path to
value=”Extensions\Schlumberger\Ora Oracle _Home\bin”/>
cle”/> for example:
C:\app\oracle\11.2.0\client_1\bin
3 Save and close the file.
ASO Configuration Configuring the Advanced Security Option for Kerberos authentication against Active
Directory consists of three main procedures:
1. Configure the Active Directory service account.
2. Configure the Oracle database server.
3. Configure the Oracle client.
 To Configure the Client

1 Create a krb5.conf file.
2 Configure Oracle net parameters (sqlnet.ora): Add the following parameters to
the sqlnet.ora file:
• SQLNET.AUTHENTICATION_SERVICES=(KERBEROS5)
KERBEROS5 should be added to other authentication services if there are
any.
• SQLNET.KERBEROS5_CONF=c:\oracle\network\krb5\krb5.conf
This parameter points to the krb5.conf file.
• SQLNET.KERBEROS5_CONF_MIT=TRUE
• SQLNET.KERBEROS5_CC_NAME=OSMSFT://
C-2 Petrel Platform Installation Guide 2013.2

Connecting to the Database
Connecting to the Database

The first time you log in to the Studio Database (for example, to load repository data
or access database features), you must have a connection to the database.
For instructions:
• If you are a database user, open the Petrel Help Center and navigate to Studio >
Knowledge Database > Accessing Studio Knowledge > Managing
Database Connections > Creating a Connection to a Database.
• If you are a database administrator, open the online help in Studio Manager.

Turning On the Remember Password Feature
Turning On the Remember Password Feature

A Petrel database administrator can turn on the Remember password feature for
each Petrel database workstation. When it is turned on, a Remember password
option displays on the Petrel database Login window. If a user selects this option,
the user's password is saved so that he or she does not have to log in when opening
the Petrel database.
 To Turn On the Remember Password Feature

1 On the Petrel database workstation, open the Slb.P4E.Dbx.Config file (in the
Petrel installation directory, at ...\Schlumberger\Petrel 2013.1\Extensions\
Schlumberger\DBX).
2 Set ProvideSavePasswordOption to True.
The line should be:
<ConnectionOptionsSection ProvideSavePasswordOption=
“false” />
3 Save the file.

Changing the Configuration for Custom Coordinate Systems

The coordinate reference systems that come with Petrel are from the following
standard authorities:
• EPSG (European Petroleum Survey Group)
• Esri© (including the ones that are part of Esri 9.3.1 but are replaced in Esri 10)
• SIS (Schlumberger Information Solutions)
If your company’s geodesy group uses custom coordinate systems with codes
developed internally, you can prevent your users from making changes to the
standard authority coordinate reference systems, transforms, and
conflation policies.
• • • • • •
Important: If you did not deploy the Studio Database for Petrel and you
want to make these configuration changes, change the
configuration of the Coordinate System Manager. If you did deploy
the Studio Database, change the configuration of the Studio
Manager.
A flag within a configuration file dictates this behavior. By default:

• The configuration file for the Coordinate System Manager has the flag set to True
• The configuration file for the Studio Manager has the flag set to False
Table C-1 Comparison of the True and False Flags
AllowAdminOutOfBoxCatalog=True AllowAdminOutOfBoxCatalog=False
Default flag for Coordinate System Default flag for the Studio Database for
Manager Petrel
Can delete any coordinate reference Cannot delete any coordinate reference
system, transform, or conflation policy system, transform, or conflation policy
(if Source=EPSG, Esri, SIS, Mentor, or
PE_9_3_1)
Can create any coordinate reference Only can create coordinate reference
system, transform, or conflation policy, systems, transforms, or conflation
using any authority or code if there is no policies with Petrel as the authority (that
conflict with existing ones in the catalog is, Source=Petrel) and with a code that
is within the designated ranges
Can add a coordinate reference system Cannot add a coordinate reference
or simple transform from the Esri system or simple transform from the Esri
catalog, using the code (for example, if catalog, using the code (because it
a person deletes one and later wants to cannot be deleted)
add it back)

 To Change the Configuration

1 In a text editor such as Notepad, open the configuration file:
• To change the Coordinate System Manager configuration file (because you
did not deploy the database for Petrel), open
CoordinateSystemAdmin.exe.config.
• To change the Studio Manager configuration file (because you did deploy the
database), open StudioManager.exe.config file, please refer to the
Studio Manager Installation Guide for the location of the file.
2 In the ApplicationConfigurations section, change the flag for

AllowAdminOutOfBoxCatalog to True or False.

D Enhanced Summary File Format
The simulator output for summary results in the form of *.(F)SMSPEC and *.A/Sxxx
files reflects the way the simulator solves the mathematical equations for increasing
time. Accessing the data for a particular summary vector–usually for plotting against
time–requires the entire data set. This access pattern is poorly supported by the
simulator output mentioned above, more so if the data is located on a network
drive. In effect, accessing summary data often results in high access times over
network connections. This is the primary motivation behind the introduction of a
new, enhanced file format for storing summary data with Petrel 2013. Requesting
summary data using this new file format will result in much increased access speed
via network connections.
How does it work? The recommended workflow is to make the conversion to the enhanced summary
file format part of the simulation submission job rather than via Petrel. For further
information please refer to Technical Details. General Considerations contains
information on performance and resource requirements.
Conversion-related When you load a Petrel project, be it legacy or not, Petrel will check whether
worksteps in Petrel conversion is needed. If so, the conversion process to the new file format is started
in the background without impeding Petrel itself. Names of individual cases being
converted appear in red font with the addition "(summary conversion being
active...)" as seen in the following figure:
• • • • • •
Note: You are advised not to access summary data for a case for the duration of
the conversion process in case the data is stored on a network location.
Although you can access the data, you will not benefit from increased
summary data performance until the end of the conversion.
If you decide not to use the enhanced summary file format for a particular case,
open its settings dialog by right clicking the case, selecting the Results import tab
and clearing the Use enhanced summary file format option, as shown in the
following figure:
Enhanced Summary File Format D-1

Generally, Petrel will make sure the enhanced summary file format is being used and
kept up-to-date. However, you have the option to enforce conversion by right
clicking on a simulation case, case folder, or case collection and selecting Convert
summary data into enhanced summary file format on the popup menu.
If this option is grayed out, Petrel either has not found any summary data for this
case, or the option selection has been cleared on the Results import tab on the
case.
You will notice several messages in the message log explaining the process.
D-2 Petrel Platform Installation Guide 2013.2

Technical Details
Technical Details
There are two ways the conversion into the enhanced summary file format can
be done.
1. As part for the simulation submission workflow
Upon successfully completing the simulation, the conversion to the enhanced
file format is triggered as a port-processing step before the results are loaded
back into Petrel. This is the recommended workflow (as it hides the conversion
time).
2. When importing the deck into Petrel or loading the results
Petrel will check whether conversion is needed. In this case, the conversion will
happen on the machine on which Petrel is installed. Although the conversion is
done without impeding Petrel, it is not recommended that you allow Petrel to
do the conversion as it can be expensive in terms of resources needed (time
and memory).
The Preferred The conversion from the simulator output for the summary results into the
Workflow for enhanced summary file format may take a considerable amount of time depending
Conversion on the size of the summary data, network speed, and the load on the machine Petrel
is running. Therefore, you are advised to make the conversion process part of the
simulation submission system. This section describes three different situations to
make the conversion part of the recommended post-simulation workflow.
1. ECLRun >= 2012 Let us first consider ECLRun 2012, the first version of ECLRun aware of this new file
format. If you submit a simulation run via ECLRun 2012, it will trigger the simulation
data conversion after successful completion of the simulation run. That means by
the time the results are read back into Petrel, the enhanced summary file has
already been created and hence Petrel will not do it. You will benefit from the
advantages of this new file format immediately.
You can control certain aspects of the conversion by editing the
PetrelConfiguration.xml file.
• • • • • •
Note: Before changing this file, please close all instances of Petrel; otherwise,
Petrel will revert your changes upon shutdown.
Open the file and find the section <SimulationCommands>. It should look like
this:
<SimulationCommands>
<Command Name="ECLIPSE 100">
<Submit>eclrun.exe [-v %VERSION%] [-s %SERVER%] [-q
%QUEUE%] [--username %USERID%] [--passwd %PASSWORD%]
[%OPTIONS%] eclipse %DATAFILE%</Submit>
<Fetch>eclrun.exe [--passwd %PASSWORD%] check
%DATAFILE%</Fetch>

Technical Details
<Kill>eclrun.exe [--passwd %PASSWORD%] kill

%DATAFILE%</Kill>
</Command>
<Command Name="ECLIPSE 300">
[%OPTIONS%] e300 %DATAFILE%</Submit>
%DATAFILE%</Fetch>
%DATAFILE%</Kill>
</Command>
<Command Name="FrontSim">
[%OPTIONS%] frontsim %DATAFILE%</Submit>
%DATAFILE%</Fetch>
%DATAFILE%</Kill>
</Command>
</SimulationCommands>
The options are as follows:
• hdf-converter-version
• summary-conversion
Assume that you are using ECLRun 2012 and you have to support submissions from
both Petrel 2012 and Petrel 2013. By default, ECLRun will start the newest converter
it finds. It decides this based on the file system structure, for example \ecl\2012.1\,
\ecl\2012 etc. If you do not tell ECLRun explicitly to start the 2012 converter for
submission from Petrel 2013, the converted summary file will be rejected by Petrel
2013 and regenerated locally into the new file format, which can be time-
consuming. To avoid this, append the submission string of the 'Submit' xml tag with
[- - hdf-converter-version 2012.1] for all the simulators E100, E300 and Frontsim for
the 2012 PetrelConfiguration.xml file. For example:
eclrun.exe [-v %VERSION%] [-s %SERVER%] [-q %QUEUE%] [--
username %USERID%] [--passwd %PASSWORD%] [%OPTIONS%] [--hdf-
converter-version 2012.1] e300 %DATAFILE%
To suppress conversion into the new summary file format altogether, use [- -
summary-conversion=no], i.e.
eclrun.exe [-v %VERSION%] [-s %SERVER%] [-q %QUEUE%] [--
username %USERID%] [--passwd %PASSWORD%] [%OPTIONS%] [--
summary-conversion=no] e300 %DATAFILE%

Technical Details
The location of the xml file is system-dependent. For Windows 7 its default location
is C:\Users\UsernName\AppData\Roaming\Schlumberger\Petrel\Petrel-
version\.
2. Pre-2012 ECLRun In this case, ECLRun will be unaware of the enhanced summary file format. To
complete the conversion automatically at the end of the simulation run, use the
stand-alone converter utility. Contact Schlumberger support to obtain the version
you need. Once the converter is properly installed, ensure it is run after the end of a
successful simulation before the simulation results are read back into Petrel. See
“Stand-alone Enhanced Summary Converter Utility” on page D-5 for additional
details for using the converter.
• • • • • •
Note: If you have changed PetrelConfiguration.xml to include the hdf options
mentioned above, you should break simulation submissions from within
Petrel 2013 with older ECLRun versions in case you should decide to
downgrade.
3. Custom Remote For successful for summary conversion obtain the stand-alone converter from
Submission Systems Schlumberger support. Supported systems include Microsoft Windows and various
Linux versions. Contact your system administrator for setup instructions. See
“Stand-alone Enhanced Summary Converter Utility” on page D-5 for additional
details for using the converter.
Stand-alone The Windows version of the stand-alone converter will be installed with the Petrel
Enhanced Summary installation. The executable is named ConvertSummaryData2DataBase.exe and
Converter Utility is located in the same location as the Petrel application file petrel.exe.
• • • • • •
Note: Usually, the simulation run happens on a cluster. One way to make the
summary conversion part of the submission workflow is to install the
stand-alone converter on the same machine the simulation is being
executed. For this you will need to obtain either the Windows or Linux
version of the converter from Schlumberger support.
The converter accepts two mandatory command line options:

1. Either a directory or a path to a specific (F)SMSPEC file
2. Directory for storing temporary files
If the first argument is a directory, the converter will recursively look for (F)SMSPEC
files in that directory and convert the corresponding summary data into the new file
format. In the case of a specific (F)SMSPEC file, only its summary data will be
converted. The second argument could, for example be C:\TEMP for Windows and
/tmp for Linux. Examples for Windows include the following:
• ConvertSummaryData2DataBase.exe C:\Users\foo\foo.SMSPEC C:\TEMP
• ConvertSummaryData2DataBase.exe C:\Users\foo\foo
C:\Users\foo\AppData\Local\Temp
• ConvertSummaryData2DataBase.exe C:\Users\foo\foo %TEMP%

Technical Details
Linux examples include the following:

• ConvertSummaryData2DataBase.exe /home/foo/foo.SMSPEC /tmp
• ConvertSummaryData2DataBase.exe /home/foo /users/foo/tmp
• ConvertSummaryData2DataBase.exe /home/foo $TMPDIR
If you see errors loading shared libraries when trying to run the Linux hdf converter,
you might have to add the path to the shared libraries installed with ECLRun to your
LD_LIBRARY_PATH environment variable. This could look like this when using shell
csh: $ setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:/path/to/
shared/libraries. To make this persistent, you must add this command to the
shell config file, for example .cshrc for csh.

General Considerations
This page lists some general comments on behavior, resources and performance for
the enhanced summary file format.
Best practice • While in use by Petrel, the enhanced summary file (extension .h5) cannot be
guidelines modified/deleted outside of Petrel. This ensures that the data Petrel works with
and exposes to the user is in sync with the data on disk. If you still need to
remove or change it, you will have to remove the simulation results for the
particular case first from inside Petrel (right click on the simulation case, and
select Remove simulation results).
• Petrel will warn you upon project load if any of the enhanced summary files are
read-only. This might become an issue after a simulation run. In this case, when
the simulation results are pulled back, Petrel is unable to update the enhanced
summary file returned by the simulation submission. In order to not display wrong
summary results, Petrel will in this case fall back to the standard summary files
*.(F)SMSPEC and *.A/Sxxxx. A warning is written to the message log.
• If the option Convert summary data into enhanced summary file format,
(which appears after right clicking on a case), is greyed out, Petrel either has not
found any summary data for this case, or the option to use the enhanced
summary file format has been cleared on the Results import tab on the case.
• When summary data is loaded into Petrel, the old-style summary data is in sync
with the summary data must be the new enhanced summary file. To keep them in
sync, the converter writes the new keyword TIMESTMP (documented in the
Eclipse File Format Reference Manual) into the (F)SMSPEC file. Hence, for
conversion to work reliably, the (F)SMSPEC file must not be read-only.
Performance Performance can be an issue if you are working with large summary data sets. In
Consideration any case, the enhanced summary file should be generated as part of the simulation
run so it is available to Petrel by the time the results come back from the remote
submission. Performance considerations include the following:
• The bigger the summary data files, the longer the conversion will take.
• Make sure you have sufficient main memory> The more memory, the faster the
conversion will be. Roughly, make sure you have #physical RAM = 2*size of
summary files.
• If the project data is located on a network location, a fast network connection
pays off
• You should only request the summary data and report steps you really need. The
more data you request, the slower the conversion and import into Petrel.
• If a lot of physical memory is available (as described above), consider setting the
environment variable SLB_FAST_SUMMARY_READER on the machine that does
the enhanced file format conversion. Doing so can considerably speed up
conversion.


Index
Numerics Geophysics module, recommendations for 3-10

graphics card
2D lines, recommendations for 3-10
recommendations 3-5
3D surveys, recommendations for 3-10
3D windows and 6-DOF devices 3-8 recommendations for Geophysics module 3-10
3D windows and DOF devices 3-8 system requirements 3-2
6-degree-of-freedom devices 3-8
6-DOF devices 3-8 I
installation package 4-2
A installing
activating plug-in licenses 5-2 plug-ins 5-2
Advanced Security Option (ASO) C-2 plug-ins in different home directory 5-8
APS Printer Drivers
about B-1 L
ArcSDE direct connect C-2 laptops, recommended 3-9
license
C plug-ins 5-2
configuring selecting package 4-6
client, for single sign-on C-2 license package
coordinate reference systems, custom C-5 Favorite 4-7
customizing Plug-in Manager interface 5-3 license server
environment variables 4-4
license server environment
D defining 4-4
database using configuration file 4-5
connecting to C-3 licenses
remember password C-4 none found 4-4
display, system requirements 3-2 LiveQuest 3-12
DOF devices 3-8 LM_LICENSE_FILE 4-4
downloading installation package 4-2
drive M
recommendations for Geophysics module 3-10
system requirements 3-2 memory
recommendations for Geophysics module 3-10
system requirements 3-2
F modeling, processor recommendations for 3-5
Favorite license package 4-7 monitors, system requirements for 3-2
G N
Geobody interpretation setup scenario 3-10 network shared disk
Index 1-1
deploying plug-ins on 5-5 S
No licenses found message 4-4
Seismic interpretation setup scenario 3-10
Select license package window 4-6
O single sign on
Ocean Plug-in Manager 5-2 client system requirements C-2
Ocean Store 5-2 single sign-on
operating system, system requirements for 3-2 configuring the client for C-2
Oracle C-2 Slb.P4E.Dbx.Config file C-4
SLBSLS_LICENSE_FILE 4-4
P Software Download Center 4-2
storage
password, remembering C-4
network storage recommendations 3-11
Petrel
download 4-2
system requirements
for Petrel 3-2
uninstalling 4-13
for Petrel with LiveQuest 3-12, 3-14
Petrel license
system setup scenarios 3-10
selecting package 4-6
PetrelConfiguration.xml 4-4
and the global configuration file A-5 U
plotting B-1 uninstalling
Plug-in Manager Petrel 4-13
customizing interface 5-3 plug-ins 5-2
plug-ins upgrading repositories C-2
activating licenses for 5-2
deploying from a network shared disk 5-5
installing 5-2
installing in different directory 5-8
Ocean Plug-in Manager 5-2
Petrel 5-2
purchasing 5-2
uninstalling 5-2
printing B-1
processor
recommendations 3-4
R
recommendations
graphics cards 3-5
laptops and workstations 3-9
network storage 3-11
processors 3-4
system components for Geophysics module 3-10
registry
update server’s IRPStackSize A-6
Remember password feature C-4
remote access with LiveQuest 3-12
repository
backup and recovery C-2
upgrade C-2

Petrel 2013 Installation Guide

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Petrel 2013 Installation Guide

Diunggah oleh

Hak Cipta:

Format Tersedia

Petrel 2013

An asterisk * is used throughout this document to designate a mark of

Schlumberger Private - Customer Use

Schlumberger Private - Customer Use

Schlumberger Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

3 System Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Schlumberger Private - Customer Use

Appendix A Troubleshooting and Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . A-1

What is the Petrel Startup Optimization Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

vi Petrel Platform Installation Guide 2013.2

Schlumberger Private - Customer Use

Appendix B Advanced Printing System (APS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Appendix C Studio Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Third Party Software Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2

Appendix D Enhanced Summary File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D-1

How does it work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

Schlumberger Private - Customer Use

Schlumberger Private - Customer Use

Schlumberger Product Documentation ......................................................... 1-2

Information Resources 1-1

Schlumberger Private - Customer Use

Schlumberger Product Documentation

Typestyle The following conventions are observed throughout this guide:

1-2 Petrel Platform Installation Guide 2013.2

Schlumberger Private - Customer Use

Information Resources 1-3

Schlumberger Private - Customer Use

1-4 Petrel Platform Installation Guide 2013.2

Schlumberger Private - Customer Use

Introduction ............................................................................................... 2-2

Schlumberger Private - Customer Use

Audience This guide is useful for the following people:

2-2 Petrel Platform Installation Guide 2013.2

Schlumberger Private - Customer Use

Petrel 2013 Distribution

Schlumberger Private - Customer Use

2-4 Petrel Platform Installation Guide 2013.2

Schlumberger Private - Customer Use

Studio Deployment Overview

Schlumberger Private - Customer Use

2-6 Petrel Platform Installation Guide 2013.2

Schlumberger Private - Customer Use

System Requirements ................................................................................. 3-2

System Environment 3-1

Schlumberger Private - Customer Use

Minimum System Recommendations

Operating system Microsoft Windows 7 SP1 - (64-bit)

3-2 Petrel Platform Installation Guide 2013.2

Schlumberger Private - Customer Use

Other Required Software

Microsoft .NET® Framework 4.0

System Environment 3-3

Schlumberger Private - Customer Use

Additional Information: Operating Systems and Hardware Selections

Operating System Petrel 64-Bit

Processors Processor speed is important for the following types of tasks:

Parallel and in the background Background

3-4 Petrel Platform Installation Guide 2013.2

Schlumberger Private - Customer Use

Parallel and in the background Background

If you want to run FrontSim or ECLIPSE on the same workstation as Petrel,

It is advisable to consider the speed of Quick Path Interconnect(QPI) or Front Side

System Environment 3-5