RMDS

MCR 0024 – Updates to MPDs to remove ambiguity

The following MPDs are required to be updated to ensure greater clarity:

Click here to open document

MCR 0023 – Updates to field lengths and code values

Changes to field lengths

Meter Category is defined as AN (3). In order to cater for the codes defined this field should be length AN (5)

Meter Point status reason is defined as AN (2). In order to cater for the codes defined this should be length AN (3)

Changes to permitted code values.

Click here to view document.

 

MCR 0022 – Sending two versions of market message 111

This MCR proposes to send message 111 to the new supplier and to implement a new message

(111L)with the contents underneath to the old supplier

MPRN

Supplier ID

Cancellation Reason

Effective From Date

Click here to view document.

MCR 0021 – Sending two versions of market message 105

This MCR proposes to send message 105 to the new supplier and to implement a new message (105L)

with the contents underneath to be sent to the old supplier

MPRN

Meter Point Address

Effective From Date

Click here to view document.

MCR 0020 – 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. None of the proposed changes will impact the data formats of the data items

Changes to Definitions of Following Fields to avoid confusion with Wholesale Market Design

Click here to view document.

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 used to populate Recipient ID which

appears in the Header segment of market messages.

In addition – the Recipient ID field in the Header will also require to be populated with Generator Ids – i.e. the same

contents as the Generator MPID without the last char. For example where the Generator MPID is D04G then the Generator

ID should be D04.

Click here to view file.

DR 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 market message (602), and automatically sent or made available to participants each day at a fixed time. It will capture all the messages sent and received since the last time the message was sent.

Click here to read the document.

DR 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.

DR 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 document.

DR 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 – where the data is available on the market systems – to
ensure the MM 105 is fully populated. As the large majority of data is currently resident in the host PES this would
ensure the market is provided with this information.
Accordingly the full message 105 should ONLY be sent to the new supplier from data provided by them or the
market. If there is any inconsistency this should be notified to the new supplier to enable accurate updates provided
for DSO.

Click here to read the document.

DR 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 document.

DR 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 the document.

DR 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.

DR 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 met.
• MPD 2 – To be updated to indicate that QH Change of Supplier process will also apply to CoS for Non
Despatchable Generators.
• MPD 3 – To be updated to indicate that the objection process applies to NQH MD sites
• MPD 7 – TO be updated to indicate that Non Despatchable Generators will follow the same processes as
QH metered sites
• MPD 22 – To be updated to indicate that a customer may nominate a third party to request any data on
their behalf

Click here to read the document.

DR 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 be cancelled. This is not currently reflected in the MPDs. The MPDs listed below must also
be updated to reflect the situation with regard to chargeability where such an event occurs

Click here to read the document.