May » 2019 »

The MRA is turning 21…

This year marks the 21st Birthday of the MRA.

MRASCo was established in 1998 and change in the industry since then has been dramatic. Recent years are no exception and to commemorate the journey the MRA has been on since 1998, and to thank all those that have been involved in the Code, we have commissioned a short documentary to celebrate its successes.

Below is a trailer, the full video will be released on 11th July 2019.

 

MDB Update: April 2019

MDB was held on 25th April 2019. The table below shows the Change Proposals, voting outcomes and implementation dates.

CP ReferenceImplementation DateOutcome
WPPS CP 0179 – Remove WP77 from WPPS7th November 2019Accept Modified
DTC CP 3564 – Include Additional D0170 Data Flow Notes in Annex C7th November 2019Accepted
DTC CP 3547 – New rules in Annex C to incorporate rules previously in WP34n/aDeferred for IA
WPPS CP 0152 – Remove WP34 from WPPSn/aDeferred for IA
WPPS CP 0180 – Remove WP102 from WPPS7th November 2019Accepted
MRA CP 0260 - Amendments to the MRA to reflect the United Kingdom’s withdrawal from the European Union without a dealTBCAccept Modified

IREG Update May 2019

IREG met on 08th May 2019 and discussed the following MRA Issue Forms (MIFs) and Electricity Central Online Enquiry Service (ECOES) changes.

 

MIF219 – Full review of the Working Practice Product Set (WPPS)

IREG received an update of the progress of the review. IREG noted the further analysis carried out on the remaining Working Practices and agreed to continue the review. It noted that there were still Working Practices (WPs) that could be removed from the WPPS due to redundancy or included within the Data Transfer Catalogue. As such, it agreed the seven (7) drafted Change Proposals (CPs) as they were now redundant could progress to MDB.

 

MIF278 – Gap with HH Change of Meter Operator

IREG noted the very low volumes in the papers of how many D0150, D0268 and D0303 Data Flows were issued without the Manufacturer Make and Type being completed.

IREG agreed that a conversation would be required with the Proposer to decide whether a solution needed to be developed due to the fact that, although the fields are not Mandatory in the D0268 Data Flow they are being populated in the vast majority of cases.

 

MIF281 – Crossed Meters

A further updated draft MAP was presented to IREG reflecting the considerations agreed at the previous meeting. IREG noted the changes made and agreed that the procedure was ready to liaise with the ECOES Technical Service Provider to develop an outline ECOES solution for the procedure. The group noted that the prompts could be automated similar to current Additional MPAN request procedure. The initial prompts could be built in to notify the users set up to manage the process. IREG agreed that the next steps would be to liaise with the ECOES TSP regarding how the process could work, what changes may be required for the ECOES URS and consider them all at the next meeting.

 

MIF287 – Definitions within the D0350 Data Flow

IREG were updated on the processes that the DCC uses and the status’s which are utilised when setting up a Smart Metering System. IREG were advised that there were three Service Flag codes Active, Suspended and Withdrawn. Active meaning that the first meter on the metering system has been commissioned. Suspended meaning that a CPA Certificate has expired for the last meter in the metering system or the Device status was removed on the CPL or the Smart Metering System was no longer in place. Withdrawn meaning that there is a Service Opt out or the Smart Metering System is no longer in place. IREG were advised that on commissioning of the first meter in the Smart Meter System the Active code is utilised and issued in the D0350 Data Flow and that status would stay until all of the Smart Meter System was removed. Parties would know that as the Meter Operator would then issue the D0149/D0150 and D0312 to confirm all of the meters had been removed. IREG noted that on the Smart Meter Devices that a number of status are recorded or moved through pending what was happening with that Device, these were Pending, Whitelisted, InstalledNotCommisioned, Commissioned, Decommissioned, Suspended, Recovery, Recovered, however, these were not passed via the D0350 Data Flow only the Commissioned was translated to Active on the Service Code flag. IREG discussed that there have been instances where these other status’s have been noted rather than just Active. IREG were advised that these could be bugs in the process and should be raised to the DCC or via SEC team. IREG advised that it would be useful to receive the other statuses held on the SMS via the D0350 as the D0149 and D0150 Data Flows are received too late timewise for a Change of Supplier and better to receive confirmation of the status via the D0350. IREG agreed that as next steps it would be helpful to see if understanding could be obtained from the DCC as to how they manage the SMS updates and if possible, to make technical changes to send the data parties require.

 

MIF288 – Industry Contacts Database

IREG reviewed the high-level Impact Assessment carried out by the website Technical Service Provider. IREG noted that that a number of the requirements discussed at the last meeting could be developed, however, the bulk update requirement would require significant effort due to the data security and trying to minimise loss of data and quality when opening a spreadsheet. The TSP felt that the same result could be delivered through creating a proper database and being able then to set people up and then have the ability to select the roles those people would be undertaking. IREG agreed to the suggestion/proposals and to further develop the requirements for the solution in order to formalise any costs.

 

MIF289 – HH Related MPANs

IREG were advised that the RFI had been issued following the discussions at the last meeting and the results had been collated and included within the papers for the meeting. IREG noted the MIF and the collated results will now be discussed under the Faster Switching Expert Group to develop a solution.

 

MIF291 – Refining the list of valid codes for the J1699 (Priority Services Category) Data Item

IREG received a verbal update from the previous Safe Guarding Customer Working Group (SGCWG) highlighting that the discussions had now moved on and that DNO’s are working towards sharing PSR data via the D0225 Data Flow and have provided Water UK with examples of the Data Flows and an explanation on the how information is recorded on the PSR registers for different DNOs. IREG further noted that testing plans are in development to test water sector DTN gateways although Water Companies would not be signing up to the DTSA. Concerns on how Energy Companies can meet their GDPR obligations and respond to Subject Access Requests had been raised and responded to. IREG noted that MPAN address mapping to the water sector was being explored which IREG highlighted that ECOES was already there with an API which could be utilise.  IREG noted that some concerns had been raised due to the fact that some Distribution companies operate UK wide and therefore may be more difficult to do a one to one mapping as well as that those companies may have to receive and pass on significant volumes of updates. IREG were advised that these obligations were introduced some time ago through a combination of Water UK, Ofgem, Ofwat obligations and commence next year.

 

MIF292 – Lower Case Meter Serial Numbers

The Proposer presented the MIF and explained that an issue had been identified by FSEG whereby MPRS will be processing the D0312 and D0304 Data Flows under the new arrangements from the June 2019 release and that the data received within those Data Flows will be converted and stored in uppercase and the subsequent response data within the Data Flows are sent out in uppercase. IREG noted that this could cause issues for Meter Operators (MOps) and Supplier systems if they are expecting the MSN back in lowercase. IREG were advised that within ECOES there were approximately 2000 MSN records, current and historic that are in lowercase.

IREG discussed a potential solution to the issue in that a change could be made to the description of the MSN Data Item to state that it should be filled out in uppercase. It was agreed that this would be a large system change for the limited volumes that this would not be viable. It was also agreed that the MRA do not have the relevant vires to govern what the Mops would do to rectify this issue. IREG suggested as an alternate that a note could be added to the ECOES User Requirement Specification (URS) to highlight that MSN data will be processed as uppercase and parties should expect this when receiving response Data Flows. IREG agreed that this was a more cost-effective solution to the limited numbers affected. IREG suggested that this note could also be added to the MPAS Validation Rules and noted that this would need to be raised directly with the MPAS TSP at the next FSEG meeting and report back to IREG.

 

MIF293 – COMC identification issue for Agents

The Proposer advised IREG that as agents they could usually determine the appointment type (COS, COA) from the information contained in the D0155 and D0148 Data Flows received from the Supplier, however a COMC cannot be identified.  The COMC concurrent with a COS appears to be a COS, therefore their system works to the standards associated with the COS such as trying to produce a D0086 Data Flow and expecting historical data (D010 and D0152 Data Flows). The standards however, for a COMC and the Data Flows involved are different. The Proposer further highlighted that the number of concurrent COS with COMC from HH Elective back to NHH has increased taking it from an unusual business event to a more frequent business event prompting them to raise this issue in order to find an enduring solution. The Proposer highlighted that they felt that adding a new COMC Indicator into the current D0155 Data Flow would assist in them understanding that there was this event happening at the same time as the COS and or COA. IREG were advised that this issue had previously been considered under the BSC via Issue 49. Furthermore, changes had been considered CP1474 (Updating the CoMC processes to facilitate the elective HH Settlement of SMETS Meters) therefore may also need to consider the impacts on the BSC processes as well. IREG questioned whether it would be best to wait until the determinations on how the HH Settlement processes would be working. The Proposer highlighted that their current preference would be to a Change Proposal out for impact assessment. IREG highlighted that the Change Proposal wold be required soon in order to go out for impact assessment. IREG further highlighted the recent responses Agents had issued in respect of the consequential BSC changes linked to Faster Switching under BSC CP1515. IREG recommended that a joint IREG/BSC issue meeting was set up.

 

MIF294 – Suppliers can require New Connection registrations, without a Meter installed, to be cancelled

The Proposer advised that they intended to bring the new MIF to the June meeting. They highlighted that there is an issue where some Suppliers are unable to gain a Meter Point Administration Number (MPAN) where the old Supplier’s registration is at the New Connection status and the MPAN has not got to the stage of having a meter fitted and energised. To allow the Customer to switch, the current industry process is for the old Supplier to use a MAP04 request to ask the Distribution Business to cancel the initial registration in Meter Point Administration Service (MPAS). The ability to do this will cease once Central Switching Service (CSS) goes live, so the reasons for needing to use the MAP04 Procedure needs to be fully understood and addressed. The Proposer advised that this issue had been identified in the Faster Switching Expert Committee (FSEG) Consequential Changes workshop, but determined the issue was an existing Business as Usual (BAU) one.

IREG highlighted that the MAP04 Procedure is being used by some Suppliers to cancel the initial New Connection registration, in MPAS, so that the Customer can switch Supplier to another Supplier. This happens because the MPAN is not in the correct state such that the new Supplier can instigate a Change of Supplier. Currently the impact is on the Distribution Business in having to perform a MAP04 to cancel the initial registration and on the Customer as they need to wait for this to be performed before they can switch Supplier. When CSS goes live this process will cease to be available.

 

Secure Communications Change Proposal

The Proposer presented the draft Change Proposal (CP) to IREG. A Distribution Business informed IREG that the drafting of the CP was very Supplier orientated and as this change would affect all MRA Parties. The CP would need to be redrafted to encompass all parties. The Proposer agreed to redraft the CP to encompass all MRA Parties. An Advisor informed IREG that the service would be 100% funded by the Suppliers as this is the funding arrangement for the REC, it was suggested that this may need to be taken to MEC and Board for approval. It was advised that the sentence describing the funding requirements should be removed from the legal text section of the CP as this was not common procedure. An IREG member added that this CP may impact MAP09 and that this should be added to the affected MRA products section of the CP.

IREG discussed the implementation date for the CP and it was advised that the February 2020 may be a bit too ambitious and with the redraft that would take place after this meeting and that June 2020 may be more achievable. The Proposer agreed to look in to the implementation date and advised that the changes suggested would be made after the meeting and circulated to the group ex committee for review in order to attempt to get the CP in to the May MDB meeting and be issued out for Impact Assessment (IA). IREG discussed the timing of the subsequent MAP change CPs that would need to be drafted as a result of this CP, a Supplier suggested that the MAP CPs could be brought to MDB at the same time as the Secure Communications CP. IREG discussed if the timescales would be feasible for this to take place. The Chair advised that the best plan of action would be for the Secure Communications CP to be taken to MDB and voted on before the drafting of the MAP changes. It was advised that this CP would be the catalyst for the MAP changes and that it would make sense for this to be presented first, additionally if the Secure Communication CP was to be rejected it would negate the body of work undertaken to draft the MAP CPs.

A Distribution Business brought the solution section of the CP to the attention of IREG, particularly the line regarding the bi-lateral agreement between users of the service. IREG agreed that this gave parties the option to opt out of the service and agreed that this should not be the case. The Proposer agreed to remove this line. IREG discussed if the name of the service should be highlighted in the CP, it was agreed that this would not be necessary.

 

Next meeting

The next meeting is scheduled for Wednesday 12th June 2019.