1 / 3

Identical trade confirmation notifications

Identical trade confirmation notifications. Issue:

andra
Download Presentation

Identical trade confirmation notifications

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. Identical trade confirmation notifications • Issue: • If the QSE structures the xml in such a way as to submit each interval separately, an unconfirmed trade notification will be sent for each interval of the trade to the counterparty.  Then, when the trade is confirmed, a trade confirmation notification will also be sent for each interval of the trade to the counterparty. • Example – Submission of a 24-hour energy trade.  If the QSE submits each interval separately, the counterparty receives 96 identical notifications.  • Notification for Hour 1 Int 1, 2, 3…: • CM-ENGTRD-NOTF Energy Trade Submission update by QSE QABC: Confirmed: NO, for Trade Date: 12/10/2010, Buyer: QABC, Seller: QXYZ, Settlement Point: HB_SOUTH. • CM-ENGTRD-NOTF Energy Trade Submission update by QSE QABC: Confirmed: NO, for Trade Date: 12/10/2010, Buyer: QABC, Seller: QXYZ, Settlement Point: HB_SOUTH. • And so on (96 times total) … • This is causing an unnecessarily high number of trade notifications for both ERCOT and QSEs • Significant backlogs have been experienced in a couple of instances since go-live http://www.ercot.com 1

  2. Identical trade confirmation notifications • Solution: • Identified a mechanism to filter out identical notifications (sent at the same time) before the notifications leave the market system and are passed to external web services for delivery • Propose to implement this solution ASAP • QSEs will start to receive just one notification, rather than multiple identical notifications, upon trade submission/confirmation once this solution is implemented http://www.ercot.com 2

  3. DAM submission window queues/latency • Yesterday’s DAM took 23 minutes to complete processing of all queued transactions to ensure that all transactions submitted before 10 am were captured for the DAM • The root cause of this was a large chunk of transactions (mainly trades) for Operating Days up to 14 days out (transactions outside of the target Operating Day). • Propose to limit submission window to 8 days, from 14 • 7 days - originally 7 days to support protocol requirement for COPs • 14 days - in July, expanded to 14 days to assist QSEs in getting in those COPs • 8 days - in production, and aligns with 7 day requirement + 1 day of slack • Will implement after a 10-day advance market notice http://www.ercot.com 3

More Related