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

Protocol Revision Subcommittee

Embed Size (px)

DESCRIPTION

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 - PowerPoint PPT Presentation

Citation preview

Page 1: Protocol Revision Subcommittee

Protocol Revision SubcommitteeProtocol Revision Subcommittee

Report to the ERCOTReport to the ERCOT

Technical Advisory CommitteeTechnical Advisory Committee

August 6, 2003August 6, 2003

Page 2: Protocol Revision Subcommittee

SummarySummary

• Two Urgent TimelinesTwo Urgent Timelines

• Five PRRs for approvalFive PRRs for approval

• One rejected PRROne rejected PRR

• Status of PRR 384Status of PRR 384

Page 3: Protocol Revision Subcommittee

Urgent Timelines RequestedUrgent Timelines Requested

• PRR 442 – Profile Development Cost PRR 442 – Profile Development Cost RecoveryRecovery

• PRR 443 – Competitive MeteringPRR 443 – Competitive Metering– Preparing to meet statutory deadlinePreparing to meet statutory deadline

Page 4: Protocol Revision Subcommittee

PRR 410 – Resource Obligations PRR 410 – Resource Obligations During BLTDuring BLT• Relieves ERCOT generation resources of Relieves ERCOT generation resources of

ancillary service or other obligations to ancillary service or other obligations to ERCOT during the time the resource is in ERCOT during the time the resource is in a BLT to a non-ERCOT areaa BLT to a non-ERCOT area

• No impact to ERCOT computer systemsNo impact to ERCOT computer systems

• Effective date September 1, 2003Effective date September 1, 2003

Page 5: Protocol Revision Subcommittee

PRR 413 – RPRS OptimizationPRR 413 – RPRS Optimization

• Modifies RPRS procurement process so Modifies RPRS procurement process so that RPRS procurement process is an that RPRS procurement process is an optimum solution for the whole Operating optimum solution for the whole Operating DayDay

• Impacts ERCOT computer systemsImpacts ERCOT computer systems

• Priority 1.1Priority 1.1

• Effective upon implementationEffective upon implementation

Page 6: Protocol Revision Subcommittee

PRR 422 – OOM Zonal PRR 422 – OOM Zonal Dispatch InstructionsDispatch Instructions• Provides deployment and settlement Provides deployment and settlement

guidance for zonal OOM dispatch guidance for zonal OOM dispatch instructions – currently not in protocolsinstructions – currently not in protocols

• Impacts ERCOT computer systems and Impacts ERCOT computer systems and staffing; may have manual workaroundstaffing; may have manual workaround

• Effective September 1, 2003; manual Effective September 1, 2003; manual workaround to be exploredworkaround to be explored

Page 7: Protocol Revision Subcommittee

PRR 431 – Collateral PRR 431 – Collateral Requirements for RBS/EALRequirements for RBS/EAL• Calculates collateral requirements for Calculates collateral requirements for

QSEs using RBS; excludes certain QSEs using RBS; excludes certain portions of EAL calculation from 60-Day portions of EAL calculation from 60-Day ratchet; reduces from 3 to 2 days the ratchet; reduces from 3 to 2 days the period in which collateral must be posted; period in which collateral must be posted; allows ERCOT to accelerate due datesallows ERCOT to accelerate due dates

• No impact on ERCOT computer systemsNo impact on ERCOT computer systems• Effective September 1, 2003Effective September 1, 2003

Page 8: Protocol Revision Subcommittee

PRR 439 – Clarification of PRR 439 – Clarification of OOME as Instructed DeviationOOME as Instructed Deviation• Clarifies two exceptions on defining Clarifies two exceptions on defining

OOME as an instructed deviationOOME as an instructed deviation

• Impacts ERCOT computer systemImpacts ERCOT computer system

• Same priority as PRR 373 (in progress)Same priority as PRR 373 (in progress)

• Effective on implementation of EMMS Effective on implementation of EMMS Release 3.2Release 3.2

Page 9: Protocol Revision Subcommittee

PRR 435 – Confidentiality of PRR 435 – Confidentiality of LSE Transaction DataLSE Transaction Data• Provides confidentiality for TX Set Provides confidentiality for TX Set

transactions between REPs and ERCOTtransactions between REPs and ERCOT

• PRS recommended rejection of the PRRPRS recommended rejection of the PRR

Page 10: Protocol Revision Subcommittee

PRR 384 – Preamble and Code PRR 384 – Preamble and Code of Conductof Conduct• BOD remanded to TAC/PRS to consider if BOD remanded to TAC/PRS to consider if

preamble should be in protocol and to consider preamble should be in protocol and to consider alternative languagealternative language

• Alternative language prepared by Laurie Pappas Alternative language prepared by Laurie Pappas and Shannon McClendonand Shannon McClendon

• PUC issued draft Code of Conduct rule in PUC issued draft Code of Conduct rule in Project 26201Project 26201

• PRS recommends tabling PRR 384 until final PRS recommends tabling PRR 384 until final rule is issuedrule is issued

Page 11: Protocol Revision Subcommittee

Action ItemsAction Items• Urgent StatusUrgent Status

– PRR 442 – Profiling Cost RecoveryPRR 442 – Profiling Cost Recovery– PRR 443 – Competitive MeteringPRR 443 – Competitive Metering

• Recommend ApprovalRecommend Approval– PRR 410 – Resource Obligations during BLTPRR 410 – Resource Obligations during BLT– PRR 413 – RPRS OptimizationPRR 413 – RPRS Optimization– PRR 422 – OOM Zonal Dispatch InstructionsPRR 422 – OOM Zonal Dispatch Instructions– PRR 431 – RBS/EAL Collateral RequirementsPRR 431 – RBS/EAL Collateral Requirements– PRR 439 – OOME as Instructed DeviationPRR 439 – OOME as Instructed Deviation

• Affirm RejectionAffirm Rejection– PRR 435 – Confidentiality of LSE InformationPRR 435 – Confidentiality of LSE Information

• Affirm Recommendation to TableAffirm Recommendation to Table– PRR 384 – Preamble & Code of ConductPRR 384 – Preamble & Code of Conduct