Stormwater Management For Data Centres: Detention, Harvesting And The Reuse Link
Created on Today
Stormwater Management For Data Centres: Detention, Harvesting And The Reuse Link
Manage stormwater as both a discharge duty and a supply: size detention to the permitted release rate from the site runoff, then treat the detained water and route it to the cooling make-up as a reuse stream. Harvest roof and hardstanding separately, set the treatment to the duty standard, and size the detention and harvesting volumes together so the water balance and the discharge limit are both met.
Introduction
A data centre site is mostly hard surface: buildings, hardstandings, access roads and often a large rooftop, and every rain event turns that surface into runoff that has to go somewhere. The conventional answer is detention, a basin or tank that holds the peak and releases it slowly so the downstream system is not overwhelmed. For a water-conscious operator that is only half the story, because the same runoff is also a supply.
This article treats stormwater as both a discharge problem and a resource. It covers the runoff a site generates, how detention is sized to a release rate, the reuse link that routes detained water to the cooling make-up, the quality barrier before reuse, harvesting from roof and hardstanding, the treatment that harvested water needs, how stormwater sits in the site water balance, and how to size the detention and harvesting volumes together rather than as separate exercises.
Runoff on a data centre site
Runoff is driven by the catchment area, the rainfall intensity and the runoff coefficient of each surface, and a data centre site is dominated by low-absorption surfaces. The rational method gives the peak rate as the product of the catchment area, the runoff coefficient and the design rainfall intensity, divided by a unit constant, and the volume is that rate integrated over the storm duration. Roof, hardstanding and landscaped area each carry a different coefficient, so the site is summed surface by surface.
The first number the design needs is the total impervious area, because that sets both the peak the downstream system must accept and the volume available to capture. A large rooftop is a clean catchment with a high coefficient and, usefully, low ground-contact contamination, while access roads and hardstandings carry more deposited load. Mapping the coefficients is the basis for every sizing decision that follows, and it is also the basis for the harvesting plan, because not all runoff is equally worth catching.
Detention sizing and the release rate
Detention exists to flatten the peak. The regulator or the downstream system permits a release rate, often expressed as a fraction of the pre-development peak, and the detention volume is the storage needed to hold the excess between the incoming storm hydrograph and the permitted outgoing rate. The larger the site and the tighter the release rate, the larger the detention requirement, and the calculation is a routing of inflow against outflow, not a single volume formula.
The detention structure can be a basin or a tank; for a data centre where land and security matter, a tank suits confined or structured sites. Size it to the design storm agreed locally, typically a specified recurrence interval, and confirm the release device, an orifice or a weir, is set to the permitted rate. Under-sized detention spills or backs up; over-sized detention wastes land and capital. The release rate is the constraint that fixes the volume, so it is the first input the design must lock down.
The reuse link: from detention to cooling make-up
The reuse link is the step that turns a disposal cost into a supply. Instead of releasing all detained water downstream, a portion is drawn off, treated and fed to the cooling make-up, displacing municipal water that the towers would otherwise consume. The link is physically a pump and a pipe from the detention volume to the treatment train and then to the make-up header, with the controls set so reuse does not compromise the release-rate compliance.
The value is twofold: the site reduces its draw on the stressed mains supply and reduces the volume it must discharge, within the release limit. The constraint is that reuse cannot exceed what the cooling duty can take, and the detention must still meet its release obligation after the draw. The link is therefore designed as a parallel path, not a replacement for the discharge route, and the controls keep the two duties separate so neither fails when the other is active.
Water quality before reuse
Water that is fine to discharge is not automatically fine to reuse, because the cooling loop has its own chemistry limits. Detained stormwater carries sediment, debris, nutrients from atmospheric and landscape sources, and occasional hydrocarbons from hardstanding, and those constituents shift the scaling and biological balance of the loop if they enter untreated. The quality gate before reuse is what protects the treatment programme downstream.
The gate is a set of parameters, suspended solids, hydrocarbons, nutrients and a microbial count, measured at the detention outlet and compared to the cooling make-up specification. If the detained water meets it, it passes to treatment; if not, it is discharged within the release limit rather than forced into reuse. The point is that reuse is conditional on quality, and the conditional logic is what keeps the reuse link from becoming a water-quality liability. ASSP 3 guidance on cooling-system water treatment frames the parameters that matter.
Harvesting from roof and hardstanding
Harvesting is the deliberate capture of runoff for use rather than the incidental draw from detention, and the two catchments are handled differently. Roof runoff is the cleaner stream: it has a high runoff coefficient, low ground contact and, on a data centre, a large area, so it is the first harvest target. Hardstanding and access-road runoff carries more load and is harvested only where the treatment train can handle it.
The harvest system is a collection network to a storage tank, sized against the catchment yield, and the tank is a standard water-storage vessel specified for the incoming quality. The distinction from detention is purpose: detention holds peak for release, harvesting holds volume for use, and a site can combine them where the detained volume doubles as harvest storage. The design choice is whether to keep the streams separate, for cleaner roof water, or to pool them, for simplicity, and the treatment answer decides.
Treatment requirements
Harvested and detained water both need treatment before the cooling duty, and the level depends on the source and the loop tolerance. The baseline is screening and settlement to remove coarse solids and sediment, followed by filtration for suspended solids, and a disinfection step, typically an oxidising biocide, to control the microbial load that standing water encourages. Nutrient and hydrocarbon removal is added where the catchment load demands it.
The treatment train is set by the make-up specification from the cooling water programme, not by a generic standard, because what the loop tolerates defines the barrier. The EPA stormwater framework addresses the discharge-side controls, while the reuse side is governed by the cooling-system treatment standard. Size the train for the harvested flow, not the storm peak, because reuse is a steady draw, and confirm the treated water meets the make-up limit before it enters the tank that feeds the plant.
Interaction with the site water balance
Stormwater does not sit alone in the water picture; it interacts with the cooling make-up, the reclaimed supply if any, and the municipal draw. The site water balance totals every inflow, municipal, reclaimed, harvested and detained, against every outflow, evaporation, blowdown and discharge, and the stormwater contribution is the variable tied to rainfall. In a wet period it can displace a large share of mains make-up; in a dry period it contributes little.
The interaction matters for two reasons. First, the reuse link only helps when there is storm flow to capture, so its value is seasonal and should not be counted as firm supply in the dry-season design. Second, the detention release obligation still applies even when reuse is active, so the discharge path is always sized independently. The balance is the document that prevents double-counting, and it is where stormwater's real, weather-dependent contribution is shown honestly rather than assumed.
Sizing the detention and harvesting volumes
The two volumes are sized together, not in sequence. Start with the detention volume from the release rate and the design storm, because compliance is non-negotiable. Then decide how much of the detained or harvested volume is also held for reuse, bounded by the cooling make-up demand and the treatment capacity. A combined tank can serve both where the release obligation is met after the reuse draw, and separate tanks are used where the duties conflict.
The harvest volume is set by the catchment yield against rainfall seasonality and the reuse demand, so it is often smaller than the detention volume and sized to the average capture rather than the peak. Document both against the site water balance so the numbers reconcile. The result is a stormwater plan that meets the discharge permit and contributes a genuine, weather-aware supply, with the detention and harvesting volumes each justified by the calculation rather than by a rule of thumb.
Runoff And Detention Sizing Basis
Quantity | Definition | Source | Role |
Catchment area | Sum of surfaces | Site survey | Drives volume |
Runoff coefficient | Per-surface C | Surface type | Roof high, landscape low |
Design intensity | Recurrence storm | Local data | Peak rate |
Peak rate Q | C.i.A / k | Rational method | Detention input |
Release rate | Permitted outflow | Authority | Fixes volume |
Detention vol | Inflow minus release | Routing | Compliance storage |
Stormwater Reuse Route
Stage | From | To | Control |
Capture | Roof / hardstanding | Harvest tank | Collection network |
Detain | Site runoff | Detention tank | Orifice / weir release |
Draw | Detention | Treatment train | Pump + quality gate |
Treat | Treatment | Make-up header | Meets spec |
Reuse | Make-up | Cooling tower | Displaces mains |
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 is stormwater detention sized for a data centre site?
Detention is sized to the permitted release rate, often a fraction of the pre-development peak, by routing the storm inflow against the allowed outflow; the storage is the volume between them, not a single formula. The constraint is the release rate set by the regulator or downstream system, applied to the design storm at the agreed recurrence interval. A tank suits confined or security-sensitive sites; an orifice or weir sets the release. Under-size and it spills, over-size and it wastes land and capital.
What is the reuse link between stormwater and cooling?
The reuse link draws a portion of detained stormwater, treats it and feeds it to the cooling make-up, displacing municipal water the towers would otherwise consume. Physically it is a pump and pipe from the detention volume to the treatment train and then the make-up header, with controls that keep reuse from breaking the release-rate compliance. It is a parallel path, not a replacement for discharge, and reuse cannot exceed what the cooling duty can take.
What water quality is needed before stormwater reuse?
Detained stormwater must meet the cooling make-up specification before reuse, because it can carry sediment, debris, nutrients and occasional hydrocarbons that shift the loop's scaling and biological balance. Measure suspended solids, hydrocarbons, nutrients and a microbial count at the detention outlet and compare to the make-up limit. If it passes, treat and reuse; if not, discharge it within the release limit. Reuse is conditional on quality, and that conditional logic protects the treatment programme.
Can roof runoff be harvested for cooling?
Yes, and roof runoff is the cleanest, highest-yield harvest target: it has a high runoff contact and, on a data centre, a large area, so it yields clean, high-volume capture. Route it through a collection network to a storage tank sized against the catchment yield. Hardstanding and road runoff carry more load and is harvested only where the treatment train can handle it. The two streams can be kept separate for cleaner roof water or pooled for simplicity, with treatment deciding.
What treatment does harvested water need?
Baseline treatment is screening and settlement for coarse solids and sediment, filtration for suspended solids, and disinfection, typically an oxidising biocide, for the microbial load standing water encourages, with nutrient and hydrocarbon removal added where the catchment demands it. The train is set by the cooling make-up specification, not a generic standard, and sized for the harvested flow, a steady draw, not the storm peak. Confirm treated water meets the make-up limit before it enters the plant tank.
How does stormwater interact with the site water balance?
Stormwater is one inflow among municipal, reclaimed and harvested sources against evaporation, blowdown and discharge outflows, and its contribution tracks rainfall, large in wet periods, little in dry ones. Two consequences follow: the reuse link cannot be counted as firm dry-season supply, and the detention release obligation still applies when reuse is active, so the discharge path is always sized independently. The site water balance is what stops the stormwater contribution being double-counted or assumed.
What detention and harvesting volumes are typical?
There is no typical volume without the site data; detention comes from the release rate and design storm, and harvest from the catchment yield against rainfall seasonality and the reuse demand. The detention volume is usually the larger and compliance-driven; the harvest volume is often sized to average capture rather than peak and is bounded by cooling make-up and treatment capacity. Size both against the site water balance so they reconcile, and let the calculation, not a rule of thumb, set each.
Stormwater on a data centre site is a discharge duty and a supply at once, and the design that treats it as only one of those leaves value on the table or risk on the books. Detention sized to the permitted release rate meets the regulator; the reuse link sized against the cooling duty turns part of that detained volume into a make-up supply; and harvesting the roof captures the cleanest, largest catchment the site has.
The discipline that holds it together is the site water balance, which keeps the discharge obligation and the reuse contribution honest and stops the stormwater volume being double-counted. Send us the catchment areas, the local release rate and the rainfall data, and we will return detention and harvesting volumes sized against the same balance, with the treatment train set to the cooling make-up standard.
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