RMDS

MCR 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 Optionality of ‘Country- Ireland’ field on Notification Address

‘County Ireland’ field is mandatory for notification addresses where the country is IE. Change from D (dependent) to

O (optional). – Messages containing notification address where ‘County Ireland’ is D.

Click here to view document.

 

MCR 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 Implementation Guides

To avoid confusion, it is proposed to include these same conditions in the Market Messages Database .

Click here to view the document.

MCR 0015 – 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 and structure

Timestamp should be

YYYY-MM-DD-THH.MM.SS

And not

YYYY-MM-DD-THH.MM.SS+-HH.M

For information the ‘Interval Period Timestamp’ does include the local time offset

Click here to view document.

 

MCR 0014 – 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 revisions

Click here to view the document.

MCR 0013 – Allowable Codes for the ‘Title’ field on market messages

Ver 4.1 of the Message Data Structures defines ‘Title’ as a CHAR (4) field with no defined list of allowable codes. It

is proposed to define the following set of allowable codes for the ‘Title ‘field.

Click here to view document.

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.

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.

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 revisions
• Published codes to use NACE Codes at 2 digit level only. This provides suppliers with the flexibility to use 2 and 4 digit codes as appropriate on their own systems but when it comes to sending and receiving Market Messages the first 2 digits only will be sent.

Click here to read the document.

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 and structure
Timestamp should be
YYYY-MM-DD-THH.MM.SS
And not
YYYY-MM-DD-THH.MM.SS+-HH.M
For information the ‘Interval Period Timestamp’ does include the local time offset

Click here to read the document.

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 Implementation Guides
To avoid confusion, it is proposed to include these same conditions in the Market Messages Database .

Click here to read the document.

DR 0022 – Change Optionality of Fields on Market Messages

Click here to read the document.

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 311- Meter Problems.

Click here to read the document.

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:
Unmetered reports of problems or damage will be identified at the Technical MPRN level for group
unmetered sites and for single point unmetered. The Technical MPRN will be used as the identifier to
track and process unmetered reports, as the MPRN would be used for a NQH or QH connection. The
same process and market message can be applied to single point and group unmetered process.

Click here to read the document.

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 MOIP is now proposing to address the requirement to be able to
re-send market message related data to suppliers in the following manner:

Rather than having a suite of refresh messages covering a selected subset of market messages it is
proposed to provide a more general facility that will enable market participants to request the resending
of any given market message or all messages relating to a given MPRN

The requested “resend” message will be sent to the Supplier in exactly the same form as the original
message (the same transaction number and business reference number).

Click here to view document.

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 on
101R or 102R messages.

The Reject reason code on 101R and 102R should be ‘IEA’ – Invalid/Incomplete EAI code’

Click here to view document.