1 / 24

Supporting materials for RMS Provided by Retail Customer Choice (RCC) team

Supporting materials for RMS Provided by Retail Customer Choice (RCC) team. Pro-Active Transaction Resolution Measures. 867s Received on Cancelled Service Orders. 867s received on Cancelled Service Orders. Situation

luke-schwartz
Download Presentation

Supporting materials for RMS Provided by Retail Customer Choice (RCC) team

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. Supporting materials for RMSProvided byRetail Customer Choice (RCC) team

  2. Pro-Active Transaction Resolution Measures 867s Received on Cancelled Service Orders

  3. 867s received on Cancelled Service Orders Situation ERCOT periodically receives 867_03 Finals and 867_04s for service orders that are Cancelled in ERCOT systems. The Service Order Sub-Statuses that are considered Cancelled are: CR Requested, Customer Objection, ERCOT Operating Rule, Manual, Permit Not Received, with Exception, Unexecutable and Rejected by TDSP. This can indicate an out-of-sync condition between the TDSP and ERCOT. Mechanism for Handling 867 RCSO: Step 1: ERCOT produces 867RCSO data each Friday and submits a report file to each TDSP and CR via the ERCOT Portal Step 2: The TDSPs review the report line items and take one of the following actions: a) If the TDSP has cancelled the service order, no further action is required b) If the TDSP has completed the service order, they will initiate a day-to-day FasTrak issue and work with ERCOT to get ERCOT systems changed to complete. Completion of cancelled service orders will require the approval of the CR initiating the transaction. (Note: For Cancel by Customer Objection, the TDSP will honor the cancel in their systems)

  4. 867s received on Cancelled Service Orders

  5. Pro-Active Transaction Resolution Measures Missing 867 Report Summary

  6. Missing 867 Report Missing 867 Report • The Missing 867 Report will provide TDSPs information about Service Orders in a scheduled state for which ERCOT has not received an 867 completing transaction at least seven days after the scheduled meter read • Weekly report provided to the TDSP via the ERCOT Portal Stats Summary:

  7. Missing 867 Report

  8. MarkeTrak Issue Status

  9. Total D2D Issues Submitted 12/1/2006 - 12/31/2006 Sub-Type Issue Count 997 Issues 6 Cancel with Approval - CR 3141 Cancel with Approval - TDSP 16 Cancel without Approval 30 Inadvertent Switch 1503 Missing TXNS 743 Other 83 Reject TXNS 14 Rep of Record 18 Siebel CHG/Info 110 Usage/Billing Issues 1026 Grand Total 6690 MarkeTrak production metrics / sample reports Total D2D Issues Submitted – 12/01/06 – 12/31/06

  10. MarkeTrak production metrics / sample reports Total DEV Issues Submitted – 12/01/06 – 12/31/06

  11. MarkeTrak production metrics / sample reports Total D2D Issues ERCOT Actioned– 12/01/06 – 12/31/06

  12. MarkeTrak production metrics / sample reports Total DEV Issues ERCOT Actioned– 12/01/06 – 12/31/06

  13. MarkeTrak production metrics / sample reports Total D2D Issues No ERCOT Action – 12/01/06 – 12/31/06

  14. MarkeTrak production metrics / sample reports Total DEV Issues No ERCOT Action – 12/01/06 – 12/31/06

  15. MarkeTrak production metrics / sample reports • Reminder – escalation emails are setup for calendar days Total D2D Unacknowledged– 12/01/06 – 12/31/06

  16. MarkeTrak production metrics / sample reports • Reminder – escalation emails are setup for calendar days Total DEV Unacknowledged– 12/01/06 – 12/31/06

  17. FasTrak Issue Status

  18. ‘Day to Day’ FasTrak Issue Stats by Category (thru 12/31/2006) 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 “All Other” does not have subtype. Issues logged as “All Other” can include Transaction Issues, Rep of Record Issues, Service Order Changes, etc.

  19. ‘Day to Day’ FasTrak Issue Stats by Category (thru 12/31/2006) • Of the 68 In Progress D2D Issues, 40 are resolved and awaiting other party resolution check off • Total D2D Issue ESI IDs worked to date since January 1, 2006 = 49,016

  20. ‘Day to Day’ FasTrak Issue Stats by Category (thru 12/31/2006)

  21. DEV FasTrak Issue Stats by Issue Type (thru 12/31/2006) Legend: Counts are of issues submitted during each month.

  22. DEV FasTrak Issue Stats by Issue Category (thru 12/31/2006) • Of the 70 In Progress DEV Issues,6 are resolved and awaiting other party resolution check off

  23. DEV FasTrak Issue Statsby Issue Type(thru 12/31/2006)

  24. DEV FasTrak Issue Stats by Issue Category (thru 12/31/2006)

More Related