BSC Digital Code logo
BSC Digital Code logo
  1. Home
  2. BSC & Codes
  3. BSC Digital Codes
Advanced Search
Previous version
Next version

CONTENTS

Aggregated DUoS V1.0

Effective From Date:
Status:LIVE
Download

Aggregated DUoS

Guidance Note

Introduction

This guide will be of interest to Licensed Distribution System Operators (LDSOs), Half Hourly Data Aggregators (HHDAs) and Suppliers. It replaces the P339 Implementation Guide.

What is Aggregated DUoS?

LDSOs levy site-specific Distribution Use of System (DUoS) charges for Half Hourly (HH) Metering Systems in Measurement Classes C, D and E using metered volumes provided by Half Hourly Data Collectors (HHDCs). Non Half Hourly (NHH) Metering Systems and Half Hourly Metering Systems in Measurement Classes F and G are billed on an aggregate basis using data provided by BSC central services in two reports:

    • Aggregated DUoS Report (D0030)

    • Non Half Hourly Embedded Network DUoS Report (D0314)1

The two reports originally included aggregated volumes for NHH Metering Systems. They were updated to include elective HH sites in Measurement Classes F and G as part of Modification Proposal ‘Introduction of new Measurement Classes to support Half Hourly DCUSA Tariff Changes’ (P300) in November 2015 and were further updated to include export as part of Modification Proposal ‘Introduction of new Consumption Component Classes for Measurement Classes E-G’ (P339) in April 2017.

What are the Half Hourly Measurement Classes? What are the Half Hourly Measurement Classes?

Measurement Class

Description

C

Half Hourly Metering Equipment at above 100kW Premises

D

Half Hourly Unmetered Supplies

E

Half Hourly Metering Equipment at below 100kW Premises with current transformer

F

Half Hourly Metering Equipment at below 100kW Premises with current transformer or whole current, and at Domestic Premises

G

Half Hourly Metering Equipment at below 100kW Premises with whole current and not at Domestic Premises

Please note that Measurement Classes are defined in terms of the premises at which the Metering Equipment is installed. So an Export Metering System should be allocated to the same Measurement Class as the import Metering System at the same premises.

How are elective Half Hourly Metering Systems reported in the D0030?

HHDAs send HH data for Metering Systems in Measurement Classes F and G to the Supplier Volume Allocation Agent (SVAA). The data is aggregated by Line Loss Factor Class (LLFC) Id and Consumption Component Class (CCC) Id. The SVAA includes the data in the D0030 report as if it were profiled NHH data. Whereas the profiled NHH data is allocated to a Standard Settlement Configuration (SSC) and Time Pattern Regime (TPR), the data for Measurement Classes F and G are allocated to ‘dummy’ SSCs and TPRs. These SSC and TPR values are not included in Market Domain Data (MDD) to prevent them being used for NHH Metering Systems, as no profile coefficients are calculated for them.

The ‘dummy’ SSCs for import have three TPRs corresponding to the ‘red’, ‘amber’ and ‘green’ periods of the LDSO DUoS tariffs. Those for export can have a single rate TPR or may also have three TPRs for the ‘red’, ‘amber’ and ‘green’ periods. The ‘dummy’, SSCs and TPRs, together with the Clock Intervals for the relevant periods are defined by host LDSOs in a ‘Mapping Data for HH Aggregated Metering Systems’ (P239) flow. The same flow is used by LDSOs, including Independent Distribution Network Operators (IDNOs), to map LLFCs to the ‘dummy’ SSCs. This allows for differentiated billing of Measurement Classes F and G, which should have separate LLFCs.

The ‘VMR’ record of the D0030, which includes the SSC and TPR, will have a Profile Class of zero for elective HH records. SPM Total All EACs and SPM Total Annualised Advance Report Value are set to zero. SPM Total EAC MSID Count and SPM Total AA MSID Count are based on HH estimates and actuals respectively.

Guidance for Half Hourly Data Aggregators

What do HHDAs need to send for Elective HH Metering Systems?

HHDAs should allocate HH Import or Export volumes to the relevant Consumption Component Class (CCC) Id in the Aggregated Half Hour Data File (D0040) or BM Unit Aggregated Half Hour Data File (D0298) data flows sent to the SVAA. The allocation of energy will depend on the Measurement Quantity (i.e. whether Active Import or Active Export) and the Metering System’s Measurement Class, as notified by the Supplier Meter Registration Service (SMRS)).

The top sections of the D0040 or D0298 flows (the ‘SUP’ group and its nested sub-groups) will contain data for all CCC Ids. The bottom sections of the flows (the ‘37J’ group in the D0298, ‘24J’ group in the D0040, and their nested sub-groups) will contain data for CCC Ids associated with Measurement Classes F and G (whether Active Import or Active Export).

The data for CCC Ids associated with Measurement Classes F and G will thus be aggregated twice – once for the purposes of the Settlement calculations and, separately, for the purposes producing the Aggregated DUoS Report

(D0030).

Which Consumption Component Classes are used for elective Half Hourly?

Consumption values are categorised for the purposes of volume allocation and reporting (including performance monitoring) by a Consumption Component Class. Each CCC has a two digit identifier (CCC Id) and is defined by a combination of attributes.

The CCC Ids associated with elective HH Metering Systems, in Measurement Classes F and G, are set out in the table below.

Consumption Component Class / Measurement Class

F

G

HH Active Import Consumption (Actuals)

42

54

Active Import Metering System Specific Line Losses (Actuals)

43

55

Active Import Metering System Non-Specific Line Loss (Actuals)

44

56

Active Import Consumption (Estimates)

45

57

Active Import Metering System Specific Line Losses (Estimates)

46

58

Active Import Metering System Non-Specific Line Loss (Estimates)

47

59

Active Export Consumption (Actuals)

48

60

Active Export Metering System Specific Line Losses (Actuals)

49

61

Active Export Metering System Non-Specific Line Loss (Actuals)

50

62

Active Export Consumption (Estimates)

51

63

Active Export Metering System Specific Line Losses (Estimates)

52

64

Active Export Metering System Non-Specific Line Loss (Estimates)

53

65

Guidance for LDSOs

What do LDSOs need to set up and when?

LDSOs will need to send a P0239 file to the SVAA. Please email the mapping data to the BSC Service Desk. Where required, Elexon will check these files on behalf of the SVAA.

A revised P0239 file should be sent whenever any of the details change – for example, when new LLFCs are introduced for Measurement Classes F and/or G or when the ‘red’, ‘amber’ and ‘green’ time periods are redefined.

New LLFCs should be set up with an MS Specific LLFC Indicator of ‘A’ = ‘General LLF Class Import’ or ‘C’ = ‘General LLF Class Export’, as applicable. They should be specific to either Measurement Class F or Measurement Class G.

What is the format of the P0239?

The format of the P0239 file is shown below. The file should be in standard Energy Market Data Specification (EMDS) format – i.e. a pipe-delimited format. You can find definitions of the data items in the EMDS on the Retail Energy Code portal.

Group

Group Description

Range

L1

L2

L3

L4

Data Item

Notes

ZHD

File Header

1

G

1

File Type

P0239001

1

From Role Code

R

1

From Participant Id

MPID of LDSO

1

To Role Code

G

1

To Participant Id

CAPG

1

Creation Time

LLF

LLF/SSC Mapping

1 - *

G

1

Distributor Id

MPID of LDSO

1

Line Loss Factor Class Id

1

Standard Settlement Configuration Id

1

Effective From Settlement Date {LLFSSC}

SSC

Standard Settlement Configuration

0 - *

G

1

Standard Settlement Configuration Id

1

Standard Settlement Configuration Description

1

Effective From Settlement Date {SSC}

0

Effective To Settlement Date {SSC}

1

Standard Settlement Configuration Type

TPR

Measurement Requirement

1 - *

G

1

Time Pattern Regime Id

CKI

Clock Intervals

1 - *

G

1

Day of the Week Id

1=Monday, 2=Tuesday, 3=Wednesday, 4=Thursday, 5=Friday, 6=Saturday, 7=Sunday

1

Start Day

1

Start Month

1

End Day

1

End Month

1

Start Time

Midnight (start of day) should be expressed as 000000

1

End Time

Midnight (end of day) should be expressed as 240000

ZPT

File Footer

1

G

1

Record Count

Inclusive of the Header and Footer records.

1

Checksum

Please note:

    • If IDNOs use the same SSC, Measurement Requirements and Clock Intervals as the host LDSO, they will only need to provide the LLF Group;

    • Old LLFCs can be mapped to new Import SSCs, if revised red-amber-green periods have been defined;

    • Old LLF/SSC mappings should be retained for use in reconciliation runs;

    • Effective From Settlement Date {LLFSSC} for any new mappings should be on after the Effective From Settlement Date {SSC} and on or after the Effective Date of the LLFC Id recorded in MDD;

    • All new data items need to be recorded in advance of their effective dates, as the mapping data is fixed during the daily profile production run and is not amended in reconciliation runs;

    • Where red, amber and green periods have been revised, the end-dated SSC should be retained, along with its associated TPRs and Clock Intervals (for use in reconciliation runs);

    • more than one LLFC Id can be mapped to the same SSC; but

    • an LLFC Id must not be mapped to more than one SSC (at any point in time).

What codes should host LDSOs use for the ‘dummy’ SSCs and TPRs?

The SSCs and associated TPRs and Clock Intervals will not be registered in MDD. In order to ensure that ‘dummy’

SSCs and TPRs are kept distinct from ‘real’ SSCs and TPRs, we recommend that LDSOs adopt the following numbering convention in their mapping files.

The SSCs set up in November 2015 for P300 were of the form 9SCn where 9 is a constant and SC = the Distributor Short Code for the host LDSO for the relevant GSP Group. The final integer was set to 1 with a recommendation that any new SSCs should be increment by one. The export SSC introduced for P339 in April 2017 is 9991 with a TPR of 99911 and is standard across most GSP Groups.

TPRs are of the form 9SCn1, 9SCn2 and 9SCn3, where 1, 2 and 3 represent red, amber and green periods respectively.

The latest ‘dummy’ SSCs and TPRs are shown in the table below.

GSP Group Id

GSP Group

Import SSC

Import TPR (red)

Import TPR (amber)

Import TPR (green)

Export SSC

Export TPR(s)

_A

Eastern

9101

91011

91012

91013

9102

91021 91022 91023

_B

East Midlands

9111

91111

91112

91113

9991

99911

_C

London

9121

91211

91212

91213

9122

91221 91222 91223

_D

Merseyside and North Wales

9132

91321

91322

91323

9991

99911

_E

Midlands

9141

91411

91412

91413

9991

99911

_F

Northern

9151

91511

91512

91513

9991

99911

_G

North Western

9161

91611

91612

91613

9991

99911

_H

Southern

9202

92021

92022

92023

9991

99911

_J

South Eastern

9191

91911

91912

91913

9192

91921 91922 91923

_K

South Wales

9211

92111

92112

92113

9991

99911

_L

South Western

9221

92211

92212

92213

9991

99911

_M

Yorkshire

9231

92311

92312

92313

9991

99911

_N

South Scotland

9182

91821

91822

91823

9991

99911

_P

North Scotland

9172

91721

91722

91723

9991

99911

Further Information

Who should I contact if I have any further questions?

For more information please contact the BSC Service Desk.

FAQs

When do IDNOs have to send a P0239 file?

IDNOs need to send a P0239 file when they enter the market, if they anticipate having elective HH Metering Systems on their networks. If they are adding new LLFCs for Measurement Class F or G, IDNOs will need to submit a revised P0239 file.

Why does the P0239 file content look different compared to the files submitted by host LDSOs?

This is due to the fact that host LDSOs do not need to include the ‘dummy’ SSCs.

If the LDSO has LLFCs to be end dated on a specific future date, do they need to reflect them in their P0239 flow?

The P0239 file has no end date for the LLF-dummy SSC mappings. Once individual Metering Systems have been allocated a different LLFC Id, they will no longer be included in future D0030 reporting. To ensure that they continue to be included in reconciliation runs, we recommend that the mappings continue to be included in the P0239. Once all Metering Systems have a new LLFC Id and all relevant reconciliation runs have been carried out, the mappings can be excluded from any revised P0239 files.

When can LDSOs submit the new LLFCs?

LDSOs should wait for the MDD publish date before submitting P0239s that include new LLFC Ids.

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 Despite the flow name, the D0314 includes elective HH as well as NHH