Data Center Knowledge Base

What Is a Data Center

A data center is a facility that houses large numbers of computer servers, storage systems, and networking equipment. These facilities store, process, and distribute the data that powers internet services, cloud computing, artificial intelligence applications, financial systems, healthcare records, and much more.

Data centers range in size from a single room to massive campuses covering hundreds of acres. The largest facilities — called hyperscale data centers — are built by major technology companies such as Amazon (AWS), Microsoft (Azure), Google, and Meta, or by specialized real estate investment trusts (REITs) such as Equinix, Digital Realty, and Iron Mountain that lease space to those companies. Many projects are developed by specialized real estate firms and then leased to cloud providers under long-term agreements.

The data center industry is one of the fastest-growing real estate sectors in the United States. Growth is driven primarily by cloud computing adoption, artificial intelligence workloads, and the ongoing shift of enterprise IT to third-party facilities. Industry growth is expected to continue as AI infrastructure demands increase — the power requirements of AI-focused data centers are substantially higher than traditional cloud computing facilities, which may amplify the infrastructure and grid impact questions relevant to local communities.

Illinois, particularly the I-88 corridor west of Chicago, is one of the top five data center markets nationally.^[1] Key location factors include access to major fiber-optic networks, relatively stable weather, land availability, and historically favorable energy costs and incentive policies.

AI Workloads and the Power Surge

The recent surge in data center proposals — including projects larger than anything most communities have previously considered — is driven substantially by the infrastructure demands of artificial intelligence. Understanding this context helps communities appreciate why current proposals are different in scale and impact from data centers approved a decade ago.

Traditional vs. AI Infrastructure: A conventional cloud computing data center primarily runs general-purpose CPUs handling web requests, databases, and business applications. Power density in these facilities is typically 5 to 15 kilowatts per server rack.^[1] AI training and inference workloads run on specialized graphics processing units (GPUs) or custom AI chips, which are far more power-intensive — often 50 to 100 kilowatts per rack or more.^[1] The same building footprint, filled with AI hardware instead of conventional servers, consumes dramatically more power.

Scale of New Proposals: The hyperscale data center campuses being proposed in Illinois and nationally reflect this shift. Where a large conventional data center might require 50 to 100 MW, AI-focused campuses are being planned at 200, 500, and even 1,000 MW — equivalent to a significant fraction of the output of a major power plant. These proposals strain regional grid infrastructure in ways that earlier projects did not.

Cooling Demands: High-density AI hardware also generates more heat per square foot, requiring more aggressive cooling. This increases water consumption in evaporative-cooling facilities and drives design choices — liquid cooling systems that circulate coolant directly to chip packages — that are newer and less tested at scale in municipal utility systems.

Speed of Deployment: AI infrastructure buildout is moving faster than traditional data center development. Developers are under competitive pressure to deploy capacity quickly, which can compress the timeline communities have to evaluate, negotiate, and impose conditions on projects.

What This Means for Communities: A proposal framed as a "data center" may look very different in practice depending on its intended use. Communities should ask specifically whether a proposed facility is designed for AI training or inference workloads, what the maximum power density per building is, and whether the cooling system is air-cooled, water-cooled, or liquid-cooled — as the answers drive fundamentally different infrastructure and environmental impact profiles.

Power Consumption

Data centers are among the most power-intensive land uses that a municipality can approve. A single large data center campus can consume 100 to 500 megawatts (MW) of electricity^[1] — comparable to the power needs of tens of thousands to hundreds of thousands of homes.

For context, a typical single-family home in Illinois uses approximately 7,000 to 8,000 kilowatt-hours (kWh) per year,^[2] equivalent to roughly 0.8 to 1 kilowatt of continuous average demand. A 100 MW data center campus represents the equivalent continuous load of roughly 100,000 homes.

This power demand must be served by the local electric utility — in northern Illinois, typically Commonwealth Edison (ComEd). Large data center projects may require significant upgrades to local substations and transmission infrastructure. The costs of these upgrades, and who pays for them, vary by utility tariff and negotiation.

The energy source matters: data centers powered primarily by coal or natural gas have a different carbon footprint than those served by nuclear or renewable energy. Illinois has a significant nuclear fleet, which reduces grid carbon intensity compared to many other states.

Grid & Utility Infrastructure

When a data center developer proposes a large load — anything from 50 MW upward — the utility and regional grid operator must study whether the existing transmission and substation infrastructure can support it. Understanding this process helps communities ask the right questions and identify who bears the cost.

Interconnection Studies: Before a large industrial customer can be served, ComEd and the regional grid operator (MISO, which manages the bulk power system across the Midwest) conduct an interconnection study. This study identifies what transmission and substation upgrades are needed to deliver power reliably to the new load. Upgrade costs can range from a few million to tens of millions of dollars^[1] depending on the condition and capacity of local infrastructure.

Who Pays for Upgrades: The answer depends on whether the upgrades are classified as "customer-specific" or as shared regional improvements. Customer-specific upgrades — a new substation feed, a dedicated transmission line — are typically paid for by the developer. Regional reliability upgrades that benefit the broader grid may be socialized across all ratepayers. Cost allocation is determined through utility tariffs, interconnection agreements, and regional transmission planning processes — some upgrades are developer-funded, some are socialized, and many projects involve a combination of both. Communities should ask developers and utilities to disclose which upgrades are required and how costs are allocated, so that the specific cost responsibility for this project is part of the public record.

Substation Capacity: Local substations transform high-voltage transmission power to distribution voltage. A large data center may require construction of a new substation or significant expansion of an existing one. Substation siting, construction, and interconnection timelines can take two to five years, which affects project scheduling.

New Transmission Lines: In some cases, a large load requires new high-voltage transmission lines. These projects involve easements, environmental review, and longer timelines. Communities along potential transmission corridors have independent interests in that process.

What to Request: Communities should ask developers to provide the results of any interconnection feasibility studies, disclose the estimated cost of required utility upgrades, and confirm whether any ratepayer costs are expected. This information is often not volunteered in zoning presentations.

Water Usage

Many data centers use water for cooling — specifically, evaporative cooling towers that discharge water vapor to dissipate heat from servers. Evaporative cooling is efficient but consumes significant quantities of water.

A large data center may consume 1 to 5 million gallons of water per day during peak cooling periods.^[1] Water usage varies by cooling technology (air-cooled systems use less water but are less efficient), climate, and data center design.

For communities served by municipal water systems or drawing from local aquifers, large data center water consumption can represent a material addition to local demand. Communities should understand the source of the water (municipal, well, river), whether the water is consumed (evaporated) or returned to the watershed, and what infrastructure upgrades, if any, are required to serve the facility.

Some newer data center designs use air cooling or liquid cooling systems that significantly reduce water consumption. The specific cooling technology a developer plans to use is typically disclosed in permit applications.

Diesel Generators & Air Quality

One of the least-discussed impacts of large data centers is the scale of their diesel backup generator infrastructure. Every data center requires reliable power backup; a power outage, even briefly, can cause data loss and service disruption. The solution is banks of large diesel generators capable of carrying the full facility load.

Scale of Generator Infrastructure: A 100 MW data center campus may install 50 to 100+ individual diesel generator sets, each rated at 1 to 3 MW. In aggregate, the backup capacity can equal or exceed the facility's full operating load. This is not a small generator in a closet — it is a substantial industrial installation comparable in scale to a small power plant.

Fuel Storage: Generators require large quantities of diesel fuel stored on-site so they can run through extended outages. A large campus is typically sized for 24 to 48 hours of continuous full-load operation. At roughly 70 to 80 gallons of diesel per hour per megawatt of generator output, a 100 MW campus burns approximately 7,000 to 8,000 gallons per hour at full load. This means on-site storage of hundreds of thousands to over a million gallons — comparable in scale to a bulk petroleum storage facility. Storage above 1,320 gallons of aboveground diesel triggers EPA Spill Prevention, Control, and Countermeasure (SPCC) plan requirements.^[1] Communities should ask to review the SPCC plan and confirm that the local fire district has been briefed on storage volumes and tank locations.

Fuel Deliveries: Keeping tanks full during normal operations, and replenishing after any generator run, requires regular tanker truck deliveries. Each tanker carries approximately 8,000 to 9,000 gallons. Filling a large campus tank farm from near-empty can require dozens to over a hundred individual deliveries. During extended grid emergencies, fuel resupply becomes a logistics operation — with continuous tanker traffic that communities and emergency managers should anticipate.

Testing Requirements: Generators must be tested regularly to ensure they will start and carry load when needed. The EPA and industry practice generally call for monthly testing of emergency generators, typically for 30 minutes to two hours per unit. On a large campus, this means diesel engines running regularly — producing exhaust, noise, and fuel consumption — even when there is no actual power outage.

Air Quality Permitting: Diesel generators that run for non-emergency purposes (including testing beyond certain thresholds) must be permitted through the Illinois Environmental Protection Agency (IEPA). Facilities above certain emission thresholds require a Title V air permit. These permits specify allowable operating hours, emission limits for particulate matter, nitrogen oxides (NOx), carbon monoxide (CO), and other pollutants, and monitoring and reporting requirements. Permit applications are public records.

Health Considerations: Diesel exhaust is classified as carcinogenic to humans (Group 1) by the International Agency for Research on Cancer.^[2] Particulate matter from diesel combustion is associated with respiratory and cardiovascular disease. Communities with sensitive populations — schools, hospitals, residential neighborhoods — near proposed data center sites should consider requesting independent air quality modeling as a condition of approval.

What to Request: Communities should ask developers to disclose the total nameplate generator capacity, the total on-site diesel fuel storage volume, the planned testing schedule, whether a Title V or minor source air permit will be required, and what noise attenuation measures are proposed for the generator enclosures.

Environmental Impacts

Data center development has several categories of environmental impact that are relevant to local communities.

Land Use: Large data center campuses convert farmland, open space, or light industrial land to heavily impervious surfaces. Stormwater management, grading, and impervious cover requirements are typically addressed in site plan review.

Noise: Data centers generate continuous noise from cooling equipment — fans, cooling towers, and backup generators. Noise levels at the property line are typically regulated by local ordinance and may be a condition of zoning approval. Generator testing and emergency operations can produce higher noise levels.

Visual Impact: Data centers are large, utilitarian structures. Some include significant mechanical equipment visible from surrounding areas. Design standards (screening, landscaping, setbacks) can be negotiated as part of the approval process.

Energy Source: As noted in the power section, the carbon footprint of a data center depends significantly on the energy mix of the regional grid. Some developers make public commitments to renewable energy procurement.

Emergency Preparedness: Large electrical infrastructure and diesel generator fuel storage may create local emergency response considerations.

Impact on Nearby Property Values

One impact that is rarely discussed in developer presentations — but that directly concerns neighboring homeowners — is the effect a large data center may have on residential property values in the surrounding area. The municipal tax revenue a data center generates and the property values of adjacent homes are separate questions, and the answers can point in opposite directions.

What Research Shows: Three bodies of research are relevant to evaluating this risk. They vary in scope and depth, but together they support a consistent conclusion: proximity effects are real, site-specific, and highly sensitive to buffering, setbacks, noise, and visual character.

Data Center Studies: Peer-reviewed academic research focused specifically on data center proximity effects on residential property values is limited as of 2024–2025 — the scale of suburban and exurban data center development is relatively recent, and the research has not caught up. Available evidence comes primarily from appraisal practitioners who have evaluated specific contested projects.^[1] Those practitioner reports find that impacts are highly site-specific. Facilities with effective setbacks, full visual screening, and documented noise attenuation show little measurable effect on adjacent values. Poorly sited facilities — with significant cooling fan noise, prominent visual mass, and generator testing close to homes — have been associated with measurable discounts on nearby residential sales. The absence of a large peer-reviewed literature does not mean the risk is absent; it means that communities cannot rely on published averages and should require a site-specific appraisal analysis prepared by a licensed appraiser with industrial land-use experience.

Warehouse and Distribution Studies: Data centers and large warehouse or distribution facilities share the characteristics that drive neighborhood impact — similar building scale, 24/7 operations, heavy truck access, exterior lighting, and continuous mechanical noise. The warehouse literature is substantially more developed. Studies of large distribution and fulfillment centers, including e-commerce facilities, find statistically significant negative effects on nearby residential values, typically concentrated within a half-mile radius.^[2] The primary drivers are truck traffic volumes, noise, and visual character — not anything unique to the warehouse use category. These findings are directly relevant to data center siting because the physical land-use profile is what matters to adjacent homeowners, not the name of the use.

Industrial Facility Studies: The broadest and most established body of evidence covers heavy industrial land uses generally — manufacturing plants, power infrastructure, and large logistics operations. Appraisal industry standards and peer-reviewed academic literature consistently find negative effects on residential properties within a half-mile to one-mile radius.^[3] The magnitude varies from a few percent to more than 15 percent of assessed value, depending on the scale, proximity, and character of the specific nuisances the facility generates.

Results Vary Significantly by Site Conditions: Across all three bodies of research, the most consistent finding is that impacts are highly site-specific. The factors that most reliably determine whether proximity to a large facility affects residential values — and by how much — are: (1) physical separation, meaning setback distance from residential parcels; (2) visual screening from masonry walls, earthen berms, and dense landscaping sufficient to block sightlines; (3) noise levels at residential property lines during both normal operations and generator testing; (4) exterior lighting spillover onto neighboring properties; and (5) heavy truck access routes running through residential neighborhoods. A facility designed with generous setbacks, documented noise attenuation, and full visual screening can have a materially different impact than one sited close to homes with minimal buffering. This variability is precisely why the correct tool for evaluating a specific proposal is a site-specific, independent appraisal analysis — not a national industry average.

The Municipal Revenue vs. Neighbor Value Distinction: Developers frequently present property tax projections as a community benefit. But the taxable assessed value of a data center is not the same as its stated investment value. Illinois's tax exemption for qualifying data center equipment — servers, networking gear, cooling infrastructure — removes much of the equipment value from the tax rolls entirely. The building shell and land remain taxable, but communities should request an independent assessment of actual taxable value rather than relying on a developer's investment figure. Meanwhile, adjacent homeowners who experience noise, visual impact, or neighborhood character changes may see their own assessed values stagnate or decline — a cost that is diffuse and rarely captured in municipal impact analyses.

What Communities Can Request: Communities can require an independent real estate impact analysis as part of the application — analogous to traffic studies or environmental assessments — prepared by a licensed appraiser with experience in industrial land use impacts. This is standard practice in some jurisdictions. The analysis should estimate effects on residential values within a defined radius under different buffering and noise scenarios, and should address the specific siting conditions of the proposal. Requiring this analysis before a zoning vote creates an independent record and may reveal conditions worth negotiating.

Protections to Negotiate: Conditions that reduce property value risk to neighbors include minimum setbacks from residential property lines exceeding zoning minimums; mandatory noise limits measured at residential property lines with independent verification; screening requirements (masonry walls, earthen berms, dense landscaping) tall enough to block sightlines from adjacent homes; limits on exterior lighting spillover; and restrictions on heavy truck access routes through residential areas.

Jobs & Economic Impacts

The economic impact claims associated with data center projects require careful analysis, as the benefits and costs are not evenly distributed.

Jobs: Data centers create substantial construction employment during the build phase — often hundreds of workers for large projects. Permanent operational employment is typically much smaller: a large data center campus may employ 50 to 200 full-time workers^[1] in operations, security, and management. Job quality is generally high for technical and management roles. This is a significant difference from manufacturing facilities, which often employ more workers per square foot.

Tax Revenue: Developers and municipalities frequently cite property tax revenue as a primary community benefit. However, when tax incentive agreements (TIF, enterprise zones, abatements) are in place, the incremental tax revenue may be reduced or deferred for years or decades. The net tax benefit depends on the specific terms of any incentive agreement, which are public records.

Infrastructure Costs: Communities may bear costs for road improvements, utility upgrades, and emergency services capacity to support large facilities. These costs are sometimes negotiated as part of annexation or development agreements.

Long-Term Lock-In: Data centers are capital-intensive, long-lived assets. Once built, the land use and utility load are largely fixed for decades. Communities should consider whether the land use, infrastructure commitments, and incentive costs align with long-term municipal goals.

Illinois Tax Incentives

Illinois offers one of the most generous data center tax incentive programs in the United States. Understanding what is being given away — and what conditions apply — is essential context for evaluating any project in the state.

The Core Exemption: Under Illinois law (35 ILCS 120/1l, enacted in 2019 and significantly expanded by Public Act 102-0669 in 2022),^[1] qualifying data centers are exempt from the state's Retailers' Occupation Tax and Use Tax on data center equipment — including servers, networking hardware, cooling infrastructure, and other qualifying property. They are also exempt from the state electricity excise tax on power consumed at the facility. These are substantial exemptions: sales tax in Illinois runs 6.25% at the state level, and electricity taxes add further savings.

Qualification Thresholds: To qualify, a new facility must invest at least $250 million in Illinois over a 60-month period.^[1] Existing Illinois data centers can qualify for expansion exemptions with a lower threshold. Smaller "emerging technology" data centers have a lower threshold of $10 million. The investment must be certified by the Illinois Department of Commerce and Economic Opportunity (DCEO).

Duration: The exemption runs for 20 years from the date of the initial certification.^[1] This is a long-term fiscal commitment by the state.

Local Incentives on Top: State tax exemptions are separate from local incentives that municipalities may offer — property tax abatements, TIF financing, enterprise zone designations, or reduced infrastructure fees. Local and state incentives can stack, sometimes significantly reducing the total tax contribution a project makes relative to its stated economic impact.

What to Look For: When evaluating a local project, residents and officials should request: (1) a copy of any DCEO certification or application; (2) an estimate of the total value of state and local tax exemptions over the project's life; and (3) a clear accounting of what net tax revenue — after all incentives — is projected to flow to local taxing bodies, including school districts, park districts, and the municipality itself.

Policy Context: Illinois lawmakers have debated whether the exemptions are too generous given the relatively low job creation of large data centers. The law has been amended several times. Communities should be aware that the incentive landscape may continue to evolve.

Community Benefit Agreements

A Community Benefit Agreement (CBA) is a legally binding contract — or a set of conditions attached to a zoning or development approval — that commits a developer to specific obligations in exchange for municipal approval or support. CBAs are one of the most effective tools communities have for converting a developer's desire for local approval into tangible, enforceable benefits.

What Communities Have Negotiated: Specific provisions that communities have secured from data center developers include: caps on water consumption with monitoring and reporting requirements; noise measurement standards and decibel limits at residential property lines; local hiring preferences for construction and operations positions; commitments to procure renewable energy equivalent to a specified percentage of facility consumption; road improvement contributions; emergency services funding; and landscaping and screening standards beyond the minimum required by ordinance.

How They Are Created: CBAs can take several forms. Some are standalone agreements between the developer and the municipality or a community organization, executed before a zoning vote. Others are incorporated directly as conditions of approval in a special use permit, planned unit development, or annexation agreement — which makes them enforceable as part of the approval and tied to the facility's operating permits.

The Leverage Window: Developer leverage is highest before approval and lowest after. Once a project is approved and built, the community has little recourse if commitments are not met unless they were written into enforceable conditions of approval. Communities should negotiate and finalize all material commitments before any vote on zoning, annexation, or incentive agreements.

Enforcement: An agreement is only as good as its enforcement mechanism. Communities should ensure that CBA provisions are: written specifically enough to be measurable (decibel limits, not "reasonable noise levels"); tied to annual or periodic reporting obligations; backed by a remedy if violated (permit revocation, financial penalty, or bond forfeiture); and assigned to a specific municipal official or body responsible for monitoring compliance.

Getting Started: Residents can advocate for a CBA by presenting a written list of proposed conditions at the public hearing, contacting village board members before a vote, and asking the village attorney to review and strengthen any proposed conditions. Model CBA language from comparable projects in other communities is increasingly available through planning associations and academic research.

What Developers Usually Say

When a data center proposal comes before a planning commission or village board, developers typically present a standard set of arguments for why the project benefits the community. These arguments are worth understanding on their own terms — not to dismiss them, but to know what follow-up questions they leave open. This section presents five common claims, the context that shapes each one, and questions communities may wish to raise.

Jobs: Developers typically highlight the construction workforce — often hundreds of workers over one to two years — alongside a projected number of permanent positions. They may also cite economic multiplier effects, arguing that local spending and permanent staff salaries ripple through the regional economy. The construction employment figure is real but temporary; it ends when the building is complete. Permanent operational staffing at a large campus is typically 50 to 200 full-time workers — a contrast to manufacturing facilities, which may employ many times as many workers per acre. Multiplier estimates vary widely and are usually provided by consultants engaged by the developer. Questions communities may wish to ask: How many construction jobs are local hires versus workers brought in from outside the region? How many permanent full-time positions will be based at this specific site? What is the projected average wage and benefit level? Has an independent analyst reviewed the multiplier methodology?

Tax Revenue: Developers commonly present the total investment value of the project — often hundreds of millions to billions of dollars — and translate it into projected property tax revenue for the municipality, school district, and other taxing bodies. The investment figure is not the same as the taxable assessed value. Illinois's data center equipment exemption removes qualifying servers, networking hardware, and cooling infrastructure from state sales and use tax, and only the building shell and land are fully taxable as real property. If any local incentive agreement is in place — a TIF, enterprise zone designation, or property tax abatement — a portion of even that property tax revenue may be deferred or reduced for years or decades. The net tax benefit to any individual taxing body may be substantially lower than the headline investment figure implies. Questions communities may wish to ask: What is the projected taxable assessed value of the real property after the equipment exemption? What net property tax revenue is projected to flow to each taxing body after all incentive agreements, and on what timeline? Have the school district and other taxing bodies reviewed the projections independently?

Renewable Energy: Many developers now include renewable energy commitments in standard project presentations — pledges to achieve "100% renewable energy," "net-zero carbon operations," or to procure renewables equivalent to the facility's consumption through power purchase agreements or renewable energy certificates (RECs). There is a meaningful difference between on-site renewable generation, direct power purchase agreements with specific generators, and REC purchases — which are tradeable credits retired to claim renewable consumption without any physical delivery of renewable power to the site. REC-based commitments do not reduce the facility's physical draw on the local grid; a 200 MW facility still requires 200 MW of grid infrastructure regardless of what the developer retires on paper. Questions communities may wish to ask: What specific mechanism — on-site generation, direct PPA, or REC purchases — will be used to meet the commitment? Does the commitment cover the full facility load? Does it affect the infrastructure requirements placed on the local grid? Is it a binding condition of approval or an aspirational goal?

Grid Infrastructure Investment: Developers sometimes present required substation or transmission upgrades as a community benefit — infrastructure that will improve local grid reliability alongside serving the new facility. Grid infrastructure investments primarily serve the developer's own operational need for reliable power. Whether a particular upgrade incidentally improves reliability for surrounding customers depends on the specific design and is a technical question that communities and their utility should verify. Cost allocation — how much the developer pays versus how much is socialized to existing ratepayers — is determined through interconnection agreements and MISO processes and is not always transparent in public presentations. Questions communities may wish to ask: Which utility upgrades are required specifically for this project, and who is paying for them? Are any upgrade costs being allocated to existing ratepayers? Does any proposed infrastructure investment improve capacity or reliability for current customers — and if so, which ones?

Community Benefits: Developer presentations frequently include commitments described as community benefits — contributions to local roads, emergency services, school programs, local hiring initiatives, or charitable giving. There is an important distinction between voluntary pledges and legally enforceable conditions of approval. Commitments described in a presentation or a letter of intent are not the same as conditions written into a permit, annexation agreement, or development agreement. Voluntary pledges are difficult to enforce after approval has been granted and the developer's need for local goodwill has passed. The value of any stated community benefit depends almost entirely on how specifically it is written and where it appears — in a slide deck or in a signed, recorded legal instrument. Questions communities may wish to ask: Are these commitments conditions of approval written into the permit or annexation agreement, or are they voluntary pledges? Are they specific and measurable — dollar amounts, job counts, deadlines — or general in nature? What is the remedy if a commitment is not fulfilled? Has the village attorney reviewed each provision?

Questions to Ask Before Approving

The following questions are a due diligence checklist for village board members, planning commissioners, and engaged residents evaluating a data center proposal. Answers should be provided in writing and entered into the public record before any vote.

Tax and Incentives: What is the total estimated value of all state and local tax exemptions over the life of the project? What net property tax revenue — after all abatements, TIF diversions, and enterprise zone credits — is projected to flow to each local taxing body (municipality, school district, library, park district) and when? Has the village attorney reviewed all proposed incentive agreements?

Jobs: How many permanent, full-time jobs will be created at this facility? What is the projected average wage and benefit level for those positions? What percentage of construction jobs are expected to be filled by local or Illinois workers?

Power and Infrastructure: What is the facility's projected peak electrical load in megawatts? What utility infrastructure upgrades are required, and who pays for them? Has a formal interconnection study been completed by ComEd or MISO? Are any ratepayer costs associated with the required upgrades?

Water: What is the projected daily water consumption at full build-out? What is the source of that water, and does the municipal system have capacity to serve it? Will the facility return any water to the local watershed, or is consumption primarily evaporative?

Generators and Air Quality: What is the total nameplate diesel generator capacity in megawatts? What is the total volume of on-site diesel fuel storage? What is the planned testing schedule and duration? Has the developer applied for or received an IEPA air permit? What are the emission limits in that permit?

Noise: What noise levels are projected at the nearest residential property line during normal operations and during generator testing? What noise attenuation measures — barriers, enclosures, equipment selection — are proposed?

Community Benefits: Is the developer proposing any community benefit agreement, and if so, what are the specific, measurable commitments? Are those commitments conditions of approval or unenforceable representations?

Long-Term Considerations: What happens to the site if the data center ceases operations? Are there decommissioning or remediation obligations? Does the approval lock in any land-use or infrastructure commitments that would constrain future municipal options?

What Other Communities Have Done

Communities across the United States have responded to data center proposals in a range of ways.

Negotiated Conditions: Many communities approve data center projects but attach conditions — noise limits, setback requirements, landscaping and screening standards, water usage caps, community benefit agreements, or requirements to purchase renewable energy.

Moratoria and Studies: Some municipalities have enacted temporary moratoria on new data center approvals to allow time for comprehensive planning studies examining infrastructure capacity, incentive policy, and land use goals.

Zoning Amendments: Several communities have amended their zoning ordinances to create data center-specific use categories with tailored standards — separating large-scale hyperscale facilities from smaller commercial data centers and applying different approval standards to each.

Denials: Some communities have denied data center applications outright on grounds including inadequate infrastructure, incompatibility with surrounding land use, or insufficient benefit relative to impacts.

Incentive Policy Reform: Some states and municipalities have revised incentive policies after finding that blanket tax exemptions for data centers produced fewer local benefits than projected.

Approvals Without Conditions: Many communities have approved data center projects with minimal or no conditions, accepting developer representations about job creation and tax revenue at face value.

The range of outcomes reflects the significant discretion local governments have in this process and the importance of community participation in shaping that outcome.