Frederick, Howard, Prince George's, Anne Arundel, and Western Maryland all raise distinct siting questions
Power demand, grid upgrades, and rate impacts need review beyond a single project boundary
Cooling demand, water source, and infrastructure cost vary by county and watershed
Maryland sits between the mature Northern Virginia data center market and the next wave of Mid-Atlantic siting decisions. That makes the state a pressure point: projects can bring tax base and infrastructure investment, but they also create hard questions about electricity load, water use, air permits, land conversion, and community trust.
A statewide page is the right starting point because no single county should define the LSARS position. The same review model can apply in Frederick, Howard, Prince George's, Anne Arundel, or Western Maryland without attaching LSARS to any one contested local moment.
The core questions are consistent: how much power the project needs, where the water comes from, what backup generators emit, how far sound travels, what roads carry construction traffic, and what benefits were promised after approval. Those are not advocacy questions. They are the measurements needed for a complete public record.
LSARS frames those measurements the same way for every reader. A neighbor can see what is being weighed. A council member can see what is missing before a vote. A developer can submit a complete record without asking the community to trust a private summary.
Maryland data center review should treat utility capacity as a public issue, not a footnote. Electricity load can require transmission upgrades, new substations, and cost allocation decisions. Water demand depends on cooling technology, reuse plans, local utility capacity, and drought planning.
A project-neutral review connects those disclosures to the local service area and makes clear what is known, what is estimated, and what has not yet been filed.
Backup generators are the main air-permit issue for most data center campuses. Reviewers need generator counts, runtime assumptions, emission factors, stack assumptions, and proximity to schools, hospitals, homes, and other sensitive receptors. The useful question is not whether a project is scary. It is what the modeled contribution is and who is close enough to be affected.
LSARS keeps the calculation trail visible so the applicant, regulator, and public can all see how the result was produced.
Independent analysis. Same numbers for every reader.
Drawn from public regulatory filings, utility commission proceedings, and operator environmental reports. Methodology is published and reproducible.
Read the full methodologyQuestions we hear
Project-neutral questions for Maryland officials, applicants, and communities evaluating data center proposals.
Maryland data center interest is not limited to one county. Frederick, Howard, Prince George's, Anne Arundel, and Western Maryland each raise different questions about power access, water sourcing, land use, tax base, transportation, and proximity to communities. LSARS treats those as state-market questions first, then drills into project-specific data only when a local record is available.
Virginia already has a mature data center market with years of infrastructure, tax policy, and community history. Maryland is earlier in the cycle. That means the most important decisions are still being made: where projects fit, what information should be disclosed before votes, how utility costs are allocated, and what community commitments should be tracked after approval.
Officials should ask for disclosed electricity load, water source and daily consumption, backup generator emissions, noise modeling, school and sensitive receptor proximity, traffic impacts, and a public commitment tracker. The point is not to assume a project is good or bad. The point is to make the record complete before the decision.
Water risk depends on cooling technology, whether potable or reclaimed water is used, drought planning, and how infrastructure costs are allocated. A Maryland review should compare project demand against local utility capacity and regional watershed constraints instead of relying on generic national averages.
The primary air question is cumulative emissions from backup diesel generators, especially nitrogen oxides and particulate matter from testing or outage operations. Maryland projects may also sit in air-quality planning areas that require closer review. A useful analysis connects generator assumptions, emissions, nearby populations, and sensitive receptors in one public record.
Use the same independent measurements for the applicant, council, and community. Submit a complete technical record with the application, publish the community-facing dashboard at the same time, and track commitments after approval. That keeps the conversation on disclosed facts instead of competing talking points.
Project-specific load, emissions, water sourcing, noise modeling, and community commitments belong in one public record before the decision.
See the officials page