IREG met on 9th August 2017 and discussed the following:
MIF215 – Metering Commission Flow
ELEXON provided an update on the development of the Metering Commissioning Data Flows, as discussed at the last workshop.
The workshop has developed two Data Flows:
- For the notification of commissioning information and status, sent by the Distribution Network Operator (DNO) to the Meter Operator (MOP); and
- For the notification of additional defect information and commissioning status, sent by the MOP to the Supplier.As part of the development of these Data Flows, several Data Items are being developed, along with a list of reason codes to be used to notify defect/omission reason.Further consideration is being carried out by ELEXON on the associated risks posed by the role of National Electricity Registration Scheme (NERS) accredited Independent Connection Providers (ICPs) in the process. A BSC Issue may be raised to consider this further.ELEXON will update IREG at the next meeting, on progress.
- ELEXON is also proposing to amend Metering Code of Practice (CoP) 4 regarding the retention of commissioning records. This is because under the proposed changes to the commission process, the DNO and MOP will hold the commissioning records from their respective commissioning actions.
- ELEXON also advised that changes to the relevant processes captured in the Balancing and Settlement Code (BSC) Procedures (BSCPs) are being developed. These changes will set a maximum of 80 Working Days to complete the commissioning processes, ahead of the second reconciliation run for settlement (R2) at 84 Working Days.
- It is intended that both Data Flows will also be used on a change of MOP, sent by the old MOP to the new. The first flow is intended to pass on relevant commissioning information to the new MOP. The second flow would be used where part or all the commissioning information is incomplete. The group felt that the utility of these flows in MOP to MOP communications will negate the need for the original third Data Flow.
MIF233 – Creation of a ‘rejection flow’ response to a request to send a D0215
ELEXON presented an overview on its new MRA Issue (MIF). This proposes a new Data Flow where by the DNO can reject a request from the MOP to send a D0215 (Provision of Site Technical Details) Data Flow. This is so that the DNO can advise, for instance, that it is not the equipment owner or the metering equipment was installed pre-BSC Modification P283 (Reinforcing the Commissioning of Metering Equipment Processes).
This MIF is to address two issues:
- The current industry issues and complaints around the sending of the D0215 Data Flows from a DNO to a MOP where a request for the flow may be inappropriate; and
- BSC auditor identified issues around the quality of information provided in the D0215 Data Flow, particularly on communications sent pre-P283.
MIF219 – Accuracy of Working Practice Product Set (WPPS)
Gemserv presented draft changes to four Working Practices (WPs):
- WP45 – NHH Metering of when D0052 may be sent;
- WP61 – Content of D0148 between a Supplier and its Agents;
- WP74 – Use of D0010 and J0171 on a Change to Metering System Configuration; and
- WP75 – Use of ‘Date and Time’ in D0010 for HH market.
Pending confirmation by both ELEXON and Gemserv as to whether the provisions in the Working Practices relating to settlement are already captured under the BSC and its subsidiary documents, IREG agreed that the four WPPS CP should be raised to delete the WPs; and that no changes to the Data Transfer Catalogue (DTC) will be required. If, however, the assessment identifies that the provisions from a settlement perspective are not captured in the BSCPs, then the DTC CPs, along with the WPPS CPs can be raised.
For WP75, IREG agreed that if the BSCPs do not capture the requirements; or that there is no need for the notes to be included in the DTC for non-settlement purposes, the Gemserv should issue a request for information (RFI). This will be to determine whether the changes to the DTC as presented by amendment of the D0010 (Meter Readings) should instead be captured in the J0016 (Reading Date & Time) Data Item. In addition, any RFI should seek to determine if the notes should apply to elective Half Hourly (HH) meters, non-Data Communications Company (DCC) HH meters or both.
Gemserv also presented three additional WPs for the next reviews. IREG agreed that these should be progressed to review, which should include an assessment by both ELEXON and Gemserv on whether the provisions are already captured in the BSCPs or needed for non-settlement purposes. These being:
- WP129 – Usage of DTC flow D0290 “Instruction to Read Meter” (DP to DR);
- WP144 – The use of Site Visit check codes 02 and 20; and
- WP150 – Advanced Meters: Auxiliary Metering Information.
MIF225 – Update on legal counsel for Intellectual Property drafting
Gemserv advised that the MRASCo Board has sought legal counsel on the Intellectual Property drafting. Further clarification is being sought, which includes the impacts on Parties and third-parties; and on cross-code working.
MIF227 – Referral from MAP10 to MAP12
IREG discussed the wider considerations regarding the associated processes captured by MRA Agreed Procedures (MAPs) 10 and 12, as well as the mismatches. It was agreed that a MAP CP should be raised to clarify that the processes apply to Domestic HH sites, as well as Non-Half Hourly sites. A Sponsor for the CP was identified, who will also consider whether to progress changes (either as part of the MAP CP or as a separate MAP CP) to include Co-operative Objections
- MAP 10 – ‘Resolution of Erroneous Transfers’
- MAP 12 – ‘Customer Requested and Co-operative Objections’
MIF231 – ECOES Search Facility
MIF231 seeks to amend the ECOES User Search functionality to enable the maximum number of searches be set at a Company level. Along with initially resetting the maximum numbers to a multi-tier approach. IREG questioned the rationale for the change, and specifically the maximum number of searches for each tier. It was noted that the rationale is associated with data protection risks, identified as part of the MRA Security Committee’s (MSC) assessment of General Data Protection Regulation (GDPR). IREG requested that MSC release the rationale so that IREG could agree on the proposed solution.
MIF232 – Issue with Suppliers sending D0135 to Distribution Companies
MIF232 seeks to address issues where Suppliers are continuing to send D0135 (Asset Condition Report) Data Flows to Distribution Businesses with the relevant Asset Condition Code in the “Additional Information” field due to the restriction placed on the Supplier in the 60H group within the flow. IREG agreed to issue an RFI to determine from Suppliers:
- in what situations do they send the D0135 flow; and
- when it is sent, how they identify if the equipment is under the DNO or MOP responsibility.
IREG will next meet on 13th September 2017.