---
title: "Data Center Power Capacity: Read the Megawatts Behind a Site Claim"
description: "Leviathan Systems — Technical content Published 2026-10-15; updated 2026-10-20."
canonical: "https://www.leviathansystems.co/articles/data-center-power-capacity-claims"
last-updated: "2026-10-20"
---

# Data Center Power Capacity: Read the Megawatts Behind a Site Claim

Leviathan Systems — Technical content
Published 2026-10-15; updated 2026-10-20.

A data-center capacity claim needs a boundary and date: which campus or phase, utility supply or IT load, planned or operating state, and capacity available to which customer. A large MW figure does not by itself establish power for your equipment or an installation start date. Ask for the evidence behind each part of the claim.

## Attach a boundary to every megawatt figure

A site presentation may quote ultimate campus scale while a delivery schedule refers to one building. A facility figure can include supporting infrastructure, while a tenant offer may describe IT allocation. Retain the source’s definitions and phase boundaries; do not silently convert every number into GPU capacity.

For a comparison, place the location/phase, named quantity, unit, status, as-of date and evidence reference on the same row. If the source does not identify facility supply versus IT load, mark that boundary unresolved. The headline’s largest number should not become the default installation assumption.

## Distinguish an early power plan from delivered service

Dominion Energy’s Virginia guidance describes site-specific power plans and staged service, including an initial bridging arrangement while a final power plan is constructed. This utility example shows why initial delivery and ultimate loading can differ. It is not a universal timetable or evidence that a particular project has secured service.

Request the applicable utility and facility records through the authorized project team. Identify the delivery stage, dependencies, responsible owner and date basis. Qualified utility/electrical reviewers must assess technical commitments; appropriate commercial/legal reviewers must assess contractual language. Public guidance cannot establish an executed agreement.

References: [U1](https://www.dominionenergy.com/virginia/large-business-services/data-center-requests)

## Compare a hypothetical campus, phase and tenant allocation

Consider three claims in an illustrative project pack. They concern the same location but different boundaries. They must not be added together, ranked as interchangeable offers or used to infer an installation date.

Illustrative capacity claims that cannot be added together
| Claim in the project pack | Boundary and status | Unresolved question | Source |
| --- | --- | --- | --- |
| 200MW campus potential | Ultimate plan; supply/IT definition absent | What stages, approvals and delivery evidence support the future figure? | Planning analysis |
| 20MW first-phase facility target | One phase; facility boundary; future target | Which delivery stage and facility acceptance support the proposed date? | Planning analysis |
| 6MW tenant IT allocation | Allocation described in a hypothetical offer | When and under what actual conditions is it available to this tenant? | Planning analysis |
Fictional figures and documents. No actual site, offer, contract, utility capacity or engineering design is represented.

## Keep power, energy and efficiency in their own units

MW describes a rate of electrical power. MWh describes energy accumulated over an interval. Annual energy cannot be compared directly with an instantaneous power rating; the time basis and operating profile matter. A generator nameplate, utility supply reference and IT allocation also need their own boundaries.

The US Department of Energy describes annual PUE as total facility energy divided by IT-equipment energy. In a hypothetical annual record, 12GWh divided by 10GWh gives 1.2. That ratio does not identify which rack can receive another load today. It supplies neither a capacity allocation nor proof that dividing a proposed facility MW figure by 1.2 approves new IT equipment.

References: [G1](https://www.energy.gov/cmei/femp/cooling-water-efficiency-opportunities-federal-data-centers)

## Ask whether capacity is available to this customer

An operating data center may have already allocated capacity, an incomplete delivery stage or a product that does not match the customer’s needs. Ask the operator to identify the offered space and IT allocation, availability basis, applicable configuration and outstanding prerequisites. A site-wide statistic does not establish saleable capacity.

Separate the requested installation window from facility delivery and customer access. Even with a confirmed allocation, equipment compatibility, cooling provision, rack geometry, pathways and authorized work conditions need their own responsible review. A power milestone should close its specific question instead of becoming a blanket site-ready label.

## Read location, land and deliverable service as different propositions

A transmission line visible beside a parcel establishes a geographical observation. It does not identify the service connection, the infrastructure needed for the proposed load, the customer allocation or the date those arrangements can support that load. A map is useful for locating a question; it cannot answer the project's capacity question by itself.

Dominion Energy's Virginia FAQ says proximity to existing transmission lines and substations can shorten delivery time, while describing site-specific power plans, staged service and dependencies including rights of way, permits, materials and regulatory filings. This is one utility's account, not a national connection rule or a promised timetable. The relevant distinction is potential advantage versus a project-specific service plan.

Treat 'powered land' as a heading to unpack, rather than a self-defining quantity. Does the description concern a parcel near infrastructure, a preliminary utility plan, a defined delivery stage, or an allocation for a particular customer? Ask the seller or operator which meaning is intended and retain the supporting source. Land status, a service plan and customer-available power are separate propositions even when a sales document puts them on the same page.

The next decision is specific: identify the utility or facility owner who can return the applicable service boundary, load basis, stage and outstanding dependencies. Do not substitute a nearby line, a preliminary letter or an ultimate campus figure for that return. This article does not interpret land rights, utility commitments or an executed contract.

References: [U2](https://www.dominionenergy.com/virginia/large-business-services/data-center-requests)

## Follow a service delay through one installation dependency

A service delay affects the installation schedule through the work that depends on that service stage. It need not change every project activity by the same amount. Distinguish a requested work date, a predecessor forecast and an authorized release; none is interchangeable with the others.

EX-PW149 is a fictional eight-rack project in two four-rack groups. Its planning sheet originally places a facility service-stage return in week 8 and requests a dependent work window in week 10. The facility owner now forecasts the same stage in week 12. The forecast has moved four weeks; week 10 is two weeks earlier than the revised predecessor. That arithmetic exposes a dependency conflict. It does not prove a new week-12 start, a two-week project delay or that any physical work may proceed.

The project coordinator returns the affected activity and date assumption to its named decision owner. An equipment-inventory reconciliation may be separable from the service-stage dependency; the released physical workfront, energization, technical verification and customer acceptance each require their own applicable conditions. Keep unaffected documentary work distinct without inventing an alternative site method, temporary supply or permission to bypass the predecessor.

EX-PW149: one forecast change and distinct planning returns
| Planning item | Fictional information now available | Required coordination decision | Source |
| --- | --- | --- | --- |
| Facility service-stage predecessor | Forecast changes from week 8 to week 12 | Facility owner identifies the revised stage, basis and unresolved dependencies. | Planning analysis |
| Requested dependent work window | Week 10 remains on the customer planning sheet | Schedule owner resolves the conflict; no automatically approved replacement date. | Planning analysis |
| Equipment reconciliation for groups A and B | Eight rack identities, four in each group, are available for document review | Scope owner decides which documentary outputs can be completed independently. | Planning analysis |
| Physical workfront and subsequent acceptance | No new authorized release or acceptance return is stipulated | Responsible owners retain these decisions; a forecast does not supply them. | Planning analysis |
Entirely fictional weeks, populations and records. No duration estimate, staffing plan, actual utility delivery, electrical or installation instruction, work authorization or result is represented.

## Compare customer allocation with technical delivery without merging them

'Contracted' and 'technically available' should not be used as synonyms. A customer allocation description concerns the capacity and conditions associated with that customer. A technical delivery description concerns a specified infrastructure boundary and state. Neither description establishes the other merely because both use MW. Agreement-specific meaning and enforceability remain with the appropriate commercial and legal reviewers.

Consider fictional records CP-A and CP-T. CP-A describes a 1 MW tenant IT allocation, with its delivery conditions still to be confirmed. CP-T describes a 2 MW facility delivery stage, without identifying the tenant allocation or whether its measurement boundary is IT load. The larger number does not double this customer's allocation. The smaller number does not prove that its conditions are satisfied. The figures cannot be subtracted to advertise 1 MW spare for another customer because the boundaries and allocation state have not been reconciled.

Ask the operator for a matched customer-specific return: the offered allocation, technical boundary, applicable delivery stage and outstanding conditions, with an as-of date. Record which party owns the contractual interpretation and which owns the technical status. A physical IT scope can then refer to confirmed inputs while leaving unresolved facility and commercial decisions visible. No example here supplies a capacity offer, electrical opinion or contract term.

## Translate a stipulated rack population without dividing a site headline

A site MW figure does not tell the installer how many racks, devices or cable endpoints are in the work package. Begin with the actual stipulated equipment population and retain what the per-rack number means. Do not turn a site headline divided by a rack figure into a rack layout or a count of sellable positions.

EX-RP150 compares two fictional planning alternatives for one tenant. Each carries a stipulated 320 kW IT-allocation total, but alternative A contains eight rack positions and alternative B contains sixteen. The arithmetic below describes the input sheet only. It supplies no measured demand, circuit sizing, usable rack capacity, diversity factor, redundancy allowance, cooling design or operating limit. A separately quoted 2 MW site figure is intentionally excluded because its boundary and allocation are unresolved.

The physical scope changes with the population: sixteen rack identities require a different rack-position inventory from eight, even when these stipulated totals match. Device models, delivery state, rail and accessory identity, endpoint counts and pathways still come from the corresponding equipment and approved work package; neither kW total supplies those quantities. Compare the returned inventories and responsibilities before treating the alternatives as equivalent installation scopes.

EX-RP150: equal stipulated power totals, different rack populations
| Alternative | Population and input-field arithmetic | What this resolves | What remains unresolved | Source |
| --- | --- | --- | --- | --- |
| A | 8 rack positions × stipulated 40 kW per position = 320 kW | Eight distinct rack-position records in this alternative | Actual equipment, electrical and cooling design, pathways and authorized physical tasks. | Planning analysis |
| B | 16 rack positions × stipulated 20 kW per position = 320 kW | Sixteen distinct rack-position records in this alternative | The same project-specific decisions; matching arithmetic does not establish equivalence. | Planning analysis |
Original fictional alternatives, not a product recommendation or actual design. The two alternatives are not combined into 24 racks or 640 kW. No rack density, electrical provision, installed equipment count, material quantity or purchasing commitment is inferred.

## Carry the evidence into the IT installation package

The physical installer needs a defined workfront and reliable release inputs: facility/customer contacts, permitted space, equipment inventory, approved rack/route documents, customer-furnished materials and access/work windows. Keep uncertain predecessor dates visible. Share confidential utility or tenant records only through an authorized exchange, not a public inquiry form.

Leviathan supports agreed physical IT installation and coordination at customer facilities, subject to scope, site requirements and availability. Powered-land supply, utility capacity allocation, electrical energization and facility commissioning remain outside this physical IT scope. Use confirmed inputs to scope field work while qualified facility and commercial owners resolve their decisions.

References: [L3](https://www.leviathansystems.co/services/colocation-installation)

## Common planning questions

### Does a planned 200MW campus have 200MW available for my servers?

The figure alone does not establish that. Confirm phase, capacity definition, delivery stage and actual customer allocation.

### Does a good PUE prove that another rack can be installed?

No. PUE describes efficiency for its measurement basis. Capacity, compatibility, allocation and authorized site readiness need separate evidence.

### Does land near a transmission line already have power available for GPU racks?

Proximity can be relevant to a utility plan, but it does not identify this project's service connection, delivery stage or customer allocation. Establish those project-specific facts with the responsible utility and facility parties; a location observation is insufficient.

### Does a four-week utility forecast change move every installation task by four weeks?

It changes an input to the activities that depend on that service stage. In fictional EX-PW149, the changed predecessor conflicts with the requested dependent window, but it neither sets a new authorized start nor establishes the overall project delay. Scope and schedule owners must resolve the actual dependencies.

### Can I estimate installation scope by dividing site MW by a rack kW figure?

That quotient does not establish a rack population, usable positions or a physical work package. Start with a defined equipment inventory and the meaning of its power fields. EX-RP150 shows that different rack populations can have the same stipulated total while requiring different inventory and interface decisions.

## Primary sources

- [U1 — Dominion Energy Virginia data-center requests](https://www.dominionenergy.com/virginia/large-business-services/data-center-requests). Checked 2026-10-15. One utility describes site-specific plans and staged service. Not a universal timeline, executed agreement or site availability confirmation.
- [G1 — US Department of Energy: data-center efficiency metrics](https://www.energy.gov/cmei/femp/cooling-water-efficiency-opportunities-federal-data-centers). Checked 2026-10-15. Annual PUE definition only. No site PUE, available MW, cooling design or utility approval inferred.
- [L3 — Leviathan colocation installation scope](https://www.leviathansystems.co/services/colocation-installation). Checked 2026-10-15. Agreed tenant-side physical installation; no capacity offer, utility study or facility commissioning service.
- [U2 — Dominion Energy Virginia: current site-selection and service-connection FAQ](https://www.dominionenergy.com/virginia/large-business-services/data-center-requests). Checked 2026-10-19. Current narrow read of proximity, site-specific plans, staged service and named delivery dependencies only. Retained U1 remains exact. No numerical threshold, universal timeline, current supply condition, site capacity, utility commitment or electrical approval adopted.

## Related Leviathan resources

- [Large U.S. Data Center Projects: Plans, Power and Delivery Phases](/articles/large-us-data-center-projects-plans-phases)
- [GPU Cloud Availability: Quotas, Reservations and Capacity Windows](/articles/gpu-cloud-capacity-availability)
- [GPU Site Readiness: Inputs and Owners Before Equipment Arrives](/articles/site-readiness-before-gpus-arrive)
- [GPU Deployment Timeline: Build the Schedule Around Release Gates](/articles/gpu-deployment-timeline)
- [Colocation installation scope](/services/colocation-installation)

## Scope installation from confirmed site inputs

Share the actual workfront, equipment plan, customer responsibilities and known facility release dates.

[Discuss the scope](/contact?service=colocation-installation&from=/articles/data-center-power-capacity-claims)