Joint Theft Reporting Review (from meeting 1st March 2019) Working Group Action Updates (from meeting 1st March 2019)

Action 1 Question: Clarify if the AQ is amended following a consumption adjustment RGMA Submission Received Incrementing Reads Provided Will the AQ increase Comments No AQ will remain static and/or superficially low Yes AQ will re-calculate in line with gas used Correct Off State read provided AQ will remain static and/or superficially low however, will build overtime depending on future read submissions

TOG Scenario Theft of gas investigation logged by Shipper A Contact was closed confirming it was a valid TOG. The theft period outlined in initial contact was 13/06/2006 – 16/05/2018 Shipper provided consumption in cubic metres yet the asset on site is measuring in cubic feet Xoserve has checked the read history and no meter exchange was present or read provided for 16/05/2018. The reading has remained the same since 2014 through to the last reading recorded in April 2018 (15 non-incremental reads all provided by a meter reader). The AQ for this site has remained at 1kWh for 3 years An apportioned billing template was compiled by Xoserve following Shipper approval 03/01/14 – 04/04/2018 – 80,959 cubic feet It was also recorded from the engineer’s report that a substitute meter was found however, no RGMA flow present on system.

Scenario Impacts Our findings are ….. The asset data held on our supply point register implies that it is incorrect Read history for the supply meter point inaccurate as close out read of old asset not provided The AQ for the supply meter point has remained superficially low for 12 years impacting UIG The AQ will not change or re-calculate until either a read is loaded or RGMA flow submitted Timescales to resolve the Contact were increased due to inaccurate data initially being provided

TOG Conclusion In this specific scenario it was evident the AQ remained unchanged at 1 kWh, when in fact it should have been 5,875 kWh based on the volume of gas that was stolen. When scenarios such as these present themselves the AQ should be updated by Shippers via an AQ correction file (.AQI) in order to reflect the appropriate gas usage on site. This will also reduce the risk of future reads rejecting for breaching tolerance levels as the AQ is low It will also help reduce the impacts contributing to Unidentified Gas

Can the 80 day auto closure deadline be extended? Action 2 Question : Can the 80 day auto closure deadline be extended? As a result of this request we conducted some analysis in relation to RFI requests auto closing after 80 days The volume of TOG Contacts Xoserve received during a 6 month period is circa 4,600 Of the 4,600, 605 (13%) Contacts auto closed due to the RFI request being open for greater than 80 days Over the last 6 months, 73 Contacts with the same MPRN had been re-raised.

TOG Lifecycle Theft of Gas Contact Raised by Shipper/ Network via CMS System determines if investigation complete. If not complete will direct contact to Network or Shipper based on type of theft Shipper or Network have 80 BDs to investigate theft and provide Xoserve with correct theft period and volume. If no response contact auto closes Xoserve then validates the theft information. If validations fail it will be referred to appropriate Shipper/Network. These can remain open indefinitely pending a response If validations pass validation Xoserve will prepare the billing template and issue for invoicing Invoicing validates billing template and produces appropriate invoice to Shipper and back up data to Networks If the billing template fails validation due to tolerance breaches. This is referred back to Shipper Shipper either acknowledges or provides revised information Xoserve validates and re-issues billing template for invoicing