1. ESB Networks AIP Programme. Business Design
ESB Networks AIP Programme Business Design Update to TAG, June 22nd 2006

2. ESB Networks AIP Programme :
Agenda
1. Design Documentation and where we are
2. Key Items to be aware of
Data Model
Data Definitions
Market Messages
3. Plans to Progress the Design

3. ESB Networks AIP Programme : Design Documentation and where we are
ESB Networks draft Discussion Document 'Impact of AIP on ROI Retail Market’
1st June Draft ver 0.1
7th June Special IGG
21st June Draft ver 0.2
Key Issues in Appendix 8 discussed at todays IGG
Plans for progressing the Design with the IGG
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.

4. ESB Networks AIP Programme :
Agenda
1. Design Documentation and where we are
2. Key Items to be aware of
Data Model
Data Definitions
Market Messages - 2 Options
3. Plans to Progress the Design

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

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

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

8. Networks AIP Programme : HLD : To-Be Data Model for Data Aggregation with Multiple Supplier Units
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

9. ESB Networks AIP Programme : Issues
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

10. ESB Networks AIP Programme : 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

11. ESB Networks AIP Programme :
Agenda
1. Design Documentation and where we are
2. Key Items to be aware of
Data Model
Data Definitions
Market Messages - 2 Options
3. Plans to Progress the Design

12. ESB Networks AIP Programme : Issue 4 : Data Definitions

13. ESB Networks AIP Programme :
Agenda
1. Design Documentation and where we are
2. Key Items to be aware of
Data Model
Data Definitions
Market Messages - 2 Options
3. Plans to Progress the Design

14. 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

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

16. 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

17. ESB Networks AIP Programme :
Agenda
1. Design Documentation and where we are
2. Key Items to be aware of
Data Model
Data Definitions
Market Messages - 2 Options
3. Plans to Progress the Design

18. ESB Networks AIP Programme : 3. 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 : 3. Plans to progress the Design
Contacts
Feedback/Queries marked for Attention of ESB Networks AIP Programme & sent to
Theresa ext 47442