Data Centre Expansion Models
Executive Summary
Key Takeaways
- ✓ Data centre expansion adds incremental capacity to an already-operating facility, and should be modelled as an extension of the existing operating model rather than a standalone development project.
- ✓ Demand validation, evidence of existing tenant expansion requests or a documented market waitlist, should precede committed expansion capex, since building ahead of validated demand ties up capital in unsellable capacity.
- ✓ Expansion capex should be scheduled against the facility's existing power, space, and cooling constraint profile, since expansion is frequently limited by the same binding constraint already governing the base facility.
- ✓ Expansion construction should be modelled alongside the existing live operation, reflecting any temporary operational disruption or shared-infrastructure capacity constraint the expansion works may impose.
Objective¶
This guide sets out how to model an operational, brownfield expansion of an existing data centre within Data Centre Financial Modelling, distinct from a new greenfield development or acquisition.
Expansion as an Extension of the Existing Operating Model¶
Data centre expansion adds incremental capacity to an already-operating facility. The model should extend the existing facility's revenue base, cost structure, and financing rather than treat the expansion as a fully standalone project disconnected from current operations, since the expansion shares the base facility's tenant relationships, site infrastructure, and often its financing arrangements.
Demand Validation Before Committed Capex¶
Expansion capex should be preceded by demand validation: evidence of existing tenant expansion requests, a documented prospective tenant waitlist, or clear supporting market data, consistent with the net absorption discipline applied elsewhere in this pillar. Building expansion capacity ahead of validated demand ties up capital in unsellable capacity, the same risk that applies to a new facility's initial capacity delivery.
Scheduling Against the Existing Binding Constraint¶
Expansion is frequently limited by the same constraint, power, space, or cooling, already governing the base facility, particularly power availability in a constrained grid market. The expansion capex and delivery schedule should be tested against that same binding constraint, consistent with Data Centre Capacity Planning Models, rather than assumed unconstrained simply because it is an expansion of an existing site.
Construction Alongside a Live Operation¶
Expansion construction proceeds alongside a live, revenue-generating facility, and the model should reflect any resulting temporary operational disruption or shared-infrastructure capacity constraint, for example if expansion construction draws on the same power substation or cooling plant serving the existing operation, a risk a standalone greenfield development model does not need to capture.
Common Construction Pitfalls¶
Expansion modelled as a fully standalone project. Misses the shared tenant relationships, infrastructure, and financing connecting it to the existing operating facility.
Expansion capex committed without demand validation. Ties up capital in unsellable capacity ahead of confirmed tenant or market demand.
Expansion capacity schedule assumed unconstrained. Ignores the shared binding constraint, commonly power, already governing the base facility.
No allowance for shared-infrastructure disruption during construction. Understates operational risk to the existing live facility during the expansion build.
Recommended Practices¶
- Model expansion as an extension of the existing facility's operating model, not a standalone project.
- Require demand validation evidence before committing expansion capex.
- Test the expansion delivery schedule against the facility's existing binding constraint.
- Reflect any shared-infrastructure disruption risk to existing operations during expansion construction.
Continue Reading¶
Related Pillars¶
Related Technical Guides¶
Related Glossary¶
How OXXON tests thisRun a free structural check with FMAE
Frequently Asked Questions
How does data centre expansion modelling differ from a new development?
Expansion adds incremental capacity to an already-operating facility, so the model should extend the existing facility's operating model, revenue base, cost structure, and financing, rather than model the expansion as a fully standalone project disconnected from the base facility's current operations.
What demand validation should precede committed expansion capex?
Evidence of existing tenant expansion requests, a documented prospective tenant waitlist, or clear market data supporting the additional capacity, since building expansion capacity ahead of validated demand ties up capital in unsellable capacity, the same risk that applies to a new facility's initial capacity delivery.
Why does the existing facility's binding constraint matter to expansion planning?
Because expansion is frequently limited by the same constraint, power, space, or cooling, already governing the base facility, particularly power availability in a constrained grid market, and the expansion capex schedule should be tested against that same constraint rather than assumed unconstrained.
What operational risk does expansion construction pose to the existing facility?
Potential temporary operational disruption or a shared-infrastructure capacity constraint, for example if expansion construction draws on the same power substation or cooling plant serving the live facility, and the model should reflect any resulting temporary capacity limitation on existing operations.
Related Articles
Data Centre Financial Modelling
Data centre financial modelling is the discipline of modelling a data centre operator's revenue, cost, and capital structure from its capacity-denominated drivers, power, space, and cooling capacity, rack density, and tenant contract structure, rather than the generic market-price and headcount-growth drivers used in most corporate models, or the pure occupancy-and-lease-term drivers of conventional commercial real estate. This page is the hub for the Knowledge Centre's data centre financial modelling content: how colocation, hyperscale, and enterprise business models each require a distinct model architecture, how rack revenue and occupancy are decomposed into their separable underlying drivers, and how capacity planning and financial KPIs tie the model together, as this domain expands to cover operations, revenue, investment, and governance practice across the sector.
Data Centre Capacity Planning Models
Data centre capacity is jointly constrained by power, floor space, and cooling capability, and the binding constraint can shift as tenant rack density changes. This guide sets out how to model capacity planning across all three constraints simultaneously, how phased capacity delivery should be scheduled against demand, and why treating any single constraint as the sole capacity driver risks overstating achievable revenue.
Data Centre Occupancy & Utilisation Models
Data centre occupancy modelling requires distinguishing three related but distinct capacity states: billed (contracted) capacity, actually utilised capacity, and total available capacity. This guide sets out how to model each state and the ratios between them, and why conflating billed occupancy with actual utilisation misrepresents both revenue durability and the facility's true remaining capacity headroom.
Net Absorption (Data Centre)
Net absorption measures the net change in contracted data centre capacity over a given period, gross new bookings less capacity lost to tenant churn or downsizing. It is the standard metric used to assess genuine underlying demand growth in a market or portfolio, since a positive net absorption figure can still mask a high-churn, high-bookings-turnover portfolio if only the net figure is reported without its gross components.