Rainwater Harvesting Tank For A Data Centre: Capture, Storage And Reuse
Created on Today
Rainwater Harvesting Tank For A Data Centre: Capture, Storage And Reuse
A data centre rainwater harvesting tank is sized from the catchment yield against rainfall seasonality, not from the roof area alone, and the captured water is treated to the duty standard before use. The realistic duties are cooling make-up and non-potable uses; the value is a weather-aware supply that displaces municipal draw and improves the site water balance, bounded by capture variability and treatment cost.
Introduction
Rainwater harvesting on a data centre site starts with a simple observation: a large roof and a hardstanding shed water that is currently sent to drain, while the cooling plant draws municipal water it could partly replace. Capturing that rain turns a discharge into a supply, and the tank is the asset that makes the capture usable, holding the variable rainfall as a buffer the plant can draw from.
This article works through the capture and storage chain from the buyer's side. It covers how much water a site can actually capture, how the storage volume is set against rainfall seasonality, how the collection system and tank are sized, the treatment the harvested water needs to meet the duty, which duties can realistically use it, the cost and maintenance picture, how the harvested volume is reported, and the limits and objections that decide whether the system is worth building.
How much water a site can capture
Capture starts with the catchment: the roof area and any hardstanding diverted to the system, each multiplied by its runoff coefficient and by the rainfall depth, to give a volumetric yield. The rational relationship is yield equals catchment area times coefficient times rainfall, and the roof dominates because it is large, has a high coefficient and, being above ground contact, stays relatively clean. The hardstanding adds volume but adds load.
The number that matters is not a single annual total but the distribution across the year, because a system sized to the annual average captures little of value if the rain falls in a few storms the tank overflows. The capture is therefore expressed as a yield curve against rainfall frequency, from which the usable capture, after first-flush diversion and losses, is drawn. A site in a high-rainfall region captures more but more variably; a dry-site capture is smaller and must be sized honestly against the dry-season shortfall it cannot cover.
Storage volume against rainfall seasonality
The tank volume is the buffer between variable capture and steady demand, and seasonality decides it. A large tank captures more of each storm and carries the site through dry spells, at the cost of capital and of standing water that needs treatment; a small tank is cheap but overflows in storms and runs dry between them. The sizing is a balance of capture frequency, demand rate and the ride-through the site wants.
The standard approach matches the tank to the demand over the inter-storm period at the chosen recurrence, so the volume holds enough to supply the duty between rainfall events. Where rainfall is seasonal, the tank is sized to the dry-season gap, and the wet-season overflow is accepted as unused capture. The volume is an auditable calculation from the yield curve and the demand profile, not a fraction of roof area, and the treatment capacity is set to the draw, not the storm peak, so the tank and the train are sized on different curves.
Collection system and tank sizing
The collection system is the roof and hardstanding drains routed to the tank, with a first-flush diverter that discards the initial runoff carrying accumulated debris, and screens at the inlet. The tank itself is a standard water-storage vessel specified for the incoming quality, sized from section two, and located so it can feed the duty by gravity or pump. For a data centre the tank is often sited near the cooling plant to shorten the reuse pipe.
Tank sizing also considers the draw arrangement and the turnover, because a large quiescent volume can encourage stratification and biofilm if it sits too long, so the design matches the volume to a realistic draw and includes circulation or turnover where needed. The construction choice, bolted or welded steel with the appropriate coating, follows the volume and the water chemistry, and the coating specification, referenced to AWWA D102 for welded steel, protects the substrate the harvested water would otherwise attack. The tank is the asset; the collection system is what keeps it fed and clean.
Treatment to the duty standard
Harvested rainwater is not potable and is not assumed clean; it is treated to the standard of the duty it serves. For cooling make-up the treatment follows the cooling water programme: screening and settlement for coarse solids, filtration for suspended solids, and disinfection, typically an oxidising biocide, for the microbial load that standing water promotes, with nutrient control where the catchment contributes it. The ASSP 3 guidance on cooling-system water treatment frames the parameters.
The duty standard is the make-up specification from the cooling programme, and the treatment train is sized to the harvested draw, a steady flow, rather than the storm peak. The quality gate confirms the treated water meets the make-up limit before it enters the plant tank, and the same logic applies to any non-potable duty the water serves. Treatment cost scales with the load the catchment introduces, so a cleaner roof catchment needs a lighter train than a road-catchment one, and the design states which streams feed the tank.
Which duties can take harvested water
The realistic duties are non-potable. Cooling tower make-up is the largest and most suitable fit, because it is a high-volume, non-potable use whose treatment programme can be set for the harvested chemistry, and it directly displaces the municipal draw the site most wants to reduce. Irrigation and landscape use, vehicle wash and general non-potable services are smaller but straightforward fits where a non-potable distribution exists.
What harvested water should not do is enter anything potable or any duty the specifications bar it from, and the system is plumbed and labelled so the two never mix. The duty choice also sets the treatment level, because cooling make-up tolerates a treated industrial stream while a more sensitive use would demand more. The Green Grid WUE metric captures the benefit when the displaced make-up is reported, because the harvested volume that reaches the cooling duty is exactly the municipal draw it removes from the site balance.
Cost and maintenance
The cost case has two parts: capital for the tank, collection network, first-flush and treatment, and ongoing cost for energy, treatment chemicals and maintenance. The offset is the municipal water displaced, valued at the local tariff, plus any avoided stormwater discharge fee where the capture reduces the site's runoff burden. The payback tracks the captured volume and the water price, so a high-rainfall, high-tariff site recovers cost faster than a dry, cheap-water one.
Maintenance is the part that decides whether the system keeps working. The first-flush diverter and screens need clearing, the tank needs periodic inspection and sludge removal, the filtration and disinfection need their media and dose maintained, and the treatment performance needs monitoring against the make-up limit. A harvesting system that is cheap to build and neglected to run becomes a stagnant liability; one with a stated maintenance routine and monitored output earns its place in the site water balance year after year.
Reporting the harvested volume
Reporting closes the loop on whether the system performs. Meter the harvested volume into the duty, separate from the municipal make-up, so the displaced draw is a clean number, and report it against the total cooling make-up so the contribution is visible. The Green Grid WUE improves as harvested make-up displaces mains, and the report should show both the efficiency gain and the absolute volume captured.
Report also the capture efficiency, the share of rainfall yield actually stored and used against what overflowed, because that number tells the operator whether the tank is rightly sized. A site that reports only WUE without the harvested volume hides the source of the gain, and an auditor reading the water story wants the metered harvested flow, not an estimate. The reporting discipline is what turns a harvesting tank from a green claim into a measured, defensible water-risk reduction.
Limits and common objections
The honest limits decide whether to build. Capture is weather-dependent, so harvested water is not firm dry-season supply; the tank runs dry when the rain stops, and the design must say so rather than pretend otherwise. Treatment cost and the catchment load set how cheap the water really is, and a contaminated or road-heavy catchment can make the train expensive. Space for the tank and the collection network is a real constraint on a tight site.
The common objections are answerable but not dismissible. First-flush and maintenance burden is real and must be staffed. Water-quality risk is managed by the duty-standard treatment and the quality gate, not assumed away. Aesthetic and mosquito concerns are met by a covered, screened tank. The fair conclusion is that rainwater harvesting earns its place where rainfall, tariff and space align, and where the operator commits to the maintenance the system needs; elsewhere it is a supplement, not a strategy, and the site water balance should say so.
Catchment Yield Calculation
Input | Definition | Source | Effect |
Roof area | Building footprint | Survey | Largest clean yield |
Coefficient | Roof / hardstanding C | Surface | Scales yield |
Rainfall depth | Annual / event | Local data | Drives volume |
Yield | A.C.rainfall | Calculation | Capture |
First-flush loss | Initial diversion | Design | Reduces usable |
Usable | Yield minus losses | Net | Feeds tank |
Storage Sizing Basis
Factor | Sets | Trade-off | Basis |
Capture frequency | How often filled | Dry-spell gap | Yield curve |
Demand rate | Draw per period | Tank drawdown | Duty profile |
Ride-through | Dry days covered | Capital vs security | Recurrence |
Treatment capacity | Draw, not peak | Cost | Steady flow |
Seasonality | Wet / dry split | Overflow accepted | Dry-season gap |
About Center Enamel
Center Enamel (Shijiazhuang Zhengzhong Technology Co., Ltd.) designs and fabricates bolted steel storage tanks, welded steel tanks, fusion-bonded epoxy tanks, galvanized tanks, stainless steel vessels, pressure vessels, aluminum geodesic dome roofs and floating roofs. The company has more than 30 years of production experience and has supplied equipment to projects in more than 100 countries. Aluminum geodesic dome roofs are designed and fabricated to API 650 Appendix G, AWWA D108, the Aluminum Design Manual, ASCE 7 and IBC, and the company developed and exported a 72 m diameter aluminum dome roof in 2023. Engineering, fabrication, coating, quality control and site service are handled as one scope, which is why the drawings, the calculation basis and the delivered hardware can be reconciled against each other.
Frequently Asked Questions
How much rainwater can a data centre site capture?
Capture is the roof and hardstanding area times their runoff coefficients times the rainfall depth, and the roof dominates because it is large, high-coefficient and relatively clean. The usable figure is the yield after first-flush diversion and losses, expressed as a curve across rainfall frequency rather than a single annual total, because a tank sized to the average overflows in storms and runs dry between them. A dry site's capture is smaller and must be sized honestly against the dry-season gap it cannot cover.
How large should a rainwater harvesting tank be?
Size it from the catchment yield against rainfall seasonality and the demand it must supply between events, not from the roof area alone. A larger tank captures more of each storm and rides through dry spells at higher capital and standing-water treatment cost; a smaller tank is cheap but overflows and runs dry. The volume is an auditable calculation from the yield curve and demand profile, and the treatment capacity is set to the draw, not the storm peak.
What treatment does harvested water need?
Treat it to the duty standard, not to potable assumptions. For cooling make-up that means screening and settlement, filtration for suspended solids, and disinfection, typically an oxidising biocide, for the microbial load, with nutrient control where the catchment contributes it, following cooling-system water treatment guidance. Size the train to the harvested draw, a steady flow, confirm treated water meets the make-up limit via a quality gate, and set the train lighter for a clean roof catchment than a road one.
Can harvested water be used for cooling tower make-up?
Yes, and it is the most suitable fit: a high-volume, non-potable duty whose treatment programme can be set for the harvested chemistry, directly displacing the municipal draw the site wants to cut. The harvested water is treated to the make-up specification and metered into the duty so the displaced mains volume is a clean, reportable number that also improves the site WUE. It must never enter any potable or barred duty, and the plumbing is labelled to keep the streams separate.
Is rainwater harvesting worth the cost for a data centre?
The case has capital for tank, collection, first-flush and treatment against the municipal water displaced at the local tariff, plus any avoided stormwater fee. Payback tracks captured volume and water price, so high-rainfall, high-tariff sites recover faster. The deciding factor is maintenance: a neglected system becomes a stagnant liability, while one with a stated routine and monitored output earns its place. Where rainfall, tariff and space align and the operator commits to upkeep, it pays; elsewhere it is a supplement.
How is harvested volume reported?
Meter the harvested flow into the duty separately from municipal make-up so the displaced draw is a clean number, and report it against total cooling make-up to show contribution. Report capture efficiency too, the share of rainfall yield stored and used versus overflowed, because that reveals whether the tank is rightly sized. The WUE gain should be shown with the metered harvested volume behind it, not as an estimate, so an auditor reads a measured water-risk reduction.
What are the common objections to rainwater harvesting?
The fair objections are real: capture is weather-dependent so it is not firm dry-season supply, treatment and catchment load set the true cost, and tank-plus-network space is constrained on tight sites. Maintenance burden, water-quality risk and mosquito or aesthetic concerns are answered by a staffed maintenance routine, duty-standard treatment with a quality gate, and a covered screened tank. Harvesting earns its place where rainfall, tariff and space align and the operator commits to upkeep; otherwise it is a supplement the water balance should state as such.
Conclusion
A rainwater harvesting tank earns its place on a data centre site when the capture, the storage and the duty are sized together rather than guessed. The catchment yield against rainfall seasonality sets the tank, the treatment train is set to the duty the water actually serves, and the realistic use, cooling make-up above all, is what turns a downpipe into a measured supply that displaces municipal draw.
The two things that decide success are honesty about the weather-dependent limit and a maintenance routine that keeps the treated output within spec. Send us the roof and hardstanding areas, the local rainfall and the cooling make-up demand, and we will return a catchment yield, a storage volume and a treatment basis you can meter, report and defend.
Talk To Our Engineering Team
Send the duty, the volume basis, the governing code and the site constraints, and our engineering team will come back with a specification that a supplier can price and a reviewer can approve. We will also tell you plainly when a different tank type or a different scope is the better answer.
WhatsApp