1 / 19

Retail Sub-Committee Update

Retail Sub-Committee Update. Objectives. Update on PTB Synchronization Plan Status on synchronizing the CR of record Provide Update from Previous RMS issues Portal Performance and Changes IDR / Non IDR Meter Usage Reports 867-03 Forwarding Updates

lars-rollins
Télécharger la présentation

Retail Sub-Committee Update

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. Retail Sub-Committee Update

  2. Objectives • Update on PTB Synchronization Plan • Status on synchronizing the CR of record • Provide Update from Previous RMS issues • Portal Performance and Changes • IDR / Non IDR Meter Usage Reports • 867-03 Forwarding Updates • Information on Enhanced MP EDI Reporting Effort

  3. PTB Synchronization Plan • To address the current market issue with the rep of record getting out of synch between ERCOT, TDSP and CR systems. • The transition to AREP process identified some of these, and the Move In and Move Out “safety net” processes, market gaps and various system issues have caused many more. • The objectives of this project are to provide a plan to; • Identify the size of the problem • Provide root causes and options for correcting (if available) • Develop and implement a technical plan to synchronize databases • The Non-PTB (Over 1 MW) ESI Ids are being addressed through another process .

  4. Market Synchronization Update • RMS synchronization plan was approved at TAC unanimously • Kick off Conference Call meeting took place 5/21 • a) Minutes distributed 5/22 • Most TDSPs and CRs have identified at least one business and one technical contact to work with ERCOT • All parties agreed to action plan: • Each MP will ensure internal/provider systems are synchronized • A test run will occur to ensure queries and file layout are correct • This test run begins on May 29th and will complete by June 7th

  5. PTB Synchronization Plan - Next Steps • Market continues to support plan with appropriate technical and business resources being assigned. • Test files will be processed by ERCOT and finalize format and comparison programs verified. • ERCOT will work with MPs to correct any file format issues. • Pull together a detailed project plan to evaluate differences at a point in time and document steps required to correct • Full data send/analysis will take place once test run is complete • Report through RMS

  6. Questions

  7. Portal Performance History (Find ESI IDs) May 29, 2002 Total hits per week Unsuccessful hits

  8. Portal Performance Items • Mux E Way fix from Seebeyond on week of 3/30 • Saw a temporary 7 % improvement • Moved Portal E Ways to New Hardware week of 4/13 • Saw a temporary 10 % improvement • Added components (threads) on 4/25 • Showed some very promising improvements • Additional Architecture change was made 5/21 • Removed TCH component competing with batch transactions • Seeing a 30% improvement in errors • Also added “heartbeat” functionality to verify EAI every minute • Looking at 2 additional improvements currently being tested • Moving Siebel queries directly to Oracle • Improvements in redundancy for find transactions • Future options also being evaluated • Additional redundant paths for Portal transactions • Continue to analyze errors and respond

  9. Questions

  10. IDR Meter Usage Report (data submitted 8 weeks following Trade date)

  11. IDR Meter Usage Report (as of 5/28/02)Percent of IDR accounts received by ERCOT since August 95% or better expected 63% * NOTE: ERCOT (and REPs) may have received additional non-sequential data (i.e, February data before January data). ERCOT rejects all meter reads that introduce gaps in the database

  12. NIDR Meter Usage Report Percent of NIDR accounts received by ERCOT since August 95% or better expected

  13. Questions

  14. 867-03 Forward Update • Data Provided on Existing MP Reports will allow reconciliation

  15. 867-03 Forward Update • ERCOT Data for May 1 to May 26, 2002 • 5,557,189 Usage transactions received at ERCOT • 99.91% forwarded, 5,551,739 transactions • 5,776 Not forwarded due to invalid forwarding Duns numbers

  16. 867-03 Forwards – Sample Timings

  17. 867-03 Forwarding • ERCOT believes we are forwarding all 867s that have forwarding information provided • ERCOT provides 867 forwarding information on the current MP reports to facilitate reconciliation • ERCOT samples of turn around time are well within protocols • Next Steps • Should point to point 867 continue? • If MPs believe ERCOT is not properly forwarding 867-03s, provide Examples for ERCOT to check

  18. Questions

  19. Questions

More Related