Pennsylvania Moves to Prime the Pipeline for PJM’s Expedited Interconnections
Developers with big balance sheets and even bigger timelines suddenly have a door cracked open: Pennsylvania’s Department of Environmental Protection issued an RFI on March 28 inviting large-scale generation and storage proposals that can credibly qualify for PJM’s proposed Expedited Interconnection Track, with responses due June 5. The state is not simply collecting paperwork; it is curating a shortlist of shovel-ready candidates that could move from queue to interconnection agreement in roughly ten months and to commercial operation within three years of filing.
The stakes are straightforward yet significant. A small number of large projects can relieve reliability pressures caused by rising demand, especially from data centers, while tempering costs to ratepayers. Moreover, the RFI has a dual purpose: find EIT-ready contenders and study strong projects that miss the bar, so Pennsylvania can design alternative pathways that keep useful capacity on a viable trajectory even without fast-track access.
From Queue Backlogs to EIT: Why Scale, Speed, and State Backing Now Decide Outcomes
PJM’s queue has been clogged for years, while load growth accelerates. In response, PJM proposed EIT, capped at up to ten requests per year through 2027, aiming to move qualified projects to an interconnection agreement in about ten months. That cadence is intended to complement broader reforms while reserving scarce study resources for the most mature, de-risked proposals.
Eligibility sends a clear signal. Projects must deliver at least 250 MW of new or uprated capacity, show state support, document full site control not only for the plant but also for the interconnection facilities, and hit a three-year COD from filing. Supporters highlight reliability and speed; opponents, including Vistra and the Sierra Club, argue the design could disadvantage IPPs and skew outcomes toward large, centralized resources at the expense of market fairness and diversity.
How Developers Can Engage Pennsylvania’s RFI and Position for PJM’s EIT
Step 1: Map Your Project to EIT Thresholds and Pennsylvania’s Priorities
Begin by pressure-testing size, technology, and schedule against EIT criteriat least 250 MW, maturity that sustains a three-year COD, and a profile that supports a diverse, affordable resource mix. Show how the project reduces costs and enhances reliability rather than merely adding capacity.
Translate this fit into a narrative that connects state goals to deliverables. Emphasize dispatchability, deliverability to constrained zones, and measurable rate impacts. Projects that articulate concrete, near-term value tend to rise above generic claims of scale.
Tip: Use a Go/No-Go Matrix to Flag Gaps on Size, Timing, and Controllable Risks
Warning: Underestimate the Interconnection-Facility Site Control Requirement at Your Peril
Step 2: Lock Down Comprehensive Site Control, Including Interconnection Facilities
EIT elevates land discipline. Provide executed options or leases for both the project site and the interconnection footprint, with documented access, easements, and substation or line tap rights. Address zoning, environmental constraints, and title encumbrances early to avoid surprises.
Tie land strategy to layout. Secure road access, construction laydown areas, and contingency parcels that preserve routing flexibility. Where eminent domain is unavailable, demonstrate alternatives that achieve the same certainty.
Insight: Early Utility Coordination Can Surface Right-of-Way Constraints Before They Derail Timelines
Tip: Pair Title Work With Engineering to Align Physical Layouts With Legal Control
Step 3: Build a Credible Three-Year COD Execution Plan
Craft a parallel-path schedule that advances permitting, procurement, and financing simultaneously. Show bankability through creditable offtake pathways, tax equity or transferability strategies, and EPC capacity that matches milestones.
Anchor the plan in locked long-lead items—transformers, breakers, inverters, turbines—and document supplier commitments. A schedule that survives component slippage and seasonal construction windows carries more weight than optimistic Gantt charts.
Tip: Secure Long-Lead Equipment Slots and EPC Capacity Before Submitting
Warning: Supply-Chain Slippage Can Invalidate EIT Readiness Even if Studies Are Expedited
Step 4: Secure and Document State Support
Demonstrate alignment with Pennsylvania’s economic and reliability objectives. Include letters of interest, program fit rationales, and evidence of coordination with agencies and local governments.
Substantiate benefits with datconstruction jobs, tax base growth, capacity accreditation, and congestion relief. Showing practical benefits where the grid is tight can convert interest into explicit support.
Insight: Tailor Benefits Cases to Local Jobs, Cost Impacts, and Grid Reliability Contributions
Tip: Align Community Benefits and Workforce Plans With State Program Expectations
Step 5: Prepare a High-Caliber RFI Response by June 5
Submit a package that reads like an investment memo: technical specifications, maturity evidence, site control documents, schedule with critical path, financing readiness, and supplier commitments. Indicate whether the project is paired with data center developers meeting responsible infrastructure standards.
Make execution discipline visible. Define risks, mitigations, and decision gates, and be candid about any EIT gaps. Transparency can invite alternative state support, not just rejection.
Tip: Use Clear Milestones and Risk Registers to Show Execution Discipline
Insight: Transparency on EIT Gaps Invites Alternative Support Paths, Not Just Disqualification
Step 6: Coordinate for a Q4 2026 Submission Window to PJM
Pennsylvania intends to align candidates for late-year filings, so sync internal approvals and state interactions with PJM windows. Calibrate corporate investment committees and financing checkpoints to those dates.
Work backward from COD to establish procurement freezes, notice-to-proceed dates, and interconnection design locks. Missing the Q4 window could force a reset that narrows access to EIT before 2027 sunsets.
Tip: Back-Cast the Schedule From COD to Define Interim Decision Gates
Warning: Missing Q4 Windows May Push You Outside the EIT’s 2027 Horizon
Step 7: Anticipate and Mitigate FERC and Stakeholder Risks
Model scenarios in which EIT terms change, conditions are added, or legal challenges slow implementation. Maintain a fallback interconnection path to preserve value if fast-track access tightens.
Document nondiscriminatory compliance, especially for resource selection and state support criteria. A robust record can withstand protests and help keep timelines intact.
Insight: A Dual-Track Interconnection Plan Preserves Value if EIT Access Tightens
Tip: Document Nondiscriminatory Criteria Compliance to Withstand Protest
Step 8: Address Equity, Community, and Resource Diversity Considerations
Engage communities early with tangible commitments—local hiring, community facilities, and mitigations for construction impacts. Design projects to minimize siting friction and to complement, not crowd out, smaller resources.
Consider hybrids and storage pairings that add flexibility and frequency response. Projects that help the grid operate smoothly tend to outcompete those that merely add megawatts.
Tip: Commit to Local Benefits and Grid-Friendly Operations in Writing
Insight: Hybrid Designs and Storage Pairings Can Broaden System Value Without Sacrificing Speed
Key Steps at a Glance
Success hinges on demonstrable EIT fit—size, speed, and ironclad site control—paired with a schedule strong enough to withstand supply swings. State support, documented and specific, binds the story.
Package all of that into a complete RFI by June 5, align for a Q4 PJM filing, and keep a dual-track backstop. Manage regulatory and equity risks through transparent benefits and strict compliance.
What This Means for Markets, Developers, and Data Centers
A narrow fast lane could bring a handful of large assets online quickly, easing reliability stress while shaping the near-term resource mix. That concentration raises policy questions, yet it also offers a pragmatic bridge through rising load.
For developers, capital strength, land positions, and EPC access now separate contenders from the field. IPPs may find partnerships—especially with data centers committing to responsible standards—useful to demonstrate state alignment and accelerate decisions.
Taking the Next Step
This guide helped teams define EIT eligibility, secure full site control, build a three-year execution plan, evidence state support, and assemble a high-quality RFI by June 5 while coordinating for a Q4 PJM submission. The most prepared sponsors also kept a fallback queue strategy, documented compliance, and embedded community benefits that resonate locally.
Looking ahead, the practical edge lay in locking long-lead equipment early, stress-testing timelines against multiple scenarios, and designing projects that provide flexibility as load grows. Those moves positioned developers to convert policy windows into bankable outcomes without sacrificing fairness or long-run resilience.
