BT Wholesale Early Delivery Options 280514

Report
Ofcom Consumer Switching
BT Wholesale Timelines
23 May 2014
1
Disclaimer
The information contained in this Presentation slide-pack is confidential information for
discussion purposes only and should not be disclosed without British Telecommunications plc.
(BT's) permission. Please treat it accordingly and do not forward, republish or permit
unauthorised access.
Please note that BT has taken reasonable care to check that the information contained in this
Presentation slide-pack is accurate at the time of issue, however, it is subject to change. In
relation to any products/services referred to in this document which are currently under
development and/or trial, BT gives no undertaking or other commitment that the
product/service will be made commercially available.
References to any such service and time scales contained within this document are indicative
and estimates for information purposes only and these and other information do not constitute
any contractual or other obligation.
Applicable BT standard terms and conditions apply.
© British Telecommunications plc.,
2013 British Telecommunications plc.
Registered office: 81 Newgate Street London EC1A 7AJ
Registered in England no: 1800000
2
Story Title
21CNCE-75918
Ofcom NoT – introduction of RID and postcode to provides
Story Description
Make RIDs mandatory for all migration + provides, validate and pass
down to OR across all product types.
Provide and migration orders will be validated on DN + Postcode
21CNCE-76733
Consumption of OR Unsolicited cease KCI’s and passing through to
Strategic KCI's for Broadband cease notifications sent from Openreach CPs via B2B, email.
Mandatory Release
Optional Release AP
(Sep)
Mandatory Release AQ
(Nov)
Could defer to Release AR
(Jan)
Release AP (Sep)
21CNCE-76746
Strategic KCI's for Broadband loss notifications sent from BTW
Generation of Notice of Transfer KCIs for BTW CP to BTW CP
migrations via B2B, email.
Release AP (Sep)
21CNCE-77354
Ofcom NoT - Migrations to 20C within BTW CPs
21CNCE-77371
Ofcom NoT - Migrations to WBC Copper within BTW CPs
21CNCE-77388
Ofcom NoT - Migrations to WBC FTTC within BTW CPs
All of the migrations to 20C within BTW CPs
Release AQ switched off
All of the migrations to WBC Copper within BTW CPs
Release AQ switched off
All of the migrations to WBC FTTC within BTW CPs
Release AQ switched off
All of the migrations to WBC FTTP within BTW CPs
Release AQ switched off
LLU to all product variants (remove MAC validation from provide onto
OR)
Release AQ witched off
Gaining CP Cancellations
Release AP
21CNCE-77405
Ofcom NoT – Gaining CP Cancellation driven KCIs
Bulk LLU to WBC migrations via BUT (BBCT)
Bulk migrations within the BTW stack but with a CP change via BUT
(BBCT)
21CNCE-77419
Ofcom NoT - Cancel Other for BTW CP to BTW CP migrations
21CNCE-77431
Ofcom NoT - Cancel Other for BTW to LLU CP migrations
Cancel other for BTW CP to BTW CP migrations
Cancel other for BTW to LLU CP migrations
Consumption of cancel other when LLU CP cancels BTW migration
Ofcom NoT - MIS and Reporting of Cancel Other’
- on hold waiting Ofcom guidance on format etc
3
MIS and Reporting of cancel other
* Do not use until March to allow for testing between BTW and OR
Release AQ (Nov)
*Do not use until Mar
Release AR (Jan)
*Do not use until Mar
Release AR (Jan)
*Do not use until Mar
Release AQ (Nov)
switched off
Openreach Early Delivery Options overlaid
with BTW Plans (tbc)
4
Cancel Other (Openreach Early Delivery Options 1 and 5)
AP
13/09/14
AQ
15/11/14
AR
17/01/15
21CNCE-77419
Cancel Other for BTW to
BTW migrations
21CNCE-77431
Cancel Other for BTW to
LLU migrations
Cancel Other for LLU to
BTW migrations
2650
20/09/14
2700
22/11/14
2750
24/01/15
Option 1 : New Cancel
Other Codes
Option 5 : Full Support
for LCP Cancel Other
5
1. BTW deploy Switched On
BTW to BTW Migrations
Cancel Other in Release AQ
(only for use in agreement
with BTW)
2. BTW deploy Switched On
Cancel Other for BTW to
LLU and LLU to BTW
Migrations – full
operability dependent on
2750 going Live one week
later.
RID on SMPF Provides (Openreach Early Delivery Option 2)
AP
13/09/14
21CNCE-75918 RID
Optional for IPstream
and WBC ADSL
Provides and Migrations
2650
20/09/14
RID Optional validated if received
6
AQ
15/11/14
AR
17/01/15
RID mandatory for
IPstream and WBC
ADSL Provide and
Migration Orders
2700
22/11/14
2750
24/01/15
1. Release AP : BTW validate
RID in any Broadband
orders if present. Note that
RID accepted (but not
validated) currently.
2. From Release AQ RID is
mandatory for BTW
Provide and Migration
orders
3. RID will be passed to
Openreach, if received
from CPs – up until Release
2650, Openreach will
ignore RID
4. RIDs not mandatory in
Openreach until June 2015.
Cancel Other with RID Notification to Gaining CP
(Openreach Early Delivery Option 3)
AP
13/09/14
AQ
15/11/14
The Cancelling CP RID
will be included in
‘Cease Cancelled’ KCI
for Unsolicited/Managed
Ceases
7
AR
17/01/15
The Cancelling CP RID
will be included in
‘Provide Cancelled’ KCI
2600
20/07/14
2700
22/11/14
V26 Schema including
RID notification to
Gaining CP for SMPF
deployed
V26 Schema including
RID notification to
Gaining CP for FTTC
deployed
2750
24/01/15
1. The Cancelling CP RID will
also be included in the
‘Unsolicited/managed
Cease ‘ KCI, confirming to
the Losing CP that the
cease of the asset has
been cancelled.
2. Assuming that OR deploy
v26 schema in R2600 &
R2700, BTW will consume
this in Release AR and
make the Cancelling CP
RID available in
Cancellation related KCIs
3. Both need a schema
upgrade for CPs to
consume but we are only
mandating this from
Release AR.
SMPF and FTTC validation rules for Postcode/DN mismatch
(Openreach Early Delivery Option 4)
AP
13/09/14
21CNCE-75918
Postcode Optional for
IPstream and WBC
Provides and Migrations
2800
21/03/15
AQ
15/11/14
AR
17/01/15
Postcode Mandatory for
IPstream and WBC
Provide and Migration
Orders
2850
05/15
2875
20/06/15
Postcode Mandatory
and order rejected if
incorrect
8
1. Postcode is an optional
attribute today – if absent
a value is defaulted into
the order into Openreach
2. From Release AP, BTW will
validate postcode if
present, and return
warning message if
postcode incorrect. But
order is sent to OR with
the postcode from eMLC
3. From Release AQ the
postcode is validated and
the order is rejected if the
postcode is incorrect.

similar documents