1 / 11

Protocol Revision Subcommittee

Protocol Revision Subcommittee. Report to the ERCOT Technical Advisory Committee August 6, 2003. Summary. Two Urgent Timelines Five PRRs for approval One rejected PRR Status of PRR 384. Urgent Timelines Requested. PRR 442 – Profile Development Cost Recovery

nami
Download Presentation

Protocol Revision Subcommittee

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Protocol Revision Subcommittee Report to the ERCOT Technical Advisory Committee August 6, 2003

  2. Summary • Two Urgent Timelines • Five PRRs for approval • One rejected PRR • Status of PRR 384

  3. Urgent Timelines Requested • PRR 442 – Profile Development Cost Recovery • PRR 443 – Competitive Metering • Preparing to meet statutory deadline

  4. PRR 410 – Resource Obligations During BLT • Relieves ERCOT generation resources of ancillary service or other obligations to ERCOT during the time the resource is in a BLT to a non-ERCOT area • No impact to ERCOT computer systems • Effective date September 1, 2003

  5. PRR 413 – RPRS Optimization • Modifies RPRS procurement process so that RPRS procurement process is an optimum solution for the whole Operating Day • Impacts ERCOT computer systems • Priority 1.1 • Effective upon implementation

  6. PRR 422 – OOM Zonal Dispatch Instructions • Provides deployment and settlement guidance for zonal OOM dispatch instructions – currently not in protocols • Impacts ERCOT computer systems and staffing; may have manual workaround • Effective September 1, 2003; manual workaround to be explored

  7. PRR 431 – Collateral Requirements for RBS/EAL • Calculates collateral requirements for QSEs using RBS; excludes certain portions of EAL calculation from 60-Day ratchet; reduces from 3 to 2 days the period in which collateral must be posted; allows ERCOT to accelerate due dates • No impact on ERCOT computer systems • Effective September 1, 2003

  8. PRR 439 – Clarification of OOME as Instructed Deviation • Clarifies two exceptions on defining OOME as an instructed deviation • Impacts ERCOT computer system • Same priority as PRR 373 (in progress) • Effective on implementation of EMMS Release 3.2

  9. PRR 435 – Confidentiality of LSE Transaction Data • Provides confidentiality for TX Set transactions between REPs and ERCOT • PRS recommended rejection of the PRR

  10. PRR 384 – Preamble and Code of Conduct • BOD remanded to TAC/PRS to consider if preamble should be in protocol and to consider alternative language • Alternative language prepared by Laurie Pappas and Shannon McClendon • PUC issued draft Code of Conduct rule in Project 26201 • PRS recommends tabling PRR 384 until final rule is issued

  11. Action Items • Urgent Status • PRR 442 – Profiling Cost Recovery • PRR 443 – Competitive Metering • Recommend Approval • PRR 410 – Resource Obligations during BLT • PRR 413 – RPRS Optimization • PRR 422 – OOM Zonal Dispatch Instructions • PRR 431 – RBS/EAL Collateral Requirements • PRR 439 – OOME as Instructed Deviation • Affirm Rejection • PRR 435 – Confidentiality of LSE Information • Affirm Recommendation to Table • PRR 384 – Preamble & Code of Conduct

More Related