blog.demetriusnew.com

Category: PowerGrid

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

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

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

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

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

    From stakeholder ballot to regulatory review

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

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

    What the standards address

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

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

    The governance question for executives

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

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

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

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

    A first phase, not the finish line

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

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

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

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

  • Time to Power: Why Grid Delays Can Become Contract Risk for AI Infrastructure

    AI infrastructure projects are often described through large, attention-grabbing numbers: megawatts, GPUs, investment totals and planned opening dates. But those figures only tell part of the story. For a customer planning cloud or AI services, capacity matters when it is ready to use.

    The planned Nscale site in Loughton, Essex, offers a concrete example of how the schedule can break down.

    Reuters reported that Microsoft withdrew from its agreement for capacity at the site after the expected grid connection slipped into the 2030s. Nscale had planned a facility with 50 MW of AI capacity, scalable to 90 MW, and approximately 23,040 Nvidia GB300 GPUs for Microsoft Azure. The original announcement anticipated GPU delivery beginning in early 2027. 

    Microsoft said its decision related to one site and reaffirmed its wider partnership with Nscale. Nscale said it remained committed to Loughton and was exploring alternative power sources and other UK expansion sites. The public reporting does not disclose the contract’s terms, the exact termination provision or the financial consequences for either party. 

    A project schedule depends on more than construction

    Data centre readiness depends on several linked pieces: the building, electrical equipment, cooling, network connectivity, hardware and sufficient power. If one critical dependency arrives years later than planned, the rest of the investment may not produce its expected value on schedule.

    That creates commercial consequences. A late power connection can postpone the point when a customer can use capacity, delay revenue, extend the time capital is tied up and create uncertainty about whether demand will still be there when the site is ready. These are general project risks; the publicly available details do not establish which of them applied to this specific agreement.

    Why this can become a contract issue

    Long-term infrastructure agreements have to allocate the risks of delay. Executives and project teams should understand how the contract treats power availability, delivery milestones, delay thresholds, customer remedies and termination rights.

    The questions are practical:

    • Is the power date confirmed, estimated or dependent on future grid work?
    • What happens if service begins later than the customer’s required date?
    • Is there a defined long-stop date after which a party can exit?
    • Can capacity be moved to another site or supplied from another source?
    • Who bears added costs while the project waits?

    These are questions to raise during commercial and legal review—not assumptions about the terms of Microsoft’s agreement.

    The executive takeaway

    A planned megawatt figure doesn’t guarantee usable capacity on the date a business needs it. Time to power affects whether a project can support customer commitments and whether its economics still work when the facility is ready.

    The better diligence question is not only, “How much AI capacity will this project deliver?” It is also, “When will power be available, how certain is that date, and what happens contractually if it moves?”

    In AI infrastructure, the power schedule belongs in the commercial plan from the start.

  • 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 Grid Can Track AI Demand. But Who Has Authority to Control It?

    FERC’s PJM decision separates load visibility from curtailment authority

    The growth of AI infrastructure is making electricity demand harder to forecast and plan around. Large data centers can require hundreds of megawatts, ramp up over time, and depend on power arrangements that affect regional reliability planning.

    On October 9, 2026, the Federal Energy Regulatory Commission (FERC) took a step toward improving visibility into that demand. It approved PJM Interconnection’s definition of a “Large Load” and its proposed Large Load Registry. At the same time, FERC rejected much of PJM’s broader proposal for providing interim service to new large loads, including provisions related to curtailment. (elibrary.ferc.gov, utilitydive.com)

    The decision highlights an important regulatory distinction: collecting information about large electricity users is different from deciding when their service can be interrupted.

    What the registry is meant to show

    PJM’s approved definition covers end-use customer load with a cumulative peak of at least 50 megawatts at a single electrical site. The registry is designed to collect information such as a facility’s location, ramp schedule and capacity supply. That information can help PJM understand how large loads may affect forecasts and reliability planning. (elibrary.ferc.gov, utilitydive.com)

    A registry improves visibility. It can help answer questions such as:

    • Where is major new demand expected to connect?
    • How quickly is that demand expected to ramp up?
    • What capacity supply is associated with the load?

    Those are important planning questions. But data collection does not itself create an operational curtailment rule or settle which regulator has authority over a retail customer’s service.

    Why FERC rejected the broader proposal

    PJM’s filing also proposed an Interim Resource Adequacy Service framework for certain new large loads. Under parts of that proposal, eligible loads that did not bring their own new capacity could face load-reduction requests as the system approached an emergency.

    FERC rejected that framework. The Commission said several provisions appeared to place obligations directly on large loads that are, for the most part, retail customers; to dictate which retail customers would be curtailed; and to establish a retail compensation rate. It also found that PJM had not adequately shown that the proposed treatment of those loads would avoid undue discrimination. (utilitydive.com)

    This is where jurisdiction matters. FERC oversees interstate transmission and wholesale market rules. States have a central role in regulating retail electricity service, including determining which retail customers may be curtailed when the system is stressed. FERC’s order treated the issue as a shared regulatory challenge, not as a simple question of whether grid operators can see or manage demand. (utilitydive.com)

    What the decision does—and does not—mean

    The order does not mean large data centers are exempt from every form of curtailment, or that emergency load reduction is off the table. It addresses the specific tariff framework PJM proposed in this filing. FERC also gave PJM direction on issues it would need to address if it revises and resubmits parts of the proposal. (utilitydive.com, headwaterswire.com)

    The distinction is between three separate layers:

    1. Visibility: identifying large loads and gathering information about them.
    2. Grid operations: maintaining system reliability as supply and demand change.
    3. Decision rights: determining which customers can be asked or required to reduce demand, under what rules, and with what protections.

    The registry advances the first layer. The order shows that the third requires careful coordination across federal and state authority, as well as rules that can be defended as fair.

    The governance question behind AI power demand

    For AI infrastructure, the practical issue is not only how much electricity a facility may use. It is also whether the grid and regulators have clear, workable rules for what happens when demand exceeds available supply.

    That requires a complete chain: reliable information about large loads, transparent criteria for reliability actions, clear responsibility for issuing those actions, and consistent treatment across customer classes. Without that chain, the grid may know where demand is growing while decision-makers remain uncertain about who can require it to change.

    The registry can help the grid see the load. It cannot, by itself, determine who has authority to control it.

    Source: FERC, Docket ER26-3515-000, order issued October 9, 2026.

  • 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

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

  • AI Infrastructure Is Developing Its Own Social Contract

    The rapid expansion of artificial intelligence is often discussed as a technical race.

    Who has the most advanced chips? Who can build the largest models? Who can secure enough electricity? Who can bring new computing capacity online fastest?

    But another constraint is emerging—one that cannot be solved by ordering more GPUs or signing another power-purchase agreement.

    AI infrastructure is confronting the question of public legitimacy.

    Across the United States, communities, regulators, utilities, and lawmakers are renegotiating the conditions under which large data centers will be permitted to consume local resources and reshape regional infrastructure.

    The emerging message is not simply, “Do not build.”

    It is closer to this:

    You can build enormous AI infrastructure—but the right to build at that scale may increasingly come with obligations to pay attributable costs, disclose resource requirements, respond flexibly during grid stress, and prove that promised behavior occurred.

    That begins to resemble a social contract.

    The Debate Has Reached Spartanburg

    The issue is no longer theoretical in Spartanburg County, South Carolina.

    County officials approved a one-year moratorium affecting data-center applications that had not been finalized while the county evaluates appropriate locations and future development standards.

    At the same time, residents and environmental groups have challenged aspects of a separate computing-center project already being developed at the former Kohler manufacturing site. The concerns surrounding that project include its proposed expansion, onsite generation, air emissions, noise, and the transparency of the approval process.

    These are technically separate matters, but together they illustrate the same governance gap.

    Communities are being asked to make long-term infrastructure decisions while basic questions may still be contested:

    Who owns the project?

    How much electricity will it ultimately require?

    Will the power come from the public grid or onsite generation?

    How much water will be consumed?

    What emissions, noise, or land-use effects will accompany it?

    Which infrastructure costs will be paid by the developer, and which could eventually reach existing customers?

    What benefits will remain in the community after construction is complete?

    When those answers arrive late, change during development, or remain buried inside fragmented proceedings, distrust should not be surprising.

    The problem is not merely a communications failure. It is an evidence failure.

    From Economic Development to Cost Attribution

    For years, data centers were commonly presented through the language of investment, construction activity, tax revenue, and technological competitiveness.

    Those benefits still matter.

    But officials are now asking a second set of questions: What costs are being created, and who will pay them?

    In September 2026, the U.S. House passed the Ratepayer Protection Act with overwhelming bipartisan support. The legislation would require state utility regulators to consider whether large electricity users, including data centers, should bear the incremental infrastructure costs required to serve them.

    The measure may not settle the issue by itself, but its political significance is difficult to miss.

    The national conversation is moving from whether AI infrastructure is economically valuable to whether its costs are being allocated fairly.

    That is an important shift.

    If a private facility requires new substations, transmission capacity, generation resources, water-system upgrades, or other dedicated infrastructure, existing residents and small businesses will increasingly question why those costs should be socialized while the project’s financial returns remain private.

    “Who benefits?” is being joined by “Who pays?”

    Transparency Is Becoming a Condition of Operation

    Resource disclosure is also moving closer to the center of the regulatory bargain.

    California recently enacted a package of laws requiring greater reporting around data-center electricity and water use, while strengthening protections intended to prevent infrastructure costs from being shifted onto ordinary ratepayers.

    Virginia has proposed an accountability framework addressing project secrecy, environmental effects, and electricity costs, including restrictions on certain nondisclosure agreements.

    Different states will take different approaches, but the direction is becoming visible.

    Communities are losing patience with being asked to approve projects based primarily on economic projections while detailed resource requirements remain confidential, incomplete, or subject to later expansion.

    For major AI infrastructure, transparency can no longer be treated as a public-relations accessory.

    It is becoming part of the operating model.

    Flexibility Could Change the Bargain

    The industry is also developing a possible response to grid concerns: treating data centers as flexible loads rather than permanent, inflexible demand.

    A flexible data center could reduce its draw from the grid during constrained periods by shifting computing workloads, using batteries, drawing from approved onsite generation, or temporarily curtailing noncritical activity.

    That could make a facility more valuable to the grid and potentially reduce the need for some infrastructure expansion.

    The idea has enough momentum that Google, Nvidia, Emerald AI, utilities, power producers, and other organizations have formed the AI Energy Management Alliance to advocate for grid-enhancing data centers.

    But there is a major difference between claiming flexibility and delivering it.

    If a data center receives faster interconnection, preferential pricing, tax incentives, or regulatory accommodation because it promises to reduce demand during grid emergencies, that commitment cannot remain a sentence in an application.

    It must become an auditable operational obligation.

    A credible framework would need to record:

    • The grid condition or authorized curtailment event.

    • The time the response was requested.

    • The facility’s baseline demand.

    • The amount of load reduction promised.

    • The reduction actually delivered.

    • The duration of the response.

    • Any exception or failure to perform.

    • The process used to verify and report the result.

    This is the same distinction that appears throughout governance:

    Declared flexibility describes what the operator says the facility can do.

    Observed flexibility records what the facility actually did when the system was under stress.

    Only the second one can support a defensible decision.

    A Permit Is Not the Same as Legitimacy

    Companies sometimes treat permitting as the final boundary: if the project meets the formal requirements and receives approval, construction should proceed.

    Legally, that may be sufficient.

    Operationally and politically, it may not be.

    A permit provides legal authorization. A social license reflects continuing public acceptance of the conditions under which the facility operates.

    That acceptance can weaken when project ownership is unclear, resource requirements expand, promised benefits fail to materialize, or community costs appear only after approval.

    The result is not limited to protests.

    It can produce moratoriums, litigation, delayed permits, stricter tariffs, lost incentives, and political pressure for broader regulation.

    For developers, transparency and verifiable performance are therefore not simply compliance expenses. They are forms of project-risk management.

    The Emerging Social Contract

    The developing bargain for AI infrastructure appears to contain four core obligations.

    1. Pay attributable costs

    The costs created specifically to connect and serve a major facility should be identified rather than quietly distributed across existing customers.

    2. Disclose resource requirements

    Communities need credible information about electricity, water, land, emissions, noise, ownership, incentives, and expected local benefits before—not after—the central decisions are made.

    3. Operate as a responsible grid participant

    Where technically possible, large facilities should be capable of shifting or reducing demand during constrained conditions instead of treating the grid as an unlimited resource.

    4. Prove performance

    Flexibility, efficiency, and community-benefit commitments should produce evidence that regulators, utilities, and the public can independently review.

    These expectations will not look identical in every jurisdiction. A facility in South Carolina will face different resources, grid conditions, and community priorities than one in California, Texas, or Virginia.

    But the governing principle is likely to remain consistent:

    The greater the infrastructure footprint, the greater the obligation to make its costs, behavior, and benefits visible.

    Infrastructure Governance Is Catching Up

    AI companies are not wrong to argue that data centers are strategically important. Compute capacity will influence economic competitiveness, scientific research, national security, and the development of new industries.

    Communities are also not wrong to ask what they are being required to contribute—and what safeguards accompany that contribution.

    Those positions do not have to be mutually exclusive.

    The mature path is neither unrestricted development nor reflexive prohibition.

    It is governed development: clear conditions, attributable costs, transparent resource claims, measurable operating commitments, and evidence that those commitments were fulfilled.

    The next generation of AI infrastructure will not be judged only by how much computing power it produces.

    It will be judged by whether it behaves like infrastructure worthy of public trust.

    That is the quiet thesis underneath the current disputes:

    AI infrastructure is developing its own social contract.

    And the companies that understand that early may find it much easier to earn both a grid connection and a durable place in the communities expected to host them.

  • Declared Flexibility vs. Observed Flexibility: The Next Credibility Test for AI Infrastructure

    The AI infrastructure conversation is beginning to mature.

    For much of the current buildout, attention has centered on announced investments, proposed data-center capacity, land acquisitions, power agreements, and projected electricity demand. But as projects move closer to construction and operation, the market is learning to distinguish what has been declared from what is actually available.

    Announced capacity is not the same as energized capacity.

    A similar distinction is now emerging around power flexibility.

    Data-center developers increasingly describe their facilities as flexible loads capable of shifting computing workloads, discharging batteries, using on-site generation, or reducing electricity consumption when the grid becomes constrained.

    Those capabilities could create significant value. They may allow utilities to connect large facilities faster, use existing grid infrastructure more efficiently, protect reliability during periods of stress, and defer some expensive system upgrades.

    But a stated ability to curtail power is still only a claim.

    The more important question is whether that flexibility can be observed, measured, and repeated during actual grid events.

    From Flexible Design to Verified Performance

    The AI Energy Management Alliance, launched by Emerald AI, Google, and NVIDIA, is advancing data centers that can dynamically manage their electricity use in response to grid conditions.

    Its approach is notable because it is described as technology-neutral and performance-based. The focus is not limited to which batteries, generators, workload-management platforms, or cooling systems a facility installs. The focus is on the measurable service the facility can deliver.

    That includes response speed, duration, predictability, and behavior during emergencies.

    This is an important shift.

    A data center may be technically capable of reducing its electricity demand under controlled conditions. That does not automatically prove it will deliver the promised reduction when the regional grid is under stress, temperatures are extreme, equipment availability has changed, and computing demand is high.

    Technical capability must eventually become operational evidence.

    What Observed Flexibility Should Show

    If a facility commits to curtailing 100 megawatts during a grid emergency, verification should extend beyond confirming that a control system received the request.

    Operators and regulators may need evidence showing:

    • The facility’s electricity demand before the event
    • The amount of load actually reduced
    • The time between the grid signal and the response
    • How long the reduction was maintained
    • Which energy resources or workloads produced the reduction
    • Whether essential computing services remained within agreed performance limits
    • Whether electricity demand rebounded sharply after the event
    • Whether the facility can reproduce the result across multiple events
    • Which exceptions, failures, or overrides occurred
    • Whether the supporting telemetry and records are complete and auditable

    The baseline also matters.

    A facility should not receive full credit for a reduction that would have occurred anyway because workloads had already declined. Without a credible baseline, flexibility measurements could become another version of inflated announced capacity: technically documented but operationally misleading.

    Benefits Should Follow Evidence

    The alliance argues that credible and verifiable flexibility commitments could support faster, risk-adjusted interconnection pathways.

    That proposition makes sense. A data center that can reliably reduce its load during a limited number of critical hours may impose a different risk on the power system than a facility requiring maximum electricity delivery around the clock.

    However, any preferential treatment should be connected to continuing performance.

    Faster interconnection should not be granted solely because a developer includes flexible-load language in an application. The commitment should be defined before connection, monitored during operation, and reassessed as equipment, workloads, software, ownership, and grid conditions change.

    Otherwise, flexibility becomes a one-time qualification rather than an ongoing operating obligation.

    A defensible model would connect the lifecycle:

    Declared capability → tested capability → observed grid-event performance → verified record → continued authorization

    If performance falls outside the agreed limits, the system should identify the variance and determine whether operating conditions, interconnection terms, or incentives need to change.

    Flexibility Is Becoming a Governance Question

    This issue extends beyond electrical engineering.

    Once data-center flexibility influences interconnection priority, infrastructure spending, electricity rates, or reliability planning, the underlying evidence becomes a governance concern.

    Someone must establish:

    • What was promised
    • How performance is measured
    • Who can verify the result
    • What exceptions are permitted
    • How failures are recorded
    • When a commitment must be retested
    • What happens when observed performance no longer matches the declaration

    That is the same pattern appearing across AI governance more broadly.

    A policy is not proof of enforcement.

    A control is not proof of execution.

    A resolved incident is not proof of correction.

    And a declared flexible load is not proof of grid-responsive performance.

    The Next Infrastructure Advantage

    Flexible AI data centers could become valuable grid participants rather than passive sources of rapidly growing demand. The technical potential is increasingly credible: research and demonstrations have shown that AI workloads can be shifted or curtailed while protecting priority services. (arxiv.org)

    But the long-term value will depend on whether flexibility survives contact with real operating conditions.

    The data centers that gain an advantage may not be those making the largest flexibility promises. They may be those capable of producing a consistent, independently reviewable record showing what happened when the grid actually needed them.

    The market is moving from declarations toward evidence.

    Announced capacity must become energized capacity.

    Flexible design must become verified response.

    And declared flexibility must become observed flexibility.

  • AI Infrastructure Is Moving From Declared Capacity to Observed Readiness

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

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

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

    That distinction is becoming increasingly important.

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

    The scale is extraordinary.

    So is the uncertainty.

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

    Declared capacity is not delivered capacity

    Declared capacity describes intention.

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

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

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

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

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

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

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

    Both may claim the same number of megawatts.

    They do not represent the same level of readiness.

    The market is beginning to demand proof

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

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

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

    These are not merely administrative obstacles.

    They are attempts to convert projections into evidence.

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

    A signed lease establishes customer commitment.

    An upfront payment gives the applicant something meaningful to lose.

    A power agreement identifies a plausible energy source.

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

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

    Observed readiness is a chain, not a single document

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

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

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

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

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

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

    Scale depends on the entire chain surviving.

    Readiness may become a competitive asset

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

    The next phase will likely be more discriminating.

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

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

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

    The advantage will not come from possessing the boldest forecast.

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

    From projection to proof

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

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

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

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

    That is the transition from declared capacity to observed readiness.

    Gigawatts will remain the headline.

    Evidence will increasingly determine which ones get built.