1 / 14

WITSML Use Cases

WITSML Use Cases. Calgary Workshop April 2004. Use Cases / Practical Implementations of WITSML. Where are we now ? Different drivers in different Operators In BP, still mainly driven by LWD data applications

lester
Télécharger la présentation

WITSML Use Cases

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WITSML Use Cases Calgary Workshop April 2004

  2. Use Cases / Practical Implementations of WITSML • Where are we now ? • Different drivers in different Operators • In BP, still mainly driven by LWD data applications • About to pilot real time Torque and Drag applications (Available from service contractors for some years) but in an application independently of data acquisition contractors • Geographically in use in Norway, UK, Trinidad and Azerbaijan • Still need to get contextual data flows up and running. Push into new areas ?

  3. “Real Time” • A successful, but limited implementation, focussed around LWD data, that does not change the principle of the way WITS data was used • The challenge is to deepen the useage to include the static contextual data, far easier to handle with WITSML than was the case with WITS. • Where do we want to be ? Instigating technical changes that will make the flow of data more automated, saving cost through removing duplication of data entry.

  4. BP interest in applications of WITSML • Operator to Government • Service Contractor to Service Contractor • Drilling Contractor to Operator • Service Contractor to Operator  • Operator to Operator  • Application to Application

  5. Operator to Government • Operator to Government  • Example: Filing of statutory documents relating to the well permitting process. • PON 9 etc. • Action – Work closely with DTI and other operators (MMS, NPD … ) in piloting a project.

  6. Service Contractor to Service Contractor  • Service Contractor to Service Contractor  • Example: Sharing a BHA description at the rig between different service vendors • Action : Select project to pilot workflow on.

  7. Drilling Contractor to Operator • Example: Automation of transfer of electronic IADC report data. • Action: Engage custodians of IADC electronic report • Select data objects. • This is going to take effort and a strong case to reach implementation • Continue to build a dialog with IADC and their applications community • Select pilot where short term value can be demonstrated

  8. Service Contractor to Operator  • Examples ; • WellpathML, • Geological data (Lith and text descriptions, contextual data, in addition to time based data) from Mud Logging company into Wellsite composite log package. • Wellsite composite log package into corporate data store • Action: Pilot workflow in real environment.

  9. Operator to Operator • Example: Daily drilling report object, ideally with contextual engineering data of value. • Action: • Agree scope and location of pilot

  10. Application to Application • Application to Application  • Example: Migrating data from one application’s proprietary data format to another, using the WITSML API as the mapping tool. • Action: Identify object and project • Completion diagrams ?

  11. Wednesday meeting • Commercial drivers for deeper implementation • Drilling reports • Engagement w IADC & CAODC for Drilling Contractor to Operator • Operator to Operator • Service Contractors reports, DD, LWD, Mud Log, Fluids • Drilling Contractor to Svc Contractor • Regulatory reporting • Well Schematic & Completions • Well Planning / WellPath ML • Production data and DTS • Mud Log data • Extending WITSML to Database to Database transfer ?

  12. Actions from wednesday • Consolidate known industry public domain lithology dictionaries, in addition to Shell Operations Geology handbook, offered by Shell • Supply to group relevant bibliography material where available • Circulate enhanced PIDX nomenclature for completion components, to work toward a standard catalogue Noun, Verb, Modifiers, but keep intelligible eg Pump, Centrifugal, Electrical (ESP). Info from PIDX and ChevTex, others welcome

  13. Process issues • Formalise processes for version release approval • Pilot a process to flow a suggested change into acceptance, using the changes needed to move WellPath ML into an integral part of WITSML • Restate use cases as “Business Problem / Solution” statements • Formalise a list of non technical issues on a bulletin board for members • Slightly more formalise communications between steering committee, Tech teams and Use Cases

  14. Co-operate ! • BP keen to adjust our priorities for work with the WITSML community to foster co-operation • Keen to see projects driven from bottom up, not top down

More Related