When people say a remote site feels slow, they usually mean latency, not bandwidth. Latency is the delay a piece of data experiences on its way through the network - and for SCADA it shapes how quickly you see a reading and how responsive remote control feels. This guide explains latency and why it matters.
Latency in one line: Latency is the time it takes a packet of data to travel from source to destination across a network, usually measured as round-trip time in milliseconds; in SCADA it governs how quickly field readings arrive and how responsively remote commands take effect.
Latency and bandwidth are often confused but describe different things. Bandwidth is how much data a link can carry per second - the width of the pipe. Latency is how long a single packet takes to get through - the length of the pipe. A satellite link can have plenty of bandwidth yet high latency, so bulk data flows fine but every request feels sluggish. A link can also have low latency but little bandwidth.
Latency comes from several sources: the physical distance the signal travels, processing and queuing in each device along the path, and retransmissions when a link is noisy. On a remote site, a weak cellular signal that forces retries can drive effective latency far above the link's nominal figure.
The transport dominates latency. A good LTE connection typically adds tens of milliseconds of round-trip delay; a geostationary satellite link adds roughly half a second because of the sheer distance to orbit; low-Earth-orbit satellite falls back to tens of milliseconds. Licensed radio latency depends on the network design and poll cycle. Choosing transport is largely choosing an acceptable latency budget.
For monitoring and alarming, modest latency is fine - a reading arriving a second later is rarely a problem, and report-by-exception hides most of it. Latency bites hardest with interactive remote control and fast closed-loop logic, where a half-second delay makes a link unsuitable and control is kept local at the RTU or PLC. A cloud SCADA like Merobix is built around this reality: field control stays local while the cloud handles monitoring, historian, and alarms.
Bandwidth is how much data a link can carry per second; latency is how long a single packet takes to travel across it. A link can have high bandwidth but high latency, like satellite, or low latency but limited bandwidth.
Rarely for monitoring and alarms - a reading arriving a fraction of a second late is fine, and report-by-exception reduces traffic. Latency matters most for interactive remote control and fast closed-loop logic, which is why that control stays local in the field.
A healthy LTE link usually adds tens of milliseconds of round-trip latency. A weak signal that forces retransmissions raises the effective figure, which is why signal strength and antenna placement affect responsiveness as much as the carrier's network does.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.