1. The Problem

Distributed drilling operations required a unified and comparative view of the process (time x depth), with reliable annotations and centralized histories, while maintaining a local UI at the wells for “near-rig” decision-making.

Specific pain points:

Impact: Delays in diagnostics, lower operational standardization, higher logistics cost, and risk of decisions based on incomplete data.

Example: “Without a consolidated historical trail, each well required ad-hoc compilations for post-operation analyses, impacting the optimization of drilling parameters.”

2. The Solution

2.1 Logical Diagram (high level)

[Well/Edge Site]                              [Datacenter/Cloud]
  ?? Rig Equip.             ?????????????????????????????????
  ?    ?? WITS0/WITS                           ? FrameworX Enterprise          ?
  ?? FrameworX EdgeConnect + Local UI  ?????????  • Broker/Ingress (MQTT/HTTP) ?
  ?    • Collection (WITS0/WITS)               ?  • Integrations (WITSML)      ?
  ?    • Calculations (aggreg./prediction)     ?  • Corporate calculations     ?
  ?    • Buffer/Store&Forward                  ?  • APIs/WebAssembly Displays  ?
  ?? Connectivity (Cellular/Ethernet/VSAT)     ?  • PI connector (OSI PI)      ?
                                               ???????????????????????????????????
                                                       ?
                                                [OSI PI System]
                                                       ?
                                                [Web/Mobile/SCADA]

2.2 Topology

Layer

Component

Role

Notes

Edge

FrameworX EdgeConnect

WITS0/WITS acquisition, local UI, calculations, buffer

Resilient operation with intermittent connectivity

Transport

Cellular/Ethernet/VSAT

Telemetry and configuration

TLS, compression, and store-and-forward

Central

FrameworX Enterprise

Ingestion, orchestration, APIs, Displays

Multi-site; solution versioning

Data

OSI PI

Corporate historian

Data Archive + AF (where applicable)

Clients

Web/Mobile/SmartClient

Visualization and engineering

Comparisons by time/depth; annotations

2.3 Network Architecture

Hybrid: cellular/ethernet/VSAT, with TLS and store-and-forward at the Edge.
Logical isolation by well (independent solution) and by environment (dev/test/prod).

2.4 Redundancy & Failover

Edges: Independent operation with local buffering and local UI (continuity even offline).
Central: Redundancy of critical services (ingestion/visualization) and PI backups.

2.5 Protocols & Equipment

Collection: WITS0/WITS (drilling equipment).
Metadata/Annotations: WITSML (events/intervals/observations from the drilling system) + operator input.

2.6 Databases/Historians

Corporate: OSI PI as historical repository and source of corporate reports.
Edge: Local buffer (store-and-forward) + calculations close to the source.

2.7 Scale & Capacity (fill/validate)

2.8 Third-Party Integrations

WITSML servers (rig providers), OSI PI (connectors/SDKs), data/ML pipelines (when applicable).

3. Key Enablers

Why wasn’t this trivial on other platforms? Combination of resilient Edge + local UI, scalable WebAssembly, solution independence, and WITS/WITSML normalization ready for time/depth comparison.

4. The Results