Title Clarification on NPRR978 Short-Term Adequacy Reports
Next Group
Next Step
Status Approved on 02/09/2021


Date Gov Body Action Taken Next steps
02/09/2021 BOARD Approved
01/27/2021 TAC Recommended for Approval Revision Request Consideration
12/10/2020 PRS Recommended for Approval Revision Request Consideration
11/11/2020 PRS Recommended for Approval Impact Analysis Consideration

Voting Record

Date Gov Body Motion Result
02/09/2021 BOARD to approve NPRR1048 as recommended by TAC in the 1/27/21 TAC Report Passed
01/27/2021 TAC to recommend approval of NPRR1048 as recommended by PRS in the 12/10/20 PRS Report Passed
12/10/2020 PRS to endorse and forward to TAC the 11/11/20 PRS Report and Impact Analysis for NPRR1048 Passed
11/11/2020 PRS to recommend approval of NPRR1048 as submitted Passed


Status: Approved
Date Posted: Oct 13, 2020
Sponsor: ERCOT
Urgent: No
Sections: 3.2.3
Description: This Nodal Protocol Revision Request (NPRR) changes certain reports required by Section 3.2.3 from being aggregated “by Load Zone” to being aggregated “by Forecast Zone.” “Forecast Zones”, which have the same boundaries as the 2003 ERCOT Congestion Management Zones (CMZs), consist of North, South, West, and Houston. NPRR978, Alignment with Amendments to PUCT Substantive Rule 25.505, which was approved by the ERCOT Board on February 11, 2020, revised paragraphs (3)(a), (b), (c), (g), and (h) of Section 3.2.3, which relates to short-term adequacy reports, to reflect the requirement in amended item (d) of P.U.C. SUBST. R. 25.505, Reporting Requirements and the Scarcity Pricing Mechanism in the Electric Reliability Council of Texas Power Region, that information concerning Resource availability be aggregated by Load Zone. However, during implementation planning for NPRR978, it was determined that if these reports were aggregated by Load Zone, it could enable the identification of capacity information for certain Resources that are part of Non-Opt-In Entity (NOIE) Load Zones. Aggregation by Forecast Zone aligns with current ERCOT disclosure report aggregation practice (see Section 3.2.1, Calculation of Aggregate Resource Capacity) and will comply with item (d) of P.U.C. SUBST. R. 25.505 while also protecting against the disclosure of commercially sensitive information.
Reason: Regulatory requirements

Key Documents

Related Content