1 / 60

IGG Agenda 27 th June 2012

IGG Agenda 27 th June 2012. Minutes. Draft Minutes from IGG meeting 23 rd May 2012 For approval today. IGG Action Items. Updated IGG Action List issued in advance of meeting Actions closed since last IGG meeting: 11 IGG Actions carried forward: 7. IGG Actions Carried Forward.

booth
Télécharger la présentation

IGG Agenda 27 th June 2012

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. IGG Agenda 27th June 2012

  2. Minutes Draft Minutes from IGG meeting 23rd May 2012 For approval today.

  3. IGG Action Items Updated IGG Action List issued in advance of meeting • Actions closed since last IGG meeting: 11 • IGG Actions carried forward: 7

  4. IGG Actions Carried Forward

  5. LTNA Sites: Suppliers to consider ESBN Proposals and forward feedback to RMDS • Feedback from 2 Suppliers • 1 preference for Option 3; Supplier requests de-energisation and cost of work is socialised • It is better for the market as a whole that long term vacant sites are de-energised to ensure there are no safety risks. • numbers across the market are not significant. • With option 1 & 2 suppliers are still exposed to the cost associated with the reduced MIC (50 kVA or 100 kVA). • 1 Supplier preference for alternative Option 4 • ESBN would allow the supplier to be deregistered 3 months after the supplier has requested the de-energisation of the site • In order to quantify what impact the proposal will have on costs ESBN require details from suppliers on the connections that qualify (include MPRN, DUoS Group and current MIC).

  6. CER Update Industry Governance Group 27th June 2012

  7. Retail Market Assurance Services for the Irish Electricity Market Peter Varley IGG 27th June 2012 peter.varley@gemserv.com

  8. Assurance Activity UpdateBusiness As Usual (RMDS) Assurance Process Document Third review comments from RMDS received Final draft compiled and being reviewed by RMDS Expect it to be ready for next IGG

  9. Assurance Activity UpdateHarmonisation (HRDS) PQ Most questionnaires received but some still awaited IPTs have been prioritised and streamed scenarios and evidence requirements have been written individual Supplier Packs are being prepared Supplier test slots planned

  10. Assurance Activity UpdateHarmonisation (HRDS) • Proposed Go/No-go criteria (for discussion): • All • No major issues raised at ESBN site visit(s) • No major issues arising at EMMA/Webforms commissioning • All Priority 1 scenarios successfully completed for all Large Suppliers • If criteria not met CER take advice and then determine whether to go/no-go

  11. IPT Streaming – Large Suppliers, TSO

  12. IPT Streaming – Small Suppliers

  13. IPT scenario definition

  14. IPT Evidence Required

  15. Questions & Discussion

  16. MRSO UpdateJim Long 27 June 2012

  17. 105L Market Messages

  18. 010 Market Messages

  19. COS In Progress 19/05/2012 – 8,013 • Reviewed Monthly • Suppliers notified of individual switches outstanding and reason • Switch outstanding for Energisation or Token Meter Removal will not time-out • Contact Customer or submit cancellation • 32 Switches held due to an existing Open Service Order

  20. COS and CoLE

  21. Debt Flagging

  22. Disputed Reads Processed

  23. Objections – Erroneous Transfers

  24. Objections

  25. ROI HSP Project Update Conor Garrigan

  26. HSP Agenda Items • Project Plan Update • Design Clarifications (Extranet and Data Formats)

  27. High Level Schedule

  28. ROI HSP Design Clarification Standard Load Profile on Supplier Extranet

  29. Final position and format for new Standard Load Profile field on Extranet

  30. ROI HSP Design Clarification Data Format Changes (aligning with existing live Harmonised Design in NI)

  31. Data Format Changes in Market Messages to Support new TIBCO-based Communications Background The introduction of the new TIBCO-based communications technology requires a number of changes in the contents and/or format of certain fields in some Market Messages. Summary of Impact Changes are being introduced in the following areas: • Changes in naming convention for XML Messages • Dropping of leading zeroes in Transaction Reference Number in Message Header on all outbound from Supplier messages created by Webforms • Change in format of MarketTimeStamp field in Header Segment on all Messages to conform with UTC format These changes are described fully overleaf. All of these changes will be added to the ROI Extended Impact Summary spreadsheet as presented at the ROI MP Planning Workshop on 17 April 2012. The updated presentation will be Version 1.3 and will be replaced in the HSP Project Folder on the RMDS Calendar.

  32. 1. Change in Market Message File Naming convention Inbound to Supplier Outbound from Supplier (via Webforms) As-Is • Planning and Implementation Notes • This change does not impact on the HBL or Harmonised Schema • This change is separate from the12 message name changes in the Harmonised Schema (see the category “Message Name Changed” in the ROI Extended Impact Summary spreadsheet on page 16 of the MP Planning Workshop slide deck) MM Number Date and Time MM Number Date and Time Mxxxx_YYYYMMDDHHMMSSSSS Mxxxx_YYYYMMDDHHMMSSSSS Seconds since base date Seconds since base date MM Number TIBCO Process ID To-Be MM Number TIBCO Process ID (Pending or Outbound Folder) MIM_xxxx_sssssssssssss_pppp (Inbound Folder) MIM_xxxx_sssssssssssss_pppp DSO_MIM_xxxx_sssssssssssss_pppp (Archive/ Inbound Folder) DSO_MIM_xxxx_sssssssssssss_pppp (Archive/ Outbound Folder)

  33. 2. Dropping of leading zeros in Transaction Reference Number (TxRefNbr) in Header Segment on all messages outbound from Supplier created by Webforms MIM YYYYMMDD HHMMSSSSS As-Is (assuming message is from S98) • Planning and Implementation Notes • Change applies only to outbound messages to Networks created by Webforms • Leading zeroes are dropped from HH, MM and SS but not from milliseconds • This field is populated automatically on messages created by Webforms users • This field is unchanged on all outbound to MPs messages • Validation rules for this field on inbound to Networks messages are unchanged • This field is not to be confused with the MP Business Reference field in the body of many Market Messages (that field remains unchanged by this change) • This change does not impact on the HBL or Harmonised Schema S98_20120627090105001 To-Be (assuming message is from S98) MPID YYYYMMDD HHMMSSSSS S98_20120627915001

  34. 3.1 Change in format of MarketTimeStamp in Header segment of all messages – Inbound to Supplier WinterTime SummerTime • Planning and Implementation Notes • Change applies only to the MarketTimeStamp field and not to other timestamp fields in the message body such as those for IntervalPeriodTimestamp in 341, 342 and aggregation messages • 602 Message: the existing StartTime and EndTime timestamps are both in the format “DD-MMM-YY HH:MM:SS” so are not impacted by this change • This change does not impact on the HBL or Harmonised Schema • Note: As-Is TimeZone does not change with Wintertime/Summertime changes As-Is YYYYMMDD HH:MM:SS.SSS TimeZone TimeZone YYYYMMDD HH:MM:SS.SSS 2012-01-01T10:15:20.073+00:00 2012-06-01T10:15:20.073+00:00 To-Be YYYYMMDD HH:MM:SS.TT TimeZone YYYYMMDD HH:MM:SS.TT TimeZone 2012-01-01T10:15:20.07Z 2012-06-01T10:15:20.07Z

  35. 3.2 Change in format of MarketTimeStamp in Header Segment of all messages – Outbound from Supplier (by Webforms) WinterTime SummerTime • Planning and Implementation Notes • MarketTimeStamp is populated automatically on all messages created by Webforms • Validation rules for this field on inbound from Supplier messages are unchanged • This change does not impact on the HBL or Harmonised Schema As-Is YYYYMMDD HH:MM:SS.mmm TimeZone TimeZone YYYYMMDD HH:MM:SS.mmm 2012-01-01T10:15:20.073+00:00 2012-06-01T10:15:20.073+01:00 To-Be YYYYMMDD HH:MM:SS YYYYMMDD HH:MM:SS 2012-01-01T10:15:20 2012-06-01T10:15:20

  36. RMDS Update Retail Market Design Update Aileen O Connor, RMDS 27th June 2012

  37. LTCA Working Group • Working Group held 13/06/12 • Draft WG Report issued 22/06/12 • Wide variety of issues and partial solutions • Actions for ESBN/Suppliers to provide evidence and statistics for next meeting • Facilitate better focus on effective solutions • Conference Call 28/06/12 to discuss next meeting date • Terms of Reference V5.0 for Approval

  38. ESB Networks DR1111 Automated Debt Flagging Discussion DocumentMeeting of the IGG , 27th June 2012

  39. DR1111 Automated Debt Flagging • Background • CER Decision Customer Bad Debt in Electricity & Gas Markets CER/11/106 requires • an automated solution to replace the current interim Debt Flagging Process • Since October 2011 the manual interim process based on WP20 is in place • Subsequently a fast-track solution for Service Orders was implemented • DR1111 • The objective of these slides is to present options on the Automation of Debt Flagging to • inform the debate within the industry • The options are based on a market messaging solution • Discussion Request DR1111 will be raised and will be based on the outcome of the debate • and CER requirements • Key Concepts of Debt Flagging • Old Supplier must Debt Flag where specific conditions and thresholds are met • New Supplier can if they choose Cancel the COS, but is not obliged to do so

  40. DR1111 Automated Debt Flagging – Two Options • Two Options are presented for consideration • Option A : 3*New Market Messages; Debt Flag passed through MRSO from Old to New Supplier • Option B : 3*New Market Messages, Do not raise Service Orders (Re-energisation /Remove Token Meter), Introduce automated timelines • Comment • Option A retains the disadvantage of a need for a manual fast-track process for certain Service Orders • Option B is a more complex solution and necessitates a delay in the raising of certain Service Orders • 3* New Market Messages

  41. DR1111 Automated Debt Flagging – Option A : 3*New Market Messages Debt Flag passed through MRSO from Old to New Supplier • Option A : 3*New Market Messages Debt Flag passed through MRSO from Old to New Supplier • The Old Supplier will get a notification message 110 from MRSO that they are losing an MPRN in a COS process. • Old Supplier carries out their own checks and where a Debt Flag is necessary then the MPRN is sent to MRSO via the 018MM . • This should be timed to arrive while the COS is still in progress. • In this Option the COS process does not wait for an 018MM • Where the 018MM is not received by MRSO from the Old Supplier while the COS is still in progress then it will be rejected via 118R , and the COS process will continue as normalSee #2 • Where the Old Supplier does not Debt Flag then MRSO will not receive an 018. • and the COS process remains as-is • MRSO will perform automated checks via the Central Market System[See #7] on the 018MM and where passed will send the Debt Flagged MPRN to the New Supplier via the 118MM • however, should these checks detect a problem then the 018MM will be rejected and the • 118R will be sent to the Old Supplier with the appropriate reject reason code • After receiving a 118MM the New Supplier can cancel the COS for Debt Flagging on 011MM an via a new cancellation reason See #6 • The 011MM should be timed to arrive while the COS is in progress otherwise it will be rejected See #6 • Similar to the current interim solution, a manual fast-track process will be needed for certain Service Orders viz Re-energisation where previously Deenergised NPA/ Remove Token Meter

  42. DR1111 Automated Debt Flagging – Sundry items relevant to both Options • #1 The 110 is proposed to be amended to indicate where there is a COLE either explicit or inferred • #2 Where the Old Supplier submits a late 018MM notice of Debt Flagging then the proposal is to reject back to the old supplier via 118R • - 018MM must arrive into MRSO while the COS is in progress otherwise it will be late - Option A • - For Option B an 018MM must arrive into MRSO during the <<24hr or 48hr >> First Wait Period • #3 QH sites, where eligible for Debt Flagging, will need to be accommodated in the final approved design and where needed changes to the Central Market System will be proposed • #4 Assumption tbc is that Unmetered will be included in Debt Flagging and   • - As Unmetered is a manual process the assumption is that the Debt flagging process for Grouped Unmetered will be manual and via the current SFTS   • - Single Point Unmetered is assumed to be part of the automated solution • #5 Should Suppliers’ sign-up process include a warning where a prospective customer is de-energised due to NPA or has a token meter to be removed that the physical work of Re-Energisation or Removal of Token Meter may be prevented from starting until the Debt Flagging process has run its course

  43. DR1111 Automated Debt Flagging – Sundry items relevant to both Options • #6 Proposals for cancellation of COS due to Debt Flagging • General • The 011 is proposed to be amended to indicate a cancellation due to a Debt Flag • Currently the Cancellation Reason code ME is being used in the interim process and this is proposed to be replaced by a new value • Where a Supplier submits an 011MM and the cancellation is for Debt Flagging there will be new validations to check if MRSO has received the 011MM before an expiry window • For Option A the expiry window is proposed as follows • After receiving a 118MM the New Supplier can cancel the COS for Debt Flagging on 011MM • The 011MM should be timed to arrive while the COS is in progress otherwise it will be rejected • Noteshould Option A be the favoured option to progress then further work would be needed to define the • cancellationwindow for a manual fast track solution, as well as all other details related to this sub-process • For Option B the expiry window is proposed as follows • There will be new validations to check if MRSO has received the 011MM before the SWP expiry. • and where late the cancellation will be rejected on a 111R and with either the existing TIM or a new • rejection reason code. • Note that the Cancellation 011MM for Debt Flagging will not be accepted if sent in before the start of the SWP • because the 118MM will not have been sent out

  44. DR1111 Automated Debt Flagging – Checks on the 018MM - both Options • #7 Automated Checks proposed on the 018MM leading to rejections on the 118R to the Old Supplier • eg • Invalid MPRN [IMP] • MPRN is not registered to Supplier [SNR] • Duplicate 018MM has been sent in by the Old Supplier [IA] • COS not in Progress or Cancelled [IA] • There is a COLE with the COS [COLE rejection reason - New] • DUoS Group is invalid [DG Rejection Reason - New] • Comment existing reject reason codes will be used where possible ; new values are likely to be needed

  45. DR1111 Automated Debt Flagging – Option B : 3*New Market Messages Do not raise Service Orders (Re-energisation /Remove Token Meter), Introduce automated timelines • Option B : 3*New Market Messages Do not raise Service Orders (Re-energisation /Remove Token Meter), • Introduce automated timelines • For all COS, MRSO via the Central Market System will perform automated checks similar to those for the 018MM • and where there is a COLE either implied or explicit , or a DUoS Group that is valid for Debt Flagging , then there will be a further check carried out such that • if the MPRN has been Deenergised for NPA or has a Token Meter that is to be removed then no Service Order will at this point be raised for Reenergisation / Removal of Token Meter resp. • The Old Supplier will get a notification message 110 from MRSO that they are losing an MPRN in a COS process. • The First Wait Period of << 24hr or 48hr >> is kicked off. [FWP] • This is to allow the Old Supplier to carry out their own checks and where a Debt Flag is necessary then the MPRN is sent by the Old Supplier to MRSO via the 018MM . • MRSO will perform automated checks via the Central Market System [See #7]on the 018MM and where passed will send the Debt Flagged MPRN to the New Supplier via the 118M • Should these checks detect a problem then the 018MM will be rejected and the 118R will be sent to the • Old Supplier with the appropriate reject reason code • Should the 018MM not be received by MRSO from the Old Supplier while FWP is open then it will be rejected via 118R • Where the Old Supplier has not sent in a valid Debt Flag message 018 before the expiry of FWP then the • ReEnergisation or Token Meter Removal Service Order is now raised, where needed. • and the Cos process will continue as normal

  46. DR1111 Automated Debt Flagging – Option B : 3*New Market Messages Do not raise Service Orders (Re-energisation /Remove Token Meter), Introduce automated timelines • Option B : 3*New Market Messages Do not raise Service Orders (Re-energisation /Remove • Introduce automated timelines...continued • Otherwise at the expiry of FWP and where the Old Supplier has sent in a valid Debt Flag message 018 the • ReEnergisation or Token Meter Removal Service Order will not be raised • The Second Wait Period of <<24hr or 48hr >> is kicked off[SWP] • This is to allow the New Supplier time to send in an 011 Cancellation Message before Service Orders are raised. • If the New Supplier sends in a Cancellation 011MM there will be a new cancellation reason code for Debt • Flagging, and where a cancellation is for Debt Flagging there will be new validations to check if MRSO has received the 011MM before the SWP expiry. • If not then the cancellation will be rejected on a 111R and with either the existing TIM or a new rejection reason code. • Note that the Cancellation 011MM for Debt Flagging will not be accepted if sent in before the start of the SWP because the 118MM will not have been sent out • See #6 • Where the New Supplier does not send in a valid Cancellation 011MM by the expiry of the SWP then the • ReEnergisation or Token Meter Removal Service Orders will be raised, where needed. • and the Cos process will continue as normal

  47. DR1111 Automated Debt Flagging – Option B : 3*New Market Messages Do not raise Service Orders (Re-energisation /Remove Token Meter), Introduce automated timelines • Items specific to Option B • #8 Service Orders for certain MPRNs that are Deenergised for NPA or need a Token Meter to be removedare prevented from being raised by this process from << 2 or 3>> and possibly up to << 3 or 4>> time periods ref#11 for time periods • - There is no Fast-tracking element in this proposal • - Operationally, ESB Networks would not favour a new manual fast-tracking process • #9 Not all MPRNs that are Deenergised for NPA or need a Token Meter to be removed will meet the euro criteria for Debt Flagging. • It is the Old Supplier and not MRSO who is able to perform this calculation after receipt of the 010MM. • This is why all of these MPRNs would be included in the process to prevent the Service Orders from being • raised , and not just those that are eligible for Debt Flagging • #10 In the specific Debt Flagging scenario where Service Orders are not being raised pending the outcome of the Debt Flagging process then Suppliers would need to be aware that the 102P will issue even though no Service Order has been raised at that point , and in cases where there is a cancellation of that COS then no Service Order may have been raised at all even though a 102P has issued • ESB Networks SLA timelines start as normal once the Service Orders are raised.

  48. DR1111 Automated Debt Flagging – Option B : 3*New Market Messages Do not raise Service Orders (Re-energisation /Remove Token Meter), Introduce automated timelines • #11 Slides on Option B follow illustrating sample Message Flows and timelines for wait periods • General • The proposal is that the start of the automated timeline will be from an identified trigger , and not from midnight. • This allows for a Service Order to be raised earlier than if using a midnight-midnight clock , and from a Customer • perspective the Re-Energisation following NPA to be processed as soon as possible • Days are Working days, and therefore Weekends and Bank Holidays are not counted within the wait period timelines • <<48hr + 48hr >> wait periods • FWP starts from when 110 is outbound from SAP and ends a max of 48hr later • SWP starts from when 118 is outbound from SAP and ends a max of 48hr later • This timeline is consistent with WP20 and along Gas timelines • Up to 4 days longer for impacted Customers to have Service Order raised for Reenergisation of NPA or Token Meter removal • << 24hr + 24hr>> wait periods • FWP starts from when 110 is outbound from SAP and ends a max of 24hr later • SWP starts from when 118 is outbound from SAP and ends a max of 24hr later • Earlier raising of Service Orders than with <<48hr + 48hr >> • Less time for Suppliers to respond with 018MM [Old] , 011MM [New]

More Related