← Back to project catalogue
GP-CV-0FX1Y4MCivilOpen for request

Rural water-supply monitoring system

A monitoring and analysis system for studying continuity, storage, flow, pressure, and selected water-quality indicators in a model rural water-supply scheme.

  • Nuxt
  • Vue
  • FastAPI
  • PostgreSQL
  • PostGIS
  • Python
  • EPANET
  • Docker

Project definition

Problem statement

Rural piped-water schemes can experience intermittent supply, tank overflow, low pressure, leakage, sensor failure, and delayed maintenance, while field records and measurements may be incomplete.

The engineering problem is to combine a simplified network model with traceable telemetry checks and service indicators so that abnormal conditions can be identified without claiming control of the real scheme.

Project objectives

  • Model source, treatment, storage, pipes, valves, pumps, zones, and delivery points for a prepared scheme.
  • Process flow, level, pressure, pump-state, and selected quality observations with unit and range checks.
  • Compare measured or simulated inflow, storage change, and delivery through a water-balance calculation.
  • Detect prepared leakage, low-pressure, overflow, sensor, and supply-interruption scenarios.
  • Record alerts, inspections, maintenance actions, and service-level measures.

System design

System modules

01

Asset and network registry

Stores mapped assets, connectivity, elevation, capacity, operating limits, and service zones.

02

Telemetry processor

Validates timestamps, units, gaps, duplicates, ranges, rates of change, and sensor status.

03

Hydraulic and balance analyser

Compares prepared pressure and flow behaviour with network expectations and interval water balances.

04

Anomaly detector

Applies transparent rules and selected statistical methods to prepared failure scenarios.

05

Operations dashboard

Shows maps, tank levels, flow, pressure, quality indicators, alerts, service continuity, and maintenance history.

Methodology

System workflow

  1. 01
    Load scheme

    The student opens a prepared network with asset, demand, elevation, and operating data.

  2. 02
    Run baseline

    A normal-day simulation or prepared telemetry set establishes expected ranges and balances.

  3. 03
    Introduce scenario

    A leak, pump outage, sensor drift, overflow, or supply interruption is applied.

  4. 04
    Analyse

    The system validates signals, checks balances, identifies affected zones, and raises evidence-linked alerts.

  5. 05
    Record action

    An inspection or maintenance response is logged and the post-action condition is compared.

Demonstration scenario

A prepared village scheme supplies two zones from an elevated tank. A simulated leak increases night flow and lowers pressure in one branch. The dashboard detects the balance change, identifies the affected zone, records an inspection, and compares the indicators after the leak is removed.

Engineering

Technical architecture

Web application
Nuxt and Vue for network maps, asset records, telemetry charts, alerts, and maintenance workflows.
Monitoring API
FastAPI for assets, time series, network scenarios, analysis jobs, alerts, and exports.
Spatial data layer
PostgreSQL and PostGIS for assets, network geometry, service zones, observations, and events.
Engineering model
EPANET-compatible prepared simulations and Python checks for flow, pressure, storage, and balance behaviour.
Verification
Known network cases, injected sensor faults, balance calculations, and manually checked service indicators.

Testing

Evaluation

Evaluation measures

  • Water-balance closure error in prepared normal scenarios
  • Detection precision and recall for prepared leakage, pressure, overflow, and sensor faults
  • Alert delay and affected-zone identification accuracy
  • Agreement with prepared EPANET pressure and flow results
  • Completeness of service and maintenance records
  • Processing and map response time across network and telemetry sizes

System boundaries

  • The prototype uses prepared, simulated, or explicitly permitted scheme data.
  • It does not operate pumps, valves, chlorination equipment, or other field controls.
  • Selected quality indicators are monitoring inputs and do not certify that water is safe to drink.
  • Engineering and public-health decisions require field verification by qualified authorities.

Included

  1. 01Water-network map and monitoring interface
  2. 02Telemetry validation, balance, anomaly, and service modules
  3. 03Pressure, flow, storage, quality, and maintenance dashboards
  4. 04Prepared network model, sensor scenarios, and test results
  5. 05Complete source code in a private GitHub repository
  6. 06Complete project documentation with synopsis, abstract, methodology, network diagrams, analysis results, screenshots, and conclusion
  7. 07Setup and usage guide

Project record

No buyer information is collected on this page.

Permanent project ID
GP-CV-0FX1Y4M
Catalogued
21 Aug 2026
Completed
Pending
Verified
Pending
Demonstration
Added when ready

Handover

After purchase

  1. 01
    Payment is confirmed

    The project is marked unavailable and cannot be purchased again.

  2. 02
    Repository access is granted

    The buyer's submitted GitHub account receives access to the private repository.

  3. 03
    The purchase record is delivered

    The certification sheet is prepared from the reviewed buyer details and sent privately by email.