Data center cooling has become a standing item at utility meetings, and the American Water Works Association has issued a report to help utilities work through those requests. Water Finance and Management described the subject as one that "continues to occupy discussions across the water sector", and the report, Cooling the Cloud, is aimed at utilities evaluating such proposals. The outlet's summary is brief, so the points below describe general cross-connection practice rather than the report's specific contents.
The connection that gets missed
Cooling systems typically draw water from the utility, hold it in tanks, feed chemicals, and discharge a portion back out. Each of those steps can create a path where water moves the wrong way. A cross-connection is any physical link between a potable supply and a source that may carry contaminants. Cross-connection programs typically require a backflow prevention assembly where the hazard is high enough, and industrial cooling loops, make-up water tanks, and chemical feed points often fall within that scope. The protection is physical hardware, but the program that keeps it working is a set of records.
What the record has to show
A backflow assembly protects only if it is the right type for the hazard, it is tested on schedule, and it is repaired or replaced when it fails. For a new tie-in, the file should answer four questions: which device protects the connection, what hazard classification the connection carries, who holds the most recent test date, and what happens when a test fails. The test date matters because an assembly with a missed or failed test can look correct on a site plan while providing no assurance in service. Installation paperwork alone does not establish that status.
Ownership of the record is often unclear at the start. A facility's contractor may install the device, a third-party tester may certify it, and the utility may hold the only copy of the cross-connection file. Each party can reasonably assume another is keeping the log. Utilities should not assume the owner's contractor will maintain the record, and owners should not assume the utility will chase missed tests. The gap usually appears years later, during an incident or a routine audit, when no one can say when the device was last verified.
Set the terms before the connection
The simplest time to settle ownership is before construction is scheduled. A service agreement can name the device, the tester qualified under the local program, the testing interval, and the notice the utility receives after a failed test. These terms do not depend on how the cooling system is designed, and they are easier to write before a construction timeline creates pressure to close them quickly. Where a state or local program already defines qualified testers and reporting forms, the agreement should reference that program rather than create a parallel process that staff must reconcile later.
The same logic at household scale
Homeowners rarely consider backflow until a hose is attached to a tank, a sprayer, or an irrigation line. The principle is the same at a smaller scale. A device that is installed but untested gives the same false comfort as one on an unreviewed plan. A household adding treatment equipment, such as a unit from local RO specialists, should first confirm with the water utility which connections require protection under local rules and whether the existing device has a current test on file.
What to pull first
Before a cooling request reaches a board agenda, pull the existing backflow inventory for the parcel, the connection sizes, the hazard classifications, and the last test dates. If any of those items are missing, the request is not ready for a capacity or rate decision. Load and pressure will drive most of the public discussion, but the cross-connection file determines whether a connection can be operated safely from the day it is energized.