WITSML Client

In this WITSML Project customer wants to implement the process which reads incoming well/wellbore data from the field on an edge gateway and and then update the information at the server running on the Gateway or send it to the WITSML server repository to create/update the associated well/wellbore information.

The edge application was built to run on any Agora Edge Gateway, and it is leveraging the Agora Edge App SDK (2.0) and C# .NET 6.0 for configuration, logging, and sending/receiving data from the Agora Edge App MQTT Broker.

In WITSML we have two major components :-

• WITSML Client
• WITSML Server

Architectural Overview

This section provides a brief overview regarding the architecture showing how Agora applications and edge devices are being used, how they transmit log data, and how they store log data.

Figure 1 : Agora Edge Apps Field Architecture

• Agora gateways are installed on rig/well site for data collection.
• Agora Edge Apps (AEAs) are packaged as Docker containers.
• AEAs are deployed and configured on the gateway by AgoraOps personnel.
• The WITSML Client is communicating with AEAs bus. AEA through broker may receive data from other applications which are running on the gateway or externally using the WITSML protocol.
• The existing WITSML Client creates/reads/writes/updates data on external WITSML Servers, such as InterAct.
• The WITSML Client will have a Wep Application (will be developed) which will enable field engineer to activate (/check status) of the active Wellbore for the Well