1 / 14

ERCOT Retail Outages and Transaction Processing Notices as of September 2004

Learn about the impact of outages on transaction processing durations and market metrics. Receive recommendations for future reporting to RMS. Stay informed about planned outages and their effects on various transactions throughout the quarters.

tysonc
Download Presentation

ERCOT Retail Outages and Transaction Processing Notices as of September 2004

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. ERCOT Retail Outages and Transaction Processing Notices as of September 2004

  2. Recap • ERCOT Client Services (Retail and Wholesale) continues to work with COPS (communications team) to make improvements to market notices. • At the Sept RMS meeting, ERCOT was requested to share additional information on duration. • Today we will share information about duration and a recommendation will be made for future reporting to RMS.

  3. ERCOT Retail Outages

  4. Transaction Processing Issues

  5. Durations and Effect on Metrics Reminder: NAESB outages, when ERCOT is not receiving inbound transactions, would be reflected in market metrics. The transactions are time stamped when received by NAESB. • An 814_04 response to an 814_03 would be an example of one that would be timed LONGER because of NAESB being down and could result in protocol non-compliance. • If a REP sends an 814_01, and ERCOT is not receiving, the clock hasn’t started NAESB outages, when ERCOT is not able to push transactions, then the clock is still running for the MP on the response transaction to ERCOT.  • The 814_03 in the above example would be time stamped out by ERCOT and the clock would be running for the 814_04 back to ERCOT. Anytime ERCOT is holding transactions in the internal ERCOT systems it will be reflected in the metrics reported to the MP and PUCT and be on ERCOT’s time.

  6. ERCOT Retail Outages - Duration

  7. Duration – 1st Quarter Planned outage - weekend PF Outage

  8. Duration – 2nd Quarter Planned TML outage before TML ph1 Planned outage weekend API outage Not transactions Planned outage after hours NAESB Outage TCH Outage NAESB Outage Planned outage weekend

  9. Reminder – 1st & 2nd Qtr Metrics Switch Transactions

  10. Reminder – 1st & 2nd Qtr Metrics Move-In Transactions It should be noted that Move-In transactions have stricter protocol times than Switch transactions

  11. Reminder – 1st & 2nd Qtr Metrics Switch Meter Reading Transactions

  12. Reminder – 1st & 2nd Qtr Metrics Move-In Meter Reading Transactions

  13. Duration – 3rd Quarter TX SET 2.0 MIMO API outage Not transactions Planned outage weekend TCH Outage NAESB Outage

  14. Next Steps • Recommend to present updates quarterly to RMS along with the Performance Metrics updates. • Recommend to add monthly reports to the supporting materials sent to RMS.

More Related