Water supply that does not fail.
The Decentralised Water Grid is a business model for water security. The client buys a network of independent water points, called nodes, or pays only for the water they deliver. Each node draws mantle water from deep below, right where people need it. Nodes do not depend on rain or on each other.
It protects a city, a region, an institution or a strategic facility against water shortage.
Illustrative example. With the nodes in service, practically the whole district has access to water: homes, the hospital, the schools, the food processing plant and the field all sit within a node's service area. Nodes are built in order of importance, so protection starts with the first node. Only tested and approved nodes count towards coverage.
- Node in service
- Planned node
- Service area with designed overlap
- Homes
- Hospital
- School
- Food processing plant
- Irrigated field
The problem: everything fails together
A central water system puts all its risk where it puts all its capacity: one intake, one treatment works, one trunk main and hundreds of kilometres of pipes. When one link fails, the whole system fails. And the whole system depends on one thing: the rain that fills the dam or the shallow wells.
A shortage does not arrive in one day. It comes in steps: lower pressure, then rationing hours, then water trucks, then emergency works at several times the normal cost. By the time the shortage shows in the network, the fix takes years.
A resilience shield is built in the years before a drought.
It cannot be bought during one.
What the client buys: independent nodes
The client does not buy a single well. It buys a set of independent nodes, sized, sequenced and commissioned as one system. The grid is built from one repeatable unit: the node.
| Element | What it is |
|---|---|
| Water node | A proven water point. It is sited by Spektral-Q, drilled and built under supervision, and confirmed by an independent pumping test and laboratory analysis. It comes with wellhead, pump, power, controls, as-built records and a contracted yield. |
| Independent node | Each node works on its own. It shares no pipes, no intake and no rain with the other nodes or with the central network. |
| The grid | Nodes planned as one system: placed on a demand map, ranked by how critical each user is, sized with spare capacity, and built in order. |
| Coordination | Monitoring, yield reports, maintenance plans and records for every node, kept in one place and handed over to the operator. |
Every node draws water from outside the rain cycle.
No node depends on the rain, on a trunk main or on another node.
Business models: how the client pays
The client can own the nodes, or pay only for the water they make available. A larger programme combines both over several budget cycles.
| Option | Who carries what |
|---|---|
| The client buys the nodes | The client finances and owns the nodes. The provider carries the geophysical and delivery risk until the approved handover, with a contracted yield warranty. |
| The client buys water availability | The client pays for water that is available, not for infrastructure. Capital and technical risk stay with the provider. The client has a predictable operating cost for a defined service level. |
| A multi-node programme | Nodes delivered in phases over budget cycles, with gate-based milestones suited to results-based or tranche-based funding, and a defined handover of assets and operation. |
In every option the assets stay in the country. Local contractors drill and assemble under supervision. The skills to operate and maintain the nodes are handed over to the operator, together with the records.
The economic case
The grid is compared with what the client is actually paying today: water trucks, delayed pipeline projects or emergency works under pressure. It is not compared with a piped tariff that exists only on paper.
| Cost avoided | How it is measured |
|---|---|
| Trucked and vended water | The delivered cost per cubic metre, against the cost of water from a node. Usually the largest item, and one the client can check from its own invoices. |
| Dry and low-yield boreholes | The written-off cost of failed drilling in the client's own records. |
| Delayed pipeline projects | Major works postponed or avoided in the client's investment plan. |
| Leaks and lost water | Water lost in transport, valued at the delivered cost of water. |
| Emergency premium | The extra cost when works are bought in a crisis instead of to plan. |
| Health | Fewer illnesses and outbreaks to respond to, measured with the financing institution's own method. |
| Time spent fetching water | Hours of work freed, based on standard distance and queuing limits for the people served. |
| Continuous production | Downtime and lost output avoided in farming, food processing and industry that need a steady supply. |
The final measure is the cost of water per cubic metre over the life of the node, set against what the client pays today. Health and productivity gains are supplied as checked data for the financing institution's own appraisal. They are not turned into money here.
Three ways to deploy: Mode A, B and C
The right configuration depends on the existing network and on the client's goal. The three modes are not alternatives. They are stages of one path.
- A
Mode A: connect to the existing network
Nodes feed the existing pipes at a reservoir or pressure zone, as an extra source that does not depend on rain. Institutions, tariffs and the operator stay the same.
Eases peak demand, shortens rationing and delays major pipeline works. The easiest and fastest way to first water.
- B
Mode B: make key sites independent
A hospital, district, factory, mine, campus or strategic facility takes the node as its main supply. The central connection becomes the backup.
The site no longer depends on the network, and the network carries less load. Full replacement for facilities and small settlements; critical users only at city scale (see 7.0).
- C
Mode C: a grid across the territory
Nodes spread across the territory, locally connected, with service areas that overlap.
The full design, built node by node: water security for a whole region.
The usual path is A, then B, then C. Mode A proves performance inside a system the client already trusts. Mode B makes critical sites independent. Mode C extends that to the whole territory. Nothing built at one stage is wasted at the next.
What changes for the territory
| Property | Central system | Decentralised Water Grid |
|---|---|---|
| Climate exposure | One shared driver: rain and recharge. | No shared driver with the rain cycle. |
| Transport of water | Long pipelines, with losses and upkeep. | Water is taken where it is used. No long pipelines. |
| Investment | Large, indivisible, multi-year commitments. | Step by step. Each node is a separate unit that can be financed. |
| Time to water | Years from decision to water. | Weeks per node, with nodes built in parallel. |
| When demand grows | A new scheme is needed. | A new node is needed. |
| Physical security | A trunk main is a single line to defend. | No single line to defend. |
How a grid is sized
A grid is designed, not piled up. Its size follows a published design basis with six inputs:
- the population or load to serve;
- the service level, in litres per person per day;
- a factor for peaks and losses;
- the minimum capacity of a node;
- an operating factor that turns tested capacity into a steady daily rate;
- a spare-capacity allowance for each cluster.
Node capacity is a contractual minimum, not a hopeful estimate. A node is not built where the survey does not show at least that minimum, and every delivered node meets it. Capacity comes from the pumping test, measured against the water level available above the deepest productive zone.
Service levels come from recognised international standards: the Sphere minimum for domestic use, the WHO and UNHCR figures, and the JMP service ladder. They are cross-checked against the national standard. No in-house norm is used, so the financing institution can check every figure against references it already applies.
A shield is sized for what a territory cannot stop using, not for everything it uses.
A single facility or a settlement of up to about 25 000 people can be fully supplied by the grid; that limit follows from the current design basis. A city is covered in tiers. The grid first covers what must never stop: health facilities, water treatment for the wider network, food and cold chains, schools, emergency reserves and strategic industry. That tier is a small part of total use and a programme that can be financed. Coverage then grows outward, as budget and results allow.
The design always follows six steps
- 1
Demand map
Where water is actually used, how much, in which season, against current and future supply.
- 2
Critical users
Which users must never be cut off, and how much water they really need.
- 3
Promising rock
Where the geology allows a node, found by survey, with the number of points to survey per node for each rock type.
- 4
Coverage
Number of nodes, spacing, layout and planned overlap for the area to serve.
- 5
Build order
Most critical and most promising first, so protection starts with the first node.
- 6
Approval gate
No node joins the grid before independent testing. Only approved nodes count towards coverage.
The full model, with the sizing formula and the reference service levels, is set out in the Design Basis Note. Project figures are set in Phase 0 and become binding only at project level.
Grid layouts
The layout follows the shape of the settlement and of the existing network. There is no fixed template.
Point
A single node at the facility.
One hospital, plant, campus or strategic installation.
Star
Several nodes feeding one reservoir or pressure zone.
Mode A integration into an existing network; lowest institutional friction.
Ring
Nodes on the perimeter of the built area, feeding inward.
Compact settlement with a single centre of demand.
Mesh
Regular spacing across the territory with designed overlap of service areas.
Dispersed rural settlement; Mode C. Spacing is set by the maximum acceptable distance from household to water point.
Corridor
Nodes along a road, valley or settlement axis.
Linear settlement patterns, where a regular mesh would be wasted coverage.
Core and shell
A compact cluster covering critical loads, extended outward in stages.
Cities and district capitals; the core is built first and has protective value on its own.
We plan the layout, and the rock decides where nodes can go. The final layout is the planned one matched against the map of promising rock structures. The feasibility phase shows the difference between the two; it is not assumed in advance.
What the grid does not do
A resilience tool that promises too much cannot be relied on when it is needed. So here is what the grid does not claim.
- It does not replace good utility management, demand control or leak repair. A grid built over a badly run network inherits its losses.
- It does not treat polluted or salty surface water or shallow wells. It is a separate source, not a repair of a damaged one.
- It is not emergency equipment. Nodes are planned and commissioned assets. The shield must exist before the shortage, so the time to decide matters more than the time to build.
How to start
Every programme follows four phases. Phase 0 is where the decision is made.
- 0
Feasibility
Demand map, critical users, rock survey, list of candidate nodes with an indicative number of nodes, choice of layout, programme design and financing structure.
- 1
Pilot node
One node delivered end to end under the full testing protocol, in Mode A or Mode B. Proof of performance inside the client's own system.
- 2
Cluster
A small group of nodes for the most critical users. The first measurable protection, with the client's own staff trained to run it.
- 3
Grid
The grid grows to its planned coverage, node by node, following the order set in Phase 0 and updated with each approved node.
After Phase 0, everything is the execution of a plan that already exists.
Contact
To request a Phase 0 feasibility study for a city, region, institution or strategic facility, write to askforaquote@decentralisedwatergrid.com.
Every node is sited by Spektral-Q. Its measurement method, the Drilling Specification and the six-gate testing protocol are described in the Spektral-Q Technology Note.
Read about Spektral-Q