Technical Team WITSML SIG Paris 16 May 2007

Technical Team Representatives mainly from service companies Energistics (Gary) keep a global issue list Monthly conference calls 6-monthly face-to-face meetings

Technical Team Extended Queries & Log Pass Extended Queries Current WITSML queries are for exact match to a query template Current WITSML queries are for exact match to a query template<name>123-45/36</name> Need 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 items WITSML 1.1 defined an extended query syntax for alpha and numeric items<name>SEL(“123*”)</name><md>SEL(>123.4)</md> This was not considered a part of the standard and not uniformly adopted This was not considered a part of the standard and not uniformly adopted PRODML is also looking into similar capabilities PRODML is also looking into similar capabilities Want to be able to use an appropriate industry standard if appropriate Want 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 solution WITSML and PRODML will work to a common solution Log Pass/Trip Issue is to be able to properly organize data from multiple passes through the same formation Issue is to be able to properly organize data from multiple passes through the same formation WITSML log object does not currently provide enough information to define the number and type of passes through a depth section WITSML log object does not currently provide enough information to define the number and type of passes through a depth section Proposed to add pass number and passType to log and wellLog objects in future version (probably 1.4) Proposed to add pass number and passType to log and wellLog objects in future version (probably 1.4)

Technical Team – WITS Data WITS Data in Realtime? Need to ba able to provide an easy upgrade path for current providers of WITS level 0 data Need to ba able to provide an easy upgrade path for current providers of WITS level 0 data Use HTTP POST instead of custom socket connections Use HTTP POST instead of custom socket connections Use WITSML log object Use WITSML log object Define some standard configurations of log objects based on WITS with the following changes Define some standard configurations of log objects based on WITS with the following changes WITS survey, geology, drill string, casing, survey, operations records replaced by WITSML mudLog, tubular, wellboreGeometry, trajectory and opsReportrecords WITS survey, geology, drill string, casing, survey, operations records replaced by WITSML mudLog, tubular, wellboreGeometry, trajectory and opsReportrecords WITS log objects replace most of the sequential records WITS log objects replace most of the sequential records Need to re-define the LWD records to account for different sensor at different depths Need to re-define the LWD records to account for different sensor at different depths Also need to accommodate image data for LWD data Also need to accommodate image data for LWD data

Technical Team – Time Zones Timezone issues How to handle date/time information as it passes from initial provider through one or more aggregation servers to end user applications? How to handle date/time information as it passes from initial provider through one 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 daily reporting intervals Normally want to see data in time zone of original well site e.g. for relating to daily reporting intervals Well object includes a time zone for the rig Well object includes a time zone for the rig Recommend always including time zone offset in any time stamps Recommend always including time zone offset in any time stamps T09:16:36+06:00 If offset is not specified, assume rig time. If offset is not specified, assume rig time. Issues under discussion Issues under discussion 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 time zone changes?

Technical Team Use Case Profiles Need to stay SOA, web services compliant Must be XML schema compliant in all web service requests Must be XML schema compliant in all web service requests Need to have at least 4 schemas per object Need to have at least 4 schemas per object Normative schema – all elements are optional AddToStore schema – defines basic required set of data Query schema Returned object schema Total Proposals Geodetics Geodetics Wellbore Positioning Uncertainty Wellbore Positioning Uncertainty Both priority for v1.4 Both priority for v1.4

Technical Team – Other Issues Lithology Qualifiers Can apply to a depth interval or at a single depth Can apply to a depth interval or at a single depth Some qualifiers occur at a point, some over a range Some qualifiers occur at a point, some over a range Comma delimiters Short term – remove commas Short term – remove commas Longer term specify an encoding technique Longer term specify an encoding technique Embedded Objects Intellifield implemented attachment object with a reference back to original data object w/ base64 encoding and file type Intellifield implemented attachment object with a reference back to original data object w/ base64 encoding and file type Similar object reference to message object Similar object reference to message object Can handle multiple attachments to the same object Can handle multiple attachments to the same object Needed for state regulatory data Needed for state regulatory data WMLS prefix WMLS_DeleteFromStore is bigger than 16 chars WMLS_DeleteFromStore is bigger than 16 chars Work-around – ignore 16 char limitation Work-around – ignore 16 char limitation Different implementations Different implementations Bug fix: go with WMLS_XXX and increase string size to 64 Bug fix: go with WMLS_XXX and increase string size to 64

Technical Team – Other Issues Change Log Should objectType and dTimLastChanged be mandatory? Should objectType and dTimLastChanged be mandatory? Same as discussed earlier. Mandatory for AddToStore use case, optional for query or returned value. Same as discussed earlier. Mandatory for AddToStore use case, optional for query or returned value. Error messages from WITSML servers Add a new error code for permission denied for a SOAP operation Add a new error code for permission denied for a SOAP operation Implement as suggested – error code 206 Implement 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 data Add new element dTimHeaderLastChanged to realtime object. Yes Add new element dTimHeaderLastChanged to realtime object. Yes New use case for when a log structure changes in real time New use case for when a log structure changes in real time Need to query server to find the current growing logs

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