A Pragmatic Approach to Data and Application Integration

1
A Pragmatic Approach to Data and Application
Integration

• Anadarko Petroleum Corporation
• Petris Technology

John Jacobs Manager, Exploration Data
Base Information Technology Services Anadarko
Petroleum Corp.
Jeffrey W. Pferd, Ph.D. Sr. V.P. of Product
Development and Delivery Petris Technology
2
Presentation Outline

• Scope / Requirements / Environment
• Design / Technology
• Philosophy / Development
• What Was Not Done
• Maximize ROI in Data
• Workflow Data-flow Analysis
• Summary

3
Problem Scope

• Available Data
• Available Applications
• Exchange of Data

4
User Requirements

• Browse All Accessible Data
• by geographic location
• by type(s)
• Browse All Available Applications
• list application functionality
• Select Transfer Data to Destination

5
Anadarko EP Environment
SeisWorks
StratWorks
Recall
Geographix
Intellex
ZMap
Petra
Application Data
Geo graphix
Intellex
ZMap
Open Works
Recall
Petra
External Data
Tobin / (DCW)
PI
Auspex
Dwights
6
WINDS Enterprise
User Interface
Common Desktop
Seismic Interpretation
Data Browsers
Mapping
X-Section Log Analysis
Applications
SeisWorks
StratWorks
Recall
Geographix
Intellex
ZMap
Petra
Application Data
Geo graphix
Intellex
ZMap
Open Works
Recall
Petra
Data Catalog / Exchange
Meta Data
Data Exchange with Common Data Format
External Data
Tobin / (DCW)
PI
Auspex
Dwights
7
Design Components

• Common Desktop
• Application Search and Launch
• Data Browsers
• Summary - Tree Browser
• Detail - Tabular Browser
• Spatial Browser
• Meta Data
• for Data
• for Applications
• Data Exchange
• Data Synchronization

8
Selected Technology

• Java Based Client
• Applet or Application
• Intranet Internet Compliant
• Distributed Object Architecture
• CORBA IIOP Based Communication
• Data Streaming for Large Data Sets
• Spatial Toolkit from Formida Software
• Spatial Data stored in Oracle 8 SDC
• Functionality coded in Java C

9
Philosophy

• Add Value not Complexity
• Maximize Resource Usage ROI
• Modular Design
• Flexible
• Extensible
• Customizable
• Phased Functionality / No Big Bang
• Keep It Simple
• Must be Commercially Supported

10
Development Process

• Define Architecture System Design
• Prototype Key Components
• Present to Users for Feedback
• Incorporate Feedback into Design
• Buy Available 3rd Party Components

11
What Was Not Done

• Modify Third Party Applications
• Touch Data in Transfer
• Develop a Master/Project Database
• Develop a Data Warehouse or Data Marts
• Develop a Corporate Database

12
Maximize ROI in Data

• Increase Data Visibility
• Increase Data Accessibility
• Understand Workflow
• Understand Data Flow
• Track Data Movement

13
Project Workflow Example
14
Prospect Workflow
Continue
Prospect Indicated
Block/ Lease Negotiation
Drilling Plan
New Ventures/ Basin Studies
Prospect Analysis
Field Analysis
Development
Yes
Yes
Yes
No
No
No
Archive
Archive
Archive
15
Data-flow
16
Data Integration Opportunities

• Identify Where Data Might Be Shared
• common type
• Availability of Access
• published APIs
• non standard methods
• standard SQL
• Identify Required Attributes
• merge with another source

17
WINDS ENTERPRISE99
User Interface
Common Desktop Application Launcher
Mapping
Database
X-Section Log Analysis
Browsers (GIS Textual)
Seismic Interpretation
Reservoir Engineering
Applications
SeisWorks EarthCube VoxelGeo Stratimagic
StratWorks
Recall
CTC Insightful
NAODB Guardian Excalibur
Geographix Petra Intellex/GOM
OpenWorks / OpenExplorer
Recall Log Curves
NAODB, Guardian/TRC, Excalibur
Application Data
Data Catalog / Exchange
Meta Data
Data Exchange / Common Data Model
External Data
18
Summary

• Increased Data Visibility
• Data Catalog
• Data Browsers
• Increased Application Visibility
• Application Search
• Application Launch
• Data Exchange
• Data Transfer
• Catalog Synchronization Spyder Process
• Dynamic Common Model