WITSML - Common Data Component Schema An identifier to indicate the data originator. This identifies the server that originally created the object and thus most of the uids in the object (but not necessarily the uids of the parents). This is typically a url. When the data was created at the persistent data store. Last change of any element of the data at the persistent data store. The change time is not updated for a growing object while it is growing. The item state for the data object. Comments and remarks. WITSML - Custom or User Defined Element and Attributes Component Schema. Specify custom element, attributes, and types in the custom data area. Any element or attribute in any namespace. It is strongly recommended that all custom data definitions be added to a unique namespace. A schema to capture a set of data that is relevant for many exchange documents. It includes information about the file that was created, and high-level information about the data that is being exchanged within the file. An identifier for the document. This is intended to be unique within the context of the NamingSystem. constraints:@minOccurs="1" Zero or more alternate names for the document. These names do not need to be unique within the naming system. The date of the creation of the document. This is not the same as the date that the file was created. For this date, the document is considered to be the set of information associated with this document information. For example, the document may be a seismic binset. This represents the date that the binset was created. The FileCreation information would capture the date that the XML file was created to send or exchange the binset. A document class. Examples of classes would be a metadata classification or a set of keywords. The information about the creation of the exchange file. This is not about the creation of the data within the file, but the creation of the file itself. Information about the security to be applied to this file. More than one classification can be given. A free-form string that allows a disclaimer to accompany the information. A collection of events that can document the history of the data. The owner of the data. WITSML query parameters. An optional comment about the document. A structure for WITSML query parameters. The intent is to allow a query for all objects within an index range (whether or not the object is growing). These would typically be something like a daily report. The minimum start time for an object. This only applies to objects with a root level date and/or dateTime element(s). The objects may or not be growing objects but the See the API specification for behavior related to this query parameter. The maximum start time for an object. This only applies to objects with a root level date and/or dateTime element(s). See the API specification for behavior related to this query parameter. A block of information about the creation of the XML file. This is different than the creation of the data that is included within the file. The date and time that the file was created. constraints:@minOccurs="1" If appropriate, the software that created the file. This is a free form string, and may include whatever information is deemed relevant. The person or business associate that created the file. Any comment that would be useful to further explain the creation of this instance document. Information about the security classification of the document. This is intended as a documentation of the security so that the file will not inadvertently be sent to someone who is not allowed access to the data. This block also carries a date that the security classification expires. For example, a well log is confidential for a period of time, and then becomes open. All security classes are characterized by their classification systems. The security class in which this document is classified. Examples would be confidential, partner confidential, tight. The meaning of the class is determined by the System in which it is defined. The security classification system. This gives context to the meaning of the Class value. The date on which this security class is no longer applicable. A general comment to further define the security class. The audit records what happened to the data, to produce the data that is in this file. It consists of one or more events. constraints:@minOccurs="1" An event type captures the basic information about an event that has affected the data. The date on which the event took place. constraints:@minOccurs="1" The party responsible for the event. A free form comment that can further define the event that occurred. The instrument box used for distributed temperature surveys The date the instrument box was installed. The company that installed the instrument box in the wellbore measurement system. The date the instrument box was de-installed from the wellbore. The properties of the instrument box. The unique identifier of a container element. This attribute is generally required within the context of a WITSML server. There should be no assumption as to the semantic content of this attribute. This should only be used with recurring container types (i.e., maxOccurs greater than one). The value is only required to be unique within the context of the nearest recurring parent element. Calibration parameters vary from vendor to vendor, depending on the calibration method being used. This is a general type that allows a calibration date, business associate, and many name/value pairs. The date of the calibration The business associate that performed the calibration. This may be a standard protocol, or a software application. Attribute name is the name of the parameter. Optional attribute uom is the unit of measure of the parameter. The value of the element is the value of the parameter. Note that a string value may appear as a parameter. Any remarks that may be useful, regarding the calibration information. The unique identifier of a container element. This attribute is generally required within the context of a WITSML server. There should be no assumption as to the semantic content of this attribute. This should only be used with recurring container types (i.e., maxOccurs greater than one). The value is only required to be unique within the context of the nearest recurring parent element. Parameters are given by name/ value pairs, with optional uom. The parameter name and uom are attributes, and the value is the value of the element. The element value for which a match is requested. The unit of measure of the parameter value. The name of the parameter. constraints:@use="required" The optical fiber used for distributed temperature surveys A human understandable name for the fiber. This is used for identification of the instance. The mode of fiber. constraints:@minOccurs="1" Zero or more instances that allow other classifications to be assigned to the fiber. The type of coating on the fiber. The type of jacket covering the fiber. The inner diameter of the core, generally measured in microns (um). The diameter of the core plus the cladding, generally measured in microns (um). The diameter of the cable and all its sheathing, generally measured in microns (um). This is intended to be the diameter of the cable on the spool. The refractive index of the fiber. Also included is the frequency in Hz for which this refractive index is valid. There may be multiple instances of this element. The power loss (usually in decibels) per unit of length of the fiber. Also included is the frequency for which this loss is measured. There ay be multiple instances of this element. Additional parameters to define the fiber as a material. These should not be parameters to define the installation of the fiber in a well, or other system. This element should be used only if an appropriate parameter is not available as an element, or in the calibration operation. The spool number located on the particular spool. The spool number may contain alphanumeric characters. The length of the fiber on the spool when purchased. A fiber may go through several manufacturers for its various parts. The supplier is the final company in the chain that supplies the fiber to the end user. A fiber may go through several manufacturers for its various parts. The supplier is the final company in the chain that supplies the fiber to the end user. The model number (alphanumeric) that is used by the supplier to reference the type of fiber that is supplied to the user. Information about calibrations and quality checks that were performed on the cable at the factory. This is not to include calibrations that are run at installation time and at measurement time. A reference to a dtsInstalledSytem object that previously used the fiber. The unique identifier of a container element. This attribute is generally required within the context of a WITSML server. There should be no assumption as to the semantic content of this attribute. This should only be used with recurring container types (i.e., maxOccurs greater than one). The value is only required to be unique within the context of the nearest recurring parent element. A fiber installed in a "U" configuration has two end points that a cable may hook to. When making a measurement, it is useful to be able to say which end was hooked to the input from the instrument box. In order to do this, the fiber ends must be identified. The identifier is a name, along with a description to further aid the interpreter in determining which end was used as the input A name, unique within the context of the well, for an instrument box cable to hook to. constraints:@minOccurs="1" Any description of the node that may be useful in identifying the hookup. The unique identifier of a container element. This attribute is generally required within the context of a WITSML server. There should be no assumption as to the semantic content of this attribute. This should only be used with recurring container types (i.e., maxOccurs greater than one). The value is only required to be unique within the context of the nearest recurring parent element. The optical fiber used for distributed temperature surveys The date the fiber is installed. The company that installed the fiber in the wellbore. The date the fiber was de-installed from the wellbore. The diameter of the capillary tube into which one or more fibers will be installed. If the installation has fibers that go to different wellbores, only those fibers installed in the parent wellbore should be included in this instance. The properties of the fiber or fibers installed in the wellbore. A wrapper for multiple instances of the point in a well. This carries the information about one point constraints:@minOccurs="1" The instrument box used for distributed temperature surveys A name for the instrument box. This can be used to access the instrument box. The ultimate manufacturer of the instrument box. The date the manufacturing of the instrument box was completed. The type of instrument box used. An identification tag for the instrument box. A serial number is a type of identification tag however some tags contain many pieces of information. This structure just identifies the tag and does not describe the contents. The version of the software installed in the instrument box. Information about the calibration of the instrument box that was performed. This includes factory calibrations before shipping, and bench calibrations. This does not include calibrations made in preparation for taking measurements. Near distance of the oven from the beginning of the fiber. constraints:@minOccurs="1" Far distance of the oven from the beginning of the fiber. The temperature of the oven. constraints:@minOccurs="1" The cable used to test the instrument box. The offset setting applied to the instrument box based on the factory or bench calibration. The power loss over the length of the cable. Additional parameters to define the instrument box as a piece of equipment. These should not be parameters to define the installation or use of the box in the wellbore, or other system. This element should be used only if an appropriate parameter is not available as an element, or in the calibration operation. The unique identifier of a container element. This attribute is generally required within the context of a WITSML server. There should be no assumption as to the semantic content of this attribute. This should only be used with recurring container types (i.e., maxOccurs greater than one). The value is only required to be unique within the context of the nearest recurring parent element. Calibration parameters vary from vendor to vendor, depending on the calibration method being used. This is an extension of the general cs_dtsCalibration, and allows for specific parameters associated with an instrument box. The two additional parameters are the offset temperature calibration, and the slope calibration. These allow for a linear shift in temperature vs measurements. Additional offset and slope calibrations may be performed at measurement time. The date of the calibration The business associate that performed the calibration. This may be a standard protocol, or a software application. Attribute name is the name of the parameter. Optional attribute uom is the unit of measure of the parameter. The value of the element is the value of the parameter. Note that a string value may appear as a parameter. Any remarks that may be useful, regarding the calibration information. The temperature offset correction that is applied to the dts instrument box. The temperature slope correction that is applied to the dts instrument box. The unique identifier of a container element. This attribute is generally required within the context of a WITSML server. There should be no assumption as to the semantic content of this attribute. This should only be used with recurring container types (i.e., maxOccurs greater than one). The value is only required to be unique within the context of the nearest recurring parent element. The The power loss for one way travel of a beam of light, usually measured in decibels per unit length. It is necessary to include both the value (and its unit) and the wavelength. The wavelength varies with the refractive index, while the frequency remains constant. The wavelength given to specify this type is the wavelength in a vacuum (refractive index = 1). The value of the one way loss per unit of length. The usual uom is decibels per kilometre (dB/km), although this might vary depending on the calibration method used. constraints:@minOccurs="1" The frequency (and uom) for which the one-way loss is measured. The wavelength (and uom) for which the one-way loss is measured. The reported wavelength should be the wavelength of the light in a vacuum. The unique identifier of a container element. This attribute is generally required within the context of a WITSML server. There should be no assumption as to the semantic content of this attribute. This should only be used with recurring container types (i.e., maxOccurs greater than one). The value is only required to be unique within the context of the nearest recurring parent element. This records the result arrays, along with context information, from an Optical Time Domain Reflectometry (OTDR) run. The arrays will define the relative scattered power from the Rayleigh scattering vs distance along the fiber. The actual data values are recorded in a wellLog object, which is referenced in a subelement. The reason the OTDR test was run. The three main reasons are 'pre-installation', which is before the installation of the fiber; 'post-installation', which is used to validate a successful fiber installation; and 'DTS run', which is a quality check of the fiber prior to a DTS run. A fourth permitted value is 'other'. constraints:@minOccurs="1" The dateTime of the run. A reference to the well log used to record the table of data. constraints:@minOccurs="1" A pointer to the fiber connection node. If more than one node is available for a well/wellbore, this element is used to specify which node is connected to the instrument box. This name should correspond to the fiberEndPoint/name that is recorded in the installed system object. A general comment about the OTDR run. The unique identifier of a container element. This attribute is generally required within the context of a WITSML server. There should be no assumption as to the semantic content of this attribute. This should only be used with recurring container types (i.e., maxOccurs greater than one). The value is only required to be unique within the context of the nearest recurring parent element. The activity of pumping the fiber downhole. A name which can be used to reference the pumping activity. In general, a pumping activity does not have a natural name, so that this element will not be often used. The name of the InstalledFiberInstance that this activity relates to. The date of the pumping activity. The person in charge of the pumping activity. The company that performed the pumping activity. The type of fluid used in the pump. The type of fluid used in the control line. The direction of the pumping. The type of end seal on the fiber. The type of cable meter. The serial number of the cable meter. The date the cable meter was calibrated. True or False. Was a drift run performed? This element should be used to indicate if a drift run was performed or not, where the instance of the drift run (OTDR) is not available. If the OTDR is available, use the OTDRPerformed element to specify the OTDR instance. A reference to the OTDR that was run. If an OTDR was run, but there is not instance of the OTDR to reference, choose the wasDriftRunPerformed element, and set it to True. The length of the excess fiber that was removed. Information about the pumping activity, that is captured in the pump log. The unique identifier of a container element. This attribute is generally required within the context of a WITSML server. There should be no assumption as to the semantic content of this attribute. This should only be used with recurring container types (i.e., maxOccurs greater than one). The value is only required to be unique within the context of the nearest recurring parent element. The pump log row are elements defined in the sequence below. The speed of the cable. The length of fiber pumped into the wellbore. The operating pressure of the pump. The fluid used in the pumping operation. The temperature going into the wellbore. The temperature at the end of the operation Any general remarks about the pumping operation. The unique identifier of a container element. This attribute is generally required within the context of a WITSML server. There should be no assumption as to the semantic content of this attribute. This should only be used with recurring container types (i.e., maxOccurs greater than one). The value is only required to be unique within the context of the nearest recurring parent element. Data type supporting a pump log for DST fiber installation data. This is a row of the pump log table. constraints:@minOccurs="1" The refractive index of a material depends on the frequency or wavelength of the light. Hence it is necessary to include both the value (a unitless number) and the frequency or wavelength. The frequency will be a quantity type with a frequency unit, such as Hz, kHz, or MHz. The wavelength will be a quantity type with a length unit, such as m, cm, um, in, or ft. The value of the refractive index. constraints:@minOccurs="1" The frequency (and uom) for which the refractive index is measured. The wavelength (and uom) for which the refractive index is measured. The reported wavelength should be the wavelength of the light in a vacuum. The unique identifier of a container element. This attribute is generally required within the context of a WITSML server. There should be no assumption as to the semantic content of this attribute. This should only be used with recurring container types (i.e., maxOccurs greater than one). The value is only required to be unique within the context of the nearest recurring parent element. A set of points recorded during the installation process. The information can include the length along the fiber, the measured depth, and a type of point. The measured depth of the installed point of the fiber. This is optional, because the sender may want to record points that are outside the well. The length along the fiber, from the zero point, for this particular point. constraints:@minOccurs="1" The type of point that is being recorded. The unique identifier of a container element. This attribute is generally required within the context of a WITSML server. There should be no assumption as to the semantic content of this attribute. This should only be used with recurring container types (i.e., maxOccurs greater than one). The value is only required to be unique within the context of the nearest recurring parent element. WITSML - Equipment NameTag Schema The physical identification string of the equipment tag. constraints:@minOccurs="1" The format or encoding specification of the equipment tag. The tag may contain may different pieces of information and knowledge of that information is inherent in the specification. The "identification string" is a mandatory part of the information in a tag. constraints:@minOccurs="1" Identifies the general type of identifier on an item. If multiple identifiers exist on an item, a separate description set for each identifier should be created. For example, a joint of casing may have a barcode label on it along with a painted-on code and an RFID tag attached or embedded into the coupling. The barcode label may in turn be an RFID equipped label. This particular scenario would require populating five nameTags to fully describe and decode all the possible identifiers as follows: 'tagged' - RFID tag embedded in the coupling, 'label' - Serial number printed on the label, 'tagged' - RFID tag embedded into the label, 'label' - Barcode printed on the label, 'painted'- Mill number painted on the pipe body. An indicator of where the tag is attached to the item. This is used to assist the user in finding where an identifier is located on an item. This optional field also helps to differentiate where an identifier is located when multiple identifiers exist on an item. Most downhole components have a box (female thread) and pin (male thread) end as well as a pipe body in between the ends. Where multiple identifiers are used on an item, it is convenient to have a reference as to which end, or somewhere in the middle, an identifier may be closer to. Some items may have an identifier on a non-standard location, such as on the arm of a hole opener. 'other', by exclusion, tells a user to look elsewhere than on the body or near the ends of an item. Most non-downhole tools will use either 'body', 'other' or not specified as the location tends to lose value with smaller or non threaded items. When the tag was installed in or on the item. The name of the company that installed the tag. Reference to a manufacturers or installers installation description, code, or method. A comment or remark about the tag. The unique identifier of a container element. This attribute is generally required within the context of a WITSML server. There should be no assumption as to the semantic content of this attribute. This should only be used with recurring container types (i.e., maxOccurs greater than one). The value is only required to be unique within the context of the nearest recurring parent element. Data that represents a foreign key to a wellbore. The wellbore may be defined within the context of another well. A pointer the wellbore with which there is a relationship. constraints:@minOccurs="1" A pointer to the well that contains the wellboreReference. This is not needed unless the referenced wellbore is outside the context of a common parent well. A reference to a rig within a wellbore. The wellbore may be defined within the context of another well. This value represents a foreign key from one node to another. A pointer to the rig with which there is a relationship. constraints:@minOccurs="1" A pointer to the wellbore that contains the rigReference. This is not needed unless the referenced rig is outside the context of a common parent wellbore. A pointer to the well that contains the wellboreParent. This is not needed unless the referenced wellbore is outside the context of a common parent well. Within the context of a WITSML Server, this data should duplicate the equivalent information in the well object. Name of the field in which the well is located. An alias name associated with the well. If the wellName is associated with a naming system then it should be included in this list. A datum to which elevations and depths are referenced. Defines the datums associated with elevation, vertical depth and measured depth coordinates within the context of a well. The human understandable contextual name of the reference datum. The code value that represents the type of reference datum. This may represent a point on a device (e.g., kelly bushing) or it may represent a vertical reference datum (e.g., mean sea level). The name of the vertical reference datum in a particular naming system. This should only be specified if the above 'code' represents some variation of sea level. An optional short name (code) can also be specified. Specifying a well known datum is highly desired if the above code is a variant of sea level because sea level varies over time and space. An example would be to specify a name of 'Caspian Sea' with a code of '5106' in the 'EPSG' naming system. Since various activities may use different points as measurement datums, it is useful to characterize the point based on its usage. A well reference datum may have more than one such characterization. For example, it may be the datum used by the driller and logger for measuring their depths. Example usage values would be 'permanent','driller', 'logger' 'WRP' (well reference point) and 'SRP' (site reference point). A pointer to the wellbore that contains the reference datum. This should be specified if a measured depth is given. A pointer to the rig that contains the device used as a reference datum. The rig may be associated with a wellbore in another well (e.g., pattern drilling using a rig on a track). The gravity based elevation coordinate of this reference datum as measured from another datum. Positive moving upward from the elevation datum. An elevation should be given unless this is a vertical reference datum (e.g., sea level). The measured depth coordinate of this reference datum as measured from another datum. The measured depth datum should either be the same as the elevation datum or it should be relatable to the elevation datum through other datums. Positive moving toward the bottomhole from the measured depth datum. This should be given when a local reference is "downhole", such as a kickoff point or ocean bottom template, and the borehole may not be vertical. If a Depth is given then an Elevation should also be given. A contextual description of the well reference datum. True indicates that this is the default reference datum for measured depth coordinates. False or not given indicates that this is not the default reference datum. Measured depth coordinates that do not specify a datum reference should be assumed to be measured relative to this default reference datum. Only one reference datum may be designated as the default measured depth datum for each well. Values are "true" (or "1") and "false" ( or "0"). True indicates that this is the default reference datum for vertical depth coordinates. False or not given indicates that this is not the default reference datum. Vertical depth coordinates that do not specify a datum reference should be assumed to be measured relative to the default reference datum. Only one reference datum may be designated as the default vertical depth datum for each well. Values are "true" (or "1") and "false" ( or "0"). True indicates that this is the default reference datum for elevation coordinates. False or not given indicates that this is not the default reference datum. Elevation coordinates that do not specify a datum reference should be assumed to be measured relative to the default reference datum. Only one reference datum may be designated as the default elevation datum for each well. Values are "true" (or "1") and "false" ( or "0"). The unique identifier of a container element. This attribute is generally required within the context of a WITSML server. There should be no assumption as to the semantic content of this attribute. This should only be used with recurring container types (i.e., maxOccurs greater than one). The value is only required to be unique within the context of the nearest recurring parent element. The WITSML API mandated plural root element which allows multiple singular objects to be sent. The plural name is formed by adding an "s" to the singular name. Information about the XML message instance. Main wrapper for all the distributed temperature survey information about the installed system. Note that this can serve as a standalone object for messages that are not part of the WITSML server architecture. constraints:@minOccurs="1" Data object schema version. The fourth level must match the version of the schema constraints (enumerations and XML loader files) that are assumed by the document instance. constraints:@use="required" Human recognizable context for the well that contains the wellbore. constraints:@minOccurs="1" Human recognizable context for the wellbore that contains the installed system. constraints:@minOccurs="1" Human recognizable context for the dts. constraints:@minOccurs="1" The minimum date index contained within the object. The minimum and maximum indexes are server query parameters and will be populated with valid values in a "get" result. That is, all measurements for a well in the specified period defined by the min/max. See the WITSML API Specification appendix on "Special Handling" of growing objects for a description of the behavior related to this parameter. The maximum date index contained within the object. The minimum and maximum indexes are server query parameters and will be populated with valid values in a "get" result. See the WITSML API Specification appendix on "Special Handling" of growing objects for a description of the behavior related to this parameter. The definition of the "current date" index for this object. The current date index is a server query parameter which requests the selection of a single node from a recurring set (e.g., the data related to one point in a date series). That is, the "most recent" (at or before the specified date) installation for a well. See the WITSML API Specification appendix on "Special Handling" of growing objects for a description of the behavior related to this parameter. Contextual data about the well in which the system was installed. Is this a planned installation in a well, or has the installation already occurred. Note that the default value is 'false', which states that this is an actual installation. Information about the fiber used, and its installation. Information about the instrument box used, and its installation. The configuration of the fiber installation. Example values would be linear, linear with gauge, J, U. A fiber installed with a "U" configuration will have two ends available for hookup to an instrument box. In order to record which end is cabled to the instrument box on a particular measurement run, it is necessary to identify the two ends. This complex type allows a name and description for each end, so that it may be identified in a later use. This may also be useful when multiple fibers in multiple wellbores converge at the same wellhead. The length of the fiber installed in the wellbore. A table of values along the length along the fiber. Total light budget available for the installation. This is generally measured in decibels, and indicates the total power loss for two-way travel of the light in the installed fiber. The activity of pumping the fiber downhole This captures the data from the pre-installation and post-installation OTDR tests run on the fiber. A standard quality control program would include these two, but the schema allows for more than two if additional runs associated with the installation of the fiber are performed. OTDR runs associated with a measurement are given as a child of the measurementInformation element. Any calibration other than the ones explicitly given may be recorded here. This is a general calibration type, which is populated with name/value pairs. If an instrument box is changed, for example, but the fiber remains the same, this instance of installed fiber is given to record that change. This element refers to a previous installed fiber, on which this one is based. For example, the wellboreFiberSchematic is unchanged, and may be obtained from the previous instance of installed fiber that is referenced here. 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. Unique identifier for the well. This uniquely represents the well referenced by the (possibly non-unique) nameWell. Unique identifier for the wellbore. This uniquely represents the wellbore referenced by the (possibly non-unique) nameWellbore. The unique identifier of a container element. This attribute is generally required within the context of a WITSML server. There should be no assumption as to the semantic content of this attribute. This should only be used with recurring container types (i.e., maxOccurs greater than one). The value is only required to be unique within the context of the nearest recurring parent element. This type disallows an "empty" boolean value. This type should not be used directly except to derive another type. All boolean types should be derived from this type rather than using xsd:boolen. This type disallows an "empty" dateTime value. This type should not be used directly except to derive another type. All dateTime types should be derived from this type rather than using xsd:dateTime. This type disallows an "empty" date value. This type should not be used directly except to derive another type. All dateTime types should be derived from this type rather than using xsd:dateTime. This type disallows an "empty" double value. This type should not be used directly except to derive another type. The intended abstract supertype of all strings. This abstract type allows the control over whitespace for all strings to be defined at a high level. This type should not be used directly except to derive another type. Replace tab, line feed and carriage return with a space, collapse contiguous sequences of spaces to a single space and then remove leading and trailing spaces. The empty string is not allowed. This constraint conbined with the whiteSpace collapse constraint means that a blank value is not allowed. constraints:@minLength="1", This defines the maximum acceptable length of a string that can be stored in a data base. This value should be the smallest "maximum size of a variable length character type" in commonly used DBMSs. This is the maximum size of a VARCHAR2 in Oracle 8. The intended abstract supertype of all user assigned human recognizable contextual name types. There should be no assumption that (interoperable) semantic information will be extracted from the name by a third party. This type of value is generally not guaranteed to be unique and is not a candidate to be replaced by an enumeration. The intended abstract supertype of all locally unique identifiers. The value is not intended to convey any semantic content (e.g., it may be computer generated). The value is only required to be unique within a context in a document (e.g., defined via key and keyref). There is no guarantee that the same data in multiple documents will utilize the same uid value unless enforced by the source of the document (e.g., a document server). Spaces are not allowed. The intended abstract supertype of all comments or remarks intended for human consumption. There should be no assumption that semantics can be extracted from the field by a computer. Neither should there be an assumption that any two humans will interpret the information in the same way (i.e., it may not be interoperable). The intended abstract supertype of all enumerated "types". This abstract type allows the maximum length of a type enumeration to be centrally defined. This type should not be used directly except to derive another type. It should also be used for uncontrolled strings which are candidates to become enumerations at a future date. The intended abstract supertype of all "units of measure". This abstract type allows the maximum length of a UOM enumeration to be centrally defined. This type is abstract in the sense that it should not be used directly except to derive another type. The type of local or permanent reference datum for vertical gravity based (i.e., elevation and vertical depth) and measured depth coordinates within the context of a well. This list includes local points (e.g., kelly bushing) used as a datum and vertical reference datums (e.g., mean sea level). casing flange: A flange affixed to the top of the casing string used to attach production equipment. crown valve derrick floor ground level kelly bushing rotary bushing rotary table sea floor Lowest Astronomical Tide. The lowest tide level over the duration of the National Tidal Datum Epoch (19 years). Mean Sea Level - A tidal datum. The arithmetic mean of hourly heights observed over the National Tidal Datum Epoch (19 years). Mean Higher High Water - A tidal datum. The average of the higher high water height of each tidal day observed over the National Tidal Datum Epoch (19 years). Mean High Water - A tidal datum. The average of all the high water heights observed over the National Tidal Datum Epoch (19 years). Mean Lower Low Water - A tidal datum. The average of the lower low water height of each tidal day observed over the National Tidal Datum Epoch (19 years ). Mean Low Water - A tidal datum. The average of all the low water heights observed over the National Tidal Datum Epoch (19 years). Mean Tide Level - A tidal datum. The arithmetic mean of mean high water and mean low water. Same as half-tide level. kickoff point The value is not known. This value should not be used in normal situations. All reasonable attempts should be made to determine the appropriate value. Use of this value may result in rejection in some situations. The meaning of the endpoint for min/max query parameters on "growing objects". The list of standard values is contained in the PRODML enumValues.xml file. The endpoint of the range is inclusive of the specified range value. hat is, a node index value which matches the specified range value is considered to be within the range. The endpoint of the range is exclusive of the specified range value. That is, a node index value which matches the specified range value is considered to be outside the range. The endpoint of the range may be extended to the first encountered value if an exact value match is not found. That is, if a node index value does not match the specified range value then the next smaller value (on minimum end) or larger value (on maximum end) in the index series should be used as the endpoint. Basically, this concept is designed to support interpolation across an undefined point. The endpoint of the range may be extended to the first encountered value if the interval is overlapped with the index interval. That is, if a node index value does not match the specified range value then the next smaller value (on minimum end) or larger value (on maximum end) in the index series should be used as the endpoint. This concept is designed to select ALL nodes whose index interval overlap with the query range. The value is not known. This value should not be used in normal situations. All reasonable attempts should be made to determine the appropriate value. Use of this value may result in rejection in some situations. The mode of a Distributed Temperature Survey (DTS) fiber. The list of standard values is contained in the PRODML enumValues.xml file. A single, narrow, core of constant refractive index, surrounded by glass cladding. The core diameter is comparable to a wave length of the light (about 5 um). The core has a graded refractive index. The core is generally about 50um in diameter. The fiber mode is neither singlemode or multimode. The value is not known. This value should not be used in normal situations. All reasonable attempts should be made to determine the appropriate value. Use of this value may result in rejection in some situations. These values represent the state of a WITSML object. Actual data measured or entered at the well site. Model data used for "what if" calculations. A planned object. That is, one which is expected to be executed in the future. The value is not known. This value should not be used in normal situations. All reasonable attempts should be made to determine the appropriate value. Use of this value may result in rejection in some situations. The type of Distributed Temperature Survey (DTS) fiber point. The list of standard values is contained in the PRODML enumValues.xml file. A point at which a fiber is physically, and semi-permanently, connected to another length of fiber. A point at which a cable connector is installed, which allows the fiber to be connected to another instrument or fiber length. The end of the fiber. If a U-geometry is used, and a connector is at both ends, the connector classification should be used rather than the end of fiber classification. The deepest point of the installed fiber in a well. This is a valid value for fiber installations that do NOT turn around at the bottom (J- and U-type installations). The point in the turn-around-sub at which measured depth stops increasing and begins decreasing. This is a valid value for fiber installations of the J- and U- type only. The start of the fiber. If appropriate, the connector classification should be used instead of this classification. The point on the fiber at which it enters the oven. The point on the fiber at which it exits the oven. The oven exit point should be closer to the wellbore than the oven entry point. A downhole point on the fiber at which a gauge is attached. The connector between the laser head and the optical fiber. The oven within or near the DTS instrument box which maintains a length of fiber at a reference temperature. Container in which ends of lengths of fiber are joined. The device at which a fiber originating at the instrument box is joined to a fiber installed in a wellbore. This is a recommended location at which LengthAlongFiber and measuredDepth in the wellbore are correlated The device at the base of the wellhead to which the production tubing is attached. This is a recommended location at which LengthAlongFiber and measuredDepth in the wellbore are correlated. The top-most point at which the fiber intersects the PBR (polished bore receptacle). For J- and U- installations, on the upward portion of the fiber, this is the point at which it leaves the pbf. The top of the electrical submersible pump (ESP). This is the minimum measured depth point of the pump. The base of the electrical submersible pump (ESP). This is the maximum measured depth point of the pump. Temperature measuring device at the wellhead independent of the optic fiber sensor. The point which is the minimum measured depth of a completion zone. The point which is the maximum measured depth of a completion zone. The value is not known. This value should not be used in normal situations. All reasonable attempts should be made to determine the appropriate value. Use of this value may result in rejection in some situations. Defines the locations where an equipment tag might be found.. The list of standard values is contained in the WITSML enumValues.xml file. The body of the equipment. For tubular components this specifies a location toward the middle of the component. The female threaded end of a device. The male threaded end of a device. This, by exclusion, tells a user to look elsewhere than on the body or near the ends of a component. The value is not known. This value should not be used in normal situations. All reasonable attempts should be made to determine the appropriate value. Use of this value may result in rejection in some situations. Defines the specifications for creating equipment tags.. The list of standard values is contained in the WITSML enumValues.xml file. RFID - Electronic Product Code, 64 bit. RFID - Electronic Product Code, 96 bit. RFID - Merrick Systems Rapid Component Identification. Barcode - 1995, Uniform Symbology Specification Barcode - 1995, Uniform Symbology Multi Row Specification Barcode - 1996, International Symbology Specification - MaxiCode Barcode - Composite Symbology Magnetic - ISO/IEC 7811 Magnetic - "Modified Frequency Modulation for Magnetic Stripes" standard developed by AIM Inc. Serial number contains a code which does not require any further knowledge of an encoding scheme to manipulate or process. The identifier is the only information in the "tag". The value is not known. This value should not be used in normal situations. All reasonable attempts should be made to determine the appropriate value. Use of this value may result in rejection in some situations. Defines the mechanisms for attaching an equipment tag to an item.. The list of standard values is contained in the WITSML enumValues.xml file. Independent identification components attached or embedded to a larger component for purposes of identification of the larger component. Tags typically use electronic, radio or sound based technologies and that require a special non-optical device to read them. Radio Frequency Identification (RFID tags) are of this type, as are some magnetic and sound based identification technologies. An optical label attached to a component. The label may be glued, riveted or attached by some other method and may contain a serial number, barcode or other optically recognized information. Note that a label may possibly have a combination of identifiers associated with it, such as a serial number, a barcode and an embedded RFID identifier. This would generate three nameTags for the one physical label, two of type 'label' for the barcode and serial number and one of type 'tagged' for the RFID identifier. Identification technologies where the intrinsic properties of the component to be identified contain the identification information and no other unique code has been added. For example, some magnetic identification technologies use grooves machined into a component. Some components may also be identified, for example, by their individual sonic signature or optical profile. An identification code physically stamped into the base material of the component to be identified. Note that if a serial number is stamped into a label attached to a component, 'labeled' should be used and not 'stamped'. Stamped identifiers can wear off but can not fall off. Painted or stenciled on the material. Temporary identification codes marked with grease pencil, chalk, or such. The value is not known. This value should not be used in normal situations. All reasonable attempts should be made to determine the appropriate value. Use of this value may result in rejection in some situations. The reason an Optical Time Domain Reflectometry (OTDR) test was run within a Distributed Temperature Survey (DTS). The list of standard values is contained in the PRODML enumValues.xml file. The OTDR was run prior to installing the fiber in the well. The OTDR was run after installating the fiber in the well in order to quality check the installation process. The OTDR was run in conjunction with a DTS run. This is generally immediately preceding the timed run. The OTDR was run for another reason. The value is not known. This value should not be used in normal situations. All reasonable attempts should be made to determine the appropriate value. Use of this value may result in rejection in some situations. The element value for which a match is requested. The element value for which a match is requested. A type with a classType attribute. This allows a user to give a classification of something, and to specify the type of classification that it is. There is no control over the class values, or the class types. The element value for which a match is requested. This identifies the classification system to which the class belongs. A timestamp value used for min/max query parameters related to "growing objects". The meaning of the endpoint of an interval can be modified by the endpoint attribute. The element value for which a match is requested. The default is "inclusive". A date value used for min/max query parameters related to "growing objects". The meaning of the endpoint of an interval can be modified by the endpoint attribute. The element value for which a match is requested. The default is "inclusive". Values of "true" (or "1") and "false" (or "0"). A julian date. A date with the time of day and an optional time zone. While the time zone is optional, it is strongly advised that the zone always be specified in each date time value. A unitless quantity. This should not be confused with a dimensionless measure. A reference to a name in another node of the xml hierachy. This value represents a foreign key from one element to another. The element value for which a match is requested. A reference to the unique identifier (uid attribute) in the node referenced by the name value. This attribute is required within the context of a WITSML server. A reference to a wellDatum in the current well. This value must match the uid value in a WellDatum. This value represents a foreign key from one element to another. This is an exception to the convention that a foreign key must utilize both a human contextual name and a uid value. For messages outside the context of a server then this value will commonly match the value of the name of the wellDatum (e.g., 'KB') if uids are not not used in that context. This was a compromise in order to allow the coordinate structures to be simple and still be usable both within the context of a server and outside the context of a server. A user assigned human recognizable contextual name of something. There should be no assumption that (interoperable) semantic information will be extracted from the name by a third party. This type of value is generally not guaranteed to be unique and is not a candidate to be replaced by an enumeration. A comment or remark intended for human consumption. There should be no assumption that semantics can be extracted from this field by a computer. Neither should there be an assumption that any two humans will interpret the information in the same way (i.e., it may not be interoperable). A textual description of something. A community assigned human recognizable name. This type of value is intended to be unique and is generally a candidate to be constrained to an enumerated list. A unit of measure acronym from the POSC unit of measure file. A locally unique identifier. The value is not intended to convey any semantic content (e.g., it may be computer generated). The value is only required to be unique within a context in a document (e.g., defined via key and keyref). There is no guarantee that the same data in multiple documents will utilize the same uid value unless enforced by the source of the document (e.g., a document server). A reference to the unique identifier of another element. This value represents a foreign key from one element to another. The value should match the value of an attribute of type uidString. The version of the schema. The first three levels are fixed. The fourth level can vary to represent the constraints defined in enumerations and XML loader files. The name of something within a naming system. The element value for which a match is requested. The naming system within the name is (hopefully) unique. The name of something within a mandatory naming system with an optional code. The element value for which a match is requested. The naming system within the name is unique. constraints:@use="required" A unique (short) code associated with the name. A measured depth coordinate in a wellbore. Positive moving from the reference datum toward the bottomhole. All coordinates with the same datum (and same uom) can be considered to be in the same Coordinate Reference System and are thus directly comparable. The element value for which a match is requested. The unit of measure of the quantity value. constraints:@use="required" A pointer to the reference datum for this coordinate value as defined in WellDatum. This value is assumed to match the uid value in a WellDatum. If not given then the default WellDatum must be assumed. The units of measure that are valid for measured depths in a wellbore. meter International Foot US Survey Foot A vertical (gravity based) elevation coordinate within the context of a well. Positive moving upward from the reference datum. All coordinates with the same datum (and same uom) can be considered to be in the same Coordinate Reference System and are thus directly comparable. The element value for which a match is requested. The unit of measure of the quantity value. If not given then the default unit of measure of the explicitly or implicitly given datum must be assumed. constraints:@use="required" A pointer to the reference datum for this coordinate value as defined in WellDatum. If not given then the default WellDatum must be assumed. The units of measure that are valid for vertical gravity based coordinates (i.e., elevation or vertical depth) within the context of a well. meter International Foot US Survey Foot British Foot 1865 The element value for which a match is requested. Indexes things with the same name. That is the first one, the second one, etc. constraints:@use="required" The element value for which a match is requested. constraints:@use="required" The element value for which a match is requested. constraints:@use="required" The element value for which a match is requested. constraints:@use="required" The element value for which a match is requested. constraints:@use="required" The element value for which a match is requested. constraints:@use="required"