POSC epiSEM

1
POSC epiSEM

• Paul Maton, POSC

2
3-Part Presentation

• Project OverviewPaul Maton, POSC
• epiSEM Information ServicesRobin Getty, PDS
• Vendor PerspectiveNajib Abusalbi, Schlumberger

3
epiSEM Partners

• Agip
• Chevron
• IFP
• Landmark
• Mobil

• PDS
• POSC
• Schlumberger
• Shell
• Statoil

Design team members
4
Time Line1998-1999
Q3
Q4
Q1
Q2
Q3
Q4
Q1
5
Project Objective
To define specifications for open interfaces and
shared services that enable the implementation of
a new generation of interoperable earth modeling
products epiSEM
Vendor Product B
Vendor Product A
epiSEM Interface
Multi-vendor epiSEM Compliant Modeling Platform
6
Problem Statement Issue Occurrence
Knowledge management
Inverse modeling
Administration/versions/data dependency
Sharable earth model
Unified time and distance scales
Data loading/other
Coverage/generality
Coherent spatial model
Uncertainty/quality
7
Current Earth Models
Seismic interpretation
Geologic modeling
Upscaling
Property modeling
Simulation
8
Shared Earth Model Vision
Geologic modeling understands depositional
environments, sequence stratigraphy, tectonics,
lithology, ...
Image consistency understands acoustic wave
propagation structural feature identification
SEM
Property modeling understands rock and fluid
properties, petrophysics, and property
distribution within and between fault blocks
Flow simulation understands conservation
of mass and energy, fluid flow pressure response
9
epiSEM Risks

• Risk
• Multiple Platforms
• Distribution complexity
• Vendor resistance
• Manual capture
• Persistent Storage
• Poor Data Mgmt
• Wrong Problem
• ???

• Counter Measure
• Java
• JNDI vs CORBA/COM
• Big Guys aboard
• Big Guys aboard
• AnOther Big Guy
• Were all screwed
• Marketing/Feedback
• ???

10
POSC epiSEMInformation Services

• Robin Getty, PDS BV

11
Earth Models
12
Project Objective
To define specifications for open interfaces and
shared services that enable the implementation of
a new generation of interoperable earth modeling
products epiSEM
Vendor Product B
Vendor Product A
epiSEM Interface
Multi-vendor epiSEM Compliant Modeling Platform
13
Requirements Analysis
Earth Modelling Tomorrow(SOLUTIONS)
Functionality
Earth Modelling Today(PROBLEMS)
Specification of solutions that satisfy the
requirements
epiSEM Project
Requirements imposed by problem on their
solutions
Future
Today
14
Problem Statements

• 1 - Geological Models and Geosteering
• 2 - Seismic Interpretation and Well Planning
• 3 - Well Planning and Uncertainty
• 4 - Best Practices and Knowledge Capture
• 5 - Data Quality
• 6 - Use of Legacy Data
• 7 - Data Exchange/Reuse
• 8 - Change Management
• 9 - Fault Handling

• 10 - Immersive 3D Visualisation
• 11 - Integration of Geological and Reservoir
  Models
• 12 - Infrastructure Platforms
• 13 - Earth Object Representations
• 14 - Earth Modelling Terminology
• 15 - Information Sharing
• 16 - Complexity
• 17 - Application Interaction
• 18 - Shared Services
• 19 - Model Management

15
Information Services

• Captures and re-uses contextual data about
  interpretations and models
• What, Who, When, Where, Why, How good..
• Track dependencies of data and models
• Transform the implicit to the explicit

16
Information Services

• Capture the artifacts of collaborative
  interpretation
• Track dependencies
• Transform the implicit to the explicit
• Provide mechanisms to capture contextual
  information
• Make available

17
Clients of Model Information

• How
• What
• When
• Who
• Why

Multi Disciplinary Asset Team
18
Meta Data Catalog
VendorApplication
epiSEMIS API
Repository ProviderAPI
VendorData Store
19
Using the Catalog

• Create Catalog
• Register Artifact
• Replace Artifact
• Amend Artifact Attributes
• Query Catalog
• Register Interest
• Notification of Change

• Stand-alone applications
• API calls in vendor products
• Agents browse and report

20
The velocity model is used to process the seismic
data into an image of horizons in the subsurface.
Faults are detected as discontinuities in the
horizons. Several faults (and horizons, whose
displacements indicate the motion on the faults)
together make up the fault framework.
Example
21
Benefits - IT Point of View

• Addresses todays problems
• Achievable
• Leverages prior collaborative investment
• Scaleable Design, Implementation, Deployment
• Vendor Neutral
• Facilitates interoperability

22
Benefits - EP Point of View

• Satisfies Short and Long Term Needs
• Scaleable from Asset Team to Corporation
• Applicable to most types of Earth Model
• Applicable to many Vendors products
• Retains and protects value of Models
• Enables assessment of Decision Quality

23
! Histories, like ancient ruins, are the fictions
of Empires.While everything forgotten, hangs in
the dark ever threatening to return. Velvet
Goldmine !
24
POSC epiSEMVendor Perspective

• Najib Abusalbi, GeoQuest