Termination on Material Default 30.2.1 The Authority may terminate this Framework Agreement for material Default by issuing a Termination Notice to the Supplier where:
Program Requirements Provided At No Charge to the Judicial Council A. The Contractor shall provide the following items during the Program at no charge to the Judicial Council:
Termination on Default The Authority may terminate this Framework Agreement by serving written notice on the Supplier with effect from the date specified in such notice where the Supplier commits a Material Default and if:
H2 Termination on Default H2.1 The Authority may terminate the Contract by written notice in accordance with clause A5.2 (Notices) to the Contractor with immediate effect if the Contractor commits a Default and if:
Default Events (a) Any material breach of the Funding Agreement by the Recipient, including those set out below, will be an event of default (“Default Event”):
Certification of Funds; Budget and Fiscal Provisions; Termination in the Event of Non-Appropriation This Agreement is subject to the budget and fiscal provisions of the City’s Charter. Charges will accrue only after prior written authorization certified by the Controller, and the amount of City’s obligation hereunder shall not at any time exceed the amount certified for the purpose and period stated in such advance authorization. This Agreement will terminate without penalty, liability or expense of any kind to City at the end of any fiscal year if funds are not appropriated for the next succeeding fiscal year. If funds are appropriated for a portion of the fiscal year, this Agreement will terminate, without penalty, liability or expense of any kind at the end of the term for which funds are appropriated. City has no obligation to make appropriations for this Agreement in lieu of appropriations for new or other agreements. City budget decisions are subject to the discretion of the Mayor and the Board of Supervisors. Contractor’s assumption of risk of possible non-appropriation is part of the consideration for this Agreement. THIS SECTION CONTROLS AGAINST ANY AND ALL OTHER PROVISIONS OF THIS AGREEMENT.
DISTRIBUTION AND DEFAULT SERVICE TERMS AND CONDITIONS Capacity Pipeline Capacity, Underground Storage Withdrawal Capacity, Underground Storage Capacity and Peaking Capacity as defined in these Terms and Conditions. Capacity Allocators The proportion of the Customer’s Total Capacity Quantity that comprises Pipeline Capacity, Underground Storage Withdrawal Capacity and Peaking Capacity. City Gate The interconnection between a Delivering Pipeline and the Company’s distribution facilities. Company Eversource Gas Company of Massachusetts d/b/a Eversource Energy Company Gas Allowance The difference between the sum of all amounts of Gas received into the Company’s distribution system and the sum of all amounts of Gas delivered from the Company’s distribution system as calculated by the Company for the most recent twelve (12) month period ending July 31. Such difference shall include, but not be limited to, Gas consumed by the Company for its own purposes, line losses and Gas vented and lost as a result of an event of Force Majeure, excluding gas otherwise accounted for. Company-Managed Supplies Capacity contracts held and managed by the Company in accordance with governing tariffs, but made available to the Supplier pursuant to Section 13.9 of these Terms and Conditions, including supply-sharing contracts and load- management contracts. Consumption Algorithm A mathematical formula used to estimate a Customer’s daily consumption. Critical Day In accordance with Section 19.0 of these Terms and Conditions, a Day declared at any time by the Company in its reasonable discretion when unusual operating conditions may jeopardize operation of the Company’s distribution system.
Default Events and Termination 18.1 Each of the following circumstances shall constitute a General Default:
Train Operator Events of Default The following are Train Operator Events of Default:
Developer Event of Default Any of the following events shall constitute an event of default by the Developer ("Developer Event of Default") unless such event has occurred as a result of a Force Majeure Event or the Authority Event of Default or any governmental action for reasons other than any breach, default or lapse on the part of the Developer:
