Industrial IoT gateways and telemetry: getting remote-site data to a dashboard

An industrial IoT gateway is a device that reads data from sensors, PLCs or meters through field protocols, stores it temporarily when the network drops, and then sends it to a server or the cloud over a cellular or Ethernet network.

Telemetry is the wider practice of measuring at one place and seeing the result somewhere else. Think of river levels at a mine jetty, pressure along a fuel pipeline, or temperature inside an electrical panel. These points are often far from any control room, and running cable to each one costs more than the measurement is worth. A gateway with a cellular link closes that gap.

The technology is mature, and the hard parts sit at the edges of the system. The sensor must be mounted where it reads the real process. The power supply must survive the rainy season. The data path must keep history intact when the signal comes and goes.

A telemetry system is a chain of five links, and the data is only as reliable as the weakest one.

At the field end, sensors deliver 4-20 mA, digital inputs or Modbus. The gateway polls them on a set interval, converts raw values into engineering units, adds a timestamp and checks alarm limits. It then sends the data over cellular, radio or Ethernet, often with MQTT, to a server that stores history and drives the dashboard and notifications.

Every link adds a setting someone must own: the sensor range, the polling interval, the alarm limits, the SIM card and data plan, the server account. Write them down in one place per site. When a reading looks wrong, that sheet tells you which link to check first.

Choose the polling interval from the process, not from habit. A river level that changes over hours does not need a reading every second, while a pipeline pressure used for leak alarms may need fast sampling at the gateway with only changes and alarms sent upward. Faster intervals cost data volume and, at solar-powered sites, battery capacity.

Telemetry tells you what is happening far away; SCADA also lets you act on it.

A telemetry system mainly measures, records and alarms. Data may arrive every few minutes, and nobody expects to start a pump from the dashboard. SCADA, supervisory control and data acquisition, runs closer to the process: operators issue commands, see responses within seconds, and the system talks to PLCs and RTUs that carry interlocks.

The line between the two blurs when a remote site needs control, for example a pump at a river intake. Even then, keep the control logic and safety interlocks in the local PLC or RTU. The remote link should send setpoints and commands that the local controller checks, never replace the controller.

Pick a gateway by the site it will live in, not by the longest feature list.

Start with the field side: which protocols and signals must it read, and how many points. Then the network side: which carriers cover the site, whether a private APN or VPN is required, and how the data reaches the server. Then the environment: supply voltage, temperature, dust and water, vibration, and hazardous-area classification if the gateway sits near fuel.

Security belongs on the same list. IEC 62443-4-2:2019 sets technical security requirements for industrial automation components, grouped under seven foundational requirements such as identification and authentication control, system integrity and data confidentiality. Ask suppliers which of these the gateway supports, and how firmware updates are delivered and verified.

Remote management decides how often someone must drive to the site. A gateway that reports its own health, signal strength and supply voltage, and accepts configuration changes over the secure link, saves trips. Keep a backup of every gateway configuration on the server, so a failed unit can be replaced and restored in one visit.

At a remote site, the gateway is usually the easy part; keeping it powered and dry is harder.

Without grid power, a solar panel and battery must carry the load through cloudy days and nights. Lower the energy budget by choosing the reading interval carefully, letting the modem sleep between transmissions, and sizing the battery with margin. The enclosure must keep out rain and insects, and cable entries need glands that stay sealed.

Wireless sensors remove signal cabling where wires are hard to run, for example on busbars inside live switchgear. CATALYST CT-WTS reads temperature at the asset and sends it into the CATALYST data path. Wireless works well for monitoring when the radio path is surveyed first; keep safety functions on wired, certified loops.

Lightning is the other remote-site risk. Antenna masts, long sensor cables and solar frames all collect surges. Bond them to a proper earth and fit surge protection on signal and communication lines. The ATG gateway replacement at Jambi recorded the lesson plainly: install line protection from the start in areas prone to lightning.

A gateway connected to the internet is a door into the plant network, so lock it like one.

Make every connection outbound from the gateway to a known server, so no port on the site needs to be open to the internet. Use TLS for the transport; IANA lists port 8883 for secure MQTT. Give each gateway its own credentials or certificate, so one lost device does not expose the rest. Keep the gateway on its own network zone, separated from PLC and safety networks by a firewall.

Plan the lifecycle as well: who changes passwords, who installs firmware updates, and what happens to the data and credentials when a gateway is replaced or removed.

Citia projects show that remote monitoring succeeds or fails on the site survey and on testing the whole chain.

For PT Adaro Energy in Barito Selatan, Central Kalimantan, Citia installed a river water level monitoring system in 2022 around a VEGAPULS C30 radar sensor. The site is remote, with limited access and no grid power, so a solar panel and battery supply the devices. The project record credits the field survey, the sensor mounting position and verification before commissioning for the result.

CATALYST Telemetering applies the same pattern to river level, pipeline and tank pressure, and panel temperature and humidity, with power, connectivity and reading interval designed per site. On the Balongan to Plumpang pipeline, restoring PressMon communication meant replacing fibre optic converters and then testing real-time data, pump status, alarms and the shutdown function, not only the network link.

The same thinking extends to terminal software. INTEGRA CTP, which is still in development, places gateways and edge software at each site to collect device data and keep local work going, with buffering when the connection drops. How each site behaves during an outage is assessed per implementation rather than assumed.