Technical Team WITSML SIG Houston 15 May 2008 John Shields / Gary Masters.

Slides:



Advertisements
Similar presentations
Proposed update of Technical Guidance for INSPIRE Download services based on SOS Matthes Rieke, Dr. Albert Remke (m.rieke, 52°North.
Advertisements

SPE WITSML: Technology to Business (T2B) for the Oilfield J
Completion Object Overview June 2013 WITSML/PRODML Standards.
Evolution 1. WITSML Life Cycle Timeline Years Version 1.0 Version 1.1 Version 1.2 Version
WITSML Office Aggregrator
Modern app development Continuous value delivery and rapid response to change.
Employee Central Presentation
Global Real Time More Efficiency. More Possibilities and.
Overview 1. 2 WITSML Special Interest Group Members A set of Data Exchange and Web Services Standards First published in 2001 Version 1.4 due in Q3 50+
1 General Well Message Operations Report Real Time Wellbore Wellbore Geometry Risk Directional Drilling Systems Tubular / Bit Record BHA Run Fluids Systems.
Best Cost-Effective Technology Independent and Neutral Company 24/7 Worldwide Technical Support MARCH 2011 TECHNICAL UPDATE The independent.
3rd Annual Energistics Standards Summit Standards – Benefits across Industries Michael Strathman Aspen Technology, Inc 23 October 2008.
Speaker Introduction John Shields Software Projects Manager, Baker Hughes, Aberdeen 30 years working for Baker Hughes 30 years working for Baker Hughes.
© 2009 IBM Corporation 1 RTC ClearQuest Importer and Synchronizer Lorelei Ngooi – RTC ClearQuest Synchronizer Lead.
Form Builder Iteration 2 User Acceptance Testing (UAT) Denise Warzel Semantic Infrastructure Operations Team Presented to caDSR Curation Team March.
1 © 2007 Cisco Systems, Inc. All rights reserved. Cisco ConfidentialSTC Global Impact Review Multi-ReOrg: Cisco's Innovation in Changing it’s Selling Company.
Schlumberger Update Nigel Deeks Real Time Technology Manager
PRODML Review Energistics Western Europe London, 31 May 2011.
SPE Wellsite Information Transfer Standard Markup Language, WITSML, an Update M.A Kirkman, SPE, BP; M.E. Symmonds, SPE, Schlumberger; S.W. Harbinson,
Geophysics SIG Work Meetings Houston, 12 March 2009 Web Conference, 26 March 2009.
Proposal for App Id and Service Provider Id registration Group Name: Shelby Kiewel Source: Shelby Kiewel, iconectiv / Ericsson,
SNIA/SSIF KMIP Interoperability Proposal. What is the proposal? Host a KMIP interoperability program which includes: – Publishing a set of interoperability.
Wellsite Information Transfer Standard Markup Language, WITSML, an Introduction Alan Doniger, POSC November 2004.
Technical Team WITSML SIG Paris 16 May Technical Team Representatives mainly from service companies Energistics (Gary) keep a global issue list.
INTEQ Answers While Drilling SM John Shields Director of Software Baker Atlas/INTEQ Houston, TX.
Welcome to corporate.eircom.ie This presentation aims to give you an overview of corporate.eircom.ie, what it offers you and how best to navigate your.
WITSML at the Wellsite.
AIXM Users’ Conference, March Implementing AIXM in Instrument Flight Procedures Automation Presenter: Iain Hammond MacDonald, Dettwiler &
WITSML – Realizing the Value John Shields Baker Hughes.
Copyright © 2004 by The Web Services Interoperability Organization (WS-I). All Rights Reserved 1 Interoperability: Ensuring the Success of Web Services.
Project Review POSC / WITSML Mudlog SIG - April 27, Agenda:
Promoting Web Services Interoperability Across Platforms, Applications and Programming Languages Basic Profile 1.0 August 12, 2003 Copyright © 2003 by.
MINT Working Group Jan 9-10 at Harris FBC Melbourne, FL.
Baker Hughes & WITSML John Shields Software Projects Manager Baker Hughes Aberdeen.
The Global Video Grid: DigitalWell Update & Plan For SRB Integration Myke Smith, Manager Streaming Media Technologies University of Washington / ResearchChannel.
Development Process and Testing Tools for Content Standards OASIS Symposium: The Meaning of Interoperability May 9, 2006 Simon Frechette, NIST.
Technical Team WITSML SIG Dubai - November 2008 John Shields / Gary Masters.
FIMS v1.1 Version numbers in schema Richard Cartwright Quantel July 2013.
WITSML Meeting Houston, May 15, 2008 WITSML end to end implementation: Results and way forwards at Total Raphael Henri-Bally, Total Geosciences IT systems.
Energistics Asia South Region Meeting: (Drilling) WITSML SIG Update New Delhi, IndiaAlan Doniger 14 January 2007Chief Technology Officer Le M▲ridien New.
© 2005 Baker Hughes Incorporated All rights reserved. Improving work processes with WITSML John Shields Software Projects Manager Baker Hughes.
Agenda Introduction Energistics Standards Panorama / History / Participants Web Services Interoperability Standards v1.0 WITSML Version 1.x Services /
WITSML Public Seminar and Vendor Exhibition: Welcome Alan Doniger, Energistics CTO May 28, 2009.
WellPath Progress Report: Re-spudded and drilling ahead John Turvill and Paul Maton WITSML SIG, Houston TX, 9 – 11 May 2006 POSC Regional SIG, Stavanger,
Proposal for App Id and Service Provider Id registration Group Name: Shelby Source: Shelby, iconectiv / Ericsson,
Welcome to the WITSML Public Seminar and Vendor Exhibition Paris, France 16 May 2007 Sponsored by Total.
Geophysical SIG Towards reduced cycle time In Geophysical Work Processes.
WITSML™ Drilling Standards Pemex 21 August 2008 Ciudad de México Alan Doniger, Energistics.
© 2006 Petrolink International WITSML Conference 19/10/06 WITSML Developments Steven Johnstone Data Management Starts At The Point Of Acquisition.
WITSML Technical Team Update Houston May Technical Team Responsible for technical content of WITSML standard XML Schemas XML Schemas Application.
Samit Sengupta Geologix Ltd.
Registration Solutions for your Event Management.
Gold – Crystal Reports Introductory Course Cortex User Group Meeting New Orleans – 2011.
Service Component Architecture (SCA) Policy TC … Face to Face Agenda – Jan 24,
Baker Hughes & WITSML WITSML Conference – Houston, May 2005
© 2007 Petrolink International WITSML vs WITS – at the Wellsite 16 th May, 2007.
ISA 95 Working Group Process Centric Exchanges Gavan W Hood July 23, 2015 GWH 2.1.
Rich Internet Applications: Better Practices for Financial Services Stephen Turbek, Avenue A | Razorfish.
1 Future Consideration for WITSML from Total Products should migrate to the same version of WITSML Need provisions for backup in case of system failure.
WITSML Technical Team Aberdeen, Oct Technical Team Organization Representatives from service companies Monthly conference calls 2 day session at.
PIX/PDQ – Today and Tomorrow Vassil Peytchev Epic.
16 May 2006IVOA Interoperability – Registries WG1 VOResource Schema v1.0 Release 6 Ray Plante NCSA T HE I NTERNATIONAL V IRTUAL O BSERVATORY A LLIANCE.
GDSN Mandatory Attributes -- Simplified 3 December 2008.
6/13/2016 U.S. Environmental Protection Agency 1 Starting a Facilities Flow Lee David
WITSML direction in BP SIG Public Meeting – May 2006 Dr Julian Pickering Domain Lead, Drilling & Completions.
Project Objectives Publish to a remote server
Mudlog Object - Pilot Samit Sengupta.
Julian Pickering, Domain Lead Drilling & Completions
Health Ingenuity Exchange - HingX
AES The Alliance's name for the proposal is OCA 1.4.
Presentation transcript:

Technical Team WITSML SIG Houston 15 May 2008 John Shields / Gary Masters

WITSML Technical Team Representatives mainly from service companies Energistics (Gary) keeps a global issue list accessible via private area on Energistics web site Monthly conference calls Twice a year face-to-face meetings at WITSML SIG working meetings

WITSML Issues List

Automation - Standard Logs & WITS Migration Lack of standardization of log/curve names on WITSML servers How to identify curves of similar types e.g Gamma Ray from different vendors? Identify common data sets across WITSML servers Accommodate legacy data from WITS data streams

Log Curve issues Curve mnemonic –classWitsml Link to units class Needs some clean up –Service company mnemonic – use element Data group element (WITS record) e.g. ‘DRILLDEPTH’ Service group (mudlogging, LWD, wireline, cementing, rig contractor) PWLS classification (multiple attributes) –Processing, depth of investigation etc. –Add these items to logCurveInfo –Need to keep PWLS up to date Service companies can add extra curves to standard data groups LWD image data is service company proprietary until standards emerge How to splice runs & passes (sections)? Handling of real-time & memory data

Standard WITS style data sets General Time ‑ Based Drilling Depth ‑ Based Drilling Connections Hydraulics Tripping Time ‑ Based Tripping Connections LWD (time based) w/bit depth curve & sensor offset LWD (depth based) w/data at measured depth LWD Mechanical Pressure Evaluation Mud Tank Volumes Chromatograph Gases: Cycle ‑ Based Chromatograph Gases: Depth ‑ Based Lagged Continuous Mud Properties Cementing Well Testing Vessel Motion / Mooring Status Weather / Sea State

Performance Exchange of issues with Use Case Team High volume data –Seismic (SEGY), Wireline, Wired pipe, LWD memory data Compression –Use standard technology (GZIP), Include in 1.4 –Available in HTTP and.NET etc. Metrics & Certification –Aim is 5 seconds from real time –Difficult to know where the time delays are. Need to measure from client and server –Proposal to add custom data object to convey speed for processing data within WITSML server. Could add to documentInfo AuditTrail Data resampling & filtering –Filter at server. Resampling, filtering or arithmetic. Resample rather than filter –Can use to reduce bandwidth –End user apps may require evenly sampled data Download limits –Clients need to cope with incomplete data sets –Servers can indicate max data size

Automation - WITSML API Discussions SOAP API and alternatives RPC Encoding issues - industry changing to WS-I Current query complexity using WITSML Object templates Specific vs generic technology Do we need to align with PRODML API? Proposal for ‘WITSML Express’ with a simpler web service to assist early adopters Continue to work with use case team Standard queries and server profiles can enable certification of profiles

Resolved Issues – Make nameWellbore optional in attachment – Fix delta-length and water depth elements by changing type to length – Add CRS object but keep (deprecate) the old geodetic definitions Add qualifierForm element to capture whether a qualifier represents a “noun” or “adjective” – Recurring element identification – Automation use case: handle repeated items e.g. multiple gamma or pit volumes

Resolved Issues – Add object in a way that does not impact.NET – Add compression- method (gzip) options-in for Add, Get, Update. Add compression- direction – Only top level object (e.g. well) has a globally unique uid – Server validation of data. Suggest researching Schematron – Make the uom attribute mandatory in genericMeasure Rename uom types. Cleanup documentInfo schema and add event type

New Issues this meeting 1.Clarify scope of transform between versions 2.Attachment on well 3.Realtime dTim selection 4.Server profile name in capabilities 5.Options-in for client identifier 6.Log query response based on stepIncrement 7.Use server Capabilities for max return data size 8.Depth correction 9.More detail on Automation use case

Technical Team If you want to contribute – join the SIG!

Thank you