Transportation by Train Sample Clauses

Transportation by Train. When deadheading by train, the following provisions shall be met: • Deadhead duration will not be planned for more than four (4) hours
AutoNDA by SimpleDocs
Transportation by Train. Transportation by train can be arranged either by the Seller or Buyer. Specifications for the goods station(s) are listed in Annex 4.

Related to Transportation by Train

  • Termination by Regulators All obligations under this Agreement shall be terminated, except to the extent determined that continuation of this Agreement is necessary for the continued operation of the Bank: (1) by the Director of the Office of Thrift Supervision (the "Director") or his or her designee, at the time the Federal Deposit Insurance Corporation enters into an agreement to provide assistance to or on behalf of the Bank under the authority contained in Section 13(c) of the FDIA; or (2) by the Director or his or her designee, at the time the Director or his or her designee approves a supervisory merger to resolve problems related to operation of the Bank or when the Bank is determined by the Director to be in an unsafe or unsound condition. Any rights of the parties that have already vested, however, shall not be affected by any such action.

  • Termination by ICANN (a) ICANN may, upon notice to Registry Operator, terminate this Agreement if: (i) Registry Operator fails to cure (A) any fundamental and material breach of Registry Operator’s representations and warranties set forth in Article 1 or covenants set forth in Article 2, or (B) any breach of Registry Operator’s payment obligations set forth in Article 6 of this Agreement, each within thirty (30) calendar days after ICANN gives Registry Operator notice of such breach, which notice will include with specificity the details of the alleged breach, (ii) an arbitrator or court of competent jurisdiction has finally determined that Registry Operator is in fundamental and material breach of such covenant(s) or in breach of its payment obligations, and (iii) Registry Operator fails to comply with such determination and cure such breach within ten (10) calendar days or such other time period as may be determined by the arbitrator or court of competent jurisdiction. (b) ICANN may, upon notice to Registry Operator, terminate this Agreement if Registry Operator fails to complete all testing and procedures (identified by ICANN in writing to Registry Operator prior to the date hereof) for delegation of the TLD into the root zone within twelve (12) months of the Effective Date. Registry Operator may request an extension for up to additional twelve (12) months for delegation if it can demonstrate, to ICANN’s reasonable satisfaction, that Registry Operator is working diligently and in good faith toward successfully completing the steps necessary for delegation of the TLD. Any fees paid by Registry Operator to ICANN prior to such termination date shall be retained by ICANN in full. (c) ICANN may, upon notice to Registry Operator, terminate this Agreement if (i) Registry Operator fails to cure a material breach of Registry Operator’s obligations set forth in Section 2.12 of this Agreement within thirty (30) calendar days of delivery of notice of such breach by ICANN, or if the Continued Operations Instrument is not in effect for greater than sixty (60) consecutive calendar days at any time following the Effective Date, (ii) an arbitrator or court of competent jurisdiction has finally determined that Registry Operator is in material breach of such covenant, and (iii) Registry Operator fails to cure such breach within ten (10) calendar days or such other time period as may be determined by the arbitrator or court of competent jurisdiction. (d) ICANN may, upon notice to Registry Operator, terminate this Agreement if (i) Registry Operator makes an assignment for the benefit of creditors or similar act, (ii) attachment, garnishment or similar proceedings are commenced against Registry Operator, which proceedings are a material threat to Registry Operator’s ability to operate the registry for the TLD, and are not dismissed within sixty (60) calendar days of their commencement, (iii) a trustee, receiver, liquidator or equivalent is appointed in place of Registry Operator or maintains control over any of Registry Operator’s property, (iv) execution is levied upon any material property of Registry Operator, (v) proceedings are instituted by or against Registry Operator under any bankruptcy, insolvency, reorganization or other laws relating to the relief of debtors and such proceedings are not dismissed within sixty (60) calendar days of their commencement, or (vi) Registry Operator files for protection under the United States Bankruptcy Code, 11 U.S.C. Section 101, et seq., or a foreign equivalent or liquidates, dissolves or otherwise discontinues its operations or the operation of the TLD. (e) ICANN may, upon thirty (30) calendar days’ notice to Registry Operator, terminate this Agreement pursuant to Section 2 of Specification 7 or Sections 2 and 3 of Specification 11, subject to Registry Operator’s right to challenge such termination as set forth in the applicable procedure described therein. (f) ICANN may, upon notice to Registry Operator, terminate this Agreement if (i) Registry Operator knowingly employs any officer who is convicted of a misdemeanor related to financial activities or of any felony, or is judged by a court of competent jurisdiction to have committed fraud or breach of fiduciary duty, or is the subject of a judicial determination that ICANN reasonably deems as the substantive equivalent of any of the foregoing and such officer is not terminated within thirty (30) calendar days of Registry Operator’s knowledge of the foregoing, or (ii) any member of Registry Operator’s board of directors or similar governing body is convicted of a misdemeanor related to financial activities or of any felony, or is judged by a court of competent jurisdiction to have committed fraud or breach of fiduciary duty, or is the subject of a judicial determination that ICANN reasonably deems as the substantive equivalent of any of the foregoing and such member is not removed from Registry Operator’s board of directors or similar governing body within thirty (30) calendar days of Registry Operator’s knowledge of the foregoing. (g) ICANN may, upon thirty (30) calendar days’ notice to Registry Operator, terminate this Agreement as specified in Section 7.5. (h) [Applicable to intergovernmental organizations or governmental entities only.] ICANN may terminate this Agreement pursuant to Section 7.16.

  • No Limitation by Insurance The obligations under this Article 26 will not be limited in any way by any limitation of subcontractor’s insurance.

  • Termination by the University i) The university may terminate this agreement under the following circumstances:

  • Cooperation by the Company If any Shareholder shall transfer any Registrable Securities pursuant to Rule 144, the Company shall cooperate, to the extent commercially reasonable, with such Shareholder and shall provide to such Shareholder such information as such Shareholder shall reasonably request.

  • Cooperation by Holders The Partnership shall have no obligation to include Registrable Securities of a Holder in a Registration Statement or in an Underwritten Offering pursuant to Section 2.03(a) if such Holder has failed to timely furnish such information that the Partnership determines, after consultation with its counsel, is reasonably required in order for any registration statement or prospectus supplement, as applicable, to comply with the Securities Act.

  • Termination by University (a) If LICENSEE fails to perform or violates any term of this Agreement, then UNIVERSITY may give written notice of default (“Notice of Default”) to LICENSEE. If LICENSEE fails to cure the default within sixty (60) days of the Notice of Default, UNIVERSITY may terminate this Agreement and the license granted herein by a second written notice (“Notice of Termination”) to LICENSEE. If a Notice of Termination is sent to LICENSEE, this Agreement shall automatically terminate on the effective date of that notice. Termination shall not relieve LICENSEE of its obligation to pay any fees owed at the time of termination and shall not impair any accrued right of UNIVERSITY. During the term of any such Notice of Default or period to cure, to the extent the default at issue is a failure to pay past or ongoing Patent Costs as provided for under this Agreement, UNIVERSITY shall have no obligation to incur any new Patent Costs under this Agreement and shall have no obligation to further prosecute Patent Rights or file any new patents under Patent Rights. (b) This Agreement will terminate immediately, without the obligation to provide sixty (60) days’ notice as set forth in Paragraph 7.1(a), if LICENSEE files a claim including in any way the assertion that any portion of UNIVERSITY’s Patent Rights is invalid or unenforceable where the filing is by the LICENSEE, a third party on behalf of the LICENSEE, or a third party at the written urging of the LICENSEE. (c) This Agreement shall automatically terminate without the obligation to provide sixty (60) days’ notice as set forth in Paragraph 7.1 (a) upon the filing of a petition for relief under the United States Bankruptcy Code by or against the LICENSEE as a debtor or alleged debtor.

  • TERMINATION BY MPS MPS further reserves the right to terminate this Contract at any time for any reason by giving Contractor written notice by Registered or Certified Mail of such termination. MPS will attempt to give Contractor 20 days’ notice, but reserves the right to give immediate notice. In the event of said termination, Contractor shall reduce its activities hereunder, as mutually agreed to, upon receipt of said notice. Upon said termination, Contractor shall be paid for all services rendered through the date of termination, including any retainage. This section also applies should the Milwaukee Board of School Directors fail to appropriate additional monies required for the completion of the Contract.

  • Termination by CAISO Subject to Section 5.2, the CAISO may terminate this Agreement by giving written notice of termination in the event that the Participating Load commits any material default under this Agreement and/or the CAISO Tariff which, if capable of being remedied, is not remedied within thirty (30) days after the CAISO has given, to the Participating Load, written notice of the default, unless excused by reason of Uncontrollable Forces in accordance with Article X of this Agreement. With respect to any notice of termination given pursuant to this Section, the CAISO must file a timely notice of termination with FERC, if this Agreement was filed with FERC, or must otherwise comply with the requirements of FERC Order No. 2001 and related FERC orders. The filing of the notice of termination by the CAISO with FERC will be considered timely if: (1) the filing of the notice of termination is made after the preconditions for termination have been met, and the CAISO files the notice of termination within sixty (60) days after issuance of the notice of default; or (2) the CAISO files the notice of termination in accordance with the requirements of FERC Order No. 2001. This Agreement shall terminate upon acceptance by FERC of such a notice of termination, if filed with FERC, or thirty (30) days after the date of the CAISO’s notice of default, if terminated in accordance with the requirements of FERC Order No. 2001 and related FERC orders.

  • Emergency Escalation initiated by Registrars Registry Operator will maintain an emergency operations department prepared to handle emergency requests from registrars. In the event that a registrar is unable to conduct EPP transactions with the registry for the TLD because of a fault with the Registry Service and is unable to either contact (through ICANN mandated methods of communication) the Registry Operator, or the Registry Operator is unable or unwilling to address the fault, the registrar may initiate an emergency escalation to the emergency operations department of ICANN. ICANN then may initiate an emergency escalation with the Registry Operator as explained above.

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