Exelon's October 30 earnings materials separate prospective data center demand into about 11 GW of high-probability load and about 23 GW in a future pipeline. The useful detail for infrastructure engineers is how the company defines those groups. A site in a cluster study carries different planning evidence from one in advanced design or backed by a transmission security agreement.
The figures appear on slide 15 of Exelon's third-quarter presentation, published with its October 30 results. This is a new disclosure about projected demand, rather than an announcement that the corresponding facilities have been energized.
My engineering reading is that power status deserves its own place in the deployment schedule. A regional demand forecast provides context. The decision to deliver and commission compute needs evidence tied to the particular site and phase.
Read the categories before adding the megawatts
Exelon describes its high-probability group as projects in advanced design or backed by FERC-approved transmission security agreements. It says roughly 45% of that group has such agreements. The future pipeline covers current or future cluster studies.
Those descriptions leave meaningful differences even inside the higher-confidence category. A project team should preserve them when translating a market update into its own capacity plan.
Ask what the site's current milestone actually establishes. Does it identify required network work, secure a financial commitment, authorize construction, or permit a defined electrical service? Record the supporting document and its conditions. Each answer helps a different part of the deployment team.
Turn the power schedule into a phased delivery plan
For a proposed AI campus, my recommendation is to map each intended compute phase to its own power dependency.
Start with the load the facility expects at the utility meter, then document the assumptions used to derive the IT capacity available to racks. Keep cooling, electrical losses and operating reserves visible. A utility load figure alone does not specify how many accelerators a facility can support.
Connect that calculation to dates and prerequisites. Identify the infrastructure required for initial energization, the work needed for later expansion and the acceptance tests before production use. Assign an owner to each unresolved item.
This gives procurement a practical basis for staging deliveries. Equipment arriving ahead of usable facility capacity creates storage, handling and commercial decisions that deserve an explicit plan.
Review financial commitments alongside technical dependencies
The presentation's reference to transmission security agreements also raises a question for the people writing the deployment schedule: what commitments become binding before the site can operate?
The specific contract needs review by the responsible commercial team. Engineers can contribute a dependency list showing which delays affect the load ramp and which design changes could alter the requested service.
As a proposed internal review, compare the utility milestones with equipment acceptance dates, construction payments and customer delivery promises. Flag any commitment whose timing assumes that another party will finish work on an unconfirmed date.
That exercise helps expose schedule risk early enough to negotiate a change or arrange a contingency.
Update workload promises when a milestone changes
A capacity forecast becomes useful to application teams when it explains what they can schedule.
Consider a planned cluster whose first facility phase can proceed while expansion remains dependent on further network work. That is a planning example, not a disclosed Exelon customer deployment. Its service plan should distinguish workloads supported by the initial phase from those relying on expansion.
Define who updates those commitments when the power schedule changes. Preserve the previous assumption, the new evidence and the workloads affected. The same record should inform sales, infrastructure operations and compute scheduling.
Without that shared record, different teams can continue using different versions of the site's readiness date.
Ask for the evidence behind the next decision
Exelon's update is useful because it exposes development stages behind a large demand forecast. The categories remain company assessments of future load, with execution still ahead.
For an infrastructure buyer, the next step is to request a site-specific account of the remaining power work and map it to the deployment decision at hand. Document the service assumptions, prerequisites, responsible parties and consequences of delay.
That produces a plan a team can revise as evidence changes, from the first study through commissioning and the eventual workload ramp.
Top comments (0)