Take this proposed control-system change as an example. An OEM controller supplier says a software update improves pump operation, while the enclosure, circuit board and bill of materials remain unchanged. Is the old approved sample still sufficient? No. Executable control logic can change start delays, restart behaviour, fault handling and alarms without changing the visible hardware. Treat the update as an identifiable configuration change and approve the functions it can affect.
Begin with the functions that actually depend on software
This applies to a supplied electronic controller or external control system. It does not imply that a mechanical float-operated pump contains updateable firmware. Identify the controller, hardware revision, software version and parameter set that belong together. A version displayed by an app may refer to the app or gateway rather than the logic commanding the pump.
Ask for release notes describing behaviour, affected models, required hardware and compatibility with saved settings. “Bug fixes” is not enough to assess whether a previous start sequence has changed. Retain a way to identify the production-loaded version, using approved readout or production records rather than opening a live controller.
Test transitions, not only a steady pumping run
A controller can run the pump normally for ten minutes and still mishandle the next loss of power. Make the acceptance matrix follow the changed state transitions: level rises, level falls, supply fails, supply returns, a sensor becomes invalid, a fault clears and an alarm is acknowledged. Verify only through the maker's approved simulation or test arrangement; do not short protective inputs or create hazardous pump operation.
| Transition | Compare with the released requirement |
|---|---|
| Power restored with a standing demand | Automatic restart, retained mode or required reset |
| Brief sensor disturbance | Filtering, delay and eventual safe response |
| Fault clears | Whether restart is allowed and what remains latched |
| Settings imported | Units, scaling, limits and defaults |
| Network unavailable | Local control and alarm behaviour |
Select regression checks around the change and other safety-relevant functions that share its logic. A firmware update to an alarm delay might also alter a shared timer. The amount of testing depends on the change assessment, not merely on how few lines the supplier says were edited.
Preserve the installed parameter meaning
For an illustrative change, an earlier version stores a delay as a number of tenths of a second, while a new parameter interface expects seconds. Importing the same raw number without the required conversion would change behaviour. This is a hypothetical compatibility issue, not a reported product fault. Record both displayed engineering values and the supported transfer method.
Test factory defaults separately from the approved customer settings. Confirm whether an update resets operating mode, level offsets, motor settings or communication credentials. A replacement controller that powers up successfully has not necessarily inherited the installation's valid configuration. Supply the service team with the applicable settings and identification method for the affected serial range.
Release the new version through the existing change record
Keep the approved package, validation evidence, hardware applicability, first production lot and instructions connected. Control programming stations and unprogrammed boards so that an old image cannot reappear unnoticed after a station restart. Where rollback is permitted, confirm that the earlier image also supports the current hardware and settings; never assume every downgrade is safe.
Do not automatically update installed drainage protection during a storm or an unattended critical duty. Qualified personnel need a maintenance window, suitable backup and a way to restore a verified working configuration. Recheck actual wet start and stop behaviour after the change under the approved procedure.
For small sump and drainage pumps sold with external electronic controls, the purchasing deliverable is a defined pump/controller combination. Unchanged plastic and wiring do not prove unchanged behaviour. Conversely, a carefully bounded software correction need not become an unrelated redesign: document the affected functions, test them and preserve traceability through production and service.
Frequently asked questions
Can the circuit-board part number identify the software?
Only if the controlled configuration explicitly links them. Several program versions can exist on the same hardware part number.
Is an update successful when the download tool reports completion?
That establishes transfer status. Confirm the installed identity, correct settings and required functional checks before release.
Must old controllers all be updated immediately?
Not automatically. Determine applicability, risk, field conditions and compatibility through the approved change plan; distinguish required corrective action from an optional improvement.
