Gateways, Edge Computers, and RTUs
Gateways, Edge Computers, and RTUs
Section titled “Gateways, Edge Computers, and RTUs”These categories overlap just enough to confuse many buying decisions. The right answer depends less on marketing language and more on how much control logic, compute ownership, and field reliability the site actually requires.
Use a gateway when
Section titled “Use a gateway when”- Protocol translation and upstream connectivity are the primary job.
- The site does not justify a heavy local software footprint.
- The operating model favors simpler deployment and lower maintenance overhead.
Use an RTU when
Section titled “Use an RTU when”- Remote monitoring and deterministic light control are central requirements.
- Field reliability and low-touch operation matter more than local application flexibility.
- The team wants a control-oriented remote asset footprint.
Use an edge computer when
Section titled “Use an edge computer when”- Local analytics, storage, custom applications, or complex integrations are required.
- The team can own patching, software updates, and application lifecycle tasks.
- The site benefits from compute flexibility more than appliance simplicity.