ERCOT Large Load Batch Study Workshop Feb 26, 2026 summary

ERCOT Large Load Batch Study Workshop Feb 26, 2026 summary

Large Load Batch Study Workshop Feb 26-2026–Summary 

Author: Basit Mushtaq

Purpose of the Workshop 

The workshop focused on refining the Batch Zero framework, aligning stakeholders on governance timelines, study design, eligibility criteria, and integration with PUCT Project 58481. The primary objective being: 

  • Define scope and boundaries of Batch Zero 
  • Finalize revision request structure (NPRR / PGRR) 
  • Align governance pathway to June 1 Board approval 
  • Confirm readiness of protocol changes 
 
Technical Significance 

Batch Zero is not just a governance exercise; it is a system-wide reliability allocation mechanism that will: 

  • Determine year-by-year deliverable MW (2028–2032) 
  • Identify required transmission upgrades 
  • Establish financial security exposure 
  • Remove non-committed projects before final transmission planning 
  • Transition to a structured semi-annual batch framework 
 
Governance Pathway and Critical Timeline 
  • The critical path to implementation relies on successive May 2026 votes across PRS, ROS (if required), TAC, and the ERCOT Board. 

Key Dates 

Milestone 

Target Date 

ERCOT files Batch Zero RRs 

March 4, 2026 

PRS Vote 

May 6 

ROS Vote 

May 7 

TAC Vote 

May 19–20 

Board Approval 

June 1 

Board approval authorizes implementation of Batch Zero by approval of NPRR and any associated PGRRs, with a target effective date of August 1, 2026. 

 

Batch Zero Structural Overview 

Batch Zero is structured in two phases: a Batch Zero Study followed by a Batch Zero Refinement Study. The study applies one consistent, system-wide reliability evaluation using common assumptions, criteria, and cases. 

Phase 1 – Batch Zero Study (~6 Months) 

Study horizon: 2028–2032 by building annual cases from SSWG base cases. Evaluation includes summer peak, summer peak net load, and fall peak conditions. Core activities include: 

  • Steady-state contingency analysis 
  • Stability screening 
  • Identification of planning criteria violations 
  • Iterative coordination with TSPs on upgrades 
  • Year-by-year reliably served MW allocation 
 
Phase 2 – Batch Zero Refinement (~3 Months) 
  • Removal of non-committed loads 
  • Re-evaluation of transmission upgrades 
  • Right-sizing of transmission scope, and 
  • Preparation of the final Transmission Plan for RPG submission. 
Technical Process Flow 

Case Build (From SSWG-base cases) 
↓ 
Add Eligible Large Loads 
↓ 
Steady-State Contingency Analysis 
↓ 
Stability Screening 
↓ 
Identify Planning Violations 
↓ 
ERCOT–TSP Iteration on Upgrades 
↓ 
Year-by-Year Reliably Served MW 
↓ 
Load Commissioning Plan (LCP) 
↓ 
Developer Commitment Gate 
↓ 
Refinement Study 
↓ 
Transmission Plan to RPG 

 
Study Methodology and Reliability Framework 

ERCOT will perform a singular, system-wide reliability study applying NERC Reliability Standards, ERCOT Protocols, Planning Guide criteria, and selected contingencies. 

Allocation Logic: 

Study Year 

Allocation Treatment 

2028–2032 

Reliably served MW determined annually 

2033 

Remaining requested MW allocated 

If insufficient generation exists in the study cases, ERCOT will use the PGRR127 methodology

 
Eligibility Framework – Who Gets In? 

Eligibility is governed by fundamental principles including ERCOT’s reliability responsibility, alignment with PUCT Project 58481 gating rules, recognition of pre-transition approvals, assessment of near-term energizations, and reallocation of non-utilized capacity. 

Eligibility Decision Logic 

A. Included as Base Load 

  • Operational or approved to energize 
  • Meets full 58481 criteria 
  • Valid studies 
  • Demonstrated development activity 

Allocated MW = Based on 2025 RTP modeling or interconnection agreement limits. 

B. Studied in Batch Zero 

  • Meets intermediate criteria 
  • Has partial/complete studies 
  • Does not meet full commitment criteria 

Allocation determined by Batch Zero study results. 

C. Not Included in Batch Zero 

Loads that do not meet intermediate agreement requirements or fail to provide required information by the deadline are not included and may qualify for future batch cycles. 

 
Commitment Gate – Planning Certainty Mechanism 

Following issuance of the Batch Zero Study Report, ILLEs must execute an interconnection agreement meeting Project No. 58481 requirements. TDSP attestation triggers inclusion in the Refinement Study. Non-committed loads are removed. 

 

Controllable Load Resources (CLR) Treatment in Batch Studies 
  • CLR status will be binding during the Batch Study
  • CLRs receive full load allocation but may be required to have a minimum load amount assigned in the Batch Study process. 

 

Co-Location (BYOG) – Scenario Matrix  

ERCOT discussed multiple configurations involving Large Loads with generation. 

Scenario 

Grid Consumption 

Allocation Treatment 

Rules Needed 

Fully islanded 

No 

Full allocation 

Ensure no consumption from grid 

Temporary islanding 

Later yes 

Full allocation 

Separate exit study 

Load + dispatchable gen 

Yes 

Full allocation (except G-1+N-1) 

Link LLI + GINR 

Load + intermittent gen/storage 

Yes 

No specific rules proposed 

TBD 

Key Clarifications for Developers 

The following points were emphasized during discussion and are important for developers to understand: 

  • The MW allocations communicated to developers after the Batch Zero Study will not change during the Refinement phase.
  • The Refinement process will not increase or decrease allocated MW. It will only reassess and right-size the transmission upgrade projects based on committed loads. 
  • After Batch Zero Study results are issued, developers have 30 days to commit or withdraw. 
  • Once the ILLE executes the required commitment agreement, the developer’s financial responsibility is locked at that point. 
  • Unsynchronized backup generation will not be treated as BYOG (Bring Your Own Generation). 
  • Meeting Planning Guide Section 9.5 requirements alone does not automatically qualify a load to be treated as base load. ERCOT indicated that further clarification on this topic will be provided in future meetings.