9
Technical Team Technical Team WITSML SIG WITSML SIG Paris 16 May 2007 Paris 16 May 2007

Technical Team WITSML SIG Paris 16 May 2007. Technical Team Representatives mainly from service companies Energistics (Gary) keep a global issue list

Embed Size (px)

Citation preview

Page 1: Technical Team WITSML SIG Paris 16 May 2007. Technical Team Representatives mainly from service companies Energistics (Gary) keep a global issue list

Technical TeamTechnical Team

WITSML SIGWITSML SIG

Paris 16 May 2007Paris 16 May 2007

Page 2: Technical Team WITSML SIG Paris 16 May 2007. Technical Team Representatives mainly from service companies Energistics (Gary) keep a global issue list

Technical TeamTechnical Team

Representatives mainly from service Representatives mainly from service companiescompanies

Energistics (Gary) keep a global issue listEnergistics (Gary) keep a global issue list

Monthly conference callsMonthly conference calls

6-monthly face-to-face meetings6-monthly face-to-face meetings

Page 3: Technical Team WITSML SIG Paris 16 May 2007. Technical Team Representatives mainly from service companies Energistics (Gary) keep a global issue list

Technical TeamTechnical TeamExtended Queries & Log PassExtended Queries & Log Pass

Extended QueriesExtended Queries Current WITSML queries are for exact match to a query templateCurrent WITSML queries are for exact match to a query template

<name>123-45/36</name><name>123-45/36</name><depth uom=‘m’>123.45</name><depth uom=‘m’>123.45</name>

Need to be able to use wild card match for strings or > < for numeric & datetime valuesNeed to be able to use wild card match for strings or > < for numeric & datetime values WITSML 1.1 defined an extended query syntax for alpha and numeric itemsWITSML 1.1 defined an extended query syntax for alpha and numeric items

<name>SEL(“123*”)</name><name>SEL(“123*”)</name><md>SEL(>123.4)</md><md>SEL(>123.4)</md>

This was not considered a part of the standard and not uniformly adoptedThis was not considered a part of the standard and not uniformly adopted PRODML is also looking into similar capabilitiesPRODML is also looking into similar capabilities Want to be able to use an appropriate industry standard if appropriateWant to be able to use an appropriate industry standard if appropriate SQL, XMLQuery etc.SQL, XMLQuery etc. WITSML and PRODML will work to a common solutionWITSML and PRODML will work to a common solution

Log Pass/TripLog Pass/Trip Issue is to be able to properly organize data from multiple passes through the same Issue is to be able to properly organize data from multiple passes through the same

formationformation WITSML log object does not currently provide enough information to define the number and WITSML log object does not currently provide enough information to define the number and

type of passes through a depth sectiontype of passes through a depth section Proposed to add pass number and passType to log and wellLog objects in future version Proposed to add pass number and passType to log and wellLog objects in future version

(probably 1.4)(probably 1.4)

Page 4: Technical Team WITSML SIG Paris 16 May 2007. Technical Team Representatives mainly from service companies Energistics (Gary) keep a global issue list

Technical Team – WITS DataTechnical Team – WITS Data

WITS Data in Realtime?WITS Data in Realtime? Need to ba able to provide an easy upgrade path for current Need to ba able to provide an easy upgrade path for current

providers of WITS level 0 dataproviders of WITS level 0 data Use HTTP POST instead of custom socket connectionsUse HTTP POST instead of custom socket connections Use WITSML log objectUse WITSML log object Define some standard configurations of log objects based on Define some standard configurations of log objects based on

WITS with the following changesWITS with the following changes WITS survey, geology, drill string, casing, survey, operations WITS survey, geology, drill string, casing, survey, operations

records replaced by WITSML mudLog, tubular, records replaced by WITSML mudLog, tubular, wellboreGeometry, trajectory and opsReportrecordswellboreGeometry, trajectory and opsReportrecords

WITS log objects replace most of the sequential recordsWITS log objects replace most of the sequential records Need to re-define the LWD records to account for different Need to re-define the LWD records to account for different

sensor at different depthssensor at different depths Also need to accommodate image data for LWD dataAlso need to accommodate image data for LWD data

Page 5: Technical Team WITSML SIG Paris 16 May 2007. Technical Team Representatives mainly from service companies Energistics (Gary) keep a global issue list

Technical Team – Time ZonesTechnical Team – Time Zones

Timezone issues Timezone issues How to handle date/time information as it passes from initial provider through one How to handle date/time information as it passes from initial provider through one

or more aggregation servers to end user applications?or more aggregation servers to end user applications? Normally want to see data in time zone of original well site e.g. for relating to Normally want to see data in time zone of original well site e.g. for relating to

daily reporting intervalsdaily reporting intervals Well object includes a time zone for the rigWell object includes a time zone for the rig Recommend always including time zone offset in any time stampsRecommend always including time zone offset in any time stamps

2007-05-16T09:16:36+06:002007-05-16T09:16:36+06:00 If offset is not specified, assume rig time.If offset is not specified, assume rig time. Issues under discussionIssues under discussion

What happens if we change time zone during a log?What happens if we change time zone during a log?How to handle clock changes when we know that LWD tools often run across daylight How to handle clock changes when we know that LWD tools often run across daylight time zone changes?time zone changes?

Page 6: Technical Team WITSML SIG Paris 16 May 2007. Technical Team Representatives mainly from service companies Energistics (Gary) keep a global issue list

Technical TeamTechnical TeamUse Case ProfilesUse Case Profiles

Need to stay SOA, web services compliantNeed to stay SOA, web services compliant Must be XML schema compliant in all web service Must be XML schema compliant in all web service

requestsrequests Need to have at least 4 schemas per objectNeed to have at least 4 schemas per object

Normative schema – all elements are optionalNormative schema – all elements are optionalAddToStore schema – defines basic required set of dataAddToStore schema – defines basic required set of dataQuery schemaQuery schemaReturned object schemaReturned object schema

Total ProposalsTotal Proposals GeodeticsGeodetics Wellbore Positioning UncertaintyWellbore Positioning Uncertainty Both priority for v1.4Both priority for v1.4

Page 7: Technical Team WITSML SIG Paris 16 May 2007. Technical Team Representatives mainly from service companies Energistics (Gary) keep a global issue list

Technical Team – Other IssuesTechnical Team – Other Issues

Lithology QualifiersLithology Qualifiers Can apply to a depth interval or at a single depthCan apply to a depth interval or at a single depth Some qualifiers occur at a point, some over a rangeSome qualifiers occur at a point, some over a range

Comma delimitersComma delimiters Short term – remove commasShort term – remove commas Longer term specify an encoding techniqueLonger term specify an encoding technique

Embedded ObjectsEmbedded Objects Intellifield implemented attachment object with a reference back to original data Intellifield implemented attachment object with a reference back to original data

object w/ base64 encoding and file typeobject w/ base64 encoding and file type Similar object reference to message objectSimilar object reference to message object Can handle multiple attachments to the same objectCan handle multiple attachments to the same object Needed for state regulatory dataNeeded for state regulatory data

WMLS prefixWMLS prefix WMLS_DeleteFromStore is bigger than 16 charsWMLS_DeleteFromStore is bigger than 16 chars Work-around – ignore 16 char limitationWork-around – ignore 16 char limitation Different implementationsDifferent implementations Bug fix: go with WMLS_XXX and increase string size to 64Bug fix: go with WMLS_XXX and increase string size to 64

Page 8: Technical Team WITSML SIG Paris 16 May 2007. Technical Team Representatives mainly from service companies Energistics (Gary) keep a global issue list

Technical Team – Other IssuesTechnical Team – Other Issues

Change LogChange Log Should objectType and dTimLastChanged be mandatory?Should objectType and dTimLastChanged be mandatory? Same as discussed earlier. Mandatory for AddToStore use case, Same as discussed earlier. Mandatory for AddToStore use case,

optional for query or returned value.optional for query or returned value.

Error messages from WITSML serversError messages from WITSML servers Add a new error code for permission denied for a SOAP Add a new error code for permission denied for a SOAP

operationoperation Implement as suggested – error code 206Implement as suggested – error code 206 Do we need a new method GetPermissions?Do we need a new method GetPermissions?

How to detect changes in realtime dataHow to detect changes in realtime data Add new element dTimHeaderLastChanged to realtime object. Add new element dTimHeaderLastChanged to realtime object.

YesYes New use case for when a log structure changes in real timeNew use case for when a log structure changes in real time

Need to query server to find the current growing logsNeed to query server to find the current growing logs

Page 9: Technical Team WITSML SIG Paris 16 May 2007. Technical Team Representatives mainly from service companies Energistics (Gary) keep a global issue list

Technical TeamTechnical Team

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

Questions?Questions?