Integrated Operations SIG: Distributed Temperature Survey Data Transfer Standard: Update Houston 12 May 2006 Paul Maton and John Bobbitt (POSC)

Overview Introduction Summary of the technology Early applications, emerging requirements of DTS in E&P Business drivers for DTS in E&P SIG formation and activities Current status and plans

DTS proprietary data format Well/Wellbore Backscatter to Temperature converter Near-real Time Data Server / RTU / … Vendor Datastore Vendor Applications Proprietary Datastore Proprietary Applications Partner(s) Wellsite Operations Centre and/or Offices WITSML standard data format Overview: DTS Data Diagram Vendor Datastore Vendor Applications Proprietary Datastore Proprietary Applications Operator Wellhead Optical fiber carrying transmitted and backscattered light WITSML adaptor Laser DTS Box SupplierOpen Standard Client

Backscatter spectrum Stokes component Temperature independent Raman bands Wavelength Intensity Brillouin bands Rayleigh component equal to incident wavelength Anti-Stokes component Strongly temperature dependent Temperature = f(( I +/ I -) +…) I-I- I+

Why establish a standard? Manufacturers Enabler for greater industry use of DTS Possible applicability in other industries Service companies Avoids the requirement for customization for each client Enabler for greater industry use of DTS Operators Consistent access to data from different service companies Earlier availability of DTS data

June ‘04 Proposal Collaborative design and development of DTS data transmission and exchange standard between DTS manufactures and suppliers and operators Leverage WITSML architecture, infrastructure (API) and process (SIG) Evolution and maintenance of public domain standard through POSC Transfer functionality, applications, and storage of information are out of scope

Deliverables Definition of data content requirements Standard vocabulary and thesaurus of vendor specific terminology to standard Analysis of the usability of the candidate technologies (XML, WITSML, OPC) Was released as part of WITSML v1.3.1 –includes schema, stylesheet, sample DTS data, and documentation

DTS Group formation BP sponsor Richmond meeting (March ’04) –Attendees: BP, Shell, Baker Hughes, Halliburton, POSC, Polarmetrix, Schlumberger, Sensornet, Wood Group POSC publish project proposal (June ‘04) Participation established (Sept ’04) –Active: BP, Shell, Halliburton, Schlumberger, Sensornet –Funding (17) and monitoring (3): POSC members of IntOPS SIG

DTS Group Activities Teleconferences (~4) –Reviewed scope, raised issues (IP, data content, flexibility, XML or OPC?, etc.), enumerated reference information, etc Workgroups at Shell, London (2) –Refined and reviewed requirements, scoping, issues, received submissions, reviewed initial draft specification Support work by POSC staff –Documenting and analysing requirements –Revised XML schemas and documentation –Preparation of materials for reviews and subsequent revisions

Resources BP / Baker initial DTS schema Shell DTS Primer Service company publications and data WITSML specifications – particularly alignment with WITSML 1.3

Issues - 1 XML and/or OPC? –DTS Group reviewed status of OPC migration from COM to XML –Selected XML development leveraging BP/BHI and WITSML assets Reuse of WITSML assets –Leverage data objects such as Well, Wellbore and wellLog in addition to architecture and data types Flexibility and Extensibility –DTS is a young and evolving technology –Standard must not constrain innovation

Issues - 2 Bandwidth constraints –Between wellhead / control center / office –Any of three levels of bandwidth are common in the oilfield: Low: 9600 baud RTU connection Low to medium: 64kB to 100MB High: in the order of GBytes/sec –Need to design for minimal verbosity of XML messages Data transmission functionalities –Batch and near real-time data access –Network integrity and quality of service monitoring –Deferred, but future implementations may use WITSML Server capabilities

Requirements - 1 System installation data –Well and wellbore contextual data –Fiber and ‘DTS box’ contextual data –Permanent and temporary installations –Various fiber installation patterns –Interchange of equipment Calibration of DTS system and data to wellbore –Determining position of DTS measurements along fiber and in wellbore –Calibrations used to convert Stokes/Anti-Stokes intensity ratio to temperature and apply other corrections OTDR (Optical Time Domain Reflectometry): –self-checking fiber and system functionality

Requirements – 2 DTS data types –Stokes, anti-Stokes, OTDR, raw Temperature, calibrated Temperature –Routine ability to select all or some of the above Flexible DTS Message Content –Enable selection of calibration, context and temperature types for particular purposes –Need to satisfy transfers between wellsite to office, office to wellsite, and office to office

(DTS) Fiber configuration patterns Single straight fiber Single straight fiber plus independent sensor Partially returned fiber or ‘J’ Fully returned fiber or ‘U’ Wellhead level

DTS Data Model dtsInstalledSystem id, dTim, …. instrumentBox Information mfr, serial#, dTim… dtsCalibration (Name, value) pairs OTDR 0..n*[ Rayleigh] fiber mfr, serial#, … fiberInformation length, mD, dTim… wellbore nameWellbore, … well nameWell, field … instrumentBox mfr, serial#, dTim… wellboreFiber Schematic lAF,mD, type wellLog lAF, Stokes, antiStokes, tRaw, tCal dtsIMeasurement id, dTim, ….

DTS Features: 1 Flexibility – allow evolution of technology –fiber and instrumentBox are independent of E&P application –location in wellbore in terms of lengthAlongFiber and measuredDepth with reference points such as baseTubingHangerFlange –WITSML:WellLog used to transfer temperature and fiber self-test (OTDR) profiles

DTS Features: 2 Re-using WITSML schemas and architecture –Well, wellbore objects –Log with flexible table structure –Many data types, and elements –Composite schema to enable use independently of WITSML server Adding DTS specific sub-schemas and elements

DTS Features: 3 Documentation Package –Addresses 3 audiences: Petroleum Engineers and Geoscientist end-users, Data Managers, Software Engineers –XML Schemas and Style sheets –Sample XML –Shell DTS Primer

fiber.xml <!-- Standalone description of a fiber Note that this is an example only, and may not actually exist --> Example Fiber One 50/125 multimode gold hytrel AA Corning

dtsMeasurement 1FO19 1FO19-1 Wellbore 1FO19-1 measurement 8Oct Hole 1FO19-1 installation 1 Wellbore 1FO19-1 measurement 8Oct2005 C wellhead junction box

Calibration data DT001 DTS Company X T20:12:15 length YYYY true … DTS Company X internal 1.1 … Calibration data are described in self-defining structures

Temperature curve information LAF length along fiber m length along the fiber, with zero point where the fiber emerges from the instrument box. TEMP DTS temperature degC Calculated temperature value, after corrections. ST Stokes intensity Summed value of the stokes frequency AST anti-Stokes intensity Summed value of the anti-stokes frequency

Temperature Data in wellLog format … 8.776,27.51, , ,27.005, , ,26.505, , ,25.102, , ,24.529, , ,24.295, , ,24.322, , ,24.304, , ,24.358, , ,24.332, , ,24.307, , ,24.076, , ,23.936, ,

Current Status Published as integrated part of WITSML v1.3.1 First non-drilling member of WITSML family of standards Promote and support implementation(s) in Use feedback from implementations to iterate on specification as needed in 2006

POSC DTS Standards in Shell Martijn Hooijmeijer Linda Dodge

Why Shell Contributes Fits into Shell Data Architecture Standards Data handling and processing independent of DTS hardware vendors allows global standards, reduces interfaces Standard interfaces facilitate usage of best in class visualisation, interpretation and monitoring tools POSC DTS Standards in Shell

What Shell has contributed Shell DTS Primer (a foundational document for the WITSML DTS definition) Integration expertise DTS Expertise Stimulating vendors to implement and comply with WITSML DTS POSC DTS Standards in Shell

Office Domain Distributed Data DB XML ? XML (?) Client Software Envisioned DTS Architecture POSC DTS Standards in Shell Process Control Domain Storage required for 72 hours Data to be sent in POSC DTS ML Exchange format. Temporary Storage DTS Hardware XML / OPC Transfer raw data: (unscaled) Stokes / anti-Stokes data Transfer temperature traces Transfer other distributed data Flexible header that may include parameters relating to Light box, Fiber, and Well details. Transfer installation / hardware configuration (either as an “extended” header of regular message, or as separate message, with preference for the prior).

Shell’s plans A DTS data handling architecture has been designed around the WITSML DTS, including Oracle DTS Database First application using WITSML DTS due to be up and running in Q4 this year: will probably generate change requests Continue working with all our DTS vendors to have their devices export WITSML DTS POSC DTS Standards in Shell

BP: dts summary Initiated external collaboration amongst DTS service providers and operator community to establish industry standard data format. Active participation in Integrated Operations SIG to develop data specification requirements based on experience from prototype XML schema developed by BP. Proven the application of DTS data transmission via XML through a BP developed schema prototype. This prototype was implemented as an interim solution prior to the release of the industry standard format. We are committed to the development and application of an industry standard that will be held by POSC.

Conclusions Business case exists for DTS data transfer standard: with benefits to Operators, Service Companies and DTS system manufacturers Clear, focussed objectives and community of interest established Requirements, Issues and Resources collected, analysed, draft schemas and documentation reviewed by DTS Workgroup, WITSML technical team and Industry Published as first non-drilling extension of WITSML family of standards in Jan Operational implementation(s) planned and proceeding

More information from Paul Maton Tel: John Bobbitt Tel: