Version	Date	Description of Changes	Changes Included	Mods/ Panel/ Committee Refs
1.0	27/02/14	February 2014 Release	CP1396	SVG153/03 P219/07
2.0	30/06/16	June 2016 Release	CP1434	Panel 241/05
3.0	01/09/21	1 September 2021 Non-Standard Release	P420	P316/05

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 INTRODUCTION

1.1 Background

Market Domain Data (MDD) is the central repository of Supplier Volume Allocation (SVA) market information and is essential to the operation of the SVA Trading Arrangements as it includes critical information such as Standard Settlement Configurations, Profile Classes and GSP Groups which is common to all Market Participants.

The development of MDD was to ensure that all Market Participants work from the same version of data and that it is updated simultaneously. In order for the trading arrangements to operate efficiently it is essential that all parties utilise the correct data at all times. Therefore, the generation, maintenance and distribution of such data requires managing in a secure and auditable manner.

To meet this requirement the SVA Agent acts as the single, central repository for all such data and is responsible for its maintenance and distribution to Market Participants, Party Agents, BSC Agents and other interested parties.

The following Market Roles receive MDD and use it to update their internal systems to keep them in step with the rest of the market:

Half Hourly Data Collector
Non Half Hourly Data Collector
Half Hourly Data Aggregator
Non Half Hourly Data Aggregator
SVA Agent
Meter Operator
SMR Agent
Licensed Distribution System Operator
Supplier.

These parties use the information distributed from MDD for a variety of purposes including:

Calculation of profile coefficients by the SVAA;
Construction of initial EAC values (i.e. splitting a Metering System level across registers) by Suppliers; and
Generation of default EAC values by NHHDAs.

Note that the MDD application and the contents of the MDD database are owned by BSCCo. The application is maintained by the SVA Agent (SVAA), which incorporates the role of Market Domain Data Manager (MDDM).

1.2 Purpose of this Document

This document is aimed at all Market Participants who use MDD and need to raise MDD Change Requests. The purpose of the document is to provide information on the data items and validation rules that apply to each MDD Entity.

1.3 MDD Format

Market Domain Data is held in a standalone database which is updated in accordance with details published by BSCCo. The MDD application produces a series of structured files that form the input to Market Participants’ internal systems. The files consist of a series of groups of related information and require specialised programmes to interpret their contents. When MDD is updated, a new version of the files is created and is then distributed (Published) to the relevant parties.

MDD files can be identified by unique Energy Market Data Specification (EMDS) reference numbers.

The D0269 version of MDD is the complete set of data (excluding Teleswitch and BM Unit details which are distributed via the D0280 and D0299 flows respectively).

The D0270 contains only the incremental updates of the most recent version to be published.

Once received, the files are managed by the recipients, who are responsible for updating their systems in accordance with instructions from BSCCo. Details of the structure of the files are documented in the EMDS.

MDD is published approximately monthly. A release schedule which states all MDD publish dates is available on the BSC Website.

1.4 Code Subsidiary Documentation

The management of the MDD process is governed by the following BSC Procedures (BSCPs).

Reference	Description
BSCP508	This document covers implementation of MDD Changes by the SVA Agent.
BSCP509	The purpose of this BSCP is to ensure that all changes to Market Domain Data are made in a controlled and auditable manner.
BSCP509 – Appendix 1: MDD Entity Change Request Forms	Prescribed forms used by Market Participants to specify which tables within MDD they wish to make changes to.
BSCP509 – Appendix 2: MDD Change Request Entity Validation	This document provides details of the information required when completing the associated Entity forms for a MDD Change Request

2 ACRONYMS AND DEFINITIONS

The terms used in this BSCP are defined as follows:

AA	Annualised Advance
AFYC	Average Fraction of Yearly Consumption
BM	Balancing Mechanism
BSC	Balancing and Settlement Code
BSCP	Balancing and Settlement Code Procedure
CRA	Central Registration Agent
EAC	Estimated Annual Consumption
EFSD	Effective from Settlement Date
EMDS	Energy Market Data Specification
ETSD	Effective to Settlement Date
GSP	Grid Supply Point
LDSO	Licensed Distribution System Operator
LLF	Line Loss Factor
LLFC	Line Loss Factor Class
MDD	Market Domain Data
MDDM	Market Domain Data Manager
MMT	Meter Timeswitch Meter Type
MPID	Market Participant Identification
MPR	Market Participant Role
MPT	Meter Payment Type
MTC	Meter Timeswitch Class
SMETS	Smart Metering Equipment Specifications
MTCPA	MTC for Distributor area
SMRA	Supply Meter Registration Agent
SSC	Standard Settlement Configuration
SVA	Supplier Volume Allocation
SVAA	Supply Volume Allocation Agent
TPR	Time Pattern Regime
VMTCLC	Valid MTC/LLFC Combination
VMTCSC	Valid MTC/SSC Combination
VMTCLSC	Valid MTC/SSC/LLFC Combination
VMTCLSPC	Valid MTC/SSC/LLFC/PC Combination

A detailed glossary of terms is provided in Appendix A.

3 MDD DATA ENTITIES

This section details the tables that are required for each MDD Change Request and the validation rules for each change. The tables shown are in the format that must be provided to the SVA Agent for data entry.

The key Entities and those that are most frequently updated by Market Participants are individually described in sections 3.1 to 3.32. Entities that are updated by annual data file loads, or which relate to information that is rarely changed are summarised in sections 3.34 to 3.36.

Note that BSCP509 Appendix 1 should be read in conjunction with this section.

3.1 Entity 1 – Market Participant ID¹

Market Participant Id	Market Participant Name	Trading Party Id

Brief Description

Defines an organisation that participates in the GB electricity market. The Market Participant ID (MPID) must be unique. To ensure that the chosen MPID is unique please refer to the ‘Market Participant’ table within MDD or contact the BSCCo MDD Co-ordinator.

Guidance on Change Process

When choosing a new MPID, whether it is for a new Supplier ID, additional Supplier ID, or some other Role, the participant must select an ID with 4 alpha characters that is unique and has never previously been registered by another participant. In order to confirm that the ID chosen is acceptable the participant must liaise with the BSCCo MDD Co-ordinator. The Trading Party Id field is mandatory for Suppliers and should be the same as the Market Participant Id. Once registered, the Market Participant ID cannot be changed, but the Market Participant Name may be updated.

Approved MDD changes for new Suppliers, new LDSOs, existing LDSOs and new Party Agents should be made in accordance with the criteria detailed in BSCP509 Section 4.3.

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
Market Participant ID	4	A	M	Liaise with the BSCCo MDD Co-ordinator to ensure that the chosen MPID is unique.
Market Participant Name	30 Max. (including spaces)	A/N	M	The name of the market participant organisation.
Trading Party Id	4	A	O	For Suppliers, this field is mandatory and should be the same as the Market Participant Id unless otherwise agreed with BSCCo. For Market Participants who are not Suppliers, this field must be left blank.

Links to Other Entities

For Each Market Participant there must also be at least one Market Participant Role Code record (Entity 45).

In the case of Suppliers (role code ‘X’), there must also be a Base BM Unit (Entity 61) for every GSP Group.

3.2 Entity 2 – GSP Licensed Distribution System Operator

GSP Group Id	Market Participant Id	Market Participant Role Code	Effective From Date {MPR}	Effective From Settlement Date {GGD}	Effective To Settlement Date {GGD}

Brief Description

A party which is the holder of a Distribution Licence in respect of distribution activities within a GSP Group.

Guidance on Change Process
Approved MDD changes for new Suppliers, new LDSOs, existing LDSOs and new Party Agents should be made in accordance with the criteria detailed in BSCP509 Section 4.3. There are four individual steps that Parties are required to complete during the registration process of a new Licensed Distribution System Operator (LDSO) in MDD. In theory a Party could complete all four steps of the process in parallel and in the same Publish of MDD. In practice, however, it is unlikely they would do this because of the time-scales involved in SVA Qualification Testing. It is more likely that the registration process of a new LDSO would take place over 2-3 separate MDD Publishes. The individual steps involved in the registration of an LDSO are: 1. Submit Change Requests to create an association between new or existing Market Participant IDs of Role Codes ‘P’ for SMR Agent and ‘R’ for Distributor. 2. Submit Change Request to create SMR Agent and LDSO appointments for each GSP Group that the Distributor will operate in. 3. Submit a Change Request to add new MTC for Distributor and subsequent combinations if required. 4. Submit Change Request if new LLFCs are required. Note: Individual Line Loss Factors are not held in MDD but the D0265 file will also need to be submitted to BSCCo in accordance with BSCP128. The final stage in the LDSO registration process is the requirement to set up MTC and LLFC data (and associated combinations) in MDD. The LLFCs and corresponding D0265 file will be loaded into the ISRA systems. Following SVA Qualification Testing, the MPID of the LDSO needs to be associated with the appropriate GSP Group(s) in the MDD system and subsequently entered into the ISRA system by the SVA Agent. At the same time the SMR Agent appointment data needs to be loaded into the MDD system.

Guidance on Change Process

Approved MDD changes for new Suppliers, new LDSOs, existing LDSOs and new Party Agents should be made in accordance with the criteria detailed in BSCP509 Section 4.3.

There are four individual steps that Parties are required to complete during the registration process of a new Licensed Distribution System Operator (LDSO) in MDD. In theory a Party could complete all four steps of the process in parallel and in the same Publish of MDD. In practice, however, it is unlikely they would do this because of the time-scales involved in SVA Qualification Testing. It is more likely that the registration process of a new LDSO would take place over 2-3 separate MDD Publishes.

The individual steps involved in the registration of an LDSO are:

1. Submit Change Requests to create an association between new or existing Market Participant IDs of Role Codes ‘P’ for SMR Agent and ‘R’ for Distributor.

2. Submit Change Request to create SMR Agent and LDSO appointments for each GSP Group that the Distributor will operate in.

3. Submit a Change Request to add new MTC for Distributor and subsequent combinations if required.

4. Submit Change Request if new LLFCs are required.

Note: Individual Line Loss Factors are not held in MDD but the D0265 file will also need to be submitted to BSCCo in accordance with BSCP128.

The final stage in the LDSO registration process is the requirement to set up MTC and LLFC data (and associated combinations) in MDD. The LLFCs and corresponding D0265 file will be loaded into the ISRA systems.

Following SVA Qualification Testing, the MPID of the LDSO needs to be associated with the appropriate GSP Group(s) in the MDD system and subsequently entered into the ISRA system by the SVA Agent. At the same time the SMR Agent appointment data needs to be loaded into the MDD system.

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
GSP Group Id	2	_A	M	The unique character identifier for the relevant GSP Group
Market Participant Id	4	A	M	The unique identifier for the Market Participant.
Market Participant Role Code	1	A/N	M	The assigned role code for the Market Participant (LDSO ‘R’).
Effective From Date {MPR}	10	D	M	The date on which the Market Participant was accredited as a Licensed Distribution System Operator.
Effective From Settlement Date {GGD}	10	D	M	The first Settlement Date on which the Market Participant became active as a Licensed Distribution System Operator within the GSP Group.
Effective To Settlement Date {GGD}	10	D	O	The last Settlement Date on which the Market Participant was active as a Licensed Distribution System Operator within the GSP Group.

Additional Validation

If a Market Participant has a Role code of R (LDSO), it must also have a Role code P (SMRA) with the same MPID, and vice versa.

Links to Other Entities

To add a new GSP Licensed Distribution System Operator, there must already be a Market Participant record (Entity 1) and Market Participant Roles (Entity 45).

3.3 Entity 3 – SVA Agent Appointment

GSP Group Id	Market Participant Id	Market Participant Role Code	Effective From Date {MPR}	Effective From Date {IAA}	Effective To Date {IAA}

Brief Description

An association between the MPID of an SVA Agent and the GSP Groups in which it is active.

Guidance on Change Process

Changes to this entity would occur at the direction of the BSCCo on the appointment of a new SVA Agent. Additionally, the introduction of new GSP Group Ids or merger of existing GSP Group Ids would initiate changes to this entity as directed by the BSCCo.

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
GSP Group Id	2	_A	M	Unique character identifier for the relevant GSP Group.
Market Participant Id	4	A	M	The unique identifier for the SVA Agent Market Participant.
Market Participant Role Code	1	A/N	M	The assigned role code ‘G’ for the SVA Agent Market Participant.
Effective From Date {MPR}	10	D	M	The first date on which the Market Participant was accredited as an SVA Agent.
Effective From Date {IAA}	10	D	M	The first day on which the Market Participant became active as the SVA Agent within the GSP Group.
Effective To Date {IAA}	10	D	O	The last day on which the Market Participant was active as the SVA Agent within the GSP Group.

Links to Other Entities

To add a new SVA Agent Appointment, there must already be a Market Participant record (Entity 1) and Market Participant Roles (Entity 45).

3.4 Entity 4 – SMR Agent Appointment

GSP Group Id	Market Participant Id	Market Participant Role Code	Effective From Date {MPR}	Effective From Date {PAA}	Effective To Date {PAA}

Brief Description

An association between the MPID of the Supplier Metering Registration Agent and the GSP Groups in which they operate.

Guidance on Change Process

Approved MDD changes for new Suppliers, new LDSOs, existing LDSOs and new Party Agents should be made in accordance with the criteria detailed in BSCP509 Section 4.3.

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
GSP Group Id	2	_A	M	The unique identifier for the relevant GSP Group.
Market Participant Id	4	A	M	The unique identifier for the Market Participant.
Market Participant Role Code	1	A/N	M	The assigned role code for the Market Participant (SMRA ‘P’).
Effective From Date {MPR}	10	D	M	The date on which the Market Participant was accredited as a SMR Agent.
Effective From Date {PAA}	10	D	M	The first day on which the Market Participant became active as a SMR Agent within the GSP Group
Effective To Date {PAA}	10	D	O	The last day on which the Market Participant became active as a SMR Agent within the GSP Group

Additional Validation

If a Participant has a Role code of R (LDSO), it must also have a Role code P (SMRA) with the same MPID, and vice versa.

Links to Other Entities

To add a new SMR Agent Appointment, there must already be a Market Participant (Entity 1) and Market Participant Roles (Entity 45).

3.5 Entity 11 – Average Fraction of Yearly Consumption Set

GSP Group Id	Profile Class ID	Standard Settlement Configuration Id	Effective From Settlement Date {VSCPC}	Effective From Settlement Date {AFOYCS}	Effective To Settlement Date {AFOYCS}

Brief Description

A set of data specifying how average consumption is split across registers for a particular GSP Group, SSC and Profile Class.

Guidance on Change Process

This data may need to be created in a number of different circumstances including:

When a new SSC is created, in which case there may also be associated changes to many other entities (see the Entity Diagram in Section 4.2 and guidance on Entity 32).
When an existing SSC is introduced into a new GSP Group or Profile Class, in which case there would be associated changes to Average Fraction of Yearly Consumption, GSP Group Daily Profile Class Average EAC and possibly MTC-related entities.
The SVAA recalculates AFYC values for an existing SSC, in accordance with the rules in Annex S-2 of the BSC. In these cases there would be associated changes to Average Fraction of Yearly Consumption, GSP Group Daily Profile Class Average EAC and GSP Group Profile Class Default EAC.

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
GSP Group Id	2	_A	M	The identifier for the chosen GSP Group.
Profile Class Id	1	N	M	The profile classification identified as a number from 1-8.
Standard Settlement Configuration Id	4	N	M	The identifier for the relevant Standard Settlement Configuration.
Effective From Settlement Date {VSCPC}	10	D	M	The first Settlement Date on which the Valid Settlement Configuration Profile Class is active.
Effective From Settlement Date {AFOYCS}	10	D	M	The first Settlement Date on which the Average Fraction of Yearly Consumption Set is active.
Effective To Settlement Date {AFOYCS}	10	D	O	The last Settlement Date on which the Average Fraction of Yearly Consumption Set is active.

Links to Other Entities

A new Average Fraction of Yearly Consumption Set can only be created if there is an existing GSP Group (Entity 18) and a linked Valid Settlement Configuration Profile Class (Entity 40).

3.6 Entity 12 – Average Fraction of Yearly Consumption

GSP Group Id	Profile Class Id	Standard Settlement Configuration Id	Effective From Settlement Date {VSCPC}	Effective From Settlement Date {AFOYCS}	Time Pattern Regime Id	Average Fraction of Yearly Consumption	Alternative Average Fraction of Yearly Consumption

Brief Description

The fraction of the annual demand that a profile will allocate to the Settlement Periods covered by a TPR.

Guidance on Change Process

This data may need to be created in a number of different circumstances including:

When a new SSC is created, in which case there may also be associated changes to many other entities (see the Entity Diagram in Section 4.2 and guidance on Entity 32).
When an existing SSC is introduced into a new GSP Group or Profile Class, in which case there would be associated changes to Average Fraction of Yearly Consumption Set, GSP Group Daily Profile Class Average EAC and possibly MTC-related entities.
The SVAA recalculates AFYC values for an existing SSC, in accordance with the rules in Annex S-2 of the BSC. In these cases there would be associated changes to Average Fraction of Yearly Consumption Set, GSP Group Daily Profile Class Average EAC and GSP Group Profile Class Default EAC.

Default values will be used initially to derive the Average Fraction of Yearly Consumption until Actual data is available in Settlement to recalculate. These defaults can be derived by summating the appropriate data on the BSC Website in the MDD table ‘Default Period Profile Class Coefficient’ for all Profile Classes except 2 and 4. If an AFYC is wished to be raised for Profile Classes 2 or 4 then this can be requested through the MDD Co-ordinator at BSCCo.

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
GSP Group Id	2	_A	M	The identifier for the chosen GSP Group.
Profile Class Id	1	N	M	The profile classification identified as a number from 1-8.
Standard Settlement Configuration Id	4	N	M	The Id for the relevant Standard Settlement Configuration.
Effective From Settlement Date {VSCPC}	10	D	M	The first Settlement Date on which the Valid Settlement Configuration Profile Class is active.
Effective From Settlement Date {AFOYCS}	10	D	M	The first Settlement Date on which the Average Fraction of Yearly Consumption Set is active.
Time Pattern Regime Id	5	N	M	The Id for the relevant Time Pattern Regime.
Average Fraction of Yearly Consumption	1.6	N	M	A numeric figure, with up to 6 decimal places, which must be a positive value between 0 and 1 inclusive.
Alternative Average Fraction of Yearly Consumption	1.6	N	O	A numeric figure, with up to 6 decimal places, which must be a positive value between 0 and 1 inclusive.

Additional Validation

The values of Average Fraction of Yearly Consumption (across all Time Pattern Regime Ids within an AFOYCS) must sum to 1.

Links to Other Entities
A new Average Fraction of Yearly Consumption can only be created if there is an existing Average Fraction of Yearly Consumption Set (Entity 11) and Valid Measurement Requirement Profile Class (Entity 39).

3.7 Entity 13 – GSP Group Daily Profile Class Average EAC

GSP Group Id	Profile Class Id	Standard Settlement Configuration Id	Effective From Settlement Date {VSCPC}	Effective From Settlement Date {GGPCAE}	Effective To Settlement Date {GGPCAE}	Researched Average EAC

Brief Description

A classification of profile which represents an exclusive category of customers whose consumption can be reasonably approximated to a common profile for the purpose of attributing an EAC or Annualised Advance to individual half hours for Settlement purposes.

Guidance on Change Process

This data may need to be created in a number of different circumstances including:

When a new SSC is created, in which case there may also be associated changes to many other entities (see the Entity Diagram in Section 4.2 and guidance on Entity 32).
When an existing SSC is introduced into a new GSP Group or Profile Class, in which case there would be associated changes to Average Fraction of Yearly Consumption Set, Average Fraction of Yearly Consumption,, GSP Group Daily Profile Class Average EAC and possibly MTC-related entities.

Default GSP/PC EACs can be initially used as the ‘Researched Average EAC’ until Actual data is available in Settlement to recalculate.

Field Details
Fieldname	No. of Chars	Format	M/O	Description/Comments
GSP Group Id	2	_A	M	The identifier for the chosen GSP Group.
Profile Class Id	1	N	M	The profile classification identified as a number from 1-8.
Standard Settlement Configuration Id	4	N	M	The Id for the relevant Standard Settlement Configuration.
Effective From Settlement Date {VSCPC}	10	D	M	The first Settlement Date on which the Valid Standard Settlement Configurations for a Profile Class is active.
Effective From Settlement Date {GGPCAE}	10	D	M	The first Settlement Date on which the GSP Group Daily Profile Class Average EAC is active.
Effective To Settlement Date {GGPCAE}	10	D	O	The last Settlement Date on which the GSP Group Daily Profile Class Average EAC is active.
Researched Average	12.1	N	M	A numeric figure, zero or positive value.

Links to Other Entities

A new GSP Group Daily Profile Class Average EAC can only be created for an existing valid GSP Group Id (Entity 18) and a parent Valid Settlement Configuration Profile Class (Entity 40).

3.8 Entity 17 – Line Loss Factor Class (LLFCs)

Market Participant Id	Market Participant Role Code	Effective From Settlement Date {MPR}	Line Loss Factor Class Id	Line Loss Factor Class Description	MS Specific LLF Class Indicator	Effective From Settlement Date {LLFC}	Effective To Settlement Date {LLFC}

Brief Description

The reference for a Line Loss Factor, within a Distributor’s system, that applies to a group of Metering Systems.

Guidance on Change Process

Licensed Distribution Businesses are required to register Line Loss Factor Classes in MDD in accordance with the processes outlined in BSCP509 and BSCP128.

When the description of an existing Line Loss Factor Class is changed, no other details must change (including Effective From Settlement Date LLFC). The change is applied as a direct overwrite of the previous description, i.e. no dates will be affected.

When creating a new LLFC in MDD the Distributor must also provide the amended D0265 detailing the LLFs which will coincide with the Effective From Settlement Date of the new LLFC. A Change Request raising a new LLFC cannot be implemented into MDD without a supporting D0265.

If it is not the Distributor creating an LLFC, the appropriate authorisation must be gained from the relevant LDSO. This authorisation must also be gained if an LLFC is to be linked to any valid combinations (Entity 55, Entity 56 and Entity 63).

When raising new LLFCs, it is the responsible of LDSOs, or BSC Parties to ensure the appropriate combinations are entered into MDD within the relevant timescales.

When a Distribution Business discontinues an LLFC in MDD it is the responsibility of the Distribution Business to liaise with their SMRA and ensure that any Metering Systems that were previously registered to that LLFC have been migrated to another LLFC. If the Metering Systems are not migrated, validation warnings will be created by the ISRA system. In addition to this the LLFs will automatically default to 1.

The discontinuation of a Line Loss Factor Class is done by giving the LLFC an Effective To Settlement Date. The LLFC will remain valid for all Settlement Dates up to and including the Effective To Settlement Date {LLFC}, and so be valid for reconciliation runs.

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
Market Participant Id	4	A	M	The identifier for the Market Participant.
Market Participant Role Code	1	A/N	M	One character code for Distributor role (R).
Effective From Settlement Date {MPR}	10	D	M	It must be the date the Distributor became active in the Market, i.e. the date provided in the Market Participant Role table.
Line Loss Factor Class Id	3	A/N	M	Excluding ‘000’ and any combination using ‘I’ or ‘O’ or starting ‘0’ or ‘00’.
Line Loss Factor Class Description	30 Max. (including spaces)	A/N	M
MS (Metering System) Specific LLF Class Indicator	1	A	M	See details in Additional Validation below.
Effective From Settlement Date {LLFC}	10	D	M	The first Settlement Date on which the Line Loss Factor Class is active.
Effective To Settlement Date {LLFC}	10	D	O	The last Settlement Date on which the Line Loss Factor Class is active.

Additional Validation

MS (Metering System) Specific LLFC Indicator must take one of the following values:

A - General LLFC for Import Active Energy

B - MS Specific LLFC for Import Active Energy

C - General LLFC for Export Active Energy

D - MS Specific LLFC for Export Active Energy

When raising or end dating a LLFC, the Effective From/To Settlement Date {LLFC} must be greater than or equal to the MDD Go-live date.

When a Line Loss Factor Class is discontinued, all valid child combinations (Entity 55, Entity 56 and Entity 63) joined with the LLFC must also be end dated using a date no later than the Effective To Settlement Date {LLFC}. When discontinuing a Line Loss Factor Class and associated child combinations, the originator should check if any Valid MTC SSC Combinations (Entity 54) are now redundant, and can also be end dated. If so, there may also be MTCs (Entity 53) and SSCs (Entity 32) that can be end dated.

Links to Other Entities

There must be a Market Participant (Entity 1) and a Market Participant Role (Entity 45) with Role Code ‘R’ assigned to the Market Participant.

3.9 Entity 18 – GSP Group

GSP Group Id	GSP Group Name	Region Id

Brief Description

A set of Distribution Systems which form a distinct electrical system and are treated as a group for the purpose of allocating errors in Settlement i.e. GSP Group Correction.

Guidance on Change Process

Changes to this entity would occur on the introduction of a new GSP Group or Merger of existing GSP Groups as directed by the BSC Panel or delegated BSC Panel Committee.

There would be associated changes to SVA Agent Appointment, SMR Agent Appointment, Average Fraction of Yearly Consumption Set, Average Fraction of Yearly Consumption, Base BM Unit for Supplier in GSP Group, GSP Group Daily Profile Class Average EAC, GSP Group Profile Class Default EAC, GSP Licensed Distribution System Operator and GSP Group Profile Tolerances.

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
GSP Group Id	2	_A	M	The identifier for the chosen GSP Group.
GSP Group Name	30 Max. (including spaces)	A/N	M	The name of the Grid Supply Point Group.
Region Id	2 Max. (including spaces)	A	M	Either ‘EW’ for England & Wales, or ‘S’ for Scotland

Additional Validation

Within a single GSP Group, more than one reference can exist to a given GSP Group Distributor and SMR Agent ID.

Within a single GSP Group, if a GSP Group Distributor entry exists for a Distributor then its SMR Agent Appointment entry must also exist and vice-versa.

3.10 Entity 20 – GSP Group Profile Class Default EAC

GSP Group Id	GSP Group Name	Profile Class Id	GSP Group Profile Class Default EAC	Effective From Settlement Date	Effective To Settlement Date

Brief Description

Failures in a Supplier's registration and Agent appointment processes can cause there to be no EAC available for use in the Settlement process. In order to minimise the impact on the Settlement process a default EAC is used. This default EAC is based on an average of the values for that Supplier's other similar customers in the GSP Group. This data is updated on an annual basis, and is manually distributed to Market Participants, in word format, on a monthly basis by email.

Guidance on Change Process

This data may need to be created in a number of different circumstances including:

When a new SSC is created, in which case there may also be associated changes to many other entities (see the Entity Diagram in Section 4.2 and guidance on Entity 32).
When an existing SSC is introduced into a new GSP Group or Profile Class, in which case there would be associated changes to Average Fraction of Yearly Consumption Set, Average Fraction of Yearly Consumption and GSP Group Daily Profile Class Average EAC.
Introduction of new GSP Groups or Profile Classes.

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
GSP Group Id	2	_A	M	The unique identifier for the relevant GSP Group.
GSP Group Name	30 Max. (including spaces)	A/N	M	The name of the GSP Group.
Profile Class Id	1	N	M	The profile classification identified as a number from 1-8.
GSP Group Profile Class Default EAC	12.1	N	M	The default EAC value.
Effective From Settlement Date	10	D	M	The first Settlement Date on which the Default EAC becomes active.
Effective To Settlement Date	10	D	O	The last Settlement Date on which the EAC is active.

3.11 Entity 27 - Clock Interval

Time Pattern Regime ID	Week Day ID	Start Day	Start Month	End Day	End Month	Start Time	End Time

Brief Description

A time period for a particular day of the week, within a calendar period, when the Time Pattern Regime is active.

Guidance on Change Process

This data may need to be created when a new SSC is created with an associated Time Pattern Regime (only where the Teleswitch/Clock Indicator equals ‘C’), in which case there may also be associated changes to many other entities (see the Entity Diagram in Section 4.2 and guidance on Entity 32).

This data could also change for Time Pattern Regimes associated with Standard Settlement Configurations that have a Standard Settlement Configuration Type of ‘E’ on direction of the Panel or delegated Panel committee to change the ‘deemed’ switching times for ‘Export’ Metering Systems associated with small scale third party generation plant.

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
Time Pattern Regime Id	5	N	M	The 5 digit Id for the relevant Time Pattern Regime (with leading zeros where necessary).
Week Day ID	1	N	M	The identifier for the day of the week between 1 and 7 (Mon – Sun).
Start Day	2	N	M	The identifier for the relevant day of the month, i.e. between 1 and 31.
Start Month	2	N	M	The identifier for the relevant month, i.e. between 1 and 12 (Jan – Dec).
End Day	2	N	M	The identifier for the relevant day of the month, i.e. between 1 and 31.
End Month	2	N	M	The identifier for the relevant month, i.e. between 1 and 12 (Jan – Dec).
Start Time	4 - 6	N	M	The Clock Interval start time in the format hhmm or hhmmss (e.g. 0730 or 073000).
End Time	4 - 6	N	M	The Clock Interval end time in the format hhmm or hhmmss (e.g. 0830 or 083000).

Additional Validation

Clock Time Pattern Regime is a sub set of Time Pattern Regime where the Teleswitch/Clock Indicator equals ‘C’.

If a 4 digit Start Time or End Time is submitted, the MDD system will default the 5^th and 6^th digit to 00.

Start Time and End Time will need to be validated to ensure that they are valid times:

Start Time > = 0 and < 240000

End Time > 0 and < = 240000

Start Time < End Time

Links to Other Entities

The relevant Time Pattern Regime (Entity 38) must exist.

3.12 Entity 29 - Measurement Requirement

Standard Settlement Configuration Id	Time Pattern Regime ID

Brief Description

This details the Time Pattern Regimes associated to a Standard Settlement Configuration.

Guidance on Change Process

This data needs to be created when a new SSC is created, in which case there may also be associated changes to many other entities (see the Entity Diagram in Section 4.2 and guidance on Entity 32).

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
Standard Settlement Configuration Id	4	N	M	The unique identifier for the SSC. It must consist of four digits (with leading zeros where necessary).
Time Pattern Regime Id	5	N	M	The Id for the relevant Time Pattern Regime.

Additional Validation

Links to Other Entities

A new Measurement Requirement can only be created if the following parent entities exist:

Standard Settlement Configuration (Entity 32)

Time Pattern Regime (Entity 38).

3.13 Entity 32 - Standard Settlement Configuration

Standard Settlement Configuration Id	Effective From Settlement Date {SSC}	Effective To Settlement Date {SSC}	Standard Settlement Configuration Description	Standard Settlement Configuration Type	Teleswitch User Id	Teleswitch Group Id

Brief Description

The unique market wide reference for a Standard Settlement Configuration (logical Non-Half Hourly metering configuration supported by the Settlement process).

Guidance on Change Process

This data needs to be created when a new SSC is required, in which case there may also be associated changes to many other entities (see the Entity Diagram in Section 4.2).

The creation of new SSCs is subject to approval by the BSC Panel or delegated BSC Panel Committee.

New SSCs may also be created at the direction of the BSC Panel or delegated BSC Panel Committee for ‘Export’ Metering Systems associated with small scale third party generating plant.

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
Standard Settlement Configuration Id	4	N	M	The unique identifier for the SSC. It must consist of four numeric digits (with leading zeros where necessary).
Effective From Settlement Date {SSC}	10	D	M	The first Settlement Date on which the Standard Settlement Configuration is active.
Effective To Settlement Date {SSC}	10	D	O	The last Settlement Date on which the Standard Settlement Configuration is active.
Standard Settlement Configuration Description	50 Max. (including spaces)	A/N	M	The narrative representation of the Standard Settlement Configuration.
Standard Settlement Configuration Type	1	A	M	Either Import ‘I’ or Export ‘E’.
Teleswitch User Id	2	N	O	Identifier for the Teleswitch User.
Teleswitch Group Id	4	N	O	Identifier for the Teleswitch Group.

Additional Validation
A Change Request for a new Standard Settlement Configuration that is assigned to a Teleswitch Time Pattern in Measurement Requirements can only be created if the Teleswitch Group parent entity exists.
The Teleswitch User Id and Teleswitch Group Id can only be updated if they are null.
When a Change Request is raised to end-date a Standard Settlement Configuration the originator must also end-date all associated child combinations with an Effective To Settlement Date no later than the Effective To Settlement Date of the SSC.

Links to Other Entities

If the Market Participant is linking the Standard Settlement Configuration to a Teleswitch Time Pattern Regime, there must already be a valid Teleswitch Group Id (Entity 37).

3.14 Entity 33 - Teleswitch Time Pattern Regime

Time Pattern Regime ID	Teleswitch User Id	Teleswitch Group Id	Teleswitch Switch Id

Brief Description

The details for a Time Pattern Regime that specifically relate to a Radio Teleswitch controlled pattern of switching.

Guidance on Change Process

This data needs to be created when a new SSC is introduced that has associated Time Pattern Regimes where the Tele-Switch/Clock Indicator set to ‘S’ in which case there may also be associated changes to many other entities (see the Entity Diagram in Section 4.2).

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
Time Pattern Regime Id	5	N	M	The 5 digit Id for the relevant Time Pattern Regime (with leading zeros where necessary).
Teleswitch User Id	2	N	M	Identifier for the Teleswitch User.
Teleswitch Group Id	4	N	M	Identifier for the Teleswitch Group.
Teleswitch Switch Id	1	A	M	1 Character identifier (A, B, C or D).

Links to Other Entities

Combination of Teleswitch User Id and Teleswitch Group Id must already exist in Teleswitch Group (Entity 37).

3.15 Entity 34 - Teleswitch Register Rules

Time Pattern Regime ID	Teleswitch Register Rule Id

Brief Description

This function allows the user to maintain the list of Teleswitch Register Rules.

Guidance on Change Process

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
Time Pattern Regime Id	5	N	M	The 5 digit Id for the relevant Time Pattern Regime (with leading zeros where necessary).
Teleswitch Register Rule Id	2	N	M	A number which distinguishes between the different rules associated with a Teleswitch Time Pattern Regime. The rules identify the switching relationships between teleswitch contacts and Settlement registers.

Links to Other Entities

A new occurrence of Teleswitch Register Rules can only be created if the Teleswitch Time Pattern Regime (Entity33) already exists.

3.16 Entity 35 - Teleswitch Contact Rule

Time Pattern Regime Id	Teleswitch Register Rule Id	Teleswitch Contact Code	Teleswitch Contact Rule

Brief Description

This function allows the user to maintain Teleswitch Contact Rules.

Guidance on Change Process

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
Time Pattern Regime Id	5	N	M	The 5 digit Id for the relevant Time Pattern Regime (with leading zeros where necessary).
Teleswitch Register Rule Id	1	N	M	Distinguishes between the different rules associated with a Teleswitch Time Pattern Regime. The rules identify the switching relationships between teleswitch contacts and Settlement registers.
Teleswitch Contact Code	1	A	M	A one character identifier (A, B, C or D) that identifies the logical switching of the Teleswitch Register Rule
					A	Logical Switch 1
					B	Logical Switch 2
					C	Logical Switch 3
					D	Logical Switch 4
Teleswitch Contact Rule	1	N	M	Indicates whether the rule, identified by a Teleswitch Register Rule Id is satisfied depending on the state of a particular teleswitch contact, ‘0’ meaning the Teleswitch Register Rule Id is satisfied if the contact is off; ‘1’ meaning the Teleswitch Register Rule Id is satisfied if the contact is on.

Additional Validation

During update, only the Teleswitch Contact Rule can be updated.

Links to Other Entities

A new occurrence of Teleswitch Contact Rules can only be created if the relevant Teleswitch Register Rules (Entity 34) exists.

3.17 Entity 36 – Teleswitch Contact

Teleswitch Contact Code

Brief Description

This function allows the user to maintain the list of Teleswitch Contact Codes. As there are no non-key attributes, no updates are permitted.

Guidance on Change Process

There are four codes A, B, C and D which cannot be changed or new codes created.

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
Teleswitch Contact Code	1	A	M	1 character code for the Teleswitch Contact.

3.18 Entity 37 - Teleswitch Group

Teleswitch User Id	Teleswitch Group Id

Brief Description

This function allows the user to maintain the list of Teleswitch Groups. As there are no non-key attributes, no updates are permitted.

Guidance on Change Process

The Supplier is required to start using a new Teleswitch Group in accordance with the Radio Teleswitch Agreement.

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
Teleswitch User Id	2	N	M	A maximum 2 character identifier for the Teleswitch User.
Teleswitch Group Id	4	N	M	Up to 4 character identifier for the Teleswitch Group.

3.19 Entity 38 - Time Pattern Regime

Time Pattern Regime ID	Teleswitch/Clock Indicator	GMT Indicator

Brief Description

The unique Market wide reference for a pattern of switching behaviour through time that one or more Settlement registers uses.

Guidance on Change Process

This data needs to be created when a new SSC is created, in which case there may also be associated changes to many other entities (see the Entity Diagram in Section 4.2).

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
Time Pattern Regime Id	5	N	M	The 5 digit Id for the relevant Time Pattern Regime (with leading zeros where necessary).
Teleswitch/Clock Indicator	1	A	M	Set to ‘S’ (Teleswitch) or ‘C’ (Clock – Time Pattern)
GMT Indicator	1	A	M	Set to Y’ (Yes) or ‘N’ (No).

Additional Validation

When Teleswitch/Clock Indicator is set to ‘C’, then the Time Pattern Regime will have a single child Clock Time Pattern Regime but it cannot also have an occurrence of Teleswitch Time Pattern Regime. Conversely, when Teleswitch/Clock Indicator is set to ‘S’, then the Time Pattern Regime must have a single child Teleswitch Time Pattern Regime but it cannot also have an occurrence Clock Time Pattern Regime.

If a new Time Pattern Regime is created, then at least one Teleswitch Time Pattern Regime or Clock Time Pattern Regime must be created at the same time.

Links to Other Entities

If Teleswitch/Clock Indicator is ‘S’, Teleswitch Time Pattern Regime (Entity 33), must also be completed for the same Time Pattern Regime Id.

3.20 Entity 39 - Valid Measurement Requirement Profile Class

Profile Class ID	Standard Settlement Configuration Id	Time Pattern Regime Id	Effective From Settlement Date {VSCPC}	Switched Load Indicator

Brief Description

Measurement Requirement Profile Class links a Measurement Requirement to a valid Standard Settlement Configuration and Profile Class set.

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
Profile Class Id	1	N	M	The profile classification identified as a number from 1-8.
Standard Settlement Configuration Id	4	N	M	In the range 0000-9999.The code for the relevant Standard Settlement Configuration.
Time Pattern Regime Id	5	N	M	In the range 00000-99999. The code for the relevant TPR.
Effective from Settlement Date {VSCPC}	10	D	M	The first Settlement Date on which the Valid Settlement Configuration Profile Class is active.
Switched Load Indicator	1	A	M	Indicates if the load is supplied by a dedicated circuit which is open or closed by time–switch or Teleswitch receiver (T) True, or a non – switched, normal circuit (F) False.

Additional Validation

A Valid Measurement Requirement Profile Class must be created for each Measurement Requirement of the Standard Settlement Configuration.

If the Profile Class has a Switched Load Profile Class Indicator set to ‘F’, then it cannot be linked to any Measurement Requirement with a Switched Load Indicator of ‘T’.

If the Profile Class has a Switched Load Profile Class Indicator set to ‘T’, it must be associated with at least one Measurement Requirement that has a Switched Load Indicator of ‘T’.

Links to other entities

A new Valid Measurement Requirement Profile Class can only be created if a Valid Settlement Configuration Profile Class (Entity 40) already exists.

A Measurement Requirement (Entity 29) must already exist for the SSC/TPR combination.

3.21 Entity 40 - Valid Settlement Configuration Profile Class

Profile Class ID	Standard Settlement Configuration Id	Effective From Settlement Date {VSCPC}	Effective To Settlement Date {VSCPC}

Brief Description

The record linking a valid Standard Settlement Configuration to a Profile Class.

Guidance on Change Process

This data needs to be created when a new SSC is created or an existing SSC is introduced for use in a new Profile Class in which case there may also be associated changes to many other entities (see the Entity Diagram in Section 4.2).

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
Profile Class Id	1	N	M	The profile classification identified as a number from 1-8.
Standard Settlement Configuration Id	4	N	M	In the range 0000-9999. The code for the relevant Standard Settlement Configuration.
Effective From Settlement Date {VSCPC}	10	D	M	The first Settlement Date on which the Valid Settlement Configuration Profile Class is active.
Effective To Settlement Date {VSCPC}	10	D	O	The last Settlement Date on which the Valid Settlement Configuration Profile Class is active.

Additional Validation

Links to Other Entities

A new Valid Settlement Configuration Profile Class can only be created if the Standard Settlement Configuration (Entity 32) and Profile Class (Entity 31) exist.

3.22 Entity 45 - Market Participant Role

Market Participant Id
Market Participant Role Code
Effective From Date {MPR}
Effective To Date {MPR}
Address Line 1
Address Line 2
Address Line 3
Address Line 4
Address Line 5
Address Line 6
Address Line 7
Address Line 8
Address Line 9
Post Code
Distributor Short Code

Brief Description

Defines the Roles within the electricity market that a Participant will perform. Each Market Participant must have at least one Role Code. There must be a separate record for each Role that the Participant will perform.

Guidance on Change Process

Approved MDD changes for new Suppliers, new LDSOs, existing LDSOs and new Party Agents should be made in accordance with the criteria detailed in BSCP509 Section 4.3.

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
Market Participant Id	4	_A	M	The unique identifier for the Market Participant.
Market Participant Role Code	1	A/N	M	Defines the role of the Market Participant, this must already be defined in Entity 21.
Effective From Date {MPR}	10	D	M	The calendar date from which the Market Participant will perform this Role. This date must match the Effective From Date {BMUIGG} and the Supplier Base BM Unit in CRA)
Effective To Date {MPR}	10	D	O	The calendar date on which the Market Participant will cease to perform this Role.
Address Line 1	40 Max. (with spaces)	A/N	M	This must reflect the name of the ‘Market Participant’.
Address Lines 2 – 9	40 Max. (with spaces)	A/N	O	These optional fields are for the address of the Market Participant for this Role.
Post Code	10	A/N	M	The relevant post code.
Distributor Short Code	2	N	O	A code taken from the first two characters of the MPAN for the LDSO. This field is mandatory for Role Code ‘R’ (LDSO), but should be left blank for all other Role Codes.

Additional Validation

If the Role code is ‘X’ (Supplier), the related Market Participant record (Entity 1) must include the Trading Party Id.

If a Participant has a Role code of ‘R’ (LDSO), it must also have a Role code ‘P’ (SMRA) with the same MPID, and vice versa.

Links to Other Entities

A new Market Participant Role can only be created if an associated Market Participant record (Entity 1) and Role Code record (Entity 21) already exists.

3.23 Entity 52 - Meter Timeswitch Class

Meter _Timeswitch _Class_Id	MTC _Meter _Type_ID	Meter Type Effective From Settlement Date	MTC _Payment _Type_Id	Payment Type Effective From Settlement Date	Effective From _Settlement _Date_{MTC}	Effective To _Settlement _Date_{MTC}	MTC Common _Code_Indi_c_ator

MTC Related Metering System Indicator	MTC Description	MTC _{Communication} _Indicator	MTC Type Indicator

Brief Description

A three-digit code representing the type of Metering System serving a customer’s premises.

Guidance on Change Process

When new MTCs are requested, both Meter Timeswitch Class and MTC for Distributor tables must be submitted. The first table sets up the MTC, while the second specifies which Distributor the MTC will be valid for. If the change is to extend an existing MTC (i.e. already present in Meter Timeswitch Class) to a further Distributor, only the MTC for Distributor table (Entity 53) is required.

When Change Requests are made for Meter Timeswitch Class with an Effective to Settlement Date, the associated MTC for Distributor (Entity 53) details should be checked, to ensure the Effective To Settlement Date MTCPA is no later than the Effective To Settlement Date MTC i.e. MTC for Distributor records cannot remain effective after the Meter Timeswitch Class is discontinued.

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
Meter Timeswitch Class Id	3	N	M	The MTC Id must be within the range 0-999.
MTC Meter Type Id	2	A/N	O	A code from those already defined on Entity 57.
Meter Type Effective From Settlement Date	10	D	O	The Settlement Date from which the Meter Type is active.
MTC Payment Type Id	2	A/N	O	A code from those already defined on Entity 58.
Payment Type Effective From Settlement Date	10	D	O	The Settlement Date from which the Payment Type is active.
MTC Effective From Settlement Date	10	D	M	The Settlement Date from which the Meter Timeswitch Class Id is active.
MTC Effective To Settlement Date	10	D	O	The last Settlement Date on which the MTC Id is active
MTC Common Code Indicator	1	A	M	Either T (Common) or F (Specific)
MTC Related Metering System Indicator	1	A	M	T (True) or F (False)
MTC Description	50 Max. (with spaces)	A/N	O	The narrative representation of the Meter Timeswitch Class.
MTC Communication Indicator	1	A	O	Either Y (Yes), N (No), X (Not Known).
MTC Type Indicator	1	A	O	Either ‘N’ (NHH Metering System), ‘H’ (HH Metering System), or ‘X’ (Metering System details not available).

Additional Validation
When raising a new Meter Timeswitch Class, if the MTC is not common (i.e. with a MTC Common Code Indicator of ‘F’) then the fields: MTC Meter Type Id, MTC Payment Type Id, MTC Description, MTC Communication Indicator and MTC Type Indicator must be null as they are held in the MTC for Distributor Areas.
When raising a new Meter Timeswitch Class, if the MTC is common (i.e. with a Common Code Indicator of ‘T’) then the Field Details: MTC Meter Type Id, MTC Payment Type Id, MTC Description, MTC Communication Indicator and MTC Type Indicator must be supplied.
Effective To Settlement Date MTC, where it is not null, must be greater than or equal to Effective From Settlement Date MTC.
MTC Type Indicator can only be updated if MTC Common Code Indicator equals ‘T’ and there are no child valid combinations.
The Meter Timeswitch Class Id must be within the range 0 – 999.
If the Meter Timeswitch Class Id is in either of the following ranges then the MTC Common Code Indicator must be ‘T’: 500 – 509 800 – 999
If the Meter Timeswitch Class Id is in either of the following ranges then the MTC Common Code Indicator must be ‘F’: 0 – 399 510 – 799
If the Meter Timeswitch Class Id is in the following range then the MTC Related Metering System Indicator must be ‘T’: 500 – 799
If the Meter Timeswitch Class Id is in either of the following ranges then the MTC Related Metering System Indicator must be ‘F’: 0 – 399 800 – 899
The range 400 – 499 is reserved. In this range the MTC Common Code Indicator and MTC Related Metering System Indicator can be either ‘T’ or ‘F’.
MTC Common Code Indicator can only be updated if the Meter Timeswitch Class Id is in the range 400 – 499 (the reserved range) and there are no child MTC for Distributor records.
MTC Related Metering System Indicator can only be updated if the Meter Timeswitch Class Id is in the range 400 – 499.

Links to Other Entities

There must be a Market Participant Role (Entity 45) with Role Code ‘R’ assigned to the Market Participant.

If MTC Meter Type Id is entered, then the value must exist in MTC Meter Types (Entity 57).

If MTC Payment Type Id is entered, then the value must exist in MTC Payment Type (Entity 58).

Examples of MDD Entity 52

For MTC Ids with a MTC Common Code of ‘F’, the MTC details are specific for each Distributor and defined under the MTC for Distributor table. The Meter Timeswitch table submitted should look like the example given below:

Meter Timeswitch Class Id	MTC Meter Type Id	Meter Type Effective From Settlement Date	MTC Payment Type Id	Payment Type Effective From Settlement Date	Effective From Settlement Date {MTC}	Effective To Settlement Date {MTC}	MTC Common Code Indicator
1					01/04/1006		F

MTC Related Metering System Indicator	MTC Description	MTC Communication Indicator	MTC Type Indicator
F

For MTC Ids with MTC Common Code of ‘T’, the MTC details are common and the same for each GSP Group. The Meter Timeswitch table submitted should look like the example given below:

Meter Timeswitch Class Id	MTC Meter Type Id	Meter Type Effective From Settlement Date	MTC Payment Type Id	Payment Type Effective From Settlement Date	Effective From Settlement Date {MTC}	Effective To Settlement Date {MTC}	MTC Common Code Indicator
864	TN	01/04/1006	CR	01/04/1006	10/11/2000		T
MTC Related Metering System Indicator	MTC Description	MTC Communication Indicator	MTC Type Indicator
F	Economy	N	N

3.24 Entity 53 - Meter Timeswitch Class for Distributor

Meter Timeswitch Class Id	MTC Effective From Settlement Date	MTC Effective To Settlement Date	MTC Common Code Indicator	Market Participant Role Code	Market Participant Role Effective From Settlement Date	MTC Meter Type Id	Meter Type Effective From Settlement Date	MTC Payment Type Id

Payment Type Effective From Settlement Date	Distributor Id	MTC Description	MTC Communication Indicator	MTC Type Indicator	MTC for Distributor Effective From Date	MTC for Distributor Effective To Date

Brief Description

Indicates that a particular Meter Timeswitch Class is supported by a Distributor.

Guidance on Change Process

Existing MTCs can be extended to cover further GSP Groups. If a valid entry exists for the MTC in Meter Timeswitch Class, the MTC can be extended to a further GSP Group by adding an entry to MTC for Distributor.

When a Change Request is made to discontinue a MTC for Distributor, by giving a MTC for Distributor Effective To Settlement Date, the following should be checked:

All valid child combinations that belong to the discontinued MTC for Distributor have an Effective To Settlement Date earlier or equal to that for the MTC for Distributor record. All valid child combinations that belong to the discontinued MTC for Distributor have an Effective To Settlement Date earlier or equal to that for the MTC for Distributor record.
When a Change Request is made to discontinue a Market Participant Role with Role Code ‘R’, the Participant should check all MTC for Distributor combinations that belong to the closed MPR record. In each case the Effective To Settlement Date of the MTC for Distributor should be no later than Effective To Settlement Date of the Market Participant role.

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
Meter Timeswitch Class Id	3	N	M	The MTC Id must be within the range 0-999.
MTC Effective From Settlement Date	10	D	M	The Settlement Date from which the Meter Timeswitch Class Id is active.
MTC Effective To Settlement Date	10	D	O	The last Settlement Date on which the MTC Id is active.
MTC Common Code Indicator	1	A	M	Indicator set to T (Common) or F (Specific).
Market Participant Role Code	1	A/N	M	Distributor role code ‘R’.
Market Participant Role Effective From Settlement Date	10	D	M	The Settlement Date from which the Market Participant Role is active.
MTC Meter Type Id	2	A/N	O	Code from those already defined on Entity 57.
Meter Type Effective From Settlement Date	10	D	O	The Settlement Date from which the Meter Type is active.
MTC Payment Type Id	2	A/N	O	Code from those already defined on Entity 58.
Payment Type Effective From Settlement Date	10	D	O	The Settlement Date from which the Payment Type is active.
Distributor Id	4	A	M	The Market Participant id for the Distributor.
MTC Description	50 Max. (with spaces)	A/N	O
MTC Communication Indicator	1	A	O	Either Y (Yes), N (No), or X (Not Known).
MTC Type Indicator	1	A	O	Either ‘N’ (NHH Metering System), ‘H’ (HH Metering System) or ‘X’ (Metering System details not available).
MTC for Distributor Effective From Settlement Date	10	D	M	The Settlement Date from which the MTC for Distributor is active.
MTC for Distributor Effective To Settlement Date	10	D	O	The last Settlement Date on which the MTC for Distributor is active.

Additional Validation

If the MTC Common Code Indicator equals ‘T’ then the fields: MTC Meter Type Id, MTC Payment Type Id, MTC Description, MTC Communication Indicator and MTC Type Indicator must be null as they are held in Meter Timeswitch Class table instead.

If MTC Common Code Indicator equals ‘F’ then the fields: MTC Meter Type Id, MTC Payment Type Id, MTC Description, MTC Communication Indicator and MTC Type Indicator must be supplied.

MTC Type Indicator can only be updated if the Common Code Indicator equals ‘F’ and there are no associated valid combinations.

Additional Validation

The Effective From/To Settlement Dates MTC for Distributor must fall within the Effective From/To Settlement Dates MTC for the parent Meter Timeswitch Class.

The Effective From/To Settlement Dates MTC for Distributor must fall within the Effective From/To Settlement Dates MPR for the linked Market Participant Role.

Effective To Settlement Date MTC for Distributor, if entered, must be greater than or equal to Effective From Settlement Date MTC for Distributor.

It is not permissible to have more than one MTC for Distributor, with the same Meter Timeswitch Class Id and Distributor Id, effective in MDD for the same Distributor.

For Distributor specific MTCs the MTC Common Code must equal ‘F’.

For Common MTCs the MTC Common Code must equal ‘T’.

Links to Other Entities

There must be a Market Participant Role (Entity 45) with Role Code ‘R’ assigned to the Market Participant.

A record for Meter Timeswitch Class Id must exist in Meter Timeswitch Class (Entity 52).

If MTC Meter Type Id is entered, then the value must exist in MTC Meter Types (Entity 57).

If MTC Payment Type Id is entered, then the value must exist in MTC Payment Type (Entity 58).

Examples of MDD Entity 53

The details in the 5 columns MTC Meter Type Id, MTC Payment Id, MTC Description, MTC Communication Indicator and MTC Type Indicator should be given in the MTC for Distributor table if the common code indicator is set = ‘F’, since they will be typically different for each GSP Group:

In this example, since all of the values in the 5 columns are Specific, they are detailed in the MTC for Distributor table below.

Meter Timeswitch Class Id	MTC Effective From Settlement Date	MTC Effective To Settlement Date	MTC Common Code Indicator	Market Participant Role Code	Market Participant Role Effective From Settlement Date	MTC Meter Type Id	Meter Type Effective From Settlement Date	MTC Payment Type Id
1	01/04/1996		F	R	01/03/1996	UM		CR

Payment Type Effective From Settlement Date	Distributor Id	MTC Description	MTC Communication Indicator	MTC Type Indicator	MTC for Distributor Effective From Date	MTC for Distributor Effective To Date
	ABCD	Budget Warmth	N	N	01/05/1996

In the example below, all of the values in the 5 columns are Common, the MTC Common Code Indicator is set to ‘T’ in the Meter Timeswitch Class entity and the columns are detailed in the Meter Timeswitch Class (Entity 52), so the MTC for Distributor table should look like below:

Meter Timeswitch Class Id	MTC Effective From Settlement Date	MTC Effective To Settlement Date	MTC Common Code Indicator	Market Participant Role Code	Market Participant Role Effective From Settlement Date	MTC Meter Type Id	Meter Type Effective From Settlement Date	MTC Payment Type Id
1	01/04/1996		T	R	01/03/1996

Payment Type Effective From Settlement Date	Distributor Id	MTC Description	MTC Communication Indicator	MTC Type Indicator	MTC for Distributor Effective From Date	MTC for Distributor Effective To Date
	ABCD				01/05/1996

3.25 Entity 54 - Valid MTC SSC Combinations

Meter Timeswitch Class Id	Effective From Settlement Date {MTC}	Market Participant Id	Effective From Settlement Date of MTC for Distributor	Effective To Settlement Date of MTC for Distributor	Standard Settlement Configuration Id	SSC Effective From Settlement Date	SSC Effective To Settlement Date	Valid MTC/SSC Effective From Settlement Date	Valid MTC/SSC Effective To Settlement Date

Brief Description

A valid combination of Meter Timeswitch Class and Standard Settlement Configuration

Guidance on Change Process

See the Entity Diagram in Section 4.2 for valid combinations.

When Change Requests are made for Valid MTC SSC Combination with an Effective To Settlement Date VMTCSC the Participant should check that all related valid combinations (Entity 56 and Entity 63) have an Effective To Settlement Date no later than Effective To Settlement Date VMTCSC.

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
Meter Timeswitch Class Id	3	N	M	The MTC Id must be within the range 0-999.
MTC Effective From Settlement Date	10	D	M	The Settlement Date from which the Meter Timeswitch Class Id is active.
Market Participant Id	4	A	M	The Distributor Id.
Effective From Settlement Date of MTC for Distributor	10	D	M	The Settlement Date from which MTC for Distributor is active.
Effective To Settlement Date of MTC for Distributor	10	D	O	The last Settlement Date on which MTC for Distributor is active.
SSC Id	4	N	M	The relevant SSC Id to be linked to the MTC Id.
SSC Effective From Settlement Date	10	D	M	The first Settlement Date on which the Standard Settlement Configuration is active.
SSC Effective To Settlement Date	10	D	O	The last Settlement Date on which the Standard Settlement Configuration is active.
Valid MTC/SSC Combination Effective From Settlement Date	10	D	M	The first Settlement Date on which the Valid MTC SSC Combination is active.
Valid MTC/SSC Combination Effective To Settlement Date	10	D	O	The last Settlement Date on which the Valid MTC SSC Combination is active, must be the same as the MDD Go Live Date or later.

Additional Validation
A Valid MTC SSC Combination can only be created if a parent record exists in MTC for Distributor with a Type Indicator of ‘N’, or Type Indicator is null and the parent Meter Timeswitch Class Type Indicator equals ‘N’.
A Valid Standard Settlement Configuration Id must exist in Standard Settlement Configurations.
The Effective From/To Settlement Dates VMTCSC must fall within the Effective From/To Settlement Dates MTC for Distributor.
The Effective From/To Settlement Dates VMTCSC must fall within the Effective From/To Settlement Dates for the linked Standard Settlement Configuration.
Effective To Settlement Date VMTCSC, where it is not null, must be greater than or equal to Effective From Settlement Date VMTCSC.
It is not permissible to have more than one Valid MTC SSC Combination, with the same Meter Timeswitch Class Id, Distributor Id and Standard Settlement Configuration Id effective in MDD at the same time.
All SSCs associated with a given MTC for Distributor must have the same number of Measurement Requirements.
Effective From Settlement Date VMTCSC must be the same as the MDD Go Live date or later.
Effective From Settlement Date MTC, Effective From Settlement Date MTC for Distributor must be the same as in MDD, or if they are all being set up simultaneously, must be the same as the MDD Go Live date or later.

Links to Other Entities

SSC must have an entry in the Standard Settlement Configuration table (Entity 32).

3.26 Entity 55 - Valid MTC LLFC Combinations

Meter Timeswitch Class Id	MTC Effective From Settlement Date	Market Participant Id	Effective From Settlement Date of MTC for Distributor	Effective To Settlement Date of MTC for Distributor	Line Loss Factor Class Id	Market Participant Role Code	Market Participant Role Effective From Settlement Date

LLFC Effective From Settlement Date	LLFC Effective To Settlement Date	Valid MTC/LLFC Combination Effective From Settlement Date	Valid MTC/LLFC Combination Effective To Settlement Date

Brief Description

A valid combination of Meter Timeswitch Class and Line Loss Factor Class.

Guidance on Change Process

See the Entity Diagram in Section 4.2.

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
Meter Timeswitch Class Id	3	N	M	The MTC Id must be within the range 0-999.
MTC Effective From Settlement Date	10	D	M	The Settlement Date from which the Meter Timeswitch Class Id is active.
Market Participant Id	4	A	M	The Distributor Id.
Effective From Settlement Date of MTC for Distributor	10	D	M	The Settlement Date from which MTC for Distributor is active
Effective To Settlement Date of MTC for Distributor	10	D	O	The last Settlement Date on which MTC for Distributor is active
Line Loss Factor Class Id	3	A/N	M	The relevant LLFC Id to be linked to the MTC Id. Excluding ‘000’ and any combination using ‘I’ or ‘O’ or starting ‘0’ or ‘00’.
Market Participant Role Code	1	A/N	M	The Distributor Role Code ‘R’.
Market Participant Role Effective From Settlement Date	10	D	M	The Settlement Date the Market Participant became active in this role.
LLFC Effective From Settlement Date	10	D	M	The first Settlement Date on which the Line Loss Factor Class is active.
LLFC Effective To Settlement Date	10	D	O	The last Settlement Date on which the Line Loss Factor Class is active.
Valid MTC/LLFC Combination Effective From Settlement Date	10	D	M	The first Settlement Date on which the Valid MTC LLFC Combination is active.
Valid MTC/LLFC Combination Effective To Settlement Date	10	D	O	The last Settlement Date on which the Valid MTC LLFC Combination is active. If entered, must be the same as the MDD Go Live Date or later.

Additional Validation
A Valid MTC LLFC Combination can only be created if a parent record exists in MTC for Distributor with a MTC Type Indicator of ‘H’, or Type Indicator is null and the parent Meter Timeswitch Class Type Indicator of ‘H’.
LLFC can have any MS Specific Type Indicator.
The Effective From/To Settlement Dates VMTCLC must fall within the Effective From/To Settlement Dates for Distributor of the parent MTC for Distributor.
The Effective From/To Settlement Dates VMTCLC must fall within the Effective From/To Settlement Dates for the parent Line Loss Factor Class.
Effective To Settlement Date VMTCLC, where it is not null, must be greater than or equal to Effective From Settlement Date VMTCLC.
It is not permissible to have more than one Valid MTC LLFC Combination, with the same Meter Timeswitch Class Id, Distributor Id and Line Loss Factor Class Id, effective in MDD at the same time.
Effective From Settlement Date VMTCLC must be the same as the MDD Go Live date or later.
Effective From Settlement Date MTC, Effective From Settlement Date for Distributor must correspond with the dates held in MDD, or if they are all being set up simultaneously, must be the same as the MDD Go Live date or later.

Links to Other Entities

There must already be a Market Participant record (Entity 1) and Market Participant Role (Entity 45).

There must be a valid Line Loss Factor Class (Entity 17) for the participant.

There must be a valid Meter Timeswitch Class (Entity 52) and Meter Timeswitch Class for Distributor (Entity 53).

3.27 Entity 56 - Valid MTC SSC LLFC Combinations

Meter Timeswitch Class Id	Distributor Id	Standard Settlement Configuration Id	Valid MTC/SSC Effective From Settlement Date	Valid MTC/SSC Effective To Settlement Date	Line Loss Factor Id	Market Participant Role	Market Participant Role Effective From Settlement Date

LLFC Effective From Settlement Date	LLFC Effective To Settlement Date	Valid MTC/LLFC/SSC Combination Effective From Settlement Date	Valid MTC/LLFC/SSC Combination Effective To Settlement Date

Brief Description

Allows the user to link specific Line Loss Factor Classes to Valid MTC SSC Combinations.

Guidance on Change Process

See the Entity Diagram in Section 4.2.

When Change Requests are made for Valid MTC LLFC SSC Combinations with an Effective To Settlement Date VMTCLSC the Participant should check that all related Valid MTC LLFC SSC PC Combinations (Entity 63) have an Effective To Settlement Date VMTCLSCPC no later than Effective To Settlement Date VMTCLSC

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
Meter Timeswitch Class Id	3	N	M	In the range 0-999.
Distributor Id	4	A	M	The Market Participant Id
Standard Settlement Configuration Id	4	N	M	In the range 0000-9999. The SSC Id linked to the MTC Id.
Valid MTC/SSC Effective From Settlement Date	10	D	M	The first Settlement Date on which the MTC/SSC combination is active.
Valid MTC/SSC effective To Settlement Date	10	D	O	The last Settlement Date on which the MTC/SSC combination is active.
Line Loss Factor Class Id	3	A/N	M	Excluding ‘000’ and any combination using ‘I’ or ‘O’ or starting ‘0’ or ‘00’. The relevant LLFC Id to be linked to the Valid MTC SSC Combination.
Market Participant Role	1	A/N	M	The Distributor Role Code - ‘R’.
Market Participant Role Effective From Settlement Date	10	D	M	The Settlement Date on which the Market Participant became active in the Role.
LLFC Effective From Settlement Date	10	D	M	The first Settlement Date on which the Line Loss Factor Class is active.
LLFC Effective To Settlement Date	10	D	O	The last Settlement Date on which the Line Loss Factor Class is active.
Valid MTC/LLFC/SSC Combination Effective From Settlement Date	10	D	M	The first Settlement Date on which the Valid MTC SSC LLFC Combination is active.
Valid MTC/LLFC/SSC Combination Effective To Settlement Date	10	D	O	The last Settlement Date on which the Valid MTC SSC LLFC Combination is active.

Additional Validation
The MTC must have a MTC Type Indicator of ‘N’, indicating a NHH Metering System.
Only an LLFC with a MS Specific LLFC Indicator of ‘A’ can be linked to an SSC with Type of ‘I’.
Only an LLFC with a MS Specific LLFC Indicator of ‘C’ can be linked to an SSC with Type of ‘E’.
The Valid MTC/LLFC/SSC Combination Effective From/To Settlement Dates must fall within the Valid MTC/SSC Effective From/To Settlement Dates for the Valid MTC SSC Combination.
The Valid MTC/LLFC/SSC Combination Effective From/To Settlement Dates must fall within the LLFC Effective From/To Settlement Dates for the linked LLFC.
When end-dating a Valid MTC SSC LLFC Combination, the Valid MTC/LLFC/SSC Combination Effective To Settlement Date must be greater than or equal to the Valid MTC/LLFC/SSC Combination Effective From Settlement Date.
When end-dating a Valid MTC SSC LLFC Combination, the Valid MTC/LLFC/SSC Combination Effective To Settlement Date must be greater than or equal to the MDD Go-live date.
It is not permissible to have more than one Valid MTC LLFC SSC Combination, with the same Meter Timeswitch Class Id, Distributor Id, Standard Settlement Configuration Id and Line Loss Factor Class Id, effective in MDD at the same time.

Links to other entities

There must already be a Market Participant (Entity 1) and Market Participant Role (Entity 45).

There must already be a Line Loss Factor Class (Entity 17) for the LLFC and Distributor.

A Valid MTC SSC Combination (Entity 54) must exist with the matching MTC and SSC codes.

There must be a valid Meter Timeswitch Class (Entity 52) and Meter Timeswitch Class for Distributor (Entity 53).

3.28 Entity 57 - MTC Meter Types

MTC Meter Type Id	MTC Meter Type Description	Effective From Settlement Date {MMT}	Effective To Settlement Date {MMT}

Brief Description

Indicates the capability of the meter, with the exception of COP 1-5 meters currently being used for register load billing (i.e. Profiled), which will be treated as TP (Timeswitch Programmable).

Guidance on Change Process

Introduction of a new meter type with a capability not covered by the existing data set would require additional data to be created for this entity.

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
MTC Meter Type Id	2	A/N	M	The id for the MTC Meter type.
MTC Meter Type Description	50 Max. (with spaces)	A/N	M	Description of the MTC Meter Type Id.
Effective From Settlement Date {MMT}	10	D	M	The Settlement Date from which the Meter Type Id is active.
Effective To Settlement Date {MMT}	10	D	O	The last Settlement Date on which the Meter Type Id is active.

Additional Validation

Effective To Settlement Date MMT, where it is entered, must be greater than or equal to Effective From Settlement Date MMT.

It is not permissible to have more than one MTC Meter Type, with the same MTC Meter Type Id, effective in MDD at the same time.

3.29 Entity 58 - MTC Payment Type

MTC Payment Type Id	MTC Payment Type Description	Effective From Settlement Date {MPT}	Effective To Settlement Date {MPT}

Brief Description

This function allows the user to maintain details of MTC Payment Type.

Guidance on Change Process

The introduction of metering with a payment methodology not covered by the existing set would require additional data to be created for this entity.

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
MTC Payment Type Id	2	A/N	M	The Id for the MTC payment type.
MTC Payment Type Description	50 Max. (with spaces)	A/N	M	Description of the MTC Payment Type Id.
Effective From Settlement Date {MPT}	10	D	M	The Settlement Date from which the Payment Type Id is active.
Effective To Settlement Date {MPT}	10	D	O	The last Settlement Date on which the Payment Type Id is active.

Additional Validation

If entered, the Effective To Settlement Date MPT must be greater than or equal to Effective From Settlement Date MPT.

It is not permissible to have more than one MTC Payment Type, with the same MTC Payment Type Id, effective in MDD at the same time.

3.30 Entity 60 - GSP Group Profile Tolerances

Profile Class Id	GSP Group Id	Lower limit Tolerance	Upper Limit Tolerance

Brief Description

Profile Class Tolerances are used during the EAC/AA calculation and are GSP Group specific.

Guidance on Change Process

The tolerances for this entity may be changed from time to time as directed by the BSC Panel or delegated BSC Panel Committee.

Introduction of new Profile Classes or GSP groups would also require additional data to be created for this entity and would also be directed by the BSC Panel or delegated BSC Panel Committee.

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
Profile Class Id	1	N	M	The profile classification identified as a number from 1-8.
GSP Group Id	2	_A	M	The identifier for the relevant GSP Group.
Lower Limit Tolerance	7	N	M	Must be a negative integer value in kWh.
Upper Limit Tolerance	7	N	M	Must be a positive integer value in kWh.

3.31 Entity 61 - Base BM Unit for Supplier in GSP Group

GSP Group	Market Participant (Supplier) ID	Market Participant _Role_Code	Effective From Date {MPR}	BM Unit ID	Effective From Settlement Date _{BMUIGG}	Effective To Settlement Date {BMUIGG}

Brief Description

A BM Unit is a representation of an association of generation equipment or of consumption, as the case may be, registered under the BSC for the purposes of participation in the Balancing Mechanism. Every single Metering System in Great Britain, whether for generation or consumption, is a component of a BM Unit (and only one BM Unit).

There are two different types of BM Unit, Base BM Units and Additional BM Units. For the purpose of clarification the distinction between the two types of BM Unit is as follows:

A set of Base BM Units will be assigned to the first Supplier ID registered by a Party. All Suppliers must have one Initial Base BM Unit in each GSP Group.

Suppliers are permitted to register Additional BM Units and can choose to use any of the Supplier IDs that they have registered, provided that the Supplier ID chosen is effective in MDD. There is no requirement for a Supplier to register an Additional BM Unit in each GSP Group and there is no limit to the number of Additional BM Units that a Supplier can register in each GSP Group.

Guidance on Change Process
For any SVA BM Unit to be successfully registered, it needs to be recorded in two separate systems that operate independently of one another, the Market Domain Data (MDD) system and the Central Registration Agency (CRA) system. Both systems need to be synchronised with the same data at the same time and in order to ensure that this occurs, a number of process controls are in place. The registration and de-registration processes for each type of BM Unit are documented in BSCP509 and BSCP15, for Base BM Units and Additional Base BM Units BSCP65 and for Additional BM Units BSCP509 and BSCP15. The following paragraph gives a brief description of how the validation process works. All types of SVA BM Unit are subject to the same process controls during registration or de-registration. The Party is required to register or de-register the BM Units in the CRA and MDD systems in parallel, with the same Effective From / To Date in both systems. The process takes approximately 30 Working Days and is initiated by the Party declaring their intention to register or de-register a set of SVA BM Units to both the CRA and BSCCo. BSCCo will ensure the following criteria are met: that the Party is aware of their obligation to register in both the MDD and CRA systems simultaneously that the Party is aware of the time-scales involved that the Party is aware of the requirement to synchronise the Effective To / From Dates in both the MDD and CRA systems that the Effective To / From Dates are required to be on or after the next ‘Go-Live’ date of MDD.
Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
GSP Group Id	2	_A	M	The identifier for the relevant GSP Group.
Market Participant (Supplier) Id	4	A	M	The identifier for the Market Participant.
Market Participant Role Code	1	A/N	M	The assigned role code for the Market Participant (Supplier ‘X’).
Effective From Date {MPR}	10	D	M	The date on which the Market Participant was accredited as a Supplier.
BM Unit Id	11	A/N	M	See Additional Validation for format of the BM Unit Id.
Effective From Date {BMUIGG}	10	D	M	The first day on which the BM Unit was active within the GSP Group
Effective To Date {BMUIGG}	10	D	O	The last day on which the BM Unit was active within the GSP Group

Additional Validation

The naming convention for Base and Additional BM Units is as follows:

Base BM Unit, 2__ASUPP000 Additional BM Unit, 2__ASUPP001

(2_) = SVA BM Unit (2_) = SVA BM Unit

(_A) = GSP Group _A (_A) = GSP Group _A

(SUPP) = 4 Character Supplier ID (SUPP) = 4 Character Supplier ID

(000) = Base BM Unit (001)* = Additional BM Unit

*The number increments as more additional BM Units are registered.

You cannot have more than one occurrence of BM Unit for Supplier in GSP Group for the same BM Unit Id effective on the same Settlement Date.

Each combination of GSP Group and Market Participant with a Supplier Role Code of ‘X’ must have one instance of BM Unit for Supplier in GSP Group with the Default BM Unit Flag set to ‘T’ TRUE from the Effective From Settlement Date, this must be greater than or equal to either the NETA Start Date (27/03/2001) where Region Id equals ‘EW’ (GSP Group’s in England/Wales) or BETTA Start Date (01/04/2005) where Region Id equals ‘S’ (GSP Group’s in Scotland).

Links to Other Entities

There must be a Market Participant (Entity 1) and a Market Participant Role (Entity 45) with Role Code ‘X’ assigned to the Market Participant.

3.32 Entity 62 - Details of Proposed Change to Unmetered Supplies Operational Information

Proposed Change to Unmetered Supplies Operational Information
Section
Page number
Reason for Change.
Details of Change (including redlined version of change, if appropriate).
Additional Information

Brief Description

Proposed changes to the Unmetered Supplies Operational Information are incorporated in the MDD Impact Assessment Circular. However, they are not added to any EDMS data flow, but remain in the existing document format and are held on the BSC Website. MDD Circulars refer participants to the location of the Operational Data document on the website.

This information is not included in the MDD database, but can be found on the BSC Website.

3.33 Entity 63 - Valid MTC LLFC SSC PC Combinations

Meter Timeswitch _Class_Id	Distributor Id	Standard Settlement Configuration Id	Valid MTC/SSC Effective From Settlement Date	Line Loss Factor _Class_Id	Market Participant _Role_Code	Market Participant Role Effective From Settlement Date	LLFC Effective From _Settlemen_t_Date

Valid MTC/LLFC/SSC Combination _Effective_From_Settlemen_t_Date	Profile Class _Id	Valid MTC/LLFC/SSC/PC Combination _Effectiv_e_From_Settlemen_t_Date	Valid MTC/LLFC/SSC/PC Combination _Effective_To_Settlemen_t_Date	Preserved _Tariff_Indicator

Brief Description

Allows the user to link specific Profile Classes to Valid MTC LLFC SSC Combinations.

Guidance on Change Process

See the Entity Diagram in Section 4.2.

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
Meter Timeswitch Class Id	3	N	M	In the range 0-999.
Distributor Id	4	A	M	The Market Participant Id
Standard Settlement Configuration Id	4	N	M	In the range 0000-9999. The SSC Id linked to the MTC Id.
Valid MTC/SSC Effective From Settlement Date	10	D	M	The first Settlement Date on which the MTC/SSC combination is active.
Line Loss Factor Class Id	3	A/N	M	Excluding ‘000’ and any combination using ‘I’ or ‘O’ or starting ‘0’ or ‘00’. The relevant LLFC Id linked to the MTC/SSC combination.
Market Participant Role Code	1	A/N	M	The Distributor Role Code – ‘R’
Market Participant Role Effective From Settlement Date	10	D	M	The Settlement Date on which the Market Participant became active in the Role.
LLFC Effective From Settlement Date	10	D	M	The first Settlement Date on which the Line Loss Factor Class is active.
Valid MTC/LLFC/SSC Combination Effective From Settlement Date	10	D	M	The first Settlement Date on which the Valid MTC SSC LLFC Combination is active.
Profile Class Id
Valid MTC/LLFC/SSC/PC Combination Effective From Settlement Date	10	D	M	The first Settlement Date on which the Valid MTC SSC LLFC PC Combination is to be active.
Valid MTC/LLFC/SSC/PC Combination Effective To Settlement Date	10	D	O	The last Settlement Date on which the Valid MTC SSC LLFC PC Combination is to be active.
Preserved Tariff Indicator	1	A	M	The Preserved Tariff Indicator, “T” or “F”

Additional Validation
The MTC must have a MTC Type Indicator of ‘N’, indicating a NHH Metering System.
Only an LLFC with a MS Specific LLFC Indicator of ‘A’ can be linked to an SSC with Type of ‘I’.
Only an LLFC with a MS Specific LLFC Indicator of ‘C’ can be linked to an SSC with Type of ‘E’.
The Valid MTC/LLFC/SSC/PC Combination Effective From/To Settlement Dates must fall within the Valid MTC/LLFC/SSC Combination Effective From/To Settlement Dates for the Valid MTC LLFC SSC Combination.
The Valid MTC/LLFC/SSC/PC Combination Effective From/To Settlement Dates must fall within the Valid Settlement Configuration Profile Class Effective From/To Settlement Dates for the linked Profile Class and SSC.
When end-dating a Valid MTC SSC LLFC PC Combination, the Valid MTC/LLFC/SSC/PC Combination Effective To Settlement Date must be greater than or equal to the Valid MTC/LLFC/SSC/PC Combination Effective From Settlement Date.
When end-dating a Valid MTC SSC LLFC PC Combination, the Valid MTC/LLFC/SSC/PC Combination Effective To Settlement Date must be greater than or equal to the MDD Go-live date.
It is not permissible to have more than one Valid MTC LLFC SSC PC Combination, with the same Meter Timeswitch Class Id, Distributor Id, Standard Settlement Configuration Id, Line Loss Factor Class Id and Profile Class Id, effective in MDD at the same time.
Preserved Tariff Indicator must be either T (True) or F (False

Links to other entities

There must already be a Market Participant (Entity 1) and Market Participant Role (Entity 45).

There must already be a Line Loss Factor Class (Entity 17) for the LLFC and Distributor.

A Valid MTC SSC Combination (Entity 54) must exist with the matching MTC and SSC codes.

There must be a valid Meter Timeswitch Class (Entity 52) and Meter Timeswitch Class for Distributor (Entity 53).

SSC must have an entry in the Standard Settlement Configuration table (Entity 32).

Profile Class and SSC must have an entry in the Valid Settlement Configuration Profile Class (Entity 40) table.

A Valid MTC LLFC SSC Combination (Entity 56) must exist with the matching MTC, SSC and LLFC codes.

3.34 Entity 64 – SMETS Version

SMETS Version	SMETS Version Description

Brief Description

The available versions of the Smart Metering Equipment Technical Specifications (SMETS) established under the Smart Energy Code (SEC).

Guidance on Change Process

Introduction of new versions of the SMETS will be initiated under SEC governance, but once approved will be reflected as an update to this entity, usually progressed by BSCCo.

Field Details
Fieldname	No of Chars	Format	M/O	Description/Comments
SMETS Version	8	A/N	M	Identifier of the particular SMETS Version.
SMETS Version Description	30	A/N	M	Long description of the particular SMETS Version.

3.35 Entities Changed by the BSCCo.

The following entities make up the Base Calendar information and are updated annually by the BSCCo.

Entity No.	Entity Name	Description and comments
14	Clock Time Changes	A change in the Time, e.g. a change from BST to GMT (or vice-versa).
16	Year	A calendar year in format yyyy e.g. 2007
22	Settlement Day	A date on which energy is deemed to be used and must be later settled through Supplier Volume Allocation Settlement and Reconciliation.
23	Settlement Period	A period of 30 minutes beginning on the hour or the half-hour, used in the BSC for Settlement purposes. The Settlement Period Id is unique within the Settlement Date.
26	Yearly Season Details	The start and end dates of the Seasons throughout the year.

3.36 Entities Changed by the Profile Administrator

The following entities are provided by the Profile Administrator and are updated annually.

Entity No.	Entity Name	Description and comments
5	Default Period Profile Class Coefficients	Coefficients used by Half Hourly Data Collectors (HHDC) to estimate demand values for Half Hourly meters.
6	GSP Group Average EAC	The estimated average annual consumption for Metering Systems for a GSP Group.
7	Period Regression Equation	A reference to a Regression Equation for a Settlement Period within a Profile, for a Season and Day-type combination.
8	Period Regression Equation Set	A reference to the Regression Equations for a Profile, Season and Day-type combination.
9	Profile Set	Reference for a set of Profile Data.
10	Regression Coefficient	A coefficient or variable which specifies how consumption for a Profile varies and is substituted into a Period Regression Equation Reference for a set of Profile Data.

3.37 Entities Changed by the SVAA

The following entity is provided by the SVAA and is updated annually.

Entity No.	Entity Name	Description and comments
15	Settlement Calendar	Used by all Market Participants to give them notification of their Payment dates and the dates to process and submit Data Aggregator data to the SVA Agent.

3.38 Rarely Changed Entities

The following entities are hardly ever changed as part of the Market Domain Data process.

Entity No.	Entity Name	Description and comments
19	GSP Group Correction Scaling Factor	A factor which can be applied to the GSP Group Correction Factor to define to what degree it will be applied to a particular Consumption Component Class.
21	Market Role	A code representing a Market Role that a Market Participant may take.
24	Smoothing Parameter	A standard positive factor which determines when calculating a new value for an EAC, how much weight is given to an AA and how much is given to the previous EAC.
25	Threshold Parameter	The minimum numbers of valid EACs/AAs that must be provided for averaging. These are used as the mechanism for determining an EAC substitute for missing or invalid EACs/AAs.
30	Profile	The reference number for a Profile, unique within Profile Class.
31	Profile Class	A classification of profile which represents an exclusive category of customers whose consumption can be reasonably approximated to a common profile for the purpose of attributing an EAC or AA to individual half hours for Settlement purposes. A Profile Class may be for Switched Load or Non-Switched Load.
41	Consumption Component Class	Identifies the category of Half Hourly and Non Half Hourly consumption.
42	Day of the Week	The reference number for a Day of the Week, used in the representation of Clock intervals.
43	Day Type	A two character code for the type or day e.g. Weekday, Saturday, Boxing Day etc.
44	Energisation Status	A one character code identifying the Energisation Status (either ‘E’ for Energised or ‘D’ for De-energised).
46	Measurement Class	Unique identifier for the measurement classification of a Metering System which determines how the power values for a Metering System are to be aggregated.
47	Measurement Quantity	A two character code that identifies the quantity that may be measured.
49	Regression Coefficient Type	A code identifier for the type of Regression Coefficient.
50	Season	A one character code identifier for the Season.
51	Settlement Type	The types of Settlement and reconciliation which can be performed for a Settlement Day.
59	Half Hourly Default EAC	Default EACs are used when estimating consumption for Half Hourly Metering Systems in the absence of sufficient historical data where the Supplier has not provided a metering specific value.

4 ENTITY DIAGRAM

4.1 Introduction

The purpose of this diagram is to show the relationship of the most common data entities raised and held in Market Domain Data.

The structure of the diagrams displays how records are positioned in a relationship format and should not be used for format checks or creating new records or profiles. The Participant should use existing information from their MDD records and Section 3 of this document which provides a valid check of the table entities needed to create an overall profile or new record.

4.2 Entity Diagram

Appendix A: Glossary

Term	Description
Annualised Advance (AA)	The rate of consumption for a Settlement Register over the period between two meter readings. The value is nominally expressed as kWh/Year, but this is only for ease of understanding and cannot be relied upon as a true value.
Average Fraction of Yearly Consumption	The specification of the proportion of the profile shape that falls within the designated Settlement Periods.
Average Fraction of Yearly Consumption Set	A set of data specifying how average consumption is split across registers for a particular GSP Group, SSC and Profile Class.
BM Unit	Balancing Mechanism (BM) Units are used as units of trade within the Balancing Mechanism. Each BM Unit accounts for a collection of plant and/or apparatus, and is considered the smallest grouping that can be independently controlled. As a result, most BM Units contain either a generating unit or a collection of consumption meters.
Calendar Data	Data including details of the dates of the Calendar Seasons, dates of British Summer Time and the timetable for certain operational requirements of the SVA Agent and Data Aggregators.
Clock Interval	The ‘on’ interval of a clock based Time Pattern Regime. Clock Intervals for a Time Pattern Regime are defined in terms of Start and End Dates, Days of the Week, and Start and End Times.
Clock Time Change	A change in the Date and Time or a change from BST to GMT or vice versa.
Clock Time Pattern Regime	A Time Pattern Regime associated with a clock-switched Standard Settlement Configuration.
Consumption Component Class	Identifies the category of Half Hourly and Non - Half Hourly consumption. For example, metered or unmetered.
Day of the Week	The reference number for a Day of the Week, used in the representation of Clock Intervals.
Day Type	An identifier for the type of Settlement Day, used to identify which regression equations and time patterns are valid on a specific Settlement Day.
Default Period Profile Class Coefficient	Coefficients used by Half Hourly Data Collectors (HHDC) to estimate demand values for Half Hourly meters.
Energisation Status	Identifies the Energisation status of the Metering System.
Estimated Annual Consumption (EAC)	An estimated rate of consumption, nominally expressed in kWh/Year, that is used in settlement until an AA is calculated.
GSP Group	The identifier of a distinct electrical system, consisting of all or part of a distribution system owned and operated by a Distributor that is supplied from one or more Grid Supply Points for which the total supply into the GSP Group can be determined for each half hour. There are currently 14 GSP Groups in England, Scotland and Wales. In Scotland the equivalent term BSP (Bulk Supply Point) is used and this has more or less the same definition to that described for a GSP Group in England and Wales. For simplicity the England and Wales GSP Groups and Scottish BSP Groups are held in the same GSP Group table of MDD.
GSP Group Average EAC	The estimated average annual consumption for Metering Systems for a GSP Group.
GSP Group Correction Scaling Factor	A factor which can be applied to the GSP Group Correction Factor to calculate how the GSP Group Factor will be applied to a particular consumption component class.
GSP Group Distributor	The Distributor for a GSP Group, from the specified Effective From Settlement Date.
GSP Group Daily Profile Class Average EAC	The estimated average annual consumption for Metering Systems in a Profile Class and Standard Settlement Configuration for a GSP Group.
GSP Group Profile Class Default EAC	The estimated average annual consumption for Metering Systems in a Profile Class for a GSP Group.
SVA Agent Appointment	SVA Agent appointed to a specific GSP Group. In practice this is the same Agent for all GSP Groups.
Line Loss Factor Class	The reference for a Line Loss Factor Class within a Distributor’s system which applies to a group of Metering Systems.
Market Participant	The unique market wide reference for a Market Participant.
Market Participant Role	Identifies the role that a Market Participant performs in the market.
Market Role	The Valid Set of market roles, identifying a Market Participant’s role. For example ‘Supplier’.
MDD Version	Identifies the version of the Market Domain Data publication.
Measurement Class	Unique identifier for the measurement classification of a Metering System which determines how values for a Metering System are to be aggregated.
Measurement Quantity	Identifies the quantity which may be measured. For example, consumption or generation.
Measurement Requirement	The set of Time Pattern Regimes for a Standard Settlement Configuration.
Meter Timeswitch Class	A three-digit code representing the type of Metering System serving a customer’s premises. Data recorded includes Half Hourly and Non - Half Hourly classes, Effective From and To Settlement Dates, permitted values of Meter Type code, Payment Type code and which Distribution areas support the code.
Metering System	A Metering System is made up of items of Metering Equipment; voltage transformers, current transformers, Meters and Outstations, the wires and connections between each item and connections required to transfer metered data to the outside world (e.g. modems and communication lines).
MTC in Distributor Area	Indicates that a particular Meter Timeswitch Class is supported in a SMR area.
MTC Meter Type	Indicates the capability of the meter.
MTC Payment Type	Identifies the method of payment associated with a Meter Timeswitch Class.
Parent record and child record relationship	MDD Datasets that contain related data tables are represented as a parent/child relationship. When creating or updating information in these tables it will also affect the relevant parent/child record containing the same data.
Period Regression Equation	A Regression Equation and associated Regression Coefficients for a Settlement Period within a Profile and GSP Group, for a season and day-type combination. When evaluated using GSP Group and Settlement Date specific parameters, the regression equation produces a Basic Period Profile Coefficient.
Profile	The reference number for a Profile, unique within Profile Class. Each set of profiles for a profile class will include one base load profile and a number of switched load profiles.
Profile Class	A classification of profile which represents an exclusive category of customers whose consumption can be reasonably approximated to a common profile for the purpose of attributing an EAC or AA to individual half hours for Settlement purposes.
Profiling Data	Researched numerical information used to estimate and profile electricity consumption in half hour periods for Metering Systems throughout the year.
Profile Regression Equation Set	The set of regression equations for a profile, for a season and day type combination.
Profile Set	A set of profile data as provided by the Profile Administrator.
Regression Coefficient	A coefficient or variable which specifies how consumption for a Profile varies and is substituted into a Period Regression Equation.
Regression Coefficient Type	The valid types of Regression Coefficient.
Season	The reference number for a season.
Settlement	Calendar or Settlement activities specifying dates that files must be delivered to the SVA Agent for processing.
Settlement Day	The date on which energy is deemed to be used and must be later settled through Supplier Volume Allocation Settlement and Reconciliation.
Settlement Period	The reference for a Settlement period, unique within Settlement Date. Periods Ids are assigned sequentially to each period in local time day.
Settlement Type	The types of Settlement and reconciliation which can be performed for a Settlement Day.
Smoothing Parameter	Parameter that controls how quickly Estimated consumption reacts to changes in actual consumption. A standard, positive factor which determines how much weight is given to an AA and how much is given to the previous EAC, when calculating a new value for an EAC.
SMR Agent Appointment	SMR Agent appointed to a specific GSP Group.
Standard Settlement Configuration	The unique market wide reference for a Standard Settlement Configuration (logical Non-Half Hourly metering configuration supported by the Settlement process). The data includes Settlement register ‘on’ times, teleswitch rules and average fractions of yearly consumption and estimates of annual consumption.
Teleswitch Time Pattern Regime	A Time Pattern Regime associated with a teleswitched Standard Settlement Configuration. A Teleswitch Time Pattern Regime can only belong to one Teleswitch Group.
Threshold Parameter	The minimum numbers of valid EACs/AAs that must be provided for averaging to be used as the mechanism for determining an EAC substitute for missing or invalid EAC/AAs.
Time Pattern Regime	The unique market wide reference for a Time Pattern Regime being used to calculate money owed for energy used by each customer. A pattern of switching behaviour through time that one or more Settlement registers uses.
Valid Sets	Valid Sets are tables of information that define the discrete set of values allowable for certain data items and are used to check MDD against mis-specification or inconsistency.
Valid Measurement Requirement Profile Class	Measurement Requirement within a valid Standard Settlement Configuration and Profile Class set.
Valid Settlement Configuration Profile Class	The valid Standard Settlement Configurations for a Profile Class.
Valid MTC SSC Combination	Indicates that a particular combination of Meter Timeswitch Class and Standard Settlement Configuration is supported in a Distributor area. Specified for Non - Half Hourly MTCs only
Valid MTC LLFC Combination	Indicates that a particular combination of Meter Timeswitch Class and Line Loss Factor Class is supported in a Distributor area. Specified for Half Hourly MTCs only.
Valid MTC LLFC SSC Combination	Indicates that a particular combination of Meter Timeswitch Class, Standard Settlement Configuration and Line Loss Factor Class is supported in a Distributor area. Specified for Non - Half Hourly MTCs only.
Valid MTC LLFC SSC PC Combination	Indicates that a particular combination of Meter Timeswitch Class, Standard Settlement Configuration, Line Loss Factor Class and Profile Class is supported in a Distributor area. Specified for Non-Half Hourly MTCs only.
Year	A valid Settlement year.
Yearly Season Details	Data detailing the dates of the seasons throughout the year.

Need more information?

For more information please contact the BSC Service Desk at bscservicedesk@cgi.com or call 0870 010 6950.

1 Key: Format:A=Alphabetic, N=Numeric, A/N=Alphanumeric, D=Date (dd/mm/yyyy), M/O: M=Mandatory, O=Optional

BSC Procedures

CONTENTS

BSCP509 Appendix 02: MDD Change Request Entity Validation

1 INTRODUCTION

1.1 Background

1.2 Purpose of this Document

1.3 MDD Format

1.4 Code Subsidiary Documentation

2 ACRONYMS AND DEFINITIONS

3 MDD DATA ENTITIES

3.1 Entity 1 – Market Participant ID1

3.2 Entity 2 – GSP Licensed Distribution System Operator

3.3 Entity 3 – SVA Agent Appointment

3.4 Entity 4 – SMR Agent Appointment

3.5 Entity 11 – Average Fraction of Yearly Consumption Set

3.6 Entity 12 – Average Fraction of Yearly Consumption

3.7 Entity 13 – GSP Group Daily Profile Class Average EAC

3.8 Entity 17 – Line Loss Factor Class (LLFCs)

3.9 Entity 18 – GSP Group

3.10 Entity 20 – GSP Group Profile Class Default EAC

3.11 Entity 27 - Clock Interval

3.12 Entity 29 - Measurement Requirement

3.13 Entity 32 - Standard Settlement Configuration

3.14 Entity 33 - Teleswitch Time Pattern Regime

3.15 Entity 34 - Teleswitch Register Rules

3.16 Entity 35 - Teleswitch Contact Rule

3.17 Entity 36 – Teleswitch Contact

3.18 Entity 37 - Teleswitch Group

3.19 Entity 38 - Time Pattern Regime

3.20 Entity 39 - Valid Measurement Requirement Profile Class

3.21 Entity 40 - Valid Settlement Configuration Profile Class

3.22 Entity 45 - Market Participant Role

3.23 Entity 52 - Meter Timeswitch Class

3.24 Entity 53 - Meter Timeswitch Class for Distributor

3.25 Entity 54 - Valid MTC SSC Combinations

3.26 Entity 55 - Valid MTC LLFC Combinations

3.27 Entity 56 - Valid MTC SSC LLFC Combinations

3.28 Entity 57 - MTC Meter Types

3.29 Entity 58 - MTC Payment Type

3.30 Entity 60 - GSP Group Profile Tolerances

3.31 Entity 61 - Base BM Unit for Supplier in GSP Group

3.32 Entity 62 - Details of Proposed Change to Unmetered Supplies Operational Information

3.33 Entity 63 - Valid MTC LLFC SSC PC Combinations

3.34 Entity 64 – SMETS Version

3.35 Entities Changed by the BSCCo.

3.36 Entities Changed by the Profile Administrator

3.37 Entities Changed by the SVAA

3.38 Rarely Changed Entities

4 ENTITY DIAGRAM

4.1 Introduction

4.2 Entity Diagram

Appendix A: Glossary

3.1 Entity 1 – Market Participant ID¹