BRD states the Allocation Confirmed at PN UNC on 04/12/12: the requirements as 1 26/11/2012 Closed Scaling Adjustment is calculated daily stated in the BRD are still Allocation Confirmation and applied to all sites within the LDZ. AUGE allocate values of. AUGE role will Reconciliation Scaling A percentage is applied to the the unidentified energy. change as a result of the new BRD Adjustment consumption of all sites within an LDZ arrangements as unidentified at Shipper portfolio level gas will be shared to all sites within an LDZ. 2 26/11/2012 Closed Issue Asset data 3 26/11/2012 Closed Question AQ & SOQ AQ 4 26/11/2012 Closed Proposal Read Validation 5 26/11/2012 Closed Proposal AQ Notification AQ 6 26/11/2012 Closed Proposal 7 26/11/2012 Closed Issue 8 26/11/2012 Closed Proposal Replacing reads Gas Nominations Replacing reads Meter readings will be validated by the GT however, the asset data is used to calculate consumptions. Quality of asset data held on the Supply Point Register is believed to be poor and where it is incorrect this will affect the quality of the reads being loaded or reject reads which are valid. Should there be validation to ensure the SOQ is never less than the AQ for Product 1 & 2 sites? Read validation to apply to final meter readings e.g. on meter removals as the read will trigger reconciliation & AQ review. The notification of the revised AQ at [D- 5] will be sent to the Registered Shipper and Shippers with a Confirmation that will go live (within 7 days). Agreed that actual reads will not be replaced before GFD+5 for Product 1 & 2 sites. Reads should also not be replaced after GFD+5. The D-7 default for gas nominations will not provide an incentive for Shippers to input their gas nominations. BRD states missing reads can be inserted however this only adjusts the energy between periods. Validation to be performed by Xoserve on the asset data received. If agreed this validation could apply at Confirmation stage. However, for AQ review may need to just flag if AQ is less than SOQ. Consumptions adjustments should be used to replace the consumption for a day or a period. By applying a zero default this incentives Shipper to input Gas Nominations else Scheduling charges apply. Principle that only existing reads can be replaced after the read submission deadline. 22/01/13: Xoserve to carry out analysis & take proposals to SPAA & MAMCoP for agreement. 05/02/13: Analysis being carried out by Xoserve, MAMCoP have been made aware. 22/10/13: Agreed at PN UNC for issue to be moved to RAID log. Agreed at PN UNC on 04/12/12 that validation should not be applied to the AQ for Products 1 & 2. The AQ should reflect 12 months consumption data, which may be less than the SOQ. Shipper nominates SOQ. Agreed at PN UNC on 04/12/12: Validation should apply to final meter readings. Proposal agreed at PN UNC on 04/12/12: Agreed that actual meter reads will not be replaced for Product 1 & 2 sites, consumption adjustments will be used to replace consumption. Alternative option proposed at PN UNC on 04/12/12: Where a value has not been input a D-7 default will be loaded but scheduling will be based on a non input. BRD to be updated. Principle agreed at PN UNC on 04/12/12. Confirmed at 08/01/13 meeting. AQ BRD v4.0 BRD AQ BRD BRD BRD BRD Updated 17/06/2013 Page 1 of 6
9 26/11/2012 Closed Proposal DM Mandatory 10 26/11/2012 Closed Proposal Unidentified gas share AQ & AQ & 11 19/12/2012 Closed Proposal AQ AQ 12 19/12/2012 Closed Proposal Change in Product 13 19/12/2012 Closed Proposal Valid Reads 14 19/12/2012 Closed Issue Ratchets 15 19/12/2012 Closed Proposal AQ AQ Where a site's AQ exceeds the DM Mandatory threshold (after 3 calculations ) the site must be transferred into Product 1. After X period if no action taken by the Shipper the site is auto confirmed into Product 1. Also need a process for sites that go below DM mandatory threshold. Should the share of unidentified gas be based on the same value:- Allocation Scaling Adjustment share is based on consumption at GFD+5, Reconciliation Scaling Adjustment share is based on AQ Should the AQ be weather corrected for Product 2 sites? Recommend maximum number of switches between Products where there is no change in Shipper. Only Closed Out reads for Products 1 & 2 will be classed as valid reads & used in downstream processes e.g. AQ review will not use reads until after GFD+5 Ratchets will apply to Products 1 & 2 sites (where the Shipper nominates the SOQ). For Product 2 sites particularly the read can be replaced with a Consumption Adjustment which could invalidate the Ratchet. This will affect allocations to all Shippers within the LDZ (increase the amount of unidentified gas). For Greenfied Sites recommend wait for 12 months history before AQ is calculated, AQ rolled over until 12 month anniversary Option for Shipper to keep their metering equipment at the site & be responsible for sending in the daily reads as per requirement for Product 1. Principle supported at 08/01/13 meeting for throughput to be used rather than AQ for the Allocation & Reconciliation Scaling Adjustment. Further consideration on the value used for the Rec Scaling Adjustment; consumption at GFD+5 or latest value. 4 times within a 12 month period and 2 month gap between change in Products (unless change in Shipper or asset data) Option for a Ratchet to be applied to sites in Product 2 where AQ is above 732,000 KwH only. 22/01/13: Workgroup agreed that a site should not be auto confirmed into Product 1 when the DM Mandatory threshold has been met or exceeded or out of Product 1 when the site is no longer DMM. Current UNC rules to remain. Xoserve to present proposal for 05/02/13 meeting. 05/02/13: To be agreed at meeting following review by PN UNC members of the options & their preferences. : Agreed by PN UNC that lastest consumption should be used for the rec Scaling Adjustment. Agreed that Product 2 sites should not be weather corrected. Agreed that a 2 month limit was sufficient. No further limits on Product switches although this will be reportable for Quality Assurance. Agreed that only closed out valid reads will be used. 22/01/13: Workgroup agreed that Ratchets should apply to all sites in Product 1 & 2 as per existing UNC rules. Number of consumption adjustments invalidating a ratchet will be reportable to the PAB. 08/01/13: PN UNC did not agree that an AQ should not be calculated until 12 month anniversary as the original AQ is only a default AQ from NExA table. Agreed to use 9 months consumption history & pro rata to calculate new AQ. 22/01/2013 22/01/2013 as no change to original requirements documented as no change to original requirements documented BRD as original requirements not changed AQ BRD Updated 17/06/2013 Page 2 of 6
16 09/01/2013 Closed Proposal Faulty Meters 17 09/01/2013 Closed Proposal EUC & SPR AQ & 18 09/01/2013 Closed Proposal AQ Correction AQ 19 16/01/2013 Closed Proposal Transfer Reads 20 16/01/2013 Closed Issue Ratchets SPR 21 22/01/2013 Closed Assumption 22 28/01/2013 Closed Issue LDZ Telemetered sites Shared Supply Meter Points SPR 23 28/01/2013 Closed Proposal AQ AQ Treatment of a Faulty meter needs to be considered for all Products Is a different EUC for I&C sites with an AQ less than 73,200 kwh? Where an AQ Correction has been accepted any new reads loaded will trigger an AQ review based on previous consumption history which may not be relevant. Product 2: as per DM process currently. Product Xoserve to produce flows for 3 & 4, notify of faulty status 18/02/13 PN UNC. & consumption adjustment : proposals agreed to correct consumption during period. If agreed this needs to be referred to DESC The effective date of the new AQ should be used as a backstop date to ensure a new AQ is not calculated based on previous history. For Products 1, 2 & 3, the read for the GFD will be used to close out the A transfer reading is not for a previous period. For change in Product where no change in Product 4 an estimate will Shipper. be calculated. Shipper can submit a read for the transfer date and it will be accepted. Where a Ratchet as taken place the SOQ is increased but the SHQ remains the same. This results in the SOQ & SHQ being out of line. LDZ Telemetered sites will be treated as DM Mandatory, processed as per NTS sites in Product 1 regardless of AQ.. SSMP sites have slightly different timescales for Nomination & Confirmation. A Nomination for a newly requested SSMP requires 2 months notice before the effective date and the Confirmation must allow 20 working days notice (UNC G1.7.10). This is due to the current manual & offline processes. Existing SSMPs have the same notification timescales as 'normal' sites Where a site moves from Product 3/4 to Product 2/1 there may not be 365 days consumption to calculate the AQ, especially when transfering from Product 4, Increase the SHQ to the same ratio of SOQ to SHQ prior to the Ratchet Nomination & Confirmation timescales for SSMP are treated the same as any other DM Mandatory site Use NDM rules for calculating the AQ (profiles) until 9 months consumption profile is available. 22/01/13: PN UNC agreed that the requirements for an I&C EUC in SSP market & a Domestic EUC for the LSP market. Email sent to Fiona Cottam to raise at DESC. 22/10/13: Agreed at PN UNC to close issue. 22/01/13: PN UNC agreed with Xoserve proposal. : Proposal agreed at PN UNC. BRD updated & change reflected in version 2.0. : PN UNC agreed to increase the SHQ only if the ratio between the SOQ & SHQ becomes out of tolerance following a Ratchet. :Agreed at PN UNC. BRD to reflect assumption. 05/02/13: PN UNC agreed timescales should be the same wherever possible for all meter points, including SSMP.s 05/02/13: PN UNC agreed to proposal. SPR BRD 22/01/2013 AQ BRD v4.0 BRD See Issue Ref 33 BRD SPR BRD AQ BRD v4.0 Updated 17/06/2013 Page 3 of 6
24 28/01/2013 Closed Issue Check Read SPR 25 28/01/2013 Closed Issue Opening Read 26 28/01/2013 Closed Issue (raised by P. Thompson) MRF SPR & SPR & In order to satisfy the Check Read requirement Shippers will need to flag that meter reading equipment installed. For a Shipper transfer to Product 3 from either Product 3 or 4 the transfer read needs to be obtained on the transfer date to ensure all previous & subsequent daily reads follow on. Determine and agree the frequency of meter reads to be received by Xoserve. A reasonable frequency for the readings from meters which currently fall into the domestic dumb meter category would be six monthly. For domestic Smart then fortnightly would be appropriate. For SME dumb meters, Monthly. For Smart SME, weekly. Should there be any dumb I&C meters then Monthly readings, otherwise for I&C Smart or Advanced, daily. Transfer read obtained on the transfer date & submitted within 10 days. These read proposals can cut across the four categories / products being proposed for Nexus as the frequency of reads sent to Xoserve do not have to be linked to those products necessarily. Improvement in read frequency reduces significantly the time taken to identify poor data, either following meter exchange or poor read taking and therefore helps reduce disputed invoices so reducing administration cost. Not to mention more accurate allocation processes. 05/02/13: In principle PN UNC agreed however Xoserve need to consider during detailed analysis if this can be done via read file (preference) or via asset update. 05/02/13: PN UNC agreed that transfer to Product 3 the incoming Shipper must obtain a transfer read on the transfer date. 05/02/13: All to consider current proposals for 18/02/13 meeting. Xoserve to publish proposals in BRD (table).: Updates to gvalues currently held in the BRD were discussed & amended. BRD to be updated to reflect changes agreed. BRD BRD 27 28/01/2013 Closed Proposal Re-confirmation SPR 28 28/01/2013 Closed Proposal Re-Synch Currently a re-confirmation is for changes to certain Supply Point data items, where no change in Shipper, If the details of a re-synch are not input on the same day any subsequent reads loaded may cause reads to be rejected/incorrect consumption to be calculated - especially for Products 1 & 2. Ability for Shipper to submit a Supply Point amendment rather than go through the re-confirmation process, this will include a change in Product. Re-synch details input on same day as Check Read carried out for Products 1 & 2. For Products 3 & 4 - within 5 days? 05/02/13: proposal agreed. SPR BRD 05/02/13: to be considered further on 18/02/13. Xoserve to produce process flow. : Agreed that the Shippers MRA to notify Xoserve of the site visit & any check read & re-synch details must be sent to Xoserve by GFD+5 for Product 2 to ensure allocations were correct before Close Out. SPR BRD Updated 17/06/2013 Page 4 of 6
Assumption has been made with all 29 Closed Issue the external BRDs and internal Mod 0428 approved on Single Meter analysis that a Supply Point will consist 31/07/13 with an Point Supply SPR of only one Meter Point. If Mod 0428 is 31/07/2013 Implementation date of April Points not approved this will require re-work 2014. to the external BRDs & analysis carried out to date. 30 Closed Issue 31 Closed Review Meter Read Frequency Read Submission 32 08/03/2013 Closed Proposal File Responses Various 33 01/03/2013 Closed Proposal Confirmations SPR Currently an AQ can increase following AQ review to above 293,000 kwh but the meter point can continue as annually read. Only obligation to amend is at Confirmation in which case it would reject if annual MRF is elected. Review performance targets & read submission deadlines in the BRD. Currently response files are sent which includes all the data sent in by the Shipper. Currently Shippers can only cancel a Confirmation upto D-8 for SSP. Auto change of MRF from Annual to Monthly. Agreed : Remove Must Read obligation for Product 1. Amend Performance Targets for Product 4. Amend Max Read Submission for Product 4. With some exceptions, e.g. Confirmation (?), only respond with 'Accept' or 'Reject' and reason for rejection. Allow Confirmations to be cancelled for LSP aswell : PN UNC agreed this was a UNC obligation on the Shipper & should remain. Instances of sites with an AQ above 293,000 kwh on an Annual MRF should be reported to PAB : Changes agreed at PN UNC & will be reflected in the updated BRD (presentation amended & published under 05/03/2013 PN UNC) 18/03/13: PN UNC agreed that the response files to remain as is. The confirmation of the data held provides a check for the Shipper. 18/03/13: PN UNC believe that the facility to cancel a Confirmation should only be available for domestic & SME sector. Believe AQ threshold should be parameterised;initial thoughts is 732,000 kwh. 10/04/13: Agreed at PN UNC for the ability to cancel a Confirmation upto D-8 to be available to all sites. BRD 18/03/2013 SPR BRD 10/04/2013 SPR BRD Updated 17/06/2013 Page 5 of 6
34 18/03/2013 Closed Monitor Ratchets SPR Previous PN UNC meeting it was agreed that following a Ratchet to increase the SHQ to the same ratio of SOQ to SHQ prior to the Ratchet. This has since been discussed with GTs who do not believe this should be done as the SHQ would not be reflective of the true hourly consumption, as set by the Shipper. No change to current process. Shipper to update SHQ. 23/04/13: Discussions at PN UNC as to whether the SHQ should be increased when out of tolerance of the SOQ as a result of a Ratchet. 20/05/13: CW discussed at PN UNC that this needs further review by GTs and any changes to the current process will require a Mod. Agreed to retain as 'Monitor' but no further action from PN UNC. 17/06/13: Agreed that this was not a requirement for PN but agreed to leave as an issue to 'monitor'. 22/10/13 PN UNC - Agreed this can be closed. 35 13/08/2013 Closed Issue Demand Estimation Mod 0453 Issue raised at PN UNC that the current proposal was an interim solution for 18 month period only. Possible for an alternative methodology to be proposed before implementation of Nexus requirements. Risk that Xoserve are basing all analysis on Mod 0453. 36 10/09/2013 Closed Monitor Gas Day EU Reform 37 30/09/2013 Closed Monitor 38 30/09/2013 Closed Monitor Demand Estimation methodology UNC Supplementary Documents 39 30/10/2013 Closed Requirement Read Validation All The new Demand Estimation methodology mat need to be implemented on the 1st October The UNC Supplementary Documents need to be reviewed & amendments made to meet the requirements within the BRD's. Following a transfer of ownership the new Shipper will be unable to validate the first read received from a consumer as they will have no history. Meeting on 10th September to discuss further Monitor developments for any impacts to Project Nexus requirements Believe that it can be implemented mid month but the impacts need to be considered. Updated documents to be considered at 16/10/2013 PN UNC Send new Shipper the lastest read before the transfer effective date. 10/09/2013: Agreed to provide some text in UNC stating the algorithm will need to be reviewed by xxx and updates to BRDs agreed at 30/09/2013 meeting. 22/10/13 PN UNC - Agreed this can be closed. 22/10/13 PN UNC - Agreed this can be closed. Issue transferred onto RAID log. 22/10/13 PN UNC - Agreed this can be closed. Included in requirements, legal text needs to be written. 30/09/2013 BRD v 3.2 Updated 17/06/2013 Page 6 of 6