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 11 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 12
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. 13
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 14
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 15 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 New users will not be able to access Access of MPI A user who is registered in the Balancing scope, Target to historical I-SEM data before their information Market receives a market effective date. They include in Rel. D 117257/ registration date in the MPI. Public before are not able to access any published In Analysis 6031 reports are published to the SEMO registration information in the MPI before this date Resolution: website. Users will be unable to access Date market effective date. Software update reports from before registration. from vendor In Day 1 plus scope, Target to May cause issues for Market include in Rel. E REPT_082 PUB_AvgOutturnAvail is publishing 5977 REPT_082 Participants that are validating against In Analysis data for de-registered units PUB_DailyRegisteredUnits Resolution: Software update from vendor Application of Imbalance Pricing validation is resulting in In Day 1 plus De Minimis QBOA volumes greater than DMAT to not be scope, target to Acceptance included in Imbalance Pricing calculations. Incorrect QBOA values, resulting in include in Rel E 5991 Threshold Where a Unit has an Accepted Offer and In Analysis impact to Imbalance Price Resolution: (DMAT) in Accepted Bid, one of which is below DMAT, Software update Imbalance both volumes are being omitted from the from vendor Pricing calculation. VTOD changes will take effect in the In Day 1 plus market systems on the date of VTOD Approved changes to VTOD are taking effect scope, target to approval. Changes on the operational day that the change is include in Rel E 5942 In Analysis Taking Effect approved, rather than the next Trading Day for Resolution: Note – SEMO are implementing a on Approval which Gate Closure 1, has not yet occurred. Software update workaround whilst this defect remains from vendor 16 open.
Known Issues Update – Balancing Market Resolution ID Name Description Impact to Market Participants Status Date In Day 1 plus scope, Release The report may display incorrect Total TBC REPT_008: I Total Unit Availability field within the Unit Availability values. The report 5952 mbalance Imbalance Price Report is being In Analysis presents inaccurate information. Resolution: Price Report calculated incorrectly. Software update from vendor In Day 1 plus scope, Release This issue affects 39 reports. This is a TBC 5195 Report display HTML report is displayed in UTC rather display issue only, as the values and In Analysis Resolution: than always in local time. corresponding time interval are correct. Software update from vendor 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. 17
Known Issues Update – Balancing Market Resolution ID Name Description Impact to Market Participants Status Date This impact report availability to participants as well as use of dynamic TBC SEMO and reporting to provide an accurate The SEMO and SEMOpx website currently has issues SEMO_WEB SEMOpx representation of the static reports. All Resolution: with the dynamic reporting, report retention and In Analysis .001 ongoing reports are available in the static section Software update ongoing manual workaround to publish reports issues and manual workaround are carried out from vendor on a daily basis to ensure reports are not missed MPS are unable to download historical TBC SEMO and reports from the SEMO and SEMOpx SEMO_WEB SEMOpx The SEMO and SEMOpx websites currently does not website. A CR has been raised with the In Analysis Resolution: _002 website File show historical reports. website vendor to make these files Software update retention available from vendor 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. 18 REPT_080: Aggregated Contract Quantities for Wind
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 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 19
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 20
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 REPT_088 Net The report is published every hour instead Information is available less frequently. 5317 Imbalance of 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 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. 21
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 22
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 23
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) 24
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. 25
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 26
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 27
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. 28
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 29
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 30
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 31
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 32
Known Issues Update – Settlement Resolution ID Name Description Impact to Market Participants Status 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 Simple/Complex COD: Flags and Tags scope, target to are not being applied in the half hours include in Rel. E 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 In Analysis COD only to the period where the DI is Resolution: all associate BOAs. effective then persisting for all Software associate BOAs. update from vendor Multiple instances In Day 1 plus of QAO and QAB scope, drop TBC 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 5936 In Analysis Resolution: QAO and a large QAO and a large negative QAB when inconsistent Software negative QAB FPN and QD are similar. update from when FPN and QD vendor are similar. 33
Known Issues Update – Settlement Resolution ID Name Description Impact to Market Participants Status Date 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 update from vendor TBC Inconsistency between detailed and Incorrect rounding applied to detail summary records within the same Resolution: 5339 REPT_043 records. Summary and Detail records In Analysis REPT_043. Research indicates this to be Software do not sum correctly. small amount relative to document totals. update from vendor TBC FMOC FX rate applied not aligned FMOC is applying the trading day FMOC is applying the trading day exchange Resolution: 5808 with the Trade and exchange rate of the last day of the In Analysis rate of the last day of the month. Software settlement code month. update from 1.3.9. vendor 34
Known Issues Update – Settlement Resolution ID Name Description Impact to Market Participants Status Date 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 35
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 36 update from vendor
Known Issues Update – Settlement Resolution ID Name Description Impact to Market Participants Status Date CFC calculation will sum the CIMB, Fixed Cost Calculation CPREMIUM, CDISCOUNT, CABBPO, TBC sums values from all Incorrect CFC amounts in settlement CAOOPO and CCURL amounts from both Ad AdHoc runs of a Billing documents where there is an instance of 6035 Hoc Run #1 and Ad Hoc Run #2. In Analysis Resolution: Week instead of using an ad-hoc completed over a previous ad- It should only make use of the values from Software update the latest AdHoc run hoc for the same billing period. the latest Ad Hoc Run.. from vendor for each day if a GU does not have an RO in which to QD determinant calculate difference charges QD not TBC QD determinant missing from REPT_44 in missing from REPT_44 present on REPT_044 as it is calling the indicative & initial reports for a range of 6044 in indicative & initial value from the difference charges In Analysis Resolution: units and dates based on Reliability Options reports for a range of calculations. Result is QD is never Software update not being present for the units. units and dates published in REPT_044 for affected units from vendor (particularly wind units) Settlement Documents containing re- settlement Billing periods, Resettlement - TBC the previous_gross_amount figure is Settlement Document Unable to view the previous sale and correctly populated as the figure from the 6042 Previous Purchases and purchases proportion within settlement In Analysis Resolution: original settlement however none of the Previous Sales are not documents containing re-settlement. Software update ***_prev figures are being populated. populated correctly from vendor Change required for the provisions for loss- TBC CR092 – Loss Factor adjustment when an Interconnector is Loss factors (export) incorrect on Application for exporting (see below). This Change CR092 interconnectors in settlements leading to In Analysis Resolution: Interconnectors in Request introduces the omitted provisions, underpayment to this point in the market Software update Settlement as they are resulting in incorrect settlement from vendor outcomes. 37
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 TBC CCC, CCP and CSOCDIFFP settlement for NI units not applying the Annual 5772 Capacity CCC, CCP and CSOCDIFFP settlement Resolution: Capacity Exchange rate as per G.1.3.5 & In Analysis Charges/Payments for NI units not correct Software G.1.3.6. Balancing market FX rate update from incorrect being applied. 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. 38
Agenda Item Presenter Welcome Anne Fitzgerald General System Failure Anne Fitzgerald Known Issues Update Eoin Farrell Ex-Ante Market Liam McAllister, Michael Atcheson Balancing Market Rory Cafferky Settlements Sean O’Rourke, John O’Dea, John Tracey Disputes & Repricing Update Julie McGee Brexit Update Michael Kelly Market Participant Roadmap Mark Needham Query Management Anne Fitzgerald Q&A 39
Ex-Ante Markets • Market Value % of DAM Volumes from ex-ante (9 th May – 9 th June) DAM € 154,829,047 – DAM is dominant IDA1 € 10,159,769 6.56% IDA2 € 4,226,771 2.73% *Using approx. prices IDA3 € 1,461,683 0.94% IDC € 1,191,113 0.77% 40
Ex-Ante Auction Price Look Back 41
Ex-Ante Auction Price Look Back • Outliers – What was happening in the market on these days? 42
• Outliers – What were the fundamentals? 43
• Outliers – What were the fundamentals? 44
• Outliers – What were the fundamentals? 45
• Outliers – What were the fundamentals? 46
• Outliers – What were the fundamentals? 47
• Outliers – What were the fundamentals? 48
• Outliers – What were the fundamentals? 49
Ex-Ante IDC Price Look Back • Outliers – What were the fundamentals? 50
Ex-Ante IDC Price Look Back • Outliers – What were the fundamentals? 51
Ex-Ante IDC Price Look Back • Outliers – What were the fundamentals? 52
European Market De-coupling Incident June 7 th 53
European Market De-coupling Incident June 7 th 54
Interconnector Flows Re-visited DAM Flows SEM dearer - importing from BETTA 1200 1000 800 600 400 200 0 ( € 100.00) ( € 50.00) € 0.00 € 50.00 € 100.00 € 150.00 € 200.00 € 250.00 € 300.00 -200 -400 -600 -800 SEM cheaper - exporting to BETTA -1000 55
Interconnector Flows Re-visited Actual Flows SEM dearer - importing from BETTA 1200 1000 800 600 400 200 0 ( € 100.00) ( € 50.00) € 0.00 € 50.00 € 100.00 € 150.00 € 200.00 € 250.00 € 300.00 -200 -400 -600 -800 SEM cheaper - exporting to BETTA -1000 56
Interconnector Flows Re-visited DAM Flows overlayed Actual Flows SEM dearer - importing from BETTA 1200 1000 800 600 400 200 0 ( € 100.00) ( € 50.00) € 0.00 € 50.00 € 100.00 € 150.00 € 200.00 € 250.00 € 300.00 -200 -400 -600 -800 SEM cheaper - exporting to BETTA -1000 57
Ex-Ante Market Analysis • In Summary SEMOpx markets are able to successfully mitigate issues seen in European Market De-Coupling events, by using our fall back processes SEMOpx markets are consistently performing Processes are working! 58
ETS Release Schedule ETS Version Date Content Client type Impact Functionality improvements for API services. Safety settings for No impact on output V3.3.1 18/06/2019 order submission. MO and Trader client files Improvement of member exclusion process. . Format of the market results file and the bid Introduction of unique file will change. V3.3.2 *September 2019 MO and Trader client trade and trader ID Impact on Market Participants. Introduction of block bid submission graph in the trader GUI Impact analysis will be V3.4 *End of 2019 MO and Trader client in the course of 2019 Trading Session Automation * Date to be Confirmed 59
M7 Release Schedule M7 Version Date Content Client type Impact No impact on output files Passwords will expire every 90 days Passwords must be 12 characters Members can reset SEMOpx members should them any time before be advised, that the only expiry via the impact for SEMOpx V6.7 *Early Q3 2019 MO and Trader client ComTrader login screen members is a password to reset the 90 day policy change countdown. Email will be sent 10 days before expiration to remind each user. If a password expires, an email with a reset link will be sent. * Date to be Confirmed 60
ETS API Conformance Testing Update • Simulation environments 1&2 made available to perform testing in advance of ETS 3.3.1 • Additional test day of 17/06/19 was added • Successful passes for all members – Some will be *contacted to advise of some enhancements that could be made to API configurations • All API connections tested will work with new version of ETS 3.3.1 * Only contacted in event of a API recommendations from EPEX 61
62
Partial De-coupling Event 07/06/2019 Technical issue in EPEX SPOT ETS system resulting in Order Book submission failure (SEMOpx Order Books not impacted) This was a local issue with EPEX Markets Impacted multiple market areas due to Order Book issues that caused server locks several times • France-Belgium Order Book • France-Germany Issue • 10:39 IST • Germany-Austria Identified • Germany-Denmark • Germany-Netherlands • Great Britain-Netherlands • Great Britain-Belgium Partial De- • Great Britain -France coupling • 11:49* IST • Great Britain -Ireland/Northern Ireland Declared • Great Britain 1- Great Britain 2 • Italy-France • Italy-Austria • Netherlands-Belgium Local DAM • Norway-Netherlands Auction for • 12:36 IST • Slovenia-Austria SEM • Spain-France • Sweden-Germany * 9 Minute delay to agreed procedure due to attempts to 63 remain coupled
De-coupling Summary of Events • Since its launch in February 2014, more than 5 years ago, the Day-Ahead Multi Regional Coupling (MRC) has been operating successfully. • On the 7th June an issue occurred which prevented the EPEX CWE and EPEX GB order books from being sent to the common coupling system. • The incident was caused by an internal IT issue at EPEX and was not caused by the common market coupling algorithm. • The issue could not be fixed in time and at 11:50 IST the market was informed about the partial decoupling of EPEX CWE, EPEX GB and consequently, SEMOpx • This triggered the execution of the agreed fallback procedures. • Common coupling system and procedures worked as expected, ensuring the coupling of the remaining part of MRC. https://www.semopx.com/documents/general-publications/JSC_Communication-note-incident- 07.06.2019_final.pdf System patch deployed on 07/06/2019 @ 18:30 IST to resolve issue 64
Fallback Processes for SEMOpx • All Fallback processes worked as designed • Local DAM completed within agreed timeframes • All communications as sent at agreed times to members • Capacity for DAM transferred to IDA1 65
Agenda Item Presenter Welcome Anne Fitzgerald General System Failure Anne Fitzgerald Known Issues Update Eoin Farrell Ex-Ante Market Liam McAllister, Michael Atcheson Balancing Market Rory Cafferky Settlements Sean O’Rourke, John O’Dea, John Tracey Disputes & Repricing Update Julie McGee Brexit Update Michael Kelly Market Participant Roadmap Mark Needham Query Management Anne Fitzgerald Q&A 66
Balancing Market: Imbalance Price *Excludes high prices on the 24 th of January May 11 th to June 18 th 5 Minute 30 Minute No of Prices Available 10,443 /10,994 1,733 /1824 5.01% 4.99% No of Backup Prices Used NA 103 Minimum Price € -€451.06 -€219.60 Max Price € €491.98 €482.09 Standard Deviation 71.04 55.87 Rolling Average € €38.85 €39.02 Average Imbalance Price YTD €58.08 €57.96 67
Balancing Market: Imbalance Price 21 st of May 22 nd of May 68
Balancing Market: Imbalance Price 69
Balancing Market: Imbalance Price 70
Balancing Market: Imbalance Price 71
Balancing Market: Imbalance Price 72
Balancing Market: Imbalance Price 73
Balancing Market: Imbalance Price 74
Balancing Market: Imbalance Price 75
Balancing Market: Imbalance Price 76
Balancing Market: Imbalance Price 77
Balancing Market: Imbalance Price 78
Agenda Item Presenter Welcome Anne Fitzgerald General System Failure Anne Fitzgerald Known Issues Update Eoin Farrell Ex-Ante Market Liam McAllister, Michael Atcheson Balancing Market Rory Cafferky Settlements Sean O’Rourke, John O’Dea, John Tracey Disputes & Repricing Update Julie McGee Brexit Update Michael Kelly Market Participant Roadmap Mark Needham Query Management Anne Fitzgerald Q&A 79
Settlements : May 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 27 3 1 1 st – 31 st Settlements Initial 31 25 5 1 1 st – 31 st Settlement Weekly 4 4 - - Documents 1 st – 31 st Credit Reports Daily 66 63 - - 1 st – 31 st Payments In Weekly 4 4 - - 1 st – 31 st Payments Out Weekly 4 4 - - 80
Settlements: May 2019 Indicative settlements 81
Settlements: May 2019 Initial settlements 82
Key issues impacting publication June 2019 timelines Key Date (s) Issue Impact to schedule timelines Issue Status • Wednesday General System Failure Caused delays to the Indicative runs of the 11 th / 12th Systems back up & running 12 th & 13 th June allowing Settlements to • Caused delays to the Initials of the 6 th /7 th /8 th & 9 th continue. June • Settlement Documents for the Billing period of the 2 nd - 8 th published late afternoon on the 14 th June • Monday 10 th Registration of new unit set Caused continued delays to indicative run of the 12th Unit details corrected & tested. effective June 12 th set-up in meaning subsequent runs of the 13th -17th also Backlog of indicatives to be application with incorrect file delayed processed. type Key points: • Increase of additional catch-up days in June due to the backlog of runs caused by above event • Additional pro-active analysis continues re: “Incorrect IPQBOA values (KIR ID: 5893 )” – impact to processing timelines to perform required analysis 83
Resettlement Update June 20 th 2019
Overview – Resettlement Drivers (i) Modifications - Two high priority modifications relating to Fixed Cost Payments* have been deployed to production on the 11 th June (See Initial Settlement 8 th June): • Mod_07_19 / CR77 - No-Load Costs • Mod_34_18 / CR73 - Make-Whole Payments (ii) Fixed Costs Transfer Defect - A data transfer defect resulted in low Fixed Costs* being paid to Participants from October 1, 2018 to 27 January 2019. This has accrued valid Fixed Charges of € 32 million that will be paid out over 16 weeks on the commencement of M+4 on the 5 th July (iii) CFC & IP QBOA Defects – 6/8 Fixed Costs and 3 Settlement QBOA fixes deployed 11 th June (See Initial Settlement 6 th June). Remaining two CFC defects relate to the transfer of heat state to settlements and the recovery of saved costs (CSUR/ CNLR) *Fixed Cost Payments or Charges (CFC) - the differences between how a Participant would ideally run their unit to meet its ex-ante market commitments and how the unit was operated to support a secure operate power system. 2
Resettlement - Processing Planning on running a single resettlement process (Inc. accelerated catch-up) : The priority is the large volume of formal queries/defects to be captured in first month of resettlement (October 2018). Simultaneous resettlement of different billing periods is not planned due to the following considerations: Additional large volume of statements for actual M4 BALIMB/CRM/MO could affect participants processing ability i.e. multiple REPT_044 for simultaneous resettlement runs. Cash collateral impacts of catch-up resettlement as well as actual M4 in single SD. Re-running of multiple IPs for resettlement has an implication for the accuracy of initial conditions because every day leading into next. 2
Resettlement timeline – short term Publish Sign-off Release C (11 th ) 1 st resettlement publication Jun Jul w/e 7 th w/e 14 th w/e 21 st w/e 28 th w/e 5 th w/e 12 th w/e 19 th w/e 26 th Environment W1 Process W1 Analysis Forecast W2 Process W2 Analysis Test Agree Internal Review Internal Forecast Internal Forecast Internal Forecast Internal Forecast Internal Forecast Internal Forecast Analysis Process Analysis Analysis Analysis Analysis Analysis W1 IP W1 CSB W1 Analysis W2 IP W2 CSB W2 Analysis Production Final Run W3 IP W3 CSB W3 Analysis W4 IP W4 CSB W4 Analysis W5 IP W5 CSB W5 Analysis W6 IP W6 CSB W6 Analysis
Timeline June 11 th System upgrades for CR73 and CR77 deployed (subject to passing test) June – 5 th Data preparation, loading of use cases and preliminary checks leading to Instruction July Profiling (Inc. QBOA) re-runs and import into the Billing System • Commence M+4 resettlement (Included in Settlement Documents) 5th July • Commence payment of accrued Fixed Charges from October 2018 – January 19 (Approximately € 32.0m - € 2.0m per week for 16 weeks) • Additional ~ € 500K to be payed out in CFC due to defect fixes in Release C Once rolling M4 period covers the modifications effective dates: • M4 recovery of CR 73 payments back to January 27 (Approximately € 19.2m - € 0.80m per week for 24 weeks) • M4 recovery of CR 77 payments back to May 3 (Approximately € 6.0m € 1.5m per week for 4 weeks) September Confirm the inclusion of the increased Fixed Costs in 2018-2019 in the 2019-2020 2019 tariff November Commence M+13 2019 5
Fixed Cost Payments or Charges - Overview • Fixed Cost Payments or Charges: – Difference between Market Operations and Physical Operations can result in units incurring or saving additional fixed costs versus those incurred in a unit’s ex -ante market schedule; – Fixed costs include additional or reduced number of starts, and additional or reduced number of Imbalance Settlement Periods where the unit is synchronised and incurring fixed costs for operating. • Whether these charges or payments apply depends on Commercial Offer Data used in settlement: – If settlement is based on Simple format, fixed costs can be incorporated into those Price Quantity Pairs, with fixed costs recovered through the Imbalance and Premium Components; – If settlement is based on Complex format, fixed costs are explicitly stated while Price Quantity Pairs represent variable costs, therefore this side-payment mechanism is needed to recover fixed costs. • This Payment or Charge is intended to: – Make the unit whole if their balancing market revenues are not sufficient to cover their additionally incurred fixed costs; and – To recover the unit’s fixed costs which were saved. 89
Fixed Cost Payments or Charges - Key calculations Fixed Cost Payments or Charges has four main formulas feeding into its calculation: Per contiguous operating period 90
Fixed Cost Payments or Charges - Scenarios MW Start Payable Start Recoverable No Load Payable No Load Recoverable Market Operation (qFPN) Physical Operation (qD) t Pure Commitment (when Complex COD applies): • Start cost payable; • No-load costs payable for entire commitment period. 91
Fixed Cost Payments or Charges - Scenarios MW Start Payable Start Recoverable No Load Payable No Load Recoverable Market Operation (qFPN) Physical Operation (qD) t Pure Decommitment (when Complex COD applies): • Start cost recoverable; • No-load costs recoverable for whole decommitment period. 92
Fixed Cost Payments or Charges - Scenarios MW Start Payable Start Recoverable No Load Payable No Load Recoverable Market Operation (qFPN) Physical Operation (qD) t Keep On (when Complex COD applies): • Start cost recoverable for prevented start; • No-load costs payable for additional commitment period. 93
Fixed Cost Payments or Charges - Scenarios MW Start Payable Start Recoverable No Load Payable No Load Recoverable Market Operation (qFPN) Physical Operation (qD) t Two-Shift (when Complex COD applies): • Start cost payable for additional start; • No-load costs recoverable for reduction in commitment period. 94
Fixed Cost Payments or Charges - Modifications There have been two modifications made to the T&SC since go live: • MOD_34_18 which relates to units being made whole for their negative imbalance revenue, including when the unit has no balancing market related costs (effective from 27 th January 2019). Martin Kerin chaired a call with participants on how to calculate this mod on 24 th May. • MOD_07_19 which relates to an incorrect logical connector in the No Load Cost in T&SC F.11.2.3 (a) part (i) and (ii). The “and” has now changed to “or” which is effective from 3rd May 2019. Both modifications are in production settlement system from 11 th June 2019. 95
Fixed Cost Payments or Charges - Modifications Example of MOD_07_19 MW CNL applies prior to 3 rd May Market Operation (qFPN) Meter Quantity (QM) t Prior to the mod if a unit had a non zero FPN value and a non zero meter value then the no load costs would have applied. From 3 rd May onwards, units will not receive no load costs in this scenario. 96
Fixed Cost Payments or Charges - Modifications Example of MOD_07_19 MW CNL applies Market Operation (qFPN) Meter Quantity (QM) t In the example above, the unit will continue to receive no load costs when FPN equals zero and QM equals a non zero value. 97
Agenda Item Presenter Welcome Anne Fitzgerald General System Failure Anne Fitzgerald Known Issues Update Eoin Farrell Ex-Ante Market Liam McAllister, Michael Atcheson Balancing Market Rory Cafferky Settlements Sean O’Rourke, John O’Dea, John Tracey Disputes & Repricing Update Julie McGee Brexit Update Michael Kelly Market Participant Roadmap Mark Needham Query Management Anne Fitzgerald Q&A 98
Disputes and Repricing Update 1 October 2018 to 12 June 2019 Count of Days Issue Dates Issue Present in Imbalance ID Issues to be resolved via repricing Present Pricing 5720 Negative Reserve Flag 8 1/10/18 to 8/10/18 5739 Exchange Rate 24 1/10/19 to 24/10/18 1/10/18 to 26/3/19 5737 Units being skipped in the QBOA calculations 220 29/4/19 to 11/6/19 1/10/18 to 26/3/19 5831 Cancelled Dispatch Instructions 220 29/4/19 to 11/6/19 5806 DESY Pump Storage Instructions 254 1/10/18 to 11/6/19 5712 Non Controllable Wind QBOAs 121 1/10/18 to 29/1/19 9/3/19 to 11/3/19 Rpc4 Wind DIs Datafeed Error 8 9/4/19 to 13/4/19 COD sporadically switching between Simple and 1/10/18 to 26/3/19 5785 220 Complex 29/4/19 to 11/6/19 Rpc1 Incorrect QBOA for a Unit 8 1/10/18 to 8/10/18 Rpc2 QBOA being calculated for a Decommissioned Unit 2 1/10/18 to 2/10/18 14/12/19; 7/1/19; 14/2/19; 112877 Under Test PN Validation Error 8 15/2/19; 28/2/19; 22/3/19; 10/4/19; 17/4/19 NA Dispatch Instruction Timing Issue 254 1/10/18 to 11/6/19 5817 Initial Conditions Being Incorrectly Applied 254 1/10/18 to 11/6/19 LCLO Instruction causing QBOAs for whole 5 minute 1/10/18 to 11/6/19 5929 254 period to drop LOCL/LCLO not working across settlement day 1/10/18 to 11/6/19 5957 254 boundaries 99
Pricing Disputes • All known manifest errors have been closed in Release C. The rolling dispute should cease from 12 th June 2019. • If any new errors are detected in the pricing calculation, then we would remind Participants to follow the Pricing Dispute process; and continue to raise any anomalies identified with SEMO for investigation. • Planned Repricing Implementation Date: August / September 2019* - Release D *Pending successful testing. 100
Recommend
More recommend
