1. Single Electricity Market SEM Release 2.1.0 – October 2012 Change Control Forum (CCF) Meeting Conference Call Number: +353 (0) 1 6647777 Participant PIN: 79592 26 th January 2012 (Dublin)

2. © SEMO. 2 Agenda Provisional Priority List Proposal Introduction & Review Change Requests for consideration Next Steps Questions

3. Introduction & Review  Welcome to the second of two Change Control Forum (CCF) meetings for the SEM R2.1.0 release (October 2012).  The first meeting decided on a Provisional Prioritisation List of Change Requests (CRs) based on business criticality.  The SEM Design Service (SDS) has since secured vendor Impact Assessments for the CRs on this list.  This meeting is to finalise the list of non Trading & Settlement Code (T&SC) CRs for the October 2012 release on the basis of cost/benefit and remaining release capacity.  Subsequent to this meeting the SEMO IT Manager will issue a final recommendation report to the Regulatory Authorities (RAs) for approval.  On receiving RA approval, SEMO IT will direct our vendors to include the CRs in scope.  SDS to publish complete scope to the industry once finalised.  Please Note: CRs relating to our Finance Application do not come under the release vendor capacity agreement with ABB/Navita and can be considered separately (unless there is an interface dependency on Navita systems). © SEMO 3

4. Capacity Review  The following table details what changes are already in scope. These consist of Modification Proposals, approved to date. © SEMO 4

5. 5 Agenda Provisional Priority List Proposal Introduction & Review Change Requests for consideration Next Steps Questions

6. Provisional Priority List Proposal – ABB/Navita (20-Dec)  The following tables (over 2 pages) comprises the Provisional Priority List as determined at the CCF of 20-Dec-2011 involving CRs that are ABB/Navita related: © SEMO 6 Change Requests CR RefSystemDescriptionPriorityOrg.Imp H/M/L Risk H/M/L Return Years Vendor Hours SEM_PC_CR267MAWind and Load Forecast DataHighSEMO H M 84 SEM_PC_CR266MIChange of Effective Date in MPIHighSEMO H M 356 SEM_PC_CR263MI/POMAXPOMAX does not read updates From MPIHighSEMO H M 356 SEM_PC_CR260MIAdditional MI-AMP feedHighEast West/ Moyle 480 SEM_PC_CR207SettlementsAutomation of FMOC CalculationHighSEMO M M 90 SEM_PC_CR261SettlementsRemoval of Orphan Trading Site Settlement PointsHighSEMO M M 196 SEM_PC_CR224STLType 3 statement version identificationHighAirtricityBase 704 Opt1) +88 Opt2) +48 Total 840 SEM_PC_CR168STTLUnnecessary File Import Type selectionMediumSEMO M M 52 SEM_PC_CR231MI/SettlementsMI-STL Daily PushMediumSEMO M M Option1) 220 Option2) 464 SEM_PC_CR265PomaxTask FunctionalityMediumSEMO M M 232 SEM_PC_CR286MAPublication of zero IUNs when no PQ pairs available MediumSEMO M M 268

7. Provisional Priority List Proposal – ABB/Navita (20-Dec)  Total Vendor Hours Assessed : 5814 hours  Available Capacity: 1424 hours © SEMO 7 Change Requests continued.. CR RefSystemDescriptionPriorityOrg.Imp H/M/L Risk H/M/L Return Years Vendor Hours SEM_PC_CR188MII Include a "Download" in PDF" option for SEMO published Invoices MediumESB International 552 SEM_PC_CR189MIInvoices Filter Checkbox Change Note: Is dependent on SEM_PC_CR224 (additional 840 hours) MediumESB International Base 340 Opt1) +16 Opt2) +32 Total 388 SEM_PC_CR193MITLAF publishing in the MPIMediumEnergia432 SEM_PC_CR198MIAdditional COD ValidationsMediumESB International 652 SEM_PC_CR271Axapta, MI, CRM Automated FX download to Central Market Systems MediumSEMO M M 372 SEM_PC_CR264PomaxBatch FunctionalityMediumSEMO Under Internal Discussion SEM_PC_CR272AxaptaAmalgamation of payments for multiple SBIs per PT MediumSEMO Finance System Change – Awaiting Assessment SEM_PC_CR262MIUnit Under Test Submission ScreenHighSEMO Assessment not yet received Total (ABB/Navita) CR Hours based on vendor impact assessments5814

8. © SEMO 8 Agenda Provisional Priority List Proposal Introduction & Review Change Requests for consideration Next Steps Questions

9. Change Requests for consideration The following slides detail those CRs which were agreed to be included on a Provisional Prioritisation List from the CCF meeting of December 20 th. SEMO have subsequently secured Impact Assessments from our vendors to enable the CCF to evaluate the implementation impact and cost of each CR. The implementation of these CRs will:  Reduce impacts on Market Participants  Provide greater transparency for the SEM  Mitigate the risk of Operator Error  Introduce efficiencies to SEMO Market Operations (time and cost)  Reduce queries to the Market Helpdesk  Reduce support costs from our vendors  Introduce increased robustness to the CMS 9 © SEMO

10. Change Requests for consideration Three new classifications for each CR have been defined: Impact on the Market of Not Implementing:  High: Cashflow is affected  Medium: Timelines / Credit Cover affected  Low: Minor disruption Risk of Occurrence:  High : Has caused issues more than 5 times previously  Medium: Has caused issues up to 5 times  Low: Rarely occurs – metrics not available Return Period:  The amount of time SEMO estimates to recoup the costs of the change. This value only considers SEMO costs, not Market Participant costs. It has been determined for CRs raised by SEMO only. Note: Those CRs that, in the opinion of the CCF, will not deliver sufficient benefit (when considered in the context of the associated costs) should be considered for Closure at this meeting. © SEMO 10

11. Change Requests for consideration © SEMO 11 CR Ref. : SEM_PC_CR266 Proposed By: SEMO Priority: High  Complexity: Medium Hours: 356 Impact On Market: HighRisk of Occurrence: MediumReturn (Years): n/a Description: Change of Effective Date in MPI Will allow Market Operations to revise Effective Date in the MPI should it be required after original entry is at Accept in MPI. Rationale / Benefit: Greater Efficiency through Automation This will contribute to the full deployment of automated settlement processing. Currently, script is required to change data. CR Ref. : SEM_PC_CR267 Proposed By: SEMO Priority: High  Complexity: Low Hours: 84 Impact On Market: HighRisk of Occurrence: MediumReturn (Years): n/a Description: Wind and Load Forecast Data Currently Trading Day data for Wind and Load in MOI does not include Optimisation Horizon. Also, if this data missing, currently getting no error message in DSI run. Rationale / Benefit: Compliance and increased efficiency 1.Only data submitted by TSO is used – realistic Generator Schedule. 2.Compliance with T&S Code. 3.Increased efficiency in quality of data for completing a Ex-Ante. (DSI perpetuating last value in place of missing values).

12. Change Requests for consideration © SEMO 12 CR Ref. : SEM_PC_CR263 Proposed By: SEMO Priority: High  Complexity: Medium Hours: 356 Impact On Market: HighRisk of Occurrence: MediumReturn (Years): n/a Description: POMAX does not read updates From MPI To allow greater functionality in the MPI pertaining to registration of new units and their data. Rationale / Benefit: Operational Efficiency Current system restrictions mean that unit data must be accepted into all the market systems (including the settlement system POMAX) 17 working days in advance of the unit market effective date. This is to give sufficient time for the System Operator to approve VTOD for this new unit. The problem with this is that once the new unit data has been pushed to POMAX with a market effective date this data cannot be changed for this date. There was a recent issue where unit data was accepted in the MPI and pushed to POMAX but a few days before the market effective date of the new unit, the participant requested to push back the effective date. It was possible to cancel the new unit details in the MPI however this was not possible in POMAX. A vendor script was required to fix this in POMAX which delayed Indicative Settlement and caused breaches to timelines in the Trading and Settlement Code (T&SC).

13. © SEMO 13 CR Ref.: SEM_PC_CR260 Proposed By: East West and Moyle Priority: High  Complexity: Medium Hours: 480 Impact On Market: HighRisk of Occurrence: HighReturn (Years): n/a Description: Additional MI-AMP feed As part of the discussions regarding the implementation of intra-day trading, a means of charging for implicitly allocated capacity are being discussed. In order to provide data required by the Interconnector Owners in SEM, additional data feeds from the Central Market Systems are required following each EA2 and WD[x] MSP Software Run: Implicit Auction Results (by Trading Period) Rationale / Benefit SEM Committee require the Interconnector Owners to have a form of implicit congestion charging and in order to achieve this the above data will need to be provided by SEM. Change Requests for consideration

14. © SEMO. 14 CR Ref.: SEM_PC_CR261 Proposed By: SEMO Priority: High  Complexity: Low Hours: 196 Impact On Market: MediumRisk of Occurrence: MediumReturn (Years): n/a Description: Removal of Orphan Trading Site Settlement Points To provide facility to end-date or remove orphan Trading Sites. Rationale / Benefit : Reduced Errors, Operational Efficiency When a new Trading Site has been created during a unit registration a supplier unit is typically associated with the Trading Site. However if the supplier unit is not associated to the Trading Site at the time of registration but added at a later time instead a duplicate Trading Site will be created in settlement. This has a detrimental effect on the market as it prevents Settlement from being completed. Vendor scripts are required to remove the duplicate Trading Sites, which adds to delays and incurs a cost on the market. CR Ref.: SEM_PC_CR207 Proposed By: SEMO Priority: High  Complexity: Low Hours: 90 Impact On Market: MediumRisk of Occurrence: MediumReturn (Years): n/a Description: Automation of FMOC Calculation To remove the use of manual, spreadsheet, calculation of FMOC to automated. Rationale / Benefit : Reduce Errors Errors are mainly due to registration of new units or changes in Registered Capacity (RC). Error potential coupled with processing times (2 hrs per month & training new members of staff) provide sufficient reasoning for this settlement task to be fully automated.

15. © SEMO 15 Change Requests for consideration CR Ref.: SEM_PC_CR224 Proposed By: Airtricity Priority: High  Complexity: High Hours: Base 704 Opt1) +88 Opt2) +48 Total 840 Previous design: 1770 Impact On Market: HighRisk of Occurrence: HighReturn (Years): n/a Description: Ad-hoc flag in Type 3 statements A new flag / signal to indicate it is an ad-hoc re-settlement would facilitate users to easily and efficiently identify the Type-3 resettlement statements. We are requesting an indicator to be used in the relevant reports / data downloads. Include a flag in the statements to indicate if it is an ad-hoc statement. Rationale / Benefit Currently when the market completes an ad-hoc resettlement, it is difficult to identify the actual settlement run for Type 3 statements. (e.g. D + 4, M + 4 and M +13). A new flag / signal to indicate it is an ad-hoc re-settlement would facilitate users to easily and efficiently identify the Type-3 resettlement statements. There is a large volume of resettled days in the market. It is not easy to identify the settlement run for the ad-hoc run. Easy identification of each statement would reduce the possibility of errors, increase the accuracy of interpretation of market messages and reduce manual workarounds. Two calls have been previously raised with the helpdesk regarding this issue (F0015495 and F0016085) and several discussions have taken place at MOUGs. This request is very similar to CR206 (Re-Pricing Flag on Reports) and therefore consideration should be given to the benefits of combining this CR with CR206.

16. Change Requests for consideration © SEMO 16 CR Ref. : SEM_PC_CR168 Proposed By: SEMO Priority: Medium  Complexity: Low Hours: 52 Impact On Market: MediumRisk of Occurrence: MediumReturn (Years): n/a Description: Unnecessary File Import Type selection Removal of unnecessary File Import Type radio button selection in POMAX \ Import \ Import Files screen Rationale / Benefit: Reduced Errors The flexibility of the Import Files screen in Settlements introduces potential for operator error when running file imports. For operational purposes the Import type radio button (Full import / File import Only / XML import only) selection is unnecessary and is never used. ‘File Import Only’ mode does not save the data in the POMAX database rather it saves the data in the xml file. Incorrect selection of the import type due to operator error has caused occurrences where invoices have been delayed and payment dates have had to be pushed out. Vendor consulting time to generate a script to fix the issue was required and there were knock-on issues for CRM and Funds Transfer. Given the import is always the same there is no need to have the multiple selection options.

17. 17 © SEMO CR Ref. : SEM_PC_CR231 Proposed By: SEMO Priority: Medium  Complexity: Low Hours: Option 1 – 220 Option 2 - 464 Impact On Market: MediumRisk of Occurrence: MediumReturn (Years): n/a Description: MI-STL Daily Push MISTL DLY PUSH Event Window: If parameters of this MOI event have not been extended correctly to push across historical data feeds they cannot be retrieved without resubmission of data. Rationale / Benefit: Reduced Errors From time to time, it may be required to transfer a large amount of incremental data for past dates from MI to Settlements for the purpose of resettlement. This could happen for example when the TSO has realised that the already submitted TLAF values for a range of dates were incorrect. Change Requests for consideration CR Ref. : SEM_PC_CR265 Proposed By: SEMO Priority: Medium  Complexity: Medium Hours: 232 Impact On Market: MediumRisk of Occurrence: MediumReturn (Years): n/a Description: Task Functionality Improved end to end processing of Settlement in POMAX. Rationale / Benefit: Reduce Errors Reduction of errors due to reduced involvement of Market Operator in settlement processing. It will enable increased design flexibility of future batch processes.

18. Change Requests for consideration © SEMO 18 CR Ref.: SEM_PC_CR286 Proposed By: SEMO Priority: Medium  Complexity: Low Hours: 268 Impact On Market: MediumRisk of Occurrence: MediumReturn (Years): n/a Description: Publication of zero IUNs when no PQ pairs available Provision of an output file for all Participants irrespective of PQ pairs being submitted Rationale / Benefit: Market Efficiency MIUN files will not be able to be provided to the IA if no interconnectors bid CR Ref. : SEM_PC_CR188 Proposed By: ESB International Priority: Medium  Complexity: Medium Hours: 552 Impact On Market: HighRisk of Occurrence: HighReturn (Years): n/a Description:. Include a "Download" in PDF" option for SEMO published Invoices Rationale / Benefit Facilitate more efficient processing and distribution of SEMO invoices to Participants.

19. © SEMO 19 CR Ref. : SEM_PC_C189 (ref CR232) Proposed By: ESB International Priority: Medium  Complexity: Low Hours: 388 NOTE: Design is dependent on CR224 – additional 840 Impact On Market: HighRisk of Occurrence: HighReturn (Years): n/a Description: Invoices filter checkbox change The Invoices filter “Check Box” (Most Recent Invoices) if ticked will not include the Month + 4 and Month + 13 SEMO Invoices published. While the date range may be used to filter the most recent invoices it would be beneficial to include the Month + 4 and Month + 13 Invoices in the “Most Recent Invoice” “Check Box” or have an additional “Check Box” which would include Most Recent Month + 4 and Month + 13 Invoices in the selection returned. Rationale / Benefit Facilitate quicker selection of Most Recent Published Invoices including Initial, Month + 4, Month + 13, Market Operator and Capacity Invoices. Change Requests for consideration

20. © SEMO 20 CR Ref. : SEM_PC_CR193 Proposed By: Energia Priority: Medium  Complexity: Medium Hours: 432 Impact On Market: HighRisk of Occurrence: HighReturn (Years): n/a Description:. TLAF publishing in the MPI Publish an agreed format and standardised list of TLAFs, i.e. in Excel, XML or CSV format that will be published ad-hoc and will be downloaded via Type 3 and Type 2 communications. Rationale / Benefit Currently SEMO publishes an Excel format of TLAFs on their website. This is not an official version and so it is liable to change format. As we have multiple units in the market we would like to programmatically load the TLAFs into our system. If the format of the TLAF file was standardised and published on the SEMO WebService, our systems could download this file and store it programmatically. Without this change, many TLAFs need to be manually entered for all units of the year, which is very time consuming. Change Requests for consideration

21. © SEMO 21 Change Requests for consideration CR Ref. : SEM_PC_CR198 Proposed By: ESB International Priority: Medium  Complexity: Medium Hours: 652 Impact On Market: HighRisk of Occurrence: HighReturn (Years): n/a Description:. Additional COD Validations Preventing the accidental submission of erroneous bid data. A simple sense check on input data ought to be embedded into the MPI website, such that warning messages should be flashed up when apparently erroneous bid data is to be entered. This should not prohibit such data being entered, but should warn the participant that the values are unusual. Including specifically, but not limited to:  Price values < €5/MWh for thermal units  Price values > €100/MWh for CCGTs / Coal units  Start up costs <€100  Start up costs >€1,000,000  The top Q value being less than Mingen  Any Q value exceeding the Firm Access Quantity Rationale / Benefit This could prevent erroneous data being submitted which would then lead to the prevention of an erroneous schedule being produced. Such an event can cause prices to be more than 20% higher (estimate from NIAUR) than if the correct data was submitted and prevent the day needing to be rescheduled

22. Change Requests for consideration © SEMO 22 CR Ref.: SEM_PC_CR271 Proposed By: SEMO Priority: Medium  Complexity: Medium Hours: 372 Impact On Market: MediumRisk of Occurrence: MediumReturn (Years): n/a Description: Automated Exchange Rate download to Central Market Systems Provision for automated data feed from specific FX source into MOI, AXAPTA and MOI. Rationale / Benefit: Reduce Errors, Operational Efficiency Further reduce instances of errors due to manual intervention CR Ref.: SEM_PC_CR264 Proposed By: SEMO Priority: Medium  Complexity: Medium Hours: Under Internal Discussion Impact On Market: n/aRisk of Occurrence: n/aReturn (Years): n/a Description: Batch Functionality Reduction of errors due to reduced involvement of Market Operator in settlement processing. It will enable increased design flexibility of future batch processes. This will contribute to the full deployment of automated settlement processing. Rationale / Benefit – Reduction in Error, Operational Efficiency Reduction of errors due to reduced involvement of Market Operator in settlement processing. It will enable increased design flexibility of future batch processes. This will contribute to the full deployment of automated settlement processing.

23. Change Requests for consideration © SEMO 23 CR Ref. : SEM_PC_CR262 Proposed By: SEMO Priority: High  Complexity: Low Hours: Awaiting Assessment Impact On Market: n/aRisk of Occurrence: n/aReturn (Years): n/a Description: Unit Under Test Submission Screen To allow for separate Unit Under Test submission screen away from normal TOD data. Rationale / Benefit: Reduce Errors P&S should not be making changes to registration data, therefore the UUT fields should be displayed separately from registration data. Note that Registration data changes take 29 days to approve whereas UUT process is 2WD turnaround. There is a risk of Registration data being committed with UUT changes without TSO Approval. CR Ref. : SEM_PC_CR272 Proposed By: SEMO Priority: Medium  Complexity: Low Hours: Awaiting Assessment Impact On Market: n/aRisk of Occurrence: n/aReturn (Years): n/a Description: Amalgamation of payments for multiple SBIs per PT Improve efficiency in Funds Transfer by consolidating payments due to Participants into one single payment, instead of multiples. Rationale / Benefit: Operational Efficiencies Would reduce number of authorisations (i.e. instead of 3 single payments, one payment on SBI) Reduce banking charges to the SEM also.

24. © SEMO 24 Agenda Provisional Priority List Proposal Introduction & Review Change Requests for consideration Next Steps Questions

25. Next Steps  CCF (this meeting) to agree a priority list of CRs to be considered for October scope (SEM R2.1.0)  SEMO IT Manager to issue final recommendation report to the Regulatory Authorities for approval.  On receiving final Regulatory approval, SEMO IT will direct our vendors to include the CRs in scope (subject to vendor capacity).  SEMO IT to publish complete scope to the industry immediately once finalised. © SEMO 25

26. © SEMO 26 Questions