INDIANAPOLIS | A proposed $2 billion data-center campus on Indianapolis’s east side moved closer to approval after a Metropolitan Development Commission hearing examiner recommended the project, but the decision is not the final word. DC BLOX wants to build three large facilities on former industrial land near Irvington and the Pennsy Trail. The proposal promises redevelopment and investment while raising questions about power demand, generator emissions, noise, neighborhood setbacks and the pace at which Indianapolis is approving data centers before adopting comprehensive citywide rules.
The site lies near South Kitley Avenue on property associated with a former Ford operation. Reusing an industrial brownfield can reduce pressure to develop undeveloped land and may bring environmental cleanup. It can also place a modern, high-energy facility near homes and a heavily used trail. Residents have asked whether the proposed use is compatible with surrounding neighborhoods and whether protections will remain enforceable after construction begins.
Project materials describe three data-center buildings that could draw up to 78 megawatts of electricity. That is not the same as saying the campus will use its maximum capacity at all times, but it illustrates the scale of the requested service. Citizens want to know which utility investments will be required, who will pay for them and whether other customers could face higher costs or reliability consequences.
The proposal also includes as many as 56 backup generators. Data centers use generators to maintain computing during grid failures, and they are generally tested periodically even when no emergency occurs. Diesel equipment can create noise and local air emissions. Permit conditions should specify testing hours, acoustic limits, fuel storage, emissions controls and public reporting of actual operation.
The hearing examiner’s recommendation followed public testimony and review of a use variance. The full Metropolitan Development Commission retains authority over final action. That distinction matters because a recommendation can be reported as momentum without being presented as completed approval. Commissioners can adopt conditions, reject the request or seek additional information.
DC BLOX argues that the campus would convert a difficult industrial property into productive use and contribute substantial private investment. Data centers can generate construction work, property-tax revenue and demand for electrical and technical services. Their permanent employment is often smaller than that of manufacturing plants with similar footprints, so public officials should separate construction jobs from long-term positions when describing economic benefit.
Neighborhood concerns are not necessarily opposition to technology. Residents have asked for detailed answers about noise, water, traffic, power and the relationship to the Pennsy Trail. Those are ordinary land-use questions for a facility operating continuously. A reliable approval process should provide measurable standards rather than asking neighbors to trust future good intentions.
The former industrial use creates an environmental dimension. Brownfield redevelopment can be valuable when contaminated soil is properly assessed and remediated. Construction plans should explain what testing has occurred, how excavated material will be handled and whether groundwater or vapor concerns exist. Environmental obligations should survive changes in ownership or project financing.
Water use also needs clarity. Some data centers use significant water for cooling, while others rely more heavily on air cooling or closed-loop systems. The developer should publish expected annual and peak demand under realistic operating scenarios. Indianapolis residents should not have to infer consumption from generic descriptions of the industry.
The city is considering how to regulate data centers more broadly as proposals multiply across Indiana. Project-by-project zoning can leave residents and developers without consistent expectations. A citywide ordinance could set minimum setbacks, noise monitoring, generator rules, energy and water disclosures, design standards and decommissioning requirements. Approving major projects before those standards are complete can make later policy harder to apply evenly.
Electricity planning is regional. Utilities must build generation, substations and transmission based on expected loads, and those costs can extend beyond city boundaries. Data-center customers may sign special contracts, but regulators should ensure ordinary ratepayers are not left funding infrastructure dedicated mainly to private facilities. Public disclosure is needed when economic-development agreements affect cost allocation.
The project also intersects with Indiana’s push to attract technology infrastructure. State leaders see data centers as a source of investment and strategic importance. Local governments bear the immediate land-use effects, however. A state incentive does not answer whether a particular site has adequate buffers or whether a neighborhood should accept generator noise. The two levels of policy must be evaluated separately.
If approved, compliance should be monitored after construction. Noise limits need measurements at property lines, not only modeling before permits are issued. Generator testing and emissions should be logged. Landscaping and trail buffers should be inspected after plants mature. A complaint process should identify who responds and what remedies are available.
The city should also require a decommissioning plan. Computing equipment changes rapidly, and a large specialized building can become difficult to reuse if a tenant leaves. Financial assurances can protect taxpayers from abandoned infrastructure or environmental cleanup. Long-term planning is part of evaluating a project advertised as a long-term economic asset.
The recommendation gives DC BLOX a stronger path forward, but the public debate should continue through final action. Indianapolis can support redevelopment and digital infrastructure while insisting on transparent utility costs, enforceable neighborhood protections and consistent standards. The decision should not be reduced to being for or against technology. It is a test of whether the city can define the conditions under which a very large industrial load belongs near an established community.
Tax incentives and abatements should be disclosed alongside projected revenue. A project described as a multibillion-dollar investment may still receive public support that reduces near-term tax collections. Residents need a net fiscal analysis showing construction incentives, infrastructure costs, expected payments and the assumptions used to estimate benefit.
Emergency planning should address fuel, fire suppression and access for first responders. Large battery systems, electrical equipment and diesel storage create specialized risks. The fire department should review site design and conduct exercises before operation, with information available to nearby residents about alarms and emergency routes.
Data-center security should not create an opaque compound disconnected from its surroundings. Fencing and controlled access are understandable, but site design can preserve landscaping, trail safety and visual buffers. Lighting should protect the facility without spilling into homes or disrupting wildlife along the trail corridor.
The developer’s future customers may also affect public scrutiny. Cloud and artificial-intelligence tenants can change, but the city’s land-use approval remains. Conditions should apply to the property and operation regardless of which company leases capacity, preventing a later tenant from avoiding commitments made during zoning.
A transparent community-benefits agreement could identify local hiring, environmental monitoring, trail improvements and complaint resolution. Such agreements should contain measurable obligations and enforcement, not promotional promises. The project’s scale gives Indianapolis leverage to require a durable public return.
Public officials should also examine the cumulative effect of multiple proposed data centers. One facility may fit within available electric and water capacity, while several projects can require major upgrades. Regional planning should publish aggregate demand scenarios so each zoning case is not evaluated as though it exists alone.
Construction traffic deserves enforceable routing and hours. Heavy equipment and material deliveries can affect nearby roads, schools and the trail long before servers begin operating. A logistics plan should identify truck routes, road repairs and a contact for residents reporting violations.
Additional Reporting By: Rick Ellis, CGN News Local Reporter, Daniel Cho, CGN News Technology Reporter and James Holloway, CGN News Energy Reporter; Mirror Indy; WFYI; DC BLOX; WTHR