Enterprise Data Centre Models
Executive Summary
Key Takeaways
- ✓ An enterprise/captive data centre should be modelled as an internal cost centre with chargeback to business units, not as an external revenue-generating asset, since there is no third-party tenant revenue.
- ✓ Chargeback should be allocated on a basis that reflects actual consumption, typically power draw or allocated rack space, rather than a flat headcount or revenue-based allocation that misrepresents which business unit is actually driving facility cost.
- ✓ The build-versus-colocate-versus-cloud decision should be modelled on a total cost of ownership basis over a consistent time horizon and capacity assumption, not a simple capex-versus-opex comparison.
- ✓ Utilisation efficiency, since there is no external revenue signal disciplining capacity investment, is a more important governance control in an enterprise data centre model than in a commercial operator's model.
Objective¶
This guide sets out how to model an enterprise, or captive, data centre within Data Centre Financial Modelling, as an internal cost centre rather than an external revenue-generating asset.
Cost Centre Framing¶
An enterprise/captive data centre serves an organisation's own internal IT needs and has no third-party tenant revenue. The model's objective should accordingly be framed around cost efficiency and internal capital allocation discipline, total cost per unit of IT capacity delivered, rather than revenue maximisation, which distinguishes this business model from the colocation and hyperscale models covered elsewhere in this pillar.
Chargeback Mechanics¶
Facility cost, power, cooling, space, and shared infrastructure depreciation, should be allocated to consuming business units through a chargeback mechanism based on actual consumption, typically metered power draw or allocated rack/floor space, rather than a flat headcount or revenue-based allocation. A consumption-based chargeback correctly attributes cost to the business unit actually driving facility demand and creates an internal incentive for efficient capacity use. See Data Centre Operating Cost Models for the underlying cost category decomposition this chargeback allocates.
The Build-Versus-Colocate-Versus-Cloud Decision¶
Enterprise IT capacity investment increasingly involves an explicit choice between three paths: building and operating a proprietary facility, leasing colocation capacity from a third-party operator, or migrating workloads to public cloud infrastructure. This decision should be modelled on a total cost of ownership basis, capital cost, operating cost, refresh and migration cost, over a consistent time horizon and capacity assumption across all three options, not a simplified capex-versus-opex comparison that can bias the decision toward whichever option's cost structure the simplified comparison happens to favour.
Utilisation Efficiency as a Governance Control¶
A commercial operator's capacity investment is disciplined by an external revenue signal: occupancy and achievable pricing constrain how much capacity is actually worth building. An enterprise/captive facility has no such external signal, so utilisation efficiency tracking, actual power and space consumption against built capacity, is a more important internal governance control against over-building capacity than in a commercial operator's model. See Data Centre Occupancy & Utilisation Models.
Common Construction Pitfalls¶
Chargeback allocated by headcount or revenue rather than actual consumption. Misrepresents which business unit is actually driving facility cost and removes the incentive for efficient capacity use.
Build-versus-colocate-versus-cloud compared on a simple capex-versus-opex basis. Ignores operating cost, refresh cycles, and migration cost, biasing the comparison toward whichever option the simplified framing favours.
No utilisation efficiency tracking. Without an external revenue signal, an enterprise facility can accumulate significant unused, sunk capacity investment without an internal metric surfacing the inefficiency.
Recommended Practices¶
- Frame the model around cost efficiency and internal capital allocation, not revenue maximisation.
- Allocate chargeback on metered power draw or allocated space, not headcount or revenue.
- Model the build-versus-colocate-versus-cloud decision on a consistent total cost of ownership basis.
- Track utilisation efficiency as an explicit internal governance metric.
Continue Reading¶
Related Pillars¶
Related Technical Guides¶
How OXXON tests thisRun a free structural check with FMAE
Frequently Asked Questions
How does an enterprise data centre model differ from a commercial operator's model?
A commercial operator's model projects external tenant revenue against operating and capital cost. An enterprise/captive data centre has no third-party tenant revenue, so it should be modelled as an internal cost centre, with the objective of cost efficiency and internal capital allocation discipline rather than revenue maximisation.
How should chargeback be allocated to business units?
On a basis that reflects actual consumption, typically power draw or allocated rack/floor space, so that the business unit actually consuming the most facility capacity bears the corresponding cost. A flat headcount or revenue-based allocation misrepresents which unit is driving facility cost.
What is the build-versus-colocate-versus-cloud decision, and how should it be modelled?
The choice between building and operating a proprietary facility, leasing colocation capacity from a third-party operator, or migrating workloads to public cloud infrastructure. It should be modelled on a total cost of ownership basis over a consistent time horizon and capacity assumption across all three options, not a simple capex-versus-opex comparison that ignores operating cost, refresh cycles, or migration cost.
Why does utilisation efficiency matter more in an enterprise model than a commercial operator's model?
Because a commercial operator has an external revenue signal, occupancy and pricing, disciplining capacity investment decisions. An enterprise/captive facility has no such signal, so utilisation efficiency tracking is a more important internal governance control against over-building capacity.
Can an enterprise data centre model include a notional revenue or return calculation?
Some organisations calculate a notional internal rate of return by comparing chargeback revenue against cost, useful for capital allocation benchmarking, but this notional return should not be treated as equivalent to a commercial operator's actual external revenue and market-tested pricing.
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 Business Models
Data centre operators run under several structurally different business models, wholesale colocation, retail colocation, hyperscale build-to-suit, enterprise/captive, and managed services, each of which ties revenue, contract tenor, and capital intensity to a different mechanism. This guide sets out how each business model's revenue and cost mechanism differs and, correspondingly, how the financial model architecture appropriate to each differs, since applying a retail colocation-style model to a hyperscale build-to-suit facility, or vice versa, misrepresents the operator's actual revenue and risk exposure.
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 Operating Cost Models
A data centre operating cost model should separate power, cooling, maintenance, staffing, security, and insurance into distinct, activity-linked cost categories rather than a single blended operating cost percentage of revenue. This guide sets out the full operating cost structure, how each category's driver differs, and why a blended cost assumption conceals which category is actually responsible for a margin change.