1 / 11

Data Fusion via SOA Middleware

Data Fusion via SOA Middleware. Clay Harter Lynn Babec OpenSpirit Corporation. Earth Model. $ Decisions. Data Fusion. Well. Seismic. Initial Interpretation. Potential Field. Rock and fluid measurements. Production Tests. People. Software. Science. Data Fusion - The Software Pieces.

tien
Download Presentation

Data Fusion via SOA Middleware

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Data Fusion via SOA Middleware Clay Harter Lynn Babec OpenSpirit Corporation

  2. Earth Model $ Decisions Data Fusion Well Seismic Initial Interpretation Potential Field Rock and fluid measurements Production Tests People Software Science

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

  4. Windows UNIX UNIX Software Integration Problems Applications can’t 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 • Applications don’t interoperate • No sharing of user interaction events • No sharing of data change events • Inconsistent user interface conventions • No coordination of displays

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

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

  7. “Live” Demo Paradigm GOCAD SIS Petrel ESRI ArcMap Perigon iPoint Google Earth OpenSpirit Runtime Data Access Event Notification Coordinate Unit Metadata Movie: 9:41 OpenWorks, GeoFrame, PPDM, Petra, ArcSDE

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

  9. 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

  10. 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.

  11. Thank you!clay.harter@openspirit.com 11

More Related