1. ESB Networks AIP Programme Update to IGG, June 22nd 2006

2. ESB Networks AIP Programme :
Agenda
1. Recap on Process and where we are
Review of Key Issues in Appendix 8
3. Plans for progressing the Design with the IGG

3. ESB Networks AIP Programme : Recap on Design Process
The definition of wholesale market requirements is managed by the Regulatory Authorities through the
SIMDRACS forum and the SEM.
The impacts included in the ESB Networks documentation have been arrived at through
interpretation of various SIMDRACS and SEM documentation
the SIMDRACS workshop on non-SEM Participant trading held on 12 April 2006
various clarification meetings convened by the SIMDRACS Project Co-Ordinator
and involving SMO and MRSO.
Feedback received to date from some Market Participants
ESB Networks are awaiting the detailed requirements of the SMO baseline design.
In advance of these being available, the SIMDRACS Co-Ordinator has where appropriate
provided ESB Networks with working assumptions to allow the ESB Networks Design work
to proceed.
There are planned to be Industry Consultations through the Rules Liaison Group forum
and the outcome from these could affect currently understood requirements.
NB. The ROI Retail Market design for SEM is not yet baselined

4. ESB Networks AIP Programme : Appendix 8
ESB Networks Draft Discussion Document 'Impact of AIP on ROI Retail Market’ has been
updated since last meeting to version 0.2
2. This contains
an up-to-date list of all Issues – Appendix 8.
Responses from two Market Participants
Working assumptions have where appropriate been provided by the SIMDRACS Co-Ordinator.
The intention is to discuss Key Issues in Appendix 8 at today’s IGG

5. ESB Networks AIP Programme : Appendix 8 – Key Issues
A : Working Assumptions
For ‘A’ items, ESB Networks is looking for agreement of the IGG that the assumptions that have been documented in Appendix 8 are a reasonable basis on which to proceed
B : Retail /Wholesale Issue
For 'B' items, ESB Networks is looking for input before the issue can be resolved and propose the following timeline
Market Participants to respond , as appropriate, by 29th June
SIMDRACS Co-Ordinator to provide clarifications/decisions by 4th July
ESB Networks would issue an updated version of this document to Market Participants on 6th July
and that there would be a Special IGG on 13th July 2006 where ESB Networks would be looking to come to
conclusions on issues and to arrive at agreement on the design, apart from outstanding items.
C : No Date Agreed , a Future Item
There are outstanding items, some of which are required more quickly than others but for which we do not have an agreed date for resolving.
A plan will be agreed with SIMDRACS co-ordinator and included in the next updated version of the documentation.

6. ESB Networks AIP Programme : Plans to progress the Design
1st June Draft ver 0.1
7th June Special IGG
21st June Draft ver 0.2
22nd June IGG today to discuss Appendix 8 – Key Issues
29th June Responses from Market Participants due back
4th July SIMDRACS Co-Ordinator clarifications/decisions
6th July Draft ver 0.3
13th July Special IGG - looking to come to conclusions on issues
and to arrive at agreement on the design, apart from
outstanding items.

7. ESB Networks AIP Programme :
ISSUES

8. ESB Networks AIP Programme : Issue 3
Requirements of Meter Data providers to accommodate multiple Supplier/SSACs for a single Supplier Unit to be clarified by CER/SIMDRACS.

9. ESB Networks AIP Programme : HLD: As-Is Data Model for Data Aggregation

10. ESB Networks AIP Programme : HLD : To-Be Data Model for Data Aggregation with Single Supplier Unit Option 1

11. ESB Networks AIP Programme : HLD : To-Be Data Model for Data Aggregation with Multiple Supplier Units Option 2
To-Be
Supplier ID
Data
Supplier Unit
Supplier Unit
SSAC
SSAC
SSAC
SSAC
Green
Brown
Green
Brown QH
NQH QH
NQH QH
NQH QH
NQH
Initial Aggregation
Messages
525
521
525
521 QH
NQH QH
NQH
to Suppliers
Impor t
Import
Import
Import
& NQH also to TSO
Initial Aggregation
520
526
data for SMO and
SMO
Supplier
Supplier
Suppliers
Unit Data
Unit Data
copy to Suppliers

12. ESB Networks AIP Programme : Issue 3
Requirements of Meter Data providers to accommodate multiple Supplier/SSACs for a single Supplier Unit to be clarified by CER/SIMDRACS.
Option 1
Establish a one to one relationship between Supplier ID and Supplier Unit and use this mapping for summing by SSAC per Supplier Unit and communication with the SMO.
Retail market MMs remain the same.
Option 2
Implement a one to many relationship between Supplier ID and Supplier Unit
Pros
No material change to the data structure for aggregation
Significantly minimises development effort and complexity for Market Participants
Easing of transitional arrangements for dual operation over 13 month ‘cutover’
Cons
New data mapping for ESB Networks
Exceptional handling for Trading Site Supplier
Unit - mapped per MPRN
Pros
Allows multiple Supplier Units per Supplier
Cons
Significant effort to implement for ESB Networks
Inclusion of Supplier Unit in 12 MMs (follows)
New market processes for Change of Supplier Unit
Changes to internal ESB Networks processing to handle Supply Unit rather than Supplier/SSAC

13. ESB Networks AIP Programme : Issue 3 - Option 2
Messages Involved:
Change of SSAC Rejection
115R
Change of SSAC Confirmation
115
Change of Supplier Confirmation
105
Change of Supplier Registration Rejection
102R
Change of Supplier Provisional Acceptance
102P
Change of Supplier – Default Registration Notification
102N
Change of Supply Registration Acceptance
102
New Registration Rejection
101R
New Connection Provisional Acceptance
101P
New Connection Registration Acceptance
101
Change of SSAC request (changes to “Change of Supplier Unit / SSAC request”)
015
Registration request
010
ESB Networks Impact = Significant Effort
Additionally Required Functionality
A new data item must be defined to store the Supplier Unit identifier
All messages where the SSAC is currently included (except current 5xx messages) will now also need to include the Supplier Unit identifier.
New rules and processing surrounding Changes to Supplier Unit must be developed.
Changes to internal SAP processing to handle Supply Unit rather than Supplier/SSAC

14. ESB Networks AIP Programme : Issue 28
Composite Aggregations Messages to be provided to Market Participants instead of Individual messages per aggregation process
2 Options presented for Discussion

15. ESB Networks AIP Programme : Aggregation Messages Example : Initial Aggregation …..Option 1D A
A,C
Summated per registered Supplier unit
Summated per registered Supplier unit
B,C,
B,D
[A] Messages to be similar to existing 501,505,504
[B] Messages to be in SMO format
[C] New Messages to support Non-Participant Generators
[D] New Messages for SMO/ New Message Format/ QH+NQH,30 minutes,MWh,Long/Short Day
B,D

16. ESB Networks AIP Programme : Aggregation Messages Example : Initial Aggregation …..Option 2

17. ESB Networks AIP Programme : Issue 28 : Market Messages
Composite Aggregations Messages to be provided to Market Participants instead of Individual messages per aggregation process
Option 2
ESB Networks would send 8 Market Messages to each Market Participant per settlement day. There would be 2 formats, each would have 4 messages per settlement day.
5xx MM based upon the 5x0 data to SMO
5yy MM with lower level detail
Each MM would contain within it an indicator as to which Aggregation it relates to.
Option 1
ESB Networks would send separate market messages as per the earlier slide.
Each MM number would indicate which Aggregation it relates to.
Pros
Analysis confirms MM size within hub ‘ ‘bandwidth’
Ease of identification and search
Allows for specific market message to be suppressed should a MP not require it
Cons
Overhead to maintain multiple MMs.
Pros
Minimises maintenance overhead for Market Participants
Cons
Larger MM size for the Hub - 5yy message
Could cause bottlenecks in development and maintenance
somewhat more effort required to identify and search for data

18. ESB Networks AIP Programme : Plans to progress the Design
1st June Draft ver 0.1
7th June Special IGG
21st June Draft ver 0.2
22nd June IGG today to discuss Appendix 8 – Key Issues
29th June Responses from Market Participants due back
4th July SIMDRACS Co-Ordinator clarifications/decisions
6th July Draft ver 0.3
13th July Special IGG - looking to come to conclusions on issues
and to arrive at agreement on the design, apart from
outstanding items.

19. ESB Networks AIP Programme :
Thank You