- Home
- Market Rules
- Issues
NPRR354
Summary
| Title | Revisions to Non-Spin Performance Criteria Language and Provision for ICCP Telemetry of Non-Spin Deployment |
|---|---|
| Next Group | |
| Next Step | |
| Status | Approved on 09/20/2011 |
| Effective Dates |
06/28/2012
|
Action
| Date | Gov Body | Action Taken | Next Steps |
|---|---|---|---|
| 09/20/2011 | BOARD | Approved | |
| 08/04/2011 | TAC | Recommended for Approval | ERCOT Board consideration of NPRR354 |
| 07/21/2011 | PRS | Recommended for Approval | TAC consideration of NPRR354 |
| 06/23/2011 | PRS | Deferred/Tabled | PRS Impact Analysis review |
| 05/19/2011 | PRS | Recommended for Approval | PRS Impact Analysis review |
Voting Record
| Date | Gov Body | Motion | Result |
|---|---|---|---|
| 09/20/2011 | BOARD | To approve NPRR354 as recommended by TAC in the 8/4/11 TAC Report. | Passed |
| 08/04/2011 | TAC | To recommend approval of NPRR354 as recommended by PRS in the 7/21/11 PRS Report. | Passed |
| 07/21/2011 | PRS | To endorse and forward the 5/19/11 PRS Report, Impact Analysis and preliminary Cost Benefit Analysis for NPRR354 to TAC with a recommended priority of High and rank of 31. | Passed |
| 06/23/2011 | PRS | To table NPRR354 for one month. | Passed |
| 05/19/2011 | PRS | To recommend approval of NPRR354 as amended by the 4/29/11 ERCOT comments. | Passed |
Background
| Status: | Approved |
|---|---|
| Date Posted: | Apr 15, 2011 |
| Sponsor: | WMS |
| Urgent: | No |
| Sections: | 6.5.7.6.2.3, 8.1.1.4.3 |
| Description: | 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 6.5.7.6.2.3 and 8.1.1.4.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. |
| Reason: | This NPRR is necessary to address issues realized during Nodal stabilization. The Non-Spin performance criteria in Section 6.5.7.6.2.3, paragraph (4) requires revision to make them consistent with Section 8.1.1.4.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. |
Key Documents
Apr 15, 2011 - doc - 86.5 KB
Apr 29, 2011 - doc - 58 KB
May 23, 2011 - doc - 98 KB
Jun 17, 2011 - doc - 57.5 KB
Jun 22, 2011 - xls - 183 KB
Jun 27, 2011 - doc - 99 KB
Jul 25, 2011 - doc - 100 KB
Aug 3, 2011 - xls - 185.5 KB
Aug 8, 2011 - doc - 102 KB
Sep 21, 2011 - doc - 104 KB