Solution to Stacking - Rep Rule 1: Reps who have a pending move out and submit a move in (same rep) with an earlier requested date are responsible for canceling the pending move out if that is what the customer requires (rep manages customer expectations). if the rep does not cancel the move out, the move out will be allowed to effectuate.
Next Step:
The group discussed the issue. It was stated that the TDSPs do not review the customer name when receiving an 814_24 transaction. It was also determined that the retail market guide specifies the responsibilities in this scenario explicitly. No change to the TX SET 814_24 will be needed.
The group discussed the issue. It was stated that the TDSPs do not review the customer name when receiving an 814_24 transaction. It was also determined that the retail market guide specifies the responsibilities in this scenario explicitly. No change to the TX SET 814_24 will be needed.
Background
Status:
Closed
Date Posted:
08/13/2013
Sponsor:
CenterPoint Energy
Urgent:
No
Sections:
814_24
Description:
CNP feels there is confusion in the market as to how REP of Record should manage their MVOs when they are both Current MVI and Previous MVO Customer’s REP of Record -- Solution to Stacking REP Rule 1. Also REP should understand that once the MVI is completed, the TDSP will automatically force-out (MVO) the prior customer for the same effective date as the Move-In.
Reason:
New MVI Customer experienced an unnecessary outage due to an assumption that CNP or TDSPs validate on the NAME field received in an 814_24 transaction before determining if the transaction should be executed. CNP was advised that we are the only TDSP not validating on the NAME field; therefore, we are the only TDSP executing the MVO when we shouldn’t.
