Chorus Portal System Changes November 2019

Overview What are we doing When In preparation for a Chorus unbundled fibre product being launched at the start of January 2020, Chorus is making a number of small changes to the Chorus Portal. The changes outlined in this pack will be visible to RSPs but not used in any order processing until Chorus launches its unbundled fibre products. This pack focuses on the changes that will be made to B2B web services For the most part the B2B web services associated with the PONFAS distribution product will work in the same way as layer 2 bitstream products. This pack outlines the changes made to support PONFAS distribution Examples of the updates XML is included in the appendix. When We are looking to put these changes in production on 9 November 2019 Changes will be visible in EMMA on 17 September Customers will need to ensure that the changes being introduced will not impact any current ordering processes for existing Chorus products.

Customer Changes (Unbundled Products) What happens today What the changes mean for you The B2B call QueryProductOfferAvailability does not reflect the ‘unbundling capable’ value The QueryProductOfferAvailabilityResponse.xslt has been updated to make use of a new “Unbundling_Capable” value from the Product Query Dialogue Service (PQDS) ProductOfferAvailabilityCheckResponse and populate this into the B2BDS QueryProductOfferAvailabilityResponse as a new ProductOfferingInteractionItemDetail element with a ‘name’ of “Unbundling_Capable” The response value will be either “Y” or “N” This value will be returned from 9 November PONFAS Distribution is not a supported product family for current B2B queries Any logic which attempts to validate or otherwise restrict functionality or the information that can be supplied or returned to specific Product Families only (i.e. 'Bitstream' or 'CSE') must be updated to include 'PONFAS_DISTRIBUTION" as a valid Product Family and treat it the same as 'Bitstream‘. This includes the query ProductOfferAvailability Family Type filter to include PONFAS_DISTRIBUTION” PONFAS Distribution will not use the current 1637xxxxxx product ID range The PONFAS Distribution product will use the product ID range 1381000000-1381999999. The retain copper attribute is currently limited to the Bitstream product family The existing GetOrder function / XSLT (which is used by many B2B functions to fetch COM Order data used for request validation & processing) should be updated to ensure it is not limited to 'Bitstream' and must be updated to also apply to 'PONFAS_DISTRIBUTION' Valid handover connections are returned for Bitstream product family as part of the QueryOrderFeasibilityResponse Where a Feasibility request is for an Unbundled Fibre (PONFAS Distribution) Product Offer the ‘handover connections; section of the QueryOrderFeasibilityResponse will be blank

Customer Changes (Unbundled Products) What happens today What the changes mean for you A B2B exception code does not exist for CSE and product offer compatibility exceptions A new B2B exception code (080) is included with the queryOrderFeasibility function and will be returned by the createorder response where the product offer and CSE are not compatible Where {%s} is a variable to be replaced by the description value returned by the createOrder response – “CSE Validation Failure: The selected CSE is not compatible with the Product Offer ordered.” A CSE is not required for a disconnect bitstream order aim The disconnect order aim for a PONFAS distribution offer will require a mandatory CSE. The queryOrderFeasibility has been updated with a new exception code (081) returned by the createorder response Where {%s} is a variable to be replaced by the description value returned by the createOrder response – “CSE Validation Failure: Disconnect Primary PONFAS Distribution Orders must include a CSE Offer.”

Appendix (B2B XML Examples) B2B Web Service Example XML 1a queryProductOfferAvailability – Unbundling Capable = Y (Request/Response) 1b queryProductOfferAvailability – Unbundling Capable = N (Request/Response) 1c queryProductAvailability – New product family and PONFAS product offer returned (Request/Response) 1d queryProductAvailability – New product family and PONFAS no product offer(s) returned (Request/Response) 2a queryOrderFeasibility – Handover ID’s not returned (Request/Response) 2b queryOrderFeasibility – Invalid CSE exception 080 returned (Request/Response)

Appendix (B2B XML Examples) B2B Web Service Example XML 2c queryOrderFeasibility – Disconnect Primary with no CSE exception 081 returned (Request/Response) 3a querySiteInformation – PONFAS product only so no ONT ID or ONT Status returned (Request/Response) 3b querySiteInformation – PONFAS product at the location. Example response where RSP owns and does not own the product (Request/Response) 4a createOrder – With a PONFAS product offer (Request/Response) 5a queryOrder – For a PONFAS order (Request/Response)

Appendix (B2B XML Examples) B2B Web Service Example XML 6a amendOrder – For PONFAS order (Request/Response) 7a Service Given Notification – For PONFAS order