A data center operator once asked in a tech community whether anyone had actually deployed edge computing, and what equipment had to be prepared on site. Coming from someone who works in data centers, the question says more than it would from an outsider. In a data center, the equipment list is ready-made — servers, switches, firewalls, UPS — buy from the list and spend the rest of the time tuning. When the edge node moves into a workshop, a factory floor, or a light industrial park, the environment changes and that list stops working. Data has to travel from PLCs, meters, and sensors through protocol conversion and local processing before it reaches the cloud or a headquarters system. Which device handles each link of that chain is exactly what needs to be sorted out. One term worth keeping in mind: industrial gateway. It is the core role of the whole node.
Deploying edge computing does not start with picking a product model. It starts with recognizing the four roles inside an Edge Node. Once the roles are clear, it becomes possible to judge which of them can be merged into one device and which have to stay separate.
Industrial gateway — the entry point for on-site data and the first tier of computing.It takes in device data arriving over serial and Ethernet ports and performs protocol conversion, such as Modbus RTU/TCP conversion and parsing of common PLC protocols. Then it handles filtering, threshold judgment, alarms, and data caching locally, and reports data to the designated platform according to set conditions. Most of the "computing" in edge computing happens at this layer — the lightweight, real-time kind.
Industrial router — the node's link to the outside world.It carries the segment between the site and headquarters or a cloud platform, with VPN and firewall, providing both 4G and wired access. Public network conditions around a factory or industrial park are not what a data center enjoys; losing contact with a node when the primary link drops is not rare. Link redundancy often deserves attention before computing power does.
Industrial switch — wired aggregation inside the node.When many devices have to be connected over a wired network, the switch joins PLCs, meters, host computers, and cameras into a single LAN. When only a handful of devices are involved, connecting them directly to the gateway's Ethernet ports is enough, and a dedicated switch is not necessarily required.
Industrial PC — for heavy workloads that stay on site.It only enters the picture when local HMI/SCADA screens, large-capacity storage, or image-type processing is needed. On most water utility and HVAC sites, the data work is acquisition, interlocking, and reporting; this kind of heavy load is uncommon.
Choosing what to deploy does not require guesswork. Walk through three questions.
First, can all the data be collected? The interface types and the number of points on site determine whether the gateway's serial ports, Ethernet ports, and acquisition capacity are sufficient. When the point count is especially large or the interfaces are mixed, add a switch for aggregation and add expansion modules. Second, can a broken link be tolerated? If communication between the node and headquarters must not be interrupted, dual channels and local caching are needed — which usually means a gateway that supports 4G and can buffer data locally while the network is down. Third, are there applications that must run on site? An industrial PC only enters the list when such applications genuinely exist.
After these three questions, most water and HVAC projects reach the same conclusion: one industrial gateway handles both the gateway role and the router role; the switch depends on how many devices are connected; in most sites, an industrial PC is not needed.
Take PUSR's USR-M300 edge computing gateway as an example of how far a single-device setup can go. It runs a dual-core Linux system and supports Node-RED graphical programming, so edge logic can be adjusted on site. It supports Modbus RTU/TCP conversion and common PLC protocols, and can acquire data from serial ports, Ethernet ports, and I/O simultaneously, with up to 2000 data points. Interfaces include two serial ports (RS232/485 and RS485), dual Ethernet ports (WAN/LAN reusable), and DI/DO/AI, with an optional 4G global-band version and modular I/O expansion. Routing capability is built in — VPN, firewall, and both 4G and wired channels — which is exactly where the idea of a gateway doubling as a router lands. For on-site conditions: a wide operating temperature range of -25 to 75 °C, a wide-input DC power supply, Level 3 EMC protection, and DIN-rail or wall mounting. Certifications include 3C, CE, FCC, ROHS, and SRRC model approval, among others. The series offers six sub-models, so the final choice follows the serial, I/O, and communication requirements of each site.
A single-gateway setup is not a cure-all: when the number of devices grows to the point where wired aggregation is needed, or heavy local workloads actually appear, a switch and an industrial PC can be added as required. But for most water utility and HVAC sites, starting from one industrial gateway and first getting acquisition, conversion, judgment, caching, and reporting to run smoothly is the more practical way to go.
