1 / 6

WITSML Interoperability Challenges

WITSML Interoperability Challenges. John Shields Director of Software Baker Hughes, Houston. Engineering Support. Enterprise Systems. WellCAD. EWF. Baker Hughes Direct Corporate Data Store. BEACON Real-Time Operations Support Center Well Planning. Tool Data. SAP.

benoit
Download Presentation

WITSML Interoperability Challenges

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. WITSML Interoperability Challenges John Shields Director of Software Baker Hughes, Houston

  2. Engineering Support EnterpriseSystems WellCAD EWF Baker Hughes Direct Corporate Data Store BEACON Real-Time Operations Support Center Well Planning Tool Data SAP Data Flow – Job Startup Field Systems SiteCom Server Other Data Stores Offset Well Data Job Data

  3. Geoscience Clients 3rd Party Applications WellCAD Geoscience Data Store Realtime Transfer Realtime Data Baker Hughes Direct Corporate Data Store BEACON Real-Time Operations Support Center Well Planning Data Flow – Job Operations Field Systems WellLink Service SiteCom Server Other Data Stores

  4. Geoscience Clients 3rd Party Applications Reporting Applications Engineering Support EnterpriseSystems Geoscience Data Store Run/Report Data Job Reports Baker Hughes Direct Corporate Data Store BEACON Real-Time Operations Support Center Well Planning Tool Performance SAP Data Flow – Post Run/Job Field Systems Job Results WellLink Service SiteCom Server Other Data Stores

  5. WITSML Challenges & Solutions • In-house and 3rd party applications need to work seamlessly • Currently requires some manual data transfer via LAS, ASCII files or WITSML 1.2 • More applications becoming WITSML compliant • How to handle large data sets (wired pipe, wireline)? • Technical team identified technique for more efficient log updates and discussed handling of compressed/binary data • No easy way to identify similar data from different sources. Where is the Gamma ray curve for a wellbore section? • Proposal for definition of ‘standard’ WITSML logs • Different applications use different variations on the WITSML query templates leading to inconsistent behavior • Proposal for the definition of more specific API rather than query templates

  6. Questions?

More Related