To recommend approval of NPRR354 as amended by the 4/29/11 ERCOT comments.
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.
Apr 15, 2011
This Nodal Protocol Revision Request (NPRR) clarifies the performance criteria for Non-Spinning Reserve (Non-Spin) Service deployments, adds language for provision of a Non-Spin deployment flag to Qualified Scheduling Entities (QSEs) via Inter-Control Center Communications Protocol (ICCP), and adds a requirement for Extensible Markup Language (XML) notification to all QSEs when Non-Spin is deployed. Specifically, a clarification for the requirement that a Resource be "released to SCED" is added to Sections 22.214.171.124.2.3 and 126.96.36.199.3 to clarify the expectation of ERCOT that at 25 minutes after receipt of the deployment instruction, the Resource must be participating in Security-Constrained Economic Dispatch (SCED) at a net MW output at least equal to its Low Sustained Limit (LSL). The requirements for the three Resource types providing Non-Spin have been divided into separate paragraphs, one each for Load, On-Line and Off-Line Generation Resources. In addition, Generation Resources that are providing Non-Spin from Off-Line Generation Resources would be entitled to receive a compliance exemption for documented start-up loading failures. This language is adopted from the zonal Protocols and is included to recognize the difficulty inherent in unit start-up from a cold state for immediate deployment.
This NPRR is necessary to address issues realized during Nodal stabilization. The Non-Spin performance criteria in Section 188.8.131.52.2.3, paragraph (4) requires revision to make them consistent with Section 184.108.40.206.3, paragraph (3). The full deployment of Non-Spin capacity must be released and available for SCED within 25 minutes. The current XML notification of Non-Spin deployment is not adequate for such a crucial operating parameter due to the high volume of XML notifications that normally occur. By relying on an XML notification, the QSE’s awareness of the need to start Resources for system reliability in response to a market notification can be delayed. The Non-Spin deployment flag communicated via ICCP is necessary to immediately notify the QSEs of Non-Spin deployments when timely deployment of Off-Line Resources is critical to provide capacity for system reliability.