Geoshare Data Model, Version 13.0

217-WELL-HEADER

Description    Attributes    Comments    References   

Description

Wells are holes drilled in the earth to gain access to underground formations, along with their associated materiel: casing, cement, christmas trees, etc. The use of a well may change over its lifetime, and could include any or all of the following:

This object contains the general description of a well, and makes reference to other objects containing the logs (formation properties), deviation surveys (well trajectory), markers (location of formations traversed by the hole), seismic well ties (correspondence with features located using seismics), well tests (tests to determine pressure and flow rate for a potentially producible zone), production history data, and other object types containing data about this well.

Well Topology

The drilling process starts by drilling a hole starting from a well tophole location down to some depth. Thereafter it is not unusual to drill a number of sidetracks, each starting from a 'kickoff point' in an existing part of the hole. The resulting topology can be generalized as a tree of holes rooted at the well tophole location. 'Wellbore' is the term applied to the hole extent from the deepest (in measure depth) point of such a unique branch all the way back up to the well tophole location.A result is that a given extent of hole may be part of a number of wellbores; for example, the hole immediately below the tophole location participates in all wellbores associated with the well.

There has long been inconsistency in the industry about whether 'well' means one such wellbore, or the collection of all wellbores sharing a common tophole location, or indeed, even some other concept. It has long been the practice to use the term 'well' to refer to the concept that was most meaningful for a given application. Applications such as reservoir simulators have even modeled individual completions as distinct wells; since simulators deal with fluid sources and sinks, generalizing each completion as an identifiable well is a convenient organization for that application.

Traditional Geoshare half-links have not made this distinction precisely, and have usually used 'well' to mean one such wellbore for a variety of reasons. Many regulatory agencies treat each distinct wellbore as a unique well, and even when this restriction is not in effect, many wells consist of a single wellbore anyway. Some (or most) of the time, there is often a single wellbore implied or active in the context of a given well at a given time.

For applications viewing wells distinct from wellbores, and allowing multiple wellbores per well, both wells, and wellbores must be uniquely identified, and this need is anticipated by most naming systems. API numbers, for example, include a sidetrack identifier, so each distinct wellbore would have distinct API identifiers consisting of the well API number with the sidetrack identifier appended as a suffix.

Beginning with GDM 11.0, Geoshare supports a unification of the views of these two classes of application. Although the resulting agreement is not ideal, it does address the needs of both classes of applications and maximizes the communication between them. The agreement is to use (this) 217-WELL-HEADER object to represent both well and wellbore, and to explicitly allow the representation of the tree-structuring of wellbores within wells in terms of hierarchies of 217-WELL-HEADER objects.

If a sending application knows the well in which each wellbore is defined, this can be encoded using the PARENT-UWI, and PARENT-UWI-NAMING-SYSTEM. If the sender additionally knows the identity of a wellbore from which each wellbore is 'kicked off', this can be encoded in PARENT-WELLBORE-UWI, and PARENT-WELLBORE-UWI-NAMING-SYSTEM. Consider the following example:

This should be represented as three 217-WELL-HEADER objects with the following attributes (the naming system attributes should be encoded, but are not shown).

The preferred encoding for the cell containing 'X or {left null}' is 'X'. However, many senders will continue sending 217-WELL-HEADER objects without a value encoded for PARENT-UWI as was legal for pre GDM 11.0.

The definition of a 217-WELL-HEADER object that either a) has PARENT-UWI = UNIQUE-WELL-ID, or b) without a PARENT-UWI value is as follows: Here is a well with a possibly-trivial primary wellbore. If there is a meaningful wellbore with associated data (logs, markers, deviations, etc. referenced from the same 217-WELL-HEADER object) then its identity is the same as the identity of the well. Trivial wellbore is used here to mean one of insignificant extent, and no associated wellbore-specific data. Primary wellbore is used to mean a wellbore whose identity is indistinguishable from that of the well.

If possible, data describing a well and all of its wellbores should be encoded in the same logical file. In some cases however, data size considerations (see section below) will dictate that wellbores Y and Z from the example above have their associated data in distinct logical files. In this case, a 217-WELL-HEADER object for well 'X' should appear in each logical file in which data for any wellbore of this well resides. In this case, each such instance must have at least the identifying fields encoded giving the UNIQUE-WELL-ID, WELL-NAME, WELL-NUMBER, SHORT-NAME, PLOT-NAME, all of the associated naming-system identification etc. Some receivers will also find it helpful to find the identities of any business associates, tophole location, etc., so a good general rule would be for the sender to encode all well-specific attributes in these replicated objects.

Elevation References

A working datum can be defined as part of the well data, and this is used as a reference point for some or all of the many depth measurements made in the well. Working datum information, when associated with the well header, is given using the ELEV-PHYSICAL-REF and DATUM-ELEVATION attributes. When present, GROUND-ELEVATION, KELLY-BUSHING-ELEVATION, and CASING-FLANGE-ELEVATION should be referenced to the reference datum defined in the controlling 217-CARTOGRAPHIC-PROJECTION object. This is usually mean sea level.

Logical File Size Considerations

Databases of well information can be quite large, sometimes running on the order of many gigabytes. Since systems using Geoshare often have limited hardware and software capabilities, guidelines are needed to help developers break up such datasets into pieces small enough to be handled. Geoshare provides for such decomposition by allowing parts of a larger dataset to be placed in each of a number of logical files. Well data can be broken up by placing a limited number of wells into each logical file.

For a Geoshare dataset containing just well data, the number of wells in a logical file should not exceed the following guideline based on the amounts of associated data of various types:

where L is the number of log traces, M is the number of well markers, P is the number of production history objects, R is the number of well remarks, S is the sum of the number of deviation and checkshot surveys, T is the number of well tests and Z is the number of zoned variables. If this limit comes up e.g. 2.7, then limit the number of wells to 2 per logical file.

Additional information on this subject can be found in the section 'Logical Composition of Large Datasets'.

Description    Attributes    Comments    References   

Attributes

Description    Attributes    Comments    References   

Comments

1. UNIQUE-WELL-ID   C=1, R=ASCII   MAND   
   UNIQUE-WELL-ID-NAMING-SYSTEM   C=1, R=ASCII      
         

   Unique well identifier and the system in which it is named. Certainly this must be unique within a given logical file. The general expectation is that the UWI is unique in the scope of the sender. So if the same UWI is used for well data from a given sending system in two completely different datasets, the data should apply to the same well. A complete list of known naming systems can be found in the section titled " Namespaces in Geoshare".

2. PLOT-SYMBOL   C=1, R=ASCII   COND   
         

   Name of the plot symbol to use for well. A candidate list can be found in the write-up for 217-MAP-SYMBOL. Use of PLOT-SYMBOL is depreciated in favor of PLOT-CODE starting with GDM 12. PLOT-SYMBOL is preserved only for compatibility with previous versions of the GDM.

3. PLOT-CODE   C=1, R=UNORM   COND   
         

   Code of the plot symbol to use for well. A candidate list can be found in the write-up for 217-MAP-SYMBOL. Use of PLOT-CODE is prefered to use of PLOT-SYMBOL starting with GDM 12.

4. DEVIATION-SURVEY   R=OBJREF      
         

   Reference to one or more objects of type 217-WELL-DEVIATION-SURVEY .

5. WELL-NAME   C=1, R=ASCII      
   WELL-NAME-NAMING-SYSTEM   C=1, R=ASCII      
         

   The full legal name of the well, and the naming system in which it is named. In some cases, the official name of the well is the concatenation of lease name and lease permit number. In this case, WELL-NAME should contain the lease name, and WELL-NAME-NAMING-SYSTEM must be `Lease name'. A complete list of known naming systems can be found in the section titled " Namespaces in Geoshare".

6. WELL-NUMBER   C=1, R=ASCII      
   WELL-NUMBER-NAMING-SYSTEM   C=1, R=ASCII      
         

   `Number' of the well and the system in which it is named. May contain non-numeric characters. When the official name of the well is the concatenation of lease name and permit number, this attribute should contain the well permit number within the lease. A complete list of known naming systems can be found in the section titled " Namespaces in Geoshare".

7. PLOT-NAME   C=1, R=ASCII      
         

   Shortened name for well lease plotting.

8. SHORT-NAME   C=1, R=ASCII      
   SHORT-NAME-NAMING-SYSTEM   C=1, R=ASCII      
         

   Shortened or informal name of the well. A complete list of known naming systems can be found in the section titled " Namespaces in Geoshare".

9. OPERATOR   C=1, R=ASCII      
         

   The name of the company actually operating the well on behalf of themselves, or under contract to the organization named in COMPANY.

10. LICENSEE   C=1, R=ASCII      
          

    Licensee of the well lease.

11. AGENT   C=1, R=ASCII      
          

    Name of the agent.

12. WELL-CLASS   C=1, R=ASCII      
          

    Class of the well. A suggested list of values follows. With the addition (GDM 9.0) of attributes WELL-PURPOSE, WELL-FLOWING-MODE, WELL-FLOWING-FLUID and SHOWS-TYPE, WELL-CLASS is deprecated, and will probably be dropped at a future date.

    Well Class
    Abandoned_Producer
    Core_Hole
    Core_Test
    Deeper_Pool_Test
    Development
    Dry_Hole
    Gas
    Gas_Condensate
    Geopressure
    Geothermal
    Hot_Dry_Rock
    Injection
    Injection_Air
    Injection_CO2
    Injection_Gas
    Injection_Propane
    Injection_Water
    Junked_Abandoned
    Multiple_Completion_Gas
    Multiple_Completion_Gas_Condensate
    Multiple_Completion_Oil
    Multiple_Completion_Oil_Gas
    New_Field_Wildcat
    New_Pool_Wildcat
    Observation
    Oil
    Outpost_Test
    Permafrost
    Potash
    Salt
    Service
    Shallower_Pool_Test
    Storage
    Stratigraphic_Test
    Suspended
    Temperature_Gradient
    Temperature_Observation
    Temporarily_Abandoned
    Unclassified
    Waste_Disposal
    Water_Disposal
    Water_Source

13. CURRENT-STATUS   C=1, R=ASCII      
          

    Current well status. Status indicates the disposition of a well at a given time. A well has a status from the time of its conception to its abandonment. Dates can be associated with most changes in status using the EVENT attribute. See also the 217-EVENT object description. The following list of status values is suggested. Multiword code values are separated by single spaces:

    Current Well Status
    Code	Description
    PROPOSED	the status of a well from conception to either regulatory approval or commencement of drilling
    PERMITTED	a well that has been granted regulatory approval to drill but has not yet been spudded
    DRILLING	drilling operations are ongoing
    DRILLING SUSPENDED	drilling operations are suspended temporarily in a manner that allow immediate resumption of activities
    ACTIVE	a well capable of being operated
    SUSPENDED	a well whose operations have been suspended in a manner that allows immediate resumption of activities
    TEMPORARILY ABANDONED	a well whose activities have been terminated temporarily in a manner that precludes immediate resumption of activities
    ABANDONED	the status of a well in which drilling, completion, and production operations have been permanently terminated
    PLUGGED AND ABANDONED	an abandoned well whose wellbores have been plugged to prevent migration of fluids from one stratum to another

14. ORIGINAL-STATUS   C=1, R=ASCII      
          

    Original well status. Same candidate values as for the CURRENT-STATUS attribute.

15. PREVIOUS-STATUS   C=1, R=ASCII      
          

    Previous well status. Same candidate values as for the CURRENT-STATUS attribute.

16. TOP-LOCATION   C=1, R=OBJREF      
          

    Reference to a 217-MAP-LOCATION object giving top hole location.

17. TOP-HOLE-LEGALS   C=1, R=OBJREF      
          

    Reference to an object of type 217-LEGAL-LOCATION describing the legal location of the top of the well.

18. BOTTOM-LOCATION   C=1, R=OBJREF      
          

    Reference to a 217-MAP-LOCATION object giving bottom hole location.

19. BOTTOM-HOLE-LEGALS   C=1, R=OBJREF      
          

    Reference to an object of type 217-LEGAL-LOCATION describing the legal location of the bottom of the well.

20. OFFSHORE   C=1, R=OBJREF      
          

    Reference to an object of type 217-WELL-PLATFORM describing an offshore drilling platform if the well is offshore.

21. TOTAL-DEPTH   C=1, R=OBJREF      
          

    Reference to an object of type 217-WELL-TOTAL-DEPTH describing the location of the well at total depth.

22. DATUM-ELEVATION   C=1, R=FDOUBL      U
          

    Elevation of the ELEV-PHYSICAL-REF (working datum) with respect to the ELEV-HISTORICAL-REF (reference datum) in the controlling 217-CARTOGRAPHIC-PROJECTION. For example, if this has a value of 10 feet, then the ELEV-PHYSICAL-REF is 10 feet above the ELEV-HISTORICAL-REF. Additional information on resolution of elevations can be found in the "Elevation References" section.

23. ELEV-PHYSICAL-REF   C=1, R=ASCII      
          

    Physical reference point (working datum) for elevations as per following table:

    Elevation Physical Reference
    Code	Description
    KB	Kelly Bushing
    DF	Drill Floor
    MT	Drill Floor Mat
    RT	Rotary Table
    RB	Rotary Bushing
    GL	Ground Level
    CF	Casing Flange
    TS	Topographic Sheet
    ET	Estimated
    IN	Interpolated
    SL	Sea Level
    ES	Echo Sounder
    UN	Unknown
    NA	Not Available

24. DEPTH-UNIT   C=1, R=UNITS      
    TIME-UNIT   C=1, R=UNITS      
          

    Units for depths and times.

25. ORIGINAL-UNIT-SYSTEM   C=1, R=USHORT      
          

    The unit system in which the original data was recorded. Codes are interpreted according to the following table:

    Unit System
    Code	Description
    1	Imperial unit system
    2	Metric system
    3	Other unit system

26. GROUND-ELEVATION   C=1, R=FDOUBL      U
          

    Ground elevation of the well measured from the reference datum - not the working datum. This is typically sea level. This is not intended to be the identification of the working datum in use. The attributes ELEV-PHYSICAL-REF and DATUM-ELEVATION are provided for this purpose.

27. KELLY-BUSHING-ELEVATION   C=1, R=FDOUBL      U
          

    Kelly Bushing elevation of the well measured from the reference datum - not the working datum. This is typically sea level. This is not intended to be the identification of the working datum in use. The attributes ELEV-PHYSICAL-REF and DATUM-ELEVATION are provided for this purpose.

28. CASING-FLANGE-ELEVATION   C=1, R=FDOUBL      U
          

    Elevation of the casing flange of the well measured from the reference datum - not the working datum. This is typically sea level. This is not intended to be the identification of the working datum in use. The attributes ELEV-PHYSICAL-REF and DATUM-ELEVATION are provided for this purpose.

29. CONFIDENTIALITY   C=1, R=OBJREF      
          

    Reference to an object of type 217-WELL-CONFIDENTIALITY describing the confidentiality of the well.

30. CHECK-SHOT-SURVEY   R=OBJREF      
          

    Reference to one or more objects of type 217-WELL-CHECK-SHOT-SURVEY describing any check shot surveys, if any done on the well.

31. DRILLING-INFORMATION   C=1, R=OBJREF      
          

    Reference to an object of type 217-DRILLING-INFORMATION describing the drilling of the well.

32. PRIMARY-SOURCE   C=1, R=ASCII      
    OWNER   C=1, R=ASCII      
          

    The source and the owner of the data. The source is the business associate or algorithm responsible for the data content or the interpretation represented by the data. The owner is the business associate that has the authority to create, view, update, or delete a particular data item and also has the authority to grant/revoke other business associates these same rights.

33. PROPRIETARY   C=1, R=STATUS      
          

    If present, this well contains proprietary information.

34. DISCOVERY   C=1, R=STATUS      
          

    If present, this is a discovery well.

35. FAULT   C=1, R=STATUS      
          

    If present, this well has a faulted section.

36. LAST-UPDATE   C=1, R=DTIME      
          

    The date of the last update to the well information. Starting with GDM 11, such significant dates can be handled with the more general event mechanism so these attributes may be deprecated at a future date. See the EVENT attribute.

37. SPUD-DATE   C=1, R=DTIME      
          

    The spud date of the well. Starting with GDM 11, such significant dates can be handled with the more general event mechanism so these attributes may be deprecated at a future date. See the EVENT attribute.

38. COMPLETION-DATE   C=1, R=DTIME      
          

    The completion date of the well. Starting with GDM 11, such significant dates can be handled with the more general event mechanism so these attributes may be deprecated at a future date. See the EVENT attribute.

39. RIG-RELEASE-DATE   C=1, R=DTIME      
          

    The rig release date of the well. Starting with GDM 11, such significant dates can be handled with the more general event mechanism so these attributes may be deprecated at a future date. See the EVENT attribute.

40. ON-PRODUCTION-DATE   C=1, R=DTIME      
          

    The on production date of the well. Starting with GDM 11, such significant dates can be handled with the more general event mechanism so these attributes may be deprecated at a future date. See the EVENT attribute.

41. CALCULATED-ON-PRODUCTION   C=1, R=DTIME      
          

    The calculated on production date of the well. Starting with GDM 11, such significant dates can be handled with the more general event mechanism so these attributes may be deprecated at a future date. See the EVENT attribute.

42. ON-INJECTION-DATE   C=1, R=DTIME      
          

    The on injection date of the well. Starting with GDM 11, such significant dates can be handled with the more general event mechanism so these attributes may be deprecated at a future date. See the EVENT attribute.

43. STATUS-DATE   C=1, R=DTIME      
          

    The date the last status of the well was entered. Starting with GDM 11, such significant dates can be handled with the more general event mechanism so these attributes may be deprecated at a future date. See the EVENT attribute.

44. FINAL-DRILLING-DATE   C=1, R=DTIME      
          

    The final drilling date. Starting with GDM 11, such significant dates can be handled with the more general event mechanism so these attributes may be deprecated at a future date. See the EVENT attribute.

45. WELL-PURPOSE   C=1, R=ASCII      
          

    Indicates why the well was drilled or will be drilled. Candidate values are:

    Well Purpose
    Values	Description
    Blowout Relief	A service well or wellbore drilled with the specific purpose to provide communication at some point below the surface to another well or wellbore which is out of control. [12] 1/25/93 #P0003265
    Borehole Reacquisition	A service well or wellbore drilled to intersect another well or wellbore below the surface for the purpose of extending the life of a well whose surface wellbore has been lost or damaged.
    Deeper Pool Wildcat	An exploratory wellbore drilled to search for additional pools of hydrocarbon in close proximity to known pools of hydrocarbon but at a deeper stratigraphic levels than the known pools.
    Delineation	A well or wellbore drilled to establish the areal limits of a known pool of hydrocarbon. [11]
    Development	A well or wellbore drilled in a zone in an area already proved productive. [12] 1/25/92 #P0000602
    Drilling Test	A well or wellbore drilled to test the suitability of a particular type of equipment or drilling practice.
    Fluid Storage	A service well or wellbore drilled for the purpose of injection of fluids into a reservoir for storage and later withdrawal. [11]
    General Service	A well or wellbore drilled to provide a service such as subsurface fluid monitoring, waste disposal, fluid storage, blowout relief and wellbore re-acquisition. Not necessarily an E&P wellbore.
    Geothermal	A well or wellbore drilled with the specific purpose of extracting heat from the earth.
    Infill Development	A developmental well or wellbore drilled to fill in between established wells, usually part of a drilling program to reduce the spacing between wells to increase production.
    Mineral	A non-E&P well drilled for the purpose of locating and/or extracting a mineral from the subsurface, usually through the injection and/or extraction of mineral-bearing fluids. [11]
    Monitor	A service well or wellbore drilled to allow continuous or periodic measurement of a property of the subsurface through time.
    New-Field Wildcat	An exploratory well or wellbore drilled to search for an occurrence of hydrocarbon at a relatively considerable distance outside the limits of known pools of hydrocarbon, as those limits were understood at the time. [11]
    New-Pool Wildcat	An exploratory well or wellbore drilled to search for additional pools of hydrocarbon in close proximity and at the same stratigraphic level as known pools.
    Outpost Wildcat	An exploratory well or wellbore drilled to search for additional pools of hydrocarbon or to extend the limits of a known pool by searching in the same interval at some distance from a known pool. [11]
    Shallower Pool Wildcat	An exploratory well or wellbore drilled to search for additional pools of hydrocarbon in close proximity, but at a shallower stratigraphic levels than the known pools.
    Stratigraphic Test	An exploratory well or wellbore drilled for the purpose of gathering geologic information on the stratigraphy of an area. Also called core test or C.O.S.T. well. [11]
    Waste Disposal	A service wellbore drilled for the purpose of injection of waste fluids into the subsurface for disposal. [11]
    Wildcat	A exploratory wellbore drilled in an unproved area to test for a new field, a new pay, a deeper reservoir, or a shallower reservoir. [12] 1/25/92 #P0002423

46. WELL-FLOWING-MODE   C=1, R=ASCII      
          

    Indicates current (or latest known) fluid flow conditions of well. Candidate values are:

    Flow Condition
    Values	Description
    Dry	Well or completion is not flowing and is not capable of commercial production.
    Injector	Fluid is being injected into the well or completion. Gas introduced for lift is not considered injection.
    Injector-Producer	Fluid is both being injected into and produced from the well or completion. Gas introduced for lift is not considered injection.
    No Flow	Well or completion is not flowing.
    Producer	Fluid is being produced from the well or completion.

47. WELL-FLOWING-FLUID   C=1, R=ASCII      
          

    Indicate the fluid flowing. A value of `Multiple' or `Other' should be explained using attribute WELL-REMARKS. Candidate values are:

    Flowing Fluid
    Value	Description
    Brine	water saturated with, or containing significant dissolved minerals such as salt
    Condensate	A light hydrocarbon liquid obtained by condensation of hydrocarbon vapors. It consists of varying proportions of butane, propane, pentane and heavier fractions, with little or no methane or ethane (Penwell)
    Gas	Dry gas
    Gas_Oil	Commercial quantities of both gas and oil are produced from a single completion.
    Multiple	Multiple fluids
    None	No fluid flow
    Oil	Oil (may have associated gas)
    Other	Other fluid
    Steam	Steam
    Water	Water

48. SHOWS-TYPE   C=1, R=ASCII      
          

    Indicates one or more shows associated with well. Candidate values are:

    Hydrocarbon Shows
    Coal
    Gas
    Gas_Oil
    None
    Oil

49. LOG-RUNS   R=OBJREF      
          

    A list or references to objects of type 217-LOG-RUN which describe logs run on the well.

50. SEISMIC-WELL-TIES   R=OBJREF      
          

    A list of references to objects of type 217-SEISMIC-WELL-TIE which describe the well ties for the well.

51. STRAT-COLUMNS   C=1, R=OBJREF      
          

    A reference to an object of type 217-STRATIGRAPHIC-COLUMN which gives the name, citation and the ordered list of stratigraphic layers for this well.

52. CORES   R=OBJREF      
          

    A list of references to objects of type 217-WELL-CORE which describe well cores taken on this well.

53. MARKERS   R=OBJREF      
          

    A list of reference to objects of type 217-WELL-MARKER which describe well markers associated with this well.

54. PRODUCTION   R=OBJREF      
          

    A list of references to objects of type 217-WELL-PRODUCTION which describe the production history of this well.

55. WELL-REMARKS   R=OBJREF      
          

    A list of references to 217-WELL-REMARKS objects, to convey a set of depth-indexed general remarks.

56. WELL-TUBULARS   R=OBJREF      
          

    A list of references to objects of type 217-WELL-TUBULAR which describe the tubulars in the well.

57. ZONE-VALUES   R=OBJREF      
          

    A list of references to objects of type (RP66 public) PARAMETER, each of which describes a zoned variable and its values in the well. See the "Use of RP66 PARAMETER and ZONE Objects" section for more information.

58. SYNTHETIC-TRACES   R=OBJREF      
          

    A list of references to 217-SYNTHETIC-TRACE objects for synthetic seismic trace data.

59. TESTS   R=OBJREF      
          

    A list of references to objects of type 217-WELL-TEST which describe well test data.

60. TARGETS   R=ASCII      
          

    Names matching the NAME attribute of the 217-WELL-TARGET objects to be drilled in the future, or already pierced by this well. If target names are known to both sender and receiver, the objects describing the targets need not be in the dataset containing this object.

61. PATH-OF-WELL   R=OBJREF      
          

    Reference to one or more 217-WELLPATH objects showing the composition of the well's path in terms of a number of surveyed sections.

62. WELLPATH-SEGMENT   R=OBJREF      
          

    A reference to one or more 217-WELLPATH-SEGMENT objects. These show composition of the well's path in terms of the individual segments drilled.

63. DRILL-RUNS   R=OBJREF      
          

    Reference to one or more 217-DRILL-RUN objects for information about drilling runs, the logs acquired while drilling, and the downhole equipment used.

64. COMPANY   C=1, R=ASCII      
          

    The name of the organization owning, or having rights to operate, the well or containing field or lease. This is typically a private or national oil company. Compare to OPERATOR.

65. WELLBORE-SHAPE   C=1, R=ASCII      
          

    The shape of the associated wellbore, when there is only one, or when one wellbore (from among several drilled) is predominantly associated with the well. This would be the same wellbore associated with any markers, logs, production histories, deviation and checkshot surveys, etc. Legal values are codes from the following list from [5]:

    Wellbore Shape
    Code	Description
    Vertical	A wellbore that is nearly vertical with respect to the surface location
    Deviated	A well or wellbore that significantly departs from the vertical with respect to the surface location
    Build and Hold	A Wellbore configuration where the inclination is increased to some terminal angle of inclination and maintained at that angle to the specified target
    Double Kick Off	Incorporates two tangential (constant, non-zero inclination) sections. The second of which must be at a higher inclination than the first
    S Shaped	A well or wellbore drilled with a vertical segment, a deviated segment, and return toward a vertical segment
    Horizontal	A well or wellbore whose path deviates from the vertical by at least 75 degrees

66. COMPLETION-INTERVALS   R=OBJREF      
          

    A list of references to 217-WELL-COMPLETION-INTERVAL objects which describe well connections to the reservoir.

67. FLUID-SAMPLES   R=OBJREF      
          

    A list of references to 217-FLUID-SAMPLE objects representing the fluid samples taken out of a well, in particular those submitted for PVT fluid analyses.

68. PARENT-UWI   C=1, R=ASCII      
    PARENT-UWI-NAMING-SYSTEM   C=1, R=ASCII      
    PARENT-WELL-NAME   C=1, R=ASCII      
    PARENT-WELL-NAME-NAMING-SYSTEM   C=1, R=ASCII      
          

    The unique well identifier and well name, together with their defining namespaces, of the well to which this wellbore belongs. These attributes should be encoded as the UWI and name of a well, not the UWI and name of a wellbore, by systems which maintain this distinction. It is not intended to show a hierarchy of wellbores and sub-wellbores, just which wellbores belong to which well.

    UWI Names: There are two common methods for naming wellbores and wells. The first method stems from the view that wellbores are typically drilled one at a time and the names are assigned as they are drilled. When the first wellbore is drilled, the UWI of the wellbore is the UWI of the well. When the second wellbore is drilled, it is assigned a new unique name. The first wellbore retains its original name, which is the name of the well. Thus one sees names like:

    UWI Names
    WELL_UWIWELLBORE_UWI AA AB

    In this first method, wellbore 'A' is the 'primary' wellbore because its name is used as the name of the well. The second method stems from the view that multiple wellbores are planned and named in advance. When the first wellbore is drilled, it is given a name and the well is given a different name. When the second wellbore is drilled, it is given a new unique name. Thus you end up with names like:

    UWI Names
    WELL_UWIWELLBORE_UWI AA1 AA2

69. PARENT-WELLBORE-UWI   C=1, R=ASCII      
    PARENT-WELLBOREUWI-NAMING-SYSTEM   C=1, R=ASCII      
          

    For systems that maintain the full hierarchy of wellbores within a well, these attributes can be used to identify the immediate wellbore parent of a given wellbore. See the description section.

70. EVENT   R=OBJREF      
          

    References to a number of 217-EVENT objects giving the significant events for this drill run. Some significant events for this object would be handled as follows:

    Event Example
    Event	217-EVENT.CODE	217-EVENT.BEGIN-END-FLAG
    last update to well or well data	ACTIVITY MOST RECENT	none
    spud date	SPUD	none
    completion date	COMPLETE	none
    rig release date	RIG RELEASE	none
    on production date	PRODUCE	BEGIN
    calculated on production	PRODUCE ESTIMATED	none
    on injection	INJECT	BEGIN
    status date (see CURRENT-STATUS attribute)	STATUS ACHIEVE	none
    final drilling	DRILL	END
    shutin	VALVE CLOSE	none
    total depth achieved	AT TOTAL DEPTH	none
    abandon date	ABANDON	none

Description    Attributes    Comments    References   

References

• 217-FIELD

Geoshare Data Model, Version 13.0

Send questions and comments to Jim.Theriot@POSC.org
Copyright © 2002, 03 Petrotechnical Open Software Corporation. All rights reserved.
This file is made available under the POSC Product License Agreement, which may be found at http://www.posc.org/about/license.shtml (on the POSC web site under 'About Us' > 'License Agreement').
POSC ®, the POSC logo ® and Epicentre ® are registered trademarks of Petrotechnical Open Software Corporation.
Copyright © 2001 Geoshare Users Group.