POSC Informal SIGs: Houston 13 May 2005 Paul Maton

1

Well Path Data Transfer Standard An Update

• POSC Informal SIGsHouston 13 May 2005Paul
  Maton

2
Presentation Outline Introduction Uses and
Requirements for WellPath data Prior Well Path
data formats Well Path data in WITSML
1.3Conclusions
3
Glossary

• WITSML the Wellsite Information Transfer
  Standard Mark-up Language
• Well - A well is a unique surface location from
  which wellbores are drilled into the Earth for
  the purpose of either (1) finding or producing
  underground resources or (2) providing services
  related to the production of underground
  resources.
• Wellbore - A wellbore is a unique, oriented path
  from the bottom of a drilled borehole to the
  surface of the Earth. The path must not overlap
  or cross itself.

4
Glossary - 2

• obj_trajectory the WITSML construct that
  contains contextual information about the
  trajectory and the trajectoryStation data objects
  
• obj_trajectoryStation the WITSML construct that
  references the containing well, wellbore and
  trajectory objects AND the inclination/azimuth
  and location data plus much (optional)
  instrument, acquisition and processing data

5
Deviated Well Terminology
Vertical Reference Datum
e.g Mean Sea Level, Lowest Astronomical
Tide
Sidetrack wellbore
Parent well
Azimuth
Inclination
Acknowledgement UKOOA P7/2000
6
Presentation Outline Introduction Uses and
Requirements for WellPath data Prior Well Path
data formats Well Path data in WITSML
1.3 Conclusions
7
Life-Cycle Uses of WellPath Data

• Planning can result in many well paths, some of
  which may be drilled
• Define intersections with geological and
  reservoir targets
• Originate either from surface or pre-existing
  wellbores
• Ensure safety and collision avoidance
• Support well engineering design in- or
  out-of-house
• Satisfy regulatory permitting requirements
• Drilling
• Initial Drilling Geosteering, MWD acquisition
  and near-real-time processing
• Sharing and integration with specialist wellsite
  services
• Lateral and infill drilling Tie-in to existing
  wellbore

8
Life-Cycle Uses of WellPath Data - 2

• EP Operations
• Maintenace and Optimisation of subsurface
  facilities
• Static and dynamic reservoir modelling, analysis
  and visualisation
• Provision and maintenance of Asset data resources
  for users and applications
• Regulatory reporting
• Asset Disposal
• Sale, relinquishment, or decommissioning

9
Requirements of WellPath data

• Critical nature of WellPath data requires optimum
  accuracy and consistency in measurement,
  computation, and contextual data throughout the
  life-cycle
• Different usages of WellPath data require
  differing levels of detail, but optimal detail
  should be preserved to enable re-use,
  re-evaluation, or re-measurement

10
Presentation Outline Introduction Uses and
Requirements for WellPath data Prior Well Path
data formats Well Path data in WITSML
1.3 Conclusions
11
Prior Well Path data formats

• WITS EDI (1980 and subsequently)
• LAS version 3 (2000)
• UKOOA P7/2000 (2002)
• POSC WellPathML (2003)
• Minerals Management Service NTL2004-N03 (2004)
• WITSML Version 1.3 (released March 2005)
• Trajectory and Trajectory Station updated
• WellPath Composite Object - new capability in
  draft

12
Well Path Data Categories

• Well, Wellbore identification and context
• Name, Field, Lease/Licence, Basin, Country etc
• Survey information and context
• Operator, acquisition and processing
  contractor(s)
• Dates, depth ranges
• Survey tools, algorithms, corrections, gravity
  and magnetic field models,
• Coordinate Reference System data
• Geographic and projected coordinates and
  transformations
• Vertical datums permanent and drilling related
• Well Path Trajectory and Trajectory Stations
• Measured depth, inclination and azimuth
• True vertical depth, geographical, projected and
  engineering coordinates

13
Strengths of UKOOA P7/2000

• Supports multiple contractors, roles and survey
  phases, including wireline and MWD/LWD
• Supports multiple Vertical Datums and
  relationships between them
• References EPSG geodetic and coordinate system
  standards
• Supports post-acquisition life-cycle usages

14
Presentation Outline Introduction Uses and
Requirements for WellPath data Prior Well Path
data formats Well Path data in WITSML
1.3 Conclusions
15
Well Path data in WITSML

• Objectives in WITSML V1.3
• Extend previous capabilities from WITSML V1.2 for
  reporting raw measurements to also support
  planned well paths and calculated well paths
• Reuse WITSML specifications and objects as far as
  possible

16
Well Path data in WITSML
well
wellbore
trajectory
trajectoryStation

• wellCRS

acqn. proc. parameters (gt45)
location
17
obj_well Example
ltwellsgt ltwell uidw1gt ltnamegt207/29-A6lt/namegt
ltnameLegalgt207/29-A6Zlt/nameLegalgt
ltnumGovtgt207/29-A6Zlt/numGovtgt
ltfieldgtSaltirelt/fieldgt ltcountrygtGBRlt/countrygt
ltblockgt207/29lt/blockgt lttimeZonegt0.00lt/timeZonegt
ltoperatorgtHighland Oillt/operatorgt ltwaterDepth
uomft datumVRD1gt118.40lt/waterDepthgt   lt!--
well location the location of the well reference
point --gt ltwellLocationgt ltnameWellCRS
uidRefproj1gtED50 / UTM Zone 31Nlt/nameWellCRSgt
lteasting uommgt425353.84lt/eastinggt
ltnorthing uommgt6623785.69lt/northinggt
ltdescriptiongtlocation of well reference point in
proj systemlt/descriptiongt lt/wellLocationgt
lt/wellgt lt/wellsgt    
18
wellCRS Example (geographic)
ltwellCRS uid"geog1"gt ltnamegtED50lt/namegt
ltgeographicgt ltnameCRS namingSystem"epsg"
code"4230"gtED50lt/nameCRSgt ltgeodeticDatumCodegt
ED50lt/geodeticDatumCodegt ltxTranslation
uom"m"gt-89.5lt/xTranslationgt ltyTranslation
uom"m"gt-93.8lt/yTranslationgt ltzTranslation
uom"m"gt-123.1lt/zTranslationgt ltxRotation
uom"seca"gt0lt/xRotationgt ltyRotation
uom"seca"gt0lt/yRotationgt ltzRotation
uom"seca"gt-0.156lt/zRotationgt
ltscaleFactorgt1.200lt/scaleFactorgt
ltellipsoidName namingSystem"epsg"
code"7022"gtInternational 1924
lt/ellipsoidNamegt ltellipsoidCodegtINT24lt/ellipso
idCodegt ltellipsoidSemiMajorAxis
uom"m"gt6378388lt/ellipsoidSemiMajorAxisgt
ltinverseFlatteninggt297.0lt/inverseFlatteninggt
lt/geographicgt lt/wellCRSgt
19
wellCRS Examples(projected, local)
ltwellCRS uid"proj1"gt ltnamegtED50 / UTM Zone
31Nlt/namegt ltmapProjectiongt ltnameCRS
namingSystem"epsg" code"23031"gtED50 / UTM Zone
31Nlt/nameCRSgt ltprojectionCodegtUniversalTransver
seMercatorlt/projectionCodegt ltprojectedFrom
uidRef"geog1"gtED50lt/projectedFromgt
ltzonegt31Nlt/zonegt lt/mapProjectiongt lt/wellCRSgt ltwel
lCRS uid"localWell1"gt ltnamegtWellOneWSPlt/namegt lt
localCRSgt ltusesWellAsOrigingttruelt/usesWellAsOri
gingt ltnorthDirectiongtGrid northlt/northDirection
gt ltyAxisAzimuth uom"dega"gt0lt/yAxisAzimuthgt
ltxRotationCounterClockwisegtfalselt/xRotationCounter
Clockwisegt lt/localCRSgt lt/wellCRSgt
20
obj_trajectory Example
lttrajectory uidWell"W-12" uidWellbore"B-01"
uid"pe84e"gt ltnameWellgt6507/7-A-42lt/nameWellgt
ltnameWellboregtA-42lt/nameWellboregt ltnamegtPlan
2lt/namegt ltparentTrajectorygt lttrajectory
uidRef"pe84d"gtPlan 1lt/trajectorygt lt/parentTraj
ectorygt ltdTimTrajStartgt2001-10-31T081500.000lt/
dTimTrajStartgt ltdTimTrajEndgt2001-11-03T163000.
000lt/dTimTrajEndgt ltmdMn uom"ft"gt0lt/mdMngt ltmdM
x uom"ft"gt14089.3lt/mdMxgt ltserviceCompanygtAnadri
lllt/serviceCompanygt ltmagDeclUsed
uom"dega"gt-4.038lt/magDeclUsedgt ltgridCorUsed
uom"dega"gt0.99961lt/gridCorUsedgt ltaziVertSect
uom"dega"gt82.700lt/aziVertSectgt ltdispNsVertSectO
rig uom"ft"gt0lt/dispNsVertSectOriggt ltdispEwVertS
ectOrig uom"ft"gt0lt/dispEwVertSectOriggt
21
obj_trajectory Example (ctd)
ltdefinitivegttruelt/definitivegt ltmemorygttru
elt/memorygt ltfinalTrajgttruelt/finalTrajgt ltaziRef
gtGrid northlt/aziRefgt lttrajectoryStation
uid"34ht5"gt
lt/trajectoryStationgt ltcommonDatagt ltitemStategt
Planlt/itemStategt ltcommentsgtThese are the
comments associated with
the trajectory data object.lt/commentsgt lt/common
Datagt lt/trajectorygt
22
obj_trajectoryStation Example
lttrajectoryStation uid"34ht5"gt ltdTimStngt2001-10
-21T081500.000lt/dTimStngt lttypeTrajStationgtTieIn
Pointlt/typeTrajStationgt ltmd uom"ft"gt0lt/mdgt lttvd
uom"ft"gt0lt/tvdgt ltincl uom"dega"gt0lt/inclgt ltazi
uom"dega"gt47.3lt/azigt ltmtf uom"dega"gt47.3lt/mtfgt
ltgtf uom"dega"gt0lt/gtfgt ltdispNs
uom"ft"gt0lt/dispNsgt ltdispEw uom"ft"gt0lt/dispEwgt
ltvertSect uom"ft"gt0lt/vertSectgt ltdls
uom"dega/ft"gt0lt/dlsgt ltrateTurn
uom"dega/ft"gt0lt/rateTurngt ltrateBuild
uom"dega/ft"gt0lt/rateBuildgt ltmdDelta
uom"ft"gt0lt/mdDeltagt lttvdDelta
uom"ft"gt0lt/tvdDeltagt ltmodelToolErrorgtgood
gyrolt/modelToolErrorgt ltgravTotalUncert
uom"m/s2"gt0lt/gravTotalUncertgt ltdipAngleUncert
uom"dega"gt0lt/dipAngleUncertgt ltmagTotalUncert
uom"A/m"gt0lt/magTotalUncertgt ltgravAccelCorUsedgtfa
lselt/gravAccelCorUsedgt ltmagXAxialCorUsedgtfalselt/m
agXAxialCorUsedgt ltsagCorUsedgtfalselt/sagCorUsedgt
ltmagDrlstrCorUsedgtfalselt/magDrlstrCorUsedgt ltstatu
sTrajStationgtPositionlt/statusTrajStationgt
Note many non-mandatory attributes have been
omitted
23
obj_trajectoryStation (ctd)
ltrawDatagt ltgravAxialRaw uom"ft/s2"gt0.116lt/
gravAxialRawgt ltgravTran1Raw uom"ft/s2"gt-0.168lt
/gravTran1Rawgt ltgravTran2Raw uom"ft/s2"gt-1654lt/
gravTran2Rawgt ltmagAxialRaw uom"Oe"gt22.77lt/magAx
ialRawgt ltmagTran1Raw uom"Oe"gt22.5lt/magTran1Rawgt
ltmagTran2Raw uom"Oe"gt27.05lt/magTran2Rawgt lt/ra
wDatagt ltcorUsedgt ltgravAxialAccelCor
uom"ft/s2"gt0.11lt/gravAxialAccelCorgt ltgravTran1A
ccelCor uom"ft/s2"gt0.14lt/gravTran1AccelCorgt ltgr
avTran2AccelCor uom"ft/s2"gt0.13lt/gravTran2AccelCo
rgt ltmagAxialDrlstrCor uom"Oe"gt0.17lt/magAxialDrl
strCorgt ltmagTran1DrlstrCor uom"Oe"gt0.16lt/magTra
n1DrlstrCorgt ltmagTran2DrlstrCor
uom"Oe"gt0.24lt/magTran2DrlstrCorgt ltsagIncCor
uom"dega"gt0lt/sagIncCorgt ltsagAziCor
uom"dega"gt0lt/sagAziCorgt ltstnMagDeclUsed
uom"dega"gt-4.038lt/stnMagDeclUsedgt ltstnGridCorUs
ed uom"dega"gt-0.4917lt/stnGridCorUsedgt ltdirSenso
rOffset uom"ft"gt48.3lt/dirSensorOffsetgt lt/corUsed
gt
24
obj_trajectoryStation (ctd)
ltvalidgt ltmagTotalFieldCalc
uom"Oe"gt51.19lt/magTotalFieldCalcgt ltmagDipAngleC
alc uom"dega"gt41.5lt/magDipAngleCalcgt ltgravTotal
FieldCalc uom"ft/s2"gt0.999lt/gravTotalFieldCalcgt
lt/validgt ltmatrixCovgt ltvarianceNN
uom"ft2"gt0.005236lt/varianceNNgt ltvarianceNE
uom"ft2"gt0.005236lt/varianceNEgt ltbiasE
uom"ft"gt0lt/biasEgt ltbiasVert uom"ft"gt0lt/biasVer
tgt lt/matrixCovgt ltlocationgt ltwellCRS
uidRef"geog1"gtED50lt/wellCRSgt ltlatitude
uom"dega"gt59.755300lt/latitudegt ltlongitude
uom"dega"gt1.71347417lt/longitudegt lt/locationgt ltl
ocationgt ltwellCRS uidRef"proj1"gtED50 / UTM
Zone 31Nlt/wellCRSgt lteasting uom"m"gt427710.69lt/e
astinggt ltnorthing uom"m"gt6625015.54lt/northinggt
lt/locationgt lt/trajectoryStationgt
25
Status at 2Q2005

• WITSML 1.3 is being evaluated against other
  specifications
• P7 evaluation is in progress
• MMS NTL2004-N03 content is satisfied
• PPDM evaluation is in progress
• Expectation is that most requirements will be
  satisfied from what is available, perhaps with
  minor changes /or additions.

26
Next Steps

• Validate with DTI/UKOOA, MMS, NPD/DISKOS, PPDM,
  WITSMLTTand other interested parties (June)
• Provide feedback to WITSML TT (ongoing)
• Produce Technical Report / Usage Document
  describing all of the above (July)

27
Conclusions

• WITSML V1.3 was released in March 2005
• Use of V1.3 in pilot testing and commercial
  products anticipated during remainder of 2005
  leading to change requests and further iteration
• WellPath will satisfy several uses cases, to
  include raw measurement reporting, planned well
  path transfer, and post-processing wellpath
  transfer.

28
More information available from- Paul Maton,
tel[phone]maton_at_posc.orgAlan Doniger,
tel [phone]donger_at_posc.orghttp//www.pos
c.org