Remote Monitoring Architecture Guide
A decision guide for engineers and operations managers designing monitoring for remote assets - wellsites, tanks, pump stations, lift stations, or anything else far from the office. It walks the reference architecture end to end, then works through the decision factors and the cellular vs satellite vs radio trade-offs.
The Reference Architecture
Nearly every remote monitoring system, regardless of vendor or industry, reduces to the same five stages. Getting the architecture right is mostly a matter of making deliberate choices at each stage instead of inheriting defaults.
- Field devices - the transmitters, sensors, meters, and controller I/O that produce the measurements. Their protocols and signal types constrain everything downstream.
- RTU / edge gateway - translates field protocols, buffers data locally, and forwards it upstream. Local store-and-forward matters: the comms layer will drop out, and a gateway that buffers and backfills turns an outage into a non-event instead of a data gap.
- Comms layer - cellular, satellite, or radio (compared below). This is usually the layer that dominates operating cost and reliability discussions.
- Platform - the historian, alarming, dashboards, and reporting, hosted in the cloud or on your own infrastructure.
- Users - the people the system exists for. If the pumper, the on-call tech, and the manager cannot each get what they need quickly, the architecture has failed regardless of how elegant the middle is.
Decision Factors
Site count and growth
One site justifies almost any ad-hoc solution; fifty sites punish it. The more sites you expect, the more the decision should weight standardized gateway configurations, remote management, and per-site recurring cost over per-site cleverness.
Power at the site
Grid power removes constraints; solar-plus-battery imposes them everywhere. On a solar site the power budget - panel size, battery capacity, and worst-season sun - drives gateway selection, radio choice, polling rate, and even protocol (report-by-exception traffic costs less energy than tight polling). Actual figures are site-specific: build a power budget per site class rather than borrowing numbers.
Comms availability
Survey before you standardize. Cellular coverage maps are optimistic at antenna height on a tank battery in a draw; radio needs line of sight or engineered paths; satellite works nearly anywhere with sky view but changes the cost and latency profile. Mixed fleets commonly end up with a primary technology plus exceptions.
Latency and update needs
Be honest about what the operation needs rather than what sounds impressive. Daily production accounting, hourly tank levels, and prompt alarm callouts have different requirements, and the strictest one sets the design. Report-by-exception protocols can deliver prompt event notification even on modest links.
Security constraints
Common practice for cloud-connected sites is outbound-only connections initiated by the gateway, TLS on every hop that supports it, and no inbound ports open to the field network. Corporate policy may additionally require private APNs, VPNs, or on-premise hosting. The zones-and-conduits concepts of the ISA/IEC 62443 series and the guidance in NIST SP 800-82 are the standard reference points for structuring this.
Budget structure
The technologies split less on total cost than on cost shape: radio is capex-heavy (you build and own the infrastructure), cellular and satellite are opex-heavy (recurring service per site). Which shape fits depends on your ownership horizon and how your organization funds projects.
Cellular vs Satellite vs Radio
| Factor | Cellular | Satellite | Private radio (licensed or unlicensed) |
|---|---|---|---|
| Coverage | Wherever carriers have built; verify at each site, not on the map | Nearly anywhere with a clear sky view | Wherever you engineer it: line of sight or designed paths to your own infrastructure |
| Infrastructure you own | Gateway and antenna only | Terminal and antenna only | Radios at every site plus repeaters or towers - yours to build and maintain |
| Cost shape | Recurring service per site | Recurring service per site, historically at a premium for airtime | Capex up front; low recurring cost, plus licensing fees where a licensed channel is used |
| Bandwidth | Generally ample for SCADA telemetry | Varies widely by service class; plan around the plan you buy | Modest by modern standards; well matched to report-by-exception telemetry |
| Latency character | Low for telemetry purposes | Depends on constellation: geostationary links add noticeable round-trip delay from orbital distance; low-earth-orbit services are lower | Low on a healthy path |
| Typical failure modes | Tower outages, congestion, carrier sunsets of older network generations | Weather fade, antenna obstruction or misalignment | Path obstruction (growth, new structures), interference on unlicensed bands, your own tower maintenance |
| Best fit | Fleets of dispersed sites inside coverage; fastest to deploy | Sites outside terrestrial coverage; backup path for critical sites | Dense clusters of sites you will operate for years, especially where coverage is poor |
Patterns That Tend to Work
- A handful of covered sites: cellular gateways with a report-by-exception protocol, buffering locally. Simplest to deploy and manage.
- A dense field with poor coverage: radio from each site to a concentrator with good backhaul (wired, cellular, or licensed microwave), then one link to the platform.
- Truly remote sites: satellite, with polling rates and payload sizes designed around the service plan.
- Mixed fleets: standardize the gateway and the upstream protocol so the comms technology can vary per site without changing anything else.
- Where alarms matter: add a second path (dual-SIM, or satellite backup on critical sites) and make sure the gateway buffers and backfills across outages - alarm delivery and historical completeness are separate problems, and both need an answer.
Sources & Standards
Primary references for securing and structuring remote monitoring architectures:
- NIST SP 800-82 Rev. 3 - the Guide to Operational Technology (OT) Security, covering architectures and network segmentation for control systems.
- CISA - U.S. government advisories and recommended practices for industrial control system connectivity.
- International Society of Automation (ISA) - home of the ISA/IEC 62443 series, the source of the zones-and-conduits security model referenced above.
From Diagram to Dashboards
This guide is complete without us - use it to pressure-test any vendor, including this one. If the platform stage is the part you would rather not build, that is what Merobix is.