Phased Technical Solution for DAM Context: In case of no-deal Brexit, the two GB bidding zones will be excluded from the MRC topology. Proposed Plan • An Interim Solution allows flexibility to retain existing DAM coupling should a no-deal Brexit be avoided. • A move to the MRC agreed Enduring Solution (in approximately 6-8 weeks) after the Brexit date (currently 31/10/2019) has passed. Interim Solution : Back Up Procedures Enduring Solution: Two separate local auctions GB/IE&NI GB bidding zones are excluded from the MRC topology. GB & IE/NI bidding zones will be decoupled from SEMOpx and EPEX launch two separate local auctions. the MRC topology. EPEX will run both bidding zones as a Local Auction in Back up Mode. MRC SEM – GB NI GB2 NI NL GB1 IRE GB1 BE IRE GB2 FR Schema representation applicable for both scenarios Note: During both phases the SEM Ex-Ante markets will operate in the same way i.e. no coupling in the DAM, it is only the underlying technical solution that will change.
Agenda Item Presenter Welcome Anne Fitzgerald Known Issues and Release Update David Lee Ex-Ante Market Michael Atcheson, Liam McAllister Balancing Market John Ging, Rory Cafferky Repricing Update Julie McGee Settlements Claire Kane, Sean O’Rourke, John O’Dea Query Management Claire Breslin Q&A 28
Data issues impacting on System Operations 1. Submission of PNs that are outside of Real-Time availabilities submitted via EDIL, e.g.: • PN < Lower Operating Limit (LOL) • PN > Higher Operating Limit (HOL) • PN within unit forbidden zone • PN with no EDIL and/or MPI availability • PN for retired units or units on long term outage – Default data 2. Failure to update MPI with revised availability (to match EDIL) Submission of invalid COD data for selected TOD set, e.g.: • Commercial Offered Data for CCGT mode when unit is in OCGT mode 3. Failure to update MPI with revised availability (to match EDIL) • Typically post tripping or during outages • Ambient conditions • Rounding to nearest Integer 4. Combined submissions for “Units under Test” and non -test units • Treated as a single transaction which must be approved within short timeframes 5. Tertiary fuel • Submission of availability on Tertiary fuel not accounted for in Market Design 29
Scheduler periodicity and horizons 30
MMS Data Flows – Forecasts for long term horizons Initial Conditions Initial Conditions MPI LTS Grid Schedule RTC SCADA Schedule RTD DATA DI DECL MMS EDIL Schedule AVAILABILITY DATA (NOW) 31
Obligations to declare availability • Real Time Declared Availability (per EDIL) • Forecast Availability (per MPI) • EirGrid Grid Code and SONI Grid Code (SDC1 - SCHEDULING AND DISPATCH CODE) SDC1.4.1 states: – The Availability Notice shall state the Availability of the relevant CDGU , Controllable PPM , Interconnector , Demand Side Unit or Pumped Storage Plant Demand as the case may be, (including, in the case of a CCGT Installation , the Availability of each of the CCGT Unit s within it) for each Imbalance Settlement Period in the time up to and including the end of the relevant Trading Day (subject to revision under SDC1.4.3.6). – This shall be submitted not later than the Gate Closure 1 each day (i.e. 13:30 on TD-1) Clarification on DSU forecast availability • A Note for Participants on FNDDS Calculation Methodology which was published in November 2018. – “DSUs only declare availability (forecast and real-time) for which the SOs can schedule to , while ensuring Distribution System Operator (DSO) and Distribution Network Operator (DNO) congestion restrictions are still observed . This entails submitting Physical Notifications, forecast availability and declared availability prior to Balancing Market gate closure, and in real-time operation, reflecting DSO / DNO Instruction Sets. SOs schedule and dispatch DSUs up to their declared availability only (DSU availability which reflects for DSO / DNO instruction sets) .” 32
Tutorial – Updating availability per MPI • https://mms.sem-o.com/mpi/ GENERATORs DSUs 33
Generators – Step 1: Header data 1 2 3 34
Generators – Step 2: Data entry (per BCoP) 1 2 3 4 5 Hydro / Storage { 35
Generators – Step 3: Reflect Actual Output 3 • Ambients 1 • Outages • Restrictions 2 36
DSUs – Step 1: Header data 1 2 3 37
DSUs – Step 2: Data entry (per BCoP) 1 2 3 38 4
DSUs – Step 3: Reflect Actual Output • Ambients • Outages • Restrictions • Constraints 39
Imbalance Price Performance issue 40
25 th of August: Black Start Test 41
25 th of August: Black Start Test 42
25 th of August: Black Start Test 43
25 th of August: Black Start Test 44
25 th of August: Black Start Test 45
25 th of August: Black Start Test 46
25 th of August: Black Start Test 47
Agenda Item Presenter Welcome Anne Fitzgerald Known Issues and Release Update David Lee Ex-Ante Market Michael Atcheson, Liam McAllister Balancing Market John Ging, Rory Cafferky Repricing Update Julie McGee Settlements Claire Kane, Sean O’Rourke, John O’Dea Query Management Claire Breslin Q&A 48
Repricing Update Application of an amended Price Materiality Threshold of 0% on a temporary basis, until such time as an I.T. solution that is capable of calculating materiality is delivered. Progress Update: • Testing of repricing solution on track – Release D to be deployed on the 15 th of October – Further 2 to 3 weeks of analysis (in test) post deployment. • Commencement of repricing early to mid November. • Alignment with M+13 resettlement? – Unable to meet first M+13 runs. • Data for M+13 required early October. – Potentially able to meet M+13 by November / December. – Adhoc resettlement for October and November 2018 . • To be completed mid 2020. 49
Repricing and Price Materiality Threshold Parameter Consultation 1. Application of repricing for the period from 1 October 2018 to 11 June 2019 using the currently approved 5% Price Materiality Threshold. 2. Application of an amended Price Materiality Threshold of 0% on a temporary basis, until such time as an I.T. solution that is capable of calculating materiality is delivered. 3. Raising an Urgent Modification to the Trading and Settlement Code, to amend Section E.3.8 on a temporary basis with the intention of not carrying out repricing from 1 October 2018 to 11 June 2019. 4. Raising an Urgent Modification to the Trading and Settlement Code, to amend Section E.3.8 on an enduring basis in order to require any repricing to be completed by the 13 th month after the trading date at the latest. 50
SEMO review of options posed based on current work-plan. Proposal Status 1. Apply 5% PMT SEMO do not currently have a repricing solution capable of applying a 5% PMT. To implement this solution would mean repricing would not commence until at least Q4 2020. 2. Apply 0% PMT until an I.T Solution is Status update discussed on the previous slide. available. 3. Urgent Modification to amend Section SEMO would turn attention to implementing a solution that can E.3.8 on a temporary basis with the intention apply a 5% PMT for future periods requiring repricing. of not carrying out (or suspend) repricing from 1 October 2018 to 11 June 2019. 4. Urgent Modification on an enduring basis If a 0% PMT was applied, the plan for option 2 would apply, albeit in order to require any repricing to be October and November 2018 would not be repriced. completed by the 13 th month after the trading date at the latest. If however the intention was to apply a 5% PMT, SEMO would not have a solution in place by M + 13 for any periods requiring repricing, and therefore would be unable to reprice 1 st October 2018 to 11 th June 2019. 51
Repricing Update: Practical Issues • Fix as many issues as possible when repricing – includes those which were unknown defects at the time of a particular dispute. • Not all defects will be resolved within release D. Issue Type Count of Issue ID Issues Pricing Algorithm 10 5739; 5737; 5831; 5806; 5875; 5817; 5929; 5957; 112877; 6076 Incorrect Input Data (Late issuance of DIs; missing DIs etc) 4 Rpc3; Rpc4; Rpc1; Rpc2 Flags calculated incorrectly (RTD) 2 6105; 6003 Incorrect Application of SO Flags in Pricing 2 5720; 5973 – 6003: MWMIN STH and MW MAX STH Constraint not being correctly calculated – 6076: PN’s reverted to ‘null’ for one 5 minute Period – 6105: Unit is not being flagged despite reserve constraint being binding. • RTD is the real time decision making tool for the control centre which also calculates the flags . – Two known defects (6003 and 6105) are currently impacted by flags. – RTD cannot be re-run. The M.O currently unable to reprice these defects. 52
Disputes Issue ID Manifest Errors Repricing Summary Status 6076 Imbalance Price - Missing PN's 23rd July With vendor for a solution Unit is not being flagged despite reserve 6105 constraint being binding Fix as part of Release E. To be corrected as part of repricing Wind DI datafeed error & trip DI (15th - August) 53
Agenda Item Presenter Welcome Anne Fitzgerald Known Issues and Release Update David Lee Ex-Ante Market Michael Atcheson, Liam McAllister Balancing Market John Ging, Rory Cafferky Repricing Update Julie McGee Settlements Claire Kane, Sean O’Rourke, John O’Dea Query Management Claire Breslin Q&A 54
Resettlement Updates • M+4 Progress to Date • M+13 Resettlement Approach • M+4 Doubling Up • Ad hoc resettlement 55
Settlements : July 2019 data key process updates Settlement Run Category Run Type Runs to On Delayed – Same Delayed > 1 Dates complete Time Day publication Day 1 st – 31 st Settlements Indicative 31 17 4 10 1 st – 31 st Settlements Initial 31 29 2 - Sep 30 th 2018 – M+4 Weekly 28 28 - - Oct 27 th 2018 Resettlement 1 st – 31 st Credit Daily 66 66 - - Reports 1 st – 31 st Payments In Weekly 4 4 - - 1 st – 31 st Payments Out Weekly 4 4 - - 56
Settlements : August 2019 data key process updates Settlement Run Run Type Runs to On Delayed – Same Delayed > 1 Dates Category complete Time Day publication Day 1 st – 31st Settlements Indicative 31 19 3 8 1 st – 31 st Settlements Initial 31 28 3 - Oct 28 th 2018 M+4 Weekly 28 28 - - – Dec 1 st 2018 Resettlement 1 st – 31 st Credit Daily 66 66 - - Reports 1 st – 31 st Payments In Weekly 4 4 - - 1 st – 31 st Payments Weekly 4 4 - - Out Key points : • Increase of additional catch-up days in July & August due to Bank Holidays had an impacts on indicative publication timelines • Delays with MDP data, Instruction profiling processing issues and additional processing re-runs were other reasons which caused delays to indicative publications (sequential nature of processing also has an impact) • Initial data publications on time for ~95% of time for July & August (up from 40% for June 2019) 57
Settlement Documents publication timelines Settlement Dates Run Category Date published On Time Delayed – Same Day Delayed > 1 Day publication June 23 rd – June 29 th Settlements 05/07/2019 1 - - June 30 th – July 6 th Settlements 15/07/2019 1 - - July 7 th – July 13 th Settlements 19/07/2019 1 - - July 14 th – July 20 th Settlements 26/07/2019 1 - - July 21 st – July 27 th Settlements 02/08/2019 1 - - July 28 th – Aug 3 rd Settlements 12/08/2019 1 - - Aug 4 th – Aug 10 th Settlements 16/08/2019 1 - - Aug 11 th – Aug 17 th Settlements 23/08/2019 1 - - Aug 18 th – Aug 24 th Settlements 30/08/2019 1 - - Aug 25 th – Aug 31 st Settlements 06/09/2019 - 1 - Sep 1 st – Sep 7 th Settlements 13/09/2019 Due to publish Sep - - 13 th 58
Issues impacting SD publication timelines Date (s) Issue Impact to schedule timelines Issue Status • • Friday 6 th KIR ID 5443 (to be Settlement Documents for the Billing period of the Fix currently in test with Release published in KIR Sep 13 th ) delayed publication within same day on Sep 6 th due to September D. internal workaround process to be implemented • BMCRM SD calculation Workaround was in place for Sep 6 th publications. fails for same start or end day of Billing Period for BALIMB and CRM Other updates : • Average Outturn Availability Report update : Update on previous reports published with no data (over 60 days) 59
M4 Resettlement Cashflow (2 Months) Adjusted Amount by Component 30,000,000 25,000,000 20,000,000 € 15,000,000 10,000,000 5,000,000 0 CDIFFCN CUNIMB CDIFFCW CDIFFPI CABBPO CPREMIU CDISCOU CCA CTEST CREV CIMP CCURL CAOOPO CIMB CFC P D MB M NT Difference 2,617 7,584 63,995 79,614 206,413 289,628 396,567 549,272 985,061 1,156,01 1,855,41 2,211,12 2,611,74 6,043,14 27,201,4 € 43 Million is the Absolute Weekly M4 Cashflow up to Week 47 (01.12.2018) for BALIMB. Total SEM Payment Amount € 43,659,611.55 BALIMB Payments IN € 9,857,604.75 BALIMB Payments OUT € 33,802,006.80 60
M4 Resettlement Cashflow (2 Months) Component Difference (Exclude CFC) € 2,000,000.00 € 1,500,000.00 € 1,000,000.00 € 500,000.00 € 0.00 Cashflow ( € 500,000.00) ( € 1,000,000.00) ( € 1,500,000.00) ( € 2,000,000.00) ( € 2,500,000.00) ( € 3,000,000.00) CDISCO CDIFFPI CDIFFC CPREMI CDIFFCN CABBPO CAOOPO CCURL CCA CTEST CREV CIMP CUNIMB CIMB UNT MB WD UM P Component DIFFERENCE ( € 2,611, ( € 1,855, ( € 985,06 ( € 1,156, ( € 549,27 ( € 289,62 € 2,616.6 € 7,583.7 € 17,114. € 63,995. € 79,614. € 206,412 € 396,567 € 1,565,5 Charge Component Ad Hoc M4 Diff Charge Component Initial M4 Diff CCC -54,513,385.20 -54,132,481.27 380,903.93 CMOAU -149,395.06 -149,303.20 91.86 CCP 53,676,824.60 53,703,221.00 26,396.40 CMOAV -3,889.69 -3,888.77 0.92 CSOCDIFFP -1,253,807.92 -1,245,046.93 8,760.99 CVMO -2,911,230.34 -2,892,076.18 19,154.17 Grand Total -2,090,368.52 -1,674,307.20 416,061.32 Grand Total -3,064,515.10 -3,045,268.15 19,246.94 € 435K is the Total M4 Cashflow up to Week 47 (01.12.2018) for CRM & MO. 61
Agenda Item Presenter Welcome Anne Fitzgerald Known Issues and Release Update David Lee Ex-Ante Market Michael Atcheson, Liam McAllister Balancing Market John Ging, Rory Cafferky Repricing Update Julie McGee Settlements Claire Kane, Sean O’Rourke, John O’Dea Query Management Claire Breslin Q&A 62
Query Management – Overall Status 116 Open closed 2638 General Queries from 1.10.18 to date 63
Formal Queries and Disputes • Disputes : Disputes received in total: 100 , Completed: 96; Open: 2; Rejected: 2 • Formal Settlement Queries : Received in total: 284, Completed: 263, In progress: 20; rejected 1 64
Queries Over 20 Working Days • 63 Queries are open over 20 working days. • This is a 59% reduction on the queries over 20 working days in July. 25 Queries Over 20WD by Area 20 20 15 Series1 10 7 5 5 4 5 0 Settlement OPI Front Office Trading Registration 65
Agenda Item Presenter Welcome Anne Fitzgerald Known Issues and Release Update David Lee Ex-Ante Market Michael Atcheson, Liam McAllister Balancing Market John Ging, Rory Cafferky Repricing Update Julie McGee Settlements Claire Kane, Sean O’Rourke, John O’Dea Query Management Claire Breslin Q&A 66
Close SEMO Website: http://www.sem-o.com/ Semopx Website: http://www.semopx.com/ Queries: Info@sem-o.com; Info@semopx.com Thank you for your attendance. 67
Appendix 1 • Link to MOUG Action register – SEMO website 68
Appendix 2 • Known Issues Report 69
Known Issues Update – SEMOpx Impact to Market Resolution ID Name Description Status Participants Date Bid/Ask Curves report fails to generate To be Low impact to Members as SEMOPX. Production of Bid/Ask following an auction, for a given removed as the file would otherwise be Closed 001 jurisdiction, when there are no orders not planned Curves Report empty. received for that auction. for delivery Known issues with the delay in SEMOpx Member SEMOPX. reporting SEMOpx Member REMIT Reporting transactions are not reported Closed Jan 2019 003 transaction to ACER REMIT platform. to ACER until this is resolved. Testing of solution ongoing "The latest M7 version brought a display bug in the system. When traders enter orders using M7 client, orders from the logged in trader are shown in white instead of No material impact to coloured.This was resolved in SEMOpx Members; impacts ComTrader version 6.6.100 deployed user experience with SEMOpx. for SEMOpx members 03/05/2019. 3 rd May 2019 M7 ‘Own Orders’ platform as ‘own trades’ Closed 004 Our service provider has advised no cannot be easily downtime will be required for this differentiated from deployment however, SEMOpx competitors. Members were advised that the new ComTrader version is available for download via a dedicated link, via an operational message issued to registered Traders." 70
Known Issues Update – SEMOpx Resolution ID Name Description Impact to Market Participants Status Date Raised 22/05/2019: Bug in market view > aggregation display. If a On the trader has an order in for a certain 04/06/2019 the contract, this contract is expected new non- to display in the Market Overview in mandatory Blue indicating inclusion of own ComTrader order in the aggregation of all version orders for this contract. SEMPOpx.0 Display issue only. No impact to 6.6.100.2 was M7 – Market View Closed 05 matching. made available However it can, on occasion, be under the seen that the Market Overview still following link: displays the contract in white http://m7tradin despite containing an own order. g.deutsche- It should be noted that matching is boerse.com/sem unaffected, the bug being limited o-prod/ solely to the display colour. No material impact to SEMOpx Members. Members can view all auction results. Members will need to Message log is not retaining the ETS Auction look at auction results No Confirmed 92601 message indicating availability of Unplanned Results reports/screens to determine Delivery date the ETS Auctions availability of auction results, as opposed to reviewing the message log. 71
Known Issues Update – Balancing Market Resolution ID Name Description Impact to Market Participants Status Date REPT_102: Some instances of the Hourly Dispatch PUB_HrlyDispatchInstr report (REPT_102) The instance of the Hourly DI Report is Instructions in XML format have failed to generate on not available in XML format until it is Report Release A 5635 the MPI and as a result, are also no published as part of the Daily DI Reports, Closed Jan 29 th 2019 Intermittently appearing on the public website. The which are unaffected by this issue. The Fails to report is generated and available in HTML report is available in HTML. generate in format. XML format. Units being Unit being skipped in pricing due to “Error Release B skipped in QBOA is missed for a Unit, resulting in March 26 th 5737 in Slope Calculation” causing periodic drop Closed QBOA impact to Imbalance Price in NIV 2019 calculations Cancelled Dispatch Dispatch Instructions which are cancelled Release B Instructions are Incorrect QBOA values, resulting in March 26 th 5831 with a ‘Not Accepted’ status are being Closed being impact to Imbalance Price. processed in pricing 2019 processed in pricing 72
Known Issues Update – Balancing Market ID Name Description Impact to Market Participants Status Resolution Date 5785 RTQBOA: PBOA Intermittent switching PBOA from Simple Incorrect PBOA values, resulting in Release B Closed March 26 th 2019 COD to Complex COD impact to Imbalance Price After further investigation with the The Forecast Imbalance Report is not The PNS are currently being vendor, this report is 5844 (PNs) REPT_042 calculating the some of the data within the calculated incorrectly. The report Closed working as correctly and reports correctly. presents inaccurate information. as per the design for the TSO Demand Forecast column. After further The TSO Demand Forecast value is investigation with the inaccurate as it reads from the all vendor, this report is The Forecast Imbalance Report is not island values and reports working as correctly and 5913 REPT_042 calculating the some of the data within the Closed inaccurate figures. The report as per the design for the reports correctly. corrects itself and is accurate TSO Demand Forecast leading up to the gate closure column. The performance of the Imbalance Imbalance Pricing Pricing The Imbalance price is using the market Participants are receiving the function has improved 108598 workflow backup price for multiple periods at a time market backup price for multiple Closed and no Market Back Up producing during the night. periods at a time. Prices have been used backups since the release on 73 26th March 2019.
Known Issues Update – Balancing Market Resolution ID Name Description Impact to Market Participants Status Date Participants cannot rely on these data until the issue is resolved. Participants Incorrect MW MW QTY values in REPT_078, _079, _080 should use alternate means to formulate Release C, 5641 QTY values in Closed 11 th June 2019 . are not being calculated correctly. these totals. These data are available at REPT_078/079 the individual portfolio (unit) level in the ETS Market Results files published D+1. REPT_014: Daily REPT_014 is producing incorrect demand The data in the report are incorrect and Release C, 5751 Demand Closed 11 th June 2019 . control values not available from other sources ControlData REPT_081 hourly REPT_081 can contain records for a full day Closed Release C, 5870 Anonymized rather then on a 30 minutes basis as per Report can publish inaccurate data 11 th June 2019 . INC and DEC design Curves REPT_011 Entries for each COD offer type Impacting units with both Simple and Release C, 5644 Duplicate (Simple/Complex) leading to the duplicate Complex COD submissions. Participants Closed 11 th June 2019 . Entries entries in Daily Technical Offer Data Report to continue to use report as normal 74
Known Issues Update – Balancing Market Resolution ID Name Description Impact to Market Participants Status Date The Annual CLAF is published to the SEMO website in XLS format. The production of Annual CLAF the XML version (specified as REPT_023) is Report not REPT_023: Annual CLAF Report is not subject to a software update from the Release C, 5740 Closed 11 th June 2019 . produced and produced and available via the MPI. vendor. Market Participants and General available via MPI Public audiences can download the data from the SEMO website, albeit in a different format. Report currently creates multiple records for each registered unit, each one with a different trading site. It will create these List of 105605/ multiple records for each trading site Release C, Registered Units' Report contains duplicate records Closed 11 th June 2019 . 5753 which is assigned to the unit's report participant. It is also creating multiple (duplicate) records with a N/A trading site When retrieving VTOD from the MPI via type 2 or type 3, the SOAK WARM This leads to confusion for MPs as they QUANTITY values are incorrect. The cannot view the accurate Soak WARM 5497 VTOD Soak values shown are the SOAK HOT Release C, QUANTITY values. The SO and MO approve Closed 11 th June 2019 . Times QUANTITY values. the correct values, and those are used in Please note: the integrity of the VTOD the Scheduling & Dispatch process. set is unaffected. This is simply an incorrect display in the MPI. 75
Known Issues Update – Balancing Market Resolution ID Name Description Impact to Market Participants Status Date Various flags incorrect in REPT_011 (Daily Technical Offer Data Report) – PUMP_STORAGE FLAG, Fuel Type for Participants to continue to use report as Release C, 5756 REPT_011 Pumped Storage Units (linked to Closed 11 th June 2019 . normal PUMP_STORAGE FLAG issue), Firm Access Quantity defaulting to zero for all units (should be Trading Site FAQ) LOCL/LCLO not working across LOCL/LCLO is not applying correctly LOCL instruction is not applied resulting in Release C, 5957 Closed 11 th June 2019 . settlement day across the calendar day boundary. the QBOA to be dropped. boundaries Initial conditions being incorrectly Initial conditions being incorrectly reset Incorrect QBOA values, resulting in impact Release C, 5817 Closed 11 th June 2019 . reset in some in some circumstances to Imbalance Price circumstances DESY Pumped Storage Incorrect QBOA values, resulting in impact DESY Pumped Storage instructions are Release C, 5806 instructions are to Imbalance Price. A workaround has Closed 11 th June 2019 . not processing correctly not processing been put in place for this issue. correctly 76
Known Issues Update – Balancing Market ID Name Description Impact to Market Participants Status Resolution Date LCLO Instruction Issuing an LCLO within minutes 1 – 5 of a causing QBOAs 5 minute pricing period should still result QBOAs are dropped for the relevant 5 Release C, 5929 for whole 5 in a QBOA value being created for that Closed 11 th June 2019 . minute pricing period. minute period to period up until the LCLO instruction is drop issued. The Net Interconnector Schedule value is In Day 1 plus scope, incorrectly reporting as 0 when both Target to include in The Forecast Imbalance Report is not interconnectors are on full export. The Rel. D 5796 REPT_042 calculating the some of the data within data for the Moyle Interconnector are In Analysis the reports correctly. sometimes not contained within the Resolution: calculated and reported value for the Net Software update Interconnector Schedule attribute. from vendor In Day 1 plus scope, Target to include in REPT_022: Initial Rel. D Interconnector This report is appearing EMPTY in the Report unavailable to Market Participants 5845 Flows and In Analysis Resolution: MPI and website. and General Public. Residual Software update Capacity from vendor CR currently in review In Day 1 plus scope, The Dispatch Quantity report (REPT_068) MPs will observe incorrect values for Target to include in erroneously calculates the “Dispatch pumping mode MWh values in this report 5812 REPT_068 UOM Rel. D Quantity” field as MW for P/S units when until remedied. Settlement is unaffected In Analysis error Resolution: in pumping mode. These values should as those calculations use metered Software update 77 be calculated and reported as MWh. generation. from vendor
Known Issues Update – Balancing Market ID Name Description Impact to Market Participants Status Resolution Date In Day 1 plus scope, New users will not be able to access Access of MPI Target to include in A user who is registered in the Balancing Market historical I-SEM data before their information Rel. D 117257/6 receives a market effective date. They are not able registration date in the MPI. Public reports before In Analysis 031 to access any published information in the MPI are published to the SEMO website. Users registration Resolution: before this date market effective date. will be unable to access reports from Date Software update before registration. from vendor In Day 1 plus scope, Target to include in May cause issues for Market Participants Rel. E REPT_082 PUB_AvgOutturnAvail is publishing data 5977 REPT_082 that are validating against In Analysis for de-registered units PUB_DailyRegisteredUnits Resolution: Software update from vendor VTOD changes will take effect in the In Day 1 plus scope, Approved changes to VTOD are taking effect on market systems on the date of approval. target to include in VTOD Changes the operational day that the change is approved, Rel E 5942 Taking Effect In Analysis rather than the next Trading Day for which Gate Note – SEMO are implementing a Resolution: on Approval Closure 1, has not yet occurred. workaround whilst this defect remains Software update open. from vendor In Day 1 plus scope, Incorrect target to include in QBOA are not calculated for the impacted application of LOCL instruction intermittently not being applied Rel E 6021 units, resulting in impact to Imbalance In Analysis LOCL/CRLO after a CRLO has been issued. Resolution: Price. Instruction Software update from vendor 78
Known Issues Update – Balancing Market ID Name Description Impact to Market Participants Status Resolution Date Application of Imbalance Pricing validation is resulting in n Day 1 plus De Minimis QBOA volumes greater than DMAT to not be scope, target to Acceptance included in Imbalance Pricing calculations. include in Rel E Incorrect QBOA values, resulting in 5991 Threshold Where a Unit has an Accepted Offer and In Analysis impact to Imbalance Price (DMAT) in Accepted Bid, one of which is below DMAT, Resolution: Imbalance both volumes are being omitted from the Software update Pricing calculation. from vendor In Day 1 plus The report may display incorrect scope, Release REPT_008: I Total Unit Availability field within the Total Unit Availability values. The TBC 5952 mbalance Imbalance Price Report is being calculated report presents inaccurate In Analysis Price Report incorrectly. information. Resolution: Software update from vendor In Day 1 plus This issue affects 39 reports. This is a scope, Release 5195 Report display HTML report is displayed in UTC rather than display issue only, as the values and TBC In Analysis always in local time. corresponding time interval are Resolution: correct. Software update from vendor 79
Known Issues Update – Balancing Market Resolution ID Name Description Impact to Market Participants Status Date TBC Resolution: SEMO are carrying out an Report is designed to show NTC (Net Report is designed to show NTC (Net impact Transfer Capacity) values however is Transfer Capacity) values however is The assessment as currently showing the TTC (Total Transfer currently showing the TTC (Total Transfer 82044 Interconnector In Analysis this impacts Capacity) values. This is due to a Capacity) values. This is due to a NTC report multiple IT configuration change requested by configuration change requested by systems and National Grid prior to go-live National Grid prior to go-live also has a knock on impact for other processes. This impact report availability to participants TBC as well as use of dynamic reporting to The SEMO and SEMOpx website currently has SEMO_ SEMO and provide an accurate representation of the issues with the dynamic reporting, report Resolution: WEB.00 SEMOpx ongoing static reports. All reports are available in the In Analysis retention and ongoing manual workaround to Software update 1 issues static section and manual workaround are publish reports from vendor carried out on a daily basis to ensure reports are not missed TBC MPS are unable to download historical SEMO_ SEMO and The SEMO and SEMOpx websites currently reports from the SEMO and SEMOpx WEB_0 SEMOpx website In Analysis Resolution: does not show historical reports. website. A CR has been raised with the 02 File retention Software update website vendor to make these files available from vendor 80
Known Issues Update – Balancing Market Resolution ID Name Description Impact to Market Participants Status Date This will result in PNs reverting to a ‘null’ TSO rejection of Under Test PNs that have been value for the entire period covered by the submitted in the same Type 3 transaction (multiple TBC rejected PN submission. Type 3 PNs units in the same xml) as other PNs (i.e. not Under 112877 Validation Test) will result in the rejection of all PNs at gate In Analysis Resolution: Note – SEMO would ask Market Error closure. Rather than reverting to the previous Software update Participants to submit Type 3 Under Test approved submission as per the design, the system from vendor PNs in separate submissions. will apply a ‘null value’. Reports not showing first ISP interval for trade date The MPs will not be able to source data TBC in report. In the Reports for the first ISP of a trade date from this REPT_078: Aggregated Contract Quantities for process of missing 1st report until the issue is remedied. These Resolution: 5329 Generation submission ISP of Trade data can be sourced elsewhere. They are Software update REPT_079: Aggregated Contract Quantities for to the RA's Day available in the ETS Market Results from vendor Demand for approval published on the SEMOpx website, D+1. REPT_080: Aggregated Contract Quantities for Wind TBC Data is currently duplicated on the Daily Meter following dates in the dynamic meter Duplicate entries are appearing in the Dynamic Resolution: 109895 Data Report data report on the website. 17th + In Analysis report for Daily meter data. Software (Website) 27th Nov 7th Dec has 3 line entry per update from timestamp 13th Dec 11th + 19th Jan. vendor Incremental When a participant submits 9 Price Quantity TBC & Pairs for Incremental and Decremental costs As a workaround participants are Decrement curves the sequences do not see the prices as requested to not submit 9 PQ pairs Resolution: 110321 In Analysis al Price monotonically increasing and then defaults them when submitting Commercial Offer Software quantity to zero. This is a defect and has knock on Data. update from pairs impacts on the scheduling of LTS, RTC and RTD vendor 81
Known Issues Update – Balancing Market Resolution ID Name Description Impact to Market Participants Status Date In the Missing TBC 2 Reports are currently not publishing to No material impact to Market process of Reports on the new SEMO website. REPT_027 (Four Participants or General Public as these submissio 5587 the new Resolution: Day Rolling Wind Forecast) and REPT_013 reports are now being uploaded n to the SEMO Software update (Daily Commercial Offer Data) manually to the SEMO website. RA's for Website from vendor approval The PQ pairs reported in REPT_081 In the REPT_081 erroneously report values that exceed TBC Currently the report cumulatively adds process of hourly the generation capacity in Ireland. The each MW quantity to the last MW quantity submissio 5603 Anonymized report is inaccurate and the commercial Resolution: rather then the difference. This results in n to the INC and DEC bidding behaviour of the aggregated Software update erroneous MW values in the report. RA's for Curves generation on the Island is not accurately from vendor approval represented. TBC The Daily and Hourly SO Interconnector 5794 REPT_030, Trades reports are failing to publish to the Participant unable to acquire these data In Analysis Resolution: REPT_103 MPI and subsequently to the SEMO until this issue is addressed Software update website from vendor 82
Known Issues Update – Balancing Market Resolution ID Name Description Impact to Market Participants Status Date Market Participants Market tools may fail to REPT_102: TBC This report will now generate even if there is a pull this report where a dispatch instruction Hourly Dispatch 5841 null Dispatch Instruction. However this conflicts contains a null dispatch instruction. Report is In Analysis Instructions Resolution: with the XSD schema for the report now available in all cases were before the Report ITS Update report was available intermittently. TBC REPT_088 Net The report is published every hour instead of Information is available less frequently. 5317 Imbalance every half hour , as specified by the ITS, Market Participants continue to use the In Analysis Resolution: Forecast Volume C. information as available. ITS update TBC Submitted Physical Notifications not used in Incorrect QBOA are calculated for the 6076 PNs not used in Imbalance Price calculation for an isolated impacted units, resulting in impact to In Analysis Resolution: Imbalance Pricing Imbalance Pricing Period. Imbalance Price. Software update from vendor For P/S Units, intermittent representation of duplicate values (MWOF) instructions appearing. 102081 REPT_006: Daily For P/S units, the Market Participant will need No Confirmed This is due to internal processing of records Unplanned DI Report to ignore the duplicate entry until resolved. Delivery date and does not affect the Instruction Profiling process, only the outbound report. 83
Known Issues Update – Settlement Resolution ID Name Description Impact to Market Participants Status Date Incorrect result for In REPT_043, the CPREMIUM & CDISCOUNT and The REPT_043 will be incorrect for these CDISCOUNT charge calculations for the Release A 5654 CPREMIUM for the charge types until the issue is resolved Closed Jan 29 th 2019 IRCU unit are incorrect due to missing IRCU unit in within the software. data. REPT_043 Settlement Report is reporting QCOB Minimal Impact the report only REPT_044, and QCNET as daily values instead of 30 represents a single value for both QCOB Release A 5658 incorrect values for minute values, the calculation is Closed Jan 29 th 2019 and QCNET in REPT_033, the settlement QCOB, QCNET working as designed using each ISP calculation is unaffected. values in the Settlement calculations. PN and Availability are not being DQ values not correct, leading to 5741 FPN / Controllable Release A profiled correctly i.e. the start and end incorrect settlement charge calculations Closed Jan 29 th 2019 Wind (DQ) of trading period effective values. in all settlement artefacts 84
Known Issues Update – Settlement Resolution ID Name Description Impact to Market Participants Status Date FPN within period leading to incorrect QFPN being calculated in MMS based on The FPN value in IP Instruction Profiling outcomes, values of FPN profile on each half hour Release A 5757 is different from affecting quality of data used for Closed Jan 29 th 2019 boundary point only and not considering CSB settlements determinants and charge changes in profile within the half hour. type calculations. Current logic needs to be modified so that CSB gets the correct complex offer data for when a complex bid has been used for a Some Fixed Cost calculations are Release A 5761 Fixed Costs Closed Jan 29 th 2019 BOA. Fixes required on both Settlements incorrect. System (CSB) and upstream Market Systems (MA/MI). IP Time Weighted Average calculation of Release A 5766 Actual Availability qAA only referencing beginning and end of In some cases, qAA not correct. Closed Jan 29 th 2019 trading period 85
Known Issues Update – Settlement Resolution ID Name Description Impact to Market Participants Status Date CIMB, Premium & Discount for IRCU and Interconnector settlements for CIMB, Release A 5652 Interconnectors Closed Jan 29 th 2019 IEU not using QAO and QAB. CPREMIUM, CDISCOUNT not correct. Traded positions of TU units are not Difference Charges and Payments for Release A 5646 Autoproducers being considered for difference autoproducer units not correct when Closed Jan 29 th 2019 payments and charges. traded positions exist. CCA is not being calculated for Supplier Currency lite windfarms registered as suppliers. Settlement Release A 5710 adjustment charge CCA should be calculated for all supply Reports/Documents/Statements incorrect Closed Jan 29 th 2019 defect units (currently only being charged if QMLF < 0) 86
Known Issues Update – Settlement Resolution ID Name Description Impact to Market Participants Status Date CFC not available Due to internal data transfer issues, Release A 103722 in Settlement the CFC costs are not available in the CFC not available in Settlement artefacts Closed Jan 29 th 2019 artefacts settlement artefacts 5799 Incorrect CFC and Caused by incorrect QBOA calculation Partially Release A CFC and Premium data incorrect Jan 29 th 2019 Premium Payments in particular circumstances Closed CRM Within Day Difference Charges 5743 CRM Sttl, W/in Day Release A will not make use of a BOA where Calculation incorrect at the time. Closed Jan 29 th 2019 Difference Charges there is both a QAO and a QAB. 87
Known Issues Update – Settlement Resolution ID Name Description Impact to Market Participants Status Date 5804 No Load Cost Recoverable No Load Costs in CFC Release A Incorrect value in CFC for these cases Closed Jan 29 th 2019 calculation in CFC double what they should be Settlement Document incorrect amount Incorrect amounts reported in Settlement 5881 Settlement for New gross amount and Net amount document when settlement calendar is Release A Closed Jan 29 th 2019 Document when Settlement Calendar is configured configured with 2 AH runs for a Billing with 2 AH runs for a Billing Period Period Settlement Document incorrect amount Incorrect amounts reported in Settlement 5881 Settlement for New gross amount and Net amount document when settlement calendar is Release A Closed Jan 29 th 2019 Document when Settlement Calendar is configured configured with 2 AH runs for a Billing with 2 AH runs for a Billing Period Period 88
Known Issues Update – Settlement Resolution ID Name Description Impact to Market Participants Status Date Difference Payment Calculation sets final Difference Payment Calculation sets Difference payment Calculations are Feb 19th 2019 5883 QDIFFTRACK to zero if final QDIFFTRACK to zero if there are incorrect when a supplier unit has no Closed Closed as hotfix there are no intraday no intraday trades - Supplier Unit intraday trades trades - Supplier Unit ISEM_OUI and CSB_CIMB incorrectly CSB is not calculating the No impact to market participants manual Feb 18th 2019 5931 Closed been charged to interconnectors CIMB incorrectly workaround is in place. Closed as hotfix interconnectors QDIFFTRACK was calculated Settlement 5884 QDIFFTRACK Error for Feb 2nd 2019 incorrectly where a capacity market reports/documents/Statements were Closed CAU units Closed as hotfix unit only has day ahead trades. delayed in publication to participants Biased Quantities for Biased Quantities are currently being The SEMO settlements team has Release B Generator Units calculated for all generator units developed a work around for this issue. March 26 th 5657 Closed registered as part of which is registered as part of an We will retain the item on this list, but it 2019 an Autoproducer site Autoproducer site has no impact on the Market Participants. Release B March 26 th 5688 Bills case Bill cases taking over two hours to Affects Settlement operations meeting Closed performance run and process agreed upon publication time lines 2019 89
Known Issues Update – Settlement Resolution ID Name Description Impact to Market Participants Status Date The CNL & CSU are being displayed in NI units CNL & CSU REPT_044 for NI units in EUR. in REPT_44 being Issue with shadow settling CNL & CSU as 5 th April 2019 5988 displayed in Closed These costs are to be reported in GBP as report determinants are in EUR. EUR. Report per the report registered currency. should be in GBP DSUs should not have an undelivered Affecting settlement calculations for DSUs, Release C, 5888 Metered Quantity quantity. Metered quantity must be made resulting in non-zero undelivered quantities, Closed 11 th June 2019 . for DSUs equal to the dispatched quantity which should be zero. Settlement reports/documents/Statements All Settlement reports produced in unavailable to participants after 2 months Settlement reports MMS currently only have a retention of through the MPI. Temporary workaround Release C, 5886 are only being kept 2 months in the MPI. They are then applied on the 21/01/2019 ensures that Closed 11 th June 2019. for 2 months archived and not available through the no further report will be removed from front end the MPI. Vendor is working on solution to republish all Settlement reports/documents/Statement to MPI Period of Market Operation Trading Not applying the correct starting points MPOP FPN Period Starting points in CSB not aligned for FPNs in relation to the calculation of Release C, 5940 Misalignment with with the MM, including incorrect Closed 11 th June 2019. fixed costs for the Period of Market MMS application of minute resolution. Should Operation be 30 min resolution. 90
Known Issues Update – Settlement Resolution ID Name Description Impact to Market Participants Status Date DSUs Day Ahead, Within Day Difference Quantities & Charges are being DSUs specific – The calculation of incorrectly applied to DSUs as per F.18.4 QDIFFTRACK should be zero as per F.18.5 & F18.5 of the TSC. exclusion clause within the TSC including 5950 Difference & NP Release C, Calculation of QDIFFTRACK for DSUs F2.1.2. Closed 11 th June 2019. Charges for DSUs being incorrectly applied to DSUs Day Ahead, Within Day Difference Ex-Ante quantities are tracked via the Quantities & Charges and Non- FNDDS calculation. Performance Charges There are two problems: a) The Fixed Cost calculation of CNLR will for (most) periods of MPOP include the interval prior to MPOP start in the 5972 Incorrect CNLR to Release C, summation. Incorrect CNLR to Generators Closed 11 th June 2019. Generators b) The Fixed Cost calculation of CNLR will for (most) periods of MPOP not do correct check on Dispatch Quantity for the last interval. Incorrect CFC and Caused by incorrect QBOA calculation in CFC and Premium data incorrect. Release C, 5799 Premium Closed 11 th June 2019 particular circumstances Improvement in QBOA Calculation Payments Multiple instances of QAO and QAB being inconsistent Multiple instances of QAO and QAB i.e. large positive being inconsistent i.e. large positive Multiple instances of QAO and QAB being Release C, 5936 Closed 11 th June 2019 QAO and a large QAO and a large negative QAB when inconsistent negative QAB FPN and QD are similar. when FPN and QD 91 are similar.
Known Issues Update – Settlement Resolution ID Name Description Impact to Market Participants Status Date Contiguous Periods of Operation are not Error in Import of being applied correctly where the Dispatch Instruction Profile is not being Dispatch Dispatch Instruction Profile has not Release C, 5979 imported correctly into CSB where there Closed 11 th June 2019 . Instruction Profiles imported correctly. Resulting in incorrect are updated values from MA to Settlement CFC calculation for affected Settlement Day/units. Difference QDIFFPIMB not being calculated where Payment System not considering the scenario there are no Day Ahead Trades. Calculation does where there are no Day Ahead trade not set final and thereby no QDIFFDA. Release C, 5990 Missing trading Period calculation & data Closed 11 th June 2019 . QDIFFTRACK to 0 if on reports where there are no Day Ahead there are no Day QDIFFDA should default to 0 in trades. Ahead or Intra Day calculation of QDIFFTRACK. trades BOA and Start up / System changes between Simple and no load cost not Release C, 5909 Complex COD use when the Order of This affects CFC calculation Closed 11 th June 2019 . being calculated the first BOA does not equal 1. when first BOA = 0 BOAs were intermittently calculated FPN yet large variances in QAO and QAB. incorrectly when QD was equal to the IPQBOA values were not correct. 5893 Incorrect IPQBOA Release C, FPN with a BOA generated. Also where Temporary workaround is in place. Closed 11 th June 2019 . values QD is similar to FPN yet large variances Permanent solution to be provided by in QAO and QAB. ABB Settlement Documents containing re- Resettlement - settlement Billing periods, Settlement the previous_gross_amount figure is Defect does not affect participant SD reports. Document Previous correctly populated as the figure from the Defect confirmed to only affect internal 6042 Purchases and Closed 5 July 2019 original settlement however none of the application UI screen. As such issue has been Previous Sales are ***_prev figures are being populated. closed – No impact to market participants 92 not populated correctly
Known Issues Update – Settlement Resolution ID Name Description Impact to Market Participants Status Date Trading Site Reg data being end dated in the settlement system when Error occurs, In Day 1 plus therefore correct TS config and scope, target to Registration Import for Trading Sites(TS) calculations are affected. include in Rel D Trading Site Units is creating an Error for future effective 6010 not linked to In Analysis date elements and end dating TS Settlement check and Manual Resolution: GU/SU IDs in CSB registration Data. workaround in place to ensure Trading Software site configuration is applied before update from running settlement. vendor In Day 1 plus scope, Target to FPN Curve not include in Rel. D CSB not receiving correct FPN curve Incorrect or No Heat State being applied applying Heat 5944 from Balancing Market resulting in within CSB, therefore Start-Up costs not In Analysis State to CFC inputs Resolution: incorrect Start-Up status. being included within the CFC calculation correctly Software update from vendor In Day 1 plus scope, Target to The system shall calculate the include in Rel D Error in calculation Calculation is currently setting the last CDIFFCNPB and CDIFFCNPA as zero in 6004 of CDIFFCNPA and and first ISP to CDIFFCNPA / B_(Ω(γ -1)) for In Analysis the 1st and last ISP of the capacity year Resolution: CDIFFCNPB the Capacity Tear for each CMU for each CMU. Software update from vendor 93
Known Issues Update – Settlement Resolution ID Name Description Impact to Market Participants Status Date In Day 1 plus scope, Target to Aggregated Metered Demand not being Metered Volumes include in Rel. D published on RET_066. Currently only by Jurisdiction Unable to view the Aggregated Metered 5923 reporting Aggregated Metered In Analysis (REPT_066) - Zero Demand within the Report Resolution: Generation Metered Demand Software update from vendor The Stop Loss Limits (CSLLA/CSLLB) In Day 1 plus calculation is looping over units with scope, Target to Stop Loss Limits Reliability Options that are associated Stop Loss limits are not being calculated include in Rel. D (CSLLA/CSLLB) is with a Trading Site. The settlement for IU and CAUs for the application of the 5922 not being calculation should also include units In Analysis a calculated % applied to the Non- Resolution: calculated for IU with Reliability Options that are not performance Software and CAU associated with a Trading Site like CAU update from and IU units. vendor In Day 1 plus scope, target to PUBLICATION_TIMESTAMP attribute is include in Rel. D The difference in time is very brief and 5322 REPT_048 incorrectly assigned the start time of has no material effect on the report In Analysis Collateral Report the credit assessment, rather than the Resolution: quality finish time. Software update from vendor 94
Resolution ID Name Description Impact to Market Participants Status Known Issues Update – Settlement Date In Day 1 plus scope, Target to MA is currently providing Startup Flag include in Rel. D Startup flag for and Warmth State for Synchronize 5910 CSUR with Warmth This affects CFC calculation In Analysis Dispatch Instructions that relates to Resolution: State CSU calculation Software update from vendor In Day 1 plus Fixed Cost CFC calculation will sum the CIMB, scope, Target to Calculation sums CPREMIUM, CDISCOUNT, CABBPO, include in Rel. D values from all CAOOPO and CCURL amounts from both Incorrect CFC amounts in settlement documents AdHoc runs of a 6035 Ad Hoc Run #1 and Ad Hoc Run #2. where there is an instance of an ad-hoc completed In Analysis Billing Week instead Resolution: It should only make use of the values from over a previous ad-hoc for the same billing period. of using the latest Software the latest Ad Hoc Run.. AdHoc run for each update from day vendor In Day 1 plus Simple/Complex COD: Flags and Tags scope, target to include in Rel. E are not being applied in the half hours Prices are being applied only to the period 5943 Simple/Complex they should. Prices are being applied where the DI is effective then persisting for all In Analysis COD only to the period where the DI is Resolution: associate BOAs. effective then persisting for all Software associate BOAs. update from vendor A Small subset of units have a unique In Day 1 plus Units not being reserve curve whereby they have both scope, target to flagged on upward a positive slope at the beginning of the This defect is only present on four units. If the include in Rel. E slope of reserve curve and a negative slope at the end unit is on a positive slope and the constraint is 6105 In Analysis curve, despite of the curve. If reserve is binding all binding the unit will not be flagged and may Resolution: reserve constraint units with a non zeroslope should be contribute to the price as a result. Software binding flagged. The positive slope is not being update from vendor flagged correctly. 95
Known Issues Update – Settlement Resolution ID Name Description Impact to Market Participants Status Date In Day 1 plus scope, target to FMOC FX rate include in Rel. E applied not aligned FMOC is applying the trading day FMOC is applying the trading day exchange 5808 with the Trade and exchange rate of the last day of the In Analysis rate of the last day of the month. Resolution: settlement code month. Software 1.3.9. update from vendor In Day 1 plus QD determinant if a GU does not have an RO in which to scope, target to QD determinant missing from missing from calculate difference charges QD not present include in Rel. E REPT_44 in indicative & initial reports REPT_44 in on REPT_044 as it is calling the value from 6044 for a range of units and dates based In Analysis indicative & initial the difference charges calculations. Result Resolution: on Reliability Options not being reports for a range is QD is never published in REPT_044 for Software present for the units. of units and dates affected units (particularly wind units) update from vendor In Day 1 plus scope, target to Report 044 missing Market Participants unable to view the include in Rel E Accept time for Settlement Report not showing 5953 accept time of QBOAs used within In Analysis QAO and QAB Accept Times for QAO & QAB Resolution: Settlement determinants Software update from vendor In Day 1 plus scope, drop TBC 31st Indicative related to long day Multiple units had no BOAs created for the 6001 ISEM Slope Error affecting 11 units - still being In Analysis Resolution: 31st March Indicative Settlement IP run. investigated by ABB Software 96 update from vendor
Known Issues Update – Settlement Resolution ID Name Description Impact to Market Participants Status Date In Day 1 plus Market participants and any third-party scope, target to The timestamp attribute in the Value system providers should ignore the include in Rel E 5314 REPT_043, _044 element contains +1 second, which it additional 1-second on the timestamp and In Analysis Resolution: should not. consider the time to be exactly on the ISP Software update interval. from vendor In Day 1 plus scope, target to CNL in CFC not being No Load costs are not being paid include in Rel E Multiple participants may be underpaid until 123413 calculated correctly correctly in some instances in CFC In Analysis defect is fixed. in M4 calculation of M+4. Resolution: Software update from vendor In Day 1 plus QAOBIAS / QABBIAS scope, target to M+4 QABBIAS & QABUNDEL volumes are Ranked Set is being presented to the calculation incorrect ordering of include in Rel E being calculate lower than expected by ranking number descending within position K 6083 ranked set for In Analysis outcomes. of the QABBIAS & QABUNDEL calculations calculation leads to Resolution: Similar to QABBIAS defect 6047 incorrectly. This should be ascending incorrect result Software update from vendor In Day 1 plus QAOBIAS / QABBIAS scope, target to Ranked Set is being presented to the calculation incorrect ordering of include in Rel E Initial Calculation of ordering & ranking by ranking number descending within position K 6047 ranked set for In Analysis not performing in ascending order. of the QAOBIAS / QABBIAS calculation calculation leads to Resolution: incorrectly. This should be ascending incorrect result Software update from vendor 97
Known Issues Update – Settlement Resolution ID Name Description Impact to Market Participants Status Date Where data is not present in CSB , a In Day 1 plus Defect 6066 - CSB default value of zero shall apply within Seeing inconsistencies between trading periods scope, target to not applying a the settlement calculations to allow for for a number of charge codes on statements & include in Rel E default value of zero the full calculation, publication of 48 reports within Indicative, Initial and re- CR118 In Analysis in settlement trading periods that is to be reflected settlement. Unable to correctly shadow Resolution: calculations where within statements , reports. A default settlement off inconsistent statements & Software update data is not present value is not being applied resulting is reports from vendor missing trading periods. In Day 1 plus scope, target to CFC calculation is COCMWP element of CFC was incorrectly include in Rel E including values for Some participants have been over paid CFC in 6054 calculated from 00:00 on 30/09/18 In Analysis intervals prior to the first week of market for M+4. instead of 23:00 on 30/09/18. Resolution: Market Start Software update from vendor A defect fix in release C corrected incorrectly applied DSU difference In Day 1 plus charges within Initial settlement. These scope, target to The correction of incorrect difference charges Re-settlement of charges should be reflected / refunded in include in Rel E applied to DSUs are not being reflected within 6065 DSU Difference re-settlement due to the fix for the In Analysis their re-settlement statements or settlement charges defect. This is not being reflected within Resolution: documents. the re-settlement calculation of Software update difference charges and on the re- from vendor settlement settlement documents. In Day 1 plus scope, target to After the clock change the push & or CSB ISEM CSB FX rate include in Rel E is not applying the FX rate to the trading Inaccurate settlement due to FX rate for 1hour 5997 after short day In Analysis period 23:30 and & 00:00 correctly when period incorrect Resolution: they change. Software update 98 from vendor
Known Issues Update – Settlement Resolution ID Name Description Impact to Market Participants Status Date TBC Inconsistency between detailed and Incorrect rounding applied to detail summary records within the same Resolution: 5339 REPT_043 records. Summary and Detail records do In Analysis REPT_043. Research indicates this to be Software not sum correctly. small amount relative to document totals. update from vendor TBC CCC, CCP and CSOCDIFFP settlement for NI units not applying the Annual 5772 Capacity CCC, CCP and CSOCDIFFP settlement for Resolution: Capacity Exchange rate as per G.1.3.5 & In Analysis Charges/Payments NI units not correct. Software G.1.3.6. Balancing market FX rate update from incorrect being applied. vendor TBC Trading Periods misalignment has QD and QM not Long Day Trading periods not aligned resulted in the Long day trading periods Resolution: 5890 matching on long between MAMI and CSB. In Analysis being incorrectly settled within Initial Software day (28/10/18) Settlement. update from vendor TBC Dropdown filters 11/03/2019 operational day is not not available on SEMO Website Settlement Calendar > available and possibly additional trade Resolution: 105608 the SEMO website Publication > “Settlement Documents” In Analysis dates. We will confirm these dates once Software Settlement is not present for users to filter. available update from Calendar vendor 99
Known Issues Update – Settlement Resolution ID Name Description Impact to Market Participants Status Date The Controllable flag status in registration details contained within Generator Operational Characteristics that also has Technical Offer Data don’t ISEM_OUI_ExPost_In match what’s in the Resource Balancing M+ 4 Resettlement will move back into struction_Profiler_M TBC screen. This is an issue while trying to a regression test phase for a short +4_Generator rerun IP for M+4. The registration period and re-planned for production. Operational Resolution: 113784 details within Initial Ex-Post \ Initial An update will be provided by the In Analysis Characteristics Software Instruction Profile \ Instruction Profile settlement team with the appropriate _changes required for update from Input \ Generator Operational changes made to the settlement 01/10/2018 and vendor Characteristics screen are incorrect calendar. going forward compared to what’s in Market Information \ Registration\ Interface Views\ Resource Balancing this is affecting controllable flag status TBC After the clock change the push & or ISEM CSB FX rate CSB is not applying the FX rate to the Inaccurate settlement due to FX rate Resolution: 5997 after short day In Analysis trading period 23:30 and & 00:00 for 1hour period Software incorrect correctly when they change. update from vendor TBC Differences in BOA Differences in BOA values between OUI Missing volumes from Initial IP leading Resolution: 5998 values between OUI In Analysis and CSB intermittently to inaccurate balancing settlement Software and CSB update from vendor 100
Recommend
More recommend
