WITSML Data Schema Overview

Version 2.0

WITSML is data exchange standard for specifying and exchanging data for wells and well-related operations and objects, such as drilling, logging and mud logging. The main focus of WITSML is for the right-time, seamless flow of well data between operators and service companies to speed and enhance decision making.

WITSML Packages:



Attachment data object

  

The attachment object is used to provide a central location for finding a digital attachment that is associated with another WITSML wellbore related object. The attachment is captured in a base 64 binary type

  XSD
  Schema
 Attachment.xsd XSD


BhaRun data object

  

The bhaRun object is used to capture information about one run of the drill string in to and out of the hole. The drill string configuration is described in the tubular object. That is, one configuration may be used for many runs.

  XSD
  Schema
 BhaRun.xsd XSD


CementJob data object

  

The cementJob object is used to capture information about cementing operations which are undertaken to seal the annulus after a casing string has been run, to seal a lost circulation zone or to set a plug to support directional drilling operations or seal a well so that it may be abandoned. This object is uniquely identified within the context of one wellbore object.

  XSD
  Schema
 CementJob.xsd XSD


CementJobEvaluation data object

  

CementJobEvaluation is a top-level object that is used to record the testing and evaluation of a previously performed cement job.

  XSD
  Schema
 CementJob.xsd XSD


Channel data object

  

A channel object. Corresponds roughly to the LogCurveInfo structure in WITSML1411, and directly corresponds to the ChannelMetadataRecord structure in ETP. In historian terminology, a Channel corresponds directly to a tag. Channels are the fundamental unit of organization for WITSML logs.

  XSD
  Schema
 Log.xsd XSD


ChannelSet data object

  

A grouping of Channels with a compatible index for some purpose. As discussed earlier, each Channel effectively has its own index. By compatible index, we simply mean that all of the Channels are either in time or in depth using a common datum.

  XSD
  Schema
 Log.xsd XSD


CuttingsGeology data object

  

Container for Cuttings Lithology items. The mud logger at the wellsite takes regular samples of drilled cuttings while the well is being drilled and examines the cuttings to determine the rock types (lithologies) present in each sample. The cuttings samples will typically contain a mix of different lithologies in each sample because there may have been multiple rock types that were drilled within the sample depth interval and there can also be mixing of cuttings as they travel up the wellbore and are collected on the shakers. CuttingsGeology therefore will typically contain multiple lithology elements for each interval so that the percentages of each lithology in the sample along with the more detailed geological description can be recorded.

  XSD
  Schema
 WellboreGeology.xsd XSD


DepthRegImage data object

  

Information about the composition, layout, and depth registration of a digital image of a well log, typically a scanned image of a paper well log document. A depth registration is performed that provides digital depth references on the raster log image. The results of the calibration are stored in another file, separate from the image, which is commonly known as the depth registration file. The primary role of the depth registration file is to match pixels from the well log image with depth pixels represented in the wellbore.

  XSD
  Schema
 DepthRegImage.xsd XSD


DownholeComponent data object

  

Contains all the wellbore equipment in a well. Components are identified as to which wellbore they are in. This data-object covers the openhole boreholes, the strings of equipment, the components in each string and the details of these components, and the connections from these elements to the reservoir.

  XSD
  Schema
 DownholeComponent.xsd XSD


DrillReport data object

  

The drillReport object is used to capture a daily drilling report focused on reporting from the operator to partners or to a governmental agency. See the opsReport object for a similar report whose focus is service company to operator.

  XSD
  Schema
 DrillReport.xsd XSD


FluidsReport data object

  

The fluidsReport object is used to capture an analysis of the drilling mud. This object is uniquely identified within the context of one wellbore object.

  XSD
  Schema
 FluidsReport.xsd XSD


InterpretedGeology data object

  

Container for Interpreted Lithology items. These are manually entered per sample by the wellsite geologist or mud logger as an interpretation of the actual lithology sequence along the length of the wellbore by correlating the percentage lithologies observed in the cuttings samples along with other data (typically the drill rate and gamma ray curves), to estimate the location of the boundaries between the different lithology types. This analysis creates a sequence of individual lithologies along the wellbore. InterpretedGeology therefore will typically contain a single lithology element for each interval that captures the detailed geological description of the lithology.

  XSD
  Schema
 WellboreGeology.xsd XSD


Log data object

  

Primarily a container for one or more ChannelSets. Most of the information is now at the ChannelSet level. The concept of multiple ChannelSet in a single Log is significant change from WITSML v1.4.1.1 where each Log represented exactly one group of curves and their data.

  XSD
  Schema
 Log.xsd XSD


MudLogReport data object

  

Details of wellbore geology intervals, drilling parameters, chromatograph, mud gas, etc., data within an mdInterval.

  XSD
  Schema
 MudLogReport.xsd XSD


OpsReport data object

  

Captures a daily drilling report focused on reporting from the service company to the operator. See the drillReport for a similar data-object whose focus is operator to partner or to governmental agency.

  XSD
  Schema
 OpsReport.xsd XSD


Rig data object

  

The rig object is used to capture information about a drilling rig used to drill a wellbore. This object is uniquely identified within the context of one wellbore object.

  XSD
  Schema
 Rig.xsd XSD


RigUtilization data object

  

Rig Utilization Schema. Used to capture information related to the usage of a specific rig. For information unique to the rig itself, see the Rig object.

  XSD
  Schema
 Rig.xsd XSD


Risk data object

  

The risk object is used to provide a central location for capturing risk information about other well related objects.

  XSD
  Schema
 Risk.xsd XSD


ShowEvaluation data object

  

Container for Show Evaluation items. In a similar way to the InterpretedGeology, these are manually entered by the wellsite geologist or mud logger as an interpretation of the hydrocarbon show along the wellbore, based on the raw readings from one or more show analyses of individual show tests on cuttings samples.

  XSD
  Schema
 WellboreGeology.xsd XSD


StimJob data object

  

Captures a post job summary report about a stimulation (fracture) job. See the WITSML stimJob data-object Usage Guide for an overview of its intended usage.

  XSD
  Schema
 StimJob.xsd XSD


StimJobStage data object

  

Stage treated during a stimulation job.

  XSD
  Schema
 StimJob.xsd XSD


StimPerforationCluster data object

  

Information about a set of perforations. The assumption is that all perforations within a given set are created with the same device or method.

  XSD
  Schema
 StimJob.xsd XSD


SurveyProgram data object

  

Captures information about the nature, range, and sequence of directional surveying tools run in a wellbore for the management of positional uncertainty. This object is uniquely identified within the context of one wellbore object.

  XSD
  Schema
 SurveyProgram.xsd XSD


ToolErrorModel data object

  

The toolErrorModel object is used to define a surveying tool error model. This object is globally unique.

  XSD
  Schema
 ToolErrorModel.xsd XSD


ToolErrorTermSet data object

  

The toolErrorTermSet object is used to define a set of surveying tool error terms which may be utilized in a toolErrorModel. This object is globally unique.

  XSD
  Schema
 ToolErrorTermSet.xsd XSD


Trajectory data object

  

The trajectory object is used to capture information about a directional survey in a wellbore. It contains many trajectory stations to capture the information about individual survey points.

  XSD
  Schema
 Trajectory.xsd XSD


Tubular data object

  

The tubular object is used to capture information about the configuration of a drill string. See the bhaRun object for information about a use of this configuration.

  XSD
  Schema
 Tubular.xsd XSD


Well data object

  

A well is a boring in the Earth that has two main purposes: 1) Exploration of the subsurface to determine viability of economic development and production of hydrocarbons. 2) Production of hydrocarbons to the surface and conducting of a variety of operations and services for the safe and efficient operation of the wells. The well provides the key context for activities that occur in a well and its wellbores, and the resulting data generated, such as drilling and logging.

  XSD
  Schema
 Well.xsd XSD


WellCMLedger data object

  

This name is short for Well Construction and Maintenance Ledger. Contains details of events (which were defined in Section 2.1.4.1, page 13). Each event also has a pointer to elements of downhole components that the event changes. It can reference UID well and UID wellbore for each event, making this data-object able to represent events on multiple wells.

  XSD
  Schema
 WellCMLedger.xsd XSD


WellCompletion data object

  

The Well Completion data-object represents a “flow” or “stream” from the well (e.g., from a wellhead port) that is associated with a set of Wellbore Completions. When there is more than one such Wellbore Completion, the flows from them commingle in the well (the Wellbore Completions may be located in multiple wellbores). The Well Completion represents this commingled flow. It can be associated with business concept such as field, rights, etc.

  XSD
  Schema
 WellCompletion.xsd XSD


Wellbore data object

  

The wellbore object is used to capture the general information about a wellbore. This might sometimes be called a wellbore header. A wellbore represents the path from surface to a unique bottom-hole location.

  XSD
  Schema
 Wellbore.xsd XSD


WellboreCompletion data object

  

Each Wellbore Completion represents a flowing connection between wellbore and reservoir. It contains Contact Intervals, which reference the physical aspects of these connections detailed in downholeComponents.

  XSD
  Schema
 WellboreCompletion.xsd XSD


WellboreGeology data object

  

This is the former MudLog object. This includes lithologic information derived from cuttings encountered on a shaker screen at a site.

  XSD
  Schema
 WellboreGeology.xsd XSD


WellboreGeometry data object

  

Captures information about the configuration of the permanently installed components in a wellbore. It does not define the transient drilling strings (see the tubular data-object) or the hanging production components.

  XSD
  Schema
 WellboreGeometry.xsd XSD


WellboreMarker data object

  

Captures information about a geologic formation that was encountered in a wellbore.

  XSD
  Schema
 WellboreMarkers.xsd XSD


WellboreMarkerSet data object

  

The WellboreMarkerSet is a collection of WellboreMarkers.

  XSD
  Schema
 WellboreMarkers.xsd XSD


WitsmlAllObjects data object

  

This Package includes all individual Witsml data objects in 1 file, ideal for importing all of them using a common schema location.

  XSD
  Schema
 WitsmlAllObjects.xsd XSD


WitsmlCommon data object

  

Shared data-objects and related objects. These data-objects are shared across all packages in the WITSML schema.

  XSD
  Schema
 WitsmlCommon.xsd XSD


Copyright(c) 2003-2016 Energistics. All rights reserved.
WITSML� and the WITSML logo� are trademarks of Energistics.