Presentation is loading. Please wait.

Presentation is loading. Please wait.

ESB Networks AIP Programme Meeting of the IGG, November 1st 2006

Similar presentations


Presentation on theme: "ESB Networks AIP Programme Meeting of the IGG, November 1st 2006"— Presentation transcript:

1 ESB Networks AIP Programme Meeting of the IGG, November 1st 2006

2 ESB Networks AIP Programme : Agenda
1. Review of where we are 2. Purpose of Today’s meeting 3. Issues 4. MCRs 5. Next Steps

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

5 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

6 ESB Networks AIP Programme : Agenda
1. Review of where we are 2. Purpose of Today’s meeting 3. Issues 4. MCRs 5. Next Steps

7 ESB Networks AIP Programme : 2 Purpose of Today’s Meeting
The Agenda is to present the MCRs at today’s IGG We are looking for sign-off to the MCRs by Retail Market Participants by November 8th If Market Participants have any comments or queries that are preventing them from sign off on particular MCRs, we are asking for final comments or queries to be returned to us by 8th November Following this , we will issue a full set of queries that have been received and responses by 15th November. If needed, we will issue revised versions of MCRs to take account of these. With agreement of the CER , we plan to proceed with the build based on the MCRs, subject to any amendments as a result of queries received.

8 ESB Networks AIP Programme : 2 Purpose of Today’s Meeting …… contd
Update Since the Special IGG of 16th October, it has been clarified by the SIMDRACS Co-Ordinator that Directed Contracts annual/monthly report to CER - is within scope PSO Levy/ LBA Tariff - is not within scope As noted at the Special IGG on 16th October, there are 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 Material Differences Consumption Adjustments inside or outside the 13 months

9 ESB Networks AIP Programme : 2 Purpose of Today’s Meeting…....contd
Notes [1 of 3] The Wholesale Market baseline for Meter data providers has been agreed through the SIMDRACS forum, exceptions are documented below, and any changes could mean that MCRs could need to be changed. If so, any changes will be progressed through formal MCR change control process as previously documented in Draft ver 0.41 ‘Impact of AIP on ROI Retail’, there are two Change Requests that have been raised by SIMDRACS 2 CRs have been raised by SIMDRACS to SMO. There is a risk that if not accepted then ESB Networks would have to operate on a calendar day basis and to accommodate D+1 and D+3 requirements of SEM for Price Effecting data . 2 CRs have been raised by SIMDRACS to SMO. There is a risk that if not accepted it means that there would be another unit, called by the SMO a ‘Unique Associated Supplier Unit’, and that for this unit, Demand Data would have to be aggregated for the MPRNs registered with PES. Design is proceeding on the assumption that these CRs will be accepted and that there will not be a need for a ‘Unique Associated Supplier Unit. the Agreed Procedures have not been baselined by the BLG/TLG/RLG

10 ESB Networks AIP Programme : 2 Purpose of Today’s Meeting…....contd
Notes [2 of 3] Placeholders in MCRs The following MCRs contain placeholders. When finalised, revised versions of MCRs will be issued to the IGG for review and agreement.

11 ESB Networks AIP Programme : 2 Purpose of Today’s Meeting …....contd
Notes [3 of 3] Non-Participant Generators MCRs 098,100,101,102,125 have been raised in advance of a final decision of the CER on document CER 06/151. Should this decision mean that changes are needed to these MCRs, then we will issue revised versions to the IGG - note that it is considered to be unlikely.

12 ESB Networks AIP Programme : 2 Purpose of Today’s Meeting…….contd
As noted at the Special IGG on 16th October , 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 5 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

13 ESB Networks AIP Programme : Agenda
1. Review of where we are 2. Purpose of Today’s meeting 3. Update on Issues 4. MCRs 5. Next Steps

14 ESB Networks AIP Programme : 3. Update on Issues [1 of 5]
Updates since Draft Ver 0.41: Impact of AIP on ROI Retail Market Discussion Document: Since this document was discussed at the Special IGG on 16th October, these changes have been reflected in the MCRs: The SMO has confirmed the following approach for signing: 590, 596 and Demand will be signed as a Negative and both Generation and zeros will not be signed The Generator Unit ID will be 9 digits long and will be of format "GU_nnnnnn", where n is a numeric. The field Time Created within the 590, 596 and 597 messages is confirmed as Mandatory and will be to a precision of seconds A numeric field named Row has been added to the 590 message as a Mandatory field A numeric field named Reading Number has been added to the 590, 596 and 597 messages as a Mandatory field

15 were consolidated into one MCR and one MPD - 16 2.1 Data Aggregation.
ESB Networks AIP Programme : Update on Issues [2of 5] Option 3 - Messaging Selection of Market Messaging Option 3 As described at the Special IGG on October 16th 2006, this resulted in the consolidation of the 5xx series of market messages into a 59x series with the use of a Settlement Run Indicator contained within the body of the messages. A further result of this change was that the planned 4 Aggregation Process Flows were consolidated into one MCR and one MPD Data Aggregation. As a result , proposed MCRs 111, 113 and 114 were not required. A majority of Retail Market Participant’s views have supported this option. Accordingly, the MCRs have been drafted along these lines. As normal, this is still subject to discussion at the IGG and final decision by CER.

16 ESB Networks AIP Programme : 3. Update on Issues [3 of 5]
Updates to TSO requirements for Market Messages The TSO have requested receipt of the 591 and 595 market messages for Initial, Ad Hoc, M+4 and M+13 Re-Aggregations. This has been incorporated into the MCRs. The SEM IT have confirmed that Cancellations of Change of Supplier for an MPRN registered to a Trading Site should be rejected by the MRSO. This has been incorporated into the design documentation for MPD 3. In addition, MCR 118 for Extranet Guidance Notes refers to the addition of a Trading Site Flag which will be set when the MPRN is registered to a Trading Site and therefore sites registered against either Associated or Trading Site Supplier Units will be flagged. As described at the Special IGG on October 16th 2006, MCR 121 has been raised to request the future proofing of the Total Usage Factor field within the 501 and 591 market messages. [note that total count of MPRNs remains at 8 and will not be changed]

17 ESB Networks AIP Programme : 3. Update on Issues [4 of 5]
MCR063 The MCRs have issued without MCR063. Further work is needed to review the issues raised in MCR063. This will be done before the next IGG and findings will then be presented. Replacement of ‘15’ in the Settlement Interval field with a counter An action was taken at the Special IGG on 16th October to prepare draft version of a long day message containing a incremental counter to replace the Settlement Interval which currently always contains ‘15’ . A sample extract based on a 501 message is contained on the next slide. The following messages can be amended so that every Settlement Interval field in these messages is replaced with a sequential counter value. Retail Market Participant views are sought. All 591,595,594,598

18 ESB Networks AIP Programme : 3. Update on Issues [5 of 5]
Replacement of ‘15’ in the Settlement Interval field with a counter <?xml version="1.0" encoding="UTF-8" ?> - <!-- edited with XMLSPY v5 rel. 4 U ( by John Moloney (Electricity Supply Board) --> - <ieXMLDocument xmlns:xsi=" <MessageHeader MarketTimestamp=" T16:19: :00" MessageTypeCode="501" RecipientID="AAA" SenderID="DSO" TxRefNbr=" " VersionNumber=" " /> - <MIM501_EstimatedAggregatedSupplierNQHConsumption SSAC=”X" SettlementDate=" " SupplierMPID=”SXX"> <AggregatedConsumption AggregatedConsumption="11.41" IntervalPeriodTimestamp=" T00:00:00+01:00" LossAdjustedAggregatedConsumption="12.3" SettlementInterval="1" /> <AggregatedConsumption AggregatedConsumption="11.41" IntervalPeriodTimestamp=" T00:15:00+01:00" LossAdjustedAggregatedConsumption="12.3" SettlementInterval="2" /> <AggregatedConsumption AggregatedConsumption="12.94" IntervalPeriodTimestamp=" T00:30:00+01:00" LossAdjustedAggregatedConsumption="13.95" SettlementInterval="3" /> <AggregatedConsumption AggregatedConsumption="12.94" IntervalPeriodTimestamp=" T00:45:00+01:00" LossAdjustedAggregatedConsumption="13.95" SettlementInterval="4" /> <AggregatedConsumption AggregatedConsumption="15.24" IntervalPeriodTimestamp=" T01:00:00+01:00" LossAdjustedAggregatedConsumption="16.43" SettlementInterval="5" /> <AggregatedConsumption AggregatedConsumption="15.24" IntervalPeriodTimestamp=" T01:15:00+01:00" LossAdjustedAggregatedConsumption="16.43" SettlementInterval="6" /> <AggregatedConsumption AggregatedConsumption="8.94" IntervalPeriodTimestamp=" T01:30:00+01:00" LossAdjustedAggregatedConsumption="9.64" SettlementInterval="7" /> <AggregatedConsumption AggregatedConsumption="8.94" IntervalPeriodTimestamp=" T01:45:00+01:00" LossAdjustedAggregatedConsumption="9.64" SettlementInterval="8" /> <AggregatedConsumption AggregatedConsumption="8.81" IntervalPeriodTimestamp=" T01:00:00+00:00" LossAdjustedAggregatedConsumption="9.49" SettlementInterval="9" /> <AggregatedConsumption AggregatedConsumption="8.81" IntervalPeriodTimestamp=" T01:15:00+00:00" LossAdjustedAggregatedConsumption="9.49" SettlementInterval="10" /> <AggregatedConsumption AggregatedConsumption="8.24" IntervalPeriodTimestamp=" T01:30:00+00:00" LossAdjustedAggregatedConsumption="8.88" SettlementInterval="11" /> <AggregatedConsumption AggregatedConsumption="8.24" IntervalPeriodTimestamp=" T01:45:00+00:00" LossAdjustedAggregatedConsumption="8.88" SettlementInterval="12" /> <AggregatedConsumption AggregatedConsumption="7.66" IntervalPeriodTimestamp=" T02:00:00+00:00" LossAdjustedAggregatedConsumption="8.26" SettlementInterval="13" /> <AggregatedConsumption AggregatedConsumption="7.66" IntervalPeriodTimestamp=" T02:15:00+00:00" LossAdjustedAggregatedConsumption="8.26" SettlementInterval="14" /> ………………………………………... <AggregatedConsumption AggregatedConsumption="12.94" IntervalPeriodTimestamp=" T23:45:00+00:00" LossAdjustedAggregatedConsumption="13.95" SettlementInterval="100" />

19 ESB Networks AIP Programme : Agenda
1. Review of where we are 2. Purpose of Today’s meeting 3. Issues 4. MCRs 5. Next Steps

20 ESB Networks AIP Programme : 4. MCRs Data Aggregation

21 ESB Networks AIP Programme : 4. MCRs QH Data Processing

22 ESB Networks AIP Programme : 4. MCRs Generators

23 ESB Networks AIP Programme : 4. MCRs NQH Registration

24 ESB Networks AIP Programme : 4. MCRs QH Registration

25 ESB Networks AIP Programme : 4. MCRs Ancilliary Documents

26 ESB Networks AIP Programme : Agenda
1. Review of where we are 2. Purpose of Today’s meeting 3. Issues 4. MCRs 5. Next Steps

27 ESB Networks AIP Programme : 5. Next Steps
We are looking for sign-off to the MCRs by Retail Market Participants by November 8th If Market Participants have any comments or queries that are preventing them from sign off on particular MCRs, we are asking for final comments or queries to be returned to us by 8th November All Retail Market Participant are asked to comment on the replacement of all Settlement Interval fields in all 591,595,594,598 messages by Nov 8th Following this , we will issue a full set of queries that have been received and responses by 15th November. If needed, we will issue revised versions of MCRs to take account of these. With agreement of the CER , we plan to Baseline the MCRs at the 15th November, and proceed with the build based on them. We propose, with agreement of IGG and CER, to request that a meeting of the TAG would be convened in December outstanding items will be reviewed with the IGG as and when the information is available all subsequent changes will be progressed through formal MCR change control process Finally, an updated ver 0.5 of Impact of AIP on ROI Retail Market’ will issue on 24th November

28 ESB Networks AIP Programme :
Thank You


Download ppt "ESB Networks AIP Programme Meeting of the IGG, November 1st 2006"

Similar presentations


Ads by Google