ERDS Service Definition timezone correction
Summary
This change seeks to specify timezones within the ERDS Service Definition. For example: Data received by the ERDA shall be included within the ERDS Total Daily Processing on the basis that all data received prior to 23:00hrs is made available to the SMRA, EES Provider or CSS Provider (as applicable) by 06:00hrs the following Working Day. Data received after 23:00hrs will be made available to the SMRA, EES Provider or CSS Provider (as applicable) by the second Working Day
Latest update and next planned activity
Date of latest update
Latest Update
This Change Proposal was implemented as part of the 7 November 2025 REC Release.
Impacts Overview
Impacted Consumers
Electricity
Impacted REC Parties and Market Participants
Distribution Network Operator
Priority and rationale
Standard
Priority last updated on 29 May 2026
Solution development
Problem Statement
The ERDS Service Definition does not specify the time with a specified time zone. This has led to some instances of MPRS close of day running at 22:00GMT instead of 23:00GMT. A confirmation of time zone is required within the ERDS Service Definition to negate any confusion or delays in flow processing and systems becoming misaligned.
Proposed solution summary
- As a Supplier, I want to have confidence that the data in the systems is aligned and accurate.
- As ERDS Provider, I want to be able to provide accurate and appropriately labelled data that can be aligned with data from other systems.
No documents available.
Change Plan
Change Proposal Plan and Impact Assessment Report Published
Completed
Start:
22 Aug 2022Due:
18 Jun 2024Completion:
18 Jun 2024Change report and Consultation issued
Completed
Start:
18 Jun 2024Due:
28 Jun 2024Completion:
27 Jun 2024Consultation closed
Completed
Start:
28 Jun 2024Due:
19 Jul 2024Completion:
19 Jul 2024Responsible Committee decision
Completed
Start:
19 Jul 2024Due:
28 Aug 2024Completion:
28 Aug 2024Appeal Window Closure
Not Started
Start:
28 Aug 2024Due:
12 Sep 2024Completion:
Original submission
Change details
Daniel Tadecicco - St Clements Services
22 Aug 2022
Change details
ERDS Service Definition timezone correction
The ERDS Service definition does not specify any timezones for example: Data received by the ERDA shall be included within the ERDS Total Daily Processing on the basis that all data received prior to 23:00hrs is made available to the SMRA, EES Provider or CSS Provider (as applicable) by 06:00hrs the following Working Day. Data received after 23:00hrs will be made available to the SMRA, EES Provider or CSS Provider (as applicable) by the second Working Day
Due to the differences in System timezone, CSS and UKLINK in Localtime and EES, DSP and MPRS in GMT (UTC0) there was some confusion at Go Live when the end of day is in MPRS (ERDA) as the Schedule only specifies the 23:00 time and not the Timezone. This lead to some instances of MPRS close of day running at 22:00GMT instead of 23:00GMT.
The ERDS Service Definition should be amended to add the GMT Timezone to any timebased statements for example: Daily Processing on the basis that all data received prior to 23:00hrs GMT is made available to the SMRA, EES Provider or CSS Provider (as applicable) by 06:00hrs the following Working Day. Data received after 23:00hrs GMT will be made available to the SMRA, EES Provider or CSS Provider (as applicable) by the second Working Day
-
Impacts
Electricity
Billing accuracy
All DTS flows must be in GMT, this is a S3P4V1-7_User_File_Design_S Requirement. Data Aggregators require D0209s to be in GMT. If the MPRS (ERDA) end of day closes an hour earlier than expected, it can lead to a delay in flow processing and systems becoming misaligned.
No details provided
Electricity Retail Data Service Definition
No details provided
-
No details provided
-
No details provided
-
No details provided
-
No details provided
-
Distribution Network Operators
-
No details provided
-
-
No details provided
Priority & timing
No
-
-
-
No details provided
-
Activity
Proposed solution summary changed to As a Supplier, I want to have confidence that the data in the systems is aligned and accurate.As ERDS Provider, I want to be able to provide accurate and appropriately labelled data that can be aligned with data…
Proposed solution summary changed to As a Supplier, I want to have confidence that the data in the systems is aligned and accurate.As ERDS Provider, I want to be able to provide accurate and appropriately labelled data that can be aligned with data from other systems..
Show moreStatus has been changed to Implemented.
Implementation Date has been updated to 07 Nov 2025.
beth.brown, Orphaned SME: Lead Assurance Analyst have been allocated as SME.