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 Planned Report not REPT_023: Annual CLAF Report is not subject to a software update from the Release C, 5740 Resolution produced and produced and available via the MPI. vendor. Market Participants and General May 2019 . Date 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 Planned 105605/ multiple records for each trading site Release C, Registered Units' Report contains duplicate records Resolution 5753 which is assigned to the unit's May 2019 . report Date 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 Planned 5497 VTOD Soak values shown are the SOAK HOT Release C, QUANTITY values. The SO and MO approve Resolution Times QUANTITY values. May 2019 . the correct values, and those are used in Date Please note: the integrity of the VTOD the Scheduling & Dispatch process. set is unaffected. This is simply an incorrect display in the MPI. DESY Pumped Storage Incorrect QBOA values, resulting in impact Planned DESY Pumped Storage instructions are Release C, 5806 instructions are to Imbalance Price. A workaround has Resolution not processing correctly May 2019 . not processing been put in place for this issue. Date 11 correctly
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 Planned Participants to continue to use report as Release C, 5756 REPT_011 Pumped Storage Units (linked to Resolution normal May 2019 . PUMP_STORAGE FLAG issue), Firm Date Access Quantity defaulting to zero for all units (should be Trading Site FAQ) LOCL/LCLO not Planned working across LOCL/LCLO is not applying correctly LOCL instruction is not applied resulting in Release C, 5957 Resolution settlement day across the calendar day boundary. the QBOA to be dropped. May 2019 . Date boundaries Initial conditions Planned being incorrectly Initial conditions being incorrectly reset Incorrect QBOA values, resulting in impact Release C, 5817 Resolution reset in some in some circumstances to Imbalance Price May 2019 . Date circumstances DESY Pumped Storage Incorrect QBOA values, resulting in impact Planned DESY Pumped Storage instructions are Release C, 5806 instructions are to Imbalance Price. A workaround has Resolution not processing correctly May 2019 . not processing been put in place for this issue. Date correctly 12
Known Issues Update – Balancing Market Resolution ID Name Description Impact to Market Participants Status Date LCLO Instruction Issuing an LCLO within minutes 1 – 5 of a causing QBOAs 5 minute pricing period should still result Planned QBOAs are dropped for the relevant 5 Release C, 5929 for whole 5 in a QBOA value being created for that Resolution minute pricing period. May 2019 . minute period to period up until the LCLO instruction is Date drop issued. VTOD changes will take effect in the TBC Approved changes to VTOD are taking market systems on the date of approval. VTOD Changes effect on the operational day that the Resolution: 5942 Taking Effect on change is approved, rather than the next Note – SEMO are implementing a In Analysis Software Approval Trading Day for which Gate Closure 1, workaround whilst this defect remains update from has not yet occurred. open. vendor TSO rejection of Under Test PNs that This will result in PNs reverting to a ‘null’ have been submitted in the same Type 3 value for the entire period covered by the TBC transaction (multiple units in the same rejected PN submission. xml) as other PNs (i.e. not Under Test) 112877 Type 3 PNs Resolution: will result in the rejection of all PNs at In Analysis Validation Error Note – SEMO would ask Market Software gate closure. Rather than reverting to the Participants to submit Type 3 Under Test update from previous approved submission as per the PNs in separate submissions. vendor design, the system will apply a ‘null value’. 13
Known Issues Update – Balancing Market Resolution ID Name Description Impact to Market Participants Status Date Market Participants Market tools may fail REPT_102: This report will now generate even if there to pull this report where a dispatch TBC Hourly Dispatch is a null Dispatch Instruction. However this instruction contains a null dispatch 5841 In Analysis Instructions conflicts with the XSD schema for the instruction. Report is now available in all Resolution: Report report cases were before the report was ITS Update available intermittently. TBC The Daily and Hourly SO Interconnector 5794 REPT_030, Trades reports are failing to publish to the Participant unable to acquire these data Resolution: In Analysis REPT_103 MPI and subsequently to the SEMO until this issue is addressed Software website update from vendor The Net Interconnector Schedule value is TBC incorrectly reporting as 0 when both The Forecast Imbalance Report is not interconnectors are on full export. The Resolution: 5796 REPT_042 calculating the some of the data within the data for the Moyle Interconnector are In Analysis Software reports correctly. sometimes not contained within the update from calculated and reported value for the Net vendor. Interconnector Schedule attribute. 14
Known Issues Update – Balancing Market Resolution ID Name Description Impact to Market Participants Status Date This impact report availability to TBC participants as well as use of dynamic SEMO and The SEMO and SEMOpx website currently reporting to provide an accurate Resolution: SEMO_WE SEMOpx has issues with the dynamic reporting, representation of the static reports. All In Analysis Software B.001 ongoing report retention and ongoing manual reports are available in the static section update from issues workaround to publish reports and manual workaround are carried out vendor on a daily basis to ensure reports are not missed In Day 1 plus scope, Release May cause issues for Market Participants TBC REPT_082 PUB_AvgOutturnAvail is 5977 REPT_082 that are validating against In Analysis Resolution: publishing data for de-registered units PUB_DailyRegisteredUnits Software update from vendor TBC MPS are unable to download historical SEMO and reports from the SEMO and SEMOpx SEMO_WE SEMOpx The SEMO and SEMOpx websites Resolution: website. A CR has been raised with the In Analysis B_002 website File currently does not show historical reports. Software website vendor to make these files retention update from available vendor 15
Known Issues Update – Balancing Market Resolution ID Name Description Impact to Market Participants Status Date TBC Resolution: SEMO are carrying Report is designed to show NTC (Net Report is designed to show NTC (Net out an impact Transfer Capacity) values however is Transfer Capacity) values however is The assessment as this currently showing the TTC (Total Transfer currently showing the TTC (Total Transfer 82044 Interconnector In Analysis impacts multiple IT Capacity) values. This is due to a Capacity) values. This is due to a NTC report systems and also configuration change requested by configuration change requested by has a knock on National Grid prior to go-live National Grid prior to go-live impact for other processes. TBC REPT_022: Initial Resolution: Interconnector This report is appearing EMPTY in the MPI 5845 There are no data available in the report. In Analysis Software update Flows and and website. from vendor Residual CR currently in Capacity review 16
Known Issues Update – Balancing Market Resolution ID Name Description Impact to Market Participants Status Date Data is currently duplicated on the TBC Daily Meter following dates in the dynamic meter Duplicate entries are appearing in the 109895 Data Report data report on the website. 17th + 27th In Analysis Resolution: Dynamic report for Daily meter data. (Website) Nov 7th Dec has 3 line entry per Software update timestamp 13th Dec 11th + 19th Jan. from vendor TBC REPT_008: The report may display incorrect Total Total Unit Availability field within the Imbalance Unit Availability values. The report Resolution: 5952 Imbalance Price Report is being In Analysis Price presents inaccurate information. Software update calculated incorrectly. Report from vendor TBC REPT_088 The report is published every hour instead Information is available less frequently. Net 5317 of every half hour , as specified by the ITS, Market Participants continue to use the In Analysis Resolution: Imbalance Volume C. information as available. Software update Forecast from vendor When a participant submits 9 Price Incremental Quantity Pairs for Incremental and TBC & As a workaround participants are Decremental costs curves the sequences Decremental requested to not submit 9 PQ pairs 110321 do not see the prices as monotonically In Analysis Resolution: Price when submitting Commercial Offer increasing and then defaults them to zero. Software update quantity Data. This is a defect and has knock on impacts from vendor pairs on the scheduling of LTS, RTC and RTD 17
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 data In the TBC for the first ISP of a trade date from this process of Reports REPT_078: Aggregated Contract Quantities report until the issue is remedied. These submissio 5329 missing 1st ISP for Generation Resolution: data can be sourced elsewhere. They are n to the of Trade Day REPT_079: Aggregated Contract Quantities Software update available in the ETS Market Results RA's for for Demand from vendor published on the SEMOpx website, D+1. approval REPT_080: Aggregated Contract Quantities for Wind 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. 18
Known Issues Update – Balancing Market Resolution ID Name Description Impact to Market Participants Status Date The Initial Interconnector Flows and Residual Capacity Report (REPT_022) is produced EMPTY on the MPI, and 5845 REPT_022 Report unavailable to Market Participants No Confirmed subsequently to the SEMO website. This is Unplanned Showing Empty and General Public. Delivery date an error with the vendor design that causes the report to fail when no SO Trades are available in the system. The Dispatch Quantity report (REPT_068) MPs will observe incorrect values for erroneously calculates the “Dispatch pumping mode MWh values in this report 5812 REPT_068 UOM No Confirmed Quantity” field as MW for P/S units when until remedied. Settlement is unaffected Unplanned error Delivery date in pumping mode. These values should be as those calculations use metered calculated and reported as MWh. generation. For P/S Units, intermittent representation of duplicate values (MWOF) instructions appearing. For P/S units, the Market Participant will 102081 REPT_006: Daily No Confirmed This is due to internal processing of records need to ignore the duplicate entry until Unplanned DI Report Delivery date and does not affect the Instruction Profiling resolved. process, only the outbound report. This issue affects 39 reports. This is a 5195 Report display HTML report is displayed in UTC rather No Confirmed display issue only, as the values and Unplanned than always in local time. Delivery date corresponding time interval are correct. 19
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 20
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 21
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) 22
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. 23
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 24
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 25
Known Issues Update – Settlement Resolution ID Name Description Impact to Market Participants Status Date Multiple instances of QAO and QAB being inconsistent Multiple instances of QAO and QAB Planned i.e. large positive being inconsistent i.e. large positive Multiple instances of QAO and QAB being Release C, 5936 Resolution QAO and a large QAO and a large negative QAB when inconsistent May 2019 . Date negative QAB FPN and QD are similar. when FPN and QD are similar. BOAs were intermittently calculated FPN yet large variances in QAO and QAB. incorrectly when QD was equal to the IPQBOA values were not correct. Planned Incorrect IPQBOA Release C, 5893 FPN with a BOA generated. Also where Temporary workaround is in place. Resolution values May 2019 . QD is similar to FPN yet large variances Permanent solution to be provided by Date in QAO and QAB. ABB 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 Planned Release C, 5888 are only being kept 2 months in the MPI. They are then applied on the 21/01/2019 ensures that Resolution May 2019 . for 2 months archived and not available through the no further report will be removed from Date front end the MPI. Vendor is working on solution to republish all Settlement reports/documents/Statement to MPI 26
Known Issues Update – Settlement Resolution ID Name Description Impact to Market Participants Status Date Settlement reports/documents/Statements unavailable to participants after 2 months All Settlement reports produced in through the MPI. Temporary workaround Settlement reports MMS currently only have a retention Planned applied on the 21/01/2019 ensures that no Release C, 5886 are only being kept of 2 months in the MPI. They are then Resolution further report will be removed from the May 2019 . for 2 months archived and not available through Date MPI. Vendor is working on solution to the front end republish all Settlement reports/documents/Statement to MPI Period of Market Operation Trading Period Starting points in CSB not MPOP FPN Not applying the correct starting points for Planned aligned with the MM, including Release C, 5940 Misalignment with FPNs in relation to the calculation of fixed Resolution incorrect application of minute May 2019 . MMS costs for the Period of Market Operation Date resolution. Should be 30 min resolution. Simple/Complex COD: Flags and Tags are not being applied in the half hours Prices are being applied only to the period they should. Prices are being applied Planned Simple/Complex where the DI is effective then persisting for Release C, 5943 only to the period where the DI is Resolution COD all associate BOAs. May 2019 . effective then persisting for all Date associate BOAs. 27
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 Planned & F18.5 of the TSC. exclusion clause within the TSC including Difference & NP Resolution Release C, 5950 Calculation of QDIFFTRACK for DSUs F2.1.2. Charges for DSUs Date May 2019 . 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 BOA and Start up / System changes between Simple and Planned no load cost not Release C, 5909 Complex COD use when the Order of This affects CFC calculation Resolution being calculated May 2019 . the first BOA does not equal 1. Date when first BOA = 0 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 Planned 5972 Incorrect CNLR to Release C, summation. Incorrect CNLR to Generators Resolution Generators May 2019 . b) The Fixed Cost calculation of CNLR Date will for (most) periods of MPOP not do correct check on Dispatch Quantity for the last interval. Incorrect CFC and Planned Caused by incorrect QBOA calculation in CFC and Premium data incorrect. Release C, 5799 Premium Resolution particular circumstances Improvement in QBOA Calculation May 2019 . Payments Date 28
Known Issues Update – Settlement Resolution ID Name Description Impact to Market Participants Status Date In Day 1 plus FMOC FX rate scope, drop TBC applied not aligned FMOC is applying the trading day FMOC is applying the trading day 5808 with the Trade and exchange rate of the last day of the exchange rate of the last day of the In Analysis Resolution: settlement code month. month. Software 1.3.9. update from vendor In Day 1 plus CCC, CCP and CSOCDIFFP settlement for scope, drop TBC NI units not applying the Annual 5772 Capacity CCC, CCP and CSOCDIFFP settlement for Capacity Exchange rate as per G.1.3.5 & In Analysis Resolution: Charges/Payments NI units not correct. G.1.3.6. Balancing market FX rate Software incorrect being applied. update from vendor In Day 1 plus The CNL & CSU are being displayed in NI units CNL & CSU scope, drop TBC REPT_044 for NI units in EUR. in REPT_44 being Issue with shadow settling CNL & CSU as 5988 displayed in In Analysis Resolution: These costs are to be reported in GBP as report determinants are in EUR. EUR. Report Software per the report registered currency. should be in GBP update from vendor In Day 1 plus scope, drop TBC FPN Curve not 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 Resolution: State to CFC inputs incorrect Start-Up status. being included within the CFC calculation Software correctly update from vendor 29
Known Issues Update – Settlement Resolution ID Name Description Impact to Market Participants Status Date In Day 1 plus scope, drop TBC MA is currently providing Startup Flag Startup flag for CSUR and Warmth State for Synchronize 5910 This affects CFC calculation In Analysis Resolution: with Warmth State Dispatch Instructions that relates to CSU Software calculation update from vendor TBC Aggregated Metered Demand not being Metered Volumes by published on RET_066. Currently only Jurisdiction Unable to view the Aggregated Resolution: 5923 reporting Aggregated Metered In Analysis (REPT_066) - Zero Metered Demand within the Report Software Generation Metered Demand update from vendor The Stop Loss Limits (CSLLA/CSLLB) calculation is looping over units with TBC Reliability Options that are associated Stop Loss Limits Stop Loss limits are not being with a Trading Site. The settlement (CSLLA/CSLLB) is not calculated for IU and CAUs for the Resolution: 5922 calculation should also include units In Analysis being calculated for application of the a calculated % Software with Reliability Options that are not IU and CAU applied to the Non-performance update from associated with a Trading Site like CAU vendor and IU units. TBC Trading Periods misalignment has QD and QM not Long Day Trading periods not aligned resulted in the Long day trading Resolution: 5890 matching on long day between MAMI and CSB. In Analysis periods being incorrectly settled within Software (28/10/18) Initial Settlement. update from 30 vendor
Known Issues Update – Settlement Resolution ID Name Description Impact to Market Participants Status Date TBC Dropdown filters not 11/03/2019 operational day is not SEMO Website Settlement Calendar > Resolution: available on the available and possibly additional trade 105608 Publication > “Settlement Documents” In Analysis Software SEMO website dates. We will confirm these dates is not present for users to filter. update from Settlement Calendar once available vendor 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 31
Known Issues Update – Settlement Resolution ID Name Description Impact to Market Participants Status Date No BOA volumes are generated for the TBC QBOA defect for There are no IP QBOAs created for units in question for certain trading Error in Slope GU_X at the end of the day error periods. This results in missing BALIMB Resolution: 113353 In Analysis messages resulting in message appears: Error in Slope payments and charges in the billing Software no QBOAs calculation for unit GU_X runs. To date this has only affect update from thermal generator units and DSUs. vendor TBC Report 044 missing Settlement Report not showing Accept Market Participants unable to view the Accept time for QAO Resolution: 5953 Times for QAO & QAB accept time of QBOAs used within In Analysis and QAB Software Settlement determinants update from vendor Market participants and any third-party The timestamp attribute in the Value system providers should ignore the No Confirmed 5314 REPT_043, _044 element contains +1 second, which it additional 1-second on the timestamp Unplanned Delivery date should not and consider the time to be exactly on the ISP interval. 32
Known Issues Update – Settlement Resolution ID Name Description Impact to Market Participants Status Date PUBLICATION_TIMESTAMP attribute is The difference in time is very brief and No Confirmed REPT_048 incorrectly assigned the start time of 5322 has no material effect on the report Unplanned Delivery date Collateral Report the credit assessment, rather than the quality finish time. Inconsistency between detailed and Incorrect rounding applied to detail No Confirmed summary records within the same 5339 REPT_043 records. Summary and Detail records do Unplanned Delivery date REPT_043. Research indicates this to be not sum correctly. small amount relative to document totals. CCC, CCP and CSOCDIFFP settlement for NI units not applying the Annual Capacity CCC, CCP and CSOCDIFFP settlement for No Confirmed 5722 Capacity Exchange rate as per G.1.3.5 & Unplanned Charges/Payments NI units not correct Delivery date G.1.3.6. Balancing market FX rate incorrect being applied. 33
Agenda Item Presenter Welcome Anne Fitzgerald Known Issues Update Eoin Farrell Ex-Ante Market Liam McAllister Balancing Market Brendan O’Sullivan, Martin Kerin, Sam Matthews Disputes & Repricing Update Dermot Campfield Settlements & M+4 Resettlement Sean O’Rourke, John O’Dea Capacity Market Timetable Anne Fitzgerald Query Management Claire Breslin Q&A 34
Ex-Ante Markets • Market Value % of DAM Volumes from ex-ante (25 th Feb – 27 th Mar) DAM € 176,360,511 – DAM Auction still dominant IDA1 € 10,952,645 6.21% IDA2 € 6,686,259 3.79% *Using approx. prices IDA3 € 1,645,832 0.93% IDC € 1,707,168 0.97% 35
Ex-Ante Market Flows – 6 Months 36
Ex-Ante Market Flows – 6 Months 37
Ex-Ante Market Flows – 6 Months 38
Ex-Ante Auction Price – 6 Month DAM Look Back € 365.04 2 nd Jan € -10.29 17 th Feb 39
Ex-Ante Auction Price – 6 Month DAM Look Back 40
Ex-Ante Auction Price – 6 Month DAM Look Back • Coming out of winter months… Price Volatility Declining ? 41
Ex-Ante Auction Price – 6 Month IDA’s Look Back • Prices generally higher in later auctions – though uniform to DAM 42
Ex-Ante Auction Volume – 6 Month DAM Look Back • Coming out of winter months… Volume Steady at 100 -120K 43
Ex-Ante Auction Volume – 6 Month IDA’s Look Back • MP’s using later auctions to do business, more frequently... IDA1 - Outliers 44
Ex-Ante Auction Volume – 6 Month IDA’s Look Back • MP’s using later auctions to do business, more frequently... IDA1 - Outliers 45
Ex-Ante Auction Volume – 6 Month IDA’s Look Back • MP’s using later auctions to do business, more frequently… IDA2 - Outliers 46
Ex-Ante Auction Volume – 6 Month IDA’s Look Back • MP’s using later auctions to do business, more frequently… IDA2 - Outliers 47
Ex-Ante Auction Volume – 6 Month IDA’s Look Back • MP’s using later auctions to do business, more frequently… IDA2 - Outliers 48
Ex-Ante Auction Volume – 6 Month IDA’s Look Back • MP’s using later auctions to do business, more frequently… IDA3 - Outliers 49
Ex-Ante Auction Volume – 6 Month IDA’s Look Back • MP’s using later auctions to do business, more frequently… IDA3 - Outliers 50
Ex-Ante Auction Volume – 6 Month IDA’s Look Back • MP’s using later auctions to do business, more frequently… IDA3 - Outliers 51
Ex-Ante IDC Market Price – 6 Month Look Back € 600.00 24 th Jan € -63.20 23 rd Feb 52
Ex-Ante IDC Market Volume – 6 th Month Look Back Large Unit Trip MP Balancing Units 53
Ex-Ante IDC Market Volume – 6 th Month Look Back 54
Ex-Ante IDC Market Volume – 6 th Month Look Back 55
Ex-Ante IDC Market Volume – 6 th Month Look Back 56
Ex-Ante IDC Market Volume – 6 th Month Look Back 57
Ex-Ante IDC Recalls & Cancels – 6 th Month Look Back IDC Orders Recalled, Cancelled 7 6 5 4 3 2 1 0 2018- 2018- 2018- 2018- 2018- 2018- 2018- 2018- 2018- 2018- 2018- 2019- 2019- 2019- 2019- 2019- 2019- 2019- 2019- 2019- 2019- 10-02 10-04 10-15 10-22 11-01 11-20 11-27 12-04 12-12 12-15 12-17 01-02 01-08 01-09 01-15 01-19 01-23 01-29 02-07 03-11 03-15 Recalled 1 2 1 3 1 1 0 4 1 3 3 6 1 1 0 1 2 1 1 4 1 Cancelled 1 1 2 58
Ex-Ante Market Analysis • In Summary Successful 6 months of SEMOpx in the books Healthy and consistent volumes observed in DAM Participants increasingly making use of later auctions to do business Liquidity is available across our markets Processes are working! 59
Agenda Item Presenter Welcome Anne Fitzgerald Known Issues Update Eoin Farrell Ex-Ante Market Liam McAllister Balancing Market Brendan O’Sullivan, Martin Kerin, Sam Matthews Disputes & Repricing Update Dermot Campfield Settlements & M+4 Resettlement Sean O’Rourke, John O’Dea Capacity Market Timetable Anne Fitzgerald Query Management Claire Breslin Q&A 60
Imbalance Pricing • Important defect fixes: • Included a fix for the issue where the COD was switching from Simple to Complex and back, was one of the defects causing a large number of disputes; • No 5-minute price drops since fix for performance improvements on – pricing becoming more stable. • The Imbalance Settlement Price is following the NIV and it’s relationship to the Ex - ante Market prices is also relative to the NIV: • Generally Imbalance Price is above the ex-ante prices for larger positive NIV, below the ex-ante prices for larger negative NIV: • Factors which impact the price: level of imbalance, time of day (and therefore demand / margin / units available), level of constraints on the system, curtailment of priority dispatch plant, these may lead to unintuitive results where price does not directly follow NIV. • Volatility seems to have reduced slightly: • Fewer missing prices, e.g. the half hour price won’t be jumping from levels typical of large positive or negative NIVs to the level of the Backup Price; • Less negative prices mean that the average is becoming larger, and the negative prices tend to be larger jumps, meaning that the volatility reduces as the number of negative prices reduce; • Average NIV has reduced, as have the max and min NIV 61 and standard deviation on the NIV.
Imbalance Pricing Examples of defect where prices jump from Simple to Complex. 62
Imbalance Pricing Day of the fix being delivered, a few examples of the defect earlier in the day, then the blank space is when the outage 63 to provide the fix was taken.
Imbalance Pricing No longer any examples of COD switching from Simple to Complex, all changes in colour seem to match change in 64 unit COD or unit PN/Dispatch, graph makes more sense.
Imbalance Pricing No longer any examples of COD switching from Simple to Complex, all changes in colour seem to match change in 65 unit COD or unit PN/Dispatch, graph makes more sense.
Imbalance Pricing No longer any examples of COD switching from Simple to Complex, all changes in colour seem to match change in 66 unit COD or unit PN/Dispatch, graph makes more sense.
Imbalance Pricing No longer any examples of COD switching from Simple to Complex, all changes in colour seem to match change in 67 unit COD or unit PN/Dispatch, graph makes more sense.
Imbalance Pricing Some unintuitive results, such as PIMB going up above ex-ante prices when NIV is negative. This seems to occur normally when the system is highly constrained, PMEA set in opposite direction to NIV. This could happen in particular during morning load rise and evening peak: not many units available unflagged as lots of units are ramping, therefore even if NIV is low or negative, it is often a high priced unit which is available for energy balancing. 68
Imbalance Pricing Otherwise, examples are generally intuitive: when have high positive imbalance then PIMB has a higher price than ex-ante, low positive or large negative imbalance then PIMB has a lower price than ex-ante. Very intuitive example - red and blue almost directly follow NIV in terms of being less than or greater than green. 69
Imbalance Pricing Generally intuitive example: imbalance is generally low positive or negative at start of day, PIMB is lower than ex-ante, jumps potentially unintuitively to much lower level because of curtailment of priority dispatch, at midday despite low imbalance the price goes above ex- ante because the system is highly constrained at this time, in the evening the imbalance price follows the large imbalance volume above the ex-ante price, in later evening despite volumes rising the price falls 70 because it is past the peak so cheaper units are available.
Imbalance Pricing Again generally intuitive example: Imbalance price follows imbalance, when large and positive price goes above, when large and negative price goes below. Doesn’t really change for change in direction of NIV between midnight and 2am, this is because there is low demand and lots of cheap generation available but the system is possibly quite constrained so the same units in positive and negative imbalance rules are being used. Again exception around midday and morning load rise. 71 Backup price used during planned outage
Imbalance Pricing Almost entirely intuitive example. 72
Imbalance Pricing Generally intuitive example, with again exceptions around morning load rise and evening peak where imbalance price goes above ex-ante for negative imbalance volume, due to constrained system. 73
Imbalance Pricing Almost entirely intuitive with imbalance price following imbalance volume all weekend. 74
Imbalance Pricing Number of Times per Week Backup Half Hour PIMB Used 80 70 60 No. of Imbalance Settlement Periods 50 40 30 20 10 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 Weeks Since Go-live 75
Imbalance Pricing Number of Times per Week Half Hour PIMB was Negative 60 50 No. of Imbalance Settlement Periods 40 30 20 10 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 Weeks Since Go-live 76
Imbalance Pricing Daily Average Half Hour Average NIV 150 100 50 MWh 0 1 5 9 13 17 21 25 29 33 37 41 45 49 53 57 61 65 69 73 77 81 85 89 93 97 101 105 109 113 117 121 125 129 133 137 141 145 149 153 157 161 165 169 173 177 181 185 -50 -100 -150 Days Since Go-live Average of NIV30 (MWh) 77
Imbalance Pricing Weekly Average Half Hour PIMB and Standard Deviation ( € /MWh) 400 300 200 € /MWh 100 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 -100 -200 Weeks Since Go-live Average of Original 30min Price ( € /MWh) 78
€ /MWh -500 -400 -300 -200 -100 100 200 300 400 500 600 0 Imbalance Pricing 00:00:00 00:30:00 01:00:00 01:30:00 Daily Average 5 Minute PIMB Price Profile - 01/10/2018 - 02/04/2019 02:00:00 02:30:00 03:00:00 03:30:00 04:00:00 04:30:00 05:00:00 05:30:00 06:00:00 06:30:00 07:00:00 07:30:00 08:00:00 08:30:00 Average of Original 5min Price ( € /MWh) 09:00:00 09:30:00 Imbalance Pricing Periods of Day 10:00:00 10:30:00 11:00:00 11:30:00 12:00:00 12:30:00 13:00:00 13:30:00 14:00:00 14:30:00 15:00:00 15:30:00 16:00:00 16:30:00 17:00:00 17:30:00 18:00:00 18:30:00 19:00:00 19:30:00 20:00:00 20:30:00 21:00:00 21:30:00 22:00:00 79 22:30:00 23:00:00 23:30:00
€ /MWh -300 -200 -100 100 200 300 0 Imbalance Pricing 00:00:00 00:30:00 01:00:00 01:30:00 Daily Average 5 Minute PIMB Price Profile - 01/10/2018 - 02/04/2019 02:00:00 02:30:00 03:00:00 03:30:00 04:00:00 04:30:00 05:00:00 05:30:00 06:00:00 06:30:00 07:00:00 07:30:00 08:00:00 08:30:00 Average of Original 5min Price ( € /MWh) 09:00:00 09:30:00 Imbalance Pricing Periods of Day 10:00:00 10:30:00 11:00:00 11:30:00 12:00:00 12:30:00 13:00:00 13:30:00 14:00:00 14:30:00 15:00:00 15:30:00 16:00:00 16:30:00 17:00:00 17:30:00 18:00:00 18:30:00 19:00:00 19:30:00 20:00:00 20:30:00 21:00:00 21:30:00 22:00:00 80 22:30:00 23:00:00 23:30:00
€ /MWh -300 -200 -100 100 200 300 0 Imbalance Pricing 00:00:00 00:30:00 01:00:00 01:30:00 Daily Average 5 Minute PIMB Price Profile - 01/02/2019 - 28/02/2019 02:00:00 02:30:00 03:00:00 03:30:00 04:00:00 04:30:00 05:00:00 05:30:00 06:00:00 06:30:00 07:00:00 07:30:00 08:00:00 08:30:00 Average of Original 5min Price ( € /MWh) 09:00:00 09:30:00 Imbalance Pricing Periods of Day 10:00:00 10:30:00 11:00:00 11:30:00 12:00:00 12:30:00 13:00:00 13:30:00 14:00:00 14:30:00 15:00:00 15:30:00 16:00:00 16:30:00 17:00:00 17:30:00 18:00:00 18:30:00 19:00:00 19:30:00 20:00:00 20:30:00 21:00:00 21:30:00 22:00:00 81 22:30:00 23:00:00 23:30:00
€ /MWh -300 -200 -100 100 200 300 0 Imbalance Pricing 00:00:00 00:30:00 01:00:00 01:30:00 Daily Average 5 Minute PIMB Price Profile - 01/03/2019 - 31/03/2019 02:00:00 02:30:00 03:00:00 03:30:00 04:00:00 04:30:00 05:00:00 05:30:00 06:00:00 06:30:00 07:00:00 07:30:00 08:00:00 08:30:00 Average of Original 5min Price ( € /MWh) 09:00:00 09:30:00 10:00:00 10:30:00 Days Since Go-live 11:00:00 11:30:00 12:00:00 12:30:00 13:00:00 13:30:00 14:00:00 14:30:00 15:00:00 15:30:00 16:00:00 16:30:00 17:00:00 17:30:00 18:00:00 18:30:00 19:00:00 19:30:00 20:00:00 20:30:00 21:00:00 21:30:00 22:00:00 82 22:30:00 23:00:00 23:30:00
€ /MWh -200 -100 100 200 300 400 0 Imbalance Pricing 00:00:00 00:30:00 01:00:00 01:30:00 Daily Average Half Hour PIMB Price Profile - 01/10/2018 - 02/04/2019 02:00:00 02:30:00 03:00:00 03:30:00 04:00:00 04:30:00 05:00:00 05:30:00 06:00:00 06:30:00 07:00:00 07:30:00 08:00:00 Average of Original 30min Price ( € /MWh) 08:30:00 09:00:00 Imbalance Settlement Periods of Day 09:30:00 10:00:00 10:30:00 11:00:00 11:30:00 12:00:00 12:30:00 13:00:00 13:30:00 14:00:00 14:30:00 15:00:00 15:30:00 16:00:00 16:30:00 17:00:00 17:30:00 18:00:00 18:30:00 19:00:00 19:30:00 20:00:00 20:30:00 21:00:00 21:30:00 22:00:00 83 22:30:00 23:00:00 23:30:00
€ /MWh -200 -100 100 200 300 400 0 Imbalance Pricing 00:00:00 00:30:00 01:00:00 01:30:00 Daily Average Half Hour PIMB Price Profile - 01/02/2019 - 28/02/2019 02:00:00 02:30:00 03:00:00 03:30:00 04:00:00 04:30:00 05:00:00 05:30:00 06:00:00 06:30:00 07:00:00 07:30:00 08:00:00 Average of Original 30min Price ( € /MWh) 08:30:00 09:00:00 Imbalance Settlement Periods of Day 09:30:00 10:00:00 10:30:00 11:00:00 11:30:00 12:00:00 12:30:00 13:00:00 13:30:00 14:00:00 14:30:00 15:00:00 15:30:00 16:00:00 16:30:00 17:00:00 17:30:00 18:00:00 18:30:00 19:00:00 19:30:00 20:00:00 20:30:00 21:00:00 21:30:00 22:00:00 84 22:30:00 23:00:00 23:30:00
€ /MWh -200 -100 100 200 300 400 0 Imbalance Pricing 00:00:00 00:30:00 01:00:00 01:30:00 Daily Average Half Hour PIMB Price Profile - 01/03/2019 - 31/03/2019 02:00:00 02:30:00 03:00:00 03:30:00 04:00:00 04:30:00 05:00:00 05:30:00 06:00:00 06:30:00 07:00:00 07:30:00 08:00:00 Average of Original 30min Price ( € /MWh) 08:30:00 09:00:00 Imbalance Settlement Periods of Day 09:30:00 10:00:00 10:30:00 11:00:00 11:30:00 12:00:00 12:30:00 13:00:00 13:30:00 14:00:00 14:30:00 15:00:00 15:30:00 16:00:00 16:30:00 17:00:00 17:30:00 18:00:00 18:30:00 19:00:00 19:30:00 20:00:00 20:30:00 21:00:00 21:30:00 22:00:00 85 22:30:00 23:00:00 23:30:00
Imbalance Pricing Half Hour PIMB versus Average NIV - 01/10/2018 - 02/04/2019 4000 3500 3000 2500 PIMB € /MWh 2000 1500 1000 500 0 -150 -100 -50 0 50 100 150 -500 NIV MWh
Imbalance Pricing Half Hour PIMB versus Average NIV - 01/10/2018 - 02/04/2019 500 400 300 200 100 PIMB € /MWh 0 -150 -100 -50 0 50 100 150 -100 -200 -300 -400 -500 NIV MWh
Imbalance Pricing Half Hour PIMB versus Average NIV - 01/02/2019 - 28/02/2019 500 400 300 200 100 PIMB € /MWh 0 -150 -100 -50 0 50 100 150 -100 -200 -300 -400 -500 NIV MWh
Imbalance Pricing Half Hour PIMB versus Average NIV - 01/03/2019 - 31/03/2019 500 400 300 200 100 PIMB € /MWh 0 -150 -100 -50 0 50 100 150 -100 -200 -300 -400 -500 NIV MWh
Balancing Market Are there points of additional clarity required in the report on Jan 24 th ? “Clarification on the initial conditions of the RTD” Not clear from notes taken and communications what clarification is required. Can participants specify what they need in this space and we will update the report accordingly. Is there value in a similar report on Oct 9 th ? “ ... a similar report for the 3rd and 9th of October would be useful for participants …” Team have begun work on a report on October 9th. Timeline of drafting is likely to see publication late April / early May Report on October 3 rd was not on our plan. To be further considered. 90
Balancing Market What additional information do participants feel they need to assist in their understanding and analysis of flagging & tagging and imbalance pricing? “Provision of a loss of load probability report for ROI, NI and SEM would assist participants in identifying potential upcoming issues without needing a warning from the TSOs .” “The correction of the known issues with the NIV report and the creation of extra separate NIV reports for each jurisdiction (ROI & NI). Three in total; SEM, ROI and NI. These reports would easily help participants foresee similar events arising again .” Changes to reports will be a Day 2 (or later) implementation. Feedback received being provided to the Day 2 team for consideration. Meantime, SEMO to review what data available and to potentially provide information note to advise how this information can be collected from existing reports. 91
Balancing Market Further design questions arising from the event of Jan 24 th ? MO, TSOs and RAs have met to consider implications of current design Reviewing many aspects of imbalance pricing calculations (e.g., impact of locational constraints on pricing, application of PMEA, application of PAR when PMEA applied, etc.) Any further discussion of changes will be through the Modifications Panel Next steps to be expanded on at next meeting on April 11 th 92
Balancing Market “From a previous MOUG, I asked if it would be possible for SEMO to do a review of the number of actions settled on simple and complex since the start of ISEM” SEMO agreed to look at this from the January MOUG Task has proved to be more difficult than expected Whether an action is settled on simple or complex bids is not a reportable requirement As such, this data is not built in to our systems, nor is it retained by them 93
Balancing Market Currency data converted to € SEM Systems under Part B Scheduling for common use in scheduling Applications tools (LTS/RTC/RTD) Scheduling Outputs only – no pricing data Native currency Participant submits COD in stored in native currency market COD retrieved to IP database software Balancing Instruction Profiling Market Market (QBOA) / Real Time Information Interface Imbalance Pricing Database Outputs Settlement published to Systems Settlement System without IP outputs = currency QBOA and PBOA distinction
Balancing Market “From a previous MOUG, I asked if it would be possible for SEMO to do a review of the number of actions settled on simple and complex since the start of ISEM” The IP QBOA software is the application that applies the rules of which COD to apply Outputs are simply the QBOA and the PBOA Settlement systems consume the outputs of the IP QBOA process assuming previous steps have been completed 95
Balancing Market To determine actions settled on complex / simple COD – Could see the PBOA output and determine which COD type by reviewing COD submissions Complex option – needs to consider all COD submissions to determine which was “live” at the Bid Offer Acceptance Time (BOAT) Other option to consider the inputs to the IP QBOA Using the PUB_5MinImbalPrcSuppInfo report, identify which units are SO Flagged or NIV tagged Once a unit is flagged in any five minute period, settled on complex for the entire half hour 96
Balancing Market Results not validated but wanted to provide initial finding High proportion of actions settled on complex COD versus simple 97
Balancing Market Expressed as quantity 173K as simple Over 4m as complex 98
Balancing Market 99
Balancing Market By aggregate volume… 100
Recommend
More recommend
