WITSML (Wellsite Information Transfer Standard Markup Language) is the oil and gas industry's standard protocol for transferring wellsite data between service providers, operators, and third-party applications. Developed and maintained by the Energistics consortium, WITSML provides a common data model and transport mechanism that enables real-time and historical drilling data to flow seamlessly between systems that would otherwise be incompatible. First released in 2000, WITSML has become the universal language for drilling data exchange, with adoption by every major service company and operator worldwide.
How It Works
Data Objects
WITSML defines a comprehensive hierarchy of data objects that represent the full lifecycle of well construction:
- Well — The top-level object containing well identification, location, and reference data.
- Wellbore — A specific borehole within a well. Supports sidetracks and multilaterals.
- Log — Depth-indexed or time-indexed measurement data (MWD surveys, LWD logs, surface parameters).
- Trajectory — The directional survey path of the wellbore, including stations with MD, inclination, azimuth, and calculated coordinates.
- MudLog — Geological data including lithology, gas readings, and cuttings descriptions.
- Tubular — Drill string and BHA component descriptions with dimensions and properties.
- BhaRun — Operational data for a specific BHA run, including footage, hours, and reason pulled.
- Risk — Operational risk events and observations.
- FluidsReport — Drilling fluid properties and treatments.
- OpsReport — Operational summaries similar to DDR data.
Version History
- WITSML 1.3.1 — Widely deployed legacy version. SOAP-based web services. Still in production at many operators.
- WITSML 1.4.1 — Added data objects (attachment, changelog) and improved store interface. Most broadly adopted version in active use today.
- WITSML 2.0 / ETP — Major architectural shift. Replaces SOAP with the Energistics Transfer Protocol (ETP), a WebSocket-based streaming protocol that supports real-time data push with significantly lower latency. Uses the common OSDU-aligned data model.
Data Transfer Mechanisms
- WITSML Store — A server-side repository that clients query using SOAP calls (GetFromStore, AddToStore, UpdateInStore, DeleteFromStore). The store model is request-response.
- ETP (Energistics Transfer Protocol) — The modern streaming protocol. Supports publish-subscribe patterns, enabling real-time data push from wellsite to office at sub-second latency. ETP uses Avro serialization for efficiency.
Why It Matters in Oil & Gas Operations
Before WITSML, every service company and operator used proprietary data formats, requiring expensive custom integrations for every data exchange. A single well might involve 5 to 15 service providers (directional, mud logging, fluids, wireline, cementing), each generating data in a different format. WITSML standardized this exchange, reducing integration costs and enabling real-time operational intelligence.
Today, WITSML is required in virtually every drilling services contract. Operators mandate that service companies deliver data via WITSML feeds to centralized operations centers, where it is consumed by monitoring, analytics, and reporting applications. The transition from WITSML 1.4.1 to ETP/WITSML 2.0 is currently underway, driven by the need for lower-latency streaming data in automated drilling systems.
How Netora Handles WITSML Data
Netora Drilling Intelligence is designed to ingest WITSML data feeds, mapping standard data objects — trajectories, logs, tubulars, and operational reports — into Netora's unified well model. This enables operators to consolidate data from multiple service providers into a single operational platform without manual data entry or custom integrations. Learn more about Netora Drilling Intelligence.