Data Centre Modelling Best Practices
Executive Summary
Key Takeaways
- ✓ Capacity should always be verified against the actual binding constraint, power, space, or cooling, before any revenue is projected, since revenue cannot exceed genuinely sellable capacity under whichever constraint binds first.
- ✓ Revenue should always be decomposed into separable drivers, occupancy, price, and density tier mix, so a reviewer or model owner can identify which driver is responsible for any given forecast change.
- ✓ Every material contract term should be traced to its source agreement, not summarised from memory, given how directly contract-specific provisions affect revenue durability in this sector.
- ✓ Governance should be built to survive personnel turnover, with documented ownership, event-driven update triggers, and reporting that surfaces sector-specific risk indicators, not just aggregate revenue and EBITDA.
Objective¶
This capstone guide synthesises the construction discipline that should govern any data centre financial model within Data Centre Financial Modelling, drawing together the individual disciplines covered throughout this pillar.
Verify Capacity Before Projecting Revenue¶
Capacity should always be verified against the actual binding constraint, power, space, or cooling, before any revenue is projected, since revenue cannot exceed genuinely sellable capacity under whichever constraint actually binds. See Data Centre Capacity Planning Models.
Decompose Revenue Into Separable Drivers¶
Revenue should always be decomposed into occupancy, price per unit of committed capacity, and density tier mix, so a reviewer or model owner can identify which driver is responsible for any given forecast change or variance, rather than working from a single blended rate that conceals the underlying dynamic. See Rack Revenue Models.
Trace Every Material Contract Term to Its Source¶
Every material contract term, escalators, renewal rates, SLA provisions, take-or-pay structure, should be traced directly to its source agreement, not summarised from memory, given how directly these provisions affect revenue durability. See Data Centre Model Documentation Standards.
Build Governance That Survives Personnel Turnover¶
Governance should be built with documented ownership, event-driven update triggers tied to capacity delivery milestones and contract renewal dates, and reporting that surfaces sector-specific risk indicators, capacity headroom, contracted revenue mix, tenant concentration, not just aggregate revenue and EBITDA. See Data Centre Model Governance Framework.
Test Both Structural Integrity and Assumption Reasonableness¶
A model should be both structurally audited, confirming formulas compute what they are represented to compute, and separately validated, confirming input assumptions are reasonable and well-sourced. Neither discipline substitutes for the other.
Bringing the Disciplines Together¶
These five disciplines are mutually reinforcing: verified capacity bounds what revenue can realistically be, decomposed revenue reveals which driver a capacity or market change actually affects, traced contract terms determine the durability of that revenue, and governance ensures the whole structure remains current and defensible as conditions change. See Common Data Centre Modelling Errors for the failure modes each discipline exists to prevent.
Continue Reading¶
Related Pillars¶
Related Technical Guides¶
How OXXON tests thisRun a free structural check with FMAE
Frequently Asked Questions
What is the purpose of this capstone guide?
To synthesise the individual construction disciplines covered throughout this pillar into a single, practical standard for building or reviewing a data centre financial model, rather than restating any one guide's detailed content.
What is the single most important capacity discipline?
Verifying capacity against the actual binding constraint, power, space, or cooling, before projecting any revenue, since a model that assumes floor space is the sole constraint can materially overstate achievable revenue as tenant rack density rises and a different constraint binds first.
What is the single most important revenue discipline?
Decomposing revenue into separable drivers, occupancy, price per unit, and density tier mix, so that a reviewer or model owner can identify which driver is responsible for any given forecast change or variance, rather than working from a single blended rate that conceals the underlying dynamic.
Why does contract traceability matter as much as capacity and revenue discipline?
Because data centre contracts carry specific provisions, SLA service credits, renewal options, escalators, take-or-pay structure, that materially affect revenue durability, and a model that summarises these terms from memory rather than tracing them to the source agreement risks a material, avoidable error.
References
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.
Rack Revenue Models
Rack revenue is the core billing unit of colocation data centre revenue, priced per rack, per kW of committed power, or a hybrid of the two, with premium pricing for higher-density racks. This guide sets out the mechanics of rack-based pricing, density tiering, and how to model power draw billing and contract escalation without conflating them into a single blended average rate per rack.
Data Centre Model Documentation Standards
A data centre financial model should maintain a documentation standard that traces capacity assumptions to their engineering or survey source, contract terms to the underlying agreements, and power cost pass-through methodology to the specific contractual mechanism it implements. This guide sets out the documentation practice that keeps a data centre model auditable and defensible as it is updated and handed over across successive reporting periods and personnel.
Data Centre Model Governance Framework
A data centre model governance framework assigns clear ownership for capacity, pricing, and contract assumptions, defines update triggers tied to capacity delivery milestones and contract renewal dates, and structures reporting so an investment committee or board can assess model risk consistently across successive reporting periods, surviving personnel turnover rather than depending on undocumented institutional knowledge.
Common Data Centre Modelling Errors
This capstone guide indexes the structural modelling errors that recur most frequently across data centre financial models, drawn from the capacity, revenue, contract, cost, and governance disciplines covered throughout this pillar. It is intended as a single reference point for identifying the specific mistake behind a data centre model finding, rather than a restatement of any individual guide's detailed content.