1. Supporting materials for RMS Provided by Retail 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 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 MarkeTrak 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 - 2008

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 Statistics

9. Day to Day Issues - Summary

10. Day To Day Issues: Subtype Descriptions
Issue Sub-Type:
Submitted when…
Inadvertent Switch
…CR has inadvertently gained or lost (or is pending the gain/loss) an LSE Relationship to another CR in error.
Cancel w/Approval
…CR/TDSP requesting cancellation of an initiating transaction in instances submitting an 814_08 would result in a rejection.
Cancel w/o Approval
…TDSP requesting cancellation of an initiating transaction for market defined reasons that do not require approval from the CR.
Missing Transaction
…CR/TDSP is missing any expected 814, 867_04 or 867_03 Final.
Usage/Billing Issues
…CR/TDSP has questions pertaining to point-to-point transactions excluding the 867 Contingency Plan.
Reject Transactions
…CR/TDSP has questions pertaining to rejected transactions or reject reasons.
REP of Record
…CR/TDSP has questions pertaining to ERCOT LSE or TDSP LSE relationship histories.
Projects
…CR/TDSP has issues pertaining to internal/market projects, system trouble, or related problems as defined by the submitter.
Siebel/Chg Info
…CR/TDSP questioning a discrepancy pertaining to Siebel service order status changes and Start/Stop time issues when transactions are present in ERCOT systems.
997 Issues
…CR/TDSP verification of a 997 sent/received.
Other
…CR/TDSP has Day to Day issues that do not fit one of the Sub Types indicated above such as: Siebel/997 reports, CSA’s.

11. Inadvertent Gains - Detail by State

12. Inadvertent Gain: State Description
State Details…
Pending Issue
…Issue has not yet been submitted for consideration by the initiating party.
New (ERCOT)
…Pending either initial acknowledgement by an individual at ERCOT or returned to ERCOT for additional consideration.
Withdrawn
…Initiating MP has the option to remove the issue from consideration prior to acknowledgement by another MP.
In Progress (ERCOT)
…ERCOT to provide necessary information to move the issue towards resolution including IAS data and assistance with market guidelines.
New
…Pending acknowledgement by CR2 – the non submitting CR involved in the issues resolution.
Vote
…Submitting CR, CR2, and TDSP have simultaneous access to view, comment and ultimately vote on the resolution to the issue.
Agreement Reached (PC)
…All parties have indicated the issue has or will be resolved per the information agreed upon in the Vote state. Barring updates the Issue will auto close in 2 weeks.
No Agreement Reached (PC)
…Any party has indicated the issue is not a valid IAS or cannot be resolved as submitted per market guidelines. Barring updates the Issue will auto close in 2 weeks.
Complete
…Closed state: Issue resolution Accepted by submitting party from a state of Agreement Reached (PC) or No Agreement Reached (PC).
Auto Complete
…Closed state: No updates to issue for 2 weeks from a state of Agreement Reached (PC) or No Agreement Reached (PC).
Closed by ERCOT
…Closed state: ERCOT Intervention required to remove visibility due primarily to proprietary information updated to issue.

13. Cancel With Approval - Detail by State

14. Cancel with Approval: State Description
State Details…
Pending Issue
…Issue has not yet been submitted for consideration by the initiating party.
New
…Pending either initial acknowledgement by an individual at the TDSP or returned to TDSP for additional consideration.
Withdrawn
…Initiating MP has the option to remove the issue from consideration prior to acknowledgement by another MP.
In Progress
…TDSP to provide ERCOT with agreement with cancel request or CR indication that request is already complete / unable to be completed.
New (ERCOT)
…Pending acknowledgement by ERCOT
In Progress (ERCOT)
…ERCOT to perform agreed upon cancels in the Registration System, request additional information or indicate that cancel cannot be performed .
Cancelled (PC)
…All parties have indicated the requested service order has or will be cancelled. Barring updates the Issue will auto close in 2 weeks.
Unable to Cancel (PC)
…Any party has indicated the issue is not a valid Cancel w Approval issue or cannot be cancelled. Barring updates the Issue will auto close in 2 weeks.
Complete
…Closed state: Issue resolution Accepted by submitting party from a state of Agreement Reached (PC) or No Agreement Reached (PC).
Auto Complete
…Closed state: No updates to issue for 2 weeks from a state of Agreement Reached (PC) or No Agreement Reached (PC).
Closed by ERCOT
…Closed state: ERCOT Intervention required to remove visibility due primarily to proprietary information updated to issue.

15. DEV LSE Issues - Summary

16. DEV LSE Issues: Subtype Descriptions
Issue Sub-Type:
Submitted when…
LSE in MP System not ERCOT: Active
…MP systems show an Active LSE relationship not present in ERCOT’s Registration System (Siebel) as indicated by MP SCR727 Extracts.
LSE in MP System not ERCOT: Inactive
…MP systems show an Inactive LSE relationship not present in ERCOT’s Registration System (Siebel) as indicated by MP SCR727 Extracts.
LSE in ERCOT System not MP
…MP systems do not show an LSE relationship which is present in ERCOT’s Registration System (Siebel) as indicated by MP SCR727 Extracts.
LSE date change: Start Time
…MP systems show an LSE relationship present in ERCOT’s Registration System (Siebel) as indicated by MP SCR727 Extracts with a different initiation/enrollment date.
LSE date change: Stop Time
…MP systems show an LSE relationship present in ERCOT’s Registration System (Siebel) as indicated by MP SCR727 Extracts with a different end date.
LSE date change: Start and Stop Time
…MP systems show an LSE relationship present in ERCOT’s Registration System (Siebel) as indicated by MP SCR727 Extracts with a initiation/enrollment and end date.