In lieu of obtaining performance of Make Sample Clauses

In lieu of obtaining performance of Make. Ready WorkAbTy&T, CLEC at its option may arrange for the performance of such work by a contractor certifiedAbTy&T to work on or in its Facilities. Certification shall be granted based upon reasonable and customary criteria employeAdTb&yT in the selection of its own contract labor. Notwithstanding any other provisions of this Section, CLEC may not employ a contractor to accomplish Make-Ready WorkAiTf &T is likewise precluded from contractor selection under the terms of an applicable joint use Agreement or collective bargaining Agreement. In accordance with Section 4.6.9 above, all Manhole pumping and purging shall be performed by a vendor approvAeTd&bTy.
AutoNDA by SimpleDocs

Related to In lieu of obtaining performance of Make

  • Performance of Obligations The Company shall have performed and complied with all agreements, obligations and conditions contained in this Agreement that are required to be performed or complied with by it on or before the Closing.

  • Excuse from performance of obligations If the Affected Party is rendered wholly or partially unable to perform its obligations under this Agreement because of a Force Majeure Event, it shall be excused from performance of such of its obligations to the extent it is unable to perform on account of such Force Majeure Event; provided that:

  • Performance of Agreement Purchaser shall have performed in all material respects all obligations and agreements and complied in all material respects with all covenants and conditions contained in this Agreement to be performed or complied with by it at or prior to the Closing Date.

  • Performance of Covenants Each covenant or obligation that the Company is required to comply with or to perform at or prior to the Closing shall have been complied with and performed in all material respects.

  • Performance Monitoring A. Performance Monitoring of Subrecipient by County, State of California and/or HUD shall consist of requested and/or required written reporting, as well as onsite monitoring by County, State of California or HUD representatives.

  • CONTRACTOR PERFORMANCE AUDIT The Contractor shall allow the Authorized User to assess Contractor’s performance by providing any materials requested in the Authorized User Agreement (e.g., page load times, response times, uptime, and fail over time). The Authorized User may perform this Contractor performance audit with a third party at its discretion, at the Authorized User’s expense. The Contractor shall perform an independent audit of its Data Centers, at least annually, at Contractor expense. The Contractor will provide a data owner facing audit report upon request by the Authorized User. The Contractor shall identify any confidential, trade secret, or proprietary information in accordance with Appendix B, Section 9(a), Confidential/Trade Secret Materials.

  • PROJECT MILESTONES, REPORTING AND PAYMENTS 15. The milestones for the projects, their relationship to the outputs, expected completion dates, relevant reporting dates and expected payments to be made are set out in bilateral schedules to this Agreement. The Commonwealth will make payments subject to the performance reports demonstrating the relevant milestone has been met.

  • PERFORMANCE OF THE CONTRACT II.1.1 The Contractor shall perform the Contract to the highest professional standards. The Contractor shall have sole responsibility for complying with any legal obligations incumbent on him, notably those resulting from employment, tax and social legislation.

  • Performance of the Services In addition to the Common Articles, it is specified that:

  • Covenants of Performance Measurement No interference. Registry Operator shall not interfere with measurement Probes, including any form of preferential treatment of the requests for the monitored services. Registry Operator shall respond to the measurement tests described in this Specification as it would to any other request from an Internet user (for DNS and RDDS) or registrar (for EPP). ICANN testing registrar. Registry Operator agrees that ICANN will have a testing registrar used for purposes of measuring the SLRs described above. Registry Operator agrees to not provide any differentiated treatment for the testing registrar other than no billing of the transactions. ICANN shall not use the registrar for registering domain names (or other registry objects) for itself or others, except for the purposes of verifying contractual compliance with the conditions described in this Agreement. PUBLIC INTEREST COMMITMENTS Registry Operator will use only ICANN accredited registrars that are party to the Registrar Accreditation Agreement approved by the ICANN Board of Directors on 27 June 2013 in registering domain names. A list of such registrars shall be maintained by ICANN on ICANN’s website. (Intentionally omitted. Registry Operator has not included commitments, statements of intent or business plans provided for in its application to ICANN for the TLD.) Registry Operator agrees to perform the following specific public interest commitments, which commitments shall be enforceable by ICANN and through the Public Interest Commitment Dispute Resolution Process established by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/picdrp), which may be revised in immaterial respects by ICANN from time to time (the “PICDRP”). Registry Operator shall comply with the PICDRP. Registry Operator agrees to implement and adhere to any remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of doubt, the termination of the Registry Agreement pursuant to Section 4.3(e) of the Agreement) following a determination by any PICDRP panel and to be bound by any such determination. Registry Operator will include a provision in its Registry-Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting Registered Name Holders from distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable law, and providing (consistent with applicable law and any related procedures) consequences for such activities including suspension of the domain name. Registry Operator will periodically conduct a technical analysis to assess whether domains in the TLD are being used to perpetrate security threats, such as pharming, phishing, malware, and botnets. Registry Operator will maintain statistical reports on the number of security threats identified and the actions taken as a result of the periodic security checks. Registry Operator will maintain these reports for the term of the Agreement unless a shorter period is required by law or approved by ICANN, and will provide them to ICANN upon request. Registry Operator will operate the TLD in a transparent manner consistent with general principles of openness and non-discrimination by establishing, publishing and adhering to clear registration policies.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!