1 / 13

MOD455s 9th October 2013

MOD455s 9th October 2013. David Addison / Steve Deery. Agenda. Scope Scenarios Illustrative Timescales Potential Charging Methodology Root Cause Workgroup. Scope. Draft Principles of 455s.

suchin
Télécharger la présentation

MOD455s 9th October 2013

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. MOD455s9th October 2013 David Addison / Steve Deery

  2. Agenda • Scope • Scenarios • Illustrative Timescales • Potential Charging Methodology • Root Cause Workgroup

  3. Scope Draft Principles of 455s • Will be applied when the Transporter becomes aware of different asset details to those held on UK Link – which may include a site visit. • Relevant secondary sources will be used (e.g. UKLink, C&D store, etc.) where applicable to further support findings. • Triggers can occur during the investigation of a number of existing processes (scenarios). • Further triggers may be identified

  4. Scenarios

  5. Gas Safety Regulations Instigated when a User has removed a meter and/or isolated a supply, a Gas Safety visit is carried out by the Transporter after 12 months and this has identified a live meter on site using gas. • Pre 455s Anomalies – 260 per month • Post 455s Anomalies – No change anticipated

  6. Must Read If no read has been received within 4 months for monthly read sites, the must read process will initiate. Monthly read sites are pre-noted to enable Users to obtain a read themselves. Non monthly Large Supply Point sites will be passed directly to the MRA. 80 Days • Pre 455s Anomalies – 300 per month • Post 455s Anomalies – No change anticipated

  7. Isolations A challenge to the status of a Meter Point held on UKLink. If the request is to set the Meter Point Status to Dead (DE), the Transporter will attend the site to ensure the service is not capable of flowing gas. Any anomalies found are reported back to Xoserve. NB - Xoserve set a Meter Point from Capped/Clamped to Live on the Users request – without the need for a site visit. • Pre 455s Anomalies – 90 per month • Post 455s Anomalies – No change anticipated

  8. Primesand Sub-Deducts The Transporter will use reasonable endeavours to procure a meter reading where there is a Prime and Sub configuration. On occasion when this has not been possible (due to an asset discrepancy), a notification will be issued to Users who are then required to update the meter information. • Pre 455s Average Anomalies – 200 per month • Post 455s Average Anomalies – anticipated 0 per month

  9. Illustrative Timescales

  10. Current Timescales For Asset Updates Data passed Asset - Meter, Converter, Datalogger Model Manufacture Serial Numbers Yr of Manufacture Metric / Imperial Register Dials Reading Indexes Read Factors ONUPD +2 business days ONUPD ONJOB Xoserve S&M +2 business days C&D ONUPD ONJOB CDJOB Shipper +2 business days ONJOB Supplier C&D Notn. C&D Flows MAM C&D Exception Flows

  11. Xoserve S&M C&D Potential Timescales For Asset Updates Timescales for Discussion +2 business days +2 business days Shipper +2 business days +6 business days (UNC 3.2.15) Supplier Suggest Code proposes [20] days from provision by Transporter to User [+2] business days MAM [+2] business days [+10] business Days

  12. Potential Charging Methodology • Trigger points in the process where the Transporter would look to charge:- 1) At the point of conclusion of Transporter investigation (following ‘no response’ from User where Transporters consider an asset update is required. 2) Where the Transporter updates asset data on behalf of the User.* • * Discussion point: • Should a charge be incurred where the User updates an asset with the same data that was provided by the Transporter? “Same data” to be defined

  13. Root Cause Workgroup • Recommended to SPAA that they facilitate this Workgroup due to these arrangements being covered under SPAA Governance. • The Workgroup was asked to consider root cause/s – Xoserve can contribute. • Does not prevent 455s progression. • Purpose/aims need to be agreed by the Workgroup.

More Related