MIS LOG IN

PGRR056

Summary

Title: Alignment with NPRR562, Subsynchronous Resonance
Next Group:
Next Step:
Status: Approved on 06/13/2017
Effective Dates:
09/14/2017

Sections 2.1, 3.1.2.1, 5.1.2, 5.4.1, 5.4.2.1, 5.4.5, 5.4.5.1 (delete), and 5.7.1 

07/02/2018

Section 3.1.8

Action

Date Gov Body Action Taken Next Steps
06/13/2017 BOARD Approved
05/25/2017 TAC Recommended for Approval Revision Request Consideration
04/06/2017 ROS Recommended for Approval Revision Request Consideration
03/22/2017 PLWG Recommended for Approval Revision Request Consideration
02/22/2017 PLWG Recommended for Approval Impact Analysis Consideration

Voting Record

Date Gov Body Motion Result
06/13/2017 BOARD Approved PGRR056 as recommended by TAC in the 5/25/17 TAC Report. Passed
05/25/2017 TAC To recommend approval of PGRR056 as recommended by ROS in the 4/6/17 ROS Report and as revised by TAC. Passed
04/06/2017 ROS To recommend approval of PGRR056 as recommended by PLWG in the 3/22/17 PLWG Report. Passed
03/22/2017 PLWG To endorse and forward to ROS the 2/22/17 PLWG Report and Impact Analysis for PGRR056. Passed
02/22/2017 PLWG To recommend approval of PGRR056 as revised by PLWG. Passed

Vote tallies here reflect individual votes, not the weight of the votes by market segment. Affirmative votes are not recorded in these vote tallies. For additional details on the voting record, please consult the Recommendation or Action Report, or the official vote tally if available, as posted in the key documents.

Background

Status: Approved
Date Posted: Jan 27, 2017
Sponsor: ERCOT
Urgent: No
Sections: 2.1; 3.1.2.1; 5.1.2; 5.4.1; 5.4.5; 5.4.5.1; 5.7.1
Description: This Planning Guide Revision Request (PGRR) aligns the Planning Guide with 1/27/17 ERCOT comments to NPRR562, Subsynchronous Resonance, by accounting for potential Subsynchronous Resonance (SSR) vulnerability in the transmission project planning process, providing references and citations to the appropriate Protocol sections related to SSR, and removing the definition of SSR from the Planning Guides as it is relocated to the Protocols.
Reason: Addresses current operational issues

Key Documents

Related Content