Initial IT load
Target capacity for the first deployable stage.
For operators
An early requirement brief lets DataParks test the relationship between demand, location, timing and infrastructure before unnecessary decisions are locked in.
Operator capacity brief
This is a structured starting point, not a request for confidential design documents or a representation that a site or connection is available.
Target capacity for the first deployable stage.
The long-term load and expansion envelope.
Target date, staging assumptions and decision gates.
Preferred geography and any location constraints.
Redundancy, uptime and network expectations.
Route diversity, carrier access and connectivity needs.
Cooling approach, water and supporting utility assumptions.
Campus, powered land, powered shell or build-to-suit.
Ownership, lease, partnership or other delivery model.
Deployment sequence, modularity and future expansion.

Questions operators ask
Only where a pathway has been substantiated. Proximity to infrastructure does not establish capacity, timing or connection rights.
Yes. Starting with the operating requirement allows geography, infrastructure and staging to be tested before a location is treated as preferred.
Campus, powered land, powered shell, build-to-suit and partnership pathways can be assessed, subject to evidence and appointed delivery parties.
DataParks screens for a credible fit, agrees any confidentiality arrangements, then defines a proportionate diligence pathway.
Engagement sequence
Start early
DataParks can begin with a high-level brief and define the next information step only where there is a relevant fit.
Discuss a capacity requirement