Restriction on self-performance Sample Clauses

Restriction on self-performance. Unless prior written approval is provided by the Principal's Representative to the Integration Partner (which approval may be given or withheld by the Principal's Representative in its sole discretion), neither the Integration Partner, its Personnel nor any related body corporate (as defined in section 50 of the Corporations Act, but also including any body corporate that is related to the Integration Partner by virtue of the Integration Partner's shareholding or other direct or indirect economic or commercial interest in that body corporate) of: (a) the Integration Partner; (b) any entity that forms a part of the Integration Partner; or (c) any Subcontractor, may: (d) perform any function specified in Schedule 13 in respect of a Project or the Program; (e) have any direct or indirect involvement in a Project, a Project Contract or the Program other than for the Principal; or (f) provide services to or advise any other person in relation to a Project, a Project Contract or the Program. Any approval to self-perform may be given subject to any conditions the Principal sees fit, including the entering into of contracts between the Principal and the Integration Partner for the performance of the relevant work.
AutoNDA by SimpleDocs

Related to Restriction on self-performance

  • Prohibition of Performance Requirements 1. The provisions of the Agreement on Trade-Related Investment Measures in Annex 1A to the WTO Agreement (TRIMs), which are not specifically mentioned in or modified by this Agreement, shall apply, mutatis mutandis, to this Agreement. 2. Member States shall undertake joint assessment on performance requirements no later than 2 years from the date of entry into force of this Agreement. The aim of such assessment shall include reviewing existing performance requirements and considering the need for additional commitments under this Article.

  • 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: (a) the suspension of performance shall be of no greater scope and of no longer duration than is reasonably required by the Force Majeure Event; (b) the Affected Party shall make all reasonable efforts to mitigate or limit damage to the other Party arising out of or as a result of the existence or occurrence of such Force Majeure Event and to cure the same with due diligence; and (c) when the Affected Party is able to resume performance of its obligations under this Agreement, it shall give to the other Party notice to that effect and shall promptly resume performance of its obligations hereunder.

  • 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.

  • Excuse for Nonperformance or Delayed Performance Except with respect to defaults of subcontractors, Contractor/Vendor shall not be in default by reason of any failure in performance of this contract in accordance with its terms (including any failure by Contractor/Vendor to make progress in the prosecution of the work hereunder which endangers such performance) if Contractor/Vendor has notified the Commission or designee within 15 days after the cause of the delay and the failure arises out of causes such as: acts of God; acts of the public enemy; acts of the State and any other governmental entity in its sovereign or contractual capacity; fires; floods; epidemics; quarantine restrictions; strikes or other labor disputes; freight embargoes; or unusually severe weather. If the failure to perform is caused by the failure of a subcontractor to perform or to make progress, and if such failure arises out of causes similar to those set forth above, Contractor/Vendor shall not be deemed to be in default, unless the services to be furnished by the subcontractor were reasonably obtainable from other sources in sufficient time to permit Contractor to meet the contract requirements. Upon request of Contractor, the Commission or designee shall ascertain the facts and extent of such failure, and, if such officer determines that any failure to perform was occasioned by any one or more of the excusable causes, and that, but for the excusable cause, Contractor’s progress and performance would have met the terms of the contract, the delivery schedule shall be revised accordingly, subject to the rights of the State under the clause entitled (in fixed-price contracts, “Termination for Convenience,” in cost-reimbursement contracts, “Termination”). (As used in this Paragraph of this clause, the term “subcontractor” means subcontractor at any tier).

  • Vesting and Lapse of Restrictions Subject to Sections 2.2(a) and 2.2(c), the Award shall vest and Restrictions shall lapse in accordance with the vesting schedule set forth on the Grant Notice.

  • Performance of Covenants and Satisfaction of Conditions To use its reasonable best efforts to do and perform all things required to be done or performed under this Agreement by the Company prior to each Closing Date and to satisfy all conditions precedent to the delivery of the Firm Stock and the Optional Stock.

  • Representations, Performance All representations and warranties of Buyer contained in this Agreement shall be true and correct in all respects at and as of the date hereof, and shall be repeated and shall be true and correct in all respects on and as of the Closing Date with the same effect as though made on and as of the Closing Date.

  • Performance of Agreements and Covenants Each and all of the agreements and covenants of Buyer to be performed and complied with pursuant to this Agreement and the other agreements contemplated hereby prior to the Effective Time shall have been duly performed and complied with in all material respects.

  • Contractor’s Performance Warranties Contractor represents and warrants to the State that: (i) Each and all of the services shall be performed in a timely, diligent, professional and skillful manner, in accordance with the highest professional or technical standards applicable to such services, by qualified persons with the technical skills, training and experience to perform such services in the planned environment. (ii) Any time software is delivered to the State, whether delivered via electronic media or the internet, no portion of such software or the media upon which it is stored or delivered will have any type of software routine or other element which is designed to facilitate unauthorized access to or intrusion upon; or unrequested disabling or erasure of; or unauthorized interference with the operation of any hardware, software, data or peripheral equipment of or utilized by the State. Without limiting the generality of the foregoing, if the State believes that harmful code may be present in any software delivered hereunder, Contractor will, upon State’s request, provide a new or clean install of the software. Notwithstanding the foregoing, Contractor assumes no responsibility for the State’s negligence or failure to protect data from viruses, or any unintended modification, destruction or disclosure. (iii) To the extent Contractor resells commercial hardware or software it purchased from a third party, Contractor will, to the extent it is legally able to do so, pass through any such third party warranties to the State and will reasonably cooperate in enforcing them. Such warranty pass-through will not relieve the Contractor from Contractor’s warranty obligations set forth herein.

  • Limitations of Performance The Custodian shall not be responsible under this Agreement for any failure to perform its duties, and shall not be liable hereunder for any loss or damage in association with such failure to perform, for or in consequence of the following causes:

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