Single Electricity Market SEM Release 2.1.0 – October 2012 Change Control Forum (CCF) Meeting...

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

26th January 2012 (Dublin)

© SEMO.2

Agenda

Provisional Priority List Proposal

Introduction & Review

Change Requests for consideration

Next Steps

Questions


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).

© SEMO3

Capacity Review

The following table details what changes are already in scope. These consist of Modification Proposals, approved to date.

© SEMO4

© SEMO5

Agenda




Next Steps

Questions

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:

© SEMO6

Change Requests

CR Ref System Description Priority Org. ImpH/M/L

RiskH/M/L

ReturnYears

Vendor Hours

SEM_PC_CR267 MA Wind and Load Forecast Data High SEMO H M 84

SEM_PC_CR266 MI Change of Effective Date in MPI High SEMO H M 356

SEM_PC_CR263 MI/POMAX POMAX does not read updates From MPI High SEMO H M 356

SEM_PC_CR260 MI Additional MI-AMP feed High East West/ Moyle

480

SEM_PC_CR207 Settlements Automation of FMOC Calculation High SEMO M M 90

SEM_PC_CR261 Settlements Removal of Orphan Trading Site Settlement Points High SEMO M M 196

SEM_PC_CR224 STL Type 3 statement version identification High Airtricity Base 704Opt1) +88Opt2) +48Total 840

SEM_PC_CR168 STTL Unnecessary File Import Type selection Medium SEMO M M 52

SEM_PC_CR231 MI/Settlements MI-STL Daily Push Medium SEMO

M M

Option1) 220

Option2) 464

SEM_PC_CR265 Pomax Task Functionality Medium SEMO M M 232

SEM_PC_CR286 MA Publication of zero IUNs when no PQ pairs available

Medium SEMO M M 268

Provisional Priority List Proposal – ABB/Navita (20-Dec)

Total Vendor Hours Assessed : 5814 hours

Available Capacity: 1424 hours

© SEMO7

Change Requests continued..

CR Ref System Description Priority Org. ImpH/M/L

RiskH/M/L

ReturnYears

Vendor Hours

SEM_PC_CR188 MI I Include a "Download" in PDF" option for SEMO published Invoices

Medium ESB International

552

SEM_PC_CR189 MI Invoices Filter Checkbox ChangeNote: Is dependent on SEM_PC_CR224 (additional 840 hours)

Medium ESB International

Base 340Opt1) +16Opt2) +32Total 388

SEM_PC_CR193 MI TLAF publishing in the MPI Medium Energia 432

SEM_PC_CR198 MI Additional COD Validations Medium ESB International

652

SEM_PC_CR271 Axapta, MI, CRM

Automated FX download to Central Market Systems

Medium SEMO M M 372

SEM_PC_CR264 Pomax Batch Functionality Medium SEMO Under Internal Discussion

SEM_PC_CR272 Axapta Amalgamation of payments for multiple SBIs per PT

Medium SEMO Finance System Change – Awaiting Assessment

SEM_PC_CR262 MI Unit Under Test Submission Screen High SEMO Assessment not yet received

Total (ABB/Navita) CR Hours based on vendor impact assessments 5814

© SEMO8

Agenda




Next Steps

Questions


The following slides detail those CRs which were agreed to be included on a Provisional

Prioritisation List from the CCF meeting of December 20th.

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


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 sufficientbenefit (when considered in the context of the associated costs) should be considered for Closure at this meeting.

© SEMO10


© SEMO11

CR Ref. : SEM_PC_CR266Proposed By: SEMO

Priority: High Complexity: MediumHours: 356

Impact On Market: High Risk of Occurrence: Medium Return (Years): n/a

Description: Change of Effective Date in MPIWill 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 AutomationThis will contribute to the full deployment of automated settlement processing. Currently, script is required to change data.


Priority: High Complexity: LowHours: 84


Description: Wind and Load Forecast DataCurrently 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 efficiency1. 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).


© SEMO12




Description: POMAX does not read updates From MPITo allow greater functionality in the MPI pertaining to registration of new units and their data.

Rationale / Benefit: Operational EfficiencyCurrent 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).

© SEMO13

CR Ref.: SEM_PC_CR260Proposed By: East West and Moyle


Impact On Market: High Risk of Occurrence: High Return (Years): n/a

Description: Additional MI-AMP feedAs 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.



© SEMO.14

CR Ref.: SEM_PC_CR261Proposed By: SEMO


Impact On Market: Medium Risk of Occurrence: Medium Return (Years): n/a

Description: Removal of Orphan Trading Site Settlement PointsTo provide facility to end-date or remove orphan Trading Sites.

Rationale / Benefit : Reduced Errors, Operational EfficiencyWhen 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.




Description: Automation of FMOC CalculationTo remove the use of manual, spreadsheet, calculation of FMOC to automated.

Rationale / Benefit : Reduce ErrorsErrors 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.

© SEMO15


CR Ref.: SEM_PC_CR224Proposed By: Airtricity

Priority: High Complexity: HighHours: Base 704• Opt1) +88• Opt2) +48

Total 840Previous design: 1770


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-3resettlement statements. We are requesting an indicator to be used in the relevant reports / data downloads. Include a flagin 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 3statements. (e.g. D + 4, M + 4 and M +13). A new flag / signal to indicate it is an ad-hoc re-settlement would facilitateusers to easily and efficiently identify the Type-3 resettlement statements. There is a large volume of resettled days in themarket. 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 severaldiscussions have taken place at MOUGs. This request is very similar to CR206 (Re-Pricing Flag on Reports) andtherefore consideration should be given to the benefits of combining this CR with CR206.


© SEMO16


Priority: Medium Complexity: LowHours: 52


Description: Unnecessary File Import Type selectionRemoval of unnecessary File Import Type radio button selection in POMAX \ Import \ Import Files screen

Rationale / Benefit: Reduced ErrorsThe 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 © SEMO


Priority: Medium Complexity: LowHours: Option 1 – 220 Option 2 - 464


Description: MI-STL Daily PushMISTL 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.



Priority: Medium Complexity: MediumHours: 232


Description: Task FunctionalityImproved 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.


© SEMO18




Description: Publication of zero IUNs when no PQ pairs availableProvision 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_CR188Proposed By: ESB International



Description:. Include a "Download" in PDF" option for SEMO published Invoices

Rationale / Benefit Facilitate more efficient processing and distribution of SEMO invoices to Participants.

© SEMO19

CR Ref. : SEM_PC_C189 (ref CR232)Proposed By: ESB International


NOTE: Design is dependent on CR224 – additional 840


Description: Invoices filter checkbox changeThe 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.


© SEMO20

CR Ref. : SEM_PC_CR193Proposed By: Energia



Description:. TLAF publishing in the MPIPublish 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 downloadthis file and store it programmatically. Without this change, many TLAFs need to be manually entered for all units of theyear, which is very time consuming.


© SEMO21


CR Ref. : SEM_PC_CR198Proposed By: ESB International



Description:. Additional COD ValidationsPreventing 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 beentered. 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 unitsPrice values > €100/MWh for CCGTs / Coal unitsStart up costs <€100Start up costs >€1,000,000The top Q value being less than MingenAny 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


© SEMO22




Description: Automated Exchange Rate download to Central Market SystemsProvision for automated data feed from specific FX source into MOI, AXAPTA and MOI.

Rationale / Benefit: Reduce Errors, Operational EfficiencyFurther reduce instances of errors due to manual intervention


Priority: Medium Complexity: MediumHours: Under Internal Discussion

Impact On Market: n/a Risk of Occurrence: n/a Return (Years): n/a

Description: Batch FunctionalityReduction 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 EfficiencyReduction 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.


© SEMO23


Priority: High Complexity: LowHours: Awaiting Assessment


Description: Unit Under Test Submission ScreenTo allow for separate Unit Under Test submission screen away from normal TOD data.

Rationale / Benefit: Reduce ErrorsP&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.


Priority: Medium Complexity: LowHours: Awaiting Assessment


Description: Amalgamation of payments for multiple SBIs per PTImprove 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.

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.

© SEMO25

Single Electricity Market SEM Release 2.1.0 – October 2012 Change Control Forum (CCF) Meeting...

Documents

Transcript of Single Electricity Market SEM Release 2.1.0 – October 2012 Change Control Forum (CCF) Meeting...