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

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

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.

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.

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.

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).

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).

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).

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.

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).

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.

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.

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.

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).

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.

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).

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.

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.

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.

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.

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.

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.

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.

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).

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.

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.

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).

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).

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

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).

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.

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

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).

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.

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.

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.

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.

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.

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.

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.

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.

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}

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.

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).

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).

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

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

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.

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).

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

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

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.

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.