Chorus System and Operational Changes External Customer Change

Chorus System and Operational Changes External Customer Change Pack Proposed for Dec 2020

Overview What are we doing • To support the Chorus ONT RGW full release, a number of Chorus systems will need updating. This pack outlines the Chorus Portal and B 2 B changes. • Examples of the updated XML is included in the appendix on the last page. When is the happening? • • We are requesting that you assess the impact of these changes, including confirmation of whether this will impact your current ordering systems/processes by 4 September. We are looking to put these changes in production targeting the 4 th December 2020 and need an impact assessment from you to confirm that you will either be able to make the changes; or that not making the changes won’t affect your ability to order Chorus products through your usual channels. What we need from you Customers will need to ensure that the changes being introduced will not impact any current ordering processes for existing Chorus products. As this year has been particularly difficult with the global pandemic, lockdowns and all the other challenges that COVID-19 has created, we would like you to please review the changes and conduct an impact assessment. We’d like to know if you are able to make the changes within the timeline indicated in the pack. If not, then we would like to understand if these changes would impact any of your current processes. Please confirm with your Service Delivery Manager by COB on 4 September 2020. What other systems are impacted • There will also be changes to Assurance Website and API. These are not covered in this pack and will be communicated separately. • The Line Test API will also be updated to include RGW results with new fields. • We are introducing a Remote Management Service that will configure the routing capability of compatible ONTs. This will initially be available as a website and later introduced as an API.

Customer Changes – UNI Port Display Changes What happens today What the changes mean for you RGW Change 1 (Port Display Changes) The port information available today shows UNI or AT but does not show the types of port available When using the Portal SSP the order entry screen will show advanced information for the type of UNI port available. These will now be ‘ 1 G’ or ‘ 10 G’ or ‘RGW’ If the ONT has been configured to ‘RGW’ this will be reflected with Mode being ‘RGW’. The new characteristics will also be seen for any in-flight orders. The Query. Site. Information response will be updated to reflect if the UNI is ‘ 1 G’ or ‘ 10 G’ or ‘RGW’ <Product. Characteristic> <name>UNI_PORT_TYPE</name> <value>1 G</value> </Product. Characteristic> The same changes will also be applied to any Hyperfibre offers plus any completed orders.

Customer Changes – UNI Port Display Changes What happens today What the changes mean for you RGW Change 1 continued (Port Display Changes) The port information available today shows UNI or AT but does not show the types of port available Intact ONT with spare ports Location with multiple ONT’s and active services

Customer Changes – Pre-feasibility characteristics What happens today What the changes mean for you RGW Change 2 (Pre-feasibility characteristics) Chorus does not support the configuration of the ONT in RGW mode Other than for ONT’s that support Chorus Hyperfibre offerings the ONT mode is always configured to ‘standard’. When entering an order using the Portal SSP additional pre-feasibility offer characteristics will need to be provided before the order is submitted. The ONT Mode will be required. The values will be either ‘Standard’ or ‘RGW’. Chorus will default this value as ‘Standard’. If an RSP needs the ONT configured in RGW mode the default ONT mode will need to changed to ‘RGW’ N. B. The Chorus Hyperfibre ONT can already be configured in RGW mode Pre-feasibility characteristics will ONLY be required for offers that support the ONT being configured as ‘Standard’ or ‘RGW’. A list of offers that can be ordered in ‘RGW’ mode will be provided. Query. Product. Offer. Availability: response will now include the ONT modes that are supported ‘Standard’ or ‘RGW’ but only for relevant offers that support this. Query. Order. Feasibility: request. Chorus will default the ONT mode to ‘Standard’. This will need to be overridden and the ONT mode requested as ‘RGW’ Query. Order. Feasibility: response. The ONT mode selected will be returned. Only two options are ‘standard’ and ‘RGW’. If the configuration of the ONT in ‘RGW’ requires an ONT, swap the need for a site visit will also be returned. For in-flight orders the ONT Mode will be visible. <Order. Feasibility. Result. Item. Detail> <name>ONT_MODE</name> <value>RGW</value> </Order. Feasibility. Result. Item. Detail> If a feasibility request is submitted with a value that does not match ‘RGW’ or ‘Standard’ an exception will be returned Code 026 (Request Validation Failed) Message{%} Characteristic [name: ONT_mode, value: RGWW] out of range Meaning The ONT mode requested is not valid

Customer Changes – Pre-feasibility characteristics What happens today What the changes mean for you RGW Change 2 Continued (Pre-feasibility characteristics) Other than for ONT’s that support Chorus Hyperfibre offerings the ONT mode is always configured to ‘standard’. Create Order screen updated for any offers that support the ONT being configured in ‘RGW’ mode and needing prefeasibility characteristics. If an existing service/offer is going to be configured as ‘RGW’ the update must be submitted as a change offer.

Customer Changes – Pre –feasibility characteristics What happens today What the changes mean for you RGW Change 2 Continued (Pre-feasibility characteristics) Other than for ONT’s that support Chorus Hyperfibre offerings the ONT mode is always configured to ‘standard’. Pre-feasibility characteristics options with the default being ‘standard’. Normal order submission will be after the ONT mode has been selected. N. B. Pre-feasibility characteristic value cannot be amended in an in-flight order once the Feasibility step is completed.

Customer Changes – Secondary Services What happens today What the changes mean for you RGW Change 3 (Secondary Services) Secondary offers are supported on the majority of current Chorus ONT’s If an ONT has been configured in RGW mode it will not be possible to configure a secondary service as RGW mode uses all 4 UNI ports. The order will be rejected during the feasibility in Portal SSP and the reason for the rejection provided. If the ONT already has a working secondary service it will not be possible to request an offer that configures the ONT in ‘RGW’ mode. The Query. Order. Feasibility: response will return a new exception. <Order. Feasibility. Result. Item. Detail> <name>FEASIBILITY_CODE</name> <value>997</value> </Order. Feasibility. Result. Item. Detail> <name>FEASIBILITY_REASON</name> <value>The current ONT mode does not support this</value> </Order. Feasibility. Result. Item. Detail> Code 997 Message {%} The current ONT mode does not support this Meaning If the ONT is RGW mode a secondary service can not be ordered

Customer Changes – Voice Characteristics What happens today What the changes mean for you RGW Change 4 (Voice Characteristics) All current Chorus offers support voice services During order entry using the Portal SSP if the ONT mode is selected as ‘RGW’ (during pre-feasibility) voice related characteristics will not be available for selection. In addition UNI Tagging must be set to ‘Tagged’ If the Create. Order: request or Amend. Order: request includes a voice characteristic the order will be rejected and a new exception code returned. This includes UNI tagging being requested as ‘Untagged’ <code>026</code> <description>Product. Characteristic VOICE_HANDOVER_CONNECTION_ID does not belong to Product. Offer</description> <reference>//Order. Item/Product. Offering/Product. Characteristic</reference> Code 026 Message {%} VOICE_HANDOVER_CONNECTION_ID does not belong to Product. Offer Meaning A voice service is not supported when configuring an ONT is RGW mode

Customer Changes - Billing What happens today What the changes mean for you RGW Change 5 (Billing) Billing does not indicate how the ONT is configured If an order is completed and the ONT mode configured as ‘RGW’ a new line item will be shown in the order charges screen. The Amend. Order. Notification: Completed_billing will include a new reference for ‘ONT Mode’ The Amend. Order: response & Create. Order: response will include applicable one off charges for an ONT swap and recurring charges for the RGW service

Customer Changes – Resource Exhaustion What happens today What the changes mean for you RGW Change 6 (Resource Exhaustion) When placing an order today the suitability of free ports on the ONT to support the request can’t be determined. Orders are only cancelled after order submission If an order is submitted on ONT where the resources required are exhausted (e. g. secondary ATA services on type 300 ONT) this will either a trigger an ONT swap if an alternative ONT can be used or the request will be determined to be not feasible The Query. Order. Feasibility: response will be updated with a new exception reason Code 026 Message No free suitable ports are available to support this request Meaning No order can be submitted This will mean that the 3 rd Gen ONT Blocking service (used to identify that there is no 2 nd ATA on 3 rd Gen ONTs) will no longer be required so all instances of this service will be removed.

Appendix (B 2 B XML Examples) B 2 B Web Service RGW Change 1 RGW Change 2 RGW Change 3 RGW Change 4 RGW Change 5 RGW Change 6 Example XML