MIS LOG IN

TXSETCC766

Summary

Title: In order to provide codes that are more specific than "Other" with a text explanation, TX SET shall add a new code T023 to the REF~G7 for Move Out treated as a force off due to Move In scheduled for same date.
Next Step: Classified as Non-Emergency by RMS
Status: Implemented

Action

Date Gov Body Action Taken Next Steps
01/19/2011 RMS Approved Classified as Non-Emergency by RMS
12/08/2010 RMS Approved Approved by RMS
11/08/2010 TXSET Recommended for Approval

Background

Status: Implemented
Date Submitted: 10/28/2010
Submitter Name: Kathy Scott
Submitter Company: CenterPoint Energy
Emergency: No
Sections: 814_28
Description: In order to provide codes that are more specific than "Other" with a text explanation, TX SET shall add a new code T023 to the REF~G7 for Move Out treated as a force off due to Move In scheduled for same date.
Reason: If CNP received a same day MVI and MVO scheduled for the same date and per the ERCOT rules from stacking we cannot complete them both for the same date, CNP will treat the MVI as a force off and either wait for ERCOT’s 814_08 cancel request for the MVO or we will send ERCOT an 814_28 complete unexecutable purpose code of "T018 Other" to complete the BPI for the MVO request. In the case of the 814_28 unexecutable T018 applied to the MVO we will provide a text explanation indicating that it was treated as a force off since MVI was scheduled for the same date if we don’t receive the 814_08 cancel from ERCOT. In order that we provide codes that are more specific than "Other" with a text explanation, TX SET should adopt a new more specific code that can provide the same information to market participants to allow reporting and validations off the code instead of requiring the receiver to read or resolve the initiating transaction based upon the text comments. Add new code T023 to the REF~G7 for "Move-Out transaction (814_24) was treated as a force off since (814_03) Move-In transaction received by the TDSP was scheduled for the same date".
Version: 4.0
Protocol Impact: No

Key Documents

Related Content