WITSML Interoperability Challenges
description
Transcript of WITSML Interoperability Challenges
WITSML Interoperability Challenges
John ShieldsDirector of SoftwareBaker Hughes, Houston
2
BEACONReal-Time
Operations Support Center
Well Planning
Data Flow – Job Startup
Baker Hughes DirectCorporate Data Store
SiteCom ServerOther Data Stores
Field Systems
EngineeringSupport
EnterpriseSystems
SAP
EWF
Offset Well D
ata
Job Data
WellCAD
Tool Data
3
Clients3rd Party Applications
BEACONReal-Time
Operations Support Center
Well Planning
Data Flow – Job Operations
Baker Hughes DirectCorporate Data Store
WellLink ServiceSiteCom Server
Other Data Stores
Field Systems
Realtime Transfer
WellCAD
Realtime Data
Geoscience
GeoscienceData Store
4
Geoscience
GeoscienceData Store
Clients3rd Party Applications
BEACONReal-Time
Operations Support Center
Well Planning
Data Flow – Post Run/Job
Baker Hughes DirectCorporate Data Store
WellLink ServiceSiteCom Server
Other Data Stores
Field Systems
EngineeringSupport
Job ResultsRun/Report Data
ReportingApplications
EnterpriseSystems
SAP
Job Reports
Tool Performance
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?