Map the package before counting panels
Main switchboard
Incoming sources, distribution and agreed protection interfaces.
MCC & pump feeders
Starting equipment, protection and local operating interfaces.
PLC, telemetry & field signals
Commands, measured conditions, alarms and the approved operating sequence.
The diagram is a scope map, not a wiring design. Some projects combine functions in one assembly; others separate them for access, environment or project delivery. Decide the functional boundaries before assigning suppliers.
Include the auxiliary supplies needed to make the controls work. Identify which circuits need continuity through a supply disturbance and who defines any UPS or DC system. The availability of a pump is affected by its control and auxiliary arrangements as well as its power feeder.
Define duty and standby in operating terms
“Two pumps, duty/standby” is an incomplete functional description. Explain how the duty pump is selected, whether both may run, what allows changeover and what the operator can command locally. Establish what should happen after a motor trip, a missing process signal or a return of supply.
The process designer should define the required response. A water-supply booster, stormwater installation and wastewater transfer station can have different consequences when a pump stops or continues running. Do not copy the sequence from another site simply because the motor ratings match.
Record the motor duty, starting load, operating frequency, sensors and any supplier limits on starts or speed. For drive-controlled pumps, provide the required operating range and feedback arrangement. Pump starting and stopping may also need a hydraulic assessment; electrical controls alone do not establish acceptable pressure behaviour.
Give each interface an owner
| Interface | Define before manufacture | Acceptance evidence |
|---|---|---|
| Power to packaged plant | Supply characteristics, protection boundary, cable and terminal requirements. | Approved connection schedule and site termination checks. |
| MCC to PLC | I/O list, signal type, auxiliary voltage and local-control authority. | Factory point checks and the agreed functional simulation. |
| PLC to field devices | Device supply, ranges, wiring, scaling and fault interpretation. | Field-loop and instrument checks by the allocated party. |
| PLC to telemetry or SCADA | Protocol, addressing, alarms, commands and access requirements. | Integration tests with the actual destination system. |
| Software and settings | Who develops, approves, loads and retains the versions. | Identified software, parameter and backup records. |
| Complete operating sequence | Process acceptance criteria and test responsibilities. | Site acceptance against the approved functional description. |
Do not use “by others” without identifying the relevant package and deliverable. A controls integrator may be responsible for software while the board builder is responsible for internal wiring. The installation contractor may complete external cabling and testing. Put the actual allocation in the contract documents.
Where remote access is required, have the asset owner’s IT or operational-technology team approve the access method, accounts and network boundaries. A communication port does not constitute an approved remote-access arrangement.
Test the exceptional states on paper first
The duty feeder trips
Specify how the fault is detected and presented, who can reset it and what conditions permit another pump to operate.
A level or pressure signal fails
Define how an invalid signal is recognised and the approved response. Do not assume a failed input should look like a real zero reading.
Communications are lost
Distinguish loss of local controller communication from loss of remote telemetry. The required process response can be different.
Supply returns
Define the permitted restart sequence, operator actions and any limits on simultaneous starting.
These are questions for the approved design, not universal fallback instructions. Agree the intended behaviour with operations before hardware and software acceptance tests are finalised.
Separate factory evidence from site performance
The factory can check the manufactured assembly, internal wiring and agreed signals or control simulations. It cannot establish actual wet-well behaviour, pump hydraulic duty or field-instrument accuracy without the relevant equipment and conditions.
Make a factory/site test split. For each requirement, identify the method, location, responsible party and evidence. Carry unresolved dependencies into the site plan rather than recording a simulated test as proof of a complete installed function.
Treat drawings and software versions as part of the test record. If the site integrator changes an I/O allocation or sequence after FAT, identify the affected documents and tests. The handover package should show the installed result. CWS automation and control panels can be supplied within an agreed manufacturing and interface scope.
A documented CWS water-project example
For Frimley and Eastbourne drinking-water infrastructure, CWS manufactured main switchboards, MCCs and control panels supplied to ICE Electrical for Hastings District Council. The published scope includes panel manufacture, wiring, I/O termination and FAT. Project integrators carried out software programming and site commissioning.
That example illustrates a clear package boundary. It is a drinking-water reference, not a wastewater case study or a claim that CWS supplied every part of the control system.
For your next package, send the board list, motor schedule, functional description and proposed division of responsibility. Add required delivery dates and the acceptance stages so the MCC manufacturing scope can be developed.
