What a data centre noise assessment has to answer
A data centre is a building full of heat. Every watt the servers draw comes out as heat that has to be removed continuously, so the chillers and dry coolers that do it run day and night, all year, at a duty set by the IT load and the outside air. Behind them sit the standby generators, usually several, which stand idle most of the time and run on a test schedule. Between the site and the grid sits a substation with its transformers. Each of those sources behaves differently, and a data centre noise assessment has to treat them as the different problems they are. For battery storage schemes, see our renewables and battery storage page.
The planning question is the BS 4142 one: what is the rating level of the site's sound at the nearest homes, and how does it compare with the background sound level there without the site? Our BS 4142 explainer sets out how the rating level is built. What matters here is how that method meets a source that never switches off, on land chosen for its grid connection rather than for its neighbours. Where the background and the rating level are both low, the standard says the absolute level might be as relevant as the margin over background, or more so, and where the council or a planning condition sets its own plant noise limit, the result is tested against that limit as well.
The condition that controls the result is rarely the average one. Cooling plant works hardest in hot weather, and a hot night with little wind can bring a heavy cooling load, a low background and open bedroom windows together. So we assess the heaviest cooling load the site can credibly run at night against a representative night-time background, typical of the quietest part of the night the plant runs in, not an average load against an average background, and the report states which case it has used for each. That background is logged over several nights at the nearest homes, with Class 1 sound level meters holding current traceable laboratory calibration certificates, field-checked before and after each deployment.





