RMDSQuestions
Answers
| MCR 1111 | ||
| Q1 | How will the network decide if it is CoLE or not? What are the exceptions for Cole? | Back to top |
| A1 | There is no change in MCR1111 to the way MRSO determine if there is a COLE with the COS and so this will continue to operate as-is. | |
| Q2 | FWP & SWP – 48 hours window compulsory? Will FWP or SWP set to 0 hr if msg is rejected? | Back to top |
| A2 | MCR1111 is an approved Market Change Request and describes the new wait periods that will become automated.The FWP and SWP are as described in MCR1111, there will be no reset of any wait period in cases where a Supplier sends in an invalid market message. | |
| Q3 | Is it mandatory to automate the process of Debt flag, especially for commercial customers? | Back to top |
| A3 | MCR1111 is an approved Market Change Request and covers the automation of Debt Flagging for all relevant metered sites and single point unmetered sites as determined by CER.Debt Flagging will be automated as described in MCR1111 for all relevant metered sites and single point unmetered sites as determined by CER, and there are no exceptions. | |
| Q4 | What if we do not automate? Is there a way we could still run via the manual process? | Back to top |
| A4 | MCR1111 is an approved Market Change Request and describes the automation of Debt Flagging.Debt Flagging will be automated as described in MCR1111 for all relevant metered sites and single point unmetered sites as determined by CER, and there are no exceptions. | |
| Q5 | The MCR (1111)quotes the decision by the CER/ 11/106 in June 2011 which affects customer bad debt in Electricity and Gas markets. Will the Gas messages be changing under this MCR ? Will they need to be tested as part of supplier or market testing ? | Back to top |
| A5 | The scope of MCR1111 is for the automation of Debt Flagging for the Electricity Retail Market in RoI for all relevant metered sites and single point unmetered sites as determined by CER. | |
| Q6 | N/A | Back to top |
| A6 | N/A | |
| Q7 | Will the current manual Secure file transfer process remain for some debt objections following go live? For example will it remain only for unmetered GMPRN manual debt objections as WP 23 suggests? | Back to top |
| A7 | Debt Flagging will be automated as described in MCR1111 for all relevant metered sites and single point unmetered sites as determined by CER, and for those there are no exceptions.There will be a manual SFTS solution for Grouped Unmetered as per MCR1133. | |
| Q8 | If we were to send a debt objection via the secure file transfer process post go-live which should have been sent via 012 market message, would the business be notified via email to resend? | Back to top |
| A8 | When MCR1111 is introduced MRSO will not manually handle Debt Flagging for any metered or single point unmetered sites which will then be automated. | |
| Q9 | Should 112R contain the new code “DCN” where used to Reject an 012MM submitted for with “DCN”? | Back to top |
| A9 | The Objection Reason Code with a value ’DCN’ is sent by the losing Supplier on a MM012 to notify that a debt flag is being raised for the MPRN.The Objection Reason Code with a value ’DCN’ is sent to the gaining Supplier on a MM112 to notify that a debt flag has been raised by the losing Suppler , and that it has been successfully validated for the MPRN.MM112R is the Notification of Objection Rejection Message • MM112R will never contain a Reject Reason Code ‘DCN’• The existing logic that triggers a MM112R, on foot of a MM012 , is being changed to take account of scenarios where a DCN will come in on a MM012, for these three Reject Reason Codes viz IRC,QHM, TIM . These three Reject Reason Codes can currently issue on a MM112R, although not for Debt Flagging reasons. (extracts from MCR1111 are in italics below) Changes to existing reject reason code usage for RoI 112R Notification of Objection Rejection are proposed as followsIRC – The Objection Reason Code is invalid (not for Erroneous Transfer) will be changed to allow for an 012MM to be submitted with a ‘DCN’ Debt contact notification objection reason code – ie ‘DCN’ will become a valid Objection Reason Code on MM012 QHM – An objection is not valid for an Interval Meter Point will be changed to allow for an 012MM to be submitted for an Interval Meter Point with a ‘DCN’ Debt contact notification objection reason code . Note QHM will remain as a valid objection reject code eg should ‘ ET’ be submitted for QH site TIM – The objection has been received more than 60 days after effective date of Change of Supplier will be changed to allow for a check against the new automated timelines where an 012MM is submitted with a ‘DCN’ objection reason code, such that ‘TIM’ will be sent on a 112R to the Old Supplier where the 012MM is received from the Old Supplier after the expiry of the FWP . In other words, the present timeline that suspends the Change of Supplier process for a period of 10 working days as a result of an ‘ET’ Erroneous Transfer code will not apply in Debt Flagging Cases as identified by an 012MM with a DCN objection reason code – an 012MM with a DCN objection reason code that is received by the CMS any time after the expiry of the FWP will be ‘late’, and is proposed to be rejected on a 112R with a reject reason code ‘TIM’ • MCR1111 will introduce two Reject Reason Codes which already exist in the COBL and Schema but which currently do not issue on a MM112R , viz COL and IID . This will be done by adding logic that will trigger a MM112R on foot of a MM012 where it has been sent by a Supplier with Objection Reason Code value ’DCN’ and for the scenarios that will give rise to a COL or and IID: (extracts from MCR1111 are in italics below)Existing Rejection Reason Codes will become valid in RoI for use on the 112R Notification of Objection Rejection following validation of an 012MM Notification of Objection with ‘DCN’ Debt contact notification – COL where there is a COLE with the COS [COL rejection reason ‘Change of Legal Entity in progress’] – IID Rejection Reason ‘Invalid/Incomplete data’ will apply where the DUoS Group is invalid • MM112R currently could contain Reject Reason Code AMM, IMP, SNR , IA, and the logic around these will not be changed by MCR1111.(extracts from MCR1111 are in italics below)Existing reject reason codes will continue to be used as normal for non-debt flagging reasons on the 112RExisting rejection reason codes that are valid for RoI on the 112R and which will be valid as a result of a ‘DCN’ Debt contact notification objection reason code being sent on an 012MM are :AMM – The Meter Point Address on the message does not match that held by DSO for the MPRNIMP – The MPRN does not exist or is for a Grouped Un-metered site (either at GMPRN or TMPRN level) or is not valid for this jurisdiction SNR – The Supplier submitting the objection is not registered to this MPRN and is not the Old Supplier for this MPRN IA – The 012 received was a duplicate request. MRSO Already have a valid, open objection for this MPRN Note on IA: this means that the receipt in MRSO of an 012MM which has either the same or a different objection reason code than a concurrent open012 MM is not valid and will be rejected. |
|
| Q10 | It has been queried in regards to how to handle 012MMs for debt flagging when submitted on a non working day? | Back to top |
| A10 | Clarification : We will start the wait period from the start (00:00:00) of the next working day. | |
| Q11 | The 110 is proposed to be amended to indicate where there is a COLE either explicit or inferred. How will this be displayed on the 110 message? | Back to top |
| A11 | There is an existing field on MM110 which will be utilised to indicate where a COS has been identified as having a COLE , whenever this is explicit or inferredThis field has the data definition name Change of Tenant Legal Entity and the schema name ‘COT_LE_Flag’ .This currently exists as a required field on the MM110 and it is a ‘Boolean flag’. The change from MCR1111 will be that where a COS has been identified as having a COLE – either explicit or inferred – then the ‘COT_LE_Flag’ will be populated on MM110 with a value of 1, otherwise where a COS has been identified as having no COLE then the ‘COT_LE_Flag’ will be populated on MM110 with a value of 0
This is a change to how things currently work i.e. before MCR1111 is implemented the value of the ‘COT_LE_Flag’ on the 110 message mirrors the value of the ‘COT_LE_Flag’ populated by the Supplier on the MM010, regardless of whether or not MRSO infer that a CoLE has taken place. |
|
| MCR 1122 | ||
| Q1 | Essential Plant flagging will be done by networks via 17 messages. This could be an issue for Supplier’s Credit control as they will not be able to de-energise them. Can the flagging be done before registration so as to put in place certain deposits in case the customer defaults? | Back to top |
| A1 | The intention is for Essential Plant to be flagged for New Connections before registration and to appear on the Extranet as per MCR1122Please note that Essential Plant is currently in operation, see WP0022And that the Registered Suppliers of sites which are Essential Plant are routinely sent a list of these sites from ESB Networks. | |
| Q2 | Precise definition of Essential Plant. What premises comprises of being Essential Plant. How do they decide if EP. Is it based on info provided by customers? | Back to top |
| A2 | Please note that Essential Plant is currently in operation, see WP0022 as well as MCR1122 | |
| Q3 | Will the Gas messages be changing under this MCR (1122)? Will they need to be tested as part of supplier or market testing ? | Back to top |
| A3 | The scope of MCR1122 is for the introduction of the Essential Plant Flag for the Electricity Retail Market in RoI. | |
| Q4 | MCR (1122) refers to a new schema name “essentialplantflag” Is this the extent of the schema changes ? Can more detail be provided on the structure of the schema change in advance of the 21/08? | Back to top |
| A4 | The amended schema will be implemented as Version 11.00.00MCR1122 Market Message ChangesA new optional EssentialPlantFlag field will be added to the following 17 Market Messages viz: 101 New Connection Registration Acceptance ,101P New Connection Provisional Acceptance, 102 Change of Supply Registration Acceptance ,102P Change of Supplier Provisional Acceptance, 105 Change of Supplier Confirmation301 Meter Point Characteristics ,106D Meter Point Status Confirmation DeEnergisation, 106E Meter Point Status Confirmation Energisation ,306 306W Meter Point Status Change Confirmation DeEnergisation, and Withdrawal, 307, 307W Meter Point Status Change Confirmation Energisation and Withdrawal, 331 Interval Meter Technical Details, 332 332W Non Interval Meter Technical Details, and Withdrawal 700 700W Unmetered Characteristics and WithdrawalThis field will be populated only where it has been determined that there is essential plant at the MPRN.The EssentialPlantFlag will be at MPRN level within the messages.MCR1122 Harmonised Data Changes A new flag will be added to the Harmonised Data Definitions with the name Essential Plant Flag and schema name EssentialPlantFlag. The Harmonised Data Definition for Essential Plant Flag is “As and where an MPRN is determined to be Essential Plant, or where Essential Plant flag has been removed, then this flag will be highlighted.” This flag will be a new Boolean Flag. Where the flag appears with a value of 1 it will mean that there is essential plant at this MPRN, and in the exceptional case where this flag appears with a value of 0 this would mean that there was previously – but there is not now – essential plant at this MPRN. |
|
| Q5 | Will sample market messages be provided for testing purposes for internal testing ? | Back to top |
| A5 | The intention is to fabricate , and have anonymous data so that it is not specific to any Supplier or Customer , one each of the 17 market messages that are being changed for MCR1122 ,and to issue them to all Retail Market Participants in RoI. This would happen in tandem with the project timeline for the amended schema ver 11.00.00. | |
| Q6 | What group of customers is this MCR applicable for (MCR1122)? | Back to top |
| A6 | Please note that Essential Plant is currently in operation, see WP0022 as well as MCR1122And that the Registered Suppliers of sites which are Essential Plant are routinely sent a list of these sites from ESB Networks. | |
| Q7 | If MCR 1122 Essential Plant is an ROI Commercial only change or can it apply to domestic sites also? The definition below taken from WP 22 suggests it can apply to both types of property, can you confirm?Essential Plant (EP) includes: − Water pumping/treatment systems, − Fire Fighting Equipment incl. Alarms, Pumps, Access gates for Fire Brigade etc. − Sewage systems, − Lighting/lifts in indoor/outdoor common areas of apartment blocks/private developments |
Back to top |
| A7 | Please note this text from MCR1122 viz ‘This flag is valid for relevant Unmetered DG3/DG4 at a TMPRN level and Business DG5 and higher’ | |
| Q8 | Would it be possible for Essential Plant to be a DG1 or DG2 (Residential) (maybe in the case of a Water Pump/ Landlord Supply at a block of apartments etc) reading the MCR – the change will only affect DG5 + ..is this correct ? | Back to top |
| A8 | The Essential Plant Flag is valid for relevant Unmetered DG3/DG4 at a TMPRN level and Business DG5 and higher, and not DG1 or DG2.Where we come across a site that is DG1/DG2 and it is a landlord supply, we will advise the Supplier to issue a M013 to change the site to DG5. All Landlord Supplies should be DG5. | |
| Q9 | Will Connection Agreements for these installations need to be changed ? | Back to top |
| A9 | Connection Agreements are not being altered by MCR1122. | |
| Q10 | The Essential Plant CR impacts 17 messages in total, the ones in question here are the 301, 331, 332 messages. Could site works carried out on site change the flag on a MPRN i.e. if a meter was exchanged or MP chars changed, at the same time the Essential Plant flag was applied or removed?i.e. when a supplier takes on a MPRN at that point the flag will noted for the duration of that MPRN with the supplier, but could a supplier take on a MPRN and then later on while registered, the flag could be changed? | Back to top |
| A10 | From MCR1122: Where ESB Networks determine that there is a change at an MPRN which affects the value of the Essential Plant Flag, then this will be notified on the 301MM.This means that the Essential Plant Flag could be added or removed from an MPRN , where necessary, at any stage. | |
| Q11 | Culd a W message ever be used to withdraw the Essential Plant flag if it was incorrectly applied in the first instance. i.e. the meter details and read are unchanged only the flag changes? | Back to top |
| A11 | From MCR1122: Where ESB Networks determine that there is a change at an MPRN which affects the value of the Essential Plant Flag, then this will be notified on the 301MM.This means that the 301MM will be the vehicle to advise the registered Supplier of a change in the Essential Plant Flag status, and not a ‘W’ withdrawal message. | |
| Q12 | To confirm, there are 3 scenarios for the details carried on the xml message?o The message tag =1 -> essential plant is present o The message tag =0 -> essential plant is not present any more o No message tag present -> essential was never present |
Back to top |
| A12 | From MCR1122: A new flag is proposed to be added to the Harmonised Data Definitions with the name Essential Plant Flag and schema name EssentialPlantFlag. The Harmonised Data Definition for Essential Plant Flag is “As and where an MPRN is determined to be Essential Plant, or where Essential Plant flag has been removed, then this flag will be highlighted.” This flag will be a new Boolean Flag. Where the flag appears with a value of 1 it will mean that there is essential plant at this MPRN, and in the exceptional case where this flag appears with a value of 0 this would means that there is not essential plant at this MPRN.From 10.04.2013 IGG Clarification on MCR1122: Under “Data Definition” – “This flag will be a new Boolean Flag. Where the flag appears with a value of 1 it will mean that there is essential plant at this MPRN, and in the exceptional case where this flag appears with a value of 0 this would means that there is not essential plant at this MPRN”.In what circumstances would the flag appear with value 0? Clarification: A value of 0 will only appear on the 301MM, 700MM and 700W MM when an MPRN that was Essential plant has been updated and the flag removed i.e. it was originally created as an Essential plant and a value of 1 had been sent to suppliers on the original 301MM or 700MM. ESB Networks wish to advise the suppliers that it is no longer an Essential Plant and as part of this the flag will be removed from the MPRN on the Central Market system and this removal will be sent to the supplier in the form of a 0 in the field Essential Plant. If a site was never an Essential Plant then the Essential Plant field will never be populated i.e. a blank value. ESBN Update July 2015: for the avoidance of doubt, this means that the essential plant flag will not be present in the market message. |
|
| Q13 | Is the status of a MPRN being flagged as essential plant in any way impacted if the MPRN is d/e or r/e by the supplier i.e. both statuses are totally separate? | Back to top |
| A13 | Where there is no re-classification of the Essential Plant status, then a De-Energisation or a Re-energisation of a site will not impact on the Essential Plant Flag value.However, where there is a re-classification of the Essential Plant Flag status, please see the clarification given to the IGG on 10.04.2013 and published on the RMDS Calendar for that date viz:From 10.04.2013 IGG Clarification on MCR1122:
3. Could a Re-energisation occur concurrently with reclassification from No Essential Plant to Essential Plant and, if it did would a 301MM be sent to the Supplier as well as the usual Re-energisation messages? Clarification: Yes, a re-energisation and reclassification from No Essential Plant to Essential Plant and Essential Plant to No Essential plant can occur. In this case a 301MM and the relevant re-energisation messages would be sent out. 4. Similarly for De-en when going from Essential Plant to No Essential Plant. |
|
| Q14 | Under “Market Messages” – “With regard to Unmetered Change of Supplier Confirmation, for Grouped unmetered the 700MM is the relevant message whereas for Single Point Unmetered it is the 105MM, as is the current market design”.When I look at MPD33 it shows both 105mm AND 700MM being sent to the New Supplier. Can you clarify, please? | Back to top |
| A14 | Clarification: A differentiation was made in relation to the Grouped Unmetered and the Single Point Unmetered in regards the messages that are sent due to the manual nature of Grouped UnmeteredThe point in the MCR relates to the fact that the initial notification of the Essential Plant will be on the 700MM for Grouped Unmetered as there is no 105MM sent in this case.For Single Point Unmetered, the 105MM will be sent as normal and this will contain the field Essential Plant at this time.This is the same as metered sites. Subsequently a 700MM will be sent containing the details of the Essential Plant field as per normal market operations | |
| Q15 | Under “Data Definition” – “This flag will be a new Boolean Flag. Where the flag appears with a value of 1 it will mean that there is essential plant at this MPRN, and in the exceptional case where this flag appears with a value of 0 this would means that there is not essential plant at this MPRN”.In what circumstances would the flag appear with value 0? | Back to top |
| A15 | Clarification: A value of 0 will only appear on the 301MM, 700MM and 700W MM when an MPRN that was Essential plant has been updated and the flag removed i.e. it was originally created as an Essential plant and a value of 1 had been sent to suppliers on the original 301MM or 700MM. ESB Networks wish to advise the suppliers that it is no longer an Essential Plant and as part of this the flag will be removed from the MPRN on the Central Market system and this removal will be sent to the supplier in the form of a 0 in the field Essential Plant.If a site was never an Essential Plant then the Essential Plant field will never be populated i.e. a blank value. ESBN Update July 2015: for the avoidance of doubt, this means that the essential plant flag will not be present in the market message. | |
| Q16 | Could a Re-energisation occur concurrently with reclassification from No Essential Plant to Essential Plant and, if it did would a 301MM be sent to the Supplier as well as the usual Re-energisation messages? | Back to top |
| A16 | Clarification: Yes, a re-energisation and reclassification from No Essential Plant to Essential Plant and Essential Plant to No Essential plant can occur. In this case a 301MM and the relevant re-energisation messages would be sent out.Similarly for De-en when going from Essential Plant to No Essential Plant. | |
| Q17 | Will TSO ever receive the Essential Plant Flag on any MMs? | Back to top |
| A17 | Yes, should there be an MCR1122 essential plant flag implication for any MPRN for which a relevant market message is being sent to TSO. This applies to Market Messages • 101 – New Connection Registration Acceptance • 105 – Change of Supplier Confirmation • 301 – Meter Point Characteristics • 106D – Meter Point Status Confirmation – De-Energisation • 106E – Meter Point Status Confirmation – Energisation • 331 – Interval Meter Technical Details |
|