1 / 19

WIAB WECC Interchange Authority Backup

WIAB WECC Interchange Authority Backup. BY LOU MIRANDA BONNEVILLE POWER ADMINISTRATION TRANSMISSION SERVICES WECC ISAS SCHEDULERS MEETING SALT LAKE CITY, UTAH MAY 19 – 20, 2015. INT – 020 – WECC – CRT – 1.1.

davidpowers
Télécharger la présentation

WIAB WECC Interchange Authority Backup

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. WIABWECC Interchange Authority Backup BY LOU MIRANDA BONNEVILLE POWER ADMINISTRATION TRANSMISSION SERVICES WECC ISAS SCHEDULERS MEETING SALT LAKE CITY, UTAH MAY 19 – 20, 2015

  2. INT – 020 – WECC – CRT – 1.1 • Purpose: The purpose of this document is to establish a coordinated back-stop scheduling process that protects the reliability of the grid during an Interchange Authority Emergency • WIT stops working and Reliability Coordinator (RC) declares WIAB in effect. • Peak Reliability is the Reliability Coordinator.

  3. WECC INTERCHANGE TOOL • WIT is the sole source for confirmed interchange throughout the WECC . • Developed by Open Access Technology International (OATI), Inc. • Peak Reliability holds the contract for WIT Services. • WIT is also referred to as the Interchange Authority Software in this document.

  4. INDICATORS OF A WIT FAILURE • Balancing Authority (BA) “ In-house” Net Scheduled Interchange (NSI) does not match the NSI calculated by WIT. • New e-tags and e-tag adjustments unable to be submitted by Interconnection members. • May receive calls by other Balancing authorities about discrepancies in NSI totals. • Receive WECC net message from Peak Reliability Coordinator (RC) declaring an Interchange Authority emergency and implementing WIAB criteria.

  5. WIAB INT-020-WECC-CRT -1.1 -- REQUIREMENTS AND MEASURES • WR1. Each Interchange Authority shall monitor the real-time operational status of the Interchange Authority software. • WM1. Each Interchange Authority shall provide evidence that it monitored the real- time operational status of the Interchange Authority software.

  6. WIAB INT-020-WECC-CRT -1.1 -- REQUIREMENTS AND MEASURES • WR2. Each Transmission Service Provider shall maintain a record of the transactions on its paths for the current hour plus the next four consecutive hours. • WM2. Each Transmission Service Provider shall produce a record of all transactions on its paths for a specified audit hour plus the next four consecutive hours. • WR3. Each Purchasing Selling Entity shall maintain a record of its interchange schedules for the current hour plus the next four consecutive hours. • WM3. Each Purchasing Selling Entity shall produce a record of all of its interchange schedules for a specified audit hour plus the next four consecutive hours.

  7. WIAB INT-020-WECC-CRT -1.1 -- REQUIREMENTS AND MEASURES • WR4. Each Balancing Authority shall maintain a duplicate copy of its aggregate Net Scheduled Interchange (NSI) as previously confirmed by the Interchange Authority for the current hour plus the next four consecutive hours. • WM4. Each Balancing Authority shall produce its retained duplicate copy of its aggregate Net Scheduled Interchange (NSI) as previously confirmed by the Interchange Authority for a specified audit hour plus the next four consecutive hours. • WR5. Each Balancing Authority shall store a duplicate copy of its aggregate NSI on a storage system independent from the Interchange Authority. • WM5. Each Balancing Authority shall produce evidence that storage of its aggregate NSI takes place on a storage system independent from the Interchange Authority.

  8. WIAB INT-020-WECC-CRT -1.1 -- REQUIREMENTS AND MEASURES • WR6. Each Balancing Authority and Purchasing Selling Entity shall report suspected failure of the Interchange Authority software to the Interchange Authority Software Provider. • WM6. Each Balancing Authority and Purchasing Selling Entity shall produce all reports, if any, submitted to the Interchange Authority Software Provider that indicated suspected failure of the Interchange Authority software. • WR7. Each Interchange Authority shall report confirmed failure of the Interchange Authority software to the Reliability Coordinator. • WM7. Each Interchange Authority shall produce all reports, if any, submitted to the Reliability Coordinator that indicated confirmed failure of the Interchange Authority software.

  9. WIAB INT-020-WECC-CRT -1.1 -- REQUIREMENTS AND MEASURES • WR8. Each Reliability Coordinator shall declare the start of an Interchange Authority Emergency using the WECC Net messaging system or alternate method. • WM8. Each Reliability Coordinator shall produce evidence that it used the WECC Net messaging system or alternate method to communicate the start of all Interchange Authority Emergencies.

  10. WIAB INT-020-WECC-CRT -1.1 -- REQUIREMENTS AND MEASURES • WR9. During an IA Emergency, each Balancing Authority shall operate to the most recent duplicate copy of its aggregate NSI as last confirmed by the Interchange Authority (net of all individual adjacent NSI’s) or as adjusted by changes described in below. • WM9. Each Balancing Authority shall produce evidence that it operated to the data contained in its most recent duplicate copy of its aggregate NSI as last confirmed by the Interchange Authority (net of all individual adjacent NSI’s) or as adjusted by changes allowed in this criterion for each specified period covered by an Interchange Authority Emergency. • WR10. During an IA Emergency, each Balancing Authority shall exhaust all of its internal and dynamically scheduled or pseudo-tied external resources before requesting new interchange. • WM10. Each Balancing Authority shall produce evidence that it exhausted all of its internal and dynamically scheduled or pseudo-tied external resources before it requested a new interchange for each specified period covered by an Interchange Authority Emergency.

  11. WIAB INT-020-WECC-CRT -1.1 -- REQUIREMENTS AND MEASURES • WR11. During an IA Emergency, each Sink Balancing Authority shall implement new interchange transactions when necessary to maintain load-to-generation balance, reserve requirements, or to maintain reliability. • WM11. Each Sink Balancing Authority shall produce evidence that it implemented new interchange transactions that were necessary to maintain load-to- generation balance, reserve requirements, or to maintain reliability, for each specified period covered by an Interchange Authority Emergency. • WR12. During an IA Emergency, each Sink Balancing Authority shall create new interchange by verbally communicating and confirming with the Source Balancing Authority and the Transmission Service Providers that are parties to the transaction. • WM12. Each Sink Balancing Authority shall produce evidence that, the Sink Balancing Authority created and confirmed new interchange with the Source Balancing Authority and the Transmission Service Providers that were parties to the newly created transaction, for each specified period covered by an Interchange Authority Emergency.

  12. WIAB INT-020-WECC-CRT -1.1 -- REQUIREMENTS AND MEASURES • WR13. During an IA Emergency, each Sending Balancing Authority that is a party to the newly created interchange transaction shall verbally communicate and confirm with each Receiving Balancing Authority and Transmission Service Provider involved in the transaction created by the Sink Balancing Authority. • WM13. Each Sending Balancing Authority that is a party to the newly created interchange transaction shall produce evidence that it communicated and confirmed the newly created interchange transaction with each Receiving Balancing Authority and Transmission Service Provider involved in the transaction created by the Sink Balancing Authority, for each specified period covered by an Interchange Authority Emergency.

  13. WIAB INT-020-WECC-CRT -1.1 -- REQUIREMENTS AND MEASURES • WR14. During an IA Emergency, each Balancing Authority shall verbally communicate upward adjustments to existing non-dynamic transactions with each Balancing Authority and each Transmission Service Provider that is a party to the transaction as if those adjustments were a new transaction. • WM14. Each Balancing Authority shall provide evidence that upward adjustments to existing non-dynamic transactions were arranged by verbally communicating with each Balancing Authority and each Transmission Service Provider that is a party to the transaction, as if the upward adjustment were a new transaction, for each specified period covered by an Interchange Authority Emergency.

  14. WIAB INT-020-WECC-CRT -1.1 -- REQUIREMENTS AND MEASURES • WR15. During an IA Emergency, each Balancing Authority and each Transmission Service Provider shall verbally communicate downward adjustments or curtailments to existing non-dynamic transactions with each Balancing Authority and each Transmission Service Provider that is a party to the transaction. • WM15. Each Balancing Authority and each Transmission Service Provider shall provide evidence that downward adjustments or curtailments to existing non- dynamic transactions were arranged by verbally communicating with each Balancing Authority and each Transmission Service Provider that is a party to the transaction, for each specified period covered by an Interchange Authority Emergency.

  15. WIAB INT-020-WECC-CRT -1.1 -- REQUIREMENTS AND MEASURES • WR16. During an IA Emergency, each Balancing Authority and each Transmission Service Provider shall complete the Transaction Data Template (Attachment A) for each new transaction. • WM16. Each Balancing Authority and each Transmission Service Provider shall produce a completed Transaction Data Template for each new transaction created during each specified period covered by an Interchange Authority Emergency.

  16. WIAB INT-020-WECC-CRT -1.1 -- REQUIREMENTS AND MEASURES • WR17. Each Interchange Authority shall report confirmed restoration of the Interchange Authority software to the Reliability Coordinator. • WM17. Each Interchange Authority shall produce its report of confirmed restoration of the Interchange Authority software to the Reliability Coordinator. • WR18. Each Reliability Coordinator shall declare the termination of an Interchange Authority Emergency using the WECC Net messaging system or alternate method. • WM18. Each Reliability Coordinator shall produce evidence that it used the WECC Net messaging system or alternate method to declare the termination of an Interchange Authority Emergency

  17. WIAB INT-020-WECC-CRT -1.1 -- REQUIREMENTS AND MEASURES • WR19. Each Sink Balancing Authority shall submit or cause to have submitted an after-the-fact e-Tag, after termination of each Interchange Authority Emergency and before the end of the after-the-fact e-Tag submission deadline, for each transaction implemented during each Interchange Authority Emergency. • WM19. Each Sink Balancing Authority shall produce evidence that it submitted an after-the-fact e-Tag after termination of each Interchange Authority Emergency and prior to the end of the after-the-fact e-Tag submission deadline, for each transaction implemented during each Interchange Authority Emergency.

  18. WIAB INT-020-WECC-CRT -1.1 -- REQUIREMENTS AND MEASURES • WR20. Each Sink Balancing Authority shall update or cause to have updated its dynamic tags, after termination of the Interchange Authority Emergency and before the end of the dynamic tag adjustment deadline, using the actual interchange values that occurred during the Interchange Authority Emergency. • WM20. Each Sink Balancing Authority shall provide evidence that it updated or caused to be updated its dynamic tags, after termination of the Interchange Authority Emergency and before the end of the dynamic tag adjustment deadline, using the actual interchange values that occurred during the Interchange Authority Emergency.

  19. WIAB • QUESTIONS ?

More Related