RMDS
Monthly Archives: May 2007
DR 0144 – Changes to the Aggregation Briefing Document, MPD 15 and MPD 16 (2_1) for RA 324 Mitigation and PES Trading Sites
The Aggregation Briefing Document is at v3.3 via MCR 133 and forms part of the baseline for SEM Implementation. MPD 15 – QH Data Processing was baselined in the Retail Market Design at version 6.0, as detailed within MCR 097,…
Read MoreDR 0145 – Estimation of QH values for Indicative Aggregation
MPD 15 – QH Data Processing was baselined in the Retail Market Design at version 6.0, as detailed within MCR 097, as part of the suite of changes to satisfy new requirements of SEM implementation. Within the requirements of the…
Read MoreDR 0146 – Inclusion of Seconds (SS) in the Date Timestamp Format
There is an inconsistency between the technical specification of the xml schema provided by the SEMIT and the SEM-MDP Meter Data Format which does not include SS level for these DateTime data Items. All elements within the xml schema defined…
Read MoreDR 0147 – Clarification regarding date selection in WP12
Working Practice 12– To nominate / denominate a Supplier as a recipient of Participant Generator messages was baselined in the Retail Market Design at version 6.0, as detailed within MCR 0123, as part of the suite of changes to satisfy…
Read MoreMCR 0058 – Addition of new Code ‘CoG’ Change of Group MPRN
Analysis of scenarios, such as Local Authority boundary changes, where it is found a TMPRN should move from one GMPRN to another reveals the need for an additional Unmetered MPD. To support this, a new Transaction Reason Code “CoG” should…
Read MoreMCR 0057 – Add customer name to Extranet
To facilitate the registration process and prevent erroneous CoLEs being processed the Customer name should be provided on the Extranet site for all MPRNs (Existing and New Connections) where the DUoS Group is DG5 or above. Where the customer is…
Read MoreDR 0148 – Reformatting of the Load Profile data
Suppliers are looking for a standard format for receipt of the annual load profile data, to ensure delivery of the required year to year consistency that will allow automated upload of the data into their systems. A standard format will…
Read More