1 Supporting materials for RMS Recommendations for improvements from EDIM team (ESI ID Data Integrity Management team)

Slides:



Advertisements
Similar presentations
Retail Market Subcommittee Update to TAC February 5, 2004.
Advertisements

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.
MarkeTrak Update Retail Market Subcommittee December 6, 2006 Adam Martinez & Karen Farley.
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.
1 Update from ERCOT Retail Market Services to RMS April 23, 2003.
Price Responsive Load / Retail DR Update to RMS Karen Farley June 3, 2014.
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 ERCOT True-Up Resettlement Restart Criteria Discussion Retail Market Subcommittee Meeting, February 24, 2003.
RMS Update to TAC January 3, Goals Update ► Complete and improve SCR745, Retail Market Outage Evaluation & Resolution, implementation and reporting.
1 MIMO/Stacking (Including Tx SET Version 2.0) Post Implementation Success Report.
1 RMS Update - ERCOT June 10, Supporting Reports Section.
1 Update from ERCOT Retail Market Services to RMS May 15, 2003.
MARS Taskforce COPS Update May 12, Execution MilestonesBaseline DateStatus Technical Architecture Complete 05/15/2009On Schedule Development Complete07/24/2009On.
RMS Update to TAC January 8, Voting Items From RMS meeting on 12/10/2008  RMGRR069: Texas SET Retail Market Guide Clean-up – Section 7: Historical.
09/15/10 RMS RMS Market Reports – Recommendations Karen Farley Manager, Retail Customer Choice.
Flight V1.4F2 TTPT Update to RMS May 1. Participants of Flight V1.4F2 5 CRs 3 New CRs Andeler Constellation UBS Warburg 2 Existing CRs Electric America.
Role of Account Management at ERCOT PRR 672 Collaborative Analysis October 2, 2006 DRAFT ONLY.
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.
1 Update from ERCOT Retail Market Services to RMS December 11, 2003.
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.
Rob Connell May 29, 2002 Retail Sub-Committee Update.
1 RMS Update on Move-In / Move-Out Task Force November 14, 2002.
Profiling Working Group October 16, PWG Update Report By Ernie Podraza of Reliant Energy ERCOT PWG Chair for RMS Meeting October 16, 2003.
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.
ERS Update – DSWG Presentation September 21, 2012.
1 Transaction or Issue Clean Up. 2 Customer Protection and 814_08 Issue (Phase 2 – Potentially Late 08s) Background Completed Items Next Steps.
1 Supporting materials for RMS Provided by Retail Customer Choice (RCC) team.
1 RMS Update By Don Bender January 9, RMS Approved Resolution Upon TAC approval, suspend further True-up settlements for True-up resettlement.
Feb 18, TAC Report to the ERCOT Board February 18, 2003.
February 10, 2010 RMS ERCOT 1/24/10 Production Issue Overview and Lessons Learned Karen Farley Manager, Retail Customer Choice.
February 19, 2009 ERCOT Follow up on questions from 2/11 discussion on proposed Expedited Switch rulemaking changes…
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.
1 Update from ERCOT Retail Market Services to RMS July 17, 2003.
ERCOT Portal Replacement Phase 2 Project Update to RMS Presented by Dave Odle Thursday, October 16 th, 2003.
Update to RMS January 10, Project(PR) 010_03 SCR756 Part B – High Level Timeline DRAFT:  Planning Phase: ~ (End of 2013) ◦ Business requirements.
RMS Update to TAC October 2, RMS Update to TAC TAC Confirmation Vote Request Kyle Patrick of Reliant Energy and Independent Power Marketer segment.
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.
Retail Market Subcommittee Update to TAC March 4, 2004.
1 Customer Objections in Complete Status (CCO Clean-up Phase 3) Background Next Steps.
Retail Market Subcommittee Update to TAC May 6, 2004.
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.
SHARYLAND TRANSITION TASKFORCE (STTF) UPDATE UPDATE TO RMS APRIL 1,
1 Update from ERCOT Retail Market Services to RMS August 14, 2003.
1 Texas Data Transport & MarkeTrak Systems (TDTMS) Update to RMS March 1, 2016 Jim Lee (AEP) – Chair Monica Jones (NRG) – Vice Chair.
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.
Market Metrics RMS March 13 th, 2002 ERCOT MetCenter.
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.
Multiple ESI IDs Linked to a Single Service Address Record Linked-Address Action Items.
1 Supporting materials for RMS Provided by Retail Customer Choice (RCC) team.
August 9, 2006 Retail Market Subcommittee Meeting MarkeTrak Update.
Retail Market Update November 6, Flight Time Lines Retail market has several market occurring in the second quarter Flight 0304, GISB.
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
Pro-Active Transaction Resolution Measures
Pro-Active Transaction Resolution Measures
Demand Response – ERCOT discussion items
Presentation transcript:

1 Supporting materials for RMS Recommendations for improvements from EDIM team (ESI ID Data Integrity Management team)

2 Background ERCOT began providing these reports in In March 2004, RMS chair/vice chair gathered input from RMS members, working groups/task force leadership on proposed changes to format of RMS meetings. In April 2004, a revised agenda format was followed / very similar to today’s agenda. This set of reports have been in the supporting reports section for 18 months.

3 Approach To facilitate this discussion, would like to take the approach to identify what questions asked and what answers to be provided. Some questions may need to be updated due to Market changes. New questions may need to be added. Appreciate the ideas from the Market Participants.

4 Missing 867 Report When did this reporting begin? November 13, 2003 Frequency – weekly report, posted on Wednesday for each TDSP. This is a point-in-time report, not an aggregate report. Questions asked –Is ERCOT receiving 867_03F/867_04 in timely manner according to market needs? –This item was originally part of the Pre-TX Set 1.5 clean-up and the Ongoing Transaction Clean-up efforts Slides provides –Volume of Service Orders in ERCOT system that have not received the 867 completing transaction at least 7 days after scheduled meter read date Stats shown by TDSP territory Chart show over time the reduction in volume Recommendation –Continue to provide supporting materials to RMS –Change frequency to quarterly reporting

5 Missing 867 Report Input from one MP prior to RMS Missing suggest that the 867_03 reporting would be suspended and created only in the event of a high volume of missing 867_03 transactions indicating that either a MP has a system or processing issue/problem that needs to be communicated to RMS. There will always be a number of 867's expected but not received, the market should never expect a zero number in this area for any month's report. However, do feel that RMS should be made aware if there is a month where the 867_03 backlog or expected number exceeded 5,000 or 10,000 for any one TDSP that this would be reported. Maybe ERCOT should ask RMS on what the magic number of missing 867's should be for the red flag alert to be pulled. In the case of a red-flag alert ERCOT would provide a RMS update to the earliest RMS agenda under emerging issues to communicate directly to RMS for their awareness of the problem (cause and resolution, pending or resolved). So in short, report only when necessary.

6 Missing 867 Report

7 867 RSCO Reporting When did this reporting begin? November 13, 2003 Question asked –What are some of the ongoing market synch issues? Slides provide answer by –Volume of 867_03F/867_04 received by ERCOT on service orders that are cancelled in ERCOT systems Stats shown by cancel type Stats shown by TDSP territory Recommendation –Continue to provide supporting materials monthly to RMS –No change in frequency

8 867 RSCO Reporting

9 FasTrak D2D Reporting When did this reporting begin? April 1, 2003 Question asked –What are the volumes of issues reported? Slides provide answer by –Volume of issues (approximately 1 month buckets) Stats shown by calendar year Stats shown by New, In Progress, Resolved and Rejected Stats (ERCOT only) In Progress broke down by CR, TDSP, ERCOT Older Stats shown by submitting party and escalated to Client Services for facilitation of resolution between parties / or clean up. Recommendation –Continue to provide supporting materials monthly to RMS –Change slide formats

10 FasTrak DEV Reporting When did this reporting begin? May 15, 2003 Question asked –What are the volumes of issues reported? Slides provide answer by –Volume of issues (approximately 1 month buckets) Stats shown by calendar year Stats shown by New, In Progress, Resolved and Rejected Stats (ERCOT only) In Progress broke down by CR, TDSP, ERCOT Recommendation –Continue to provide supporting materials monthly to RMS –Change slide formats

11 FasTrak D2D New Slides Recommend reporting FasTrak D2D by category and minor modifications to show totals of resolved / rejected / in progress. Recommend escalation of any 2003, 2004 issues to ERCOT Client Services, closing the issues and reporting the escalations by submitting party back to RMS. New question asked –What are the types of issues being logged each calendar month? Slides provide answer by –Volume of issues (actual 1 month buckets) Value provided –Begin moving towards what improved tool set will be able to provide –Raise awareness of Market of types of issues logged –Easier to report in full month – instead of everything up to 1 week prior to RMS. As RMS meetings are not always 4 weeks apart, could make trend analysis a bit easier.

12 FasTrak D2D New Slides Input from one MP prior to RMS FasTrak - any reports prior to the current year 2005 should be removed from the report because that would be more historical information, which is not needed. Suggest that this report be provided quarterly and the Market/ERCOT should re-evaluate the need to continue reporting the quarterly information following the implementation of the FasTrak software replacement. The new tool may provide reporting capabilities that may satisfy the needs of the individual MPs where ERCOT would not need to provide this information at all or if provided, could be every 3 or 6 months. Another suggestion would be to make sure on a yearly update to RMS provide a report of any previous year's FasTrak issues that have not been resolved to prevent open issues unresolved for multiple years.

13 ‘Day to Day’ FasTrak Issue Stats by Category (thru 11/02/2005) Legend: Counts are of issues submitted during each month. EI = ERCOT Initiated Issue Non-ERCOT issue = Issues logged directly between the CR and TDSP with no ERCOT involvement to resolve. Category of “Other” does not have subtype. Issues logged as “Other” can include Transaction Issues, Rep of Record Issues, Service Order Changes, etc.

14 ‘Day to Day’ FasTrak Issue Stats by Category (thru 11/02/2005) Of the 229 In Progress D2D Issues, 144 are resolved and awaiting other party resolution check off Total D2D Issue ESI IDs worked to date since January 1, 2005 = 104,835

15 ‘Day to Day’ FasTrak Issue Stats by Category (thru 11/02/2005)

16 FasTrak DEV New Slide Recommend reporting FasTrak DEV by issue type and calendar month New question asked –What are the types of issues being logged each calendar month? Slides provide answer by –Volume of issues (actual 1 month buckets) Value provided –Begin moving towards what improved tool set will be able to provide –Raise awareness of Market of types of issues logged –Easier to report in full month – instead of everything up to 1 week prior to RMS. As RMS meetings are not always 4 weeks apart, could make trend analysis a bit easier.

17 DEV FasTrak Issue Stats by Issue Type (thru 11/02/2005) Legend: Counts are of issues submitted during each month.

18 DEV FasTrak Issue Stats by Issue Category (thru 11/02/2005) Of the 203 In Progress DEV Issues, 50 are resolved and awaiting other party resolution check off

19 DEV FasTrak Issue Stats by Issue Type (thru 11/02/2005)

20 DEV FasTrak Issue Stats by Issue Category (thru 11/02/2005)

21 Recommendations RECAP of recommendations ERCOT recommends staying with monthly reporting cycle on the following reports: 867 RCSO, new FasTrak D2D, new FasTrak DEV. ERCOT recommends moving to a quarterly reporting cycle for the following reports: Missing 867 ERCOT recommends that all reports stay in the supporting reports section. ERCOT recommends consolidating current D2D and DEV slides with new slides shown today. ERCOT recommends escalation of any 2003, 2004 issues to ERCOT Client Services, closing the issues and reporting the escalations by submitting party back to RMS. ERCOT recommends that RMS ask TX SET or Market Metrics to add quarterly review of the supporting reports to their agendas.

22 Next Steps Appreciate the ideas from the Market Participants Will take action after RMS meeting on 11/09/05. Most changes could occur for 12/07/05 RMS meeting.