Daily demand and reserve should be entered explicitly.
RHELGAN · WATER STORAGE
Water storage planning for remote and humanitarian programmes.
Tank volume should be the result of a demand-and-resilience calculation, not a guess based on the number of buildings.
SHORT ANSWER
Storage volume is a demand, source-reliability and autonomy decision.
Start with daily demand, source yield/reliability, refill frequency, treatment throughput, reserve policy and seasonal risk. Then select tank type, modularity, foundation, inlet/outlet arrangement, pumping and distribution around the actual site.
KEY PROJECT POINTS
What should drive the decision.
These are project inputs, not substitute engineering or automatic product approvals.
Reliable municipal supply and intermittent bore supply need different autonomy.
Treatment throughput can become the real bottleneck.
Tank material and format must fit freight and assembly conditions.
Foundation and structural requirements are project-specific.
Water quality protection continues through storage and distribution.
COMPARISON
Use-case fit before product preference.
The table is deliberately directional. Exact configurations still require project and evidence review.
| Pathway | Best fit | Watch closely |
|---|---|---|
| Sectional / panel tank | Larger site-assembled storage where container freight and modular expansion are valuable. | Foundation flatness, panel/joint system, access, cleaning and exact potable-water evidence. |
| Factory tank / rigid tank | Smaller capacities and sites with straightforward transport access. | Transport envelope, unloading, UV/environment and site access. |
| Flexible / temporary tank | Rapid-response or temporary storage where speed and packability dominate. | Ground preparation, puncture risk, water-contact evidence and shorter service assumptions. |
Calculate demand before capacity
Use project-entered litres-per-person or institutional demand, fixed process loads, operating days and reserve. Avoid hiding assumptions in a default tank size.
Model source reliability
A bore, rainwater source, municipal connection and trucked water all have different failure modes. Storage should reflect the realistic refill pattern.
Coordinate treatment and distribution
Raw-water storage, treated-water storage, chlorination, pumps and distribution pressure may require separate tanks or zones.
Design for inspection and cleaning
Access, drain-down, internal cleaning, level monitoring, overflow, screens and spare seals/valves should be part of the procurement scope.
PROJECT INPUTS
What to have ready before asking for the exact system.
A stronger brief shortens the gap between product interest and a useful technical/commercial response.
Daily demand basis
Peak/seasonal demand
Source type and yield
Refill frequency
Treatment flow rate
Required autonomy
Reserve percentage
Tank location/elevation
Foundation/ground condition
Distribution/pump requirement
Potable/non-potable use
Freight/site access
EVIDENCE BOUNDARY
A tank datasheet is not the complete water-system evidence package.
Verify exact tank materials, seals, structural configuration, potable-water evidence where applicable, foundation requirements, valves/fittings and cleaning/maintenance documentation against the selected configuration.
FAQ
Questions project teams usually need answered.
How many days of water storage should a remote site have?
There is no universal number. It depends on source reliability, refill logistics, criticality, treatment capacity and the programme's resilience policy.
Can storage volume be based only on litres per person?
No. Add institutional/process loads, reserve, losses, peak demand and source/refill constraints.
Does Apollo design the tank foundation?
Apollo can provide product/interface information; the local appointed team remains responsible for site-specific structural/foundation design unless expressly included.