Central Volume Allocation Agency (CVA) Metering Systems | Supplier Volume Allocation Agency (SVA) Metering Systems |
BSCCo | BSCCo |
LDSO | LDSO |
Registrant | SVAA |
CDCA | Suppliers |
Panel | HHDAs |
| Panel |
CVA Metering Systems | SVA Metering Systems |
BSCP15 - BM Unit Registration | BSCP38 - Authorisations |
BSCP25 - Registration of Transmission System Boundary Points, Grid Supply Points, GSP Groups and Distribution Systems Connection Points | BSCP68 - Transfer of Registration of Metering Systems between CMRS and SMRS |
BSCP38 - Authorisations | BSCP503 - Half Hourly Data Aggregation For Metering Systems Registered in SMRS. |
BSCP68 - Transfer of Registration of Metering Systems between CMRS and SMRS | BSCP508 - Supplier Volume Allocation Agent. |
BSCP75 - Registration of Meter Aggregation Rules for Volume Allocation Units | BSCP509 - Changes to Market Domain Data |
BSCP515 - Licensed Distribution | BSCP515 - Licensed Distribution |
BCA | Balancing and Settlement Code Change Administrator |
BSCCo | BSC Company |
BSCP | Balancing and Settlement Code Procedure |
CMRS | Central Meter Registration Service |
Code | Balancing and Settlement Code |
CDCA | Central Data Collection Agency |
CVA | Central Volume Allocation |
CVA LLF(s) | CVA Line Loss Factor(s) |
EFD | Effective From Date |
GSP | Grid Supply Point |
GSPG | Grid Supply Point Group |
HHDA(s) | Half Hourly Data Aggregator(s) |
Id | Identifier |
LDSO | Licensed Distribution System Operator1 |
LLF | Line Loss Factor |
LLFC Id(s) | Line Loss Factor Class Identifier(s) |
LLFC(s) | Line Loss Factor Class (es) |
MDD | Market Domain Data |
MSID | Metering System Identifier |
SMRS | Supplier Meter Registration Service |
SVA | Supplier Volume Allocation |
SVA LLF(s) | SVA Line Loss Factor(s) |
SVAA | Supplier Volume Allocation Agent |
WD | Working Day |
Extra High Voltage (EHV) | As defined in the LDSO’s approved LLF methodology. |
Embedded LDSO | A LDSO operating an independent distribution network connected to a Host LDSO’s distribution network2. e.g. This includes both independent LDSOs; and Host LDSOs that are operating outside their geographical area. |
Day (Generic) | As defined in each Distribution System Operator’s Methodology Statement. |
Generic LLF | The adjustment factor applied to the readings from a (group of) metering system(s) to adjust for losses on the distribution network and calculate the associated amount of energy at the GSP. |
LLFC Group (Generic) | A group of Line Loss Factor Classes that share the same generic set of Line Loss Factors. |
Night (Generic) | Hours of the Settlement Day not covered by Day (Generic). |
Host LDSO | A LDSO operating a distribution network that is directly connected to the Transmission System in their own distribution licence area. |
High Voltage (HV) | As defined in the LDSO’s approved LLF methodology excluding those high-voltage metered sites defined as EHV sites. |
Low Voltage (LV) | As defined in the Special Conditions of a distribution licence granted pursuant to section 6(1)(c) of the Electricity Act 1989. |
Manifest error: Retrospective changes | An unambiguous error in the application of the approved methodology, in the calculation input data or corruption of the LLF values in the submission process in such a way that there is a material impact on Settlement or a material impact to the advantage or detriment of the customer. |
Material impact: Retrospective changes
Mirror/Mirroring | An impact or estimated impact that has a value or estimated value greater than or equal to the Materiality Threshold for rectification of a valid Trading Dispute (as defined in BSC Procedure BSCP11). Where the Embedded LDSO replicates the Generic Line Loss Factors of the relevant Host LDSO for their own specified LLFCs for the GSP Group. |
Non-Technical Losses | Losses other than Technical Losses. |
Registrant | See BSC Annex X-1 |
Remote Audit | An audit that is not performed at the LDSO’s offices but is performed using data requests to review records and conduct interviews remotely |
Site Specific LLF | Where the Line Loss Factor is calculated for an individual Metering System and represents distribution losses specific to Metered Volumes measured by that Metering System. |
Site Specific: Material Change | A Material Change (that occurs mid year) to the physical plant, apparatus, or distribution network that causes a significant change to the Technical Losses specific to the Metered Volumes measured by the Metering System as determined by the Panel. |
Site Specific: Relevant Change | A significant change to the physical plant, apparatus, distribution network, or capacity that causes a change to the Line Loss Factors. This is used to determine whether Site Specific LLFs shall be recalculated for the annual LLF submission. |
Technical Losses | Technical Losses are losses caused by the intrinsic electrical characteristics internal to the power system and consist mainly of power dissipation in electrical system components such as transmission lines, power transformers and measurement systems. |
REF. | WHEN | ACTION | FROM | TO | INFORMATION REQUIRED | METHOD |
2.1.1 | By 1 August prior to the relevant BSC year | Submit proposed methodology and MSAD, or MSAD only where there has been no change since the methodology was last approved. | LDSO | BSCCo
| MSAD and methodology or MSAD confirming continued use of approved methodology in accordance with Appendix 1. | Email or other electronic means |
2.1.2 | Within 2 WD of 2.1.1 | Acknowledge receipt of methodology and MSAD, or confirmation that there has been no change since the methodology was last approved. If the methodology has not changed, proceed to Ref (2.1.6) below. Or if incomplete information has been received from LDSO contact LDSO to advise of any further information required; or advise LDSO that no methodology has been submitted. | BSCCo | LDSO
| Confirmation of receipt and notification of any initial concerns; or notification of failure to submit methodology. | Email, telephone or other electronic means |
2.1.3 | Within 5 WD of 2.1.1 | Review methodology for compliance with the LLF Methodology Principles in accordance with Section 3.1 and provide draft report highlighting any non-compliance(s); or confirmation of continued use of approved methodology has been submitted. | BSCCo | LDSO
| Methodology, MSAD, draft LDSO report, any non-compliances or confirmation of continued use of approved methodology. | Email or other electronic means |
2.1.4 | Within 5 WD of 2.1.3 | Resolve any identified non-compliance(s) and submit updated methodology and MSAD; or submit methodology and MSAD if not submitted by deadline; or submit MSAD confirming continued use of existing approved methodology. | LDSO | BSCCo | MSAD, updated methodology, evidence of resolved non-compliance(s), methodology or MSAD confirming continued use of approved methodology. | Email, telephone or other electronic means |
2.1.5 | Within 15 WD of 2.1.1 | If non-compliance(s) have been identified, review submission in Ref (2.1.4). Provide report with confirmation of compliance or non-compliance. | BSCCo | LDSO | LDSO report. | Email, telephone or other electronic means |
2.1.6 | To meet Panel requirements | Submit a final report to Panel stating: (a) Recommendations for the approval of each methodology with no non-compliance(s) or corrected non-compliance(s); or (b) Any continued non-compliance(s); or (c) Any failures to submit methodology or confirmation of continued use of approved methodology. | BSCCo | Panel | Final report. | Email or other electronic means |
2.1.7 | Within 1 WD of 2.1.6 | Review report submitted in Ref (2.1.6) and: Approve methodologies with no outstanding non-compliance(s); and Note any non-compliance(s); and Note any failures to submit a methodology or confirmation of continued use of existing approved methodology. | Panel | BSCCo | Final report and Panel decision. | - |
2.1.8 | Within 5 WD of 2.1.7 | Notify each LDSO stating whether the Panel: Approved the methodology; or Noted any non-compliance(s); or Noted the failure to submit a methodology; or Noted the failure to submit confirmation of continued use of existing approved methodology. | BSCCo | LDSO | Notification detailing the Panel’s decision. | Email or other electronic means |
2.1.9 | To meet PAB requirements | Provide report detailing non-compliance(s) or failures to submit a methodology or failure to confirm continued use of existing approved methodology. | BSCCo | PAB | Report detailing non-compliance(s) and failures. | Email or other electronic means |
REF. | WHEN | ACTION | FROM | TO | INFORMATION REQUIRED | METHOD |
2.2.1 | By 1 August prior to relevant BSC year | If Embedded LDSO intends to use their own methodology they must submit proposed methodology and MSAD or MSAD only where there has been no change since the methodology was last approved. | Embedded LDSO | BSCCo | Confirmation of Mirroring Host or Embedded LDSO methodology and MSAD, in accordance with Appendix 2. | Email or other electronic means |
2.2.2 | Within 2 WD of 2.2.1 | Acknowledge receipt of notification to Mirror. Or where incomplete information received from Embedded LDSO contact Embedded LDSO to advise of any further information required. | BSCCo | Embedded LDSO | Confirmation of receipt and notification of any initial concerns. | Email, telephone or other electronic means |
2.2.3 | To meet Panel requirements | Submit a Panel paper stating: (a) The Embedded LDSO shall Mirror Host or Embedded LDSO methodology (or methodologies). (b) Any failures to submit notification to Mirror Host or Embedded LDSO methodology. | BSCCo | Panel | Report. | Email or other electronic means |
2.2.4 | Within 1 WD of 2.2.3 | Review report submitted in Ref (2.2.3) and: Note any interaction with Host or Embedded LDSO Methodologies reviewed in 2.1.7 and any non-compliance(s); and Note any failures to notify BSCCo that the Embedded LDSO will Mirror Host or Embedded LDSO methodology (or methodologies). | Panel | BSCCo | Report detailing Panel decision. |
|
REF. | WHEN3 | ACTION | FROM | TO | INFORMATION REQUIRED | METHOD |
2.3.1 | By 1 August prior to the relevant BSC year | If required, send request to the relevant Host LDSO for boundary equivalent LLF values at the boundary between a Host LDSO and Embedded LDSO within the same GSP Group, to enable the Embedded LDSO to calculate Site Specific LLFs. | Embedded LDSO | Host LDSO | Embedded LDSO boundary equivalent profile(s) and other information required by the relevant Host LDSO. This should be agreed by the Host LDSO and Embedded LDSO prior to this deadline. | Email or other electronic means |
2.3.2 | Within 2 WD of Ref (2.3.1) | Acknowledge receipt of LLF request.
Or if incomplete information has been received from Embedded LDSO, request outstanding information. | Host LDSO | Embedded LDSO | Confirmation of receipt and notification of any initial concerns. | Email or other electronic means |
2.3.3 | By 1 September | If LLF methodology has been approved, submit data request for Remote Audit or propose dates to conduct a site visit. If LLF methodology has not been approved, submit data request for Remote Audit or agree site visit dates as soon as any outstanding non-compliance(s) have been resolved. | BSCCo | LDSO | Data request4 or dates for site visit. | Email, telephone or other electronic means |
2.3.4 | By 10 September | If a site visit is required, agree date(s) with BSCCo. Where a date has not been agreed by this time BSCCo shall determine a suitable date for the site visit. If a data request for Remote Audit has been provided, confirm that the data can be provided by 30 September. | LDSO | BSCCo | Data request or dates for site visit. | Email, telephone or other electronic means |
2.3.5 | By 1 October | If applicable, provide calculated boundary equivalent LLFs requested in Ref (2.3.1).5
| Host LDSO | Embedded LDSO | LLF values. | Email or other electronic means |
2.3.6 | Within 2 WD of Ref (2.3.5) | If applicable, acknowledge receipt of LLF values. | Embedded LDSO | Host LDSO | Confirmation of receipt. | Email or other electronic means |
2.3.7 | By 30 September
or
31 October for Embedded LDSOs submitting Site Specific LLFs | Submit calculated LLFs6 in accordance with the approved methodology. This should be in the form of a completed CSAD7 signed by an authorised signatory as well as a completed CSAD Appendix 5. If you are a Host LDSO, submit any calculated boundary equivalent LLFs requested in Ref (2.3.1). Additionally, if there has been a change to a Line Loss Factor Class (LLFC) for an SVA submission then submit appropriate changes in accordance with BSCP509. | LDSO | BSCCo | CSAD (Appendix 3) signed by an authorised person in accordance with BSCP38, a completed CSAD Appendix 5 and: (a) If CVA Submission: CVA Long or Short Format data files, in accordance with Appendix 6; and/or (b) If SVA Submission: SVA Format data file (D0265) in accordance with Appendix 7 and information in accordance with BSCP509 if MDD changes are required. (c) Keep equivalent boundary LLFs in a separate file from BSCP128 Appendix forms. | Email or other electronic means |
2.3.8 | Within 2 WD of Ref (2.3.7) | Acknowledge receipt of CSAD and LLFs and confirm authorised signature. | BSCCo | LDSO | Confirmation of receipt and authorised signature. | Email, telephone or other electronic means |
2.3.9 | Within 10 WD of Ref (2.3.7)8 | Provide SVA LLF summary report to Host LDSOs and/or Embedded LDSOs that do not Mirror. | BSCCo | LDSO | Summary Report for SVA LLFs in accordance with Appendix 8. | Email or other electronic means |
2.3.10 | Within 10 WD of Ref (2.3.7) | Publish submitted LLFs on the BSC Website with a status of ‘pending’. | BSCCo |
| SVA LLF Summary Report and: (a) If CVA Submission: CDCA-I022 data files; and/or (b) If SVA Submission: D0265 data files. | BSC Website |
2.3.11 | Between 1 October and 20 November on date agreed in Ref (2.3.4) above | Conduct calculation audit in accordance with Section 3.5.9,10 If LLFs have been re-calculated conduct audit, including spot checks on MSIDs. If Host LDSOs have provided boundary equivalent LLFs to the Embedded LDSO, complete Host LDSO audit between 1 October and 12 November. | BSCCo |
| CSAD and CSAD Appendix 5 and: (a) If CVA Submission: CDCA-I022 data file; and/or (b) If SVA Submission: D0265 data file. | CSAD review, LLF validation system, site visits |
2.3.12 | Within 5 WD of calculation audit11 | Provide draft audit report highlighting any identified non-compliance(s) including where non-compliance of boundary equivalent LLFs requires recalculation of Embedded LDSO Site Specific LLF values. | BSCCo | LDSO | Draft LDSO report. | Email or other electronic means |
2.3.13 | Within 15 WD of calculation audit | Resolve any non-compliance(s) identified in Ref (2.3.12) and notify BSCCo.
If applicable, provide recalculated boundary equivalent LLFs to Embedded LDSO. | LDSO | BSCCo
Embedded LDSO | Any further information required and evidence of resolved non-compliance(s).
LLF values | Email, telephone or other electronic means |
2.3.14 | By 10 December | Submit any revised LLFs to address any outstanding non-compliance(s). | LDSO | BSCCo | Any revised LLFs as required and final CSAD with evidence of resolved non-compliance(s). Final CSAD signed by an authorised person in accordance with BSCP38 and: (a) If CVA re-submission: CVA Long or Short Format data files in accordance with Appendix 6; and/or (b) If SVA re-submission: SVA Format data file (D0265) in accordance with Appendix 7 and information in accordance with BSCP509 if MDD changes are required. | Email or other electronic means |
2.3.15 | By 31 December | Conduct calculation audit on revised submission. | BSCCo | - | CSAD and: (a) If CVA Submission: CDCA-I022 data file; and/or (b) If SVA Submission: D0265 data file. | CSAD review, LLF validation system |
2.3.16 | By 31 December. | Provide final audit report and confirmation of compliance or non-compliance. | BSCCo | LDSO | Final LDSO report. | Email, telephone or other electronic means. |
2.3.17 | By 31 December | Publish revised LLFs on the BSC Website with a status of ‘pending’. | BSCCo |
| SVA LLF Summary Report and: (a) If CVA Submission: CDCA-I022 data files; and/or (b) If SVA Submission: D0265 data files. | BSC Website |
2.3.18 | To meet Panel Requirements | Submit a final report specifying the LLFs for which the audit did not identify non-compliance(s) (including resolved non-compliance(s)) and the LLFs for which the audit identified non-compliance(s) including any default values requiring approval12. Where MDD changes have been identified submit notice in accordance with BSCP509 that there has been (or is due to be) a change to MDD for Panel approval. | BSCCo | Panel | Final report, any default values and any MDD changes. | Email or other electronic means |
2.3.19 | To meet Panel Requirements | Approve LLFs with no identified non-compliance(s) and note any non-compliant LLFs in Ref (2.3.18) above. Approve default values for any non-compliant LLFs. | Panel | BSCCo | LLFs, Final report and any default values. | - |
2.3.20 | Within 1 WD of Ref (2.3.19) | Notify Panel decision. | Panel | BSCCo | Panel decision. | - |
2.3.21 | To meet PAB requirements | Provide a copy of the final report in Ref (2.3.18) giving details of any non-compliance(s). | BSCCo | PAB | Final report in Ref (2.3.18) with details of any non-compliance(s). |
|
2.3.22 | Within 2 WD of Ref (2.3.20) | Provide a final report for the LDSO stating whether the Panel: Approved LLFs with no outstanding non-compliance(s); or Noted any continued non-compliance(s) and approved default values. | BSCCo | LDSO | Final report detailing Panel approval of LLFs; any default values and any continued non-compliance(s). | Email or other electronic means |
2.3.23 | As agreed between BSCCo and the LDSO | If the Panel has noted any non-compliance(s), liaise with BSCCo to correct and re-submit LLFs.13 | LDSO | BSCCo | Any revised LLFs as required and final CSAD with evidence of resolved non-compliance(s). | Email or other electronic means |
2.3.24 | Within 2 WD of Ref (2.3.20) | Notify Parties of LLFs approved by the Panel. | BSCCo | Parties | LLFs approved by the Panel (including any default LLFs). | Email or other electronic means |
2.3.25 | Within 2 WD of Ref (2.3.20) | Update LLFs on BSC Website to be utilised in Settlement, when either: (a) The Panel has approved the submission, update LLFs and EFD; or (b) If the Panel has approved default values, update LLFs to default values to be used in Settlement and EFD. If SVA submission only – BSCCo should proceed to Ref (2.3.32). If both CVA and SVA submission then – BSCCo should proceed from Ref (2.3.28) onwards. | BSCCo | - | Confirmation of Panel decision, LLFs and default values for non-approved LLFs. | Electronic means |
2.3.26 | Within 5 WD of Ref (2.3.25) | Obtain LLFs for the LLFCs from BSC Website. | - | HHDAs/ Suppliers | D0265 data files. | BSC Website |
2.3.27 | Within 10 WD of Ref (2.3.26) | HHDAs and Suppliers implement into systems. | HHDAs/ Suppliers | - | D0265 data files. | - |
2.3.28 | By 10 March. | Provide CDCA with CVA LLFs for use in Settlement: (a) If the Panel has approved the CVA LLF submission, provide CVA LLFs and EFD; or (b) If the Panel has approved default values, provide default CVA LLF values and EFD. | BSCCo | CDCA | Confirmation of approval of CVA LLFs and EFD contained in CDCA-I022 data files; or CVA Metering System ID, CDCA-I022 data files and EFD. | Email or other electronic means |
2.3.29 | Within 1 WD of Ref (2.3.28) | Acknowledge receipt of CVA LLFs and notify BSCCo of any exceptions via the CDCA-I023 data file. | CDCA | BSCCo | CDCA-I023 data file. | Email or other electronic means |
2.3.30 | Within a timescale agreed between CDCA and BSCCo | Implement approved CVA LLFs in accordance with CDCA-I022 data files supplied in Ref (2.3.28) above into CDCA systems. | CDCA | - | CDCA-I022 data files. | - |
2.3.31 | Within 1 WD of Ref (2.3.30) | Notify BSCCo of successful CDCA-I022 load. | CDCA | BSCCo | - | Email or other electronic means |
2.3.32 | By 10 March. | Provide SVAA with SVA LLFs for use in Settlement: (a) If the Panel has approved the SVA LLF submission, provide SVA LLFs and EFD; or (b) If the Panel has approved default values, provide default SVA LLF values and EFD. | BSCCo | SVAA | Confirmation of approval of SVA LLFs and EFD contained in D0265 data files; or D0265 data files, default values and EFD. | Email or other electronic means |
2.3.33 | Within 1 WD of Ref (2.3.32) | Acknowledge receipt of SVA LLFs. | SVAA | BSCCo | - | Email or other electronic means |
2.3.34 | Within a timescale agreed between SVAA and BSCCo | Implement approved SVA LLFs in accordance with D0265 data files supplied in Ref (2.3.32) above into SVAA systems. | SVAA |
| D0265 data files. | Email or other electronic means |
2.3.35 | Within 1 WD of Ref (2.3.34) | Notify BSCCo of successful D0265 data file load. | SVAA | BSCCo | - | Email or other electronic means |
REF. | WHEN | ACTION | FROM | TO | INFORMATION REQUIRED | METHOD |
2.4.1 | By 1 September | Provide list of Metering Systems to be audited for the correct application of LLFC. | BSCCo | Embedded LDSO | List of Metering Systems | Email or other electronic means |
2.4.2 | By 30 September | Confirm LLFC and voltage for each Metering System in list provided by BSCCo. | Embedded LDSO | BSCCo | List of Metering Systems | Email or other electronic means |
2.4.3 | By 10 October | Check a representative sample of Metering Systems are assigned to the correct LLFC. | BSCCo | - | MSAD Metering System sample | Email, other electronic means or Site visit |
2.4.4 | By 10 October | Provide Metering System sample report highlighting any non-compliance(s). | BSCCo | Embedded LDSO | Metering System sample report. | Email or other electronic means |
2.4.5 | By 31 December | Resolve any identified non-compliance(s) in Ref (2.4.4) and notify BSCCo. | Embedded LDSO | BSCCo | Any further information required and evidence of resolved non-compliance(s). | Email, telephone or other electronic means |
2.4.6 | By 31 December + 10 WD | Obtain LLFs submitted by the relevant Host LDSO(s) or Embedded LDSOs that do not Mirror; and submit LLFs5 and CSAD documents in accordance with approved Host LDSO or Embedded LDSO methodology. | Embedded LDSO | BSCCo | LDSO’s submitted LLFs; (a) If CVA Submission: CVA Long or Short Format data files in accordance with Appendix 6; and/or (b) If SVA Submission: SVA Format data file (D0265) or Short Format data file(s) in accordance with Appendix 7 and information in accordance with BSCP509 if MDD changes are required. This must be accompanied by a CSAD for Embedded LDSOs that Mirror in accordance with Appendix 4, signed by an authorised person in accordance with BSCP38 and an Appendix 5. | BSC Website or Host LDSO or Embedded LDSO that does not Mirror Email or other electronic means |
2.4.7 | Within 2 WD of 2.4.6 | Acknowledge receipt of CSAD and LLFs and confirm authorised signature. | BSCCo | Embedded LDSO | Confirmation of receipt and authorised signature. | - |
2.4.8 | Within 4 WD of 2.4.6 | Conduct LLF Calculation Audit. | BSCCo | - | CSAD and: (a) If CVA submission: CVA Long or Short Format data files or other format agreed with BSCCo; and/or (b) If SVA submission: D0265 data files or other format agreed with BSCCo. | LLF Validation System, Host LDSO LLF submissions |
2.4.9 | Within 6 WD of 2.4.6 | Provide draft audit report highlighting any non-compliance(s). | BSCCo | Embedded LDSO | Draft LDSO report. | Email or other electronic means |
2.4.10 | Within 10 WD of 2.4.9 | Resolve any identified non-compliance(s) in Ref (2.4.9) and notify BSCCo. | Embedded LDSO | BSCCo | Any further information required and evidence of resolved non-compliance(s). | Email, telephone or other electronic means |
2.4.11 | At same time as 2.4.10 | Submit any revised LLFs to address any outstanding non-compliance(s). | Embedded LDSO | BSCCo | Any revised LLFs as required and final CSAD with evidence of resolved non-compliance(s). The submission should include the final CSAD signed by an authorised person in accordance with BSCP38 as well as an Appendix 5 and; and: (a) If CVA re-submission: CVA Long or Short Format data files in accordance with Appendix 6; and/or (b) If SVA re-submission: SVA Format data file (D0265) or Short Format file(s) in accordance with Appendix 7 and information in accordance with BSCP509 if MDD changes are required. | Email or other electronic means |
2.4.12 | Within 4 WD of 2.4.10 | Conduct calculation audit on revised submission. | BSCCo | - | - | CSAD review, LLF validation system. |
2.4.13 | Within 6 WD of 2.4.10 | Produce final audit report and confirmation of compliance or non-compliance. Proceed to Section 2.3 of this BSCP and continue onwards from Ref (2.3.18) to complete the submission and audit process. | BSCCo | Embedded LDSO | Final LDSO report. | Email or other electronic means |
REF. | WHEN3 | ACTION | FROM | TO | INFORMATION REQUIRED | METHOD |
2.5.1 | >= EFD-50 WD if mid-year submission for new site; or >=EFD-40 WD if mid-year submission of revised LLFs for an existing site | Submit calculated LLFs in accordance with the approved methodology and completed CSAD6 (Appendix 10) signed by an authorised signatory. | LDSO | BSCCo | CSAD signed by an authorised person in accordance with BSCP38; and (a) If CVA Submission: CVA Long or Short Format data files in accordance with Appendix 6; and/or (b) If SVA Submission: SVA Format data file (D0265) in accordance with Appendix 7 and information in accordance with BSCP509 if MDD changes are required. | Email or other electronic means |
2.5.2 | Within 2 WD of 2.5.1 | Acknowledge receipt of CSAD and LLFs and confirm authorised signature. | BSCCo | LDSO | Confirmation of receipt and authorised signature. | Email or telephone |
2.5.3 | Within 5 WD of 2.5.1 | Conduct calculation audit.8 | BSCCo |
| CSAD and (a) If CVA submission: CVA Long or Short Format data files; and/or (b) If SVA submission: D0265 data files. | LLF validation system |
2.5.4 | Within 5 WD of 2.5.3 | Produce final report and confirmation of compliance or non-compliance. Proceed to Ref (2.3.19). | BSCCo | LDSO | Final Report. | Email or other electronic means |
Requirement | Description of Requirement |
1 | The calculation details must be provided in a spreadsheet format (requirement 7 and 9 can be provided in additional attachments) |
2 | Show the year of data being used to calculate the Line Loss Factor |
3 | Show that the Line Loss Factor calculation takes into account both variable losses and fixed losses |
4 | Show/confirm that the Line Loss Factor calculation takes into account Technical Losses only |
5 | Show that Line Loss Factor is calculated for the SToD as defined in the methodology statement |
6 | Show the difference in network losses when the customer is connected and disconnected |
7 | Provide screenshot/raw data to support requirement 6 |
8 | Show the customer's load data that is being used to calculate the Line Loss Factor |
9 | Show the customer's line diagram and label the connection voltage for the customer |
10 | Check the calculated Line Loss Factor values against previously approved values (within acceptable tolerance level) |
11 | Show both export and import LLF calculations using the “Additional LLF Calculation” sheet. Provide a description on how the export LLF and import LLF are combined to calculate the final LLF. This is only applicable if export and import LLFs are individually calculated and then combined to derive the final LLF. |
Version | Date | Description of Changes | Changes Included | Mods/ Panel/ Committee Refs |
1.0 | 20/04/09 | First Published | P216 | 153/04 |
2.0 | 24/06/10 | June 10 Release | CP1326 | ISG111/03 SVG111/01 |
3.0 | 30/06/11 | June 11 Release | CP1343 | SVG122/02 ISG122/03 |
4.0 | 28/06/12 | June 12 Release | CP1370 | ISG135/05 SVG136/05 |
| 28/06/12 | June 12 Release | CP1371 | ISG135/06 SVG136/06 |
5.0 | 28/02/13 | February 13 Release | CP1375 | ISG137/07 SVG139/07 |
6.0 | 26/06/14 | June 14 Release | CP1407 v2.0 | ISG157/01 SVG160/05 P225/12 |
7.0 | 03/11/16 | November 16 Release | CP1461 | ISG128/08 SVG186/04 |
8.0 | 22/02/18 | February 2018 Release | CP1492 | ISG198/06 SVG200/04 |
9.0 | 27/02/20 | February 2020 Release | CP1519 | ISG221/05 SVG224/04 |
10.0 | 01/09/21 | 1 September 2021 Non-Standard Release | P420 | P316/05 |
11.0 | 04/11/21 | 4 September Standard Release | CP1547 | ISG245/05 SVG247/03 |
12.0 | 29/02/24 | 24 February 2024 Standard Release | CP1578 | ISG269/01 SVG271/02 |
Intellectual Property Rights, Copyright and Disclaimer The copyright and other intellectual property rights in this document are vested in Elexon or appear with the consent of the copyright owner. These materials are made available for you for the purposes of your participation in the electricity industry. If you have an interest in the electricity industry, you may view, download, copy, distribute, modify, transmit, publish, sell or create derivative works (in whatever format) from this document or in other cases use for personal academic or other non-commercial purposes. All copyright and other proprietary notices contained in the document must be retained on any copy you make. All other rights of the copyright owner not expressly dealt with above are reserved. No representation, warranty or guarantee is made that the information in this document is accurate or complete. While care is taken in the collection and provision of this information, Elexon Limited shall not be liable for any errors, omissions, misstatements or mistakes in any information or damages resulting from the use of this information or action taken in reliance on it. |
1 This includes both Host LDSOs and Embedded LDSOs.
2 An Embedded LDSO may also operate an independent distribution network that is connected to Host LDSO’s distribution network via another Embedded LDSO’s network (known as a nested network). Furthermore, an Embedded LDSO may also operate an independent distribution network that is connected to Transmission System within a Host LDSO’s geographic distribution area.
3 Changes to the timescales set out below can be made at the discretion of BSCCo when CVA LLF approval is necessary in less than 40 WD before the Effective Date to carry out BM Unit Registrations and Registration transfers from SMRS to CMRS.
4 The data request will include a list of Metering Systems to be audited for the correct application of LLFC.
5 If the boundary LLFs are later recalculated as a result of a non-compliance, the Embedded LDSO will need to recalculate the impacted Site Specific LLFs.
6 Separate Site Specific LLFs for Import and Export Metering Systems may be applied in accordance with BSCP75.
7 Please note that the CSAD covers both CVA and SVA LLFs.
8 If Host LDSO LLFs have not been submitted by 30 September,or if Embedded LDSOs that do not Mirror LLFs have not been submitte by 31 October, provide summary report of LLFs after 5 WD from the date of Host LDSO LLF submission (or LLF submission by Embedded LDSOs that do not Mirror).
9 The calculation audit may involve further exchange of information between BSCCo and the LDSO to clarify, correct and re-audit any non-compliance(s). The LDSO shall use reasonable endeavours to provide any information requested by BSCCo. BSCCo will feedback to the LDSO the results of the review of the CSAD and the validation of the LLFs prior to site visit to enable the LDSO to address and identify non-compliances at an early stage. As part of the site visit BSCCo may also wish to target certain areas of the LDSO systems and processes to seek evidence on whether the LDSO has addressed these non-compliance(s).
10 Where revised LLF values for existing sites have been submitted mid-year prior to commencement of the current submission cycle and are awaiting approval by the Panel, BSCCo shall include the LLF values in the calculation audit.
11 Where no site visit is required the calculation audit will be limited in scope.
12 Where no methodology has been approved, default LLFs shall be presented to the Panel for approval.
13 As appropriate, BSCCo shall present the corrected LLFs to Panel for approval and inform PAB of the Panel outcome.
14 Mid year submission of revised LLFs are subject to the criteria defined in the LLF Methodology Principles 14, 15 and 16, see Appendix 3.1 of this document.
15 This principle allows Site Specific Losses to be calculated individually or in aggregate and then used in the calculation of Generic LLFs.
16 This principle only applies to the calculation of Generic LLFs. The BSC Year is 1 April to 31 March, LLFs for use in the BSC Year commencing 1 April 2011 should be calculated using the Settlement Data from the 2008 BSC Year, 1 April 2008 to 31 March 2009.
17 Appendix 3.4 provides clarification on how this should be implemented.
18 If a connection is at EHV due to the Import/Export capacity associated with its primary purpose but, a much lower Import/Export capacity is also required for secondary purposes, which would be a non-EHV connection if considered in its own right, this default replacement process MAY also apply e.g. a single Metering System with separate Import and Export MSIDs
19 In this context, Site has the meaning given to it in BSC Section K 1.6
20 This also applies to new sites energised mid-year.
21 STOD (Seasonal Time of Day) Distribution losses vary according to the time the power is taken by the customer. Typically there will be different LLFs for Day, Night, Summer Day and Winter Day and Winter Peak times. The STOD periods are specified in the LDSO’s methodology statement.
22 BSCCo will use a LLF validation system to conduct a number of the validation checks as outlined in this section.
23 For checks 7(a) to 7(e) BSCCo shall compare the value submitted by the LDSO with a previous factor for a similar time period.
24 The loss refers to the proportion of energy lost as a result of electricity flowing through the Distribution System.