Champaign County task force debates 1,000-foot separation, noise and monitoring rules for data centers

Acting Chair (vice chair) opened the Champaign County Data Center Task Force meeting and noted Chair Rodriguez was absent; the group approved the agenda by voice vote.

The task force spent the bulk of the meeting reviewing a memorandum adapted from Aurora ordinances that proposes minimum separations, noise and vibration standards, a complaint hotline and phased verification to govern large data centers when the county’s yearlong moratorium ends. Director John Hall, who presented the draft, said he recommends a 1,000-foot separation from dwellings and structures and that the county adopt the Illinois Pollution Control Board (PCB) noise standards rather than invent a local noise metric: “I’m gonna ahead and recommend 1000 feet separation whether or not there are backup generators,” he said. Hall also proposed requiring companies to log complaints and submit copies of complaints to the county annually.

The memorandum and subsequent discussion focused on four linked challenges: how far noise and low-frequency vibration travel, how to verify that modeled noise projections match operation after construction, who pays for noise and compliance studies, and the county’s enforcement capacity. Andrew Rain of Prairie Rivers Network framed the task force’s mandate as creating “defensible regulation” during the moratorium so the county can protect water, energy and neighbors while avoiding an outright ban that would be legally vulnerable.

Several task force members and public commenters raised concerns that low-frequency and infrasonic noise can travel well beyond 1,000 feet and affect livestock and wildlife. One public commenter cited an example of noise traveling more than a mile and said such sound can “elevate stress hormone concentrations” in animals. Task force members responded by discussing a tiered approach keyed to data center size and phased construction: require an initial noise model based on the full build-out but perform post-construction verification after each phase so the county can catch discrepancies between modeling and real-world noise.

The group debated monitoring mechanics and cost. Hall said a professional, PCB‑standard noise study can cost on the order of $140,000 (figure cited as recent estimate), and members discussed making the developer pay for consultant studies while giving the county approval over the selected consultant. The task force also discussed application and monitoring fees or fines to fund planning-and-zoning capacity for reviewing reports; members noted statutory limits and practical constraints on county fines (court-determined fines are limited historically to roughly $500 a day in similar contexts). One member suggested limiting how often the county could require studies in a year to prevent abuse of the process, while others asked for a cap or fee schedule tied to administrative review needs.

Generator testing schedules and noise from backup generators prompted detailed debate. The Aurora template limits concurrent generator tests and prescribes testing durations; task force members considered baseline testing rules, a variance process, and a prohibition on adding unapproved generators without county review. Hall noted some facilities test each generator periodically and that limits on the number that may run simultaneously can be written into conditions of approval.

The meeting also considered land-use and decommissioning questions. Members and public speakers were skeptical that intensive data center construction could be returned to productive row-crop farmland after concrete pads, compaction and topsoil handling; several said full restoration would be unlikely and urged preserving county control by keeping sites zoned in agricultural categories (Ag‑1/Ag‑2) so any future reuse or rezoning would require a separate approval.

No large data center application is currently pending in Champaign County, staff said; two companies had briefly met with county planning staff and county board members late last year but did not advance proposals. The task force asked staff to revise the draft ordinance to incorporate phased noise verification, options for measuring or specifying lower-frequency standards (with defensible scientific references), and mechanisms to ensure monitoring capacity is funded (for example by application fees or dedicated review fees). The group scheduled the next meeting for early August to walk through the draft ordinance in more detail.

Votes and formal actions at this meeting were limited. The agenda and addendum were approved by the task force; there were no ordinance adoptions or final actions on substantive rules during this session.

What’s next: staff will return with a revised draft that flags phasing rules, options for specifying measurable low-frequency metrics with scientific justification, a proposed monitoring fee structure or applicant-paid consultant protocol, and clarifications about complaint-handling and approved consultant review. The task force will review the full draft at the next meeting.