110 likes | 392 Views
Electricity: Mandating the population of MSN on the Registration Service through: ... load of MSN required. CD-Rom provided by the Online Service providers. ...
E N D
Slide 1:Introduction
3 Sets of Solution Options to Consider today Solution Options Explanation Effect of our Solutions Our Objective For the Executive to give positive affirmation that progress to date is reasonable Agree the Next Steps
Slide 2:Taken as a whole, we are improving:
Closing agent appointment loophole that causes issues Making more data available to check the correct customer and site 3 data items for gas & electricity customers Introducing a new data flow to transfer core data and meter readings between Old Supplier and New Supplier post-registration Providing the facility to always use a read agreed between Suppliers & customer at CoS
Slide 3:Appoint & De-appoint Agents appropriately
This is an Electricity Issue only (a watching brief has been undertaken in an effort to avoid a similar situation occurring in Gas post-RGMA) Why? Gap in current Governance - New Supplier is not mandated to de-appoint Agents, if an Objection is upheld. Evidence suggests that some Suppliers dont do this, resulting in: More than one agent appointed to customer - confusion and a poor experience. Exceptions in future industry processes Correct charges by agents to Suppliers for services that they dont need. Some Suppliers already choose not to appoint the agents until after the Objection Window closes, removing the issue What? Ensuring that Suppliers always de-appoint Agents when required by tightening Governance in this area. How? The Options we are progressing to achieve this Translate Working Practice 34 into a MAP for inclusion into formal MRASCo Governance. Under development with Gemserv.
Slide 4:Register the correct customer and site
What is Triangulation? Elec Reg Systems Site Address MPAN Core NEW SUPPLIER Enquiry Service On-line service CD Rom Gas Reg Systems MSN MSN
Slide 5:Register the correct customer and site
How? The Options we are progressing to achieve this Electricity: Mandating the population of MSN on the Registration Service through: MPAS Databases + MPAS Online (if they provide it) + CD-Rom 14 different Online MPAS Enquiry Services no MPAS load of MSN required. CD-Rom provided by the Online Service providers. A central Online MPAS Enquiry Service no MPAS load of MSN required. CD-Rom provided by the Online Service providers. Gas: Easy access to all iGT Registration Data by mandating through industry governance: All iGTs provide an Online Enquiry Service (Some, like IPL, already do) All GTs populate a Central Online Enquiry Service Xoserve in process of pulling together commercial proposition for full SPAA Service for iGTs which would satisfy this.
Slide 6:Accurate Billing Accounts:Obtain enough data to set up an accurate billing account
What? Cross Validation & Core Data Transfer NEW SUPPLIER MAM / MOP OLD SUPPLIER Billing Address Related MPAN MSN Register ID No Dials / Digits Metric / Imperial PP Indicator Meter Read Factor Meter Type Remotely Read Import/Export Profile Class MTC LLF Class ID REGISTRATION SERVICE DC Master Data Master Data Replicated Data Core Data Transfer Flow
Slide 7:Accurate Billing Accounts:Obtain an Agreed Read for CoS Billing
What? Agreeing CoS Read to Close / Open Bills NEW SUPPLIER NEW DC / GT Last Valid Read Read History OLD SUPPLIER (Holds Reads for Billing Purposes) Last Valid Read Read History Do not match in all cases Forecast Of acceptable CoS Read Via Core Data Transfer Flow Via existing mechanisms Ideal: Settlement = Old Supplier = New Supplier = Customer
What? Utilise an early Read if it is captured NEW SUPPLIER NEW DC / GT Last Valid Read Read History OLD SUPPLIER Read History Via Early Read Flow before SSD-9 Via D0010 / U01 Flow If validated against Billing Read History If invalidated against Billing Read History Ideal: Early Read agreed by Suppliers and included in History sent between DCsSlide 8:Accurate Billing Accounts:Obtain an Agreed Read for CoS Billing
What? Submit the Forecast Read if no CoS Read received NEW SUPPLIER CUSTOMER NEW DC / GT Last Valid Read Read History If no response from customer, submit at end of Read Window as a COR Ideal: Read submitted to DC is acceptable to Customer and Old Supplier Forecast Of acceptable CoS Read OLD SUPPLIER Forecast Of acceptable CoS Read Requests CoS Read and notifies customer of estimate from OS as backstop During Core Data TransferSlide 9:Accurate Billing Accounts:Use the Agreed Read for CoS Billing
Slide 10:Accurate Billing Accounts:Use the Agreed Read for CoS Billing
NEW SUPPLIER NEW DC / GT OLD SUPPLIER Forecast Read from Old Supplier COR validated against Old Suppliers Forecast Read OR (For Billing) Via Backstop Read Flow What? Provide a backstop for delayed D0086 / U03 Validates CoS Reads NEW SUPPLIER D0086 / U03 eventually arrives Reconcile any difference between Billing and Settlements If no D0086/U03 received after, say SSD+20: Ideal: Seamless Billing not compromised by delayed D0086 / U03
Slide 11:The Effect (benefits not yet quantified)
Sale Register Appoint Agents Submit COS Read Set up Account Bill Reads Not Validated Contract Not Actionable Cancellation Rejection Objection / Reconfirmation (inc Coops) ET Delays Related Meters MPAS/GT Enquiries Meter Type Error (e.g. CR/Ppt) Appointment errors / Rejections Meter Read history not received Asset information Not recd Incorrect Appointments (Objection) Mismatch between history / asset details Opening Read processing Account Set-Up Issues Reads Not Utilised No Opening / Closing Read received Double-billing Disputed Readings Unsupported Meters KEY Process Area Likely to be improved Unlikely to be improved