petrel database extension - petreldbx
TRANSCRIPT
Petrel Database Extension - PetrelDBXInsight into data management in Petrel
Todd Olsen
Petrel Portfolio Product Champion - Petrel IM
Have you ever heard or felt this way yourself?
• “Petrel‟s great, but what
database does it run on?”
• “A filesystem!! That‟s never
going to work in my
organization!”
• “You can‟t handle projections?
That won‟t work in my company”
• “How will Petrel interpreters
share their data?”
Data managers see Petrel differently than users
If we are going to be successful with Petrel…
• We need to embrace our users who are working with and continually
improving data and interpretations.
• Working with Petrel is different than working with Openworks or
GeoFrame. G&G users go through a learning curve with Petrel, so too
will the Petrel data management community.
• We need to support our users inside of their chosen environment of
Petrel and guide them to use their product and create solid best
practices they can use in a responsible way
• Lets learn a little more about Petrel and its data…
Positives and challenges with Petrel today
Complete workflow tool covering seismic to
simulation
Petrel users are not limited by their creativity
Easy for users to update interpretations when
there is new or updated data
Petrel User
Petrel Project
Petrel Project
Petrel Project
Petrel Project
Petrel Project
Petrel Project
Petrel Project
Petrel Project
Creates many Petrel projects
Without best practices it may become
difficult for users to share their data
Difficult to reconcile data when best
practices are not followed
Petrel User
Petrel Project
Petrel Project
Petrel Project
Petrel Project
Petrel Project
Petrel Project
Petrel ProjectPetrel Project
Petrel User
Petrel Project
Petrel Project
Petrel Project
Petrel Project
Petrel Project
Petrel Project
Petrel ProjectPetrel Project
Petrel Data - importance of the GUID in Petrel
• Relationship between objects is
remembered via GUID
• It allows Petrel to easily
regenerate, e.g. a complex
model if the input data was
changed
E.g. put surface Top Ness in the
Result field in the Make/Edit surface
dialog.
Interpretation Top Ness automatically
shows up in the Input field.
Interpreters
DM Challenges - Issues with different GUIDs
Modeler
Legacy Project(GeoFrame Project) Base Cretaceous
Arun’s Petrel Project
Dave’s Petrel Project
via OpenSpirit or ASCII export/import
Lisa’s Petrel Project
via Reference Project Tool
Legacy Interpretation
Base Cretaceous
Surface S1
Note: Links are remembered via the GUID!
via Reference Project Tool
Lisa ended up with two
interpretations.
Base CretaceousGUID1
Base CretaceousGUID2
Base CretaceousGUID1
Base CretaceousGUID2
Legacy Interpretation
Base Cretaceous
Legacy Interpretation
Base Cretaceous
Arun’s Interpretation
Base Cretaceous
Dave’s Interpretation
Base Cretaceous
Arun’s Interpretation
Base Cretaceous
Dave’s Interpretation
Base Cretaceous
She had to re-link the surface to the
updated source .
Right way: regeneration is easy
Data Managers/Asset Team Leads
Modeler
Interpreters
Legacy Project(GeoFrame Project)
Arun’s Petrel Project
Dave’s Petrel Project
via OpenSpirit or ASCII export/import
Lisa’s Petrel Project
via Reference Project Tool
Surface S1
Workgroup Ref. Project
via Reference Project Tool
Base Cretaceous
Base CretaceousGUID1
Base CretaceousGUID1
Base CretaceousGUID1
Base CretaceousGUID1
Legacy Interpretation
Base Cretaceous
Legacy Interpretation
Base Cretaceous
Legacy Interpretation
Base Cretaceous
Arun’s Interpretation
Base Cretaceous
Arun’s Interpretation
Base Cretaceous
Dave’s Interpretation
Base Cretaceous
Legacy Interpretation
Base Cretaceous
Arun’s Interpretation
Base Cretaceous
Dave’s Interpretation
Base Cretaceous
Dave’s Interpretation
Base Cretaceous
Issues with re-linking
• In this case, it was not such a big deal to re-link. So, why
should we care?
– Because, it puts the responsibility on someone to do this.
– Because, this person needs to know which item to re-link to
(which is difficult when the data sets are large).
– Because, it may be a lot of work when many objects have to
be re-linked.
– Because, changes are often made just before the final
presentation and we cannot afford simple mistakes
Another example – it‟s not just data it‟s Petrel data
Every object has a Settings window.
Note: The Settings window may remain
open at all times during a session.
A few stated challenges for a PetrelDBX solution
• Support small to large scale deployments of Petrel. Scale beyond Reference Project
Workflows
• Perform Cartographic Reference System (CRS) conversions of data
• Remove CRS bound restrictions to Petrel Project Network thus eliminating a number
of redundant Petrel reference projects
• It‟s more than just data, it‟s Petrel data – retain the Petrel intelligence/fidelity
• Put the information in a database where everything is more transparent
• Keep the interface simple as it is going to be inside of Petrel and used by Petrel users
• Provide data managers capabilities to rescue data when it was parented by a
duplicate GUID item
Diagram legend
Petrel Project Network Example
PetrelProject
PetrelProject
Data transfer
via Reference
project tool
Data Transfer
via OpenSpirit
Petrel
Reference
Project
Petrel User
Project
Petrel User (workflow step)
Data Manager (workflow step)
(n)
(n)
WorkgroupReference Project
Workgroup Petrel Users
User 2 Project
User 1 Project
User (n) Project
3
External 3D ZGY
External 2D Seg-y
Data must enter the Petrel Project Network only once
Note: Reference
Projects are
constrained by CRS,
project units and
data volume
1
Ref. Project
4
Petrel Staging Project
2
Petrel Project Network Example
WorkgroupReference Project
Workgroup Petrel Users
User 2 Project
User 1 Project
User (n) Project
3
External 3D ZGY
External 2D Seg-y
Note: Reference
Projects are
constrained by CRS,
project units and
data volume
1
Ref. Project
4
Petrel Staging Project
2
Data workflow steps
Data manager uploads
wellbore, well deviation,
timedepth data, well markers
using OpenSpirit data
selector.
Data manager moves staged
data to workgroup reference
projects using Petrel
reference project tool (RPT).
Note that only seismic data
pointers are copied.
Petrel User 1 moves well
data and seismic data into
personal working project
using RPT. Note that only
seismic data pointers are
copied. Bulk data remains on
external corporate disk
network
Petrel User 2 moves well
data and seismic data into
personal working project
using RPT.
2
1
3
4
Ignoring the Petrel Project data entry golden rule
• Every object in Petrel has a GUID
• If objects that were loaded directly into two
user projects, they will have different
GUIDS
• This behavior limits sharing of data in the
Reference Project Tool (RPT) and
PetrelDBX
Data must enter the Petrel Project Network only once
Diagram legend
Example: Expanded Petrel Project Network
PetrelProject
PetrelProject
Data transfer
via Reference
project tool
Data Transfer
via OpenSpirit
Petrel
Reference
Project
Petrel User
Project
Petrel User (workflow step)
Data Manager (workflow step)
(n)
(n)
WorkgroupReference Project(s)
2
(n)
External 3D ZGY
External 2D Seg-y
Note: Reference
Projects are
constrained by CRS,
project units and
data volume
1
Workgroup Petrel Users
User 2 Project
User 1 Project
User (n) Project
Ref. Project
(n)
Workgroup Petrel Users
User 2 Project
User 1 Project
User (n) Project
Workgroup Petrel Users
User 2 Project
User 1 Project
User (n) Project
Ref. Project
Ref. Project
Petrel Staging Project
(n)
Diagram legend
Example Petrel Project Network with PetrelDBX
PetrelProject
PetrelProject
Data transfer
via Reference
project tool
Data Transfer
via OpenSpirit
Petrel
Reference
Project
Petrel User
Project
Petrel User (workflow step)
Data Manager (workflow step)
(n)
(n)
DBX repository can scale to support multiple workgroups
2
(n)
External 3D ZGY
External 2D Seg-y
1
Workgroup Petrel Users
User 2 Project
User 1 Project
User (n) Project
(n)
Workgroup Petrel Users
User 2 Project
User 1 Project
User (n) Project
Workgroup Petrel Users
User 2 Project
User 1 Project
User (n) Project
Petrel Staging Project
(n)
DBX Repository
WORKSPACE PROJECTS
Traditional Petrel
using .pet files
Geologist Geophysicist Res. Eng.
.pet .pet .pet
• Full enterprise capabilities of a database without sacrificing the flexibility of files
• Expands upon existing Reference Project workflows, similar look and feel
• Accessed directly from Petrel
Petrel DBX
• Efficiently and effectively share data in a safe manner
• Maintain the completeness of the Petrel data
Collaboration
• Pack-and-go: portability of projects
• Good performance; scalable
Flexible environment
• Tools to lock data
• Tools to manage users and projects
• Better architecture for future DBX advancements
• Ensure security of data
The power of a database
• Generate data reports directly from Oracle
• DBX repository indexed and accessible from Petrel Data in Context
Open access
Petrel Project Network
Petrel
reference
project
Petrel
reference
project
Petrel
reference
project
DBX
User Tools Manager
DBX
What is Petrel DBX?
Data in database, uses
Seabed schemaDBX
Repository
Scheduling and
automation is possible
Another way of looking at Petrel and Petrel DBX:
It‟s like iTunes® to an iPod®Other solutions are like a radio signal: must be
connected to get the music.
Similarly, users must be connected in order to work
with the data and all changes to the data are
instantaneously reflected, regardless of whether they
intended to share the results or not.
Petrel DBX is like iTunes to an iPod: sync music
when ready; always have music available. You can
have your own playlists, and add new songs when
wanted.
Similarly, Petrel Users can choose when to share
their work with the team. They don‟t have to mine
through endless copies of colleagues intermediate
interpretations. They can work offline with the same
Petrel functionality they know and love.
Typical Data Lifecycle – Collaborate as Required
Gather DataAnalyze
Data
Create Derived
Data
Peer Review
Accepted?
Final Review
Accepted?
Baseline Data
Update Data
Update Data
Reuse Baseline Data
Work Alone
Isolation/Stability
Work as a Team
Interactivity
Milestone
Petrel Projects DBX Repository
Access Shared Data
Application independent of Petrel (does not require Petrel to use)
Features of Petrel DBX
Manage repositories Manage your Petrel repository standards
Manage the project life cycle Create snapshots of data during project life cycles
Manage users & rights Manage Petrel DBX users
Manage data access rights Assign users access rights to repository data
Manage coordinate systems Create custom coordinate systems
Manage quality attributes Define control lists used to tag Petrel data
Petrel DBX
Manager Application to manage
the Petrel DBX
environment
+
Tools and features built into the Petrel application
DBX tool Synchronize data between Petrel and PetrelDBX
repositories
Filter feature Filter repository data to the area of interest (AOI)
Quality attribute feature Label, or flag, data with team ownership & quality measures
Table tools View Petrel project data and repository data in a table
Dashboard tool Keep informed about changes to data of interest
Complete feature Keep certain data always read-only
Copy feature Retrieve repository data as a copy
Auto-sync feature Sync data to DBX Repository via command line
Petrel DBX Data collaboration
tools and features
What does Petrel DBX give you?
• Users can quickly find their data of interest
• Users are able to share their data with the team
• Users and data administrators can apply quality tags to data that is then accessible in Petrel
• Users share data safely without overwriting others‟ work
Collaboration
• DBX repository can consolidate Petrel projects
• Coordinate and unit conversions
• Many teams can easily share data
• Data volume not limited by Petrel‟s capabilities
• Advanced transfer selection capability from well markers
• Concurrent access to Petrel data with pack-n-go
Scalability
Sync Data
Quality
attributes/flags
Multi-User
Coordinates,
UnitsConsolidate
Projects
Filters
Filters
What does Petrel DBX give you?
• Manage project lifecycle through snapshots
• Data recovery workflows
• Limit proliferation of Petrel projects
• Data Managers can control access
• Quality context from users eases management
• Backup DBX repositories
Manageability
• DBX repository indexed by Petrel Data in Context. Further PDC can launch PetrelDBX in context with search results to complete a data transfer workflow
• Oracle, ESRI, Linux, Windows (client)
• Database backend makes other interesting workflows possible
• DBX repository based on Seabed a published data model
Integration
Manage Users
Backup/Restore Dashboards
Snapshots
Seabed-based
Initial Petrel DBX data footprint
Petrel name Alias
Well Borehole
Deviation Trajectory
Checkshots
Well logs
Markers
Seismic 3D survey Seismic collection
Seismic 3D volumes Seismic cube
Seismic 2D survey Seismic line 2D
collection
Seismic 2D line
Petrel name Alias
Seismic 3D interpretation Horizon
Seismic 3D interpretation
attribute
Horizon property 3D
Seismic 2D interpretation Horizon interpretation 2D
Seismic 2D interpretation
attribute
Horizon Property 2D
Fault interpretation
Fault interpretation
attribute
Fault property
Surface
Surface attribute Surface property
Petrel DBX compared to the Reference Project Tool
Feature Description RPT DBX
Send/retrieve data Tool to send/retrieve data
Timestamp filter Filter based on the state of the data (new, old, updated)
Spatial filter Filter based on an area of interest (spatial filter)
Data attribute filter Filter by attributes (Ex: Wells begin with „A‟; Data updated by User1)
Filter management Save and share filters; Create public & personal filters
Coordinate/unit conversions Perform coordinate/unit conversions when transferring
Timestamp comparison Compare timestamp information
Data attribute comparison Compare key attributes
Manage data lifecycle Track the progression of data; Mark data as complete (read-only)
User access management Ensure only those with access rights update/read data
Quality attributes Tag data with quality measurements, which can also be filtered against
Table views View Petrel project/repository data in a table; Export data to MS Excel
Petrel DBX Dashboard Easily stay informed about key data changes
Milestone data Tool to milestone data at project milestones
Increased scalability Create a data store for multiple asset teams‟ data
Repository
data tree
Error
capturing &
transfer
status
Copy mode
Timestamp
filters
Send and
recieve data
Petrel
data tree
Data synchronization - Petrel DBX Tool
Data synchronization
is easy and intuitive
Dashboard
Advanced
filters
Data
transfer
selection
Export
contents
to Excel
Column
filters
Data synchronization – Table view of dataRe-order
and sort
columns
View the Petrel project data or the Seabed data in a table
Data synchronization – Advanced filtersManage scalability by easily creating data subsets of
interest
Show data meeting
specific attribute criteria
Show data within a
specific area
Show only particular
data types
Create filters
for the entire
team to use
and
and
Applies the
filter to the
data in
Seabed
Data synchronization – Other options
Automate synchronizations via a
command line script
Select data in the Input pane,
right-click and select
Send or Receive data
petrel.exe
-DbxCommand Help*|Push|Pull
[-DbxListOnly [Yes*|No]]
[-DbxUser <user>]
-DbxPassword <password>
[-DbxDataSource <datasource>]
[-DbxRepository <repository>]
[-DbxState Any*|New|Updated|Older]
[-DbxFilter <filter>]
[-DbxExit OnSuccess*|Always|Never]
<file.pet>
Track the quality of data
– Data status
Ex: In progress, Complete
– Confidence factor
Ex: Low, High
– Critical update
Yes/No
– Business project
Ex: Block 15, Exploration
Project 09
– Comments
Ex: Approved by Team Lead
Quality attributes – Know the data status
Add rules for
mandatory
fields
Quality attributes – Set for many data items
Tag multiple data items with quality attribute values at once
Quality attribute columns
List of
reports
Add and
customize
reports
Petrel DBX DashboardMonitor quality and changes to the data in your PetrelDBX Repository
Report
resultsAutomatic
display option
Application independent of Petrel (does not require Petrel to use)
Features of Petrel DBX
Manage repositories Manage your Petrel repository standards
Manage the project life cycle Create snapshots of data during project life cycles
Manage users & rights Manage Petrel DBX users
Manage data access rights Assign users access rights to repository data
Manage coordinate systems Create custom coordinate systems
Manage quality attributes Define control lists used to tag Petrel data
Petrel DBX
Manager Application to manage
the Petrel DBX
environment
+
Tools and features built into the Petrel application
DBX tool Synchronize data between Petrel and PetrelDBX
repositories
Filter feature Filter repository data to the area of interest (AOI)
Quality attribute feature Label, or flag, data with team ownership & quality measures
Table tools View Petrel project data and repository data in a table
Dashboard tool Keep informed about changes to data of interest
Complete feature Keep certain data always read-only
Copy feature Retrieve repository data as a copy
Auto-sync feature Sync data to DBX Repository via command line
Petrel DBX Data collaboration
tools and features