MIS LOG IN

PGRR125

Summary

Title Update of LSIPA Compliance Attestation
Next Group
Next Step
Status Approved on 07/31/2025
Effective Dates
08/01/2025

Action

Date Gov Body Action Taken Next Steps
07/31/2025 PUCT Approved
06/24/2025 BOARD Recommended for Approval Revision Request Consideration
05/28/2025 TAC Recommended for Approval Revision Request Consideration
05/01/2025 ROS Recommended for Approval Revision Request Consideration

Voting Record

Date Gov Body Motion Result
07/31/2025 PUCT to approve PGRR125 and accompanying ERCOT Market Impact Statement as presented in Project No. 54445, Review of Protocols Adopted by the Independent Organization Passed
06/24/2025 BOARD to recommend approval of PGRR125 as recommended by TAC in the 5/28/25 TAC Report Passed
05/28/2025 TAC to recommend approval of PGRR125 as recommended by ROS in the 5/1/25 ROS Report as revised by TAC Passed
05/01/2025 ROS to grant PGRR125 Urgent status; to recommend approval of PGRR125 as amended by the 4/29/25 ERCOT comments as revised by ROS; and to forward to TAC PGRR125 and the 3/25/25 Impact Analysis Passed

Background

Status: Approved
Date Posted: Mar 25, 2025
Sponsor: ERCOT
Urgent: Yes
Sections: 5.2.2, 5.2.4 and 8D
Description: This Planning Guide Revision Request (PGRR) makes the Lone Star Infrastructure Protection Act (LSIPA) attestation in the Planning Guide consistent with the language in ERCOT’s existing Protocol Section 23, Form Q, Attestation Regarding Market Participant Citizenship, Ownership, or Headquarters in the Protocols. Specifically, it adds language that would permit an Interconnecting Entity (IE) or property owner to demonstrate compliance under LSIPA even if it has a subsidiary or Affiliate that falls under any of the citizenship or headquarter criteria of LSIPA, so long as the subsidiary does not have direct or remote access to or control of the project, the real property utilized by the project, Resource Integration and Ongoing Operations (RIOO), the Market Information System (MIS), other ERCOT systems, or any confidential data from such systems.
Reason: Regulatory requirements

Key Documents

Related Content