igg agenda – 29 th february 2008

1IGGIGGIGGIGG Industry Governance GroupSecretariat:Secretariat: RMDS RMDS www.rmdservice.com

IGG Agenda – 29th February 2008

• Minutes from last IGG meeting 10.00 – 10.10• Change of Supplier Objection to Debt 10.10 – 10.30• Review of Action Items 10.30 – 10.50• Schema Release 10.50 – 11.20• CER Update 11.20 – 11.30• Gemserv Update 11.30 – 11.40• Market Operations Update 11.40 – 11.50• Address Standards Workshop Update 11.50 – 12.00• TAG Update 12.00 – 12.10• Retail Market Design Service Update 12.10 – 12.20• Market Design Update 12.20 - 12.50• Next Steps 12.50 – 13.00


Minutes

Minutes from IGG meeting – 10th January 2008


Action Items

• Actions Addressed in Advance of Meeting• Update on Action Items• Actions to be covered during remainder of presentation• Actions to be carried forward• Other Action Items


Action Items addressed in advance of meeting (closure proposed)

E- Mail issued in advance of meeting listing IGG Actions to be closed, agreement sought


Action Items to be covered later in the presentation

Action Item 10

Prepare proposals on addresses in the Retail Market

Action Item 195

RMDS to document the ‘Outage Notification Process’ and distribute it to market participants

Action Item 202

RMDS to redistribute the revised version of MCR 0063 (MRSO presentation)

Action Item 227

RMDS to inform participants of the date for the next schema release


Action Items to be covered later in the presentation

Action Item 211

MRSO to report back on the preventative steps taken to prevent duplicate batch runs from occurring


Action Items to be covered later in the presentation (Market Design)

Action Item 173

Update the SoLR process to take account of the SoLR decision paper /07/171

Action Item 200

RMDS to provide worked examples showing how the versioning of the 341 message would work for the two proposed solutions


Update on Action Items

Action Item 24 (& Action Item 75)

DR 112 - New MPD 37 New Transmission Connected Sites

– Received feedback from Eirgrid January 24th

– Revised the MPD 37 process to take account of the changes

– Meeting to be arranged to finalise the proposed changes to MPD 37



Action Item 95

Investigate the possibility of addressing inconsistencies between the DUoS rules and the MICs and DUoS Groups in the MPRN data



Action Item 108 (& Action Item 159)

Issue Data Storage and Archiving Document to Market Participants

– Originally issued on Thursday 22nd November and subsequently withdrawn

– Updated version has been re-issued



Action Item 109

New Commercial Policy required to cover Erroneous De-registrations

– Document has been submitted to CER



Action Item 198 (& 197)RMDS to investigate the possibility of publishing the Generator Unit ID / Generation Unit ID and the suitability of using the Export

Arrangement ID on the Extranet – E-mail sent to suppliers on 20th February 2008 seeking

feedback on displaying Export Arrangement ID(s) on the Extranet, four supplier responses received:

• One Supplier had no requirement to see this field on the Extranet• Two suppliers would like this field on the Extranet• One supplier disagreed that the field should be displayed at all as it

is an identifier for an arrangement between two parties



Action Item 198 (& 197) cont

RMDS to investigate the possibility of publishing the Generator Unit ID / Generation Unit ID and the suitability of using the Export Arrangement ID on the Extranet

– Next Steps• A flag (similar to the one used for TSSU) could

indicate the presence of an Export Arrangement ID on the MP Extranet ?



Action Item 206

RMDS to check how the Usage Factor is affected in the case of an MPRN with a mixture of actual and estimated readings on the registers for the same reading visit

– Usage factors will be updated if at least one reading is an actual reading value



Action Item 210

RMDS to follow up with Networks to see if the Service Order they receive contains the meter type details

Item arose from Universal Meter discussion

– MCC appears on the Service Order and meter type details are not on the Service Order



Action Item 212

To publish the Multiplier value associated with an MPRN on the Extranet site

– Multiplier value was not stored for migrated sites– For most NQH sites, the value is 1– Stored at register level for NQH sites– Multiplier not stored in all cases


CER Update


Gemserv Update


Market Operations Update

20

RMDSRMDSRMDSRMDS Retail Market Design Service www.rmdservice.com

Address Standards Workshop


Data Standards and Addresses

Key Outcomes– Well attended– All Address and Customer name Standards agreed– Considerable number of learning outcomes e.g.

Participants should fill in the Notification address in full (including a Care Of Name) when submitting a 010 market message. This will reduce considerably the number of returned Connection Agreements.

– 15 New Action Items• 8 actions relate to the data standards document• 7 other actions

• Job Aids• Print Rules• Use of Technical address etc.


Data Standards and AddressesWorkshop Participants agreed with and approved the following Address Data Standards:

– Upper Case, Apostrophes and Data Entry Rules – Customer Name– Unit/Apt Number– Address Line 1 – Address Line 2– House Number– Street Field– Address Lines 4 and 5– Postal Code – City Field– County Field– Country Field

23


TAG Workshop


MPCC Issues

Market Participants– No new functionality– No plans to develop this product further– Limited visibility of message throughput– Message logs need to be maintained

ESB Networks– ESBN have adopted SAP’s application

integration platform– SeeBeyond OnRamp expertise will gradually

become more limited within ESBN


MPCC Issues

Regulatory– New design could facilitate new market entrants

Technical Issues– Current software has a maximum shelf life of 3 to 5 years.

While the technology is currently working fine it will not last more then 5 years.

– Significant parts of the technical architecture are obsolete:– Access 97 – Windows 2000– IE 5.0– CGI

– Software upgrades involve the distribution installation of CDs.

– There is a licensing overhead which may be removed through the use of open source software.


Key Learning Points

1. Technical Architecture used in the North is very similar to that of the ROI but is using fully supported software

2. ebXML is their business to business protocol used in NI as opposed to RossettaNet in the ROI

3. ESB Networks will not develop the current MPCC4. Security issues

– Unsupported software– Unsecure clients– Continued use of Windows 2000

5. Cannot track messages being processed– Should be able to drill down and check the status of a

message

6. Need a more complete message reconciliation


Key Learning Points cont

7. MPCC can only support one Supplier per MPCC

8. Cannot support large volumes

9. CER and NIAUR will review the current retail systems in use as part of the harmonisation project.

Possible Solutions1. Upgrade Seebeyond

2. Use Open source software– Java, MySql etc.

3. Develop a different paradigm– Web services for smaller suppliers

28


Retail Electricity Market Issues Update

Cormac Madden, RMDS


Retail Electricity Market Issues Log

• Log continuing to issue on a weekly basis

• Summary Statistics (as per last release – 270208)

– Total Number of Issues Logged 149

– Total ‘Closed’ 134– Total ‘In Progress’ 10– Total ‘Being Monitored’ 1– Total ‘Logged’ 4

– Total Raised Since Last Issue 0– Total Closed Since Last Issue 0

30


Retail Market Design Service Update

C. Madden, RMDS


Retail Market Design Service Update – AI 195

IGG Action Item 195 - RMDS to document the 'Outage Notification Process' and distribute it to market participants.

Market System Outage Notification

ES

B N

etw

ork

sR

MD

SM

ark

et

Pa

rtic

ipa

nts

IT S

erv

ice

s

Customer ServiceManager is

informed aboutpending outage

Customer ServiceManager informsSLA owners ofpending outage

SLA holder checkswith all affectedparties to see if

outage can go ahead

NetworkServicesadvise on

outage impacts

Outage Goahead

Inform all internaland External

stakeholders ofpending outage

Yes

MarketParticipantsinformed of

pending outage

MarketParticipants

receive outagenotification

Outage isproposed

RMDS InformsMarket

Participants ofpending outage

Market Participantsreceive notificationof pending outage

No

Outagerescheduledor cancelled

RMDS updatesthe Calendar ofEvents on theRMDS website

32


Discussion Requests & Market Change Requests

Cormac Madden, RMDS


Discussion Request

DR 0153 - Working Practice 0016 – Document the procedure to be used for like-to-like QH meter replacement

• Circulated to the market 22.02.08

• Any comments/feedback?


Discussion Request

DR 0113 - Supplier of Last Resort UpdateSupplier

– A list of alternative suppliers should be sent in the communication to customer affected by SoLR.

SoLR– As SoLR we do not intend listing alternative

suppliers to the customers in our communication with them instead we will refer them to the CER website for details.

Other– 3 month lock down period?


Discussion RequestDR 0128 - Increase in tolerance levels for NQH Meter Reading Validation– Query The 100% tolerance looks OK but should it

not have a max consumption– Response calculations are based on having two

actual reads. Any abnormal consumption is regularly monitoredProposed Tolerance Levels

Expected Consumption on Register (kWh/kVArh)

Absolute Tolerance (kWh/kVArh)

Relative % Tolerance

Resulting consumption range for plausibility (kWh/kVArh)

0 199 1000Expected Consumption +1000

200 499 250 700 to 1750

500 799 200 1500 to 2400

> or = 800 100 1600 to ∞


Market Change RequestMCR 0154 – Versioning of the 341• Question raised – How will the MCR handle version numbers for import

and export data. Worked examples were requested from the previous IGG.– Solution 1 Provide a Version Number at the channel level. This would mean

that the Import QH kW, Import QH kVAr, Export QH kW and the QH Export kVAr would each have a version number. The Read Replacement Flag would no longer be required as the version would indicate the reading being replaced.

MPRN Register Type Version Number

1123230985

50 IMP QH (kW) 1

1123230985

50 IMP QH (kW) 2

1123230985

50 IMP QH (kW) 3

1123230985

53 EXP QH (kVAr) 1

1123230985

50 IMP QH (kW) 4

1123230985

53 EXP QH (kVAr) 2

1123230985

51 IMP QH (kVAr) 1


Market Change RequestMCR 0154 – Versioning of the 341

Proposed Solutions for MCR 154– Solution 2 Provide a separate Version Number at the MPRN level for Import

and Export data and a read replacement flag at the Channel Level Details which would indicate the channel being updated.

MPRN Version No.

Register Type Read Replac Flag

1123230985

1 50 IMP QH (kW) Y

1123230985

2 50 IMP QH (kW) Y

1123230985

3 50 IMP QH (kW) N

1123230985

1 53 EXP QH (kVAr) Y

1123230985

4 50 IMP QH (kW) Y

1123230985

2 53 EXP QH (kVAr) Y

1123230985

5 51 IMP QH (kVAr) Y

Single Channel Update


Market Change Request

MCR 0159 - Working Practice 0013Document the procedure to be used to terminate Meter Point Reference Numbers identified as duplicates

– Circulated to the market 14.02.08– No Feedback– Approval Requested


Next Steps

• Proposed Diary dates for IGG meetings in 2008:

– 03.04.2008– 15.05.2008– 26.06.2008– 07.08.2008– 18.09.2008– 30.10.2008– 11.12.2008– 22.01.2009

– Proposed dates are on Calendar of Events on RMDS website


Next Steps

• Propose to continue with conference call every two weeks – proposed dates for Q1 and Q2, 2008.

- 13.03.2008- 27.03.2008- 17.04.2008- 01.05.2008- 29.05.2008

• Call details have new contingency PIN No:– Number: 01-6647602 PIN : 77640 – Contingency number remains: 01-6647777 New PIN: 80490

• Upcoming Outage Saturday 1st March 9am until 10am– Hub database maintenance


Thank You

igg agenda – 29 th february 2008

Documents