On a metered cellular or satellite link, every byte a remote site sends costs money and battery. Bandwidth - how much data a link can move - is one of the tightest constraints in remote SCADA design. This guide explains what bandwidth is, how it differs from latency, and how engineers conserve it.
Bandwidth in one line: Bandwidth is the maximum rate at which data can be transferred across a network link, usually measured in bits per second; in telemetry it sets how much field data a remote site can send in a given time and, on metered links, how much that data costs.
Bandwidth is the width of the pipe - how much can flow per second - while latency is how long any one packet takes to get through. The two are independent: a link can have generous bandwidth but high latency, or low latency but little bandwidth. For SCADA, bandwidth determines how many tags, how often, and how large a payload a site can push before the link is the bottleneck.
Remote telemetry is usually bandwidth-constrained and, crucially, metered. Cellular plans bill by the megabyte and satellite data is costlier still, so a site that polls thousands of tags every second on a cellular SIM can run up a real bill. Bandwidth conservation is therefore a design goal, not an afterthought.
The main technique is report by exception: instead of sending every tag on every scan, the RTU sends a value only when it changes beyond a deadband. A pressure holding steady generates almost no traffic; a moving value reports as it moves. This alone can cut data volume dramatically versus blind periodic polling. Protocols like DNP3 and MQTT are built around this event-driven model.
Other tactics include longer poll intervals for slow-moving process values, compact binary protocols instead of verbose ones, compression, and store-and-forward that batches buffered readings after an outage rather than reconnecting constantly. A cloud SCADA such as Merobix reads devices over efficient protocols like Modbus, DNP3, and MQTT, so an operator can tune scan rates and deadbands to fit the bandwidth and cost budget of each site.
Bandwidth is how much data a link can carry per second; latency is how long a single packet takes to cross it. Bandwidth limits total throughput and cost, while latency limits responsiveness - they are separate properties of a link.
Use report by exception with sensible deadbands so tags transmit only when they change, lengthen poll intervals for slow values, choose compact protocols like DNP3 or MQTT, and rely on store-and-forward instead of frequent reconnects.
Usually not. Typical process telemetry - pressures, levels, flows, states - is low-bandwidth, especially with report-by-exception. High bandwidth only matters for data-heavy needs like video or frequent high-resolution polling.
This page references the protocol specifications published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
Last reviewed: July 27, 2026. Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.