WITSML - Monthly Production Report - NPD Profile The root container for all WITSML data. This schema is not designed for use with the WITSML API. Rather it captures the logical model represented by the API queriable objects. As such it can represent all data in a server or it can represent data outside the context of a server. The data in the API objects have been incorporated into a normal XML hierarchy of well/wellbore. The plural API root elements have essentially been renamed to "xxxSet". The content of the well and wellbore API objects has been captured in "generalInformation" elements. The realtime object is not included because it is considered to be a transient server concept. The trajectoryStation object is not included because it is redundant to the data in trajectory. Information about the XML message instance. A collector for product volume reports. A single product volume report. 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. 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. 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 collection of events that can document the history of the data. The owner of the data. The audit records what happened to the data, to produce the data that is in this file. It consists of one or more events. An event type captures the basic information about an event that has affected the data. The date on which the event took place. The party responsible for the event. A free form comment that can further define the event that occurred. The current document version. The non-contextual content for a product volume report. Unique identifier for the product volume report. The non-contextual content of a WITSML Product Volume object. 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 month that the report represents. A facility for which product information is being reported. WITSML - Report Facility Component Schema. The name of the facility. The name can be qualified by a naming system. This also defines the kind of facility. Reports a flow of a product. Unique identifier for the Product Volume Facility. WITSML - Product Volume Flow Component Schema. Indicates the type of flow that is being reported. The type of flow is an indication of the overall source or target of the flow. A production flow has one or more wells as the originating source. An injection flow has one or more wells as the ultimate target. An import flow has an offsite source. An export flow has an offiste target. A consumption flow generally has a kind of equipment as a target. Qualifies the type of flow that is being reported. Unique identifier for the Product Volume Flow. Reports a product flow stream. WITSML - Product Volume Product Component Schema. The type of product that is being reported. Unique identifier for the Product Volume Product. The density of the product. The density of the product. The density of the product after it has been corrected to standard temperature and pressure. The volume of the product. The uncorrected volume of the product. A positive value for an inlet port indicates flow into the port. A negative value for an inlet port indicates flow out of the port. A positive value for an outlet port indicates flow out of the port. A negative value for an outlet port indicates flow into of the port. This convention is designed such that a positive sign indicates an expected condition based on the intended port direction while a negative sign indicates an anomolous condition. The volume of the fluid, corrected to standard conditions of temperature and pressure. The sign of the value should conform to the above description of volume. The mass of the product. The side of the contract this is a part of. The company share of the density of the product. The company share of the density of the product. The company share of the density of the product after it has been corrected to standard temperature and pressure. The company share of the volume of the product. The company share of the volume of the product. The company share of the volume of the product after it has been corrected to standard temperature and pressure. The company share of the mass of the product. The destination... . Defines qualifiers for type of flow. Indicates product characteristics that were allocated back to a well as opposed to being measured at the well. Indicates product volumes that were actually measured at the port. A single field. Defines the types of flows for volume reports. Stock at a facility. For a period that represents an event, the amount would represent the current amount of inventory. For other periods, the amount would represent the addition (positive value) or drawdown (negative value) over that period. For an individual storage facility (e.g., a tank), the amounts would represent that tank. For an overall facility, the amounts would represent all tanks. A period of one calendar month. Oil with water removed. Mixture of ethane, propane and butane with small quantities of heaver hydrocarbons. Partially liquid at atmospheric pressure. 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 floating point value between zero (inclusive) and one (inclusive) This value can be zero but cannot be negative. This value can not be greater than one. 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 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 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. The name of something within a naming system. The naming system within the name is (hopefully) unique. The version of the schema. The first three levels are fixed. The fourth level can vary to represent on the constraints defined in enumerations and XML loader files. 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 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). Year and month type in the format of YYYY-MM 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). 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. 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. This type disallows an "empty" double value. This type should not be used directly except to derive another type. 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 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'. 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 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 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 "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.