1 / 2

Contingency Plan Report (Updated 12/11/01)

Contingency Plan Report (Updated 12/11/01). Implementation issues around using a “carbon copy” type transaction have been reviewed. Naming convention will follow GISB standards 824s generated due to duplicate 867_03s will be suppressed by CRs and not sent to ERCOT

atira
Download Presentation

Contingency Plan Report (Updated 12/11/01)

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. Contingency Plan Report (Updated 12/11/01) • Implementation issues around using a “carbon copy” type transaction have been reviewed. • Naming convention will follow GISB standards • 824s generated due to duplicate 867_03s will be suppressed by CRs and not sent to ERCOT • 997s back to TDSP will be suppressed by CRs • The Texas SET team has addressed the forwarding issues and other naming convention issues. • If the market determines the 997 solution proposed is not working, it will be re-evaluated. • The contingency plan will go into effect on January 29th

  2. Contingency Plan Report (Updated 12/11/01) • How do we synchronize the usage data error when: • TDSP sends original 867 (and 810) sent to CR • TDSP recognizes problem with usage and rebills • CR recognizes non-usage problem and sends 824 to TDSP prior to receiving corrected usage • TDSP gets 824 reject on original usage, which has been superseded by a corrected usage • Solution: TDSP ignores the CRs 824 if TDSP correction & CR 824 are for the same usage problem.

More Related