1 Update on the 867_03 Contingency Plan Nancy Hetrick February 25, 2003.

Slides:



Advertisements
Similar presentations
Market True-Up Discussion RMS Meeting 03/13/02 Draft Only for Discussion Purposes.
Advertisements

Retail Market Subcommittee Update to TAC Kathy Scott February 26,
Retail Sub-Committee Update Robert Connell June 14, 2002.
Retail Market Update June 5, New meter is requested for a specific customer’s location. 2.Application is filed by customer and/or the customer’s.
Role of Account Management at ERCOT PRR 672 Collaborative Analysis Presentation to RMS November 8, 2006 DRAFT ONLY.
Retail Market Subcommittee (RMS) Update Kathy Scott January 3, 2013Technical Advisory Committee 1.
1 Update from ERCOT Retail Market Services to RMS Additional Material February 12, 2004.
814_20 – Substation ID updates Background and Proposed Action Plan TX SET – 10/25/07.
1 Transaction or Issue Clean Up. 2 Linked-Address Issue Multiple ESI IDs Linked to a Single Service Address Record Background Counts Matrix Completed.
TX SET Update to RMS Wednesday, October 10, 2007.
1 RMS Update - ERCOT June 10, Supporting Reports Section.
1 RMS Update on Move-In / Move-Out Task Force October 16, 2002.
MARS Taskforce COPS Update May 12, Execution MilestonesBaseline DateStatus Technical Architecture Complete 05/15/2009On Schedule Development Complete07/24/2009On.
Advanced Meter Settlement Background and NPRR. Overview PUC Rule (wholesale settlement) Project – Wholesale Settlement Project Filed Deployment.
 Advanced Metering Working Group (AMWG) Update to RMS 1 August 5, 2014.
Retail Market Subcommittee Update to TAC Kathy Scott February 27,
09/15/10 RMS RMS Market Reports – Recommendations Karen Farley Manager, Retail Customer Choice.
1 Update from ERCOT Retail Market Services to TAC January 9, 2003.
Rob Connell May 1, 2002 Retail Sub-Committee Update.
Texas Test Plan Team Market Testing Update to RMS October 16, 2002.
1 Supporting materials for RMS Provided by Retail Customer Choice (RCC) team.
Profiling Working Group March 14, PWG Update Report By Ernie Podraza of Reliant Energy ERCOT PWG Chair for COPS Meeting March 14, 2006.
10/13/10 RMS RMS Market Reports – Recommendations Karen Farley Manager, Retail Customer Choice.
RMS Update to TAC April 7, RMS Voting Items  RMGRR032- Transaction Timing Matrix Corrections Includes updates to Appendix D to correct examples.
1 Processing Large Volumes 814_20s Issues / Discussion / Ideas.
Report to RMS January 14, TTPT Key Dates and Deadlines as of 1/14/03 1/05/04 - Mandatory Connectivity Kick Off Call & Penny Tests begin 1/12/03.
1 RMS TAC Update April 3, Test Plan Flight Dates It is the practice of RMS to approved the dates for future testing flights. This enables new.
1 ESI ID SERVICE HISTORY AND USAGE DATA EXTRACT SYSTEM CHANGE REQUEST (SCR 727) February 24, 2003.
1 MVI/MVO Workshop June 3 – 12, 2002 Workshop Results.
October 9, 2012 Commercial Operations Subcommittee RMS Update Kathy Scott RMS Vice Chair.
Rob Connell May 29, 2002 Retail Sub-Committee Update.
Retail Market Subcommittee Update to COPS Kathy Scott March 17,
RMS/COPS Workshop VI 1 October 06, Antitrust Admonition ERCOT strictly prohibits Market Participants and their employees who are participating in.
MARS Taskforce RMS Update November 10, Conference Call concerning Settlement Estimates TDSPs held a conference call on October 28, 2010, where we:
1 Transaction or Issue Clean Up. 2 Linked-Address Issue Multiple ESI IDs Linked to a Single Service Address Record Background Counts Matrix Completed.
1 Linked-Service Address Discussion Thursday - April 8, 2004 (Updated 4/12/04 to include meeting results) Airport Hilton - Austin.
1 Transaction or Issue Clean Up. 2 Customer Protection and 814_08 Issue (Phase 2 – Potentially Late 08s) Background Completed Items Next Steps.
Retail Market Subcommittee Update to COPS Kathy Scott February 11,
814_20 – Substation ID updates Background and Proposed Action Plan RMS – 11/07/07.
1 Critical Retail Issues RMS Update RMS Meeting Results 2/01 RMS Formed 3/01 RMS Identified “pent-up” issues Tx Set transaction development Service Order.
1 Supporting materials for RMS Provided by Retail Customer Choice (RCC) team.
1 TX SET Update to RMS November 12, RMGRR Activity RMGRR065 – Disconnect and Reconnect for Non-Payment Updates and Corrections – –Normal Timeline.
TX SET Update to RMS Wednesday, November 7, 2007.
Retail Market Subcommittee (RMS) Update Kathy Scott April 9, 2013Commercial Operations Subcommittee 1.
1 RMS Update By Don Bender January 9, RMS Approved Resolution Upon TAC approval, suspend further True-up settlements for True-up resettlement.
Changes to SSO Extract:  Based on DEWG discussions in 2005, ERCOT is recommending the following changes to the SSOE: In lieu of the current daily files.
February 10, 2010 RMS ERCOT 1/24/10 Production Issue Overview and Lessons Learned Karen Farley Manager, Retail Customer Choice.
Demand Response Task Force. 2 2 Outline  Overview of ERCOT’s role in the CCET Pilot  Overview of Stakeholder Process – What’s been done to date?  Questions.
December 9, 2015 Retail Market Subcommittee Update to COPS Kathy Scott January 13,
1 TX SET Mass Transition Project RMS Update March 15, 2006.
1 Supporting materials for RMS Follow up from April RMS presentation Expedited Switch/Customer Rescission (Retail Customer Choice Team)
Retail Market Subcommittee Update to COPS Kathy Scott November 5,
1DRAFT for DISCUSSION Transition From Non-IDR to IDR Load Profile and LSE 15-minute Data for AMS Market Advanced Readings and Settlements Taskforce 10/9/09.
1 Move-In Move-Out Task Force Update to RMS May 15, 2003.
February 2, 2016 RMS Meeting 1. * Reasons: * Per the ERCOT Board Report dated 8/5/14 there were 6.6M Advanced Metering System (AMS) Electric Service Identifiers.
1 Customer Objections in Complete Status (CCO Clean-up Phase 3) Background Next Steps.
MIMO Stacking Document and the current RMG are inconsistent with current logic and should be updated.
Proposal to Discontinue Retail Market Call RMS October 15, 2008.
SHARYLAND TRANSITION TASKFORCE (STTF) UPDATE UPDATE TO RMS APRIL 1,
1 TDTWG Update to RMS Wednesday May 6, Primary Activities 1.Reviewed ERCOT System Outages and Failures 2.Reviewed Service Availability 3.Reviewed.
RMGRR058 Overview RMS Meeting – August 15, Background / Reference PUCT Substantive Rule 25.43(n)(8) Protocol Customer Billing Contact.
1 Customer Objections in Complete Status (CCO Clean-up Phase 3) Background Next Steps.
Summary of the November 11, 2002 Market Synchronization “How-to-Fix” Decisions For presentation to RMS November 14, 2002.
Mass Transition—Timelines & Volume Limitation RMGRR116—Acquisition Transfer Non-standard Metering Future Meetings 1.
1 Supporting materials for RMS Provided by Retail Customer Choice (RCC) team.
1 Transaction or Issue Clean Up. 2 Customer Protection and 814_08 Issue (Phase 2 – Potentially Late 08s) Background Completed Items Next Steps.
Settlement Timeline Workshop
MARS Taskforce RMS Update December 9, 2009.
Pro-Active Transaction Resolution Measures
Pro-Active Transaction Resolution Measures
Presentation transcript:

1 Update on the 867_03 Contingency Plan Nancy Hetrick February 25, 2003

2 867_03 Contingency Plan History RMS approved the 867_03 Contingency Plan on December 11, 2001: –Per 12/11/01 RMS Minutes, the plan was developed in the event that ERCOT is unable to forward 867_03 transactions –Per Protocol, TDSPs to continue sending 867_03 Monthly Usage to ERCOT –ERCOT then forwards the usage to the CR –TDSPs also send the 867_03 Monthly Usage to the CR point to point via GISB

3 867_03 Contingency Plan History Implemented prior to or on January 29, 2002 in the following TDSP areas: –AEP –CenterPoint –ONCOR –Texas-New Mexico Power

4 RMS Discussion Requested Why is the 867_03 Contingency Plan being revisited at RMS today? –Market Participants initiated discussion on the Retail Market Call. –Some Market Participants noted they were no longer relying on the 867_03 Contingency Plan and did not want to receive usage via the Contingency Plan any longer. –Other Market Participants noted they still relied on the usage received via the 867_03 Contingency Plan as they felt they were not receiving all usage from ERCOT. – As the 867_03 Contingency Plan was the result of an RMS decision, Market Participants requested it be revisited in the same forum as it was developed.

5 RMS Discussion To assist with the RMS Discussion: Root Cause Analysis Performed –ERCOT encouraged CRs to provide data to help assess why CRs could potentially not be receiving usage from ERCOT that they received from TDSPs via the 867_03 Contingency Plan. –Two CRs provided ERCOT with 867_03 usage instances in which they believed usage was received via the 867_03 Contingency Plan, but not from ERCOT. –ERCOT researched the instances in question and provided feedback. Informal Poll taken on February 17, 2003 Retail Market Call

6 Research Results for CR A CR A provided 59 files for December 2002 Research Results: –7 usage instances (867_03) never sent to ERCOT by TDSP Request forwarded to TDSP for further research –1 usage instance sent to ERCOT by TDSP, but ERCOT did not forward No forwarding information provided in 867_03 from TDSP –51 usage instances forwarded by ERCOT on same day as received from TDSP Run IDs provided to CR for further research 100% of valid 867_03s sent to ERCOT were forwarded to the applicable CR

7 Research Results for CR B CR B provided 88 files for October 2002 Research Results: –1 usage instance sent by TDSP A, but the 867_03 failed TX SET validation at ERCOT TDSP to correct the transaction and re-drop –1 usage instance never sent by TDSP B to ERCOT TDSP reported to have a problem with the account and has not sent an 867 or 810 for 8 months; TDSP still researching –7 usage instances sent by TDSP C, but ERCOT did not forward No forwarding information provided in 867_03 from TDSP –79 usage instances forwarded by ERCOT on same day as received from TDSP Run IDs provided to CR for further research 100% of valid 867_03s sent to ERCOT were forwarded to the applicable CR

8 Research Results for CR B Cont. CR B provided 29 files for November 2002 Research Results: –26 usage instances sent by TDSP A, but these 867_03s failed TX SET validation at ERCOT TDSP to correct the transactions and re-drop –3 usage instances forwarded by ERCOT on same day as received from TDSP Run IDs provided to CR for further research 100% of valid 867_03s sent to ERCOT were forwarded to the applicable CR

9 Research Results for CR B Cont. CR B provided 425 files for December 2002 Research Results: –200 of the 425 usage instances have been researched by ERCOT –200 usage instances forwarded by ERCOT on same day as received from TDSP Run IDs provided to CR for further research 100% of valid 867_03s sent to ERCOT were forwarded to the applicable CR for those files researched for December

10 Research Summary 2 CRs provided data for ERCOT to research Of the _03 usage instances in question as provided by the CRs: –8 usage instances were never sent to ERCOT by the TDSP –8 usage instances did not contain forwarding information from the TDSP –27 usage instances failed TX SET validation at ERCOT –333 usage instances were forwarded by ERCOT on the same day as received from the TDSP –225 usage instances remain to be researched

11 Informal Poll Results ERCOT took an informal poll of Market Participants of their position on the February 17, 2003 Retail Market Call Informal Poll Results include Retail Market Call as well as Votes: –8 in favor of Discontinuing the 867_03 Contingency Plan –4 in favor of Continuing the 867_03 Contingency Plan –1 MP Abstained from voting on the Retail Market Call

12 Final Comments Comments Received from Market Participants: A CR commented that based on December 2002, the stats have improved significantly. We are currently showing only a 2% gap of expected 867s which we did not receive from ERCOT. One CR supports continuing the 867_03 Workaround process until such time that the percentages of delivered meter reads reaches a sustained 98% success rate. A CR noted that if two trading partners wish to discontinue the 867 Contingency Plan between themselves, they may. However, a TDSP noted that some do not have the ability to quit providing the Contingency Plan to some while continuing to provide it for others.

13 Thank You