blog.demetriusnew.com

Tag: Infrastructure

  • The Next AI Infrastructure Bottleneck May Be Electrical Cable

    AI infrastructure is often discussed through its most visible assets: advanced chips, enormous data centers and new sources of power. But those assets only become a functioning system when the supporting electrical infrastructure is available and connected.

    Electrical cable is one of those less visible dependencies—and it may be harder to scale quickly than project announcements suggest.

    On October 22, Reuters reported that Nexans CFO Vincent Piquet said cable production capacity is emerging as a bottleneck for AI-driven data-center construction. He described global capacity as tight and said that establishing a new cross-linked polyethylene (XLPE) cable production line, known in the industry as a CV line, takes around three years. 

    That estimate needs to be read precisely. It concerns the time required to establish a new production line. It does not mean that every cable order has a three-year delivery time, nor does it establish that all cable categories are constrained to the same degree.

    Why cable matters to data-center construction

    A data center is not simply a building filled with servers. It needs electrical systems that bring power into the site and distribute it through the facility. Reuters reported that data centers require large amounts of low- and medium-voltage cable for those connections, with larger facilities consuming proportionately more medium-voltage cable. 

    That creates a timing challenge. Demand for a project’s power infrastructure can rise faster than manufacturers can add capacity. Even when a developer has secured land, financing or computing equipment, the project still depends on the availability of components needed to connect and distribute electricity.

    The mismatch is between project urgency and industrial lead time. Data-center developers may want to move quickly, while manufacturing expansion requires investment, equipment, skilled labor and time to bring new lines into service.

    Procurement is already adapting

    The Reuters report also described a change in procurement behavior: French distribution network operator Enedis has moved from annual agreements to contracts lasting six or seven years to secure cable supply. That is one example of a buyer seeking more certainty through longer commitments; it should not be generalized to every market or customer. 

    Still, it points to a wider planning question. When essential components are scarce or slow to expand, procurement becomes part of infrastructure strategy. Buyers may need earlier demand forecasts, longer supplier relationships and clearer visibility into which projects will actually proceed.

    Where the opportunity may be

    The opportunity is broader than cable manufacturing alone. It may include:

    • Manufacturers able to expand the specific cable capacity the market needs.
    • Suppliers of specialized materials, production equipment and related components.
    • Procurement teams that secure supply early and coordinate across project schedules.
    • Developers and utilities that identify long-lead electrical components before construction is underway.

    These are possible areas of opportunity, not guarantees of demand or financial returns. The specific product, market, customer commitments and ability to deliver all matter.

    Nexans’ own October 22 financial release provides a concrete company response: it said it is investing to expand medium-voltage production capacity in Europe and the United States, with data centers among the markets it aims to serve. That confirms Nexans is adding capacity in that area; it does not show that the broader supply constraint has been resolved. 

    The bigger lesson for AI scaling

    The cable story fits a recurring pattern in infrastructure development: the component that limits progress may not be the one receiving the most attention.

    AI capacity depends on a sequence of linked systems—generation, grid connections, substations, electrical distribution, cooling, buildings and computing equipment. A delay in one essential layer can affect the schedule of the whole project.

    For executives, the practical question is not only how much capacity has been announced. It is whether the critical components can be manufactured, delivered and installed on the timeline the project assumes.

    A data center can be planned in megawatts. It still has to be built one connection at a time.

  • The Next AI Power Plant May Not Look Like a Traditional Power Plant

    AI infrastructure is changing the conversation about electricity supply. Data centers need large, dependable amounts of power, while new generation and transmission can take years to plan and build. As a result, utilities and technology companies are considering a wider set of generation options.

    American Electric Power’s planned fuel-cell project near Cheyenne, Wyoming, is one example. Announced on October 14, the project is expected to provide 702 megawatts of generation for Google under a 20-year power purchase agreement. AEP estimates the investment at approximately $4 billion. Construction is planned to start in 2026, with the facility expected to be fully operational by the end of 2028. The project company, Cheyenne Fuel Cell LLC, is approximately 92% owned and controlled by AEP, with the remaining ownership held by funds advised by Basalt Infrastructure Partners. 

    Why fuel cells enter the AI power conversation

    Fuel cells generate electricity through an electrochemical process. Unlike a combustion-based generator, they do not burn fuel to produce electricity. Bloom Energy’s solid oxide systems can operate on natural gas, biogas, or hydrogen. This gives developers several possible fuel pathways, though the project’s actual fuel choice and supply arrangements matter to its cost and emissions. 

    The technology can therefore broaden the generation toolkit. A large customer may be able to contract for a dedicated source of on-demand electricity without relying solely on new conventional generation or waiting for grid upgrades to serve every increment of demand. That does not mean fuel cells replace the grid. It means they may become one part of a portfolio that includes grid supply, renewables, storage, conventional generation, and other emerging technologies.

    The scale of this project is also significant. At 702 MW, it is not a small backup installation. It is a large generation development with a substantial capital commitment and a long-term customer relationship. The structure links an energy supplier, a technology provider, an infrastructure investor, and a major electricity customer.

    The contract creates visibility, not certainty

    A 20-year power purchase agreement provides a long-term commercial framework. It signals that Google expects a sustained electricity need in the Cheyenne area and that AEP sees an opportunity to invest in dedicated generation for a large customer. Reuters also reported that Google has a separate arrangement with Black Hills Corp. for generation supporting its proposed data center in the area. 

    However, a long-term agreement does not by itself establish the final price of electricity, the project’s full risk allocation, or its performance over time. The economics will depend on details such as fuel procurement, financing, maintenance, operating costs, construction execution, and the terms that govern availability and performance. Those details are not all provided in the public announcement.

    Emissions claims need to be measured in operation

    AEP says the technology generates electricity without combustion of natural gas and that the project includes plans to integrate carbon-capture technology, with the goal of delivering near-zero-emissions power. Those statements describe the project’s design intent. They are not a published, measured operating emissions result. 

    Fuel-cell generation should not be described as inherently zero-carbon. Bloom notes that systems running on natural gas produce carbon emissions, while fuel choice affects the emissions outcome. The project’s eventual impact will depend on what fuel it uses, how that fuel is sourced, and whether carbon capture is installed and performs as expected. 

    For executives and policymakers, the useful questions are concrete:

    • What fuel will the facility use, and how secure is the supply?
    • What will the delivered power cost over the contract term?
    • What availability and reliability levels are guaranteed?
    • What emissions will be measured at the facility, including any upstream fuel impacts?
    • What carbon-capture system is planned, and how will its performance be verified?
    • What happens if construction, fuel delivery, or equipment performance falls behind plan?

    The broader signal: diversify generation, then verify performance

    The AEP–Google project illustrates a broader shift. AI-related electricity demand is encouraging new commercial arrangements and more varied generation technologies. The potential value of fuel cells is not that they solve every power constraint. It is that they add another possible source of dependable generation that can be evaluated alongside other options.

    The decision standard should remain consistent across technologies: compare delivered cost, dependable output, fuel risk, construction schedule, emissions, and operational performance. A promising configuration becomes useful infrastructure only when it can demonstrate those outcomes.

    The power plant of the AI era may look different from the traditional model. Its business case still has to pass familiar tests.

    How much dependable power will it deliver, at what cost, with what fuel and emissions profile—and can the project prove those results over time?

  • A $1.5 Billion AI Drug Deal Shows the Difference Between Price and Potential Value

    AstraZeneca’s October 15 collaboration with insitro offers a useful look at how a buyer and a specialist partner can divide payment across the life of a high-risk project.

    The announced terms include a $40 million upfront payment, eligibility for up to approximately $1.46 billion in potential discovery, development, and commercial milestone payments, and potential single-digit royalties based on global sales. AstraZeneca will have exclusive worldwide rights to advance selected programs identified through the collaboration. The milestone amount is contingent, and royalties depend on products reaching the market and generating sales. The headline value should not be read as guaranteed revenue for insitro. (astrazeneca.com)

    Three layers of compensation

    The agreement combines three types of payment, each attached to a different point in the work and risk.

    1. Upfront compensation funds the work

    The $40 million upfront payment gives the collaboration immediate economic value. It recognizes the capabilities and work brought into the partnership while providing funding before the long path from discovery to commercial sales is known.

    In this case, insitro applies its Virtual Human platform to identify causal disease biology and advance AstraZeneca-nominated targets from discovery toward development candidates. AstraZeneca leads clinical development, regulatory work, and commercialization. (insitro.com)

    That division matters. The upfront amount is not merely an hourly fee. It sits within an agreement covering specialized capabilities, research activity, and rights to pursue selected programs.

    2. Milestones tie payment to defined progress

    The potential milestone payments connect additional compensation to future discovery, development, and commercial achievements. In principle, a milestone makes payment depend on an agreed event rather than time spent.

    But a milestone is only useful if the parties define it clearly. The contract needs to say what qualifies, who verifies it, what evidence is required, when payment is due, and what happens if the project changes direction. Otherwise, “pay for progress” can turn into a dispute over what progress means.

    Milestones also create a way to share risk. The specialist partner may earn more if programs advance, while the buyer avoids paying the entire potential value before results are known. The partner, in turn, accepts that some of the potential compensation may never be earned.

    3. Royalties connect compensation to commercial performance

    Potential royalties add a longer-term layer: if a resulting medicine is commercialized and produces sales, insitro may receive a share. That is different from a payment for completing a research task. It ties future compensation to commercial performance.

    Royalties also carry more uncertainty. A program must survive scientific, clinical, regulatory, and commercial hurdles before sales exist. The deal therefore places some potential upside far into the future, where outcomes are uncertain and the value of future payments differs from cash received today.

    The value is in the partnership, not just the AI

    It would be easy to describe this as a company licensing AI and another company paying for it. That misses the broader arrangement.

    The announced collaboration combines insitro’s AI-enabled biological discovery work with AstraZeneca’s clinical development, regulatory, and commercialization capabilities. It also grants AstraZeneca exclusive worldwide rights to advance selected programs. The commercial structure reflects an exchange of capabilities, work, rights, and risk—not simply access to a model. (astrazeneca.com)

    That distinction is important for businesses selling AI-enabled expertise. Buyers rarely pay a premium just because AI was used. They pay when the work helps solve a consequential problem, produces evidence they can evaluate, and fits into a process that can turn the work into business value.

    What entrepreneurs can take from the deal

    Most consulting firms should not copy a pharmaceutical deal’s royalties or long development timeline. The transferable idea is to build a pricing structure that matches compensation to the work and the outcome.

    A business could combine:

    • A base fee for discovery, setup, access, or reserved capacity.
    • Milestone payments for defined and accepted outputs, such as a validated workflow, completed implementation, or measurable quality threshold.
    • A success fee or revenue share when the result can be measured and the provider’s contribution is clear.

    This structure should also protect both sides. Define the baseline, measurement method, data source, acceptance criteria, payment trigger, time period, and responsibilities. Address what happens when the client changes scope, delays implementation, or controls an important part of the result. Keep guaranteed compensation sufficient to fund the work, especially when results depend on external factors.

    Outcome-based pricing is not “charge more if the client gets lucky.” It is a deliberate agreement about what value means, what evidence will prove it, and how the parties will share uncertainty.

    The AstraZeneca–insitro deal makes that structure visible: some compensation is paid upfront, more may follow verified milestones, and additional upside may depend on commercial success. The headline amount captures the maximum potential under the agreement. The actual economics depend on what gets achieved.

    Entrepreneur question: Which part of your expertise could be priced around verified progress or results instead of hours alone?

  • 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.

  • 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.

  • AI May Make Grid Throughput More Valuable Than Grid Size

    For much of the recent discussion about artificial intelligence and electricity, the central question has been how much new power the country can produce.

    That question is essential. Data centers, manufacturing, transportation, and other forms of electrification are adding pressure to the power system. More generation can help meet that demand.

    But generation is only one part of the system. Electricity must also move from where it is produced to where it is needed, at the time it is needed, within the limits of the network.

    That brings a second question into focus:

    How efficiently can the existing grid move electricity to the places where demand is growing?

    Capacity is not the same as deliverability

    A grid can have electricity available somewhere in the system and still face difficulty delivering it to a particular location. Transmission congestion, constraints on individual lines, and limited transfer capability can affect how much power can move between regions.

    In practical terms, this means that the amount of electricity a system can generate does not, by itself, tell us how much electricity a particular customer or facility can reliably receive. Location and delivery capability matter too.

    This distinction is especially relevant to AI infrastructure. Data centers need large amounts of electricity at specific sites, often on demanding timelines. A national supply figure alone cannot tell a project developer whether power can reach a particular location, or when the necessary network upgrades will be complete.

    DOE’s investments highlight the delivery side

    The U.S. Department of Energy recently announced investments across 26 states. DOE says project recipients 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, the projects are expected to make more than 23 GW of additional electricity capacity available. 

    These figures describe a mix of transmission upgrades and technologies intended to improve use of the existing grid. They do not mean that all grid constraints are solved, or that new generation and new transmission will no longer be needed. They do show that improving the performance of existing infrastructure is part of the response to rising demand.

    Some grid-enhancing technologies help operators understand or control the network more precisely. Dynamic line ratings, for example, use current conditions to estimate how much electricity a line can safely carry. Power-flow control devices can help redirect electricity toward lines with available capacity. 

    These measures can help unlock capacity in existing corridors. Their usefulness depends on the specific line, operating conditions, system needs, and the ability of grid operators to deploy and manage the technology.

    The value of throughput

    It may help to think of the grid as a network with both supply and movement constraints. Adding electricity is one way to increase what the system can serve. Improving the movement of electricity is another.

    For executives and infrastructure planners, that suggests a more complete set of questions:

    1. Is generation available?
    2. Can the grid transfer it to the relevant region?
    3. Can it be delivered to the specific site?
    4. Will it be available at the times the load needs it?
    5. What upgrades are needed to make that delivery reliable?

    These questions are connected, but they are not interchangeable. A project may have access to a potential energy supply while still depending on transmission work, interconnection steps, or local network upgrades before that power is deliverable.

    For large electricity users, this has implications for site selection, project schedules, utility coordination, and the cost of bringing infrastructure online. The grid’s ability to move power can influence whether a location is practical, how quickly a project can be served, and what additional investment may be required.

    A broader view of the AI power question

    The discussion should not become a contest between building new infrastructure and improving existing infrastructure. Growing demand may call for more generation, new transmission, upgrades to existing lines, and better tools for operating the system.

    The strategic point is that grid size and grid performance are different parts of the same challenge.

    As AI infrastructure expands, the value of the grid may increasingly be measured not only by how much electricity it can produce or connect, but by how effectively it can move that electricity to the right place at the right time.

    The supply question remains important. The delivery question is becoming just as important.

  • The AI Data Center Hit a Force-Majeure Clause Because the Power Wasn’t Ready

    AI infrastructure risk is moving from the grid connection into the contract

    A data center can be announced. It can attract financing, begin construction and have a major customer waiting for capacity. Yet those facts do not, by themselves, establish that the facility will have the power it needs when it is supposed to become operational.

    A recent report about Oracle’s Project Jupiter in New Mexico puts that gap into contractual terms.

    Reuters reported on September 24 that Oracle issued a force-majeure notice to a Blue Owl unit connected to the project, citing potential delays in securing power. Reuters also reported that securing power for the site is Oracle’s responsibility under the contract. Oracle said the project remained on its planned schedule, and Blue Owl said the notice did not change its financial commitments. (reuters.com)

    That combination deserves a measured reading. The notice does not prove that the project has failed, that power is unavailable, or that the 2028 target will be missed. It does show that uncertainty around power timing has reached the parties’ contractual relationship.

    That is the larger signal.

    Planned capacity and operational readiness are different claims

    Infrastructure announcements often combine several stages into one story: investment committed, land secured, construction underway, customer demand identified, power planned.

    Those are meaningful milestones. But they do not all answer the same question.

    “Planned” capacity is not necessarily capacity that has been secured. A power arrangement is not necessarily proof that electricity will be available at the required scale and date. And a building nearing completion does not automatically mean the facility is ready to deliver computing capacity.

    Each step needs its own evidence.

    For an AI data center, the sequence may involve site development, permits, fuel or grid supply, generation or transmission infrastructure, electrical equipment, commissioning, and the final handoff into operations. A delay in one part can affect the schedule for the whole project.

    When power timing reaches the contract

    Electricity is often discussed as an operating cost: a major expense that grows as computing demand increases. But power availability can matter before a facility begins operating.

    If the power timeline affects a project’s ability to meet an operational milestone, the consequences may include delayed revenue, changed payment timing, pressure on financing assumptions, or disputes about which party carries the cost of the delay.

    In the Project Jupiter case, Reuters reported that Oracle’s notice could allow it to delay payments if the data center were derailed and did not come online as planned. The report also said the notice did not amount to Oracle exiting as the main tenant. Blue Owl said its financial commitments were unchanged. (reuters.com)

    The precise effect depends on the contract and how the parties resolve the notice. The broader point does not: power risk can become delivery risk, and delivery risk can become contractual and financial risk.

    The readiness questions executives should ask

    The lesson is not that every data-center project is in trouble. It is that a headline capacity figure is only one piece of the readiness picture.

    Executives, investors and customers should ask:

    1. What does “power secured” mean in this project?
      Is there an executed supply agreement, a completed interconnection, fuel availability, installed generation, or some combination?
    2. Who is responsible for each power milestone?
      The answer may differ across utility service, transmission upgrades, fuel supply, on-site generation, permits and equipment.
    3. What evidence supports the schedule?
      A target date is a plan. Milestone records, approvals, construction status and commissioning evidence help show whether the plan is progressing.
    4. What happens if a milestone slips?
      Review who carries the cost, which payments may change, how notice requirements work, and whether customer commitments depend on the same schedule.
    5. What is the fallback plan?
      A backup source or phased energization may reduce exposure, but only if it is technically feasible, contractually available and supported by evidence.

    The declared-versus-observed distinction applies to infrastructure

    This is the same discipline that applies to other forms of risk: separate what has been stated from what has been demonstrated.

    A project may declare a capacity target. Operational readiness asks whether the required power is available, tested and usable on the relevant timeline.

    That distinction is especially important in AI infrastructure because the project’s value depends on more than a completed building. Compute capacity must be delivered in a form customers can use, when contracts say it will be available.

    The force-majeure notice around Project Jupiter is not a final verdict on the project. It is a visible sign that the power timeline has become material enough to enter the contractual conversation.

    The next phase of AI infrastructure will be judged not only by what gets announced or financed, but by what can be energized, delivered and supported by evidence.