NPRR #364 · Revision Request
NPRR364 Clarify Active and Inactive SCED Constraint Reporting
ReasonThis NPRR clarifies Protocol language as to what should be reported regarding transmission constraint information. Network Security Analysis (NSA) is the application used to activate different constraints for economic dispatch by SCED. A constraint consists of a contingency and a monitored Transmission Element paired together. Pursuant to Protocol requirements, the NSA results are currently provided on the Market Information System (MIS) Secure Area; however, the delineation of "active" versus "inactive" is not clear in the current Protocol language. As an example, an inactive constraint is not one in which ERCOT has determined to be inaccurate or inappropriate but rather one that is present in the Transmission Constraint Manager (TCM) that has not been selected for SCED resolution by ERCOT. This NPRR provides a firm delineation for active and inactive constraints, and separates the concept from contingencies that have been rendered ineligible due to being inaccurate or inappropriate. Such invalid contingencies, or contingencies identified by ERCOT as being incorrectly defined or otherwise in error, are already being posted to the MIS per Section per paragraph (6) of Section 5.5.1, Security Sequence.
Created2011-05-19
Approved2011-10-18
Sections Affected
6.5.7.1.11
Summary
This Nodal Protocol Revision Request (NPRR) clarifies the reporting requirements for Security-Constrained Economic Dispatch (SCED) constraints and aligns the Protocols with current practices.
Timeline
- May 4 '11
- May 19 '11
- Jun 15 '11
- Jun 23 '11
-
Jul 13 '11
Listed without action at 1 meeting
-
Jul 21 '11
PRS PRS MeetingPRSRecommended for Approval Recommended for approval Amended by the Jul 14 '11 J Aron comments“To recommend approval of NPRR364 as amended by the 7/14/11 J Aron comments.” — Passed→ PRS for Impact Analysis review.
-
Aug 5 '11
Listed without action at 1 meeting
-
Aug 18 '11
PRS PRS MeetingPRSRecommended for Approval Recommended for approval Forwarded → TAC“To endorse and forward the 7/21/11 PRS Report and Impact Analysis for NPRR364 to TAC.” — Passed→ TAC for consideration.
-
Sep 1 '11
TAC TAC MeetingTACRecommended for Approval Recommended for approval“To recommend approval of NPRR364 as recommended by PRS in the 8/18/11 PRS Report.” — Passed→ ERCOT Board for consideration.
-
Oct 18 '11
BOARD Board of Directors MeetingBOARDApproved Recommended for approval“To approve NPRR364 as recommended by TAC in the 9/1/11 TAC Report.” — Passed
-
—
Posted since the last meeting