WITSML UseCase Requirement Implementation Support

1
WITSML Use-Case RequirementImplementation
Support

• Julian Pickering
• David Johnson
• Lars Olav Grovik

2
Immediate Results

• Initial discussions (with other teams)
• V1.3.1 re-issued
• Resolution of critical bug issues
• Immediate release
• Other issues deferred to future release(s)

3
Issue List review

• Dialects of WITSML
• Varied server implementation
• RunNumber issue
• What has changed?
• StatusWellbore
• Detect New object
• Latest MD
• Automation Use Case

4
Profiles

• Statement of the data and behaviors needed to
  support the workflow.
• Minimum data
• Content
• Organization
• Units
• Interface
• Response times
• Data expectations
• Benefit
• Reduce the ambiguity of WITSML communications

2 eggs 1 cup milk ¾ cup flour ¼ tsp Salt Pinch
baking powder
350f for 35 min
5
RunNumber

• Proposed
• Additional sequence to allow run number WITSML
  sequence.
• TT implementation
• BHA run number Run number

6
Automation UCR Discover changes

• Problem - Need to be able to determine, through
  WITSML Queries, when an object has changed and
  which objects are Current. The extension is to
  be able to identify what changed. This includes
  both the contents of objects, and new objects
  appearing.
• Business value Successful Automation.
• - Figure out what need to do to remove manual
  intervention in the workflow.
• Reduce cost of the Workflow (by removing people
  from the loop).
• Reasons for failure in the past.
• - People listening to the pipe in the ground,
  dont have time to record what's going on.
• No consensus on support for parameters which
  enable this (such as dtLastchanged and ltgt queries
  for this param (instead of equals)
• Publish/subscribe has issues to implementation.
• Solution What does one look like
• Can run a query that returns what has changed
  (Objects, elements, attributes)
• Since a point in time (real world date/time)
• Since a specific Index ???
• Can run a query that returns what NEW objects
  (instances)
• Since a point in time (real world date/time)
• Since a specific Index ???

7
Other high-value considerations

• Resolution of data
• Filter, average, etc
• Rune, Samit
• Historical Changes (may be fixed above)
• How to determine holes are retro filled?
• Douwe, DJ, Ovind, Mark, Rune
• Error recovery and handling
• Detection and resolution of failures
• DJ, Lars, Mark, Ovind

8
Happy Halloween!