1 / 44

Harmonisation Working Group Meeting: Harmonisation Technical Infrastructure Update & Harmonisation Project Approach to M

This meeting agenda includes updates on the technical infrastructure for harmonization and the project approach to market testing and go-live. It also discusses planning for supplier go-live in Northern Ireland and the scope and timelines for the Republic of Ireland.

Télécharger la présentation

Harmonisation Working Group Meeting: Harmonisation Technical Infrastructure Update & Harmonisation Project Approach to M

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Harmonisation Working Group HWG Meeting Wednesday, 6th April, 2011 NIAUR Offices Belfast

  2. HWG Agenda

  3. Harmonisation Technical Infrastructure Update& Harmonisation Project Approach to Market Testing and Go-Live Sub-Agenda • ROI Technical Platform Delivery • Planning for Supplier Go Live in NI • Approach to Supplier Market Testing in NI • RoI Scope and Indicative Timelines

  4. RoI Technical Platform Delivery Bob Turley

  5. Technical Platform Delivery in RoI • Overall design for common market message infrastructure is well advanced, although details remain to be confirmed • Design will comprise: • Single TIBCO Business Connect “ Black box “ interface between Suppliers and, • Shared TIBCO NI / RoI Market Hub • TIBCO Market Hub will route messages to appropriate market system hub. Common PI/TIBCO solution will determine the receiver/sender based on the details held in the market message. • ESB and NIE retain their separate back end systems

  6. Technical Platform Schematic Supplier A NIE Tibco BC NIE SAP PI Hub NIE SAP ISU Supplier B Tibco Market Hub ESB SAP PI Hub ESB SAP ISU Supplier C ESB Suppliers will retain existing ROI MPCC until ROI Harmonisation project delivers new SAP PI hub New Systems delivered as part of NI enduring solution System hub replaced as part of ROI Harmonisation project Existing System

  7. Planning for Supplier Testing and Go Live in NI NIAUR

  8. Regulatory Key Objectives • The Enduring Solution is planned to Go Live in May 2012. • Supplier certification / qualification and readiness is an important activity within the overall project plan • Suppliers need to be ready to fully participate in Market Testing and support a single co-ordinated Go Live in NI • Delay to Go Live resulting from any Supplier lack of readiness is highly undesirable and will have a negative impact on the competitive market

  9. Planning for Go Live • NIAUR needs adequate assurance that all Suppliers will be able to support the overall market implementation plans • Suppliers are being asked to develop their own delivery plans leading up to a May 2012 Go Live in conjunction with both the ES project, and the RoI project team, during April / May 2011 • Once such plans are available NIE will need to check these plans to ensure they meet the critical milestone dates • When Suppliers have had a opportunity to review the market implementation plans, and to complete their own in house development planning, NIAUR will seek written assurance from each Supplier that they will meet the timetable for market testing and Go Live • NIAUR will then consider the best way of monitoring overall progress to Go Live

  10. Approach to Supplier Market Testing in NI Helen Mounsey Jim McAllister

  11. Introduction Supplier Testing comprises two main activities: Ability Testing (AT) and Market Testing (MT) AT is conducted prior to MT to demonstrate that a Supplier can communicate with Central Systems according to industry baseline requirements. In the case of ES, AT will utilise the EMMA / GEMMA replacement. MT is conducted to certify that a Supplier is operating according to the Harmonisation Baseline and market procedures. It also tests interfaces to the wholesale market, and message turnaround times. Initial planning for MT and AT has now commenced within the ES Programme.

  12. Scope of AT and MT AT will require all message types for the NI Market specified within the market procedures and message specifications to be exercised. MT will require all market procedures for the NI Market to be exercised Both AT and MT will apply to the replacement central systems Both AT and MT will be completed by all suppliers wishing to participate in the market when the ES Programme is delivered. AT and MT as part of the ES Programme will contribute to the re-certification requirements of individual suppliers. AT and MT for each supplier will apply to the market sector(s) for which the supplier is certified at the time of test execution MT will execute single supplier tests and use suppliers as testing partners where beneficial

  13. Principles of AT and MT The approach to AT and MT will build on experience gained from the NI2005 and 2007 programmes, but taking into account a potential increase in the number of Certified Suppliers in NI across all market sectors MT and AT will be fully synchronised with and managed as part of the overall ES test programme Overall governance and assurance of MT / AT in NI will be via the MEPCT. A MT / AT Test Co-ordination Centre will be established to facilitate Supplier liaison, run by an experienced MT / AT manager and supported by a dedicated team of testers Current plans for Go Live in both NI and RoI suggest that Inter Participant Testing (IPT) for the RoI market will apply during July and August 2012 In the light of a common market message infrastructure, and a harmonised baseline schema, the scope of certification and assurance for Suppliers operating in both jurisdictions should be co-ordinated

  14. Approach to AT and MT The TCC will co-ordinate the overall programme of work needed for both AT and MT with all Suppliers For AT, this will include the publication of a number of supporting documents, for example: AT Approach & Testing Principles Test plan and schedule for each supplier The overall AT test plan as part of the ES Test Strategy AT scripts and test data Revised certification documentation For MT, the list includes: MT Approach & Testing Principles Test plan and schedule for each supplier The overall MT test plan as part of the ES Test Strategy MT scripts and test data Revised certification documentation Although both AT and MT execution will be dependent upon supplier readiness, they will need to be fully synchronised with and managed as part of the overall ES test programme

  15. MT Testing Principles The overall approach for Market Testing (MT) will include the following high-level principles: • Clearly defined roles and responsibilities will be specified for all parties • A structured approach to test preparation and execution will be employed • Effective co-ordination and management of testing by MEPCT and TCC • The Supplier’s test environment used for Market Testing will be configured as for ‘live’ running • A discrete set of acceptance criteria (entry and exit criteria) will apply to Market Testing • NIAUR and NIE T&D will be kept informed on the progress of testing • Testing staff will, where possible, be operators with the same/similar role in live operations • Issues that are specific to a supplier will not be communicated to any other supplier • Design issues will be managed at ES Programme level • Market tests will be witnessed by MEPCT/TCC representatives

  16. Timeline 2011 2012 24th 6th Will also confirm scope of changes to MRC First SIG workshop 30/3 Early testing of replacement GEMMA included in UAT 4th MT will not start until UAT complete (17/2) 21st

  17. RoI Scope and Indicative Timelines Bob Turley

  18. Scope • Delivery of harmonised retail market schema for RoI: • Includes harmonised: • Market messages • Data Definitions • Data Codes • Excludes: • Market facing processes • Market facing applications eg Extranet • RoI scope extended to include delivery of new TIBCO platform

  19. Revised Harmonised Schema Baseline • V1 approved in July 2010 • Since then: • NIE adoption of SAP has driven a number of changes • Additional accumulation of changes (code change request, Customer Needs functionality) need to be incorporated • We also revised baseline documents to increase their useability • Revised V2 baseline to be approved at the IGG / HWG following the completion of the NI ES realisation phase • Draft documentation for information purposes can be circulated in advance of this to the market

  20. Accumulated changes impacting on Harmonised Baseline V1 since publication

  21. Proposed timeline for RoI

  22. Timing Timing of Project is dependent on: • Receipt of updated MCR which includes all changes to MCR1002 V1.0 • Agreement with NIE Enduring Solution • Cutover Strategy • Sequencing • Time lag to Go-Live • Timing / Duration of other projects • Keypad Meter Solution • Customer Bad Debt Consultation • Free Electricity Allowance • Smart Metering • Electric Vehicles

  23. Feedback from HSG, 24th March 2011 To be provided

  24. Market Design Update Summary DR List for Consideration

  25. DR1051 v1- New 017 Meter Point Status Reason - Re-energise (Rewire) • Change Request • Allow Suppliers to inform Networks that a de-energised site has been rewired before requesting its re-energisation • New Meter Point Status Reason (E04 - Re-energise (Rewire) to be allowed on the 017 message • Harmonisation Impacting change request • At today’s Meeting • Approval to MCR and as MCR

  26. DR1052 v1 - Removal of Old Keypad Premises Number from Market Messages • Change Request • Remove Old Keypad Premises Number from 110 and 105L messages (and schema) • Old Supplier can determine Number via MPRN • Provides greater harmonisation with ROI Market • Harmonisation Impacting change request • At today’s Meeting • Approval to MCR and as MCR

  27. DR1053 v1 - Fieldwork Cancellation on CoS • Change Request • Provide new Cancellation Reason Code on 111 and 111L messages • New value of “FC – Fieldwork Cancelled” will indicate the registration request was cancelled because the associated field work was cancelled • Harmonisation Impacting change request • At today’s Meeting • Approval to MCR and as MCR

  28. DR1054 v1- Removal of Supplier Certification • Change Request • Removal Supplier Certification requirement from ESP • Removal of Reject Reason code "ISC - Invalid Supplier Certification” from 101R, 102R and 130R messages • Provides additional harmonisation with ROI market • ROI did not plan to use new code at harmonisation • Harmonisation Impacting change request • At today’s Meeting • Approval to MCR and as MCR

  29. DR1055 v1- New Register Types, Time of Use Codes and MCC Codes • Change Request • Register Types/Timeslot Codes • To more accurately define the types of registers and the time periods for measuring consumption that exist within the NI Market and to support the MCC codes that are proposed for the ESP • MCC Codes • To rationalise the set of MCC codes that will be available to Suppliers so that where possible a single MCC code will describe a unique register configuration. The proposed set of MCC codes will support the tariffs that will be available to Suppliers in the Enduring Solution and will reflect the Register Types and the time periods for measuring consumption that exist in the NI market • Harmonisation Impacting change request • At today’s Meeting • Approval to MCR and as MCR

  30. DR1059 v1- Removal of Implied Energisation from 030 • Change Request • Removal of the concept of implied energisation from the 030 message • Change of meter configuration request for de-energised site no longer taken as an implicit request for energisation and will be rejected • Supplier must submit a 017 market message to request re-energisation • NI-Specific change request • At today’s Meeting • Agreement to Classify as NI-Specific (already treated at the SIG)

  31. DR1060 v1- Removal of Fieldwork Notice Periods • Change Request • Removal of the notice periods for fieldwork appointments / requests and to prevent a Supplier booking an appointment on the Market Website for a Change of Supplier with related fieldwork for a date less than two business days in the future • Facilitates the processing of objection/debt contact notification market messages. re-energisation • NI-Specific change request • At today’s Meeting • Agreement to Classify as NI-Specific (already treated at the SIG)

  32. DR1061 v1 - De-energisation Requests by Old Suppliers during a CoS • Change Request • De-energisation requests from the Old Supplier will be rejected in the event that a CoS is in progress • The validation check will be made on receipt of the 017 market message from the Old Supplier when a CoS is in progress. The rejection reason code "CIP" will be used. • Provides further harmonisation with ROI CoS arrangements • Removes the possibility of a de-energisation after the CoS has completed • NI-Specific change request • At today’s Meeting • Agreement to Classify as NI-Specific (already treated at the SIG)

  33. DR1062 v1-Removal of DUoS Tariff - T051 • Change Request • Removal of DUoS Tariff T051 (4 Rate Unrestricted Keypad) from NI market • Tariff created to facilitate situation where a keypad customer on a single rate unrestricted tariff moved to an alternative Supplier without being disadvantaged • Keypad customer on a single rate unrestricted tariff can move and stay on the same DUoS Tariff T053 (Standard Rate Keypad) • Applies to NI Enduring Solution and Interim Solution only • ROI did not intend to use DUoS Tariff T051 • Harmonisation Impacting change request • At today’s Meeting • Approval to MCR and as MCR

  34. DR1063 v1 - EUF calculation for Re-energised sites • Change Request • Current draft retail NI market procedure for the enduring solution for Non-Interval readings (MP NI 104 NHH Readings Processing) states the following: "The re-calculated EAC will be used from the point of re-energisation unless the period of de-energisation exceeds 24 weeks in which case a class average EAC will be used." It is now proposed to re-calculate the Estimated Usage Factor (EUF) at the point of re-energisation irrespective of the period of de-energisation • Provides greater harmonisation with the arrangements in RoI • NI-Specific change request • At today’s Meeting • Agreement to Classify as NI-Specific (already treated at the SIG)

  35. DR1050 v1- NI COS Read Mix-Ups • Change Request • Where it is obvious that valid readings have been provided for CoS but are assigned by the Supplier against an incorrect register, NIE T&D will swop the readings and assign to the correct register • Provides for greater efficiency in that the CoS proceeds rather than the CoS being rejected/ timed out • NI-Specific change request • At today’s Meeting • Agreement to Classify as NI-Specific (already treated at the SIG)

  36. DR1058 v1-Meter Works Type Code, Access Arrangements - CoS • Change Request • Where meter works are required as part of a COS, provides details in a new field on the 010 message • New field to be called Meter Works Type Code, with values: • M01 Credit meter configuration code change (Non Interval) • M12 Change from Prepayment to Credit • K02 Prepayment meter configuration code change • K05 Change from Credit to Prepayment • Provides better alignment with requests for non-CoS meter works • Harmonisation Impacting change request • At today’s Meeting • Approval to MCR and as MCR

  37. DR1057 v1-Removal of Usage Type on 010 • Change Request • Removal of Usage Type field from the 010 COS message • Was used in NI to allow for change in MCC / DUOS Group during a COS • Changes in Usage Type will be prevented from occurring on a 010 market message. Additionally, a change of DUoS Group will not be allowed as part of a COS process • Provides greater harmonisation RoI processes • Harmonisation Impacting change request • At today’s Meeting • Approval to MCR and as MCR

  38. DR1056 v1- Removal of Fields from NI Market Website • Change Request • Removal of the following fields from the Website for the Enduring Solution: • Usage Type • Meter Multiplier • Certification Category • Annual Burning Hours • NI-Specific change request • At today’s Meeting • Agreement to Classify as NI-Specific (already treated at the SIG)

  39. DR1064 v1 - Interim Manual Market Process for Pre-payment Meters • Change Request • Current Token Meter technology in use in ROI is near end of life • Solution is needed to facilitate financial hardship customers beyond limited supply of current units • Proposed solution is detailed in WP0019 • Solution is largely manual, with no implications for SAP • ROI-Specific change request • At today’s Meeting • Agreement to Classify as ROI-Specific (to be treated at the IGG)

  40. DR1065 v1 - Removal of Implied Change of Usage from 030 • Change Request • Removal of the concept of implied Change of Usage from the 030 message • Provides further harmonisation with the ROI processes and consistency with the proposed DR1057 "Removal of Usage Type on 010". • NI-Specific change request • At today’s Meeting • Agreement to Classify as NI-Specific (already treated at the SIG)

  41. HWG Action Items update since last meeting

  42. Next Steps • Next HWG meeting 18th May, 2011 (Dublin) • Dates for all meetings for 2011 are on the Calendar on the RMDS website

  43. HWG Meeting • AOB

  44. HWG Meeting Thank You

More Related