ERCOT provided the latest data which showed a dramatic reduction in the volume of this occurring, indicating that the issue has been addressed by the CR that was systematically sending the CSA By-Pass flag on all MVOs. MPs request that ERCOT continue to monitor the volumes for spikes and alert TX SET if any spikes occur. ERCOT agreed to this monitoring. Also, ERCOT is concerned about the continued volume of by-pass flags being used for premises without a CSA agreement but cannot tell how many are B44 vs. 2W, so ERCOT will be creating a SIR so that they can determine the volume of each type of by-pass flag still being used and will report results back to TX SET. This issue is being closed.
ERCOT provided the latest data which showed a dramatic reduction in the volume of this occurring, indicating that the issue has been addressed by the CR that was systematically sending the CSA By-Pass flag on all MVOs. MPs request that ERCOT continue to monitor the volumes for spikes and alert TX SET if any spikes occur. ERCOT agreed to this monitoring. Also, ERCOT is concerned about the continued volume of by-pass flags being used for premises without a CSA agreement but cannot tell how many are B44 vs. 2W, so ERCOT will be creating a SIR so that they can determine the volume of each type of by-pass flag still being used and will report results back to TX SET. This issue is being closed.
TX SET reviewed the updated data provided by ERCOT and found some reduction in the numbers, however the problem still exists. TX SET will be monitoring to see if CR makes the corrections to their system to no longer send CSA Flag on MVOs where they are not CSA CR. TX SET would expect these corrections to be completed and implemented by September’s TX SET meeting. Update will be provided by Kathryn Thurman (ERCOT) at the September meeting on the CRs progress. It was stated at RMS by Rob Bevill that the CR will be making the corrections but it was taking a little time to complete.
TX SET reviewed updated data provided by ercot. volume is unchanged. There was substantial discussion/concern regarding the fact that this continues to happen ~4-5 months since the issue was identified. TX SET agreed to notify the offending rep that if this is not corrected by the time TX SET meets in August, TX SET will take some action to escalate the issue at RMS.
TX SET decided to continue to monitor this data and ERCOT agreed to contact the CR that is sending the majority of these every month and to provide a monthly update from that CR as to their progress on changing their practice of sending the CSA-By Pass flag when they do not own the CSA.
ERCOT provided updated data on the frequency of MVOs being submitted with the CSA By-Pass flag in which a different CR is the owner of the CSA. The data shows that this issue continues to occur at a concerning frequency (see data below). ERCOT stated that >75% of these transactions came from a single CR and it was agreed that ERCOT Client Services would escalate the issue to that CR and request that they cease this business practice. (TX SET’s interpretation of the 814_24 I.G. is that this practice (using the REF~2W) is not allowed.) ERCOT agreed to continue to monitor the volume and to bring updated data back to TX SET in May. Also, these data include both the REF~2W and B44 and ERCOT agreed look at a sample of the data to get an idea for how many of these are B44 (which is a valid market process).
ERCOT provided updated data on volumes with additional detail on the use of B44 as well as 2W. Determined that the issue is coming primarily from three REPs. ERCOT to contact these CRs and request that they stop using these codes inappropriately. ERCOT to continue to track volumes for next TX SET meeting.
ercot is going to assess (perform a system impact analysis) what it would take to add validation to check that the cr submitting a ref 2w (csa by-pass) is also the current csa cr (including under a different duns number). note the grey-box language in the 814_24 in the ref~2w limiting the use of the code to the current rep of record.
ERCOT presented additional data for consideration which provided counts of occurrences of this scenario during the last 3 days of January. ERCOT stated that most of these were caused by a single CR and agreed to contact that CR and request that they stop doing this. ERCOT is going to provide similar data for TX SET to review in March to monitor for improvement. However, this behavior is not expressly prohibited in any market guides or rules and it is possible that CRs are using the By-Pass flag intentionally, following a DNP, so as not to re-energize a premise. CRs will need to consider this trade-off if we decide to expressly limit the use of the CSA By-Pass flag to the owner of the CSA.
ERCOT’s investigation showed a lot of activity with numerous CRs sending this code where they may or may not have been CSA CR. The information obtained by ERCOT isn’t definite as to the findings because the CSA CR could have changed from the time the information was pulled. Additional data is needed from ERCOT to ensure correct result is obtained going forward.
crs will need to check internally with their shops to determine what the best solution should be for this scenario.
Background
Status:
Closed
Date Posted:
11/16/2007
Sponsor:
TXU Energy
Urgent:
No
Sections:
814_24
Description:
Non -- CSA CR sends a MVO with the indicator for ignore the CSA at ERCOT. Resulting in CSA CR never knowing the ESIID is not active.
Reason:
CSA CR does not know the ESIID is not active. CSA premise management company is left with a Unit with no power and may incur charges for permits in the hundreds of Dollars.
