Sample cluster · fictional metro · public preview
What an addon subscriber sees
Below is the per-cluster detail surface a paying Data Center Intelligence subscriber receives. The metro below is fictional (not a real cluster by name); the structure, scoring, and narrative are exactly what ships on a real water-constrained cluster.
Cluster / AZ
Apache Bend Cluster
Central Arizona · 3 hyperscale + 2 colocation · 480 MW announced
78
Water-constrainedSupplier opportunity composite
Load concentration
Five operators, 480 MW announced over 36 months
86
Host-utility water capacity gap
12 MGD headroom against 22 MGD implied draw at typical PUE
88
Host-utility credit profile
A-rated municipal authority; rate-base sensitivity moderate
72
P3 partner readiness
State allows DBOO; two qualified partners in the operator network
75
Chemical supply pull-through
Sodium hypochlorite plus polymer coagulant lanes extend with new load
70
Permitting runway
NEPA-equivalent state process; 14-18 month median
65
Community posture
One open opposition petition; council vote scheduled Q3
60
Recent trigger events
- 2026-04-22Operator 3 filed siting application for an incremental 80 MW campus phase.
- 2026-03-15Host utility issued a $32M cooling-water capacity RFP; bid window 90 days.
- 2026-02-08State water department finalized the Active Management Area replenishment rule; baseline shifts.
Analyst recommendation
The composite reads at 78 because the host-utility water-capacity gap is large (12 MGD headroom against 22 MGD implied draw), load concentration is high (five operators, 480 MW), and the state permits a P3 structure that could close the capacity gap faster than the utility-only path. The community-posture component is the lone weak spot; the Q3 council vote is the gating event. Recommend the chemical supplier track open the cooling-water RFP; recommend the Infrastructure capital track open the conversation with the two pre-qualified partners.
Methodology note
Cluster topology groups individual data center sites by interconnection queue, host utility, and contiguous water-supply system. Implied water draw is computed against the 1.5 to 5.0 gallon per kWh range at typical PUE; cluster-level draw uses the announced load as the upper bound and the operating load as the lower bound. Per-site host-utility attribution and audit-trail traceability are on the v1 ingest roadmap.
Unlock the real clusters
The named clusters and the full constraint-pressure map
Subscribers receive every cluster by name with the water-and-power constraint overlay, the per-cluster supplier opportunity composite, the ranked supplier list nationwide, and real-time alerts when a cluster crosses the Tier-1 threshold. For data-center developers and capital partners, the bespoke Data Center Water Report walks the host-utility math and introduces a vetted P3 partner where the host utility cannot deliver alone.