.png)
Retrofitting Older Pumps for Remote Monitoring and Control
- 5 hours ago
- 10 min read
Older pump stations often fail in boring, expensive ways. A float switch sticks. A pressure line blocks. A contactor trips at 2 am. Nobody knows until a tank runs dry, a sump overflows, or an operator drives out to find a fault lamp that has been on for hours.
The good news is that many older pump installations do not need a full control panel replacement to become visible and controllable from anywhere. A practical retrofit can add a PLC, cellular gateway, pressure or level sensors, and a secure cloud dashboard while leaving the existing starters, breakers, contactors, overloads, and selector switches in place.
That approach suits water transfer pumps, wastewater pump stations, irrigation systems, industrial sumps, stormwater pits, booster sets, and remote tanks across Australia. It keeps the electrical work contained, limits downtime, and gives operators the data they actually need: pump status, faults, levels, pressure, run hours, alarms, and remote start or stop where appropriate.
Why retrofit instead of replacing the whole panel
A full panel replacement can make sense when the enclosure is badly corroded, the wiring is unsafe, or the control gear no longer meets the site’s needs. Many older pump panels, though, still do the basic job well. They start motors, protect them from overload, switch between duty and standby, and provide manual control on site.
A retrofit works by adding a new layer of monitoring and control around the existing equipment. The old panel keeps handling the high-power switching. The new equipment handles the information, logic, communications, and alarms.
That separation matters.
Motor control circuits and pump starters are often simple and reliable. Replacing them just to gain remote visibility can add cost and risk. A retrofit lets the upgrade focus on the missing parts:
Knowing whether each pump is running
Seeing water level, tank level, or discharge pressure
Receiving alarms before a spill, dry run, or pressure loss
Tracking pump starts, run hours, and faults
Allowing authorised remote control when the site design permits it
This is often the most sensible first step for ageing infrastructure. It brings the site into the connected era without turning a small upgrade into a major rebuild.
Start with the existing control panel
A good retrofit starts with a site assessment, not a shopping list.
The existing panel must be checked for safety, spare space, wiring condition, earthing, protection, labelling, and available control signals. Some older panels have neat terminal strips and clear drawings. Others have hand-written labels, unused relays, and years of small changes.
The aim is to understand what the panel already provides and what the new system needs to add.
Typical checks include:
Supply voltage and available auxiliary power
Motor starter type, such as DOL, star-delta, soft starter, or VSD
Existing auto and manual controls
Overload, trip, and fault contacts
Pump run feedback
Float switch, pressure switch, or level probe wiring
Available space for PLC, power supply, relays, terminals, and gateway
Enclosure condition and ingress protection
Mobile signal strength at the site
Safe isolation and compliance requirements
If the panel is sound, the retrofit can usually connect through auxiliary contacts, interposing relays, and additional terminals. This avoids interfering with the motor power circuit more than necessary.
If the panel is unsafe, water-damaged, or overloaded with undocumented wiring, the best answer may still be a staged replacement. Remote monitoring should never be used to hide poor electrical condition.
The main parts of a pump monitoring retrofit
Most pump retrofit systems use a small set of well-understood components. The design changes from site to site, but the pattern is usually the same.
Component | What it does | Common examples of signals |
PLC | Reads field inputs, runs local logic, and controls outputs | Pump run, fault, auto mode, start command |
Cellular gateway | Sends data to the cloud using the mobile network | 4G or 5G data link, VPN, MQTT, HTTPS |
Sensors | Measure the actual process condition | Pressure, level, flow, temperature |
Secure cloud dashboard | Displays status, trends, alarms, and history | Pump state, trends, notifications, reports |
Interposing relays | Separate old control circuits from new PLC outputs | Remote start enable, reset pulse, alarm output |
Power supply and protection | Provide safe low-voltage power | 24 V DC supply, fuses, surge protection |
The PLC is the local brain. It should keep doing its basic job even if the mobile network drops out. For example, a tank transfer pump should still respond to local level signals and stop on a fault. The cloud dashboard improves visibility, but it should not be the only thing keeping the site safe.
The cellular gateway provides the link. For many rural and semi-rural pump sites, mobile data is more practical than fixed internet. The gateway needs a suitable antenna, a suitable data plan, and a secure method of connecting to the cloud system.
The dashboard gives operators a clear view. It should show current status at a glance, then allow more detail when needed. A screen full of raw tags is not helpful during a fault callout. A simple display that shows Pump 1 running, Pump 2 available, Wet well level high, and Last communication 2 minutes ago is much more useful.
Sensors turn pump status into useful information
A pump run signal tells you that a motor starter pulled in. It does not prove that water is moving, pressure is building, or a tank is filling.
That is why pressure and level sensors are central to a useful retrofit.
Pressure sensors
Pressure transmitters are common on booster systems, irrigation mains, filter feeds, and transfer lines. A typical sensor sends a 4 to 20 mA signal back to the PLC. The PLC scales that signal into kilopascals, bar, or metres of head, depending on the site standard.
With discharge pressure available, the system can detect problems such as:
Pump running with low pressure
High pressure against a closed valve
Pressure loss after hours
Blocked filters or rising system resistance
Uneven performance between duty and standby pumps
Pressure trends also help maintenance planning. If a pump takes longer to build pressure than it used to, that may point to wear, air ingress, blockage, or valve issues.
Level sensors
Level measurement suits tanks, sumps, pits, wells, and wet wells. Depending on the environment, the retrofit might use an ultrasonic sensor, radar sensor, hydrostatic probe, or existing float switches.
Analogue level sensors give richer data than basic floats. Instead of only knowing “high” or “low”, the operator can see the level rising, falling, and responding to pump operation.
That supports better alarms, such as:
High level warning before high-high trip
Low level cut-out to protect the pump
No level change while pump is running
Rapid rise rate during storm inflow
Long run time without expected level drop
Floats still have value as independent backup devices. In many sites, the best setup uses an analogue level sensor for control and trending, with high-high floats wired as a separate alarm or safety function.
Remote control needs clear rules
Remote monitoring is usually simple to justify. Remote control needs more thought.
Starting or stopping a pump from a cloud dashboard can be useful, especially for unmanned sites. It can help an operator reset a duty sequence, run a standby pump for testing, or stop a system during a fault. Yet remote control should never bypass local safety devices or create risk for people working on site.
A sound retrofit design uses layers of permission.
The existing local controls should remain in charge of safety. Emergency stops, overloads, isolation switches, low-level protection, high-pressure trips, and critical interlocks must still stop the pump regardless of any remote command.
Remote control can be limited by conditions such as:
Panel selector switch must be in `Auto`
Local isolator must be closed
No active overload or critical fault
Level or pressure must be within a safe range
Remote command must time out if not confirmed
Manual local control must override remote control
All commands must be logged with user and time
For many systems, remote start does not need to energise the motor directly. The PLC can request a start through an interposing relay, while the original panel logic decides whether the pump is allowed to run. This keeps the old protective circuit active.
A practical example is a tank fill system. The cloud dashboard may include a remote `Start Fill` command. The PLC accepts it only if the panel is in auto, the source tank is not low, the destination tank is not full, and no fault is active. If the mobile signal drops after the command, local control still stops the pump when the destination level reaches its setpoint.
The cloud dashboard should show decisions, not just data
A cloud dashboard can quickly become cluttered. Every PLC has plenty of signals, but not every signal deserves a place on the main page.
The best dashboards answer a few questions fast:
Is the site online?
Are the pumps available?
Which pump is running?
Is the level or pressure normal?
Are there active alarms?
When did the state last change?
Has the pump been running too long?
Does the trend look normal?
A simple pump station dashboard may include:
Site communications status
Pump 1 and Pump 2 run status
Pump 1 and Pump 2 fault status
Auto, manual, or off position
Wet well level trend
Start count per pump
Run hours per pump
Alarm list with acknowledgement
Remote command history
Maintenance notes
Alarms should be useful and limited. If every small state change sends a text message, people start ignoring the system. Alarm delays, deadbands, and escalation rules help reduce nuisance alerts.
For example, a pressure system might send a warning if pressure stays low for 60 seconds while a pump is running. It might send a higher priority alarm if pressure remains low after the standby pump starts. The first alert tells maintenance to check the system. The second tells operations that supply may be at risk.
Security must be built into the retrofit
Any remote access system needs good security from the start. Pump sites may not look like obvious digital targets, but they control real equipment in the physical world.
A secure design avoids exposing the PLC directly to the public internet. The cellular gateway should connect outbound to a trusted cloud service or use a managed private network. Remote users should sign in with individual accounts, strong passwords, and multi-factor authentication where available.
Good practice includes:
Encrypted communications between gateway and cloud
No open inbound ports to the PLC where possible
User roles for view-only, operator, and administrator access
Logged remote commands and alarm acknowledgements
Regular firmware updates for gateways and connected devices
SIM and data plan management
Clear offboarding when staff or contractors leave
Backups of PLC and dashboard configuration
Physical security also matters. A locked enclosure, protected antenna cable, labelled isolators, and tidy wiring reduce the chance of tampering and accidental damage.
For critical water, wastewater, or industrial services, the retrofit should align with the site’s wider operational technology policies. If there is no policy, the upgrade is a good time to create simple rules for access, passwords, backups, and change control.
A typical staged retrofit process
A retrofit is less risky when done in clear stages. This also helps keep the pump installation available during the work.
Assess the site and agree on the control intent
The first stage is to document how the pump system works now and how it should work after the upgrade. This includes normal operation, fault behaviour, local manual control, remote control limits, and alarm priorities.
This step should involve the people who maintain and operate the site. They often know the real failure modes better than the drawings do.
Design the interface to the existing panel
The next step is deciding how the PLC will read and control the old panel. Digital inputs may read pump run, fault, auto mode, high level, or low level. Analogue inputs may read pressure or level transmitters. Relay outputs may provide start requests, reset commands, or alarm contacts.
Interposing relays are useful because they separate the new low-voltage PLC system from older control circuits. They also make testing and fault finding easier.
Install sensors and communications hardware
Sensors need careful mounting. A pressure transmitter should have isolation valves and suitable fittings. A level sensor should avoid turbulence, foam, obstruction, and cable damage. A cellular antenna should be placed where signal is reliable, not just where it is easy to mount.
Surge protection is sensible for remote sites, especially where long cable runs, outdoor sensors, and exposed equipment are involved.
Configure the PLC and dashboard
The PLC program should be simple, readable, and well labelled. The dashboard should use plain names that match site language. Operators should not need to decode `DI_07` during an alarm.
Useful names look more like:
`Pump 1 Running`
`Pump 2 Fault`
`Wet Well Level`
`Discharge Pressure`
`Remote Start Enabled`
`Comms Healthy`
Trends should be set up for level, pressure, run hours, starts, and any values linked to frequent issues. Alarm thresholds should be tested against real operation, then adjusted if they cause nuisance alerts.
Test locally before enabling remote commands
Before remote control goes live, every local function must be tested. Start, stop, auto operation, manual operation, fault trips, level cut-outs, and alarms should behave as expected.
Remote commands should then be tested under controlled conditions. The test should include failed commands, loss of communications, active faults, and local override. A retrofit is only finished when the unwanted actions have been tested as carefully as the desired actions.
What success looks like after the upgrade
A successful retrofit does not draw attention to itself. It makes the old pump station easier to trust.
Operators can open a secure dashboard and see the site condition in seconds. Maintenance staff can compare pump run hours before choosing which pump to service. Alarms arrive early enough to prevent avoidable callouts. Remote sites no longer need routine inspection visits just to confirm that everything is normal.
The signs of a good result include:
Fewer blind callouts
Faster fault diagnosis
Clearer pump duty history
Better balance between duty and standby pumps
Earlier warning of abnormal level or pressure
Less time spent travelling to check simple faults
A safer split between local protection and remote operation
Just as important, the existing control panel still works in a familiar way. Local operators can use the selector switches, isolators, and manual controls they already know. The new system adds visibility and controlled remote access without making the site harder to maintain.
The best retrofit keeps old strengths and adds new visibility
Retrofitting older pumps is rarely about adding technology for its own sake. The real value comes from using a PLC, cellular gateway, sensors, and secure cloud dashboard to answer basic operational questions before they become urgent problems.
The existing panel can keep doing what it already does well. The retrofit adds measured level or pressure, clear alarms, run history, secure remote access, and better control rules. That combination can extend the useful life of a pump installation while making it safer and easier to manage.
For many older pump sites, that is the right balance: keep the proven hardware, add the missing intelligence, and make every callout better informed.
