1
MOD455s
9th October 2013
David Addison / Steve Deery
2
Agenda
• Scope
• Scenarios
• Illustrative Timescales
• Potential Charging Methodology
• Root Cause Workgroup
3
• 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
Draft Principles of 455s
Scope
4
Scenarios
5
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.
Gas Safety Regulations
• Pre 455s Anomalies – 260 per month
• Post 455s Anomalies – No change anticipated
User removes asset & submits
RGMA flow
Network carry out Gas Safety checks
9-12mths
Safety check complete
Notify Xoserve
Meter Found On Site?
Notify UserYes
No
As Is
MOD455s Triggered
To Be
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.
• Pre 455s Anomalies – 300 per month
• Post 455s Anomalies – No change anticipated
Pre-Note Triggered
Notification Triggered
Notify User
Read Entered By User?
As Is
20 Days
Read Entered By MRA?
No 20 Days
Auto close20 DaysNotify Xoserve
(MEX / Incorrect Asset)
No
MOD455s Triggered
To Be
80 Days
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.
• Pre 455s Anomalies – 90 per month
• Post 455s Anomalies – No change anticipated
User raises service status challenge
If challenge is to change status to
Dead, SV is required
Anomaly found?
YesTransporter Notifies
XoserveXoserve Notify
User
As Is
MOD455s Triggered
To Be
NB - Xoserve set a Meter Point from Capped/Clamped to Live on the Users request – without the need for a site visit.
8
Primes and Sub-Deducts
• Pre 455s Average Anomalies – 200 per month
• Post 455s Average Anomalies – anticipated 0 per month
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.
PSA REQM-1
Read ObtainedReads
entered?
Notify User (MEX / Incorrect Asset)
Autoclose
1Mth 1Mth
No
20 Days
As Is
MOD455s Triggered
To Be
9
Illustrative Timescales
10
Current Timescales For Asset UpdatesData passedAsset - Meter, Converter, DataloggerModelManufactureSerial NumbersYr of ManufactureMetric / ImperialRegister DialsReading IndexesRead Factors
MAM
XoserveShipper
Supplier
C&D Exception Flows
S&MC&D
+2 business days
+2 business days
+2 business days
ONJOB
ONJOB
ONJOB
C&D Flows
CDJOB
ONUPD
ONUPD
ONUPD
C&D Notn.
11
Potential Timescales For Asset Updates
MAM
Shipper
Supplier
Xoserve
S&MC&D
+6 business days (UNC 3.2.15)
[+2] business days
[+2] business days
[+10] business Days
+2 business days
+2 business days
+2 business days
Suggest Code proposes [20] days from provision by Transporter to User
Timescales for Discussion
12
• 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”“Same data” to be defined
Potential Charging Methodology
13
• 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.
Root Cause Workgroup