RMDS
Monthly Archives: May 2005
MCR 0050 – Modifications to CoS Readings process in CoS loss scenario
Current scenario – Ref IPT Learning points issued Dec 8 Where CoS is in progress and a “wait” period (“Wait” period means the initial 5 day period after notification to the Old Supplier – via MM 110), crosses with the…
Read MoreMCR 0049 – Estimate of consumption at register level
DR 0056 was raised to address the issue of Suppliers requirement to receive an estimate of consumption for each register for non standard MCCs. There was a conference call held on 03/03/05 to clarify business requirement where it was agreed…
Read MoreMCR 0056 – Package messages on MPCC
The proposal is to modify the MPCC software so that the MPCC will send multiple market messages in each Package. This would reduce the number of packages sent, processed and receipt acknowledged and would therefore improve performance, both at the…
Read MoreMCR 0055 – Optionality of settlement date on aggregation messages
The optionality of the Settlement Date on the 501, 504 and 505 should be changed from Optional to Mandatory for the Settlement Date field. Click here to view document.
Read MoreMCR 0054 – Add functionality to Extranet to display Group & Singlepoint
As described in DR 0067 Extranet to be modified: Functionality to be added to Extranet to display Grouped MPRN (GMPRN), Technical MPRNs associated with GMPRN (TMPRN) & Single Point Unmetered MPRN datasets Existing functionality will be enhanced to accommodate unmetered…
Read MoreMCR 0053 – Reject if MM received for Group unmetered sites
Where the following market messages are received for a group unmetered site (either at GMPRN or TMPRN level) they should be rejected for reason IMP – invalid MPRN: 010 – Meter Point Registration (rejected with 101R or 102R as appropriate)…
Read MoreMCR 0052 – Amendments to de-registration process
At present validation rules for de-registration requests are based on an elapsed six months between de-energisation and de-registration. In line with CER rulings this should be changed to a three month period. Clcick here to open the document.
Read MoreMCR 0051 – Read date on multi function meters
For programmable devices used as NQH meters the population of the ‘Read Date’ should reflect the actual date of the recording of the read not the date it was read by the Meter Reader. Clcick here to open the document….
Read MoreDR 0078 – Amendment to 105 required date when 102P received
In scenarios where the COS process for a QH customers is delayed because of an outstanding connection agreement, the effective from date gets pushed back until the connection agreement is resolved. Click here to read the document.
Read MoreDR 0072 – Amendments to market messages 501, 501S, 505 and 505S
In order to facilitate Market Participants carrying out various reconciliation & data tracking exercises e.g. reconciling MRSO provided settlement data, billing reconciliation and checking/tracking changes and updates to meter points. Click here to read the document.
Read MoreDR 0074 – Amendment to market message 208 to allow it to be sent by suppliers to dispute MRSO Readings
Amend Market Message 208 (Replacement Reading) to allow it to be sent by suppliers to dispute MRSO readings. This would involve changing some mandatory fields as suppliers may not always be able to provide a replacement reading but based on…
Read MoreDR 0077 – Transaction Charge to be invoiced only after the job completion market message sent
The transaction charge for a job should only become eligible for inclusion in the next Networks Transaction Charges Invoice after the job completion market message, or e-mail, has issued to the Supplier. At present the charge is created in Networks…
Read MoreDR 0066 – Addition of new Code ‘CoG’ Change of Group MPRN
Analysis of scenarios, such as LA boundary changes, where it is found a TMPRN should move from one GMPRN to another reveals the need for an additional Unmetered MPD. Whilst initial thoughts regarding this process are being documented for circulation in…
Read MoreDR 0068 – 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. Click here to read the document.
Read More