PGRR #35 · Revision Request
PGRR035 DC Tie Interconnection Process
- ROS withdrawn Nov 22 '13
- TAC —
- BOARD —
- PUCT —
ReasonTo formalize the Direct Current Tie (DC Tie) interconnection process in the Protocols and Guides. It is recognized that the current DC Tie definition in the Protocols is not technically correct and separate actions will be pursued to more accurately use the terms "asynchronous tie" and "DC Tie" in both the Protocols and Guides.
Created2013-11-22
Sections Affected
2.26.11 (new)7 (new)7.1 (new)7.1.1 (new)7.1.2 (new)7.2 (new)7.2.1 (new)7.2.2 (new)7.3 (new)7.3.1 (new)7.3.2 (new)7.4 (new)7.4.1(new)7.4.2 (new)7.4.3 (new)7.4.3.1 (new)7.4.3.2 (new)7.4.3.3 (new)7.4.3.4 (new)7.4.3.5 (new)7.5 (new)7.6 (new)7.7 (new)7.8 (new)7.9 (new)7.10 (new)7.11 (new)7.12 (new)7.13 (new)7.14 new)7.14.1 (new)7.14.2 (new)7.15 (new)
Summary
This Planning Guide Revision Request (PGRR) incorporates the ERCOT white paper describing the Asynchronous Tie Interconnection Process into the Planning Guides; renames the "Tie" to be "DC Tie"; and reflects the current definition of DC Tie in the Protocols. This PGRR also replaces PGRR034, Asynchronous Tie Interconnection Process, which was withdrawn on 10/28/13.
Timeline
- Nov 4
-
Nov 22
PLWG Planning Working Group (PLWG) MeetingPLWGDeferred/Tabled“Consensus to table PGRR035.”→ PLWG for consideration.
- Jan 22
-
Mar 26
Listed without action at 5 meetings (Mar 26 '14 – Aug 20 '14)
- Nov 18