Site grading, roads and stormwater

A data centre campus is a large industrial development: a hyperscale site can cover 20 to 100 hectares, with buildings hundreds of metres long, substations, generator yards, fuel storage, cooling equipment, roads for heavy deliveries and parking. Before any structure is designed, civil engineers shape the land: grading it so buildings sit on level, well-drained pads; designing roads that can carry the heaviest equipment ever delivered to the site; and managing the large volumes of rainwater that run off roofs and pavement. Mistakes here are expensive to fix later and can flood a facility whose whole purpose is reliability. This course applies civil and structural engineering (CIV-330, CIV-340) to data centres; this lesson covers the site, and the section at the end of the lesson shows how the twelve lessons fit together.

Site investigation

Civil design starts with information about the site:

• A topographic survey, typically with contours at 0.25 to 0.5 m intervals from ground survey, drone photogrammetry or lidar, plus existing utilities, trees, watercourses and boundaries.
• A geotechnical investigation: boreholes and test pits to identify soil and rock layers, groundwater levels, bearing capacity, settlement characteristics, frost susceptibility and, in seismic regions, the site class used in seismic design (Lesson 7). Investigations for large buildings typically place boreholes every 30 to 60 m across the footprint.
• Environmental and hydrological information: floodplains, wetlands, watercourses and their setbacks, contamination from previous uses (DCE-410).
• Utility capacity: water, sewer, power and fibre routes.

Data centre owners increasingly standardize their building designs and adapt them to each site, so site conditions that differ from the standard, such as poor soils, high groundwater or a steep slope, must be identified early because they change foundation and grading costs significantly.

Grading

Grading reshapes the ground to provide level building pads, drain water away from buildings and towards collection systems, and give vehicles acceptable slopes. Typical criteria are:

• Building pads: level, with the finished floor elevation set above the design flood level with freeboard (often 0.3 to 0.6 m above the 100-year flood level, more for critical facilities; some owners use the 500-year level) and above surrounding grades.
• Ground sloping away from buildings at 2 to 5% for at least 3 m.
• Paved areas at 1 to 2% minimum for drainage; grassed areas at 2% minimum; slopes steeper than 3 horizontal to 1 vertical need erosion protection or retaining walls.
• Roads with longitudinal grades usually under 6 to 8% for heavy trucks, and gentler where heavy-haul equipment is delivered.

Grading design aims to balance cut and fill on site, since importing or exporting soil is costly. Unsuitable soils (organic topsoil, soft clay) must be stripped and replaced with engineered fill compacted in layers to a specified density, typically 95 to 98% of the standard or modified Proctor maximum dry density under buildings.

Roads, access and heavy haul

Data centre sites need several kinds of vehicle access:

• Heavy-haul routes for the largest deliveries: power transformers of 50 to 200 tonnes or more, generators of 30 to 60 tonnes, and prefabricated modules. These arrive on multi-axle trailers whose gross weight can exceed 300 tonnes, requiring special permits, route surveys, and roads, culverts and bridges designed for the load.
• Truck routes for routine deliveries, fuel trucks and maintenance vehicles, with turning radii for tractor-trailers (typically 15 m outside radius for a WB-20 or WB-67 design vehicle).
• Fire department access, which building codes specify (see below).
• Staff and visitor parking and secure entry, with vehicle barriers and controlled gates (DCE-440).

Pavements are designed for traffic loading over their life. Flexible (asphalt) pavements suit general roads; rigid (concrete) pavements suit truck aprons, generator yards and areas with fuel spills or heavy point loads. Pavement design converts mixed traffic into equivalent single-axle loads (ESALs) and sizes layer thicknesses for the subgrade strength. A few heavy-haul deliveries do relatively little cumulative damage, but a single overload on a weak subgrade or a buried pipe can cause failure, so heavy-haul routes are checked separately.

In Canada, the National Building Code (Article 3.2.5.6) and provincial codes require fire department access routes with a clear width of at least 6 m, headroom of at least 5 m, a centreline turning radius of at least 12 m, a change of gradient not exceeding 1 in 12.5 over 15 m, and a surface able to carry fire apparatus. Access must reach within the specified distances of building entrances and fire department connections. Municipal fire departments may impose larger dimensions for aerial apparatus.

Stormwater: why it matters

Developing a site replaces soil and vegetation, which absorb much of the rain, with roofs and pavement, which shed almost all of it. Runoff peaks rise several-fold and arrive sooner, and total runoff volume increases. Without control, development causes downstream flooding, erosion of channels and pollution from sediment, oil and chemicals. Regulators therefore require new developments to manage stormwater, typically by limiting post-development peak flows to pre-development rates for a range of storms (often the 2-year to 100-year events), treating runoff to remove sediment, and in many places retaining the first part of each storm on site.

Data centres are an extreme case: their roofs and paved areas can cover 60 to 80% of the site. Stormwater facilities, such as ponds and underground tanks, can take a significant share of land and cost, and their design also protects the facility itself, since the site must stay dry in storms larger than the design event.

The rational method

For small catchments (typically under 50 to 80 ha), peak runoff is estimated with the rational method:

where \(Q\) is the peak flow in m³/s, \(C\) the dimensionless runoff coefficient (the fraction of rainfall that runs off), \(i\) the rainfall intensity in mm/h for a storm lasting the time of concentration, and \(A\) the area in hectares. (In US customary units, \(Q = CiA\) gives cubic feet per second with \(i\) in in/h and \(A\) in acres.) The time of concentration \(t_c\) is the time for runoff to travel from the most distant point to the outlet. Intensity comes from intensity-duration-frequency (IDF) curves published for each location, which give the average intensity for storms of a given duration and return period.

Detention and retention

Detention facilities store runoff temporarily and release it through a controlled outlet (an orifice or weir sized so the outflow never exceeds the allowable rate). Common forms are dry ponds, wet ponds (which also settle sediment and treat water), underground chambers and tanks under parking areas, and rooftop storage. Retention and infiltration facilities (bioretention, infiltration trenches, permeable pavement) keep water on site to soak in or evaporate, reducing runoff volume and recharging groundwater; many jurisdictions now require a minimum retention volume, often the first 10 to 25 mm of each storm.

The required detention volume is the largest difference between inflow and outflow volumes over the range of storm durations. The modified rational method computes this by trying storms of increasing duration:

import numpy as np

# site: 12 ha campus, modified rational method for detention sizing
A = 12.0                       # drainage area (ha)
C_pre, C_post = 0.30, 0.72     # runoff coefficients: meadow before; 70% roofs and paving after

def intensity(t_min, a=1400.0, b=8.0, n=0.82):
    # IDF curve for a 100-year storm, i = a / (t + b)^n in mm/h (illustrative coefficients)
    return a / (t_min + b) ** n

def Q(C, i):
    return C * i * A / 360.0    # rational method, m3/s (i in mm/h, A in ha)

tc_pre, tc_post = 30.0, 12.0    # times of concentration (min)
Q_allow = Q(C_pre, intensity(tc_pre))
print(f"pre-development peak (100-yr): {Q_allow:.2f} m3/s;  post-development uncontrolled: {Q(C_post, intensity(tc_post)):.2f} m3/s")

# storage needed = max over storm durations of (inflow volume - outflow volume)
best = (0, 0)
for d in range(10, 361, 5):
    inflow = Q(C_post, intensity(d)) * d * 60
    outflow = Q_allow * d * 60 * 0.5 + Q_allow * tc_post * 60 * 0.5   # outflow rises linearly as the pond fills
    need = inflow - outflow
    if need > best[1]:
        best = (d, need)
print(f"critical storm duration {best[0]} min, detention volume about {best[1]:.0f} m3")
print(f"pond 1.5 m deep would need about {best[1] / 1.5:.0f} m2 ({best[1] / 1.5 / (A * 10000) * 100:.1f}% of the site)")

pre-development peak (100-yr): 0.71 m3/s;  post-development uncontrolled: 2.88 m3/s
critical storm duration 50 min, detention volume about 2291 m3
pond 1.5 m deep would need about 1527 m2 (1.3% of the site)

For this campus, controlling the 100-year peak to the pre-development rate requires about 2300 m³ of storage, governed by a 50-minute storm, longer than the 12-minute time of concentration. A pond 1.5 m deep would cover about 1500 m², about 1.3% of the site, although in practice side slopes, freeboard, access and multiple design storms make ponds two to three times this area. Where land is valuable, underground tanks under paving are used, at higher cost.

Water quality and erosion control

Stormwater carries sediment, metals from roofs and vehicles, hydrocarbons and, at data centres, possible spills of diesel fuel, glycol and other fluids. Treatment measures include oil-grit separators, wet ponds and wetlands, bioretention and filter strips, and spill containment around fuel and generator areas (DCE-340), with shut-off valves to keep spills out of the storm system. During construction, when large areas of bare soil are exposed, erosion and sediment control (silt fences, sediment basins, stabilized construction entrances, staged clearing and prompt revegetation) prevents sediment from leaving the site.

In Canada, stormwater is regulated by provinces and municipalities. In Ontario, for example, stormwater systems need an Environmental Compliance Approval (increasingly through a consolidated linear infrastructure approval held by the municipality), designed to the province's stormwater management guidance and municipal standards, which typically require quantity control to pre-development levels, enhanced (80% total suspended solids removal) quality treatment and erosion control. The federal Fisheries Act prohibits depositing deleterious substances, including sediment, into fish-bearing waters and protects fish habitat, which affects outfalls and work near watercourses. Conservation authorities in Ontario and similar agencies elsewhere regulate development near rivers, wetlands and floodplains.

Designing beyond the code event

Regulations define the storms a stormwater system must control, but a critical facility must also survive larger events. Good practice includes overland flow routes that carry water around buildings when pipes are overwhelmed, finished floor levels well above the routes' water levels, no below-grade critical equipment without flood protection, and checking the site for extreme rainfall such as the 500-year storm or a probable maximum precipitation scenario. Rainfall intensities are increasing in many regions, so designers increasingly apply climate change factors (often 10 to 20% increases in design intensities) to IDF curves.

How this course is organized

The twelve lessons move from the site to the finished, resilient building:

• Lesson 1 (this lesson): site investigation, grading, roads and stormwater management.
• Lesson 2: site utilities: fire and cooling water, drainage, fuel, duct banks and fibre routes.
• Lesson 3: floor loads, slabs on grade and foundations.
• Lesson 4: soils, consolidation, earthworks and ground improvement.
• Lesson 5: structural systems, load combinations, roof equipment, ponding and overhead services.
• Lesson 6: steel structures and long-span roofs.
• Lesson 7: snow, wind and earthquake design under the National Building Code.
• Lesson 8: concrete structures: tilt-up, precast and multi-storey floors.
• Lesson 9: prefabrication and modular construction.
• Lesson 10: building envelope, roofing and moisture control.
• Lesson 11: resilience: flood, extreme wind, vehicle and blast hazards.
• Lesson 12: construction, quality assurance, embodied carbon and a site design project.