blog.demetriusnew.com

Category: DataCenters

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

  • FERC’s Pause on PJM’s Backstop Plan Shows Why Speed Needs Structure

    A regulatory fast-track can shorten a process. It cannot make unresolved obligations disappear.

    On September 29, FERC acted on PJM Interconnection’s proposed Reliability Backstop Procurement, or RBP. PJM designed the one-time procurement to secure additional capacity after its 2028/2029 capacity auction fell approximately 6,800 MW short of the region’s reliability target. The plan was intended to help address a near-term supply gap amid rapid load growth, including demand from data centers. 

    FERC accepted parts of PJM’s proposal but suspended it for five months, with an effective date of February 28, 2027, while opening further proceedings on unresolved provisions. PJM confirmed that the procurement would not begin on September 30 as originally planned. The commission also asked PJM to improve its data-center demand forecasts. 

    The issues are practical, not procedural trivia. PJM identified concerns around cost allocation, transmission-owner exit rules, and collateral requirements for load-serving entities. Those rules shape who bears financial exposure if the procurement moves forward, and whether the obligations remain dependable over time. 

    That makes this a useful infrastructure-planning signal: a mechanism designed to move quickly can still be delayed if its allocation of costs and risks is not sufficiently defined. FERC did not say the region does not need new capacity. Its order accepted core elements while requiring more work on how the proposal would function.

    The distinction between this case and “fast-track interconnection” also matters. The RBP is a capacity procurement. PJM’s Expedited Interconnection Track is a separate process for qualifying new generation projects, and FERC approved that track separately. Calling the RBP pause the “death of shortcut interconnections” would merge two different mechanisms and draw a broader conclusion than the order supports. 

    For developers and large energy users, the practical takeaway is to treat policy support as one input to a project plan—not as proof of available power. Before relying on a site or procurement pathway, teams should verify the relevant capacity, interconnection status, needed network upgrades, enforceable commitments, and who carries the costs if assumptions change.

    PJM’s case illustrates a broader principle: speed can help a project move, but clear rules make that speed usable. The next advantage may belong to developers who can show not only that they have a path to power, but that the path is operationally and financially credible.

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

  • AI Infrastructure Is Moving From Maximum Capacity to Maximum Certainty

    The AI infrastructure conversation has been dominated by scale: more data centers, more generation, more chips, more gigawatts.

    Scale is still essential. AI workloads need enormous amounts of compute and power. But a large capacity announcement does not, by itself, mean a project can be financed, built, connected, and operated on a dependable schedule.

    That gap is moving to the center of the conversation.

    A project’s real value depends on several linked conditions: a site that can be developed, power that can be delivered, equipment that can be procured, financing that can support the timeline, permits that can be secured, and a community willing to live with the project. If one critical dependency remains uncertain, the announced capacity may be far from usable compute.

    The signals are converging

    Recent developments point toward a more coordinated approach to AI infrastructure.

    In the United States, utility and regulatory processes are placing greater emphasis on whether large-load projects are financially ready and accountable for the infrastructure costs they create. Texas has adopted financial security requirements for large-load interconnection requests, while federal regulators have also focused on cost recovery and protections for existing customers.

    In Japan, a project involving JERA, Dell, and RHAELM brings together power capabilities, a site, data-center development, financing, and AI infrastructure. The project illustrates the appeal of planning these components as an integrated deployment rather than treating them as separate problems to solve one by one.

    Developers are also pursuing onsite generation. Recent reporting describes growing interest in smaller gas turbines and other behind-the-meter options, partly in response to equipment lead times and the challenge of securing grid connections. Onsite power may offer a different schedule path, but it does not erase the trade-offs: fuel supply, permitting, emissions, cost, and the eventual relationship with the grid still matter.

    Community relationships are becoming a more visible part of the infrastructure strategy as well. AWS recently announced a multiyear investment in programs for communities near its U.S. data centers. These commitments do not guarantee public support, but they show that local impact and engagement are now part of the deployment conversation.

    From announced capacity to predictable dependencies

    These examples are different, but they point in the same direction: the challenge is no longer just assembling enough capacity. It is coordinating the conditions that allow capacity to become operational.

    That means executives may need to ask a broader set of questions:

    • Is the power timeline credible, and what assumptions does it depend on?
    • Who pays for the upgrades needed to serve the load?
    • Are land, permits, equipment, and financing progressing on compatible schedules?
    • If grid power is delayed, what alternatives are available—and what new risks do they create?
    • How are local costs, benefits, and concerns being addressed?

    These questions do not replace the traditional focus on capacity. They make the capacity claim more useful by connecting it to execution.

    Certainty as a competitive advantage

    “Certainty” here does not mean that every project outcome is guaranteed. Large infrastructure projects will always involve uncertainty.

    It means that fewer critical dependencies are left unresolved, that assumptions are visible, and that decision-makers have a credible plan for what happens when conditions change.

    As AI infrastructure scales, the strongest projects may not be the ones with the largest headline number. They may be the ones that can show how power, capital, land, equipment, compute, and community considerations fit together—and how the project can move from announcement to operation.

    The optimization target is shifting from “How many gigawatts can we announce?” to “How many dependencies can we make predictable?”

    In AI infrastructure, certainty is becoming part of the product.

  • The New AI Infrastructure Product May Be the Repeatable Campus

    The conversation about AI infrastructure often centers on visible constraints: access to electricity, data center capacity, land, and advanced computing equipment.

    A new partnership in Japan points to a less visible constraint: the complexity of coordinating those pieces into a functioning project.

    JERA, Dell Technologies, and RHAELM have signed a memorandum of understanding to develop a standardized model for AI infrastructure in Japan. The model is planned to start with a 400 MW class hyperscale data center project in Chiba. JERA is expected to provide the site and power capacity; RHAELM leads project delivery; and Dell contributes standardized, rack scale AI infrastructure. Apollo is expected to serve as RHAELM’s strategic investment and financing partner. 

    The announcement is notable not simply because of the project’s size. It is also an attempt to treat infrastructure development as a model that could be repeated.

    Project complexity is a constraint of its own

    A large AI campus brings together systems that are often planned and delivered by different organizations. The project has to align its site, energy supply, electrical infrastructure, cooling, computing equipment, financing, construction, and operating model.

    Each interface creates work: decisions to coordinate, dependencies to manage, and potential delays to resolve. If every project requires partners to define those interfaces from the beginning, the development process can remain slow even when the necessary equipment and capital are available.

    Standardization aims to reduce some of that repeated design and coordination work. JERA describes the initiative as a standardized, repeatable model intended to integrate power generation, electrical infrastructure, cooling, and AI computing. Dell’s rack scale infrastructure is meant to standardize the compute layer, while RHAELM leads project delivery. 

    In practical terms, the goal is not necessarily to make every campus identical. It is to identify which components, decisions, and working relationships can be reused—and which must be adapted to local conditions.

    The campus as a coordinated product

    This suggests a broader way to think about AI infrastructure. The product being delivered may not be only a building, a power contract, or a rack of servers. It may be a coordinated campus model that combines those elements in a form that can be developed again.

    That model could have value if it makes future projects easier to scope, finance, engineer, and deliver. Reusing parts of the development approach could reduce the amount of project-by-project reinvention.

    This is an inference about the potential of the model, not a result the announcement has demonstrated. The MoU sets out a plan. The Chiba project will be an early test of whether the approach works in practice.

    Standardization does not erase local constraints

    A repeatable framework cannot make every location interchangeable. Each site still has its own power and grid conditions, permitting requirements, cooling needs, construction environment, financing terms, and operating considerations.

    Standardized compute infrastructure also does not, by itself, guarantee that power will be deliverable when needed or that every other part of the project will arrive on schedule. It can address a portion of the development challenge while leaving other constraints to be solved.

    That is why the most useful question is not whether standardization eliminates complexity. It is whether the partners can reduce enough of the repeated complexity to make later projects faster and more predictable.

    The real test is repeatability

    Reuters reports that the Chiba facility is expected to begin operating in phases in 2028 and reach full capacity in 2029. The companies have also described broader ambitions to develop additional AI data center capacity in Japan. Those are plans and targets; the delivery record is still ahead. 

    The evidence to watch will be concrete: whether the project advances on schedule, whether the partners reuse the model at other sites, and whether later deployments show less development friction.

    AI infrastructure still needs more power, equipment, capital, and sites. But the industry may also need a more repeatable way to combine them.

    The next AI infrastructure advantage may come from turning a complex campus project into a model that can be delivered again.

    Source note: The partnership details above are based on JERA’s October 1 announcement and Reuters’ reporting. The assessment of standardization’s potential benefits is analysis; the proposed model has not yet demonstrated repeat deployments.

  • 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 Curtailment Question Data Centers Need to Ask About Air Permits

    Grid flexibility can shift the emissions question

    As electricity demand grows, grid operators are looking for ways to manage periods when supply is tight. Data centers may be asked to reduce demand, and some emergency reliability measures can direct large customers to use onsite backup generation as a last resort.

    That creates an important distinction. A facility can reduce the electricity it draws from the grid without reducing its total energy use. If onsite engines take over some or all of the load, the grid sees a reduction in demand—but the facility has shifted where its electricity is produced.

    That shift raises an air-permitting question alongside the electrical one: What operating rules and permit conditions apply to the generators during the event?

    “Emergency generator” is a regulatory status with conditions

    Stationary engines are subject to federal requirements that can include the New Source Performance Standards for compression-ignition engines under 40 CFR Part 60, Subpart IIII, and the RICE NESHAP under 40 CFR Part 63, Subpart ZZZZ.

    For engines regulated under Subpart IIII, the rules distinguish emergency operation from other use. They generally allow up to 100 hours per calendar year for maintenance and testing, with certain non-emergency use limited to as much as 50 hours within that total. The rules restrict using that allowance for ordinary peak shaving or non-emergency demand response, while providing a narrow exception for specified local reliability dispatches.

    The details of a particular grid event matter. EPA has also stated that operation under certain 2026 Department of Energy emergency orders is considered emergency operation for covered stationary engines. Those orders apply in defined circumstances; they do not establish that every curtailment request qualifies as an emergency.

    So “the grid asked us to curtail” is not, by itself, a complete answer. The operator needs to know who issued the dispatch, under what authority or protocol, and how the facility’s permit addresses the proposed operation.

    Permitting consequences require a facility-specific analysis

    A generator’s operating classification is only one part of the permitting picture. Title V and New Source Review requirements depend on factors such as the facility’s potential to emit, pollutant totals, source aggregation, location, and applicable state rules.

    A major-source determination does not automatically mean that every facility will need the same controls. PSD applicability and its requirements—including any BACT determination—depend on the source and the proposed construction or modification. SCR, diesel particulate filters, continuous emissions monitoring, or dispersion modeling may be relevant in particular cases, but they are not universal consequences of a generator being used during a grid event.

    The same care applies to temporary generation. A portable engine used or intended to remain at one location for 12 months or longer can cease to qualify as a nonroad engine under federal rules. That fact alone does not answer every permitting question: source status, emissions aggregation, permit obligations, and enforcement depend on the circumstances and applicable requirements.

    Treat the dispatch plan as an air-permitting input

    Before relying on onsite generation as part of a demand-response or emergency plan, engineering and environmental teams should review:

    • The facility’s permit conditions and engine classifications.
    • The dispatch authority, purpose, and applicable reliability protocol.
    • Runtime limits and how testing or other operation counts toward them.
    • Potential emissions from the engines operating together.
    • Whether planned changes require agency review or a permit revision.

    There may be other ways to manage a grid event, including reducing flexible workloads, shifting computing tasks, using stored energy, or combining approaches. The right mix depends on the facility’s design, reliability obligations, grid program, and permits.

    Curtailment can help manage grid reliability. But the effect depends on what the site actually does. If the response transfers load from the grid to onsite combustion, the plan should account for the emissions and permit implications as carefully as it accounts for electrical continuity.

    The practical question is not only whether the data center can stay online. It is what powers it during the event—and whether that operating plan fits the facility’s air permit.

    Regulatory references

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

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