Common Data Centre Modelling Errors
Executive Summary
Key Takeaways
- ✓ The most consequential recurring data centre modelling errors cluster around capacity constraint tracking, revenue driver decomposition, contract term treatment, and power cost pass-through, each covered in depth elsewhere in this pillar.
- ✓ Capacity errors typically involve tracking floor space alone rather than the actual binding constraint among power, space, and cooling, overstating achievable revenue.
- ✓ Revenue errors typically involve a single blended rate that conceals whether occupancy, pricing, or density mix is driving a change, or confusing billed capacity with actual utilisation under a take-or-pay contract.
- ✓ Contract and power cost errors typically involve ignoring SLA service credit exposure, assuming a market-rate renewal despite a tenant-favourable option, or applying a simplified power cost pass-through assumption that does not match the actual contractual allocation.
Objective¶
This capstone guide indexes the structural modelling errors that recur most frequently across data centre financial models within Data Centre Financial Modelling, as a single reference point rather than a restatement of any individual guide's detailed content.
Capacity Constraint Errors¶
Floor-space-only capacity tracking. Overstates achievable revenue where power or cooling actually binds first, particularly as tenant rack density rises. See Data Centre Capacity Planning Models.
Capacity delivery scheduled to a single completion date. Ignores intermediate demand and either constrains near-term growth or over-builds ahead of contracted leasing.
Revenue Decomposition Errors¶
Single blended revenue rate per rack. Conceals whether occupancy, price, or density tier mix is actually driving a change. See Rack Revenue Models.
Billed capacity conflated with actual utilisation. Understates revenue durability under a take-or-pay contract structure. See Data Centre Occupancy & Utilisation Models.
Net occupancy growth without separate gross bookings and churn. Conceals the underlying retention dynamic driving the forecast.
Contract and Power Cost Errors¶
SLA service credit exposure ignored. Overstates revenue by assuming perfect service level performance with no contingent deduction. See Data Centre Customer Contract Models.
Market-rate renewal assumed despite a tenant-favourable pre-agreed renewal option. Overstates achievable re-pricing at contract expiry.
Power cost pass-through modelled as a simplified default. Misstates cost exposure where the actual contractual allocation differs from the simplified assumption. See Data Centre Power Consumption Models.
Investment and Governance Errors¶
Terminal value assuming indefinite continuation of current favourable contract terms. Overstates valuation where re-contracting at the horizon is unlikely to match current terms.
Tenant concentration risk folded into a generic churn assumption. Understates the concentrated, contract-specific risk in hyperscale-anchored facilities.
Capacity claims documented without engineering or survey traceability. Prevents independent verification of a claim that directly determines achievable revenue.
How to Use This Index¶
Use this index to identify which detailed guide in this pillar addresses a specific error encountered during a model review, build, or audit, then consult that guide for the full modelling discipline required to correct it. See Data Centre Modelling Best Practices for the constructive counterpart to this error index.
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 index, in one place, the structural modelling errors that recur most frequently across data centre financial models, so a reviewer or model developer can quickly identify which detailed guide in this pillar addresses a specific error they have encountered, rather than searching across the pillar's individual technical guides.
What is the most common capacity-related error?
Tracking floor space as the sole capacity constraint rather than the actual binding constraint among power, space, and cooling, which overstates achievable revenue where power or cooling in fact binds first, particularly as tenant rack density rises. See Data Centre Capacity Planning Models.
What is the most common revenue-related error?
Modelling revenue as a single blended rate that conceals whether occupancy, pricing, or density tier mix is actually driving a change, or conflating billed (contracted) capacity with actual utilisation under a take-or-pay contract structure. See Rack Revenue Models and Data Centre Occupancy & Utilisation Models.
What is the most common contract and power cost related error?
Ignoring SLA service credit exposure, assuming a market-rate contract renewal despite a tenant-favourable pre-agreed renewal option, or applying a simplified power cost pass-through assumption that does not match the actual contractual allocation between tenant and operator. See Data Centre Customer Contract Models and Data Centre Power Consumption Models.
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 Customer Contract Models
Data centre customer contracts carry specific structural provisions, SLA-linked service credits, renewal options, fixed annual escalators, and early termination rights, that materially affect revenue durability and should be modelled explicitly rather than assumed away in a simplified revenue growth curve. This guide sets out how to model each provision's financial effect and why contract-level detail matters more in this sector than in a generic subscription revenue model.
Data Centre Power Consumption Models
Power consumption modelling forecasts a data centre's actual electricity draw and cost, distinct from the capacity planning discipline that governs how much power can be sold. This guide sets out how to model load factor, utility tariff structure (demand charges versus consumption charges), and the distinction between contracted and actual power draw, since power is typically the largest single operating cost category in this sector.
Data Centre Modelling Best Practices
This capstone guide synthesises the construction discipline that should govern any data centre financial model: verify capacity against the actual binding constraint before projecting revenue, decompose revenue into separable drivers, trace every material contract term to its source agreement, and build governance that survives personnel turnover. It draws together the individual disciplines covered throughout this pillar into a single, practical construction standard.