Industrial Remote Monitoring: How It Works, What It Costs, and When You Don't Need SCADA

Cellular and satellite RTUs that watch your pumps, tanks, and process equipment and tell you the moment something is wrong. Built for water, wastewater, and industrial operators who want operational awareness without the cost and complexity of a full SCADA build.

Industrial remote monitoring is the practice of using sensors, an on-site controller (an RTU or industrial gateway), and a communication network (usually cellular, satellite, or radio) to track equipment and process conditions at unmanned sites and send alerts when something falls outside normal operating range. It is supplemental to operator rounds, designed for sites where running a full SCADA system would be expensive or impractical.

Table of contents

1. What is industrial remote monitoring

2. How it works in four steps

3. Is it the same as SCADA?

4. Use cases by industry

5. Choosing the right system

6. What a deployment actually looks like

7. Industrial remote monitoring vs. alternatives

8. Frequently asked questions (FAQ)

9. Get started with RACO

What is industrial remote monitoring?

ndustrial remote monitoring is the use of field hardware, a wireless or wired network, and a cloud or on-prem application to keep tabs on industrial equipment from somewhere other than the site itself. A sensor reads a condition (level, pressure, flow, temperature, runtime, fault state). A controller decides whether that reading needs attention. The network carries the message. A person, on a phone or a dashboard, gets told what to do about it.

It is not new. Operators have been using telemetry to watch remote pump stations and tank farms since the 1980s. What is new is the cost. A modern cellular RTU and a cloud dashboard can do, for one site, what a SCADA project a decade ago took six figures and a system integrator to build.

In one sentence: Industrial remote monitoring is how you know what is happening at a site without standing there.

How industrial remote monitoring works (four steps)

Every remote monitoring system, from a single tank gauge to a hundred-site water utility, follows the same four-stage architecture.

1. Sensing and inputs

The system reads conditions from the field. That can be:

• Analog signals (4-20 mA, 0-10 V) from level transmitters, pressure sensors, flow meters

• Digital signals from pump fault contacts, float switches, intrusion alarms, generator status

• Pulse inputs from flow meters and water meters

• Protocol-level data from existing PLCs and meters (Modbus RTU, Modbus TCP, DNP3)

2. Local logic and alarming

An RTU (remote terminal unit) or industrial gateway sits at the site. It reads the inputs continuously. It applies local logic (above this level, send an alarm; this pump has run for too long, send an alarm; this fault has cleared, send an all-clear). The important word is local: the RTU keeps working when the network is down, then catches up when it comes back.

3. Communication

The RTU sends data and alarms out to wherever the operator is. The most common paths today are:

• Cellular (LTE Cat-1, Cat-M, NB-IoT) — primary for most modern deployments

• Satellite (Skylo IoT-NTN, Iridium, Inmarsat) — fallback or sole-use where cellular is absent

• Wi-Fi or Ethernet — when the site already has IT infrastructure
• Licensed and unlicensed radio (900 MHz, 450 MHz) — legacy and rural backbones
• Redundant designs use cellular as primary with satellite as fallback, so a tower outage does not silence the site.

4. Notification and dashboard

Alarms reach the operator by voice call, SMS, email, push notification, or webhook. A web dashboard (in RACO's case, the RACO Monitoring Center, or RMC) shows current state, historical trends, alarm history, and lets the operator acknowledge alarms or, where the system supports it, send a control signal back (start a pump, open a valve, reset a fault).

[Custom diagram here: Sensor → RTU → Cellular/Satellite → Cloud → Phone/Dashboard. Alt text: "Industrial remote monitoring system architecture diagram showing field sensors, an RTU, cellular and satellite networks, cloud platform, and operator alerts."]

In one sentence: A sensor reads, an RTU decides, a network carries, and a human gets told.

Is industrial remote monitoring the same as SCADA?

No, and the distinction matters because confusing them is the most common reason operators overspend on monitoring.

SCADA (Supervisory Control and Data Acquisition) is a full operational platform: PLCs, HMIs, historians, redundant servers, engineering workstations, often a control room. It is built for plants and utilities that need second-by-second visibility and active control across dozens or hundreds of process points, with a dedicated controls team to maintain it.

Industrial remote monitoring, as the term is usually used today, is a lighter-weight solution: a few I/O points per site, alarms when conditions fall out of band, dashboards for operators to spot-check, sometimes basic control like starting a backup pump. It is supplemental to whatever local automation already exists. It does not replace a PLC. It does not replace a SCADA system. It fills the gap for sites that have neither, or that have a PLC but no way to see it from anywhere but the panel door.

Use cases by industry

RACO systems are deployed across water, wastewater, industrial process, agriculture, and facility infrastructure. Each industry monitors a different mix, but the underlying pattern is the same: critical asset, unmanned site, need to know.

Water utilities

Booster pump stations, well sites, reservoirs, PRV vaults, chlorine residual monitoring. The default ask is "tell me when the pump fails, the tank is low, or the chlorine is out of range." Compliance pressure (LCRI, SDWA reporting, source water alerts) is pushing more utilities toward continuous monitoring of sites they used to drive past. See water utilities solutions →

Wastewater

Lift stations are the headline use case. Storm overflows, treatment plant process points, force main pressure, generator status. A lift station SSO can cost a utility tens of thousands of dollars in cleanup plus a notice of violation. Remote monitoring catches the high-wet-well alarm before the float trips. See wastewater solutions →

Industrial process

Tank levels, batch process timers, vibration, motor runtime, compressed air, refrigeration temperatures, generator and UPS status. The pattern is the same as water: distributed assets, intermittent attention, expensive consequences if something is missed. See industrial process solutions →

Agriculture and irrigation

Irrigation pump pressure and runtime, well levels, soil moisture, frost alarms, grain bin temperatures. Cellular and satellite are usually the only practical networks; sites are far from any IT infrastructure. See agriculture solutions →

Tank, fuel, and bulk storage

Above-ground and underground tank level monitoring for fuel, water, chemical feed. Inventory data goes to dashboards. Level and leak alarms go to phones.

Pumps and motors

Status, runtime, fault contacts, vibration, current draw. Often the cheapest first step a utility can take: bolt-on monitoring of pumps that already have fault contacts but no way to read them from off-site.

Generators and critical facilities

Generator run status, fuel level, transfer switch state, battery, room temperature, intrusion, power loss. Common at telecom shelters, water treatment plants, data centers, and remote control rooms.

How to choose the right system

There is no single right answer; there is a small set of questions that quickly narrows the field.

1. How many sites and points do you need to monitor? Under 10 sites and under 20 points per site: a dedicated alarm dialer or a small RTU per site is usually the most cost-effective path. Above that, you start needing a cloud platform with multi-site rollup.
2. What signals are you reading? Just dry contacts (fault, full, empty)? An alarm dialer works. Mix of analog and digital? You need an RTU with both. Existing Modbus or DNP3 PLCs? You need a gateway with protocol support.
3. What network is available? Reliable cellular at every site simplifies everything. No cellular at some sites? Satellite fallback or a mix of cellular and licensed radio. Existing fiber or Ethernet at the site? Use it.
4. Who needs to see the data? One operator with a phone wants voice and SMS. A four-person ops team wants a dashboard and shift scheduling. A regulator wants exportable history.
5. What is the budget model? One-time capital with low recurring cost favors a dedicated RTU like Verbatim Gen2. Subscription-first with no upfront cost favors a managed IoT platform. Both have tradeoffs.

RACO product matrix (quick reference)

What a deployment actually looks like

A typical RACO deployment for a mid-size water utility adding remote monitoring to a single lift station:

Day 0: Sales conversation. Site walk, signal list, network check, cellular survey. Quote with hardware, RMC service, and any installation services.

Week 1: Hardware ships. Pre-configuration done in RACO Monitoring Center so the unit comes online configured.

Week 2: Field install by the utility's electrician or a RACO-authorized integrator. Power, I/O wiring, antenna mount. Power up. Unit registers with RMC.

Week 3: Operator training, alarm escalation setup, contact list, on-call rotation, dashboard layout. Documentation handoff.

Week 4 onward: Site is live. Alarms route to phones. Dashboard is the daily check.

Rough cost ranges 

• Hardware: $2,000 to $5,000 per site for a full cellular RTU (Verbatim Gen2 base unit is $2,995)
• Service: cellular plan and cloud platform subscription, typically a per-site monthly fee in the $25 to $100 range depending on data and features
• Installation: $500 to $3,000 per site depending on local electrical labor and site readiness

Compare that to a SCADA buildout, which typically starts in the high five figures per site once you include PLC, HMI, panel, programming, and integration labor.

Industrial remote monitoring vs. the alternatives

vs. SCADA

SCADA is the right tool when you need continuous control across many process points by a controls team. It is the wrong tool when you have unmanned sites, a small operations team, and a need to know about exceptions, not run a control loop. Most water utilities under 50,000 connections do not need SCADA at every site. Many treatment plants run SCADA inside the plant and use remote monitoring for the outlying lift stations and reservoirs.

vs. consumer IoT and prosumer sensor platforms

Consumer-grade IoT (off-the-shelf wireless sensors with a smartphone app) is fine for a workshop or a home. For industrial deployment, the same gear typically fails on environment (heat, cold, vibration, condensation), on network reliability (consumer Wi-Fi was not designed for unmanned outdoor sites), and on operator workflow (a notification app is not a 24/7 escalation system). Industrial-grade RTUs and platforms are built to a different durability and reliability bar.

vs. building it yourself

Open-source platforms and single-board computers can absolutely monitor a tank. The hidden cost is the engineering required to maintain it: cellular modem firmware, certificate rotation, dashboard uptime, alarm path validation, training a backup person, support for the operator at 2 a.m. when the modem stops responding. Most utilities that try this end up either buying a commercial system anyway or carrying a permanent dependency on one engineer.

vs. PLC and HMI only

A PLC alone gives you control at the panel. It does not solve the problem of knowing about that control from a phone. Adding an industrial gateway to an existing PLC is one of the cheapest and fastest paths to remote monitoring, because the I/O is already wired and the logic already exists.