ESB Networks AIP Programme Business Design Update to

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

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 1

ESB Networks AIP Programme : Design Documentation and where we are ESB Networks draft Discussion Document 'Impact of AIP on ROI Retail Market’ ü 1 st June - Draft ver 0. 1 ü 7 th June - Special IGG ü 21 st June - Draft ver 0. 2 Key Issues in Appendix 8 discussed at todays IGG Plans for progressing the Design with the IGG 29 th June - Responses from Market Participants due back 4 th July - SIMDRACS Co-Ordinator clarifications/decisions 6 th July - Draft ver 0. 3 13 th July - Special IGG - looking to come to conclusions on issues and to arrive at agreement on the design, apart from outstanding items. 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 - 2 Options 3. Plans to Progress the Design 3

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

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

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

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

ESB Networks AIP Programme : Issues 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. 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 Option 2 Implement a one to many relationship between Supplier ID and Supplier Unit 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 8

ESB Networks AIP Programme : Option 2 Messages Involved: 010 Registration request 101 New Connection Registration Acceptance 015 101 P New Connection Provisional Acceptance 101 R New Registration Rejection 102 N Change of Supplier – Default Registration Notification 102 R Change of Supplier Registration Rejection 115 Change of SSAC request (changes to “Change of Supplier Unit / SSAC request”) Change of Supply Registration Acceptance 102 P Change of Supplier Provisional Acceptance 105 Change of SSAC Confirmation Change of Supplier Confirmation 115 R Change of SSAC Rejection 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 5 xx 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 9

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 10

ESB Networks AIP Programme : Issue 4 : Data Definitions 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 : Aggregation Messages Example : Initial Aggregation …. . Option 1 D A A, C 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 13 Summated per registered Supplier unit

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

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

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 16

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

ESB Networks AIP Programme : 3. Plans to progress the Design Contacts Feedback/Queries marked for Attention of ESB Networks AIP Programme & sent to RMDS@esb. ie Theresa ONeill @ 6765831 ext 47442 18