Workstream Page: ADCS Software Interface

Click on the tabs below for more information or click here to return to all D-WIS Workstreams.

ADCS Overview

The focus of this workstream is to define a standardized software interface to enable third party applications to utilize the features and functions of an Automated Drilling Control System (ADCS).  The ADCS Software Interface is composed of requirements, specification and Units of Conformance (UoC).  

The interface provides end users the ability to read/write data through the interface.

Standardized Software Interface

Transport Protocol Module


Non-functional RequirementDefinition
AffordabilityConcerns issues associated with development costs pre-delivery, and lifecycle costs post- delivery (i.e., supportability) – as the data model matures these are the associated lifecycle costs. We do not want to reinvent the data model over and over again – what is the total cost of ownership?
The ability of two or more systems or components to exchange information and to use the information that has been exchanged (Institute of Electrical and Electronics Engineers (IEEE)). We need to have semantic understanding of the data to be exchanged between systems. The model must be able to support structures that include the semantic information relevant to the data.

The ease with which a system or component can be modified to increase its storage or functional capacity. The model needs to be able to support growth. The rules need to manage the growth. We need well-defined rules for managing extensions to the model. Extensibility defines the ability of the software architecture to host future planned technology insertions as well as third-party developed applications.
PerformancePerformance is about timing. Events (interrupts, messages, requests from users, or the passage of time) occur, and the system must respond to them. There are a variety of characterizations of event arrival and the response but basically performance is concerned with how long it takes the system to respond when an event occurs. The degree to which a system or component accomplishes its designated functions within given constraints, such as speed, accuracy, or memory usage.

UsabilityHow easy it is for the user to accomplish a desired task and the kind of user support the system provides. It can be broken down as follows:
  • Learning system features: If the user is unfamiliar with a particular system or a particular aspect of it, what can the system do to make the task of learning easier?
  • Using a system efficiently: What can the system do to make the user more efficient in its operation?
  • Minimizing the impact of errors: What can the system do so that a user error has minimal impact?
  • Adapting the system to the user needs: How can the system adapt to make the user’s task easier?
  • Increasing confidence and satisfaction: What does the system do to give the user confidence that the correct action is being taken?

ADCS Motivation

Reuse of software is a business objective for D-WIS as a mechanism to reduce cost for software related expenses and enable deployment of digital solutions, at scale, across the value chain.  The effort to reuse software is directly related to the design of that software and the target platform. Through common use of the D-WIS ADCS Software Interface, software architectures would be aligned, reducing the impact of porting capability software from one ADCS to another. 

One of the principal goals of the D-WIS Software Interface is to reduce the efforts to bring new capabilities to the field.  The Equipment Interfaces for equipment control using tag level values and set points on specific equipment.  Standard pieces of equipment should be considered, including TopDrive, Drawworks, MudPumps, {etc.}.  Additional topics could include how specialized equipment, like Power Slips, might be introduced into the system.

ADCS Examples

To be completed

ADCS Extension Process

To be completed

ADCS Software Interface Contributors

  • Mark Anderson – Ensign Energy Services
  • Ketan Bhaidasna – Haliburton
  • Hans-Uwe Brackel – Baker Hughes
  • Mark Carrier – Real-time Innovations
  • Clinton Chapman – Schlumberger
  • Dmitriy Dashevskiy – Baker Hughes
  • Aaron Eddy – Pason Systems
  • Darryl Fett – Total Energies
  • Fred Florence – Rig Operations, LLC
  • Loic Hoarau – Schlumberger
  • Dimitrios Pirovolou – Weatherford
  • Robert Van Kuilenburg – Nobel
  • Robert Wylie – XN Drilling



Scroll to Top