Remote monitoring for pumping stations and water systems
Last updated on 22 September 2026
Distributed pumping stations and water installations need both visibility and targeted service access. A ServiceGate can make the agreed OT segment reachable and collect controller data. The right setup starts with the installed PLC or RTU and the operator’s requirements.
Access
Reach only the agreed controller.
Data
Read selected measurements.
Configuration
Validate the integration before use.
Remote Engineer · Knowledge base
What problem does this address?
A “pump fault” alert does not tell you whether the pump, controller or connection is responsible. Looking at water level, operating status, running hours and connection status together gives maintenance teams more clues. Distinguish a process alarm from missing recent data.
Brands, controllers and protocols
Schneider Electric SCADAPack: controlled telemetry access
Schneider lists Modbus, DNP3 and IEC 60870 for the SCADAPack 470 RTU. Check the project configuration for the actual variant and available data. Transporting IP traffic through a VPN is not the same as having a suitable logging driver. Assess DNP3 or IEC 60870 separately; do not simply replace an existing telemetry connection.
ABB AC500: register mapping matters
ABB documents AC500 water applications and Modbus TCP communication in the processor. An available Modbus server can be assessed as a source of agreed registers. Define status bits, level measurements and counters precisely. A register address without its data type and scaling factor is not enough for reliable dashboards.
Connecting the ServiceGate
Connect the ServiceGate to the agreed controller network, not indiscriminately to every network segment. Create a location and suitable user groups for each station or installation. Check the service route and test data collection in read-only mode first. Compare levels, pump states and totals with the local display. Choose an interval that captures the process without placing unnecessary load on the controller.
From a connection to useful insight
Example setup: when the level is high, you need to know whether the pump is running and the values are current. Configure separate alerts for process deviation and connection loss. If logging must continue locally during an internet outage, explicitly design and test buffering duration, storage, clock synchronisation and retransmission. A router alone does not guarantee them. Local protective functions remain authoritative.
Remote access and data logging, with clear boundaries
All ServiceGate routers support remote access and data logging/monitoring. The actual integration depends on model, firmware, interface and configuration. With VPN, your computer connects to the authorised location; configured VNC, RDP, HTTP or HTTPS services provide another access route through the portal. For logging, configure the protocol, data points and destination. The router receives that configuration and forwards data to the relevant service. Then configure dashboards, alarms and events. A named brand is a technical example, not a statement of certification, partnership or support for every model.
Permissions and traceable connections
Assign routers to locations and grant users or groups only the permissions they need. The portal shows who connected to which location. This records connections, not automatically every action inside the machine. For audit purposes, also define retention periods and any additional log sources. Agree a firewall profile for each customer or location, such as deny by default with explicit exceptions. Segmentation does not replace controller and machine security updates.
What do we need to assess your integration?
- Brand, exact model, firmware and installed software licences.
- Network diagram, IP addresses, interfaces and the owner’s approval.
- Required service tasks and the people who may access the installation.
- Measurements with register or object lists, units and collection intervals.
- Requirements for alarms, retention and any on-site logging during connection loss.
Remote Engineer has worked on remote access and controller solutions since 2008. Share your documentation and application with our team. We assess what is standard and where configuration or custom development is needed. Contact us for pricing and a suitable proposal.
Continue with your application
Sources and scope
Manufacturer documentation consulted on 22 September 2026. The examples describe possible architectures, not completed integration tests or customer results. Always check the exact model’s documentation before implementation. Trademarks belong to their respective owners.
In this article
