DCA timeline and ROM Overview

1. DCA timeline and ROM Overview 12 October 2012

2. Smart Metering Indicative Timeline Modification (MOD) 0430 raised ( June ‘12) EVS 2646 received / ROM commenced (May '12) Q1 ’2012 Q1 2013 Evaluation Service (EVS) 2528 received / Rough Order of Magnitude ROM commenced (Jan '12) Evaluation 2528 Completed. ROM produced (May ’12) Evaluation 2646 Completed. ROM produced (Sept ‘12) MOD 0430 re-submitted / Request for DCA re-submitted (2528 / 2646) Change Identified – Request for DCA (2528) (Sept ‘12) Project Start-Up (Sept ‘12) Initial Assessment of timescales / costs (Oct ‘12) Detailed Assessment of timescales / costs DCA delivered

3. Outline ROM Solution • Assumes full Uk Link portfolio of required data items on day one. • Includes daily delta updates. • Receipt processing and response of amended or new inputs to shippers and DCC. • Data submission by suppliers via shippers. • Data provision by Xoserve in support of CoS processes. • Significant re-design of the interface will mean that it will be easier to define and introduce new industry roles in the future.

4. ROM Analysis • Implementation timescales are estimated to be between 54 and 62 weeks. • An additional piece of analysis will be required once the DCC has been appointed. • DCC Gateway solution has not yet been defined. • It is assumed that there will be new flows for data collection. • Information which is communicated to the industry as part of CoS will be in new record types within existing flows. • The meter mech code to be utilised. • New values will be utilised to capture the meter tech spec. (e.g. ADM, SMETS1, SMETS2 & SMETS3.) • Short versions of tech spec codes req’d due to field size imitations.

5. Data Item issues • MPRN • All meter points (Including any dead or extinct MPRNs) will be included in the extract. • Unique Sites MPRNs will not be included in the extract. • Supplier • Current history of supplier lies at supply point level. This will be mapped across to meter points for the extract. • Supplier EFD • This will be in line with current confirmation • SUN file. (Unless industry curtail its use.) • AD Hoc bulk update. (Used typically on terminations.) • MAM ID & EFD • Current system holds new and current MAM. History not available • Meter Type • Solution assumes use of meter mech code.

6. Data Item Issues Cont’d • SMSO & EFD • Assumed to be a 3 character abbreviation that should be unique within gas & electricity industry. • EFD will be provided by supplier via shipper. • DCC Service Flag • This will be a unique separate field. • Input will be restricted to DCC only. • IHD Install Status • IHD will be held as an attribute of the premise. • Unsure whether or not IHD will be a new asset class. • IHD is costed outside of the RGMA flows. • Concerns from DECC regarding DCC inventory • UPRN • A field will be provided, although if this is not mandated as compulsory it is unsure how this will be populated or validated.

7. Data Item Issues Cont’d • GT identifier and EFD • GTs are geographically distinct entities • However iGTs are not • iGTs do buy and sell specific CSEPS • An EFD will also be required • Registration System identifier required • DECC requirement to show source of registration database • Installing Supplier • Required for Foundation stage especially at CoS

8. Cost Factors • Analysis and implementation of comms infrastructure to iGTs not included. • Further clarity on DCC gateway req’d to understand costs in this area. • Further work required to decide how history will be displayed to DCC. • Neither costs or timescales for industry testing and trialling are included. • Does not include infrastructure costs for Xoserve to deal with increased volumes of:- • Meter Asset updates • Meter Read submissions • Costs for implementing a fully integrated UPRN solution are included separately. • Does not include the facility for DCC to update DCC service flag on iGT systems. • Any changes to iGT systems not included. • Any supplier shipper costs not included. The ROM provides an enabler not a solution.