Data Center Model Ordinance

The Southeastern PA Data Center Community Protection Team has developed some materials that build on templates and guidance from other organizations to create a toolkit for local governments to defend against the challenges we face from the boom of data center proposals in our area.

 

Don't count on Pennsylvania legislation or a possible moratorium to buy us time. Local governments need to take proactive action by passing local ordinances ASAP.

 

For Municipal Officials

Ver 7.2 Release Notes

What is new in this consolidated version

- v7.2 restored non-regression protections from the original model, including AERMOD/EPA-
preferred modeling, the 2,000-foot stack-to-Sensitive-Receptor modeling trigger, output-based NOx and PM limits, methane LDAR, Chapter 94 overload protection, QRA thermal-radiation thresholds,
public annual summaries, and telemetered monitoring.

- v7.2 restored and strengthened transparency, public-record, no-blanket-NDA, protective-order,
public-study, annual-reporting, audit, Right-to-Know, and Sunshine Act safeguards.

- v7.2 added gas infrastructure and pipeline-impact disclosure, associated-energy-infrastructure
anti-segmentation, gas-specific emergency response, methane inventory, intergovernmental notice,
and material-change triggers for new or expanded gas infrastructure.

- v7.2 added SCR, ammonia slip, reagent storage, secondary pollutant, stack testing, SCR bypass,
catalyst degradation, spent catalyst, and monitoring safeguards.

- v7.2 added this reader orientation and a master revision-history cross-reference so first-time
readers understand the package structure and version sequence.

- v7.2 strengthens cooling and water-resource protections by requiring true non-evaporative closed-
loop cooling for primary IT cooling and facility heat rejection; prohibiting evaporative cooling, cooling towers, open-loop/once-through cooling, adiabatic/wet-assist operation, routine cooling-water withdrawal from any source, and cooling blowdown; and adding a zero routine cooling-water demonstration.

- v7.2 clarifies checklist language regarding aggregation/anti-evasion and strengthens
applicant/operator-funded study, reporting, peer-review, and monitoring language, subject to
adopted fee schedules, escrow procedures, itemized billing, and applicable fee-dispute rights.

- v7.2 adds turbine-specific and behind-the-meter generation controls, including strict treatment of
simple-cycle/aeroderivative turbines, prohibition of water-consuming CCGT/HRSG/steam-cycle
configurations, turbine inlet cooling/wet-compression/fogging restrictions, startup/shutdown/ramping modeling, turbine-specific noise review, continuous or parametric monitoring, and explicit aggregation of redundant, black-start, bridge-power, mobile, rental, future-pad, and adjacent/affiliate-owned generation.

- v7.2 added the state/federal permit backstop, ozone nonattainment explanation, and closed-loop
coolant/chemical management requirements.

- v7.2 clarified citizen-facing materials by explaining municipal versus
county/state/federal/basin/sewer/water-authority/utility roles and simplifying selected anti-evasion,
scenario, and public-hearing language. It did not change operative ordinance standards.

- v7.2 clarifies ongoing compliance verification, annual municipal compliance review, operator-
funded monitoring/inspection/third-party review, remedies for violations, and the principle that approval is not a one-time event. The update preserves lawful fee/escrow guardrails: reasonable and necessary costs, adopted fee schedules, itemized billing, and applicable dispute procedures.

- v7.1 added a Project / Common Plan of Development concept, strengthened Unified Development
aggregation, and added anti-segmentation certification language to address separate parcels, separate
tenants, separate meters, affiliates, phased applications, and common infrastructure structures.

 - v7.2 added Cumulative Impact Review Area, Cumulative Source, Receiving Environment, and Concurrent
or Pending Application provisions so genuinely separate nearby LLDC applications are reviewed for
combined effects on the same neighboring communities without incorrectly treating unrelated applicants as
one project.

- v7.2 added no-first-in-time entitlement, coordinated technical-review, common receptor/modeling protocol,
and solicitor scenario-playbook provisions for same-day, pending, approved-but-unbuilt, and operating
nearby data-center scenarios.

For Solicitors / Technical Review

Find more resources for concerned residents and activists HERE


 A strong ordinance does not ban data centers; it requires responsible siting, objective standards, and proof of compliance. Large fossil-fueled generation serving a data center has separate impacts and should be reviewed as a separate land use.

CONTACT INFO

To ask a question or learn how you can contribute to the Data Center team, use the SPG Volunteer Interest Form. A volunteer leader will get back to you.

Happy to Help Municipal Officials

Want help analyzing your data center ordinance? Or assess your exposure to the risks that a new data center proposal might bring based on the ordinances currently on the books? Or want to learn about our process? We can help! All analysis is confidential and free. Contact us with the SPG Volunteer Interest Form.