WITSML Technical Team Update Houston May 2006

1
WITSMLTechnical Team UpdateHouston May 2006
2
Technical Team

• Responsible for technical content of WITSML
  standard
• XML Schemas
• Application Programming Interface (API)
• Interpretation of API usage issues
• Interface with Use Case Implementation teams

3
Technical Team Process

• Yahoo Group for posting issues
• WITSML.org site for internal documentation
  maintained by POSC
• Monthly conference calls
• 2 days of meetings twice a year

4
WITSML Issue List
5
Issues Discussed

• MudLog object issues
• Create a volume per volume measure that only has
  for lithPC
• Sum of lithPCs should be 100 - add
  undifferentiated item
• Abundance code need to define a list
• Md top and bottom for qualifiers should be within
  geology interval
• Interp. Lithology qualifiers has both qualifiers
  (silty) and modifiers (fossil) needs more offline
  discussion.
• Units of measurement
• Units of measure magnetic flux density for survey
  corrections
• Remove gigaradians to avoid confusion with Grad
• Review query behavior for growing objects
• Documentation to be updated
• Errors in schema files
• Problem with validating individual xsd file due
  to missing include file. Needs to be fixed in the
  schema

6
Issues Discussed

• Well log depth registration schemas
• Add one new element to log and well log to define
  scaling adjustment
• Also add geopolitical location
• Performance of v1.2 to v1.3 transform
• 1.2 to 1.3 transform performance. SDC using it
  but its slow.
• Unique mnemonics
• Are mnemonics unique in realtime and log objects?
  
• Important issue for identifying log curves and
  realtime channels

7
Issues Discussed

• Coordinate Reference System
• WellCRS proposal to create a separate CRS
  object independent of well. Recommend use GML
  existing standard or a cut-down version
• Run numbers
• How to find active run number (e.g for logs or
  BHAs in a wellbore)?
• Different run numbers for bit, BHA, LWD, wireline
• How to find logs in a hole section?
• Query wbGeometry then depth range in a wellbore
• May not catch just the logs in the latest hole
  size section

8
Issues Discussed

• Active wells wellbores and current objects
• statusWellbore should be populated and updated or
  not present or used while drilling if it is not
  going to be kept up to date.
• How to find most recent instance of anything?
• How do we know when an activity stops?
• Could use a realtime object to carry current
  information for various objects
• Delete method for realtime.
• WITSML API only allows delete of whole objects so
  can not delete a channel from realtime
• Discussed special behavior to avoid putting uids
  in realtime and channel

9
Issues Discussed

• Embedded objects in WITSML
• XML attachments to SOAP?
• Needs further review by Use Case team
• How to identify when objects are created and
  updated
• Works fine for non-growing objects
• Need to define when existing objects are
  modified.
• Randomly growing objects are a problem mudLog
  may have sub-objects out of sequence
• Trajectory can query the dTim on stations to
  detect new additions or edits
• Stations transmitted via WITS may not have time
  stamp. Server needs to populate time stamp
• Use standard naming technique for start end
  depths and times in all objects

10
Next Steps

• If you want to contribute to WITSML
• Meet interesting people
• Travel to exotic locations
• Join the SIG!