Download
1 / 14
140 likes | 275 Views
Protocol Revision Subcommittee. Report to Technical Advisory Committee January 9, 2003. Overview. SCR 727 4 Protocol Revision Recommendations 1 PRR for resubmission to Board RMR Task Force. SCR 727. ‘Take SCR 727….please!’ Priority 1.1. PRR 361 – Section 15 Update.
E N D
Protocol Revision Subcommittee Report to Technical Advisory Committee January 9, 2003
Overview • SCR 727 • 4 Protocol Revision Recommendations • 1 PRR for resubmission to Board • RMR Task Force
SCR 727 • ‘Take SCR 727….please!’ • Priority 1.1
PRR 361 – Section 15 Update • Updates Section 15 per RMS directive that Critical Care be relabeled “Special Needs” in the TXSET Implementation Guides • Conforms Section 15 to use the 814_82/29 for both Unexecutable and Permit Required for move-ins/move-outs • Effective with implementation of Version 1.5
PRR 367 – IDR Installation & Use • Clarifies that ERCOT does not install IDRs, but may request an IDR to be installed • Clarifies that the IDR would be used to calculate coincident demand as one of the components—currently refers only to “demand” • No computer system impact • Effective February 1, 2003
PRR 368 – Section 18 References • Changes the reference from “Load Profiling Operating Guides” to “Load Profiling Guides” • No computer system impact • Effective February 1, 2003
PRR 370 – RMR Contract Process • PRR 370 previously approved by TAC and forwarded to the Board • Board remanded to PRS to address the Board’s involvement in the approval process • Recommended PRR 370 includes Board Task Force recommendations • Does not reflect changes that may be recommended by the RMR TF
PRR 370 – RMR Contract Process • Board no longer involved in process to approve “multi-year contracts” or any other RMR contract • Clarifies alternatives ERCOT will evaluate prior to executing RMR agreements • Reasserts point that ERCOT will minimize use of RMR facilities (Section 6.3.1 (17)) • Sets contract term at 12 months with a 90-day cancellation notice
PRR 370 – RMR Contract Process • Clarifies applicability to include resources that would “…otherwise not be available to be operated in the ERCOT Region…” • Establishes comment period on RMR use • ERCOT will certify to the Board that the resource owner complied with the application requirements, information was posted on the MIS, consistency with Protocols and that ERCOT made the required evaluation of alternatives
PRR 370 – RMR Contract Process • Confidentiality • Makes available information pertaining to ERCOT’s assessment of whether an RMR unit satisfies ERCOT’s criteria • No impact to computer systems • Effective upon Board approval
PRR 342 – Simultaneous Select of Ancillary Services • Forwarded by TAC to Board for approval • Board remanded to PRS to review a suggested clarification of PRR 342 to clarify that the bid qualifications applied to capacity • Following lengthy discussion, PRS recommends the proposed clarifications (insert “capacity”) • PRS recommends a 1.1 priority
RMR TF Update • RMR TF examining RMR/OOM issues • Discussed three strawdogs addressing RMR/OOM applicability, pricing, cost allocation and exit strategies (transmission planning) • Will review two proposals at next meeting (January 16)
RMR TF Update • Transmission Planning Process • Openness of Regional Planning Process • Increased communication of when work product is posted/made available for comment • ERCOT has plan to formalize the transmission planning process • Acutely aware of stakeholder concerns listed above • ERCOT implementation should be monitored to ensure concerns are addressed • RMR TF may still amend Protocols to reflect portions of ERCOT transmission planning process (e.g., exit strategy)
