WITSML from a Technical Perspective

WITSML Subcomponents

The WITSML standard consists of a set of subcomponents, each playing a specific role in managing and transferring well data. These components include data objects, transfer protocols, and development tools that together create an integrated ecosystem for data exchange. According to Energistics, WITSML version 2.1 (released in May 2022) includes over 20 standard data objects designed to cover various aspects of well operations. These data objects, defined based on XML schemas (XSD), enable the recording and transfer of complex information such as drilling data, well completion, and geology.

Some of the most important WITSML data objects include:

• Well: Includes general well information, such as geographical location, owner, and technical specifications.
• Wellbore: Data related to the wellbore structure, such as depth and path.
• Trajectory: Well path information, including 3D coordinates and deviations.
• WellLog: Data recorded by well sensors, such as electrical resistivity, rock density, and porosity.
• MudLog: Drilling mud logging data, such as the chemical and physical properties of the mud.
• BhaRun: Information about drill bit and bottom-hole assembly operations.
• CementJob: Data related to well cementing operations.
• DrillReport: Daily drilling reports, including activities and events.

These data objects are designed to cover all aspects of well operations and enable data exchange between different systems. For example, the "WellLog" object can store data from MWD (Measurement While Drilling) and LWD (Logging While Drilling) sensors, while the "Trajectory" object is used for tracking the well path in directional wells.

In addition to data objects, WITSML includes the Energistics Transfer Protocol (ETP), which replaces the SOAP-based web services in older versions. ETP enables data streaming with low latency and lower bandwidth consumption, which is crucial for real-time data transfer in drilling projects. Energistics also provides tools such as the Standards DevKit, which includes XML data samples and .NET packages for developing WITSML-based software. These tools help developers design and test WITSML-compatible systems.

The WITSML components also include the Energistics Common Technical Architecture (CTA), which ensures coordination between WITSML, PRODML (for production data), and RESQML (for reservoir modeling). This architecture enables data integration across the entire oilfield lifecycle, helping companies combine well data with production and reservoir data.

Implementation Methods in the Software Domain

Implementing the WITSML standard in the software domain requires the use of modern technologies and software development methods that are compatible with the needs of the oil and gas industry. According to Energistics, for new software development, WITSML should be implemented with version 2.1 and ETP version 1.2, as these versions offer higher performance and interoperability. The methods for implementing WITSML in software include design, development, testing, and deployment stages, which are explained below.

System Design: WITSML implementation begins with analyzing project requirements. Developers must determine which WITSML data objects (such as Well, WellLog, or Trajectory) are needed for the specific project. Energistics recommends using XML schemas (XSD) to define data structures. These schemas act as standard contracts and ensure that data is compatible between different systems. For example, a drilling management software might use the "DrillReport" object to generate daily reports.

Software Development: The development of WITSML-based software is typically done using programming languages such as C#, Java, or Python. Energistics provides the Standards DevKit tool, which includes .NET packages for generating WITSML objects. This tool allows developers to integrate their code with WITSML data objects. For example, a program can convert well sensor data into XML format and transfer it to a central server via ETP. The ETP protocol supports data streaming and has replaced the SOAP web services in older WITSML versions.

Integration with Existing Systems: WITSML is designed to integrate with existing systems such as data analysis software, asset management systems, and cloud platforms. For example, WITSML data can be imported into software like DrillWorks or CoViz 4D to perform geological analysis or reservoir simulation. This integration requires the use of ETP-based APIs that enable low-latency data exchange.

Testing and Validation: Energistics offers Certification Programs to ensure that WITSML-based software is compatible with the standard. Developers can use the XML data samples provided by Energistics (such as the data donated by Statoil in 2016) to test their software. This data simulates real-world scenarios such as drilling and mud logging data. Testing includes verifying data correctness, compatibility with XML schemas, and ETP protocol performance.

Deployment and Maintenance: After development and testing, the software is deployed in an operational environment. WITSML supports deployment in both on-premise and cloud environments. For example, WITSML data can be transferred to the OSDU platform for large-scale storage and analysis. Software maintenance involves updating with new versions of WITSML and ETP to keep pace with standard advancements.

WITSML implementation methods also support software development patterns like Waterfall, Agile, or Spiral. For complex projects, the Spiral model, which emphasizes risk analysis, is suitable because it allows for iterative testing and improvement.

Databases Used for Storing and Retrieving Information

Databases play a vital role in storing and retrieving WITSML data, as the massive volume of data generated by well sensors, drilling equipment, and IoT systems requires efficient management. WITSML is designed to be compatible with both relational and non-relational databases, but the choice of database depends on project needs and organizational infrastructure. Based on available information, WITSML does not mandate a specific database but works well with modern database management systems (DBMS) that support structured data.

Relational Databases: Relational databases like Oracle, Microsoft SQL Server, MySQL, and PostgreSQL are suitable for storing WITSML data due to their ability to manage structured data. These databases support relational models such as tables with primary and foreign keys, which are compatible with the structure of WITSML data objects. For example, "WellLog" object data can be stored in a table with columns for different parameters such as depth, electrical resistivity, and porosity. Oracle and SQL Server are particularly popular in large enterprise projects that require high scalability and security.

Non-relational Databases: In projects that require managing unstructured or semi-structured data, non-relational databases like MongoDB or Apache Cassandra can be used. These databases are suitable for storing XML or JSON data generated directly from WITSML schemas. For example, IoT sensor data transferred in real-time via ETP can be stored in a NoSQL database for faster processing.

Cloud Platforms: WITSML is compatible with cloud platforms like OSDU, which allows data to be stored in cloud databases such as Amazon RDS, Microsoft Azure SQL, or Google Cloud BigQuery. These platforms offer high scalability and easy access to data, which is suitable for global projects with distributed teams. OSDU, as a standard platform for the oil and gas industry, supports WITSML data and enables integration with other standards like PRODML and RESQML.

Data Management and Retrieval: Database management systems (DBMS) use operations like Selection, Projection, and Join to store and retrieve WITSML data. For example, a query can retrieve "WellLog" data for a specific well and combine it with "Trajectory" data to perform well path analysis. WITSML also supports advanced technologies like indexing and caching to speed up data retrieval, especially in projects where real-time data is critical.

Data Security and Integrity: WITSML ensures information security in databases by using secure protocols like HTTP/S and data encryption. The databases used should support minimal data redundancy and centralized control to maintain data integrity. For example, in a relational database, using foreign keys can prevent data duplication and preserve the relationships between WITSML data objects.

Ultimately, the choice of database depends on factors such as data volume, real-time processing needs, scalability, and project budget. With its high flexibility, WITSML allows for the use of a wide range of databases, enabling companies to choose the appropriate infrastructure based on their needs.