The bill directs the Federal Energy Regulatory Commission to implement a shared‑savings incentive that returns a portion of quantified cost savings from investments in grid‑enhancing technologies (GETs) back to the entity that pays to install them (the “developer”). It also requires standardized congestion reporting from transmission operators and tasks the Department of Energy with an application guide and technical assistance for deploying GETs.
This package attempts to change investment incentives for non‑wire transmission solutions by creating a predictable financial reward for private actors who install GETs, while creating new data and planning tools for regulators and utilities. Compliance officers and grid planners should watch the rulemaking hooks that will define eligibility, measurement, and the consumer protections that govern how savings are calculated and shared.
At a Glance
What It Does
The bill requires FERC to promulgate a rule establishing a shared‑savings incentive that returns a fixed portion of savings from GET investments to the installing developer, and it imposes standardized annual congestion reporting on transmission operators. It also directs DOE to publish an application guide, operate a clearinghouse, and offer technical assistance for GET projects.
Who It Affects
Transmission owners and operators, entities that fund GET installations (developers), FERC and DOE staff, and any parties participating in regional transmission planning. Vendors of GET hardware and software, and utilities that plan investments to relieve congestion, are directly affected.
Why It Matters
By attaching a monetized, predictable incentive to GET deployment and requiring consistent data on congestion, the bill aims to make non‑wire solutions more bankable and visible in planning processes—potentially shifting where and how transmission investment decisions get made.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill creates three distinct but coordinated tracks: a FERC shared‑savings incentive for GET installers, a new universal congestion‑reporting regime, and a DOE‑run application guide and technical assistance program. For the incentive, the bill defines a “developer” as the party that pays to install the GET and directs FERC to write a rule implementing section 219(b)(3) of the Federal Power Act.
That rule will set the mechanics for returning a portion of the benefits produced by the GET back to the developer rather than leaving all savings to the transmission owner or system operator.
The incentive is procedural as much as financial: FERC must specify how to measure “savings” and how to quantify the cost of a GET investment. The bill insists that the Commission apply the same incentive percentage across eligible GET investments (rather than negotiating per‑project), requires a limited recovery window for the money returned to developers, and bars application of the incentive to GETs already in service when the law takes effect.
The Commission also must design consumer protections and define which costs may be counted (explicitly allowing permitting and installation costs among those inputs).Separately, the statute compels transmission operators to submit annual congestion reports under a protocol FERC must adopt; the required data include the causes of constraints that produce measurable costs and whether planned upgrades will address them. FERC and the Department of Energy will use the data to run analyses and produce a publicly available, annually updated map of congestion costs to improve transparency for planners and market participants.Finally, DOE must assemble practical materials for utilities and installers: an application guide, an annually updated clearinghouse of completed projects, and technical assistance on request.
The law also authorizes modest appropriations for DOE to stand up and sustain that work. Together, the measures seek to reduce information barriers, standardize measurement, and provide a predictable commercial return that makes GET investments more attractive to third‑party funders.
The Five Things You Need to Know
FERC must issue a final rule within 18 months of enactment to implement the shared‑savings incentive under section 219(b)(3) of the Federal Power Act.
The Commission must set a single shared‑savings percentage applied consistently across eligible GET investments that falls between 10 percent and 25 percent.
The statute requires that any returned savings to a developer be paid out over a fixed 3‑year recovery period.
A GET investment is eligible for the incentive only if FERC determines the expected savings over that 3‑year period are at least four times the investment cost; the statute directs the Commission to define how to quantify both costs and expected savings.
Transmission operators must report annually on congestion, identifying each constraint that caused more than $500,000 in associated costs and the planned upgrades (and FERC and DOE must publish an annually updated public map using that data).
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Gives the Act two short names used throughout the statute. This is a standard drafting provision and does not alter substantive obligations or deadlines in later sections.
Definitions (Commission, GET, Secretary)
Clarifies the statute’s core terms: the Federal Energy Regulatory Commission, the Secretary of Energy, and a broad functional definition of 'grid‑enhancing technology' that covers hardware or software added to transmission systems to increase capacity, efficiency, reliability, resilience, or safety. The practical import is that many kinds of sensing, control, topology optimization, dynamic line rating, and power‑flow management systems will likely qualify if they fit the listed functions.
Shared‑savings incentive: rulemaking, eligibility, and limits
Directs FERC to promulgate a rule establishing an incentive that returns a portion of the savings from GET investments to the installing developer. Key mechanics the Commission must resolve include the uniform percentage (statute caps it at 10–25 percent), the three‑year payback window, the prohibition on retroactive application to GETs already installed, and the threshold test requiring expected savings to be at least four times the investment cost. The section also tasks FERC with defining measurement approaches, deciding which costs count toward eligibility, and setting consumer protections—so the rulemaking will combine technical metrology, cost accounting, and rate‑design choices.
Congestion reporting, metric rulemaking, and public map
Requires transmission operators to submit annual reports on congestion costs per a universal metric that FERC must adopt. Reports must flag constraints that incurred more than a specified dollar impact, document causes and the next limiting element, and identify planned upgrades. FERC and DOE must publish the underlying data and jointly produce and annually update a public map showing where congestion costs are concentrated—tools meant to improve transparency for planners and private investors weighing GET deployments.
DOE application guide, technical assistance, and funding
Directs DOE to publish an application guide for utilities and developers, maintain an annual update cycle, offer technical assistance on request, and establish a clearinghouse of completed GET projects for reuse of lessons learned. The section authorizes upfront and continuing appropriations to operate the program, signaling that DOE will play an active implementation role beyond simple guidance.
This bill is one of many.
Codify tracks hundreds of bills on Energy across all five countries.
Explore Energy in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Third‑party developers and vendors of GETs — they gain a predictable, monetized return stream tied to measured savings that can improve project bankability and support financing deals.
- Transmission planners and regional planners — the statutory data collection and public congestion map provide consistent, system‑level information to identify non‑wire alternatives and inform long‑term planning.
- Smaller utilities and municipal systems seeking non‑wire options — the DOE clearinghouse and technical assistance lower transaction costs and provide replicable project examples that can reduce development risk.
Who Bears the Cost
- Transmission owners and ratepayers — shared‑savings payments reduce the portion of system savings retained by utilities and could be recovered through rates in ways that require allocation decisions (creating potential rate impacts).
- FERC and DOE — both agencies must develop new rulemakings, metrics, public maps, and an assistance program, producing administrative and staffing costs beyond existing workloads.
- Developers and vendors — while eligible for returns, they face upfront measurement, reporting, and compliance obligations (e.g., demonstrating savings meet the 4x threshold and furnishing data for audits), which raise transaction costs for smaller firms.
Key Issues
The Core Tension
The bill seeks to accelerate private deployment of GETs by paying installers from measured system savings, but doing so requires precise, enforceable measurement and accounting; the central dilemma is balancing a simple, predictable incentive structure (uniform percentage, short payback) that drives deployment against the technical reality that benefits and costs of GETs vary widely by technology, location, and time—so a rule simple enough to administer may under‑compensate valuable projects or over‑reward marginal ones.
The bill places a heavy evidentiary burden on FERC to produce robust, economically sound measurement rules. Translating the phrase 'savings attributable to an investment' into an auditable, reliable metric raises difficult attribution questions: how much of a reduction in congestion or avoided upgrade cost is due to a single GET versus market changes, demand shifts, or concurrent upgrades?
The requirement that FERC quantify expected savings and investment costs for a 3‑year window means the agency will need modeling conventions and baseline definitions that can withstand litigation and stakeholder challenge.
A second tension is the statute’s insistence on a uniform percentage across all eligible GETs and a steep eligibility gate (expected savings at least four times costs). Uniformity simplifies administration and reduces gaming but ignores heterogeneity across technologies, regions, and project roles—some GETs may produce long‑tail system benefits or reduce downstream costs only over longer horizons and thus fail the 3‑year×4 test despite being socially valuable.
Likewise, excluding GETs already in service eliminates retroactive rewards for early adopters and may disincentivize incremental pilots before the rule takes effect. Finally, the public map and data transparency objectives must be balanced against security and confidentiality concerns (e.g., revealing operational limits or grid topology), and the statute leaves the design of consumer protections and data redaction largely to FERC’s discretion.
Operationally, coordination with Order No. 1920's regional planning mandates is necessary to avoid double recovery or inconsistent treatment of GETs between planning and incentive streams. The evaluation and sunset provision creates an explicit checkpoint but delegates the thorny alignment issues to FERC and stakeholders during the post‑implementation review period.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.