Help
This page shows the Flow Structure for one Market Message, including its Scenario Variants and the REC Data Specification version it belongs to.
MM20023
UTC Settlement Period Consumption Data
Select version
Latest
- Local Catalogue Reference
- Message Version
- 11
- Description
- Data Service will provide Actual or Estimated UTC Settlement Period Consumption data (Active and where appropriate Reactive), for each MPAN, for each day that they are appointed.
- Notes
- * A maximum of 1 MQID and 200 Settlement Days combinations per individual message * Assumption that Central Settlements Systems will utilise the 'S1 - Sending Party Timestamp' to determine the date/time data was issued and this will subsequently be used to identify the most recent data for a given MPAN / UTC Period. Consumption submitted on a De-Energised site will be accepted, but will generate a warning returned using IF-014. * Connection Type should be the Connection Type of the MPAN on the Settlement Day for which information is being submitted. As a result of routing requirements, consumptions for periods where a different Connection Type was effective should be sent in a new/separate message. * Response messages will only be sent in the case of Validation Failure / Business Validation Rejection; in the absence of a error response the message should be assumed to have been accepted and fully processed. In the case of failed validation no data will be loaded by the MDS and all data contained in the message should be resubmitted as part of the 'corrected' message. For the avoidance of doubt 'message' in this context relates to all data associated with a Common Block (i.e. * JSON field names in this interface 'ONLY', have been shortened to the values shown in RED in col C/Data Item, so as to reduce the size of this particularly high volume interface.
| Variant ID | Name | Source | Target | Owner | Actions |
|---|---|---|---|---|---|
| Variant ID SV20211 | Name ActivePower & DI-015 = W | Source Data Service | Target | Owner Balancing and Settlement Code Company | Change selection |
Structure
SV20211
| ID | Name | Range | Level | Required |
|---|---|---|---|---|
| S0 | Transactional Info | Range: 1-1 | L1 |
|
| Interface ID |
|
|||
| Schema Version |
|
|||
| Event Code |
|
|||
| S1 | Sender Info | Range: 1-1 | L1 |
|
| Environment Tag |
|
|||
| SubText | Optional | |||
| Sender Unique Reference |
|
|||
| Sender Timestamp |
|
|||
| (Participant) Sender DIP ID |
|
|||
| Sender Role ID |
|
|||
| Sender Correlation ID | Optional | |||
| Connection Provider DIP ID | Optional | |||
| D0 | Transactional Info - DIP Set | Range: 1-1 | L1 |
|
| DIP Transaction ID |
|
|||
| DIP TimeStamp |
|
|||
| Publication ID |
|
|||
| DIP Correlation ID | Optional | |||
| Replay Indicator |
|
|||
| Msg Service Ticket URL | Optional | |||
| A0 | Addressing | Range: 0-1 | L1 | |
| DIP IDs Primary Recipients |
|
|||
| DIP ID Secondary Recipients |
|
|||
| DIP Roles / IDs Always Receipient ID |
|
|||
| Unnamed collection | Range: 0-0 | L1 | Null | |
| Unnamed collection | Range: 0-0 | L1 | Null | |
| M0 | MPAN | Range: 1-1 | L1 |
|
| MPAN Core |
|
|||
| Distributor DIP ID |
|
|||
| GSP Group Id |
|
|||
| B044 | Data Service Information | Range: 1-1 | L1 |
|
| Issuing Data Service DIP ID |
|
|||
| B067 | Connection Type | Range: 1-1 | L1 |
|
| Connection Type |
|
|||
| Connection Type Effective From Date |
|
|||
| B045 | MQID | Range: 1-1 | L1 |
|
| Measurement Quantity Id |
|
|||
| B046 | UTC Settlement Day | Range: 1-* | L2 |
|
| UTC Settlement Date |
|
|||
| Settlement Period Duration |
|
|||
| B047 | UTC Settlement Period Consumption Data | Range: 1-* | L3 |
|
| Settlement Period Effective To Date/Time |
|
|||
| UTC Period Consumption Value |
|
|||
| Settlement Period Quality Indicator |
|
|||
| Estimation Reason Code | Conditional | |||
| Supplier Consumption Amendment Reason Code | Conditional |