DCFR Insight 02 / Site Fit
Why Megawatts Alone Do Not Tell You If a Site Works
Megawatts become useful only when they are converted into racks, modules, building footprint, yards, access, buffers, and stormwater.
Problem: MW is not a site plan
A data center site is often marketed around a target power number: 20 MW, 40 MW, 100 MW, or more. That number is important, but it is not a site plan. MW must translate into IT load in kW, rack-density assumptions, estimated rack count, data hall module count, building footprint, electrical and transformer yards, generator yards, cooling or heat-rejection area, parking, loading, fire access, stormwater reserve, buffer zones, utility corridors, and expansion space before it can support an acquisition decision.
Why it matters before land acquisition
If a buyer prices land based on an attractive MW target before testing the physical site-fit logic, the deal can inherit hidden constraints. The parcel may be too narrow for the modules and support yards, the electrical yard may conflict with truck or fire access, the cooling yard may create sensitive-edge exposure, or stormwater may consume the only expansion zone. Planning-grade translation protects acquisition discipline by separating marketable capacity from capacity that can actually fit the parcel.
Planning-grade calculation logic
The early feasibility sequence should move from load to land. Convert MW to kW, divide by a planning-grade rack density, estimate rack count, group racks into data hall modules, apply a gross-up factor to translate the modules into a building footprint, and then add exterior systems. Facility load drives electrical and transformer yard planning; backup load drives generator yard planning; cooling load drives heat-rejection area; and hardscape drives stormwater reserve. These are early site-fit assumptions, not final engineering, but they make the land demand visible before the team relies on the MW number.
Concrete 40 MW example
A 40 MW program equals 40,000 kW. At 40 kW per rack, that implies approximately 1,000 racks. If each data hall module supports approximately 10 MW, the program becomes roughly four data hall modules. Those modules then require a building footprint, back-of-house support, electrical and transformer yard, generator yard, cooling or heat-rejection yard, parking, loading, fire/service access, stormwater reserve, buffers, and expansion allowance. The building footprint and exterior support yards must be tested against parcel geometry before the site can be called viable.
Confirmation required
Rack density, IT load, module strategy, redundancy, MEP system selection, cooling technology, utility capacity, transformer and generator layout, civil grading, stormwater criteria, fire access, acoustic exposure, and equipment clearances are assumptions until confirmed by the owner, utility, design team, vendors, AHJ, licensed consultants, and counsel where applicable.
CTA: use the DCFR report package before relying on MW claims
The DCFR report package is built to convert a target MW program into planning-grade site-fit outputs, DCFR flags, and confirmation-required items so brokers, developers, land teams, infrastructure investors, and site-selection teams can compare parcels before acquisition momentum hardens around an untested number.
MW-to-site-fit translation
| MW translation step | Planning question | DCFR output |
|---|---|---|
| MW to kW | What IT load is being screened? | Target load converted into kW for calculation. |
| kW to rack count | What rack-density assumption is being applied? | Estimated rack count with assumption clearly stated. |
| Racks to data hall modules | How many deployable modules does the rack count imply? | Approximate module count and planning block. |
| Modules to building footprint | Can the module block and back-of-house space fit the usable envelope? | Planning-grade building footprint and geometry test. |
| Facility load to electrical yard | Where do transformers, switchgear, utility interface, and replacement access go? | Electrical/transformer yard allowance and conflict flags. |
| Backup load to generator yard | Can backup generation, service clearances, fuel access, and acoustics fit? | Generator-yard allowance, service path, and sensitive-edge flags. |
| Cooling load to heat rejection area | Where does heat rejection sit without airflow, access, or noise conflicts? | Cooling-yard or heat-rejection allowance and adjacency flags. |
| Site hardscape to stormwater reserve | How much detention, water quality, conveyance, and grading reserve is needed? | Stormwater reserve carried before leftover space is consumed. |
Early screening checklist
What to verify before advancing this site.
- MW converted to kW and tied to IT-load assumptions
- Rack density, rack count, and module strategy stated
- Building footprint tested against parcel geometry
- Electrical, generator, cooling, utility, and expansion zones reserved
- Parking, loading, fire/service access, stormwater, and buffers included
- Confirmation-required register created before acquisition reliance
What DCFR would flag
Risks surfaced at the screening stage.
DCFR would flag oversized MW claims, unsupported rack-density assumptions, under-allocated support yards, weak circulation, stormwater pressure, utility-route conflicts, and total site demand that exceeds the usable envelope.
Professional confirmation required
Items requiring licensed validation.
MEP, utility, structural, civil, fire/AHJ, acoustic, vendor, owner program, survey, title, zoning, and legal assumptions require professional confirmation.
Final takeaway
A site is not viable because a target MW is attractive. It becomes viable only when the MW can be translated into a physical plan that fits the parcel, utility path, access system, and confirmation-required constraints.
Screen up to 20 candidate sites before selecting one for the full DCFR report.
Each DCFR Report Package includes a preliminary 20-site comparison PDF / export package plus one selected planning-grade feasibility report.