PRODML™: |
Enabling Production Operations, Optimization, Reporting and Data Management for the Exploration and Production (E&P) Domain. |
Version: |
V1.3 |
Abstract |
This document provides an overview of the PRODML V1.3 data schema. |
Prepared by: |
Energistics and the PRODML SIG |
Date created: |
24-July-2014 |
Document Information |
|
DOCUMENT VERSION: |
V1.3 |
DATE: |
24-July-2014 |
Technical |
Color: R:210 G:124, B50 |
Language |
US English |
|
Amendment History |
|||
---|---|---|---|
Version |
Date |
Comment |
By |
1.3 |
24-July-2014 |
Final Release |
Joey Magsipok |
|
|
|
|
1.4 Key Terms used in this Document
2.3 Production Operation Report
2.5 Distributed Temperature Survey
3.2 WITSML Data Object Schema Design
3.3 WITSML Naming Convention in Schemas
PRODML is an industry initiative to provide open, non-proprietary, standard interfaces between software tools used to monitor, manage and optimize hydrocarbon production. The PRODML standards define web services that are described by service contracts, defined in WSDL and XML Schema, that can be implemented (server-side) by different software engineering technology and consumed by clients using different programming environments.
The PRODML Data Schemas define a collection of XML Schemas that are oriented towards reporting operations and near real-time operations.
This document provides a non-normative overview of the data schemas contained in this version. This document will list the data objects and will provide some insight to the file structure used in constructure used in constructing the schemas.
If there is any discrepancy between this document and the XSD files that use XML Schema syntax then the XSD files will prevail.
It is assumed that the reader is:
While the above is not necessary for reading this document, it is necessary for understanding each of the data schemas.
This document is organized as follows:
This material has been crafted to be consistent with the WITSML v1.4.0.0 Data Schema.
Further information requests and technical feedback may be addressed to Energistics.
The Product Flow Model can be used to define a directed graph of flow connections. The basic building block is a Unit which can be used to define the flow behavior of any facility (where the term facility represents any use of equipment to perform a function - somethimes called an asset) such as a separator, a wellhead, a valve, a flowline. It utilizes a general hierarchy of:
The network only describes how things are connected for the purposes of enabling fluid flow. It does not attempt to provide physical descriptions of the things that are connected. The ports may also represent measurement points within the network. The following are some general characteristics of the flow network model:
It is anticipated that the flow network can provide a mechanism to initialize and update software which processes information related to fluid flow. For example, a historian could initialize all of its internal SCADA equipment tags using aliases defined in the network. A simulator could initialize its internal model and could then monitor for mismatches between that internal model and the external site model. The "expected" information can allow an application to understand "where" to look for data. For example, controls exist in the network where facility parameters such as "block valve status" are be expected.
See the PowerPoint file for an overview of the Product Flow Model. This model defines how product could flow. The Product Volume Report is required in order to define how it actually flowed.
As part of the initial PRODML project, a Gas Lift Optimization scenario was developed in order to paper test the requirements of an optimization loop. As part of that exercise, a flow network picture was drawn in order to better visualize the scenario and to understand where measurement points existed within that scenario. In turn, a flow network was generated to match the scenario. See file PRODML_Gas_Lift_Scenario_Network_Construction.ppt for a pictorial view of this process. The example XML in the schema section represents this network.
The Product Volume Report can be used to define, for example, the daily volume of oil production at each wellhead. It can also define other characteristics (pressure, temperature, flow rate, concentrations, etc) associated with that wellhead. The report can be a simple one for something like one well or it can be a complex one for something like an offshore field with multiple platforms. It utilizes a general hierarchy of:
Parameter Sets allow time varying "usage" parameters to be defined for the facility. For example, a valve status may be toggled from "open" to "closed" to indicate that a well is offline.
The concept of the flow provides a high level view of a network where low level details are not needed. For example, a flow of "production" versus "gas-lift" provides an interoperable recognition of the relative location of information for a wellhead. The Flow may be associated with a Port in the Product Flow Model in order to support detailed analysis of a flow network. This can allow for unambiguous association of data with a complicated network.
This schema was originally designed to support production reporting (for the Norwegian OLF Partner Daily Reporting project) but has been extended and utilized by PRODML for retrieving historian-like data using a query interface that was patterned after the WITSML interface. The key extensions were:
The enumerated values are especially important because they provide the mechanism for mapping the data back to real world business terms. The key kinds are:
These kinds, in addition to the specific property type (e.g., pressure), allow an instance of data to be related to one "fluid flow" business term. The production reporting context utilizes several different Period Kinds while the production optimization context primarily focuses on an instant in time. In addition, qualifiers allow variations on a theme to be captured:
In order to support local exensions, the enumerated values have been moved to an external enumValues.xml or enumValuesProdml.xml which can be used to load the expected values rather than having to recompile the code. See the PRODML data qualifier spreadsheet for an example of terms that have been utilized to date. Future PRODML work will extend this list to include a broader context.
As part of the initial PRODML project, a Gas Lift Optimization scenario was developed in order to paper test the requirements of an optimization loop. As part of that exercise, data values were defined to correspond with the network described above. See file PRODML_Gas_Lift_Example_Data.xls for tabular view of the data. The example XML in the schema section represents the contents of this file. Note that this simplistic scenario assumes that measurements for several properties all occurred at the same time which is not particularly realistic.
The Production Operations Report can capture the activities related to production operations for a stated period (day, month, arbitrary, ...). It utilizes a general hierarchy of:
The report can represent one overall facility (e.g., a platform or field) but can include information from many related facilities.
The Well Test object captures the results of a well test. This object is derived from the well test part of the older POSC ProductionML schema. It utilizes a general hierarchy of:
Each Well Test Report can represent one and only one of: a Fluid Level Test, a Production Test or an Injection Test
Click here for an overview of Distributed Temperature Survey. There are 4 schemas: dtsInstalledSystem, dtsInstrumentBox, dtsMeasurement and fiberOpticalPath. The dtsInstalledSystem schema captures knowledge of the equipment installed in a wellbore. The dtsInstrumentBox schema is concerned with the equipment. The dtsMeasurement schema captures the knowledge that a measurement took place and where the data is stored. The fiberOpticalPath is concerned with the sequence and inventory of the fiber path.
The fluid analysis schema is split into three data objects: fluidSample, fluidAnalysis, fluidAnalysisResult. The presumed relationship between these objects is that a fluidSample may have many fluidAnalysis and a fluidAnalysis may have many fluidAnalysisResult. A fluidAnalysis points to its parent fluidSample. A fluidAnalysisResult points to its partent fluidAnalysis.
The time series data schema is designed to capture how a value varies with time. This provides a historian style view of the data but it utilizes a set of keyword-value pairs to define the business identity of the series.
The time series statistic schema is designed to capture derived statistics about time series data within a time interval. In a persistent data store, it represents a view of the time series and cannot be added, updated or deleted.
The wftRun schema is designed to capture information from one run of a wireline formation test (WFT).
The report schema is a special schema that is only intended to be used with the Energistics Aggregate Specification. It will provide a report style context to a collection of other objects. That is, it will provide the who, what, where, when and why information for that collection. An example might be a monthly production report which contains an productionOperation object, a productVolume object, many wellTest objects and many fluidAnalysisResult objects along with their required fluidSample and fluidAnalysis objects. This is not a normal data object because it does not contain a plural root element. It also does not contain a unique identifier because it is not intended to recur.
The aggregate schema is a special schema that is intended to be used for transporting a collection of other data objects within a context. This schema is not specific to PRODML and can also be used to transport WITSML data objects. It is intended to replace the older composite schema. A complex reporting scenario might make use of the aggregate to compose information content from a variety of data objects. A DTS aggregate might contain the well, wellbore, dtsInstalledSystem, dtsMeasurement and related wellLogs for the survey. This could also be uesd for something like collecting together all data related to one well or one field.
The Wellsite Information Transfer Standard Markup Language (WITSML) is a standard for sending well site information in an XML document format between business partners. These PRODML schemas are crafted to be conformant to the design characteristics of WITSML version 1.4.0. XML schemas are used to define the content of an XML document. This section provides an overview of the Data Schema design. The PRODML specification consists of a set of independent data object schemas. A data object schema defines a set of data that can be transmitted within a single XML document. Data object schemas contain attributes, elements, and included component sub-schemas.
Component schemas may be in separate XML schema files, but do not represent complete data objects (becasue they do not contain global elements). A component schema may be included by more than one data object schema. All component schemas are prefixed with (cs_). Each component schema file generally defines one type that has the same name as the file name. While the normative schema utilizes multiple files, the PRODML Web Services will utilize derived schemas which are packaged with all components of a schema in one file.
An attribute group file (attgrp_uid.xsd) is used to define a unique identifier (uid) attribute for all recurring container elements. A container element is an element that contains other elements. The uid attribute is optional but is required within the context of a WITSML server. This is the equivalent of a RDBMS system generated primary key.
Low level simplistic types are defined in the following files. Each file defines many types. Each component schema file must directly or indirectly include file typ_dataTypes.xsd. If a component schema includes another component schema then it will be indirectly including typ_dataTypes.xsd.
The typ_catalog.xsd file contains enumerations that are considered to be relatively static and should not require frequent changes. However for some data the list of recognized values may change relatively frequently. For this type of data the values are enumerated in files enumValues.xml or enumValuesProdml.xml.
The unit of measure conversion information is defined in file witsmlUnitDict.xml. Abbreviations used within the WITSML schemas are documented here.
Since all XML documents can only have one root level element and there are situations where it is necessary to send multiple occurrences of a data object in a single XML document (e.g.; multiple wellTests), a pluralized version of the data object name was established as the schema root element. That is, the object name followed by an "S" (e.g.; productVolumes). In some cases, this leads to incorrect pluralization, but is required to order to meet the requirements of the WITSML API which generates root tag names based on the data object name. One component schema is included in all plural data object schemas:
The unique identifiers (uid) for data objects are always defined as attributes at the singular data object name level (i.e., not the plural).
A WITSML type can be one of four kinds; a definition only with possibly a restricted size specified, a definition with enumerated values that are permitted, a reference to a component schema and a reference to a element group schema. While not really a type, the element group schemas allow the same elements to be used in multiple different contexts. In order, to help identify which type is being referenced, the following naming convention is used.
This release includes the following data object schemas, component schemas and element group schemas. A non-normative spreadsheet view of the content of the schemas is available in an Excel file.
Schemas | Links to Documents | |
---|---|---|
XSD Schema |
XML Document |
|
obj_aggregate.xsd | XSD | XML |
Schemas | Links to Documents | |||
---|---|---|---|---|
XSD Schema |
XML Document |
|||
obj_dtsInstalledSystem.xsd | XSD | XML | ||
grp_dtsInstalledSystem.xsd | XSD | |||
cs_dtsCalibration.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_commonData.xsd | XSD | |||
cs_extensionAny.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_customData.xsd | XSD |
Schemas | Links to Documents | |||
---|---|---|---|---|
XSD Schema |
XML Document |
|||
obj_dtsInstrumentBox.xsd | XSD | XML | ||
grp_dtsInstrumentBox.xsd | XSD | |||
cs_instrument.xsd | XSD | |||
cs_dtsEquipment.xsd | XSD | |||
cs_businessAssociate.xsd | XSD | |||
cs_personName.xsd | XSD | |||
cs_generalAddress.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_businessAssociate.xsd | XSD | |||
cs_personName.xsd | XSD | |||
cs_generalAddress.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_dtsCalibration.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_dtsPatchCord.xsd | XSD | |||
cs_commonData.xsd | XSD | |||
cs_extensionAny.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_customData.xsd | XSD |
Schemas | Links to Documents | |||
---|---|---|---|---|
XSD Schema |
XML Document |
|||
obj_dtsMeasurement.xsd | XSD | XML | ||
grp_dtsMeasurement.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_dtsMeasurementTrace.xsd | XSD | |||
cs_logDataTrace.xsd | XSD | |||
cs_logData.xsd | XSD | |||
cs_dtsInterpretationLogSet.xsd | XSD | |||
cs_dtsInterpretationData.xsd | XSD | |||
cs_logDataInterpretation.xsd | XSD | |||
cs_logData.xsd | XSD | |||
cs_commonData.xsd | XSD | |||
cs_extensionAny.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_customData.xsd | XSD |
Schemas | Links to Documents | |||
---|---|---|---|---|
XSD Schema |
XML Document |
|||
obj_fiberOpticalPath.xsd | XSD | XML | ||
grp_fiberOpticalPath.xsd | XSD | |||
cs_fiberOpticalPathInventory.xsd | XSD | |||
cs_fiberOpticalPathSegment.xsd | XSD | |||
cs_fiberCommon.xsd | XSD | |||
cs_dtsEquipment.xsd | XSD | |||
cs_businessAssociate.xsd | XSD | |||
cs_personName.xsd | XSD | |||
cs_generalAddress.xsd | XSD | |||
cs_fiberRefractiveIndex.xsd | XSD | |||
cs_fiberOneWayAttenuation.xsd | XSD | |||
cs_fiberConveyance.xsd | XSD | |||
cs_interventionConveyance.xsd | XSD | |||
cs_permanentCable.xsd | XSD | |||
cs_fiberControlLine.xsd | XSD | |||
cs_fiberPumpActivity.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_fiberTurnaround.xsd | XSD | |||
cs_fiberCommon.xsd | XSD | |||
cs_dtsEquipment.xsd | XSD | |||
cs_businessAssociate.xsd | XSD | |||
cs_personName.xsd | XSD | |||
cs_generalAddress.xsd | XSD | |||
cs_fiberSplice.xsd | XSD | |||
cs_fiberCommon.xsd | XSD | |||
cs_dtsEquipment.xsd | XSD | |||
cs_businessAssociate.xsd | XSD | |||
cs_personName.xsd | XSD | |||
cs_generalAddress.xsd | XSD | |||
cs_fiberConnection.xsd | XSD | |||
cs_fiberCommon.xsd | XSD | |||
cs_dtsEquipment.xsd | XSD | |||
cs_businessAssociate.xsd | XSD | |||
cs_personName.xsd | XSD | |||
cs_generalAddress.xsd | XSD | |||
cs_fiberTerminator.xsd | XSD | |||
cs_fiberCommon.xsd | XSD | |||
cs_dtsEquipment.xsd | XSD | |||
cs_businessAssociate.xsd | XSD | |||
cs_personName.xsd | XSD | |||
cs_generalAddress.xsd | XSD | |||
cs_fiberOpticalPathNetwork.xsd | XSD | |||
cs_productFlowModel.xsd | XSD | |||
cs_productFlowExternalReference.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_productFlowNetwork.xsd | XSD | |||
cs_productFlowlExternalPort.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_productFlowUnit.xsd | XSD | |||
cs_productFlowExpectedUnitProperty.xsd | XSD | |||
cs_productFlowQualifierExpected.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_relativeCoordinate.xsd | XSD | |||
cs_productFlowPort.xsd | XSD | |||
cs_connectedNode.xsd | XSD | |||
cs_productFlowQualifierExpected.xsd | XSD | |||
cs_productFlowExpectedPortProperty.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_productFlowChangeLog.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_productFlowNetworkPlan.xsd | XSD | |||
cs_productFlowChangeLog.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_fiberPathDefect.xsd | XSD | |||
cs_fiberFacilityMapping.xsd | XSD | |||
cs_fiberFacilityMappingPart.xsd | XSD | |||
cs_fiberFacilityWell.xsd | XSD | |||
cs_fiberFacilityPipeline.xsd | XSD | |||
cs_businessAssociate.xsd | XSD | |||
cs_personName.xsd | XSD | |||
cs_generalAddress.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_fiberOTDR.xsd | XSD | |||
cs_fiberOTDRInstrumentBox.xsd | XSD | |||
cs_instrument.xsd | XSD | |||
cs_dtsEquipment.xsd | XSD | |||
cs_businessAssociate.xsd | XSD | |||
cs_personName.xsd | XSD | |||
cs_generalAddress.xsd | XSD | |||
cs_businessAssociate.xsd | XSD | |||
cs_personName.xsd | XSD | |||
cs_generalAddress.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_businessAssociate.xsd | XSD | |||
cs_personName.xsd | XSD | |||
cs_generalAddress.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_commonData.xsd | XSD | |||
cs_extensionAny.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_customData.xsd | XSD |
Schemas | Links to Documents | |||
---|---|---|---|---|
XSD Schema |
XML Document |
|||
obj_fluidAnalysis.xsd | XSD | XML | ||
grp_fluidAnalysis.xsd | XSD | |||
cs_commonData.xsd | XSD | |||
cs_extensionAny.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_customData.xsd | XSD |
Schemas | Links to Documents | |||
---|---|---|---|---|
XSD Schema |
XML Document |
|||
obj_fluidAnalysisResult.xsd | XSD | XML | ||
grp_fluidAnalysisResult.xsd | XSD | |||
cs_fluidResultDataQuality.xsd | XSD | |||
cs_fluidResultComposition.xsd | XSD | |||
cs_fluidResultSaturationTest.xsd | XSD | |||
cs_fluidResultSaturationTestStep.xsd | XSD | |||
cs_fluidResultConstantCompositionExpansionTest.xsd | XSD | |||
cs_fluidResultVolumeReference.xsd | XSD | |||
cs_fluidResultCceTestStep.xsd | XSD | |||
grp_fluidResultCommonTestGroup.xsd | XSD | |||
cs_fluidResultStockTank.xsd | XSD | |||
cs_fluidResultPhaseComposition.xsd | XSD | |||
cs_fluidResultCompositeComposition.xsd | XSD | |||
cs_fluidResultConstantVolumeDepletionTest.xsd | XSD | |||
cs_fluidResultVolumeReference.xsd | XSD | |||
cs_fluidResultCvdTestStep.xsd | XSD | |||
grp_fluidResultCommonTestGroup.xsd | XSD | |||
cs_fluidResultStockTank.xsd | XSD | |||
cs_fluidResultPhaseComposition.xsd | XSD | |||
cs_fluidResultCompositeComposition.xsd | XSD | |||
cs_fluidResultDifferentialLiberationTest.xsd | XSD | |||
cs_fluidResultVolumeReference.xsd | XSD | |||
cs_fluidResultDifferentialLiberationTestStep.xsd | XSD | |||
grp_fluidResultCommonTestGroup.xsd | XSD | |||
cs_fluidResultStockTank.xsd | XSD | |||
cs_fluidResultPhaseComposition.xsd | XSD | |||
cs_fluidResultCompositeComposition.xsd | XSD | |||
cs_fluidResultJCurveTest.xsd | XSD | |||
cs_fluidResultVolumeReference.xsd | XSD | |||
cs_fluidResultJCurveTestStep.xsd | XSD | |||
grp_fluidResultCommonTestGroup.xsd | XSD | |||
cs_fluidResultStockTank.xsd | XSD | |||
cs_fluidResultPhaseComposition.xsd | XSD | |||
cs_fluidResultCompositeComposition.xsd | XSD | |||
cs_fluidResultTransportPropertiesTest.xsd | XSD | |||
cs_fluidResultTransportTestStep.xsd | XSD | |||
grp_fluidResultCommonTestGroup.xsd | XSD | |||
cs_fluidResultStockTank.xsd | XSD | |||
cs_fluidResultPhaseComposition.xsd | XSD | |||
cs_fluidResultCompositeComposition.xsd | XSD | |||
cs_fluidResultSeparatorTest.xsd | XSD | |||
cs_fluidResultVolumeReference.xsd | XSD | |||
cs_fluidResultSeparatorTestStep.xsd | XSD | |||
grp_fluidResultCommonTestGroup.xsd | XSD | |||
cs_fluidResultStockTank.xsd | XSD | |||
cs_fluidResultPhaseComposition.xsd | XSD | |||
cs_fluidResultCompositeComposition.xsd | XSD | |||
cs_fluidResultContaminant.xsd | XSD | |||
cs_commonData.xsd | XSD | |||
cs_extensionAny.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_customData.xsd | XSD |
Schemas | Links to Documents | |||
---|---|---|---|---|
XSD Schema |
XML Document |
|||
obj_fluidSample.xsd | XSD | XML | ||
grp_fluidSample.xsd | XSD | |||
cs_commonData.xsd | XSD | |||
cs_extensionAny.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_customData.xsd | XSD |
Schemas | Links to Documents | |||
---|---|---|---|---|
XSD Schema |
XML Document |
|||
obj_productFlowModel.xsd | XSD | XML | ||
grp_productFlowModel.xsd | XSD | |||
cs_productFlowExternalReference.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_productFlowNetwork.xsd | XSD | |||
cs_productFlowlExternalPort.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_productFlowUnit.xsd | XSD | |||
cs_productFlowExpectedUnitProperty.xsd | XSD | |||
cs_productFlowQualifierExpected.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_relativeCoordinate.xsd | XSD | |||
cs_productFlowPort.xsd | XSD | |||
cs_connectedNode.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_productFlowQualifierExpected.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_productFlowExpectedPortProperty.xsd | XSD | |||
cs_productFlowQualifierExpected.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_productFlowChangeLog.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_productFlowNetworkPlan.xsd | XSD | |||
cs_productFlowChangeLog.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_commonData.xsd | XSD | |||
cs_extensionAny.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_customData.xsd | XSD |
Schemas | Links to Documents | |||
---|---|---|---|---|
XSD Schema |
XML Document |
|||
obj_productVolume.xsd | XSD | XML | ||
grp_productVolume.xsd | XSD | |||
cs_businessAssociate.xsd | XSD | |||
cs_personName.xsd | XSD | |||
cs_generalAddress.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_geographicContext.xsd | XSD | |||
cs_offshoreLocation.xsd | XSD | |||
cs_northSeaOffshore.xsd | XSD | |||
cs_productVolumeBusinessUnit.xsd | XSD | |||
cs_productVolumeBusinessSubUnit.xsd | XSD | |||
cs_productVolumeBusinessOwnershipShare.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_productVolumeBusinessAccountInfo.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_productVolumeFacility.xsd | XSD | |||
cs_datedComment.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_productVolumeParameterSet.xsd | XSD | |||
cs_curveDefinition.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_productVolumeParameterValue.xsd | XSD | |||
cs_curveData.xsd | XSD | |||
cs_productVolumeAlert.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_productVolumeFlow.xsd | XSD | |||
cs_productVolumeRelatedFacility.xsd | XSD | |||
grp_commonPropertiesProductVolume.xsd | XSD | |||
cs_volumeValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_flowRateValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_productVolumePortDifference.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_densityValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_productVolumeProduct.xsd | XSD | |||
cs_refProductFlow.xsd | XSD | |||
grp_commonPropertiesProductVolume.xsd | XSD | |||
cs_volumeValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_flowRateValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_productVolumePortDifference.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_densityValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_productVolumeComponentContent.xsd | XSD | |||
grp_commonPropertiesProductVolume.xsd | XSD | |||
cs_volumeValue.xsd | XSD | |||
cs_flowRateValue.xsd | XSD | |||
cs_productVolumePortDifference.xsd | XSD | |||
cs_densityValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_productVolumePeriod.xsd | XSD | |||
grp_commonPropertiesProductVolume.xsd | XSD | |||
cs_volumeValue.xsd | XSD | |||
cs_flowRateValue.xsd | XSD | |||
cs_productVolumePortDifference.xsd | XSD | |||
cs_densityValue.xsd | XSD | |||
cs_productVolumeComponentContent.xsd | XSD | |||
grp_commonPropertiesProductVolume.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_productVolumeBalanceSet.xsd | XSD | |||
cs_productVolumeDestination.xsd | XSD | |||
cs_productVolumeBalanceDetail.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_productVolumeAlert.xsd | XSD | |||
cs_datedComment.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_datedComment.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_datedComment.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_commonData.xsd | XSD | |||
cs_extensionAny.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_customData.xsd | XSD |
Schemas | Links to Documents | |||
---|---|---|---|---|
XSD Schema |
XML Document |
|||
obj_productionOperation.xsd | XSD | XML | ||
grp_productionOperation.xsd | XSD | |||
cs_businessAssociate.xsd | XSD | |||
cs_personName.xsd | XSD | |||
cs_generalAddress.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_geographicContext.xsd | XSD | |||
cs_offshoreLocation.xsd | XSD | |||
cs_northSeaOffshore.xsd | XSD | |||
cs_productionOperationInstallationReport.xsd | XSD | |||
cs_productionOperationHSE.xsd | XSD | |||
cs_productionOperationSafety.xsd | XSD | |||
cs_datedComment.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_productionOperationWeather.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_productionOperationActivity.xsd | XSD | |||
cs_productionOperationLostProduction.xsd | XSD | |||
cs_productionOperationThirdPartyProcessing.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_productionOperationWaterCleaningQuality.xsd | XSD | |||
cs_datedComment.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_productionOperationShutdown.xsd | XSD | |||
cs_datedComment.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_productionOperationAlarm.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_productionOperationMarineOperation.xsd | XSD | |||
cs_datedComment.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_productionOperationCargoShipOperation.xsd | XSD | |||
cs_datedComment.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_productionOperationOperationalComment.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_commonData.xsd | XSD | |||
cs_extensionAny.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_customData.xsd | XSD |
Schemas | Links to Documents | |||
---|---|---|---|---|
XSD Schema |
XML Document |
|||
obj_report.xsd | XSD | XML | ||
cs_businessAssociate.xsd | XSD | |||
cs_personName.xsd | XSD | |||
cs_generalAddress.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_geographicContext.xsd | XSD | |||
cs_offshoreLocation.xsd | XSD | |||
cs_northSeaOffshore.xsd | XSD | |||
cs_customData.xsd | XSD |
Schemas | Links to Documents | |||
---|---|---|---|---|
XSD Schema |
XML Document |
|||
obj_timeSeriesData.xsd | XSD | XML | ||
grp_timeSeriesData.xsd | XSD | |||
cs_customData.xsd | XSD |
Schemas | Links to Documents | |||
---|---|---|---|---|
XSD Schema |
XML Document |
|||
obj_timeSeriesStatistic.xsd | XSD | XML | ||
grp_timeSeriesStatistic.xsd | XSD | |||
cs_timeSeriesThreshold.xsd | XSD | |||
cs_commonData.xsd | XSD | |||
cs_extensionAny.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_customData.xsd | XSD |
Schemas | Links to Documents | |||
---|---|---|---|---|
XSD Schema |
XML Document |
|||
obj_wellTest.xsd | XSD | XML | ||
grp_wellTest.xsd | XSD | |||
cs_wellContext.xsd | XSD | |||
cs_wellDatum.xsd | XSD | |||
cs_refWellWellbore.xsd | XSD | |||
cs_refWellWellboreRig.xsd | XSD | |||
cs_location.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_wellTestValidationOperation.xsd | XSD | |||
cs_wellTestFluidLevelTest.xsd | XSD | |||
cs_wellTestProductionTestData.xsd | XSD | |||
cs_wellTestInterval.xsd | XSD | |||
cs_wellTestWellheadData.xsd | XSD | |||
cs_wellTestTestVolume.xsd | XSD | |||
cs_wellTestFluidRate.xsd | XSD | |||
cs_wellTestBottomholeData.xsd | XSD | |||
cs_wellTestElectricSubmersiblePumpData.xsd | XSD | |||
cs_wellTestPointData.xsd | XSD | |||
cs_wellTestSeparatorData.xsd | XSD | |||
cs_wellTestCumulative.xsd | XSD | |||
cs_wellTestProductionTestResults.xsd | XSD | |||
cs_wellTestTestVolume.xsd | XSD | |||
cs_wellTestFluidRate.xsd | XSD | |||
cs_wellTestInjectionTestData.xsd | XSD | |||
cs_wellTestInterval.xsd | XSD | |||
cs_wellTestCumulative.xsd | XSD | |||
cs_wellTestInjectionTestResults.xsd | XSD | |||
cs_wellTestTestVolume.xsd | XSD | |||
cs_wellTestFluidRate.xsd | XSD | |||
cs_commonData.xsd | XSD | |||
cs_extensionAny.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_customData.xsd | XSD |
Schemas | Links to Documents | |||
---|---|---|---|---|
XSD Schema |
XML Document |
|||
obj_wftRun.xsd | XSD | XML | ||
grp_wftRun.xsd | XSD | |||
cs_wftStation.xsd | XSD | |||
cs_wftEvent.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_wftTest.xsd | XSD | |||
cs_wftTestResult.xsd | XSD | |||
cs_wftTestData.xsd | XSD | |||
cs_wftCurveSection.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_wftInOutParameter.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_wftInOutParameter.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_wftResultRef.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_wftSampleAcquisition.xsd | XSD | |||
cs_wftTestResult.xsd | XSD | |||
cs_wftTestData.xsd | XSD | |||
cs_wftCurveSection.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_wftInOutParameter.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_wftInOutParameter.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_wftResultRef.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_wftTestData.xsd | XSD | |||
cs_wftCurveSection.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_wftInOutParameter.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_wftTestResult.xsd | XSD | |||
cs_wftTestData.xsd | XSD | |||
cs_wftCurveSection.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_wftInOutParameter.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_wftInOutParameter.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_wftResultRef.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_wftTestResult.xsd | XSD | |||
cs_wftTestData.xsd | XSD | |||
cs_wftCurveSection.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_wftInOutParameter.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_wftInOutParameter.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_wftResultRef.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_commonData.xsd | XSD | |||
cs_extensionAny.xsd | XSD | |||
cs_extensionNameValue.xsd | XSD | |||
cs_customData.xsd | XSD |
Copyright(c) 2006-2014 Energistics. All rights reserved. Energistics®, POSC®, Epicentre®, WITSML™, PRODML™, RESQML™, Upstream Standards. Bottom Line Results.®, The Energy Standards Resource Centre® and their logos are trademarks or registered trademarks of Energistics. Access, receipt, and/or use of these documents and all Energistics materials are generally available to the public and are specifically governed by the Energistics Product Licensing Agreement at http://www.energistics.org.