Reliable Water in the Digital Age: Data Centers, Drinking Water and Ratepayers
Citation dossier on data-center water demand, ratepayer protection, drinking-water infrastructure, PFAS and cybersecurity risks for water systems.
Built from LongScribe ASR of the full public hearing and cross-checked against the House Energy and Commerce hearing materials.
Featured speakers
- Gary Palmer
- Paul Tonko
- Neil Bradley
- May Wu
- Julie Moore
Transcribed and published by Longscribe. Editorial policy.
The hearing connects the expansion of data centers with a practical infrastructure question: who should pay when large digital facilities require new or upgraded water capacity? Source · 15:00
Witnesses and members also treat water affordability, aging infrastructure, PFAS, lead replacement and cyber resilience as linked constraints rather than separate policy problems. Source · 39:38
Key facts
- Data-center cost principle
- The opening statements repeatedly argue that households and small businesses should not be forced to absorb water-infrastructure costs directly attributable to large data-center projects. Source · 16:28
- Infrastructure need cited
- A witness cites EPA's latest needs survey at roughly $625 billion for drinking-water-system investment. Source · 19:19
- Water affordability cited
- The hearing cites an EPA estimate that 12 to 20 million U.S. households lack affordable access to water services. Source · 22:06
- State Revolving Fund debate
- Witness testimony argues for substantially higher Drinking Water State Revolving Fund support and a permanent federal low-income water-assistance program. Source · 39:38
- Cooling alternatives
- The hearing discusses air cooling and immersion cooling as ways some data centers can reduce conventional water use, while stressing that suitability depends on climate and facility design. Source · 76:06
- Small-system cyber gap
- The Q&A describes a serious resource gap between large utilities with dedicated cybersecurity teams and small rural systems with only a handful of staff. Source · 130:25
Who pays for data-center water infrastructure?
The clearest bipartisan through-line is the ratepayer question. Members and Neil Bradley distinguish the simple principle from its implementation: a large user should pay the costs it imposes on the system, but utilities also have to account for the fixed-cost contribution that a large new customer can provide. That turns a slogan into a project-by-project accounting problem involving connection costs, operating costs and local utility expertise.
Cooling technology and water use
A member asks what dry-cooling approaches can reduce water demand without creating new environmental or health risks. Bradley points to air cooling in suitable climates and closed-loop immersion systems using non-conductive liquid. The exchange is useful because it avoids treating every data center as technically identical: climate, workload and cooling architecture determine what is feasible.
Affordability, SRF financing and aging systems
The hearing repeatedly returns to the mismatch between capital need and the ability of small systems to borrow. Testimony calls for stronger State Revolving Fund support, lead-service-line replacement funding, PFAS resources and low-income assistance. Julie Moore also describes the tension states face when communities most in need of investment cannot safely take on additional debt.
PFAS: cleanup versus source control
Late in the hearing, the discussion separates downstream treatment from upstream source control. Witnesses argue that utilities should not bear the entire cleanup burden and point to industrial effluent limits and product restrictions as tools for reducing new PFAS entering wastewater while treatment continues for legacy contamination.
Cybersecurity for small and rural water systems
Small systems are described as facing the same modern cyber risks as large utilities without comparable staff or budgets. The exchange emphasizes technical assistance, infrastructure hardening and ways to share security costs across small providers. One revealing detail is that some small systems avoid internet connectivity as a defensive measure, which creates operational trade-offs of its own.
Key timestamped claims
Each claim is an original Longscribe summary anchored to the moment(s) in the recording where it is supported; follow a timestamp to verify it in the source video.
15:00The hearing opens by linking drinking-water reauthorization with the new infrastructure demands created by large data centers.
19:30Members broaden the frame to affordability, aging infrastructure, PFAS and cybersecurity.
31:00The witness panel is introduced and testimony begins.
39:40Testimony argues that federal financing and low-income assistance are central to keeping water bills affordable while systems modernize.
42:00State-level testimony explains why communities with the greatest infrastructure needs can also be the least able to take on new debt.
76:10A technical exchange covers air cooling and closed-loop immersion cooling as alternatives that can reduce conventional water demand in some data centers.
78:34The ratepayer discussion distinguishes the principle that large users pay their costs from the harder project-level accounting needed to implement it.
[126:40] The hearing contrasts PFAS cleanup with upstream source-control strategies.
[128:30] Members examine why small rural water systems face a disproportionate cybersecurity and staffing burden.
Key exchanges
What cooling approaches can reduce conventional water use at data centers?
Bradley describes air cooling where climate permits and closed-loop immersion systems using non-conductive liquid, while cautioning that the right method depends on the facility and environment. — Neil Bradley
Why it matters: It identifies concrete engineering alternatives instead of treating water use as fixed.
How should utilities apply the principle that large users pay their own infrastructure costs?
Bradley says large users should cover the costs they impose, but utilities should also credit the contribution those users make toward fixed system costs and work the balance out locally on a project basis. — Neil Bradley
Why it matters: This is the hearing's clearest operational explanation of ratepayer protection.
How large is the cybersecurity resource gap for small rural water systems?
Moore calls the gap real and daunting and argues that technical assistance and infrastructure hardening have to move together for small communities. — Julie Moore
Why it matters: Cyber requirements can become unfunded mandates when staffing capacity is ignored.
Timeline
- 15:00 — Opening statements frame drinking-water reauthorization and data-center infrastructure costs. Source · 15:00
- 31:00 — The witness panel is introduced and testimony begins. Source · 30:54
- 39:40 — Testimony turns to SRF funding, low-income water assistance, lead replacement and PFAS. Source · 39:38
- 42:00 — State-level testimony describes financing pressure on small and rural systems. Source · 41:49
- 76:10 — Members ask about lower-water cooling methods for data centers. Source · 76:06
- 78:34 — The committee examines how to allocate large-user costs without overcharging other ratepayers. Source · 78:30
- 128:30 — Q&A focuses on the administrative and cybersecurity capacity gap in small water systems. Source · 128:28
Source & methodology
LongScribe downloaded the public House hearing recording and produced a timestamped ASR source artifact with 1,852 retained segments. The public page is an editorial paraphrase, not a verbatim reproduction. Names, roles, hearing title, date and legislative context were cross-checked against the House Committee on Energy and Commerce hearing materials. Source links on individual claims jump to the underlying recording timestamp.
Paste an accessible public YouTube video or Shorts URL: you do not need to download it to your device. LongScribe uses captions when available or transcribes reachable speech with AI. Three hours is 180 transcription minutes; signed-in Free includes 60 minutes across 20 recordings per month, subject to remaining allowance, per-job limits and source availability. Completed eligible account jobs can export TXT, SRT, DOCX or JSON; the anonymous demo is a separate flow with its own limits.