POSC epiSEM Earth Model Information Management

1
POSC epiSEM Earth Model Information Management

• Dan Schenck, POSC

2
Shared Earth Model Vision
3
epiSEMPrimary Objective
To define specifications for open interfaces and
shared services that enable the implementation of
a new generation of interoperable earth modeling
products
Vendor Product B
Vendor Product A
epiSEM Interface
Multi-vendor epiSEM Compliant Modeling Platform
4
epiSEM Partners

• Agip
• Chevron
• IFP
• Landmark
• Mobil

• PDS
• POSC
• Schlumberger
• Shell
• Statoil

Design team members
5
Project Time Line1998-2000
Q3
Q4
Q1
Q2
Q3
Q4
Q1
6
The Situation
Seismic interpretation
Geologic modeling
Upscaling
Property modeling
Simulation
7
The Problems

• 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 Modeling Terminology
• 15 - Information Sharing
• 16 - Complexity
• 17 - Application Interaction
• 18 - Shared Services
• 19 - Model Management

8
epiSEM Information Services Vision

• Define shared (vendor neutral) interfaces to
  earth modeling catalog services to

• Publish, organize, improve manage diverse earth
  model information
• Discover critical earth model information from a
  variety of sources
• Allow users to access the resources indexed by
  the catalog

9
Examples of Questions Answered using epiSEM

• What input data has been updated since model X
  was last used?
• What downstream models depend on the results of
  model Y?
• On what assumptions are these models based?
• What compensations for uncertainty have been
  considered in model Z?
• What are the differences between this model and
  its previous version?

10
Clients of Catalog Information Services
PortfolioManagement
Multi Disciplinary Asset Team
11
Architecture of Catalog System
VendorApplication
epiSEMIS API
Repository ProviderAPI
VendorData Store
12
Using the Catalog

• Services

Clients of Services

• 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

13
Example
14
Architecture of Prototype
Web Client
Servlet
Catalog List
epiSEM API
epiSEM Information Services Manager
Repository Provider API
Demo
Catalog 1
Rep-1
15
Benefits -
?

• IT Point of View
• Addresses todays problems
• Achievable
• Leverages prior collaborative investment
• Scaleable Design, Implementation, Deployment
• Vendor Neutral
• Facilitates interoperability Model Centric work
  processes

16
Benefits - EP Point of View
?

• Satisfies Short and Long Term Needs
• Scaleable from Asset Team to Corporation
• Supports Model Centric work processes
• Applicable to most types of Earth Model
• Applicable to many Vendors products
• Retains and protects value of Models
• Enables assessment of Decision Quality
• Moves us towards ultimate goal of a unified
  approach to earth modeling.

17
Whats Next? - SEM Phase 2

• Develop complete proof-of concept to
• Validate epiSEM services interfaces
• Flesh out remaining interface design
• Boost confidence of vendors and end users in
  epiSEM approach
• Timeframe
• Start in February 2000
• Deliver initial proof-of-concept by end of April

18
SEM Needs Your Support!

• Seeking Oil Company Vendor Sponsors
• To fund building the proof-of-concept
• To test the proof-of-concept
• Estimated budget - 500K
• Desire 10 funding sponsors

19
For More Information

• Visit the SEM web site
• http//www.posc.org/workprgm/sem.shtml
• Contact Dan Schenck
• Phone [phone]
• Fax [phone]
• Email schenck_at_posc.org