Water supply & consumptive use

How much water the project consumes, against the receiving water's own cited low flows.

Partial

cooling method undisclosed — but the water quantity is CONTRACTED, so the figures are a stated account rather than a bracketed range; what stays open is how the heat is rejected, not how much water it takes

A real impact study states how much water AWS Sidney Data Center Campus consumes at buildout. It sets that figure against the Great Miami River's own cited design low flows, which are the drought floors a permit writer screens every discharge against. This chapter reports as much of that comparison as the record supports. It names what it cannot compute.

Cooling methodnot disclosed [open] a facility is on the record here; no record says how it rejects heat

The water figure is a bracket, and that is the finding

No record discloses how AWS Sidney Data Center Campus rejects heat, so its consumptive water figure is a range across candidate cooling archetypes — 0 MGD (closed-loop dry) to 4.03 MGD (evaporative tower) — not an estimate. A single headline would fabricate the site's most load-bearing number; the bracket stands until the method is on the record.

baseline

Current municipal loop, no data-center cooling draw.

Cooling demand

0 MGD

baseline: no campus cooling load

Consumptive loss

0 cfs

0 MGD x 0 consumptive (scenario baseline)

Great Miami River 7Q10

24 cfs

Ohio EPA "Fact Sheet for NPDES Permit Renewal, City of Sidney WWTP, 2022" (permit 1PD00009*SD, application OH0027421), Table 14 "Instream Conditions and Discharger Flow", printed p.32 — GMR above Sidney, 7Q10 annual 24.0 cfs, USGS gage #03261500, 1927-2021 data. Read from the source PDF text layer (data/documents/oepa/sidney/1PD00009.c43b66fd.pdf, 0-based page 80), digits clean; structured read at data/extracted/oepa/sidney/1PD00009.npdes.yaml.

The draw is set against the receiving water's cited design low flow as a worst-case, basin-scale bound — a screening comparison, not a withdrawal claim.

The record behind this chapter

What this chapter stands on: the records it reads, the inputs its modeled figures rest on, and the reference data behind its baselines — the same pages the record screens serve, not a second copy. A figure the record does not support stays [open] and links nothing.

Cited by name

Record groups this chapter reads

Permits6 records