Infinite Integration Clay Harter Lynn Babec OpenSpirit Corporation Data Fusion via SOA Middleware

Data Fusion Seismic Potential Field Well Rock and fluid measurementsProduction Tests Initial Interpretation People Science Software $ Decisions Earth Model

Data Fusion - The Software Pieces Acquisition Processing & Modeling & Inversion Interpretation Analysis

Applications dont interoperate –No sharing of user interaction events –No sharing of data change events –Inconsistent user interface conventions –No coordination of displays Software Integration Problems Applications cant readily access data –Inconsistent, limited, or missing project catalogs –Inconsistent data models –Inconsistent formats –Mixed operating systems and computer languages –Inconsistent/unknown units and coordinates UNIX Windows UNIX

Approaches to Integration One unified standard database –POSC –PPDM Buy applications from a single vendor Transfer data – Geoshare – scripts... Use common middleware Integration Bus

Event Service Service Oriented Middleware Unit Service Coordinate Service Data Access Service Metadata Repository Available in Java,.NET, and C++ Windows, Linux, and Solaris Reference Value Service Metamodel Service Data Connector

Live Demo OpenWorks, GeoFrame, PPDM, Petra, ArcSDE OpenSpirit Runtime Data Access Coordinate Event Notification UnitMetadata ESRI ArcMap SIS Petrel Paradigm GOCAD Perigon iPointGoogle Earth Movie: 9:41

Future Possibilities Extend data foot print cover additional data types –Reservoir grid (commercialize earlier prototype) –Engineering data –... Earth Model Services

Share simple common services rather than complicated data objects Examples –Property Evaluation Given a pointset or grid return array of property values –Interpolation Given a x,y coordinate return surface z value –Intersection Given a polyline return a series of intersection points with Earth Model surfaces Given a grid return a series of polyline intersections with Earth Model surfaces... –Time-Depth Conversion Given a pointset or grid in one domain return array of values in other domain Provides interoperability without exposing details of proprietary implementations

Conclusions Data Fusion is greatly enhanced by having easy accessible data and application integration. Basing this integration on a service oriented architecture allows flexibility in choice of solution components - today and over time. There are logical next steps that elevate the types of services provided to a higher level to enable more innovative workflows.

Thank you! 11