1

Smart Metering Portfolio DCC Day 1

SMIP Focus Group – DCC Day 1 Update & Shipper Design Overview

Thursday 05th September 2013

Welcome to Xoserve Ltd at 31 Homer Road

• No planned Fire Alarm today

• Toilets are located by the Staircase

• Workshop is planned to finish by 15.00

• Refreshments will be available at 10.00 & 1400 with lunch at 1200

2

3

Agenda

• Introductions

• Action Review

• Shipper File Formats

• Update on UK Link, SPAA and SEG on June 14 Implementation date

• Proposed iGT File Formats

• Exchange of Data between iGT’s & Shippers

• Detailed Cost Assessment

• High Level Plan/Governance – Delivery

• Expectations for Testing – Initial Discussion

4

Action Review

• Outstanding Smart Metering Portfolio Focus Group actions for review:

Microsoft Excel 97-2003 Worksheet

5

UK Link Committee

Representations received from 3 parties after presenting the UK Link hierarchies and file formats at the August 13 meeting. These have been responded to by Xoserve and the implementation plan will be discussed at the September 13 UK Link Committee meeting to agree the 27th June 14 implementation date.

SPAA Expert Group

RGMA change has been discussed further at July & August 13 SEG meetings. A revised change pack (final) has been distributed (V2). Final change is in progress to be agreed for a June 14 implementation.

Update from UKLC & SPAA Expert Group - June 14 Imp Date

6 File Format and HierarchiesFor Approval at September 2013 UK Link Committee Meeting

Existing Files Change Summary DCC Day-1 Data Items Requirement Mapping

ONJOB & ONUPD1. IHD Install Status through DATASET_GROUP_ASSET

17. IHD Install Status

FR01 – Data items from Shippers to Xoserve

GEA Supplier Update Notification process including Supplier EFD

GEO Response to Supplier Update Notification process

SUN & RSN Existing SUN and RSN file will be decommissioned

NRF & NMRIntroduce new record type RT_S98_Smart_Data under RT_S75_Meter_Point

05. Network Owner ID

06. Network Owner ID EFD

13. SMS Operating Entity ID

14. SMS Operating Entity EFD

15 .DCC Service Flag

16. DCC Service Flag EFD

17. IHD Install Status

18. First SMETS Installation Date

19. UPRN

FR11 – Data items from Xoserve to Shippers

CFR

1. Introduce new record type RT_S98_Smart_Data under RT_S75_Meter_Point

2. Introduce new record type RT_S98_Smart_Data under RT_S77_Withdrawal_Meter_Point

TRF1. Introduce new record type RT_S98_Smart_Data under RT_S75_Meter_Point

MRI & PAC

1. Introduce new record type RT_S98_Smart_Data under RT_U06_Meter_Read_Instructions

2. Introduce new record type RT_S98_Smart_Data under RT_N90_ASSET_DETAILS

DCC Day 1 file formats.zip

7

iGT File Formats – Part 1

Proposed iGT File Format

Consideration has been given to the discussions being held about the iGT Communication Mechanism (DTN or IX). The iGT

File Format has been designed to be compliant to SPA UK Link File Formats.

The recommended iGT File Format is proposed to be a single record with a Header and Footer record (See Slide 10).

This ensures that the changes for iGT’s DCC Day 1 solution is cost effective in advance of the changes due to be delivered

under the UKL Programme and the introduction of Single Service Provision.

8

iGT File Formats – Part 2

Issues with making the iGT File Format fully RGMA compliant with record datasets is:

1. Would be a complex design in advance of Single Service Provision that would require significant changes to iGT,

GT and potentially Shipper systems which is not cost effective to all participants.

2. Making RGMA dataset compliant will impact on the Shipper File Format designs being agreed at UKLC.

3. Would require changes through SPAA.

4. Modifying the existing datasets to add additional attributes will impact Shipper file formats.

5. Existing dataset have mandatory attributes which are not related with iGT’s data extract (eg - TRANS_TYPE,

DATA_UPDATE_CODE in TRANS dataset).

6. Only some of the attributes in the existing datasets will be relevant to iGT’s and other attributes in the dataset will be

blank or have to be ignored. Eg:- METER dataset contains 11 attributes and only one (MME_Code) is relevant for

iGT flows.

7. MKPRT dataset will be multiple for each entity. Eg:- separate dataset for SMSO, Supplier, Network, MAM.

9

iGT File Formats – Part 3 - Hierarchies

iGT Draft Hierarchies – Inbound and Outbound

iGT- Inbound File (IGT) Hierarchy v0.1.pdf

iGT- Outbound File (XID) Hierarchy v0.1.pdf

10

iGT File Formats – Part 4 – File Formats

iGT Draft File Formats – Inbound and Outbound

iGT - Inbound File (IGT) Structure v0.1.pdf iGT - Outbound File (XID) Structure v0.1.pdf

RT_xxx (IGT) v0.1.pdfRT_yyy (XID) v0.1.pdf

11

Exchange of Data Between Shippers & iGT’s

The following diagram shows the iGT UNC Modification 047 SMIP Process and Flows of data between Shippers and

iGT’s (SMU file) as per the ancillary document to support the modification.

Areas of discussion:

1.Timescales for iGT development of SMU files

2.Testing windows for Shippers to test new SMU files

3.Implementation Timescales – Xoserve assume that final implementation date for UNC Modification 047 is targeted

to be 27th June 2014 to align to the GT Registration System changes being agreed at UKLC?

iGT047+SMIP Process Diagram.pdf

12

Plan and Governance

UK Link file formats issued to UK Link Committee (09/08/13)

UK Link file formats representations close out (23/08/13)

UK Link file formats re-issued (30/08/13)

UK Link Committee meeting (12/09/13)

Industry Testing & Trialling (April ’14)

Q3 2013 Q3 2014

Smart Metering DCC Day 1 Implementation (27th June ‘14)* Contingency implementation date is 11/07/13

Industry Testing & Trialling preparation activities (approach & scope) (Feb ’14)

13

Expectations for Testing

Xoserve will be undertaking detailed testing of all DCC Day 1 changes. As part of the Project Plan there is a 4 week

User Trials period to allow all external parties (Shippers, iGT’s and the DSP) to participate in testing developed

interface files to meet the signed off design (hierarchies and file formats). Xoserve will be documenting a full Testing

Strategy to define the overall testing required and this will include External User Trials. External User Trails are not

mandatory for parties to take part in but considering the scale of change and importance it is expected that a majority

of parties would want to.

1.What external organisations are planning to take part in External User Trials?

2.Who should be engaged from Shipper and iGT parties?

3.Suggestion is that a separate Group is set up to work through testing timescales and scope?

4.Thoughts on high level scope of External Trials testing (GT Registration changes)?

14

Next Steps

• Approve UK Link File Format changes at September 13 UK Link Committee

• SPAA (CP 13/231) RGMA change for DCC Day 1 changes to be approved for a June 14 implementation.

• Identify any other SPAA changes required to support DCC Day 1 delivery (eg new iGT File Formats, changes to DES etc)

• Testing Strategy workshop to be planned with External Stakeholders to agree scope and approach (eg file testing, DES Screen testing etc)

• Detailed planning of User Trails phase to be completed

• Engagement with DSP appointee (CGI) to commence shortly