A water supply SCADA system should help an operator answer practical questions: Is the pump actually running? Is water reaching the tank? Has the supply stopped because of an electrical fault, an empty source or a communication problem?
A dashboard showing a green pump icon is not enough. The quality of the system depends on the information collected at site, the control rules and the response when something goes wrong.
For village water schemes, campuses and pump houses, start with operating requirements before comparing screens or quotations. These seven checks can help you prepare a clearer project scope.
What does water supply SCADA do?
SCADA means Supervisory Control and Data Acquisition. It brings information from field equipment into a common interface and can support authorised remote operation.
A project may combine pump status, tank levels, pipeline flow, electrical readings and alarms. Actual functions depend on the installed instruments and agreed configuration. Kewintech provides project-specific monitoring and control solutions for water-supply and pump-house applications.
1. Separate a start command from running confirmation
A remote start command tells the controller what an operator wants. It does not, by itself, prove that the motor started or that water is moving.
Ask the supplier how the system confirms each stage:
- Command received by the controller.
- Starter or contactor operation confirmed.
- Motor operating condition checked.
- Water movement measured, where instrumentation is provided.
The screen should distinguish these states instead of presenting every successful command as successful pumping.
सरल भाषा में: “मोटर चालू करने का आदेश गया” और “पानी आ रहा है” अलग बातें हैं।
This distinction helps an operator investigate a failed start without repeatedly sending commands.
2. Define tank-level and source-water requirements
Before selecting sensors, list every storage point: underground sump, source reservoir, overhead tank and any intermediate tank.
Decide whether operators need continuous level readings or only specific conditions such as low level and high level. Sensor selection should consider the tank arrangement, installation access and maintenance needs.
Agree on the control sequence
Write down when a pump may start, when it must stop and what should happen if a level signal becomes invalid.
Avoid a vague requirement such as “automatic tank filling.” Specify which tank controls the pump and whether source-water availability is a start condition.
The design should address frequent switching around a level threshold, using suitable separation between start and stop conditions and manufacturer-approved timing.
3. Measure water delivery, not only operating hours
Pump running hours are useful, but they do not show how much water reached its destination.
Where flow measurement is included, ask for instantaneous flow and a totalised volume reading. Confirm displayed units and whether totals represent a shift, a day or the meter’s cumulative reading.
Meter suitability depends on the pipeline and operating conditions. Share pipe material, diameter, accessibility and whether the pipe remains full. Installation requirements must follow the selected meter’s documentation.
Use trends to guide investigation
A pump running while measured flow remains unexpectedly low deserves attention. However, that pattern alone does not prove leakage.
Possible explanations include valve position, source conditions, pump performance or measurement problems. SCADA should help narrow the investigation, not turn an uncertain observation into a definite diagnosis.
4. Make alarms useful to the person responding
A long alarm list can look impressive while offering little practical help.
Start by identifying conditions requiring action: pump trip, abnormal tank level, communication loss or missing flow when pumping is expected. Include only alarms supported by suitable signals and agreed logic.
Each alarm should identify the site, equipment, condition and time. Agree on who receives it, which delivery channel is included and what happens if nobody acknowledges it.
For example, “Pump House A: running feedback missing after start request” is more useful than “Error.”
Separate alarm acknowledgement from fault clearance. Acknowledging a message should not make an unresolved condition appear healthy.
5. Ask what happens when connectivity fails
Remote water-supply sites may experience communication interruptions. Ask for a written explanation of operation during an outage.
Will approved local control continue? What information will be stored? Will missed records upload after reconnection? How will the dashboard show that displayed values are old?
Display the last update clearly
A stale reading must not look like a live measurement. Operators should see the last communication time and recognise when remote status is uncertain.
Define how remote commands behave during disconnection and reconnection. Do not assume a delayed command will remain appropriate when the connection returns. These behaviours should be demonstrated during commissioning.
6. Keep access and local operation clearly defined
Not everyone who views the dashboard should be able to start a pump or change operating settings.
Specify separate permissions for viewing, operating and configuration. Request individual accounts and an activity record where these are part of the project scope.
Local and remote operating modes should be clearly indicated. Maintenance arrangements must prevent unexpected remote operation, using procedures and isolation designed by qualified personnel.
SCADA does not replace electrical protection, safe isolation or on-site maintenance. Panel design, protective devices and wiring require competent engineering review.
7. Test the complete sequence before handover
Prepare an acceptance checklist before installation, not after the dashboard is ready.
Ask the commissioning team to demonstrate normal starts and stops, relevant tank-level conditions, missing feedback, communication failure and recovery. Fault simulations should use an approved safe test method.
Check that event times, equipment names, alarm messages and reports match the site.
Handover should include operating instructions, drawings, instrument details, access arrangements and support responsibilities. Confirm recurring connectivity or software costs in the quotation without assuming they are included.
A practical village-water example
Consider an illustrative scheme where a borewell fills an overhead tank. The operator receives a complaint that supply is unavailable.
Useful monitoring separates the questions: Was a start requested? Did the motor run? Was flow recorded? Did the tank level rise? Are the readings current?
That sequence gives maintenance staff a clearer starting point. It is not a claim that software can identify every fault or eliminate site visits.
Frequently asked questions
Can SCADA work with an existing pump panel?
Often, integration is possible, but compatibility requires inspection of the starter, available signals, protection and control circuit. Do not assume every panel can be connected without modification.
Is internet required for every automatic action?
Remote monitoring needs a working communication path. Properly specified local automation may operate independently, but that behaviour must be confirmed for the proposed system.
Does SCADA guarantee electricity savings?
No. It can help identify unnecessary running and operational problems. Savings depend on the original installation, operating practices and corrective action.
What should I send when requesting a quotation?
Share site location, pump details, panel photographs, tank arrangement, pipeline information, connectivity conditions and required monitoring points.
Discuss your water-supply project with Kewintech
Planning a new installation or upgrading an existing pump house? Share your requirements with Kewintech Private Limited for a project-specific discussion.
Send your name, mobile number, location and pump/tank details. Request a clearly defined monitoring, control and commissioning scope before finalising the system.