Site & Campus Constraints

What this screen is for

A data center design can look coherent inside the building and still depend on a site that cannot deliver its first electrical phase, ultimate expansion, diverse communications, water allocation, backup-fuel access, land envelope, noise boundary, hazard mitigation or permit path. This educational screen keeps those external dependencies visible as ten separate constraint axes. It does not collapse them into a weighted site score, rank locations or hide missing evidence behind a reassuring average.

The starting values and three presets are illustrative teaching assumptions, not claims about a real market or parcel. Replace them with a documented project brief when you have one. A blank optional field remains unknown. Zero is treated as an entered value where it can be meaningful, such as an intentionally dry annual-water estimate, rather than being silently converted to missing data.

• Keep utility, carrier, water, fuel, land, noise, hazard and permit evidence as separate constraints
• Stress one external dependency at a time without manufacturing a site score or preferred location
• Save a reproducible site-screen dossier that preserves unknowns, boundaries and unresolved verification work

Power, routes, resources and evidence

The power layer compares phase-one demand with entered firm utility capacity and keeps ultimate demand separate so a workable opening phase cannot disguise an expansion shortfall. Target-ready and utility-delivery months are compared directly, while the permit path remains an independent categorical state. The routes layer checks carrier entrance count, declared physical route diversity, stored fuel runtime and fuel-delivery route count. It does not infer diverse ducts, substations, roads or suppliers from a number alone.

The resources layer compares entered water demand with an entered allocation, available site area with an entered requirement, and predicted boundary noise with an entered limit. The evidence layer records flood, seismic, wind or wildfire, and industrial-neighbor screens as unknown, screened clear, mitigation required or exclusion. Those labels are evidence states, not probabilities or engineering conclusions. An exclusion takes precedence over mitigation, which takes precedence over unknown, without creating a synthetic hazard index.

Dependency drills and the campus boundary

A deterministic stress drill changes only one selected external dependency: utility capacity, one carrier route, water allocation or one fuel route. The reduction percentage is an assumption for the drill, not an event probability. A layered campus schematic then traces utility, carrier, water, fuel, land and evidence connections to the entered campus boundary. Each lane reports within entered boundary, dependency, outside entered boundary or unknown. The constraint register shows the exact comparison and the next verification step for every axis.

This separation matters. Unknown is not a failure, and within an entered boundary is not proof that the boundary is correct. A carrier count does not prove route separation; a water allocation does not prove entitlement or pressure; stored fuel hours do not prove resupply; a land-area comparison does not prove geometry, geotechnical suitability or constructability.

Versioned dossier and limitations

You can save a named version in browser-local storage, reopen it from Design Pro, and export Markdown or JSON. The frozen dossier records the normalized inputs, selected stress event, ten constraint states, connection states, unresolved register, model version and scope boundaries. It deliberately contains no winner, recommendation or aggregate score.

This model is not a geographic information system, site-selection service, utility study, carrier-route survey, water-rights assessment, fuel logistics plan, acoustic study, hazard analysis, environmental review, permit opinion, cost estimate or construction schedule. It includes no regional facts, live provider data, weather probabilities or authority decisions. Real due diligence requires surveyed parcel and route evidence, provider studies, current jurisdiction requirements, qualified engineering and project-specific commercial review. Save and compare site-screen versions in Design Pro or continue through the system Playbook.