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

Slides:



Advertisements
Similar presentations
RXQ Dual Billing Process Flow Distribution Company Supplier Customer Distribution Company reads meter(s) ( ) Supplier receives and processes.
Advertisements

RXQ Dual Billing Process Flow Distribution Company Supplier Customer Distribution Company reads meter(s) ( ) Supplier receives and processes.
RXQ Dual Billing Process Flow Distribution Company Supplier Customer Distribution Company reads meter(s) ( ) Supplier receives and processes.
1 Siebel Service Order Extract MIMO Impact May 03, 2004.
Retail Market Subcommittee Update to TAC February 5, 2004.
AMS DATA WORKSHOP III TDSP UPDATE September 19,
1.  An inadvertent issue begins upon the discovery of an Inadvertent Gain or Move-In transaction submission. Upon identification of an Inadvertent Gain.
1 Pre-TX Set 1.5 Data Clean Up. 2 Pre-TX SET 1.5 Data Clean-up Process In-Review - currently 12 (Original Quantity = 863) –June RMS, count 207 In-Review.
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.
ERCOT MARKET EDUCATION
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 MIMO/Stacking (Including Tx SET Version 2.0) Post Implementation Success Report.
1 RMS Update - ERCOT June 10, Supporting Reports Section.
1 RMS Update on Move-In / Move-Out Task Force October 16, 2002.
1 Update from ERCOT Retail Market Services to RMS May 15, 2003.
Market Impact Assessment TF Final Report to RMS June 11, 2008.
09/15/10 RMS RMS Market Reports – Recommendations Karen Farley Manager, Retail Customer Choice.
Rob Connell May 1, 2002 Retail Sub-Committee Update.
1 Supporting materials for RMS Provided by Retail Customer Choice (RCC) team.
10/13/10 RMS RMS Market Reports – Recommendations Karen Farley Manager, Retail Customer Choice.
ESI IDs Retired in Error! RMS – August 10, 2005 Discussion.
RMS Update to TAC April 7, RMS Voting Items  RMGRR032- Transaction Timing Matrix Corrections Includes updates to Appendix D to correct examples.
TX SET v2.1 Implementation Plan. Table of Contents A.Shut Down Procedure B.Shut Down Timeline Details C.Conference Calls D.Additional Contingencies.
Texas SET Version 3.0 Production Implementation Plan.
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 ESI ID SERVICE HISTORY AND USAGE DATA EXTRACT SYSTEM CHANGE REQUEST (SCR 727) February 24, 2003.
1 RMS Update - ERCOT May 14, Supporting Reports Section.
1 MVI/MVO Workshop June 3 – 12, 2002 Workshop Results.
October 14, 2015 LRIS v2 / Self-scheduled Third party DR Provider Data Submission Proposal Carl L Raish.
Load Profiling Working Group RMS Presentation 8/01/2002 by Ernie Podraza Reliant Energy Retail Group Chair PWG.
Rob Connell May 29, 2002 Retail Sub-Committee Update.
1 RMS Update on Move-In / Move-Out Task Force November 14, 2002.
ERCOT MARKET EDUCATION Retail 101. Retail Transaction Processing.
MARS 867_03F ROR vs. Settlement vs. 810 Scenarios ERCOT September 2008.
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 Update on the 867_03 Contingency Plan Nancy Hetrick February 25, 2003.
1 Transaction or Issue Clean Up. 2 Customer Protection and 814_08 Issue (Phase 2 – Potentially Late 08s) Background Completed Items Next Steps.
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 RMS Update By Don Bender January 9, RMS Approved Resolution Upon TAC approval, suspend further True-up settlements for True-up resettlement.
Profiling Working Group August 14, PWG Update Report By Ernie Podraza of Reliant Energy ERCOT PWG Chair for RMS Meeting August 14, 2003.
ERCOT MARKET EDUCATION Retail 101. Introductions, Roles and Responsibilities.
Issue 2007-I071 Modify Cancellation Window to Accept Cancels Closer to SMRD.
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.
1 TX SET Mass Transition Project RMS Update March 15, 2006.
Update to RMS December 18, Project(PR) 010_03 SCR756 Part B – High Level Timeline DRAFT:  Planning Phase: ~ (End of 2013) ◦ Business requirements.
Update to RMS June 3, Project(PR) 010_03 SCR756 Part B High Level Timeline  Planning Phase - complete  Execution/Development - complete  Testing.
Update to RMS January 10, Project(PR) 010_03 SCR756 Part B – High Level Timeline DRAFT:  Planning Phase: ~ (End of 2013) ◦ Business requirements.
1 Move-In Move-Out Task Force Update to RMS May 15, 2003.
Retail Market Subcommittee Update to TAC March 4, 2004.
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.
Proposed Timeline for Extract, Variances, True-Ups Extracts 10/1/03 Clear all “old” extracts from Portal 9/26/03 Post last “old” daily extract 10/6/03.
Mass Transition Lessons Learned. Should the FASD (First Available Switch Date) be revised for Mass Transition Projects? We need a better definition of.
MMWG Performance Measures Questionnaire. Performance Measure Reporting Requirements The reporting requirements allowed the commission to obtain information.
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.  What is the purpose of DEVs? Data Extract Variances (DEVs) are used to synchronize the data among all Market Participants (MP)  What is a DEV? It's.
1 Market Participant Default Joint Taskforce Update and Report on Recent Customer Transition Activity Report to WMS August 17, 2005.
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.
Pro-Active Transaction Resolution Measures
Pro-Active Transaction Resolution Measures
Usage Billing Issues.
Stacking Implementation Plan
Demand Response – ERCOT discussion items
Presentation transcript:

Market True-Up Discussion RMS Meeting 03/13/02 Draft Only for Discussion Purposes

2 Definition of issue Risks of Not Performing True-Up Other Markets’ Actions Prep Activities Ground Rules Risks of Performing True-Up Next Steps Points for Discussion

3 Definition of Issue Currently, the market as a whole has a large number of discrepancies in retail status These discrepancies include: –Which CR is responsible for an ESI ID –What the status of an ESI ID is –What date did that status or ownership change These discrepancies are a result of market gaps, general system errors and manual intervention

4 Risks of Not Performing True-Up ESI ID statuses may be incorrect. –ESI ID may be considered de-energized when it is not (resulting in UFE) –ESI ID may be considered active – but under a different CR (resulting in incorrect CR and market level settlements) CRs may be prevented from submitting certain transactions –For example, CR will not be able to submit a MVI or DTP if they are not the CR of record CRs may not receive certain transactions –For example, 814_20s may not be forwarded to a CR if that CR is not the CR of record at ERCOT –This may prevent a CR from receiving meter modifications or retires A CR may stop receiving transactions for an ESI ID he believes he is responsible for –CR may stop receiving usage for an ESI ID –CR cannot bill customer without manual intervention and inquiry

5 Customers may end up being double billed by multiple CRs (who both think they are responsible for an ESI ID) Alternately, a customer may not be billed for usage he is receiving Market level settlements may result in billing to an incorrect QSE Transactions submitted later in the market may result in notification to the incorrect CR –For example, in a situation where the MVI Safety Net was performed by CR1 but this transaction was not reflected at ERCOT –CR3 submits a switch –ERCOT will either –Reject the transaction – if it believes the ESI ID is de-energized –Accept the transaction – but notify the TDSP that the dropping CR is the old CR (not CR1) –CR1 gets no notification of a drop due to a switch –The TDSP may or may not correctly change the relationship leaving one CR without information Risks of Not Performing True-Up (cont)

6 Other Markets’ Actions Most markets have performed some sort of reconciliation –Pennsylvania performed a true-up for the first 6 months of market open (spending an additional 4 months closing market and system issues) –New Jersey performed a true-up for the first 8 months –New York has performed a reconciliation from market open to current –Illinois performed a true-up for the first 4 months These true-ups were mostly initiated by the CR working with a TDSP to resolve differences in data Other markets have only had to reconcile with two parties (the TDSP and CR) Other markets have not been constrained by the fact that the TDSP could not provide energy in situations differences appeared –Pennsylvania did not separate energy services until after market open

7 Prep Activities Market buy-in and support will be required prior to beginning any true-up process TDSPs need to provide a list to each CR of all ESI IDs that CR owned or does own. This list should include begin date and end date (if applicable) for that CR. These dates are the energy start and stop flow dates ERCOT needs to provide the same list for each CR by TDSP CR needs to take both lists and identify accounts that are not in synch This list can be divided by ESI ID Type (with the market deciding to prioritize by type) or effective date by month

8 Ground Rules Ahead of an actual true-up meeting, the CR must sent the list of discrepancies to ERCOT ERCOT must then perform analysis to determine whether or not there is a pending order for that ESI ID or if another CR already owns the ESI ID The CR must also send the list to the TDSP and ERCOT All Market Participants (CR, TSDP and ERCOT) must have available what the read dates for those ESI IDs are within their respective systems As disputes are resolved, read dates will be used to determine effective dates of switches No manual updates will be performed without a matching read All read dates should be based on actual accepted usage

9 Risks of Performing True-Up Potential discrepancies could be due to timing issues of when Market Participants run their list and perform the true up QSEs may be out of the true-up loop due to manual processing –CR needs to ensure that the QSE is notified of any manual updates There will be market contention for ESIIDs that multiple CRs claim ownership over –This will require resolution on a case by case basis –The resolution may require contact with the customer –There will need to be a predefined set of rules the market agrees on to work through resolution of disputes. Every market participant needs to agree and adhere to these rules Corrections may involve resending of multiple retail transactions. This may be a significant quantity –Example: 814_20s (Create/Maintain ESIID) or initial/final usage may need to be resent as part of the reconciliation. Currently there is no prioritization of transaction being re-processed as part of the reconciliation.

10 Risks of Performing True-Up (cont) Not all Market Participants have to or will participate or prioritize the reconciliation process The Market Participants will resolve the issues for the ESIIDs but will not address the overall market issues The reconciliation will affect customer billing. The TDSP and the CR will need to have procedures in place to deal with billing discrepancies The reconciliation may occur after the settlement process has completed. The market will need to determine how to re-settle for periods already completed Reconciliation will need to occur multiple times until market stabilizes and potentially even long term Reconciliation may be too large. May have to divide reconciliation up into all pilot first to gather and apply lessons learned This reconciliation only covers current and past relationships. Another may need to be performed for pending transactions

11 Next Steps Review Possible Discrepancy Scenarios (see attached word document) Determine set of rules to begin to resolve discrepancies Determine timeline for true-up Determine schedule for true-up Get market buy-in