market operator
play

Market Operator User Group Dublin, 17 January 2019 1 Agenda Item - PowerPoint PPT Presentation

Market Operator User Group Dublin, 17 January 2019 1 Agenda Item Presenter Welcome Anne Fitzgerald Known Issues & Day 1+ Update David Lee High Level Market Overview Brendan OSullivan Ex-Ante Market Liam McAllister Balancing


  1. Market Operator User Group Dublin, 17 January 2019 1

  2. Agenda Item Presenter Welcome Anne Fitzgerald Known Issues & Day 1+ Update David Lee High Level Market Overview Brendan O’Sullivan Ex-Ante Market Liam McAllister Balancing Market Aodhagan Downey Disputes & Repricing Update Dermot Campfield Settlements & Cash-flow Analysis Sean O’Rourke, John O’Dea REMIT & Urgent Market Messages Update Severin Garanzuay Query Management Claire Breslin Q&A 2

  3. Agenda Item Presenter Welcome Anne Fitzgerald Known Issues & Day 1+ Update David Lee High Level Market Overview Brendan O’Sullivan Ex-Ante Market Liam McAllister Balancing Market Aodhagan Downey Disputes & Repricing Update Dermot Campfield Settlements & Cash-flow Analysis Sean O’Rourke, John O’Dea REMIT & Urgent Market Messages Update Severin Garanzuay Query Management Claire Breslin Q&A 3

  4. I-SEM Day 1+, High-Level Indicative Release Timeline • Day 1+ consists of a series of releases to the I-SEM Market systems over 2019. Items discovered by operations or participant teams will be assessed, prioritised, and packaged into a release if material. • M+4 Resettlement will kick off on 17 th January as planned, with ad hoc settlement utilising the latest code later in the year. This would see improvements in QBOA and settlement issues • Repricing is targeted to be begin once testing is successfully completed. Jan Mar May Jun Aug Sept Release Release Release Release Release Release Jan Feb Mar Apr May Jun July Aug Sept Day to Day SEMO / SEMOpx Operations Operational Issue Identification, Triage and Prioritisation Runnings Issue Identification, Triage and Prioritisation Rel. A Rel. B Rel. C Rel. D Rel. E Rel. F Testing Resettle Resettle Repricing M+4 Resettlement Resettlement Ad Hoc with Latest Rel. Operation Ad Hoc with Repricing Repricing Operations Repricing

  5. Known Issues Update - Summary • Known Issues continue to be analysed and prioritised as and when they occur. • Once a defect has been raised, the issue will be assessed in the wider defect pool and assigned to a code drop in line with its severity and priority. • Drop dates to test have been agreed with our vendor, with release to production plans provided based on successful test closure. • The table below presents a breakdown of the upcoming releases, Known Issues coverage and expected benefit. Release Bundle Status Known Issues Coverage Expected Benefit • Release A Delivered 14 Issues Resolution to a number of settlement issues including Fixed Cost complex bid resolution, Interconnection charges, and Autoproducers difference payments and charges fix • Report 44 incorrect values for QCOB and QCNET • Report 102 publication issue • Internal operational improvements • Improved resettlement and repricing functionality • Release B Contents Agreed 3 Issues Improvements to QBOA function including resolution to units being skipped • Incorrect MW QTY values in REPT_078/079 • Improved resettlement and repricing functionality • Release C Planned – Contents TBC Contents TBC TBC

  6. Known Issues Update – Process Summary • Below graphic provides a view of how participant facing issues may be identified, managed and delivered to the I-SEM Market Systems • Issue Participant Raises Issue through I-SEM Front Office • Participants can highlight the urgency and business Logged impact • Issue is analysed by SMEs and vendors to confirm if system defect Issue • Severity and impact are assessed against other known issues and recommended delivery drop is Triage proposed • Delivery schedule is updated in Known Issues Guide • Software fix or workaround solution is delivered Fix and • Test team validate in non-production environments Test and clear release for production • Productio Participants are notified of an upcoming release date • Release is applied to production and issue is n Release validated

  7. Known Issues Update – SEMOpx Resolution ID Name Description Impact to Market Participants Status Date SEMOPX Bid/Ask Curves report fails Low impact to Members as the file Closed To be .001 to generate following an would otherwise be empty. removed as auction, for a given not planned Production of jurisdiction, when there for delivery Bid/Ask Curves are no orders received for Report that auction. SEMOPX REMIT Reporting Known issues with the SEMOpx Member transactions are Planned Jan 2019 .003 delay in reporting SEMOpx not reported to ACER until this is Release Resolution: Member transaction to resolved. Date Deployment ACER REMIT platform. of Internal Testing of solution ongoing Solution 92601 ETS Auction Message log is not No material impact to SEMOpx Unplanned No Results retaining the message Members. Members can view all Confirmed indicating availability of auction results. Members will need Delivery the ETS Auctions to look at auction results date reports/screens to determine availability of auction results, as opposed to reviewing the message log.

  8. Known Issues Update – Balancing Market Resolution ID Name Description Impact to Market Participants Status Date When retrieving VTOD from the MPI via In Day 1 plus type 2 or type 3, the SOAK WARM This leads to confusion for MPs as scope, Quarter QUANTITY values are incorrect. The they cannot view the accurate Soak 1 release 5497 VTOD Soak values shown are the SOAK HOT WARM QUANTITY values. The SO and Planned Times QUANTITY values. MO approve the correct values, and Release Date Resolution: Please note: the integrity of the VTOD those are used in the Scheduling & Software set is unaffected. This is simply an Dispatch process. update from incorrect display in the MPI. vendor REPT_102: Hourly Some instances of the Jan 2019 Dispatch PUB_HrlyDispatchInstr report The instance of the Hourly DI Report is Release Instructions (REPT_102) in XML format have failed not available in XML format until it is Planned 5635 Report to generate on the MPI and as a result, published as part of the Daily DI Resolution: Release Date Intermittently are also no appearing on the public Reports, which are unaffected by this Software Fails to website. The report is generated and issue. The report is available in HTML. update from generate in available in HTML format. vendor. XML format. In Day 1 plus scope, Quarter Units being 1 release Unit being skipped in pricing due to skipped in QBOA is missed for a Unit, resulting in Planned 5737 “Error in Slope Calculation” causing QBOA impact to Imbalance Price Release Date Resolution: periodic drop in NIV calculations Software update from vendor

  9. Known Issues Update – Balancing Market Resolution ID Name Description Impact to Market Participants Status Date Reports not showing first ISP interval for trade date in report. The MPs will not be able to source TBC data for the first ISP of a trade date Reports REPT_078: Aggregated Contract from this report until the issue is Resolution: 5329 missing 1st ISP Quantities for Generation remedied. These data can be sourced In Analysis Software of Trade Day REPT_079: Aggregated Contract elsewhere. They are available in the update from Quantities for Demand ETS Market Results published on the vendor REPT_080: Aggregated Contract SEMOpx website, D+1. Quantities for Wind TBC 2 Reports are currently not publishing Missing No material impact to Market to the new SEMO website. REPT_027 Reports on the Participants or General Public as these Resolution: 5587 (Four Day Rolling Wind Forecast) and In Analysis new SEMO reports are now being uploaded Software REPT_013 (Daily Commercial Offer Website manually to the SEMO website. update from Data) vendor The PQ pairs reported in REPT_081 TBC REPT_081 Currently the report cumulatively adds erroneously report values that exceed hourly each MW quantity to the last MW the generation capacity in Ireland. The Resolution: 5603 Anonymized quantity rather then the difference. report is inaccurate and the In Analysis Software INC and DEC This results in erroneous MW values in commercial bidding behaviour of the update from Curves the report. aggregated generation on the Island is vendor not accurately represented.

Recommend


More recommend