RMDS

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
• Reset Token Meter
• De-Energise
• Remove Token Meter
• Token Meter Fault/Ex (If this is a no Supply situation is should be referred to Networks as a No Supply call with
a Token Meter)
• Special test in-situ

Click here to view document.

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.

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 message would only have the following fields populated :
• MPRN
• Supplier ID
• Cancellation Reason
• Effective From Date

Click here to open document

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 in the 105 message to the Old Supplier:

• MPRN
• Meter Point Address
• Effective From Date

Click here to view document.

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 field to ‘Message Status’ in line with the XML schema and to avoid
confusion as these fields are used in two completely different contexts with different valid values and
field sizes.

Click here to view document.

MCR 0004 – Sundry Changes to Ver 4.1 Market Messages & Data Codes

Aggregation Messages – 501, 501S, 505, 505S

The first Additional Aggregation segment in messages 501, 501S, 505 and 505S should be documented as level 4.

second Additional Aggregation segment in messages 501, 501S, 505 and 505S should be documented as level 5

Message – 341

Message 341 is missing the cardinality of the Channel Level Details – Level 4. It should be 1..N

Optionality of Customer Service Special Needs and Medical Equipment Special Needs

The optionality of Customer Service Special Needs and Medical Equipment Special Needs is incorrect on messages
101, 105, 102N. These fields should be Optional not Mandatory.

Click here to view the document.

MCR 0003 – Additions to Message 501 – Estimated Aggregated NQH Supplier Consumption – DNGP

Amend 501 message to include total EUF by profile and timeslot and the count of MPRNs used in
Aggregation run

Input file for aggregation run to be available on request. Format (probably CD) to be determined at later
date

Click here to view document.

DR 0002 Additions to Message 501 – Estimated Aggregated NQH Supplier Consumption – DNGP

Please click here to open the document

DR 0005 Sundry Changes to Ver 4.1 Market Messages

Please click here to open document

DR 0006 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 field to ‘Message Status’ in line with the XML schema and to avoid
confusion as these fields are used in two completely different contexts with different valid values and
field sizes.

Please click here to open document

DR 0008 Defaulting Business Reference on Web forms

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 in the 105 message to the Old Supplier:

MPRN
Meter Point Address
Effective From Date

Click here to open document

 

DR 0009 Sending Different data on the 111 message to old and new supplier

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

 

Please click here to open document

DR 0010 Change optionality of Market Participant Business Reference on 331 Message

Change optionality of Market Participant Business Reference on 331 Message

Please click here to open document

DR 0011 Appointments Functionality

Please click here to open document

DR 0012 Use of customer read for Change of Supplier

Please click here to open document