1 / 29

Integrated Operations SIG: Distributed Temperature Survey

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

shalin
Download Presentation

Integrated Operations SIG: Distributed Temperature Survey

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. Integrated Operations SIG:Distributed Temperature Survey Data Transfer Standard: UpdateHouston 12 May 2006Paul Maton and John Bobbitt (POSC)

  2. 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

  3. Near-real TimeData Server /RTU / … Overview: DTS Data Diagram Supplier Open Standard Client Wellhead Operations Centreand/or Offices WITSML standarddata format DTS proprietary data format Vendor Applications Proprietary Applications Laser Vendor Datastore Proprietary Datastore Backscatter to Temperature converter Partner(s) WITSML adaptor Proprietary Applications Vendor Applications DTS Box Wellsite Vendor Datastore Proprietary Datastore Optical fiber carrying transmittedand backscattered light Well/Wellbore Operator

  4. Backscatter spectrum Temperature = f((I+/I-) +…) Rayleigh componentequal to incident wavelength Intensity Anti-Stokescomponent Stronglytemperature dependent Stokescomponent Temperature independent Brillouin bands I- I+ Wavelength Raman bands

  5. 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

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

  7. 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

  8. 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

  9. 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

  10. 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

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

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

  13. 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

  14. 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

  15. 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

  16. fiber.xml <?xml version="1.0" encoding="UTF-8"?> <!-- Standalone description of a fiber Note that this is an example only, and may not actually exist --> <fiber id="fiberExample1" xmlns="http://www.witsml.org/dts" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.witsml.org/dts ../obj_dts.xsd"> <name>Example Fiber One</name> <type>50/125 multimode</type> <coating>gold</coating> <jacket>hytrel</jacket> <diameter uom="um">900</diameter> <refractiveIndex>1.4976</refractiveIndex> <oneWayLoss uom="dB/km">.18</oneWayLoss> <spoolNumberTag>12345AA4</spoolNumberTag> <spoolLength uom="m">10000</spoolLength> <manufacturingDate>1965-03-08</manufacturingDate> <manufacturer>Corning</manufacturer> </fiber>

  17. dtsMeasurement <dtsMeasurement uidWell="D88CA733F" uidWellbore="82996A3B" uid="1FO19-120050603-1"> <nameWell>1FO19</nameWell> <nameWellbore>1FO19-1</nameWellbore> <name>Wellbore 1FO19-1 measurement 8Oct2005</name> <runDuration uom="s">600</runDuration> <installedSystemUsed uidRef="1FO19-1-1">Hole 1FO19-1 installation 1</installedSystemUsed> <dataInWellLog uidRef="8CA290B22">Wellbore 1FO19-1 measurement 8Oct2005</dataInWellLog> <fiberEndConnected uidRef="A6">C-1</fiberEndConnected> <fiberDefinedPoint uid="I2"> <lengthAlongFiber uom="m">127</lengthAlongFiber> <type>wellhead junction box</type> </fiberDefinedPoint> </dtsMeasurement>

  18. Calibration data <wellLog uid="1FO19-dts1"> <name>DT001</name> <serviceCompany>DTS Company X</serviceCompany> <creationDate>2004-06-11T20:12:15</creationDate> <indexType>length</indexType> <logParam index="1" name="first parameter">YYYY</logParam> <logParam index="1" name="third parameter">true</logParam> <logParam index="1" name="fourth parameter">492.2</logParam> … <logParam index="1" name="eighth parameter" uom="db/km">0.269</logParam> <logParam index="1" name="tenth parameter" uom="degC">12.2</logParam> <logParam index="2" name="tenth parameter" uom="degC">13.3</logParam> <logParam index="1" name="calculation method">DTS Company X internal</logParam> <logParam index="1" name="calculation method version">1.1</logParam> … Calibration data are described in self-defining structures

  19. Temperature curve information <logCurveInfo uid="LAF"> <mnemonic>LAF</mnemonic> <classWitsml>length along fiber</classWitsml> <unit>m</unit> <curveDescription>length along the fiber, with zero point where the fiber emerges from the instrument box.</curveDescription> </logCurveInfo> <logCurveInfo uid="TEMP"> <mnemonic>TEMP</mnemonic> <classWitsml>DTS temperature</classWitsml> <unit>degC</unit> <curveDescription>Calculated temperature value, after corrections.</curveDescription> </logCurveInfo> <logCurveInfo uid="ST"> <mnemonic>ST</mnemonic> <classWitsml>Stokes intensity</classWitsml> <curveDescription>Summed value of the stokes frequency</curveDescription> </logCurveInfo> <logCurveInfo uid="AST"> <mnemonic>AST</mnemonic> <classWitsml>anti-Stokes intensity</classWitsml> <curveDescription>Summed value of the anti-stokes frequency</curveDescription> </logCurveInfo>

  20. Temperature Data in wellLog format </wellLog> … <logData> <data id="1">8.776,27.51,2469381.354,1901640.98</data> <data id="1">9.278,27.005,2320534.5,1782170.336</data> <data id="1">9.78,26.505,2192484.861,1679296.566</data> <data id="1">10.281,25.102,2122306.103,1613174.898</data> <data id="1">10.783,24.529,2094591.895,1587087.951</data> <data id="1">11.285,24.295,2085332.057,1578006.606</data> <data id="1">11.787,24.322,2082312.362,1575909.093</data> <data id="1">12.289,24.304,2082709.971,1576001.859</data> <data id="1">12.791,24.358,2082038.717,1575914.364</data> <data id="1">13.293,24.332,2077303.063,1572056.944</data> <data id="1">13.795,24.307,2066563.314,1563676.817</data> <data id="1">14.296,24.076,2053080.526,1551465.609</data> <data id="1">14.798,23.936,2039563.062,1540018.394</data> </logData> </wellLog>

  21. 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 2005 - 2006 • Use feedback from implementations to iterate on specification as needed in 2006

  22. POSC DTS Standards in Shell Martijn Hooijmeijer Linda Dodge

  23. 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

  24. 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

  25. Envisioned DTS Architecture Process Control Domain Storage required for 72 hours Data to be sent in POSC DTS ML Exchange format. DTS Hardware • 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). Temporary Storage XML / OPC Office Domain XML ? XML (?) Distributed Data DB Client Software POSC DTS Standards in Shell

  26. 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

  27. 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 .

  28. 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 2006. • Operational implementation(s) planned and proceeding

  29. More information from Paul Maton maton@posc.org Tel: +44 1932 828794 John Bobbitt bobbitt@posc.org Tel: +1 713 267 5174

More Related