1. ESB Networks Market Release Meeting of the IGG, May 28th 2009

2. ESB Networks Market Release : Agenda
1. Release Update
2. Next Steps
3. TAG Implications

3. ESB Networks Market Release : 1. Release Update
Tuesday 16th June
We will formally confirm the content of the November 2009 release on Tuesday 16th June. Dates will also be proposed for the November go-live and xml schema release.
Provisionally included will be the content of the May 2010 release, with formal confirmation in September 2009
Updated proposals to the content are covered in later slides
Summary of the changes to the proposed content of the Releases:
Vulnerable Customers
1 MCR moved to May 2010 from November 2009 viz MCR0169 – revised content
1 MCR provisionally removed from May 2010 viz MCR0152
And want to discuss separately MCR0170 – see next slide

4. ESB Networks Market Release : 1. Release Update – MCR0170
Action item 476 : to investigate the potential to implement MCR170 earlier than Nov.
A key element of the investigation has been on how to ensure that there is a sustainable level of
access to a new webservice for all who require it, as well as protecting the availability and
performance of the Market Systems. As previously stated this was a non-trivial exercise.
Various options were examined and the outcomes of those led us to consider a number of
solutions. None of them is a Silver Bullet.
Key findings
* We believe that the volumes described in the MCR at 3000 per day are low. If actual
volumes are greater, or the flow is significantly large at times when there is a high
processing requirement on the system, then the Webservice solution may not deliver to your
expectations.
* An option considered was to build new Market Messages. As you are aware the market
message design means that there is a non-instantaneous response. This would have been
for a November 2009 timeframe
* The solution we propose is to support , from now, the testing by Suppliers who want to
build their own application to extract data from the existing Extranet application.
And ask that RMDS/Gemserv would inform what assurance would be needed
Please be aware that with this solution a technical limit can continue to be reached and is indicated by the ‘no data found’ message.
Unless there is a serious objection to this solution then we propose to go ahead along
these lines.

5. ESB Networks Market Release : 1. Release Update – MCR0174
MCR0174 Allow incomplete set of reads for multiple meters to be accepted by ESBN
We have been asked to consider if this could be included in the November 2009 release
The response is that this could not be added into the November 2009 release due to the volume of testing required.

6. MCR0170 New MP Extranet Web Service - earlier discussion refers
ESB Networks Market Release : 1. Content of November 2009 , May Releases : Updated Proposals
The proposed content of the November 2009 release is
MCR New MP Extranet Web Service - earlier discussion refers
MCR Versioning of 341 message and new 342 MM for QH Export *
MCR MM sent when QH Meter removed
MCR Recalculation of Consumption estimates v *
MCR Delivery of 106d message to EirGrid
The proposed content of the May 2010 Release is
MCR0169 # Addition of Vulnerable customer flag to 102 MM Ver *
MCR0162 @ SOLR Process *
MCR Increase the threshold for connection agreement in COS
MCR Include Meter Multiplier on Extranet
MCR Proposal to add Acceptance/Completion/Cancellation * message to Meter Works design (new 131 MM)
MCR Vulnerable Customers Phase *
# Revised Content – MCR moved into May 2010 from November 2009
@ SOLR : many of the components will be delivered in November 2009
+ MCR0171 : this will be included in the May 2010 release
- MCR0152 Vulnerable Customers Phase 3: ESBN to formally discuss with CER
* Requires schema changes

7. ESB Networks Market Release : Agenda
1. Release Update
2. Next Steps
3. TAG Implications

8. ESB Networks Market Release : 2. Next Steps
Tuesday 16th June we will confirm the contents of the November 2009 release
including proposed dates for the November go-live and xml schema release.
in September 2009 we will confirm the contents of the May 2010 release.
finally, please be aware that until confirmed there may be changes

9. ESB Networks Market Release : Agenda
1. Release Update
2. Next Steps
3. TAG Implications

10. ESB Networks Market Release : 3. TAG Implications: Updated Proposals
Summary of the changes to the proposed xml element of the Releases:
SOLR MCR0162 xml changes to be included in November 2009 ,
1 new Objection Reason Code for lock down period
1 extra data value in existing field viz new Read Arrangement code
1 revised MCR provisionally moved to May 2010 from November 2009 viz MCR0169
The revised content means that provisionally, subject to agreement on the content
of the MCR, have an extra 4 MM changes viz Outbound: 010, 013, 016, 017
MCR0152 provisionally removed from May 2010 – this had changes to 8 MMs viz
Outbound: 010, 013, 016, 017 Inbound: 114, 116, 101, 105

11. ESB Networks Market Release : 3. TAG Implications: Updated Proposals
Scope of Changes to XML Schema
Nov 2009 : MCRs require changes to the schema
1 new Market Message viz MM MCR0154
2 existing messages are being changed viz
MCR0154
add new field to MM MCR0165
SOLR MCR0162
1 new Objection Reason Code for lock down period
1 extra data value in existing field viz new Read Arrangement code
May 2010 : MCRs require changes to the schema
1 new Market Message (131) MCR0171
5 existing messages are being changed, provisionally included MCR0169
Outbound: 010, 013, 016, 017, 102

12. ESB Networks Market Release :
Thank You