Traceability of Fibre Cable Sample Clauses

Traceability of Fibre Cable. It was indicated in section 2 Background Information, Part 3 of the RFP file (page 39) that the fibre cable is not traceable. ONTC would like to clarify that the cable is traceable and can be detected using inductive clamp method or other proper locates techniques. Regards, Xxxxx Xxxxx Contract Administrator Xxxxx.Xxxxx@xxxxxxxxxxxxxxxx.xx 705-472-4500 ext. 398 This Agreement made on the day of , 2021, BETWEEN: ONTARIO NORTHLAND TRANSPORTATION COMMISSION (“ONTC”) and (the “Contractor”). ONTC and the Contractor agree as follows: Contract Documents
AutoNDA by SimpleDocs

Related to Traceability of Fibre Cable

  • Technical Feasibility of String While ICANN has encouraged and will continue to encourage universal acceptance of all top-­‐level domain strings across the Internet, certain top-­‐level domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.

  • STABILITY OF AGREEMENT Section 1 No amendment, alteration or variation of the terms or provisions of this Agreement shall bind the parties hereto unless made and executed in writing.

  • Unavailability of Tenor of Benchmark Notwithstanding anything to the contrary herein or in any other Loan Document, at any time (including in connection with the implementation of a Benchmark Replacement), (A) if the then-current Benchmark is a term rate (including the Term SOFR Reference Rate) and either (1) any tenor for such Benchmark is not displayed on a screen or other information service that publishes such rate from time to time as selected by the Administrative Agent in its reasonable discretion or (2) the regulatory supervisor for the administrator of such Xxxxxxxxx has provided a public statement or publication of information announcing that any tenor for such Benchmark is not or will not be representative, then the Administrative Agent may modify the definition of “Interest Period” (or any similar or analogous definition) for any Benchmark settings at or after such time to remove such unavailable or non-representative tenor and (B) if a tenor that was removed pursuant to clause (A) above either (1) is subsequently displayed on a screen or information service for a Benchmark (including a Benchmark Replacement) or (2) is not, or is no longer, subject to an announcement that it is not or will not be representative for a Benchmark (including a Benchmark Replacement), then the Administrative Agent may modify the definition of “Interest Period” (or any similar or analogous definition) for all Benchmark settings at or after such time to reinstate such previously removed tenor.

  • Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-­‐to-­‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.

  • Protection of Customer Data The Supplier shall not delete or remove any proprietary notices contained within or relating to the Customer Data. The Supplier shall not store, copy, disclose, or use the Customer Data except as necessary for the performance by the Supplier of its obligations under this Call Off Contract or as otherwise Approved by the Customer. To the extent that the Customer Data is held and/or Processed by the Supplier, the Supplier shall supply that Customer Data to the Customer as requested by the Customer and in the format (if any) specified by the Customer in the Call Off Order Form and, in any event, as specified by the Customer from time to time in writing. The Supplier shall take responsibility for preserving the integrity of Customer Data and preventing the corruption or loss of Customer Data. The Supplier shall perform secure back-ups of all Customer Data and shall ensure that up-to-date back-ups are stored off-site at an Approved location in accordance with any BCDR Plan or otherwise. The Supplier shall ensure that such back-ups are available to the Customer (or to such other person as the Customer may direct) at all times upon request and are delivered to the Customer at no less than six (6) Monthly intervals (or such other intervals as may be agreed in writing between the Parties). The Supplier shall ensure that any system on which the Supplier holds any Customer Data, including back-up data, is a secure system that complies with the Security Policy and the Security Management Plan (if any). If at any time the Supplier suspects or has reason to believe that the Customer Data is corrupted, lost or sufficiently degraded in any way for any reason, then the Supplier shall notify the Customer immediately and inform the Customer of the remedial action the Supplier proposes to take. If the Customer Data is corrupted, lost or sufficiently degraded as a result of a Default so as to be unusable, the Supplier may: require the Supplier (at the Supplier's expense) to restore or procure the restoration of Customer Data to the extent and in accordance with the requirements specified in Call Off Schedule 8 (Business Continuity and Disaster Recovery) or as otherwise required by the Customer, and the Supplier shall do so as soon as practicable but not later than five (5) Working Days from the date of receipt of the Customer’s notice; and/or itself restore or procure the restoration of Customer Data, and shall be repaid by the Supplier any reasonable expenses incurred in doing so to the extent and in accordance with the requirements specified in Call Off Schedule 8 (Business Continuity and Disaster Recovery) or as otherwise required by the Customer. Confidentiality

  • Equality of Treatment Unless otherwise provided in this Agreement, the persons specified in Article 3, who ordinarily reside in the territory of a Contracting State, shall receive equal treatment with nationals of that Contracting State in the application of the legislation of that Contracting State.

  • Confidentiality of Student Records 1. Student educational records created as a result of this Agreement shall be retained and disseminated in accordance with Family Educational Rights and Privacy Act (FERPA) requirements.

  • Changes in Equipment, Systems, Etc USBFS reserves the right to make changes from time to time, as it deems advisable, relating to its systems, programs, rules, operating schedules and equipment, so long as such changes do not adversely affect the services provided to the Trust under this Agreement.

  • Availability of Records Consultant shall maintain the records supporting this billing for not less than three years following completion of the work under this Agreement. Consultant shall make these records available to authorized personnel of the Town at the Consultant's offices during business hours upon written request of the Town.

  • Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

Time is Money Join Law Insider Premium to draft better contracts faster.