Documentation for WITSML_Composite

'Information about the XML message instance.'

'A collector for wells.'

'A collector for production operation reports.'

'A collector for product volume reports.'

'A collector for production flow models.'

'A container element that can contain custom or user defined data elements. This is intended for adding new objects that are not a child of well.'

'Information about the XML message instance.'

'A collector for wells.'

'A collector for production operation reports.'

'A collector for product volume reports.'

'A collector for production flow models.'

'A container element that can contain custom or user defined data elements. This is intended for adding new objects that are not a child of well.'

'Human recognizable context for the completion string.'

'The type of tubular assembly.'

'The measured depth at the top.'

'The measured depth at the base.'

'The true vertical depth at the top.'

'The true vertical depth at the base.'

'The date on which the string was installed.'

'The date and time at which the string was instlled.'

'These are the items of equipment that are commonly found in a completion string. MISSING ITEMS: power and gauge cable, capillary tube.'

'This is a rod string within a completion string. It is not defined how this rod string is connected to the prime mover at the surface. QUESTION: What about other pumping methods?'

'The effective length of the string.'

'The effective volume of the string.'

'xxxxxxxxxxxxxxxxxx'

'A collector for completion string classes.'

'A recording of a status associated with the string.'

'An event associated with the string.'

'A remark about the string.'

'A container element that contains elements that are common to all data objects.'

'A container element that can contain custom or user defined data elements.'

'Human recognizable context for the Product Flow Model.'

'The name of the facility which is represented by this model. The name can be qualified by a naming system. This also defines the kind of facility.'

'The name and type of a facility whose context is relevant to the represented installation.'

'The date and time of the start of validity for this model.'

'The date and time of the termination of validity for this model.'

'Defines the external port in another Product Flow Model to which an external port in this model is connected. An external port should be connected to an external port with the opposite direction. The connected external port must be in another Product Flow Model. These connections should always be defined on a one-to-one basis. For example, if a facility may receive input from multiple other facilities then a separate input port should be defined for each of those facilities. This allows any question about mass balancing to be contained within each individual model. The external port name must match the name of an external port on the network that represents this model.'

'The description of one named network within this model. Each model is self contained but may reference other newtorks for defining internal detail. One of the networks must represent this model.'

'A descriptive remark about the model.'

'A container element that contains elements that are common to all data objects.'

'A container element that can contain custom or user defined data elements.'

'Human recognizable context for the Product Volume Report.'

'The name of the facility which is represented by this report. The name can be qualified by a naming system. This also defines the kind of facility.'

'The name and type of a facility whose context is relevant to the represented installation.'

'The type of report.'

'The type of period that is being reported. This value must be consistent with the reporting start and end values.'

'The beginning date and time that the report represents.'

'The ending date and time that the report represents.'

'The beginning date that the report represents.'

'The ending date that the report represents.'

'The operator of the facilities in the report.'

'The tile of the report if different from the name of the report.'

'The geographic context of the report.'

'The date that the report was issued.'

'The person or company that issued the report. This may contain the role of the person or company within the context of the report.'

'The date that the report was approved.'

'The person or company that approved the report. This may contain the role of the person or company within the context of the report.'

'The Product Flow Model for the overall installation. This model represents all Product Flow Units referenced within this report.'

'Defines the standard temperature and pressure to which all standard volumes in this report have been corrected. This applies to all elements whose name is suffixed by Std and documented to be corrected to conditions of standard temperature and pressure.'

'A facility for which product information is being reported.'

'A container element that contains elements that are common to all data objects.'

'A container element that can contain custom or user defined data elements.'

'Human recognizable context for the Production Operation Report.'

'The name of the facility which is represented by this report. The name can be qualified by a naming system. This also defines the kind of facility.'

'The name and type of a facility whose context is relevant to the represented installation.'

'The type of report.'

'The type of period that is being reported. This value must be consistent with the reporting start and end values.'

'The beginning date and time that the report represents.'

'The ending date and time that the report represents.'

'The beginning date that the report represents.'

'The ending date that the report represents.'

'The operator of the facilities in the report.'

'The tile of the report if different from the name of the report.'

'The geographic context of the report.'

'The date that the report was issued.'

'The person or company that issued the report. This may contain the role of the person or company within the context of the report.'

'The date that the report was approved.'

'The person or company that approved the report. This may contain the role of the person or company within the context of the report.'

'A report for each installation'

'A container element that contains elements that are common to all data objects.'

'A container element that can contain custom or user defined data elements.'

'Human recognizable context for the well.'

'General information about a well.'

'A collector for wellbores.'

'A collector for well completions.'

'A container element that can contain custom or user defined data elements. This is intended for adding new custom objects that are a child of well.'

'Human recognizable context for the well completion.'

'The kind of completion.'

'The date when the completion is first operational.'

'The date when the completion is no longer operational.'

'The date when the completion was finished.'

'The recording of a status associated with the completion.'

'The ratio of flow rate to pressure drop. Used for oil wells, PI is the barrels of oil produced per day per psi decline in bottomhole flowing pressure.'

'The term that accounts for additional pressure drops in the immediate vicinity of a well in well performance calculations, such as transient pressure test analysis. Positive skin effects indicate damaged conditions. Negative skin effects indicate stimulated conditions.'

'A pointer to to the completion string utilized by this well completion.'

'A pointer to a wellbore open hole interval that is part of the well completion.'

'A pointer to a wellbore perforation interval that is part of the well completion.'

'A container element that contains elements that are common to all data objects.'

'A container element that can contain custom or user defined data elements.'

'Legal name of the well.'

'License number of the well.'

'Government assigned well number.'

'Date and time license was issued.'

'Name of the field in which the well is located.'

'Country in which well is located.'

'State or province in which well is located.'

'County in which the well is located.'

'Geo-political region.'

'Geo-political district name.'

'Block name in which well is located.'

'The time zone in which well is located. It is the deviation in hours and minutes from UTC. This should be the normal time zone at the well and not a seasonally adjusted value such as daylight savings time. While the time zone is optional in a date time value, it is strongly advised that the zone always be specified in each date time value. The time zone in a date time value may use seasonally adjusted values.'

'Operator company name.'

'Division of operator company.'

'Interest for Operator. Commonly in percent.'

'American Petroleum Institute well number.'

'POSC Well status.'

'POSC well purpose.'

'POSC well fluid. The type of fluid being produced from or injected into a well facility.'

'POSC well direction. The direction of flow of the fluids in a well facility (generally, injected or produced, or some combination).'

'Date and time at which well was spudded.'

'Date and time at which well was plugged and abandoned.'

'Elevation of wellhead relative to a wellDatum.'

'A datum to which elevations and depths are referenced.'

'Elevation of ground level (land rigs).'

'Depth of water (not land rigs).'

'the 2D coordinates of the well surface point in one coordinate reference system. This is where the well crosses ground level on land and crosses the platform offshore.'

'Defines a reference point within the context of the well.'

'A coordinate reference system that was used within the context of this well.'

'A container element that contains elements that are common to all data objects.'

'A container element that can contain custom or user defined data elements.'

'Human recognizable context for the well test.'

'The date-time of well test.'

'The date-time of the previous well test.'

'The date-time of the last valid well test.'

'The reason for the well test: initial, periodic, revision.'

'The type of well production test.'

'The size of the opening in the flow choke at the wellhead.'

'A port on a Product Flow Unit that is represented by this test.'

'The Product Flow Unit represented by the port. This is defined within the Product Flow Model'

'The Product Flow Model that represents the above Product Flow Unit.'

'Defines the standard temperature and pressure to which all standard volumes in this report have been corrected. This applies to all elements whose name is suffixed by StdTempPres.'

'Data from a fluid level test.'

'Data from a production test.'

'Data from an injection test.'

'A container element that contains elements that are common to all data objects.'

'A container element that can contain custom or user defined data elements.'

'Human recognizable context for the wellbore.'

'General information about a wellbore.'

'A collector for completion strings.'

'A collector for wellbore intervals.'

'A collector for well tests.'

'A container element that can contain custom or user defined data elements. This is intended for adding new objects that are a child of wellbore.'

'This is a pointer to the parent wellbore. No parent = starts from top.'

'Operator borehole number.'

'API suffix.'

'Government assigned number.'

'POSC wellbore status.'

'POSC wellbore purpose.'

'Type of wellbore.'

'POSC wellbore trajectory shape.'

'Date and time of wellbore kickoff.'

'True (\"true\" of \"1\") indicates that the wellbore has acheieved total depth. That is, drilling has completed. False (\"false\" or \"0\") indicates otherwise. Not given indicates that it is not known whether total depth has been reached.'

'The current measured depth of the borehole. If status is plugged, indicates the maximum depth reached before plugging.'

'The current true vertical depth of the borehole. If status is plugged, indicates the maximum depth reached before plugging.'

'Kickoff measured depth of the wellbore.'

'Kickoff true vertical depth of the wellbore.'

'Planned measured depth for the wellbore total depth.'

'Planned true vertical depth for the wellbore total depth.'

'Planned measured for the wellbore total depth - with respect to seabed.'

'Planned true vertical depth for the wellbore total depth - with respect to seabed.'

'Target days for drilling wellbore.'

'A container element that contains elements that are common to all data objects.'

'A container element that can contain custom or user defined data elements.'

'Human recognizable context for the wellbore interval.'

'The type of interval.'

'The date when the interval was created.'

'The date and time when the interval was created.'

'The measured depth at the top of the interval.'

'The measured depth at the base of the interval.'

'The true vertical depth at the top of the interval.'

'The true vertical depth at the base of the interval.'

'A description of the perforations in this interval.'

'Commonly specified for fraced intervals.'

'A description of a single fracturing stage.'

'A recording of a status with regard to the interval'

'An event associated with the interval.'

'A textual remark about the interval.'

'A container element that contains elements that are common to all data objects.'

'A container element that can contain custom or user defined data elements.'