market operator user group meeting 1 market operator user group meeting may 18th, 2010 belfast

Market Operator User Group Meeting1

Market Operator UserGroup Meeting

May 18th, 2010Belfast


Agenda

Market Operator User Group Meeting / 11th August 2009

Releases and Infrastructure 10:50

Website Update 11:10

Market Operations 10:40

Questions and Answers 12:20

Customer Service 11:00

Review of Action Items 10:30

Unit Under Test Discussion 11:30

Resettlement Discussion 11:55

Review of Action Items


Updates to April payment dates on Settlement Calendar

Website - list of dynamic reports

Reducing Ad-hoc Resettlement discussion


Agenda











2010 Published Reports

Overall Report Publishing

0%

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

Jan-10 Feb-10 Mar-10 Apr-10

Not done on the day

> 1 hour late

< 1 hour late

On Time

Market Operator User Group Meeting6Market Operator User Group Meeting / June

30th 2009

Key Performance Indicators

Ex-Ante Delivery

90%

95%

100%

Oct-09

Nov-09

Dec-09

Jan-10

Feb-10

Mar-10

Apr-10

May-10Jun-10

Jul-10

Aug-10

Sep-10

TargetActual

Ex-Post Initial Delivery

90%

95%

100%

Oct-09

Nov-09

Dec-09

Jan-10

Feb-10

Mar-10

Apr-10

May-10Jun-10

Jul-10

Aug-10

Sep-10

TargetActual

Invoicing Delivery

60%65%70%75%80%85%90%95%

100%

Oct-09

Nov-09

Dec-09

Jan-10

Feb-10

Mar-10

Apr-10

May-10Jun-10

Jul-10

Aug-10

Sep-10

TargetActual

Credit Cover Increase Notice Delivery

90%

95%

100%

Oct-09

Nov-09

Dec-09

Jan-10

Feb-10

Mar-10

Apr-10

May-10Jun-10

Jul-10

Aug-10

Sep-10

TargetActual


P&S Issues

Market Operator User Group Meeting / June 30th 2009

Trade Date Issue Resolution

29th Mar EP2 publication late due to publication events running before data was pushed to Market Interface Database (DSP module)

Events were rerun. Awareness of publication events times highlighted to Market Controllers

31st Mar SONI I/C trade file for EP1 could not be automatically loaded to an initial error in the schema. This delayed the publication time for EP1

File corrected and sent through to Market Controller for manual upload

3rd & 4th April

Missing reports PUB_D_InitialExPostMktSchDetail report missing from website and MPI PUB_D_EPInitShadowPrices report missing from website and MPI

ABB investigating. Additional logging in SEM R1.7.0 release


Settlement Issues


Settlement Run Run Type Issue Resolution

25th March 2010 Capacity

Indicative

Late Publishing Due to resource type change

from PPMG to PPTG on this date.

Issue calculating CPGPF preventing settlement processing.

Temporary script deployed into Settlements system to ensure a ‘P’ type statements were issued to Participants.

This scenario will be tested and fixed in the next system release

March 2010 Capacity Initial Late Publishing Knock on effect from Capacity

Indicative publication

Published one working day late. Participants notified via market message.

March 2010 Capacity Invoicing Late Publishing Knock on effect from Capacity

Initial publication being delayed

Published two working days late. Participants notified via market message.

Week 52, 2009 M+4 Energy

Resettlement

Late Publishing Late file submission for

settlement dates 27th and 28th December by MDP delaying processing

Published one working day late. Participants notified via market message.

31st March 2010 Energy Indicative Late Publishing Due to Ex Post Indicative pricing

run being delayed as a result of SONI file requiring manual upload

Published at 17:59 instead of 17:00 obligation timeline under T&SC. Participants notified via market message.


Recent RegistrationsParty

Castledockrell Supply Ltd – Effective 06/05/2010 Crystal Energy Ltd – Effective 06/05/2010 NRG Vend Ltd – Effective 15/04/2010 Hunters Hill Windfarm Ltd – Effective 20/03/2010 No other Party applications currently in progress

UnitsGeneration Hunters Hill Windfarm Ltd (Hunter’s Hill APTG) – Effective 13/05/2010 Garvagh Glebe Power Ltd (Garvagh Glebe APTG) – Effective 06/05/2010 Hibernian Wind Power Ltd (Tullynahaw APTG) – Effective 29/04/2010 ESB AER (Arklow Bank Phase 1 APTG) – Effective 22/04/2010 transfer from Arklow Energy Ltd Airtricity Ltd (Kingsmountain Phase 2 (Dunniel) APTG) – Effective 08/04/2010 Viridian Energy Ltd (Ballincollig Hill APTG) – Effective 04/03/2010 Five other Generator Unit applications in progress

Supply

Six Supplier Unit applications in progress



Recent RegistrationsParty

Castledockrell Supply Ltd – Effective 06/05/2010 Crystal Energy Ltd – Effective 06/05/2010 NRG Vend Ltd – Effective 15/04/2010 Hunters Hill Windfarm Ltd – Effective 20/03/2010 No other Party applications currently in progress

UnitsGeneration Hunters Hill Windfarm Ltd (Hunter’s Hill APTG) – Effective 13/05/2010 Garvagh Glebe Power Ltd (Garvagh Glebe APTG) – Effective 06/05/2010 Hibernian Wind Power Ltd (Tullynahaw APTG) – Effective 29/04/2010 ESB AER (Arklow Bank Phase 1 APTG) – Effective 22/04/2010 transfer from Arklow

Energy Ltd Airtricity Ltd (Kingsmountain Phase 2 (Dunniel) APTG) – Effective 08/04/2010 Viridian Energy Ltd (Ballincollig Hill APTG) – Effective 04/03/2010 Five other Generator Unit applications in progress



Recent Registrations

Units

Supply Six Supplier Unit applications in progress

Unit Type Change

Garves Windfarm from APTG to VPTG – Effective 25/03/2010 Aughinish Alumina Ltd two PPMG to PPTG – Effective 25/03/2010



Agenda










SEM R1.7.0 Release

Market Operator User Group Meeting / 22nd September 2009

Release postponed – notification issued April 28th.

Why the delay?

Market Trial uncovered issue downloading a small number of Settlement reports via Type 3 – this was as a result of the Java 3rd party upgrade.

Workaround was available (Type 2) but this was deemed unacceptable to support Production operations.

Not enough time remaining to:• Take delivery of the fix;• Test internally (system & regression); and• Test with Participants (Market Test).

SEM R1.7.0 Release


What has this identified?

Our vendors Vendor Unit / System testing must be expanded Quality of deliverables must be improved

SEMO Internal Integration Testing must be broadened to cover all reports

(Type 2 and Type 3 was tested but not all reports were run for each channel)

Our Participants Must engage in a meaningful way with Market Test phases. SEMO

cannot verify impact on downstream Participant systems. The onus is on the Participant to ensure interfaces are functioning as expected.

Overall Must guard against complacency. Each stakeholder has a

responsibility for the successful implementation of change. “Past Performance is not a guarantee of future success”.

SEM R1.7.0 Release


What is being done to mitigate future risk?

SEMO Expanding Integration Testing coverage to include all reports for

both Type 2 and Type 3.

Investigating Automated Testing to:• Allow for greater coverage in same test period duration;• Ensure more robust and consistent testing; and• Reduce the risk of “human error”.

Have agreed a release checklist / procedure with our vendors to improve quality of deployments to test environments.

Exploring the implementation of KPI’s with our vendors to measure improvements.

Have established monthly meeting with senior ABB management to evaluate quality issues, implement appropriate controls and monitor progress.

SEM R1.7.0 Release


What is being done - Vendors?

Established Fact: Up to this point the vendor testing function has been too closely aligned to the development teams.

Set up of a dedicated “offshore” test team to • Ensure impartial testing takes place; and• Increase test coverage.

Vendors are also investigating Automated Testing.

Monthly management meetings with SEMO.

SEM R1.7.0 Release


The methodology worked: Market Test fulfilled it’s function.

SEMO have identified and will implement more thorough and robust controls with our vendors

Refocus: All of us must guard against complacency – we have

been very successful to date but “past performance ………….”

Delivering change to a complex suite of systems across multiple platforms is not a simple task.

Importance of engagement – all stakeholders (SEMO, Participants, MDPs, TSOs etc) are responsible for their own testing – this cannot and should not be delegated.

SEM R1.7.0 Release – Updated Deployment


May 7th : Vendors deliver software update to SEMO to resolve issue

May 10th to May 21st: SEMO executes internal testing

May 10th: SEMO issues revised Market Test Schedule to the SEM

May 17th to May 27th: Market Test Phase - Conference Calls daily at 16:30 Phone No: 01 6647777 Participant PIN : 79592

May 28th: Deployment of SEM R1.7.0 to Production (subject to successful conclusion of testing).

SEMO IT – SEM Release R1.7.0 – Scope Reminder


In addition 73 defects (46 raised from Production) are included in scope.

Change Requests

Ref. Mod. Ref Sub-System Description Raised By

SEM_PC_CR139 N/A MI Change to Daily Load Forecast Report. Current report reports on a Trading Day basis. The T&SC code stipulates this report should be on a Calendar Day basis.

SEMO

SEM_PC_CR151 N/A Settlements / Metering

SEMO Internal Meter Data Loading Mechanism SEMO

SEM_PC_CR157 N/A MI Enhance SEMO ability to update Registration Effective Date as required. SEMO

SEM_PC_CR165 N/A Settlements Invoice Job – Confirmation for Approval of Invoices. SEMO

SEM_PC_CR166 N/A Settlements Invoice Job – Self-Billing Invoice Due Dates Defaulted. SEMO

SEM_PC_CR169 N/A MI Single entry of Exchange Rates. SEMO

SEM_PC_CR175 88_07 MI Actual Load Summary Report: Provide a new version of the Daily Actual Load Summary Report to be run at d+4 and to include EP2 data only.

Mods Cmte

SEM_PC_CR177 N/A MI / Settlements

Data Service for the transfer of data from the Central Market Systems to the new SEMO website (Regulatory approved project).

SEMO

SEM_PC_CR194 N/A MI Remove ability of Interconnector Units to enter default data (e.g. COD). SEMO

SEM_PC_CR196 N/A RCUC VPT Optimisation SOs

SEM Release R1.7.0 – MP Functional Changes


Release will have minimal functional impact on Participants: 1 new report – D+4 Daily Actual Load Summary

• MPUD has been issued along with sample reports on Jan 14th to aid Participants development effort

1 modified report – 4 Day Load Forecast Report • Switching from Trading Day to Calendar Day• No interface change required however contents will differ (TD Vs

CD)

Specific tests for verifying that these changes function correctly were included in the Market Test Pack issued on April 8th.

SEM R1.8.0 – Scope Reminder

Change Requests

Ref. Mod. Ref Sub-System Description Raised By

SEM_PC_CR145 34_08 MI/MA Dual Rated Generator Amendment Mods Cmte

SEM_PC_CR148 47_08 MI / MA Enduring Solution for the validation of Technical Offer Data – dependency on SEM_PC_CR158.

Mods Cmte

SEM_PC_CR150 N/A Settlements Cross Border VAT. Legislative

SEM_PC_CR158 N/A MI Registration – Additional Validations. SEMO

SEM_PC_CR164 N/A Settlements Inter-day Batch Dependency SEMO

SEM_PC_CR167 N/A Settlements Processing Environment Dashboard SEMO

SEM_PC_CR179 N/A MI Unit Under Test Scheduling SEMO

SEM_PC_CR191 N/A Settlements Fix for Eligible Availability Workaround SEMO

SEM_PC_CR195 N/A MI SEMO MPI User Effective Date in the past SEMO

SEM_PC_CR197 N/A MI M+13 JESU Feed EirGrid TSO

SEM_PC_CR202 N/A Settlements Dispatch Start Up Cost Calculation SEMO

SEM_PC_CR208 N/A Settlements IPCCEN IPCCCP Batch Alert SEMO

Defined scope includes 12 Change Requests:

SEM R1.8.0 – Major Milestones


March 18th: Scope confirmed

March 26th: High-Level scope document issued to Participants

March 30th: Potential Participant impact document issued to Participants

May 14th: First official draft of interface documentation from vendors (SEMO review)

End May: Issue of first draft (post SEMO Review) to Participants

Early June: Participant Workshop – feedback

End June: Final Documentation issued from vendors

Early July 2010: Follow up Participant workshop

September 27th - October 22nd: Market Test (4 weeks)

October 29th: Deployment

SEM R1.8.0 Timeline

01/12/2009 16/11/2010

Jan-10 Feb-10 Mar-10 Apr-10 May-10 Jun-10 Jul-10 Aug-10 Sep-10 Oct-10 Nov-10

29/10/2010SEM R1.8.0 Deployment

Dec - JunVendor Design & Code

02/08/2010Start SIT

27/09/2010Begin MT

27/08/2010SEM R1.9.0 Cut-Off Date

SEM R1.8.0Test Phase DurationFAT: Factory Acceptance Test 4 weeksSIT : System Integration Test 7 weeksMT : Market Test 4 weeks

18/09/2010Complete SIT

23/07/2010Complete FAT

28/06/2010Start FAT

03/12/2009 - 25/06/201029 Weeks

Revised Release ScheduleRelease DeploymentSEM R1.7.0 May 28th, 2010SEM R1.8.0 October 29th 2010SEM R1.9.0 April 29th, 2011

23/04/2010Final URS Signoff

22/10/2010Complete MT

SEM R1.8.0 – October 2010 Provisional High Level Sequence of Events and Time Lines

28/05/2010SEM R1.7.0 Deployment

Revised

19/02/2010SEM R1.8.0 Cut-Off Date

08/03/2010Start SIT

12/04/2010Start MT

19/03/2010Proposal Document Forwarded to RAs

03/03/2010CCB Meeting 1

16/04/2010Complete SIT

26/03/2010Scope document

published

16/03/2010CCB Meeting 2

14/05/2010Initial MP

Documentation

30/06/2010Documentation

finalised

Apr-10Complete MT

Phase 1

27/05/2010Complete MT

Phase 2

SEMO IT – SEM Release R1.9.0 (April 2011)


Release Cut-Off Date for the SEM R1.9.0 release

Friday, August 27th, 2010

SEMO-IT Infrastructure Update

Market Operator User Group Meeting / 18th May 2010

Central Market Systems – Planned Maintenance

Tuesday 24th of April The CMS were taken offline as part of our monthly planned maintenance.

Tuesday 4th of May The CMS were taken offline to perform Database maintenance.

Monday 17th of May – 27th of May 2010 Market Test (MT) performed by Participants – covering both functional and technical

upgrades. SEMO strongly recommends that all participants test their systems (which will include their upgrades). These tests should include both Type 2 & Type 3 and cover all critical business processes.

SEMO-IT Infrastructure Update


Issues:Date Issue Cause Resolution

7th & 8th of May Some Market Participants received an error when trying to retrieve certain reports.

Issue identified in cross-site synchronisation application.

Issue only effected retrieval requests that were serviced by the Belfast site, an interruption to one of the Wide Area Network circuits caused the sync application to fall behind. The application was allowed to ‘catch-up’. All reports were available on the Dublin side during the issue.

17/5/10 All CMS applications stopped responding to requests at 12:30pm.

Still under investigation but initial indications are pointing towards a network infrastructure issue.

Stopped all CMS applications and brought the second Oracle server into the cluster. Market applications were then restarted.

SEMO-IT Infrastructure


SEM Release R1.7.0 (May 2010): Release time

Revised release window:SEMO will bring the Central Market Systems offline at 6pm on Friday the 28 th of May until 6am of Saturday the 29th at 6am.The Dublin servers will be upgraded first followed by Belfast site.


Agenda











Query Statistics Mar-Apr 2010

No. of calls older than 30 days: 12


Query Statistics Mar-Apr 2010


Disputes – May 2010

There are currently no outstanding disputes

2 disputes have been resolved since the last MOUG in March


Group Customer Survey

Eirgrid Group Customer Survey Eirgrid TSO, SONI & SEMO

Participant consultation at development phase

Timescales – July 2010

Findings will be reported – MOST & Group Customer Conference


Agenda











SEMO Website Project

Project Update

Testing ongoing User Awareness

– June Go Live – late June For further details visit www.sem-o.com


Agenda










Introduction


Understanding of SEMO market system for units requesting to go under test

Unit under test current process

Proposed new unit under test process

Process for units requesting to come off test

UUT Semo Market System


Parameters that are submitted by Market Participant for Unit Under TestEffective Date- SEMO controller will accept unit under test request in market system. It’s only when effective

date equals the Ex-Ante date, the details will be processed in our system.- The request expires when new request has been accepted. Only 1 valid request in the system

at any one time.- Its specific to SEMO Market Systems in order to change units from PPMG to PPTG.

Start Date & End Date- Dates are inclusive.- Submit start date and end dates relating to the trading days the unit will be under test.

For example if the unit is going under test from the 06th to the 15th, the unit will be under test from 6am on the 06th until 5.59am on the 16th.

- If the test is for 1 day only, Test Start Date = Test End Date.

Participant Name & Number

Generator Number

Ex Ante pricing schedule is run ONE DAY BEFORE the TRADE DATE. Under test flag follows TRADING day convention, not calendar day.

UUT Current Process


Monday D-5 = 01/02/101. Market Participant submit request through MPI by 12 noon.

2. SEMO email request to TSO

Tues D-4 =02/02/101. TSO Accept/Reject Request by 16:00

2. SEMO Accept through MPI 3. Alert Market Participant and TSO

Wed D-3 = 03/02/10 and Thurs D-2 = 04/02/10 Market Participant can submit COD.

Fri D-1 = 05/02/10Market Participant submit COD by 10:00am

SEMO run Ex-Ante @10am for 06/02/10

Example:Effective Date: 04/02/10

Start Date: 06/02/10End Date: 15/02/10

•The Trading and Settlement code states that 5 working days notice in advance of unit under test start date.

•Approval/Rejection time is required from the TSO (currently around 24 hours)

•Effective date is prior to Start Date option to make amendments to Unit Under Test request.

•Accept/ Reject can be delayed until more information is obtained.

•New request can overwrite current accepted request up until effective date.

•Market Participant can cancel request.

•System has been designed and tested around the 5 working day’s notice.

UUT proposed new 5 working day Process


Monday D-5 01/02/10Market Participant send email notification

Tues D-4 =02/02/10 and Wed D-3 = 03/02/10Market Participant can finalise information with TSO

Thurs D-2 = 04/02/10

1. Market Participant submit through MPI by 12noon.2. SEMO email TSO to accept or reject by 12:30.

3. TSO Accept/Reject Request by 16:00 & email SEMO.4. SEMO Accept through MPI by 16:30 and change MP status.

5. Alert Market Participant and TSO6. Market Participant can submit nomination profile.

Fri D-1 = 05/02/10Market Participant submit COD until 10:00am

SEMO run Ex-Ante @10am for 06/02/10

•Before submission of request through the MPI date range and profiles will be agreed.•Strict response timeline by all making process more efficient.

•SEMO market operator will review under test request @ 12noon for D-2.If a Market Participant submits a request through MPI ahead of D-2 this request will not be picked up until D-2.

•TSO has just 4-5hrs to review and accept request.

•System not fully tested to deal with criteria, defects may arise.

•Impossible to change start date once it’s been accepted in SEMO market system. A script will be required.

•Must receive 5 working day notice. If email notification is not received, request will be rejected.•Process not applicable at weekends.



Changing End Date


Extending or Reducing End Date:

-Request must be submitted D-2 from test end date as per the trade and settlement code.-The end date and effective date is required to be equal.-The Ex-Ante for the prior date must be completed before new request is accepted.-The same process applies, TSO must approve any changes.

Example of Extending End DateOriginal Request: New Request: Extend to 20/02/10

•Can only be accepted in SEMO market system after Ex-Ante for Trade Date 15/02/10 has been completed.

Example of Reducing End DateOriginal Request: New Request: Reduce to 10/02/10

•Can only be accepted in SEMO market system after Ex-Ante for Trade Date 09/02/10 has been completed.










Agenda











Cost to the Market of Resettlement

• Approx 75 Participant Accounts in Market

• ½ day per resettlement event to reconcile and pay

• MO time, 5-10 person days per event

=> Estimate of 45 Person Days for each Resettlement event

• 24 ad-hoc resettlement events per year => 3 people for a year

• 200 Post M+13 resettlement events per year => 24 people for a year


Quality of Feeds &

Calculations

Timing of Corrections

Criteria for Ad-hoc

Effective Resettlement


Errors by Responsible Party

0

100

200

300

400

500

600

700

800

900

Eirgrid IA MRSO NIE SEMO SONI

System

SOSO

Operational

MDP

LF

ITF

DI

CLAF

AA


Quality of Feeds &

Calculations


Criteria for Ad-hoc



Resolution of Errors by Resettlement Run

0

200

400

600

800

1000

1200

1400

2007 2008 2009 2010

Post M+13

M+13

M+4

Initial

Adhoc

40%

40%

20%


Quality of Feeds &

Calculations


Criteria for Ad-hoc


Ad-hoc Resettlement based on Materiality(Nov '07 to March '10)

0

10

20

30

40

50

60

50k 60k 70k 80k 90k 100k 110k 120k 130k 140k 150k 160k 170k 180k 190k 200k

Materiality (Euro)

Nu

mb

er o

f D

ays

Res

ettl

ed

Cummulative Total

Market Operator User Group Meeting48Materiality 5

0k

60k

70k

80k

90k

100

k

110

k

120

k

130

k

140

k

150

k

160

k

170

k

180

k

190

k

200

k

Cummulative Total 57 50 47 45 45 43 43 43 43 43 43 43 41 41 41 41


Quality of Feeds &

Calculations


Criteria for Ad-hoc


Quality of data feeds and

processing needs continue to

improve

Timing of Queries needs to

be appropriate

Conclusions

Changes to criteria for ad-

hoc resettlement needs

considered, especially due

to re-pricing and Post M+13


Lets Discuss……..

Option 1: Discrete periods for Query of Resettlement

Option 2: Increase Materiality Level

Option 3: Timetabled Resettlement of Re-pricing only

Option 4: Threshold for Whole Market Resettlement Post M+13


Agenda










market operator user group meeting 1 market operator user group meeting may 18th, 2010 belfast

Documents

market operations

hour latenot

hr latenot

indicativemonthon time

resettlement discussion11

website update

review of action items10

customer service11