Citizen Portal
Sign In

Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

Get email alerts on the Data Center topic

No spam. Unsubscribe anytime.

Joliet council hears weeks‑long public hearing on proposed 800‑acre data center; decision recessed

City of Joliet City Council · March 16, 2026
AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

Developers presented the proposed Joliet Technology Center campus and city staff and outside experts addressed reliability, water and noise. Dozens of residents urged delay or rejection over aquifer, generator noise and electricity concerns; council recessed the matter to continue deliberations March 19.

The Joliet City Council spent its March 16 meeting hearing hours of testimony on the proposed Joliet Technology Center, an 800‑acre data‑center campus that would require annexation, zoning changes and infrastructure commitments. Developers from Hillwood and Powerhouse sought approval for an annexation agreement, rezoning to light industrial, a planned unit development and preliminary subdivision approval. After extended presentations from the developer team, ComEd, engineers and consultants and a prolonged public‑comment period, the council recessed the item for further consideration and reconvened the hearing for March 19, 2026 at 5:30 p.m.

Developer presentations described a multi‑campus design with 24 buildings organized in four groupings, dedicated on‑site substations, stormwater systems, extensive native screening and developer‑funded road and utility extensions (Millsdale Road, Ral Road and Ridge Road) to be dedicated to the city. Powerline and reliability testimony from ComEd and a regional transmission representative said the proposed loads are subject to PJM planning and that 345 kV network upgrades can provide service; the utility process and federal filings were cited as part of measures to protect distribution customers.

Technical experts described the project’s water and cooling approach as closed‑loop chilled‑water systems, which developers and their consultants said require a single initial fill per building and minimal ongoing make‑up water. The development agreement and staff materials set an average campus limit of 150,000 gallons per day (aggregate at full buildout) with a 300,000‑gallon per day peak cap; contract remedies for exceedance include a surcharge (three times the water rate) and, in material breach, city remedies up to termination of service.

Council members and residents pressed the developer and city staff on who may authorize increases in water allocation, how meter data and compliance would be enforced, and whether a surcharge and the ability to shut off service are sufficient deterrents. Staff said metering with frequent reporting would enable near‑real‑time monitoring and that the annexation agreement gives the city enforcement remedies; administration testimony indicated the city manager would have authority to approve certain allocations under the agreement.

Noise and emergency‑generator impacts were also heavily debated. Acoustical consultants described design choices, testing protocols and sound attenuation measures and noted state sound‑level limits that must be met at closest residential receivers, while residents cited reports from other locations about low‑frequency hum and generator exercises that disturbed nearby neighborhoods. City consultants said the project anticipates tier‑4‑equivalent generator standards to limit local emissions.

Economic and traffic studies presented by the developer showed large construction‑phase employment (estimates ranged in the thousands) and a smaller number of permanent operations jobs (the developer cited roughly 600–700 permanent positions), plus multi‑billion‑dollar property‑tax potential over decades and developer funding commitments described in the annexation agreement (including a $100 million community contribution, with $20 million due at property closing and staged payments tied to closing deadlines and optional extensions).

Opposition from residents, community groups and some regional advocates focused on long‑term risks: possible impacts on wells and the local aquifer prior to the city joining Grand Prairie Water Commission (anticipated by 2030), the adequacy of penalties, cost‑shifts of transmission upgrades to ratepayers via transmission service agreements reviewed by FERC, generator emissions and infrasound, equitable distribution of community benefit funds, and the pace of the review process. A petition presented to the council had roughly 4,700 signatures opposing the project.

City counsel and outside legal advisers described enforcement provisions in the annexation agreement, including developer obligations for public improvements at developer cost, indemnities, and a covenant limiting future legal challenges to the agreement. The agreement also includes a clause under which the city may assist (at developer expense) with acquisition of off‑site easements and, in narrow circumstances, eminent domain for rights‑of‑way necessary for public improvements; council members asked for clarification on the legal scope and limits of that clause.

No final legislative vote was taken March 16; staff and council said the complex technical and public‑interest questions require further review and that the council would reconvene the public hearing and consider action on March 19 at 5:30 p.m. before any final approvals. The project remains pending and any city action will reference the annexation agreement, plan unit development controls, and the detailed engineering and permitting documentation that will be required before buildings can be constructed or utilities connected.