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 business associate describes any company, person, group, consultant, etc, which is associated within a context (e.g., a well). The information contained in this module is: (1) contact information, such as address, phone numbers, email, (2) alternate name, or aliases, and (3) associations, such as the business associate that this one is associated with, or a contact who is associated with this business associate. The name of the business associate. This can be the name of a person, business, group, etc. constraints:@minOccurs="1" The role of the business associate within the context. For example, "driller" or "operator", "lead agency - CEQA compliance" "regulatory contact", "safety contact". A business associate will generally have one role but the role may be called different things in different naming systems. constraints:@minOccurs="1" If the business associate is a person, this specifies the component names of the person. The alias is an alternate name of a business associate. It is generally associated with a naming system. An alias is not necessarily unique within the naming system. Note that address may occur more than once, because it may be necessary to give a physical address, a mailing address, or both. The various types of phone numbers may be given. The may be office or home, they may be a number for a cell phone, or for a fax, etc. Attributes of PhoneNumber declare the type of phone number that is being given. The email address may be home, office, or permanent. More than one may be given. The preferred method of being contacted within the context of this role. A pointer to another business associate that this business associate is associated with. The most common situation is that of an employee being associated with a company. But it may also be, for example, a work group associated with a university. A pointer to a business associate (generally a person) who serves as a contact for this business associate. The count of the number of personnel in a group. A general comment. This should not be used to carry semantic information. This is not intended to be machine interpretable. Unique identifier for the business associate. 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 general timestamped comment structure. The name of the person providing the comment. The role of the person providing the comment. This is the role of the person within the context of comment. The date and time where the comment begins to be valid. The date and time where the comment is no longer valid. The relevant comment. constraints:@minOccurs="1" The unique identifier of the recurring element. 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. An general address structure. This form is appropriate for most countries. The Name line of an address. If missing, use the Name of the business associate. The Street is a generic term for the middle lines of an address. They may be a street address, PO Box, Suite number, or any lines that come between the "name" and "city" lines. This may be repeated for up to four, ordered lines. constraints:@minOccurs="1" The City for the business associate's address constraints:@minOccurs="1" The GeneralAddress allows the choice of a State, Province, or County element. It is assumed that different elements would be appropriate in different countries. A user community should choose which element is appropriate in the various countries. constraints:@minOccurs="1" constraints:@minOccurs="1" constraints:@minOccurs="1" The Country may be included. Although this is optional, it is probably required for most uses. A postal code, if appropriate for the country. In the USA this would be the five or nine digit zip code. The type of address: mailing, physical, or both. The unique identifier of the recurring element. A geographic context of a report. The name of the country. The state of province within the country. The name of the field within whose context the report exists. An offshore context. An general comment that further explains the offshore location. A type of offshore location that captures the North Sea Offshore terminology. An optional, uncontrolled value, which may be used to describe the general area of offshore North Sea in which the point is located. The number or letter of the quadrant in the North Sea. constraints:@minOccurs="1" A lower case letter assigned if a block is subdivided. A generic type of offshore location. This allows an offshore location to be given by an Area Name, and up to four block names. A comment is also allowed. A general meaning of Area. It may be as general as 'UK North Sea' or 'Viosca Knoll'. The user community must agree on the meaning of this element. One to four block ID's, that can more tightly locate the object. The BlockID should be an identifying name or code. The user community must agree on the exact meaning of this element. constraints:@minOccurs="1" An offshore location using the North Sea Offshore terminology. constraints:@minOccurs="1" An general comment that further explains the offshore location. The components of a persons name. A name prefix. Such as, Dr, Ms, Miss, Mr, etc. The persons first name. constraints:@minOccurs="1" The persons middle name or initial name. The persons last or given name. constraints:@minOccurs="1" A name suffix. Such as Esq, Phd, etc. WITSML - Production Activity Component Schema. Infomation about a lost production. Infomation about a lost injection. Information about the contaminants in water, and the general water quality. Infomation about a shutdown event. Infomation about an alarm. Information about a marine operation. Information about a cargo operation. A comment about a kind of operation. The time of the operation can be specified. A structure to record informaion about a single alarm. The date and time when the alarms went off. The area where the alarm went off. The type of alarm that went off. The reason for the alarm going off. A general comment relevant for the alarm. The unique identifier of the recurring element. Infomation about a cargo ship operation. Name of the cargo vessel for the installation. The date and time that the vessel arrived. The date and time that the vessel left. Name of the captain of the vessel. the cargo identifier. The cargo batch number. Used if the vessel needs to temporarily disconnect for some reason (e.g., weather). Description of cargo on the vessel. Gross oil loaded to the ship during the report period. Gross oil includes BS and W. This volume has been corrected to standard conditions of temperature and pressure. Gross oil loaded to the ship in total during the operation. Gross oil includes BS and W. This volume has been corrected to standard conditions of temperature and pressure. Net oil loaded to the ship during the report period. Net oil excludes BS and W, fuel, spill and leaks. This volume has been corrected to standard conditions of temperature and pressure. Net oil loaded to the ship from the beginning of the month to the end of the reporting period. Net oil excludes BS and W, fuel, spill and leaks. This volume has been corrected to standard conditions of temperature and pressure. Density of the liquid loaded to the tanker. This density has been corrected to standard conditions of temperature and pressure. Density of the liquid loaded to the tanker. Reid vapor pressure of the liquid. Basic sediment and water is measured from a liquid sample of the production stream. It includes free water, sediment and emulsion and is measured as a volume percentage of the liquid. Salt content. The product formed by neutralization of an acid and a base. The term is more specifically applied to sodium chloride. A commnet about the operation. The unique identifier of the recurring element. WITSML - Operational Health, Safety and Environment Component Schema. the number of incidents of accidents and injuries that were reported. The amount of time since the most recent Lost Time Accident. The amount of time since the most recent accident prevention exercise. The amount of time since the most recent defined hazard and accident situation (Norwegian DFU). The number of medical treatments that have occurred. The number of system alarms that have occurred. The number of personnel safety introductions that have occurred. A textual description of safety considerations. Safety information at a specific installatino. Information about the weather at a point in time. The unique identifier of the recurring element. WITSML -Installation Report Component Schema The installation represented by this report. Total count of beds available on the installation. The count of personnel on a type of crew. One of the types is all personnel on board. The total cumulative amount of time worked during the reporting period. Commonly specified in units of hours. Note that a day unit translates to 24 hours worked. The total cumulative amount of time worked from the beginning of the month to the end of reporting period. Commonly specified in units of hours. Note that a day unit translates to 24 hours worked. The total cumulative amount of time worked from the beginning of the year to the end of reporting period. Commonly specified in units of hours. Note that a day unit translates to 24 hours worked. Health, Safety and Environmenal information. Production activities. The unique identifier of the recurring element. WITSML - Lost Production Component Schema. A estimated lost volume and the reason for the loss. The estimated amount of oil and gas lost due to third party processing at an installation. Infomation about a marine operation. The beginning date and time that the information represents. The ending date and time that the comment represents. A general comment on marine activity in the area Name of supply vessel for the installation. Name of standby vessel for the installation. Comment regarding the supply ship. Comment regarding the standby vessel. Report of any basket movement to and from the installation. A comment on a special event in the marine area. The unique identifier of the recurring element. WITSML - Operational Comments Component Schema. The kind of operation The beginning date and time that the comment represents. The ending date and time that the comment represents. A comment about the operation and/or the activities within the operation. The unique identifier of the recurring element. WITSML - Safety Component Schema. The mean time between safety incidents. The count of a type of safety issue. Safety related comment. The unique identifier of the recurring element. Infomation about a shutdown event. The name of the installation which was shut down. The name can be qualified by a naming system. This also defines the kind of facility. A general description of the shutdown with reason and other relevant information. The time the shutdown started. The time the shutdown ended. Downtime when the installation is unable to produce 100% of its capability. Estimated loss of oil deliveries because of the shutdown. This volume has been corrected to standard conditions of temperature and pressure. Estimated loss of gas deliveries because of the shutdown. This volume has been corrected to standard conditions of temperature and pressure. A description of main activities from time to time during the shutdown period. The unique identifier of the recurring element. Production losses due to Third Party Processing. The name of the installation which performed the processing. The name can be qualified by a naming system. This also defines the kind of facility. The estimated amount of oil lost. This volume has been corrected to standard conditions of temperature and pressure The estimated amount of gas lost. This volume has been corrected to standard conditions of temperature and pressure The unique identifier of the event. Information about the contaminants in water, and the general water quality. The values are measured from a sample, which is described below. Values measured from other samples should be given in different instances of the type. An identifier of the point from which the sample was taken. This is an uncontrolled string value, which should be as descriptive as possible. Total measured oil in the water after the water cleaning process, but before it is discharged from the installation. Total measured oil in the water after the water cleaning process, but before it is discharged from the installation The amount of ammonium found in the water sample. The amount of total organic carbon found in the water. The water is under high temperature and the carbon left is measured The amount of Fenol found in the water sample. The amount of Glycol found in the water sample. The pH value of the treated water. The pH value is best given as a value, with no unit of measure, since there are no variations from the pH. The temperature of the water before it is discharged. Total measured residual clorines in the water after the water cleaning process, but before it is discharged from the installation. Total measured Oxygen in the water after the water cleaning process, but before it is discharged from the installation. A measure of the cloudiness of water caused by suspended particles. A measure of the number of particles in water as measured by a coulter counter. Any comment that may be useful in describing the water quality. There can be multiple comments. The unique identifier of the recurring element. WITSML - Operations Weather Component Schema Date and time the information is related to. constraints:@minOccurs="1" Name of company that supplied the data. Atmospheric pressure. The Beaufort wind scale is a system used to estimate and report wind speeds when no measuring apparatus is available. It was invented in the early 19th Century by Admiral Sir Francis Beaufort of the British Navy as a way to interpret winds from conditions. Average temperature above ground for the period. Temperature of the atmosphere. Minimum temperature above ground. Temperature of the atmosphere. Maximum temperature above ground. A measure of the combined chilling effect of wind and low temperature on living things, also named chill factor, e.g., according to US weather service table, an air temperature of 30 degF with a 10 mi/h corresponds to a windchill of 22 degF. Sea temperature. Horizontal visibility. The direction from which the waves are coming, measured from true north. Average height of the waves. An average of the higher 1/3 of the wave heights passing during a sample period (typically 20 to 30 minutes). The maximum wave height. The elapsed time between the passing of two wave tops. The direction from which the wind is blowing, measured from true north. Wind speed. Type of precipitation. Amount of precipitation. Description of cloud cover. Height of cloud cover. Current speed. Azimuth of current. Comments and remarks. The unique identifier of the recurring element. The non-contextual content of a WITSML Production Operation object. 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 reporting period. If one value from a pair are given the both values must be given. The beginning date and time that the report represents. constraints:@minOccurs="1" The ending date and time that the report represents. constraints:@minOccurs="1" The beginning date that the report represents. constraints:@minOccurs="1" The ending date that the report represents. constraints:@minOccurs="1" 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 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. Information about a single productionOperation. 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 Production Operation Report. constraints:@minOccurs="1" The non-contextual elements for general Production Operation information. The name should be unique within the context of the overall 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. Unique identifier for the Production Operation Report. 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. This type disallows an "empty" short 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. The intended abstract supertype of all quantities that have a value with a unit of measure. The unit of measure is in the uom attribute of the subtypes. This type allows all quantities to be profiled to be a 'float' instead of a 'double'. 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 singular data objects. 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. A non-negative integer (zero based count or index) with a maximum vaulue of 32767 (2-bytes). This value cannot be negative. Kind of Address. The list of standard values is contained in the PRODML enumValues.xml file. The mailing address of a business associate or facility. The physical address - location - of a business associate or facility. Both the mailing address and the physical address. 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. What kind of email (or phone) is this? Is it a work phone? Or personal? Or is a permanent one? The list of standard values is contained in the PRODML enumValues.xml file. The phone number or email address is personal, and can probably be received at the business associates home. The phone number or email is a work number, which is subject to change if the business associate changes jobs. The phone number or email is permanent, which will still be valid if the person changes home or work locations. 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 preferred method of contacting a business associate. The list of standard values is contained in the PRODML enumValues.xml file. Postal mail at the business address. Business fax. Business email. Postal mail at the business address. Business voice phone. Mobile phone. Pager. Personal fax. Personal email. Postal mail at the personal address. Personal voice phone. 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. 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. One method of characterizing a phone number. The list of standard values is contained in the PRODML enumValues.xml file. The telephone number is a conventional number which is used for voice contact. The telephone number is exclusively used for receiving faxes. The telephone number is a mobile telephone, such as a cell phone. The telephone at this number is capable of voice communication and of receiving faxes. The telephone is connected directly to voice mail. A voice phone may lead a caller to voice mail. However this choice qualifies the phone type as being only voice mail. The telephone is intended only for pages. 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. A kind of facility (usage of equipment or material). The list of standard values is contained in the PRODML enumValues.xml file. A single block valve. A single bottomhole. A single choke. A single cluster. A single completion. A single compressor. A single lift gas controller. DEPRECATED: use "controller" instead. A single county. A single country. A single field. A single flowline. A single flow meter. A single lease. A single manifold. A single platform. A single pressure meter. Note that this represents the device and not the sensor itself. A single production processing facility. A single regulating valve. A single reservoir. A single separator. A single sleeve valve. This is a type of tubing valve which has a sliding sleeve to cover holes in the tubing. You cover all of the holes in order to close the valve. For configurations oriented toward production, the inlet is on the casing side and the outlet is on the tubing side. For injection, the reverse would be true. A single state or province. A single tank. A single temperature meter. Note that this represents the device and not the sensor itself. A single template. A single trunkline. A single tubing head within a wellhead. A single named group of wells. A single well, possibly with many wellbores (sidetracks). A single wellbore (sidetrack) within a well. A single wellhead for one well. See also "tubing head". A single 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. A commercial entity is an organisational construct through which the a group of organisations or facilities are grouped as if it were a single composite. xxxxxxxxxxxxxxxxxxxxxxx A ground that is an area above an oilfield. An area concept that is a grouping of two or more selcted petroleum fields for commercial reasons or other purposes. An area concept that is an area that forms part of a petroleum field. xxxxxxxxxxxxxxxxxxxxxxx A physical object that is an appliance involved in the extraction, production, transportation or storage of oil or gas. A regulatory agreement that gives the licensees excluding rights to investigate, explore and recover petroleum deposits within the geographical area and timeperiode stated in the agreement. A fluid conductor that consists of pipe, possibly also including pumps, valves, and control devices, intended for conveying liquids, gases, or finely divided solids. A system for the storage of gaseous, liquid and solid products. A physical object that is an industrial facility for the storage of oil and/or petrochemical products and from which these products are usually transported to end users or further storage facilities. A time period for a report. The list of standard values is contained in the PRODML enumValues.xml file. A period of one day. If the report does not represent one day then this represents the 24 hour period ending at the end of the report period. A period of one week. If the report does not represent one week then this represents the 7 times 24 hour period ending at the end of the report period. A period of one calendar month. A period of one gregorian year. A period from the beginning of the year to the end of the report period. A period from the beginning of the calendar month to the end of the report period. The average per day over the period from the beginning of the year to the end of the report period The average per day over the period from the beginning of the month to the end of the report period A period with no beginning that ends at the end of the report period. A period coinciding with the report period. A point in time coinciding with the start of report period. A point in time coinciding with the end of report period. The previous reporting period. For example, if the report period represents a day then the previous period represents the previous day. A point in time coinciding with midnight during the report period. This can be ambiguous if the report begins and ends at midnight - use report start/end instead. This cannot be used for a reporting period that is greater than 24 hours. A point in time coinciding with noon during the report period. This can be ambiguous if the report begins and ends at noon - use report start/end instead. This cannot be used for a reporting period that is greater than 24 hours. A point in time coinciding with 6 am during the report period. This can be ambiguous if the report begins and ends at 6 am - use report start/end instead. This cannot be used for a reporting period that is greater than 24 hours. A period in time that is all space of time within a day (24 hour period) starting at 06:00 AM and ending 06:00 AM next day. A period in time that is all space of time within a whole given month starting at 06:00 AM the first day and ending at 06:00 AM the first day of next month. A period in time that is all time within a period starting at 06:00 AM October 1st and ending at same date and time the following year. A period in time that is all space of time within a period starting at 06:00 AM October 1st ending at 06:00 AM at a given date. The type of personnel grouping. A count that is the number of persons from the catering contractor spending the night at the installation. A count that is the number of persons from other than operator spending the night at the installation. A count that is the number of persons visiting the installation but not spending the night at the installation. A count that is the number of persons from the drilling contractor spending the night at the installation. A count that is the number of persons from the operator normally working on the installation and spending the night there. A count that is the number of persons from the operator normally not working on the installation, but spending the night there. A count that is the number of persons from an unknown source normally not working on the installation, but spending the night there. A count of the total personnel on board. The type of operation for which general comments can be defined. Production operations. Well operations. Deviations from existing procedures and guidelines. Maintenance work. Construction work. Failure of a power station. Air traffic in the area. Other comment relevant for the production periods on the installation. Reason for lost production. Estimated loss of production due to equipment failure and maintenance topside. Estimated loss of production due to extended maintenance turnaround. Estimated loss of production due to extended maintenance turnaround on export terminal. Estimated loss of production due to preventive maintenance topside. Estimated loss of production due to planned maintenance turnaround. Estimated loss of oil production due to lost export due to marked product. Estimated loss of gas production due to lost export due to marked product. Estimated loss of production due to modification projects. Estimated loss of production due to operation mistakes reference. Estimated loss of production due to unspecified reasons. Estimated loss of production due to process and operation problems. Estimated loss of production due to total loss of production. Estimated loss of production due to regulatory reference. Estimated loss of production due to reservoir losses. Estimated loss of production due to well testing and logging. Estimated loss of production due to unavailable tanker storage. Estimated loss of production due to well equipment failure and maintenance. Estimated loss of production due to planned well operations. Estimated loss of production due to preventive maintenance on a well. Estimated loss of production due to weather conditions. Estimated loss of production due to Safety or Emergency requirements. Estimated loss of production due to strike or lock-out. Estimated loss of production due to 3rd party processing. Estimated total loss of production. Estimated loss of production due well problems. The type of safety issues for which a count can be defined. An incident resulted in an injured employee who required medical treatment and could not return to work the next day. An accident resulting in lost time from work . A type of accident that may challenge safety systems at a level much higher than expected.. xxxxxxxxxxxxxxx. xxxxxxxxxxxxxxx. xxxxxxxxxxxxxxx. xxxxxxxxxxxxxxx. xxxxxxxxxxxxxxx. xxxxxxxxxxxxxxx. An incident which, under different circumstances, could have caused injury, illness and/or major damage to/loss of assets, or harm to the environment or to a third party. xxxxxxxxxxxxxxx. xxxxxxxxxxxxxxx. xxxxxxxxxxxxxxx. Safe Job Analysis. xxxxxxxxxxxxxxx. xxxxxxxxxxxxxxx. xxxxxxxxxxxxxxx. xxxxxxxxxxxxxxx. xxxxxxxxxxxxxxx. xxxxxxxxxxxxxxx. 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 default is "inclusive". An email address with an attribute, used to "qualify" an email as personal, work, or permanent. Identifies a facility. The kind of facility. The naming system within which the name is unique. For example, API or NPD. If the facility is defined and instantiated within the context of a WITSML server, this is a pointer to the uid value of that object instance. A phone number with two attributes, used to "type" and "qualify" a phone number. The type would carry information such as fax, modem, voice, and the qualifier would carry information such as home or office. The kind of phone such as voice or fax. constraints:@use="required" Indicates whether the number is personal, business or both. The phone number extension. 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. The mnemonic of a log index curve plus the column index of the curve. The column index of the curve. constraints:@use="required" A representation of a list of xsd:string values, restricted to strings without embedded whitespace. A reference to a name in another node of the xml hierachy. This value represents a foreign key from one element to another. 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 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 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 naming system within the name is (hopefully) unique. A non-negative integer (zero based count or index) with a maximum value of 32767 (2-bytes). For items that represent "number of" something or a "sequential" count or index. This value can be zero but cannot be negative. An estimate wind strength based on the Beaufort Wind Scale. Values range from 0 (calm) to 12 (hurricane). A one based count of personnel on a type of crew. The type of crew for which a count is being defined. Unique identifier for the each XML node. A volume corrected to standard temperature and pressure. constraints:@use="required" Defines why the volume was lost. constraints:@use="required" A zero based count of a type of safety item. The type of safety issue for which a count is being defined. The type of period being reported by this count. constraints:@use="required" constraints:@use="required" constraints:@use="required" constraints:@use="required" constraints:@use="required" constraints:@use="required" constraints:@use="required" constraints:@use="required" constraints:@use="required" constraints:@use="required" constraints:@use="required"