One-Way Interconnection Trunks 2.3.1 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Onvoy to Frontier, Onvoy, at Xxxxx’s own expense, shall:
2.3.1.1 provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or
2.3.1.2 obtain transport for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier.
2.3.2 For each Tandem or End Office One-Way Interconnection Trunk group for delivery of traffic from Onvoy to Frontier with a utilization level of less than sixty percent (60%) for final trunk groups and eighty-five percent (85%) for high usage trunk groups, unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for all final trunk groups and eighty-five percent (85%) for all high usage trunk groups. In the event Onvoy fails to submit an ASR to disconnect One-Way Interconnection Trunks as required by this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the rates set forth in the Pricing Attachment.
2.3.3 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Frontier to Onvoy, Frontier, at Frontier’s own expense, shall provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA.
Sub-processing 11.1 The data importer shall not subcontract any of its processing operations performed on behalf of the data exporter under the Clauses without the prior written consent of the data exporter. Where the data importer subcontracts its obligations under the Clauses, with the consent of the data exporter, it shall do so only by way of a written agreement with the sub-processor which imposes the same obligations on the sub- processor as are imposed on the data importer under the Clauses. Where the sub-processor fails to fulfil its data protection obligations under such written agreement the data importer shall remain fully liable to the data exporter for the performance of the sub-processor’s obligations under such agreement.
11.2 The prior written contract between the data importer and the sub-processor shall also provide for a third-party beneficiary clause as laid down in Clause 3 for cases where the data subject is not able to bring the claim for compensation referred to in paragraph 1 of Clause 6 against the data exporter or the data importer because they have factually disappeared or have ceased to exist in law or have become insolvent and no successor entity has assumed the entire legal obligations of the data exporter or data importer by contract or by operation of law. Such third-party liability of the sub-processor shall be limited to its own processing operations under the Clauses.
11.3 The provisions relating to data protection aspects for sub-processing of the contract referred to in paragraph 1 shall be governed by the law of the Member State in which the data exporter is established, namely ........................................
11.4 The data exporter shall keep a list of sub-processing agreements concluded under the Clauses and notified by the data importer pursuant to Clause 5(j), which shall be updated at least once a year. The list shall be available to the data exporter’s data protection supervisory authority.
SUB-CONTRACTING 31.1. The Authority approves the appointment of the sub-contractors specified in Schedule 10 (Approved Sub-contractors) in respect of the obligations specified in that Schedule.
31.2. The Contractor may not sub-contract its obligations under the Framework Agreement to other sub-contractors without the prior written consent of the Authority. Sub-contracting of any part of the Framework Agreement shall not relieve the Contractor of any obligation or duty attributable to the Contractor under the Framework Agreement. The Contractor shall be responsible for the acts and omissions of its sub-contractors as though they are its own.
31.3. Where the Contractor enters into a sub-contract the Contractor must ensure that a provision is included which:
31.3.1. requires payment to be made of all sums due by the Contractor to the sub- contractor within a specified period not exceeding 30 days from the receipt of a valid invoice as defined by the sub-contract requirements and provides that, where the Authority has made payment to the Contractor in respect of Services and the sub-contractor’s invoice relates to such Services then, to that extent, the invoice must be treated as valid and, provided the Contractor is not exercising a right of retention or set-off in respect of a breach of contract by the sub-contractor or in respect of a sum otherwise due by the sub-contractor to the Contractor, payment must be made to the sub-contractor without deduction;
31.3.2. notifies the sub-contractor that the sub-contract forms part of a larger contract for the benefit of the Authority and that should the sub-contractor have any difficulty in securing the timely payment of an invoice, that matter may be referred by the sub- contractor to the Authority;
31.3.3. requires that all contracts with subcontractors and suppliers which the subcontractor intends to procure, and which the subcontractor has not before the date of this Framework Agreement, already planned to award to a particular supplier are advertised through the Public Contracts Scotland procurement portal (xxx.xxxxxxxxxxxxxxxxxxxxxxx.xxx.xx) and awarded following a fair, open, transparent and competitive process proportionate to the nature and value of the contract; and
31.3.4. is in the same terms as that set out in this clause 31.3 (including for the avoidance of doubt this clause 31.3.4) subject only to modification to refer to the correct designation of the equivalent party as the Contractor and sub-contractor as the case may be.
31.4. The Contractor shall include in every sub-contract:
31.4.1 a right for the Contractor to terminate that sub-contract if the relevant sub- contractor fails to comply in the performance of its contract with legal obligations in the fields of environmental, social or employment law or if any of the termination events (involving substantial modification of the Contract, contract award despite the existence of exclusion grounds or a serious infringement of EU legal obligations) specified in clause 42.4 occur; and
31.4.2 a requirement that the sub-contractor includes a provision having the same effect as 31.4.1 in any sub-contract which it awards. In this Clause 31.4, ‘sub-contract’ means any contract between two or more contractors, at any stage of remoteness from the Authority in a sub-contracting chain, made wholly or substantially for the purpose of performing (or contributing to the performanace of) the whole or any part of this Framework Agreement.
31.5. Where requested by the Authority, copies of any sub-contract must be sent by the Contractor to the Authority as soon as reasonably practicable.
31.6. Where the Contractor proposes to enter into a sub-contract it must:
31.6.1 advertise its intention to do so in at least one trade journal, and the Public Contracts Scotland Portal; and
31.6.2 follow a procedure leading to the selection of the sub-contractor which ensures reasonable competition following principles of equal treatment, non-discrimination and transparency and which ensures that such procedure is accessible by small and medium enterprises.
Water Supply The system may or may not meet state and local requirements. It is the right and responsibility of Buyer to determine the compliance of the system with state and local requirements. [For additional information on this subject, request the “Water Supply and Waste Disposal Notification” form.]
Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.
Merchant has the power and authority to authorize the automatic funds transfer provided for in the Merchant Agreement;
Transportation Management Tenant shall fully comply with all present or future programs intended to manage parking, transportation or traffic in and around the Building, and in connection therewith, Tenant shall take responsible action for the transportation planning and management of all employees located at the Premises by working directly with Landlord, any governmental transportation management organization or any other transportation-related committees or entities.
Sub-processor For the purposes of this Agreement, the term “Sub-processor” (sometimes referred to as the “Subcontractor”) means a party other than LEA or Provider, who Provider uses for data collection, analytics, storage, or other service to operate and/or improve its software, and who has access to PII.
Logistics The Client shall arrange their own transportation and accommodation, unless Client and Performer agree otherwise. If requested, the Performer shall arrange transport within Ostrava, and provide accommodation in a hotel.
Two-Way Interconnection Trunks 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and PCS, PCS shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Interconnection Trunks from Verizon, PCS shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Interconnection Trunks and the interface specifications at the Point of Interconnection (POI). Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection Trunks.
2.4.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI.
2.4.4 On a semi-annual basis, PCS shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that PCS anticipates Verizon will need to provide during the ensuing two (2) year period to carry traffic from PCS to Verizon and from Verizon to PCS. PCS’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks.
2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.
2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5).
2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.01 during the average time consistent busy hour. Verizon and PCS shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275.
2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three
