Plan Termination by Political Subdivision Sample Clauses

Plan Termination by Political Subdivision. A Participating Employer may terminate its participation in the Plan if it takes the following actions:
AutoNDA by SimpleDocs

Related to Plan Termination by Political Subdivision

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

  • 341 Termination by Forest Service (a) The Chief or the Chief’s designee may unilaterally terminate this contract, in whole or in part, for any of the reasons set forth in paragraph (a) of B8.33.

  • 222 Termination by Forest Service This contract may be terminated by written notice from Contracting Officer, if there is Catastrophic Damage and Purchaser does not agree, under B8.32, within 30 days of receipt from Contracting Officer of contract modifications proposed to permit the harvest of the catastrophe- affected timber.

  • Termination by University A. The University may terminate this contract if the student fails to fulfill financial obligations specified in this contract or if the student violates any of the terms of this contract or published University or University Housing policy. In such cases, the student will be charged a cancellation fee of 35% of the remainder of contract price plus prorate for the time occupied.

  • Termination by City Notwithstanding any other term, provision or conditions of this Agreement, subject only to prior written notification to Licensee or its successor-in- interest, this Agreement is revocable by the City if:

  • Termination for Non-Appropriation by DIR DIR may terminate Contract if funds sufficient to pay its obligations under the Contract are not appropriated: by the i) Texas legislature or ii) by budget execution authority provisioned to the Governor or the Legislative Budget Board as provided in Chapter 317, Texas Government Code. In the event of non-appropriation, Vendor and/or Order Fulfiller will be provided thirty (30) calendar days written notice of intent to terminate. In the event of such termination, DIR will not be considered to be in default or breach under this Contract, nor shall it be liable for any further payments ordinarily due under this Contract, nor shall it be liable for any damages or any other amounts which are caused by or associated with such termination.

  • Termination by Provider This Agreement may be terminated by Provider in accordance with the following: (a) except for SAP’s breach of its obligations under Sections 8 or 9, thirty (30) days after Provider gives SAP notice of SAP’s breach of any provision of the Agreement, unless SAP has cured such breach during such thirty (30) day period; (b) immediately if (1) SAP commences negotiations with one or more of its creditors with a view to rescheduling major parts of its indebtedness or (2) SAP files for bankruptcy, has a petition for bankruptcy filed on its behalf which is not dismissed within sixty days of filing, becomes insolvent, or makes an assignment for the benefit of creditors; and/or (3) SAP breaches its obligations under Sections 8 and/or 9 [Intellectual Property Ownership, Confidentiality].

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

  • COMMUTE TRIP REDUCTION AND PARKING 24.1 The Employer will continue to encourage but not require employees to use alternate means of transportation to commute to and from work consistent with the Commute Trip Reduction (CTR) law and the needs of the Employer and the community.

  • Emergency Escalation initiated by ICANN Upon reaching 10% of the Emergency thresholds as described in Section 6 of this Specification, ICANN’s emergency operations will initiate an Emergency Escalation with the relevant Registry Operator. An Emergency Escalation consists of the following minimum elements: electronic (i.e., email or SMS) and/or voice contact notification to the Registry Operator’s emergency operations department with detailed information concerning the issue being escalated, including evidence of monitoring failures, cooperative trouble-­‐shooting of the monitoring failure between ICANN staff and the Registry Operator, and the commitment to begin the process of rectifying issues with either the monitoring service or the service being monitoring.

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