News & Insights

Data center developers are used to solving hard problems: power availability, speed to market, land constraints, utility coordination, cooling strategy, and community acceptance. Noise is now part of that equation.

As data centers grow larger, denser, and more power-intensive, the acoustic profile of a site is changing. Cooling equipment, generators, substations, transformers, and other supporting infrastructure all contribute to sound that may meet a technical decibel limit yet still raise real concerns for nearby communities.

But residents don’t talk about octave bands or tonal characteristics. They describe a persistent hum, a low-frequency vibration, or a general nuisance that alters how they experience their homes and neighborhoods.

For developers, that distinction matters. A project can comply with a stated ordinance yet still face complaints, delays, public resistance, or reputational risk if acoustic control isn’t addressed early. As local governments respond to growing community pressure, noise abatement is shifting from a late-stage technical detail to an early development risk that deserves the same attention as power, water, traffic, and visual impact.

The acoustic footprint is getting harder to manage

Chillers, cooling towers, rooftop fans, generators, and transformers can all operate continuously. Most of that equipment sits outside the building, where sound travels freely. As facilities grow in capacity, more of this infrastructure is added to the site, and while sound doesn’t scale linearly, the complexity of managing it does.

One of the more underappreciated dynamics is generator testing. Because data centers are critical infrastructure, backup generators must be tested at least once a month per unit to confirm performance in the event of an emergency.

On a smaller campus with a handful of units, that testing window is short and manageable. But on a large hyperscale campus with hundreds of generators, completing the required testing for every unit can consume the entire allowable daytime window under most ordinances. What starts as a monthly maintenance protocol becomes, in effect, a regular daytime noise condition that nearby residents will notice and respond to, even if it technically falls within the ordinance’s limits.

Additionally, the character of the sound matters as much as the volume. Transformer hum, which originates from the frequency of electrical power cycling through the equipment, is particularly difficult to address. It’s tonal, meaning it has a distinct pitch, and tonal sounds tend to attract complaints even at lower decibel levels than broadband noise.

Several jurisdictions have begun adding tonal penalties to their ordinances in direct response to this problem. They’re placing stricter limits on facilities that produce identifiable tones rather than ambient-style sound.

That’s a meaningful shift, and it’s happening unevenly, town by town, with no statewide or national consistency to guide developers from one project to the next. The best time to get ahead of that complexity is before the site layout is set.

Acoustic planning belongs at the beginning of site design

Acoustic planning has the most leverage during early site layout, which is also when it’s least often included. Before equipment is selected, before computational fluid dynamics modeling begins, and before permits are filed is when the decisions that most affect acoustic performance get made.

The placement of equipment on the site, its distance from property boundaries, and the positioning between noisy sources and sensitive receptors are all cost-effective to optimize at this stage and expensive to change later.

At a minimum, keeping the loudest equipment as far as possible from the most sensitive neighbors (residential properties, schools, healthcare facilities) is a low-cost way to build in margin before engineering begins. Identifying those neighbors as part of early due diligence and understanding how quiet their baseline environment is shapes every subsequent decision about mitigation and layout.

That baseline question deserves particular attention on rural sites, where a significant share of large data center development is occurring. Local noise regulations vary widely, with some not updated for many years. Many ordinances base limits on ambient sound levels rather than fixed decibel thresholds, so the quieter the environment, the more stringent the standards effectively become.

The baseline for “quiet” in rural areas is very different from what’s considered quiet in suburban areas, and a facility that comfortably meets its ordinance in one context may be clearly audible in another. Developers who discover this late often find themselves choosing between expensive retrofits and community relations problems that don’t have clean engineering solutions.

Three project milestones are the critical checkpoints for acoustic planning:

1. During site acquisition, the essential steps include identifying receptors, reviewing local ordinance structures (fixed thresholds, ambient-based limits, and tonal criteria), and designing a site layout that maintains sufficient distance between the loudest sources and nearby sensitive properties.
2. When CFD modeling begins, acoustic modeling should be running in parallel, since the two are interdependent once equipment positions start shifting.
3. During equipment selection, the frequency profile should be part of the evaluation criteria alongside thermal and electrical performance, particularly for transformers and cooling equipment that generate tonal sound.

The relationship between acoustic and airflow modeling is more than procedural. CFD analysis determines how heat moves away from equipment, and engineers often adjust equipment positions to improve thermal performance. Relocating a unit farther from a noise barrier to enhance airflow can reduce the barrier’s effectiveness at mitigating sound from the unit.

When acoustic and thermal modeling are done separately, conflicts often emerge late, leading to higher resolution costs. Running them in tandem allows tradeoffs to be evaluated with full information before positions harden and options narrow.

Addressing the noise source by source

Managing acoustic risk across a data center development comes down to three areas: early planning, source-specific mitigation, and community engagement. The following covers the mitigation side, organized by the primary noise sources a facility generates.

1. Cooling equipment

Among the loudest continuous sources on a data center campus, chillers and cooling towers produce broadband noise from fan operation and heat rejection. The exhaust path is particularly significant because sound generated inside the unit travels out through openings. Without treatment, the sound propagates freely across the site.

Sound attenuators installed on chiller exhaust paths are the most common mitigation approach. On a recent project subject to a noise standard tied to the ambient L90 level (essentially the quietest 10 percent of the day, which typically occurs in the early morning hours), receptor properties were roughly 1,500 feet from the site. Meeting a target of approximately 34 dBA at those properties required 10-foot attenuators on all chiller exhaust paths.

The main implementation challenge is that adding an attenuator causes a pressure drop, which makes the fan work harder and may decrease the unit’s rated capacity. Verifying that the chiller maintains its specified performance after installing the attenuator requires direct coordination with the equipment manufacturer.

Additionally, changes in mechanical performance influence electrical load calculations. These interdependent factors are often overlooked when acoustic design is handled separately from mechanical and electrical design.

2. Generators

Generator testing requires running each unit individually. This testing results in some of the loudest single-source noises on site.

The typical solution involves sound-mitigating enclosures with mufflers on the exhaust stack, but enclosure standards vary by location. Units closer to sensitive areas or with less physical separation require higher-rated enclosures than those farther away. For the project mentioned earlier, enclosure ratings were assigned based on each unit’s position, requiring a detailed acoustic model to determine the appropriate level of sound treatment.

The main consideration is thermal management. Generator enclosures limit airflow, affecting the generator’s cooling. The ventilation inside the enclosure must be designed to handle heat accumulation during long runs. The height of the exhaust stack can also be a concern. To get the exhaust high enough to satisfy the CFD requirements generally pushes it above any sound barriers, rendering them ineffective for this sound source.

This is particularly important on campuses where multiple generators run at once. Close collaboration between acoustic and mechanical engineers on enclosure specifications is essential, as both fields influence the same physical design.

3. Transformers and substations

Transformer hum is one of the most persistent acoustic problems in data center development, and one of the hardest to resolve after equipment is already in place. The hum originates from the frequency of electrical power cycling through the equipment, producing a tonal sound at a predictable frequency. That tonality matters: many ordinances now apply stricter limits to tonal noise than to broadband noise at the same decibel level, and tonal sounds tend to draw complaints at lower absolute levels than other noise sources.

Standard NEMA-rated transformers are specified primarily for electrical performance, with acoustic output treated as a secondary consideration. On sites where tonal criteria apply or where ambient levels are low enough that the hum will be audible at receptor properties, standard ratings are frequently insufficient.

The solution is to source transformer manufacturers who build equipment to acoustic standards beyond the default NEMA specifications. Identifying those manufacturers and incorporating acoustic requirements into the procurement process requires additional lead time that must be planned for during design.

On the same project, perimeter barrier walls were installed at the roofline to limit sound traveling off the property. Barrier walls provide site-level mitigation across multiple source types, but their effectiveness depends on their placement relative to equipment positions. Moving a piece of equipment to improve airflow can shift it outside the barrier’s coverage area, which is another reason acoustic and CFD modeling need to run in tandem.

Each of these solutions required cross-disciplinary coordination. An attenuator on a chiller affects mechanical performance, which in turn affects electrical load. A generator enclosure affects ventilation, which in turn affects thermal performance. Barrier wall placement interacts with equipment layout and airflow. None of these decisions can be made in isolation, and when they’re made late in design or during construction, the cost of accommodating them multiplies.

As more jurisdictions add tonal criteria to their ordinances, equipment selection and treatment strategies need to account for frequency profile alongside overall decibel output. For facilities with transformers or other tonal sources, changing the character of what leaves the site is as important as managing the volume.

Community engagement as part of the development strategy

Even a project that meets every requirement can face legal exposure and community opposition if perception is left unmanaged.

Ordinance compliance doesn’t prevent nuisance lawsuits, and these cases aren’t always based on technical measurements. A neighbor’s attorney might play a recording of ambient noise for a jury, and if the jury finds it objectionable, the developer’s technical compliance record may not influence the decision.

The most effective approach is to involve the community before problems are raised. Attending public meetings, inviting questions about noise concerns, and committing to specific mitigation measures on the record all build the kind of goodwill that reduces legal exposure and makes the permitting process more predictable.

The conditional use permit process is both a risk and an opportunity. More jurisdictions now require one before land development or building permits can be issued because it provides a formal venue for raising noise concerns. Equally important, it also creates a formal record of the developer’s response to those concerns.

Developers who navigate this most effectively are typically those managing facilities over the long term and maintaining ongoing community relationships. Those with a shorter-term focus, mainly acquiring and entitling land for resale, tend to have less motivation to invest in community relationships. But the liabilities associated with the project remain regardless of the operator, and the reputational damage caused by a noisy facility affects more than just the individual developer.

Early site planning, source-specific mitigation, and community engagement are compounding investments, each shaping the difficulty of what comes next. Decisions made at the layout stage determine how much mitigation will be required, and mitigation choices made during design determine how much community relations work remains. Treating any of these as a separate workstream pushes risk downstream, where the cost of addressing it is higher, and the available options are fewer.

How can Salas O’Brien help?

Every project starts with a different ordinance, a different site, and a different set of neighbors. It intersects mechanical performance, electrical design, and permitting strategy.

Salas O’Brien brings technical depth and cross-disciplinary coordination to navigate complexity without losing time or adding risk. Our acousticians are INCE board-certified and can do more than produce a noise study, by helping you:

• Model acoustic performance in conjunction with CFD analysis
• Coordinate mitigation specifications directly with equipment manufacturers
• Represent the project at conditional use permit hearings and community meetings

We work through the tradeoffs between acoustic treatment and mechanical performance before they become conflicts. We also help you understand what your specific ordinance requires and where the gaps between compliance and community satisfaction are likely to appear.

To talk through what acoustic planning looks like for your next project, reach out to one of our data center experts or contact us at [email protected].

For media inquiries on this article, reach out to [email protected].