BA 90 Day CP Notification Release BA Targeted for delivery 10 th July 2016

Transcription

1 BA 90 Day CP Notification Release BA Targeted for delivery 10 th July th April 2016 Alan Cameron: BTW Senior Product Manager 1

2 Confidentiality & Legal Statement 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 2016 British Telecommunications plc Registered office: 81 Newgate Street London EC1A 7AJ Registered in England no:

3 BTW 90 DAYS CP Notification - Release BA L2C - SoGEA Stories covered: 1.BTWCE [SoGEA L2C Reporting Phase 2 - To complete L2C reporting and cover omissions from release AZ story BTWCE-64984] 2.BTWCE BUILD BA - Cancel a SoGEA order (OR ORCE 86271) 3. BTWCE BUILD BA - Amend a SOGEA order (OR ORCE 78165) 4. BTWCE SoGEA - Cease ORCE (Build targeting release BA) 3

4 BTW 90 DAYS CP Notification - Release BA BTWCE SOGEA L2C REPORTING PHASE 2 - TO COMPLETE L2C REPORTING AND COVER OMISSIONS FROM RELEASE AZ STORY BTWCE Slide 4

5 BTW 90 DAYS CP Notification Release BA Description and CP Interface Impacts Summary BTWCE Description This story is a continuation of the Rel AZ Story BTWCE-64984, where the BBPR GUI Reports and BBPR XML Reports (BBCR now renamed as BBPR - Broadband Progress Reporting) would be present to display SOGEA related information of orders so that SoGEA L2C performance into BTW operational measures and Customer reports can be determined. This Story BTWCE in Release BA would cover the below:- BBPR GUI Reports BBPR XML Reports The story is not covering: WCR Report (Wholesale Customer Reporting ): No impact / no change in any of the WCR reports for this story from Rel AZ. WBMC Reports 5

6 BTW 90 DAYS CP Notification Release BA Description and CP Interface Impacts Summary BTWCE CP Interface Impacts As part of the SOGEA L2C Reporting, the below Reports would be impacted where SOGEA attributes would be added (shown in later slides):- BBPR GUI REPORTS Circuit Activity Search Report Order Delta Search Report Order Search Report Order Summary Report Service History Search report 6

7 BTW 90 DAYS CP Notification Release BA Description and CP Interface Impacts Summary BTWCE CP Interface Impacts As part of the SOGEA L2C Reporting, the below Reports would be impacted where SOGEA attributes would be added (shown in later slides):- BBPR XML REPORTS ORDER DELTA GM DATES XML V4 ORDER DELTA GM DATES XML V5 order delta gm dates xml v6 Order Delta GM Dates XML v3 ORDER DELTA GM DATES XML V2 Order Delta Dates XML Product Family Migration XML rpt_xml_speedsync_download.xml rpt_xml_speeddelta_download.xml rpt_xml_dslmax_service_option.xml rpt_xml_eusummary_download.xml 7

8 BTW 90 DAYS CP Notification Release BA Description and CP Interface Impacts Summary BTWCE Portal Changes ecoplus Portal None 8

9 BTW 90 DAYS CP Notification Release BA XML Structural Changes (B2B, BBAC, BBCR, KBD, Sentry) BTWCE B2B XML Changes : None BBAC XML changes None BBCR XML Reporting changes Yes KBD XML changes None Sentry Webservices changes None 9

10 BTW 90 DAYS CP Notification Release BA BTWCE Reporting Changes: Yes No new BBPR GUI or BBPR XML reports have been created. The reports would have certain SOGEA attributes displayed. Also the BBPR GUI reports can be filtered by selecting SOGEA as a Access Technology from the BBPR GUI. The SOGEA Attributes are added in the BBPR GUI Reports, PFA The SOGEA Attributes are added in the BBPR XML Reports, PFA 10

11 BTW 90 DAYS CP Notification Release BA BTWCE Reporting Changes: Mockups of BBPR GUI reports 11

12 BTW BB 90 Day CP Notification - Release BA BTWCE BUILD BA - CANCEL A SOGEA ORDER (OR ORCE 86271) 12 Slide 12

13 BTW BB 90 Day CP Notification Release BA Description and CP Interface Impacts Summary BTWCE Description This story solution aims to provide the functionality for CPs to cancel SOGEA inflight orders for below order journey. No new OR response code and response messages have been introduced for this journey, existing GEA-FTTC response code and response messages will be applicable. CP will have option to place cancel order on below inflight orders: New SOGEA Provide Order (inflight) 20CN IP Stream to 21CN WBC SOGEA Migration Order (inflight) 21CN ADSL/ADSL2+ to 21CN WBC SOGEA Migration Order (inflight) Additional cancel journeys (e.g. cancel of WBC SOGEA provide from FTTC) will be covered in stories in later releases. 13

14 BTW BB 90 Day CP Notification - Release BA Description and CP Interface Impacts Summary BTWCE Description CP can place SOGEA Cancel Order with below parameters: The BTWS Order Reference of the SOGEA order which is to be cancelled (Mandatory) Cancellation Reason (Mandatory) RID (optional) PONR-BAU 14

15 BTW BB 90 Day CP Notification - Release BA Description and CP Interface Impacts Summary BTWCE CP Interface Impacts CP B2B Documentation will be updated to include the SOGEA Cancel Order Journey. As per existing changes, it will be similar to the GEA-FTTC Cancellation Order and there will be no schema change. Portal Changes eco Plus GUI has no significant changes and the screens are similar to existing GEA-FTTC Cancellation Order Journey. 15

16 BTW BB 90 Day CP Notification Release BA Description and CP Interface Impacts Summary BTWCE CP Interface Impacts Channels through which the SOGEA Cancel order can be placed by CP at Wholesale: ecoplus Portal B2B Channel A Cancel Order B2B XML must contain: The BTWS Order Reference of the SOGEA order which is to be cancelled (Mandatory) Cancellation Reason (Mandatory) RID (optional) 16

17 BTW BB 90 Day CP Notification Release BA Description and CP Interface Impacts Summary BTWCE Portal Changes There is no change in eco Plus Portal screens and will be similar to the GEA-FTTC Cancellation Order. A SOGEA Cancel Order must contain: The BTWS Order Reference of the SOGEA order which is to be cancelled (Mandatory) Cancellation Reason (Mandatory) RID (optional) PONR-BAU as GEA-FTTC ****Full details would be covered as part of 28 days CP notification Slide Pack. 17

18 BTW BB 90 Day CP Notification - Release BA XML Structural Changes (B2B) BTWCE B2B XML Changes CP B2B Documentation will SOGEA Cancel Order details. BBAC XML changes None BBCR XML Reporting changes None KBD XML changes None Sentry Webservices changes None 18

19 BTW BB 90 Day CP Notification Release BA XML Content Change BTWCE XML Content Change BTW Completion Code Description When will this be sent? N/A N/A N/A 19

20 BTW BB 90 Day CP Notification Release BA Response Codes B2B & OneSiebel BTWCE No new OR response code and response messages have been introduced for SOGEA Cancel Order journey, existing GEA-FTTC solution pattern will be applicable for this story. In case of OR acceptance of SOGEA Cancel Order, CP will be informed using the appropriate KCI. In case of OR rejection of SOGEA Cancel Order, CP will be notified using the same approach as used for the handling of rejections of GEA-FTTC cancel orders. OR rejection code will be routed to the SOGEA Exception Queues as below 20

21 BTW BB 90 Day CP Notification - Release BA BTWCE BUILD BA - AMEND A SOGEA ORDER (OR ORCE 78165) 21 Slide 21

22 BTW BB 90 Day CP Notification - Release BA Description and CP Interface Impacts Summary BTWCE Description This story solution aims to provide the functionality for CPs to amend an inflight WBC SOGEA order for the order journeys below. Three new OR response codes and messages have been introduced. Other response codes and messages reuse existing ones for WBC FTTC. CP will have option to place an amend order on the following journeys: New SOGEA Provide Order 20CN IP Stream to 21CN WBC SOGEA Migration Order 21CN ADSL/ADSL2+ to 21CN WBC SOGEA Migration Order Additional amend journeys (e.g. amend of WBC SOGEA provide from FTTC) will be covered in stories in later releases. A maximum of 7 Site Visit Reasons would be permitted on BT Wholesale irrespective of the Site Visit Action. 22

23 BTW BB 90 Day CP Notification Release BA Description and CP Interface Impacts Summary BTWCE Description A CP can place a WBC SOGEA Amend Order with the following parameters: The BTWS Order Reference of the inflight WBC SOGEA order which is to be amended - Mandatory Amend Reason - Mandatory Retailer Id (RID) Optional Amendable Attribute- Optional (see later) Revision Action-Mandatory (For SVR Amend order via B2B channel only) 23

24 BTW BB 90 Day CP Notification Release BA Description and CP Interface Impacts Summary BTWCE Amendable Attributes: S. NO. Amendable Attributes 1 CRD 2 OTD 3 App Ref 4 TRCharge Band 5 Site Visit Reason Notes 6 Site Safety Notes 7 Special Arrangement Notes 8 Password 9 Hazard 10 First Name 11 Last Name 12 Work Phone Mobile Number 15 Handover Port Service Id 16 Outer Tag 17 Fixed Porting Date 24

25 BTW BB 90 Day CP Notification Release BA Description and CP Interface Impacts Summary BTWCE Point of No Return (PoNR) Rule: The point of no return (PONR) rules for WBC SOGEA amend orders are as per the BAU PONR rules for WBC FTTC. OS Portal Channel: Post PoNR if user hits the amend button the following error message will be shown :- Error message -> It is not possible to amend this item as it has passed the point in the journey where it can be amended. Please wait for this item to complete before making changes to your service. B2B Channel: If PoNR has reached and amend order is received then following error code and error message will be returned by OS:- Error message -> Cannot amend Order as point of no return has passed Error Code ->

26 BTW BB 90 Day CP Notification - Release BA Description and CP Interface Impacts Summary BTWCE CP Interface Impacts CP B2B Documentation will be updated to include the WBC SOGEA Amend Order Journey. It will be similar to the WBC FTTC Amend Order with a new tag called Revision Action (for Site Visit Reason Amend Orders only ) in existing schema via B2B Channel Only. Portal Changes Product Model Screen change will be covered in the 28 days CP notification slide. Site Visit Reason (SVR) Amend Order (OS/B2B Channels): It is advisable please DO NOT raise an amend order (RevisionAction LoV: Amend/Cancel) until you receive the Seller Id (linked with SVR) in KCI2 of original provide order. Please ensure to populate the correct RevisionAction LoVs while placing SVR Amend Order via B2B channel Only. 26

27 BTW BB 90 Day CP Notification Release BA Description and CP Interface Impacts Summary BTWCE CP Interface Impacts Channels through which the WBC SOGEA Amend order can be placed by CP : ecoplus Portal B2B Channel An Amend Order B2B XML must contain: The BTWS Order Reference of the inflight WBC SOGEA order which is to be amended - Mandatory Amend Reason - Mandatory Retailer Id (RID) Optional Amendable Attribute- Optional (see later) Revision Action-Mandatory (For SVR Amend order via B2B channel only) 27

28 BTW BB 90 Day CP Notification Release BA Description and CP Interface Impacts Summary BTWCE CP Interface Impacts Site Visit Reason (SVR) Amend Order via B2B Channel: B2B has introduced a new tag called RevisionAction which is mandatory while placing SVR Amend Order. It has this list of values: Create Amend Cancel CP must provide delta SVR information in an amend Order (original unchanged SVR info should not be present) with appropriate RevisionAction values. RevisionAction will come at Child line item level for all SVRs in the request B2B XML. RevisionAction will not be returned in KCIs. Instead the "Action" Product Model attribute will be returned in KCIs. 28

29 BTW BB 90 Day CP Notification Release BA Description and CP Interface Impacts Summary BTWCE CP Interface Impacts S. No SVR Order Type B2B XML Tag Required 1 Add New SVR Seller ID Applicable-No RevisionAction value: Create (Mandatory) 2 Amend Existing SVR Seller ID Applicable-Yes, (Mandatory) RevisionAction value: Amend (Mandatory) Note: Site Visit Code is non amendable, only site visit notes are amendable. 3 Delete Existing SVR Seller ID Applicable-Yes, (Mandatory) RevisionAction value: Cancel (Mandatory) 29

30 BTW BB 90 Day CP Notification Release BA Description and CP Interface Impacts Summary BTWCE Amend Reasons: (B2B & OS Portal Channel) S. No. Amend Reason 1 Change in submitted details 2 Change in requirements 30

31 BTW BB 90 Day CP Notification Release BA Description and CP Interface Impacts Summary BTWCE B2B XML Snippet- Add New SVR 31

32 BTW BB 90 Day CP Notification Release BA Description and CP Interface Impacts Summary BTWCE B2B XML Snippet- Amend Existing SVR (Site Visit Code is non amendable, only site visit notes are amendable) 32

33 BTW BB 90 Day CP Notification Release BA Description and CP Interface Impacts Summary BTWCE B2B XML Snippet- Delete Existing SVR 33

34 BTW BB 90 Day CP Notification Release BA Description and CP Interface Impacts Summary BTWCE OS Portal Changes: Details will be covered as part of 28 days CP notification Slide Pack. 34

35 BTW BB 90 Day CP Notification - Release BA XML Structural Changes (B2B) BTWCE B2B XML Changes CP B2B Documentation will publish SOGEA Amend Order details. BBAC XML changes None BBCR XML Reporting changes None KBD XML changes None Sentry Webservices changes None 35

36 BTW BB 90 Day CP Notification Release BA XML Content Change BTWCE XML Content Change BTW Completion Code Description When will this be sent? N/A N/A N/A 36

37 BTW BB 90 Day CP Notification - Release BA Response Codes B2B and OneSiebel BTWCE Three new OR response code and message have been introduced for SOGEA Amend Order journey. Other codes and messages will be reused from existing GEA-FTTC response code and response messages. S. No. BTWS Error Code BTWS Error Message (KCI as an amend rejection) When it will be sent? Cannot amend order as point of no return has passed When point of no return has passed Requested date is sooner than earliest delivery date for CRD must not be earlier than the minimum lead time the product. when the Expedite flag is not set to Y Order cannot be progressed as the CRD date is less than CRD must not be earlier than the current date today's date (today) Requested date is too far in future CRD must not be greater than the maximum lead time (90 days) The appointment reference specified is not of the correct format. Please insert a valid appointment reference We are unable to confirm the new appointment details. If an Appointment Reference is provided it must be valid. If an Appointment Reference is provided it must not be expired There are no suitable appointments available. If an Appointment Reference has not been provided The appointment that has been booked is incompatible with this type of order Order Cancelled-Head End Issue If an Appointment Reference is provided it must be for the correct Appointment Type. Order was received outside the stipulated time window 37

38 BTW BB 90 Day CP Notification - Release BA Response Codes B2B and OneSiebel BTWCE S. No. BTWS Error Code BTWS Error Message (KCI as an amend rejection) When will it be sent? The order exceeds the maximum number of Site Visit The maximum number of Site Visit Reasons Reasons allowed, Max=7. exceeded from The Site Visit Reason ID and the Site Visit Reason in the order do not match the values stored against the original order. The SVR ID and the Site Visit Reason in the Amend order do not match the values stored against the original order The order exceeds the Site Visit Reason notes field length The Site Visit Reason notes field length more than more than 100 characters. 100 characters Requested date is too far in future CRD must not be greater than the maximum lead time (90 days) Informational KCI (New Response): S. No. BTWS Code BTWS Message (KCI as an information) When will it be sent? The order is now appointed as one or more Site Visit Reasons have been added. Please check the new CCD. The order is now appointed as one or more Site Visit Reasons have been added This order does not require an engineering visit to the end The order does not require an engineering visit to the customer premises. end customer premises The appointment has been cancelled as no engineering The appointment has been cancelled as no visit is required for this order. engineering visits are required for this order. 38

39 BTW BB 90 Day CP Notification - Release BA Response Codes B2B and OneSiebel BTWCE S. No. BTWS Error Code BTWS Error Message (KCI as an amend rejection) When will it be sent? Amend rejected due to insufficient lead-time Insufficient lead time for the amend order Amend to earlier date not supported for this order type Order doesn t not support earlier date Invalid Appointment Type Appointment type given in order invalid 39

40 BTW BB 90 Day CP Notification - Release BA Response Codes B2B and OneSiebel BTWCE S. No. BTWS Error Code BTWS Error Message (KCI as an amend rejection) When will it be sent? Order is beyond latest lead time Amend Order is placed beyond the lead time Unable to amend the order because its status is: cancelled/complete/cancellation request/cancellation pending/amend request/amend pending Amend order placed while one of the inflight order is pending Amend Reason is incorrect Incorrect Amend Reason has been supplied Requested date should not be earlier than CDD Amend requested date is earlier than CDD An Appointment Reference must be provided. Appointment Ref is missing Order cannot be progressed as CDD is less than today's date Amend order CDD is before than todays date CDD must be less than Product Maximum Lead time CDD is greater than product maximum lead time The appointment date does not match the Required date Appointment date is not matching with required date The CRD cannot be changed to today's date. CRD is greater than todays date This order cannot be expedited. Order expedite cannot be done We are unable to confirm the new appointment details. New appointment details are not available 40

41 BTW BB 90 Day CP Notification - Release BA BTWCE SOGEA CEASE ORCE ( BUILD TARGETING RELEASE BA) 41 Slide 41

42 BTW BB 90 Day CP Notification Release BA Description and CP Interface Impacts Summary BTWCE Description This story solution aims to provide the functionality for CPs to cease a WBC SOGEA service. WBC SoGEA Cease replicates the functionality of WBC FTTC Cease from BTW perspective. Standard validation and KCI messages will apply as per GEA-FTTC. The cease orders to Openreach will be fulfilled in as STOP PCP jumpers left in. This would imply that a SoGEA service cease can be followed by a start on the same PCP jumpers. The Openreach minimum lead time for a SoGEA cease is the same day, for orders received before 16:00, and next calendar day, for orders received after 16:00. Amend or Cancel of a WBC SOGEA cease is not in scope of this design. 42

43 BTW BB 90 Day CP Notification Release BA Description and CP Interface Impacts Summary BTWCE CP Interface Impacts CP B2B Documentation will be updated to included the SOGEA Cease xmls. Portal Changes Summary of changes or None One Siebel GUI has no significant changes, the screens are similar to WBC FTTC Cease. WBC SOGEA Cease via the GUI is triggered using the service id. 43

44 BTW BB 90 Day CP Notification Release BA XML Structural Changes (B2B, BBAC, BBCR, KBD, Sentry) BTWCE B2B XML Changes B2B Documentation will be updated to included the WBC SOGEA Cease xmls BBAC XML changes None BBCR XML Reporting changes None KBD XML changes None Sentry Webservices changes None 44

45 BTW BB 90 Day CP Notification Release BA XML Content Change BTWCE XML Content Change BTW Completion Code Description When will this be sent? N/A N/A N/A 45

46 BTW BB 90 Day CP Notification Release BA Response Codes New (OneSiebel; KBD; Sentry) BTWCE New error or response codes BTW Completion Code Description When will this be sent? N/A N/A N/A 46

47 47 Any questions on SoGEA?

48 BTW 90 DAYS CP Notification - Release BA L2C - FTTC Stories covered: 1.21CNCE FTTC Removal of Basic and Managed Install from portfolio Part 2 (Build in AY, Test and Deploy in BA) 2. BTWCE SIM2 Escalate 3.BTWCE SIM2 Inflight Expedite (FTTC) 4. BTWCE WBC FTTC G.Fast: Cease for G.Fast 48

49 BTW BB 90 Day CP Notification - Release BA 21CNCE FTTC REMOVAL OF BASIC AND MANAGED INSTALL FROM PORTFOLIO PART 2 (BUILD IN AY, TEST AND DEPLOY IN BA) 49 Slide 49

50 BTW BB 90 Day CP Notification Release BA Description and CP Interface Impacts Summary 21CNCE Description After 31 st March 2016 Openreach will not be providing the VDSL modem for the FTTC orders. Hence as part of this story we need to remove the basic and managed install order with Openreach provided modem from FTTC portfolio. Hence from now the allowed value for OpenreachModem attribute will be No. CP Interface Impacts 1. CP should not place order with OpenreachModem as Yes and while order placement it should have the value of OpenreachModem as No. 2. Default value changes: We have changed the default value of OpenreachModem attribute to No. Because Yes is not allowed from now. 3. If user places order with OpenreachModem as Yes then it would be rejected by OS with existing business error code Also if user places order with Self Install as No, OpenreachModem as No and none of the MI modules selected then order will be rejected by OneSiebel with 2000 error code. If we have many orders coming from B2B with such combination then there would be many rejections. 50

51 BTW BB 90 Day CP Notification Release BA Description and CP Interface Impacts Summary 21CNCE Portal Changes 1. In OS portal and internal client the value for OpenreachModem as Yes will be highlighted in red and if user selects that value then error message would be shown saying OpenreachModem value Yes is not allowed for FTTC with Managed Install. 2. User can select No value only for OpenreachModem. 3. If user will not select anything in the customization page then by default the values will be Self Install No, OpenreachModem No and none of Managed install would be selected by default and even if user has selected No for both and no MI modules then on submission/summary page on submitting the page error message will come as: To order Self Install, please change the selection to Yes. To order Managed Install, please select the mandatory Managed Install Base Module. Press Edit to continue. and user will either have to select Self Install as Yes or any one of the MI module. Basically preference is to place order with Self Install as Yes. 51

52 BTW BB 90 Day CP Notification Release BA On-line Content Changes 21CNCE B2B XML Changes None BBAC XML changes None BBCR XML Reporting changes None KBD XML changes None Sentry Webservices changes None Impacted Documents None 52

53 BTW BB 90 Day CP Notification Release BA Response Codes Changes 21CNCE Changes to existing Response Code BTW Completion Code (Openreach response code) Old description New description None N/A N/A 53

54 BTW BB 90 Day CP Notification Release BA Response Codes Changes 21CNCE New error or response codes BTW Completion Code (OR response code) Description NA NA NA When will this be sent? 54

55 BTW BB 90 Day CP Notification - Release BA BTWCE SIM2 ESCALATE 55 Slide 55

56 BTW BB 90 Day CP Notification Release BA Description and CP Interface Impacts Summary BTWCE Overview CP should be allowed to place escalate of an appointment on SIM2 orders for stated products where narrowband is primary; this will compete against non BTW customers. Escalate refers to amend requests placed with an Amend Reason of In Response To BT Delay with Expedite flag set as Y 56

57 BTW BB 90 Day CP Notification Release BA Description and CP Interface Impacts Summary BTWCE CP Interface Impacts CPs should be allowed escalate of SIM2 FTTC orders for both PCPOnly and non PCPOnly CPs should be enabled the CRD of the order to be amended so that it is earlier than the standard lead time CPs should allow an Amend Reason of "In Response to BT Delay" to be submitted when Expedite flag is Y in an likewise, Amend Reason of "In Response to BT Delay" to be submitted by CP when Expedite flag is N indicates Standard/Flexible appointment can be booked by BTW CPs (i.e. non Escalate Amend). SIM2 Escalate should take into account PONR as BAU SIM2 escalates bring the delivery date forward from the current date, should allow amend request be accepted with or without appointment reference. SIM2 escalate enables new appointment type of Supplier Failed" be booked by BTW CP The appointments can be booked Monday to Sunday (including bank holidays) Both Standard (AM/PM) and Flexible (EM/EV) slots will be available for SIM2 Escalate Mockups: 57

58 BTW BB 90 Day CP Notification Release BA On-line Content Changes BTWCE B2B XML Changes None BBAC XML changes None BBCR XML Reporting changes None KBD XML changes None Sentry Webservices changes None Impacted Documents None 58

59 BTW BB 90 Day CP Notification Release BA Response Codes Changes BTWCE Changes to existing Response Code BTW Completion Code (Openreach response code) Old description New description This order cannot be expedited This order cannot be expedited or escalated. 59

60 BTW BB 90 Day CP Notification Release BA Response Codes Changes BTWCE New error or response codes upfront Amend Order rejection BTW Completion Code (OR response code) Description When will this be sent? 8000 Same day escalate is not allowed Escalate amend if the CRD is same as the current system date 8001 Order cannot be escalated before KCI2 committed. Escalate amend before the design complete stage 8002 Escalate amend cannot be placed for next working day as cut-off time has passed This is a CP Migration order that requires a 10 working day lead time, it is not possible to escalate this order to a shorter lead time Validation responses for orders via Internal Client / Portal Escalate order received after 1PM with CRD = Next working day Escalate for CP migration orders should be rejected Validation Scenarios GUI error message 1 Escalate amend if the CRD is same as the current Same day escalate is not allowed system date 2 Escalate amend before the design complete stage (i.e. Order cannot be escalated before KCI2 committed KSU006) 3 Amend reason is other than Customer requested Amend reason must be Customer requested escalate. escalate in escalate amend. 4 Escalate order is raised after 1PM with CRD = Next working day Escalate amend cannot be placed for next working day as cut-off time has passed. 5 Escalate for CP migration orders should be rejected This is a CP Migration order that requires a 10 working day lead time, it is not possible to escalate this order to a shorter lead time 60

61 BTW BB 90 Day CP Notification - Release BA BTWCE SIM2 IN-FLIGHT EXPEDITE (FTTC) 61 Slide 61

62 BTW BB 90 Day CP Notification Release BA Description and CP Interface Impacts Summary BTWCE Overview CP should be allowed to place a Expedite for Inflight amend appointment on SIM2 orders for stated products where narrowband is primary; this will compete against non BTW customers. Expedite: This is where customers can pay for an earlier appointment than they are given. 62

63 BTW BB 90 Day CP Notification Release BA Description and CP Interface Impacts Summary BTWCE CP Interface Impacts Expedite Amends may be placed for the following amend reasons: Customer Requested Expedite If CPs place an expedite amend request to change the CRD and other parameters within the same request but CRD is not accepted, then the entire amend request will not be accepted; i.e. there will not be partial completion of such amends. Expedite amend requests may be placed either with or without an appointment reference. The exception being if CPs wish to change the appointment slot whilst keeping the same CRD; in this case an appointment reference is mandatory Expedite can be for PCP or non PCP orders Both Standard (AM/PM) and Flexible (EM/EV) slots will be available for Expedite BAU expedite charges will be applicable. Same expedite appointment book to be used for both PCP only and MI PFA the mockups 63

64 BTW BB 90 Day CP Notification Release BA On-line Content Changes BTWCE B2B XML Changes None BBAC XML changes None BBCR XML Reporting changes None KBD XML changes None Sentry Webservices changes None Impacted Documents None 64

65 BTW BB 90 Day CP Notification Release BA Response Codes Changes BTWCE Changes to existing Response Code BTW Completion Code (Openreach response code) Old description None N/A N/A New description 65

66 BTW BB 90 Day CP Notification Release BA Response Codes Changes BTWCE New error or response codes BTW Completion Code (OR response code) Description Narrowband order could not be amended to the new date, therefore the BB order has not been amended When will this be sent? Synchronisation of the CCD with the linked Narrowband order is not achieved 66

67 BTW BB 90 Day CP Notification Release BA BTWCE WBC FTTC G.FAST: CEASE FOR G.FAST 67 Slide 67

68 BTW BB 90 Day CP Notification Release BA Description and CP Interface Impacts Summary BTWCE Description This story solution aims to provide the functionality for CPs to cease a WBC FTTC G.fast service. WBC FTTC G.fast Cease replicates the functionality of WBC FTTC Cease from BTW perspective. Standard validation and KCI messages will apply as per GEA-FTTC. Amend of Cease and Cancel of Cease is part of this design. G.fast would be managed as a stop-start service. The PCP jumpers-are left in when CP ceases a G.fast service. CP Interface Impacts 1) No impact as the same current FTTC cease XMLs is used for FTTC G.fast cease XMLs. The same FTTC cease XMLs published as part of CP B2B documentation can be used for FTTC G.fast cease XMLs. 68

69 BTW BB 90 Day CP Notification Release BA Description and CP Interface Impacts Summary BTWCE Portal Changes One Siebel GUI has no significant changes, the screens are similar to WBC FTTC Cease. WBC G.fast Cease via the GUI is triggered using the service id. 69

70 BTW BB 90 Day CP Notification Release BA XML Structural Changes (B2B, BBCR, KBD, Sentry) BTWCE B2B XML Changes None BBAC XML changes None BBCR XML Reporting changes None KBD XML changes None Sentry Webservices changes None 70

71 Any questions on FTTC? Or anything else? 71

72 Broadband 90 day CP Notification Release BA for New KBD BTW Story Design CP Impacts Category : T2R KBD Version : 2.0 Date : 8 April 2016 British Telecommunications plc

73 Confidentiality & Legal Statement 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 Registered office: 81 Newgate Street London EC1A 7AJ Registered in England no: British Telecommunications plc

74 Broadband 90 day CP Notification - Release BA Stories covered: Broadband: 1. BTWCE-62054: Degraded Services Further Enhancements 2. BTWCE-65393: WBC FTTC G.Fast: T2R & Test and diagnostic support of G.Fast Variant 160/30 & 330/50 (DESIGN, REVIEW, BUILD, TEST and DEPLOY) British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 74

75 BTWCE-62054: Degraded Services Further Enhancements British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 75

76 Broadband 90 day CP Notification Release BA Description and CP Interface Impacts Summary Broadband : BTWCE Description As part of this story, Performance problem related to degraded services within BTW network will be identified by NewKBD. Outcome description will change for outcome code ND23 and ND511. NewKBD will send new outcomes for WBC copper and FTTX products. Outcome code ND24 is added for WBC copper product. Outcome code ND512 is added for WBC fibre product. CP Interface Impacts for 90 days Changes in KBD Outcome code sheet. British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 76

77 Broadband 90 day CP Notification Release BA Broadband : BTWCE Change to existing outcome codes description BTW Completion Code Outcome Old description New description ND23 ND511 FAIL FAIL Problem Explanation: Potential Performance issue has been identified related to VLAN Utilization. Resolution/Recommendation: Please inform the End User the VLAN Regrade date is {actual date}. Please wait until Regrade is complete before retesting. Problem Explanation: Potential Performance issue has been identified related to VLAN Utilization. Resolution/Recommendation: Please inform the End User the VLAN Regrade date is {actual date}. Please wait until Regrade is complete before retesting. Problem Explanation: Potential Performance issue has been identified related to VLAN Utilization. Resolution/Recommendation: Please inform the End User the VLAN Regrade date is {actual date}. Please wait until Regrade is complete before retesting. OR Resolution/Recommendation: Please inform the End User the VLAN Upgrade will be completed by {PEW End Date}. Please wait until Upgrade is complete before retesting. Problem Explanation: Potential Performance issue has been identified related to VLAN Utilization. Resolution/Recommendation: Please inform the End User the VLAN Regrade date is {actual date}. Please wait until Regrade is complete before retesting. OR Resolution/Recommendation: Please inform the End User the VLAN Upgrade will be completed by {PEW End Date}. Please wait until Upgrade is complete before British Telecommunications plc CP Notification 90-Day Template v2-0 Slide retesting. 77

78 Broadband 90 Day CP Notification Release BA Broadband : BTWCE Addition of New outcome Codes BTW Completion Code ND24 ND512 Outcome Fail Fail New description Problem Explanation: Potential Performance issue has been identified related to a network node. Device Id is <SNE ID >. Resolution/Recommendation: Please inform the End User the VLAN Upgrade will be completed by {PEW End Date}. Please wait until Upgrade is complete before retesting. Problem Explanation: Potential Performance issue has been identified related to a network node. Device Id is <SNE ID>. Resolution/Recommendation: Please inform the End User the VLAN Upgrade will be completed by {PEW End Date}. Please wait until Upgrade is complete before retesting. British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 78

79 BTWCE-65393: WBC FTTC G.Fast: T2R & Test and diagnostic support of G.Fast Variant 160/30 & 330/50 (DESIGN, REVIEW, BUILD, TEST and DEPLOY) British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 79

80 Broadband 90 day CP Notification Release BA Description and CP Interface Impacts Summary Broadband : BTWCE Description In this story, 21C NewKBD needs to support GEA service test for FTTC G.Fast product which is a new access product of Openreach. Possible answer to a question has been added. These changes apply to the 21CN FTTC G.Fast product only. CP Interface Impacts for 90 days Changes in KBD GUI Input Parameter Sheet Changes in KBD Initiate request xml. British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 80

81 Broadband 90 Day CP Notification Release BA Broadband : BTWCE Changes in possible answer options New KBD questi on Id New KBD question text Possible answers Next Step(question) FTTC 103:1 102:1 Product Type FTTP 103:1 SOGEA 103:1 FTTC G.Fast 103:1 British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 81

82 90 Day CP Notification - Release BA GUI Changes New KBD Release BA GUI : BTWCE For FTTC G.Fast access, 21C New KBD would display FTTC G.Fast under product info tab; This would be applicable for NewKBD test history as well. British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 82

83 90 Day CP Notification - Release BA GUI Changes New KBD Release BA GUI : BTWCE For FTTC G.Fast access, Performance test results would have Policy ID as FTTC G.Fast. This would be applicable for NewKBD test history as well. British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 83

84 90 day CP Notification - Release BA XML Changes New KBD Release BA XML : BTWCE and BTWCE B2B XML Changes For story BTWCE-65393; For FTTC G.Fast product, value for below tags would be FTTC G.Fast in KBD result. /kbdfinalresultnotification/kmtoolmessage/customer/profileinfo /kbdfinalresultnotification/kmtoolmessage/customer/productinfo /kbdfinalresultnotification/kmtoolmessage/testresults/ptresults/result/testbody/testdetai l/testconfiguration/policyid BBAC XML changes No changes. BBCR XML Reporting changes No changes. KBD XML changes For Story BTWCE-65393; Possible answer added for Q102:1. PFA updated KBD Initiate Request xml. Sentry Webservices changes No changes.. British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 84

85 90 day CP Notification - Release BA XML Changes New KBD Release BA XML : BTWCE and BTWCE New KBD outcome code sheet PFA the updated sheet New KBD Question list Possible answer added for Q102:1. PFA the updated sheet Updated ICD No changes. Modified KBD xsd No changes. British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 85

86 BTW BB 90 Day CP Notification - Release BA BTWCE WBC FTTC G.FAST: T2R & TEST AND DIAGNOSTIC SUPPORT OF G.FAST VARIANT 160/30 & 330/50 (DESIGN, REVIEW, BUILD, TEST AND DEPLOY) British Telecommunications plc Slide 86

87 BTW BB 90 Day CP Notification Release BA Description and CP Interface Impacts Summary BTWCE Description 1) This solution is to support all existing T2R journeys for new FTTC Variant, G.Fast. 2) For FTTC G.Fast, the new value for attribute PolicyId will be shown. And the new value will be FTTC G.Fast. British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 87

88 BTW BB 90 Day CP Notification Release BA Description and CP Interface Impacts Summary BTWCE CP Interface Impacts Portal Journey On BTW.com GUI, new value for PolicyID will be shown for PT Standalone test as FTTC G.Fast. Screenshot will be shared in 28 days CP Notification. British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 88

89 BTW BB 90 Day CP Notification Release BA Description and CP Interface Impacts Summary continued.. BTWCE CP Interface Impacts XML Journey For PT Standalone test from WS Sentry and B2B, the new value for PolicyID will be shown as FTTC G.Fast. PFA the sample GTCJ XML. British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 89

90 BTW BB 90 Day CP Notification Release BA XML Structural Changes (B2B, BBAC, BBCR, KBD, Sentry) BTWCE B2B XML Changes There is no change in the B2B Schema. British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 90

91 BTW BB 90 Day CP Notification Release BA XML Structural Changes (B2B, BBAC, BBCR, KBD, Sentry) continued.. BTWCE BBAC XML changes None BBCR XML Reporting changes None KBD XML changes Yes. KBD changes are covered separately in the CP Notification for KBD. Sentry Webservices changes No British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 91

92 BTW BB Early CP Notification Release BA BTW Story Design CP Impacts Category : L2C 21C Version : 3-0 Date : 16/Mar/16 British Telecommunications plc

93 CP Notification Criteria 90 Days 28 Days Any structural change to XML consumed by our CPs: B2B BBAC XML BBCR XML reports KBD XML Sentry Webservices Any change to XML content that makes the interface unusable for CPs Any new response codes: OneSiebel KBD Sentry Webservices Any change to online content: eco Plus (OneSiebel) BBAC GUI BBCR online reports Any change to XML data content e.g. new attribute values where the change does not make the interface unusable Any process changes that impact our CPs Changes to existing Response Codes WCR new report / measure WCR changes to existing attributes or data on the portal British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 93

94 BTW BB Early CP Notification - Release BA Stories covered: 1. BTWCE-60251: BUILD BB - Designed in AZ & BA - Expedite of a SoGEA order (OR ORCE 86309) N.B Design re-opened in BA to include POSE 2. BTWCE-60333: DESIGN ONLY BA- BUILD BB - SoGEA provide from existing FTTC ( ORCE ) 3. BTWCE : DESIGN ONLY BA - Build BB -SoGEA Cease Amend and Cease Cancel (ORCE-87421, 87495, 88090) 4. BTWCE DESIGN ONLY BA -BUILD BB SoGEA - WBC RT QoS product pricing and charging changes 5. BTWCE DESIGN ONLY - WBC FTTC G.Fast: Ability to modify an existing FTTC service between technologies (excluding appointing) (ORCE & BTWCE-69310) 6. BTWCE DESIGN ONLY BA - BUILD BB - SoGEA - L2C- Integration of QoS into the default configuration for SoGEA ( FV Programme CR34) 7. BTWCE BTW WBC FTTC G.Fast: All modify types (excluding change of access technology) operate on G.Fast variants in line with current FTTC. [Design Only] British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 94

95 BTW BB Early CP Notification targeted at Release BB BUILD BB - DESIGNED IN AZ & BA - EXPEDITE OF A SOGEA ORDER (OR ORCE 86309) N.B DESIGN RE-OPENED IN BA TO INCLUDE POSE BTWCE British Telecommunications plc Slide 95

96 BTW BB Early CP Notification targeted at Release BB Description and CP Interface Impacts Summary BTWCE Overview This story deals with SOGEA Expedites via Amends (inflight orders) and Point of Sale Expedite (PoSE). Expedite is defined as an effort to try and bring install/provision date within the lead time. Standard lead time for provide order would be 1 working day and 4 working days for integrated Order with Number Port. Product Affected: SOGEA Please note that It is advised to always book an appointment for an Expedite to ensure that a suitable slot is available and avoid unnecessary rejections due to unavailability when providing a CRD only. OR will accept Expedite orders placed with an Expedite appointment reference that is in excess of the Standard Lead Time. Note: you will still be charged Expedite charges in this case. British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 96

97 BTW BB Early CP Notification targeted at Release BB Description and CP Interface Impacts Summary BTWCE CP Interface Impacts CP should be able to raise the Point of sale Expedite orders and Amend the inflight orders. CP B2B Documentation will be updated in the build release (targeted at Release BB) and will include the Expedite XMLs. Portal Changes One Siebel GUI has no significant changes, the screens are similar to WBC FTTC Expedites. The amend reason should be selected as Customer requested Expedite and the Expedite Flag should be set to Y. British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 97

98 BTW BB Early CP Notification targeted at Release BB On-line Content Changes BTWCE B2B XML Changes CP B2B Documentation will be updated in the build release (targeted at Release BB) and will include the Expedite XMLs. BBAC XML changes None BBCR XML Reporting changes None KBD XML changes None Sentry Webservices changes None Impacted Documents None British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 98

99 BTW BB Early CP Notification targeted at Release BB Response Codes Changes BTWCE Changes to existing Response Code BTW Completion Code (Openreach response code) Old description None N/A N/A New description British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 99

100 BTW BB Early CP Notification targeted at Release BB Response Codes Changes BTWCE New error or response codes BTW Completion Code (OR response code) Description When will this be sent? No suitable POSE appointments If an appointment reference is not provided OR will attempt to book an Expedite appointment for the requested CRD and preferred slot (if provided),otherwise the PoSE order will be rejected Next-day POSE was after PONR If OR receive a PoSE order after 16:00 with a CRD of the next working day, the PoSE order will be rejected POSE rejected - network build If network build activity is required (such as the removal of DACS) the earliest available date is extended to cover the time required for the build activity. If a CRD less than the earliest available date is requested the PoSE order will be rejected POSE CRD is in the past If when OR receive the PoSE order and the CRD is in the past, it will be rejected POSE incl NP was less than MLT If a PoSE order with integrated number port is requested for a CRD less than 4 working days (minimum lead time for a number port), OR will reject the order British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 100

101 BTW BB Early CP Notification - (Build in release BB) BTWCE DESIGN ONLY BA- BUILD BB - SOGEA PROVIDE FROM EXISTING FTTC ( ORCE ) British Telecommunications plc Slide 101

102 BTW BB Early CP Notification - Release (Built in release BB) Description and CP Interface Impacts Summary BTWCE Description This story allows migration from existing WBC FTTC to WBC SOGEA service without a change of CP. Within BTW this will be a modify order on the existing service id of WBC FTTC. The solution also accepts the optional new order variants introduced as part of BTWCE-61809; Integrated Number Porting: An optional order to the potential SOGEA customers if they wish to retain installation DN linked with existing WBC FTTC and gets reassigned to the new SOGEA service. Controlled Cessation: An optional order to the potential SOGEA customers if they wish to cease existing GEA FTTC services. Flexible Appointing: An optional to book Flexible Appointing offered for the Modify Order. OR Time Related Charges: OR will send TRC details if a given CP has booked site visit reason as a Time Related Charge. Note: This design does NOT cover these optional variant designs; they are covered in BTWCE British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 102

103 BTW BB Early CP Notification - Release (Built in release BB) Description and CP Interface Impacts Summary BTWCE Description This story design follows the following Openreach design points, in summary; The scope of this story Working WLR3 PSTN + working GEA FTTC(VDSL) to SOGEA The service ID of GEA-FTTC service maybe used as the identifier in the SOGEA Order this service ID will be used internally within OR to derive the underlying WLR3 PSTN service. GEA-FTTC will be soft cease, creating a Managed Cease into BTW; new Cessation Reasons Change of CP & Change of Product Technology is applicable. If Number Port was included in the order then cessation reason used will be Synchronised Narrowband Stop. Cancel Other is not provided. The same Openreach Handover Port Service ID can be re-used or a new one may be provided. New response codes will be introduced for Customer Apparatus fault and Appointments being cancelled. Cease of GEA-FTTC will be a soft cease, leaving PCP jumpers in place and no PCP engineering work will be required. Amend of this modify journey should is supported through BTWCE NOTE : This is a design only story in release BA and build is in Release BB. This story does not cover CP migrations, which is covered in a future release. British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 103

104 BTW BB Early CP Notification - Release (Built in release BB) BTWCE Description and CP Interface Impacts Summary CP Interface Impacts CP B2B Documentation will be updated to include the WBC SOGEA Modify PFM xmls. This will be shared during build release (targeted for Release is BB ). Portal Changes No impacts to Portal. All newly introduced WBC SOGEA order variants and its corresponding screen mock-ups will be available as part of BTWCE Note : LOV for Site Visit Not Applicable will be removed from the B2B and OS Portal in this design. British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 104

105 BTW BB Early CP Notification - Release (Built in release BB) XML Structural Changes (B2B, BBAC, BBCR, KBD, Sentry) BTWCE B2B XML Changes CP B2B Documentation will be updated to include the WBC SOGEA PFM xmls. This will be shared during build release (targeted for Release BB). Please note the example xmls above are to provided as a heads ups only for this design and its subjected to change during the build release in release BB. BBAC XML changes None BBCR XML Reporting changes None KBD XML changes None Sentry Webservices changes None British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 105

106 BTW BB Early CP Notification - Release (Built in release BB) XML Content Change BTWCE XML Content Change BTW Completion Code Description N/A N/A N/A When will this be sent? Note : B2B XML have no changes and remain the same as introduced in BTWCE British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 106

107 BTW BB Early CP Notification - Release (Built in release BB) Response Codes New (OneSiebel; KBD; Sentry) BTWCE Note : The response codes for WBC SoGEA Provide are applicable for this journey. The list provided below contains those responses applicable to CP s that are newly introduced. WBC SoGEA Cease error or response codes BTW Completion Code Description An existing issue with the Customer Apparatus has been detected on this line. This may impact the new service. The appointment has been cancelled as no engineering visit is required for this order. When will this be sent? OR Response code 9712 is sent when there is a customer apparatus fault detected on the line. This message goes back to CP s as informational. CP s may decide to ignore them if they had their own engineers who could fix the issue. If they had a SVR on the order then OR Engineer will clear the fault else they can place an Amend to add SVR onto the order. OR Response code 9724 is when OR have found that the order placed in reality does not need an appointment; this also goes on the back of an information message British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 107

108 BTW BB Early CP Notification - (Build in release BB) BTWCE DESIGN ONLY BA - BUILD BB -SOGEA CEASE AMEND AND CEASE CANCEL (ORCE-87421, 87495, 88090) British Telecommunications plc Slide 108

109 BTW BB Early CP Notification - Release (Built in release BB) Description and CP Interface Impacts Summary BTWCE Description This story allows the WBC SOGEA Cease order to be cancelled or amended by CP s. This story also introduces a response from Openreach for a cease of WBC SOGEA during a parallel running period. Cancelation request for WBC SOGEA is similar to WBC FTTC. The request must be received before the PONR within BTW. Cease of a WBC SOGEA with regards to parallel running period; If a cease of WBC SOGEA is received within the parallel running period (7 days) then upon KCI1 receipt CP will receive first a delay message indicating there is a possibility of parallel running period which then could be followed by a rejection message upon OR rejection. If a rejection is not received after the delay message then it means the Cease order can progress and parallel running is not in effect. Amends of a cease order; Only CRD amends are possible for WBC SOGEA Cease order. NOTE : This is a design only story in release BA and build is in Release BB. British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 109

110 BTW BB Early CP Notification - Release (Built in release BB) BTWCE Description and CP Interface Impacts Summary CP Interface Impacts CP B2B Documentation will be updated to included the WBC SOGEA Cancel and Amend xmls. This will be shared during build release (targeted for Release is BB ). Portal Changes No impacts to Portal. British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 110

111 BTW BB Early CP Notification - Release (Built in release BB) XML Structural Changes (B2B, BBAC, BBCR, KBD, Sentry) BTWCE B2B XML Changes CP B2B Documentation will be updated to include the Amend and Cancel xmls. This will be shared during build release (targeted for Release BB). Sample attached below for reference Please note the example xmls above are to provided as a heads ups only for this design and its subjected to change during the build release in release BB. BBAC XML changes None BBCR XML Reporting changes None KBD XML changes None Sentry Webservices changes None British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 111

112 BTW BB Early CP Notification - Release (Built in release BB) XML Content Change BTWCE XML Content Change BTW Completion Code Description N/A N/A N/A When will this be sent? Note : B2B XML have no changes and remain the same as introduced in BTWCE British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 112

113 BTW BB Early CP Notification - Release (Built in release BB) Response Codes New (OneSiebel; KBD; Sentry) BTWCE Note : All the response codes published as part of BTWCE will be applicable for this journey for the amend and cancel calls, the response codes below are those specifically introduced for the BTW SOGEA Cease journey to handle parallel running checks. WBC SoGEA Cease error or response codes BTW Cancellation /Delay Code Description Service is still within the parallel running period. This order is being delayed due to the possibility of parallel running, please await a further update. When will this be sent? This order is rejected. A migration cannot be requested at this time as the existing SOGEA service is still in a period of parallel running. The WBC SOGEA Cease order was received within the parallel running period at present configured to 7 days. Hence there will be additional checks, this make take up to 4 hours within Openreach. British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 113

114 BTW BB EARLY CP Notification - Release BA BTWCE [DESIGN ONLY BA -BUILD BB SOGEA - WBC RT QOS PRODUCT PRICING AND CHARGING CHANGES] AND BTWCE [DESIGN ONLY BA - BUILD BB - SOGEA - L2C- INTEGRATION OF QOS INTO THE DEFAULT CONFIGURATION FOR SOGEA ( FV PROGRAMME CR34)] British Telecommunications plc Slide 114

115 BTW BB EARLY CP Notification - Release BA BTWCE & BTWCE PLEASE NOTE THAT THIS IS AN EARLY NOTIFICATION FOR BTWCE AND BTWCE AS BOTH THE STORIES ARE DESIGN ONLY IN RELEASE BA, TARGETTED BUILD IN RELEASE BB. British Telecommunications plc Slide 115

116 BTW BB EARLY CP Notification Release BA Description and CP Interface Impacts Summary BTWCE & BTWCE Description As part of Release BA story BTWCE (DESIGN ONLY BA - BUILD BB - SoGEA - L2C- Integration of QoS into the default configuration for SoGEA ( FV Programme CR34) ), the Real Time QoS default configuration for all WBC SoGEA End -User orders would be 220kbits/sec as distinct from 0kbits/sec for FTTC. CPs who provide critical applications such as derived voice can mark their priority downstream and upstream traffic and reduce the risk, that this traffic is not dropped under contended Core Network conditions. By exposing this functionality, CP s will be able to provide default RTQoS of 220Kbits/sec to EU s for SoGEA orders. Higher RT QoS bandwidth settings are selectable and chargeable. The companion story BTWCE (DESIGN ONLY BA -BUILD BB SoGEA - WBC RT QoS product pricing and charging changes) manages the Pricing of the bundling of RT QOS with WBC End User Access charges for SOGEA. British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 116

117 BTW BB EARLY CP Notification Release BA Description and CP Interface Impacts Summary BTWCE & BTWCE CP Interface Impacts The default value of Real Time Bandwidth for WBC EUA SOGEA Orders would be 220kbits/sec. Higher RT QoS bandwidth settings are selectable and chargeable. CPs will not be able to select 0kbits/sec Real Time bandwidth for access technology SOGEA. The 220kbits/sec is enabled by default and there is no extra charge for this on WBC SOGEA. (unlike FTTC). British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 117

118 BTW BB EARLY Day CP Notification Release BA Description and CP Interface Impacts Summary BTWCE & BTWCE Portal Changes The default Real Time Bandwidth would be 220kbits/sec for SOGEA Orders ecoplus Portal ****Details would be covered as part of 28 days CP notification Slide Pack. British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 118

119 BTW BB EARLY CP Notification Release BA XML Structural Changes (B2B, BBAC, BBCR, KBD, Sentry) BTWCE & BTWCE B2B XML Changes : If B2B sends RTQoS as 0Kbits/sec for SoGEA order, then OS will validate it and reject the request with error code 2000 This is an existing generic error code for all validations of Product Model attributes. BBAC XML changes None BBCR XML Reporting changes None KBD XML changes None Sentry Webservices changes None British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 119

120 BTW BB EARLY CP Notification Release BA BTWCE & BTWCE Reporting changes None British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 120

121 BTW BB EARLY CP Notification Release BA Response Codes New (OneSiebel; KBD; Sentry) BTWCE & BTWCE New error or response codes BTW Error Code Error Reason When will this be sent? 2000 Run Time Error Message generated If B2B sends RTQoS as 0K for SoGEA order, then OS will validate it and reject the request with error code 2000 British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 121

122 BTW BB Early CP Notification - Release BA BTWCE DESIGN ONLY - WBC FTTC G.FAST: ABILITY TO MODIFY AN EXISTING FTTC SERVICE BETWEEN TECHNOLOGIES (EXCLUDING APPOINTING) (ORCE & BTWCE-69310) British Telecommunications plc Slide 122

123 BTW BB Early CP Notification Release BA BTWCE Overview Description and CP Interface Impacts Summary This story supports modify journey for technology change within FTTC service where in it is a modify of bandwidth from VDSL speed to G.Fast speed and vice versa i.e. Modify from FTTC VDSL to FTTC GFAST (upgrade) Modify from FTTC G.Fast to FTTC VDSL (downgrade) British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 123

124 BTW BB Early CP Notification Release BA Description and CP Interface Impacts Summary BTWCE CP Interface Impacts 1) User would need to book appointment for these modify of technology change as these modify journey are appointed journey because site visit would be required either to customer premises and/or to PCP. 2) OpenreachModem, PCPOnly and Managed Install modules would be modifiable attribute for these order journeys and allowed values are as below: 1) VDSL to G.Fast ORModem= Yes/No, PCPOnly = Yes/No 2) G.Fast to VDSL ORModem =No, PCPOnly= Yes/No 3) Below mentioned details are additional for this modify journey and required to be filled. Highlighted ones in bold are mandatory for this modify. Validations for these attributes is similar to as present in Provide journey. Hazard Notes, PCPOnly, OpenreachModem, Site Visit Notes, site Visit Contact Name, Site Contact Telephone, Secondary Site Contact Telephone, Site Contact , Special Arrangement Notes, Access Password, Modules Ordered, Appointment Reference, Appointment Slot. 4) Changes in B2B XMLs for additional attributes to be sent. 5) For PCPOnly=N, Site Contact Name and Site Contact Telephone is mandatory. 6) Modify charges for this modify would be different from normal modifies and would be shared later during next release. 7) Lead time for these modify orders would be 5 days. 8) If appointment reference expires, is invalid or not has been booked then new appointment would be booked and send back in KCI2. British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 124

125 BTW BB Early CP Notification Release BA On-line Content Changes BTWCE B2B XML Changes XML changes to send additional attributes i.e. Hazard Notes, PCPOnly, OpenreachModem, Site Visit Notes, site Visit Contact Name, Site Contact Telephone, Secondary Site Contact Telephone, Site Contact , Special Arrangement Notes, Access Password, Modules Ordered, Appointment Reference, Appointment Slot. Sample Code Snippet as mentioned below: British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 125

126 BTWCE BTW BB Early CP Notification Release BA On-line Content Changes B2B XML Changes. Sample Code Snippet as mentioned below: British Telecommunications plc CP Notification 90-Day Template v2-0 Slide 126