Oil and gas remote monitoring for every wellhead, tank, and pipeline

Each site runs the ControlCom Edge Server, a containerized edge agent that collects data locally and syncs it to the cloud. When the cellular or satellite link drops, the agent keeps polling the instrumentation, and local storage buffers the unsent readings; when the connection returns, the buffered data forwards to the platform and the trend history fills in. Threshold alarms and Triggers for protective actions are evaluated at the edge, so a high-pressure alarm or a shutdown action does not depend on the backhaul being up at that moment. The agent also serves Edge HMI panels on the local network, which gives a technician standing at the site a live view even with no internet at all. ControlCom Connect itself is a hosted service; the edge agent is the component that runs inside your site boundary.

For most operators it takes over the day-to-day polling and visualization work that standalone wellhead SCADA packages were doing at each site, without touching the control layer. The RTUs, flow computers, pump-off controllers, and PLCs at each wellhead stay in place and keep running their local logic. The edge agent reads them over Modbus TCP/RTU, OPC-UA, EtherNet/IP, or MQTT and streams the values to the cloud platform, where dashboards, alarms, and reports replace the per-site polling screens. Operators who want to keep an existing SCADA system can do that too: ControlCom Connect runs alongside it, ingesting the same data feeds and adding multi-site rollup, mobile alerts, and long-term history on top. Either way there is no rip-and-replace project at the wellhead, and no custom driver development before the first values arrive.

Yes, with a clear scope. ControlCom Connect treats each point along the line, valve sites, pump and compressor stations, metering skids, as a monitored site: pressure, temperature, flow, and equipment status stream into one platform, and alarms fire when a segment moves outside the thresholds you define. Trend views across stations make a slow pressure decline or a flow imbalance visible long before a monthly report would surface it. What it is not is a computational leak-detection system; if your line requires model-based leak detection, that system keeps running and ControlCom Connect operates alongside it, carrying the operational telemetry, alarm routing, and history. For gathering systems and midstream networks whose stations were never instrumented into a single view, this is usually the fastest path to seeing the whole line at once.

There is no per-tag licensing. Legacy SCADA pricing counts every tag you poll, which quietly discourages instrumenting marginal wells and pushes teams to monitor less than they should. ControlCom Connect does not meter tags, so adding another pressure transmitter, tank level, or run-status point to a site changes nothing on the invoice. That matters in upstream production monitoring specifically because the asset count is large and the per-asset value varies: the economics should let you watch a stripper well as closely as a flagship pad. Pricing scales with the platform plan rather than the number of points collected, and current plans are listed on the pricing page. For large fields, the practical approach is a scoped pilot on one route or pad, then a rollout schedule agreed against what the pilot shows.

The edge agent ships with pre-built connectors for Modbus TCP and RTU, OPC-UA, EtherNet/IP, BACnet, and MQTT, which covers the RTUs, flow computers, PLCs, VFDs, and tank gauging systems actually installed across upstream and midstream sites. Devices from different vendors and different decades land in the same platform: a serial Modbus flow computer installed fifteen years ago and a current MQTT-native sensor feed the same dashboards and the same alarm engine. For device types that need custom handling, the Edge SDK lets you onboard them visually without writing code, mapping registers to named points once and reusing that definition across every site that runs the same hardware. If a device on your sites speaks none of these protocols, raise it during the demo and we will tell you plainly whether it can be read.

The component inside your boundary is the ControlCom Edge Server, a Docker container that makes outbound-only connections; no inbound firewall holes are opened into the OT network, which matters on cellular and satellite links where an exposed port is reachable from anywhere. Telemetry is encrypted in transit and at rest, and ControlCom holds a SOC 2 Type II report, available under NDA. On the platform side, role-based access controls who can see and acknowledge what, single sign-on via SAML or OIDC ties access to your identity provider, multi-factor authentication is standard, and audit logging records who changed which threshold and when. ControlCom Connect is a hosted service on AWS; there is no self-hosted version of the cloud platform, and the edge agent is the only software you operate at the site.