Rack Revenue Models
Executive Summary
Key Takeaways
- ✓ Rack revenue should be modelled from committed power (kW) as the primary pricing basis, with the physical rack as the billing unit, since power, not the rack itself, is what a tenant is actually paying for.
- ✓ Higher-density racks command premium per-kW pricing given the additional cooling infrastructure required to support them, and density tiers should be modelled as distinct pricing bands rather than a single average rate.
- ✓ Metered power draw billing (where tenants pay for actual consumption above a committed baseline) should be modelled separately from the committed capacity charge, since the two respond to different tenant behaviour.
- ✓ A single blended average revenue per rack figure conceals the mix shift between low-density and high-density racks, which is a common source of forecast error as facilities upgrade toward higher density.
Objective¶
This guide sets out how to model rack revenue mechanics within Data Centre Financial Modelling, the core billing unit for colocation revenue.
Power as the Primary Pricing Basis¶
Colocation pricing is typically anchored to committed power per rack (kW), not the physical rack unit itself, since power availability is the resource actually being sold and constrained. A model that prices a fixed number of racks at a flat rate regardless of committed power understates the revenue value of higher-density capacity and cannot correctly reflect the premium pricing higher-density racks command.
Density Tiers as Distinct Pricing Bands¶
Higher-density racks require proportionally more cooling infrastructure and consume a larger share of the facility's overall power and cooling capacity, so operators typically price higher committed-kW density tiers at a premium per-kW rate relative to standard-density racks. The model should define distinct density tiers (for example, standard, high-density, and ultra-high-density bands), each with its own per-kW rate, rather than a single average rate applied across all racks regardless of density.
Metered Power Draw Billing¶
Some contracts include a metered billing component, where the tenant pays for actual power consumption above a committed baseline, or is billed on a true-up basis against actual draw. This should be modelled as a distinct revenue line responding to tenant utilisation behaviour, separate from the committed capacity charge, which is contractually fixed and does not vary with actual draw.
Contract Escalation¶
Multi-year rack and power contracts typically include a fixed annual escalator applied to the existing contracted base. This escalator should be applied to the existing base separately from the pricing assumption used for new bookings, consistent with the practice described in Colocation Financial Models.
Avoiding the Blended Average Rate Trap¶
A single blended average revenue per rack figure conceals the mix shift between low-density and high-density racks. As a facility's tenant base shifts toward higher-density racks over time, whether through new bookings or existing tenant upgrades, average revenue per rack should rise even without any underlying change in per-kW pricing, and a model that tracks only the blended average can misattribute this mix-driven increase to pricing power that does not actually exist. Occupancy and pricing should be modelled together, by density tier, rather than as a single occupancy percentage applied to a flat rack price. See Data Centre Occupancy & Utilisation Models.
Common Construction Pitfalls¶
Flat per-rack pricing regardless of committed power. Understates the revenue value of higher-density capacity and misprices density upgrades.
No distinct density tier pricing bands. Prevents the model from reflecting the premium pricing higher-density racks actually command.
Metered draw billing blended into the committed capacity charge. Obscures the revenue impact of tenant utilisation behaviour separate from contracted commitments.
Blended average revenue per rack used as the sole reporting metric. Conceals density mix shift and can misattribute mix-driven revenue changes to pricing power.
Recommended Practices¶
- Price from committed power (kW) per rack as the primary basis, not a flat per-rack rate.
- Define distinct density tier pricing bands rather than a single average rate.
- Model metered power draw billing as a distinct line from the committed capacity charge.
- Track occupancy and revenue by density tier, not as a single blended average rate.
Continue Reading¶
Related Pillars¶
Related Technical Guides¶
Related Glossary¶
How OXXON tests thisRun a free structural check with FMAE
Frequently Asked Questions
What is the typical basis for colocation rack pricing?
Most colocation pricing is based on committed power (kW) per rack, since power availability, not the physical rack itself, is what actually constrains and is being paid for. A fixed number of racks priced at a flat rate regardless of power draw understates the value of higher-density capacity.
Why do higher-density racks command premium pricing?
Because supporting a higher-density rack requires proportionally more cooling infrastructure and consumes a larger share of the facility's overall power and cooling capacity, so operators typically price higher committed-kW racks at a premium per-kW rate relative to lower-density racks.
How should metered power draw billing be modelled separately from committed capacity charges?
As a distinct revenue line reflecting actual consumption above (or true-up against) a committed baseline, since metered billing responds to tenant utilisation behaviour while the committed capacity charge is contractually fixed regardless of actual draw.
What is the risk of using a single blended average revenue per rack figure?
It conceals the mix shift between low-density and high-density racks. As a facility's tenant base shifts toward higher-density racks, average revenue per rack should rise even without any change in the facility's fundamental pricing, and a model that does not track density mix separately can misattribute this shift to pricing power that does not actually exist.
How does rack revenue modelling connect to occupancy modelling?
Rack revenue is the pricing side of the equation; occupancy modelling determines how many racks (and at what density) are actually contracted. The two should be modelled together, occupancy by density tier multiplied by the corresponding tier's per-kW rate, rather than a single occupancy percentage applied to a flat rack price.
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.
Colocation Financial Models
Colocation financial models project revenue from a diversified base of tenants leasing space and power in defined units, per rack or per kW of committed capacity, rather than a single anchor contract. This guide sets out how colocation revenue is decomposed into space/power revenue, cross-connect and ancillary fees, and how occupancy, pricing, and churn assumptions should be modelled as separable drivers rather than a single blended revenue-per-tenant figure.
Rack Density
Rack density measures how much power a tenant's rack draws, expressed in kW per rack, and by extension how much heat must be removed by the facility's cooling system to support it. Rising rack density, driven by higher-performance computing equipment, is the primary reason power and cooling capacity, rather than floor space, increasingly bind data centre capacity before floor space is exhausted, and density tier is a primary basis for colocation pricing.
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.