blog.demetriusnew.com

Category: Electricity

  • AI Data Centers Are Becoming Large Enough to Require New Reliability Rules

    The growth of large computational loads is changing the operating relationship between data centers and the electric grid. NERC’s new standards point toward a more formal governance model—one that connects facility operations, engineering, and executive oversight to bulk-power-system reliability.

    A data center can be highly resilient inside its fence and still create risks at the grid interface.

    That distinction matters as AI facilities, data centers, and other computational loads grow in scale and connect to the bulk power system. Their electrical demand can change quickly, and their response during a disturbance can affect more than the facility itself. Grid operators need timely information about the load, credible models of its behavior, and clear communication with the people who operate it.

    NERC’s proposed computational-load reliability standards are an effort to establish that foundation.

    From stakeholder ballot to regulatory review

    On October 15, NERC announced that the standards and their implementation plans had passed their final stakeholder ballot. On October 26, NERC’s Board of Trustees adopted the standards. NERC has said it will submit them to the Federal Energy Regulatory Commission for approval in the United States. Until FERC approves them and the applicable implementation period arrives, they are not enforceable U.S. reliability standards. (nerc.com, nerc.com)

    The proposed registry criteria would apply to Computational Load Owners and Computational Load Operators at sites with total connected load of at least 50 MW, supplied through electrical equipment connected at 100 kV or higher. This is a proposed registration threshold—not a claim that every data center or large electricity customer is covered. The related registry criteria also have a separate approval path. (publicpower.org, nerc.com)

    What the standards address

    NERC’s first phase centers on basic capabilities needed to integrate large computational loads reliably. The proposed standards address how loads are interconnected and represented in system models; how facility operators communicate with relevant grid entities; and how protection coordination and disturbance monitoring support reliable operation. The project materials identify three foundational standards—CLO-001-1, CLO-002-1, and CLO-003-1—alongside related revisions to interconnection requirements and studies. (nerc.com)

    These requirements matter because grid reliability depends on a shared operational picture. If the load changes unexpectedly, operators need to understand what happened, how the facility responded, and whether similar behavior could recur. Reliable models, clear communications, coordinated protection, and usable disturbance records help make that possible.

    The governance question for executives

    The standards create a practical governance challenge: responsibility may be split among the entity that owns the site, the entity that operates it, the data-center tenant, the utility, and other grid participants. NERC’s registry revisions establish distinct Computational Load Owner and Computational Load Operator roles, underscoring the need to identify who is accountable for each operational duty. The proposed registry criteria remain subject to FERC approval. (nerc.com)

    Executives should begin with a clear map of ownership and accountability:

    • Assign a responsible executive. Give one leader authority to coordinate energy, engineering, operations, compliance, and external grid relationships.
    • Clarify owner and operator responsibilities. Document who maintains models and protection settings, who communicates with grid entities, who responds to disturbances, and who preserves records.
    • Assess operational readiness. Review procedures, contact paths, escalation authority, and after-hours coverage. A contact list that works only during business hours is not an operating plan.
    • Review data and model quality. Confirm that technical information shared with grid operators reflects current facility design and actual operating behavior.
    • Connect contracts to operating reality. Agreements with tenants, operators, utilities, and service providers should support timely information sharing and coordinated action.
    • Prepare evidence of control. Keep records that show how the facility manages communications, models, protection coordination, and disturbance response.

    This work is useful before a rule becomes enforceable. The goal is not to guess at final compliance obligations; it is to identify gaps early enough to resolve unclear responsibilities, missing data, and fragile operating procedures.

    A first phase, not the finish line

    NERC describes the adopted standards as the first phase of its broader large-load action plan. Additional standards work is underway around computational-load performance, planning and reliability studies, event reporting, and model quality. (nerc.com)

    That points to a wider shift in how data-center readiness will be judged. Power availability, backup generation, and facility uptime remain essential. But large computational facilities also need to show that their grid-facing behavior is understood, communicated, and governed.

    For boards and executive teams, the strategic question is straightforward: Can the organization explain who is responsible for the facility’s effects on the grid, how those responsibilities are carried out, and what evidence shows the controls work?

    As computational loads grow, reliability will depend on that answer being clear before the next disturbance—not reconstructed afterward.

  • Why a Gigawatt of Electricity Doesn’t Mean a Gigawatt of AI Compute

    A data center’s power capacity tells us how much electricity it can draw. It does not tell us how much useful AI work the facility will produce.

    That difference matters as companies compete for power, build larger campuses, and commit billions of dollars to AI infrastructure. A megawatt secured at the grid connection is only the beginning of the measurement.

    Power has to travel through the system

    Electricity entering a data center must be converted and distributed before it reaches computing equipment. The facility also needs cooling, monitoring, backup systems, and other infrastructure to operate reliably.

    Then there is the equipment itself. A GPU can be installed and powered without running at full utilization. A poorly configured rack, a failed component, or a system restart can reduce productive output even while the facility continues to draw power.

    The result is a gap between electricity consumed and useful computation delivered.

    What the reported 60–70% estimate tells us

    On October 14, TechRadar reported remarks from NVIDIA representatives at a Vertiv event suggesting that roughly 60–70% of electricity drawn by some AI data centers supports AI processing. The report described the remaining share as associated with cooling, power distribution and conversion, equipment configuration, failures, and restarts.

    That figure is an industry estimate reported from executive remarks. It is not an independently audited average for all data centers. Facility design, workload, equipment, climate, operating practices, and the way “AI processing” is measured can all affect the result.

    The estimate is still useful as a prompt: capacity figures alone do not reveal how efficiently a facility turns electricity into productive work.

    “Non-compute” power is not automatically waste

    Cooling and backup systems are necessary to keep high-density computing equipment within operating limits and protect service continuity. Power conversion and distribution are also part of delivering electricity safely to the IT load.

    The goal is not to eliminate every watt that does not go directly to a processor. The goal is to understand the full system, reduce avoidable losses, and make sure the infrastructure investment supports dependable output.

    A facility designed for peak demand and contingencies may also have capacity that is not used continuously. That may be appropriate for resilience, but it raises a management question: how much of the available infrastructure is producing useful work under typical operating conditions?

    Measure the output, not just the input

    “Gigawatt of AI compute” is shorthand. A gigawatt measures electrical power; compute output is measured through completed work and system performance.

    For executives, that means asking for more than a facility’s contracted power or nameplate capacity. Useful measures could include:

    • Electricity delivered to the facility and to IT equipment
    • AI workload throughput, such as completed jobs or tokens generated
    • Accelerator utilization and periods of idle or degraded operation
    • Cooling and power-system overhead
    • Availability, restart frequency, and time spent operating below target

    These measures need consistent definitions and a clear time period. A peak result, a design target, and an observed operating average are different kinds of evidence.

    The strategic implication

    When power is scarce, improving the amount of useful computation produced from existing electricity can be as important as securing more supply.

    That makes infrastructure efficiency an operating and capital-allocation issue. Better power delivery, cooling, equipment configuration, workload scheduling, and maintenance may help increase productive output without assuming that every problem can be solved by adding another megawatt.

    The reported 60–70% estimate should be treated as a signal to investigate, not a benchmark to apply blindly. Each operator needs facility-level evidence to understand where power goes and what work it enables.

    The executive question is therefore not only, “How much power can this data center draw?”

    It is: How much useful, reliable AI work does each megawatt deliver—and how do we know?

  • The Next AI Infrastructure Bottleneck May Be Chips Waiting on Other Chips

    AI infrastructure discussions often begin with the most visible asset: the accelerator. How many GPUs or other AI processors can a company buy, and when can they be installed?

    But installed capacity is only part of the equation. Those processors must also exchange data, coordinate work, and receive instructions from the software stack. If those connections cannot keep pace with the workload, adding more processors may not deliver a proportional increase in useful compute.

    That makes networking and integration a growing part of the economics of AI infrastructure.

    Compute depends on more than the processor

    An AI cluster is a system of connected components. Processors move data between memory, storage, and other processors while workloads are divided, coordinated, and recombined. The network affects how quickly those exchanges happen and how well the system handles congestion or failures.

    Two networking jobs matter here. Scale-up networking connects accelerators within a pod or rack. Scale-out networking connects systems across racks and throughout a data center. A workload can depend on both.

    When data movement or coordination becomes a constraint, some processors may wait for information or for other parts of the workload to finish. The hardware is present, but its potential output is not being fully realized. That can weaken the return on expensive infrastructure investments and complicate capacity planning.

    What Token Fabric is trying to do

    On October 8, Nvidia-backed Upscale AI introduced Token Fabric, a networking architecture intended to support AI processors from different suppliers. The company describes it as a combination of scale-up and scale-out networking, systems, and shared software for managing operations. Reuters reported that the platform is expected to roll out in stages, with the first component planned for the fourth quarter and the broader platform through 2027. Upscale says general availability is planned for early 2027. (reuters.com, upscale.com)

    The proposal addresses a practical challenge for operators: networking has often been assembled from separate components that customers must integrate and manage. A more unified approach could simplify parts of that work and make it easier to build clusters containing different types of accelerators.

    That is the opportunity. It is not yet proof that the architecture will deliver a specific utilization gain or make mixed-vendor systems simple to operate. Those results will depend on deployment conditions and independent performance evidence.

    Interoperability is useful, but it is not automatic

    The possibility of using multiple accelerator suppliers is attractive for organizations that want more choice in hardware procurement or want to match different processors to different workloads. It could also reduce reliance on a single hardware ecosystem.

    However, networking compatibility is only one part of interoperability. A system still needs suitable software frameworks, drivers, compilers, memory behavior, and workload orchestration. Operators must also understand how performance changes when different processors share a system.

    In other words, “connects different processors” does not necessarily mean every processor can be substituted freely, or that every workload will run equally well across all of them. The relevant test is whether the full system performs reliably and economically for the workloads a customer actually runs.

    The business metric is useful output

    For decision-makers, the central question is not simply how many processors are installed. It is how much useful work the organization gets from the complete system, at what cost, and with what operational burden.

    That means evaluating utilization alongside measures such as workload throughput, latency, energy use, network performance, software compatibility, and the cost of operating the environment. A network upgrade that improves one technical metric may not improve the business outcome if it adds complexity or fails to support the applications that matter.

    The same discipline applies to claims about future capacity. Product roadmaps and announced availability dates are signals about where vendors are investing. They are not substitutes for customer deployments, workload-level results, and independently reviewable performance data.

    The next bottleneck is system-level

    AI infrastructure is moving beyond a simple race to install more chips. The economics increasingly depend on how compute, networking, software, power, and operations work together.

    Token Fabric is one example of vendors trying to address that system-level problem and support more heterogeneous infrastructure. The broader industry question is whether these architectures can make processors easier to connect and keep productively occupied—without creating new integration and management burdens.

    The next generation of AI capacity may be shaped not only by how many chips organizations can obtain, but by how effectively those chips can work together.

  • The Compute Grid: What Happens When Idle GPUs Become Shared Infrastructure?

    AI’s next capacity gain may come from coordinating existing infrastructure more effectively. The harder question is whether shared capacity can be made dependable enough to use.

    AI compute is often described as scarce—and for many organizations, it is. But scarcity can exist alongside underused equipment. Some data centers may have capacity that is idle between workloads, while startups and researchers struggle to secure the right chips at the right time.

    The National Compute Grid initiative, announced October 7, aims to connect capacity across providers through shared scheduling. The idea is to make it easier to find available computing resources and match them with workloads, potentially improving access to infrastructure that already exists. 

    That could add a useful layer to the AI infrastructure market. It does not mean every idle GPU can immediately be combined into a reliable pool—or that shared scheduling makes new data centers unnecessary.

    The opportunity is coordination

    A GPU sitting unused at one facility cannot automatically help a team whose workload is running elsewhere. Capacity is distributed across providers, hardware types, locations, software environments, and commercial agreements.

    A shared scheduling layer could help bridge some of those gaps. In principle, it could show what capacity is available, help match workloads to suitable hardware, and coordinate access across participating providers. The initiative’s organizers have described a network that would pool capacity from labs, cloud providers, and different chip systems. 

    If it works, the value may be more than simply “more GPUs.” Better coordination could make capacity easier to discover, allocate, and use—especially for organizations that cannot secure large, long-term compute contracts.

    “Available” does not always mean usable

    A headline capacity figure can describe resources that are connected, planned, or otherwise in sight. That is not the same as compute that a customer can access continuously, at a known price, with a guaranteed performance level.

    The initiative’s reported figure of roughly 760 megawatts, for example, was described as capacity “connected or in sight,” alongside a goal of reaching 2 gigawatts by 2030. Those are organizer-reported figures, not proof that all of that capacity is currently available to run customer workloads. 

    The initiative’s current website describes its capacity figures as dated planning estimates and says access is limited to public-sector partners during a preview. That is a useful reminder to distinguish a developing network and its stated plans from a mature, broadly available service. 

    The same care applies to utilization statistics. The consortium’s paper reportedly estimates that independent, single-tenant data centers average less than 15% net computing utilization. That figure should not be read as meaning that 85% of all GPUs are sitting idle and ready to be reassigned. Utilization can be measured in different ways, and unused time does not by itself establish that hardware is compatible, accessible, or suitable for another organization’s workload. 

    Workload fit matters as much as capacity

    A pool of GPUs is not automatically a single large cluster. Large training runs can depend on fast networking between thousands of GPUs. If resources are spread across facilities, data movement, network performance, and coordination can limit what workloads are practical. Different chip architectures can also require changes to software and tooling. 

    Shared compute may therefore be useful first for workloads that can tolerate more flexibility: research jobs, inference, or smaller training runs. Whether a distributed pool can reliably support the most demanding jobs remains an operational question.

    The details to watch are concrete:

    • Availability: Can users get capacity when they need it, and for how long?
    • Performance: Does the workload complete at the expected speed?
    • Continuity: What happens if a provider withdraws capacity or a job is interrupted?
    • Compatibility: Can the workload run across the available chip and software environments?
    • Data movement: How long does it take to move datasets to the compute—and what does that cost?
    • Accountability: Who is responsible when capacity is unavailable or performance falls short?

    These are not minor implementation details. They determine whether shared capacity behaves like a dependable service or simply appears in a capacity forecast.

    A new infrastructure layer, with evidence still to build

    The National Compute Grid points toward a broader market question: can software coordination make existing infrastructure more productive and more accessible?

    If the answer is yes, some organizations may get useful compute without building their own facilities or negotiating large dedicated contracts. That could expand access and improve the use of resources already deployed.

    But the evidence that matters will come from operations: how much capacity is actually available, what workloads it supports, how reliably jobs complete, and whether performance and cost meet users’ expectations.

    The next phase of AI infrastructure may include both new buildings and better coordination of existing ones. A shared scheduler can help connect supply and demand. It cannot make every GPU interchangeable—or turn a planning estimate into dependable compute by itself.

    The measure of success is not how much capacity a grid can name. It is how much useful work users can reliably complete with it.

  • The Electrical Bottleneck Inside the AI Data Center

    AI power discussions often begin outside the data center: Can the grid serve the load? Is generation available? How long will interconnection take? Can transmission capacity reach the site?

    Those questions remain central. But they aren’t the only ones.

    After electricity reaches a campus, it must still pass through the facility’s electrical infrastructure and arrive at the equipment that performs the computing. That pathway has physical limits. Conductors, switchgear and other equipment take up space, require installation labor and must operate reliably under demanding conditions. As data centers add more power-dense computing, the electrical system inside the facility becomes part of the scaling challenge.

    VEIR’s October 8 financing announcement is a signal that investors see an opportunity in this layer. The company announced a $110 million Series C, bringing its reported total capital raised to $225 million. It says the funding will support manufacturing, product development and preparation for commercial deployments. VEIR also reports a 3-megawatt demonstration and says it is working with customers and industry partners on reference designs for AI facilities. 

    The approach centers on superconducting power-delivery systems. In VEIR’s description, the system includes more than the superconducting cable: it also requires cryogenic cooling, controls, terminations and monitoring. The goal is to move more power through a smaller physical footprint than conventional power-delivery infrastructure. 

    That could matter where space and power density are becoming linked. A smaller footprint could give designers more flexibility inside a facility or campus. But a compact cable alone doesn’t establish an operational advantage. The complete installation has to work as a system, and its economics must account for cooling, controls, installation, maintenance and the consequences of equipment failure.

    The technology also addresses a specific point in the power chain. It may improve how electricity is distributed within a data center. It does not supply the electricity, secure an interconnection or expand the grid. Those are separate constraints, and they remain part of the larger project.

    That distinction is useful because “AI needs more power” can make every proposed solution sound interchangeable. They aren’t. Some investments add generation. Some expand transmission. Others improve the way power is delivered inside a facility. A project may need progress at several of these layers at once.

    The commercial evidence is still developing. VEIR’s reported 3-megawatt demonstration is a technical milestone, while the company’s announcement describes initial commercial deployments as something it is preparing for. Reuters reported earlier this year that superconducting cables were not yet being used in data centers and that cost and manufacturing constraints had limited adoption. 

    For operators and infrastructure investors, the next questions are practical:

    • How reliably does the full system operate under real data-center loads?
    • What does it cost to install and maintain compared with conventional alternatives?
    • How does the cooling and control equipment affect operating complexity?
    • Can the system be manufactured, installed and serviced repeatedly at commercial scale?

    The $110 million round indicates investor confidence in the opportunity and provides capital to pursue commercialization. The test of the thesis will be what commercial deployments show about reliability, economics and repeatability.

    AI infrastructure can be constrained at more than one point between the grid and the server. Power availability gets attention because it is visible and difficult to solve. Power delivery inside the facility may be less visible, but it can also shape how densely and efficiently a campus grows.

    The useful question is not just how much electricity a data center can secure. It is how dependably and economically that electricity can be delivered to the compute.

    Source note: VEIR’s financing and technical milestones are company-reported; treat commercial performance claims as unproven until supported by operating data.

  • A Billion Dollars for Community Acceptance Is an Infrastructure Signal

    Community Acceptance Is Infrastructure

    Amazon’s announcement of more than $1 billion in additional investment for U.S. data-center communities is being presented as a community-benefit program. That description is accurate, but incomplete.

    The announcement also reflects a change in the conditions surrounding infrastructure development. Community concerns about power demand, utility costs, water use, transparency, and local economic benefit are becoming part of the project environment. They can influence whether a development proceeds smoothly, faces delay, or must respond to new political and regulatory scrutiny.

    That makes community acceptance relevant to execution—not as a substitute for permits or engineering, but as one of the conditions developers must manage.

    What Amazon has announced

    Amazon says its Built Together program will add more than $1 billion over five years to existing investments in communities where it operates data centers. The company describes the program as supporting education, job training, energy affordability, water and energy preservation, and other local priorities. Reuters

    The company has also published commitments on public engagement. It says it no longer uses nondisclosure agreements with government agencies it works with on its projects, plans to share information earlier, and will publish annual data on energy use, energy efficiency, water use, water efficiency, and the share of energy from carbon-free sources. aboutamazon.com

    Some program details are framed as future targets. Amazon says it aims to connect more than 300,000 students with free degree access, prepare up to 100,000 workers annually through training centers by the end of 2028, and target energy-efficiency improvements for more than 30,000 homes and over 300 schools and community buildings. These are commitments to monitor, not evidence that the benefits have already been realized. aboutamazon.com

    Why this is an infrastructure story

    Large infrastructure projects depend on more than capital and construction capacity. They also depend on access to sites and utilities, predictable approvals, available workers, and a credible relationship with the communities that host them.

    For data centers, those relationships are under pressure as the scale of development grows and residents ask who pays for additional grid infrastructure, how local resources will be used, what jobs will remain after construction, and whether the public can see the terms and impacts of proposed projects.

    When those questions go unanswered, opposition can become a schedule and investment risk. Projects may face greater scrutiny, political resistance, or demands for changes to their plans. That is why community engagement is increasingly connected to infrastructure execution.

    Amazon’s announcement is evidence that the company views these concerns as material. It is not proof that the program will secure community acceptance. That will depend on implementation: whether resources reach the places and people identified, whether commitments are reported clearly, and whether local concerns influence project decisions.

    The difference between a commitment and an outcome

    A public commitment creates a basis for accountability, but it does not complete the work.

    For the program to build trust, communities will need to be able to see what was promised, where investment was made, what results followed, and how benefits relate to the costs and impacts of hosting the infrastructure. Annual reporting can help, but the usefulness of that reporting will depend on its detail and accessibility.

    The same is true of transparency around project planning. Ending NDAs with government agencies is a meaningful stated change in practice. Its value will be clearest when residents can access relevant information early enough to understand a project while choices are still open.

    A signal worth watching

    The $1 billion announcement should not be read simply as a donation, and it should not be treated as proof that local concerns have been resolved.

    It is better understood as an infrastructure signal: community acceptance has become important enough to affect how a major developer allocates capital, communicates with public agencies, and frames its responsibilities to host communities.

    The next question is whether those commitments translate into measurable results—and whether communities consider those results sufficient. That is where the difference between a community-benefit announcement and durable community trust will become visible.

    Source notes: Reuters’ October 2 report confirms the $1 billion-plus, five-year investment and the community focus. Amazon’s announcement provides the program targets and its stated transparency commitments. The interpretation that these commitments signal community acceptance is becoming material to execution is analysis, not a claim made directly by either source.

  • When a Data Center Load Disappears, the Grid Feels It

    A facility’s protection systems are designed to respond when power conditions move outside safe limits. But when a very large load disconnects or transfers to backup power at once, that protective response can become a grid-level event.

    That is the issue behind PJM’s proposed ride-through requirements for large computational loads, including data centers and cryptocurrency-mining facilities.

    In July 2026, about 3,800 MW of data-center load in northern Virginia transferred from the PJM grid to on-site backup generation after a transmission fault. PJM and Dominion reported voltage and frequency spikes. Operators took action to restore the balance between generation and demand, and PJM reported no significant reliability impacts from the event. 

    The mechanism is straightforward. If a large amount of demand suddenly leaves the grid while generation remains online, generation temporarily exceeds load. That imbalance can push frequency upward. Voltage can also rise, with the system response depending on the location, size, and timing of the load change.

    This does not mean every sudden load transfer will destabilize the grid or cause an outage. The July event was managed. The concern is that repeated or larger events can create operational challenges, especially when the grid has little time to adjust.

    PJM presented a proposal, not a final rule, on September 8. It would set performance expectations for how large computational loads respond within defined voltage and frequency disturbance ranges. It also addresses recovery: after voltage returns to an acceptable range, the proposal calls for load consumption to recover to more than 90% of its pre-disturbance level within two seconds, subject to the proposed conditions. 

    The regulatory status matters. FERC’s June 18 show-cause order asked PJM to address questions about its large-load processes, including whether tariff requirements are needed for ride-through, ramp rates, and load restoration. PJM says it plans to file proposed solutions with FERC in November. The specific ride-through requirements remain under review. 

    For facility owners and engineers, this shifts the design conversation. The question is not only whether the facility can ride through a disturbance internally. It is whether the combined facility response—its protection settings, power systems, backup transfer, and recovery behavior—will be predictable and compatible with grid needs.

    The distinction is important: a protective action can make sense for a single facility and still create a larger system challenge when many facilities react together. As large loads become a bigger part of grid planning, their disturbance response is becoming part of the infrastructure performance discussion.

    Source note: PJM proposal and FERC filing timeline; PJM’s account of the July 22 event. Citations above.

  • The Cheapest AI Megawatt May Already Exist

    The Cheapest AI Megawatt May Already Exist

    “AI needs more power” is true as far as it goes. It is also too broad to tell an executive what to build, fund or approve.

    A growing data center needs electricity at a specific site, at a specific time, with the reliability its operations require. Several different constraints can stand between that need and an energized facility. There may be too little generation available at the required hours. An existing transmission corridor may be congested. A local substation may need upgrades. An interconnection may still be years from completion.

    Those are different problems. They do not all have the same solution.

    The Department of Energy’s September 24 announcement offers a useful example. DOE said it intends to help fund 31 grid improvement projects across 26 states through its SPARK initiative. The selected projects are expected to reconductor or rebuild more than 1,500 miles of transmission lines and deploy grid enhancing technologies across nearly 21,000 miles. Together, DOE expects those efforts to make more than 23 GW of additional electricity capacity available.

    That 23 GW is not a proposal for 23 GW of new generation. It is an expected increase in what the grid can carry and make available through transmission upgrades. The projects have been selected; the capacity gain still has to be delivered and measured.

    The constraint may be the route

    Think of generation as the source of electricity and transmission as part of the route it takes to customers. Adding supply at one end does little for a particular site if the route between them is constrained.

    Reconductoring replaces the wire on an existing transmission line with a conductor that can carry more power. Other grid enhancing technologies help operators understand or improve how existing lines are used. Dynamic line ratings, for example, use current conditions to assess a line’s safe carrying capability. Power flow controls can help direct electricity across available paths.

    These approaches are attractive because they can draw more value from infrastructure and rights of way that already exist. They may be especially useful where obtaining a new corridor would take much longer.

    That does not make every existing line an easy upgrade. A project still has to satisfy engineering, reliability and operational requirements. Nor does an increase in transmission capability guarantee that electricity will be available during every hour a customer needs it.

    What the announcement changes

    The opportunity is wider than the familiar discussion about building new generation.

    Advanced conductors, line monitoring, sensors, power flow controls and grid software all become more consequential when transfer capability is the binding constraint. So do the less visible tasks: studying where an upgrade will help, coordinating the work and proving that the promised capacity is available in operation.

    For an AI infrastructure developer, the practical question is not simply, “How many megawatts are planned in this region?” It is:

    How much power can reach this site, under the required conditions, by the date we need it?

    For utilities and policymakers, the question is where targeted upgrades can relieve real congestion—and where new generation, substations or transmission corridors are still necessary.

    From announced capacity to delivered power

    DOE’s projected 23 GW is a meaningful signal about where grid investment is headed. It is not yet 23 GW of observed, site ready power.

    The evidence will come as projects are completed and operators measure the resulting transfer capability, reliability and service to customers. That is where the declared figure becomes an operational result.

    AI’s electricity challenge is often framed as a race to produce more power. In some places it will be. In others, a faster opportunity may be to move available electricity more effectively through the grid we already have.

    The cheapest megawatt may already exist. The work is proving that it can reach the right place when it counts.

  • AI Infrastructure Is Moving From Declared Capacity to Observed Readiness

    The AI infrastructure race has largely been communicated through declarations of scale.

    Gigawatts of proposed data-center capacity. Billions of dollars in projected investment. Enormous forecasts for electricity demand. New campuses capable of housing hundreds of thousands of advanced processors.

    These numbers reveal the direction of travel—but they do not always reveal which projects can actually arrive.

    That distinction is becoming increasingly important.

    Microsoft reportedly has an internal target to expand its global data-center capacity from approximately 12 gigawatts today to more than 38 gigawatts by 2032. Meanwhile, electricity requests from large power users across portions of the United States have climbed above 700 gigawatts. Reuters⁠

    The scale is extraordinary.

    So is the uncertainty.

    The next phase of AI infrastructure may therefore be defined less by declared capacity and more by observed readiness: verifiable evidence that a proposed project possesses the physical, financial and institutional conditions necessary to become operational.

    Declared capacity is not delivered capacity

    Declared capacity describes intention.

    It may appear in a corporate target, utility interconnection request, investor presentation, electricity forecast or economic-development announcement.

    But a proposed gigawatt can exist on paper long before the organization has secured:

    • Land
    • Permits
    • Financing
    • Customers
    • Electricity
    • Grid interconnection
    • Transformers and turbines
    • Cooling infrastructure
    • Construction labor
    • Community acceptance

    Until those dependencies are resolved, the declared capacity remains conditional.

    This does not make the projection fraudulent or meaningless. Infrastructure planning requires forecasts. Organizations must reserve land, capital and power years before facilities become operational.

    The problem begins when every declaration is treated as equally probable.

    A project with a press release and an interconnection request should not carry the same planning weight as one with site control, permits, committed financing, signed tenants, equipment reservations and a defined energization date.

    Both may claim the same number of megawatts.

    They do not represent the same level of readiness.

    The market is beginning to demand proof

    Evidence of this transition is already appearing across the infrastructure stack.

    Utilities are introducing financial commitments and additional screening to separate credible large-load customers from speculative or duplicated applications. In Pennsylvania, Reuters found that only 20 of more than 100 proposed data centers had sought permits.

    Lenders are also becoming more selective. Investors are charging more for risk and demanding stronger protections against permitting delays, electricity queues and supply-chain bottlenecks. In one case, construction financing could not be accessed until permits were secured and leases signed.

    These are not merely administrative obstacles.

    They are attempts to convert projections into evidence.

    A permit demonstrates that a project has moved beyond general intention.

    A signed lease establishes customer commitment.

    An upfront payment gives the applicant something meaningful to lose.

    A power agreement identifies a plausible energy source.

    An equipment order connects the projected completion date to the physical supply chain.

    Each one increases confidence that the proposed capacity can actually materialize.

    Observed readiness is a chain, not a single document

    No single artifact proves that an AI infrastructure project will succeed.

    A signed lease is not useful if electricity cannot be delivered. A grid connection is insufficient if financing collapses. Available land does not create an operating data center without equipment, cooling, construction and customers.

    Observed readiness must therefore be evaluated as a connected chain of evidence:

    1. Commercial readiness: Are credible customers contractually committed?
    2. Financial readiness: Is capital available under conditions the project can satisfy?
    3. Regulatory readiness: Are permits, environmental requirements and local approvals progressing?
    4. Energy readiness: Is generation available, and can the electricity physically reach the site?
    5. Supply-chain readiness: Have critical transformers, turbines, switchgear, cooling equipment and chips been secured?
    6. Operational readiness: Can the facility withstand equipment failures, grid interruptions, cyber incidents and other disruptions?

    A weakness in any one of these areas can strand the rest.

    A warehouse full of GPUs without dependable electricity is stranded compute. A power reservation without financing may become ghost demand. A fully financed project without permits can remain trapped in development.

    Scale depends on the entire chain surviving.

    Readiness may become a competitive asset

    During the first phase of the AI infrastructure boom, scarcity made almost any plausible capacity valuable.

    The next phase will likely be more discriminating.

    Utilities cannot build generation and transmission around every speculative request. Lenders cannot treat every projected campus as equally financeable. Equipment manufacturers cannot reserve scarce production capacity indefinitely. Communities will increasingly question projects that consume land, water or grid capacity without producing credible benefits.

    As that scrutiny increases, organizations capable of producing verifiable readiness evidence may receive:

    • Better access to financing
    • Greater credibility with utilities
    • Stronger negotiating positions for equipment
    • Faster regulatory decisions
    • Higher confidence from customers
    • More defensible project valuations

    The advantage will not come from possessing the boldest forecast.

    It will come from reducing uncertainty for everyone whose resources are needed to make the forecast real.

    From projection to proof

    The AI infrastructure buildout is not slowing into irrelevance. It is moving into a more demanding stage.

    Announcements still matter. Forecasts still matter. Ambitious capacity targets still matter.

    But the gap between a declared gigawatt and an energized gigawatt is becoming impossible to ignore.

    The organizations that succeed may be those that can establish a traceable line from projected demand to committed capital, approved sites, contracted equipment, available generation and operational delivery.

    That is the transition from declared capacity to observed readiness.

    Gigawatts will remain the headline.

    Evidence will increasingly determine which ones get built.

  • AI Data Centers Are Beginning to Bring Their Own Power

    The power supply is becoming part of the data center.

    The artificial-intelligence infrastructure race is producing an important shift in how data centers are designed.

    For years, developers could treat electricity largely as an external utility service. They selected a location, applied for a grid connection and built the facility around the expectation that sufficient power would eventually arrive.

    That model is becoming less dependable.

    AI data centers require enormous amounts of electricity, often concentrated within a relatively small geographic area. At the same time, utilities must contend with transmission constraints, transformer shortages, lengthy interconnection studies and project requests that may be speculative or duplicated.

    The result is a widening gap between having plans for a data center and having the power required to operate one.

    A $2.6 Billion Signal

    Vertiv has agreed to acquire UtilityInnovation Group, a company specializing in microgrids, advanced power controls and behind-the-meter power architecture for data centers.

    The agreement calls for approximately $1.45 billion in cash at closing, with as much as $1.15 billion in additional payments tied to future earnings targets. That places the potential transaction value at approximately $2.6 billion.

    The acquisition is expected to add microgrid controls, onsite-generation orchestration, specialized switchgear and energy-storage integration to Vertiv’s existing power and cooling portfolio.

    That is more than a routine expansion of product offerings.

    It is evidence that power availability is moving upstream into the earliest stages of data-center planning.

    Vertiv describes the expanded architecture as extending from the utility interconnection to the chip. Its stated objective is to support grid-connected facilities, bridge-to-grid projects and sites capable of operating independently through onsite generation.

    In other words, the power supply is becoming part of the data center itself.

    Why Waiting for the Grid Is Becoming a Competitive Risk

    A developer may control the land, secure financing and purchase computing equipment, yet remain unable to bring the facility online because the local grid cannot supply the requested load.

    That delay carries serious consequences.

    Equipment can sit idle. Construction schedules can slip. Customer commitments can be missed. Capital remains tied up in infrastructure that is not producing usable computing capacity.

    For AI companies, this creates a direct connection between energy availability and speed to market.

    The competitive metric is no longer merely how many GPUs a company owns. It is how quickly those GPUs can be converted into operational compute.

    The industry increasingly describes this as “time to power” or “time to first token.”

    Both phrases point to the same underlying reality: compute capacity does not exist in a commercially meaningful sense until it can be energized.

    What a Microgrid Changes

    A microgrid can coordinate multiple sources of electricity within a defined site or operating area. Depending on its design, it may combine utility service with onsite generation, battery storage and advanced control systems.

    This creates several possible operating models.

    A grid-connected data center can use onsite resources to strengthen reliability or manage peak loads.

    A bridge-to-grid facility can begin operating with onsite generation while waiting for a larger utility connection.

    An islanded facility can operate independently when utility power is unavailable or insufficient.

    These options do not make the traditional grid irrelevant. Large data centers may still require substantial utility service over the long term.

    What changes is the developer’s dependence on a single delivery timeline.

    Instead of waiting passively for the grid to expand, the project can be designed around a coordinated portfolio of energy sources.

    Power Architecture Is Now Data-Center Architecture

    This shift has consequences beyond electrical engineering.

    Site selection must account for access to natural gas, renewable resources, storage capability and future utility interconnection—not merely available land.

    Financing must cover generation and energy infrastructure as well as buildings, cooling and computing hardware.

    Operating plans must address fuel availability, emissions, maintenance, cybersecurity and the interaction between onsite systems and the surrounding grid.

    Regulators and communities will also have questions about who absorbs the cost, risk and environmental impact of these facilities.

    Bringing your own power does not eliminate infrastructure constraints. It relocates and redistributes them.

    A microgrid can reduce dependence on the utility queue, but the project still needs credible equipment, fuel, permits, controls and operating capability. The bottleneck may move from grid interconnection to turbine availability, gas supply, emissions approval or energy-storage procurement.

    There is no magic extension cord hiding behind the data center.

    A New Test of Project Readiness

    The move toward onsite power could also make the distinction between declared demand and observed readiness more visible.

    A speculative developer may submit a large electricity request to preserve a position in the grid queue.

    An execution-ready developer can demonstrate site control, financing, equipment commitments, a credible load schedule and an integrated power plan.

    One has declared demand.

    The other has evidence of deployment readiness.

    That distinction will matter as utilities, investors and regulators decide which projects deserve scarce infrastructure capacity.

    The Larger Signal

    Vertiv’s proposed acquisition suggests that energy infrastructure is no longer an adjacent concern for the data-center industry. It is becoming part of the core technology stack.

    The emerging architecture is not simply:

    Grid → Data center → Servers

    It is becoming:

    Grid + onsite generation + storage + controls → operational compute

    That creates opportunities for microgrid developers, equipment manufacturers, energy-management platforms, project financiers and specialists capable of coordinating infrastructure across traditional industry boundaries.

    It also changes the competitive landscape.

    The next generation of AI infrastructure leaders may not be the companies that merely reserve the largest amount of electricity. They may be the companies that can prove they possess an executable path from site selection to energized compute.

    The power queue is not disappearing.

    But the most serious developers are beginning to engineer their way around it.