fttp industry process group - openreach · 12/01/2009 · industry sub working group. 6. th . ......

NGA ProductsIndustry Sub Working Group

6th November 2008, BT Centre, London

www.openreach.co.uk/orpg/products/nga/nga.do2

Disclaimer•

It should be noted that the proposals for the products outlined in this slide-pack represent Openreach’s current view of those products at the time of publication. These proposals may change through further development and feedback.

•

The purpose of this slide-pack is to provide additional information to support CP development initiatives. It does not represent a finalised definition/specification of the products. Any developments carried out by CPs based on the contents of this slide-pack are entirely at the CP’s own risk.

•

©

British Telecommunications plc 2008


Agenda•

Welcome

•

Focus on FTTC–

Network and Intermediate Agent Solution

–

Home Environment–

Migration Processes

–

Consultation update

•

DEA Consultation Update

•

Close and Review

Focus on FTTC Network Solution

Chris Clough


GEA – Connectivity Handover Port (illustration)

Openreach HandoverPoint

Existing Products

BES Circuit

ONBS /EBD circuit

Optical interfaces –

GE(1000BaseLX set to Auto-Negotiate)

New orExisting Cable

CP Flexibility point

CP Location in Building

CPRemote

nonBT Building

CPOutside

BT Building

CPRemotedifferent

BT Building

BES Circuit

BT Flexibility point

CPAggregationEquipment

Cable LinkInternal Variant 2

Cable Link External / Internal variant 3

Connectivity Handover Port

CHP connects, in building only, to flexibility point or CP equipment


VLAN Management at CHP

•

Openreach will allocate the tag value–

Is this a significant issue?

•

Single tagged handover only in current design–

Are there strong requirements for double tagged handover?–

Network -

CHP supports single tagging and double tagging on the same CHP ie CVLANs only, CVLANs within SVLANs only, or both.

–

Is the following a useable minimum set for Pilot?•

Order CHP with a

single

SVLAN•

No shaping of the SVLAN (other than to the CHP size)•

All Data Port orders on the CHP will be supplied on the SVLAN (no need to specify SVLAN separately on Data Port order)

–

Full requirements –

is this correct•

Multiple SVLANs per CHP. CP options to specify:–

Size of each SVLAN –

no rules on sum of SVLAN sizes. Would be used to shape upstream (in addition to shaping to CHP size)

–

Tag value for SVLAN•

CP specifies whether to use an existing SVLAN and if so which, to use for each Data Port:–

Provide / Convert / Transfer–

Modify


Intermediate Agent insertion - proposalCP able to select value for remoteID

in Intermediate Agent

•

Provide–

Value applied as part of the port configuration ahead of service

connection by engineer.

•

Transfer (change of CP for the Data Port + new service id)

–

Transfer requires change of CVLAN (new Handover Port)–

remoteID

value change applied as close as possible to CVLAN mapping change–

EU service down (CP dependent) while CVLAN remoteID

values are not aligned.

•

Modify (change of remoteID

value for same Data Port)

–

remoteID

value change applied as close as possible to CVLAN mapping / throughput rate change(s) so that new service appears in one change as far as EU is concerned (depends on CP config as well)

–

Assumes that CP will support old and new remoteID

in parallel for the day of the change


GEA Data Port Ordering - Peak / Upstream

•

All new GEA Data Ports will be Provided as:–

Peak = 20M, Assured = 10M, Upstream = 2M–

Accept order only if line qual expects highly likely to operate at >=20M–

Investigating whether possible to offer other values (30 or 40Mbit/s) on provision

•

Line will stabilise over a period–

Report line rate to CP via ANCP –

current proposal•

ANCP version supports reporting of speed values (may not be possible for the pilot)•

CPs expected to track future changes as vendors upgrade to standard ANCP.•

CPs can use values to shape their downstream traffic–

DSLAM estimates Max Achievable Line Rate (MALR).

•

Once stabilisation period complete, CP can then Modify:–

Downstream options for “peak”/”assured”

(assured based on peak)•

A Peak value can only be ordered if d/s MALR is higher than ordered value•

Options of 20/10, 30/15 or 40/20–

Upstream can be set separately –

not driven from peak downstream•

An Upstream value can only be ordered if u/s MALR is higher than

ordered value•

Options of–

2 / 5 for 20/10–

2 / 5 / 10 for 30/15–

2 / 5 / 10 / 15 for 40/20


Lines where stable line rate < Peak or < Upstream

•

Lines can stabilise below the ordered Peak and/or Upstream

•

No pro-active Openreach activity –

CP needs to report as a fault

•

Accept slow speed fault if line rate below Peak and/or Upstream–

Attempt to resolve–

If can’t resolve, then CP should have option to downgrade•

Ops should place this order and waive charges.•

No min term reset–

CP can choose to remain on service -

eg for 30M peak but line at 29.5M•

Still better than 20M which is next level down•

Assured is 15M rather than 10M + allows upstream up to 10M rather than 5M–

For discussion

•

Is the speed criteria based on average line rate over a period or instantaneous values?

•

Should Openreach set a slow speed threshold value eg 80% of peak/upstream?•

Set FTR where CP agrees to keep a line incapable of sustaining ordered peak/upstream?


QoS and traffic shaping

Modem

L2S/OLT

Modem

CP

CP

DSLAM

DownstreamVLAN Based Policing to

Peak RateScheduling based on CP .1p

values

UpstreamShape/Police End Users to port bandwidth

Optional IA insertion for PPPoE or Option 82 for DHCP per VLAN (default is no insertion). CP to specify Remote ID (Under investigation for Pilot)

Map End Users to CP specified Handover port

CP traffic 802.1p marked (per EU):•

802.1p = ‘3,2,1’

= “Should Not Drop”•

802.1p = ‘0’

= “Can Drop”•

802.1p = ‘7,6,5,4’

re-marked to ‘3’

Traffic marking is optional. Unmarked traffic treated as “can drop”.

Handover Port Options:•

GE (set to Auto-Negotiate)•

Single Tagged Handover•

Specify outermost tag Ethertype:•

S VLAN = 0x88-A8 •

C VLAN = 0x81-00 (default)•

Max frame size of 1600 bytes

Customer 10/100BaseT interface set to Auto-

Negotiate. Port based service to EU

VLAN Based Policing to Upstream speed


All “can drop” “should not drop”

> Assured

AND

rest = “can drop”

All “should

not drop”

QoS – Target / Pilot differences

Peak

Assured

Target & Pilot Target0

PilotTarget & Pilot

“should not drop”

-

passed“should not drop”

–

possibly dropped“can drop”

-

passed“can drop”

–

possibly dropped

•

Target: .1p bits -

0 = “can drop”, 1-3 = “should not drop, 4-7 will be re-marked to 3

•

Pilot: –

Under congestion between OHP and DSLAM, traffic drop will ignore

“can drop”

/ “should not drop”

marking

However, congestion occurs only when demand to a DSLAM >1G. Expected to be very, very, rare given likely traffic profiles and EU volumes

–

Markings 4-7 will not be re-marked

May impact ability to get modem management traffic through, otherwise no impact

“should not drop”

< Assured

AND

rest = “can drop”

Target Pilot

Home Environment

Chris Clough / Simon Fisher


Engineering visit process (outside premises)•

Engineer rings EU prior to starting work on cabinet.–

If no reply, engineer visits premises. If nobody present to provide access, then no work is done at the

cabinet and the provision is suspended and CP is requested to book a new appointment via KCI.

–

Otherwise, work goes ahead.–

Note –

if engineer misses the appointment, then the CP will be contacted via operations to request a new appointment

•

Engineer performs jumpering at the cabinet–

Short outage on baseband service (minutes). Looking at ways of no break jumpering.–

Incompatible products no longer work (eg SMPF)


Engineering visit process (at premises)•

2 hours work within connection charge–

additional time will not be charged within the Pilot

•

NTE5 will be fitted if necessary–

NTE5 essential in order to allow use of VDSL SSFP–

Process for external NTEs

being worked on

•

3m demarcation–

Expect to fit NTE in line with existing 3m rule where suitable power outlet available–

3m rule will be waived where necessary to access mains power for

VDSL2 modem

•

Test service–

Engineer will power up modem and check it trains up correctly at

expected speed–

Connect to Openreach test service to show service works•

Supported via switching service at the OHP, close to the Handover Port.•

Is there a reliable way of testing into CP service? Maybe via test account?

•

Internal wiring–

Within the Pilot, if after fitting the SSFP there are still service issues resulting from internal wiring, engineer will attempt to fix

•

D side wiring–

If there are problems with D-side wiring engineer will attempt to fix


Fibre to the Cabinet

NGA Products TWG


GEA FTTCab platform

Assumptions –

•

Overlay infrastructure deployment

•

Voice and Legacy services supplied from the exchange.

•

Premium Broadband product provided as GEA over FTTCab

D-Side Copper

ESHOCP1

CPn

Direct fibre

Hand-Over Node

Multiple GigE links

VDSL2 modem

End User Premises

GEA Data PortNTE 5 & SSFP

Baseband Voice & Legacy Services

Existing Copper E-side Network from DLE

240Vac

PCPDSLAM(VDSL2)

GEA Premium Product


End User environmentNetwork termination unit -•

Active NTU containing VDSL2 modem (matched to DSLAM in early days)

•

Presenting Ethernet interfaces to End User (similar to FTTP ONT)

• One CP model

• Powering –

230Vac mains adapter (Fat plug)

Home wiring –•

Service Specific Front Plate required to isolate Home Wiring

•

Engineer visit will be required in early stages (self install desirable)

•

Openreach may offer additional products for Home Wiring beyond the NTU.

FTTP ONT

NTE5 VDSL2 Service Specific Filter Plate


Cabinet Deployment Options

DSLAM

Power Supply

Batteries

splitters

Tie Cable PCP

DSLAM

Power Supply

Batteries

splitters

Tie Cable

PCP

mini DSLAMsplitters

PSU

PCPTie Cable

mini DSLAMsplitters

PSU

PCP

DSLAM

Power Supply

Batteries

DSLAM

Power Supply

Batteries

PCP

DSLAM

splitters

PSU

Joint Box

Tie CableDSLAM

splitters

PSU

Joint Box

Tie Cable

Stand-alone Cabinet Re-shell or re-build PCP

DSLAM Top boxUnderground DSLAM

The FTTC architecture is based on VDSL2 in a range of housings located at the site of the existing PCPs. PCP sizes can vary but cabinets serving an average of 400 lines can be expected (with a range between 48 and 1100). For an overlay deployment it is expected that remote active cabinet would support a service take-up ranging from 10% to 40% of working lines.

Day 1 options:Standalone DSLAM cabinet A cabinet for deployment alongside an existing PCP

Re-shell (&/or re-build PCP) A single cabinet that houses both the existing E-

side and D-side connector fields and the VDSL2 DSLAM, for deployment in situations such as poor PCP condition or insufficient space.

DSLAM Top Box An extension enclosure that replaces the roof section of an existing PCP and houses a VDSL2 DSLAM.

Post Day 1 options:

Underground Remote DSLAM A waterproof housing (known as a VDSL2 Brick) placed in the cable joint box to serve a small number of end users.

User Stories / Development Priorities

Toby Gibbard


User Story – Function & Format•

Express customer requirement or business function.

•

Format:–

As a <role>

–

I want to <description of requirement or function>–

So that I can <description of customer or business objective>

•

The User Story expresses the customer need that typically does not evolve over time, but remains constant. The Story does not describe solution.

•

Story has associated acceptance criteria. These do evolve over time, typically becoming more stringent, to drive shape and maturity of solution.

•

Stories are not detailed requirements.. rather is a ‘promise for a conversation’


Definitions•

We Scope a set of Stories as candidates for a Release.

•

We chop the releases into development “Sprints”–

2 weeks of intense coding and testing.

•

The “stories”

scoped into a Sprint are fully defined–

As part of a “design iteration”–

2 weeks of intense design activity which bottom all aspects of the solution•

Including tests, and costs!–

Defined stories are COMMITTED into Sprints.

•

As coding is done it is tested right away (Continuous Integration Test)

•

As stories pass the CIT, they go into e2e test

•

Why is this good:–

We only work on the top priorities–

We can modify those priorities as we learn–

We test ALL THE TIME–

E2E test starts very early on–

We involve “everyone”

in “everything”

(Design, Development, Test)–

Progress is tangible–

Sprints can in principle deliver to field


Scope

User Story & agile delivery approach covers…

•

Product & Product Features

•

E2e Service Delivery –

L2C, T2R

•

E2e Geographical Capacity

www.openreach.co.uk/orpg/products/nga/nga.do23Slide 23

Stories, and Scope….

FTTC

Tech Trial

“alpha Trial”

Pilot

Volume--------------

----------------

-------

----------story 1

story a

story Astory 2

etc

etcstory 3story 4 story 5story 6story 7story 8story 9-----------story 10story 11story 12

List of prioritised

stories for trial(by benefit)

View of “minimum”

acceptable scope at iteration1

Stories scoped for

design iteration 1



FTTC

Tech Trial

“alpha Trial”

Pilot

Volume--------------

----------------

-------

----------story 1

story a

story Astory 2

etc

etcstory 3story 4 story 5story 6story 7story 8story 9-----------story 10story 11story 12

Stories scoped for

development in Sprint 1



FTTC

Tech Trial

“alpha Trial”

Pilot

Volume--------------

----------------

-------

----------story 1

story a

story Astory 2

etc

etcstory 3story 9 story 5story aaStory 6story 5story 8story 9-----------story 4story 10story 11story 12

Stories scoped for

development in Sprint 1

New story added!!

Story priority changed

Stories scoped for design in iteration

2So we build in iterations toThe minimum needed.But we expect that minimumTo be a “different”

one than

the one we knew at the start


Release 2 Scoping and Sign off points

Agreed list of candidate e2e stories for R2.

Agreed list of Stories

for Design 1

Agreed list of “designed”

Stories for Sprint 1 dev.

Agreed list of stories for Design 2

Agreed stories for Sp2, Agreed stories for Design iteration 3(Sp1 is now “coded”)

Code into e2e test ASSOON as CITdRelease Tested by jointTeam (inc. CPs!)Signed off.


Initial Customer Experience User Story Sprint Mapping (not a delivery commitment)

Rank Customer Experience User Story SprintMapping

1 Customer Establishment 1

2 Provide Connectivity Product 1

3 Order SVLANs 1

4 Provide GEA Product with a existing WLR2 Voice Product 1

5 Provide GEA Product with a existing BTR-C Voice Product 1

6 Provide GEA Product with a existing MPF Product (Voice Only) 1

7 Provide GEA Product with a existing WLR3 Voice Product 1

8 Migration from SMPF with a existing WLR2 Voice Product to GEA 1

9 Migration from SMPF with a existing BTR-C Voice Product to GEA 1

10 Migration from MPF to GEA with MPF voice (where existing supports both Voice & BB) 1

11 Migration from SMPF with a existing WLR3 Voice Product to GEA 1

12 New Trouble Report 1

13 Assured Service Quality 1

14 Cease of GEA Services 1

15 Transfer active GEA services 1

16 Modify GEA Service Bandwidth 1

17 External User Reports 1

18 Cancel Request for In-flight Order 1

Sprint 1



19 Migration from GEA to SMPF with WLR2 Voice Product 2

20 Amend Request for In-Flight Order 2

21 Amend Trouble Report 2

22 Cancel Trouble Report 2

23 Order and Activity Monitoring/Tracker 2

24 Fault and Activity Monitoring/Tracker 2

25 Migration from GEA with MPF voice to MPF (Voice and Data) 2

26 Simultaneous Provide of GEA and WLR3 Product 2

27 Migration from GEA to SMPF with WLR3 Voice Product 2

28 Expedited Provision 2

29 Amend Order Details (Reseller & Handover) 2

30 Migration from GEA to SMPF with BTR-C Voice Product 2

Sprint 2




31 Managed Cease triggered by Cessation of WLR2 Service 3

32 Managed Cease triggered by Cessation of MPF Service 3

33 Managed Cease triggered by Cessation of BTR-C Service 3

34 Managed Cease triggered by Cessation of WLR3 Service 3

35 Cancel Managed Cease 3

36 Maintain Association of WLR3, WLR2 or BTR-C to GEA services 3

37 Wider Service Availability (Plan & Build) 3

38 Wider Service Availability (Handover Points) 3

39 Wider Service Availability (Backhaul Capacity) 3

40 Modify Care Level 3

41 Intermediate Agent 3

42 Modify Intermediate Agent 3

Sprint 3




43 Notify Outages on Planned Engineering Work 4

44 Notify Outages on Major Service Outages 4

45 Fault History Report 4

46 Special Fault Investigation Product 4

47 GEA fault notification to WLR3 Voice product 4

48 GEA fault notification to WLR3 Voice product 4

49 GEA fault notification to BTR-C Voice product 4

50 GEA fault notification to MPF Voice product 4

51 Managed Cease of Connectivity Product 4

52 Shift of End 4

53 Modify SVLANs 4

54 MIS Reports -

Internal Reporting 4

Sprint 4




55 Complaints and Escalations 5

56 Throughput Monitoring 5

57 Number Portability 5

58 SLG Payments 5

? ? TBC

Sprint 5



Summary

•

Overall Ranking has been based on CP input

•

Sprint 1 (Design) scope has been locked (to make progress on some of the essential requirements)

•

Ongoing opportunity for committed CPs

to influence scope of Sprints 2-5 and beyond..

FTTC/GEA Process Overview

Introducing the CP Interface

Andrew Sheppard


Introduction

•

This is a very high level overview of the process around the main CP interface points–

More detailed walk-throughs

will be User Story specific

•

Two main threads are:–

Generic Lead to Cash

–

Trouble to Resolve

•

This presentation will not cover anything relating to the interconnect and backhaul products –

These are intended to be existing portfolio items

Lead to Cash


Generic Lead to Cash Process - Overview

Line Check

BookAppointment

PlaceOrder

KCIUpdates

Ordercomplete

Dialogue Services Plan is to build on existing

dialogue services. Portal version

will definitely be available.

Investigating whether it will be

possible to also make

available B2B versions

Order Placement New order types will work along existing lines.

Improved CP Portal journey was demonstrated

at the Open House.

At pilot stage it is only sensible to have this as a portal interface. B2B definitions need to wait

for the launched product


Generic Lead to Cash Process – Dialogue Services

Line Check, including MLC

availability

BookAppointment

Check MLC using:DN for WLR PSTN

LLU ID for MPF

End

Use

r

Enquiry about

GEA service

CP

Ope

nrea

ch

Find spareappointment slots

Check forappointments

Choose

appointment

Confirmappointment

Choose

appointment

Nextslide


Generic Lead to Cash Process – Place Order

ProvideService

End

Use

rC

PO

penr

each

Start Usage

SubmitOrder

Validate Order

Accept/reject

KCI accept/

reject

InitiateBilling

Serviceworking?

Ordercomplete

No

Yes

Trouble to Resolve


Trouble to Resolve Process - Overview

Line Test

BookAppointment

Submit TroubleReport

KCIUpdates

Fault Cleared

Dialogue Services Plan is to build on existing

dialogue services. Portal version

will definitely be available.

Order Placement New order types will work along existing lines.

At pilot stage it is only sensible to have this as a portal interface. B2B definitions need to wait

for the launched product


Trouble to Resolve Process – Dialogue Services

Test GEA service and

indicate whether appt reqd

BookAppointment

Run Line Test

End

Use

r

Raise Fault

CP

Ope

nrea

ch

Find spareappointment slots

Check forappointments

Choose

appointment

Confirmappointment

Choose

appointment

NextslideIf

required

Next slide if appointment not required


Trouble to Resolve Process – Submit Trouble Report

Resolve Fault

End

Use

rC

PO

penr

each

Resume Usage

SubmitTroubleReport

Validate TroubleReport

Accept/reject

KCI accept/

reject

InitiateBilling

Fault clear accepted?

Ordercomplete

No

Yes

CloseFault

Migration Processes

Chris Clough


EU on GEA

EU on SMPF

Migrating to GEA from SMPF (animated)

MDF

Start:•

CPX owns EU, on CPA’s SMPF

Prepare:•

CPB orders GEA for EU (with MAC if CPA ≠

CPB)•

GEA Migrate KCI1 →CPB•

SMPF Cease KCI →CPA•


CVLAN on CHB CHP specified•

CCD confirmed•

CPB able to set up their configuration•

SMPF Cease KC2 →CPA (inc CCD)

CPA DSLAM

Migrate – on CCD (stage 1):•

Openreach configures DSLAM and CHP•

Openreach engineer jumpers at cabinet•

EU downtime starts when jumpering starts

Complete:•


SMPF Cease KC3 →CPA•

Frames jumpering remains in place (LIJ) to support PSTN/WLR

FTTC DSLAM

CPBCHP

PCP SSFP/ Modem

NTE EU

Migrate – on CCD (stage 2):•

Openreach engineer installs SSFP & Modem •

EU downtime ends when modem trains up•

Assumes CPB configures EU ahead of

engineer visit

Jumpering left in to support PSTN/WLR

NB -

PSTN wiring omitted for clarity


Variations•

Conversion from GEA+WLR to SMPF+WLR–

Inverse of conversion to GEA except

•

removal of VDSL modem and SSFP is CP/EU responsibility•

VDSL SSFP expected to support ADSL (SSFP must be removed for ADSL to be available via extension wiring –

standard SSFP issue)•

EU will receive a jiffy bag to return the VDSL modem if they wish•

Frames task to set up SMPF, service enabled once cabinet jumpering removed

•

Adding GEA to MPF–

the same as for GEA replacing SMPF, except

•

CPA DSLAM can still provide baseband service as MPF still in place

•

Conversion from GEA + MPF to MPF–

As for conversion from GEA+WLR to SMPF+WLR, except

•

CP/EU may have to remove SSFP for MPF based service to work•

MPF wiring already in place at the frame

FTTC Consultation update

Andrew Sheppard


FTTC Consultation Update

•

Consultation commenced on 21st

August and closed on

29th

September

•

Formal responses received from 10 CPs.

•

Consultation Summary Report and a revised version of the Product Proposal document were published on: http://www.openreach.co.uk/orpg/products/nga/nga.do

•

CP respondents were invited to a multi-lateral event on 14- 15th

October to hold further talks on the product and

development plan

•

Product is moving into design phase and further collaboration with committed CPs

is anticipated

(consultation continues in this manner throughout the design and development phases of the delivery)

http://www.openreach.co.uk/orpg/products/nga/nga.do



•

Clarifications, changes and considerations for the product from CP feedback:–

Confirmation of inclusion from the start of the Pilot :

•

GEA with MPF line sharing (same CP providing both)•

20 Hour response Enhanced Care Level

•

Migration processes for all valid product conversions•

Un-contended service based on assured rates, not peak rates

•

Services can be configured remotely for CP ownership transfer, re-grading of bandwidth and addition/removal of features

–

Consideration for the pilot:•

Intermediate Agent

•

Self-Install Service Specific Faceplate (limited introduction for initial testing)



•

Key clarifications, changes and considerations for the product from CP feedback:–

Investigate for earliest possible inclusion (post-Pilot):

•

Rationalise components in the home to improve installation (VDSL2 Modem functionality to integrate into SSFP or CP’s

CPE)

•

GEA + MPF –

Different CPs

sharing line offering voice and fast broadband)

•

GEA independent of Baseband Voice•

Sub-20Mbit/s product (if line incapable of delivering 20Mbit/s)

•

Higher speed and symmetric bandwidth options (subject to technical capability)

•

Simultaneous Provide Process, etc...•

Sub-20 hour care level response

•

Multicast•

Develop optional enabling functionality for CPs

to provide voice over

FTTC

DEA Consultation update

Andrew Sheppard


DEA Customer Consultation

•

Consultation commenced on 29th

September.

•

Bi-lateral talks have been held with 10 CPs

•

Formal responses to the consultation will be accepted up until Friday 7th

November.

•

As of 31st

October we have received 4 positive responses from Communication Providers and further responses are anticipated by

7th

November.

•

Points covered in the responses received relate to product specification, deployment strategy, commercials and network design.

•

Following conclusion of the consultation and a period of assessment, Openreach will produce a Consultation Response Summary –

targeted

for publication in early December

Close and Review

Andrew Sheppard


Industry Events – Diary

NGA Sub Working Group

12th Jan 0910:00 –

14:00

BT Centre, London

NGA Sub Working Group

12th Jan 0910:00 –

14:00

BT Centre, London

Openreach Future Access Forum

20th Nov 08

BT Tower, London

Openreach Future Access Forum

20th Nov 08

BT Tower, London

NGA Sub Working Group*

11th

Dec 08

09:30 –

13:00

TBC – ‘Livemeeting’ or BT Centre,

London


11th

Dec 08

09:30 –

13:00TBC –

‘Livemeeting’ or BT Centre,

London


29th

Jan 09

10:00 –

14:00

TBC – ‘Livemeeting’ or BT Centre,

London


29th

Jan 09

10:00 –

14:00TBC –

‘Livemeeting’or BT Centre,

London

* These two sub working group events will focus on FTTC only. Invitees will be restricted to CPs who have committed to take part in the pilot. * These two sub working group events will focus on FTTC only. Invitees will be restricted to CPs who have committed to take part in the pilot.

fttp industry process group - openreach · 12/01/2009 · industry sub working group. 6. th . ......

Documents