Version | Date | Description of Changes | Changes Included |
4.1 | 10/01/2024 | Version alignment changes following IR4/5 Changes and Industry review | ISD Data store URL. SVA and CVA table updates. Parameters update |
4.2 | 11/04/2024 | Changes following MHHS Interim Releases | Download parameters ISD Entity sample files Formats of ISD |
4.2.1 | 06/06/2024 | Changes to align with IR8 | Pages 5 & 6 |
4.2.2 | 21/10/2024 | Changes to align with IR 8.1 and 8.2 | Pages 4, 5, 6 7 & 8 |
What is Industry Standing Data?
Industry Standing Data (ISD) is a new set of common data required by Market Participants and is being introduced by the MHHS Programme to replace the legacy Market Domain Data (MDD). Some existing MDD entities will be carried over into ISD alongside some new MHHS specific entities. Many MDD entities which relate to Non-Half Hourly Settlement will not be included in ISD.
During the transitional period ISD will exist alongside MDD, after which MDD will be retired.
A new method of raising changes to ISD and an associated governance process will be implemented for changes to ISD and its publication which is described later in this document. The mechanism for publishing and receiving ISD data is also different to MDD.
Line Loss Factor data will also now be considered to be part of the overall ISD data set.
What are ISD Catalogues, Entities and Records?
The full ISD data set comprises of thirty four [34] Entities and is referred to as the ISD Catalogue. Each Entity has a specific purpose and format, for example to define the full set of valid DUoS Tariff IDs used by a specific LDSO. Each individual DUoS Tariff ID in this example is a Record of the DUoS Tariff ID Entity. Please refer to the latest MHHS documentation for details.
Note: “The ISD Entity 47 Measurement Quantity is used only for the purposes of informing the Load Shapes within the
Load Shaping Service and should not be taken as a valid set to populate Meter Technical Details. Where Meter Technical Details are populated, the correct measurement quantity should be populated through the J0103 Data Item, and for SVA Metering Systems should ensure that the correct allocation of reactive energy (considering whether the reactive energy is lagging or leading) is used.
The ISD Catalogue is version controlled (in a similar manner to its predecessor MDD) and published in accordance with a governance process to be defined in BSCPs. The latest published version should be used by Market
Participants, paying attention to any Effective From and Effective To settlement dates which apply to some entities.
ISD ensures that everyone uses the same data. It is managed on a version control basis and updated monthly. Elexon will enable Market Participants to raise ISD Change Requests for certain entities through the Kinnect communities once ISD goes live according to their role in Market.
How will Market Participants find and download the ISD?
ISD will normally be published in line with the release schedule once a month. During the MHHS Transition Period an additional ISD catalogue will also be published each month with changes relating to newly qualified MHHS participants. When a new version of the ISD catalogue is published, participants will receive a notification from the Data Integration Platform (DIP) via a PUB-047 message.
The format of this notification will be defined in a Data Integration Platform, details will be provided in future, and contains the URL which will point to the ISD Data Store – a new Elexon service to support MHHS.
Access to the data store will be via a URL (sample) below. This link is shared with the intent of facilitating access to the ISD Data Store via URL and does not imply a validation of the information provided therein.
When accessing this URL, participants may provide one of the following optional parameters, which will define which ISD entities they will receive and the authorised participant to amend the entity.
Parameters | Description | Type | Options | Default if not present |
Version | Indicates which version of the catalogue is being requested. | Integer | 1,2,3 etc | Current Latest Version |
Filter | Filter for either the full ISD catalogue (without M20 and M21 LLF), one of the three available groupings: LLF data (LLF- M20 and M21), Master Settlement Timetable (Timetable- entity M14) or ISD data (ISDData), or an individual entity (ISDEntityXX) | String | “Full”, “LLF”, ”Timetable”, “ISDData”, “ISDEntityXX” | Full ISD Catalogue (without M20 and M21 LLF |
Changed | Indicates whether the full entity will be returned (F) or just those records which have changed from the previous version (T). Applies to all entities in the return data | String | “F” “T” | “F” |
MPID | M20 and M21 LLF data will be returned for a specific distributor MPID (Note this parameter will over-ride “Filter” and if used will always return M20/M21 only) | String | Valid 4 character LDSO MPID | M20 and M21 for All LDSOs |
Note – All example URIs are dummy and do not point to a real location.
Parameters can be provided in any order. If the provided parameters cannot be parsed successfully by the ISD Data
Store, a “Page Not Found (404)” error will be returned.
If the parameters result in no records to be returned (for example – requesting changes to an entity that has not changed in that catalogue version), then a file containing just the header will be returned (see below for file details).
What will be the option around formats of ISD?
All ISD entities including LLF values will be provided in CSV format. Please refer to ISD Data store Technical Specification document
If a single entity is requested, the flat file is returned. Each file has the same header, defined as follows;
Field | Description | Type | Mandatory |
ISD Entity Id | Entity Id | String | Y |
ISD Entity Name | Full name of entity | String | Y |
ISD Catalogue Version | Catalogue version number in which the entity was last updated | Integer | |
Changes | Indicates if the file contains the changes from the previous catalogue version (T) or full set of records in the entity (F) | Char | Y |
The second row of the file lists the field names of the entity.
The remaining rows of the file will be defined as per the entity definition in “MHHS EDI021 ISD Entities”. Null fields are included, and each line ends with a carriage return, but no trailing comma.
Date/Time Format: YYYY-MM-DD HH:24:MI:SS
String – Any fields that contain line breaks, double quotes and/or commas will be enclosed in double quotes.
Empty line at end of file.
ISD Entity M1 – Market Segment
ISD Entity M4 – Load Shape Categories
ISD Entity M6 – MHHS GSPG Scaling Weights
ISD Entity 61 – BM Unit for Supplier in GSP Group
URL and Download Mechanism
You will be able to fetch data through URLs in csv formats (as shown above). There will be a csv file extract where a single entity is requested, if more entities are requested a zip file containing the CSV file(s) will be extracted. Every month you will receive a PUB-047 message from the DIP containing only a URL where you then need to query the ISD Data Store to fetch the data.
More information about the interfaces can be found in the MHHS Interface Catalogue.
Note: Opening the ISD file directly in Excel may result in strange characters appearing in the output data. To prevent this, please first open Excel and then import the ISD file. This method ensures that all characters, including non-Latin ones, are displayed correctly.
Open in Text Editor - Characters are displayed correctly
Same Open in Excel (directly) included some special Latin characters
Import the csv into Excel, and those characters are displayed corrected
Adding the correct encoding to the ISD Datastore CSV files so that Excel automatically parses them correctly upon opening is identified as an improvement on the ISD development backlog. No timeframe for this has been identified.
How many versions will be maintained/available?
The ISD Data Store will maintain copies of all versions of the ISD Catalogue; Historic versions can be requested by using the “version” parameter (see above).
How will entities be versioned controlled?
ISD entities will be version controlled subject to the ISD calendar dates and CR procedure which is defined in BSCP707s(New replacing BSCP 509). The change request deadline of each catalogue version is based on the dates of the Supplier Volume Allocation
Group (SVG) meetings. All changes (except “Fast Track”) are presented for decision at the monthly SVG meeting before they are committed to a scheduled ISD Catalogue Publish. Fast Track changes are those which do not impact other parties and do not require SVG approval, however they are still subject to the ISD Catalogue publication schedule.
Key activities in the ISD change request process are illustrated below:
The CR deadline is the last date a CR can be submitted for a proposed ISD change to a specific version. All ISD CR
(Including Fast track) must be submitted by 5pm on the day of the deadline.
“Go-live” refers to the date on which the published changes become effective, and is usually 5 working days after the date of publication. In the event of an error being detected in a published catalogue before the Go-live date Elexon will assess the potential impact on settlement and where necessary a corrected catalogue will be published with the same Go-live date. This will be given the next sequential catalogue number, and all subsequent catalogues will be renumbered. If the error is assessed to be minor, or if the error cannot be corrected before the Go-live date then the correction will be included in the next scheduled catalogue publication.
Governance of the ISD process
All submitted CRs (excluding Fast Track changes) will be issued to Market Participants (MP) via the ISD Circular to enable them to perform an Impact Assessment (IA) on the proposed ISD changes to be committed in a particular ISD version. This review allows MP to raise comments on changes that may impact their processes or systems. Comments must be returned within five working days of receiving the changes.
The proposed CRs for IA will be issued via the ISD circular.
Where a proposed change request has no adverse impact to Market Participants, it will progress to the SVG group for approval. Where a Market Participant impact assessment considers that changes may have adverse impacts, Elexon will inform the CR creator of these issues and recommend one of the following actions:
The SVG will consider the CR, the reason for change and any issues raised in the Market Participant impact assessment and either approve or reject the change.
After SVG decide on the changes presented for approval, the final circular will be issued with details of all the changes to be included in an ISD Catalogue version.
If the CR is partially rejected, you will be informed via email of the reject CR at record level and these will be removed from the CR. The approved records will be published in the ISD catalogue.
Process of raising changes to the ISD
Change Request submissions in ISD will be raised online. To submit a CR you will need to access the Kinnect Customer Portal as an authorised signatory and complete an online ISD Change Request Form and details for each individual entity affected via an online entity CR form. Where large volumes of data are being submitted, these can be done by uploading the entity file. Examples of the file formats can be downloaded from the ISD Change Request screens.
All completed changes will automatically be validated by the system and the ISD/Elexon Operator will be notified via email of submitted CRs for review. Where a CR or its associated Entity form fails validation a message will be displayed and following correction of the issue the user may resubmit.
From this stage onwards, your involvement in the process will depend on the IA outcome. If there are any issues with a CR, the Elexon ISD operator will contact you. However, you have the option to withdraw a CR before SVG approval. After SVG Approve or reject changes, a final circular will be issued containing all the changes which will be committed to that ISD version.
ISD will be updated monthly following the SVG meeting. Please note MHHS CR053 will temporarily introduce an additional monthly publication during the Transition Period, after which the frequency will revert to monthly.
This document has been made available for the purpose of providing information on the Industry Standing Data and the information contained in it are/maybe subject to change. 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.
