Migration Proposal Consultation Dave D’Arcy

1. Migration Proposal ConsultationDave D’Arcy The purpose of this presentation is to: Confirm the activity undertaken during the Migration Proposal Consultation (slide 2) Share with Communication Providers the Main themes from the Migration Proposal Consultation (Slides 3-6) Share with Communication Providers the management processes in use with Mike Cook’s customer engagement to manage implementation & migration issues (Slides 7-9) Confirm the details of the Change Control & Adjudication Process to apply for the Plan of Record (Slides 10-16) Confirm the publication timescales for the Plan of Record (Slide 17)

2. Migration Proposal Consultation – Update 14/12/05 CONSULTATION (21/10 – 16/12) • 05/12 – 16/12 • BTW/Industry Board reviews/agrees Migration Proposal Change Requests • Expert Groups on Migration methodology • Communicate outcome of Change Requests to CP’s • IMWG – 16/12/05 • 02/11-02/12 • Bi-laterals • Interconnect CP’s • Service Provider CP’s • Multi-lateral consultation through IMWG & expert groups • (21/10 – 02/11) • CP Impact Analysis • 5pm 31 October 2005: • Registration: • participation in bi-laterals • 10 CP’s registered • receipt of Change Requests • 10 CP’s registered • nominations for Adjudication board • 2 nominations (out of 3) received • Latest 13/11/05 • Adjudication Board will not sit as no Change Requests received • Potential stranded assets being reviewed between CP’s • Consultation closes @ IMWG on 16/12/05 • 5pm 02 November 2005: • Change Requests: • None received • Formal Responses: • 2 responses received • Bilaterals: • All Pathfinder interconnect CP’s bi-laterals held • No major issues identified for sequencing and timing of migration for voice services

3. Key Themes from Consultation:Migration Proposal • No Communication Provider expressed they were uncomfortable with sequencing and timing in Migration Proposal • No Change Requests made but; • A number of CP’s have indicated that they will be making Change Requests once Plan of Record established • Fit with NGN business plans • Fit with customer plans • There is a need for an extension to the Change Request Process to cover “Target NGS’s” • When is the cut-off for when Change Requests can be submitted (sequencing and timing of DLE’s)? • What are PSTN voice products? • How will migration for other products interact with the current Migration Proposal?

4. Key Themes from Consultation:Provisioning • What will new routing plans look like? • How will routing plans be managed? • How will Capacity orders be placed for VIC (previously known as VDLE/VIEC)? • How will ACO’s be placed? Will they be separate for 21CN? • How will cut over be managed in the Transfer Phase? • How will the cease process work? • Will BT issue new PNI’s for GNP to take account of the switch migration? If so how far in advance of closure will this happen? • What are the order leadtimes for the new VIC product and how will they differ from the current product? • DMA’s are they required when traffic is going from a direct DLE route to a vDLE? • How often/quickly will NIPP be updated following migration?

5. Key Themes from Consultation:Methodology & Management • What point prior to final closure and transfer of customer lines to an MSAN will BTW suspend new provisioning of products? • What are the impacts on Disaster Recovery Plans? • What is the Fallback Plan for DLE to NGS migration? • What will Command and Control look like? • How will BTW advise CP’s of the actual date of Mass Migration? Eg to NMC’s • Is there any potential for impacts on non PSTN voice products? • Testing - Supporting strategy for products & solutions. • How will PSTN migration affect services such Number Portability • How will BTW manage testing?

6. Moving Consultation Issues forward • Migration Proposal: • Change Control & Adjudication – This meeting • PSTN voice products confirmation – This meeting • Structure of Plan of Record & integration of other product migrations – Plan of Record in January 2006 • Provisioning: • Provision Experts meeting • Short workshop on 18/01/06 • Second workshop needed early February • Methodology & Management: • See Consultation Plan under development

7. Customer Engagement Process for Implementation & Migration The purpose of this section of the presentation is to: Share with Communication Providers the management processes in use with Mike Cook’s customer engagement team to manage implementation & migration issues This process will help drive the production of content for Implementation & Migration working Groups and Expert meetings and support the production of FAQ briefings

8. RFI CR SoR Risk/ Issue • Service Migration definition • how we will do Migration, • when we'll do Migration, • how Migration will be managed, • how we'll verify that Migration has been completed successfully Request Process Service Migration Request In I&MWG, Bi-Lateral, Consult21@bt.com New: Request Logged Unique ID provided to Requestor • 21CN response • established, • authorised, and • communicated to requestor Existing: ID provided to Requestor 21CN programme response provided to requestor

9. Process Principles • All Service Migration requests (RFI, CR, SoR, Risks and Issues) to be raised at I&MWG, Bi-lateral, or via Consult21@bt.com • Closure criteria agreed with CP at the time request is raised i.e. what needs to be delivered in order to address the request • Repository held within BTW to ensure consistency of responses to CP questions • All Service Migration requests to be allocated a reference number for ease of CP follow-up if necessary • All Service Migration requests proactively managed to ensure updates and responses delivered within agreed timescales • BTW & CP agree request criteria fulfilled • Responses will be fulfilled via agenda slots at relevant working groups and followed up bi-laterally as appropriate • BTW will work to develop generic versions of confidential questions to aid other Communication Providers

10. Change Request & Adjudication Process The purpose of this presentation is to: share with Communication Providers the principles of Change Request Process(es) which will apply following the publication of the Plan of Record Seek Communication Provider feedback on two aspects of the process which have been highlighted during the consultation phase

11. Plan Of Record:Change Request & Adjudication Process • Change Requests anticipated: • Route migration – changes to target NGS’s • Adjudication by BTW dependent upon capacity planning considerations (as current process) • Disparity process is as per current contractual arrangements • Migration Proposal – changes to timing and sequencing of CP Route & Mass migrations • Adjudication by joint/industry Board • Dispute process with Adjudication Board

12. Plan of Record:Change Request (sequencing & timing of migration) • Any CP can submit a Change Request • On the Change Request form with rationale • To Consult21@bt.com • CP’s will be required to register to receive submitted Change Requests • Will be required even by those who registered for the consultation phase • Enables BT to keep a distribution list targeted at “the right contacts” • Change Requests received will be circulated to the distribution list • Change Request circulated as “anonymous” ie Change X has been requested • Enables other CP’s to comment on impact (minimise requests for changes to be reversed) • All Change Requests will be Adjudicated through the Industry/BT Adjudication Board • Agreed changes will be notified to the Change Request Distribution List • Agreed Changes will be incorporated into the Plan of Record on quarterly basis

13. Plan of Record:Change Request (sequencing & timing of DLE migration) • Key Issues - Timing • Up until what point should Change Requests be considered? • Options suggested during consultation are: • Not considered after HLSAN agreed (18mths out) • Not considered after Detailed SAN Issued (15mths out) • Not Considered after ACO’s placed (14 mths out) • Not considered after Capacity Orders placed (12 mths out) • Considered until Transfer Phase commences (6 mths out) • All timeframe given are against the Complex SAN process & Mass Migration timeframes

14. Plan of Record:Change Request (sequencing & timing of migration) • Key Issues – Adjudication Panel protocols • What information on Change Requests should members of the Adjudication Panel have access to in order to make their decision? • Options suggested are: • BTW categorises each CP request according to an agreed categorisation devised by the Adjudication panel • “Request X has been made by a CP for a Category 4 reason” (where category 4 indicates serious customer affecting issue) • Adjudication Panel has access to full Change Request info

15. Plan of Record: Adjudication Panel • Remit reviewed with Steering Board on regular basis • The Panel adjudicate Change Requests for the operational sequencing of DLE migration into 21CN, based on the schedule set down during the operation of the Plan of Record • The Panel members need to bring skills and or experience related to customer and operational impact assessment • Panel will consist of 7 members: • 3 from BT (including BT Retail as an SP) • Trish Wells, BTr, Chris Basey, BTW, A.N.Other (openreach) TBC • 3 from Communications Providers (suggest review membership annually) • Paul Rosbotham, C&W, Chris Timewell, Telewest, John Crawford, Gamma • Mike Cook, BTW as Chair (who has casting vote, where required)

16. Plan of Record Adjudication Panel:Operation • Decisions will be based on the avoidance of CP and End User impact requested by the change versus the potential impact caused by the change on CPs and end users • Any change where the adverse impact is not evident should err on the side of retaining the existing schedule • Will sit as and when (min monthly) to deliberate on change requests • Simple methodology: • One member one vote • Each registered CP (including BTW and BTr) has opportunity to comment on requested change to have voice heard prior to decision • Decisions communicated to registered CP’s and requestor • Plan of Record updated quarterly to reflect changes • Subject to Steering Board Approval, any Member can be Replaced

17. Plan of Record publication • Publication Schedule – last week in Jan 06 • Plan of Record template: • Simple document focussing on: • Change Control Processes • Document & dataset Change control • Dataset publication: • Through NIPP for interconnect Communication Provider • Through LLU portal for Local Loop Unbundlers