POSC Workshop CGG and Oilfield Systems

1
POSC WorkshopCGG and Oilfield Systems

• Chevron
• Houston
• 23 April 1998

2
Major Topics

• Introduce Oilfield Systems
• Oilfield Systems CGG
• Oilfield Systems POSC
• DAEX History
• Brief explanation of DAEX
• Lead up to demonstration

3
Oilfield Systems

• Company formed in 1984
• Advanced software tools for EP
• Independent U.K. Company
• Based in Southampton, England
• Offices in Houston, Calgary Aberdeen
• Practical experience of solving data problems for
  our geological product, GeoScene

4
Oilfield Systems CGG

• Worked with CGG since 1992
• CGG was sponsor of DAEX development
• Joint Projects
• Archidex, BridgeLink, OG Project, PV-DAEX
• Joint presentation at November97 meeting in
  Dallas (with Prism Technologies)
• Joint presentation at February98 meeting in
  London

5
Oilfield Systems POSC

• Industry Pilot Projects
• Houston London
• POSC helped guide DAEX development
• Epicentre in DAEX
• Epicentre Migration Project
• the Footprint Checker
• Work with Statoil on Epicentre
• SWPACT - Enterprise Exchange

6
Oilfield Systems Experience

• Data moving
• Worked with lots of EP companies
• Loaded many different project stores
• Loaded several hundred projects
• Loaded diverse data types
• Data from many sources
• Field experience of the problems
• Developed internal support tools

7
DAEX History

• which became DAEX
• DAEX Project begun in 1994
• DAEX provides a framework for building, testing
  and running exchanges
• Scaleable solutions
• Extensible too
• roll your own
• fix at runtime

8
DAEX - The Data Exchange

• Reusable components encapsulate operations on
  data (e.g. read log from PV, write well picks to
  OpenWorks)
• networks of components implement loaders or
  exchanges
• Can build proprietary components
• DAEX provides the control program
• Single, consistent user interface

9
How DAEX is used

• Stand alone
• Interactive
• Batch
• As part of a larger solution
• eg PetroVision, ADDIE, MIMS
• As a service
• eg PetroTrek

10
DAEX behind the scenes

• Normal way to run DAEX
• Just do it
• DAEX copes with the complexity of the details
• Minimal interaction on successful transfers
• Sophisticated facilities to track down problems

11
More Detail
User Interface
DAEX Master
Read Well Picks
Write Well Picks
12
Which project?
User Interface
DAEX Master
List Projects
Read Well Picks
Write Well Picks
13
Which user?
User Interface
DAEX Master
List Projects
List Users
Read Well Picks
Write Well Picks
14
A Typical Exchange
User Interface
DAEX Master
Write Picks
Geoshare File
Check Well Names
Read Picks
PetroVision
Read Well Names
15
Fan-In/Fan-Out
DAEX
Readers
Writers
16
DAEX in the Larger Picture

• The larger picture comprises...
• Corporate Store(s)
• Meta-Database (real or derived)
• GIS or similar user-friendly selection mechanism
• DAEX or similar moves selected data to Project
  Database

17
Attraction of Standards

• Appeal of a standard oil gas database
  modelPOSC Epicentre
• Fewer databasesless change
• Actually...
• DAEX uses Epicentre internally
• Subsets provide interoperability among DAEX
  components

18
POSCs Epicentre

• A thorough EP Database description
• Provides DAEX with minimal chance of data
  leakage
• Defined footprints for data transfers
• Commercial implementation
• CGGs PetroVision

19
Summary

• DAEX can be used standalone, as part of a larger
  solution or as a service
• DAEX promotes the use of Epicentre
• Oilfield Systems is working with CGG to extend
  its DAEX links to PetroVision

20
PetroVision to DAEX
PetroVision
Trigger DAEX on file creation
OpenWorks
DAEX
dump file