EDW Technology Limited...BSC CP1441 Allowing the Peer Comparison technique to be reported on a Supplier Agent level BSC CP1442 Clarifying the application process for Metering Dispensations

EDW Technology Limited ERS Industry Compliance Statement

Date Published: 23/10/2015

ERS Industry Compliance Statement Date Published 23/10/2015

EDW Technology Limited © 2015 Page 2 of 62

Table of Contents Summary of Contents 4

ERS Industry Compliance Statement Summary 5

ERS Industry Compliance Statement Detail (CP1430) 9











ERS Industry Compliance Statement Detail (DTC CP 3445) 20





ERS Industry Compliance Statement Detail (DTC CP 3459A) 25





ERS Industry Compliance Statement Detail (MAP CP 0221) 30



















ERS Industry Compliance Statement Detail (P300) 49









ERS Industry Compliance Statement Detail (WPPS CP 0122) 56









Summary of Contents

Implementation Date

Product Set Number of Changes

11 Nov 2015 BSC 18

11 Nov 2015 MRA 30

30 Jun 2016 BSC 3

30 Jun 2016 MRA 2

03 Nov 2016 BSC 1

03 Nov 2016 MRA 0



ERS Industry Compliance Statement Summary

Implementation Date

Product Set

Change Reference

Title

05 Nov 2015 BSC CP1430 Clarification to the ECVN/MVRN processes

BSC CP1431 Extend Site Check Exemption to Measurement Classes F and G

BSC CP1432 HH Default EAC by Measurement Class

BSC CP1436 EAC/AA and NHHDA Applications – Windows Server upgrade

BSC CP1437 Recommended amendments to BSCP68

BSC CP1438 Clarification of information required for raising a Trading Dispute

BSC CP1439 Proving Test Permissible Software

BSC CP1440 Exempting Metering Systems in Measurement Class F from proving tests

BSC CP1441 Allowing the Peer Comparison technique to be reported on a Supplier Agent level

BSC CP1442 Clarifying the application process for Metering Dispensations

BSC CP1444 Extend the timescale of CoP10 Proving Tests until the implementation of P272

MRA DTC CP 3445 Update to J1824 - Asset Condition Code

MRA DTC CP 3446 Additional Asset Condition Report Response changes to the D0126 Data flow

MRA DTC CP 3453 Changes to existing DTC flows to support new Measurement Classes under P300

MRA DTC CP 3457 Update to D0135 – Asset Condition Report, following D0126/D0135 process review




Implementation Date

Product Set

Change Reference

Title

MRA DTC CP 3458 Reporting of Excluded Energy Volumes in the CFD Supplier Invoice Backing Data Flow D0362

MRA DTC CP 3459A Changes to facilitate implementation of BSC Modification Proposal P305

MRA DTC CP 3460 Reporting of Additional EMR Backing Data to Suppliers (D0362 and D0364)

MRA DTC CP 3462 Clarification of Data Item descriptions for EMR

MRA DTC CP 3465 SVAA Reporting Changes to facilitate implementation of BSC Modification Proposal P305

MRA DTC CP 3467 Changes to facilitate implementation of BSC Modification Proposal P305 (Version 3)

MRA MAP CP 0221 Amending MAP15 to mandate resolving D0312 rejections

MRA MAP CP 0222 Amending MAP15 to introduce a report detailing the number of D0312 rejections

MRA MAP CP 0223 Amending MAP15 to implement Algorithm 5

MRA MAP CP 0224 Amending MAP15 to implement an Algorithm 5 report

MRA MAP CP 0226 Amend MAP 18 to Improve Exception Handling in the GDCC (Alternative to MAP CP 0225)

MRA MAP CP 0232 Amending MAP14 to distribute unallocated Key transactions

MRA MAP CP 0233 Amending MAP15 to enhance the Transaction Routing Flag functionality

MRA MAP CP 0235 Amend MAP13 to specify invoicing frequency

MRA MAP CP 0238 Erroneous Transfers escalations




Implementation Date

Product Set

Change Reference

Title

MRA MAP CP 0239 Amending MAP14 to mandate the Redirected Report frequency

MRA MAP CP 0244 Amendment to MAP18 to change the processing times for GD Charges

MRA MAP CP 0247 MAP CP 0247 - Amendment to a Clause reference within MAP04, Section 6

MRA MAP CP 0248 Amending MAP17 to update the MDB Constitution to reference Smaller Suppliers

MRA MAP CP 0249 MAP18 SEG Recommended Changes

MRA MAP CP 0250 Removal of contractual arrangements from MAP14

MRA MAP CP 0252 Identifying whether a metering system is Whole Current or Current Transformer

MRA MAP CP 0253 MAP18 Drafting Clarifications

MRA MAP CP 0257 Amend MAP18 GDCC Exception Handling Wording Introduced by MAP CP 0226

MRA MAP CP 0258 Amending MAP17 to update the MDB Constitution for Distribution Businesses

BSC P300 Introduction of new Measurement Classes to support Half Hourly DCUSA Tariff Changes

BSC P305 Electricity Balancing Significant Code Review Developments

BSC P309 Facility to enable BSC Parties to select either replacement contract notifications or additional contract

notifications

BSC P319 Removal of annual RMP review from PAF




Implementation Date

Product Set

Change Reference

Title

BSC P322 Revised Implementation Arrangements for Mandatory Half Hourly Settlement for Profile Classes 5-8

BSC P323 Enabling inclusion and treatment of SBR in the Imbalance Price

BSC P327 Clarifications to P305 legal text

MRA WPPS CP 0122 Amendments to Working Practice 124

30 June 2016 BSC CP1434 Amend the three digit numeric Line Loss Factor Class (LLFC) Id to an Alphanumeric LLFC Id

MRA DTC CP 3469 Supplier to Supplier instance of D0010 ‘Meter Readings’ flow

MRA DTC CP 3470 New value of J0007 to support Approved BSC Modification P302

BSC P302 Improve the Change of Supplier Meter read and Settlement process for smart Meters

BSC P315 Publication of Gross Supplier Market Share Data

03 Nov 2016 BSC P297 Receipt and Publication of New and Revised Dynamic Data Items



ERS Industry Compliance Statement Detail (CP1430)

Change Reference: Title:

CP1430 Clarification to the ECVN/MVRN processes

Product Set: Implementation Date:

BSC 05 Nov 2015

Summary:

CP1430 proposes to clarify instances of ambiguous or unclear advice regarding the Energy Contract Volume Notification (ECVN) and Metered Volume Reallocation Notification (MVRN) processes. In particular CP1430 will better enhance the clarity of the methods for terminating these notifications.

History:

CP1430 was raised by ELEXON on 9 February 2015. CP1430 was presented to the ISG as part of a New CP Assessment Paper on 24 February 2015 and issued for CP consultation on 9 March 2015 with responses due by 2 April 2015. CP1430 was approved by the ISG at its meeting on 21 April 2015 for implementation on 5 November 2015.

Comments:





CP1431 Extend Site Check Exemption to Measurement Classes F and G


BSC 05 Nov 2015

Summary:

CP1431 proposes to extend the exemption to carry out HH Metering System checks to also include Measurement Classes F and G. This will reflect approved changes made by P300.

History:

ELEXON raised CP1431 on 16 February 2015. CP1431 was presented to the SVG as part of a New CP Assessment Paper on 3 March 2015 and issued for CP Consultation on 9 March 2015 with responses by 2 April 2015. At its meeting on 28 April 2015, the SVG approved CP1431 for implementation on 5 November 2015 as part of the November 2015 BSC Systems Release.

Comments:





CP1432 HH Default EAC by Measurement Class


BSC 05 Nov 2015

Summary:

CP1432 proposes to allow for HH Default EAC by Measurement Class. As with the migration of PC5-8 Metering Systems under P272, the number of non-100kW Metering Systems will result in the current HH Deafult EAC being too low for 100kW sites and too high for the non-100kW sites.

History:

CP1432 was raised by ELEXON on 17 February 2015. CP1432 was presented to the SVG as part of the New CP Assessment paper at its meeting on 3 March 2015 and issued for CP Consultation on 9 March 2015 with responses due by 2 April 2015. At its meeting on 28 April 2015, the SVG approved CP1432 for implementation on 5 November 2015 as part of the November 2015 BSC Systems Release.

Comments:





CP1436 EAC/AA and NHHDA Applications – Windows Server upgrade


BSC 05 Nov 2015

Summary:

The Non Half Hourly Data Aggregator (NHHDA) and Estimated Annual Consumption (EAC)/Annualised Advances (AA) software applications are designed to support running on a ‘Solaris only’ and a ‘Solaris/Windows Server’ platform. Two out of the 13 NHHDAs currently operate on Windows Server 2003 and the support to Windows Server 2003 will expire in July 2015. ELEXON understands that the two NHHDAs will be upgrading their systems to Windows Server 2012, which will be supported until 2023. Therefore CP1436 proposes that ELEXON and its Application Management and Development (AMD) service provider will develop, test and deploy new versions of the NHHDA and EAC/AA applications that are compatible with a currently supported version of Windows Server.

History:

CP1436 was issued for CP Consultation on 9 March 2015 with responses due by 2 April 2015. The SVG approved CP1436 at its meeting on 28 April 2015.

Comments:





CP1437 Recommended amendments to BSCP68


BSC 05 Nov 2015

Summary:

Following the rejection of CP1423, it was recommended by the Imbalance Settlement Group (ISG) and the Supplier Volume Allocation Group (SVG), that the contents be separated into two changes and progressed separately. CP1437 seeks to address the more straight forwards elements, which were not contested under the CP1423 consultation, and were agreed by both Committees.

History:

CP1437 was raised by ELEXON on 16 March 2015. This is proposed for progression as a Housekeeping CP and therefore will not be issued for CP Consultation. All changes were consulted on as part of CP1423. CP1437 was approved by the ISG on 24 March 2015 and the SVG on 31 March 2015 for implementation on 5 November 2015, as part of the November 2015 Release

Comments:





CP1438 Clarification of information required for raising a Trading Dispute


BSC 05 Nov 2015

Summary:

CP1438 seeks to align Sections 1.4 and 5.1.1 in BSCP11 to remove ambiguity and clarify that in order for a BSCP11/01 form to be accepted by ELEXON it must: - identify a breach of the BSC or Code Subsidiary Document; and - indicate the relevant Settlement Error.

History:

CP1438 was raised by ELEXON on 30 March 2015 and has been issued for CP Consultation. The TDC will make its decision on CP1438 at its meeting on 2 July 2015. CP1438 is targeted for implementation on 5 November 2015 as part of the November 2015 BSC Systems Release.

Comments:





CP1439 Proving Test Permissible Software


BSC 05 Nov 2015

Summary:

CP1439 proposes to amend BSCP514 to allow the Half Hourly Meter Operator Agent (HHMOA) to also use other BSCP601 ‘Metering Protocol Approval and Compliance Testing’ approved software during the proving test process. This software undergoes the protocol approval process within BSCP601 to ensure that it acts in the same way as the manufacturer software when dialling Meters and can be tasked with dialling Meters in batches rather than individually. This will allow batches of proving tests to be undertaken more quickly and therefore facilitate the efficient implementation of P272 ‘Mandatory Half Hourly Settlement for Profile Classes 5-8′, which will require significant volumes of Change of Measurement Class (CoMC).

History:

CP1439 was raised by SmartestEnergy on 10 April 2015 and was presented to the SVG as part of the New CP Assessment paper at its meeting on 28 April 2015. It was issued for CP Consultation on 5 May 2015, with responses due by 29 May 2015. CP1439 was approved by the SVG at its meeting on 4 August 2015 for implementation on 5 November 2015 as part of the November 2015 Release.

Comments:





CP1440 Exempting Metering Systems in Measurement Class F from proving tests


BSC 05 Nov 2015

Summary:

CP1440 proposes to introduce an exemption from proving tests for Metering Systems in Measurement Class F. This CP will remove a barrier to elective HH Settlement for domestic Metering Systems so helps to deliver the efficiencies that HH Settlement brings.

History:

CP1440 was raised by ELEXON on 28 April 2015. CP1440 was issued for CP Consultation on 5 May 2015, with responses due by 29 May 2015. CP1440 was approved by the SVG at its meeting on 30 June 2015 for implementation on 5 November 2015 as part of the November 2015 Release.

Comments:





CP1441 Allowing the Peer Comparison technique to be reported on a Supplier Agent level


BSC 05 Nov 2015

Summary:

CP1441 proposes to amend Balancing and Settlement Code Procedure (BSCP) 533 to introduce Supplier Agents into the publication criteria of Peer Comparison.

History:

CP1441 was raised on 28 April 2015. CP1441 was issued for CP Consultation on 8 June 2015, with responses due by 3 July 2015. CP1441 was approved by the PAB on 30 July 2015 and the SVG on 4 August 2015. CP1441 will be implemented on 5 November 2015 as part of the November 2015 BSC Systems Release.

Comments:





CP1442 Clarifying the application process for Metering Dispensations


BSC 05 Nov 2015

Summary:

CP1442 proposes to update the guidance provided within BSCP32 on how to populate the Metering Dispensation application form for submission. This guidance will help to inform the applicant of the level of detail required for the BSCCo to progress the application and for the relevant Panel Committee(s) to make an informed decision.

History:

CP1442 was raised on 5 May 2015. It was presented to the ISG for initial comment on 26 May 2015, and will be presented to the SVG on 2 June 2015. It was then issued for CP Consultation on 8 June 2015, with responses due by 3 July 2015. CP1442 was presented to the ISG and the SVG for approval at their meetings on 21 July 2015 and 4 August 2015 respectively. Both Committees approved the CP for implementation on 5 November 2015 as part of the November 2015 BSC Systems Release.

Comments:





CP1444 Extend the timescale of CoP10 Proving Tests until the implementation of P272


BSC 05 Nov 2015

Summary:

CP1444 proposes to extend the timescales in which to carry out a proving test for a Code of Practice (CoP) 10 Metering System. These extended timescales would only be effective until P272 ‘Mandatory Half Hourly Settlement for Profile Classes 5-8′ has been implemented. Once P272 has been implemented, these timescales would revert to those originally approved under CP1429 ‘Proving Test timescales’.

History:

CP1444 was raised by Haven Power on 7 July 2015, and has been issued for CP Consultation. The SVG approved CP1444 on 29 September 2015 for implementation on 5 November 2015 as part of the November 2015 BSC Systems Release.

Comments:



ERS Industry Compliance Statement Detail (DTC CP 3445)


DTC CP 3445 Update to J1824 - Asset Condition Code


MRA 05 Nov 2015

Summary:

DTC CP 3445 seeks to change the valid set of the J1824 Data Item following a planned review of reporting processes for Service Termination Asset Conditions by the MOCOPA®/ENA/AMO workgroup who originally introduced J1824.

History:

Data Item J1824 (Asset Condition Code) was originally implemented following a review of business processes for Service Termination Asset Reporting by the MOCOPA® issues sub-group, the ENA’s Smart Meter Operations Group and the AMO’s Electricity Metering Forum. This review highlighted the need to categorise the reports and revise the method of reporting, resulting in the introduction of J1824. MOCOPA®; ENA and AMO agreed to review the new reporting categories and associated guidance documents 6 months after implementation, which led to a series of workgroup meetings held in 2014 to discuss parties’ experiences with the process. The workgroup meetings highlighted issues with the existing Asset Condition Codes, such as duplication of asset characteristics in different reporting categories and codes, resulting in subsequent agreement of a revised set of Asset Condition Codes.

Comments:





DTC CP 3446 Additional Asset Condition Report Response changes to the D0126 Data flow


MRA 05 Nov 2015

Summary:

DTC CP 3446 seeks to add a new ‘Asset Condition Clearance Code’ “R” to Data Item J1823 to allow DNOs to distinguish and keep track of incorrectly reported faults that have been resolved by DNOs, following the approval of DCP195A.

History:

Following the acceptance of DTC CP 3435 (at MDB_14_0828), which introduced Asset Condition Clearance Code “U” – Unable to resolve to Data Flow D0126, an additional value “R” – Resolved has been suggested in order to further improve the D0135/D0126 process as part of the comments following DTC CP 3435 Impact Assessment: Following approval of DCP195A we don't think this CP offers a complete solution. We think that there is a need for an additional code letter to identify situations where DNOs have attended site, found that there was a defect but not as serious as the one reported, and have resolved this other defect. As part of the DCUSA changes DNOs will be entitled to levy a charge on Suppliers where they specify an asset condition code which indicates a more serious situation than is actually the case. Having an additional response code will give us a method of recording / counting such instances, and as Suppliers would receive notification of each instance they would be able to monitor the misreporting. It would also give visibility of potential charges should the DNO choose to invoice the Supplier.

Comments:





DTC CP 3453 Changes to existing DTC flows to support new Measurement Classes under P300


MRA 05 Nov 2015

Summary:

DTC CP 3453 contains the proposed structural changes to data flows D0040 and D0298, as well as a name only change to the D0030 Data Flow to support the implementation of BSC Modification Proposal P300 on 5th November 2015.

History:

DTC CP 3453 has resulted from the acceptance of P300 which was raised to accommodate the following changes to the Measurement Classes for customers with maximum demand of less than 100kW:

-CT metered customers that have aggregate billing;

-Domestic HH non-CT metered customers that have aggregate billing; and

DUoS bills. P300 enables aggregate DUoS billing and does not require any consumer move to HH settlement. The changes proposed also do not mandate that Suppliers use the new Measurement Classes. They may continue to use Measurement Class C (for customers with maximum demand 100kW or more) or the re-named Measurement Class E. P300 was approved by the Authority on 15th October 2014, and will be implemented on 5th November 2015 as part of the November 2015 BSC Systems Release.

Comments:

DTC CP 3453 is required to amend the D0040 and D0298 Data Flows to include new record types for the new Measurement Classes. These new record types will be similar to the existing D0040 and D0298 Data Flows. However, the consumption will be broken down by the J0189 ‘Distributor Id’ and J0147 ‘Line Loss Factor Class Id’ data items in addition to the J0084 ‘Supplier Id’, J0066 ‘GSP Group Id’ and J0160 ‘Consumption Component Class Id’ Data Items. As the new record types introduced into the D0040 and D0298 Data Flows apply only to the new Measurement Classes, a Supplier who is not using them will receive the D0040 and D0298 Data Flows with no data for the new record types. The draft red-lining for the proposed changes to the D0040 and D0298 data flows can be found in Appendix 1. In addition, the D0030 ‘Non Half Hourly DUoS Report’ data flow will require a change of title to reflect that this will now also include HH aggregated data. This CP proposes a new title of 'DUoS Report’.





DTC CP 3457 Update to D0135 – Asset Condition Report, following D0126/D0135 process review


MRA 05 Nov 2015

Summary:

Following an end to end review of the D0126 / D0135 process, two changes to the D0135 – Asset Condition report Data Flow were identified. Firstly, to make J0004 - Meter Id (Serial number) an optional Data Item and secondly, to include a flag to notify Distribution Businesses if a defect has been found when carrying out a Smart Meter installation visit as a new Data Item.

History:

Following the deferral of DTC CP 3445 and DTC CP 3446 by MDB to IREG, MIF165 was raised to review the end to end D0126 / D0135 process. At IREG_15_0114, MIF165 was discussed where it was agreed to issue a Request For information (RFI) to gain wider industry views on any issues relating to reporting Asset Condition using the D0126 and D0135 Data Flows. RFI Responses were discussed at IREG_15_0211 where a total of 9 issues were raised within the RFI. Two of the issues raised have led to this Change Proposal relating to the sending of the D0135 – Asset Condition Report Data Flow. The first issue raised relating to D0135 was that parties do not always know the Meter Id (Serial Number) and are not always able to populate this field. It was agreed for Group 258 to remain mandatory, however the Data Item J0004 Meter Id (Serial number) would be made optional. Within this group there is an Additional Information Data Item (J0012) which will allow parties to populate why they have not been able to provide the Meter Id (Serial Number). The second issue raised related to the D0135 Data Flow was the notification of an Asset Condition during a visit where a Smart Meter was due to be installed. This comes as a result of Ofgem placing an obligation on Distribution Businesses to report the volume and costs of Smart Meter related interventions. It was agreed to add a flag which will notify the Distribution Business if the visit by the Meter Operator was in relation to a Smart Meter installation.

Comments:





DTC CP 3458 Reporting of Excluded Energy Volumes in the CFD Supplier Invoice Backing Data Flow D0362


MRA 05 Nov 2015

Summary:

Changes to the CFD Supplier Obligation Regulations require amendments to the D0362 (CFD Supplier Invoice Backing Data) to report the green renewable energy (green) volumes, and make it clear that the existing excluded demand data items relate to excluded Energy Intensive Industry (EII) volumes.

History:

Following DECC’s decisions to its ‘EMR: Changes to the CFD supplier obligation’ consultation, changes are to be made to the CFD Supplier Obligation Regulations that exclude certain EII and green energy volumes from CFD Supplier’s chargeable demand. The D0362 does not report green energy volumes and it is currently ambiguous what exempt demand the existing excluded demand data items refer i.e. do they refer to the green or the EII volumes, or both.

Comments:



ERS Industry Compliance Statement Detail (DTC CP

3459A)


DTC CP 3459A Changes to facilitate implementation of BSC Modification Proposal P305


MRA 05 Nov 2015

Summary:

DTC CP 3459A intends to facilitate the implementation of BSC Modification Proposal P305, which was raised by National Grid in order to implement the conclusions of Ofgem’s Electricity Balancing Significant Code Review (EBSCR). It seeks to amend the D0018 Data Flow and also add 5 new Data Flows and 16 new Data Items.

History:

BSC Modification Proposal P305 proposes to progress and implement the conclusions to Ofgem’s Electricity Balancing Significant Code Review, which will put in place a single, marginal imbalance price, introduce Reserve Scarcity Pricing and introduce pricing for Demand Control actions. P305 introduces a method for recognising the cost of Demand Control actions in the calculation of imbalance prices and imbalance volumes. This method will require Supplier Volume Allocation (SVA) and Central Volume Allocation (CVA) parties and agents to share data with each other in order to estimate volumes of energy that are not consumed because of a Demand Control event and to make adjustments to suppliers’ metered volumes to ensure accurate allocation of energy across suppliers and settlement periods. The proposed implementation date for P305 is for the 5th November 2015. The processes proposed by P305 to estimate volumes of disconnected energy and to adjust suppliers’ metered positions are new and will require parties and agents to share and use existing and new data items. The P305 Assessment Report sets out the requirements on parties and agents in relation to Demand Control Events. In summary, the following activities will need to be supported by new and existing DTC flows and data items: DNOs will need to report details of Metering Systems affected by Demand Control events to supplier agents;

Systems that may have contributed voluntary demand side actions during Demand Control Events to supplier agents;

a revised calculation of AAs; and Supplier and Central Agents will need to share and use new data items in order to estimate HH estimates of disconnected volumes and share these so they can be aggregated in order to adjust Suppliers’ metered volumes and balancing services volumes.

Comments:





DTC CP 3460 Reporting of Additional EMR Backing Data to Suppliers (D0362 and D0364)


MRA 05 Nov 2015

Summary:

This change adds additional data groups to the D0362 and D0364 data flows to allow improved reporting to Suppliers of certain CFD and CM charges.

History:

From April 2015, the CFD and CM Settlement Services Provider will be issuing CFD and CM invoices to Suppliers. Accompanying these (for those Suppliers who elect to receive EMR reports over the DTN) will be backing data on the following DTC flows:

-related invoices; and voice Backing Data (D0364) for CM-related invoices.

Each of these data flows contains data groups for a number of different payment types (including all of the more usual and routine ones). But the following payment types do not currently have associated data groups (which means any invoices or invoice lines of these types will not be accompanied by backing data):

accordance with Regulation 18; and Settlement Cost Levy (where an excess has been recovered from Suppliers).

This Change Proposal adds additional data groups to allow the system to produce backing data for these payment types.

Comments:





DTC CP 3462 Clarification of Data Item descriptions for EMR


MRA 05 Nov 2015

Summary:

DTC CP 3462 seeks to clarify the Data Item descriptions in two EMR-related Data Flows, D0362 and D0365

History:

From April 2015, the CFD Settlement Services Provider will be issuing invoices to Suppliers and Generators. Accompanying these (for parties who elect to receive CFD reports over the DTN) will be backing data on the following DTC flows:

This CP proposes to clarify the Data Item descriptions for two Data Items on these Data Flows.

Comments:





DTC CP 3465 SVAA Reporting Changes to facilitate implementation of BSC Modification Proposal P305


MRA 05 Nov 2015

Summary:

DTC CP 3465 intends to facilitate the implementation of BSC Modification Proposal P305, which was raised by National Grid in order to implement the conclusions of Ofgem’s Electricity Balancing Significant Code Review (EBSCR). It seeks to introduce new DTC flows (equivalents of existing SVAA reports) to allow the SVAA to report on the volumes of disconnected energy in the event of a Demand Control Event.

History:

BSC Modification Proposal P305 proposes to progress and implement the conclusions to Ofgem’s Electricity Balancing Significant Code Review, which will put in place a single, marginal imbalance price, introduce Reserve Scarcity Pricing and introduce pricing for Demand Control actions. P305 introduces a method for recognising the cost of Demand Control actions in the calculation of imbalance prices and imbalance volumes. This method will require Supplier Volume Allocation (SVA) and Central Volume Allocation (CVA) parties and agents to share data with each other in order to estimate volumes of energy that are not consumed because of a Demand Control event and to make adjustments to suppliers’ metered volumes to ensure accurate allocation of energy across suppliers and settlement periods. The proposed implementation date for P305 is 5th November 2015. The P305 Assessment Report sets out the requirements on parties and agents in relation to Demand Control Events. These include a requirement (D8.11) that the SVAA will report disconnection volumes to Suppliers and LDSOs

Comments:





DTC CP 3467 Changes to facilitate implementation of BSC Modification Proposal P305 (Version 3)


MRA 05 Nov 2015

Summary:

DTC CP 3467 intends to facilitate the implementation of BSC Modification Proposal P305, which was raised by National Grid in order to implement the conclusions of Ofgem’s Electricity Balancing Significant Code Review (EBSCR). DTC CP 3467 has been raised as a consequence of the MDB’s decision to reject DTC CP 3459A. It seeks to amend the D0018 Data Flow, and add 4 new Data Flows and 15 new Data Items, and therefore is identical to DTC CP 3459A except that it: i) No longer proposes to introduce the Dwwww flow; and ii) Omits Data Items originally proposed under CP 3459A that are no longer required. Please note that we have also taken this opportunity to update the description of two existing Data Items used in the flows suggested by this proposal. The updated descriptions simply recognise that the Data Items may be used in relation to Demand Control Events.

History:

BSC Modification Proposal P305 proposes to progress and implement the conclusions to Ofgem’s Electricity Balancing Significant Code Review, which will put in place a single, marginal imbalance price, introduce Reserve Scarcity Pricing and introduce pricing for Demand Control actions. P305 will introduce a method for recognising the cost of Demand Control actions in the calculation of imbalance prices and imbalance volumes. This method will require Supplier Volume Allocation (SVA) and Central Volume Allocation (CVA) parties and agents to share data with each other in order to estimate volumes of energy that are not consumed because of a Demand Control event and to make adjustments to suppliers’ metered volumes to ensure accurate allocation of energy across suppliers and settlement periods. ELEXON will implement P305 on 5th November 2015. The P305 Final Modification Report sets out the requirements on parties and agents in relation to Demand Control Events. In summary, the following activities will need to be supported by new and existing DTC flows and Data Items:

ntary demand side actions during Demand Control Events to supplier agents;

a revised calculation of AAs; and to share and use new Data Items in order to estimate HH

estimates of disconnected volumes and share these so they can be aggregated in order to adjust Suppliers’ metered volumes and balancing services volumes.

Comments:



ERS Industry Compliance Statement Detail (MAP CP 0221)


MAP CP 0221 Amending MAP15 to mandate resolving D0312 rejections


MRA 05 Nov 2015

Summary:

MAP CP 0221 seeks to mandate Suppliers to investigate the data contained within the rejected D0312 report and resolve as many outstanding issues as practicable.

History:

The Prepayment Allocation Process Expert Group (PAPEG) convened a D0312 workshop to identify the weaknesses of the current allocation process in terms of the Data Flow itself. PAPEG reviewed the viability of mandating working the D0312 rejection report, which provides a consolidated list of rejected D0312’s to the submitting Meter Operator. Analysis conducted in 2013 highlighted that 3,631,518 rejections had occurred, of which, 14.8% were prepayment. The high level of prepayment rejections means that the updated information within the Flow has not entered ECOES, and as such impacts the prepayment allocation process as transactions will not be able to be allocated. PAPEG agreed that changes to MAP15 should be raised. By mandating resolving rejected D0312s contained within the reports, it is hoped that the percentage of transactions which can be allocated using ECOES will increase.

Comments:





MAP CP 0222 Amending MAP15 to introduce a report detailing the number of D0312 rejections


MRA 05 Nov 2015

Summary:

This CP follows MAP CP 0221 and seeks to introduce a report detailing the number of rejected D0312s which have not been resolved within the mandatory window.

History:

The Prepayment Allocation Process Expert Group (PAPEG) convened a D0312 workshop to identify the weaknesses of the current allocation process in terms of the Data Flow itself. PAPEG reviewed the viability of mandating working the D0312 rejection report, which provides a consolidated list of rejected D0312’s to the submitting Meter Operator. Analysis conducted in 2013 highlighted that 3,631,518 rejections had occurred, of which, 14.8% were prepayment. The high level of prepayment rejections means that the updated information within the Flow has not entered ECOES and as such impacts the prepayment allocation process as transactions will not be able to be allocated. PAPEG consequently agreed that changes to MAP15 should be drafted and MAP CP 0221 was raised. MAP CP 0222 seeks to introduce a report for Suppliers as a monitoring mechanism to ensure that the rejected D0312s are being resolved within the mandatory window.

Comments:





MAP CP 0223 Amending MAP15 to implement Algorithm 5


MRA 05 Nov 2015

Summary:

MAP CP 0223 seeks to introduce a new Algorithm into the prepayment allocation matching procedure.

History:

Following the implementation of MAP CP 0198, the Prepayment Allocation Process Expert Group (PAPEG) reviewed the remaining Algorithms which were not implemented as part of the original CP due to the higher associated risk of allocating transactions to the incorrect Supplier. Algorithm 5 moves the transaction date by a fixed number of days in an attempt to match the Meter Serial Number provided by a Prepayment Metering Infrastructure Provider (PPMIP) with the correct Supplier held in ECOES to allocate the transaction to. During the discussions regarding Algorithm 5, a large amount of data analysis was conducted to ensure that the benefits and the risks of the Algorithm were fully understood. This resulted in a minor modification to the originally drafted Algorithm. The analysis indicated that Algorithm 5 applied to transactions older than 6months using +/- 5 days would provide the most accurate and beneficial enhancement to the allocation process as the data analysed by Supplier parties indicated that 73% of transactions would be correctly allocated. MAP CP 0223 seeks to introduce Algorithm 5 as a permanent feature in ECOES and is an output of PAPEG to enhance the current prepayment allocation process.

Comments:





MAP CP 0224 Amending MAP15 to implement an Algorithm 5 report


MRA 05 Nov 2015

Summary:

This CP follows MAP CP 0223 and seeks to introduce a new report based on Algorithm 5, detailing the transactions Meter ID and the Supplier which it would have been matched to if the transaction date was moved by +/- 40days

History:

Following the implementation of MAP CP 0198, the Prepayment Allocation Process Expert Group (PAPEG) reviewed the remaining Algorithms which were not implemented as part of the original CP due to the higher associated risk of allocating transactions to the incorrect Supplier. Algorithm 5 moves the transaction date by a fixed number of days in an attempt to match the Meter Serial Number provided by a Prepayment Metering Infrastructure Provider (PPMIP) with the correct Supplier held in ECOES to allocate the transaction to. During the discussions regarding Algorithm 5, a large amount of data analysis was conducted to ensure that the benefits and the risks of the Algorithm were fully understood and resulted in a minor modification to the originally drafted Algorithm. The analysis indicated that Algorithm 5 applied to transactions older than 6months using +/- 5 days would provide the most accurate and beneficial enhancement to the allocation process as the data analysed by Supplier parties indicated that 73% of transactions would be correctly allocated. PAPEG consequently agreed that changes to MAP15 should be drafted and MAP CP 0223 was raised. PAPEG agreed that moving the transaction date by +/- 40days would be too risky to implement as a permanent feature but that the individual party analysis that could be conducted on a report which detailed the Supplier which a transaction would be allocated if the date had been moved by +/- 40 days would be useful. MAP CP 0224 therefore seeks to introduce a report based on Algorithm 5, detailing the transactions Meter ID and the Supplier, which the transaction would have been matched to if the transaction date was moved by +/- 40days to enhance the current prepayment allocation process.

Comments:





MAP CP 0226 Amend MAP 18 to Improve Exception Handling in the GDCC (Alternative to MAP CP 0225)


MRA 05 Nov 2015

Summary:

This CP seeks to introduce a change to the GDCC and MAP18 in order to introduce an automated process to notify the sender of a Data Flow that it could not be processed, and could not be rejected via the normal DTN route. Rather, the sender of the Data Flow would be notified by an automatically generated email sent from the GDCC. Wording would need to be introduced into MAP18 to outline the automated email process, which has been included in Appendix 1. This change is an alternative solution to MAP CP 0225. This solution will implement a complete set of GDCC exception scenarios into the automated email process. The additional scenarios not included in MAP CP 0225 have not yet occurred in the GDCC.

History:

There are certain scenarios that can occur when Green Deal Market Participants send Data Flows to the GDCC and the Data Flow cannot be processed. The GDCC has not been developed to send a rejection via the DTN for these specific scenarios. Exception error codes are generated by the GDCC in these instances and emailed immediately to the GDCC Central Administration Service (CAS), who have one (1) Working Day to manually investigate and contact the sender to resolve the issues (as outlined in MAP 18). There are fourteen (14) separate exception error codes which occur for different reasons. Once contacted by the CAS, the relevant Market Participant will investigate, and are obliged via the Green Deal Access Arrangement Agreement (GDAA) to generate a revised Data Flow to the GDCC within three (3) Working Days.

Comments:





MAP CP 0232 Amending MAP14 to distribute unallocated Key transactions


MRA 05 Nov 2015

Summary:

MAP CP 0232 proposes to introduce a process into MAP14 - Procedure for the Allocation of PPM Payments Transacted Against an Incorrect Device to distribute Unallocated Key transactions, following a lessons learned exercise of the Smartcard and Token distribution process.

History:

Following the upheld appeal of MAP CP 0130 - Treatment of Unallocatable Prepayment Revenue v2, the MRA Executive Committee (MEC) agreed the formation of the Prepayment Allocation Process Expert Group (PAPEG). PAPEG was tasked to investigate all of the available options regarding the future of the unallocated monies following a failure to allocate using the MAP14 process. This change is the result of that work and seeks to introduce a process to distribute the Key Meter Type transactions which cannot be allocated.

Comments:





MAP CP 0233 Amending MAP15 to enhance the Transaction Routing Flag functionality


MRA 05 Nov 2015

Summary:

MAP CP 0233 proposes to enhance the Transaction Routing Flag (TRF) functionality to allow the flag to be raised against a period at the beginning or the end of a Supplier registration.

History:

The TRF was first implemented in ECOES in May 2012. The TRF helps to resolve situations where ECOES returns two or more MPANs for a transaction from a pre-payment meter. Once a transaction is received by a Prepayment Meter Infrastructure Provider (PPMIP) it will use ECOES to try to identify a Supplier to send the payment to. If ECOES returns two or more Suppliers the transaction will not be allocated and be detailed within the Multiple Supplier Reports (MSRs). When multiple Suppliers are returned to Pre-Payment Meter Infrastructure Providers (PPMIPs) they are not able to allocate the transaction. The TRF allows a Supplier to renounce a claim for a transaction once the Supplier identified it has no right to the money but cannot rectify the data in ECOES. At PAPEG_15_0413 a number of options were provided to make amendments to the TRF process and functionality. At present a Supplier can only opt out of the whole registration period for which they are associated to a pre-payment meter. PAPEG discussed the requirement that in certain situations, the ability to opt out of a specific period at the beginning or the end of a registration period should be available. PAPEG agreed to introduce this functionality and to make amendments to ECOES and MAP15 - ECOES to allow Suppliers to opt out of a period at the beginning or the end of a registration period.

Comments:





MAP CP 0235 Amend MAP13 to specify invoicing frequency


MRA 05 Nov 2015

Summary:

MAP CP 0235 proposes to limit Debt Assignment Protocol (DAP) related invoices to one invoice per Supplier pair per month.

History:

As a result of an Ofgem initiative, the DAP process has been streamlined to encourage more customers who have a debt being recovered via a Prepayment Meter (PPM) to switch Supplier to enable them to obtain the best tariff. Previously only 0.5% of customers decided to go through the DAP but this figure is expected to increase significantly now the changes to the process are live. In order to minimise the number of invoices issued relating to the DAP process and therefore minimise the operational overhead, this CP seeks to limit the number of invoices to one per supplier pair per month under MAP13.

Comments:





MAP CP 0238 Erroneous Transfers escalations


MRA 05 Nov 2015

Summary:

The escalation procedure as set out under MAP10 “The Procedure for Resolution of Erroneous Transfers” does not specify the number of Working Days by which the MRA Supplier Contract Manager should action the query. This Change Proposal (CP) seeks to introduce timescales for action by the MRA Supplier Contract Manager into MAP 10.

History:

The escalation procedure within MAP10 - The Procedure for Resolution of Erroneous Transfers, currently shows a MRA Supplier Contract Manager as the final escalation point, but with no specified timescales to action escalated queries. As a result, some queries can remain unresolved for extended periods of time. Examples of escalated ET queries which relates to this issue include cases where the New Supplier is the initiating Supplier, as set out in section 3.1.2 of MAP 10:

the Old Supplier fails to register the customer within the timescales as set out in section 3.1.2;

required in order to close down ET queries in Supplier systems; and ther with a risk

that the initiating Supplier may bear Settlement costs for a prolonged erroneous period. Although queries that remain unresolved after they've reached the MRA Supplier Contract Manager escalation stage can be escalated to Gemserv, this is an extreme approach to resolve an operational query. Clearly defining required timescales for each stage of the escalation process should help to support swifter ET resolution. Sections 2.5 and 2.7 of MAP10 include Escalation Summaries for actions to be taken to resolve issues within the Erroneous Transfer Procedure and for re-registration of the relevant MPAN respectively.

Comments:





MAP CP 0239 Amending MAP14 to mandate the Redirected Report frequency


MRA 05 Nov 2015

Summary:

MAP CP 0239 proposes to formalise the frequency with which Redirected Reports are issued to Suppliers

History:

Following the upheld appeal of MAP CP 0130 - Treatment of Unallocatable Prepayment Revenue v2, the MRA Executive Committee (MEC) agreed the formation of the Prepayment Allocation Process Expert Group (PAPEG). PAPEG were tasked with developing solutions for the redistribution of unallocated prepayment transactions and enhancing the current allocation process. PAPEG identified a difference in the production frequency of the Redirected Reports and agreed that to better enable Supplier’s to process the reports, a standardised frequency to produce the reports should be implemented.

Comments:





MAP CP 0244 Amendment to MAP18 to change the processing times for GD Charges


MRA 05 Nov 2015

Summary:

The PTSC group agreed on 13th May 2015 to raise a change proposal to amend the GDAA wording in respect of the timescale for sending updated charges to the GDCC for onward progression to Suppliers. The PTSC group noted that consequential changes would be required to MAP18, the Green Deal Operational Procedures (GDOPs) and the GDCC functionality to accommodate this change. Therefore, this change amends MAP18 – GDCC, Section 4.12 ‘Green Deal Charge Periods’ to clarify that any updated charge periods sent to the GDCC should be at least 12 Working Days from the Deemed GDCC Receipt Date as per the redlined drafting in Appendix 1. The cost to amend the GDCC processing rules for updated Green Deal charge periods on D0322 Data Flows will be £2,263.

History:

Early repayment, both partial and full, may result in compliance issues for Green Deal Arrangements Agreement (GDAA) parties within the required timescales that sit within Consumer Credit Act (CCA) 1974 legislation. This Change Proposal has been raised to provide a solution that would improve GDAA parties’ ability to comply with CCA obligations and minimise risks of consumer detriment. This issue has been discussed at various meetings and working groups since 2014 and requires a consequential change to MAP18, borne out of an amendment agreed under the GDAA. A change to the functionality of the GDCC has also been raised.

Comments:





MAP CP 0247 MAP CP 0247 - Amendment to a Clause reference within MAP04, Section 6


MRA 05 Nov 2015

Summary:

Clause 32, Records, Audit and Non-Functional Requirements, should be referenced in Section 6 of MAP04: 6 SETTLEMENTS AUDIT REQUIREMENTS All documents associated with a particular Retrospective Manual Amendment should be retained in keeping with the general requirements under Clause 32 of the MRA.

History:

Within MAP04, it states that all documents associated with a particular Retrospective Manual Amendment should be retained in keeping with the general requirements under Clause 30 of the MRA. Clause 30 of the MRA is Assignment of Outstanding Charges from the Old Supplier to the New Supplier. Therefore, the correct Clause needs to be referenced.

Comments:





MAP CP 0248 Amending MAP17 to update the MDB Constitution to reference Smaller Suppliers


MRA 05 Nov 2015

Summary:

Following the Code Review Expert Groups (CREGs) review of the MDB Constitution, this change has been developed to introduce an amended version of the MDB Constitution into MAP17 - Issues Resolution and Change Management. The amended MDB Constitution includes updating the Smaller Supplier membership arrangements following discussions at CREG and MDB.

History:

The MDB Constitution was reviewed for a number of reasons. In particular, in January 2014, the MRA Executive Committee (MEC) discussed the general membership and voting arrangement of MDB as being an area for review. As a result, a review of the MDB Constitution was directed for inclusion within the scope of CREG Stage 3. There are two main reasons why the MDB Constitution was considered for review by MEC: 1. A change in the market following an acquisition meaning that a Supplier quickly developed to a much larger Supplier with many more MPANs; and 2. An increase in smaller Supplier, and additional Independent Distribution Network Operators (IDNOs) market participation over the last few years. Since then, CREG issued a Request for Information (RFI), and attended a smaller Supplier presentation and feedback session. Options were then discussed at CREG which led to two changes being raised into the MRA Change Process, including this change. This change covers the amended MDB Constitution into MAP17, and a related change (MRA CP 0233) introduces references to MDB and their delegated powers in the MRA.

Comments:





MAP CP 0249 MAP18 SEG Recommended Changes


MRA 05 Nov 2015

Summary:

This CP will allow for introduction of initial changes that will provide the baseline upon which further changes will be developed for implementation in February 2016, once the wider market solutions are agreed. In summary, these changes include: 1) Updates to section 2 that clarify the definitions of users throughout to clarify the context in which terms are used; 2) Update to Section 3 to further define the role of the CAS 3) Expand section 3.2 to include further assurance and monitoring activities in line with the findings of the risk assessment 4) Addition of a new section to provide a mechanism for enabling users once they are authorised 5) Small non-material changes throughout to provide further clarity regarding user rights and obligations

History:

The Security Expert Group (SEG) was established to review, investigate and develop potential governance, process and technical enhancements to ensure the optimal security of the personal data held within the systems governed by MRASCo. In order to identify the main security risks to the systems governed by MRASCo, The MRA Executive Committee (MEC) commissioned Red Island Consultancy to conduct a Risk Assessment to act as a basis for SEG to work from. The Risk Assessment had identified 23 risks relating to MRASCo systems. Following a review of the outcomes of the Risk Assessment, SEG identified a number of areas where the drafting of MAP18 might be amended to support a more aligned and robust approach to information security. As a result, an incremental approach has been undertaken to amend the information security measures in MAP18 due to the need to develop more complex solutions in some areas.

Comments:





MAP CP 0250 Removal of contractual arrangements from MAP14


MRA 05 Nov 2015

Summary:

MAP CP 0250 proposes to remove the contractual arrangements between PPMIPs and Suppliers with regard to Misdirected payments from MAP14. Therefore, the following will be removed from the MAP: To enable a PPMIP to recover the additional costs associated with resolving Misdirected Payments under this MAP, the Supplier registered to a relevant Metering Point as at the date of the transaction shall pay an additional charge as levied by the PPMIP in accordance with the contractual arrangements between them.

History:

The Prepayment Allocation Process Expert Group (PAPEG) was tasked with developing solutions for the redistribution of unallocated prepayment transactions and enhancing the current allocation process. Whilst discussing the distribution process for unallocated Key transactions, a question was raised regarding the contractual arrangements between Suppliers and Prepayment Metering Infrastructure Providers (PPMIPs). PAPEG concluded that contractual agreements should not be included within formal governance due to the potential differences in the contracts. The Cost of Transactions section of MAP14 - Procedure for the Allocation of PPM Payments Transacted Against an Incorrect Device outlines that Suppliers shall pay additional charges levied by the PPMIP in accordance with the contractual arrangements. As such this change seeks to remove the Cost of Transactions section of the MAP to ensure that contractual arrangements are not included within formal governance.

Comments:





MAP CP 0252 Identifying whether a metering system is Whole Current or Current Transformer


MRA 05 Nov 2015

Summary:

MAP CP 0252 seeks to introduce a new MRA Agreed Procedure (MAP) for Suppliers to provide extracts of Profile Class 5 to 8 MPANs and associated metering information.

History:

Following the approval of P322 - Revised Implementation Arrangements for Mandatory Half Hourly Settlement for Profile Classes 5 - 8, Suppliers must migrate Profile Class 5-8 MPANs with Advanced Meters to Half Hourly (HH) within 45 business days of a Change of Supplier (CoS) event. Currently, Suppliers are unable to offer customers correct HH contracts in advance of the CoS as they do now know if the metering system is Current Transformer (CT) or Whole Current (WC).

Comments:





MAP CP 0253 MAP18 Drafting Clarifications


MRA 05 Nov 2015

Summary:

This CP will allow for the introduction of housekeeping changes, alongside those introduced by MAP CP 0249, and will provide the baseline upon which further change will be developed for implementation in February 2016, once all wider market solutions are agreed. In summary, housekeeping changes shall: 1) Clarify rights and obligations 2) Provide further clarity regarding the status of users of the Green Deal Central Charge (GDCC) Database 3) Ensure appropriate terms are clearly defined 4) Make minor non-material changes which clarify operational processes 5) Remove some explanatory text that is not relevant to MRA governance, and does not clarify parties obligations 6) Removal of content of Annex G, which replicates the content of the Data Transfer Catalogue (DTC) in relation to GDCC response codes

History:

SEG was established to review, investigate and develop potential governance, process and technical enhancements to ensure the optimal security of the personal data held within the systems governed by MRASCo. In order to identify the main security risks to the systems governed by MRASCo, MEC commissioned Red Island Consultancy to conduct a Risk Assessment to act as a basis for SEG to work from. Following a review of the outcomes of the Risk Assessment, SEG identified a number of areas where the drafting of MAP18 could be amended to support a more aligned and robust approach to information security, which resulted in MAP CP 0249 being raised. As a result of discussions with a number of stakeholders regarding the drafting of the MRA Agreed Procedures (MAPs), a number of areas within MAP18 were identified as requiring further clarification. These housekeeping amendments have been drawn together into a single change proposal for consideration by parties.

Comments:





MAP CP 0257 Amend MAP18 GDCC Exception Handling Wording Introduced by MAP CP 0226


MRA 05 Nov 2015

Summary:

The proposed solution updates the drafting of MAP18 to reflect that the Green Deal Central Charge (GDCC) Data Flow exception handling process will be carried out manually by the GDCC Operator. Appendix 1 shows the full redlined drafting.

History:

MAP CP 0226 seeks to amend the wording of MAP18, to introduce an automated process that the GDCC carries out when in receipt of Data Flows which cannot be processed, known as exceptions. The change was agreed by MDB on 30th April 2015 for inclusion in the next release of the GDCC, which would be the November release (GDCC Release 9). Following agreement of this CP, a Department of Energy and Climate Change (DECC) announcement stated that Government funding for the Green Deal would end. Consequently, the MRASCo Board decided not to fund any changes to the GDCC system which would cause compliance issues if not implemented.

Comments:





MAP CP 0258 Amending MAP17 to update the MDB Constitution for Distribution Businesses


MRA 05 Nov 2015

Summary:

This Change Proposal is designed to reference the amended MRA Development Board (MDB) Constitution in MAP17 so it will fall under MRA change process governance. In particular, this change would move the MDB Constitution from a stand-alone section within the Terms of Reference, into a new appendix in MAP17. A related CP (MRA CP 0233) would also introduce a new section into the MRA under Clause 6.53A. The amended MDB Constitution includes updating the Distribution membership arrangements to allow for Distribution Network Operators to represent themselves, and independent Distribution Network Operators having one representative.

History:

The MDB Constitution was reviewed for a number of reasons. In particular, in January 2014, the MRA Executive Committee (MEC) discussed the general membership and voting arrangement of MDB as being an area for review. As a result, a review of the MDB Constitution was directed for inclusion within the scope of CREG Stage 3. There are two main reasons why the MDB Constitution was considered for review by MEC: 1. A change in the market following an acquisition meaning that a Supplier quickly developed to a much larger Supplier with many more MPANs; and 2. An increase in smaller Supplier, and additional Independent Distribution Network Operators (IDNOs) market participation over the last few years. Since then, CREG issued a Request for Information (RFI), and discussed options to be raised into the MRA Change Process. One of these options was to allow Distribution Businesses to represent themselves.

Comments:



ERS Industry Compliance Statement Detail (P300)


P300 Introduction of new Measurement Classes to support Half Hourly DCUSA Tariff Changes


BSC 05 Nov 2015

Summary:

P300 was raised by Electricity North West Limited(the proposer). It proposes to make the following changes to the Measurement Classes for customers with maximum demand of less than 100kW: • add Measurement Class F, for Domestic HH CT and non-CT metered customers that have aggregate billing; • add Measurement Class G, for Non-Domestic HH non-CT metered customers that have aggregate billing; and • rename Measurement Class E to identify that it is for HH CT metered customers thathave site specific DUoS bills. P300 enables aggregate DUoS billing and does not require any consumer move to HH settlement. The changes proposed also do not mandate that suppliers use the new Measurement Classes. They may continue to use Measurement Class C (for customers with maximum demand 100kW or more) or the re-named Measurement Class E.

History:

Smart meters are currently being rolled out for gas and electricity and are capable of recording half-hourly (HH) consumption and can be read remotely. The more accurate and timely data delivered from these meters is expected to facilitate lower consumer bills and stronger competition in the retail market. The industry considers that the current electricity distribution use of system (DUoS) charges are a disincentive for customers to move to HH settlement because: •The current HH tariff may not be appropriate for all customer types and •Currently, all HH settled customers receive site specific bills. Distribution Network Operators (DNOs) have identified they would need to upgrade their systems to process a significant increase in site specific bills. Distribution Connection and Use of System Agreement (DCUSA) change proposal DCP179 proposed to amend the existing tariff structure under the Common Distribution Charging Methodology by introducing new HH metered tariffs. The new tariffs would: •Be specifically for customers in Profile Classes (PC)1-8; •Remove discrepancies between non-half hourly (NHH)and HH tariffs, and •Enable aggregate billing for specific groups of HH metered customers.

Comments:





P305 Electricity Balancing Significant Code Review Developments


BSC 05 Nov 2015

Summary:

P305 has been raised to progress the outcomes of the Electricity Balancing Significant Code Review (EBSCR), and proposes to implement the EBSCR conclusions ahead of winter 2015/16, which consists of the following areas: -A reduction in the Price Average Reference (PAR) and Replacement PAR (RPAR) values to better reflect the marginal cost of balancing energy for a given Settlement Period. - A single imbalance price using the existing Main Price calculation. - Introduction of a Reserve Scarcity Price (RSP) function for Short Term Operating Reserve (STOR) actions to better reflect the prevailing scarcity in the market at the time of their use. - Introduction of Demand Control actions into the imbalance price, priced at the Value of Lost Load (VoLL), and an imbalance volume correction process to amend participants’ positions to account for such actions

History:

National Grid raised P305 on 30 May 2014. The Panel agreed to submit P305 to an Assessment Procedure, during which it was issued for industry Impact Assessment and the Workgroup’s Assessment Procedure Consultation. The Workgroup recommended that the Alternative Modification should be approved, and its Assessment Report was presented to the Panel on 12 February 2015. The Panel initially recommended that both the Proposed and Alternative Modifications should be rejected, and issued P305 for its Report Phase Consultation. The Panel made its final recommendation that both the Proposed and Alternative Modifications should be rejected at its meeting on 12 March 2015. The Authority approved the P305 Proposed Modification on 2 April 2015 for implementation on 5 November 2015 as part of the November 2015 Release.

Comments:





P309 Facility to enable BSC Parties to select either replacement contract notifications or additional contract notifications


BSC 05 Nov 2015

Summary:

P309 proposes to give BSC Parties the ability to specify that either replacement contract notifications or additional contract notifications are associated with an Energy Contract Volume Notification Agent (ECVNA) Authorisation. The aim is to mitigate the risk that replacement notifications might be submitted instead of additional notifications, or vice versa.

History:

P309 was raised by RWE npower on 26 June 2014. The Initial Written Assessment (IWA) was presented to the Panel at its meeting on 10 July 2014. The Panel agreed to submit P309 to a four month Assessment Procedure, however a two-month extension was granted at the 13 November 2014 Panel meeting so the Workgroup could consider the solutions and legal text further. The P309 Assessment Report was presented to the Panel on 15 January 2015. The Panel initially unanimously recommends that P309 Alternative solution should be approved. P309 was issued for its Report Phase Consultation on 16 January 2015, with responses due 3 February 2015. The Draft Modification Report was presented to the Panel at its meeting on 12 February 2015. The Panel unanimously recommended that P309 Alternative solution should be approved and P309 Proposed solution should be rejected. P309 was issued to the Authority for decision on 12 February 2015.

Comments:





P319 Removal of annual RMP review from PAF


BSC 05 Nov 2015

Summary:

P319 seeks to remove the requirement for ELEXON to provide an initial Risk Management Plan (RMP) at Qualification and annual review these. The information contained in these annual reviews is already communicated to Parties through other means, and so does not provide Parties with new information.

History:

P319 was raised by the Panel at its meeting on 12 March 2015. The Panel unanimously agreed that P319 should be progressed directly into the Report Phase and should be treated as a Self-Governance Modification Proposal with an initial recommendation that the Modification be approved. The Panel’s Report Phase Consultation was issued on 13 March 2015 with responses invited by Tuesday 7 April 2015. The Panel considered the P319 Draft Modification Report and responses to the Report Phase Consultation at its meeting on 14 May 2015. The Panel unanimously approved P319 for implementation on 5 November 2015. BSC Parties had 15 Working Days to appeal the Panel’s approval of P319. This appeal window closed on 5 June 2015. No appeals were received, and so P319 will be implemented in accordance with the Panel’s determination on 5 November 2015 (November 2015 BSC Systems Release).

Comments:





P322 Revised Implementation Arrangements for Mandatory Half Hourly Settlement for Profile Classes 5-8


BSC 05 Nov 2015

Summary:

P322 proposes new arrangements to migrate sites, classed as Profile Class (PC) 5-8 with Advanced Meters installed, to Half Hourly (HH) Settlement under the P272 obligations. P322 has the following features: Required start and end dates to facilitate a phased approach to implementation Performance Monitoring, most likely through the existing Performance Assurance Framework (PAF) An implementation approach, which considers approved Modification P272 and possible amendment to the P272 Implementation Date by the Authority

History:

RWE npower raised P322 on 28 April 2015, and requested that it be treated as an Urgent Modification. The Panel agreed that P322 should be treated as an Urgent Modification at an ad-hoc meeting on 29 April 2015, and the Authority approved the request for urgency on 7 May 2015. The Panel at its meeting on 11 June 2015 considered the Draft Modification Report, which included the Workgroup’s assessment and its recommendation that the Alternative Modification should be approved. The Panel made its final recommendation that the Alternative Modification should be approved. It also considerde the views on the P272 Implementation Date and recommended that this should be 1 April 2017. On 24 June 2015, the Authority decided to approve: P322 for implementation on 3 August 2015 as a Standalone Release; and, in accordance with Section F, Paragraph 2.11.7, the BSC Panel’s request to extend the P272 ‘Mandatory Half-Hourly Settlement for Profile Classes 5-8’ Implementation Date to 1 April 2017. P322 was implemented on 3 August 2015.

Comments:





P323 Enabling inclusion and treatment of SBR in the Imbalance Price


BSC 05 Nov 2015

Summary:

P323 proposes to enable the value of Supplemental Balancing Reserve (SBR) to be included in the imbalance price calculation without affecting Balancing Mechanism (BM) cash flows. The Proposer seeks to have this in place by 5 November 2015 in line with the implementation of approved Modification Proposal P305 ‘Electricity Balancing Significant Code Review Developments’. This is because it is necessary that other elements of P305 are in place (e.g. the Value of Lost Load (VoLL) price) and to avoid delays so that the market receives the appropriate signals.

History:

National Grid raised P323 on 26 June 2015. The Panel considered the Initial Written Assessment at its meeting on 9 July 2015 where it agreed that P323 be placed into a two month Assessment Procedure. The Panel considered the Assessment Report on 10 September 2015 and gave its initial views on P323, initially recommending that it should be approved. The Report Phase consultation for P323 was issued on 11 September 2015, with responses due by 28 September 2015. ELEXON presented the P323 Draft Modification Report to the BSC Panel at its meeting on 8 October, which recommended approval. On 15 October 2015, the Authority approved P323 for implementation on 5 November 2015.

Comments:





P327 Clarifications to P305 legal text


BSC 05 Nov 2015

Summary:

P305 proposes minor changes to the approved legal text for P305 to correct some minor inconsistencies and improve the clarity of some new definitions.

History:

P327 was raised by the BSC Panel at its meeting on 10 September 2015. At this meeting, the Panel unanimously agreed that P327 should be progressed and approved as a Fast Track Self-Governance Modification. BSC Parties have a 15 Working Day period in which to object if they disagree with the Panel’s decision that P327 should be progressed as a Fast Track Modification. This objection period will close on 1 October 2015. If no objection is notified in this time, the Panel’s decision will be final and P327 will be implemented on 5 November 2015 as part of the November 2015 BSC Systems Release.

Comments:



ERS Industry Compliance Statement Detail (WPPS CP

0122)


WPPS CP 0122 Amendments to Working Practice 124


MRA 05 Nov 2015

Summary:

WPPS CP 0122 proposes a minor amendment to WP124, following the significant rewording implemented on 26th February 2015. The minor rewording seeks to clarify the process to deal with Mis-Directed Payments following an Erroneous Transfer

History:

Following the acceptance of WPPS CP 0121, the Prepayment Metering Forum (PPMF) reviewed Working Practice 124. The review highlighted that the Working Practice could be made clearer in terms of the process, following an Erroneous gain or loss, which means that the Supplier for that customer is unknown, resulting in mis-allocated transactions. It became clear that large amounts of mis-allocations were due to Erroneous Transfers and as such PPMF agreed that the wording should be clarified. PPMF 15-01, held on 4th February 2015, agreed that the Principle 11 and Scenario 7 should be updated and progressed via the MRA Change Process.

Comments:





CP1434 Amend the three digit numeric Line Loss Factor Class (LLFC) Id to an Alphanumeric LLFC Id


BSC 30 June 2016

Summary:

CP1434 proposes to amend the format of the Line Loss Factor Class (LLFC) Identifier (ID) from a three-digit integer value to a three-digit alphanumeric value (consisting of the digits 0-9 and the capital letters A-Z excluding I and O). This will increase the number of LLFCs from 999 to 39,303.

History:

CP1434 was raised by Scottish and Southern Energy Power Distribution on 16 February 2015 and has been issued for CP Consultation. At its meeting on 28 April 2015, the SVG recommended by majority that CP1434 should be deferred and a CP Workgroup established to explore other options. At its meeting on 14 May 2015, the Panel agreed to defer a decision but elected to issue an industry Request for Information to seek answers to the SVG’s questions. At its meeting on 2 June, the SVG recommended by majority that CP1434 should be rejected. The Panel approved CP1434 at its meeting on 11 June 2015 for implementation on 30 June 2016 as part of the June 2016 BSC Systems Release.

Comments:





DTC CP 3469 Supplier to Supplier instance of D0010 ‘Meter Readings’ flow


MRA 30 June 2016

Summary:

DTC CP 3469 seeks to add the Supplier to Supplier instance to the D0010 Data Flow, and add the following to the flow notes: NHH - This flow is for notification of validated/invalid non half-hourly meter readings and includes optional fields for any site visit check information. This flow i

Documents

EDW Technology Limited...BSC CP1441 Allowing the Peer Comparison technique to be reported on a Supplier Agent level BSC CP1442 Clarifying the application process for Metering Dispensations