1 / 19

Joint Operating Guides WG

Joint Operating Guides WG. Who we are What we’ve done What we plan to do Questions we have Jan 11 Update. ERCOT Documentation. Protocols - Describe the rules which all Market Participants must abide by

hani
Download Presentation

Joint Operating Guides WG

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. Joint Operating Guides WG Who we are What we’ve done What we plan to do Questions we have Jan 11 Update

  2. ERCOT Documentation • Protocols - Describe the rules which all Market Participants must abide by • Operating Guides - Describe the relationship and interactions between ERCOT and QSEs and TDSPs to ensure system reliability and security • ERCOT Procedures - Describe the specific actions of ERCOT Operators

  3. Proposed Outline for NEW System Operating Guides 1. Introduction Document Structure Process for Revision Entity Definition and Roles 3. ERCOT System Operations 4. Operational Interfaces with ERCOT A. QSE / Generation Entities B. TDSP 5. Emergency Operations

  4. Appendices A. Operational Metering B. Communications (Voice and Data) C. Forms D. Planning Criteria E. Training

  5. Completed Activities • Reviewed existing Operating and Market Guides for applicability to new market • Prepared first draft revision of applicable existing Guides to comport with new market • Developed outline of New Operating Guides • Determined all references to “Operating Guides” contained in Protocols -- To be reviewed for Jan. revisions.

  6. More Completed Activities • Complete document (version 0.2) distributed to TAC, ‘old’ subcommittee members, TF chairs • Guides Workshop held Jan 9 • Reviewed Part 3 and 4 • WG+ met Jan 10 - reviewed rest of document, and comments from Jan 9. • Identified missing pieces • Preliminary discussion of A/S quantity determination.

  7. Direction Headed • Guides will be organized by Entity responsibility, not Activity • Exception is Emergency Operations • Guides will be a ‘complete’ document • Requires the inclusion of Protocol language, will do so in a manner that makes it identifiable. • Recognizes this creates a more difficult document revision process.

  8. Issues • Emergency Procedures for late 2001. • Access to interruptible loads through utility tariffs.

  9. Next Steps • A 2-day Operating Guides workshop will be held on Jan 24-25 to review next draft. • New Operating Guides ready for approval by late January 2001 • Training Seminar focused on Protocols and Guides will start mid February.

  10. Old stuff

  11. Question -- Timing of control signals • Will ERCOT be NERC compliant if regulation signals are sent to QSE’s every 4 seconds? This appears to leave no time for QSE’s to forward those signals to their Resources.

  12. Question -- Frequency deviation analysis Section 6.10.5.4 For all frequency deviations exceeding 0.375, ERCOT shall measure and record each two (2) second scan rate values of real power output for each QSE Resource providing Responsive Reserve. Appendix II. C. 1. ISO Data The ISO will record the following data from all ERCOT Control Areas for frequency deviations .175 Hz or greater and will use this information to generate the ERCOT initial Disturbance Report:

  13. Questions -- Operational Metering • Inconsistent accuracy requirement for Operational metering. • Require 3% accuracy, but allow relaying quality PT’s / CT’s (+/- 10%) • Maintenance and repair standards for Operational Metering TBD

  14. Beth Garza - FPLE Jim Collins - TIE Jack Karn - Southern Henry Wood - STEC Rick Keetch - Reliant David Darnell - CPS Lee Westbrook - TXU John Adams - ERCOT Mark Henry - ERCOT Eddy Reese - RCEC Bob Brodie - KEMA Joint Operating Guides WG

  15. Need review by larger group • New Subcommittee(s) • Timing problem, not seated in time • Could refer to ‘disbanded’ SC’s and TF’s • ISONP • BTDT, don’t want to do it again • Representatives from QSEs and TDSPs • Use Client Rep’s contact lists, limit to 2 people per entity • Other options??

  16. Handoffs • Black Start • A stand alone section has been drafted and is ready for ‘expert’ review. • Ancillary Services • Procedures will describe either the specific amounts required, or the methodology that will be used to determine A/S quantities.

  17. Hierarchy Issue Avoid paraphrasing or duplicating Protocols vs. Provide comprehensive document to Operators Proposed Solution: • Where Protocol language is needed in Operating Guides, include entire Protocol section. • Use Protocol Revision Process to remove language from the Protocols.

  18. Other Guides • Settlement Metering • Load Profiling The Protocols refer to ‘Operating Guides’ for more details about each of these activities. Recommend: These commercial / retail activities be the subject of their own Guide.

More Related