Features Overview

The RIGFLEX™ well-site data aggregator currently processes WITS level 0 and Modbus data streams at the rig-site and transfers to the RigFlex data store as log or trajectory WITSML objects. Each WITS 0/Modbus stream is buffered at the rig-site to ensure no data loss in the event of data connection issues. RigFlex-V (for Microsoft Hyper-V) is running on the backend server and provides data aggregation and configuration while the RigFlex WitsSender is installed at the rig-site.

WITS 0 / Modbus connection management

WITS 0 / Modbus connection management

WITS 0/ MOdbus

Multiple WITS 0 serial and TCP connections are possible as well as Modbus and incoming streams each have the capability to relay to another port for use by other rig-site devices.

WITSML configuration

WITSML configuration

WITS 0 to WITSML data mapping

The WITS 0 and Modbus streams are mapped to WITSML data objects and configured with a standard unit set. If a well or other object does not exist, RIGFLEX™ will create them. When the configuration changes the underlying WITSML objects are updated with the new data schema elements.

System status

System status

Monitor System Status

The main RigFlex screen will indicate the status of each wits 0 stream transfer status, the transfer progress for each object and system notifications. It also presents a list of authorized objects in the back-end data-store. RIGFLEX™ will manage the buffer to ensure every record is transferred using optimization methods.

Note: The following Energistics (c) products were used in the creation of this work: ETP DevKit (Energistics.DataAccess).

RIGFLEX™ EULA