ESB Networks Market Release Meeting of the IGG, 20 th August 2009

1 ESB Networks Market Release : Timelines – November 2009 Release Recap IGG March 5 th 2009 – Proposed Timeline and MCR content for November 09 and May 2010 release. Comments were requested and of those that were received, none indicated any issues with the timelines. April 16 th 2009 IGG – we confirmed that we are planning to proceed with the timelines of November 2009 and May 2010 in which to release packages of work June 16 th Dates for GoLive and Schema release, and the MCRs for the November 2009 release were confirmed Recently there have been comments which indicate that Suppliers may need extra development time. We have been planning the implementation of the November 2009 Market Release over the weekend of Friday 27th to Sunday 29th November Will Market Participants be ready to go ahead with the November Market Release?

2 ESB Networks Market Release : Timelines – May 2010 Release Future Release We have recently received comments that Suppliers are looking to have the Schema release scheduled three months in advance of IPT testing instead of go-live. In light of this, we will be taking another look at the timelines that were previously proposed for the May 2010 release and review the outcome with you at the next IGG in October. In addition, the MCR content which was previously planned to be confirmed in mid-September is now proposed to be covered at that IGG.

3 ESB Networks Market Release : November 2009 Release – MCR content The planned MCR content of the November 2009 release is MCR0154 Versioning of 341 message and new 342 MM for QH Export Ver 2.0 MCR MM sent when QH Meter removed Ver 1.0 MCR0165 Recalculation of Consumption estimates Ver 4.0 * MCR0167 Delivery of 106d message to EirGrid Ver 1.0 MCR0162 SOLR Ver 2.0 Comment see 16 th June 2009 for details * ver4.0 of MCR 0165 removes references to the 300mm

4 ESB Networks Market Release : Changes to the XML Schema for November Note that details are subject to confirmation at the release of the schema on 1 st September DataDefinitions.xsd 1.'ChannelStatus' attribute name changed to 'AlertFlag' 2.'ReadingReplacementVersionNumber' attribute added 3. 'DebitReEst' attribute added 4. 'LOC' value added to the 'RejectReasonCode' list of values 5.'DR' value added to the 'COS_ReadArrangementCode' list of values ieXML.xsd 1. added the 342 message: 2.added the 342 message reference: 3.changed the 341 message reference name MIM305.xsd 1.Added the optional 'DebitReEst' field to the MPRN level MIM341.xsd 1. Removed the 'ChannelStatus' field at ChannelInfo level 2.Added the mandatory 'AlertFlag' field at MPRN level 3. Added the mandatory 'ReadingReplacementVersionNumber' field at MPRN level 4.Changed the message name to 'MIM341_ImportQHMeterDailyReadings' MIM342.xsd Brand new market message - same fields as the MIM341 message - message name is 'MIM342_ExportQHMeterDailyReadings' VersionNumber All messages updated to version (i.e version=" ")

5 ESB Networks Market Release : Thank You