igg agenda – 11 th april 2008

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

IGG Agenda – 11th April 2008

• Minutes from last IGG meeting 11.00 - 11.10• Review of Action Items 11.10 - 11.30• Schema Release 11.30 - 12.00• Recalculation of Estimates 12.00 - 12.15• CER Update 12.15 - 12.25• Gemserv Update 12.25 - 12.35• Market Operations Update 12.35 - 12.45• Proposal for applying the DUoS rules 12.45 - 13.00• Retail Market Design Service Update 13.00 - 13.15• Market Design Update 13.15 - 13.30• Next Steps 13.30 - 13.40


Minutes

Minutes from IGG meeting – 29th February 2008


IGG Action Items


IGG Action Items

Closed IGG Actions:

List issued in advance of meeting detailing IGG Actions to be closed

IGG Actions to be carried forward:

Feedback sought on list of IGG Actions carried forward


Update on Action Items

Action Item 108 (& Action Item 159)

Issue Data Storage and Archiving Document to Market Participants

– Issued on 10th April 2008



Action Item 108 (& Action Item 159)

Issue Data Storage and Archiving Document to Market Participants

– Issued on 10th April 2008



Action Item 278

RMDS to investigate why both suppliers are not currently being contacted as outlined in WP13

• Working Practice needs to be amended so that both suppliers are advised of duplicate MPRN scenario

• The current level of duplicate MPRNs is 2 to 3 per month

• One Supplier maintains if a duplicate MPRN is registered and then de-registered as a result of ESB Networks identifying the MPRN as a duplicate, the supplier will have incurred costs signing up that MPRN and there doesn’t appear to be a mechanism to recoup these costs.

• Feedback requested.

8

RMDSRMDSRMDSRMDS Retail Market Design Service www.rmdservice.com

Schema Release

Tony Carroll,ESB Networks

9


Recalculation of Estimates

Cormac Madden


Recalculation of Estimates• Existing

– Recalculation only where present less than previous– Only as far back as present ceases to be less than previous

• Proposed– Recalculation of all estimates, subject to a significance

threshold

– DUoS tariff change flag

Actual Reading 2Actual Reading 1

Estimates

A1 E1

Time

E2 E3 A2

Consumption History with Estimates



• Time:– No. of consecutive estimated periods– Set initially to 3


Estimates

A1 E1

Time

E2 E3 A2

Consumption History with EstimatesSignificance Thresholds:

1. Time

2. Consumption



• Consumption:– Level of kWh consumption for the last period

indicated by actual read– Set initially to 25% of AUF i.e. 3 months average.


Estimates

A1 E1

Time

E2 E3 A2

Consumption History with EstimatesSignificance Thresholds:

1. Time

2. Consumption


Recalculation of Estimates (contd.)

• Present status:– Based on current functionality

– Operational impact of increased message volumes: • Not thought to be an issue with thresholds in

place

• Next steps:• DR to be raised


CER Update


Gemserv Update


Market Operations Update

17


Proposal for applying the DUoS rules

Brendan O’Connor, Commercial Section, ESB Networks

18


Retail Electricity Market Issues Update

Cormac Madden, RMDS


Market Issues Update

Issues Raised since last IGG

• Market Issue No. 153 - Customer special needs not populated on 105 message

• Market Issue No. 154 - The current service order does not take into account where a customer requests night/day meter but is also installing night storage heating. This often results in two calls to premises


Market Issues Update

Issues Closed since last IGG

• Market Issue No. 135 - Technical Contact Name and Phone number sent on CoS request without Tech contact address causes 105 to issue with blank street field in Tech Contact Address

21


Retail Market Design Service Update

C. Madden, RMDS


RMDS Update

• Report on Service Objectives• Message Reconciliation process• Revised Outage Notification process



Key Service Objectives

Area Activity Measure Objective Actual (2007)

Customer Surveys No. per year 1 1

Process Design releases No. of significant errors 0 5

Information released to website Time to release from receipt <1 day 80% approx.

Change Control Circulation of documents (days before meeting)

5100%

Query Helpline Response time to Design Queries 5 95% approx

Market Meetings Agendas (days before meeting) 5 100%

Minutes (days after meeting) 5 22%

Resolution or escalation of IGG Actions (weeks)

12 80% approx

Change Control Circulation of documents (days before meeting)

5 100%

New Release of design documents (No. of significant errors)

0 2

System planned outages Notice of part weekend outage (days) 5 50% approx



Other Service Objectives

Area Activity Measure Objective Actual

Process Design releases No. of non-significant errors < 5 5+

Response time to queries requiring input from 3rd parties (e.g. ESBN)

10

95% approx

Market Meetings Working documents (days before meeting)

2

100%

Presentations (days before meeting)

2

0%

Final presentations (days after meeting)

2

100%

Change Control New Release of design documents (no. of typographical errors)

< 5

< 5


RMDS Service Objectives

• IGG Agendas (5 days before meeting)• IGG Change Control Documents (5 days)• IGG Working Documents (2 days before meeting)• IGG Presentations (2 days before meeting)• IGG Final Presentations (2 days after meeting)• IGG Minutes to be distributed (within 5 days)• IGG Conference Call Agenda (5 days before

Meeting)• IGG Conference Call Minutes (5 days after Meeting)• System Planned Outages (5 days notice)


RMDS Service Objectives

Objective Days

Quantity

Met

Agendas 5 8 100%

Change Control Documents

5 9 100%

Working Documents 2 7 71%

Presentations 2 8 0%

Final Presentations 2 8 100%

Minutes 5 9 22%

Conference Call Agenda 5 19 79%

Conference Call Minutes 5 19 95%

Overall 87 75%


Number of Action Items by Category


Total Number of Action Items


Number of Action Items Closed


Resolution or escalation of IGG Actions (within 12 weeks)

0

20

40

60

80

100

120

140

160

180

Late In Progress

Okay

Late

On Time

31


Message Reconciliation

Colm Gaffney, RMDS


Reconciliation Reports

• Missing Receipt Acknowledgements

• Issued to Hub but not transmitted (failed validation)

• Numbers of Messages received by the HUB Inbound from Suppliers and transmitted to CMS (for 24 hr period)

• Numbers of Messages received by the HUB Outbound from CMS and transmitted to Suppliers (for 24 hr period)

Central MarketSystem

Market Hub

MPCC Client

No RA

ValidationFailure

∑ Total

∑ Total


Reasons for message failures

• Message failed to be routed– Cause - no data or invalid data

• Message routed but did not pass the Routing Schema– Cause – incorrect Port or Topic in the routing table

• Message failed to be converted– Cause – invalid data type

• Message failed validation• Message failed to be packaged• Message failed to be transmitted• Discrepancies between CMS counts and HUB

counts• Messages delayed due to outages


Action Item 187

Message Reconciliation CMS to HUBR

MD

SE

SB

Net

wo

rks

Par

tici

pan

tM

RS

OH

UB

Tea

m

MRSO identifymessages issued

by CMS

MRSO identifyReceipt

Acknowledgementsfrom the HUB

Discrepanciesare identified inconjunction withthe Hub Team

Messagediscrepanciesare confirmed

emailtelephone

Participantsinformed of any

issues

HUBTeam

HUBDB

MRSO

MessageResendsrequested

Request torebuild and

resend Messages

CentralMarket System

Messagerebuilt and

resent to CMS

RMDS informparticipants of

unplanned outages,delays or anomalies

RMDS Inbox

YESEscalationrequired

NO


Action Item 187

Message Reconciliation and Resending Process HUB to MPCC

Mar

ket

Par

tici

pan

tR

MD

SH

UB

Tea

mM

RS

OE

SB

Net

wo

rks

YES

NO

MarketMessageReports

Request torebuild and

resendMessages

MessagesTally

Participants checktheir systems to seeif the messages sent

were received

ReconciliationQuery / resendrequest sent toRMDS Inbox

Participants receiveresent message /query response

RMDS route thequery to the

relevant party

HUBDB

RMDS Inbox

END

HUBTeam

RMDSrespond to

query / resend

ESBNetworks

SAP ISU(CMS)

MRSO

602Reconciliation

Market Message

602 Market messagerun (for 3 am until 3am) and issued to

Participants

HUB/ 602Reconciliation

queries

Resend/Query

Request torebuild andresend 341Messages

Message queryresend

341resend

36


Outage Notification Process

Colm Gaffney, RMDS


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

Market System Outage NotificationE

SB

Net

wor

ksR

MD

SM

arke

tP

artic

ipan

tsIT

Ser

vice

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

Outage takesplace

Outage overand services

resumed

Inform ESB Networksthat Outage has

completed and serviceshave been restored

ESB Networksinforms

stakeholders ofOutage completion

RMDS informsparticipants of

Outage completion

Participantsreceive notification

NOTE an outage may complete by Saturday morning. Operationalsystems can run as normal after this outage completes. In thiscase it will be Monday morning at the earliest that RMDS canformally inform participants of an outage completion.

38


Discussion Requests & Market Change Requests

Cormac Madden, RMDS


Discussion Request

MCR 063 • Data Fields Published for QH Import Report

• Data Fields Published for NQH Import Report

MPRN Supplier Unit DUoS Group MCC

10000055555 SU_427000 DG7 MCC10

MPRN Supplier Unit DUoS Group MCC Load Factor

10000002321 SU_424000 DG6 MCC06 LF3

Profile Description Role Role Description Usage Factor AUF/EUF Flag

STD Prof 8 Day 00D 00 Standard day 4,523.78 A


Discussion Request

MCR 0154• A new 342 market message for export

channel data only• The 341 market message is to be modified to

exclude the Export data.• A new Version Number field will be added to

the 341 and 342 Market Message at the ‘MPRN Level Information’ segment.

• 341 and 342 market messages are to be prevented form issuing with single channel data.

• The Channel Status that currently resides at the Channel Level details should be moved up to the MPRN level and renamed ‘Alert Flag’.

341 MPRNLevel

Information

MPRN

Version Number

Optional

Read Date

TransformerLoss Fact...

Optional

GeneratorMPID

Mandatory

Mandatory

Optional

GeneratorUnit ID

Alert Flag (oldChannel Status)

Mandatory

Mandatory


Market Change Request

MCR 0160 - Working Practice 0016 - Document the procedure to be used for like-to-like QH meter replacement

• Issued to the market on 04.04.08

• Approval requested


Draft Discussion Request

Action Item 212

Publish multiplier value associated with an MPRN on the MP Extranet


Next Steps

• Proposed Diary dates for IGG meetings in 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:

- 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


Thank You