ANNEX A

PLANNING AND OPErations

CONTENTS

A1	Definitions
A2	General
A3	Network Information
A4	Location of Switch Connections
A5	Routing Principles
A6	ISI Interconnect Link Architecture
A7	Capacity Provision
A8	Traffic Forecasts
A9	Capacity Profiles and ACOs
A10	Capacity Orders and Testing
A11	Capacity Order Timescales
A12	Numbering
A13	Technical Review Meetings
A14	Switch Testing
A15	Transmission and Signalling
A16	Performance Standards
A17	Operations
A18	Services

Appendices

A	BT/Operator Network Information
B	Commercial
C	Data Management Amendments
D	Responsibilities for Traffic Types
E	STP (Signal Transfer Point) Working

1.	DEFINITIONS

1.1	In this Annex, the Appendices and tables, a reference to a paragraph or Appendix, unless stated otherwise, is to a paragraph or appendix of this Annex. Words, abbreviations and expressions have the meanings given in Annex D.

2.	GENERAL

2.1	This Annex details the planning and operational principles for conveying Calls between the BT System and the Operator System and provides the technical basis for the Specifications and for the Manuals. The Specifications define the characteristics of the interface between the BT System and the Operator System. The Manuals provide procedures for the provision and re-arrangement of Capacity (Provisioning Manual), testing (Operational Testing Manuals) and operations and maintenance (Operations and Maintenance Manual).

2.2	This Annex contains provisions on the planning and operation of services provided under this Agreement. The details of the interconnect between the Parties’ Systems and the plans for future developments relating to interconnect shall be recorded in the Technical Master Plan. The Customer Service Plan shall contain details of the points of contact within the Operator’s and BT’s organisation. The Parties shall endeavour to keep these documents up to date.

2.3	If there is a written form for the exchange of information between the Parties pursuant to Annex A, such information shall be exchanged in electronic form.

3.	NETWORK INFORMATION

3.1	Insofar as not previously provided, each Party shall provide to the other the information listed in Appendix A as soon as reasonably practicable and in any event not more than 20 Working Days from the date of this Agreement. Thereafter, such information shall be published quarterly by each Party and, wherever reasonably practicable, such publication shall be co-ordinated with the publication of other directly related information. Each Party shall take reasonable endeavours to ensure the accuracy of the information listed in Appendix A.

3.2	In addition to the requirements set out in paragraph 4 of the main body of this Agreement, each Party will provide to the other information on any proposed introduction, closure, replacement or modification to any Switch referred to in paragraph 3.1 and where relevant, adjustments to the Number Ranges supported by such Switches as soon as practicable and, in any event, at not less than 4 months prior to the implementation.

3.3	Each Party will provide to the other, on request, information on the availability (or otherwise) of sufficient transmission capacity at any BT or Operator building for establishing IECs from that location.

3.4	In connection with the BT programme for national implementation of the BT Next Generation Network, BT is progressively withdrawing BT DLEs, and therefore increasingly Network Termination Points will be connected to the BT Next Generation Network.  (For the purposes of this paragraph 3.4, BT Next Generation Network shall mean replacement IP technology network elements within the BT System). Where such connection has taken place:

3.4.1 	Calls handed over by the Operator to BT at a BT Tandem Exchange which is an NGS, for termination, shall be delivered to the BT Network Termination Point via the BT Next Generation Network. If Calls are handed over to BT at a BT Tandem Exchange other than an NGS, such Calls shall be conveyed by such BT Tandem Exchange to an NGS, and then be delivered to the BT Network Termination Point via the BT Next Generation Network;

3.4.2   	Calls originating on a Network Termination Point on the BT System and destined for the Operator System, shall be conveyed via the BT Next Generation Network before handover to the Operator System at or via an NGS.

4.	LOCATION OF SWITCH CONNECTIONS

4.1	BT Switch Connections

4.1.1	The Operator shall nominate by written notice to BT, the BT Switch Connections at the following BT Exchanges identified in accordance with paragraph 3.1 (where the Operator wishes to handover Calls from the Operator System to the BT System):

(a)	Any BT Tandem Exchange;

(b)	Any BT DLE;

(c)	Any BT ISC.

4.1.2	BT shall nominate by written notice to the Operator, BT Switch Connections where BT wishes to handover Calls (for which BT has responsibility in accordance with paragraph 5.1.3) from the BT System to the Operator System.

4.1.3	The Operator shall nominate by written notice to BT, BT Switch Connections where the Operator wishes Calls (for which the Operator has responsibility pursuant to paragraph 5.1.3) to be handed over from the BT System to the Operator System.

4.2	Operator Switch Connections

4.2.1	BT shall nominate by written notice to the Operator, Operator Switch Connections at an Operator Exchange identified in accordance with paragraph 3.1 at which BT wishes to handover Calls from the BT System to the Operator System.

4.2.2	The Operator shall nominate by written notice to BT, Operator Switch Connections at which the Operator wishes to handover Calls (for which the Operator has responsibility in accordance with paragraph 5.1.3) from the Operator System to the BT System.

4.2.3	BT shall nominate by written notice to the Operator, Operator Switch Connections where BT wishes Calls (for which BT has responsibility pursuant to paragraph 5.1.3) to be handed over from the Operator System to the BT System.

4.3	Agreement of Switch Connections

4.3.1	The Parties shall endeavour to agree which Switch Connections shall be used for the conveyance of Calls between the Parties.  In the event that agreement cannot be reached either Party may notify the other in writing of a Dispute

5.	ROUTING PRINCIPLES

5.1	Responsibilities

5.1.1	Each Party shall route the other Party’s traffic in accordance with the following routing principles:

(a)	routing within a Party's System shall be equivalent to the routing of similar types of traffic for the generality of such Party's Customers including alternative routing where appropriate;

(b)	insofar as practicable routing shall avoid analogue routing within a Party's own System. The Parties acknowledge that some International Calls and Calls to or from a Third Party's system may involve analogue routing.

5.1.2	The Parties shall develop and apply network traffic management strategies and procedures to maintain customer service quality and to protect the Parties' Systems as are appropriate. Full details of the network traffic management provisions are set out in the Operations and Maintenance Manual. These shall include:

(a)	designation of specific Traffic Routes to restore service if a route loss occurs;

(b)	establishment of overflow procedures if there is route congestion;

(c)	establishment of special procedures for busy circuits enabling either diversion of a Call to a different routing or diversion to an agreed tone or message.

5.1.3	The responsibilities for Traffic Types are set out in Table A in Appendix D. The responsibilities include choice of Switch Connections, provision of Traffic Forecasts, provision of Capacity Profiles and placing of Capacity Orders.

5.1.4	Each Party shall ensure that a Route Type is provided on each Interconnect Link for the conveyance of Traffic Types for which that Party has responsibility in accordance with paragraph 5.1.3. Where a Party wishes to segregate its traffic into different Traffic Types it may order additional Route Types in accordance with Schedule 01 or 130 as appropriate. Where a Traffic Route is used for the conveyance of Calls for both Parties in accordance with the provisions of paragraph 5.2.12(2), a single Route Type may be used.

5.2	Interconnect Traffic Route Structure

5.2.1	Subject to the provisions of paragraph  5.2.3, 5.2.4, 5.2.8 and 5.2.10 the Parties shall establish Interconnect Links to convey Calls between the BT System and the Operator System on Traffic Routes between each Operator Switch Connection and at least one BT DMSU.   

5.2.2	NOT USED 
5.2.3	If the Operator delivers traffic to a BT Switch Connection at:

(a)	a single BT DMSU; or

(b)	a BT DMSU and a single BT DJSU;

and if BT chooses to deliver traffic from more than one BT Switch Connection to the Operator System, then the relevant Interconnect Link shall be for BT's exclusive use and provided at BT's expense.

5.2.4	If the Operator wishes to provide Traffic Routes to more than one BT DJSU, the Parties shall agree the combination of BT DJSUs and the Traffic Streams to be routed through them. Under normal operations alternative routing of traffic between the Traffic Routes described in paragraph 5.2.1 will not be available.

5.2.5	A BT WAT is available for the delivery or collection of Calls to or from Number Ranges served by BT DLEs directly connected to that BT WAT and also to certain specified DMSUs and DJSUs.

5.2.6	A BT DLTE is available for the delivery or collection of Calls to or from Number Ranges served by that BT DLTE and by BT DLEs directly connected to that BT DLTE, except for Operator Groomed IP Network Calls, Operator Groomed Non-Geographic Calls, and Operator IP Network Calls. Operator Groomed IP Network Calls, Operator Groomed Non-Geographic Calls, Operator IP Network Calls and any Calls to access the internet where no time related charges are levied directly or indirectly on a pence per minute basis by any Party (“Calls that are unmetered to the Caller”) are available only from those Calling Parties directly connected to a BT DLE. Such Calls shall not be transited via a BT DLTE.

5.2.7	A BT DLE is available solely for the delivery or collection of Calls to or from the Number Ranges served by that BT DLE.

5.2.8	Subject to the provisions of paragraphs 5.2.6 and 5.2.7, where an Operator has at least one connection to a BT DMSU, and the Operator’s Switch Connections are connected via the Operator’s System, the Operator Switch Connection may connect to a BT DLE or DLTE only.

5.2.9	The Operator may choose to deliver International Calls (excluding those to Republic of Ireland) to the BT System to one or more BT ISC.

5.2.10	Notwithstanding the provisions of paragraph 5.2.1 if the Operator wishes to deliver only International Calls to the BT System (for conveyance to Authorised Overseas Systems other than the Republic of Ireland) the Operator may choose to deliver International Calls to one or more BT ISCs only.

5.2.11	If the Parties fail to agree the BT Tandem Exchanges or the BT ISC referred to in this paragraph 5.2 then either Party may notify the other in writing of a Dispute.

5.2.12	Interconnect Links shall have Traffic Routes such that:

(1)	for ISI, Traffic Routes shall be established to convey only those Traffic Types for which a Party has responsibility in accordance with paragraph 5.1.3; and

(2)	for Customer Sited Interconnect, Traffic Routes shall be established, either:

a)	in accordance with the provisions for ISI set out in (1) above; or

b)	for all Traffic Types.

5.2.13	Traffic Routes shall be supported by not less than one Signalling Link Set, except that: 

a) 	where Traffic Routes are to more than one BT ISC a Signalling Link Set may be split between the BT ISCs; or 

b) 	where the Traffic Route is for the conveyance of only traffic for which the Operator has responsibility, pursuant to paragraph 5.1.3, to a BT DLE and that Traffic Route consists of no more than ten 2Mbit/s Interconnect Links, a Single Signalling Link may be employed. Additionally, where requested by the Operator, STP working as specified by BT from time to time in Appendix E and the Provisioning Manual may be used to enable DLE connection; or 

c) 	where the Traffic Route is for the delivery of Non Geographic Call Services or IP Network Calls for which the Operator has responsibility, pursuant to paragraph 5.1.3, from a BT DLE and that Traffic Route consists of no more than ten 2 Mbit/s Interconnect Links, a Single Signalling Link may be employed. Additionally, where requested by the Operator, STP working as specified by BT from time to time in Appendix E and the Provisioning Manual may be used to enable DLE connection; or

d)	where the Traffic Route is for interconnection between NGS type BT DMSUs and Operator Next Generation Networks (for the purposes of this paragraph 5.2.13(d), Operator Next Generation Network shall mean replacement IP technology network elements within the Operator System), where requested by the Operator, STP working as specified by BT from time to time in Appendix E and the Provisioning Manual may be used to enable such connection.

If a Party intends to use a Single Signalling Link it shall, unless otherwise agreed, give the other Party 25 Working Days notice prior to implementation.

	A Signalling Link Set may be used to support:

i)	up to 64 x 2 Mbit/s Interconnect Links where such Signalling Link Set is comprised of two Signalling Links, having Traffic Routes for which a Party has responsibility pursuant to paragraph 5.1.3; or

ii)	up to 128 x 2 Mbit/s Interconnect Links where such Signalling Link Set is comprised of four Signalling Links, having Traffic Routes for which a Party has responsibility pursuant to paragraph 5.1.3; or

iii)	up to 128 x 2 Mbit/s Interconnect Links where such Signalling Link Set is comprised of two Signalling Links and the average link set loading does not exceed 20%, having Traffic Routes for which a Party has responsibility pursuant to paragraph 5.1.3; or

iv)	where the Signalling Link capability of equipment in either Party’s System or the signalling message profile resulting from the type of traffic associated with the Traffic Route supported by the Signalling Link Set is such that the number of Signalling Links specified in i) or ii) above are not capable of supporting the number of 2 Mbit/s Interconnect Links specified, then the Parties shall agree in writing the number of 2 Mbit/s Interconnect Links that may be supported by each pair of Signalling Links within the Signalling Link Set. If the Parties fail to agree the number of 2 Mbit/s Interconnect Links that may be supported by each pair of Signalling Links within the Signalling Link Set then either Party may notify the other Party in writing of a Dispute.

5.2.14	The Party whose Switch Connection conveys the relevant Calls to the other's System shall assign Traffic Streams (identified by destination) to a particular Traffic Route. BT and the Operator shall, subject to paragraph 5.4 below, advise each other which Traffic Streams are assigned to which Traffic Route. Unless otherwise agreed, each Party shall use its reasonable endeavours to ensure that traffic is directed in accordance with the advice given to the other. Traffic so routed is primary traffic as described in paragraph 5.4.

5.2.15	Where there is a Traffic Route to or from a Switch Connection and notification has been given by either Party that the relevant Switch Connection is to be removed or Capped, then no additional Capacity shall be provided on that Traffic Route save that agreed in the ACO current on the date when notification was given.

5.2.16	If BT conveys Emergency Calls from the Operator System BT shall allocate the same priority to Emergency Calls handed over from the Operator System as it provides to Emergency Calls from BT Customers.

5.3	Interconnect Traffic Route Dimensioning

5.3.1	Except as described in paragraph 5.3.3.  Traffic Routes shall be Fully Provided to carry only the traffic for which Capacity has been ordered in accordance with this Annex and such Traffic Routes shall be operational at no worse than the required grade of service. For the purposes of satisfying the Fully Provided obligation, if the Operator has multiple Traffic Routes into the Operator System from a BT Switch Connection, the Capacity on such Traffic Routes may be added together for the relevant assessment.

5.3.2	Subject to paragraph 5.3.1, if a Traffic Route is used for the conveyance of traffic for both Parties or for the conveyance of Calls that may utilise an agreed overflow routing to an alternative BT Switch Connection, the forecast requirement of Capacity shall be based upon the route busy hour. The forecasts shall be based upon a proposed grade of service of better than 0.008 subject to the route dimensioning giving a grade of service of better than 0.02 at 10 per cent traffic overload and better than 0.05 at 20 per cent traffic overload, unless the Parties agree otherwise.

5.3.2.1	The relevant grade of service shall mean that a traffic route shall not have a busy hour traffic measurement of greater than 102% of the critical traffic value in accordance with the TC4 traffic tables.

5.3.3	High Usage Traffic Routes to specified BT DLEs and Operator Local Exchanges

(a)	Traffic Routes to BT DLEs and Operator Local Exchanges may be dimensioned as High Usage Traffic Routes, that is to say, the target grade of service may be achieved by traffic being offered as first choice to the BT DLE or Operator Local Exchange, as the case may be, and, if Capacity is not available, as a second choice to the BT DMSU, BT DJSU, BT WAT or BT DLTE used for tandem switching pursuant to paragraph 5.2.6, or Operator Tandem Exchange, as the case may be.

(b)	A High Usage Traffic Route shall have a maximum size of six 2Mbit/s systems and be designed to overflow no more than 15% of the Traffic offered to the High Usage Traffic Route. The Party having responsibility for the Traffic Type, as set out in paragraph 5.1.3, shall take network management action in accordance with paragraph (d) below to limit overflow traffic to the 15% level.

(c)	This specific routing, identified in a) or b) above, encompassing a BT DMSU, BT DJSU, BT WAT or BT DLTE used for tandem switching pursuant to paragraph 5.2.6 and a BT DLE, or an Operator Tandem Exchange and an Operator Local Exchange, as the case may be, constitutes a primary routing.  Traffic shall be offered to only one BT DMSU, BT DJSU, BT WAT or BT DLTE used for tandem switching, or one Operator Tandem Exchange, as the case may be, as a primary routing.

(d)	If a High Usage Traffic Route fails, or a traffic surge causes an increase in traffic being routed to the primary tandem exchange, then in order to restore traffic balance, the Party having responsibility for the Traffic Type, as set out in paragraph 5.1.3, shall undertake immediate action to implement network management controls, agreed with the other Party’s network management organisation, to restrict overflow traffic to the design limits set out in paragraph (b) above or such greater levels as the other Party’s network management organisation considers will not adversely affect that Party’s primary traffic.  These controls shall be implemented within 15 minutes of receipt by the Party having responsibility for the Traffic Type, as set out in paragraph 5.1.3, of notice to that effect, or of the time when the overflow traffic comes to the notice of such Party, whichever is the earlier.

5.4	Interconnect Routing Rules

5.4.1	Operator to BT traffic

	The Operator may convey Traffic Streams in any combination of Fully Provided Traffic Routes, except as detailed in paragraph 5.3.3, from Operator Switch Connections to BT Switch Connections only in accordance with routing plans agreed by the Parties for those Traffic Streams.

	All traffic delivered in accordance with this paragraph shall be considered to be primary traffic

5.4.2	BT to Operator traffic

	BT may convey Traffic Streams in any combination of Fully Provided Traffic Routes, except as detailed in paragraph 5.3.3, from BT Switch Connections to Operator Switch Connections only in accordance with routing plans agreed by the Parties for those Traffic Streams.  

	All traffic delivered in accordance with this paragraph shall be considered to be primary traffic	

5.4.3	Overflow Traffic

Traffic overflowing as part of an agreed routing plan will be deemed to be included in the provisions of paragraphs 5.4.1 and 5.4.2 and shall be considered to be primary traffic.

5.4.3.1	Overflow of BT to Operator Traffic

With the exception of Targeted Transit, this paragraph 5.4.3.1 is applicable to all BT to Operator Traffic where the Operator is responsible for such Traffic Type in accordance with paragraph 5.1.3. The following sub-paragraphs (a) – (c) (inclusive) shall apply.

 (a)	Any provision of an overflow routing by BT shall be subject to the following:

(i)	there is sufficient existing spare capacity for such overflow traffic between the BT Switch Connection from which such overflow routing is to be provided and the destination BT Switch Connection;

(ii)	BT may apply network management controls in the BT System to the Calls using an overflow routing to ensure that the traffic being primarily routed over any route shall not be adversely affected by the overflow traffic that may be routed over such route;

(iii)	Subject to paragraph 5.4.3.2 an overflow facility shall be available to appropriate Number Ranges used for voice traffic, data traffic and mixed voice/data traffic;

(b)	In order to ensure the grade of service of any traffic conveyed on the BT System is not affected by the Operator’s failure to fulfil its obligations under this paragraph 5.4.3:

(i)	if a traffic route is recorded as having a Busy Hour Traffic measurement greater than that specified in paragraph 5.3.2 for any 5 days out of 7 consecutive days, the Operator shall be in breach of its Fully Provided obligations;

(ii)	if the Operator, in relation to a Traffic Route, is notified by BT that the Operator is in breach of its Fully Provided obligation, the Operator shall submit, not later than 5 Working Days after such notification, either:

-	an ACO requesting Route Augmentation; or

 	-	a revised routing plan request to rebalance traffic through routing amendments within the BT tandem layer;

to return the Traffic Route to being Fully Provided;

(iii)	if such ACO or revised routing plan (as the case may be) is agreed by BT, the Operator shall place the relevant Capacity Order(s) or Data Management Amendment not later than 5 Working Days after the date of such agreement by BT;

(iv)	if the Operator fails to submit such ACO requesting Route Augmentation or revised routing plan under paragraph 5.4.3.1 (b) (ii) or the Operator fails to submit the relevant Capacity Order or Data Management Amendment under paragraph 5.4.3.1 (b) (iii), BT may forthwith withdraw the overflow routing(s) at the relevant BT Switch Connection;

(v)	if BT has commenced removal of an overflow routing under paragraph 5.4.3.1 (b) (iv), BT shall not be required to re-provide an overflow routing until the relevant Traffic Route has returned to the position of being Fully Provided. To ensure that the relevant Traffic Route does not immediately return to being in breach of the Fully Provided obligation, the Route Busy Hour Traffic measurement shall be recorded over a 7 consecutive day period to ensure such measurement is less than 80% of the critical traffic value in accordance with the TC4 traffic tables before re-provision of an overflow routing is instigated. Subject to paragraph 5.4.3.1 (c) (ii), such re-provision shall be carried out in accordance with Appendix B.

(c)	If the Operator fails to Fully Provide the relevant Traffic Routes, the Operator shall pay to BT:

(i)	the reimbursement of BT’s reasonable costs for any associated monitoring of the relevant Traffic Routes; and

(ii)	the relevant charges specified from time to time in the Carrier Price List for the removal and re-provision of any overflow routing(s) pursuant to paragraph 5.4.3.1 (b) (v).

5.4.3.2	Overflow Traffic from BT DLEs

	Subject to paragraph 5.3.1:

(a)	If requested by the Operator and where the Number Range, CPS Routing Prefix or Access Code concerned is for voice traffic, data traffic and mixed voice/data traffic, BT shall provide overflow facilities from the BT DLE to the Operator System via the BT tandem layer in accordance with an agreed routing plan. 

(b)	The overflow facilities shall apply to services within a specified Number Range as allocated by Ofcom to the Operator, and not to the generality of Traffic Streams on a specified route. 

5.4.4	Other Traffic

	Traffic that is delivered other than as detailed in paragraphs 5.4.1, 5.4.2 and 5.4.3 may be given a lower priority than primary traffic and should only be delivered after agreement by the parties in accordance with the provisions of the Operations and Maintenance Manual.

5.4.5	BT-Operator Indirect Access Traffic, BT-Operator Carrier Pre-Selection Traffic, 118 Directory Enquiry Service Traffic and 116 European Helpline Service Traffic.

5.4.5.1	BT-Operator Indirect Access Traffic and BT-Operator Carrier Pre-Selection Traffic

(a)	If the Parties have agreed in a Schedule to convey Indirect Access Calls and/or Carrier Pre-Selection Calls, the Operator shall nominate a BT Switch Connection to receive Indirect Access Calls and/or Carrier Pre-Selection Calls from each BT Tandem Exchange where applicable compliant with the technical principles contained in the Generic Transmission Interface Specification.

(b)	For Indirect Access Calls and/or Carrier Pre-Selection Calls originating on the BT System, BT shall arrange not less than one alternative path from the originating BT DLE to the BT Switch Connection, unless only one path is requested in writing by the Operator.

(c)	For Indirect Access Calls and/or Carrier Pre-Selection Calls received at a BT Switch Connection and on the Operator's written request, BT shall arrange not less than one alternative path to be provided to the Operator System. Except where overflow routing is requested by the Operator in accordance with paragraph 5.4.3.1, routing from the nominated BT Switch Connection to the Operator System shall be limited to Traffic Routes from that BT Switch Connection.

	Where proportional distribution is 	used to facilitate such routing it shall contain routings to access up to a maximum of six Traffic Routes that are connected to the BT Switch Connection, utilising a maximum of three routing tables.

5.4.5.2	BT-Operator 118 Directory Enquiry Service Traffic

(a)	If the Parties have agreed in a Schedule to convey 118 Directory Enquiry Service Calls, the Operator shall nominate a BT Switch Connection to receive 118 Directory Enquiry Service Calls from each BT Tandem Exchange where applicable compliant with the technical principles contained in the Generic Transmission Interface Specification.

(b)	For 118 Directory Enquiry Service Calls originating on the BT System, BT shall arrange not less than one alternative path from the originating BT DLE to the BT Switch Connection, unless only one path is requested in writing by the Operator.

(c)	For 118 Directory Enquiry Service Calls received at a BT Switch Connection and on the Operator's written request, BT shall arrange not less than one alternative path to be provided to the Operator System. Except where overflow routing is requested by the Operator in accordance with paragraph 5.4.3.1, routing from the nominated BT Switch Connection to the Operator System shall be limited to Traffic Routes from that BT Switch Connection.

	Where proportional distribution is used to facilitate such routing it shall contain routings to access up to a maximum of six Traffic Routes that are connected to the BT Switch Connection, utilising a maximum of three routing tables.

5.4.5.3	Operator to BT 118 Directory Enquiry Service Traffic

The Operator shall convey Calls for BT Directory Enquiry Services to a BT DMSU Switch Connection which is as near as reasonably practical to the origination of the Call, having regard to any requirements necessary to identify the intended destination, or as otherwise may be agreed in writing by the Parties.

5.4.5.4	BT-Operator 116 European Helpline Service Traffic

(a)	If the Parties have agreed in a Schedule to convey 116 European Helpline Service Calls, the Operator shall nominate a BT Switch Connection to receive 116 European Helpline Service Calls from each BT Tandem Exchange where applicable compliant with the technical principles contained in the Generic Transmission Interface Specification.

(b)	For 116 European Helpline Service Calls originating on the BT System, BT shall arrange not less than one alternative path from the originating BT DLE to the BT Switch Connection, unless only one path is requested in writing by the Operator.

(c)	For 116 European Helpline Service Calls received at a BT Switch Connection and on the Operator's written request, BT shall arrange not less than one alternative path to be provided to the Operator System. Except where overflow routing is requested by the Operator in accordance with paragraph 5.4.3.1, routing from the nominated BT Switch Connection to the Operator System shall be limited to Traffic Routes from that BT Switch Connection.

	Where proportional distribution is used to facilitate such routing it shall contain routings to access up to a maximum of six Traffic Routes that are connected to the BT Switch Connection, utilising a maximum of three routing tables.

5.4.5.5	Operator to BT 116 European Helpline Service Traffic

The Operator shall convey Calls for 116 European Helpline Services to a BT DMSU Switch Connection which is as near as reasonably practical to the origination of the Call, having regard to any requirements necessary to identify the intended destination, or as otherwise may be agreed in writing by the Parties.

5.4.6	Non Geographic Call Services Traffic

5.4.6.1	Operator to BT Non Geographic Call Services Traffic

The Operator shall convey Calls for BT Non Geographic Call Services to a BT DMSU Switch Connection which is as near as reasonably practical to the origination of the Call, having regard to any requirements necessary to identify the intended destination, or as otherwise may be agreed in writing by the Parties.

5.4.6.2	BT to Operator Non Geographic Call Services Traffic

(a)	If the Parties have agreed in a Schedule to convey BT to Operator Non Geographic Call Services Calls, the Operator shall nominate a BT Switch Connection to receive Non Geographic Call Services Calls from each BT Tandem Exchange where applicable compliant with the technical principles contained in the Generic Transmission Interface Specification.

(b)	For Non Geographic Call Services Calls originating on the BT System and Non Geographic Call Services Calls transiting the BT System for termination on the Operator System, BT shall arrange not less than one alternative path from the originating BT DLE or other BT Exchange, where such calls are transiting the BT System, to the BT Switch Connection, unless only one path is requested in writing by the Operator.

(c)	For Non Geographic Call Services Calls received at a BT Switch Connection and on the Operator's written request, BT shall arrange not less than one alternative path to be provided to the Operator System. Except where overflow routing is requested by the Operator in accordance with paragraph 5.4.3.1, routing from the nominated BT Switch Connection to the Operator System shall be limited to Traffic Routes from that BT Switch Connection.

	Where proportional distribution is used to facilitate such routing it shall contain routings to access up to a maximum of six Traffic Routes that are connected to the BT Switch Connection, utilising a maximum of three routing tables.

5.4.7	BT to Operator Groomed IP Network Traffic, Groomed Non-Geographic Traffic and IP Network Traffic

(a)	If the Parties have agreed in a Schedule to convey Groomed IP Network Calls and/or Groomed Non-Geographic Calls and/or IP Network Calls, BT shall nominate Operator Switch Connections to receive Groomed IP Network Calls and/or Groomed Non-Geographic Calls and/or IP Network Calls (as appropriate) from each BT Switch Connection where applicable compliant with the technical principles contained in the Generic Transmission Interface Specification.

(b)	For Groomed IP Network Calls and/or Groomed Non-Geographic Calls and/or IP Network Calls received at a BT Switch Connection and on the Operator’s written request, BT shall arrange not less than one alternative path to be provided to the Operator System. Except where overflow routing is requested by the Operator in accordance with paragraph 5.4.3.1, routing from the nominated BT Switch Connection to the Operator System shall be limited to Traffic Routes from that BT Switch Connection.

Where proportional distribution is used to facilitate such routing it shall contain routings to access up to a maximum of six Traffic Routes that are connected to the BT Switch Connection utilising a maximum of three routing tables.

(c)	The aggregated Capacity for the conveyance of such Calls together with the Capacity provided for the conveyance of Non Geographic Call Services Calls and Calls pursuant to paragraph 5.4.9 at a BT Switch Connection shall be subject to normal capacity restrictions.

5.5	Interconnect Route Diversity and Security

5.5.1	Where either Party requests physical route diversity it shall take account of the Signalling Links and the Traffic Routes.

5.5.2	The Traffic Route(s) between an Operator Switch Connection and the relevant BT Switch Connection shall, subject to the normal planning practices of the relevant Party, ensure that a single failure of equipment does not give rise to failure of a Traffic Route.

5.6	Routing of International Traffic

5.6.1	The Operator may handover International Calls to the BT System at BT DMSUs or BT ISCs.  If an Operator chooses to handover International Calls direct to an ISC and has Interconnect Links to more than one BT ISC, BT shall provide the Operator with an appropriate ISC routing plan for each international destination and the Operator shall so route its International Calls.

5.6.2	If agreed, or for Number Ranges allocated to the Operator for the provision of Mobile Calls for a digital service (GSM, PCN, UMTS) Calls can be routed via BT using the following methods: 

i)	Calls may be handed over to the Operator System from a BT Interconnect Link connected to a BT ISC being a BT ISC of BT’s choice;

ii)	In exceptional circumstances, such as circuit failure, or where a Fully Provided Traffic Route experiences a short term (i.e. not more than one month) of abnormal load and subject to sufficient network capacity, the overload traffic may be routed via the BT DMSU to the Operator System.

Calls from an international destination to other Number Ranges assigned to the Operator shall be routed by BT from the Interconnect Link that BT provides to the BT ISC to the relevant BT DMSU to be handed over to the Operator System.

5.6.3	BT Basic International Outgoing Calls for conveyance to the Republic of Ireland shall be handed over to BT at a BT DMSU, unless such Calls originate in Northern Ireland and are switched only by Switches in Northern Ireland, when such Calls may be handed over to BT at designated BT Tandem Exchanges located in Northern Ireland.  BT ISDN International Outgoing Calls for conveyance to the Republic of Ireland may be handed over to BT at a BT ISC.

5.7	Record of Arrangements

The Parties shall record the physical arrangements and Number Ranges, or part thereof, for each of the Traffic Routes on an Interconnect Link. Information shall be provided in accordance with the Provisioning Manual and a record of these arrangements shall be maintained in the Technical Master Plan.

6.	ISI INTERCONNECT LINK ARCHITECTURE

ISI Interconnect Links shall be transmission systems using either PDH or SDH technology, in accordance with the interfaces set out in the Generic Electrical and Physical Interface Specification and, in the case of SDH, additionally in the Generic SDH Interface Specification.

6.1	ISI Interconnect Links using PDH

(a)	Equipment

The manufacturer and type of equipment used to terminate the ISI Interconnect Link shall be the same at each end of the fibre and be one of those agreed and listed in the Provisioning Manual.

(b)	Procedures

Operational procedures for the provision of PDH ISI Interconnect Links are described in the Provisioning Manual and their maintenance is described in the Operations and Maintenance Manual.

(c)	IECs

Interconnect Extension Circuits may be used to complete ISI Interconnect Links to Remote Switch Connections.

(d)	Path Protection

Where the Operator requests Path Protection using PDH, as set out in Schedule 01, the manufacturer and type of equipment used to effect the Path Protection shall be the same at each end of the fibre and be one of those agreed and listed in the Provisioning Manual as suitable for supporting Path Protection.

6.2	ISI Interconnect Links using SDH

(a)	Configuration

ISI Interconnect Links using SDH technology will deliver the equivalent functionality to an ISI Interconnect Link using PDH technology.

For the avoidance of doubt if an ISI Interconnect Link uses SDH technology all traffic within the BT System flowing to or from the STM-1 or STM-4 SDH Add-Drop Multiplexor will be carried by Intrabuilding Links or IECs and there shall, unless the Operator has requested Path Protection, be one single physical path between the STM-1 or STM-4 SDH Add-Drop Multiplexors.

Where such ISI Interconnect Link is provided via a PPC ISH Link with ISH Facility Mux the connection between the STM-n SDH Add-Drop Multiplexors shall be in accordance with the BT PPC Standard Handover Agreement.

(b)	Equipment

The manufacturer and type of equipment that BT shall use to terminate the SDH ISI Interconnect Link shall be one of those listed in the Provisioning Manual. Subject to successful compatibility testing between each Party’s equipment, the Operator may use any equipment that conforms to the Generic SDH Interface Specification and is of the same line rate as that used by BT.

Where such ISI Interconnect Link is provided via a PPC ISH Link with ISH Facility Mux the manufacturer and type of equipment that BT shall use conforms to the Generic SDH Interface Specification;  the Operator may use any equipment that conforms to the Generic SDH Interface Specification and is of the same line rate as that used by BT.

(c)	Management

Neither Party shall exercise management control of the other Party’s STM-1 or STM-4 SDH Add-Drop Multiplexor. In particular, the transmission messages to the other Party via the Data Communications Channel (DCC) in the Add-Drop Multiplexor section overhead shall be inhibited.

(d)	Testing and Operational Procedures

If the Operator chooses to use equipment that has not been validated to ensure that it interworks with the equipment that BT uses, the Parties shall test the equipment to ensure that the performance standards are met. Unless otherwise agreed such testing shall be completed before an order for such an Interconnect Link is placed. If the Parties agree to carry out the testing after an order is received that order shall be subject to adjustment of the delivery date to include such tests. Operational procedures for the provision of SDH Interconnect Links are described in the Provisioning Manual and their maintenance is described in the Operations and Maintenance Manual.

(e)	IECs

Interconnect Extension Circuits shall be provided using PDH or SDH at the suppliers election solely for the completion of ISI Interconnect Links to Remote Switch Connections.

(f)	Path Protection 

If the Operator requests Path Protection, all VC paths shall terminate on a single Add-drop Multiplexor at the BT Switch Connection. This configuration shall be used where VC Path Protection is deployed in the SDH equipment terminating the VC paths.

Where such ISI Interconnect Link is provided via a PPC ISH Link with ISH Facility Mux the Path Protection shall be in accordance with the PPC Standard Handover Agreement. For the avoidance of doubt, such Path Protection shall be provided using Multiplexor Section Protection (MSP) between BT PPC Add-Drop Multiplexor and the Operator PPC Add-Drop Multiplexor.

7.	CAPACITY PROVISION

7.1	Initial Interconnection

Prior to the first Capacity Order being placed under this Agreement:

7.1.1	the Operator shall provide BT with the following information:

(1)	details about the proposed Operator Exchange or Exchanges, software build level and of the relevant Operator Switch Connections nominated by the Operator;

(2)	details of the relevant BT Switch Connections nominated by the Operator;

(3)	details of the services (as in the Schedules) which the Operator requires on the first Ready for Service Date;

(4)	Number Ranges served by and that may be accessed via the Operator System;

(5)	a statement of the conformity of the Operator System to the Specifications;

(6)	the first Capacity Profile (as described in paragraph 9 below);

(7)	the first Traffic Forecast(s) (as described in paragraph 8 below);

(8)	proposed Traffic Routes, by Number Ranges (in the form set out in the Provisioning Manual);

(9)	details of proposed Points of Connection and Interconnect Links;

7.1.2	BT shall provide the Operator with the following information:

(1)	proposed signalling and testing requirements within the time scale set out in paragraph 14.2 below;

(2)	details of the relevant Operator Switch Connections and BT Switch Connections nominated by BT (if any), within 20 Working Days of a written request by the Operator;

(3)	proposed Traffic Routes by Number Ranges if the Operator is planning to use more than one Operator Switch Connection at the first Ready for Test Date, within 20 Working Days of a written request by the Operator.

7.1.3	The information specified in paragraphs 7.1.1 and 7.1.2 above shall be exchanged in the manner detailed from time to time in the Provisioning Manual.  The Parties shall hold such meetings as are required for this exchange of information.

7.2	Where the Operator is seeking an initial interconnection to the BT System to transfer traffic generated by an established customer, the Operator shall provide BT not less than 20 Working Days prior to the first planning meeting referred to in paragraph 7.1.3 above with the following information:

(1)	traffic volumes from the Operator System to the BT System for each proposed BT Switch Connection;

(2)	traffic volumes from the BT System to the Operator System for each proposed BT Switch Connection; and

(3)	specific requirements for the transfer of the Operator's existing Number Ranges.

8.	TRAFFIC FORECASTS

8.1	General

Traffic Forecasts shall be used by the Parties for planning sufficient switch and distributive network capacity to meet subsequent Capacity Order requirements. While the Parties shall use reasonable endeavours to provide accurate Traffic Forecasts, they shall not be legally binding except to the extent stated otherwise in this Agreement.

8.2	Traffic Forecast Content

8.2.1	Traffic Forecasts for each BT Switch Connection shall be prepared by the Operator for the Traffic Types listed in Table A of this Annex for which the Operator is stated to have the responsibility as defined in paragraph 5.1.3.

In addition the Operator shall prepare Traffic Forecasts for each Operator Switch Connection for the specific Traffic Types listed in Table A for which BT is stated to have the responsibilities as defined in paragraph 5.1.3. However if requested by the Operator, BT shall forecast this traffic when it is mature, that is when the Parties agree that the conditions set out in the Provisioning Manual have been met.

All Traffic Forecasts shall be in the form set out in the Provisioning Manual.

8.2.2	Where a BT ISC is used as a BT Switch Connection, Traffic Forecasts shall define the following:

(a)	outgoing traffic by destination country where the busy hour traffic is expected to exceed 5 Erlangs;

(b)	the total outgoing traffic for all countries where the busy hour traffic is less than 5 Erlangs.

8.2.3	The Parties shall endeavour to agree for each Traffic Route immediately following the first anniversary of the Ready for Service Date of that Traffic Route, and at any time thereafter, whether such Traffic Route is mature, according to the conditions set out in the Provisioning Manual. If the Parties fail to agree whether a Traffic Route is mature then either Party may notify the other in writing of a Dispute.

8.3	Forecasting Periods

8.3.1	Traffic Forecasts shall be on a rolling basis for a period of one year.

8.3.2	A Traffic Forecast provided by the Operator to BT at yearly intervals for each Switch Connection pursuant to paragraph 8.2 shall be made available at least 15 Working Days before the Technical Review Meeting immediately before the Traffic Forecast period next following. These Traffic Forecasts shall (subject as provided below) cover the following one year and shall comprise a year end forecast for this period.

8.3.3	For each mature Traffic Route (as defined in paragraph 8.2), BT shall supply the Operator with the Traffic Forecasts at yearly intervals, not less than 15 Working Days before the Technical Review Meeting immediately prior to the period which is the subject of the Traffic Forecast. These Traffic Forecasts shall cover the following one year and shall comprise a year end forecast for this period.

8.3.4	If either Party's Traffic Forecast for a category of traffic for any twelve month period at any Switch Connection has changed 10 per cent. or more since the last Traffic Forecast or where any additional Switch Connection is proposed by such Party during the next twelve months, then the changed Traffic Forecast shall be notified not later than the next Technical Review Meeting following such change or adoption of such proposal.

8.4	Traffic Forecast Information

8.4.1	Traffic Forecasts supplied pursuant to paragraph 8.3 shall:

(a)	be in terms of day and evening busy hour Erlangs. The day busy hour shall be within the period 0800 to 1800 hours and the evening busy hour shall be within the period 1800 to 0800 hours except where agreed otherwise;

(b)	identify the time of the busy hour for a Traffic Route to be configured pursuant to paragraph 8.1;

(c)	be in the form set out in the Provisioning Manual 

(d)	be authorised and signed at an appropriate level by the originating Party and acknowledged by the receiving Party.

8.5	Forecasting Evolution

8.5.1	The Parties may agree to modify the procedures in this paragraph 8 if and when additional Traffic Routes and/or Traffic Streams are identified or if presently planned Traffic Routes are subdivided.

8.5.2	The forecasting procedures shall be reviewed at the Technical Review Meeting to discuss routing and forecasting matters and to agree changes and appropriate timings for their implementation.

9.	CAPACITY PROFILES AND ACOS

9.1	Before placing Capacity Orders, the Operator shall (subject to paragraph 9.2 below) supply BT with Capacity Profiles in relation to Capacity Provision and Capacity Re-arrangement at all existing and proposed Switch Connections and separately Capacity requirements for PCPOC for existing and proposed Points of Connection. In paragraphs 9 and 10 and subject to paragraph 11.4, Capacity Re-arrangement may only be initiated by the Purchaser of the Capacity which is being rearranged. Each Capacity Profile shall encompass all the Operator's requirements for Capacity and shall be identified for each relevant Switch Connection. The obligation of the Operator under this paragraph in relation to a particular Switch Connection shall cease when the information is provided by BT under paragraph 9.2.

9.2	With effect from the second anniversary of the Ready for Service Date (or such later date as the Parties may agree pursuant to paragraph 8.2.3) for each Switch Connection, BT shall supply the Operator with a Capacity Profile for Traffic Types for which BT has responsibility pursuant to paragraph 5.1.3. The Capacity Profile shall encompass all Capacity Provision or Capacity Re-arrangement requirements and be categorised for each relevant Operator Switch Connection. The Parties acknowledge that each BT Capacity Profile shall reflect the information contained in the relevant Traffic Forecast provided under paragraph 8, plus any other relevant additional information that the Operator has provided to BT (which shall include any necessary advice on the timing of Capacity Provision).

9.3	Capacity Profiles for Capacity Provision and Capacity Re-arrangement shall be provided as described in the Provisioning Manual. The first four months of each Capacity Profile agreed in accordance with paragraph 9.5 shall form an Advance Capacity Profile (ACO) pursuant to paragraph 10.

9.4	Each Capacity Profile shall be presented to the other Party at four month intervals, not less than 15 Working Days before the relevant Technical Review Meeting.

9.5	Each Capacity Profile shall be reviewed at the relevant Technical Review Meeting. Where agreed it will be signed within 5 Working Days by the authorised representatives of each Party to signify their intention to commit to the ACO.

9.6	If the Parties fail to agree a Capacity Profile (or part thereof), then either Party may notify the other in writing of a Dispute.  Only those portions of an ACO that have not been agreed shall be a Dispute. Paragraph 10 shall apply to those parts that have been agreed (and signed by the Parties).

10.	CAPACITY ORDERS AND TESTING

10.1	Capacity Ordering

Subject to the provisions of paragraphs 9 and 10.1.1 to 10.1.6, the Parties shall agree a monthly ordering pattern for Capacity and such Capacity Orders shall be placed in the month designated within the ACO. A maximum variance of 20% per month shown shall be permitted with the appropriate Capacity Order time scale specified in paragraph 11 applying to such Capacity orders. If any Capacity Orders are placed above this level of variance:

a)	the Supplier shall not be obliged to meet the time scales set out in paragraph 11 for that part of the Capacity Order in excess of the relevant limit;

b)	the time scales shall be agreed in writing for the provision of such Capacity and the Ready for Test Dates shall be not later than 6 months after the date of receipt of the relevant Capacity Order;

c)	with regard to paragraphs 10.1.2 and 10.1.5, such Capacity Orders shall be included in the amount of Capacity ordered in the relevant ACO period; and

d)	the Supplier of Capacity in excess of the relevant limit may raise charges to cover additional costs that it may incur arising directly from the provision of Capacity above the level of variance. Neither Party may incur such additional costs or provide such Capacity without the prior written approval of the other.

10.1.1	In an ACO Period the Operator may, in respect of any BT Switch Connection nominated by the Operator (for traffic handed over from the Operator System to the BT System), and, during the period ending two years after the first Ready for Test Date, in respect of any Operator Switch Connection nominated by BT (for traffic handed over from the BT System to the Operator System), place Capacity Orders up to the amount of the aggregate Capacity Provision (i.e. Capacity to be provided plus the provide element of Capacity to be rearranged) shown in the relevant ACOs for each such Switch Connection and place Capacity Orders in respect of PCPOC at the same physical location as the specified Points of Connection shown in the relevant ACO plus the greater of (a) 10 per cent. of such Capacity and (b) 4 x 2Mbit/s units of Capacity , where such Capacity is shown as being greater than zero. Within these limits each Party shall provide such Capacity that it is to provide within the time scales laid down in paragraph 11. Where such Capacity is provided via a PPC ISH or CSH Link with ISH or CSH Facility Mux then such Capacity provision shall be subject to the provision of sufficient capacity within the appropriate PPC ISH or CSH Link within STM-1 tributaries designated for PSTN interconnect use.

10.1.2	In an ACO Period the Operator shall place Capacity Orders for a minimum of 80 per cent. of the aggregate Capacity specified in the relevant ACOs for each Switch Connection and separately for Capacity for PCPOC, for each Point of Connection, other than Capacity required at any Operator Switch Connection for incoming traffic from the BT System. Failure by the Operator to place such Capacity Orders shall result in pre-payment charges being paid by the Operator in accordance with paragraph 1 of Appendix B. Pre-payment charges arising with respect to a specific Switch Connection or, for PCPOC, Point of Connection shall be accepted as pre-payment for future Capacity Orders in respect of Capacity for the same Switch Connection or, for PCPOC, Point of Connection placed within 12 months of the end of the relevant ACO Period (thereby being credited against any charges payable by the Operator in respect of such Capacity Order(s)).

10.1.3	Capacity Orders placed by the Operator (on behalf of BT) for Capacity in respect of Traffic Types for which BT has the responsibility pursuant to paragraph 5.1.3, and any increase in order quantities above those agreed in the relevant ACO (subject to the limits set out in paragraph 10.1.1) shall require written agreement from BT prior to the placing of the relevant Capacity Order. If the Parties fail to agree an increase in a Capacity Order, either Party may notify the other in writing of a Dispute.

10.1.4	Within any ACO Period commencing two years after the Ready for Service Date for a particular Switch Connection, BT may place Capacity Orders for Capacity required at that Operator Switch Connection for Traffic Types for which BT has the responsibility pursuant to paragraph 5.1.3, up to the amount of the aggregate Capacity Provision (i.e. Capacity to be provided, plus the provide element of Capacity to be rearranged) shown in the relevant ACOs for such Operator Switch Connection plus, for any Operator Switch Connection, the greater of (a) 10 per cent. of such Capacity and (b) 4 x 2Mbit/s units of Capacity, where such Capacity is shown as being greater than zero. The Operator shall provide such Capacity within the relevant time scales specified in paragraph 11. Where such Capacity is provided via a PPC ISH or CSH Link with ISH or CSH Facility Mux then such Capacity provision shall be subject to the provision of sufficient capacity within the appropriate PPC ISH or CSH Link within STM-1 tributaries designated for PSTN interconnect use.

10.1.5	Within any ACO Period commencing two years after the Ready for Service Date of a Switch Connection, BT shall place Capacity Orders for a minimum of 80 per cent. of the aggregate Capacity specified in the relevant ACOs for that Operator Switch Connection. Failure by BT to place such Capacity Orders shall result in pre-payment charges being paid by BT in accordance with the provisions set out in paragraph 1 of Appendix B. Pre-payment charges arising with respect to a specific Operator Switch Connection will be accepted as pre-payment for future Capacity Provision Orders in respect of Capacity at the same Switch Connection placed within 12 months of the end of the relevant ACO Period (thereby being credited against any charges payable by BT in respect of such Capacity Order(s)).

10.1.6	If no ACO is provided or Capacity Orders are placed by the ordering Party in excess of the relevant limit in paragraph 10.1.1 or 10.1.4:

(1)	the Supplier shall not be obliged to meet the time scales set out in paragraph 11 for that part of the Capacity Order in excess of the relevant limit;

(2)	the time scales shall be agreed in writing for the provision of excess Capacity and the Ready for Test Dates shall be not later than 6 months after the date of receipt of a relevant Capacity Order; and

(3)	the Supplier of Capacity in excess of the relevant limit may raise charges to cover additional costs that it may incur arising directly from the provision of Capacity outside the normal planning process. Neither Party may incur such additional costs or provide Capacity outside the ACO process without the prior written approval of the other.

10.1.7	Each Capacity Order will be in the form set out in the Provisioning Manual and shall include all the information required by that form. 

10.1.8	The tributary allocation charts as set out in the Provisioning Manual, shall be amended by BT, unless agreed otherwise, and included in the Technical Master Plan.

10.2		Testing Timetables for 2Mbit/s Interconnect Links

10.2.1
(1)	BT and the Operator shall commence testing Capacity not later than 25 Working Days after the relevant scheduled Ready for Test Date. Unless agreed otherwise, the Purchaser shall provide the Supplier with a minimum of 15 Working Days notice of the date on which testing should commence. The Parties shall co-operate to ensure that testing is reasonably spread across the 25 Working Days following the date on which such Capacity is made ready for testing. The Parties shall use reasonable endeavours to complete testing in the shortest appropriate time.

(2)	If for any reason the Purchaser expects to be unable to proceed jointly with the Supplier in testing of any Capacity, the Purchaser shall notify the Supplier in writing as soon as possible and where such notice is less than 5 Working Days before the scheduled Ready for Test Date, the provisions set out in paragraph 3 of Appendix B of this Annex shall apply. Testing shall then be re-scheduled by agreement and commenced on such re-scheduled date. In the event of testing failing the Parties shall use reasonable endeavours to ensure testing is recommenced and concluded as quickly as possible.

(3)	The Parties shall agree the required test facilities. The Parties shall make such test facilities available from the date required by the other Party. If specified test facilities are missing or incorrect, Capacity Orders or Data Management Amendments will not commence until the facilities are made available.

(4)	If faults are identified during the testing period, the Party deemed to be causing the fault will clear the fault and produce updated documentation (as described in paragraph 10.1 of Annex A and detailed in the Provisioning Manual) within 5 Working Days.  Where such fault repair requires an outage of other non-related in service circuits, the fault clearance may take longer than 5 Working Days due to relevant outage notification periods, in which case the Party responsible for the fault clearance shall notify the other Party of this once identified and in any case within 5 Working Days. If the Parties do not agree as to who caused the fault, the dispute shall be referred to the agreed contact points.  If the agreed contact points do not agree as to who caused the fault, the dispute may be escalated to the next level of management in each Party.  These contact points will be as agreed from time to time between the Parties.  If there is still no agreement, the commercial dispute process under paragraph 26 of the main body may be invoked.

(5)	If the Party providing Capacity fails to commence testing of that Capacity by a date 25 Working Days after the relevant periods of time specified in paragraph 11 below, then (without prejudice to the other Party's rights and remedies under the Agreement) the Party providing such Capacity shall pay, on demand, to the other Party liquidated damages for such delay calculated in accordance with the provisions of paragraph 2 of Appendix B for up to a maximum of 25 Working Days.

(6)	If the Parties fail to agree an acceptable date for the testing of the Capacity (pursuant to 10.2.1 (2)) either Party may notify the other in writing of a Dispute.

10.2.2	Not later than the Working Day following the Ready for Test Date the Supplier shall notify the Purchaser that such Capacity is Ready for Testing. Such notice shall be in the form set out in the Provisioning Manual.

10.2.3	As soon after the Ready for Service Date as is practical, both Parties shall certify that the Capacity has been satisfactorily tested by signing the certificate set out in the Provisioning Manual.

10.3	Congestion

Where a Traffic Route is used for the conveyance of traffic for both Parties and either Party detects the grade of service referred to in paragraph 5.3.2 not being met because of non-transient causes or identifies a trend that will lead to such grade of service not being met in the current or next ACO Period, the Operator shall order Route Augmentation such that the problem or potential problem is alleviated.

10.4	Testing and Commissioning Procedures

The Parties shall jointly test the Capacity and any service specific items and make any necessary adjustment to ensure that the Capacity meets the agreed performance standards and Specification(s). Details of the testing procedures are included in the Operational Testing Manuals.

11.	CAPACITY ORDER TIMESCALES

11.1	Timescales for Provision of Capacity

The timescales for the provision of Capacity Ready for Testing are subject to the provisions set out in Schedules 01 and 130 (as appropriate) and, paragraph 10.1.6. The time scales are set out in paragraphs 11.1.3 to 11.1.6 inclusive and are concurrent with those set out in paragraph 11.1.1 and 11.1.2). Where such Capacity provision is to utilise appropriate capacity within a PPC ISH or CSH Link with ISH or CSH Facility Mux, such provision shall be subject to provision of sufficient capacity within the appropriate PPC ISH or CSH Link:

11.1.1	Capacity Provision at a Switch Connection for a Traffic Route passing through a new Point of Connection on an Interconnect Link using PDH or SDH one of the following as appropriate:

a). 85 Working Days following the date of receipt of the relevant Capacity Order where provision of such new Point Of Connection requires new transmission terminating equipment only to be provided; 
b). 110 Working Days following the date of receipt of the relevant Capacity Order where provision of such new Point Of Connection requires new transmission terminating equipment to be provided and new fibre/cable to be provided and/or fibre splicing;
c). 6 months following the date of receipt of the relevant Capacity Order where provision of such new Point Of Connection requires new transmission terminating equipment to be provided, new fibre/cable to be provided and/or fibre splicing and new duct to be provided.

11.1.2	Capacity Provision or Capacity Re-arrangement at a Switch Connection requiring a change of technology from PDH to SDH or SDH to PDH for a new or existing Traffic Route at an existing Point of Connection one of the following as appropriate:

a). 85 Working Days following the date of receipt of the relevant Capacity Order where provision of such new Point Of Connection requires new transmission terminating equipment only to be provided; 
b). 110 Working Days following the date of receipt of the relevant Capacity Order where provision of such new Point Of Connection requires new transmission terminating equipment to be provided and new fibre/cable to be provided and/or fibre splicing;
c). 6 months following the date of receipt of the relevant Capacity Order where provision of such new Point Of Connection requires new transmission terminating equipment to be provided, new fibre/cable to be provided and/or fibre splicing and new duct to be provided.

11.1.3	New Traffic Routes between Switch Connections through an established Point of Connection using the same technology, including the provision of new Traffic Routes by way of additional Customer Sited Interconnect from a particular Operator site:

25 Working Days following the date of receipt of the relevant Capacity Order.

11.1.4	Route Augmentation using the same technology, including the provision of additional Customer Sited Interconnect between the same Switch Connections:

25 Working Days following the date of receipt of the relevant Capacity Order.

11.1.5	New Traffic Routes over IECs at a Switch Connection using the same technology:

25 Working Days following the date of receipt of the relevant Capacity Order.

11.1.6	Route Augmentation using the same technology on Traffic Routes to Remote Switch Connections.

25 Working Days following the date of receipt of the relevant Capacity Order.

11.1.7	Capacity Re-arrangements involving the provision of new Traffic Routes using the same technology or a new technology already in service at the relevant Switch Connection:

25 Working Days following the date of receipt of the relevant Capacity Order.

11.1.8	Capacity Re-arrangements between established Switch Connection involving Route Augmentation using the same technology or a new technology already in service at the relevant Switch Connection:

25 Working Days following the date of receipt of the relevant Capacity Order.

11.1.9	Capacity Re-arrangements involving the provision of new Traffic Routes requiring IECs using the same technology or a new technology already in service at the relevant Switch Connection:

25 Working Days following the date of receipt of the relevant Capacity Order.

11.1.10	Path Protection - on a date such as the Parties shall agree.

11.1.11	Capacity Provision for the first order for PCPOC at an existing Point of Connection:

	30 Working Days from receipt of the relevant Capacity Order.

11.1.12	Additional Capacity on an existing PCPOC:

	10 Working Days from receipt of the relevant Capacity Order.

11.2	Removal of Capacity

11.2.1	Subject to the relevant Schedules if either Party requires the removal of Capacity it paid for (or for which payment is due by that Party under this Agreement), an order identifying the Capacity and the date from which it is no longer required (a "removal order") may be placed by that Party on the other Party. The Party receiving the removal order will remove the Capacity not later than 30 Working Days from the date of receipt of the removal order. However this timescale may be extended if agreed in writing by the Parties in order to coincide with a planned programme of work.

11.2.2	If either Party requires the removal of Capacity paid for by the other Party (or for which payment is due by the other Party under this Agreement) or the removal of Capacity used for bothway working then a written request shall be sent to the other Party detailing the requirement and giving the reasons for its removal. If the Party receiving the request agrees to the removal of the Capacity such Party shall issue a removal order to the Party requesting the removal. This Capacity will then be removed by the Supplier within 30 Working Days from the date of receipt of the removal order or such other date as the Parties may agree. Agreement to a removal request shall not be withheld where it can be demonstrated that the requirement for the Capacity is not supported by the current agreed Traffic Forecast. However, if the Party receiving the request still does not agree then that Party may notify the other in writing of a Dispute and Capacity shall not be removed until agreement has been reached or the Dispute is resolved.

11.2.3	A removal certificate shall be issued to the Party who paid (or who is responsible for payment) for the Capacity on completion of the removal work.

11.2.4	For the avoidance of doubt, if payment for Capacity provided and subsequently removed pursuant to this paragraph 11 has not been made at the time of such removal such payment shall remain due and payable.

11.2.5	Subject to clause 11.2.5A, if pursuant to this paragraph 11.2 Capacity is removed, a proportion of the relevant connection charge shall be repaid to the Party requesting the removal. The amount to be repaid shall be that set out in paragraph 4 of Appendix B to this Annex.

11.2.5A	Clause 11.2.5 does not apply to any Capacity connected on or after the date exactly 5 years before Openreach’s most recently announced PSTN shutdown date (as at the date of request for removal of such Capacity).  By way of example, as at October 2020, the PSTN shutdown is scheduled to occur no later than 1 December 2025, therefore this clause does not apply to any Capacity connected after 1 December 2020.  In the event that Openreach postpones PSTN shutdown indefinitely, this clause 11.2.5A will be of no effect.

11.2.6	With respect to the removal of Capacity the requesting Party shall ensure that where such Capacity removal results in the complete removal of a Traffic Route, the relevant Data Management Amendments (“DMAs”) are submitted by the requesting Party and completed in order to remove all traffic from the Traffic route prior to the placing of such a removal order in accordance with the process contained within the Provisioning Manual. If the requesting Party fails to ensure that the necessary DMAs are submitted and completed prior to the submission of the Order for Capacity removal the provisions set out in paragraph 5 of Appendix B shall apply. In addition the Capacity Order shall be suspended until such time as the associated DMAs are completed and notification of such sent by the providing Party to the requesting Party.

For the avoidance of doubt, with respect to this paragraph 11.2.6, where the Operator places Capacity Orders and/or DMAs on behalf of BT then BT shall be deemed to be the requesting Party.

11.3		Order Amendment

11.3.1	Capacity Orders, except those for PCPOC, may be amended as follows:

(a)	Capacity Orders which incorporate agreed amendments requested by the Supplier or are corrections of simple typing mistakes which do not affect the Ready for Test Date nor the implementation by the Supplier will not incur any charges.

(b)	Capacity Orders may be withdrawn free of charge up to 10 Working Days from receipt of the relevant Capacity Order by the Supplier. Capacity Orders, including any placed in the last 10 Working Days of an ACO Period which bring the total orders up to 80% of the Capacity specified in the ACO, and subsequently cancelled within 10 Working Days of placing those orders shall not be included in the amount of Capacity ordered in the relevant ACO Period.

(c)	Capacity Orders may be amended at a charge, details of which are specified from time to time in the Carrier Price List, up to 10 Working Days from receipt of the Capacity Order by the Supplier. The original date that the Capacity Order was placed will apply for the purpose of identifying the Ready for Test Date.

(d)	Capacity Order amendments received after 10 Working Days from receipt of the original Capacity Order by the Supplier which do not have a material affect on the order (i.e. editorial change, data build change only, without change of Supplier's Switch Connection or other change which the Parties reasonably agree does not materially affect the Capacity Provision within the stated time scales) will be accepted by the Supplier without a change in the Ready for Test Date at a charge which is set out in the Carrier Price List.

Where an amendment involves data build changes, the order amendment must be received by the Supplier not later than 10 Working Days before the Ready for Test Date

11.3.2	If a Capacity Order is amended other than as set out in (a) (b) (c) or (d) above, and the amendment is to reduce the Capacity originally ordered, the Purchaser shall pay the charge set out in paragraph 6 of Appendix B. The Supplier shall accept such an amendment without a change in the Ready for Test Date.

11.3.3	Apart from as detailed in 11.3.1 (a) (b) and 11.3.2, no amendments of Capacity Orders will be accepted after 10 Working Days from receipt of the Capacity Order by the Supplier.

11.3.4	The Supplier may extend a Ready for Test Date where there have been two or more order amendments to any matter included in the order form set out in the Provisioning Manual during the first 10 Working Days following receipt of a Capacity Order.

11.4	Capacity Re-arrangement

Capacity Re-arrangement may be requested as follows:

(a)	The Purchaser may request in writing Capacity Re-arrangement, and the Supplier shall carry out the necessary work in accordance with the time scales set out in paragraph 11.1.

(b)	If the Supplier requests Capacity Re-arrangement of Capacity previously provided by the Supplier, the Supplier shall notify the Purchaser in writing giving reasons for its request. If the Purchaser accepts the request it shall confirm the same in writing. The Supplier shall then at its own expense carry out the Capacity Re-arrangement in accordance with the request. The Purchaser shall not unreasonably withhold or delay consent to such request provided that arrangements are made, in accordance with this Agreement where applicable, to ensure that no loss is caused to or suffered by the Purchaser as a result of the Capacity Re-arrangement.

(c)	The Supplier shall issue a certificate to the Purchaser on completion of work carried out pursuant to paragraph 11.4 (a) or (b). The Purchaser may submit requests for Capacity Re-arrangement in writing to the Supplier at any time after the earlier of Ready for Service Date or one month after Ready for Test Date.

(d)	On completion of a Capacity Re-arrangement the original Capacity is deemed terminated and replaced by the rearranged Capacity.

11.5	Cancellation of Order

At any time prior to the Ready for Test Date a Party may by written notice to the other cancel a Capacity Order for Capacity on a 2Mbit/s Interconnect Link it had placed. If a Capacity Order is cancelled more than 10 Working Days after placement of the Capacity Order, the cancelling Party shall pay a cancellation charge as set out in paragraph 7 of Appendix B. Capacity Orders, including any placed in the last 10 Working Days of an ACO Period which bring the total Capacity Orders up to 80% of the Capacity specified in the ACO, and subsequently cancelled within 10 Working Days of placing those orders shall not be included in the amount of Capacity ordered in the relevant ACO period.

11.6		General

The Party in receipt of a Capacity Order shall make the relevant Capacity available and Ready for Testing within the time scale specified in paragraph 11.1. The receiving Party shall notify the ordering Party of such receipt within one Working Day of receipt.

12.	NUMBERING

12.1	Numbering Orders

	Subject to paragraph 8 of the main body of the Agreement, the Party in receipt of a request by the other Party to implement numbering orders for Number Ranges and associated changes to data in the System shall do so in accordance with Appendix C.

12.2	Number flow

12.2.1	The Parties shall convey to each other telephone numbers in the national and international number formats from time to time in force.

12.2.2	For IDD Calls to or from a BT ISC where C 7 (IUP) signalling is used, all digits including the international prefix (two leading zeros), shall be conveyed across the interface from the sending Party's System to the other Party's System.

12.2.3	For IDD Calls to a BT ISC, where C 7 (ISUP) signalling is used, the Operator shall convey all digits except the international prefix. For Calls from a BT ISC where C 7 (ISUP) signalling is used BT shall convey all digits excluding the leading zero of the national number.

12.3		Number Information	

At appropriate intervals each Party shall inform the other of all numbering additions and changes to Number Ranges within their respective Systems that may affect Call routing.

13.	TECHNICAL REVIEW MEETINGS

13.1	The first Technical Review Meeting shall occur at either Party's written request not later than 1 month from the initial in-service date. Subsequent Technical Review Meetings shall occur at no greater than four monthly intervals thereafter, not less than 5 Working Days prior to the start of the relevant ACO period next following.

13.2	At Technical Review Meetings the Traffic Forecast referred to in paragraph 8 above shall be discussed and the Capacity Profiles referred to in paragraph 9 shall be agreed.

14.	SWITCH TESTING 

14.1	Testing Principles

Each Party shall have the right to require testing of the other Party’s Switch(es) to confirm correct interworking. The testing varies according to the Switch manufacturer, the software build level and the method of implementation. The scope of the testing shall follow the relevant ITU-T guidelines.

14.2	Testing Information

14.2.1	Not later than 10 Working Days after a written request by one Party, the other Party shall provide an initial indication of the level of testing required, having been given details of Switch hardware and software build level, services, and a statement of conformity of the Party’s System to the specifications as detailed in paragraph 7.1.1. The Parties shall agree exact test requirements and timescales.

14.2.2	If, owing to the default of one of the Parties the testing procedures vary substantially from the test procedures agreed pursuant to this paragraph, the other Party may levy a reasonable charge for its direct costs resulting from such default.

14.3	Where BT requests testing, the following provisions shall apply:

14.3.1	Reduced Level of Testing

A Switch proposed as an Operator Exchange, of the same type previously successfully tested for the same type of interconnect, at the same software build will need the minimum of testing. A list of such Switches is set out in the Provisioning Manual. Commissioning and Acceptance Testing ("CAT") of such an Operator Exchange may take approximately four weeks. For additional Operator Exchanges, Traffic Routes and Capacity interconnected to the BT System, operational testing at a suitable level will take place as described in the Operational Testing Manuals.

14.3.2	Intermediate Level of Testing

A Switch proposed as an Operator Exchange of a type previously successfully tested at a different software build or implementation, will need additional testing, if such different build or different implementation could reasonably be considered likely to adversely affect Call processing. Both Network Inter-working Tests ("NIT") using BT captive models and CAT will be required, which may take approximately eight weeks.

14.3.3	Full Switch Testing

A Switch proposed as an Operator Exchange or major build change of an existing Operator Exchange not previously successfully tested for the same type of interconnect shall require Interface Validation Testing ("IVT") by the Operator, using a protocol simulator, which may take the Operator about six weeks. The total testing duration for IVT, NIT and CAT may be approximately 14 weeks. The period of time specified in 14.3.2 and 14.3.3 may, subject to the availability of the necessary BT captive models at the Operator's written request, be concurrent with the time scale set out in paragraph 11.1.1 above.

14.4	Where the Operator requests testing it will employ testing no more onerous and be of no greater duration than those set out in paragraph 14.3.

14.5	In the event that the Parties fail to agree any test procedure and/or time scale, then either Party may notify the other in writing of a Dispute.

15.	TRANSMISSION AND SIGNALLING

15.1	Transmission

Interconnection of the BT System and the Operator System shall be based on digital technology operating at 2Mbit/s in accordance with the Generic Transmission Interface Specification and, if appropriate, the Generic SDH Interface Specification.

15.2	Synchronisation

15.2.1	The Parties shall comply with the applicable synchronisation provisions of the Generic Electrical and Physical Interface Specification. Where requested, BT shall supply synchronisation from the highest order available within the relevant part of the BT System.

15.2.2	Where SDH equipment is used as part of an ISI Interconnect Link, synchronisation of the relevant SDH equipment shall be provided in accordance with ITU-T Recommendation G.803. However the STM-N timing quality should not be assumed to be referable to a clock of ITU-T Recommendation G.811 standard.

15.3	Echo Control

15.3.1	If International Calls are conveyed by the Operator to a BT ISC or handed over to the Operator by BT directly from a BT ISC, the Parties shall obtain the correct echo control by conveying signalling information in accordance with the Generic Transmission Interface Specification and the Generic C7 Signalling Interface Specification.

15.3.2	Some Calls within the UK require echo control. The Parties shall obtain the correct echo control by conveying signalling information in accordance with the Generic Transmission Interface Specification and the Generic C7 Signalling Interface Specification.

15.4	Signalling

The Parties shall comply with the applicable signalling provisions of the Generic C7 Signalling Interface Specification.

15.5	Circuit Selection

Where bothway working is employed, the following circuit selection protocols shall apply:

(1)	Circuit Selection Protocols

(a)	BT shall use the forward sequential protocol, starting from the first traffic circuit and selecting sequentially until a free circuit is found.

(b)	The Operator shall use the backward sequential protocol, starting from the last traffic circuit and selecting sequentially until a free circuit is found.

(2)	Direction of search

(a)	From BT to Operator, direction of traffic circuit 1 to Z.

(b)	From Operator to BT, direction of traffic circuit Z to 1.

15.6	Dual Seizure

i) IUP and ENV ISUP interconnect routes

BT shall have dual seizure priority

ii) ISUP interconnect routes
Each exchange will have priority on one half of the circuits in a both-way circuit group. 
The exchange with the higher signalling point code will have priority on all even-numbered circuits (circuit identification code) and the other exchange will have priority on all the odd-numbered circuits.

15.7	If operational intervention occurs due to network failure, the provisions of paragraphs 15.5 and 15.6 may be temporarily varied, for a period not exceeding 6 months, if agreed in writing by the Parties.

15.8	Numbering of traffic circuits

Circuits shall be identified pursuant to the Generic Signalling Interface Specification.

15.9	Answer Signals

15.9.1	Each Party shall provide the other with details of the timing and circumstances for the provision of all Answer Signals sent from that Party’s System including those for all types of Calls, but excluding those Calls for which that Party’s System is onward conveying such Calls to a Third Party Operator.

15.9.2	An Answer Charge Signal shall be returned in all cases for all Call Types except where agreed by the Parties and recorded in the relevant BT-Operator "Service Description For Charge Indication in IUP and UK ISUP" document.

15.9.3	Where a Party's System is onward conveying such Calls to a Third Party Operator, such Party shall use reasonable endeavours to co-operate with both the originating party and the Third Party Operator in order to ensure that any occurrences of inappropriate ANC signals are investigated and corrected by the appropriate party.

16.	PERFORMANCE STANDARDS

16.1	General

16.1.1	The Parties shall co-operate to maintain the overall quality of the conveyance of Calls and adopt the general principles on standards, techniques and methodology for the achievement of quality in telecommunications networks and services contained in the relevant ITU-T standards.

16.1.2	The Parties shall agree operational management strategies to protect service quality and to alleviate short term overloads due to abnormal conditions and address congestion due to under provisioning.

16.2	Call Service Performance

16.2.1	The Parties shall agree relevant service parameters and measurements for the monitoring of service performance. These will typically include sample sizes, frequency, time and performance threshold criteria. This data includes actual measurements of exchange or route busy hour traffic (Erlangs), lost communications (overflows), number of Calls alternatively routed, Answer Seize Ratio ("ASR") and busy hour call attempts. This shall be exchanged on a monthly basis. Exception reports shall be provided where standards have not been met or if performance thresholds have not been attained. The Parties shall use their reasonable endeavours to detect and correct adverse trends before they result in adverse performance.

16.2.2	If a service performance problem is identified, the Parties shall exchange information about the problem, including the information set out in paragraph 16.2.1 above together with the following information:

(1)	critical levels for traffic and unsuccessful Call attempts;

(2)	information on sources of traffic;

(3)	information on timing synchronisation and slippage rates.

16.2.3	Where congestion occurs on a Traffic Route used for the conveyance of Traffic for both Parties, the Parties shall agree and apply appropriate network management procedures in accordance with the provision described in the Operations and Maintenance Manual. Where such agreement cannot be reached, either Party may apply appropriate network management procedures to Traffic originating in its System to alleviate the problem.

16.2.4	In the case of BT to Operator Dial IP Calls the Grade of Service shall be measured in terms of "intent blocking" i.e. each occasion that a user instructs their computer to connect to their ISP is a single intent, even though the computer may automatically redial a number of times. The key principle in comparing voice GoS (attempt blocking) with Dial IP intent blocking is that an IP dial intent is equivalent to a call attempt in the sense that each represents a single action by the end user to obtain service.

16.2.5	The Parties shall use reasonable endeavours to identify and resolve the problem and if the Parties fail to resolve the problem it shall become a Dispute.

16.3	Interconnect Link Service Performance

Transmission performance standards over an Interconnect Link shall be based on availability, errored seconds and severely errored seconds over a one month period.

16.4		Information on Performance Standards

Each Party ("the first Party") shall provide to the other, as the other Party may reasonably require, information on the performance standards of the first Party's System from time to time for the purpose of the other Party verifying the performance by the first Party of its obligations under this Agreement, including without limitation the performance standards referred to in this paragraph 16, routine maintenance time scales and fault repair times as set out in the Operations and Maintenance Manual.

17.	OPERATIONS

17.1	General

17.1.1	Each Party shall be responsible for the safety and operation of its own System.

17.1.2	The Operations and Maintenance Manual details the responsibilities, methods and procedures for the operation and maintenance of the interconnection of the Systems. Details of contacts are given in the Customer Service Plan.

17.2	Fault Identification and Reporting

17.2.1	Each Party will advise its Customers to report all faults to its fault reporting centre.

17.2.2	If a Party's Customer reports a fault to the fault reporting centre of the other Party, that Party will inform the Customer of the correct number to which to report the fault.

17.2.3	If a major fault occurs which affects both Parties' Systems, initial responsibility for identifying the fault rests with the Party who first becomes aware of the fault.

17.2.4	If a Party identifies a fault occurring in its System which may have an adverse effect on the other Party's System, the first Party shall promptly inform the other Party of the problem and the actions being taken to resolve the problem.

17.2.5	Each Party shall bear the costs of its own fault reporting centre.

17.3	Speed of Response

Indicative response times for different fault conditions are set out in the Operations and Maintenance Manual, response time being the time from the reporting of the fault until remedial action begins.

17.4	Service Restoration

The service restoration procedures set out in the Operations and Maintenance Manual are based on the following:

(1)	service restoration shall take priority over the clearance of faults not affecting service unless it is agreed that a fault be treated as a higher priority;

(2)	the relevant Party shall automatically bring in available standby Capacity and/or carry out network management actions to restore service;

(3)	the relevant Party shall observe equipment alarms and carry out testing to identify the nature and location of the fault in co-operation with the other Party as necessary;

(4)	if possible, the relevant Party shall rectify the fault immediately, if not, the other Party must be notified and kept informed of progress on a regular basis;

(5)	if temporary repairs are made, the other Party must be informed and given the estimated time-scale and service impact of full repair; and

(6)	priority shall be given by the relevant Party to faults with the highest service loss impact on the number of Customers or the volume of traffic affected.

17.5	Restoration Times and Procedure

Indicative restoration times and procedures are set out in the Operations and Maintenance Manual.

17.6	Planned Maintenance/Works

17.6.1	Each Party shall provide not less than 3 Working Days notice of any planned maintenance which may affect the other's System. Each Party shall use its reasonable endeavours to minimise disruption and where possible provide alternative routing at no charge to the other Party for a reasonable period of time with respect to the cause of the disruption.

17.6.2	If a Party reasonably considers that the interconnection arrangements are at risk and maintenance repair activity is essential, that Party shall give as much advance notice to the other Party as is reasonably practicable.

18.		SERVICES

18.1	Introduction

This paragraph 18 sets out the technical requirements relating to the services provided in accordance with particular Schedules.

18.2	BT Operator Services

The arrangements for routing Calls from the Operator System to the services listed below are via a BT Switch Connection being a BT DMSU. The digits forwarded from the Operator System to the BT System shall be those below together with the two/three/five identification digits appropriate to the Operator as network address digits. The Operator shall use the identification digits agreed with BT:

Service									Digits

National Operator Assistance Service				100
Emergency Service							999
International Operator Assistance Service			155
Blind or Disabled Service						195

each service being as defined in the appropriate Schedules.

18.3	CLI

CLI shall be requested and provided in a manner consistent with the Generic C7 Signalling Interface Specification. 

18.4	Malicious Call Identification

Where a Party assists the police in identification of Calling Parties with malicious intent the Parties shall co-operate and when appropriate use CLI, such use being subject to paragraphs 11 and 21 of the main body of this Agreement.

18.5	Emergency Call Routing and Signalling

The handing over of Emergency Calls to the BT System at agreed BT Tandem Exchanges is subject to the following conditions:

(1)	Trunk reservation, physical separation or other appropriate method shall ensure the availability of emergency circuits to carry Emergency Calls in the Interconnect Link;

(2)	The BT Switch Connection being a BT DMSU shall route Emergency Calls to the BT Operator. Alternative routing shall be applied by the BT System when required and where this alternative routing fails, the BT System shall return a terminal congestion indication to the Operator;

(3)	Where possible, the Operator System shall present the relevant BT DMSU with an Initial and Final Addressing Message ("IFAM") containing the protection bit set.

APPENDIX A

BT/OPERATOR NETWORK INFORMATION

1.	OPERATOR INFORMATION

1.1	Names and Addresses of all Operator Exchanges within the area covered by the BT System.

1.2	Address of each Operator building within the area covered by the BT System which is capable of supporting IECs.

2.	OPERATOR NUMBERING INFORMATION

2.1	Number Ranges of Operator Exchanges within the area covered by the BT System and unless the Operator is only providing Mobile Calls the interconnectivity of and functionality provided by Operator Exchanges used for the conveyance of Calls pursuant to this Agreement.

3.	BT INFORMATION

3.1	Names and addresses of BT ISCs.

3.2	Names and addresses of BT Tandem Exchanges

3.3	Names and addresses of BT DLEs

3.4	Address of each BT building which is capable of supporting IECs.

4.	BT NUMBERING INFORMATION

4.1	Number Ranges of BT DLEs, BT DLTEs and of those exchanges which are connected by a BT DLE alone to the remainder of the BT System.

4.2	For each BT DLE and BT DLTE, the names of the BT Tandem Exchanges which are the Parent BT Exchanges.

4.3	For each BT DLE, where appropriate, the name of the BT DLTE.

5.	BT/OPERATOR INFORMATION

5.1	Addresses of relevant ISI locations together with annotated Ordnance Survey map extracts.

APPENDIX B

COMMERCIAL

1.	PRE-PAYMENT CHARGES

1.1	If either Party (the “Defaulting Party”) in any ACO Period, places Capacity Orders on the other Party for less than the minimum Capacity specified pursuant to either paragraph 10.1.2 or 10.1.5 of Annex A, then the Defaulting Party shall pay to the other Party not later than 30 Working Days from the end of such ACO Period the prepayment charges calculated in accordance with paragraph 1.2 of this Appendix.

1.2	Prepayment charges are calculated in accordance with the following formula:

A	=	((80% x B)-C) x D

Where:

A	is the prepayment charge payable;

B	is the aggregate Capacity Provision (by number of units 2Mbit/s Capacity) specified for the relevant ACO Period in the relevant ACO (not including if the Defaulting Party is the Operator, Capacity required for traffic handed over from the BT System for which BT has the responsibilities set out in Annex A, paragraph 5.1.3);

C	the Capacity (by number of units of 2Mbit/s Capacity) ordered during such ACO Period not including cancellations of Capacity Orders made during or after the relevant ACO Period;

D	is for each Interconnect Link equal to 0.35 of the IBC connection charge applicable for the ACO Period, as detailed in the Carrier Price List from time to time or for PCPOC the “fixed charge for subsequent circuits where BT plant exists” as set out in the BT Retail Price List from time to time.

2.	LIQUIDATED DAMAGES IN RESPECT OF TESTING CAPACITY

2.1	The liquidated damages referred to in paragraph 10.2.1(4) of Annex A shall be for each 2Mbit/s Interconnect Links equal to 0.0105 of the IBC connection charge specified from time to time in the Carrier Price List or for PCPOC, 1.5% of the “fixed charge for subsequent circuits where BT plant exists” as set out in the BT Retail Price List for time to time for each 2Mbit/s unit of Capacity which is subject of the relevant Capacity Order, multiplied by the number of Working Days calculated from a date 25 Working Days after the date on which the Capacity should have been Ready for Testing pursuant to paragraph 11 of Annex A, except that no liquidated damages shall be payable if the Purchaser causes a delay to the Ready for Service date by failing to complete the testing of the Capacity in the time period set out in paragraph 10.2.1(1) of Annex A.

3.	CANCELLATION CHARGES IN RESPECT OF LATE NOTIFICATION OF TESTING

3.1	If the notice by the Purchaser, pursuant to paragraph 10.2.1(2) of Annex A is given less than five Working Days before the scheduled Ready for Test Date, the Purchaser shall pay, on demand, a cancellation charge of 20% of the relevant connection charge, or charges, specified from time to time in the Carrier Price List and referred to in Schedule 01 or 130 as appropriate.

4.	REMOVAL OF CAPACITY

4.1	If, pursuant to paragraph 11.2 of Annex A, Capacity is removed within the period Y which shall not exceed 10 years, a proportion of the relevant connection charge shall be repaid to the Party requesting the removal. The amount to be repaid shall be:

R = (0.466 x C) - (0.466 x C x Y)
				10

where:

R	is the amount to be repaid

C	is the relevant connection charge referred to in Schedule 01 or 130 as appropriate and specified from time to time in the Carrier Price List

Y	is the number of years between the Ready for Test Date for the relevant Capacity and the date of the removal order rounded up to the next whole year.

5.	CHARGES IN RESPECT OF SUSPENSION OF CAPACITY REMOVAL PENDING COMPLETION OF ASSOCIATED DMAs

5.1	If pursuant to paragraph 11.2.6 of Annex A a Capacity Order is submitted by the requesting Party for removal of an entire Traffic Route without the prior completion of the associated Data Management Amendments, the requesting Party shall pay, on demand, a suspension charge of 20% of the relevant connection charge (excluding any IEC connection charge), or charges, specified from time to time in the Carrier Price List and referred to in Schedule 01 or 130 as appropriate.

6.	ORDER AMENDMENT

6.1	The charge payable pursuant to paragraph 11.3.2 of Annex A shall be 50% of the difference between the connection charges specified from time to time in the Carrier Price List, for the originally ordered and the amended Capacity Order.

7.	ORDER CANCELLATION

7.1	The charge payable pursuant to paragraph 11.5 of Annex A shall be 50% of the applicable connection charge specified from time to time in the Carrier Price List.

 APPENDIX C

DATA MANAGEMENT AMENDMENTS

1.	Introduction

1.1	This Appendix applies to Data Management Amendments made pursuant to a request by a Party (the “Requesting Party”) in the System of the other Party (the “Changing Party”).

1.2	The Parties acknowledge that no individual charges shall be invoiced by either Party in respect of a Data Management Amendment requested under paragraphs 2 to 5 of this Appendix (inclusive).

2	New Numbering Requirements

2.1	Initial provision of a given service

	The initial provision by the Changing Party to the Requesting Party of a service or facility (which the Changing Party provides under interconnect agreement(s) to Third Party Operator(s)) requiring data changes on a Switch necessary for a group of Call destinations for which the same retail charges apply (“Charge Band”) to set up Traffic Streams for Number Ranges and Access Codes, which data changes apply to:

	(a) a new Geographic Area Code;

	(b) a new Non-Geographic Code; 

	(c) discrimination of a single, or more than one, D digit, DE digit or DEF digit on a new Geographic Area Code or Non-Geographic Code;

	(d) a new Access Code;

	(e) a new Targeted Transit Prefix Code;

(f) initial service establishment for Number Portability Prefix Codes (both geographic and non-geographic).

2.2	Further provision of a service already provided

	Additional provision by the Changing Party to the Requesting Party of a service or facility requiring data changes on a Switch necessary for a group of Call destinations for which the same retail charges apply (“Charge Band”) to set up Traffic Streams for Number Ranges and Access Codes, which changes do not involve routing changes (i.e. addition of Number Blocks but not including Traffic Stream re-routing) and which data changes apply to:

	(a) an additional Geographic Area Code;

	(b) an additional Geographic Area Code or Non-Geographic Code within a geographic number range or non-geographic mobile number range;

	(c) an additional Geographic Area Code or Non-Geographic Code other than in paragraph 2.2 (b) above;

	(d) additional discrimination of a single, or more than one, D digit, DE digit or DEF digit on a new Geographic Area Code or Non-Geographic Code;

	(e) additional discrimination of a single, or more than one, D digit, DE digit or DEF digit on an existing Geographic Area Code or Non-Geographic;

	(f) an additional Access Code;

	(g) a subsequent Targeted Transit Prefix Code.

3	Traffic Stream Changes on a Switch

3.1	Traffic Stream re-routing not dependent on Capacity provision

	The data changes on a Switch necessary to alter the destination of an existing Traffic Stream, which do not require: 

(i)	Interconnect Link changes, or

(ii)	the provision of an additional Interconnect Link, or

(iii) any additional numbering (whether Number Range, access code or prefix code),

which changes apply to an existing:

	(a) Geographic Area Code;

	(b) Non-Geographic Code;

	(c) Geographic Area Code or Non-Geographic Code with routing discrimination down to one or more D digit combinations;

	(d) Geographic Area Code or Non-Geographic Code with routing discrimination down to one or more DE digit combinations;

	(e) Geographic Area Code or Non-Geographic Code with routing discrimination down to one or more DEF digit combinations;

	(f) Access Code;

	(g) Targeted Transit Prefix Code.

3.2	Traffic Stream re-routing dependent on Capacity or equipment provision

	The data changes on a Switch necessary to alter the destination of an existing Traffic Stream, which data changes require Interconnect Link changes, the provision of an additional Interconnect Link and/or additional Switch capacity, and any additional numbering changes to a  Geographic Area Code or Non-Geographic Code, which data changes apply to an existing:

	(a) Geographic Area Code;

	(b) Non-Geographic Code;

	(c) Geographic Area Code or Non-Geographic Code with routing discrimination down to one or more D digit combinations;

	(d) Geographic Area Code or Non-Geographic Code with routing discrimination down to one or more DE digit combinations;

	(e) Geographic Area Code or Non-Geographic Code with routing discrimination down to one or more DEF digit combinations;

	(f) Access Code;

	(g) Targeted Transit Prefix Code.

4	Changes to Charge Band Allocation

4.1	The data changes on a Switch necessary because of a change required by the Requesting Party to the charges payable by the Parties under a relevant Schedule, to relocate the Number Ranges from an allocated Charge Band to another current Charge Band which data changes apply to:

	(a) Non-Geographic Code(s);

	(b) Non-Geographic Code(s) with charging discrimination down to one or more D digit combinations;

	(c) Non-Geographic Code(s) with charging discrimination down to one or more DE digit combinations;

	(d) Non-Geographic Code(s) with charging discrimination down to one or more DEF digit combinations.

5	Differential D Digit Charging Discrimination

5.1	The data changes on a Switch necessary to expand an existing Geographic Area Code or Non-Geographic Code to a Geographic Area Code or Non-Geographic Code with charging discrimination to a minimum of two D digits.

6.	Requests for Data Management Amendments

6.1	The Requesting Party shall submit to the Changing Party a written request for a Data Management Amendment using the appropriate form and specified pre-requisites contained in the New Services Manual (or its successor document) to provide the Changing Party with the information necessary to enable it to produce an implementation programme. As soon as reasonably practicable and not later than two Working Days from the date of receipt, the Changing Party shall acknowledge in writing receipt of the request.

7.	Implementation Process

7.1	Subject to paragraphs 7.3, 7.4 and 7.6, following receipt of a Data Management Amendment request under paragraph 6.1, unless a longer implementation programme is requested, the Changing Party shall offer a date of completion of not more than 30 Working Days from the completion of all technical pre-requisites and contractual work (where necessary) required for such Data Management Amendment and shall make reasonable endeavours to complete the Data Management Amendment on such date.

7.2	If requested by the Requesting Party, the Parties may, on an occasional basis, agree in writing a completion date for provision of a service or facility which date is less than 30 Working Days. The Changing Party shall use its reasonable endeavours to achieve such date of completion.

7.3	Exceptionally, or where there is industry demand in excess of current DMA capacity, if the Changing Party is unable to meet a requested date it shall notify the Requesting Party as soon as practicable, and the Parties will enter into good faith negotiations to agree an alternative date. The Parties agree that if at any time the summation of forecasts for Data Management Amendment requests submitted by the industry to BT exceeds what is logistically reasonably achievable by BT, then BT shall meet with a representative industry body as soon as reasonably practicable to agree what action shall be taken (including the appropriate scaling down of Data Management Amendment requests). BT shall ensure that the Operator has reasonable advance notice of any such meeting. The Operator shall comply with the reasonable ordering procedures notified by BT from time to time following such meeting.

7.4	If the Requesting Party requires data changes requiring a series of Data Management Amendments which necessitate timing and/or sequencing of data changes for the implementation of such Data Management Amendments, including, for the avoidance of doubt, the provision or re-arrangement of any network element or capacity in either Party’s System, the Requesting Party shall provide to the Changing Party necessary information to enable the Changing Party to produce an implementation programme. 

7.5	Pursuant to paragraph 7.4 above, the Changing Party shall use reasonable endeavours to minimise the time taken to complete the implementation programme, taking into account the time-scales set out in paragraph 7.1 above for individual Data Management Amendments together with the dependencies (in terms of timing and/or sequencing of data changes) between each Data Management Amendment within the implementation programme.

7.6	The Changing Party shall proceed with the implementation programme for the Data Management Amendment agreed under paragraphs 7.1 to 7.5 (inclusive), and complete such programme not later than the agreed date of completion provided that the following pre-requisites are met:

7.6.1	the Parties have agreed in writing the relevant Schedule(s) specifying, as appropriate, the Number Range(s) applying from time to time, or the service is launched pursuant to paragraph 8 of the main body of the Agreement to which such Data Management Amendment order relates;

7.6.2	the Requesting Party has given written confirmation to the Changing Party that the Number Ranges have been allocated to the Requesting Party by Ofcom for use by the Requesting Party or the Requesting Party provides written authority, from the Third Party Operator to whom the Number Range has been allocated, to carry out the requested Data Management Amendment;

7.6.3	the Parties have agreed such test facilities as may reasonably be required and the Requesting Party has provided such test facilities (including, without limitation, such number of test lines and appropriate tone/announcement) by the time of commencement of the implementation programme;

7.6.4	the Changing Party has agreed the routing plans submitted by the Requesting Party and the Requesting Party has provided the routing plan reference to the Changing Party prior to commencement of the implementation programme;

7.6.5	the request form has been completed correctly;

7.6.6	sufficient Capacity (for testing of the Data Management Amendment) is ready for service or has been ordered with a Ready For Service Date being prior to the commencement date of the implementation programme.

7.7	Completion of the implementation programme is subject to the ongoing availability of sufficient test facilities.

7.8	If any of the provisions of paragraphs 7.6 and/or 7.7 above are not being complied with, the Changing Party may suspend the implementation programme and shall advise the Requesting Party that work shall not recommence until:

7.8.1	the Requesting Party gives written confirmation that the provisions of paragraphs 7.6 and/or 7.7 above (as the case may be) have been met; and

7.8.2	the Parties agree any amendments to the implementation programme, such agreement not to be unreasonably withheld or delayed;

and if work does not recommence within 60 Working Days of notification of suspension, the Data Management Amendment order (subject to the Changing Party giving not less than 60 Working Days’ notice) shall be deemed a cancellation by the Requesting Party.

7.9	A revision of the implementation programme in accordance with paragraph 7.8 above may result in the implementation period being extended beyond the agreed completion date taking into account the period of delay.

7.10	On completion of the implementation programme, the Changing Party shall give written confirmation to the Requesting Party within three Working Days of the full implementation of the Data Management Amendment request.

7.11	A reference to a matter being agreed between the Parties means such agreement not to be unreasonably withheld or delayed. If agreement between the Parties is not reached pursuant to paragraph 7.4 either Party may notify the other in writing of a Dispute.

8	Data Management Amendments which are individually chargeable

8.1	Subject to the provisions of this Agreement, for Data Management Amendments which are individually chargeable, the Changing Party shall install necessary changes (including data changes) for it:

8.1.1	to provide Data Management Amendments subsequent to service establishment of a specific code or service to modify, add or change codes and routings for Number Portability Prefix Codes (both geographic and non-geographic);

8.1.2	to enable reciprocal transfer of entire Number Blocks together with associated ongoing per-Switch conditioning;

8.1.3	being BT, to route Emergency Calls to appropriate Emergency Centres;

or for such other services or facilities as are notified from time to time.

9	Quotations for individually chargeable Data Management Amendments

9.1	This paragraph 9 applies to Data Management Amendments associated with services and facilities referred to in paragraph 8 above. The Requesting Party shall submit to the Changing Party a written request for a quotation for Data Management Amendments in relation to services to be provided under the appropriate Schedule of this Agreement and with such request provide to the Changing Party in writing the information necessary to enable the Changing Party to produce an implementation programme.

9.2	As soon as reasonably practicable, the Changing Party shall provide a written quotation and implementation programme both of which shall be provided not later than 20 Working Days from receipt of the Requesting Party’s request for a quotation.

9.3	A quotation shall remain valid for three months from the date of issue of the relevant quotation.

9.4	The Changing Party shall compile the quotation on the basis of the minimum cost to the Requesting Party that is consistent with good engineering practice in executing carrying out work in the BT System or the Operator’s System (as the case may be).

9.5	The implementation programme and charge shall be subject to the Parties’ written agreement. If agreement between the Parties pursuant to this paragraph 9.5 is not reached either Party may notify the other in writing of a Dispute.

10	Charging

10.1	For implementation by the Changing Party of a Data Management Amendment order referred to in paragraph 8 above, the Requesting Party shall pay the charges quoted by the Changing Party and payment shall be due on the Changing Party giving written confirmation to the Requesting Party of the full implementation of the Data Management Amendment order.

10.2	Charges for each type of Data Management Amendment shall be specified from time to time in the Carrier Price List.

10.3	If, prior to completion of the implementation programme agreed pursuant to paragraph 7 or paragraph 9.5 of this Appendix, the Requesting Party:

(a) requests a material alteration to the implementation programme, or 

(b) cancels the order, 

the Requesting Party shall pay to the Changing Party its reasonable charges for the work carried out pursuant to the Data Management Amendment order.

APPENDIX D

TABLE A

TRAFFIC TYPE	PARTY HAVING THE RESPONSIBILITIES SET OUT IN PARAGRAPH 5.1.3 OF ANNEX A	
Calls to geographic telephone numbers (i.e. to fixed telephone numbers)
BT to Operator (termination of BT originated Calls and Calls transitting the BT System)
Operator to BT (termination of Operator originated Calls and Calls transitting the Operator System)

BT

Operator	
Calls to non-geographic telephone numbers (i.e. including mobile, but excluding Non Geographic Call Services and 03 UK-wide Number Calls)
BT to Operator (termination of BT originated Calls and Calls transitting the BT System)
Operator to BT (termination of Operator originated Calls and Calls transitting the Operator System)

BT

Operator	
Groomed IP Network Calls
BT to Operator	
Operator	
IP Network Calls  
BT to Operator
Operator to BT	
Operator
BT	
International Calls
BT to Operator (to overseas)
Operator to BT (to overseas)	
BT
Operator	
Transit Calls (i.e. origination leg, all traffic types - except those detailed as specific Transit within this Table A)
BT to Operator (to transit destination)
Operator to BT (to transit destination)	

BT
Operator	
Non Geographic Call Services Calls and 03 UK-wide Number Calls (for termination not Transit)
BT to Operator (termination of BT originated Calls and Calls transitting the BT System)
Operator to BT (termination of Operator originated Calls and Calls transitting the Operator System)	

Operator

BT	
Indirect Access Calls
BT to Operator
Operator to BT	
Operator
BT	

TRAFFIC TYPE	PARTY HAVING THE RESPONSIBILITIES SET OUT IN PARAGRAPH 5.1.3 OF ANNEX A	
Carrier Pre-Selection Calls
BT to Operator
Operator to BT	
Operator
BT	
118 Directory Enquiry Service Calls
BT to Operator
Operator to BT	
Operator
BT	
BT Operator services calls
Operator to BT	
Operator	
Emergency Calls
Operator to BT	
Operator	
Targeted Transit Calls
Operator to BT (to transit destination)
via BT to Operator	
Operator
Operator	
Indirect Access Transit Calls
Operator to BT (to Third Party transit destination)
via BT to Operator	
Operator
Operator	
118 Directory Enquiry Service Transit Calls
Operator to BT (to Third Party transit destination)
via BT to Operator	
Operator
Operator	
PNS/PAS Calls
BT to Operator	
Operator	
116 European Helpline Service Calls
BT to Operator
Operator to BT	
Operator
BT	
116 European Helpline Service Transit Calls
Operator to BT (to Third Party transit destination)
via BT to Operator	
Operator
Operator	
Such other Traffic Types as may be specified from time to time in a Schedule	As specified	

For the avoidance of doubt responsibility for traffic to numbers ported under Number Portability shall be the same as that shown above. 

APPENDIX E

STP (SIGNAL TRANSFER POINT) WORKING

1.	GENERAL

1.1	STP working is available in specific instances in relation to interconnection between BT System and the Operator System: 

(a)	STP working shall allow SS7 messages that are related to a Traffic Route between an Operator Switch and a BT DLE to be passed between such two end point switches, that terminate the Traffic Route, without the need for dedicated Signalling Links between such two end point switches. Instead of the SS7 messages passing directly between the two end point switches, the messages are delivered via intermediate signal points "Signal Transfer Points". 

(b)	STP working shall allow SS7 messages that are related to a Traffic Route between an Operator Next Generation Network and a NGS type BT DMSU, or NGS type BT DJSU, (for the purposes of this Appendix E, Operator Next Generation Network shall mean replacement IP technology network elements within the Operator System) to be passed between such two end point elements, that terminate the Traffic Route (or the relevant call control element), without the need for dedicated Signalling Links between such two end points. Instead of the SS7 messages passing directly between the two end points, the messages are delivered via intermediate signal points "Signal Transfer Points".

	This Appendix describes the availability of STP working, the planning and dimensioning restrictions that apply and documentation required when STP working is to be used.

2.	STP WORKING AVAILABILITY

2.1	In respect of Traffic Routes between an Operator Switch and a BT DLE the BT STP Network architecture is detailed within the Provisioning Manual. The Traffic Route scenarios where STP working may be employed are detailed in paragraph 5.2.13 of this Annex. For clarification, the BT STP Network is available for STP working in support of Traffic Routes provided solely for the conveyance of:

(a)	IP Network Calls (including Groomed IP Network Calls);

(b)	NGCS data Calls;

(c)	Both IP Network Calls (including Groomed IP Network Calls) and NGCS data Calls;

(d)	IP Network Calls (including Groomed IP Network Calls) and Restricted NGCS Voice traffic;

(e)	NGCS data Calls and Restricted NGCS Voice traffic;

(f)	IP Network Calls (including Groomed IP Network Calls), NGCS data Calls and Restricted NGCS Voice traffic;

(g)	Restricted NGCS Voice traffic.

2.2	In respect of Traffic Routes between an Operator Next Generation Network and a NGS type BT DMSU, or NGS type BT DJSU, the BT STP Network architecture is detailed within the Provisioning Manual. The Traffic Route scenarios where STP working may be employed are detailed in paragraph 5.2.13 of this Annex. For clarification, the BT STP Network is available for STP working in support of such Traffic Routes for the conveyance of all Traffic Types.

3.	PLANNING AND DIMENSIONING RULES

3.1	BT shall allocate; (a) the relevant BT STP unit to be used for all STP Linksets, (b) the traffic routes to the STP routes and (c) the primary/secondary STPs within each STP route. 

3.2	The following restrictions shall apply to the use of STP working:

(a)	A minimum of 2 Signalling Links per Signalling Link Set - OLO STPs/end points to BT STPs

(b)	A minimum of 2 Signalling Links - OLO STP(s)/end point(s) to BT STPs;

(c)	For Traffic Routes to BT DLEs a maximum Traffic Route size of 16 x 2Mb/s shall be supported by STP working where the traffic conveyed over such route comprises of data Calls or both data Calls and Restricted NTS voice Calls;

(d)	For Traffic Routes to BT DLEs a maximum Traffic Route size of 8 x 2Mb/s shall be supported by STP working where the traffic conveyed over such route comprises of Restricted NTS voice Calls;

3.3	Each STP Signalling Link shall be subject to a Signalling Link loading threshold of 40% which shall not be exceeded. BT and/or the Operator may require that this threshold be set at a level lower than 40%, if agreed in writing by both parties. 

3.4	During the planning of STP working the Operator shall provide the following information:

(a)	The expected Signalling Link peak loading (%) in the Busy Hour;

(b)	The expected Signalling Link average loading (%) in the Busy Hour;

(c)	The STP Signalling Link occupancy (loading) threshold % be set at 40% in accordance with paragraph 3.3 of this Appendix unless otherwise agreed in writing;

(d)	Details of the Operator’s signalling routings employed in support of Traffic Routes utilising STP working;

(e)	Details of the Operator’s signalling routings employed in support of Traffic Routes utilising STP working under Operator STP unit failure;

3.5	Each Party shall monitor the STP Signalling Link loading to ensure that the Signalling Link loading threshold specified in paragraph 3.3 of this Appendix, or as otherwise agreed, is not exceeded. Either Party may reasonably request that additional Signalling Links be added to an STP Signalling Link Set to ensure that the Signalling Link loading threshold is not exceeded and the other Party shall comply with such request.

3.6	If excessive volumes of signalling messages are experienced either Party may invoke network management controls to alleviate the problem.

4.	DOCUMENTATION REQUIRED FOR STP WORKING

4.1	The documentation and forms required for the provision of STP working are contained within the Provisioning Manual.