Consent to Use of Another MEP & FP Engineer upon Termination for Default Sample Clauses

Consent to Use of Another MEP & FP Engineer upon Termination for Default. If the MEP & FP Engineer is performing architectural design services as may be incidental to its architectural design services, then in the event of termination under this Contract due to the default of the MEP & FP Engineer, the MEP & FP Engineer consents to the School District’s selection of another MEP & FP Engineer of the School District’s choice to assist the School District in any way in completing the assigned Project(s). The MEP & FP Engineer further agrees to cooperate and provide any information requested by the School District in connection with the completion of the assigned Project(s). The MEP & FP Engineer authorizes the making of any reasonable changes to the design of the assigned Project(s) by the School District and such other MEP & FP Engineer as the School District may desire. In the event that another MEP & FP Engineer is selected or changes are made to the design of the assigned Project(s), the School District agrees to indemnify and hold harmless the MEP & FP Engineer and its officers and employees from any liability arising from use and changes to the design and design documents, including costs of litigation, reasonable attorneys’ fees and time spent by the MEP & FP Engineer and its Subconsultants attending depositions and court proceedings.
AutoNDA by SimpleDocs

Related to Consent to Use of Another MEP & FP Engineer upon Termination for Default

  • Termination for Concessionaire Default 37.1.1 Save as otherwise provided in this Agreement, in the event that any of the defaults specified below shall have occurred, and the Concessionaire fails to cure the default within the Cure Period set forth below, or where no Cure Period is specified, then within a Cure Period of 60 (sixty) days, the Concessionaire shall be deemed to be in default of this Agreement (the “Concessionaire Default”), unless the default has occurred solely as a result of any breach of this Agreement by the Authority or due to Force Majeure. The defaults referred to herein shall include:

  • SUSPENSION & TERMINATION FOR DEFAULT Enterprise Services may suspend Contractor’s operations under this Master Contract immediately by written cure notice of any default. Suspension shall continue until the default is remedied to Enterprise Services’ reasonable satisfaction; Provided, however, that, if after thirty (30) days from such a suspension notice, Contractor remains in default, Enterprise Services may terminate Contractor’s rights under this Master Contract. All of Contractor’s obligations to Enterprise Services and Purchasers survive termination of Contractor’s rights under this Master Contract, until such obligations have been fulfilled.

  • Compensation for default by the Concessionaire Subject to the provisions of Clause 35.6, in the event of the Concessionaire being in material default or breach of this Agreement, it shall pay to the Authority by way of compensation, all direct costs suffered or incurred by the Authority as a consequence of such material default or breach, within 30 (thirty) days of receipt of the demand supported by necessary particulars thereof; provided that no compensation shall be payable under this Clause 35.1 for any material breach or default in respect of which Damages are expressly specified and payable under this Agreement.

  • Termination for Default The County may, by written notice to the Contractor terminate this contract for default in whole or in part (delivery orders, if applicable) if the Contractor fails to:

  • Erroneous Termination for Default If, after notice of termination of Vendor’s right to proceed under the provisions of this clause, it is determined for any reason that the contract was not in default, or that the delay was excusable under the provisions of the prior paragraph (Excuse for Nonperformance or Delayed Performance), the rights and obligations of the parties shall be the same as if the notice of termination had been one of termination for convenience.

  • Transition of Registry upon Termination of Agreement Upon expiration of the Term pursuant to Section 4.1 or Section 4.2 or any termination of this Agreement pursuant to Section 4.3 or Section 4.4, Registry Operator shall provide ICANN or any successor registry operator that may be designated by ICANN for the TLD in accordance with this Section 4.5 with all data (including the data escrowed in accordance with Section 2.3) regarding operations of the registry for the TLD necessary to maintain operations and registry functions that may be reasonably requested by ICANN or such successor registry operator. After consultation with Registry Operator, ICANN shall determine whether or not to transition operation of the TLD to a successor registry operator in its sole discretion and in conformance with the Registry Transition Process; provided, however, that (i) ICANN will take into consideration any intellectual property rights of Registry Operator (as communicated to ICANN by Registry Operator) in determining whether to transition operation of the TLD to a successor registry operator and (ii) if Registry Operator demonstrates to ICANN’s reasonable satisfaction that (A) all domain name registrations in the TLD are registered to, and maintained by, Registry Operator or its Affiliates for their exclusive use, (B) Registry Operator does not sell, distribute or transfer control or use of any registrations in the TLD to any third party that is not an Affiliate of Registry Operator, and (C) transitioning operation of the TLD is not necessary to protect the public interest, then ICANN may not transition operation of the TLD to a successor registry operator upon the expiration or termination of this Agreement without the consent of Registry Operator (which shall not be unreasonably withheld, conditioned or delayed). For the avoidance of doubt, the foregoing sentence shall not prohibit ICANN from delegating the TLD pursuant to a future application process for the delegation of top-­‐level domains, subject to any processes and objection procedures instituted by ICANN in connection with such application process intended to protect the rights of third parties. Registry Operator agrees that ICANN may make any changes it deems necessary to the IANA database for DNS and WHOIS records with respect to the TLD in the event of a transition of the TLD pursuant to this Section 4.5. In addition, ICANN or its designee shall retain and may enforce its rights under the Continued Operations Instrument for the maintenance and operation of the TLD, regardless of the reason for termination or expiration of this Agreement.

  • Transition of Registry upon Termination of Agreement text for intergovernmental organizations or governmental entities or other special circumstances: “Transition of Registry upon Termination of Agreement. Upon expiration of the Term pursuant to Section 4.1 or Section 4.2 or any termination of this Agreement pursuant to Section 4.3 or Section 4.4, in connection with ICANN’s designation of a successor registry operator for the TLD, Registry Operator and ICANN agree to consult each other and work cooperatively to facilitate and implement the transition of the TLD in accordance with this Section 4.5. After consultation with Registry Operator, ICANN shall determine whether or not to transition operation of the TLD to a successor registry operator in its sole discretion and in conformance with the Registry Transition Process. In the event ICANN determines to transition operation of the TLD to a successor registry operator, upon Registry Operator’s consent (which shall not be unreasonably withheld, conditioned or delayed), Registry Operator shall provide ICANN or such successor registry operator for the TLD with any data regarding operations of the TLD necessary to maintain operations and registry functions that may be reasonably requested by ICANN or such successor registry operator in addition to data escrowed in accordance with Section 2.3 hereof. In the event that Registry Operator does not consent to provide such data, any registry data related to the TLD shall be returned to Registry Operator, unless otherwise agreed upon by the parties. Registry Operator agrees that ICANN may make any changes it deems necessary to the IANA database for DNS and WHOIS records with respect to the TLD in the event of a transition of the TLD pursuant to this Section 4.5. In addition, ICANN or its designee shall retain and may enforce its rights under the Continued Operations Instrument, regardless of the reason for termination or expiration of this Agreement.”]

  • Withdrawal of Property from Market or Termination of Discussions Potential Investor acknowledges that the Property has been offered for sale subject to withdrawal of the Property from the market at any time or rejection of any offer because of the terms thereof, or for any other reason whatsoever, without notice, as well as the termination of discussions with any party at any time without notice for any reason whatsoever.

  • Termination for continuing Force Majeure Event Either Party may, by written notice to the other, terminate this Framework Agreement if a Force Majeure Event endures for a continuous period of more than one hundred and twenty (120) Working Days.

  • Recovery upon Termination H6.1 On the termination of the Contract for any reason, the Contractor shall at its cost:

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