1. ESB Networks AIP Programme Meeting of the IGG, December 14th 2006

2. ESB Networks AIP Programme : Agenda
1. Review of where we are
2. Issues
3. MCRs
4. MCR063
5. Next Steps
6. TAG Implications

3. ESB Networks AIP Programme : 1. Review of where we are
Before the Special IGG of 7th June 2006, a first draft document ‘Impact of AIP on ROI Retail Market’ issued from ESB Networks AIP programme. This set out the impacts for the Irish Retail Market that had at that time been identified by ESB Networks as a result of the AIP, in so far as the requirements were known.
Before the IGG of the 22nd June 2006, all key design issues were included in Appendix 8 in the second draft of the discussion document. At the IGG on the 22nd June there was a walk through of each of the issues in that document.
Before the IGG of the 13th July , updated Appendix 8 issued on 7th July , ver 0.3, containing
feedback from Market Participants, SIMDRACS Co-Ordinator, new requirements that were received from Regulatory Authority, and review of Design Issues by ESB Networks.
Following the IGG of the 13th July, four Market Participants responded to specific queries
raised at that IGG.
At the IGG of August 10, the responses were debated.
In early August , CER/SIMDRACS gave approval to proceed with the detailed design based
on what had been discussed to date with the IGG.
At the IGG of 21st September there was a recap of the high level design for AIP and an update on issues.
On 7th October draft ver 0.4 issued, followed on 13th October by version 0.41 which had the marked-up changes of ver 0.4 removed. This document was reviewed at the Special IGG on 16th October. Option 3 of the Message Model was presented and all Market participants were asked to respond by 19th Oct.
MCRs issued in 3 batches over 24th,25th and 26th October. All Market participants responded by 26th October to Option 3 : 4 in favour, 3 not. Option 3 of the Message Model was incorporated into these MCRs.

4. ESB Networks AIP Programme : 1. Review of where we are
At the IGG of 1st November, draft ver 1.0 MCRs and issues were discussed. Retail Market Participant Comments were fed back and baselined ver 1.1 MCRs were issued on 16th November.
On 6th December draft ver 0.5 issued having been updated with the outcome of the discussions from the Special IGG on the 16th October and the IGG on the 1st November. It summarises the contents of the
ver 1.1 MCRs.

5. ESB Networks AIP Programme : 1. Review of where we are……. contd
18th May Introduction
1st June Draft ver 0.1 ‘Impact of AIP on ROI Retail Market’ issued to IGG
7th June Special IGG
21st June Draft ver 0.2 ‘Impact of AIP on ROI Retail Market’ issued to IGG
22nd June IGG discussion on Appendix 8 – Key Issues
- TAG discussion on Key Issues
29th June Responses from Market Participants
4th July SIMDRACS Co-Ordinator clarifications/decisions
7th July Draft ver 0.3 [Appendix 8] ‘Impact of AIP on ROI Retail Market’ issued
13th July Special IGG
10th Aug Update to IGG
21st Sept Update to IGG
6th October - Draft ver 0.4 ‘Impact of AIP on ROI Retail Market’ issued
13th October- Draft ver 0.41 ‘Impact of AIP on ROI Retail Market’ issued

6. ESB Networks AIP Programme : 1. Review of where we are……. contd
16th October Special IGG - Draft ver 0.41 ‘Impact of AIP on ROI Retail Market’
24th,25th, 26th October - MCRs issued in 3 batches
1st November IGG review of MCRs, ver 1.0
14th November Comments/Queries on MCRs ver 1.0 issued
16th November ver 1.1 of MCRs issued
6th December Draft ver 0.5 ‘Impact of AIP on ROI Retail Market’ issued

7. ESB Networks AIP Programme : 1. Review of where we are……. contd
As noted at the IGG on 1st November,
As work progresses on the following items, further Discussion Documentation will issue and be progressed via the IGG structures.
A. These are items which are planned to be progressed in detail later,
Cutover requirements
4 month Market Trials
B. These are items which are not in scope of SIMDRACS and could potentially have impacts,
as yet currently unknown
Other CER workstreams including TSO Readiness
C. These are items which are not planned for Day1 and are not expected to impact Market
Participants for go-live, but ESB Networks need to consider from a planning perspective
for Day2
Requirements for Global Aggregation
Bulk Supply Metering

8. ESB Networks AIP Programme : Agenda
1. Review of where we are
2. Issues
3. MCRs
4. MCR063
5. Next Steps
6. TAG Implications

9. ESB Networks AIP Programme : 2 Upate on Issues
SIMDRACS items
A. There remain a number of key outstanding items and we will formally bring proposals
to the IGG when the detailed requirements are known, viz.
Data Queries and AD Hoc Aggregations Issue 20
Material Differences Issue 18
Consumption Adjustments inside or outside the 13 months Issue 19
B In addition, the following issues are outstanding
Definition of Working days Issue 1
Future Use of SSAC Issue 2/A1
Calendar for Aggregation Issue 7
EirGrid method of validation,estimation,substitution Issue 23
C The following items are not expected to be needed for go-live of AIP
and Propose to close today
Microgeneration Issue 31

10. ESB Networks AIP Programme : 2 Upate on Issues ……. contd
SIMDRACS
D. Placeholders in MCRs
Metering Responsibilities - expect to be finalised for next IGG
Non Participant Generators and SOLR event - with SIMDRACS Co-Ordinator

11. ESB Networks AIP Programme : 2 Upate on Issues ……. contd
SIMDRACS
E. Non-Participant Generators:
1. The last day we noted that the MCRs 098,100,101,102,125 ver 1.0 had been
raised in advance of a final decision of the CER on CER 06/151.
Subsequently and before ver 1.1 of MCRs, the CER issued proposed decision document
CER 06/230, and no changes to MCRs were needed.
2. MCR125 contains the text ‘It is a Regulatory requirement that in the new manual
registration process for Non-Participant Generation, a Supplier must show that they
have historic demand that has been (in all Trading Periods) 20 times greater than the
maximum contracted output of all out-of-market generation contracted to that Supplier
Unit.
At the IGG of 1st November, Retail Market Participants were requested to respond with
comments on this Regulatory requirement.
One Market participant responded , commenting that they ‘will have up to 350 MW of
AER facilities outside the SEM pool and as such feels that a multiplier if 20 is too large.
Therefore we would suggest that the historic demand be set at 1.5 times maximum
contracted output if necessary.’ This has been passed to the SIMDRACS Co-Ordinator.

12. ESB Networks AIP Programme : 2 Upate on Issues ……. contd
SIMDRACS
F RA324
RA324 will not be implemented by SMO prior to go-live
impacts on a Small number of Trading sites with firm/non firm access calculations
Unique ASU will be needed where not a TSSU
Import data is Price-Effecting and is needed by SMO on 7 day week, calendar day
basis
RA324 Mitigations strategy developed by SIMDRACS co-ordinator and is being
discussed in the SIMDRACS forum - will present outcome at next IGG

13. ESB Networks AIP Programme : 2 Upate on Issues ……………….. contd
Cutover/Transition
The following issues will be covered in our Cut-over planning , and we expect to
cover them at the next IGG :
Transitional Arrangements for Non-Participant Generators Issue 22
Eirgrid requirements in respect of data after cutover Issue A3
Investigate if any Trans sites with MEC < 10 MW Issue A6

14. ESB Networks AIP Programme : Agenda
1. Review of where we are
2. Issues
3. MCRs
4. MCR063
5. Next Steps
6. TAG Implications

15. ESB Networks AIP Programme : 3. MCRs
MCRs ver 1.1 issued 16th November
3 MCRs were late additions based on feedback to ver 1.0 MCRs,
no comments or queries were received on these, and if you have any, let us know
viz
MCR128 : MPD 8 (1.1): Changes to Connection Characteristics.
MCR129 : MPD 8 (1.2): Non Participant Generator Replaces Export
Arrangements with Submetering.
MCR068[ver 3.0] : Amendments to 591 Market Message

16. ESB Networks AIP Programme : 3. Proposed Amendment to MCR123/WP012
WPO012 : To nominate / denominate a Supplier as a recipient of
Participant Generator messages 341, and 504, 504s,594 and 597
[MCR123]
Would like to discuss a proposed amendment to WP0012 so that
if a generator nominates a supplier to receive their messages then it must
be for all GUIDs that fall under that Generator ID and not just selective
GUIDs
The reason for this proposal is to simplify processing requirements.
Looking for feedback today, and propose , if IGG is agreeable,
to proceed to draft a ver 1.2 of this MCR
to issue this before Christmas
and for responses back by 11th January
and to report back to the January IGG

17. ESB Networks AIP Programme : Agenda
1. Review of where we are
2. Issues
3. MCRs
4. MCR063
5. Next Steps
6. TAG Implications

18. ESB Networks AIP Programme : 4 MCR063
Recap on requirements in MCR063
Assess impact from a SEM perspective
Present an alternative proposal

19. Networks AIP Programme : 4. MCR063 - Requirements
MCR CR raised 08/08/2005 – revised November 3rd
Addition of New Market Message for the Provision of Reconciliation Data
In order to facilitate Market Participants carrying out various reconciliation & data tracking exercises e.g. reconciling MRSO provided settlement data, billing reconciliation and checking/tracking changes and updates to meter points.
A new Market Message (510 – Data Aggregation Reconciliation information) is requested to be sent daily to Suppliers
The message should cover the same period as is used for Aggregation run for a settlement day.
The message should provide control totals i.e not in QH format of 96 intervals per day.
An equivalent message should be updated and resent after each Re-Aggregation Run (analogous to the Re-Aggregation S messages)
The usage factors should be measured in MWh

20. Networks AIP Programme : 4. MCR063 - Requirements - NQH
A new Market Message (510 – Data Aggregation Reconciliation information) is requested to be sent daily to Suppliers providing the following information.
NQH/ Unmetered Data:
DUoS Group
MCC (Meter configuration code)
Count of MPRN per Usage Factor category (Estimated, Actual, Unmetered)
Total Consumption per Usage Factor category
Load Profile
Timeslot
Settlement day
SSAC
For NQH data the Structure of this new message is proposed to be as follows:
Level 1: Message Header Level 2: Settlement day/ SSAC Level 3: DUoS Group / MCC / Load Profile/ MPRN count per Usage Factor category Level 4: Total Consumption per Usage Factor category per timeslot (i.e. ∑ EUF per timeslot, ∑ AUF per timeslot, ∑ Unmetered per timeslot. (1:N)

21. Networks AIP Programme : 4. MCR063 - Requirements - NQH
For NQH
1. A count of MPRNs for a single settlement day,
broken down by UF type ‘category’ of Actual,est,unmetered
for every combination of
Derived Profile, MCC,Duos Group
and for every SSAC for that Supplier
Supplier/SSAC
Duos Group
MCC
Derived profile
Duos Group
MCC
Derived profile
…n Duos Group
MCC
Derived profile
EST UF
Count of MPRNs
Unmetered
Count of MPRNs
Actual UF
Count of MPRNs

22. Networks AIP Programme : 4. MCR063 - Requirements - NQH
For NQH
2. Total Consumption for a single settlement day,
broken down by timeslot for every UF type ‘category’ of Actual,est,unmetered
for every combination of
Load Profile, MCC,Duos Group
and for every SSAC for that Supplier
Supplier/SSAC
Duos Group
MCC
Derived profile
Duos Group
MCC
Derived profile
…n Duos Group
MCC
Derived profile
Actual UF
Count of MPRNs
EST UF
Count of MPRNs
Unmetered
Count of MPRNs
Day
Total Consumption
Night
Total Consumption
24hr
Total Consumption

23. Networks AIP Programme : 4. MCR063 - Requirements - QH
A new Market Message (510 – Data Aggregation Reconciliation information) is requested to be sent daily to Suppliers providing the following information
QH Data:
DUoS Group
Count of MPRN
MCC (Meter configuration code)
Settlement day
SSAC
For QH data the Structure of this new message is proposed to be as follows:
Level 1: Message Header
Level 2: Settlement day/ SSAC
Level 3: DUoS Group/ MPRN count/ MCC

24. Networks AIP Programme : 4. MCR063 - Requirements - QH
For QH
1. A count of MPRNs for a single settlement day,
for every combination of
MCC,Duos Group
and for every SSAC for that Supplier
Supplier/SSAC
Duos Group
MCC
Count of MPRNs
Duos Group
MCC
Count of MPRNs
…n Duos Group
MCC
Count of MPRNs

25. Networks AIP Programme : 4. MCR063 - would mean for AIP
From each of 4 daily aggregations viz Indicative, Initial, RA1, RA2
2 new aggregation messages, one NQH and the other QH
These would be for a particular Settlement Day
And would include Supplier Unit

26. Networks AIP Programme : 4. MCR063 - would mean for AIP MCR063.contd
A number of Issues have been identified with provision of this MCR:
Because of the SEM , we are moving from one to four daily aggregations
The requirements of MCR063 would mean that a separate aggregation would be needed to
provide the data in different granularity than that required by SMO
This is an additional processing overhead, and there is a concern that it could impact
on the performance of the core aggregations needed for SEM, in tight timeframes
In Addition
the input file to DA does not identify whether a Usage Factor is an Actual or an Estimate
the standard input files to aggregation would need to be amended to include the following
fields
Duos Group
MCC
STD Profile

27. Networks AIP Programme : 4. MCR063 - Alternative Proposal
An alternative is being proposed, viz
The provision of a Report containing control information, based on the
aggregation results for a specific Settlement Day and a Specific Settlement
Run[Indicative,Initial,RA1,RA2] - see next slides for details
Report to be provided by MRSO at the request of a Supplier. Note that this report
would need to be scheduled to run at a time that is not in conflict with the live
production schedule
Output format will be investigated, will not be a new message
Because of the costs involved, the frequency and costs of producing the reports
will be discussed as an MRSO item at future IGGs
If the proposals are acceptable then our intention is to include this as part of ESB
Networks AIP Programme, but timeline for delivery cannot be guaranteed before
go-live of SEM

28. Networks AIP Programme : 4. MCR063 - Alternative Proposal - NQH
Proposal is for the report to contain
for each combination of
Supplier/Supplier Unit/SSAC/Duos Group/MCC/Load Profile
a count of MPRNs that were included in the requested settlement run
Total Usage Factor by Time of Use
Note
will not breakdown MPRN counts of Usage Factor data between actual and
estimate
consumption by time of use will not be calculated
there could be cases where the data has changed since the settlement day has
been run, therefore there is no guarantee that data will be identical [NQH or QH]
and note that this is in addition to the new 591 messages which will have
counts of MPRN by DLF/Load profile combination
Total Usage Factor by Time of Use per DLF/Load profile combination

29. Networks AIP Programme : 4. MCR063 - Alternative Proposal - QH
Proposal is for the report to contain
for each combination of
Supplier/Supplier Unit/SSAC/Duos Group/MCC
a count of MPRNs that were included in the requested settlement run

30. Networks AIP Programme : 4. MCR063 - Alternative Proposal
Looking for feedback today, and propose , if IGG is agreeable,
to proceed to draft a new MCR for this report
to issue this before Christmas
and for responses back by 11th January
and to report back to the January IGG

31. ESB Networks AIP Programme : Agenda
1. Review of where we are
2. Issues
3. MCRs
4. MCR063
5. Next Steps
6. TAG Implications

32. ESB Networks AIP Programme : 5. Next Steps
We are proceeding with the build based on the MCRs.
outstanding items will be reviewed at the January IGG
At the next IGG , we will be discussing
Cut-over
Data Conversion
Market Trials

33. ESB Networks AIP Programme : Agenda
1. Review of where we are
2. Issues
3. MCRs
4. MCR063
5. Next Steps
6. TAG Implications

34. ESB Networks AIP Programme : 6. TAG Implications
Version 6.0 of the XML schema is currently in development.
This is baselined in line with the agreed MCRs proposed for SEM,
with one additional code being added for Vulnerable Customer
Delivery.
Dates around the release of the XML Schema to Retail Market Participants
will be advised to the IGG at the end of January.
It is our intention to make the schema available as soon as
development and unit test is complete.
And this will be subject to change control.

35. ESB Networks AIP Programme : 6. TAG Implications……………..contd
Currently we are assuming there will be an IPT phase in Sept/Oct
but could be as early as June, depending on Market Trial Strategy
Following the Business Review on Market Trials with the IGG in January,
firm proposals will be drafted for discussion with both the IGG and the
TAG shortly afterwards

36. ESB Networks AIP Programme :
Thank You