- Home
- Market Rules
- Issues
NPRR176
Summary
| Title | Resource Status Input to RUC and Ancillary Service Awards from RUC |
|---|---|
| Next Group | |
| Next Step | |
| Status | Approved on 08/18/2009 |
| Effective Dates |
12/01/2010
or per the Nodal Protocol Transition Plan http://www.ercot.com/mktrules/protocols (09/01/09 Nodal Protocols Library) |
Action
| Date | Gov Body | Action Taken | Next Steps |
|---|---|---|---|
| 07/09/2009 | TAC | Remanded | PRS Review |
| 08/18/2009 | BOARD | Approved | |
| 08/06/2009 | TAC | Recommended for Approval | ERCOT Board consideration |
| 07/23/2009 | PRS | Recommended for Approval | TAC consideration |
| 05/21/2009 | PRS | Recommended for Approval | PRS IA Review |
| 06/18/2009 | PRS | Recommended for Approval | TAC Consideration |
Voting Record
| Date | Gov Body | Motion | Result |
|---|---|---|---|
| 07/09/2009 | TAC | To remand NPRR176 to PRS. All Market Segments were present for the vote. | Passed |
| 08/18/2009 | BOARD | To approve NPRR176 as recommended by TAC in the 8/6/09 TAC Recommendation Report | Passed |
| 08/06/2009 | TAC | To recommend approval of NPRR176 as recommended by PRS | Passed |
| 07/23/2009 | PRS | To recommend approval of NPRR176 as amended by ERCOT comments and as revised by PRS. | Passed |
| 05/21/2009 | PRS | To recommend approval of NPRR176 as amended by Luminant comments. | Passed |
| 06/18/2009 | PRS | To endorse and forward the PRS Recommendation Report and Impact Analysis for NPRR176 to TAC. | Passed |
Background
| Status: | Approved |
|---|---|
| Date Posted: | May 7, 2009 |
| Sponsor: | ERCOT |
| Urgent: | No |
| Sections: | 5.5.2, 4.4.7.4, 5.5.2 |
| Description: | This Nodal Protocol Revision Request (NPRR) provides clarity in the Nodal Protocol language. Resources committed by Day-Ahead Market (DAM) are not considered as On-Line by Reliability Unit Commitment (RUC) unless a Qualified Scheduling Entity (QSE) has changed the Resource Status to On-Line in the Current Operating Plan (COP) for that hour. During Ancillary Service insufficiency, an ERCOT Operator may commit Resources in RUC to provide Ancillary Service. If the commitment is for Ancillary Service then the QSE should be able to show the Resource in COP with "ONRUC" status and non-zero Ancillary Service Resource Responsibility corresponding to the Ancillary Service awards from RUC. |
| Reason: | Minor corrections to remove conflicting Protocol language and to clarify the intent of the Protocol. |
Key Documents
May 6, 2009 - doc - 85 KB
May 6, 2009 - doc - 41 KB
May 18, 2009 - doc - 49.5 KB
May 22, 2009 - doc - 83.5 KB
Jun 16, 2009 - doc - 45.5 KB
Jun 22, 2009 - doc - 85.5 KB
Jul 14, 2009 - doc - 88 KB
Jul 15, 2009 - doc - 66.5 KB
Jul 15, 2009 - doc - 65.5 KB
Jul 17, 2009 - doc - 69 KB
Jul 24, 2009 - doc - 116 KB
Aug 7, 2009 - doc - 100 KB
Aug 20, 2009 - doc - 102 KB