RMDS

Monthly Archives: April 2004


DR 0016 – New Market Message to Cater for Negative Functional Acknowledgements from Hub

A new message needs to be designed (Message 601) – To cater for Negative Acknowledgements from ESB Messaging Hub. Click here to read the document.

Read More

DR 0017 – Allowable Codes for the ‘Title’ field on market messages

Proposed change to v6.1 of the Retail Market Design to allow for the following: Click here to read the document.

Read More

DR 0018 – Revised list of EAI Codes

The ‘Economic Activity Indicator’ codes currently defined in Ver 4.1 of Data Codes include a mixture of 2, 3 and 4 digit codes. While continuing to base the codes on the NACE standard it is proposed to make the following…

Read More

DR 0020 – Minor Update to Common Data Segments Message Implementation Guide

The Definition for ‘Timestamp’ field in the Common Data Segments is incorrect. It includes a reference to +/- BST which is not the case. The XML Schema does not need to be updated as they already reflect the correct definition…

Read More

DR 0021 – Statement of Conditions for populating ‘D’ fields on market messages

At present there are a number of fields on market messages which have an optionality of ‘D’ (meaning that the particular field is to be sent in certain circumstances.) The criteria for sending these fields are defined in the Message…

Read More

DR 0022 – Change Optionality of Fields on Market Messages

Click here to read the document.

Read More

DR 0023 – Add Market Participant Business Reference Number to Messages 260, 261 and 311

Market Participant Business Ref needs to be a mandatory item on message 260 – Observation of Problem, Damage or Tampering Market Participant Business Ref needs to be a optional item on message 261- Resolution of Problem Damage or Tampering and…

Read More

DR 0070 – Sending readings for de-energised sites

Suppliers wishing to notify ESB Networks of a potential problem at an unmetered site should use the market messages and processes as defined to support metered sites i.e. MPD 12. Section 3.1 of this MPD should be updated as follows:…

Read More

MCR 0011 – Refresh Messages

MPD 23 – Supplier Data Requests currently allows for the requesting and sending of refresh messages. These messages are also catered for in the Market Messages database V 4.1 and the XML schema. Following a review of the design ESB…

Read More

MCR 0010 – Validate EAI on 010 Message

It is proposed to make Economic Activity Indicator mandatory on 010 message in defined circumstances (ie sites where MIC > 30kva). An invalid value or blank value (for sites where MIC > 30kva) on the 010 message will be rejected…

Read More

MCR 0009 – Appointments Functionality

Suppliers will be allowed to make appointments for the following Call Types • Re-Energise • Re-Energise NPA • Exch from D/T to S/T • Exch from ST to D/T • Remove NSH MT & T/S • Install Token Meter •…

Read More

MCR 0008 – Change optionality of Market Participant Business Reference on 331 Message

Proposing to change the optionality of the Market Participant Business reference field on the 331 Message – QH Meter Technical Details message from mandatory to optional field Click here to view document.

Read More

MCR 0007 – Sending Different data on the 111 message to old and new supplier

MM 111 Registration Cancellation confirms a cancellation on an MPRN to both the Old and New Suppliers . This DR proposes that the existing message with all the fields populated is sent to the New Supplier but the Old Supplier’s…

Read More

MCR 0006 – Sending Different data on the 105 message to old and new supplier

Detail of Change Request This DR proposes to make fields on the 105 Change of Supplier Confirmation message optional so that the proposed existing version would go to the New Supplier , but that only the following fields are populated…

Read More

MCR 0005 – Change to field name on 114 message

Each of the market messages contains a field called Message Type in the header. Message 114 contains a second field called ‘Message Type’ (to indicate whether the message is a response or an advice). It is proposed to rename this…

Read More
Cookie Settings