Share
Facebook
Twitter
LinkedIn
EmailRMS-RESQML/Geolog Connector
The RMS-RESQML/Geolog Connector can be used to transfer data between RMS and third-party applications. RESQML/Geolog Connector in RMS allows the following:
RESQML DATA TRANSFER
The RESQML data transfer tool enables the import and export of RESQML files independent of application or platform, and provides a method for exchanging data via an ETP server such as Epos™. The tool is easy to use, quick and seamless. It is part of the RMS base license and uses the plug-in framework in RMS. The plug-in framework allows the tool to be updated whenever a new version is released through a separate installer, without having to rely on a new version of RMS.
The latest version of the RESQML data transfer tool, including the Release Notes, can be found on the Emerson Customer Portal.
WHY RESQML
RESQML is an industry-developed, vendor-neutral format that facilitates data exchange among the many software applications used throughout the E&P subsurface workflow. The tool helps promote interoperability and data integrity among these applications and improves workflow efficiency.
RESQML data transfers in RMS are:
- Service (ETP)
- File-based (.epc files).
Users can connect and exchange data with any ETP compliant server without having to create intermediate files. This enables RMS to integrate into the Epos environment.
Interoperability with applications outside Epos is done via import and export of RESQML files (.epc).
RESQML 2.0.1 standard format is used to transfer data between RMS and other Emerson applications or third-party applications. Support for ETP1.2, which is compliant with the Open Subsurface Data Universe (OSDU) ecosystem, will allow data transfer between RMS and OSDU. See the diagram below:
Data Types Supported
| Data Type | Data Subtype | Transfer Capabilities | Emerson Applications |
| Well data | Wellhead, trajectory, logs (continuous and discrete), picks/markers | Import + Export | Epos™, SKUA-GOCAD™, Geolog™ (via Epos) |
| Interpretation data | Horizon/fault picks, surfaces, T-surfaces, lines/polygons (fault sticks) | Import + Export | Epos, SKUA-GOCAD |
| Regular 2D data | Surfaces, 2D grids | Import + Export | Epos, SKUA-GOCAD |
| 3D grids | Straight pillar grids only, grid properties – continuous, discrete and composite (time-dependent) | Import + Export | SKUA-GOCAD |
| Blocked wells/ upscaled log data | Continuous and discrete properties only | Import + Export | SKUA-GOCAD |
RMS-GEOLOG CONNECTOR
The RMS-Geolog Connector allows the direct transfer of Geolog project data to RMS. It communicates directly with standalone Geolog projects to gather a list of available data, which is then used by the connector to choose the data to be transferred. Geolog projects can either be stored locally or over a network (data transfer of Geolog projects from the Epos database is not supported). This connector is solely designed for well-specific data transfer (refer section below) supported by RMS, beginning with the Geolog 20 release. This cross-platform protocol allows data transfer between Windows and Linux.
Data Types Supported
| RMS Well Attribute | Geolog Well Attribute | Comments |
| Well name | WELL | |
| Wellhead east UTM (X) | X-LOCATION | Unlike Geolog, RMS does not support geographic latitudes/longitudes |
| Wellhead north UTM (Y) | Y-LOCATION | |
| RKB | ELEV_MEAS_REF | In RMS, MD is referred from RKB and TVD from MSL by default. In Geolog, both MD and TVD are referred from RKB |
| Trajectory/Survey Data | REFERENCE; DEVIATION | REFERENCE is the default set specified for trajectory/survey calculation. |
| Logrun | SET | |
| Well picks | TOPS.TOPS | Geolog can have multiple sets of TOPS; however, the one mentioned here is only mapped |