operations manual for bitstream services reference offer

Chorus UFB Services Agreement Bitstream Services: Operations Manual for Bitstream Services Reference Offer July 2021

Bitstream Operations Manual July 2021

Chorus UFB Services Agreement Page i

Document Version History

Version Date Author Description of Change

1.0 November 2011 Alan Mitford-Taylor Original UFB contract document

2.0 June 2013 Alan Mitford-Taylor Multiple sections updated.

3.0 June 2015 Alan Mitford-Taylor MDU section updated

4.0 June 2018 Alan Mitford-Taylor Forecasting section updated

Standard Install section updated

Other sections updated to reflect new SLA regime

5.0 October 2020 Alan Mitford-Taylor Sections updated to reflect addition of UFB2

6.0 July 2021 Alan Mitford-Taylor

Alan Boniface

Karmen Mai

Exchange table updated

Added glass only service terminations.

Added single fibre working details.


Chorus UFB Services Agreement Page ii

TABLE OF CONTENTS PART 1 - DOCUMENT INFORMATION .................................................................................................... 1

1 Introduction ................................................................................................................................................ 1 2 People and Contact Details ....................................................................................................................... 1 3 Technical Manuals and User Guides ......................................................................................................... 4 4 Good Faith and Dispute Resolution ........................................................................................................... 4 5 Prerequisites .............................................................................................................................................. 5

PART 2 – FORECASTING ........................................................................................................................ 6 6 Service Provider Forecasting ..................................................................................................................... 6

PART 3 - PRE-QUALIFICATION AND PROVISIONING ........................................................................... 8 7 The OSS/BSS System ............................................................................................................................... 8 8 Pre-qualification ....................................................................................................................................... 12 9 Service Requests Processing .................................................................................................................. 14

PART 4 - PROBLEM MANAGEMENT ..................................................................................................... 22 10 OSS/BSS ................................................................................................................................................. 22 11 Faults ....................................................................................................................................................... 22

PART 5 – STANDARD BITSTREAM SERVICE INSTALL AND TERMINATION POINTS ...................... 27 12 Installation Services ................................................................................................................................. 27

PART 6 - CONSENTS PROCESS ........................................................................................................... 33 13 Consents for a Single Dwelling Unit (SDU) and an End User Tenancy (MDU Tenancy) in an MDU ....... 33 14 Complex Multi Dwelling Unit (MDU) Consents ........................................................................................ 42 15 Non-Building Access Point (NBAP) Consents ......................................................................................... 50

PART 7 – HANDOVER CONNECTION AND TIE CABLE INSTALLATION ............................................. 57 16 Handover Connection .............................................................................................................................. 57 17 Tie Cable Installation ............................................................................................................................... 58

PART 8 – SERVICE TEMPLATES AND THE PRODUCT DEVELOPMENT PROCESS ........................ 59 18 Service Templates ................................................................................................................................... 59 19 Building Blocks ........................................................................................................................................ 59 20 Product Development Process ................................................................................................................ 62 21 Prioritisation Process ............................................................................................................................... 63 22 Development of New Templates .............................................................................................................. 63 23 Integrated Test Facility ............................................................................................................................ 66

PART 9 – FIBRE DIVERSITY .................................................................................................................. 68 24 Diversity via additional service instances ................................................................................................. 68

PART 10 - BILLING ................................................................................................................................. 74 25 Billing ....................................................................................................................................................... 74

PART 11 – OPERATIONAL READINESS PROGRAMME ...................................................................... 75 26 Service Provider on Boarding .................................................................................................................. 75

PART 12 – MDU Connection Process ..................................................................................................... 79 27 Introduction .............................................................................................................................................. 79

PART 13 – OTHER .................................................................................................................................. 83 28 Requirements for End User Site Visits by the LFC .................................................................................. 83 29 Premises Wiring, ONT and Approved CPE Installation ........................................................................... 83 30 Premises Lead-in Fibre Installation .......................................................................................................... 84 31 Marketing Support and Roll out Plans ..................................................................................................... 84 32 Lawful Intercept ....................................................................................................................................... 85

PART 14 – LAYER 2 TRAFFIC PERFORMANCE ................................................................................... 86 33 Layer 2 Performance Measurement ........................................................................................................ 86

APPENDIX A – GLOSSARY ......................................................................................................................................... 92

APPENDIX B - ESCALATION PROTOCOL ................................................................................................................ 106

APPENDIX C - FORECASTING SPREADSHEET ...................................................................................................... 107

APPENDIX D - TECHNICAL SPECIFICATION ........................................................................................................... 108

APPENDIX E -– CANDIDATE AREAS, CENTRAL OFFICES AND POIs .................................................................. 112


Chorus UFB Services Agreement Page 1 of 134

PART 1 - DOCUMENT INFORMATION

1 Introduction 1.1 This Operations Manual (Manual) is part of the WSA and sets out the operational

processes and procedures for supply of the Bitstream Services.

1.2 This Manual should be read in conjunction with the other documents which make up the WSA, in particular the General Terms.

1.3 This Manual may be changed in accordance with the change mechanism set out in clause 24 of the General Terms.

1.4 The LFC will make the current version of this Manual available on the LFC website accessible by the Service Provider.

1.5 References to Service Level Terms are references to the Service Level Terms for Bitstream Services.

1.6 References to clauses or sections are references to clauses or sections in this Manual unless expressly provided otherwise. The Glossary (Appendix A) sets out definitions for terms contained in this Manual that are not defined in the General Terms. Otherwise, the definitions set out in the General Terms apply.

2 People and Contact Details 2.1 Immediately following the issue of the first Service Request for a Bitstream Service by

the Service Provider, the Service Provider and the LFC must provide each other with the people and contact details set out in clause 2.2. Any change to the people or contact details must be advised in writing to the other party's principal point of contact. All people and contact details will remain valid until a party has advised the other in writing of a change (and provided an updated list of people and contact details).

2.2 People and Contact Details

Contact and detail required Purpose

Both parties provide Principal point of contact for Bitstream Services. (This must include the principal point of contact's email address, mobile and work telephone numbers.)

This is the person responsible for the overall relationship between the parties with respect to the Bitstream Service. For the LFC this will usually be the Account Manager for the relevant Service Provider.

The LFC only provides Service Delivery Manager. (This must include the Service Delivery Manager's email address, mobile and work telephone numbers.)

This is the person responsible for service delivery of the Bitstream Service to the Service Provider.



The LFC only provides Provisioning Manager. (This must include the Provisioning Manager's email address, mobile and work telephone numbers.)

This is the person responsible for the provisioning of the Bitstream Service to the Service Provider.

The LFC only provides Email address for submission of Forecasts.

This is the email address to which the Service Provider must send Forecasts.

Service Provider only provides Provisioning and Forecasting Manager. (This must include the provisioning and forecasting manager's email address, mobile and work telephone numbers.)

This is the Service Provider's counterpart to the LFC provisioning manager.

Service Provider only provides Names and email addresses of one or two people to become OSS/BSS and OSS/BSS user administrators.

These people will manage the creating and disabling of Service Provider staff accounts to access the OSS/BSS and OSS/BSS websites.

Service Provider only provides People who are authorised to download eBill files.

These are the people who will be set up with access to the LFC’s secure web portal from which the Service Provider's eBills can be viewed and downloaded.

Service Provider only provides People who are authorised to download the Price List file.

These are the people who will be set up with access to the LFC’s secure web portal where the Bitstream Price List file can be viewed and downloaded.

Service Provider only provides Service Requests confirmation email address.

This is the email address to which the LFC will send confirmation of Service Requests in cases where the Service Provider has submitted a provisioning request via email.

The LFC only provides Fault reporting contact details. (This

These are the contact details the



must include an 0800 fault reporting service number.)

Service Provider must use for the reporting of faults in instances where the LFC has advised that OSS/BSS is unavailable under clause 11.7 below.

The LFC only provides Business continuity email address.

This is the email address to send forms to under clauses 7.27 to 7.30.

The LFC only provides Billing team email address.

This is the email address to which the Service Provider will send billing queries under clause 24.7.

Service Provider only provides Name, email address, mobile and work telephone number of person the LFC should respond to for billing queries.

This is the email address to which the LFC will respond in relation to billing queries.

Service Provider only provides Contact for faults. (This must include a name, email address and mobile and work telephone numbers.)

This is the contact the LFC will deal with in respect of faults.

Service Provider only provides Contact for Service Level and any other performance reports generated by the LFC. (This must include a name, email address and mobile and work telephone numbers.)

This is the contact the LFC will send Performance Reports to.



3 Technical Manuals and User Guides 3.1 This Manual refers to various technical manuals (including published New Zealand and

international standards) and user guides that contain technical and procedural detail. Such reference is necessary for both the Service Provider and the LFC so that:

(i) uniform standards of best practice are set;

(ii) the performance of the LFC Network can be maintained;

(iii) the health and safety of the Service Provider's and the LFC’s employees, contractors and other agents can be protected;

(iv) systems are in place for the management of outages, faults and any work the Service Provider or the LFC need to undertake; and

(v) the Service Provider's and the LFC’s employees, contractors and other agents have access to uniform technical instructions.

3.2 To the extent that this Manual creates any obligation to comply with a technical manual or user guide, the Service Provider and the LFC must:

(i) apply the technical manual or user guide under the terms of the Agreement in good faith;

(ii) interpret the technical manual or user guide consistently with the terms of the Agreement; and

(iii) comply with the technical and/or procedural detail the technical manual or user guide contains, to the extent it is relevant under the circumstances.

3.3 Electronic copies of all the relevant LFC technical manuals and user guides will be made available to the Service Provider via the LFC website as soon as practicable after the issue of the first Service Request for a Bitstream Service by the Service Provider or following an earlier request from the Service Provider. New Zealand and international standards are available from appropriate suppliers in New Zealand and around the world.

4 Good Faith and Dispute Resolution 4.1 The parties will deal with each other in good faith in relation to this Manual. The parties

will act co-operatively and in good faith to facilitate the processes and procedures required for supply of the Bitstream Services.

4.2 Subject to clause 4.3, any dispute, question or difference that arises between the parties should be dealt with in accordance with the Escalation Protocol in Appendix B in the first instance, and the parties will use reasonable endeavours to do so.

4.3 The most efficient mechanism for resolving any dispute in relation to a particular issue that is of a technical, operational or implementation nature, requiring significant investigation of factual matters is expected to be escalation in accordance with Appendix B, but neither party is precluded from issuing a dispute notice under clause 20.2 of the General Terms at any time.



5 Prerequisites 5.1 In addition to the commercial prerequisites set out in clause 2.2 in the General Terms,

the Service Provider must satisfy the following operational prerequisites in relation to the Bitstream Service.

(i) execution of the WSA;

(ii) set up of the OSS/BSS so that Service Requests can be placed;

(iii) Service Provider staff are trained in the use of OSS/BSS to place and track Service Requests and faults;

(iv) build of first handover connection and associated direct fibre, backhaul or tie cable (if required);

(v) build of first co-location footprint (if required); and

(vi) place a forecast of expected demand (optional).

5.2 The Service Provider and the LFC may enter into a non-disclosure agreement covering discussions prior to the Service Provider placing a Service Request for a Bitstream Service (but neither the LFC nor the Service Provider will be under any obligation to do so).

5.3 The Service Provider Operational Readiness Programme in Part 11 will be followed for the set up of a new Service Provider involving (as required) the establishment of commercial relationships, co-location, OSS/BSS interfaces, interconnection links and layer two interoperability.

5.4 Prior to placing each individual Service Request with the LFC, the Service Provider must ensure the Technical Interface Specification set out in Appendix D is complied with.

5.5 The Service Provider must ensure that the prerequisites specified in this clause 5 are complied with on an on-going basis (including, where applicable, in respect of each Bitstream Service) while that Service Provider continues to receive the Bitstream Service.



PART 2 – FORECASTING

6 Service Provider Forecasting Introduction

6.1 Forecasting is required from the Service Providers to ensure that the LFC has the resources in terms of network capacity, technicians and materials to efficiently meet the volume of Service Requests within the agreed Service Levels set out in the Service Level Terms for Bitstream Services. This takes the form of a rolling monthly volume forecast by each Service Provider, provided through the completion and submission to the LFC of Forecasting Reports in accordance with clause 11 of the General Terms and as further described in this clause 6.

6.2 The Service Provider must use all reasonable endeavours to provide the LFC with accurate Forecasts.

6.3 The Service Provider’s Forecasts are Confidential Information for the purposes of clause 15 of the General Terms.

6.4 In this clause 6:

Forecast Coverage Area means a Candidate Area;

Forecast Service Request means a future Service Request that the Service Provider is forecasting it will make in the Service Request Month, as reported in a Forecasting Report;

Forecasting Report has the meaning given in clause 11.1 of the General Terms;

Month [x] means the calendar month that is x calendar months before a Service Request Month; and

Service Request Month means the calendar month in which a Forecast Service Request is forecast to become a Service Request.

Forecasting Reports

6.5 Within the period of 10 Business Days following the last day of each calendar month, the Service Provider will submit to the LFC a Forecasting Report for the period commencing on the first day of the following month in the manner and form prescribed by the LFC from time to time (a sample is available on the LFC website), provided that any changes to the manner and form are no more onerous for the Service Provider (acting reasonably) than existed prior to such change.

6.6 Each Forecasting Report is to set out the Service Provider’s forecast for the volume of orders applicable to each Bitstream Service category for each month of the period of 6 consecutive months following the month in which the forecast is provided by reference to each applicable Forecast Coverage Area. The Service Provider is also requested to provide forecasts for Months 7 to 12. This is optional and will be treated as indicative by the LFC.



6.7 If the Service Provider is aware that volume is not likely to be evenly distributed within a Forecast Coverage Area over a Service Request Month (for example due to Bulk Service Requests), it should ensure that the Forecasting Report for that Service Request Month itemises Forecast Service Requests on a per week or per Business Day basis (as applicable and to the extent required to reflect the forecast variation in distribution of volume).

6.8 If a Forecasting Report does not specify a weekly or daily Forecast Service Request volume for any Forecast Coverage Area, Forecast Service Requests for that Forecast Coverage Area will be deemed to be evenly spread across the applicable Service Request Month.

6.9 The LFC may make a reasonable request that the Service Provider provide additional information to the LFC in support of a Forecasting Report already provided. Following receipt of such a request, the Service Provider will prepare the requested information with reasonable care and provide it within a reasonable period.

Bulk Service Request Forecasts

6.10 A Bulk Service Request is either:

(i) a Bulk Transfer which is the transfer, in a coordinated manner with project management oversight, of multiple End Users onto services based on the Bitstream Service supplied to the Service Provider; or

(ii) a Bulk New Connection which is the connection, in a coordinated manner with project management oversight, of multiple new connection Service Requests for a single or multiple End Users.

6.11 As Bulk Service Requests are carried out in accordance with an agreed plan negotiated with the Service Provider, they are treated as Service Provider negotiated terms with respect to the applicable dates requested and agreed for provisioning Service Levels set out in the Service Level Terms for Bitstream Services.

6.12 Forecasts for Bulk Service Requests must be included in the Forecasting Report and may also be provided separately as a Bulk Service Request Forecast. For any proposed Bulk Service Request, the Service Provider must notify (via its forecasts) the LFC of any Bulk Service Request at least three months before the date on which the Service Provider proposes the Bulk Service Request to commence, to enable the actual date(s) for delivery to be mutually agreed between the LFC and Service Provider.



PART 3 - PRE-QUALIFICATION AND PROVISIONING

7 The OSS/BSS System Overview

7.1 OSS/BSS allows the Service Provider to log on to a secure site for the placing and monitoring of Service Requests and Service Orders with the LFC.

7.2 Subject to the provisions below relating to business continuity all Service Requests for the Bitstream Service must be placed using OSS/BSS. Except as expressly provided elsewhere in this Manual, any Service Request that the Service Provider attempts to place by other means (for example, by email or by fax) will be invalid and may be disregarded by the LFC. The LFC will use all reasonable endeavours to notify the Service Provider if such invalid Service Requests have been received.

7.3 OSS/BSS allows the Service Provider to:

(i) submit and track the status of Service Requests; and

(ii) update existing Service Requests (up to the time they are accepted and become Service Orders).

7.4 Service Providers requesting project management of Bulk Service Requests as described in clause 6.10, must contact their LFC Service Delivery Manager to agree the date of the scheduled work. Project management of multiple coordinated Service Orders will be charged at the rate in the Price List.

B2B

7.5 The Service Provider can choose to directly integrate its systems with OSS/BSS via the OSS/BSS Business to Business Web Services Interface (B2B). If the Service Provider is interested in B2B it can contact its Account Manager for documentation describing the development required to interact with B2B. A trial agreement must be signed before access to a test site, after which an Integration Access Agreement is required to be executed prior to migrating to a production instance.

7.6 The B2B metrics set out in this section 7 are targets that the LFC will use its reasonable endeavours to achieve

7.7 The LFC will target B2B availability of 99.5% measured monthly on a 24 hour 7 day a week basis.

7.8 The B2B will be considered unavailable from the time a Trouble ticket is received by the LFC until the B2B is restored.

7.9 The B2B will not be considered unavailable during Planned Outages or if the B2B is impacted due to a Force Majeure Event.



7.10 The LFC will aim for the following B2B restoration targets:

Where:

Priority 1 incidents mean the B2B is unavailable to the Service Provider:

Priority 2 incidents mean the B2B is still available but with impaired functionality and failure imminent without intervention by the LFC.

7.11 Response and restoration targets are measured from receipt of a Trouble ticket by the LFC.

7.12 The LFC will measure the following key B2B transactions at ingress and egress from the LFC’s B2B with a target time (in seconds) at the 90th percentile as set out below:

7.13 Updates will be provided to the Service Provider by email and monthly incident reporting (aggregated for all service providers) will provided in the 3rd week of the following month.

Training and Support

7.14 The LFC will provide reasonable initial set up training on OSS/BSS as part of the Operational Readiness Programme detailed in Part 11.



Access to OSS/BSS

7.15 The Service Provider will provide the LFC with the names of at least one person to be assigned as OSS/BSS user administrators. The Service Provider’s OSS/BSS user administrator(s) will then manage the creating and disabling of Service Provider staff accounts to access OSS/BSS.

7.16 On request from the Service Provider, the LFC will reset, disable or alter the OSS/BSS user administrator accounts.

7.17 Subject to clause 7.18, the LFC may restrict or prohibit access to OSS/BSS if any of the Service Provider's staff or systems:

(i) perform malicious or unintentional actions that damage or may potentially damage OSS/BSS; or

(ii) use OSS/BSS in an unauthorised manner or in such a way that causes or may cause material performance issues; or

(iii) use OSS/BSS in an unauthorised manner or in such a way to gain information they have no lawful right to access,

provided that the LFC will restrict or prohibit access to the minimum extent practicable to protect OSS/BSS and any related system.

7.18 The LFC must use all reasonable endeavours to provide the Service Provider with reasonable prior notice of such restrictions or prohibitions. Where this is not practicable in the circumstances, the LFC will give the Service Provider notice of the restriction or prohibition as soon as practicable after the event.

Additional Functionality or Enhancements to OSS/BSS

7.19 Where the LFC creates or plans to create any additional functionality within OSS/BSS or makes any enhancement to it, the LFC will notify the Service Provider. The Service Provider will modify its own provisioning systems and/or operational procedures to the extent required. The LFC must consult with the Service Providers before notifying Service Providers of any additional functionality or enhancements to OSS/BSS which affect the use of OSS/BSS in relation to the Bitstream Services.

7.20 The Service Provider will utilise the additional functionalities or enhancements to OSS/BSS as notified by the LFC from the date specified in the LFC’s notice (at the latest).

7.21 The Service Provider is responsible for ensuring that its own systems are configured in accordance with its use of OSS/BSS and comply with the requirements in the LFC Web Services Interface Software Development Kit and the OSS/BSS User Guide. These documents are available on LFC’s website.

OSS/BSS Costs

7.22 The LFC will be solely responsible for the LFC’s costs of designing and developing OSS/BSS, including any modifications and enhancements, including any of the LFC’s costs associated with Service Provider consultation.



7.23 Service Providers will be solely responsible for the costs of modifying their systems and processes to interface with OSS/BSS and B2B and for participating in the consultation and implementation process.

Terms of Use

7.24 The Service Provider must only use OSS/BSS for purposes authorised by the LFC.

7.25 The LFC will use all reasonable endeavours to ensure that OSS/BSS is available to Service Providers 24 hours a day, 7 days a week, but always in accordance with the Service Level Terms.

7.26 The LFC must take all reasonable steps to prevent the introduction of viruses or other destructive features to OSS/BSS, but the LFC does not guarantee that it is free of such viruses or other destructive features.

Business Continuity

7.27 If the LFC advises the Service Provider that the OSS/BSS is unavailable the Service Provider may submit provisioning requests by emailing the relevant form to the LFC as outlined below.

7.28 The LFC will make the following forms available to the Service Provider for use for business continuity during any periods of OSS/BSS unavailability:

(i) Pre-qualification/ Site Investigation form;

(ii) Bitstream:

• New Connection form;

• Plan Change form;

• Handover Connection; and

• Relinquishment form.

7.29 All business continuity forms submitted in accordance with clause 7.27 should come from a generic Service Provider mailbox. This mailbox must include the Service Provider's name in the email subject line as below:

[Bitstream Form Name] - [Service Provider Name] - [Service Provider reference number]

7.30 Once completed, business continuity forms must be sent to the business continuity email address advised by the LFC in accordance with clause 9 where they will be processed on a reasonable endeavours basis.

7.31 Service Requests submitted in accordance with clause 7.27 will be subject to the appropriate Service Levels in the Service Level Terms.



8 Pre-qualification Pre-qualification Overview

8.1 Pre-qualification is a service that enables the Service Provider to:

(i) confirm if the given address is within the area of geographical coverage of the applicable Bitstream Service; and

(ii) determine when the applicable Bitstream Service will be available in the future for areas outside of the current coverage.

8.2 There are two types of pre-qualification:

(i) Automated Pre-qualification (addresses or Service Identifiers); and

(ii) Special Manual Pre-qualification Investigation (addresses).

8.3 Automated Pre-qualification will be provided through OSS/BSS. In addition to this, the B2B interface will provide pre-qualification functionality. Pre-qualification Service Requests will be processed as set out below.

Information Supplied – Automated Pre-qualification

8.4 The Service Provider will supply the item to be pre-qualified. That item may either be an existing service address or an existing Service Identifier.

8.5 For an existing service address entry to be pre-qualified, a single address needs to be identified by selection from the existing LFC address list using OSS/BSS.

Information Returned– Automated Pre-qualification

8.6 The information returned by OSS/BSS may include:

(i) Service Identifier address not found;

(ii) Service Identifier in invalid format;

(iii) search could not be done;

(iv) Central Office identifier;

(v) the type of Premises e.g. MDU or Single Dwelling Unit;

(vi) the optical budget for this query (actual optical budget if there is existing fibre to the address or estimated optical budget if there is no existing fibre to address);

(vii) if the requested address is within the Candidate Area but service is not available, the date it is expected to be available;

(viii) list of Bitstream Services available at the End User Premises or Service Provider Premises or NBAP (as applicable) for the address or Service Identifier submitted, and notes on whether there is a limitation on the throughput available to the End User due to the infrastructure available; and/or



(ix) whether further investigation is required to determine if the applicable Bitstream Service can be provided. If the Service Provider chooses to request such further investigation this can be done using the Special Manual Pre-qualification process described in clause 8.7.

Special Manual Pre-qualification

8.7 A Special Manual Pre-qualification Investigation is carried out in circumstances where the Service Provider wishes to obtain information about a new address or where a Service Provider wishes to carry out further investigation after an Automated Pre-qualification Service Request.

8.8 For Special Manual Pre-qualification the Service Provider must submit the item to be pre-qualified via OSS/BSS or by email as outlined in clauses 7.27 to 7.30. If it is a new address, all address elements must be provided (street name, number etc).

8.9 The information returned will include:

(i) Central Office identifier;

(ii) the type of Premises e.g. MDU or Single Dwelling Unit;

(iii) the optical budget for this query (actual optical budget if there is existing fibre to address or estimated optical budget if there is no existing fibre to address);

(iv) list of Bitstream Services available at the End User Premises or Service Provider Premises or NBAP (as applicable) for the address or Service Identifier submitted, and notes on whether there is a limitation on the throughput available to the End User due to the infrastructure available; and/or

(v) whether the applicable Bitstream Service can be provided.

8.10 For each Pre-qualification Service Request that is received by the LFC, the LFC will provide the Service Provider with acknowledgement of receipt of the Service Request.

8.11 Charges for Pre-qualification are set out in the Price List.

Delivery

8.12 The LFC will provide the Service Provider with geographic availability and roll out information in the form of spreadsheets, databases and geo-mapping shape files, containing Premises addresses.

Site Investigation

8.13 A Site Investigation is carried out in circumstances where the Service Provider wishes to obtain information about an address.

8.14 For Site Investigation the Service Provider must submit the item to be investigated via OSS/BSS. If it is a new address, all address elements must be provided (street name, number etc).

8.15 The information returned will be, where possible, responses to requests made by the Service Provider.

8.16 For each Site Investigation Service Request that is received by the LFC, the LFC will provide the Service Provider with acknowledgement of receipt of the Service Requests.



8.17 Charges for Site Investigation are set out in the Price List.

9 Service Requests Processing 9.1 The following types of Service Requests may be submitted using the relevant web form

in OSS/BSS:

(i) Pre-qualification / Site Investigation;

(ii) New Connection;

(iii) Change Plan;

(iv) Relinquishment; and

(v) Handover Connection.

9.2 These Service Requests will be processed as outlined below.

(i) For each Service Request that is submitted either via OSS/BSS or by email as outlined in clauses 7.27 to 7.30, the Service Provider must complete all of the fields on the relevant form that are marked as mandatory. This includes providing a contact phone number for the End User, noting that a mobile number is preferred.

(ii) The LFC will acknowledge receipt of each Service Requests.

Business Hours

9.3 Service Requests will only be processed by the LFC during Business Hours except where explicitly required by the Service Level Terms.

9.4 All Service Requests entered into OSS/BSS by Service Providers outside of Business Hours on any Business Day will be deemed to have been received in the first Business Hour on the next Business Day and Service Levels will be calculated accordingly.

Service Request Validation

9.5 A Service Request will be deemed invalid and may be rejected by the LFC if:

(i) it is not submitted in accordance with this Manual; or

(ii) one or more of the rejection reasons (a list of which will be changed from time to time in accordance with clause 24 of the General Terms and made available on the LFC website) apply; or

(iii) the Service Provider does not have capability at the required Handover Point to access and interconnect with the applicable Bitstream Service.

9.6 The LFC will perform a validation check of each Service Request that is received to determine whether the Service Request is compliant, or may be rejected in accordance with clause 9.5.

9.7 If a Service Request is rejected, the LFC will advise the Service Provider of that rejection and provide the Service Provider with the applicable rejection reason.



9.8 The LFC will waive immaterial irregularities and process Service Requests where the intention is unambiguous. Examples of such irregularities include:

(i) use of different conjunctions (e.g. '&' instead of 'and');

(ii) improper application or omission of apostrophes;

(iii) variations in letter case;

(iv) use of initials instead of first names, or vice versa; and

(v) names where letters have been accidentally transposed but the meaning is still clear (e.g. Dominoin = Dominion).

Notification of Service Configuration

9.9 If a Service Request is accepted and becomes a Service Order, the LFC will notify the RSP of the service ID and service configuration of a new or modified service on or before the point in the process when the Service Start Date is confirmed.

Service Start Date

9.10 When placing a Service Request, the Service Provider will select from a list of available dates a date for the scope visit (Scope Date), if one is required, and the expected Service Start Date. If a Service Request is accepted and becomes a Service Order, the LFC will:

(i) If a scope visit is required:

a) complete the scope work on the Scope Date or a subsequently agreed alternative date; and

b) confirm with the Service Provider and the End User, the expected Service Start Date is the date they have selected. Where there is additional work required as anticipated in clause 8.8 of the Service Level Terms the LFC will advise the Service Provider of a new expected Service Start Date within 72 hours of the Scope Date; or

(ii) If no scope visit is required complete the installation on the expected Service Start Date or a subsequently agreed alternative date.

9.11 The LFC will use all reasonable endeavours to meet the Scope Date (if one is required) and the expected Service Start Date originally selected by the Service Provider as provided in clause 9.10.

9.12 Where the LFC becomes aware that it will be unable to meet the Scope Date (if one is required) or the expected Service Start Date notified under clause 9.10, the LFC will promptly advise the Service Provider of a revised Scope Date or expected Service Start Date and the relevant consequence for a reschedule set out in the Service Level Terms shall apply.



Updating Service Requests and Service Orders

9.13 A Service Request or Service Order may be cancelled at any time before the Service Start Date. In respect of any such cancellation:

(i) for a new Connection or plan change involving a site visit, where a Service Order is cancelled on the first or second Business Day after receipt of a Service Request, and no charge shall apply;

(ii) for a new Connection or plan change involving a site visit, where a Service Order is cancelled later than 2 Business Days after receipt of a Service Request for Residential and Business Connections, if the LFC has incurred Field Technician cost prior to the change requested then the LFC may charge the Service Provider for 2 hours’ time in accordance with the hourly rates set out at Item 1.14 of Table A in Appendix 3 of the Price List for Field Technician;

(iii) for a new Connection or plan change involving a site visit, where a Service Order is cancelled later than 2 Business Days after receipt of a Service Request for an NBAP Connection, the LFC may charge the Service Provider for costs it has incurred in processing the Service Request, in accordance with the time and materials rates set out at Item 1.14 of Table A in Appendix 3 of the Price List for Field Technician; and

(iv) there is no charge for the cancellation by a Service Provider of a Service Order for a plan change that doesn’t involve a site visit, or where the cancellation is advised to the LFC within 2 Business Days of the LFC rescheduling an originally specified Service Start Date.

9.14 The Service Provider may change an existing Service Request or Service Order that has been submitted using OSS/BSS if the LFC has given its consent to the change, (such consent not to be unreasonably withheld and may be provided using OSS/BSS). If such changes are made more than 1 Business Day after a Service Request is accepted and becomes a Service Order and are material (changes to service requested or delivery address), the LFC may charge a Service Provider, in accordance with the charges set out in the Price List, for costs it has incurred to date in processing all or any part of a Service Request or a Service Order and which are no longer necessary to meet the Service Request or Service Order as a result of the changes:

(i) for a new Connection or plan change involving a site visit where a Service Order is materially changed on the first or second Business Day after receipt of a Service Request, if the LFC has incurred Field Technician cost prior to the change requested then the LFC may charge the Service Provider for 1 hours’ time in accordance with the hourly rates set out at Item 1.14 of Table A in Appendix 3 of the Price List for Office Resource;

(ii) for a new Connection or plan change involving a site visit where a Service Order is changed later than 2 Business Days after receipt of a Service Request for Residential and Business Connections, if the LFC has incurred Field Technician cost prior to the change requested then the LFC may charge the Service Provider for 2 hours’ time in accordance with the hourly rates set out at Item 1.14 of Table A in Appendix 3 of the Price List for Field Technician;



(iii) for a new Connection or plan change involving a site visit where a Service Order is changed later than 2 Business Days after receipt of a Service Request for an NBAP Connection, the LFC may charge the Service Provider for costs it has incurred in processing the request, in accordance with the time and materials rates set out at Item 1.14 of Table A in Appendix 3 of the Price List for Field Technician;

(iv) there is no charge for a change by the Service Provider of a Service Order, prior to its completion, for a plan change that doesn’t involve a site visit; and

(v) the only charges for a change to a Service Order are those set out in this clause 9.14 and Late Cancellation charges (as defined in the Service Level Terms (clause 8.5) are not to be applied additionally, and following any such change the usual Charges for the resulting Service Order will apply.

9.15 If the Service Provider changes an existing Service Request or Service Order under clause 9.14:

(i) the LFC will notify the Service Provider of a revised expected Service Start Date (where applicable to the type of Service Request or Service Order involved); and

(ii) all of the relevant Service Levels for that Service Request or Service Order, as defined in the Service Level Terms, including in relation to the Maximum Cycle Time, will be restarted and measured as from the revised Service Start Date.

9.16 If the LFC requires additional information or action from the Service Provider to complete an existing Service Request or Service Order:

(i) the LFC will notify the Service Provider of the additional requirement via a OSS/BSS notification and place order in Held - Provider to Advise status (where applicable to the type of Service Request or Service Order involved);

(ii) Depending on the type of information or action required, a response will be requested with a deadline of:

• 5 working days – e.g. for customer requested cancellation, incorrect address, or

• 30 calendar days – e.g. unable to contact the customer (order details update required, awaiting confirmation customer has landlord permission / NZ housing permission etc.) and

(iii) If no response has been received from the service provider, the LFC will cancel existing Service Request or Service Order in the OSS/BSS selecting the relevant cancellation code. The status will change to ‘Held – Intent to Cancel’, for a period of 5 working days then ‘In Progress – Intent to Cancel’ and once cancellation complete in all systems ‘Closed – Cancelled’.



Evidencing End User No-Show and Late Cancellation

9.17 This clause sets out the evidence of End User No Shows or Late Cancellations that the LFC will provide to the Service Provider if requested pursuant to clause 8.6 in the Bitstream Service Level Terms in support of any LFC claims for set off against the Bitstream Core Service Level Rebates pursuant to clauses 8.4 or 8.5 of the Bitstream Service Level Terms:

(i) For each relevant End User No Show:

To confirm the End User No Show the technician acting on behalf of the LFC will knock on the End User’s door at Premises and will call the End User on the phone number supplied by the Service Provider or End User, as the case maybe, at the agreed appointment time and will repeat this exercise again after waiting at the Premises for at least 15 minutes.

The LFC will provide the following evidence to the Service Provider:

• End User’s name & address

• Service Provider order reference

• Scheduled date of appointment and am / pm

• Contact with End User confirming appointment as set out in clause 28.2

• Time and date of Technician carrying out door knocking and 2 phone calls referred to above

• Name of the contact person which the End User has requested the LFC’s technician contact for the relevant appointment.

(ii) For each relevant Late Cancellation by the End User via LFC dispatch the LFC will provide the following evidence to the Service Provider:




• Time and date of call that led to Late Cancellation

• Name of the contact person spoken to by the LFC’s despatch

• Reason provided for cancellation or reschedule resulting in the Late Cancellation

(iii) For each relevant Late Cancellation by the Service Provider the LFC will provide the following evidence to the Service Provider:




• OSS/BSS log of Time and date of cancellation / reschedule resulting in the Late Cancellation



(iv) For each relevant Late Cancellation by the End User to the LFC’s technician at the Premises at the appointment time:




• Time and date of cancellation or reschedule resulting in the Late Cancellation

• Name of the contact person spoken to by the LFC’s technician

• Reason provided

• ‘Request to reschedule form’ signed by the End User or contact person

9.18 If the Service Provider requests evidence for the relevant Customer No Show or Late Cancellation pursuant to clause 8.6 of the Bitstream Service Level Terms and the LFC does not provide the evidence set out in clause 9.17 above, the LFC will either:

(i) Not apply the set off against the Bitstream Core Service Level Rebates for the relevant Customer No Show or Late Cancellation pursuant to clauses 8.4 or 8.5 of the Bitstream Service Level Terms; or

(ii) Reverse the set off applied against the Bitstream Core Service Level Rebates for the relevant Customer No Show or Late Cancellation pursuant to clauses 8.4 or 8.5 of the Bitstream Service Level Terms.

In addition to providing the above evidence, the LFC will undertake ongoing validation of evidence files where a statistically significant sample will be validated each month

Completion of a Service Order

9.19 The LFC will provide the Service Provider with confirmation that the Bitstream Service has been activated which may be before a Service Order has been completed if additional commercial work is being carried out to complete the Service Order.

9.20 Service Order confirmations submitted to the Service Provider outside of Business Hours will be deemed to have been received by the Service Provider at the beginning of the first Business Hour of the following Business Day.

9.21 Service Order confirmations for Bitstream Services submitted to the Service Provider will contain at least the following information:

(i) Handover Point ID(s);

(ii) E-NNI Service VLAN ID(s);

(iii) E-NNI Customer VLAN ID(s) (where applicable);

(iv) Service Identifier(s);

(v) UNI Port identifier(s) (where not defaulted in the Service Template);

(vi) UNI VLAN Identifier(s) (where applicable, and not defaulted in the Service Template); and



(vii) Circuit Identifier(s) (where applicable).

Testing

9.22 At the completion of a Bitstream Service installation the LFC will perform an end to end test of the service from the Central Office to the End User Premises or Service Provider Premises or NBAP (as applicable) to ensure it is within specification using an automated test facility. The LFC will provide the Service Provider with access to the test output.

9.23 Where the LFC has installed Service Provider equipment, the testing will include those items agreed with the Service Provider when the Service Provider equipment was accredited. Any failure of Service Provider equipment during installation by the LFC will also be dealt with in a manner agreed with Service Provider when the Service Provider equipment was initially accredited, or as subsequently agreed.

Charges

9.24 Charges for all the transactions, processes and services referred to in this clause 9 are set out in the Price List. Charges may only be made for valid Service Requests or Service Orders following the validation provided for in clause 9.6. Invoicing will commence in accordance with clause 7.3 of the General Terms.

Transfer Service Requests

9.25 Transfer Service Requests where an End User is transferring from one Service Provider (or Service Providers as the case may be) to another Service Provider are subject to clauses 9.26 and 9.27.

9.26 Service Providers must obtain Customer Authorisation to these transfers, in accordance with the terms of the Customer Transfer Code, before the relevant Service Request is submitted.

9.27 The LFC is entitled to rely on the Transfer Service Request as evidence that a valid Customer Authorisation has been obtained in accordance with the Customer Transfer Code. The LFC is not liable in the event that authorisation is found to be invalid or not in accordance with the Customer Transfer Code.

9.28 The application of provisioning service levels to transfers are set out in the Service Level Terms.

Submitting Bulk Service Requests

9.29 Bulk Service Requests enable a Service Provider to transfer or connect large volumes of End Users to the Bitstream Service in a co-ordinated manner.

9.30 Service Providers should contact their LFC Service Delivery Manager to discuss the requirements and timeframes of any Bulk Service Requests before placing a Bulk Service Request.

9.31 Once a Bulk Service Request has been placed, the LFC and the Service Provider will agree on a plan that describes how the Bulk Service Requests will be managed and carried out (including details of the dates on which the relevant batches of individual transfers will take place and, where appropriate, the resources to be used).



Relinquishment Requests

9.32 Each Bitstream Service may be subject to a Minimum Service Term. A Service Provider that terminates or relinquishes a Bitstream Service prior to the expiry of the Minimum Service Term may be required by the LFC to pay early termination charges in accordance with the Price List.

Multiple Service Providers:

9.33 In clauses 9.34 to 9.37:

Primary Service Provider means a provider of a service to an End User, either directly or via a Reseller, that uses a UFB Standard Wholesale Service as an input;

Secondary Service Provider means a provider of a service (such as Multicast) to the same End User, either directly or via a Reseller, as the Primary Service Provider that uses the same physical infrastructure as the UFB Standard Wholesale Service purchased by the Primary Service Provider; and

UFB Standard Wholesale Service means a Wholesale Service that meets or exceeds the minimum standard for the residential Bitstream Service (being 30Mbps downstream, 10 Mbps upstream with 2.5 Mbps CIR symmetrical).

9.34 If a Primary Service Provider requests the termination of the UFB Standard Wholesale Service for an End User or Reseller, the LFC will notify the Secondary Service Provider that the Primary Service Provider has terminated the UFB Standard Wholesale Service.

9.35 Upon receipt of the notification under clause 9.34 the Secondary Service Provider may, by notifying the LFC, within 5 Business Days:

(i) become the Primary Service Provider for the End User or Reseller and provide a service that uses a UFB Standard Wholesale Service as an input to that End User or Reseller; or

(ii) terminate the Wholesale Service that the Secondary Service Provider was purchasing to service that End User.

9.36 If the Secondary Service Provider does not make an election within the timeframe required under clause 9.35 the LFC may terminate the Secondary Service Provider’s Wholesale Service in respect of the relevant End User or Reseller on 5 Business Days’ notice.

9.37 If the Secondary Service Provider’s Wholesale Service is terminated under clause 9.35(ii) or 9.36 no early termination charges shall apply.



PART 4 - PROBLEM MANAGEMENT

10 OSS/BSS 10.1 The LFC has a fault management system as part of the OSS/BSS described in clause 7

above. In addition to processing Service Requests and Service Orders the OSS/BSS allows Service Providers to:

(i) create a new trouble ticket;

(ii) retrieve a trouble ticket; and

(iii) update a trouble ticket.

10.2 OSS/BSS allows the Service Provider to log on to a secure site for reporting and monitoring faults with the LFC.

11 Faults 11.1 The LFC is only responsible for faults in a Bitstream Service or the LFC Network, as set

out in clause 6 of the General Terms (LFC Fault). If the LFC investigates and no LFC Fault is affecting the Bitstream Service, the LFC may charge the Service Provider the “No fault found” Ancillary Charge as set out in the Price List. Where a fault is found which is an LFC Fault, a “No fault found” Ancillary Charge will not be charged.

11.2 It is the Service Provider's responsibility to provide initial fault diagnosis on all faults reported to it by its End Users, as set out in clause 6.2 of the General Terms.

Bitstream Diagnostic Tools

11.3 Until the LFC has provided the Service Provider with diagnostic tools that will, in the LFC’s opinion (acting reasonably), enable the Service Provider to confirm that a fault in relation to any Bitstream Service is an LFC Fault, the following process will be followed:

(i) on receiving a fault report from the Service Provider for an End User reported Fault in a Bitstream Service, the LFC will undertake diagnostics prior to ordering a truck roll;

(ii) and if the LFC determines from the results of the diagnostics that the fault is an LFC Fault the LFC will take appropriate corrective action (which may involve a truck roll) and not charge a “No fault found” Ancillary Charge; or

(iii) the LFC determines the fault is not an LFC Fault the LFC will advise the Service Provider of this and close the fault without charging a “No fault found” Ancillary Charge in accordance with the Price List. The Service Provider can request the LFC roll a truck if it believes the fault is an LFC Fault but, if it is subsequently found not to be an LFC fault, the LFC will advise the Service Provider of this, close the fault and charge a “No fault found” Ancillary Charge in accordance with the Price List.



11.4 Prior to the LFC providing the Service Provider with diagnostic tools that will, in the LFC’s opinion (acting reasonably), enable the Service Provider to confirm that a fault in relation to any Bitstream Service is an LFC Fault the LFC will provide initial training for the Service Provider’s staff for use of such diagnostic tools at no charge. Any subsequent training in the use of such diagnostic tools by the Service Provider may be charged for by the LFC in accordance with the Price List.

11.5 When the LFC has provided the Service Provider with diagnostic tools that will, in the LFC’s opinion (acting reasonably), enable the Service Provider to confirm that a fault in relation to any Bitstream Service is an LFC Fault, clause 11.3 will no longer apply and the LFC may charge a “No fault found” Ancillary Charge in accordance with the Price List for any reported fault where the fault is investigated by the LFC and is not an LFC Fault.

Reporting Faults to the LFC

11.6 Subject to clause 11.7 the Service Provider must use OSS/BSS for reporting all faults regarding the Bitstream Service. If the Service Provider uses any other method to report a fault, the Service Levels as defined in the Service Level Terms will not apply to that fault.

11.7 Where the OSS/BSS is unavailable, the Service Provider must submit fault reports to the LFC by calling the 0800 fault reporting service number provided by the LFC, and a sequence number or other manual identifier will be provided by the LFC in accordance with its business continuity process. The LFC must use all reasonable endeavours to advise Service Providers immediately upon becoming aware that the OSS/BSS is unavailable, including how it will manage fault reports lodged prior to the OSS/BSS becoming unavailable which are unresolved.

11.8 Once the Service Provider has provided initial fault diagnosis, in compliance with clause 6.2 of the General Terms and determined that it requires the LFC’s assistance to resolve the fault, the following information is required when reporting a fault:

(i) contact details of the Service Provider logging the fault;

(ii) contact name, mobile phone number, and alternate phone number (if available) of the End User experiencing the fault (where reasonably required);

(iii) End User's Service Identifier for service that is experiencing the fault (where appropriate);

(iv) fault type and description as can be best reasonably ascertained by the Service Provider;

(v) time the fault occurred or became known to the Service Provider;

(vi) address and contact details for the site of the fault (where appropriate);

(vii) confirmation that the initial fault diagnosis has been completed; and

(viii) any other relevant information reasonably required.

11.9 If any of the above information in clauses 11.8(i) to 11.8(vi) is not provided to the extent necessary for the LFC to proceed to investigate the fault, the Service Levels will not apply until such time as the Service Provider has provided the required information.



11.10 The LFC is responsible for the repair of faults in the UFB Handover Connection, including faulty termination at the MOFDF.

Updating reported faults

11.11 A fault report may be cancelled or changed, at any time before the fault report is closed. In respect of any such cancellation or change:

(i) for a fault report that is cancelled or changed before a technician has been dispatched, the LFC will not charge the Service Provider; and

(ii) for a fault report that is cancelled, or is changed (to the extent that a change prevents the dispatched technician from completing the fault investigation or repair task at the scheduled time originally advised to the Service Provider), once the technician has been dispatched, the LFC may charge the Service Provider the “No Fault Found” charge (Item 1.7 of Appendix 3 of the Price List).

11.12 If the Service Provider changes an existing fault report under clause 11.11:

(i) the LFC will notify the Service Provider of a revised expected Fault restoration time if the nature of the change requires the fault repair work to be rescheduled (change to access conditions, nature of fault, etc.); and

(ii) if rescheduled in accordance with 11.12(i), the calculation of relevant Restoration and Availability Service Levels for that fault restoration, as defined in the Service Level Terms, may take into account delay time due to this rescheduling.

11.13 If the LFC reschedules a fault without being requested to do so by the Service Provider or End User, then the calculation of relevant Availability Service Levels for that Fault restoration, as defined in the Service Level Terms, will continue to be measured from the original time of the fault report to the actual fault restoration time

Hours of Operation

11.14 Faults can be logged 24 hours a day, seven days a week.

11.15 When a fault report is received, the LFC will advise the Service Provider, acknowledging receipt of the fault report.

Fault Tracking

11.16 All faults will be logged in OSS/BSS and the Service Provider will be given a fault reference number and an expected fault restoration time. The expected fault restoration time will be provided in accordance with the LFC’s fault prioritisation systems.

11.17 The LFC will use all reasonable endeavours to meet the notified expected fault restoration time as provided in clause 11.16.

11.18 Where the LFC has allocated an expected Fault restoration time to a Fault and it subsequently becomes apparent that the Fault restoration time cannot be met, the LFC will advise the Service Provider of a revised expected Fault restoration time. In that situation the “Meet notified expected restoration time” Service Level in the Service Level Terms will continue to apply to the originally notified expected restoration time, subject to clause 11.9.



11.19 Where the Service Provider requests a specific fault response time and the LFC accepts that time (e.g. because access must be provided to a remote site or an outage scheduled):

(i) The applicable period for the Restoration Service Levels in the Service Level Terms will not include any extension of time that arises as a result of the LFC delaying its fault response due to a specific fault response time request from the Service Provider that is accepted by the LFC; and

(ii) the “Meet notified expected restoration time” Service Level in the Service Level Terms will apply to the specific fault response time requested by the Service Provider and accepted by the LFC.

11.20 The Service Provider will be able to check the progress of a fault via OSS/BSS. The fault reference number is to be used in all communications regarding the fault.

11.21 If the LFC identifies the need to send a faults contractor, the LFC will update OSS/BSS.

11.22 The Service Provider's consents to the LFC coordinating site access and any required outage window with the End User, unless the Service Provider advises the LFC that the Service Provider wishes to do so.

Fault Closure

11.23 Once the fault has been resolved, the LFC will notify the Service Provider via OSS/BSS (or other means) that the fault has been resolved, confirm the reference number and, where possible, provide the cause of the fault and any actions taken to reach resolution.

Planned Outages

11.24 The LFC may suspend supply of the Bitstream Service for the purpose of conducting works, routine maintenance, remedial work or upgrades to the LFC's Network (Planned Outage).

11.25 The LFC will use all reasonable endeavours to:

(i) conduct any Planned Outage between the hours of 11.00pm to 6.00am inclusive, where the LFC believes that is practical (acting reasonably);

(ii) advise the Service Provider in advance of any Planned Outage with at least 5 Business Days’ notice; and

(iii) provide the following information:

(i) a brief explanation of the reason for the Planned Outage;

(ii) the intended date, time and duration of the Planned Outage;

(iii) a description of the Bitstream Service (or the relevant part of it) which will be affected by the Planned Outage; and

(iv) the name and contact details of the LFC's representative(s) who gave the advice.

11.26 The duration of any Planned Outage will be deemed to be downtime for the calculation of relevant aggregate Availability Service Levels, as defined in the Service Level Terms.



Unplanned Outages

11.27 The LFC may suspend supply of the Bitstream Service:

(i) due to any unplanned unavailability of the LFC's Network or the Bitstream Service; or

(ii) in order to provide or safeguard service to the emergency or other essential services,

(Unplanned Outage).

11.28 The LFC will use all reasonable endeavours to:

(i) give the Service Provider as much advice as possible of the existence of any Unplanned Outage;

(ii) advise the Service Provider as soon as reasonably practical after the LFC becomes aware of any Unplanned Outage; and

(iii) answer any reasonable questions from the Service Provider about the extent and duration of any Unplanned Outage.

11.29 The duration of any Unplanned Outage will be deemed to be downtime for the calculation of relevant aggregate Availability Service Levels, as defined in the Service Level Terms.

11.30 If the Service Provider becomes aware of any Unplanned Outage before it receives advice from the LFC under clause 11.28, the Service Provider will make reasonable efforts to notify the LFC as soon as reasonably practical.

Emergency Faults

11.31 Emergency faults include, but are not limited to:

(i) medical emergencies;

(ii) where the End User provides an essential community service (e.g. police or a doctor's residence); or

(iii) where there is a mass outage that impacts on 200 or more End Users.

11.32 Emergency faults reported to the LFC outside of Business Hours will be treated on a case by case basis, which may include proposing a temporary solution.

11.33 The Escalation Protocol is provided in Appendix B.



PART 5 – STANDARD BITSTREAM SERVICE INSTALL AND TERMINATION POINTS

12 Installation Services

12.1 The Bitstream Service includes Installation as set out below (in each case to the extent that the relevant provisioning works are not already complete for the relevant Service Order).

Standard Installation

Fibre Lead-in

12.2 The Fibre Lead-in Standard Installation applies during the relevant UFB Period:

(i) In UFB1 Areas to installations in: a. Single Dwelling Units; b. Multi Dwelling Units with no more than three residential tenanted

storeys; and c. NBAPs.

(ii) In the UFB2 Areas to installations for all End Users including NBAPs.

12.3 The Fibre Lead-in Standard Installation for Residential Premises in UFB1 Areas and for all Premises in UFB2 Areas includes a Fibre Lead-in from the Fibre Access Point to an ETP, common ETP or OFDF as applicable, at the closest convenient point on the Premises, as agreed with the End User, up to a maximum distance of 200 metres per Premises. The Fibre Lead-in will comprise one or a combination of the following methods:

(i) in an LFC approved conduit or open trench (already in place at the time of installation); or

(ii) where the Premises is in an area of overhead deployment, an aerial drop lead and a road crossing if required; or

(iii) where the Premises does not have an LFC approved conduit or open trench already in place or and is not in an area of overhead deployment, one or a combination of the following as selected by the End User: a. surface mounted conduit (installation on either vertical or horizontal

surface) or any other low impact method (such as shallow bury); or b. slot trenching; or c. buried lead-in (other than slot trenching).

UFB1 Areas Business Fibre Lead-in

12.4 In UFB1 Areas for Business Premises, the Fibre Lead-in Standard Installation includes a Fibre Lead-in from the Fibre Access Point to an ETP, common ETP or OFDF as applicable, at the closest convenient point on the Premises, as agreed with the End User, up to the maximum distances per Premises below, comprising one or a combination of the following methods:

(i) 200 metres in an LFC approved conduit or open trench (already in place at the time of installation); or

(ii) where the Premises is in an area overhead deployment, a single span of aerial drop lead and a road crossing if required; or



(iii) where the Premises do not have an LFC approved conduit or open trench already in place or are not in an area of overhead deployment, one or a combination of the following as selected by the End User: a. 200 metres surface mounted conduit (installation on either vertical or

horizontal surface); or b. 100 metres any other low impact method (such as shallow bury); or c. 50 metres slot trenching; or d. 15 metres buried lead-in (other than slot trenching).

NBAP Fibre Lead-ins

12.5 For NBAPs in UFB1 Areas and UFB2 Areas (and subject to clause 12.16) the Fibre Lead-in Standard Installation includes a Fibre Lead-in from the Fibre Access Point to an ETP at the closest convenient point on the NBAP, as agreed with the Service Provider or End User (as applicable), up to a maximum distance of 200metres per Premises below, comprising one or a combination of the following methods capped at the distances specified;

(i) 200m in an LFC approved conduit or open trench (already in place at the time of installation); or

(ii) where the Premises is in an area of overhead deployment, a single span of aerial drop lead and a road crossing if required (excluding poles not in road corridor); or

(iii) where the Premises do not have an LFC approved conduit or open trench already in place or are not in an area of overhead deployment, one or a combination of the following:

a. 200 metres surface mounted conduit (installation on either vertical or horizontal surface); or

b. 100 metres any other low impact method (such as shallow bury); or c. 50 metres slot trenching; or d. 15 metres buried lead-in (other than slot trenching).

General Fibre Lead-in Installations

12.6 Where existing infrastructure allows for installation in accordance with clauses 12.3(i), 12.3(i)12.3(ii), 12.4(i), 12.4(ii) 12.5(i) and 12.5(ii) those installation methods will be used. In all other cases the installation method will be agreed with the End User for a Premises or Service Provider for an NBAP, or in the case of an MDU the MDU owner(s) or their agent.

12.7 For Standard Installations, the FAP in a private road or right of way is deemed to be located at the boundary between the private road or right of way and the adjoining public road. The 200m limit will be applied on a cumulative basis. For example, three Premises sharing a right of way would have up to 600m of Fibre Lead-in in total included in the Standard Installation.

12.8 In UFB2 Areas only, the FAP in a business park or complex that is located wholly on one certificate of title is deemed to be located at the boundary between the adjoining public road and the business park or complex. The 200m limit will be applied on a cumulative basis. For example, three Premises within a business park or complex would have up to 600m of Fibre Lead-in in total included in the Standard Installation.

12.9 In UFB2 Areas only, the Standard Installation has no distance limitation for the Fibre Lead-in to End Users in retirement villages.



Multi Dwelling Unit Common Infrastructure (Standard)

12.10 During the relevant UFB Period, the Standard Installation of a Bitstream Service in an MDU includes the MDU Common Infrastructure:

(i) In UFB1 Areas to all Multi Dwelling Units with no more than three residential tenanted storeys; and

(ii) In UFB2 Areas to all Multi Dwelling Units.

12.11 Prior to the completion of the First MDU Order, the LFC will carry out the MDU Connection Pre-requisite Steps set out in clause 27 or if it has not completed the MDU Connection Pre-requisite Steps within 30 days of receipt of the First MDU Order, or if consent is declined, on request the LFC will follow the Aged Tenancy Order process set out in clause 27.

12.12 The LFC Network fibre within the MDU (the Fibre Lead-in, the MDU Common Infrastructure (if any), and the fibre to an End User Tenancy), whether currently in use or not, is only available for use by the LFC.

Non-standard installations

Fibre lead-in (Non-Standard)

12.13 The Non-Standard Installation applies to the extent that any Fibre Lead-in is in excess of any of the lengths or where an installation method is not one of the methods included as part of a Standard Installation. This means there will be incremental charges for installations that are outside the criteria specified for Standard Installations.

12.14 In UFB1 Areas, the Fibre Lead-in in gated communities which are not MDUs is a Non-Standard Installation.

Multi Dwelling Unit Common Infrastructure (Non-Standard)

12.15 The installation of MDU Common Infrastructure (in MDUs which exceed 3 residential tenanted storeys) is a Non-Standard Installation in UFB1 Areas during the relevant UFB Period. The LFC will contribute $1,000 per End User Tenancy to the costs of the MDU Common Infrastructure during the relevant UFB Period in these MDUs.

NBAP Installations – Network extensions (Non-Standard)

12.16 The LFC may charge the Service Provider for extending the LFC Network to the Fibre Access Point or boundary of NBAPs that;

(i) were not an existing copper or fibre demand point at the time the LFC Network was deployed in the relevant area; or

(ii) are not built in Premises that are Passed by LFC Network (i.e a new ATM in a shopping mall).

12.17 The charges for the network extension from the nearest convenient point in the LFC network (i.e manhole or splitter) to the Fibre Access Point or boundary of the NBAP will be the charges for Non-Standard Installations set out in the Price List.



Beyond the ETP

12.18 All installations during the relevant UFB Periods include the following at the LFC’s cost:

(i) an extension of the Fibre Lead-in from the ETP (there will not necessarily be a break in the Fibre Lead-in at the ETP) or OFDF as applicable to:

a. a suitable mounted SC/APC connector at a secure location inside the Premises, End User Tenancy or NBAP; or

b. if there is an OFDF beyond the ETP, a splice or LCA connector on the OFDF within the Premises, End User Tenancy or NBAP;

The internal fibre may be surface wired from the point of entry to the connector or OFDF if wall, ceiling or floor cavities not accessible. The route and method used shall be determined by the LFC in consultation with the End User.

(ii) Except for Glass Only service, the installation of a standard ONT/NID which may include some or all of the following:

• supply and fixing of the ONT/NID to the structure of the Premises, End User Tenancy or NBAP ;

• supply and connection of a fibre pigtail between the Fibre Lead-in termination point and the ONT/NID if required; and

• testing from the UNI port of the ONT/NID and if applicable the ONT ATA port, to ensure the Bitstream Service is within the technical specification set out in Appendix B to the relevant Service Description. The ATA port testing is dependent on the RSP setup and may not be possible or may be limited to a functional out-going call test.

•

For a Premises or End User Tenancy the ONT and CPE will be mounted on the indoor surface of a wall, preferably on an external wall adjacent to 2 existing power outlets, unless an End User provided enclosure (including power outlets) is available. The ONT and CPE location is to be agreed between the LFC and the End User (e.g. close to the main computer or primary TV set top box or in the End User provided enclosure which includes power outlets).

(iii) In UFB1 Areas connection of home voice wiring to an ONT or CPE ATA voice port, including connection of approved suitable End User or agreed Service Provider CPE if required and which is available on site at the time of the ONT installation for the LFC to install. The Service Provider must ensure that the End User provides a suitably located dual mains power outlet for the standard ONT and CPE power supplies if the CPE to be installed by the LFC is to be supplied power from the same point as the ONT.

12.19 The End User is responsible for providing space and power for the ONT/NID where one is required. The location of the ONT/NID must be a suitable environment for electronic equipment being generally a dry, clean indoor area with adequate ventilation.



Reinstatement

12.20 For all installations the LFC will reinstate all surfaces on a “like for like” basis (i.e. the LFC will use concrete where concrete has been used, grass where grass has been used and asphalt where asphalt has been used. The LFC does not guarantee that it will be able to identically match surface finish (e.g. colour, texture or pattern) and reinstatement will be limited to the areas where the works have been carried out by the LFC). Reinstatement at an End User’s Premises is to be completed in accordance with Best Industry Practice to the standard that was agreed to at the scope appointment and that was accepted in writing by the End User. If reinstatement is not completed on the same day of the build/installation then the LFC shall complete the reinstatement by an agreed commitment date (which shall be no later than 30 days after the day of the completed build/installation).

Termination Points

Single Dwelling Unit Termination Point

12.21 For a Single Dwelling Unit, the termination point of the Layer 1 component of the Bitstream Service for the purposes of the Connection at the Premises, and the network demarcation point between the LFC Network and the Premises wiring is, as applicable, either:

(i) the SC/APC connector on the end of the Fibre Lead-in from the ETP; or

(ii) a splice or LCA connector on the OFDF,

provided that any ONT/NID installed by the LFC as part of the Bitstream Service will also be part of the LFC Network.

MDU Termination Point

12.22 For MDUs, the termination point of the Layer 1 component of the Bitstream Service for the purposes of the Connection at the End User Tenancy, and the network demarcation point is as applicable, either:

(i) the SC/APC connector on the end of the Fibre Lead-in; or


within the End User Tenancy provided that any ONT/NID installed by the LFC as part of the Bitstream Service will also be part of the LFC Network.

NBAP Termination Point

12.23 For a NBAP, the termination point of the Layer 1 component of the Bitstream Service for the purposes of the Connection at the NBAP, and the network demarcation point between the LFC Network and the NBAP wiring is, as applicable, either:

(i) the SC/APC connector on the end of the Fibre Lead-in from the ETP; or


provided that any ONT/NID installed by the LFC as part of the Bitstream Service will also be part of the LFC Network.



Layer 2 Termination Point

12.24 The termination point of the Layer 2 component of the Bitstream Service is either:

(i) the ATA port on the ONT; and/or

(ii) the 100/1000Base-T UNI on the ONT; or

(iii) for ‘glass only’ versions of the Bitstream, either:

a. the SC/APC connector on the ITP at the end of the Fibre Lead-in from the ETP (which is the connector); or

b. a splice or LCA connector on the OFDF; or

(iv) For SPF ONTS the SFP UNI on the SFP ONT, noting this point is internal to the host CPE and is not externally accessible.

Alternative Termination Points

12.25 The LFC and the Service Provider may agree on a different termination point as part of a Non-Standard Installation. This may be necessary where, for example, there is installation to a NBAP. A Non Standard Installation for a Bitstream Service within an MDU will not include termination in a building common area or other facility made available by the owner to service the Multi Dwelling Unit, where a Fibre Lead-in has not been extended from the OFDF to the inside of an End User Tenancy.



PART 6 - CONSENTS PROCESS

13 Consents for a Single Dwelling Unit (SDU) and an End User Tenancy (MDU Tenancy) in an MDU

Introduction

13.1 This clause 13 describes the consent process that will apply if Service is required in an End User Premises that is either:

(i) an SDU that is either a single residential or commercial occupancy within the boundary of the premises; or

(ii) an End User Tenancy is the occupancy of an End User (for example, an apartment, townhouse, office or shop) in an MDU where the Service is being provided pursuant to a First MDU Order, Subsequent MDU Order(s) or Aged Tenancy Order(s) in the relevant MDU.

13.2 Consent is required from MDU owner(s) or their agents in relation to providing Services pursuant to the First MDU Order(s) or Aged Tenancy Order(s) in the relevant MDU. The process for these consents set out in clause 14 will also apply. If Service is required in an NBAP the process described in clause 15 will apply. In this clause 13 End User Premises means a Single Dwelling Unit and an End User Tenancy in an MDU. The LFC needs the End User to consent to or, if the End User is the tenant, procure consent to, access by the LFC to the End User Premises to operate the LFC Network (including installation, maintenance, removal, etc.) so that Services can be provided. The consent process differs if:

(i) the End User Premises belongs to an End User who the Service Provider has elected to treat as an “Exempted End User”, in which case the Service Provider:

(i) must notify the LFC of that election in the Service Request and provide the LFC with the name and location details of the Exempted End User and its End User Premises; and

(ii) does not have to get the Exempted End User to agree to the LFC (End User) Terms. The LFC will be responsible for getting any other third party consents that are required including, in the case of an End User Tenancy, consents to cable up the common areas of the MDU using process described in clause 14; and

(ii) the End User Premises belongs to the Service Provider or a Reseller (other than a self-consuming Reseller), in which case the LFC (End User) Terms will not apply and the Service Provider will get all necessary consents, other than, in the case of an End User Tenancy, consents to cable up the common areas of the MDU which will use the process described in clause 14.

13.3 Other than for Exempted End Users, the process for the LFC to obtain consent to access an End User Tenancy and to protect the LFC Network once installed, is for the Service Provider (or its Reseller customer) to obtain the End User’s agreement to the LFC (End User) Terms, at the same time as the End User agrees to the Service Provider’s terms and conditions. The Service Provider will, before the Service Request is submitted:



(i) provide the LFC (End User) Terms to the End User by appropriate means which could include an on-line link or electronically; and

(ii) record the End User’s agreement to the LFC (End User) Terms by appropriate means which could include by having the End User complete an online confirmation or tick box.

13.4 The LFC will provide the Service Provider with a copy of its current standard form of the LFC (End User) Terms by electronic means, including (by way of example) by providing a link to where the LFC (End User) Terms are available online or issuing the Service Provider with an email attaching a copy of the LFC (End User) Terms. The LFC will provide a physical copy of the LFC (End User) Terms to the Service Provider on request. The LFC (End User) Terms will include the right for the LFC to require the End User to physically sign an additional consent form at the time of installation, confirming that the End User has agreed to be bound by the LFC (End User) Terms. The LFC will not require the Service Provider to obtain written evidence of agreement to the LFC (End User) Terms. However, the Service Provider may be asked by the LFC to demonstrate that the Service Provider has complied with the requirements described in clause 13.3 during the 3 months after the Service Start Date. If the LFC is not satisfied by the evidence provided by the Service Provider, the LFC may try to sign the End User up to the LFC (End User) Terms directly during that 3 month period after the Service Start Date, unless they are an “Exempted End User”.

13.5 Installations in End User Premises will fall into two categories:

(i) Simple - where the LFC Network (lead-in cable) will not cross another property between the FAP and the End User Premises, therefore no additional consent is required (apart from End User or landlord consent, if applicable) (see clauses 13.8 to 13.10); or

(ii) Complex: SDU - where the only reasonably practicable way to connect the LFC Network to the SDU is for the LFC Network to cross other property. Two frequent examples of this are:

(i) land adjacent to an SDU which is privately owned by a third party and for which the End User does not have sufficient pre-existing right to allow the LFC to install the LFC Network there to access the SDU; or

(ii) a right of way situation where the LFC Network must cross common private land in which the End User’s pre-existing rights are not sufficient to allow the LFC to install the LFC Network there to access the SDU,

in which case, consent (in this Part 6, this includes all authorisations and licences needed by the LFC) is also required from affected third parties (as well as End User or landlord consent, if applicable).

(iii) Complex: End User Tenancy – in an MDU where the LFC Network currently ends at the FAP or has only been extended to the building entry point of the relevant MDU, and consent is also required from affected third parties, such as building owners, for the LFC to extend the LFC Network to the End User Tenancy . Clause 14 applies to such Complex End User Tenancies.



The diagrams below provide some examples of Simple and Complex End User Premises installations.

Distribution Fibre Fibre

Cabinet

Your House on Main Road

External Test Point (ETP)

Your Fibre Lead-in

Fibre Access Point (FAP)

Optical Network

Terminator

Your Section

Your House on Right of Way

Rig

ht o

f Way

Cab

le re

quire

dExternal Test Point (ETP)

MultipleFibre

Lead-ins

Optical Network

Terminator

Your Neighbours House on Right of Way External Test

Point (ETP)

Optical Network

Terminator

Your Fibre Lead-in

Your Neighbours House on Right of WayExternal Test

Point (ETP)

Optical Network

Terminator

Your Neighbours House on Right of Way


Optical Network

Terminator

Grassed Footpath Area

Road

Shar

ed R

ight

of W

ay

Your Section

Your Neighbours House on Main Road


Optical Network

Terminator

Your House on Back Section with consent

required


Optical Network Terminator

Con

sent

requ

ired

for

Nei

ghbo

urs

prop

erty

‘Simple Installation’

‘Complex Installation’




13.6 To enable the LFC to determine whether an End User Premises installation is Simple or

Complex, the Service Provider will need to gather information from the End User in addition to the normal service required, address and contact details. If the Service Provider is unable to provide the additional information requested below or the information is found to be incorrect then the Service Request may be delayed while additional information or consent is gained or the order rejected. This additional information should be provided to the LFC as part of the Service Request and include the following:

(i) Is the End User the sole or a joint owner of the End User Premises or a tenant or occupier under some other occupation right? If the End User is not the sole or a joint owner, the Service Provider will get the End User to agree to obtain the landlord’s consent. It is the End User’s responsibility to obtain any landlord consents.

(ii) Is the End User Premises in a right of way? If in a right of way, are other End User Premises serviced by the right of way already taking Service and are there any relevant pre-existing rights that can be relied on by the LFC (for example, an existing telecommunications easement)?

(iii) Is the End User Premises in an MDU? If in an MDU, are other End User Premises in the MDU already taking Service and are there any relevant pre-existing rights that can be relied on by the LFC (for example, an existing telecommunications easement)?

(iv) Does the End User believe (even though they aren’t in a right of way or MDU) that LFC Network will cross another property between them and the road and, if so, details of that other property and its owner or occupier?

If a Service Request requires consent to access a right of way, MDU or adjacent third party property or another telecommunications network, then the Service Provider should set an expectation with the End User that provision of the Service is subject to obtaining those consents and therefore may be delayed. The Service Provider should also tell the End User that the LFC may call on the End User for assistance with obtaining such third party consents. The Service Provider should advise the End User that their details will be passed to the LFC who will contact them, and the Service Provider should ensure that the End User’s full contact details are included in the Service Request.

13.7 The provisioning Service Levels (but not the Maximum Cycle Time measurement), including the LFC’s obligation to proceed with (or complete) LFC Network installation, only apply from the time that all applicable consents have been obtained, excluding road opening notices but including, in the case of an End User Tenancy, consents for the installation and maintenance of common infrastructure, plus time to install the infrastructure. Other consents that may be required and the absence of which would prevent the application of provisioning Service Levels (but not the Maximum Cycle Time measurement) include, but are not limited to, the following examples:

(i) landowner consent where tenant has requested service for a rented or leased property;

(ii) council consent for work within drip line of notified trees on public land or road reserve or within the End User Premises or affected third party property



boundaries;

(iii) neighbour consent for crossing private or shared land;

(iv) special consent for work on or within notified heritage buildings; and

(v) special consent for work on or within archaeological or cultural areas.

Simple Consents

13.8 For an End User Premises where the LFC Network (lead-in cable) will not cross another property between the FAP and the End User Premises, no additional consent is required (apart from consent from the End User or landlord, if applicable). Other than for Exempted End Users, the Service Provider will obtain the End User’s agreement to the LFC (End User) Terms and confirmation from the End User of landlord consent (if applicable). This will permit the LFC to access the End User Premises to, among other things, install the LFC Network required to provide the Service.

13.9 If any doubt arises regarding the End User’s agreement to the LFC (End User) Terms during an installation, the LFC technician who attends the End User Premises to undertake installation may seek an evidential copy of the End User’s agreement to the LFC (End User) Terms, before commencing installation work. In the event that no evidential copy can be provided and the LFC technician requests the End User’s written agreement to the LFC (End User) Terms during the installation process, if the End User (or a person on site who represents the End User) refuses to sign the agreement form when requested by the LFC technician, or where for any other reason the LFC technician is denied access to the property to install the LFC Network (for example where a landlord on site advises that they have not given their consent), the LFC does not have to proceed with (or complete) the installation and may cancel the Service Order and, in the case of denied access, may invoice the Service Provider the “unable to complete installation”/“inability to complete request” charge in the Price List. If the End User Premises belongs to an Exempted End User the LFC technician will not seek written confirmation of the End User’s agreement to the LFC (End User) Terms.

13.10 Once the scope of work at the End User Premises has been determined, the LFC technician may also seek additional specific written consent from the End User (or a person on site who represents the End User) to the actual installation works required, before commencing work. The LFC technician will try and explore alternative installation options, where practical, so long as the alternative does not add installation cost which is outside the most costly Standard Installation option or create unreasonable installation delay. If the End User (or a person on site who represents the End User) refuses to sign the consent form, and provided that at all times the LFC representatives have stipulated only reasonable specifications and conditions in the consent form presented to the End User (or a person on site who represents the End User), the LFC need not proceed with (or complete) the relevant installation and may cancel the Service Order and may invoice the Service Provider the “unable to complete installation”/“inability to complete request” charge in the Price List.

Apportionment of Costs Associated with SDU Non Standard Infrastructure Installation

13.11 The LFC will contribute to the cost of cable and other items of end user specific infrastructure with a premise boundary up to the Standard Installation limits.

13.12 The LFC may charge the Service Provider, developer or other third party for the incremental cost of a Non-Standard Install of End User-Specific Infrastructure to a SDU



in accordance with the rates set out in the Price List. If agreement to pay the additional cost for installation is not provided then the LFC will deem consent not to be provided and no cabling will be installed.

13.13 The LFC will notify the Service Provider that the Service Order requires a non-standard install within two days of completing the Scope Visit.

13.14 Within a further five days, the LFC will provide a binding quote, valid for 90 days, for the non-standard component of the work to the Service Provider or other party accepting costs, for acceptance before work proceeds,.

13.15 The total cost of cabling, the sum of the non-standard portion, will indicatively include some or all the items in the following non exhaustive list, but not any part required to be provided by the LFC as part of a Standard Installation:

(i) supply and installation of ducts and cable from road boundary to the ETP position;

(ii) supply and installation of turning and joining pits; and

(iii) reinstatement of surfaces on a like for like basis.

Complex Consents: SDUs

13.16 For a Single Dwelling Unit where the only reasonably practicable way to connect the SDU to the relevant FAP requires the LFC Network to cross either:

(i) property adjacent to the SDU which is privately owned by a third party and for which the End User does not have sufficient pre-existing rights to allow the LFC to install the LFC Network there; or

(ii) common private land in which the End User’s pre-existing rights are not sufficient to allow the LFC to install the LFC Network there,

consent is also required from affected third parties. The Service Provider will obtain the End User’s agreement to the LFC (End User) Terms and confirmation from the End User of landlord consent (if applicable). This will permit the LFC to access the SDU to, among other things, install the LFC Network required to provide the Service.

13.17 The Service Provider will confirm the End User has provided consent to the LFC (End User) Terms when placing the Service Request.

13.18 The LFC will obtain any third party consents necessary for the LFC to access the SDU and third party property or rights of way (as applicable) to install, maintain or remove LFC Network required to provide the Service. The LFC will need to determine legal ownership of the third party property and details of property owners, then seek consent. For a right of way where the LFC has installed common infrastructure in response to a previous Service Order the new Service Order will be treated in accordance with clauses 13.8 to 13.10 (Simple Consents).

13.19 The LFC will be unable to supply Services to a SDU until all applicable consents are obtained and installation of any connecting cabling that might be required is complete.

13.20 The LFC will make reasonable endeavours to obtain consent from all necessary building owners or landowners. In doing so, some or all of the following listed actions may be undertaken in attempting to gain consent:

(i) title search to determine property owner(s); and



(ii) consent letters sent to address of property owner(s);

and if no response:

(iii) initial phone call and follow-up calls to property owner(s).

If that fails to get response then:

(iv) online search to identify address and contact details;

(v) enquiry to Council;

(vi) Companies Office search;

(vii) consent letters sent to physical address; and

(viii) initial phone call and follow-up calls to physical address.

If that also fails to get response then:

(ix) re-sending of consent letters to any associated address for service;

(x) initial phone call and follow-up calls to associated contact; and

(xi) discretionary visit to the property where there are outstanding consents and the majority of consents have been obtained.

Where the Service Request is for a Standard Installation and all ownership details have been provided, the initial requests for consent will be submitted within 2 days of receiving the Service Request. The LFC will endeavour to obtain all necessary consents within 30 days. If no response is obtained to consent requests within a period of 30 days or if the LFC reasonably considers there is no likelihood of consent being negotiated at 30 days the LFC may deem consent to be unobtainable and the actions in 13.21 will be taken.

13.21 If the LFC is unable to get all consents required to carry out the installation work after trying to do so the LFC need not proceed with (or complete) the relevant installation and may cancel the Service Order but will not invoice the Service Provider the “unable to complete installation”/“inability to complete request” Charge or any other Charge in the Price List, for the cancelled Service Order.

13.22 Once all consents are obtained, if any doubt arises regarding the End User’s agreement to the LFC (End User) Terms during an installation, the LFC technician who attends the End User Premises to undertake installation may seek an evidential copy of the End User’s agreement to the LFC (End User) Terms, before commencing installation work. In the event that no evidential copy can be provided and the LFC technician requests the End User’s written agreement to the LFC (End User) Terms during the installation process, if the End User (or a person on site who represents the End User) refuses to sign the agreement form when requested by the LFC technician, or where for any other reason the LFC technician is denied access (for example where a landlord on site advises that they have not given their consent), the LFC does not have to proceed with (or complete) the installation and may cancel the Service Order and, in the case of denied access, may invoice the Service Provider the “unable to complete installation”/“inability to complete request” charge in the Price List. If the SDU belongs to an Exempted End User the LFC technician will not seek written confirmation of the End User’s agreement to the LFC (End User) Terms.



13.24 Once the scope of work at the End User Premises has been determined, the LFC technician may also seek additional specific written consent from the End User (or a person on site who represents the End User) to the actual installation works required, before commencing work. The LFC technician will try and explore alternative installation options, where practical, so long as the alternative does not add installation cost which is outside the most costly Standard Installation option or create unreasonable installation delay. If the End User (or a person on site who represents the End User) refuses to sign the consent form, and provided that at all times the LFC representatives have stipulated only reasonable specifications and conditions in the consent form presented to the End User (or a person on site who represents the End User), the LFC need not proceed with (or complete) the relevant installation and may cancel the Service Order and may invoice the Service Provider the “unable to complete installation”/“inability to complete request” Charge in the Price List.

Complex Consents MDUs

13.25 Complex installations are dealt with in clause 14:

13.26 If the LFC is unable to obtain, on reasonable terms, all consents necessary for the installation of any MDU cabling required to provide the Service, the LFC may at its discretion take further action by following the process defined in the code of practice associated with the Telecommunications Act 2001, if it is a signatory to the code.

13.27 Once LFC Network is installed in an MDU, any Service Request will be treated in accordance with clauses 13.8 to 13.10 (Simple Consents).

New Right of Way Requirements

13.28 The LFC will need to undertake the specified work which will include but may not be limited to that set out below:

(i) obtain written consent from the right of way owner, sub-divider, developer or their agent to cable the right of way (in some circumstances, the LFC may, at its option, require an easement);

(ii) if requested provide a detailed design of proposed right of way cabling;

(iii) obtain all necessary consents from authorities;

(iv) source materials and complete installation work; and

(v) test cabling against the fibre specification in Appendix D.

13.29 Once LFC Network is installed in a right of way, any Service Request will be treated in accordance with clauses 13.8 to 13.10 (Simple Consents).

Typical Complex SDU Consents Process

13.30 The various steps in the process the LFC will need to complete to install LFC Network in any third party property include a number of components each with its own specified time frame. These indicative tasks are listed below with estimated completion time and dependencies. Tasks may be undertaken concurrently or out of sequence if that is desirable to complete process in an efficient and timely manner. The estimated completion time in the below table shall have no bearing on the LFCs achievement of the provisioning Service Levels or Maximum Average Cycle Time, and are illustrative only.



Task Estimated completion

time (Business

Days)

Activities Dependencies and possible constraints

1. Determine ownership structure

1 ~ 5 Search titles of affected properties to determine ownership structure and consents required.

Initial request for consent will be submitted within 2 days of receiving Service Request subject to the Service Request being for a Standard Install and all ownership details being provided. Determining an address (which can be an issue with new sub-divisions or developments).

2. Consent for private property cabling

5 ~ 20+ Gain consent to cable from each property owner by mail; chase reticent owners then negotiate with those who decline consent. Progress to be reviewed at days 11, 16, 26 and 29 to ensure details are correct and consent is progressing.

Property owner, tenant or landlord (as applicable) may be difficult to identify and or contact. There may be extended approval processes especially for overseas owners. Property owner, tenant or landlord (as applicable) may request detailed scope of work prior to consent, in which case this step will occur after steps 3 and 4 and only consent to access property to scope work will be sought.

3. Site Survey / Plan Review

5 For a right of way a detailed site survey will be required to determine best possible method of cabling, location of FAPs, common equipment and entry points.

Property tenant or owner (as applicable), or their agent need to provide access to site.

4. Solution Design and Costing

5~20 Detailed design of right of way and lead-in cabling, entry points and common equipment.

Designer may need further information and/or site access. Steps 3 and 4 may precede consent if owners require detail. Note if consent given before design complete, work will still not commence until the design is complete.

5. Quote Acceptance

5 Acceptance of any additional costs and agreement to pay.

6. Material Supply and resource allocation

10 Service Requests and supply of cables, ducts and consumables. Scheduling of labour resource.

Materials on stock and labour available.

7. Installation of cables

10~15 Installation of cabling and associated hardware, restoration of surfaces etc.

No unforeseen issues, no waiting for other trades. Actual time will depend on site size and complexity.

8. Installation of lead-in, ETP and secure jack

4 Installation of lead-in cabling from FAP to building ETP and termination jack.



Apportionment of costs associated with ROW infrastructure Installation

13.31 The LFC will contribute to the cost of cable and other items of common and End User Specific Infrastructure in an ROW up to the Standard Installation limits set out in this Manual. In practice this will be applied on a per order basis. If there is one order, the LFC will contribute to the cost of providing one Standard Installation, with the balance being charged to the Service Provider. If there are several orders which together form the first order initiating the ROW build when several people in ROW have agreed to share initial build costs, the LFC will contribute to the costs of a Standard Install for each connection, with the balance of the total cost shared equally between the ordering Service Providers.

13.32 The LFC may charge the Service Provider, developer or other third party for the incremental cost of a Non-Standard Installation of the common and End User-Specific Infrastructure to a SDU in a ROW at the rates set out in the Price List. If agreement to pay the additional cost for the Non-Standard Installation is not provided then the LFC will deem consent not to be provided and no cabling will be installed.

13.33 The LFC will notify the Service Provider that the Service Request requires a Non-Standard Installation within two days of the Scope Visit.

13.34 Within a further 5 days, the LFC will provide a binding quote, valid for 90 days, for the non-standard component of the work to the ordering Service Provider or other party accepting costs for acceptance before work proceeds.

13.35 The total cost for the non-standard component of the work of cabling an ROW may indicatively include some or all of the items in the following non exhaustive list, but not any part required to be provided by the LFC as part of a Standard Installation:

(i) the cost of undertaking design;

(ii) supply and installation of ducts, pits and cable from road boundary to ROW to the ETP position; and

(iii) reinstatement of surfaces on a like for like basis.

13.36 For second and subsequent orders the same methodology described in the clauses above will be applied i.e:

(i) the LFC will contribute to the cost of additional cable and other items of common and end user specific infrastructure in an ROW or from ROW to premises or both, up to the Standard Installation limits set out in this Manual, with the balance of the total cost paid by the ordering RSPs; and

(ii) if there are several contemporaneous orders the LFC will contribute to the costs of a Standard Installation for each connection, with the balance of the total cost shared equally between the ordering RSPs.

14 Complex Multi Dwelling Unit (MDU) Consents Introduction

14.1 This clause 14 describes the consent process that will apply if consent is required from MDU owner(s) or their agents in relation to providing Services pursuant to the First MDU Order(s) or Aged Tenancy Order(s) in the relevant MDU.



14.2 As the consent process seeks consent for the work required to install a Residential or Business Connection and complete the MDU Common Infrastructure (if any) required to complete the First MDU Order (s) or Aged Tenancy Orders in the relevant MDU, it is unchanged if the End User Tenancy belongs to an End User who is a large business customer of the Service Provider (or a large business customer of a Reseller customer of the Service Provider) whenever the Service Provider has elected to treat them as an “Exempted End User”.

14.3 To enable the Service Provider to determine what, if any, work is required following a request for Service for an End User in an MDU, the LFC as part of the prequalification service will provide the following:

(i) confirmation that the premises are an MDU; and

(ii) consent status of the MDU - required, under action, gained or declined;

(iii) build status of the MDU - no infrastructure, under action or built.

14.4 To enable the LFC to determine what, if any, work is required to connect an MDU following a request for Service by an End User to the Service Provider, the Service Provider may need to gather information from the End User in addition to the normal service required, address and contact details. If the Service Provider is unable to provide the additional information requested below or the information is found to be incorrect then the Service Request may be delayed while additional information or consent is gained. This additional information should be provided to the LFC as part of the Service Request and include the following:

(i) confirmation that the premises are an MDU; and

(ii) whether other End User Tenancies serviced by the MDU are already taking Service via the Service Provider; and

(iii) any other relevant information provided by the End User.

If, based on information provided by LFC or gained from End User by Service Provider, it seems likely the Service Request will require some or all of the following: consent to access an MDU, adjacent third party property or use of third party fibre network or build of MDU Common Infrastructure or completion of the MDU Pre-requisite Steps, then the Service Provider should set an expectation with the End User that provision of the Service is subject to obtaining those consents and additional work, and therefore may be delayed. The Service Provider should also tell the End User that the LFC may call on the End User for assistance with obtaining such third party consents. The Service Provider should advise the End User that their details will be passed to the LFC who will contact them, and the Service Provider should ensure that the End User’s full contact details, as well as those for the MDU building owner or body corporate (as applicable), are included in the Service Request.

Consents

14.5 For a Subsequent MDU Order where the LFC has installed common infrastructure in response to a First MDU Order the Subsequent MDU Order will be treated in accordance with clauses 13.8 to 13.10 (Simple Consents).



14.6 The LFC will only proceed with (or complete) LFC Network installation after all applicable consents have been obtained, these are set out in clause 27.10 of the MDU Connection Process. Other consents that may be required include, but are not limited to, the following examples:

(i) council consent for work within drip line of notified trees on public land or road reserve or within the MDU or affected third party property boundaries;

(ii) neighbour consent for crossing private or shared land;

(iii) special consent for work on or within notified heritage buildings; and

(iv) special consent for work on or within archaeological or cultural areas.

14.7 For a consent for an MDU where the LFC Network currently ends at FAP or has only been extended to the building entry point of the MDU, consent is also required from affected third parties, such as building owners, to install MDU Common Infrastructure, between the building entry point and the End User Tenancies to provide network access to the End User Tenancies. Consent may also be required from other affected third parties to access the End User’s MDU or in a right of way situation where the only reasonably practicable way to connect the LFC Network is to cross adjacent third party property between the FAP and the MDU. If a right of way is involved, the process described in clause 13.18 may apply equally when it comes to connecting the MDU.

14.8 The LFC will be unable to supply Services to any End User Tenancy within the MDU until all applicable consents are obtained and installation of any MDU or connecting cabling that might be required is complete. If the LFC is unable to get all consents required to carry out the installation work after trying to do so, the LFC may take further action in line with the MBIE MUC code of practice to gain access to the MDU. If all attempts to gain access are unsuccessful, the LFC need not proceed with (or complete) the relevant installation and may cancel the Service Order but will not invoice the Service Provider the “unable to complete installation” / “inability to complete request” Charge or any other Charge in the Price List, in relation to the cancelled Service Order.

14.9 The LFC will make reasonable endeavours to obtain consent from all necessary building owners or landowners. In doing so some or all of the following listed actions may be undertaken in attempting to gain consent:

(i) title search to determine property owner(s); and

(ii) consent letters sent to address of property owner(s); if no response

(iii) initial phone call and follow-up calls to property owner(s).

If that fails to get response then:

(iv) online search to identify address and contact details;

(v) enquiry to Council;

(vi) Companies Office search; and

(vii) consent letters sent to physical address;

(viii) initial phone call and follow-up calls to physical address.



If that also fails to get response then:

(ix) re-sending of consent letters to any associated address for service;

(x) initial phone call and follow-up calls to associated contact; and

(xi) discretional visit to the property where there are outstanding consents and the majority of consents have been obtained.

Where the Service Request is for a Standard Installation and all ownership details have been provided, the initial requested for consent will be submitted within 2 days of receiving the Service Request. The LFC will endeavour to obtain all necessary consents within 30 days. If no response is obtained to consent requests within a period of 30 days or if the LFC reasonably considers there is no likelihood of consent being negotiated at 30 days the LFC may deem consent to be unobtainable and the actions in clause 14.8 may be taken.

14.10 If the LFC is unable to obtain, on reasonable terms, all consents necessary for the installation of any MDU cabling required to provide the Service, the LFC may at its discretion take further action by following the process defined in the code of practice associated with the Telecommunications Act 2001, if it is a signatory to the code.

14.11 The Service Provider may choose to provide the LFC with contact information for the MDU building owner or body corporate (as applicable) before they receive a Service Request from an End User, in which case the LFC may choose, but is not required, to proactively seek consent from that MDU building owner or body corporate (as applicable). The Service Provider should also advise the LFC if they are willing to assist the LFC with obtaining third party consents.

Newly Built MDU Building Requirements

14.12 The LFC may need to undertake the specified work which will include but may not be limited to that set out below:

(i) execute a commercial agreement with the Service Provider, MDU building owner, body corporate, developer or their agent to install cabling in the building;

(ii) if requested provide a detailed design of proposed building cabling including riser and floor access;



(v) test cabling against fibre specification in Appendix D.

Existing MDU Buildings Requirements

14.13 If the existing MDU building has no suitable cabling in place, then it will be treated as a newly built MDU building.



14.14 If the existing MDU building cabling is suitable or can be economically brought up to the LFC standard, then the LFC will need to, once consent is obtained from the MDU building owner or body corporate (as applicable):

(i) execute a commercial agreement with the Service Provider, MDU building owner, body corporate, developer or their agent to take over, purchase or lease the building cable;

(ii) if requested provide a detailed design of any proposed changes to the building cabling including riser and floor access;



(v) test cabling against fibre specification in Appendix D.

Typical Cabling Process

14.15 The various steps in the process the LFC will need to complete to install LFC Network in an MDU include a number of components each with its own specified time frame. These are listed below with target completion time and dependencies. If crossing other third party property is necessary to access the MDU from the FAP then the steps described in clause 13.20 may also be applicable. Tasks may be undertaken concurrently or out of sequence if that is desirable to complete process in an efficient and timely manner. The estimated completion time in the below table shall have no bearing on the LFCs achievement of the provisioning Service Levels or Maximum Average Cycle Time, and are illustrative only.


time (Business

Days)


1. Determine need for consent (including ownership structure)


Initial request for consent will be submitted within 2 days of receiving Service Request subject to the Service Request being for a Standard Install and all ownership details being provided. Determining an address (which can be an issue with new MDU or developments).

2. Consent for MDU cabling

Unknown Provision of consent to access and cable MDU to an End User Tenancy. Progress to be reviewed at days 11, 16, 26 and 29 to ensure details are correct and consent is progressing.

MDU building owner or body corporate (as applicable) may be difficult to identify and or contact. There may be extended approval processes especially for overseas owners.

MDU building owner or body corporate, tenant or landlord (as applicable) may request detailed scope of work prior to consent, in which case this step will occur after steps 3 and 4 and only consent to access property to scope work will be sought.




time (Business

Days)


3. Signing of an agreement for MDU cabling

5 Checking of supplied documentation for accuracy, internal sign off, contract execution, set up of accounts and allocation of resource.

MDU building owner or body corporate (as applicable), needs to have credit guarantee and contact information for WSA.


10 For an existing building, a detailed site survey will be required to determine best possible method of cabling, location of risers, common equipment and entry points.

For a new building, a detailed plan review will be required to determine best possible method of cabling, location of risers, common equipment and entry points.

MDU building owner or body corporate (as applicable), or their agent needs to provide access to site and or plans.

5. Solution Design and Quote

10~20 Detailed design of backbone and horizontal cabling, entry points and common equipment.

Designer may need further information and or site access.

Steps 4 and 5 may precede consent if owners require detail. Note if consent given before design complete, work will still not commence until the design is complete.

6. Consents Unknown Application for and receipt of fire, building, roadway, tree, etc. consents.

Authority may need further information and/or site access.

7. Quote Acceptance

5 Acceptance by Service Provider and/or building owner of costs and agreement to pay.

MDU building owner or body corporate (as applicable), may need further information and/or redesign.


10 Service Requests and supply of cables, frames and consumables.

Scheduling of labour resource.





time (Business

Days)



10~15 Installation of cabling and associated hardware, fire sealing penetrations, restoration of surfaces etc.

No unforeseen issues, no waiting for other trades.

Actual time will depend on MDU size and complexity.

10. Installation of lead-in

6 Installation of lead-in cabling from FAP to building.

Roadway consents. This may occur at the time of communal

infrastructure deployment.

11. Testing 5 Cable testing from central office to ETP.

Apportionment of Costs Associated with MDU Infrastructure Installation

14.16 For the lead-in from the road or ROW boundary to the MDU entry point the LFC will contribute to the cost of conduit, cable and other items of common and end user specific infrastructure up to the Standard Installation limits. The LFC will contribute to the cost of providing one Standard Installation, with the balance being charged to the building owner or other party accepting costs e.g. developer or a group of tenancy owners.

14.17 For small MDUs1 where the end tenancy is served from a point externally to the building (generally the local cabinet), the LFC will contribute to the cost of cable and other items of common and end user specific infrastructure in an MDU up to the cost limits set out in the Price List, with the balance of the end user specific infrastructure cost charged to either the ordering RSP or other party accepting costs e.g. building owner, or developer or a group of tenancy owners.

14.18 For all other MDUs the LFC will contribute to the cost of cable and other items of common and end user specific infrastructure in an MDU up to the cost limits set out in the Price List, with the balance of the total cost charged to either the building owner or other party accepting costs e.g. developer or a group of tenancy owners.

14.19 The incremental cost of a Non-Standard Install of Common Infrastructure to an MDU at the rates set out in the Price List (if any) will be recovered from the party identified in clauses 14.16 or 14.17. The LFC will provide a quote for the incremental cost of the non-standard component of the work to the party accepting costs for acceptance before work proceeds. If agreement to pay the additional cost for installation is not provided then the LFC will deem consent not to be provided and no cabling will be installed.

14.20 The LFC will notify the RSP that the Service Request requires a non-standard install within two days of the Scope Visit.

1 Indicatively, such MDUs are likely to contain less than 12 End User Tenancies.



14.21 Within a further 20 days the LFC will provide a binding quote, valid for 90 days, for the non-standard component of the work to the building owner, ordering RSP or other party accepting costs for acceptance before work proceeds.

14.22 The total cost of cabling an MDU will include some all or all the items in the following indicative list:

(i) the cost of undertaking consents and design;

(ii) supply and installation of; ducts, racks, frames, passive optical equipment and cable, vertically and horizontally from entry point or MDU frame to MDU tenancy ETP position;

(iii) the cost of meeting external authority requirements e.g. fire stopping;

(iv) inter-building ducts and cabling in a multi-building MDU; and

(v) reinstatement of external and internal surfaces on a like for like basis.

14.23 The LFC may choose to only partially complete the build initially e.g. only complete MDU frame, riser cabling and floor frames, but will not seek additional payment for work within initial scope when it is completed and will be required to meet appropriate SLAs for second and subsequent orders.

Individual Tenancy Installations in absence of completing the MDU Connection Prerequisite Steps

14.24 If the LFC has not completed the MDU Connection Pre-requisite Steps within 30 days and consent is not still under negotiation, or consent is declined, it will notify the Service Provider(s) who placed the First MDU Order and any Subsequent MDU Orders relating to that MDU that the LFC has not been able to complete the MDU Connection Pre-requisite Steps and advise that the order(s) may be treated as Aged Tenancy Order(s) and installed as individual Connections if the Service Provider(s) wishes. The Service Providers then have 10 days to request that the First MDU Order and any Subsequent MDU Orders be treated as Aged Tenancy Order(s) or they will be cancelled.

14.25 If the Service Provider(s) requests that the LFC attempt to obtain the necessary permissions and consents required to install the individual Connection for an Aged Tenancy Order (with no MDU Common Infrastructure necessarily being installed in the MDU to connect the relevant tenancy). The LFC will use its reasonable endeavours to:

(i) Request all necessary permissions and consents (from the MDU owner(s) and any other parties such as, the relevant local authority or neighbours) required by Law to carry out the work to install the Residential or Business Connection as an individual Connection; and

(ii) Request the MDU owner(s) agreement to such conditions as the LFC may reasonably require in order to meet any relevant statutory, regulatory or local authority requirements (including requirements relating to weather tightness of the MDU) applying to the LFC in relation to installing the Residential or Business Connection as an individual Connection; and

(iii) Provide the Service Provider(s) who placed the Aged Tenancy Order(s) with a quote(s) for any Charges pursuant to the Price List (including Wholesale New Connection - Non Standard Install charges) and seek agreement from the Service Provider (s) to pay the Aged Tenancy Connection costs;



14.26 Where the LFC has gained consent for an Aged Tenancy Order pursuant to clause 14.24 above, then any further orders for Residential or Business Connections in that MDU will require the order to follow consent process as a First MDU Order.

14.27 If the LFC finds on commencing the MDU Connection Pre-requisite Steps, that the MDU tenancy can be built as if it was an SDU without additional consents, it will notify the Service Provider(s) who placed the First MDU Order and any Subsequent MDU Orders relating to that MDU that the LFC is able to complete the order(s) by treating them as SDU Order(s) and installed as individual Connections.

14.28 Where the LFC has completed a First MDU Order pursuant to clause 14.27 above, then any further orders for Residential or Business Connections in that MDU will follow the order and consent process for an SDU order.

15 Non-Building Access Point (NBAP) Consents Introduction

15.1 A Non-Building Access Point or NBAP examples are locations that either are not a premises (e.g. the location is a cell site or pumping station) or do not have a physical address (e.g. the location is a bus shelter or lamp post). Concentration points for a regulated backhaul service are not NBAPs (for example, a fibre to the node cabinet owned or controlled by the LFC).

15.2 This clause 15 describes the consent process that will apply if Service is required to an NBAP. If the NBAP is contained in or built upon an End User Premises that is either:

(i) an SDU that is either a single residential or commercial occupancy within the boundary of the premises; or

(ii) an End User Tenancy that is the occupancy of an End User (for example, an apartment, townhouse, office or shop) in an MDU that has had suitable common infrastructure installed,

the process described in clause 13 will apply. If the MDU doesn’t have suitable common infrastructure installed to an End User Tenancy, the MDU process described in clause 14 will apply to install the common infrastructure, then the process in clause 13 will apply.

15.3 The Service Provider will have the initial contact with an End User wanting service. The LFC needs the End User to consent to or, if the End User is the tenant, procure consent to, access to the NBAP to operate the LFC Network (including installation, maintenance, removal, etc.) so that Services can be provided. The consent process differs if the Service Provider determines that the NBAP will not be treated like an End User Premises. If so, the Service Provider will be responsible for getting all consents, including all third party consents that are required for immediately adjacent private property.

15.4 The process for the LFC to obtain consent to access an NBAP and to protect the LFC Network once installed, is for the Service Provider (or its Reseller customer) to obtain the End User’s agreement to the LFC (End User) Terms, at the same time as the End User agrees to the Service Provider’s terms and conditions. The Service Provider will, before the Service Request is submitted:



(i) provide the LFC (End User) Terms to the End User, by appropriate means which could include an on-line link or electronically; and

(ii) record the End User’s agreement to the LFC (End User) Terms, by appropriate means which could include by having the End User complete an online confirmation or tick box.

15.5 The LFC will provide the Service Provider with a copy of its current standard form of the LFC (End User) Terms, either as a physical copy of the LFC (End User) Terms or by other electronic means, including (by way of example) by providing a link to where the LFC (End User) Terms are available online or issuing the Service Provider with an email attaching a copy of the LFC (End User) Terms. The LFC (End User) Terms will include the right for the LFC to require the End User to physically sign an additional consent form at the time of installation, confirming that the End User has agreed to be bound by the LFC (End User) Terms. The LFC will not require the Service Provider to obtain written evidence of agreement to the LFC (End User) terms. However, the Service Provider may be asked by the LFC to demonstrate that the Service Provider complied with the requirements described in clause 15.4 above during the 3 months after the Service Start Date. If the LFC is not satisfied by the evidence provided by the Service Provider, the LFC may try to sign the End User up to the LFC (End User) Terms directly during that 3 month period after the Service Start Date.

15.6 Installations in NBAPs will fall into two categories:

(i) Simple - where the LFC Network (lead-in cable) will not cross another property between the FAP and the NBAP, therefore no additional consent is required (apart from End User or landlord consent, if applicable); or

(ii) Complex - where the only reasonably practicable way to connect the LFC Network to the NBAP is for the LFC Network to cross other property in which case, consent is also required from affected third parties (as well as End User or landlord consent, if applicable).

The diagram below provides some examples of Simple and Complex NBAP installations

Distribution Fibre Fibre Cabinet

Your NBAP on Footpath External Test

Point (ETP)

Your Fibre Lead-in

Fibre Access Point (FAP)

Optical Network

Terminator

Grassed Footpath Area

Road

Your NBAP on private land with consent required


Optical Network Terminator

Con

sent

requ

ired

for

priv

ate

prop

erty

‘Simple Installation’




15.7 To enable the LFC to determine whether an NBAP installation is Simple or Complex, the Service Provider will need to gather information from the End User in addition to the normal service required, location or address and contact details. This additional information will be provided to the LFC as part of the Service Request and includes the following:

(i) confirmation whether the LFC or the Service Provider is responsible for obtaining access consent for the NBAP;

(ii) whether the End User is the sole or joint owner of the NBAP or a tenant or occupier under some other occupation right. If the End User is not the sole or joint owner, the Service Provider will get the End User to agree to obtain the landlord’s consent. It is the End User’s responsibility to obtain any landlord consents; and

(iii) whether the NBAP is in such a location that the End User believes that the LFC Network will cross another property between the NBAP and the road and, if so, details of that other property and its owner or occupier.

If a Service Request for an NBAP requires consent to access adjacent third party property or other telecommunications network, then the Service Provider should set an expectation with the End User that provision of the Service is subject to obtaining those consents and therefore may be delayed. The Service Provider should also tell the End User that the LFC may call on the End User for assistance with obtaining such third party consents. The Service Provider should advise the End User their details will be passed to the LFC who will contact them, and the Service Provider should ensure that the End User’s full contact details are included in the Service Request.

15.8 The provisioning Service Levels, including the LFC’s obligation to proceed with (or complete) LFC Network installation, only apply from the time that all applicable consents have been obtained. Other consents that may be required and the absence of which would prevent the application of provisioning Service Levels include, but are not limited to, the following examples:

(i) landowner consent where tenant has requested service for a rented or leased property;

(ii) council consent for work within drip line of notified trees on public land or road reserve or within the NBAP or affected third party property boundaries;

(iii) neighbour consent for crossing private or shared land;

(iv) special consent for work on or within notified heritage buildings; and

(v) special consent for work on or within archaeological or cultural areas. NBAP Simple Consents

15.9 For an NBAP where the LFC Network (lead-in cable) will not cross another property between the FAP and the NBAP, no additional consent is required (apart from consent from the End User or landlord, if applicable). The Service Provider will obtain the End User’s agreement to the LFC (End User) Terms and confirmation from the End User of landlord consent (if applicable). This will permit the LFC to access the NBAP to, among other things, install the LFC Network required to provide the Service.



15.11 The Service Provider will confirm that the End User has provided its consent and the landlord’s consent (if applicable) when submitting the Service Request.

15.12 If any doubt arises regarding the End User’s agreement to the LFC (End User) Terms during an installation, the LFC technician who attends the NBAP to undertake installation may seek an evidential copy of the End User’s agreement to the LFC (End User) Terms, before commencing installation work. In the event that no evidential copy can be provided and the LFC technician requests the End User’s written agreement to the LFC (End User) Terms during the installation process, if the End User (or a person on site who represents the End User) refuses to sign the agreement form when requested by the LFC technician, or where for any other reason, the LFC technician is denied access to the NBAP to install the LFC Network (for example where a landlord on site advises that they have not given their consent), the LFC does not have to proceed with (or complete) the installation and may cancel the Service Order and, in the case of denied access, may invoice the Service Provider the “unable to complete installation” / “inability to complete request” Charge in the Price List.

15.13 Once the scope of work at the NBAP has been determined, the LFC technician may also seek written consent from the End User (or a person on site who represents the End User) to the actual installation works required, before commencing work. The LFC technician will try and explore alternative installation options, where practical, so long as the alternative does not add installation cost which is outside the most costly Standard Installation option or create unreasonable installation delay. If the End User (or a person on site who represents the End User) refuses to sign the consent form, the LFC need not proceed with (or complete) the relevant installation and may cancel the Service Order and may invoice the Service Provider the “unable to complete installation” / “inability to complete request” Charge in the Price List.

Complex Consents

15.14 For an NBAP where the LFC Network must cross third party property between the FAP and the NBAP, consent is also required from affected third parties. The Service Provider will obtain the End User’s agreement to the LFC (End User) Terms and confirmation from the End User of landlord consent (if applicable). This will permit the LFC to access the NBAP to, among other things, install LFC Network required to provide the Service.

15.15 The Service Provider will confirm the End User has provided consent to the LFC (End User) Terms when placing the Service Request.

15.16 The LFC will obtain any third party consents necessary for the LFC to access the NBAP and third party property or rights of way (as applicable) to install, maintain or remove LFC Network required to provide the Service. The LFC will need to determine legal ownership of the third party property and details of property owners, and then seek consent; this is expected to take a minimum of 20 days. In a location where the LFC has installed common infrastructure in response to a previous Service Order the new Service Order will be treated in accordance with clauses 15.9 to 15.12 (NBAP Simple Consents).



15.18 The LFC will be unable to supply Services to the NBAP until all applicable consents are obtained and installation of any connecting cabling that might be required is complete. If the LFC is unable to get all consents required to carry out the installation work after trying to do so the LFC need not proceed with (or complete) the relevant installation and may cancel the Service Order but will not invoice the Service Provider the “unable to complete installation” / “inability to complete request” Charge or any other Charge in the Price List, in relation to the cancelled Service Order.

15.19 The LFC will make reasonable endeavours to obtain consent from all necessary building owners or landowners. In doing so some or all of the following listed actions may be undertaken in attempting to gain consent:

(i) title search to determine property owner(s); and (ii) consent letters sent to address of property owner(s); and if no response: (iii) initial phone call and follow-up calls to property owner(s). If that fails to get response then:

(iv) online search to identify address and contact details; (v) enquiry to Council; (vi) Companies Office search; (vii) consent letters sent to physical address; and (viii) initial phone call and follow-up calls to physical address. If that also fails to get response then:

(ix) re-sending of consent letters to any associated address for service; (x) initial phone call and follow-up calls to associated contact; and (xi) discretional visit to the property where there are outstanding consents and the

majority of consents have been obtained. Where the Service Request is for a Standard Installation and all ownership details have been provided, the initial requested for consent will be submitted within 2 days of receiving the Service Request. The LFC will endeavour to obtain all necessary consents within 30 days. If no response is obtained to consent requests within a period of 30 days or if the LFC reasonably considers there is no likelihood of consent being negotiated at 30 days the LFC may deem consent to be unobtainable and the actions in 15.16 will be taken.



15.21 Once all consents are obtained, if any doubt arises regarding the End User’s agreement to the LFC (End User) Terms during an installation, the LFC technician who attends the NBAP to undertake installation may seek an evidential copy of the End User’s agreement to the LFC (End User) Terms, before commencing installation work. In the event that no evidential copy can be provided and the LFC technician requests the End User’s written agreement to the LFC (End User) Terms during the installation process, if the End User (or a person on site who represents the End User) refuses to sign the agreement form when requested by the LFC technician, or where for any other reason the LFC technician is denied access (for example where a landlord on site advises that they have not given their consent), the LFC does not have to proceed with (or complete) the installation and may cancel the Service Order and, in the case of denied access, may invoice the Service Provider the “unable to complete installation” / “inability to complete request” Charge in the Price List.

15.22 Once the scope of work at the End User’s NBAP has been determined, the LFC technician may also seek written consent from the End User (or a person on site who represents the End User) to the actual installation works required before commencing work. The LFC technician will try and explore alternative installation options, where practical, so long as the alternative does not add installation cost which is outside the most costly Standard Installation option or create unreasonable installation delay. If the End User (or a person on site who represents the End User) refuses to sign the consent form, the LFC need not proceed with (or complete) the relevant installation and may cancel the Service Order and may invoice the Service Provider the “unable to complete installation” / “inability to complete request” Charge in the Price List.

NBAP Requirements

15.23 The LFC may need to undertake special design or process development to facilitate connection of Services into an NBAP. This additional work prior to installation would be undertaken in discussion with the Service Provider, End User, Service Company and equipment supplier (as applicable). This work would include some or all of the following:

(i) assessment of the NBAP as a suitable location for LFC equipment, considering services provided, environment, power and access;

(ii) modification or alternate source requirements for any LFC equipment;

(iii) any additional consents from authorities;

(iv) source of special materials;

(v) development of special installation work practises including any assure requirements; and

(vi) quoting of installation costs.

15.24 If the NBAP is the same or effectively the same as a previously provisioned NBAP (e.g. another mobile phone cell site just further from road), then the LFC may agree, but is not required, to reuse the previous design with or without a change to the installation price.

15.25 However, if a suitable design for the provision of the Service to the NBAP cannot be agreed, after following the Escalation Protocol, the LFC is not required to provide the Service to the NBAP.

15.26 A typical NBAP Cabling Consents Process is consistent with the typical SDU consent process.



15.27 The various steps in the process the LFC will need to complete to install LFC Network to an NBAP include a number of components each with its own specified time frame. These are listed below with estimated completion time and dependencies. The estimated completion time in the below table shall have no bearing on the LFCs achievement of the provisioning Service Levels or Maximum Average Cycle Time, and are illustrative only.


time (Business

Days)


1. Determine ownership structure


Initial request for consent will be submitted within 2 days of receiving Service Request subject to the Service Request being for a Standard Install and all ownership details being provided. Determining an address (which can be an issue with NBAPs, new sub divisions or developments).

2. Consent for private property cabling

5 ~ 20+ Gain consent to cable from each property owner by mail, chase reticent owners then negotiate with those who decline consent.

Property owner, tenant or landlord (as applicable) may be difficult to identify and/or contact. There may be extended approval processes especially for overseas owners. Property owner, tenant or landlord (as applicable) may request detailed scope of work prior to consent, in which case this step will occur after steps 3 and 4 and only consent to access property to scope work will be sought.


5 A detailed site survey will be required to determine best possible method of cabling, location of FAPs, common equipment and entry points.

Property tenant or owner (as applicable), or their agent need to provide access to site.

4. Solution Design and Costing

5 Detailed design of common and lead-in cabling, entry points and common equipment.

Designer may need further information and/or site access. Steps 3 and 4 may precede consent if owners require detail.

5. Quote Acceptance 5 Acceptance of any additional costs and agreement to pay.


10 Service Requests and supply of cables, ducts and consumables. Scheduling of labour resource.



10~15 Installation of cabling and associated hardware, restoration of surfaces etc.

No unforeseen issues, no waiting for other trades. Actual time will depend on site size and complexity.

8. Installation of lead-in, ETP and secure jack

4 Installation of lead-in cabling from FAP to building ETP and termination jack.



PART 7 – HANDOVER CONNECTION AND TIE CABLE INSTALLATION

16 Handover Connection Overview

16.1 Service Providers will require one or more UFB Handover Connections at the Handover Point to pick up the applicable Bitstream Services for the Coverage Area. The UFB Handover Connection will deliver the traffic to the MOFDF at the appropriate Central Office POI requested by the Service Provider. A list of the POIs for each area is provided in Appendix E.

Connection Options

16.2 When the Service Provider places a UFB Handover Connection Service Request, the LFC will supply and install a Handover Connection as a termination on the MOFDF. The Service Provider will also need to request an additional service to get the traffic to its network and/or equipment. The additional services available from the LFC to extend the Handover Connection from the termination at the MOFDF are:

(i) a Tie Cable to the Service Provider Footprint located within the Central Office described in clause 17.2(i) provided under the Central Office and POI Co-location Service;

(ii) a Tie Cable to another Service Provider’s Footprint located within the Central Office described in clause 17.2(ii) provided under the Central Office and POI Co-location Service;

(iii) a Tie Cable between the Service Provider or third party network outside and adjacent to the Central Office manhole and the MOFDF described in clause 17.2(iii) provided under the Central Office and POI Co-location Service. The connection to the third party network may be by the TPAD service under the TPAD Service Description;

(iv) a Direct Fibre Access Service between the Central Office MOFDF and the Service Provider POI within the Central Office Coverage Area provided under the Direct Fibre Access Service;

(v) a Bandwidth Fibre Access Service between the Central Office MOFDF and the Service Provider POI within the Central Office Coverage Area provided under the Bandwidth Fibre Access Service;

(vi) an Intra Candidate Area Backhaul Service between the Central Office MOFDF and the Service Provider Footprint (provided under the Central Office and POI Co-location Service) located within another Central Office within the same Candidate Area provided under the Intra Candidate Area Backhaul Service;

(vii) an Inter Candidate Area Backhaul Service between the Central Office MOFDF and the Service Provider Footprint (provided under the Central Office and POI Co-location Service) located within another Central Office (whether in the same or different Candidate Area) within a different Candidate Area provided under the Inter Candidate Area Backhaul Service; or



(viii) combinations of services described in paragraphs (iv) or (v) with those in (vi) and (vii) to reach the Service Provider POI and the Service Provider Footprint (provided under the Central Office and POI Co-location Service) located within another Central Office (whether in the same or different Candidate Area).

16.3 The LFC responsibilities:

(i) the LFC will name all UFB Handover Connections and record these in the LFC’s system for managing fibre inventory;

(ii) the LFC will terminate the UFB Handover Connection on the MOFDF (including its splice or connection to the options in clause 16.2 above); and

(iii) the LFC is responsible for the repair and/or replacement of faults in the UFB Handover Connection and faulty termination at the MOFDF.

17 Tie Cable Installation Introduction

17.1 To use a Bitstream Service in conjunction with equipment co-located in their Footprint in the Central Office or elsewhere a Service Provider will need to have a Tie Cable between the Central Office MOFDF and their equipment. To provide services over the Bitstream Service the Service Provider may also need to have a Tie Cable between the Central Office MOFDF and their Footprint.

Types of Tie Cables

17.2 There are three types of Tie Cable available for Service Providers who take the Bitstream Services:

(i) an internal Tie Cable from the Central Office MOFDF to the Service Provider footprint;

(ii) an internal Tie Cable from one Service Provider Footprint to another Service Provider Footprint provided under the UFB Co-location Service (the footprints can be same or different Service Providers or a third party backhaul provider); or

(iii) an external Tie Cable from the Central Office MOFDF to a third party network manhole outside and adjacent to the Central Office manhole.

These Tie Cables can be used to connect Bitstream Services or UFB Handover Connections or backhaul to the Footprint and are provided under the Central Office and POI Co-location Service.

17.3 A Service Provider may supply its own Tie Cables or the Service Provider may ask the LFC to supply Tie Cables. In either case the Tie Cables must meet the specification set out in the LFC’s Cable Specification document.

17.4 The Tie Cable Service installation charges set out in the Price List will apply.

17.5 The Tie Cable Service is described further in the Central Office and POI Co-location Service Description and the Central Office and POI Co-location Service Operations Manual.

17.6 For the avoidance of doubt only the LFC contractors may undertake work on the Central Office MOFDF or anywhere else in Central Office outside of Service Provider’s Footprint.



PART 8 – SERVICE TEMPLATES AND THE PRODUCT DEVELOPMENT PROCESS

18 Service Templates Overview

18.1 The Bitstream 2, Bitstream 3 and Bitstream 3a Services support a set of modular and reusable components, which are either already included in existing Service Templates set out in the relevant Service Descriptions or can be easily combined, or modified, by Service Providers to create new Service Templates. The Product Development Process set out in this Part 8 does not apply to the Bitstream 4 Service.

18.2 A Service Template is a composite of these reusable components, the attributes associated with these reusable components and the attributes’ values that when combined result in a new variant of the Bitstream 2, Bitstream 3 or Bitstream 3a Service.

18.3 Service Templates may include one or combinations of the following changes:

(i) new composites of standard building blocks (reusable components);

(ii) modified values of existing attributes of these building blocks;

(iii) new attributes of existing building blocks with new values; and / or

(iv) new components, e.g. introduction of new technology or features as agreed between the LFC and the Service Provider.

18.4 The Service Templates model is based on creating Product Offers using a Product Service Resource (PSR) model that is premised on the TM Forum Shared Information (SID) model

19 Building Blocks Overview

19.1 The standard building blocks are a set of modular and reusable components, which can be added to an existing Service Template or combined as to create new Service Templates.

Building Blocks

19.2 These building blocks include layer 1 components, access speeds, VLANs, ATA and UNI ports, and Multicast. The standard building blocks are detailed in the table below:

Building Block Description Associations and restrictions

GPON E-APL GPON based Ethernet Virtual Private Line that supports discrete VLANs. Attributes include:

- High Priority CIR (increments of 2.5 Mbps upstream and/or downstream);

- Low Priority EIR (increments of 10 Mbps upstream and/or downstream).

Requires the End User to consume an input service that includes Baseband plus requires UFB Handover Connection for delivery to Service Provider.




GPON E-APL GPON based Ethernet Private Line that supports transparent VLAN. Attributes include:

- High Priority CIR (increments of 2.5 Mbps upstream and/or downstream);

- Low Priority CIR (increments of 2.5 Mbps upstream and/or downstream);

- Low Priority EIR (increments of 10 Mbps upstream and/or downstream).

Requires the End User to consume an input service that includes Baseband plus requires a UFB Handover Connection for delivery to Service Provider.

P2P E-APL GPON based Ethernet Private Line that supports transparent VLAN. Attributes include:

- Line rates of 100 Mbps, 1 Gbps or 10Gbps. - High Priority (increments of 10 Mbps

symmetrical) - EIR (increments of 100 Mbps symmetrical)

Requires a UFB Handover Connection for delivery to Service Provider.

HD video channel 10 Mbps Multicast HD video channel with signalling back channel.

Can be incremented in blocks of 10 Mbps multicast bandwidth.

Can be delivered on same UNI Ethernet Port as E-AVPL when delivered through one Service Provider but requires separate port on E-APL services or where the Service Provider is different to the Service Provider using the existing E-AVPL UNI.

Requires the End User to consume an input service that includes Baseband plus requires Multicast Domain for delivery to Service Provider.

ATA Voice A Voice service, delivered using SIP and a G.711a codec with an RJ11 ATA port on ONT.


Baseband includes one ATA Voice service.

Second Ethernet port

Additional RJ45 Ethernet port on ONT.

This can then be used for:

- E-AVPLs; and/or - Multicast; or - E-APL


Wi-Fi port Wi-Fi port on ONT connected to a bitstream service.

Attributes to be defined.

Requires either same or additional GPON access link and UNI port plus requires E-NNI port for delivery to Service Provider.

Multicast Domain A geographic area that supports Multicast streams. Attributes include:

- Number of Multicast channels. - Business rules around delivery of Multicast

streams.

Requires UFB Handover Connection for delivery to Service Provide.

Multicast requires tight coupling with Service Provider media broadcast platforms and will require customisation and integration testing.

P2P Dark Fibre P2P Dark Fibre from MOFDF or Footprint at Central Office to End User Premises or Service Provider Premises or NBAP (as applicable)

Requires Footprint at either local or distant Central Office if associated with backhaul service.

Layer 1 enhanced SLA

Enhanced assurance Service Levels for layer one services either SLA 1, SLA 2 or SLA 3

Applies to fibre component of GPON and P2P services.

Layer 2 enhanced SLA

Enhanced assurance Service Levels for layer two services either SLA 1 or SLA 2

Applies to bitstream component of GPON and P2P services.




Diversity Provision of a second instances of a P2P or P2MP based service with special physical characteristics either one, some or all of following:

- Diverse route; - Diverse End User Premises or Service

Provider Premises or NBAP (as applicable) access;

- Diverse Central Office access; or - Diverse Central Office.

Applies to fibre component of P2P or P2MP services as diversity to the primary service.

Co-location footprint

Provision of a 600x400mm footprint in an LFC Central Office

Includes building access for authorised personnel, 19” rack up to 2.7m high and environmental support.

Co-location power Single 48V DC supply to Footprint Requires Footprint.

RF overlay Delivery of video programming to designated end user ONT RF port.

This will only be developed based on demand.

Requires either same or additional GPON or P2P access link and special ONT with RF port and injection port for delivery to Service Provider.

19.3 Non-standard building blocks may be requested and will be provided if they meet the prioritisation criteria below. It is expected that the standard building block list will be increased over time as Service Providers utilise the Product Development Process.

19.4 The following are examples of default Service Templates:

Access Speed

Bitstream Type

Plan ATA Voice

Low Priority High Priority (CIR) High Priority CIR

Upstream Downstream Upstream Downstream

30M/10M

E-AVPL 10M 30M 2.5M 2.5M

Includes Baseband with one ATA Voice

service

E-AVPL 10M 30M 2.5M 10M

E-AVPL 10M 30M 5M 5M

100M/50M E-AVPL 50M 100M 2.5M 10M

0M ATA Voice only 0M 0M 0M 0M

100M/100M E-APL 2.5M CIR (upstream and

downstream), EIR to Access Speed

CIR options (symmetrical) are incremental, starting at 2.5M and

10M; from 10M there are additional increments of 10M up to 100M, e.g.

20M, 30M, etc. 100M/100M E-APL N/A

Education 30M/30M

E-AVPL 30M 30M 10M 10M



20 Product Development Process 20.1 A Service Provider may request that the LFC create additional Service Templates as

follows:

(i) Using combinations of one more of the set of standard building blocks listed in the table above.

(ii) Using other services or attributes requested by the Service Provider and agreed by the LFC.

20.2 Service Templates can be added incrementally to an existing service offer, or supplied as a stand-alone package. In particular:

(i) Stand alone packages must include Baseband. Stand alone packages mean that the End User connection does not need to consume any other Service Templates in order for services to be provided.

(ii) Incremental packages can be added as an additional service to an End User who is already consuming one or more Service Templates.

(iii) Baseband is a required service for all End User connections. If the Service Template that includes Baseband is removed from an End User connection and an incremental Service Template remains, then Baseband will be added to the incremental Service Template for that End User.

Product Development Process

20.3 The Product Development Process will be further detailed in the Service Provider Guide. At a high level it will proceed as follows:

(i) Service Provider submits request for an additional Service Template, outlining all of the reusable or custom components that will be required;

(ii) the LFC will confirm the prioritisation, requirements and commercials. Standard building blocks will have published prices in the price book;

(iii) iterative and cooperative prototyping and testing of the template using the Integrated Test Facility. The degree of testing will vary, particularly if custom components are requested;

(iv) following completion of testing and both parties’ acceptance, an agreed deployment schedule based on the prioritisation process and available resources; and

(v) the Service Template will move into a production environment.

20.4 Deployment of an additional Service Template will require:

(i) successful completion of the prototyping and testing; and

(ii) agreed commercials and pricing.



21 Prioritisation Process Overview

21.1 Requests for additional Service Templates will be implemented and delivered through the Product Development Process. The Product Development Process includes determination of pricing, development, testing and implementation.

21.2 The LFC will comply with the Service Provider’s request under clause 20.3(i) in a timely manner. In the event that demand for new Service Templates exceeds the LFC’s agreed capacity to deliver the new Service Templates then the LFC may prioritise the Service Template requests.

Prioritisation

21.3 Prioritisation of Service Provider’s access to the LFC’s laboratories will be on a first come first served basis.

21.4 Prioritisation of additional Service Templates will be non-discriminatory and based on the following criteria:

(i) expected and forecast demand for the Service Template;

(ii) complexity and resources available to build the Service Template;

(iii) development and implementation of any custom building blocks; and

(iv) resources available to deploy the Service Template into the production fulfil, assure, billing and network environments.

21.5 Higher priority will be given to the development of additional Service Templates that are requested by multiple Service Providers and require the minimum of system changes.

22 Development of New Templates Additions to Existing Primary Templates

22.1 A Primary, or standalone, template is one that includes Baseband. End Users do not need to consume other Service Templates in order for the template to be provided.

22.2 All new Primary templates and their pricing must be based the Bitstream base reference offers relevant for the resultant service either:

(i) for Residential Bitstream 2 – 30 Mbps/10 Mbps with 2.5 Mbps /2.5 Mbps CIR; (ii) for Business Bitstream 2 - 30 Mbps/10 Mbps with 5 Mbps /5 Mbps CIR; (iii) for Business Bitstream 3/3A - 100 Mbps/100 Mbps with 2.5 Mbps /2.5 Mbps

CIR; (iv) for Education Bitstream 2 - 30 Mbps/30 Mbps with 10 Mbps /10 Mbps CIR; or (v) for Education Bitstream 3A - 100 Mbps/100 Mbps with 10 Mbps /10 Mbps CIR.

22.3 Building blocks cannot be less than the relevant base reference offer specified in 21.2, only new components added. This excludes the reduction in EIR as CIR increases in Bitstream 3A templates, for which there is no price reduction.

22.4 For Bitstream 2 templates CIR cannot exceed 100 Mbps downstream and 50 Mbps upstream. The sum of EIR and CIR cannot exceed a 110 Mbps downstream or 52.5 Mbps upstream.



22.5 For the GPON Bitstream 3/3A templates neither the EIR nor the CIR cannot exceed 100 Mbps downstream and 100 Mbps upstream.

22.6 E-AVPLs and E-APLs can be used within the same template but must be used via separate UNI ports. There is no restriction on the combination of separate services on separate ports.

22.7 There are no charges for multiple OVCs and bandwidth can be divided among OVCs using the increments in clause 19.2.

22.8 The standard and diversity installation charges for a new template are the same as template from 22.2.

22.9 For Bitstream 2 templates the CIR of all primary and secondary templates on an ONT cannot exceed 100 Mbps downstream and 50 Mbps upstream. The sum of EIR and CIR cannot exceed 110 Mbps downstream and 52.5 Mbps upstream.

22.10 For Bitstream 3/3A templates the sum of all primary and secondary templates on an ONT the EIR and CIR cannot exceed 100 Mbps downstream and 100 Mbps upstream.

Example of Addition to a Primary template 22.11 The following is an example of the pricing of an addition to an existing primary template

where a Service Provider requires a service with the following characteristics:

(i) Residential Service; (ii) one ATA Voice port; (iii) one UNI port; and (iv) Access Speed 50/20 EIR Mbps with 15/5 Mbps CIR to support:

• One E-AVPL OVC for RGW management (2.5 Mbps CIR symmetric);

• One E-AVPL OVC for Internet (50/20 Mbps EIR with 2.5 Mbps CIR symmetric);

(v) one E-AVPL OVC for Video on Demand (10 Mbps CIR downstream) Based on Bitstream 2 template 1 which is 30/10 Mbps with 2.5/2.5 Mbps CIR priced at $37.50 the Service Provider requires the following additional items:

(vi) 20/10 Mbps EIR; and (vii) 12.5/2.5 Mbps CIR.

Item CIR EIR Price

(indicative only)

Down Up Down Up

Existing UNI port 2.5 Mbps 2.5 Mbps 30 Mbps 10 Mbps $37.50

ATA Voice port

Additional Bandwidth 12.5 Mbps $6.25

2.5 Mbps $2.50

20 Mbps $2.70

10 Mbps $2.70

Total 15 Mbps 5 Mbps 50 Mbps 20 Mbps $51.65



New Secondary Templates

22.12 A secondary template is one that can be added as an additional service to an End User who is already consuming one or more templates, one of which must be a primary template. A Service Provider that consumes a secondary template is considered the Secondary Service Provider. There can be multiple Secondary Service Providers.

22.13 There must be a primary template at the ONT for the duration of the secondary template. If the Primary Service Provider relinquishes their service then all Secondary Service Providers will be notified and either:

(i) one Secondary Service Provider agrees to become the Primary Service Provider by changing their secondary template to a primary template; or

(ii) all Secondary Service Providers must relinquish their secondary template.

22.14 It is recommended that if Secondary Service Providers intend to become a Primary Service Provider under these scenarios that they request a primary template variant of their secondary template. This primary template would include baseband and be priced according to the primary template pricing rules.

22.15 The pricing of Secondary templates is based on the price for the incremental building blocks requested by the service provider using the price points outlined in the UFB Reference Offer Price List. These include:

(i) UNI Ethernet port;

(ii) ATA Voice port;

(iii) WiFi port;

(iv) High Priority bandwidth (CIR) in increments of 2.5 Mbps upstream and/or downstream;

(v) Low Priority bandwidth (CIR) in increments of 2.5 Mbps upstream and/or downstream;

(vi) Low Priority bandwidth (EIR) in increments of 10 Mbps upstream and/or downstream;

(vii) Video ports and/or Multicast; and

(viii) Other items added in from time to time to the UFB Reference Offer Price List.

22.16 E-AVPLs and E-APLs can be used within the same template but must be used via separate UNI ports. There is no restriction on the combination of separate services on separate ports.

22.17 There are no charges for multiple OVCs and bandwidth can be divided among OVCs using the above increments.

22.18 The minimum secondary template is 1xUNI with one OVC of 2.5/2.5 CIR.



Example of Secondary template

22.19 The following is a generic example of the pricing of a secondary template to where a Service Provider requires a service with the following characteristics:

(i) one UNI;

(ii) one E-AVPL OVC for RGW management (2.5 Mbps CIR symmetric);

(iii) one E-AVPL OVC for Internet (50/20 Mbps EIR with 2.5 Mbps CIR);

(iv) one E-AVPL OVC for Video on Demand (10 Mbps CIR downstream).

Item CIR EIR Price (indicative only) Down Up Down Up

Additional UNI $10.00

OVC 1 2.5 Mbps $1.25

2.5 Mbps $2.50

OVC 2 2.5 Mbps $1.25

2.5 Mbps $2.50

50 Mbps $6.75

20 Mbps $5.40

OVC 3 10 Mbps $5.00

Total 15 Mbps 5 Mbps 50 Mbps 20 Mbps $34.65

23 Integrated Test Facility Overview

23.1 The Integrated Test Facility (ITF) comprises the laboratories described below and services that support Service Providers in development and testing of new and existing Service Templates.

23.2 The ITF is designed to foster research and development through collaboration and testing of new and existing Service Templates.

23.3 The ITF will enable Service Providers to have practical experience and thus educate themselves on fibre technology and applications.

Layer 2 Development Laboratory

23.4 The Layer 2 Development Laboratory provides a GPON bitstream service prototyping and testing facility.



23.5 The laboratory environment allows Service Providers to connect remotely between their internal test facilities and the laboratory, providing between the Service Provider Premises and the Layer 2 Development Laboratory:

(i) one or more GPON fibre connections; and

(ii) a Direct Fibre Access Service connecting to a UFB Handover Connection in the Layer 2 Development Laboratory.

23.6 The Layer 2 Development Laboratory supports:

(i) the testing of agreed in-production Service Templates, e.g. for the purposes of integration testing with Service Provider networks or CPE; and

(ii) the prototyping of new Service Templates or combinations as part of the Product Development Process.

Layer 1 Test Laboratory

23.7 The Layer 1 Test Laboratory provides a site for Layer 1 technical training, particularly around home wiring and installation.

Network Integration Laboratory

23.8 The Network Integration Lab (NIL) provides a site for technical laboratory for the purposes of technical and formal testing.

23.9 The NIL is suitable for:

(i) Detailed Technical Acceptance Testing;

(ii) Business Acceptance Testing;

(iii) prototyping new technology, where the Layer 2 development Lab is not appropriate;

(iv) detailed fault finding; and

(v) provides pre-staging and staging environments for the layer 2 production networks.

OSS/BSS Test Stub

23.10 The OSS/BSS Test Stub is a managed and supported intelligent stub test on boarding environment to support Service Providers B2B development.

23.11 The OSS/BSS Test Stub covers both fulfil and assure schemas and contains the core transactions.

23.12 The OSS/BSS Test Stub environment is able to deal with future and current releases to allow Service Providers to test for what the LFC is planning on releasing as well as when a Service Provider makes changes in their environment and needs to retest against the current schema.



PART 9 – FIBRE DIVERSITY

24 Diversity via additional service instances

Overview

24.1 Each Bitstream Service is provided over a single fibre between the LFC’s Central Office and the End User Premises or Service Provider Premises or NBAP (as applicable). Diversity will be available as a second or subsequent instance of the applicable Bitstream Service between the End User Premises or Service Provider Premises or NBAP (as applicable) and Central Office. Standard Installation Charges and Service Levels do not apply to diversity products that involve diverse access to the End User Premises or Service Provider Premises or NBAP (as applicable) or access to a Central Office that is not the local Central Office. Each instance of the applicable Bitstream Service, primary and diverse, will be treated as an individual line for the purpose of availability Service Levels.

24.2 Diversity will be available to Priority Users taking Bitstream 4 on request for Connections located in major health-care facilities, secondary or tertiary education centres, central business districts, industrial parks, business parks and strip malls.

24.3 Diversity is designed as a value added service for customers who require high reliability connectivity for critical business applications. Diversity begins with the design during the network build process, with a targeted architecture approach based on the type of area covered, and at the highest level will include on-going management to ensure core network paths remain diverse.

24.4 The diverse optical paths will be in separate fibre cable sheaths, have separate MOFDF termination shelves, and if requested in separate cable routes. The diverse cable routes will be a minimum of the width of a street apart, and should not share any manholes or access points. Separate entries into the Central Office will be used where available. Diversity that is not on separate cable routes is simply a second order for the UFB fibre service.

24.5 Service providers can also request diverse access to End User Premises or Service Provider Premises or NBAP (as applicable) or access to diverse Central offices as part of a Non-Standard Install; however this will not necessarily be available in all cases.

24.6 Where practical the LFC will also provide diversity for Bitstream 2, Bitstream 3 and Bitstream 3a, and Bitstream 4 in situations other than those listed in the Bitstream 4 Service Description on request, as an additional Service.

24.7 There may be practical limitations to providing full physical diversity to some sites. The provision of a separate entry to either an LFC Central Office or End User Premises or Service Provider Premises or NBAP (as applicable) will have unique site specific engineering considerations and may attract additional costs.



Pricing of diverse Bitstream Services

24.8 The pricing of diversity for Priority Users for Bitstream 4 Connections located in major health-care facilities, secondary or tertiary education centres, central business districts, industrial parks, business parks and strip malls is as follows:

(i) Diversity provided by the use of two Connections which share the same access to the End User Premises or Service Provider Premises or NBAP (as applicable) and the same access to the local Central Office with diverse routes from FAP to Central Office, as described in clause 24.10(i) below, will attract standard connection Charge for first connection as set out in Appendix 1 of the Price List and a diverse connection Charge for the second Connection as set out in Appendix 3 Table A item 1.4 of the Price List and standard rental Charge as set out in Appendix 2 for each Connection;

(ii) Diversity provided by the use of two Connections with either diverse access to the End User Premises or Service Provider Premises or NBAP (as applicable) and sharing the same access to the local Central Office with diverse routes from FAP to Central Office, as described in clause 24.10(ii) below, will attract standard connection Charge for first Connection as set out in Appendix 1 of the Price List and a diverse connection plus a diverse access installation Charge for the second Connection as set out in Appendix 3 Table A item 1.5 of the Price List and standard rental Charges as set out in Appendix 2 for each Connection. Construction of a diverse lead-in to the End User Premises or Service Provider Premises or NBAP (as applicable), will be deemed to be a non-standard install;

(iii) Diversity provided by the use of two Connections with either diverse access to the End User Premises or Service Provider Premises or NBAP (as applicable) and diverse access to the local Central Office with diverse routes from FAP to Central Office, as described in clause 24.10(iii) below, will attract standard connection Charge for first Connection as set out in Appendix 1 of the Price List and a diverse connection plus a diverse access installation Charge for the second Connection as set out in Appendix 3 Table A items 1.5 and 1.6 of the Price List and standard rental Charges as set out in Appendix 2 for each Connection. Construction of a diverse lead-in to the End User Premises or Service Provider Premises or NBAP (as applicable), will be deemed to be a non-standard install;

(iv) Diversity provided by the use of two Connections the first to the local Central Office and the second with a diverse route directly to an adjacent Central Office that is not the local Central Office but one where the service area boundary adjoins that of the local Central Office, with diverse routes from FAP to relevant Central Office as described in clause 24.10(iv) below, will attract standard connection Charge for first Connection as set out in Appendix 1 of the Price List and a diverse connection Charge for the second Connection as set out in Appendix 3 Table A items 1.5 and 1.6 of the Price List and standard rental charges as set out in Appendix 2 for each Connection;



(v) Diversity provided by two Connections the first to the local Central Office and the second with a diverse route to a distant Central Office that is neither the local nor adjacent Central Office, as described in clause 24.10(iv) below and with diverse routes from FAP to relevant Central Office as described in clause 24.10(iv) below, will attract standard connection Charge for first connection as set out in Appendix 1 of the Price List and a diverse connection Charge for the second Connection as set out in Appendix 3 Table A items 1.5 and 1.6 Price List and standard rental Charges as set out in Appendix 2 for each Connection plus backhaul rental Charges for the diverse connection as set out in Appendix 2 section 5 of the Price List; and

(vi) Connections involving diverse access to the End User Tenancy will attract standard time and materials installation and standard rental charges as set out in Price List.

The installation of diversity in any situations other than the ones set out in this clause 24.8 above will attract standard time and materials installation and rental charges as set out in Price List. The LFC will advise the Service Provider of the installation cost of the diversity request when the Service Request is placed.

Ordering of diverse Bitstream Access Services

24.9 To order a diverse Bitstream Access Service the Service Provider must include the following information with the Service Request:

(i) indicate that it is a request for a diverse circuit;

(ii) which fibre access it is diverse to; and

(iii) the level of diversity required.

Types of Diversity

24.10 There are 4 main types of diversity:

(i) single Central Office redundancy with diverse route;

(ii) single Central Office redundancy with diverse route and diverse access to End User Premises or MDU or NBAP (as applicable);

(iii) single Central Office redundancy with diverse route, diverse access to End User Premises or MDU or NBAP (as applicable) and diverse access to Central Office; and

(iv) dual Central Office redundancy with diverse route, diverse access to End User Premises or MDU or NBAP (as applicable) and access to a separate Central Office.

Where the MDU has diverse access, the LFC may extend this diverse access at the request of the End User to the End User Tenancy (where available) at additional cost based on standard time and materials installation charges as set out in the Price List.



Types of Diversity Diagram

Adja

cent

Cen

tral

Offi

ce E

ntry

Poi

nt

Loca

l Cen

tral

Offi

ce E

ntry

Po

int

Loca

l C

Offi

ce

1

2

3

4

5

End User site can have single or diverse entry and

single or diverse riser

Local LFC Central Office Area

Single Central Office redundancy with diverse route

24.11 Single Central Office redundancy with diverse route requires 2 fibres, on separate routes, from the End User Premises or MDU or NBAP (as applicable) to a single Central Office. This option is show as “1” and “2” in diversity diagram and has the following characteristics:

(i) the fully diverse routes will converge at the common FAP;

(ii) the LFC will design for redundancy within defined business areas and will offer diverse feeder fibres as far as the FAP only as a basic service;

(iii) each fibre access service will be priced at the rate in the Price List; and

(iv) each fibre access service will have assure Service Levels. Enhanced Service Levels may be offered and charged for at the rate in the Price List.

24.12 This option may include diverse access to the End User Premises or MDU or NBAP (as applicable).



Single Central Office redundancy with diverse route and diverse access to Central Office

24.13 Single Central Office redundancy with diverse route and diverse access to Central Office requires 2 fibres, on separate routes, from the End User Premises or MDU or NBAP (as applicable) to a single Central Office with a separate manhole and OFDF at the Central office. This option is show as “1” and “3” in diversity diagram and has the following characteristics:

(i) each fully diverse routes will have its own lead-in from a separate FAP to the ETP, OFDF or equivalent;

(ii) each fully diverse routes will have its own manhole and entrance to a separate OFDF at the Central Office;

(iii) the LFC will design for redundancy within defined business areas;

(iv) each fibre access service will be priced at the rate in the Price List; and

(v) each fibre access service will have assure Service Levels. Enhanced Service Level Terms may be offered and charged for at the rate in the Price List.


Dual Central Office redundancy with diverse route and access to a separate Central Office

24.15 Dual Central Office redundancy with diverse route and access to a separate Central Office requires 2 fibres, on separate routes, from the End User Premises or MDU or NBAP (as applicable) to a second Central Office with a separate manhole and OFDF at the Central office and a second lead-in to End User Premises or MDU or NBAP (as applicable). This option is show as “1” and “4” in diversity diagram and has the following characteristics:

(i) not available in locations with only one Central Office;

(ii) each fully diverse routes will have its own lead-in from a separate FAP to the ETP, OFDF or equivalent;

(iii) each fully diverse routes will have its own Central Office;

(iv) the LFC will design for redundancy within defined business areas;

(v) each fibre access service will be priced at the rate in the Price List; and

(vi) each fibre access service will have an assure Service Levels. Enhanced Service Levels may be offered and charged for at the rate in the Price List.




Diverse access to End User Tenancy at MDU

24.17 Where diverse access has been or is being provided to an MDU, this can be extended by the LFC at the request of the End User to an End User Tenancy (where available). This option has the following characteristics:

(i) each fully diverse route within the MDU will have fibre from a separate FAP to the ETP, OFDF or equivalent;

(ii) each fibre access Service will be priced at the rate set out in the Price List; and

(iii) each fibre access service will have assure Service Levels. Enhanced Service Levels may be offered and charged for at the rate set out in the Price List.

24.18 The diagram below shows dual Central Office redundancy with diverse route, diverse

access to End User Premises or MDU or NBAP (as applicable) and diverse access to the Central Office.

Div

erse

MD

U

Entry

Poi

nt

Cabinet(FFP) M

DU

Ent

ry P

oint

MDU containing End User Tenancy

Building Optical Fibre Distribution

Frames (OFDF)

Cabinet(FFP)

End User Floor

Direct Fibre

Access Service

End User Tenancy

Riser Cable

Diverse Riser Cable

LFC Central Office Building

LFC Equipment

LFC Equipment

Direct Fibre

Access Service

LFC Equipment

LFC Equipment



PART 10 - BILLING

25 Billing

Invoicing

25.1 The LFC will invoice the Service Provider for all charges on the basis specified in the Price List. Invoices will be in an electronic bill format (eBill). eBill will replace the provision of a paper invoice, except that a printed GST summary will be provided to the Service Provider. A hard copy paper invoice will be available to Service Providers at the price set out in the Bitstream Price List.

25.2 The eBill must include the following information:

(i) Service Identifier; (ii) Fault or Service Order identifier; (iii) Any Core Service Rebates; and (iv) Type of fee.

25.3 The LFC will transmit the eBill using a secure web portal. The eBill can be accessed through a web browser. Alternatively, the Service Provider can arrange with the LFC to write scripts and access the eBill through a script platform.

25.4 The Service Provider will provide the LFC with the list of people that are authorised to download the eBill file. The LFC will set up access rights for these people on a secure web portal.

25.5 The LFC will provide the eBill and the printed GST summary to the Service Provider free of charge.

25.6 The LFC will maintain one or more separate Service Provider accounts for services provided to the Service Provider. The LFC may alter the account structure as it considers appropriate.

Billing Enquiries

25.7 If the Service Provider wishes to raise a billing enquiry, it may do so by emailing the LFC billing team in the first instance at the billing email address supplied by the LFC under clause 2.

25.8 The email must include the following information:

(i) a header reading 'Billing Query'; and (ii) a completed Billing Enquiry Form.

25.9 The LFC will acknowledge the query and will use all reasonable endeavours to respond within the current billing period. Any billing enquiries submitted without the use of a Billing Enquiry Form will be rejected.

25.10 Additional billing information, over and above that reasonably required to assist Service Providers in interpreting invoices, will be charged in accordance with the Price List. The Service Provider may require the LFC to provide a quote for any such request for further information.

25.11 The process set out in clause 25.7 is an informal enquiry process that does not limit the General Terms. If the Service Provider wishes to claim an Invoice Error in an invoice, it must follow the procedure set out in clause 7 of the General Terms.



PART 11 – OPERATIONAL READINESS PROGRAMME

26 Service Provider on Boarding

26.1 The Operational Readiness Programme is the programme of work to be undertaken jointly by the LFC and the Service Provider as part of an on boarding process as the Service Provider prepares for connection to the LFC Network, including;

(i) the establishment of commercial relationships;

(ii) set up of OSS/BSS interfaces;

(iii) build of Footprints (if required);

(iv) build of UFB Handover Connections and associated circuits (if required);

(v) training as per clauses 26.11 and 26.12; and

(vi) the testing and commissioning of processes, products and interfaces (including layer 2 interoperability).

Each task within the on-boarding plan has appropriate service levels, milestones, the LFC and Service Provider requirements. The diagram below provides an overview of the plan.

26.2 The items in paragraphs 26.1(i) to 26.1(iii) of the on boarding process are specific to on boarding of the Service Provider to enable consumption of UFB services, e.g. execution of commercial agreements and staff training, and the Service Levels set out in this Part 11, subject to:

(i) delay in the provision of materials or information to be supplied by the Service Provider, required to complete the item;

(ii) acts or omissions of Service Providers that prevent the LFC from completely item e.g. making staff available for training; and

(iii) any period of extension agreed between the Service Provider and an End User or between the LFC and the Service Provider.

26.3 The items in paragraphs 26.1(iv) to 26.1(vi) of the on boarding process, that involve provision of UFB services e.g. Handover Connection or Co-location Footprint, will be subject to the Service Levels in the appropriate Service Level Terms, including any service level extensions in those terms.



26.4 The diagram below provides an overview of the plan with indicative timings.

Commercials

26.5 The Service Provider will be required to sign a WSA and meet the requirements of the General Terms before they can take the Bitstream Services.

26.6 The Service Provider must provide all information required in a timely manner as any delay will extend the service level time. This information includes details of insurance, credit guarantee and contact information for the WSA.

OSS/BSS

26.7 The LFC’s OSS/BSS is required to enable the Service Provider to place and track Service Requests and Service Orders for UFB Services, to report faults and to obtain other operational information.

26.8 The Service Provider needs to have the OSS/BSS system in place and staff available for training.

26.9 Set up of the OSS/BSS requires the LFC to allocate passwords and test interfaces including processing trial Service Requests.

Residential Service Provider On Boarding - Overview

Working days1 255 3010 15 20

Commercials

OSS/BSSSet up

Prepare Initial Co-location Quote

35 40

OSS/BSSTraining

BAU orders

Initial Co-location Build

Accept Order Initial DFAS / ICABs Link Build Configure and

Test Layer 2

Initial Tie Cable Build

Install Test P2P Circuits

Install ITF Test Circuits

Accept Order Initial Handover Connection Build

On Boarding Initial Build



26.10 The LFC will provide training to the Service Provider staff which includes:

(i) explanation of guides, products, processes, procedures and tools;

(ii) submission of test Service Requests;

(iii) handling exceptions; and

(iv) Q & A.

26.11 The LFC will provide reasonable initial set up training consisting of a workshop held at a location determined by the LFC. The workshop will address:

(i) overview of forecasting templates;

(ii) overview of forms for Service Requests;

(iii) basic details of OSS/BSS (including demonstration of the system);

(iv) overview of billing and accounts; and

(v) Q & A.

26.12 The Service Provider will ensure that a reasonable number of staff (up to a maximum number of 10 per session) attend any training provided. The Service Provider may choose to train only a limited number of staff initially to facilitate the placing of the infrastructure orders with a second session(s) on the wider order and assure processes once they are ready to go market.

26.13 Any additional training required by the Service Provider beyond reasonable initial set up training (up to 50 hours) may be charged for by the LFC in accordance with the Price List.

Co-location

26.14 If a Service Provider requires co-location space, the Service Provider may place an initial Service Request with all required information once the OSS/BSS is in place and their staff are trained in its use.

26.15 The LFC will provide quotes for co-location build, once these are accepted the co-location build will commence subject to the provision of any materials or information required from Service Provider. On acceptance of the co-location build, the footprints will be handed over to the Service Provider.

26.16 The provision of a Co-location Footprint and any associated ancillary services will be subject to the Service Levels in the Central Office and POI Co-location Service Level Terms.

Handover Connection or backhaul

26.17 If a Service Provider requires a UFB Handover Connection and/or backhaul, the Service Provider may place an initial Service Request with all required information when signing WSA or they can wait until the OSS/BSS is in place and their staff are trained in its use.

26.18 The LFC will commence build subject to the provision of any materials or information required from Service Provider. On completion of joint testing the links will be handed over to the Service Provider.

26.19 The provision of a Handover Connection will be subject to the Service Levels in the Bitstream Service Level Terms.



DFAS or ICABs

26.20 If a Service Provider requires a link from their UFB Handover Connection to their Premises, the Service Provider may place an initial Service Request with all required information once the OSS/BSS is in place and their staff are trained in its use.

26.21 The LFC will commence build subject to the provision of any materials or information required from Service Provider. On completion of joint testing, the links will be handed over to the Service Provider.

26.22 The provision of any ICABS or DFAS link associated with the Handover Connection will be subject to the Service Levels in the Direct Fibre Access Service Level Terms.

Tie Cables

26.23 If a Service Provider requires Tie Cables for their co-location space, the Service Provider may place initial Service Requests with all required information once the OSS/BSS is in place and their staff are trained in its use.

26.24 The LFC will provide quotes for Tie Cable build, once these are accepted build will commence subject to the provision of any materials or information required from Service Provider. On completion of the build the Tie Cables will be handed over to the Service Provider.

26.25 The provision of any Tie Cable will be subject to the Service Level in the Central Office and POI Co-location Service Level Terms.

Testing

26.26 If a Service Provider requires test circuits, the Service Provider may place initial Service Requests with all required information once the OSS/BSS is in place and the Service Provider’s staff are trained in its use. The LFC will provide test circuits for Service Provider and if required trial fault and relinquish them.

26.27 If a UFB Handover Connection Service has been requested, once it is installed and the Service Provider has all their equipment installed and available for testing. The LFC will undertake a series of end to end layer 2 testing scenarios with the Service Provider. The service level assumes all test milestones passed on first attempt with no remedial work required.

Integrated Test Facility

26.28 The Service Provider can request access to the Integrated Test Facility in circumstances where the Service Provider determines that it does not wish to install test circuits on its premises.

26.29 Initially this facility is limited to GPON services. Operational requirements for the Integrated Test Facility are not included in this Manual and will be discussed with Service Providers on a case by case basis.

BAU

26.30 Once on boarding and testing is successfully complete the Service Provider can place Service Requests for Bitstream Services.



PART 12 – MDU Connection Process

27 Introduction

27.1 The MDU Connection Process is the programme of work to be undertaken by the LFC after receipt of the First MDU Order to install the first Residential or Business Bitstream Connection in the MDU and install any MDU Common Infrastructure including:

(i) Receipt of First MDU Order (see clauses 27.4 to 27.5);

(ii) Confirm MDU status (see clause 27.6);

(iii) Design and, if necessary, quote for the installation of the first Residential or Business Connection in the MDU and the installation of any MDU Common Infrastructure (see clauses 27.7 to 27.10);

(iv) Obtain permissions and consents and, if necessary, agreement to conditions and payment of costs (see clauses 27.11 to 27.13); and

(v) Install the first Residential or Business Bitstream Connection in the MDU and install any MDU Common Infrastructure (see clause 27.15).

27.2 The tasks summarised above (and detailed in the clauses below) will take the following maximum periods to complete:

(i) Items in clauses 27.1.1 to 27.1.3 – completed within 20 business days from receipt of the First MDU Order;

(ii) Item in clause 27.1.4 – completed within 30 days from receipt of the First MDU Order (unless the LFC or MDU owner(s) and/or End User(s) (as applicable) agree to extend this time period); and

(iii) Item in clause 27.1.5 – completed on or before the First MDU Connection Date.

Receipt of Order

27.3 The MDU Connection Process starts when the LFC receives the First MDU Order.

27.4 On receipt of the First MDU Order the LFC will use its reasonable endeavours to promptly complete the tasks set out in clauses 27.5 to 27.12 (MDU Connection Pre-requisite Steps). While these steps are set out sequentially, The LFC may elect to perform them in a different order where practical or with steps in parallel to accelerate completion of the MDU Connection Pre-requisite Steps.

Confirm MDU status

27.5 The LFC will confirm whether a Connection has already been installed in the MDU or not. Subject to clause 27.15 below, if a Connection has already been installed in the MDU then the MDU Connection Process does not apply to the MDU and the order will proceed as a Subsequent MDU Order.



Design and Quote for installation of the Connection and any MDU Common Infrastructure

27.6 The LFC will, if necessary, obtain consent of the MDU owner(s) to access an MDU to undertake any preparatory assessment and investigation work to complete the design and, if necessary, quote for the cost of installing the first Bitstream Connection and MDU Common Infrastructure (if any).

27.7 Upon obtaining any consent required and undertaking any preparatory assessment and investigation work required, the LFC will then undertake a building cable network design to ensure the future needs of the MDU’s End Users can be meet in an efficient manner, factoring in factors such as building structure, capacity requirements, lead-in from boundary (including any diversity requirement), housing of OFDFs (including any splitters), compliance with fire codes, compliance with building codes and any other relevant statutory, regulatory or local authority requirements. This exercise includes determining what MDU Connection Infrastructure (if any) is to be installed. The LFC may use an existing standard building cable network infrastructure or design which is suitable for the MDU.

27.8 The scope of the work The LFC will undertake in installing the first Residential or Business Connection and the extent of the MDU Common Infrastructure to be installed (if any) will vary depending on the MDU and design requirements. However, at a minimum, on completion of the installation of the first Residential or Business Connection:

(i) The LFC will be able to meet the Service Levels for all Subsequent MDU Orders. For the purposes of measuring Service Levels for Subsequent MDU Orders, all Subsequent MDU Orders are deemed to be for Standard Installations for Residential or Business Connections; and

(ii) There will be no additional MDU Non Standard Install charges to End User, MDU owner(s) or the Service Provider(s) to install Connections and provision Services to tenancies (including End User Tenancies or Service Provider tenancies) for any Subsequent MDU Orders in the MDU.

27.9 The LFC will determine the installation costs that will be incurred by the LFC when installing the first Residential or Business Connection and the MDU Common Infrastructure (if any) and will determine the portion of those costs, if any, that the MDU owner(s) are liable for in accordance with the Price List (MDU Owner Costs).

Obtaining approvals and consents

27.10 The LFC will:

(i) Request all necessary permissions and consents (from the MDU owner(s) and any other parties such as, the relevant local authority or neighbours) required by Law to carry out the work to install the first and subsequent Residential or Business Connection and MDU Common Infrastructure (if any); and

(ii) Request the MDU owner(s) agreement to such conditions as the LFC may reasonably require in order to meet any relevant statutory, regulatory or local authority requirements (including requirements relating to weather tightness of the MDU) in relation to installing the first and subsequent Residential or Business Connection and the MDU Common Infrastructure (if any); and



(iii) If the LFC intends to recover all or some of the MDU Owner Costs from the MDU Owner(s) then the LFC will provide the MDU owner(s) with a quote for the relevant MDU Owner Costs and request agreement from the MDU owner(s) to pay the costs set out in the quote.

27.11 Once the LFC has completed the MDU Connection Pre-requisite Steps in clauses 27.5 to 27.10, including receipt of the MDU owner(s) payment of the MDU Owner Cost Quote (if any).; the LFC will advise the Service Provider and the MDU owner(s) of the First MDU Connection Date (calculated in accordance with clause 1.3 of Appendix 1 of the Service Level Terms for Bitstream Services).

27.12 Subject to clause 27.15 below, if the LFC has not completed the MDU Connection Pre-requisite Steps within 30 days of receipt of the First MDU Order it will cancel the order (unless The LFC or MDU owner(s) and/or End User(s) (as applicable) agree to extend this time period).

Installing the first Residential or Business Connection and MDU Common Infrastructure

27.13 After completion of the MDU Connection Prerequisite Steps, the LFC must complete the installation of the first Residential or Business Connection for the First MDU Order (and provision the Layer 2 services ordered in relation to that Residential or Business Connection (if any)) and the MDU Common Infrastructure (if any) by the First MDU Connection Date.

Reporting to Service Providers

27.14 Following receipt of the First MDU Order, the LFC will advise the Service Provider when the status of the order changes or on a weekly basis if there has been no status change so that Service Provider can monitor the progress of the order through the steps in the MDU Connection Process.

Individual Tenancy Installations in absence of completing the MDU Connection Prerequisite Steps

27.15 If the LFC has not completed the MDU Connection Pre-requisite Steps within 30 days and consent is not under negotiation, or consent is declined, it will notify the Service Provider(s) who placed the First MDU Order and any Subsequent MDU Orders relating to that MDU that the LFC has not been able to complete the MDU Connection Pre-requisite Steps and advise that the order(s) may be treated as Aged Tenancy Order(s) and installed as individual Connections if the Service Provider(s) wishes. The Service Providers then have 10 days to request the orders be treated as Aged Tenancy Order(s) or they will be cancelled.

27.16 If the Service Provider(s) requests that the LFC attempt to obtain the necessary permissions and consents required to install the individual Connection for an Aged Tenancy Order (with no MDU Common Infrastructure necessarily being installed in the MDU to connect the relevant tenancy). The LFC will use its reasonable endeavours to:

(i) Request all necessary permissions and consents (from the MDU owner(s) and any other parties such as, the relevant local authority or neighbours) required by Law to carry out the work to install the Residential or Business Connection as an individual Connection; and



(ii) Request the MDU owner(s) agreement to such conditions as the LFC may reasonably require in order to meet any relevant statutory, regulatory or local authority requirements (including requirements relating to weather tightness of the MDU) in relation to installing the Residential or Business Connection as an individual Connection; and

(iii) Provide the Service Provider(s) who placed the Aged Tenancy Order(s) with a quote(s) for any Charges pursuant to the Price List (including Wholesale New Connection - Non Standard Install charges) and seek agreement from the Service Provider (s) to pay the Aged Tenancy Connection costs. Noting these costs will be subject to the LFC contribution of $1,000 and when at a later date the MDU infrastructure is complete the LFC contribution tenancy calculation will be reduced by the number of Aged Tenancy orders completed.

27.17 Once the LFC has completed the Aged Tenancy Order Steps in clause 27.16, including receipt of the Service Provider(s) payment of the cost quote (if any), the LFC will:

(i) advise the Service Provider and the MDU owner(s) of the Connection Date (within 30 business days (or such later date agreed between the Service Provider and relevant End User) of receipt of acceptance of costs by the Service Provider(s)); and

(ii) install the Connection and provision Layer 2 services ordered in relation that Residential or Business Connection (if any);

27.18 Where the LFC has completed installation of an Aged Tenancy Order pursuant to clauses 27.15 to 27.17 then the provisions relating to Subsequent MDU Orders including the Service Levels in clauses 1.1 and 1.2 of Appendix 1 of the Service Level Terms for Bitstream Services will not apply to any further orders for Residential or Business Connections in that MDU.

27.19 If the LFC finds on commencing the MDU Connection Pre-requisite Steps, that the MDU tenancy can be built as if it was an SDU without additional consents, it will notify the Service Provider(s) who placed the First MDU Order and any Subsequent MDU Orders relating to that MDU that the LFC is able to complete the order(s) by treating them as SDU Order(s) and installed as individual Connections.

27.20 Where the LFC has completed an MDU First Order pursuant to clause 27.19 above, then any further orders for Residential or Business Connections in that MDU will follow the order and consent process as an SDU Order.



PART 13 – OTHER

28 Requirements for End User Site Visits by the LFC

28.1 Fault and provisioning appointments relating to site visits by the LFC to the End User Premises or NBAP (as applicable) will be arranged by the Service Provider under OSS/BSS. The LFC will not be required to consult the Service Provider or any End User when work at a site does not require entry to the End User Premises or contact with an End User, but must notify Service Provider if an outage will result from work. Where entry to the End User Premises or contact with an End User is required then the Service Provider will advise the End User that the relevant LFC representative will make arrangements for the site visit with the End User

28.2 For a provisioning related site visit the LFC or its representative may contact End Users to facilitate the LFC’s or its representative’s attendance at the End User Premises for appointments arranged through the Service Provider. The LFC or its representative will contact the End User on the supplied number 24hrs before the appointment to confirm both their availability and, if applicable, that the modem has arrived. Additionally the LFC technician will contact the End User on the supplied number before 9am on the morning of the appointment to confirm arrival time.

28.3 For a fault related site visit the LFC or its representative will contact End Users if required to facilitate the LFC’s or its representative’s attendance at the End User Premises for appointments arranged through the Service Provider. The LFC technician will contact the End User on the supplied number as they leave previous task to confirm arrival time.

28.4 For fault and provisioning appointments relating to site visits by the LFC to an NBAP the LFC or its representative will liaise with the Service Provider or the agreed site contact as appropriate.

28.5 The LFC representatives will carry LFC identification and wear appropriate clothing.

28.6 The LFC representative will use all reasonable endeavours to start all visits to an End User's site at the scheduled time.

28.7 When interacting with any End User, the LFC representatives will always act in a professional and courteous manner, and they will not use that interaction for sales and marketing purposes.

28.8 At the completion of all site visits, the LFC representative will record the relevant details in appropriate systems.

29 Premises Wiring, ONT and Approved CPE Installation

29.1 In association with an installation of the Bitstream Service the LFC may, on request, carry out additional work. For example, for an additional charge the LFC may agree to carry out premises wiring and install accredited Service Provider CPE (e.g. routers, gateways or battery back-up). The Service Provider must provide space near a permanent power outlet within a premise for the NID or ONT if one is required. The location of the NID/ONT must be a suitable environment for electronic equipment with a dry, clean indoor area with adequate ventilation.



29.2 When monitored alarms and/or other line grabbing devices (e.g. medic alarms or some broadcast digital services) are installed at an End User Premises or Service Provider Premises or NBAP (as applicable) and the Service Provider takes the Bitstream Services, the Service Provider may choose to advise its End User of the need to ensure that the necessary arrangements are made to ensure the services continue to operate, or alternatively the End User should be advised alternative arrangements are required to retain existing functionality.

29.3 If a fault is found to be caused by non-compliant wiring or equipment which is not part of the Bitstream Service or otherwise within the LFC’s responsibility, then the Service Provider will be liable for the “No fault found” Ancillary Charge as set out in the Price List. Service Providers may choose to advise its End User of the need to ensure that the installation of premises wiring at the End User Premises or Service Provider Premises or NBAP (as applicable) is correct and in accordance with the TCF premises wiring code.

30 Premises Lead-in Fibre Installation

30.1 The limits of the Standard Installation are described in this Manual. Additional work required to provide a Connection may be carried out at same time for an additional charge and that work will not be subject to the Service Levels.

30.2 The installation of conduits and lead-in pipes at each End User Premises or Service Provider’s Premises or NBAP (as applicable) will be in accordance with the LFC work practises and the TCF Premises wiring code. Any existing conduits or Lead-in pipes that are reused must also conform to the same standards.

31 Marketing Support and Roll out Plans

31.1 Raising general awareness about the LFC’s enhanced network and the benefits of fibre to End-Users will be an essential step carried out by the LFC so that End Users are motivated to change to fibre access based services and the LFC achieves the uptake rates they are targeting.

31.2 Assisting in the increasing awareness of the LFC network will be deployment information in the form of maps and address lists provided by the LFC to the Service Providers to enable Service Providers to plan their marketing.

31.3 To augment the broader awareness and marketing initiatives, the LFC will have a sales channel, which will:

(i) own the Service Provider relationship; (ii) develop an intimate understanding of their Service Provider’s requirements; (iii) champion Service Provider requirements within the LFC to ensure Service

Provider issues are understood and services are fit-for-purpose; (iv) ensure Service Provider understand the LFC offerings and can drive fibre

uptake on a retail basis; and (v) identify gaps/opportunities in the NZ market and short to medium term fibre

growth areas. This team will be supported by the service delivery teams who manage the more operational aspects of the Service Provider relationship.



32 Lawful Intercept

Introduction

32.1 Under the Telecommunications (Interception Capability) Act 2004 (TICA)2 a network operator must ensure that every public telecommunications network that the operator owns, controls, or operates, and every telecommunications service that the operator provides in New Zealand, has an interception capability. What is required in terms of interception capability is also set out in the TICA, along with the nature of the obligation to assist the Police, SIS or GCSB (Surveillance Agencies) when a warrant is served to intercept in a particular matter or there is otherwise lawful authority to do so.

32.2 Retail Service Providers should contact the Surveillance Agencies in order to discuss their obligations to provide interception capability under the TICA. The LFC can put you in contact with the appropriate contact person for the Surveillance Agencies.

Additional Interception Capability Assistance

32.3 The LFC may be able to assist the RSPs in meeting their specific obligations under the TICA on a commercial consulting basis (i.e. for a fee).

2 The relevant defined terms are set out in the TICA



PART 14 – LAYER 2 TRAFFIC PERFORMANCE

33 Layer 2 Performance Measurement 33.1 This Part 13 describes the LFC Performance Measurement and Reporting Regime for

Layer 2 traffic carried within the LFC Network.

33.2 The Layer 2 Traffic Service Levels apply to all traffic the LFC accepts into the LFC Network.

33.3 The LFC may either police traffic to the service profile on ingress, allowing for a reasonable CBS/EBS as per the Bitstream Service Description, or carry all offered traffic according to the Layer 2 Traffic Service Levels

33.4 The LFC may police any out-of-profile traffic (being the traffic that exceeds either the committed or excess information rate (CIR and EIR), or the burst size (EBS and CBS) specified in the WSA that the Service Provider offers to the LFC Network, and this may impact on End User experience. The Service Provider should shape their traffic prior to offering it to an LFC.

33.5 The Layer 2 Traffic Service Levels apply continuously and are in force during Planned Outages.

Reporting

33.6 The LFC will provide monthly reports to the Service Provider including the following information:

(i) Port Utilisation measurements for all Network Ports, indicating any Port which experiences a Port Utilisation Threshold Breach during the reporting period and the Port Utilisation Measurement Intervals at which the Port Utilisation Threshold Breach occurred. Report to include Ports not breached if requested by the Service Provider; and

(ii) the current Port Utilisation Threshold and any new Port Utilisation Threshold, if the Port Utilisation Threshold needs to be adjusted, and the implementation date; and

(iii) PON Port Utilisation measurements for review purposes.

Service Level Breach

(iv) any Bitstream Services where the LFC has failed to meet the Layer 2 Traffic Service Levels;

Reference and OAM Probes

(v) Results for any Reference Probes, indicating any Reference Probe which reports a measure that exceeds the allowable maximum FD, FDV, or FLR, during the reporting period and the Reference Probe Measurement Intervals at which the breach or breaches occurred, the Ports that the POI Probe monitors, and the duration of the Probe Performance Threshold Breach for each affected Port;



(vi) any Probe Performance Threshold Breach during the reporting period, the Probe Measurement Intervals at which the breach or breaches occurred, the Ports that the POI Probe monitors, and the duration of the Probe Performance Threshold Breach for each affected Port;

(vii) any OAM Probe breaches, the Probe Measurement Intervals at which the breach occurred, and any End Users that may have been affected by the Probe Performance Threshold Breach; and

(viii) any failure of a Probe, including the probe identity, date of failure, duration of failure, and restore time.

33.7 The LFC will also provide if requested an SLA report with additional information on an ad hoc basis. Requests for ad hoc reports must be lodged within 90 days of the relevant traffic and will be delivered through the Service Delivery Managers.

33.8 The LFC will comply with the Service Provider’s requests for ad hoc reports in a timely manner. In the event that demand for these reports exceeds the LFC’s capacity to deliver, then the LFC will prioritise the requests based on a first come first served basis and after the reports described in 33.7.

33.9 Higher priority will be given to the development of additional reports that are requested by multiple service providers and require the minimum of system changes.

33.10 The ad hoc SLA reports can include the following information:

Port Utilisation

(i) Port interface drops for all relevant interfaces if requested by the Service Provider;

Reference and OAM Probes

(ii) the results from any Reference Probes (FD, FDV and FL) on request from the Service Provider;

Data retention

33.11 Data relating to Service Levels, gathered by a probe (e.g. the OAM Probe or the OLT Probe) must be stored electronically and retained by the LFC for a minimum of 90 days.

33.12 Monthly Service Level reports must be kept by the LFC for a minimum of 7 years.

Port Utilisation

33.13 The LFC will measure the Port Utilisation of all Ports within the LFC Network between the UNI and the E-NNI, in both directions. The UNI, E-NNI and PON Ports themselves do not need to be measured for SLA purposes. Port Utilisation is a proxy for Layer 2 Traffic Service Level compliance. It does not directly measure Layer 2 Traffic Service Levels.

33.14 If the Port Utilisation measure for all Ports is less than the Port Utilisation Threshold, then the Network is compliant and Layer 2 Traffic Service Levels are met.

33.15 If Port Utilisation for any Port exceeds the Port Utilisation Threshold, then a Port Utilisation Threshold Breach has occurred and all Bitstream Services that have traffic associated with that Port are marked as unavailable for the duration of the time (i.e. the sum of the number of five minute intervals) that the Port Utilisation Threshold is exceeded.



33.16 The Port Utilisation Threshold will initially be set at 95%.

33.17 If the Port Utilisation Threshold has been reduced, and there have been no Reference Probe Breaches for three consecutive months following the introduction of the new Port Utilisation Threshold, then the LFC may increase the Port Utilisation Threshold by 1% for every three consecutive months during which no Reference Probe Breach occurs until the Port Utilisation Threshold reaches 95%.

Reference Probes

33.18 Reference Probes are in place to confirm that the LFC Network is capable of meeting the Layer 2 Traffic Service Levels at the Port Utilisation Threshold, and to identify any LFC Network failures that do not contribute to a Port Utilisation Threshold Breach, but would otherwise be breaches of the Layer 2 Traffic Service Levels.

33.19 The LFC will establish a minimum of one OLT Probe per OLT. The OLT Probe is a Reference Probe and will be located in the Test ONT, or will be a separate device connected to the Test ONT. This Test ONT must connect to the OLT via a Production Splitter. The OLT Probe acts as a reflector as defined in ITU standards G.8013 and Y.1731 (08/2015) to reflect Synthetic Test Traffic back to the POI Probe with time stamps.

33.20 The LFC will establish a minimum of one POI Probe per POI. The POI Probe is a Reference Probe and will be located in each EAS, or will be a separate device connected to each EAS. The POI Probe will inject Synthetic Test Traffic into an OVC and measure the FD, FDV, and FL of this Synthetic Test Traffic by means of the traffic reflected by the OLT Probe.

33.21 The OVC that carries the Synthetic Test Traffic must be established between the POI Probe and each OLT Probe. This OVC and the Synthetic Test Traffic must not be prioritised or otherwise treated differently from any other drop ineligible traffic within the LFC Network. The Reference Probe and test OVC will be configured with a standard Bitstream Service profile of 100Mbps downstream, 50Mbps upstream, and 2.5Mbps CIR in each direction.

33.22 The performance monitoring functions required for Reference Probes are defined in the ITU standards G.8013 and Y.1731 (08/2015)):

(i) Single-Ended Synthetic Loss

a) One Way SLR (ETH-SLM)

(ii) Single-Ended Delay

a) One Way FD/FDV (ETH-DM); or

b) Two Way FD/FDV (ETH-DM)

33.23 If a Reference Probe Breach has occurred due to lack of LFC Network capacity and a Port Utilisation Threshold Breach has not occurred, unless there is a clear Network failure:

(i) a Service Level Breach has not occurred;

(ii) the LFC Network is deemed to be incapable of supporting the Layer 2 traffic performance Service Levels at the Port Utilisation Threshold in place at that time;



(iii) the Port Utilisation Threshold must be decreased by 5% (e.g. from 95% to 90%) across the LFC Network; and

(iv) within three months of the Reference Probe Breach, the Port Utilisation of all Ports in the LFC Network must be below the new Port Utilisation Threshold which will be used determining if a Service Level breach has occurred. During this three month period, any Reference Probe Breaches may be ignored; however, any Port Utilisation Threshold Breach will be a Service Level breach.

33.24 If the Reference Probe Breach was not caused by lack of LFC Network capacity and there is a clear LFC Network failure then the LFC does not need to reduce the Port Utilisation Threshold. An LFC Network failure would include for example, the failure of a LAG group or Layer 2 Services network element (including failure due to LFC Network or software upgrades), but would not include for example, a lack of provisioned capacity (including the failure of a single link in a LAG group).

33.25 If the Probe Performance Threshold is exceeded, then there is a Probe Performance Threshold Breach. The Probe Performance Threshold is set at such a level that any breach is likely to be due to an LFC Network failure that will not show up as a Port Utilisation Threshold Breach.

33.26 If there is a Port Utilisation Threshold Breach, and a Reference Probe Breach occurs as a result, then the Reference Probe Breach may be ignored.

OAM Probes

33.27 The LFC will provide an OAM Probe in a point-to-point Bitstream Service ONU within 5 Business Days of receiving a request from the Service Provider. OAM Probes:

(i) will be used to determine compliance with the Layer 2 Traffic Service Levels;

(ii) will be used for OAM performance monitoring functions (FLR, FD, FDV, throughput);

(iii) may be used for OAM fault management functions (Ethernet Continuity Check, Ethernet Test, etc.). The LFC and the Service Provider are to agree on the type of test functions to be allowed, and update this Operations Manual accordingly;

(iv) may be software or hardware based and may be external to the ONT. All hardware or external OAM Probes will terminate on a UNI port that has no other Services provisioned on it;

(v) will be a G.8013/Y.1731 (08/2015) End Point; and

(vi) will be configured with a single dedicated test OVC terminating on a POI Probe. The POI Probe will inject Synthetic Test Traffic into the test OVC. The OVC will carry CIR (high priority) traffic and be will be configured with a point to point Bitstream Service, as requested by the Service Provider.

OAM probes are not available on Glass Only point-to-point Bitstream services.

33.28 The LFC will provide an OAM Probe for GPON Bitstream Services within 5 Business Days of receiving a request from the Service Provider, if the Service Provider provides reasonable evidence that the GPON Bitstream Service may not be complying with the Layer 2 Traffic Service Levels. Reasonable evidence could include repeat End User complaints, End User-initiated test results, or results of LFC tests to their Customer Premises Equipment. These OAM Probes:



(i) will be used to determine compliance with the Layer 2 Traffic Service Levels;

(ii) may be software or hardware based and may be external to the ONT. All hardware or external OAM Probes will terminate on a UNI port that has no other Services provisioned on it;

(iii) will be a G.8013/Y.1731 (08/2015) End Point, is an operator MEP, deployed on each OAM Probe, and the MEP is used as a G.8013/Y.1731 (08/2015) reflector;

(iv) will be configured with two dedicated test OVCs terminating on a POI Probe. One OVC will carry EIR (low priority) traffic, and one OVC will carry CIR (high priority) traffic. Synthetic Test Traffic will be injected into the test OVCs by the POI Probe. The test OVCs will be configured using a Bitstream Service profile of 100Mbps downstream, 50Mbps upstream, and 2.5Mbps CIR in each direction; and

(v) may be deactivated and/or removed by the LFC once it has been established that the Bitstream Service complies with the Layer 2 Traffic Service Levels.

33.29 Performance Monitoring Functions required for OAM Probes are:

(i) Single-Ended Synthetic Loss

a) one way SLR (ETH-SLM)

(ii) Single-Ended Delay

a) one way FD/FDV (ETH-DM or;

b) two way FD/FDV (ETH-DM)

33.30 Test OVCs and Synthetic Test Traffic must not be prioritised or otherwise treated differently from any other traffic within the LFC Network.

33.31 The results from the OAM Probe will take precedence over the Port Utilisation measurements.

Probe failures

33.32 Hardware or software failure of any Probe (including OAM Probe, OLT Probe, or POI Probe) does not contribute to a Layer 2 Traffic Service Level breach, as long as the LFC repairs the Probe within five Business Days (or, in the case of OAM Probes and if requested by the Service Provider, at a time agreed with the Service Provider). If the LFC does not repair the Probe within five business days (or, in the case of an OAM Probe, the time agreed with the Service Provider), then the Bitstream Services the Probe is measuring are marked as unavailable for the period that the Probe is not working.

Service Provider audit rights

33.33 The Service Provider may initiate a review of the regime set out in this Part 13 if the Service Provider reasonably believes that the results are not reflective of the LFC Network performance. Reasons for requesting an audit may include:

(i) The Service Provider receives an abnormally high amount of End User complaints regarding performance even that are not reflected in the reports provided by the LFC; and

(ii) The Service Provider has reasonably determined that performance issues are within the LFC Network; or

(iii) The Service Provider has performed ONT/ONU OAM testing between the UNI



and the POI with poor performance results.

33.34 Each party will bear their own costs of conducting the audit. If the audit/review turns out a ‘no fault found’ then the LFC may pass on the direct actual costs for the audit, with such costs not to include any overhead costs.

33.35 If the audit/review finds a flaw in the regime then the LFC will, within three months:

(i) review the Performance Monitoring and Reporting Regime and make any changes necessary to accurately report on the Layer 2 Traffic Service Levels; and

(ii) remedy the LFC Network so as to be compliant with the Layer 2 Traffic Service Levels.

33.36 The review/audit is to be undertaken by a suitably qualified independent party such as Accenture, KPMG or PWC.

33.37 The Service Provider cannot request more than 1 audit per quarter.

33.38 A review of this regime should be conducted by the LFC in conjunction with the service providers at least 6 monthly to ensure its effectiveness and to take into account improved/amended Industry Standards.

Change Management

33.39 Changes to the regime in this Part 13 will require CFH’s approval, and may only be made after agreement from at least 60% of the service providers purchasing Bitstream Services from the LFC, or if a service provider initiated audit finds flaws in the regime. The LFC will be required to consult with service providers in good faith prior to any changes coming into effect.



APPENDIX A – GLOSSARY

Term Definition

802.1ad means an Ethernet standard that supports Ethernet frames with two VLAN tags. These VLAN identifiers are referred to as:

(a) Service VLAN ID or SVID. Outer tag.

(b) Customer VLAN ID or CVID. Inner tag.

802.1p means an Ethernet standard that uses the 3-bit PCP field in 802.1q VLAN tags to advise the network as to what class of service should be applied to the transport of the frame.

802.1q means an Ethernet standard that allows the support of multiple independent logical networks through the use of an 802.1q header. This allows up to 4094 virtual networks to be identified through the VLAN id field. The 802.1q header also supports a 3-bit PCP field which is used to indicate the class of service the frame belongs to.

802.3/Ethernet II Ethernet standards that define the format of standard untagged Ethernet frames.

Access Rate means the Access Rate is a logical maximum upstream and downstream speed that a Bitstream 3 or Bitstream 3a Service Template can achieve, i.e. ∑CIR + ∑EIR ≤ Access Rate

Aged Tenancy Order Means either an MDU connection where the LFC has installed a Residential or Business Connection to a tenancy in an MDU and has only obtained consent for connection of that tenancy and provision of Services to that tenancy.

Availability Period means the shorter of: (a) the period of the previous 12 months; and

(b) the period of months since the LFC last failed to meet the relevant Service Level.

Automated Pre-qualification

means the automated delivery of information on the availability of services at a given address via the OSS/BSS.

ATA Voice Service means the service described in the ATA Voice Service Description.

B2B means the OSS/BSS Business to Business Web Services Interface that allows Service Providers to integrate their front end systems with the LFC’s ordering and service management systems.

Baseband means the service described in the Baseband Service Description.

BAU means business as usual – the ongoing, every day operation of business, processes and systems.

Bitstream Services means the services described in the Service Descriptions for Bitstream 2, Bitstream 3, Bitstream 3a, Bitstream 4, ATA Voice, Multicast and UFB Handover Connection.

Best Industry Practice

means the exercise of the skill, diligence, prudence, foresight and judgement, as determined by reference to good national and international practice generally applied in fibre access projects OECD countries, which would be expected from a highly skilled and experienced person under the same or similar circumstances to those applicable under the UFB Services.

Blue Zone means the area defined by Chorus as having a fixed installation fee, the boundaries of which are available on Chorus website www.Chorus.co.nz/ournetwork.



Term Definition

Bulk Service Request means a transfer or new connection of a large volume of service instances as more particularly described in the relevant Operations Manual.

Build Cost means the cost for the LFC to build the co-location Footprint requested.

Build Time means the time for the LFC to build the co-location Footprint requested measured from the time the Quote is accepted.

Burst Size means the maximum number of Bytes transmitted in a period defined by the bandwidth profile

Business means any undertaking that is carried on, whether for gain or reward or otherwise.

Business Connection means a Connection requested by a Service Provider in relation to an End User that is a Business (but excluding an NBAP Connection).

Candidate Area means the geographical area indicated as such on the candidate area map available at www.chorus.co.nz.

Central Office means the building which terminates local access fibres and may house both LFC and Service Provider equipment required for providing services over the access fibre network.

Central Office and POI Co-location Service

means a service that provides co-location facilities for a Service Provider’s equipment, and access to a Handover Point, at the LFC’s Central Office solely for the purposes of providing access to, and interconnection with, the LFC Network as described in the Central Office and POI Co-location Service description.

Central office ID means a unique alphanumeric identifier assigned by the LFC to a Central Office.

Central Office Entry Point

means the congregation point for all ducts and cables that enter a Central Office that is nominated by the LFC as the Central Office entry point, usually a manhole.

Chorus UFB Zone means the UFB fibre network comprising fibre to Premises Passed, the boundaries of which are available on the Chorus website www.chorus.co.nz/ournetwork.

Co-location Build means the build work required by the LFC to provide the co-location footprint requested by the Service Provider.

CIR means Committed Information Rate. This is the amount of guaranteed throughput – frames submitted within this throughput will be considered discard ineligible by the network.

Committed Burst Size (CBS)

means the burst size defined for a CIR bandwidth profile for a Layer 2 Service

Communal Infrastructure

means any fibre network infrastructure in the Coverage Area which is deployed independently of any End-User Specific Infrastructure and which is not located on Premises, including any of the following within the Coverage Area: (a) Interconnection Points;

(b) Central Offices;

(c) cabinets and/or fibre cross connection points;

(d) intra-Coverage Area backhaul fibre connecting the interconnection points, Central Offices and cabinets;

(e) distribution fibre running along each street, past Premises;

(f) feeder fibre running from Central Offices to cabinets or fibre cross connection points;

(g) associated ducts and other fixed civil infrastructure required to deploy fibre; and

(h) passive optical equipment installed in the LFC cabinet and/or a Central Office.

http://www.chorus.co.nz/ournetwork



Term Definition

Connection means:

(a) the cable joining the Fibre Access Point to the External Termination Point of a Premises, with such cable to be either from the pit on the adjoining boundary of two properties where the Fibre Access Point is located in underground deployment, or from the pole nearby to a number of premises in aerial deployment; and

(b) all other infrastructure (excluding Communal Infrastructure) necessary to enable the provision of the Wholesale Services (including layer 1 and layer 2 services) to the relevant End User,

and “Connected” will be construed accordingly.

Coverage Area means, as the context requires, either:

(a) the area comprising all Candidate Areas or

(b) the geographic area serviced by a given Handover Point; or

(c) the geographical area served by a Data Switch. There are multiple tiers:

• First Data Switch – typically an Intermediate POI or POI.

• POI - consists of the aggregate of all First Data Switches served by the POI. In many cases this will only be the POI itself.

CPE means Customer Premises Equipment. This is equipment used by the End User or provided by the Service Provider at the End User site to use or interface with the Bitstream service.

Customer Authorisation

means a valid authorisation for a Transfer Service Requests by a customer or a customer’s duly appointed agent that meets the requirements of the Customer Transfer Code.

Customer Transfer Code

means the Code for the Transfer of Telecommunications Services approved by the Commission on 12 October 2006 and/or endorsed by the TCF on 3 November 2006, as applicable, and any equivalent replacement Code or Codes.

CVID means Customer VLAN ID. This is the VLAN identifier contained in the inner 802.1ad tag delivered on the E-NNI.

DHCP means Dynamic Host Configuration Protocol. A Layer 3 protocol used to auto-configure basic IP settings. Optional for Service Providers. Bitstream 2 has a configurable option to insert Circuit ID information into DHCP configuration requests as defined in TR-101/156.

Direct Fibre Access means the service described in the Direct Fibre Access Service Description.

Deemed Acceptance Time

means the time which is four Business Hours after the Receipt Time of a valid Service Request. To avoid doubt, a Service Request may still be rejected notwithstanding a deemed acceptance.

Downtime means the length of time that an End User is without service, measured from the time that a fault is detected, either by an End User fault report or by an LFC Network surveillance system, to the time the fault is resolved and the service is restored. Downtime excludes service interruptions as a result of End User, Reseller or Service Provider actions, and ONT outages due to power failure.

EAS Ethernet Aggregation Switch.



Term Definition

E-APL Ethernet Access Private Line. An OVC that associates a UNI on an ONT with an E-NNI at a POI. Service Multiplexing is set to OFF. E-APLs are VLAN transparent, i.e. untagged and single-tagged frames at the UNI and Customer VLAN tags at the E-NNI are transported transparently. The OVC is identified at the E-NNI through the Service VLAN ID of the double-tagged (SVID/CVID) VLAN.

E-AVPL Ethernet Access Virtual Private Line. Ethernet Access Virtual Private Line. An OVC that associates a UNI on an ONT with an E-NNI at a POI. Service Multiplexing is set to ON. The OVC is presented as a single VLAN at the UNI and a double-tagged (SVID/CVID) VLAN at the E-NNI.

eBill means invoices provided in an electronic format.

EIR Excess Information Rate. This is the amount of un-guaranteed throughput – frames submitted within this throughput will be considered discard eligible by the network.

EMA Ethernet Multicast Access. A service that supports the transmission of multicast traffic from a Service Provider to multiple UNIs simultaneously.

End User Tenancy means the occupancy of an End User (for example, an apartment, townhouse, office or shop) in an MDU to which the Service Provider requests the LFC to provide a Service. To avoid doubt, this does not include common areas within an MDU.

End User-Specific Infrastructure

means the infrastructure in the Coverage Area separate from, and connecting with, the Communal Infrastructure and the Layer 1 Communal Infrastructure to provide service to End User connections, including the following:

(a) fibre from a Premises to the Communal Infrastructure already in place outside the boundary of a Premises;

(b) any electronic and/or optical equipment the LFC may be required to install on Premises;

(c) associated ducts and other fixed civil infrastructure required to deploy the End User-specific fibre assets;

(d) any capitalised investment directly associated with each marginal End User (for example, the value of any software licences that might be supplied to the LFC on a “per End User” basis); and

(e) any active electronic equipment installed in a Premises required to provide the layer 2 Wholesale Services.

E-NNI External Network-to-Network Interface. This is a MEF standard interface that allows connectivity between two Ethernet networks. It provides the Ethernet demarcation between the LFC and the Service Provider.

ETH-DM means Ethernet Delay Measurement function (as defined in G.8013/Y.1731 (08/2015))

ETH-SLM means Ethernet Synthetic Loss Measurement (as defined in G.8013/Y.1731 (08/2015))

ETP means a suitable fibre termination facility located as an attachment to an external structure located at the End-User Premises or Service Provider Premises or at the NBAP non building access point. It is not mandatory for the fibre to be broken and terminated at that point, although it will serve as an access point for breaking and testing should the need arise.

Excess Burst Size (EBS)

means the burst size defined for an EIR bandwidth profile for a Layer 2 Service

FFP Fibre Flexibility Point. A roadside cabinet where the feeder fibre from the Central Office is connected or patched to the distribution fibre to the End User Premises or Service Provider Premises or NBAP (as applicable). In the case of GPON services it is also likely to house the passive optic splitters.



Term Definition

Fibre Access Point or FAP

A point on the End User Premises or Service Provider Premises or NBAP (as applicable) boundary where the Fibre Lead-in connects to the distribution network, either from the pit on the adjoining boundary of two properties where the Fibre Access Point is located in underground deployment, or from the pole nearby to a number of Premises in aerial deployment to provisioning.

Fibre Lead-in The fibre from the Fibre Access Point to a jack inside the End User Premises or Service Provider Premises or NBAP (as applicable) or OFDF.

Fibre Customer Transfer Code

means the TCF Non-Regulated Customer Transfer Code for Fibre Services as amended or replaced from time to time.

First Data Switch The term applied to the first EAS after the access node. This is the first Layer 2 Handover Point at which a Service Provider can connect to the Chorus network, although Tail Extension can be used to extend the service beyond this point.

First MDU Order means the first properly completed order from a Service Provider received by the LFC for a Residential or Business Connection in relation to each MDU.

First MDU Connection Date

has the meaning given to that term in clause 1.2 (c) (iii) of Appendix 1 to the Service Level Terms;

Footprint means a space at any Chorus Central Office that is allocated to the Service Provider for the installation of its equipment but excludes any space occupied by the Service Provider’s Tie Cables.

Forecast means any or all (as the context requires) of the Forecasts required to be provided by the Service Provider in any Operations Manual.

Forecast Service Requests

means a forecast Service Requests, as reported in a Forecasting Report.

Forecasting Template

means the template provided by the LFC either as:

(a) excel spreadsheet with a separate worksheet for each Forecast type, an example of which is attached as Appendix C; or

(b) a web based template for each Forecast type.

Frame Delay (FD) This is a measurement of how long an Ethernet Frame takes to traverse part of the network, typically UNI to the POI. It measures the one-way delay and uses a 1500 byte Ethernet frame as a baseline.

Frame Delay Variation (FDV)

This is the amount at which the Frame Delay is allowed to vary across multiple Frame Delay measurements.

Frame Loss (FL) This is the amount of in-profile frames that are dropped between ingress and the point of measurement, typically the POI. Measured in %.

Glass Only means a point to point service that is provided without a NID at the premises

GPON means Gigabit Passive Optical Networking and is defined by the ITU in the G.984 series of recommendations

Green Zone means any areas outside Chorus UFB Zone and RBI Zone where the LFC provides fibre services on GPON architecture.

Handover Point This is the exchange where the bitstream service is handed over from Chorus to the Service Provider. The Service Provider can connect the service to their site, to collocation space in the Handover Point exchange or use a backhaul service to deliver the service to a different location.



Term Definition

High Priority class This is a class, defined in the TCF ELAS Service Description, which is intended for the delivery of high performing applications and content. All frames marked as high priority are considered discard ineligible. - CIR > 0. - EIR = 0 High Priority Network Performance Service Levels are set out in the Service Level Terms for the Bitstream Services

Integrated Test Facility

The Integrated Test Facility (ITF) is a collection of labs and services that support Service Providers in development of new and existing UFB services

ITU Y.1731 An ITU Ethernet standard that supports protocols and practices for OAM across Ethernet platforms.

LAG Link Aggregation Group that combines a number of Ports to make either a single high capacity data path or separate data paths to implement load sharing and/or redundancy among Ports within the group

Layer 2 means layer 2 of the OSI Model, being active fibre optic network infrastructure.

Layer 2 Communal Infrastructure

means the following Communal Infrastructure, each to the extent required to provide the Layer 2 Wholesale Services: (a) electronic and/or optical equipment installed in the LFC’s cabinet, Central Office or

POI; and

(b) active electronic equipment installed in a Central Office or cabinet in the Coverage Area.

Layer 2 Traffic Service Levels

means the Service Levels described in clause 5 of Appendix 1 of the Bitstream Service Level Terms

Law means:

(a) any statute, regulation, by law, ordinance or subordinate legislation in force from time to time to which a party is subject;

(b) the common law and the law of equity as applicable to the parties from time to time;

(c) any binding court order, judgment or decree;

(d) any applicable industry code, policy or standard enforceable by law; or

(e) any applicable direction, policy, permission, consent, licence rule or order that is binding on a party and that is made or given by any governmental, legal or regulatory body having jurisdiction over a party or any of that party’s assets, resources or business,

in any jurisdiction that is applicable to the WSA, including all applicable district or regional plans, district council bylaws, district council codes of practice and development manuals for roading and New Zealand Transport Agency guidelines and standards.

LC Connector means an LC Angle Polished Connector (APC) conforming to Grade B insertion loss and Grade 1 return loss performance as per IEC 61755-1

LCA connector Little Angled Connector conforming to Grade B insertion loss and Grade 1 return loss performance as per IEC 61755.



Term Definition

Legacy OSS/BSS means the Wireline (OO&T) and Chorus Self Service Portal (SSP - Netcracker) used for ordering UFB services.

Legacy Zone means any legacy fibre network to Premises that have not been Passed by Communal Infrastructure and excludes the Blue Zone, Green Zone and RBI Zone.

LFC Build means the build work carried out by the LFC to provide the co-location Footprint requested by the Service Provider.

Low Priority class This is a class, defined in the TCF ELAS Service Description, which is intended for the delivery of internet grade applications and content. All frames marked as low priority are considered discard eligible. - CIR = 0. - EIR > 0 Low Priority Network Performance Service Levels are set out in the Service Level Terms [for the Bitstream Services].

Measurement Interval

means a Port Utilisation Measurement Interval or Probe Measurement Interval.

Measurement Interval Number

means the specific Measurement Interval in a month. A 30 day month will consist of 8,640 Probe Measurement Intervals and a 31 day month will consist of 8,928 Probe Measurement Intervals, a 30 day month will consist of 2,880 Port Measurement Intervals and a 31 day month will consist of 2,976 Port Measurement Intervals. Measurement Interval Number 0 is the first Measurement Interval of a month.

MEF Metro-Ethernet Forum. An international industry consortium that creates standards for carrier Ethernet networks and services.

MEG Maintenance Entity Group. This is a point in the network that supports OAM management functions.

MEP MEG End Point. This is a maintenance functional entity located at each end of an end-to-end path and provides a point that can be used to initiate OAM tests or reflect OAM requests.

MIP MEG Intermediate Point. This is a maintenance functional entity located at intermediate points along the end to end path. It reacts and responds to OAM frames.

MOFDF means the main optical fibre distribution frame being a facility in the relevant office for terminating access fibres.

Month [x] means the calendar month that is [x] calendar months before a Service Requests Month.

Move Address Service Requests

means a Service Requests where an End User requests the relocation of their Service Provider telecommunications services to another physical address.

MTU Maximum Transmission Unit. The maximum Ethernet frame, including headers, which can be supported by the service.

Multicast means the service described in the Multicast service description.



Term Definition

Multi Dwelling Unit or MDU

means a premises containing within its boundaries more than one residential or commercial occupancy (or both). Examples of MDUs (albeit a non-exhaustive list) are set out below.

Includes semi-detached, apartments, townhouses, gated communities and assisted-living facilities that share a common property boundary. MDU facilities may be under a single roof or they may consist of multiple buildings on a residential campus. MDUs may include only residential units or they may have residential units along with commercial and retail spaces. The BICSI defines 3 types of MDUs:

1. Low-rise MDUs: Each unit has access to the ground level and also has a roof line such as townhouses and semi detached dwellings.

2. Mid-rise MDUs: These include duplexes, two storey apartments and other building styles in which units are stacked upon one another.

3. High-rise MDUs: High-rise MDUs most closely resemble large commercial buildings with few units having direct access to the roof line or ground floor.

MDU Common Infrastructure

means any internal cabling and other build work within the MDU (in addition to the work required to install the first Connection in the MDU to provision the First MDU Order) which the LFC considers is reasonably necessary to enable the LFC to meet the Service Levels for Subsequent MDU Orders;

MDU Connection Pre-requisite Steps

means the process set out in this Manual;

MDU Connection Process

means the process to install the first MDU Connection in the MDU to provision the First MDU Order and, if the LFC elects, to install the MDU Common Infrastructure (if any), as set out in this Operations Manual;

Multi-Dwelling Unit Infrastructure or Multi-Business Unit Infrastructure

means the individual fibre connection from the point that the End User-Specific Infrastructure terminates at the Premises to an individual residence or commercial tenancy in a multi-tenant building or if the LFC has provide backbone and floor cabling within MDU the individual fibre connection from the point that the End User-Specific Infrastructure enters the Premises to an individual residence or commercial tenancy in a multi-tenant building;

NID means Network Interface Device. An active device at the End User Premises or Service Provider Premises or NBAP (as applicable) that terminates the fibre and provides an electrical interface to the End User.

New OSS/BSS means the Chorus Portal used for ordering UFB services

NOC means Network Operations Centre.

Non-Building Access Point or NBAP3

means a location, other than End User Premises, Service Provider Premises or Reseller Premises, which may not have a physical address and where either LFC (End User) Equipment or LFC (Service Provider) Equipment is (or is to be) installed in order to deliver a Service.

Non – Standard Installation

means in relation to a service means any work required to be performed by the LFC to install that service that falls outside the definition of Standard Installation.

OAM Operations, Administration and Maintenance. A set of processes, tools and activities based on ITU Y.1731 that allows testing and monitoring of the Ethernet network.

3 NBAP examples include, but are not limited to: cell tower and base station located in a back yard or field; cellsite and base station on a roadside pole (e.g. in a street lamp); public WiFi hotspot located on a campus or on a roadside pole; surveillance equipment and camera on public land or traffic pole; ticketing systems in carparks or on roadside; ATM machine on outside premises; SCADA management of power systems.



Term Definition

OAM Probe means a device that is built-in, or connects, to an End User ONT or ONU that is used to measure the Layer 2 Traffic Service Levels between the POI Probe and OAM Probe by means of Synthetic Test Traffic.

OFDF Optical Fibre Distribution Frame. An optical fibre distribution frame installed in an MDU or End User Premises or Service Provider Premises or NBAP (as applicable) used to terminate the Fibre Lead-in.

OLT means optical line termination as defined in the ITU-T G.984 series specifications and is the device that is located in the Central Office and is the endpoint of a PON

OLT Probe means a device connected to an OLT by the LFC that measures the Layer 2 Traffic Service Levels between the POI Probe and the OLT Probe and provides the Y.1731 reflector. An OLT Probe must be connected to each OLT via a Test ONT

ONT/ONU means the Optical Network Terminal that terminates the Bitstream Services in the End User Premises, Service Provider Premises, Reseller Premises or NBAP (as applicable).

OSS means the LFC’s operational support systems.

OVC means Operator Virtual Connection.

Passed means when Premises have been passed with Communal Infrastructure (and, where the context requires, includes Layer 2 Communal Infrastructure) and is capable of Connection from the nearest point to the private boundary (if underground) or nearest pole (if aerial) (and Pass is to be interpreted accordingly).

PCP Priority Code Point. A three bit field in the 802.1q header that identifies what class a particular frame is associated with.

POI Point Of Interconnect. This is a logical point in the network where a Bitstream Service terminates. Each LFC POI shall be an LFC Central Office at which Chorus locates an aggregation switch.

POI Probe means an industry standard device (for example ITU standard G.8013/Y.1731 compliant) located by the LFC at a POI that measures the Layer 2 Traffic Service Levels, and generates Synthetic Test Traffic, between the POI Probe and an OLT Probe or a OAM Probe. The POI Probe must measure traffic to/from each EAS within a POI.

PON means Passive Optical Network as defined in ITU standard G.984.5 (May 2014).

POP Point of Presence. This is the point at which a Service Provider provides a service – either directly or via a backhaul service.

Port means a physical port within the Network, excluding UNI, E-NNI and PON ports. All virtual ports and sub-interfaces within the physical Ports must however automatically scale up to the physical Port capacity otherwise they will also form part of a Port.

Port Utilisation means the average bandwidth utilised on a Port, expressed as a percentage of the total bandwidth available on that Port, measured over a five minute interval for each five minute interval of every day.

Port Utilisation Measurement Interval

means a five minute interval used for Port Utilisation measurements.

Port Utilisation Threshold

means the maximum Port Utilisation, as set from time-to-time in accordance with Part 13 of the Operations Manual.

Port Utilisation Threshold Breach

means any Measurement Interval in which the Port Utilisation of any measured Port exceeds the Port Utilisation Threshold.



Term Definition

PPPoE Point-to-Point-Protocol over Ethernet. This is a protocol used for Layer 3 IP attribute assignment. It can be used as an alternative to DHCP. Bitstream 2 has a configurable option to insert Circuit ID information into PPPoE configuration requests as defined in TR-101/156.


The Product Development Process is the process by which Chorus will develop new Service Templates requested by a Service Provider.

Priority Users Priority Users means businesses of any size, schools (including state, state integrated and independent schools) and health service providers (including private sector health providers, hospitals and significant health care provider sites, for example emergency and medical centres, and radiologists).

Premises means a single building or structure located on a defined geographical site (such as may be evidenced by a certificate of title), which has a unique physical address recognised by NZ Post, and is occupied by or could readily be occupied by a potential End User and, for the avoidance of doubt:

a) a Premises does not include a NBAP; b) a Multi-Dwelling Unit only constitutes a single Premises; and c) a Premises includes each such building or structure that is in, or that is from

development activities reasonably anticipated in the near future to be in, a greenfields area or development site that is within or adjacent to the Coverage Area.

Priority Users Priority Users means businesses (of any size, including private sector health providers), schools (including state, state integrated and independent schools) and health service providers (hospitals and significant health care provider sites, for example emergency and medical centres, and radiologists);

Probe Failure means the occurrence of a failure to meet the Layer 2 Traffic Service Levels (within any five minute interval) by any Reference Probe.

Probe Measurement Interval

means a five minute interval which consists of a minimum of 3,000 sample measurements. The LFC may discard the worst 1% of the sample measurements.

Probe Performance Threshold

means a FL of 25% or greater, as measured between the OLT Probe and POI Probe.

Probe Performance Threshold Breach

means any Measurement Interval in which a POI Probe or an OLT Probe reports that FL is greater than the Probe Performance Threshold. Any Probe Performance Threshold Breach is a Service Level Breach.


The Product Development Process is the process by which the LFC will develop new Service Templates requested by a Service Provider.

Production Splitter means a PON splitter carrying Bitstream Services.

QnQ is an industry standard protocol similar to 802,1ad. It supports stacked VLANs, i.e. multiple VLAN tags in an Ethernet frame. Chorus supports this as an alternative E-NNI standard to 802.1ad. The primary practical difference between QnQ and 802.1ad is the Ethertype field.

Quote means an estimate provided by the LFC for services requested by Service Provider that do not have a set charge in the Price List.

RBI Zone means the RBI fibre network in RBI areas, the boundaries of which are available on the Chorus website www.chorus.co.nz/ournetwork.

http://www.chorus.co.nz/ournetwork



Term Definition

Receipt Time means: (a) for Service Requests that are made using the OSS/BSS, the time that the

electronic communication containing the Service Request enters the OOS/BSS; or

(b) for Service Requests that are made by email, the time that a Service Request is received in the LFC designated inbox for receipt of such Service Requests,

provided that where a Service Request is received outside Business Hours, the Receipt Time will be the start of the first Business Hour of the following Business Day.

Reference Probe means an OLT Probe and/or a POI Probe.

Reference Probe Breach

means the occurrence of at least five Probe Failures within an Availability Period on any single Port or combination of Ports in the LFC Network

Relinquishment means the cessation of a service.

Relinquishment Service Requests

means an order for the cessation of a service.

Residential Connection

means a Connection requested by a Service Provider in relation to an End User that is not a Business or NBAP.

Sampling Rate means the rate at which Synthetic Test Traffic is sampled and measured. The Sampling Rate for all Synthetic Test Traffic must be every ≤100 milliseconds (i.e. a minimum of 3,000 samples per five minute interval);

SC/ACP means Standard Connector / Angle Polished Connector to IEC 61754-4 conforming to Grade B insertion loss Grade 1 return loss performance as per IEC 61755-1.

SC Connector means an SC Angle Polished Connector conforming to Grade B insertion loss Grade 1 return loss performance as per IEC 61755-1

Service Area means either:

(a) the area served by the fibre terminated at an LFC Central Office, or

(b) the area within an LFC Central Office set aside for the Central Office and POI Co-location service.

Service Demarcation Point

Has the meaning given in the relevant Service Description as the context requires.

Service Identifier means a unique alphanumeric identifier assigned by the LFC to a service.

Service Level means a “Core Service Level” or “Ancillary Service Level” as those terms are defined in the Service Level Terms.

Service Level Default means a failure by the LFC to meet a Service Level.

Service Order means a Service Request accepted by the LFC in accordance with clause 4.4(b)(i) of the General Terms, and includes the Service Description, Service Level Terms, Operations Manual and Charges applicable to the Services to be provided by the LFC that are the subject of that Service Request;

Service Provider means an entity that purchases the Bitstream Service from the LFC and, combined with its own network and services, provides a telecommunication service to an End User.

Service Provider Build

means the build work carried out by the Service Provider to complete the co-location footprint requested by the Service Provider.



Term Definition

Service Rebate means a “Core Service Rebate” as defined in the Service Level Terms.

Service Request means a written or electronic request for the supply of a new Wholesale Service or Ancillary Service, or a move, add, change or termination of an existing Wholesale Service or Ancillary Service provided by the LFC under this Agreement, issued by the Service Provider to the LFC in accordance with this Manual.

Service Request Month

means the calendar month in which a Forecast Service Request is forecast to become a Service Request.

Service Start Date means the date that the LFC activates or otherwise makes available a Service ordered by the Service Provider.

Service Template means a preset combination of bitstream service components, such as VLANs, UNIs etc. that can be added incrementally to an existing service, or consumed as a package. Service Providers can consume the initial Service Templates as defined in the relevant Bitstream Services service descriptions, or request new Service Templates through the Product Development Process.

SLR means Synthetic Loss Reply.

Special Manual Pre-qualification Investigation

means the delivery of information on the availability of services at a given address following the visit to site by a technician (may include specially requested information).

Single Dwelling Unit or SDU

means premises containing within its boundaries only one residential or commercial occupancy, excluding any part of the land used to locate, or otherwise used to connect to, a NBAP.

SSP means Self Service Portal – an OSS/BSS interface.

Standard Installation means an installation of a service that is described as a Standard Installation in clause 12.

Subsequent MDU Order

has the meaning given to that term in clause 1.2 (d) of Appendix 1 to the Service Level Terms;

SVID Service VLAN ID. This is the VLAN identifier contained in the outer 802.1ad tag delivered on the E-NNI.

Synthetic Test Traffic means test traffic generated by the POI Probe. This traffic must be marked as drop ineligible (as per ITU standards G.8013/Y.1731 08/2015) and injected continuously at a minimum rate of 10 frames per second, and delivered over traffic bearing Ports. Synthetic Test Traffic may be sent over a test-only service tag, and is to be treated by the Network elements in the same way that service frames are treated.

Tagged traffic means Ethernet frames that include one or more 802.1q headers or tags.

Tail Extension means a service that extends the service attributes of the tail from the POI to a remote Handover Point. As this provides a backhaul service, the end-to-end service attributes will be different than a service that terminates at the POI.

Test ONT means the ONT to which the ONT test probe is connected or within which it is housed. The Test ONT must connect to the OLT through a production splitter.



Term Definition

Tie Cables means cable provided on request to a Service Provider who taken a fibre access service and or a co-location footprint. Can be either: (a) An internal Tie Cable from the Central Office MOFDF to the Service Provider

Footprint;

(b) An internal Tie Cable from one Service Provider Footprint to another Service Provider Footprint (the footprints can be same or different Service Providers); or

(c) An external Tie Cable from the Central Office MOFDF to a third party network outside and adjacent to the Central Office entry point.

TR-101/156 A Broadband Forum technical report that standardises how GPON can be supported using an Ethernet Aggregation Network.

Transfer Service Requests

means a Service Request by the Service Provider to transfer services of End Users between Service Providers as the result of customer acquisition as requested by the End User and submitted in accordance with the Fibre Customer Transfer Code.

Trouble ticket means the record of a fault report detailing fault and steps taken to rectify.

Truck roll means the dispatch of a technician to construct or repair the LFC network including end user infrastructure.

UFB Arrangements means the arrangements between Chorus, Crown Fibre Holdings Ltd and the Crown relating the Government’s Ultrafast Broadband Initiative under which Chorus is required to construct, and deliver services over, a fibre optic access network in certain parts of New Zealand.

UFB1 Areas means

(i) the Candidate Areas listed in Appendix E as UFB1 Candidate Areas and identified in more detail on the LFC’s website at http://ccm.wialus.co.nz/; and

(ii) any Greenfields developments adjacent to those UFB1 Candidate Areas.

UFB2 Areas means

(i) the Candidate Areas listed in Appendix E as UFB2 Candidate Areas and identified in more detail on the LFC’s website at http://ccm.wialus.co.nz/.

(ii) any Greenfields developments adjacent to those UFB2 Candidate Areas.

UFB Handover Connection Service

means the service described in the UFB Handover Connection Service Description.

UFB Services means the Bitstream Services, Baseband, Direct Fibre Access Services and the Central Office and POI Co-location Service.

UFB Periods means in UFB 1 Areas, until 31 December 2021 ; and in UFB2 Areas, until 1 January 2026.

UNI User Network Interface. The interface specification facing the End User site.

UNI Port A single Ethernet port on an ONT.

UPS Uninterruptible Power Supply.

Voice-AVPL Voice Access Virtual Private Line. This consists of an ATA port and SIP User Agent on the ONT and an OVC that associates the ATA port with an E-NNI at a POI. The OVC is presented as a single VLAN at the UNI and a double-tagged (SVID/CVID) VLAN at the E-NNI

Voluntary Zones means the total area of New Zealand’s North and South Islands and Waiheke Island excluding Chorus UFB Zone and RBI Zone.

VLAN A virtual LAN or local area network. A logical Ethernet network supported through 802.1q headers.



Term Definition

Week means a seven-day period commencing Monday and ending Sunday.

WiFi A common short range wireless network used for local connection to a WiFi hotspot. It is offered as a feature on the ONT as an alternative to house wiring, although throughput is limited by the WiFi bandwidth and the number of users on the shared network.

WSA means the “Agreement” as defined in the General Terms.

Y.1731 An ITU standard that defines protocols and practices for OAM on Ethernet networks including traffic performance measurements such as Frame Delay, Frame Delay Variation and throughput.



APPENDIX B - ESCALATION PROTOCOL

Rule No.

Escalation Rule

Further Explanation

1 Identify correct escalation path.

Before any issue is escalated, sufficient investigation should be undertaken to ensure that the functional group that will most likely be responsible for resolving the issue has been correctly identified.

2 Attempt to resolve issues at BAU level before escalating them.

Every effort should first be made to resolve an operational issue at the BAU level, i.e. direct communication between the originator and the recipient.

3 First escalation should be via e-mail.

In the first instance an escalation at BAU level should be received via e-mail and clearly labelled as such with the email subject line beginning with 'ESCALATION'. The email should contain the relevant history of the issue, including the escalation history and when applicable the customer name, Service Identifier/circuit numbers and fault/Service Request or Service Order numbers.

4 Level One and Two escalations shall be peer to peer.

If an operational issue cannot be resolved at the BAU level it must first be raised by the team member with their own team leader/manager. If the team leader/manager agrees that the issue warrants being escalated to the other party they shall contact their peer in the other organisation and endeavour to resolve the issue between them - this would normally be the level one escalation point. Under no circumstance should this step in the escalation path be bypassed unless every reasonable attempt to communicate with their peer in the other organisation has failed. Only then should the level one contact in party A attempt to escalate the issue to the level two contact in party B. Subject to the above, level two escalations should also be peer to peer.

5 A mutually agreed plan of action to resolve an issue shall not be interfered with by other individuals.

If a plan of action to address an escalated issue has been agreed to by both parties then no other individual from either organisation should attempt to interfere with that agreement. If another individual has a concern with an already agreed plan of action they should raise it in the first instance with the person in their own organisation that was party to the original agreement.

6 People who do not follow the above rules will be redirected to the correct point of escalation.

If, as part of an escalation, an individual is contacted by a person from the other company and it is discovered that that person has not followed the protocol described above, then that individual can at their discretion respectfully redirect that person to the correct escalation contact person.



APPENDIX C - FORECASTING SPREADSHEET

The forecasting spreadsheet is available online at: www.chorus.co.nz/ufbservices



APPENDIX D - TECHNICAL SPECIFICATION

This section describes the technical specifications needed to connect End User or Service Provider equipment to the LFC’s Bitstream service.

Architecture for Bitstream 2/3/3A/ATA Voice/Baseband/Multicast

Architecture for Bitstream 4

Architecture for Bitstream 4 Glass Only

ATA Interface

Port RJ11 Analogue interface compliant with PTC 220, section 5

Voice G.711a/G.711u codec at 10ms sampling rate. 200 byte packet metric. Maximum delay allowance for jitter of 20ms. Other codecs can be considered and implemented using the Product Development Process.

Service ProviderNetwork POP

End User Site

AccessNode EAS EN

NI

ATA

ATA

UNI

UNI

UNI

UNI

ONUFibre

HandoverConnection

POI

AggregationATA Interface

UNI Interface

ENNI Interface


End User Site

AccessNode EAS EN

NIFibre

HandoverConnection

POI

AggregationUNI Interface ENNI InterfaceUNI NID


End User Site

AccessNode EAS EN

NI

ATA

ATA

UNI

UNI

UNI

UNI

ONUFibre

HandoverConnection

POI

AggregationATA Interface

UNI Interface

ENNI Interface



UNI Interface

Ethernet – Bitstream 2 Ethernet II or 802.3 untagged interface; or 802.1q tagged interface with • VLAN id = As agreed with Service Provider • 802.1p = 0, 1, 2, 3, 5, 6, 7 (Low Priority) • 802.1p = 4 (High Priority)

Ethernet – Bitstream 3/3A • IEEE 802.3 – 2005 • 802.1q supporting 4093 VLANs PCP Transparent (default, Bitstream 3) High Priority Bandwidth – as per plan Low Priority Bandwidth – none PCP Transparent OFF (Bitstream 3A) High Priority Bandwidth – as per plan. Low Priority Bandwidth – as per plan.

Ethernet - Bitstream 4 • IEEE 802.3 – 2005 • 802.1q supporting 4094 VLANs High Priority Bandwidth – as per plan Low Priority Bandwidth – none

UNI – Bitstream 2/3/3A ONT supports: • 4 x UNI • 2 x ATA Voice ports • Optional additional ports:

o RF Overlay port o WiFi

Per UNI: • 100/1000Base-T

UNI – Bitstream 4 • RJ45 o 100 Mbps = 100BaseT o 1 Gbps = 1000Base-T o 10 Gbps = 10GBase-T

• Optical Only o 100 Mbps = 100Base-FX o 1 Gbps = 1000Base-LX

VLAN – Bitstream 2 Point-to-Point (E-AVPL) High Priority Bandwidth – as per plan. Low Priority Bandwidth – as per plan. MTU 2000 Bytes Unicast Frame Delivery = passed within service CIR/EIR Multicast Frame Delivery = passed within service CIR/EIR Broadcast Frame Delivery = passed within service CIR/EIR Layer 2 Control Protocols Processing = Initially none (but may be amended by the LFC from time to time)

VLAN – Bitstream 3/3A Point-to-Point (E-APL) MTU 2000 Bytes



PCP Transparent (default, Bitstream 3) • High Priority Bandwidth – as per plan • Low Priority Bandwidth – none PCP Transparent OFF (Bitstream 3A) • High Priority Bandwidth – as per plan. • Low Priority Bandwidth – as per plan. Unicast Frame Delivery = passed within service CIR/EIR Multicast Frame Delivery = passed within service CIR/EIR Broadcast Frame Delivery = passed within service CIR/EIR Layer 2 Control Protocols Processing = Initially none (but may be amended by the LFC from time to time)

VLAN – Bitstream 4 Point-to-Point (E-APL) MTU 9100 Bytes High Priority Bandwidth – as per plan. Low Priority Bandwidth – None. Unicast Frame Delivery = as per CIR Multicast Frame Delivery = as per CIR Broadcast Frame Delivery = as per CIR Layer 2 Control Protocols Processing = Limited (but may be amended by the LFC from time to time)

E-NNI Interface

UFB Handover Connection (E-NNI) Ethernet: • 802.ad VLAN (SVID, CVID); or • Double tagged Q in Q. E-NNI • 1 GigE

Single fibre working RSP end 1000BASE-BX10-U or BX40-U depending on distance (default)

LFC E-NNI Service Provider E-NNI

RX 1310 nm TX 1310 nm

TX 1490 nm RX 1490 nm

Dual fibre working 1000BASE-LX 1310 nm • 10 GigE 10GBase-LW/LR

Single fibre working RSP end 10GBASE-BX10-U (default). BX40-U not supported

LFC E-NNI Service Provider E-NNI

RX 1270 nm TX 1270 nm

TX 1330 nm RX 1330 nm

Dual fibre working 1310 nm • 10 GigE 10GBase- EW/ER

Dual Fibre 10GBase 1550 nm



Fibre

Fibre External fibre must comply with ITU-T specification G.652D or 657A. Internal building fibre cables must meet appropriate fire regulations i.e. be Flame-Retardant, Non Corrosive, Low Smoke, Zero Halogen (FRNC/LSZH).

Connector Type Fibre terminations must be SC/APC type connectors (complying with the IEC 61754-4 standard) or LC/APC also known as LCA type connectors (complying with the IEC 61754-20 standard) as appropriate.

Optic Path Laser types and path characteristics expected to be designed to a minimum standard which are contained in either IEEE 802.3 Section 5 standard or ITU-T G.984 standards.

Fibre Testing Layer 1 All commissioning Layer 1 network testing (LFC site OFDF to end of Communal Network) is by OTDR at two wavelengths, 1310nm and 1550nm using Bi-Directional method in accordance with Chorus standard described in ND0556. The methodology used will be based on bi-directionally testing all fibres in the Communal Network required to complete the service. Network test results are provided by agreement verifying performance features. Refer to the Direct Fibre Services Operations Manual for details. All Layer 1 network restoration testing will be LFC site OFDF to Premises termination point. Testing for power loss will be at either 1310 or 1550 nm. In the event of a fault restoration testing will be to the standard in Optical Performance table below. The wavelengths of 1625nm and 1650nm are reserved for network maintenance testing purposes, compliant with ITU-T L.41.

Optical Path performance Communal Network performance Total GPON Insertion Loss (ITU-T G984) = ≤ 28.5db Network Return Loss = ≥32db LFC GPON system margin (lifetime ageing factor) = 1.5db Total GPON insertion Loss OLT to ONT design target is = ≤ 27.0db (28.5db – 1.5db) Optical Fibre Attenuation Co-Efficient (L) (ITU-T G.652. & G657.A) = ≤ 0.4db/km Splice Loss (S) = ≤ 0.15db Mated Connector loss (C) = ≤ 0.3db Mated Connector Reflection = ≥55db Total Insertion Loss of network (IL) is calculated from IL = 0.4L + 0.15S + 0.3C (excluding PON splitter) Minimum Splitter performance 1:32 = ≤ 17db 1:16 = ≤ 14db 1:8 = ≤ 11db 1:4 = ≤ 7.3db 1:2 = ≤ 4.0db



APPENDIX E -– CANDIDATE AREAS, CENTRAL OFFICES AND POIs

CENTRAL OFFICE UFB LAYER 2 POI CANDIDATE AREA

AHAURA Greymouth UFB2 - Ahaura

AHIPARA Whangarei / Kensington UFB2 - Ahipara

AHIPARA Whangarei / Kensington UFB2 - Ahipara UFB2 Fringe

AIREDALE STREET Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

AKAROA Christchurch UFB2 - Akaroa

AKAROA Christchurch UFB2 - Akaroa UFB2 Fringe

AKAROA Christchurch UFB2 - Takamatua

ALBANY Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

ALBANY Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Dairy Flat/Goodland

ALEXANDRA Queenstown UFB2 - Alexandra

ALEXANDRA Queenstown UFB2 - Alexandra UFB2 Fringe

ALICETOWN Courtney Place / Johnsonville / Porirua / Wellington UFB1 - Wellington

AMBERLEY Christchurch UFB2 - Amberley

AMBERLEY Christchurch UFB2 - Amberley UFB2 Fringe

AMBERLEY Christchurch UFB2 - Leithfield

AMBERLEY Christchurch UFB2 - Leithfield Beach

ANDERSONS BAY Dunedin / North East Valley / South Dunedin UFB1 - Dunedin

ARROWTOWN Queenstown UFB2 - Arrowtown/Lake Hayes Estate

ARROWTOWN Queenstown UFB2 - Arrowtown/Lake Hayes Estate UFB2 Fringe

ARTHURS PASS Christchurch UFB2 - Arthurs Pass

ASHBURTON Ashburton UFB1 - Ashburton

ASHBURTON Ashburton UFB2 - Fairton/Ashburton Airport area and Ashburton Northpark

ASHBURTON Ashburton UFB2 - UFB1:Ashburton UFB2 Fringe

ASHHURST Fielding / Palmerston North UFB2 - Ashhurst

ASHHURST Fielding / Palmerston North UFB2 - Ashhurst UFB2 Fringe

ATAWHAI Nelson / Stoke UFB1 - Nelson

AVONDALE Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

AVONHEAD Christchurch UFB2 - Christchurch

AWANUI Whangarei / Kensington UFB2 - Awanui

AWANUI Whangarei / Kensington UFB2 - Tokerau Beach/Whatuwhiwhi

BALCLUTHA Invercargill / Waikiwi UFB2 - Balclutha

BALCLUTHA Invercargill / Waikiwi UFB2 - Balclutha UFB2 Fringe




BALCLUTHA Invercargill / Waikiwi UFB2 - Stirling

BARRYTOWN Greymouth UFB2 - Punakaiki

BAY VIEW Napier / Hastings / Marewa UFB2 - Bay View/Bay View North

BAY VIEW Napier / Hastings / Marewa UFB2 - UFB 1 Fringe: Clive Beach/Bay View

BAY VIEW Napier / Hastings / Marewa UFB2 - Whirinaki

BEACHLANDS Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

BECKENHAM Christchurch Non UFB funded build

BELFAST Christchurch Non UFB funded build

BELL BLOCK New Plymouth Non UFB funded build

BELMONT Courtney Place / Johnsonville / Porirua / Wellington UFB1 - Wellington

BENNEYDALE New Plymouth UFB2 - Benneydale

BETHLEHEM Tauranga / Otumoetai UFB2 - Te Puna

BIRKDALE Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

BIRKENHEAD Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

BLENHEIM Blenheim UFB1 - Blenheim

BLENHEIM Blenheim UFB2 - Blenheim

BLENHEIM Blenheim UFB2 - Blenheim Fringe/Old Renwick

BLENHEIM Blenheim UFB2 - Blenheim Riverlands

BLENHEIM Blenheim UFB2 - Blenheim Riverlands UFB2 Fringe

BLENHEIM Blenheim UFB2 - Blenheim Roselands Commercial

BLENHEIM Blenheim UFB2 - Blenheim Roselands Commercial UFB2 Fringe

BLENHEIM Blenheim UFB2 - Blenheim UFB2 Fringe

BLENHEIM Blenheim UFB2 - Fairhall

BLOCKHOUSE BAY Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

BLUFF Invercargill / Waikiwi UFB2 - Bluff

BLUFF Invercargill / Waikiwi UFB2 - Bluff UFB2 Fringe

BOMBAY Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Bombay/Paparata Rd

BRIGHTON Dunedin / North East Valley / South Dunedin UFB1 - Dunedin

BRIGHTWATER Nelson / Stoke UFB2 - Wakefield/Brightwater

BRIGHTWATER Nelson / Stoke UFB2 - Wakefield/Brightwater UFB2 Fringe

BROWNS BAY Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

BRYMER Hamilton / Frankton Non UFB funded build

BULLS Fielding / Palmerston North UFB2 - Bulls

BULLS Fielding / Palmerston North UFB2 - Bulls UFB2 Fringe




BUNNYTHORPE Fielding / Palmerston North UFB2 - Bunnythorpe

BURWOOD Christchurch UFB2 - Bottle Lake UFB2

CAMBRIDGE Hamilton / Frankton UFB2 - Karapiro

CANTERBURY TECH PARK Christchurch Non UFB funded build

CARTERTON Masterton UFB2 - Carterton

CARTERTON Masterton UFB2 - Carterton UFB2 Fringe

CHEVIOT Christchurch UFB2 - Cheviot

CHEVIOT Christchurch UFB2 - Cheviot UFB2 Fringe

CLAUDELANDS Hamilton / Frankton Non UFB funded build

CLEVEDON Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Clevedon

CLINTON Invercargill / Waikiwi UFB2 - Clinton

CLIVE Napier / Hastings / Marewa UFB2 - Clive Beach/Bay View UFB2 Fringe

CLOVERLEA Fielding / Palmerston North UFB1 - Palmerston North

CLYDE Queenstown UFB2 - Clyde

CLYDE Queenstown UFB2 - Clyde UFB2 Fringe

COLLINGWOOD Nelson / Stoke UFB2 - Gibbstown/Collingwood

COLVILLE Tauranga / Otumoetai UFB2 - Whangapoua

COROMANDEL Hamilton / Frankton UFB2 - Coromandel

COROMANDEL Hamilton / Frankton UFB2 - Coromandel UFB2 Fringe

CORSTORPHINE Dunedin / North East Valley / South Dunedin UFB1 - Dunedin

COURTENAY PLACE Courtney Place / Johnsonville / Porirua / Wellington UFB1 - Wellington

CROMWELL Queenstown UFB2 - Bannockburn

CROMWELL Queenstown UFB2 - Cromwell

CROMWELL Queenstown UFB2 - Cromwell UFB2 Fringe

CROMWELL Queenstown UFB2 - Cromwell/Pisa Moorings

CULVERDEN Christchurch UFB2 - Culverden

CULVERDEN Christchurch UFB2 - Culverden UFB2 Fringe

CUST Christchurch UFB2 - Cust

CUST Christchurch UFB2 - West Eyreton

DANNEVIRKE Napier / Hastings / Marewa UFB2 - Dannevirke

DANNEVIRKE Napier / Hastings / Marewa UFB2 - Dannevirke UFB2 Fringe

DARFIELD Christchurch UFB2 - Castle Hill

DARFIELD Christchurch UFB2 - Darfield

DARFIELD Christchurch UFB2 - Darfield UFB2 Fringe

DARGAVILLE Whangarei / Kensington UFB2 - Baylys Beach




DARGAVILLE Whangarei / Kensington UFB2 - Te Kopuru

DEVONPORT Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

DIAMOND HARBOUR Christchurch UFB2 - Diamond Harbour UFB2 Fringe

DIAMOND HARBOUR Christchurch UFB2 - Diamond Harbour

DOBSON Greymouth UFB2 - Dobson

DOBSON Greymouth UFB2 - Taylorville

DUNEDIN Dunedin / North East Valley / South Dunedin UFB1 - Dunedin

DUNSANDEL Christchurch UFB2 - Dunsandel

DUNTROON Oamaru UFB2 - Duntroon

DUVAUCHELLE Christchurch UFB2 - Duvauchelle

EAST TAMAKI Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

EASTBOURNE Courtney Place / Johnsonville / Porirua / Wellington UFB1 - Wellington

EDENDALE Invercargill / Waikiwi UFB2 - Edendale

EDENDALE Masterton UFB2 - Eketahuna

EDGECUMBE Whakatane UFB2 - Edgecumbe

EDGECUMBE Whakatane UFB2 - Edgecumbe UFB2 Fringe

EKETAHUNA Masterton UFB2 - Eketahuna

ELLERSLIE Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

ELTHAM New Plymouth Non UFB funded build

FAIRLIE Timaru UFB2 - Fairlie

FEATHERSTON Masterton UFB2 - Featherston

FEATHERSTON Masterton UFB2 - Featherston UFB2 Fringe

FEILDING Fielding / Palmerston North UFB1 - Fielding

FEILDING Fielding / Palmerston North UFB2 - Feilding

FEILDING Fielding / Palmerston North UFB2 - Feilding UFB2 Fringe

FENDALTON Christchurch Non UFB funded build

FLAGSTAFF Hamilton / Frankton Non UFB funded build

FLAXMERE Napier / Hastings / Marewa UFB1 - Napier

FORREST HILL Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

FOX GLACIER Greymouth UFB2 - Fox Glacier

FOXTON Levin UFB2 - Foxton UFB2 Fringe

FOXTON Levin UFB2 - Foxton Beach

FOXTON BEACH Levin UFB2 - Foxton Beach

FRANKLEIGH PARK New Plymouth Non UFB funded build




FRANKTON Hamilton / Frankton UFB2 - Temple View

FRANZ JOSEF GLACIER Greymouth UFB2 - Franz Josef/Waiau

GARSTON Invercargill / Waikiwi UFB2 - Kingston

GERALDINE Timaru UFB2 - Geraldine

GERALDINE Timaru UFB2 - Geraldine UFB2 Fringe

GISBORNE Gisborne UFB1 - Gisborne

GISBORNE Gisborne UFB2 - Gisborne

GISBORNE Gisborne UFB2 - Gisborne UFB2 Fringe

GLEN EDEN Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

GLENAVY Timaru UFB2 - Glenavy

GLENDOWIE Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

GLENFIELD Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

GLENITI Timaru UFB1 - Timaru

GLENTUNNEL Christchurch UFB2 - Coalgate/Glentunnel

GONVILLE Wanganui Non UFB funded build

GORE Invercargill / Waikiwi UFB1 - Invercargill

GRANITY Greymouth UFB2 - Granity

GREEN ISLAND Dunedin / North East Valley / South Dunedin UFB1 - Dunedin

GREEN ISLAND Dunedin / North East Valley / South Dunedin UFB2 - Dunedin

GREENHITHE Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

GREYMOUTH Greymouth UFB1 - Greymouth

GREYTOWN Masterton UFB2 - Greytown

GREYTOWN Masterton UFB2 - Greytown UFB2 Fringe

HALFWAY BUSH Dunedin / North East Valley / South Dunedin UFB1 - Dunedin

HALSWELL Christchurch Non UFB funded build

HAMILTON Hamilton / Frankton UFB2 - Hamilton - Whatawhata

HAMILTON EAST Hamilton / Frankton UFB2 - Rukuhia UFB2 Fringe

HAMILTON EAST Hamilton / Frankton UFB2 - Tamahere UFB2 Fringe

HAMPDEN Dunedin / North East Valley / South Dunedin UFB2 - Hampden

HAMPDEN Dunedin / North East Valley / South Dunedin UFB2 - Moeraki

HANMER SPRINGS Christchurch UFB2 - Hanmer Springs

HAREWOOD Christchurch UFB2 - Belfast

HARIHARI Greymouth UFB2 - Hari Hari




HASTINGS Napier / Hastings / Marewa UFB1 - Napier

HASTINGS Napier / Hastings / Marewa UFB2 - Wall Rd

HATAITAI Courtney Place / Johnsonville / Porirua / Wellington UFB1 - Wellington

HAUMOANA Napier / Hastings / Marewa UFB2 - Clive Beach/Bay View UFB2 Fringe

HAUMOANA Napier / Hastings / Marewa UFB2 - Te Awanga

HAVELOCK Blenheim UFB2 - Havelock

HAVELOCK Blenheim UFB2 - Havelock UFB2 Fringe

HAVELOCK NORTH Napier / Hastings / Marewa UFB1 - Napier

HAWARDEN Christchurch UFB2 - Hawarden

HAWARDEN Christchurch UFB2 - Waikari

HAWERA New Plymouth Non UFB funded build

HELENSVILLE Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Helensville/Parakai

HELENSVILLE Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Helensville/Parakai UFB2 Fringe

HENDERSON Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

HIBISCUS COAST Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

HIKURANGI Whangarei / Kensington Non UFB funded build

HILLMORTON Christchurch Non UFB funded build

HIMATANGI Fielding / Palmerston North UFB2 - Himatangi Beach

HINDS Ashburton Non UFB funded build

HOKITIKA Greymouth UFB2 - Hokitika

HOKITIKA Greymouth UFB2 - Hokitika UFB2 Fringe

HOKITIKA Greymouth UFB2 - Kaniere

HORORATA Christchurch UFB2 - Hororata

HOROTIU Hamilton / Frankton UFB2 - Hamilton - Horotiu

HOROTIU Hamilton / Frankton UFB2 - Horotiu UFB2 Fringe

HORSHAM DOWNS Hamilton / Frankton Non UFB funded build

HOWICK Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

HUIA Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Huia

HUNTERVILLE Fielding / Palmerston North UFB2 - Hunterville

HUNTLY Hamilton / Frankton Non UFB funded build

INGLEWOOD New Plymouth Non UFB funded build

INVERCARGILL Invercargill / Waikiwi UFB1 - Invercargill

INVERCARGILL EAST Invercargill / Waikiwi UFB2 - Mill Road

INVERCARGILL EAST Invercargill / Waikiwi UFB1 - Invercargill




ISLAND BAY Courtney Place / Johnsonville / Porirua / Wellington UFB1 - Wellington

ISLINGTON Christchurch Non UFB funded build JOHN F KENNEDY DR. Fielding / Palmerston North UFB1 - Palmerston North

JOHNSONVILLE Courtney Place / Johnsonville / Porirua / Wellington UFB1 - Wellington

KAIAPOI Christchurch Non UFB funded build

KAIKOHE Whangarei / Kensington UFB2 - Kaikohe

KAIKOHE Whangarei / Kensington UFB2 - Kaikohe UFB2 Fringe

KAIKOURA Christchurch UFB2 - Kaikoura

KAIKOURA Christchurch UFB2 - Kaikoura UFB2 Fringe

KAIKOURA Christchurch UFB2 - South Kaikoura

KAITAIA Whangarei / Kensington UFB2 - Kaitaia

KAITAIA Whangarei / Kensington UFB2 - Kaitaia UFB2 Fringe

KAITANGATA Dunedin / North East Valley / South Dunedin UFB2 - Kaitangata

KAITERITERI Nelson / Stoke UFB2 - Kaiteriteri

KAITERITERI Nelson / Stoke UFB2 - Kaiteriteri UFB2 Fringe

KAITERITERI Nelson / Stoke UFB2 - Marahau

KAIWAKA Whangarei / Kensington Non UFB funded build

KAMO Whangarei / Kensington Non UFB funded build

KAPONGA New Plymouth UFB2 - Kaponga

KARAMEA Greymouth UFB2 - Karamea

KARORI Courtney Place / Johnsonville / Porirua / Wellington UFB1 - Wellington

KATIKATI Tauranga / Otumoetai Non UFB funded build

KAUKAPAKAPA Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Kaukapakapa

KAWAKAWA Whangarei / Kensington UFB2 - Moerewa/Kawakawa

KAWAKAWA Whangarei / Kensington UFB2 - Moerewa/Kawakawa UFB2 Fringe

KAWERAU Whakatane UFB2 - Kawerau

KAWERAU Whakatane UFB2 - Kawerau UFB2 Fringe

KELBURN Courtney Place / Johnsonville / Porirua / Wellington UFB1 - Wellington

KELVIN GROVE Fielding / Palmerston North UFB1 - Palmerston North

KENSINGTON Whangarei / Kensington Non UFB funded build

KERIKERI Whangarei / Kensington UFB2 - Kerikeri

KERIKERI Whangarei / Kensington UFB2 - Kerikeri UFB2 Fringe

KERIKERI Whangarei / Kensington UFB2 - Rangitana

KERIKERI Whangarei / Kensington UFB2 - Waipapa




KHANDALLAH Courtney Place / Johnsonville / Porirua / Wellington UFB1 - Wellington

KILBIRNIE Courtney Place / Johnsonville / Porirua / Wellington UFB1 - Wellington

KIMBOLTON Fielding / Palmerston North UFB2 - Kimbolton

KIRWEE Christchurch UFB2 - Kirwee

KUMARA Greymouth UFB2 - Kumara

KUMEU Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

KUROW Oamaru UFB2 - Kurow

LAKE TEKAPO Timaru UFB2 - Lake Tekapo

LAKE TEKAPO Timaru UFB2 - Lake Tekapo UFB2 Fringe

LAWRENCE Invercargill / Waikiwi UFB2 - Lawrence

LEESTON Christchurch UFB2 - Doyleston

LEESTON Christchurch UFB2 - Leeston

LEESTON Christchurch UFB2 - Leeston UFB2 Fringe

LEIGH Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Leigh

LEITH VALLEY Dunedin / North East Valley / South Dunedin UFB1 - Dunedin

LEPPERTON New Plymouth UFB2 - Lepperton

LEVIN Levin UFB1 - Levin

LEVIN Levin UFB2 - Hokio Beach

LEVIN Levin UFB2 - Waitarere/Waitarere Beach

LINCOLN Christchurch UFB2 - Christchurch - Lincoln

LINCOLN Christchurch UFB2 - Christchurch - Lincoln UFB2 Fringe

LINWOOD Christchurch Non UFB funded build

LITTLE RIVER Christchurch UFB2 - Little River

LOWER HUTT Courtney Place / Johnsonville / Porirua / Wellington UFB1 - Wellington

LUMSDEN Invercargill / Waikiwi UFB2 - Lumsden

LYNMORE Rotorua / Lynmore UFB1 - Rotorua

LYNMORE Rotorua / Lynmore UFB2 - Hinemoa Point

LYTTELTON Christchurch UFB2 - Cass Bay

LYTTON WEST Gisborne UFB1 - Gisborne

MACANDREW BAY Dunedin / North East Valley / South Dunedin UFB1 - Dunedin

MAHENO Oamaru UFB2 - Maheno

MAHENO Oamaru UFB2 - Taranui/Kakanui

MAHURANGI Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Mahurangi

MAHURANGI Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Snells Beach




MAHURANGI Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Snells Beach UFB2 Fringe

MAKAREWA Invercargill / Waikiwi UFB2 - Wallacetown

MAKETU Tauranga / Otumoetai UFB2 - Maketu

MAKETU Tauranga / Otumoetai UFB2 - Maketu UFB2 Fringe

MAMAKU Rotorua / Lynmore UFB2 - Mamaku

MANAIA New Plymouth UFB2 - Manaia

MANAIA New Plymouth UFB2 - Manaia UFB2 Fringe

MANAKAU Levin UFB2 - Manakau

MANAKAU Levin UFB2 - Waikawa Beach

MANAPOURI Invercargill / Waikiwi UFB2 - Blackmount/Manapouri UFB2+

MANGAKINO Taupo UFB2 - Mangakino

MANGAWEKA Fielding / Palmerston North UFB2 - Mangaweka

MANGAWHAI Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Mangawhai

MANGERE Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

MANGONUI Whangarei / Kensington UFB2 - Hihi

MANGONUI Whangarei / Kensington UFB2 - Taipa

MANGONUI Whangarei / Kensington UFB2 - Taipa Bay-Mangonui

MANGONUI Whangarei / Kensington UFB2 - Taipa Bay-Mangonui UFB2 Fringe

MANUKAU CITY Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

MANUREWA Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

MANUTUKE Gisborne UFB2 - Manutuke

MAORI HILL Dunedin / North East Valley / South Dunedin UFB1 - Dunedin

MAPUA Nelson / Stoke UFB2 - Ruby Bay

MAPUA Nelson / Stoke UFB2 - Ruby Bay UFB2 Fringe

MAREWA Napier / Hastings / Marewa UFB1 - Napier

MARTINBOROUGH Masterton UFB2 - Martinborough

MARTINBOROUGH Masterton UFB2 - Martinborough UFB2 Fringe

MARTON Fielding / Palmerston North UFB2 - Marton

MARTON Fielding / Palmerston North UFB2 - Marton UFB2 Fringe

MASSEY Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

MASTERTON Masterton UFB1 - Masterton

MATAKANA Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Matakana Village

MATAKANA Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Matakana Village UFB2 Fringe




MATAKANA Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Omaha

MATAKANA Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Point Wells

MATAMATA Hamilton / Frankton UFB2 - Matamata

MATAMATA Hamilton / Frankton UFB2 - Matamata UFB2 Fringe

MATAMATA Hamilton / Frankton UFB2 - Waharoa

MATANGI Hamilton / Frankton Non UFB funded build

MATATA Whakatane UFB2 - Matata

MATATA Whakatane UFB2 - Matata UFB2 Fringe

MATATOKI Tauranga / Otumoetai UFB2 - Matatoki

MATAURA Invercargill / Waikiwi UFB1 - Invercargill

MAUNGAKARAMEA Whangarei / Kensington UFB2 - Maungakaramea

MAUNGATAPERE Whangarei / Kensington UFB2 - Maungatapere

MAUNGATAPU Hamilton / Frankton Non UFB funded build

MAUNGATUROTO Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby Non UFB funded build

MAXWELLS LINE Fielding / Palmerston North UFB1 - Palmerston North

MAXWELLS LINE Fielding / Palmerston North UFB2 - Palmerston North

MAYORAL DRIVE Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Auckland Zone

MAYORAL DRIVE Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Auckland Zone UFB2 Fringe

MAYORAL DRIVE Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

MELVILLE Hamilton / Frankton UFB2 - Hamilton - Rukuhia

MELVILLE Hamilton / Frankton UFB2 - Rukuhia UFB2 Fringe

MEMORIAL AVE Christchurch Non UFB funded build

METHVEN Ashburton UFB2 - Methven

METHVEN Ashburton UFB2 - Methven UFB2 Fringe

MIDDLETON Christchurch Non UFB funded build

MIDHURST New Plymouth UFB2 - Midhirst

MILLBROOK Queenstown UFB2 - Arrowtown

MILTON Dunedin / North East Valley / South Dunedin UFB2 - Milton

MILTON Dunedin / North East Valley / South Dunedin UFB2 - Milton UFB2 Fringe

MIRAMAR Courtney Place / Johnsonville / Porirua / Wellington UFB1 - Wellington

MOANA Greymouth UFB2 - Moana

MOKAU New Plymouth UFB2 - Mokau

MORNINGTON Dunedin / North East Valley / South Dunedin UFB1 - Dunedin




MORRINSVILLE Hamilton / Frankton UFB2 - Morrinsville

MORRINSVILLE Hamilton / Frankton UFB2 - Morrinsville UFB2 Fringe

MOSGIEL Dunedin / North East Valley / South Dunedin UFB1 - Dunedin

MOSGIEL Dunedin / North East Valley / South Dunedin UFB2 - Allanton

MOSSBURN Invercargill / Waikiwi UFB2 - Mossburn

MOTUEKA Nelson / Stoke UFB2 - Motueka

MOTUEKA Nelson / Stoke UFB2 - Motueka UFB2 Fringe

MOTUEKA Nelson / Stoke UFB2 - Riwaka

MT ALBERT Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

MT MAUNGANUI Tauranga / Otumoetai Non UFB funded build

MT PLEASANT Christchurch Non UFB funded build

MT EDEN Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

MT ROSKILL Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

MT SOMERS Ashburton UFB2 - Mt Somers

MT WELLINGTON Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

MURCHISON Nelson / Stoke UFB2 - Murchison

MURCHISON Nelson / Stoke UFB2 - Murchison UFB2 Fringe

MURUPARA Rotorua / Lynmore UFB2 - Murupara

MURUPARA Rotorua / Lynmore UFB2 - Murupara UFB2 Fringe

NAENAE Courtney Place / Johnsonville / Porirua / Wellington UFB1 - Wellington

NAPIER Napier / Hastings / Marewa UFB1 - Napier

NAPIER Napier / Hastings / Marewa UFB2 - Awatoto Industrial

NAPIER Napier / Hastings / Marewa UFB2 - Awatoto Industrial UFB2 Fringe

NATIONAL PARK Fielding / Palmerston North UFB2 - National Park

NELSON Nelson / Stoke UFB1 - Nelson

NELSON Nelson / Stoke UFB2 - Nelson The Brook

NELSON Nelson / Stoke UFB2 - Nelson The Brook UFB2 Fringe

NEW BRIGHTON Christchurch Non UFB funded build

NEW LYNN Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

NEW PLYMOUTH New Plymouth Non UFB funded build

NGAHERE Greymouth UFB2 - Blackball

NGARUAWAHIA Hamilton / Frankton Non UFB funded build

NGATEA Hamilton / Frankton UFB2 - Ngatea

NGATEA Hamilton / Frankton UFB2 - Ngatea UFB2 Fringe




NGATEA Whangarei / Kensington UFB2 - Matapouri

NGONGOTAHA Rotorua / Lynmore UFB1 - Rotorua

NGUNGURU Whangarei / Kensington UFB2 - Ngunguru

NIGHTCAPS Invercargill / Waikiwi UFB2 - Nightcaps

NORMANBY New Plymouth Non UFB funded build

NORTH EAST VALLEY

Dunedin / North East Valley / South Dunedin UFB1 - Dunedin

OAKLEIGH Whangarei / Kensington UFB2 - Portland

OAKURA New Plymouth Non UFB funded build

OAMARU Oamaru UFB1 - Oamaru

OAMARU Oamaru UFB2 - UFB 1 Fringe: Weston

OAMARU Oamaru UFB2 - Weston UFB2 Fringe

OAMARU NORTH Oamaru UFB1 - Oamaru

OHAEAWAI Whangarei / Kensington UFB2 - Ohaeawai

OHAI Invercargill / Waikiwi UFB2 - Ohai

OHAKUNE Fielding / Palmerston North UFB2 - Ohakune

OHAKUNE Fielding / Palmerston North UFB2 - Ohakune UFB2 Fringe

OHAU Levin UFB2 - Ohau

OHAUPO Hamilton / Frankton UFB2 - Hamilton - Ohaupo

OHAUPO Hamilton / Frankton UFB2 - Ohaupo UFB2 Fringe

OHOKA Christchurch UFB2 - Manderville

OHOPE Whakatane UFB2 - Ohope

OKAREKA Rotorua / Lynmore UFB2 - Lake Okareka/Okareka

OKATO New Plymouth UFB2 - Okato

OKATO New Plymouth UFB2 - Okato UFB2 Fringe

OKERE FALLS Rotorua / Lynmore UFB2 - Okere Falls

OMAKAU Queenstown UFB2 - Omakau

OMARAMA Oamaru UFB2 - Omarama

OMOKOROA Tauranga / Otumoetai UFB2 - Omokoroa

ONEHUNGA Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

ONERAHI Whangarei / Kensington Non UFB funded build

ONGA ONGA Napier / Hastings / Marewa UFB2 - Ongaonga

OPONONI Whangarei / Kensington UFB2 - Opononi

OPOTIKI Whakatane UFB2 - Kukumoa/Waiotahi Beach

OPOTIKI Whakatane UFB2 - Opotiki

OPOTIKI Whakatane UFB2 - Opotiki UFB2 Fringe

OPUNAKE New Plymouth UFB2 - Opunake

OPUNAKE New Plymouth UFB2 - Opunake UFB2 Fringe




OTAHUHU Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

OTAKI Paraparaumu UFB2 - Otaki

OTAKI Paraparaumu UFB2 - Otaki UFB2 Fringe

OTANE Napier / Hastings / Marewa UFB2 - Otane

OTANE Napier / Hastings / Marewa UFB2 - Otane UFB2 Fringe

OTARA Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

OTARA Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Flat Bush

OTATARA Invercargill / Waikiwi UFB2 - Otatara UFB2 Fringe

OTATARA Invercargill / Waikiwi UFB2 - UFB 1 Fringe: Otatara

OTAUTAU Invercargill / Waikiwi UFB2 - Blackmount/Manapouri

OTAUTAU Invercargill / Waikiwi UFB2 - Otautau

OTEMATATA Oamaru UFB2 - Otematata

OTOROHANGA Hamilton / Frankton UFB2 - Otorohanga

OTOROHANGA Hamilton / Frankton UFB2 - Otorohanga UFB2 Fringe

OTUMOETAI Tauranga / Otumoetai Non UFB funded build

OUTRAM Dunedin / North East Valley / South Dunedin UFB2 - Outram

OUTRAM Dunedin / North East Valley / South Dunedin UFB2 - Outram UFB2 Fringe

OWAKA Invercargill / Waikiwi UFB2 - Owaka

OWHANGO Fielding / Palmerston North UFB2 - Owhango

OXFORD Christchurch UFB2 - Oxford

OXFORD Christchurch UFB2 - Oxford UFB2 Fringe

PACIFIC VIEW Tauranga / Otumoetai Non UFB funded build

PAEKAKARIKI Paraparaumu UFB1 - Kapiti

PAENGAROA Tauranga / Otumoetai UFB2 - Paengaroa

PAENGAROA Tauranga / Otumoetai UFB2 - Paengaroa UFB2 Fringe

PAEROA Hamilton / Frankton UFB2 - Paeroa

PAEROA Hamilton / Frankton UFB2 - Paeroa UFB2 Fringe

PAHIATUA Fielding / Palmerston North UFB2 - Pahiatua

PAHIATUA Fielding / Palmerston North UFB2 - Pahiatua UFB2 Fringe

PAIHIA Whangarei / Kensington UFB2 - Opua/Okiato

PAIHIA Whangarei / Kensington UFB2 - Paihia

PAIHIA Whangarei / Kensington UFB2 - Paihia UFB2 Fringe

PAKURANGA Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

PALMERSTON Dunedin / North East Valley / South Dunedin UFB2 - Palmerston




PALMERSTON NORTH Fielding / Palmerston North UFB1 - Palmerston North

PAPAKURA Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

PAPAMOA Tauranga / Otumoetai Non UFB funded build

PAPANUI Christchurch Non UFB funded build

PAPATOETOE Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

PARAPARAUMU Paraparaumu UFB1 - Kapiti

PARAPARAUMU Paraparaumu UFB2 - Kapiti

PARAPARAUMU Paraparaumu UFB2 - Kapiti UFB2 Fringe

PARAPARAUMU Paraparaumu UFB2 - Otaihanga/Nikau Valley

PAROA Greymouth UFB1 - Greymouth

PATEA New Plymouth UFB2 - Patea

PATEA New Plymouth UFB2 - Patea UFB2 Fringe

PATUMAHOE Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Sedgebrook/Patumahoe

PETONE Courtney Place / Johnsonville / Porirua / Wellington UFB1 - Wellington

PICTON Blenheim UFB2 - Picton

PICTON Blenheim UFB2 - Picton UFB2 Fringe

PIHA Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Piha

PIHA Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Piha UFB2 Fringe

PIO PIO Hamilton / Frankton UFB2 - Piopio

PIO PIO Hamilton / Frankton UFB2 - Piopio UFB2 Fringe

PIRONGIA Hamilton / Frankton UFB2 - Pirongia

PIRONGIA Hamilton / Frankton UFB2 - Pirongia UFB2 Fringe

PLEASANT POINT Timaru UFB2 - Pleasant Point

PLEASANT POINT Timaru UFB2 - Pleasant Point UFB2 Fringe

PLIMMERTON Courtney Place / Johnsonville / Porirua / Wellington UFB1 - Wellington

POKENO Hamilton / Frankton UFB2 - Meremere

POKENO Hamilton / Frankton UFB2 - Pokeno

PONSONBY Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

PORIRUA Courtney Place / Johnsonville / Porirua / Wellington UFB1 - Wellington

PORT CHALMERS Dunedin / North East Valley / South Dunedin UFB1 - Dunedin

PORT WAIKATO Hamilton / Frankton UFB2 - Port Waikato

PORTOBELLO Dunedin / North East Valley / South Dunedin UFB1 - Dunedin




PORTOBELLO Dunedin / North East Valley / South Dunedin UFB2 - Dunedin UFB2 Fringe

PUHOI Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Mahurangi West/Waiwera

PUHOI Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Puhoi

PUKEHINA Tauranga / Otumoetai UFB2 - Maketu/Pukehina Beach

PUKEKOHE Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Anselmi Ridge Rd

PUKEKOHE Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Anselmi Ridge Rd UFB2 Fringe

PUKEKOHE Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Pukekohe

PUKEKOHE Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Pukekohe UFB2 Fringe

PUKEKOHE Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Pukekohe

PUKENUI Whangarei / Kensington UFB2 - Pukenui

PUKERUA BAY Paraparaumu UFB1 - Kapiti

PUTARURU Hamilton / Frankton Non UFB funded build

QUEENSTOWN Queenstown UFB1 - Queenstown

QUEENSTOWN Queenstown UFB2 - Arthurs Point

QUEENSTOWN Queenstown UFB2 - Arthurs Point UFB2 Fringe

RAETIHI Fielding / Palmerston North UFB2 - Raetihi

RAETIHI Fielding / Palmerston North UFB2 - Raetihi UFB2 Fringe

RAGLAN Hamilton / Frankton Non UFB funded build

RAKAIA Ashburton UFB2 - Rakaia

RAKAIA Ashburton UFB2 - Rakaia UFB2 Fringe

RANFURLY Queenstown UFB2 - Naseby

RANFURLY Queenstown UFB2 - Ranfurly

RANGIORA Christchurch UFB2 - Christchurch - Rangiora

RANGIORA Christchurch UFB2 - Christchurch - Rangiora UFB2 Fringe

RAUMATI Paraparaumu UFB1 - Kapiti

RAVENSBOURNE Dunedin / North East Valley / South Dunedin UFB1 - Dunedin

RAWENE Whangarei / Kensington UFB2 - Rawene

RED BEACH Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

REEFTON Greymouth UFB2 - Reefton

REEFTON Greymouth UFB2 - Reefton UFB2 Fringe

REMUERA Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

RENWICK Blenheim UFB2 - Renwick

RENWICK Blenheim UFB2 - Renwick UFB2 Fringe




RICHMOND Nelson / Stoke UFB1 - Nelson

RICHMOND Nelson / Stoke UFB2 - Hope

RIVERSDALE Invercargill / Waikiwi UFB2 - Riversdale

RIVERSDALE Invercargill / Waikiwi UFB2 - Waikaia

RIVERTON Invercargill / Waikiwi UFB2 - Riverton West

RIVERTON Invercargill / Waikiwi UFB2 - Riverton West UFB2 Fringe

ROLLESTON Christchurch UFB2 - West Melton

ROLLESTON Christchurch UFB2 - West Melton UFB2 Fringe

RONGOTEA Fielding / Palmerston North UFB2 - Rongotea

ROSS Greymouth UFB2 - Ross

ROTOITI Rotorua / Lynmore UFB2 - Rotoiti Forest

ROTORUA Rotorua / Lynmore UFB1 - Rotorua

ROTORUA Rotorua / Lynmore UFB2 - Fairy Springs Road

ROTORUA Rotorua / Lynmore UFB2 - Rotorua

ROXBURGH Queenstown UFB2 - Roxburgh

ROXBURGH Queenstown UFB2 - Roxburgh UFB2 Fringe

RUAKAKA Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - One Tree Point

RUAKAWAKAWA Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Kawakawa Bay

RUATORIA Gisborne UFB2 - Ruatoria

RUATORIA Gisborne UFB2 - Ruatoria UFB2 Fringe

RUNANGA Greymouth UFB2 - Runanga

RUNANGA Greymouth UFB2 - Runanga UFB2 Fringe

RUNCIMAN Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

RUSSELL Whangarei / Kensington UFB2 - Russell

RUSSELL Whangarei / Kensington UFB2 - Russell UFB2 Fringe

SANSON Fielding / Palmerston North UFB2 - Sanson

SEDDON Blenheim UFB2 - Seddon

SHANNON Levin UFB2 - Shannon

SHANNON Levin UFB2 - Shannon UFB2 Fringe

SHEFFIELD Christchurch UFB2 - Waddington/Sheffield

SHIRLEY Christchurch Non UFB funded build

SOUTH DUNEDIN Dunedin / North East Valley / South Dunedin UFB1 - Dunedin

SOUTH INVERCARGILL Invercargill / Waikiwi UFB1 - Invercargill

SOUTHBRIDGE Christchurch UFB2 - Southbridge

SOUTHBRIDGE Christchurch UFB2 - Southbridge UFB2 Fringe




SPOTSWOOD New Plymouth Non UFB funded build

SPRING CREEK Christchurch UFB2 - Southbridge UFB2 Fringe

SPRINGSTON Christchurch UFB2 - Lincoln

ST ALBANS Christchurch Non UFB funded build

ST ANDREWS Timaru UFB2 - Pareora

ST ARNAUD Nelson / Stoke UFB2 - St Arnaud

ST HELIERS Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

STOKE Nelson / Stoke UFB1 - Nelson

STOKES VALLEY Courtney Place / Johnsonville / Porirua / Wellington UFB1 - Wellington

STRATFORD New Plymouth Non UFB funded build

SUMNER Christchurch Non UFB funded build

TAHUNANUI Nelson / Stoke UFB1 - Nelson

TAIHAPE Fielding / Palmerston North UFB2 - Taihape

TAIHAPE Fielding / Palmerston North UFB2 - Taihape UFB2 Fringe

TAIRUA Tauranga / Otumoetai UFB2 - Tairua

TAIRUA Tauranga / Otumoetai UFB2 - Tairua UFB2 Fringe

TAITAPU Christchurch UFB2 - Taitapu

TAKAKA Nelson / Stoke UFB2 - Clifton/Tata Beach/Pohara

TAKAKA Nelson / Stoke UFB2 - Takaka

TAKAPAU Napier / Hastings / Marewa UFB2 - Takapau

TAKAPUNA Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

TAMAKI Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

TAPANUI Dunedin / North East Valley / South Dunedin UFB2 - Tapanui

TAPAWERA Nelson / Stoke UFB2 - Tapawera

TAPAWERA Nelson / Stoke UFB2 - Tasman

TAPU Tauranga / Otumoetai UFB2 - Tapu

TARADALE Napier / Hastings / Marewa UFB1 - Napier

TARADALE Napier / Hastings / Marewa UFB2 - Napier-Hastings

TARADALE Napier / Hastings / Marewa UFB2 - Napier-Hastings UFB2 Fringe

TASMAN Nelson / Stoke UFB2 - Tasman

TAUMARUNUI Hamilton / Frankton UFB2 - Taumarunui

TAUMARUNUI Hamilton / Frankton UFB2 - Taumarunui UFB2 Fringe

TAUPIRI Hamilton / Frankton UFB2 - Hamilton - Taupiri

TAUPIRI Hamilton / Frankton UFB2 - Taupiri UFB2 Fringe

TAUPO Taupo UFB1 - Taupo

TAUPO Taupo UFB2 - Acacia bay




TAUPO Taupo UFB2 - Kinloch

TAUPO Taupo UFB2 - Taupo

TAUPO Taupo UFB2 - Taupo Airport

TAUPO Taupo UFB2 - Taupo UFB2 Fringe

TAURANGA Tauranga / Otumoetai Non UFB funded build

TAWA Courtney Place / Johnsonville / Porirua / Wellington UFB1 - Wellington

TE ANAU Invercargill / Waikiwi UFB2 - Te Anau

TE ANAU Invercargill / Waikiwi UFB2 - Te Anau UFB2 Fringe

TE AROHA Hamilton / Frankton UFB2 - Te Aroha

TE AROHA Hamilton / Frankton UFB2 - Te Aroha UFB2 Fringe

TE AROHA Hamilton / Frankton UFB2 - Waihou

TE ATATU Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

TE AWAMUTU Hamilton / Frankton UFB2 - Kihikihi

TE HORO Paraparaumu UFB2 - Te Horo/Te Horo Beach

TE KARAKA Gisborne UFB2 - Te Karaka

TE KAUWHATA Hamilton / Frankton UFB2 - Te Kauwhata

TE KAUWHATA Hamilton / Frankton UFB2 - Te Kauwhata UFB2 Fringe

TE KOWHAI Hamilton / Frankton UFB2 - Te Kuiti

TE KUITI Hamilton / Frankton UFB2 - Te Kuiti

TE KUITI Hamilton / Frankton UFB2 - Te Kuiti UFB2 Fringe

TE PUKE Tauranga / Otumoetai Non UFB funded build

TE PUNA Tauranga / Otumoetai UFB2 - Te Puna (Minden)

TE PUNA Tauranga / Otumoetai UFB2 - Te Puna UFB2 Fringe

TE PUNA Tauranga / Otumoetai UFB2 - UFB 1 Fringe: Te Puna

TE PURU Hamilton / Frankton UFB2 - Te Puru

TE PURU Hamilton / Frankton UFB2 - Te Puru UFB2 Fringe

TE PURU Tauranga / Otumoetai UFB2 - Waiomu

TE RANGA Tauranga / Otumoetai Non UFB funded build

TE RAPA Hamilton / Frankton UFB2 - Rorokauri

TE TEKO Whakatane UFB2 - Te Teko

TE UKU Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Tuakau

TE UKU Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Tuakau UFB2 Fringe

TEMUKA Timaru UFB2 - Temuka

TEMUKA Timaru UFB2 - Temuka UFB2 Fringe

TEMUKA Timaru UFB2 - Winchester

THAMES Hamilton / Frankton UFB2 - Thames




THAMES Hamilton / Frankton UFB2 - Thames UFB2 Fringe

THREE KINGS Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

TIMARU Timaru UFB1 - Timaru

TIRAU Hamilton / Frankton Non UFB funded build

TITAHI BAY Courtney Place / Johnsonville / Porirua / Wellington UFB1 - Wellington

TITIRANGI Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

TITIRANGI Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Parau

TITIRANGI Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Parau UFB2 Fringe

TOKANUI Invercargill / Waikiwi UFB2 - Tokanui

TOKOMARU Levin UFB2 - Tokomaru

TOKOROA Hamilton / Frankton Non UFB funded build

TOLAGA BAY Gisborne UFB2 - Tologa Bay

TOLAGA BAY Gisborne UFB2 - Tologa Bay UFB2 Fringe

TORBAY Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

TORBAY Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Okura

TUAKAU Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Tuakau

TUATAPERE Invercargill / Waikiwi UFB2 - Tuatapere

TURAKINA Wanganui UFB2 - Turakina

TURANGI Taupo UFB2 - Kuratau/Pukawa

TURANGI Taupo UFB2 - Turangi

TURANGI Taupo UFB2 - Turangi UFB2 Fringe

TURITEA Fielding / Palmerston North UFB1 - Palmerston North

TURITEA Fielding / Palmerston North UFB2 - Summerhill

TURITEA Fielding / Palmerston North UFB2 - Summerhill UFB2 Fringe

TURUA Hamilton / Frankton UFB2 - Turua

TWIZEL Timaru UFB2 - Twizel Community

TWIZEL Timaru UFB2 - Twizel Community UFB2 Fringe

UPPER HUTT Courtney Place / Johnsonville / Porirua / Wellington UFB1 - Wellington

UPPER HUTT Courtney Place / Johnsonville / Porirua / Wellington UFB2 - Alexander Rd

UPPER HUTT Courtney Place / Johnsonville / Porirua / Wellington UFB2 - Racecourse Rd

UPPER HUTT Courtney Place / Johnsonville / Porirua / Wellington UFB2 - Racecourse Rd UFB2 Fringe

UPPER HUTT Courtney Place / Johnsonville / Porirua / Wellington UFB2 - Upper Hutt Zone UFB2 Fringe




UPPER HUTT Courtney Place / Johnsonville / Porirua / Wellington UFB2 - Ward Street

UPPER HUTT Courtney Place / Johnsonville / Porirua / Wellington UFB2 - Ward Street UFB2 Fringe

UPPER HUTT Courtney Place / Johnsonville / Porirua / Wellington UFB2 - Wellington Zone

UPPER HUTT NORTH

Courtney Place / Johnsonville / Porirua / Wellington UFB1 - Wellington

URENUI New Plymouth UFB2 - Urenui

URENUI New Plymouth UFB2 - Urenui UFB2 Fringe

WAIATARUA Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Waiatarua

WAIATARUA Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Waiatarua UFB2 Fringe

WAIATARUA Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Waiatarua/Spragg Bush/Parkinsons lookout

WAIAU Christchurch UFB2 - Rotherham

WAIAU Christchurch UFB2 - Waiau

WAIAU PA Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Waiau Beach

WAIAU PA Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Waiau Beach UFB2 Fringe

WAIHEKE Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Waiheke

WAIHEKE Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Waiheke UFB2 Fringe

WAIHEKE Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Waiheke

WAIHI Tauranga / Otumoetai UFB2 - Waihi town & Beach

WAIHI BEACH Tauranga / Otumoetai UFB2 - Waihi town & Beach

WAIHI BEACH Tauranga / Otumoetai UFB2 - Waihi town & Beach UFB2 Fringe

WAIKANAE Paraparaumu UFB1 - Kapiti

WAIKANAE Paraparaumu UFB2 - Peka Peka

WAIKANAE Paraparaumu UFB2 - Pukeko St Area

WAIKANAE Paraparaumu UFB2 - Pukeko St Area UFB2 Fringe

WAIKIWI Invercargill / Waikiwi UFB1 - Invercargill

WAIKOUAITI Dunedin / North East Valley / South Dunedin UFB2 - Karitane

WAIKOUAITI Dunedin / North East Valley / South Dunedin UFB2 - Waikouaiti

WAIKOUAITI Dunedin / North East Valley / South Dunedin UFB2 - Waikouaiti UFB2 Fringe

WAIMANGAROA Greymouth UFB2 - Waimangaroa

WAIMARAMA Napier / Hastings / Marewa UFB2 - Waimarama

WAIMATE Timaru UFB2 - Waimate

WAIMATE Timaru UFB2 - Waimate UFB2 Fringe




WAIMAUKU Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Muriwai Beach

WAIMAUKU Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Muriwai Beach UFB2 Fringe

WAIMAUKU Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Waimauku

WAIMAUKU Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Waimauku UFB2 Fringe

WAINUIOMATA Courtney Place / Johnsonville / Porirua / Wellington UFB1 - Wellington

WAIOURU Fielding / Palmerston North UFB2 - Waiouru

WAIPARA Christchurch UFB2 - Waipara

WAIPAWA Napier / Hastings / Marewa UFB2 - Waipawa/Waipukurau

WAIPAWA Napier / Hastings / Marewa UFB2 - Waipawa/Waipukurau UFB2 Fringe

WAIPU Whangarei / Kensington UFB2 - Langs Beach/Waipu Cove

WAIPUKURAU Napier / Hastings / Marewa UFB2 - Waipawa/Waipukurau

WAIRAKEI Taupo UFB2 - Wairakei Village/Wairakei

WAIROA Napier / Hastings / Marewa UFB2 - Frasertown

WAIROA Napier / Hastings / Marewa UFB2 - Wairoa

WAIROA Napier / Hastings / Marewa UFB2 - Wairoa UFB2 Fringe

WAITAKERE Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Waitakere

WAITANGIRUA Courtney Place / Johnsonville / Porirua / Wellington UFB1 - Wellington

WAITARA New Plymouth UFB2 - Waitara

WAITATI Dunedin / North East Valley / South Dunedin UFB2 - Michies Crossing/Waitati

WAITATI Dunedin / North East Valley / South Dunedin UFB2 - Warrington

WAITOA Hamilton / Frankton UFB2 - Waitoa

WAIUKU Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Waiuku

WAKATIPU Queenstown UFB1 - Queenstown

WAKATIPU Queenstown UFB2 - Jacks Point

WAKATIPU Queenstown UFB2 - Queenstown

WAKATIPU Queenstown UFB2 - Queenstown UFB2 Fringe

WAKEFIELD Nelson / Stoke UFB2 - Wakefield

WANAKA Queenstown UFB2 - Luggate

WANAKA Queenstown UFB2 - Wanaka/Lake Hawea

WANAKA Queenstown UFB2 - Wanaka/Lake Hawea UFB2 Fringe

WANGANUI Wanganui Non UFB funded build

WANGANUI GIRLS Wanganui Non UFB funded build

WARKWORTH Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Warkworth




WARKWORTH Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Warkworth UFB2 Fringe

WASHDYKE Timaru UFB1 - Timaru

WAVERLEY New Plymouth UFB2 - Waverley

WELLINGTON Courtney Place / Johnsonville / Porirua / Wellington UFB1 - Wellington

WELLINGTON SOUTH

Courtney Place / Johnsonville / Porirua / Wellington UFB1 - Wellington

WELLSFORD Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Wellsford

WELLSFORD Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Wellsford UFB2 Fringe

WESTPORT Greymouth UFB2 - Carters Beach

WESTPORT Greymouth UFB2 - Westport Urban

WESTPORT Greymouth UFB2 - Westport Urban UFB2 Fringe

WHAKATANE Whakatane UFB1 - Whakatane

WHAKATANE Whakatane UFB2 - Ohope/Coastlands

WHAKATANE Whakatane UFB2 - Ohope/Coastlands UFB2 Fringe

WHANGAEHU Fielding / Palmerston North UFB2 - Ratana/Whangaehu

WHANGAMATA Tauranga / Otumoetai UFB2 - Whangamata

WHANGAMATA Tauranga / Otumoetai UFB2 - Whangamata UFB2 Fringe

WHANGAREI Whangarei / Kensington Non UFB funded build

WHATAROA Greymouth UFB2 - Whataroa

WHATAWHATA Hamilton / Frankton UFB2 - Whatawhata UFB2 Fringe

WHENUAKITE Tauranga / Otumoetai UFB2 - Hahei

WHENUAPAI Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB1 - Auckland

WHENUAPAI Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Brigham Creek Rd

WHENUAPAI Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Brigham Creek Rd UFB2 Fringe

WHENUAPAI Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Fred Taylor Rd

WHENUAPAI Glenfield / Forrest Hill / Massey / Mayoral Drive / Mt Eden / Ponsonby UFB2 - Fred Taylor Rd UFB2 Fringe

WHITBY Courtney Place / Johnsonville / Porirua / Wellington UFB1 - Wellington

WHITIANGA Tauranga / Otumoetai UFB2 - Ferry Landing/Cooks Beach

WHITIANGA Tauranga / Otumoetai UFB2 - Kuaotunu

WHITIANGA Tauranga / Otumoetai UFB2 - Matarangi

WHITIANGA Tauranga / Otumoetai UFB2 - Whitianga

WHITIANGA Tauranga / Otumoetai UFB2 - Whitianga UFB2 Fringe

WINTON Invercargill / Waikiwi UFB2 - Winton

WINTON Invercargill / Waikiwi UFB2 - Winton UFB2 Fringe

WOODEND Christchurch UFB2 - Christchurch - Woodend




WOODEND Christchurch UFB2 - Christchurch - Woodend UFB2 Fringe

WOODEND Christchurch UFB2 - Waikuku Beach

WOODEND Christchurch UFB2 - Waikuku Beach UFB2 Fringe

WOODVILLE Fielding / Palmerston North UFB2 - Woodville

WOODVILLE Fielding / Palmerston North UFB2 - Woodville UFB2 Fringe

WYNDHAM Invercargill / Waikiwi UFB2 - Wyndham

operations manual for bitstream services reference offer

Documents