RMDS
Monthly Archives: May 2004
MCR 0019 – Additions to Recipient IDs on market messages
A new Market Role ID is required for TSO as TSO is a valid recipient of market messages. At present there are only two values, one for DSO (to incorporate all of Networks) and one for SSA. This will be…
Read MoreDR 0019 – MP Daily Summary Reconciliation Count
A record will be stored of all market messages (including 601 message proposed under DR 0016) that are received from participants and sent to participants via the Market Gateway. A daily summary reconciliation count will be automatically generated as a…
Read MoreDR 0025 – Additions to Recipient IDs on market messages
A new Market Role ID is required for TSO as TSO is a valid recipient of market messages. Click here to read the document.
Read MoreDR 0026 – Sundry Changes to Business Data Definitions arising from Discussions with SSA
Following meeting between ESB MOIP and SSA it is proposed to amend the following data definitions to avoid possible confusion with Wholesale Market Design and address inaccuracies in the current data definitions highlighted by the review exercise. Click here to read the…
Read MoreDR 0027 – Sending customer service and medical equipment special needs on 105 message
We request clarification on MARKET MESSAGE 105 optionality for issue to the new supplier regarding Medical needs and specials needs. At present in the market message it is described as ‘’see description’’ We seek this information to be automatically provided…
Read MoreDR 0028 – Sending two versions of market message 105
This DR proposes to send message 105 to the new supplier and to implement a new message with the contents underneath to the old supplier • MPRN • Meter Point Address • Effective From Date Click here to read the…
Read MoreDR 0029 – Sending two versions of market message 111
This DR proposes to send message 111 to the new supplier and to implement a new message with the contents underneath to the old supplier • MPRN • Supplier ID • Cancellation Reason • Effective From Date Click here to…
Read MoreDR 0031 – Updates to field lengths and code values
Changes to field lengths To allow field lengths to cater for defined codes Changes to permitted code values. To prevent contradictions between code values and reflect current design Click here to read the document.
Read MoreDR 0034 – Updates to MPDs to remove ambiguity
The following MPDs are required to be updated to ensure greater clarity: • MPD 1 – Steps 14, 15 to be updated to clarify that an acceptance will not be fully accepted until all conditions for provisional acceptance have been…
Read MoreDR 0035 – Update Meter Works related MPDs to reflect manual interaction between Networks & suppliers
Where a Network Technician makes repeated attempts to complete a call to carry out meter works requested by the supplier (e.g. De-energise, re-energise or change to MCC) then the supplier will be manually contacted and informed that the call will…
Read MoreDR 0071 – Addition of field with associated codes to messages 331 & 332
Add new field with associated data codes to the 332 & 331 messages to flag the reason why the message is being sent. Click here to read the document.
Read MoreMCR 0012 – 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. Message No: 601 Description: Rejection to Invalid Message Click here to view document.
Read MoreMCR 0018 – 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 MoreMCR 0017 – Change Optionality of Fields on Market Messages
016 Change of Legal Entity • Make the ‘Read Reason’ field on the 016 Change of Legal Entity message ‘Optional’ rather than ‘Mandatory’ • In addition the optionality of the ‘Serial Number’ field should be changed to ‘D’ Change to…
Read MoreMCR 0016 – 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