Developed possible solutions for communication of the Switch Hold Flag. A WebEx will be set up for Thursday, June 17th to make a final decision on the long term transactional solution.
Will pass this information to the Meter Tampering Task Force for their discussion. MTTF will bring feedback to Texas SET.
Background
Status:
Closed
Date Posted:
04/12/2010
Sponsor:
CenterPoint Energy
Urgent:
No
Sections:
814 Transactions, 650_01 and 650_02
Description:
Potentially new processes with the bi-directional point to point transaction for TDSPs and CRs. These changes would be additional functionality for existing 814 transactions for ERCOT and Market participants requiring a TX SET Release to implement.
Reason:
There will be a need for the following to support and automate processes:
New Reject Code on appropriate Response Transactions to indicate that ESI ID has a "SWITCH HOLD" preventing Switch or Move-In.
New data element/segment to identify ESI ID has "SWITCH HOLD" since a Mass Transition will not prevent the Switch from being completed, however the gaining CRs (POLRS) will need the SWITCH HOLD indicator. TX SET should decide if this is a Y/N flag or if the "SWITCH HOLD" segment is only present when the "SWITCH HOLD" condition is applicable.
Develop Point to Point communications bi-directional TX SET transaction that will allow the REP of Record to receive "SWITCH HOLD" notifications from TDSP or vice versa. It would also work from REP of Record to TDSP providing notification to TDSP to "RELEASE SWITCH HOLD" along with response acknowledgement. This would work for any scenario where there is a Switch hold regardless of the reason in which it was applied to the ESI ID.
The transactions should include a unique code to indicate which entity placed the SWITCH HOLD on the ESI ID for example:
CR Switch Hold = CSH (example- future use by REP of Record related holds)
TDSP Switch Hold = TSH (example -- TDSP Tampering Switch Hold)
Switch Hold Released at CR Request = CSR (example -- Switch Hold Released at CR request- Customer satisfied obligation or agreement of New Customer Move-In)
Switch Hold Released at TDSP Request= TSR ( example -- Switch Hold Released at TDSP request- no response to new Move-In application within Rule timeline)
Clarify or add new codes in 650_01 and 650_02 transaction that will allow CRs to Disconnect Premise due to Tampering and also Reconnect Services related to Tampering if CR chooses to do so, also a response 650_02 transaction would be needed for both the Disconnect and Reconnect due to tampering. The only tampering code in the current 650_01 transaction is MM006 Tampering Suspected, but it doesn’t state that it is a request to disconnect. It could be interpreted as a means to start a tampering investigation by the TDSP at the request of the CR.
