Emergency Funding terms Sample Clauses

Emergency Funding terms. (a) Each of the Lender (or any Lender Affiliate) and the Xxxxx Shareholder shall, within 10 Business Days of receipt of the Funding Offer Request, notify the Borrower of the terms on which it would be prepared to participate in such Emergency Funding (the Offer Terms).
AutoNDA by SimpleDocs

Related to Emergency Funding terms

  • DURATION, AMENDING, TERMINATING, AND MISCELLANEOUS PROVISIONS 3.1 This Agreement shall take effect on 07/01/2021 and shall remain in effect until 06/30/2022.

  • Funding Provisions 4.1 All salaries, fringe benefits, professional development, local travel, supplies for the College and Career Counselor will be provided by Collin College.

  • Emergency Conditions “Emergency Condition” shall mean a condition or situation: (1) that in the judgment of the Party making the claim is imminently likely to endanger life or property; or (2) that, in the case of the Transmission Provider, is imminently likely (as determined in a non-discriminatory manner) to cause a material adverse effect on the security of, or damage to the Transmission System, the Transmission Owner’s Interconnection Facilities or the Transmission Systems of others to which the Transmission System is directly connected; or (3) that, in the case of the Interconnection Customer, is imminently likely (as determined in a non-discriminatory manner) to cause a material adverse effect on the security of, or damage to, the Small Generating Facility or the Interconnection Customer’s Interconnection Facilities. Under Emergency Conditions, the Transmission Owner may immediately suspend interconnection service and temporarily disconnect the Small Generating Facility. The Transmission Provider shall notify the Interconnection Customer promptly when it becomes aware of an Emergency Condition that may reasonably be expected to affect the Interconnection Customer’s operation of the Small Generating Facility. The Interconnection Customer shall notify the Transmission Provider promptly when it becomes aware of an Emergency Condition that may reasonably be expected to affect the Transmission Owner’s Transmission System or other Affected Systems. To the extent information is known, the notification shall describe the Emergency Condition, the extent of the damage or deficiency, the expected effect on the operation of both Parties’ facilities and operations, its anticipated duration, and the necessary corrective action.

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

  • Emergency Thresholds The following matrix presents the emergency thresholds that, if reached by any of the services mentioned above for a TLD, would cause the emergency transition of the Registry for the TLD as specified in Section 2.13 of this Agreement. Critical Function Emergency Threshold DNS Service (all servers) 4-hour total downtime / week DNSSEC proper resolution 4-hour total downtime / week EPP 24-hour total downtime / week RDDS (WHOIS/Web-based WHOIS) 24-hour total downtime / week Data Escrow Breach of the Registry Agreement as described in Specification 2, Part B, Section 6.

  • SAFETY CONDITIONS 1.0 The responsibility for providing for safe working conditions that are in conformance with applicable law and which are within fiscal constraints shall be the District’s. Employees shall be responsible for complying with safety procedures and practices and for reporting any unsafe condition, facility, or equipment of which he/she is aware. The District shall be responsible for informing employees of necessary safety procedures and practices. There shall be no reprisal against an employee for reporting any real or potentially unsafe condition, facility, or equipment.

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

  • Mandatory Conditions (a) Should the Employee or the Union fail to comply with any time limit in the grievance procedure, the grievance will be considered to be abandoned, unless the Parties have mutually agreed in writing to extend the time limits.

  • Emergency Situations If the condition is an emergency, this will be communicated to the Contractor with the request that corrections are to be accomplished immediately. The Contractor shall respond to the notice in emergency situations within twenty-four hours. If the Contractor fails to respond within this time limit, the Owner may correct the defect and charge the Contractor for the Work. If it is determined the complaint is not the responsibility of the Contractor, the Contractor shall be promptly paid for the cost of the corrective work. The Contractor shall give notice in writing to the Owner when corrections have been completed.

  • Emergency Transition Registry Operator agrees that, in the event that any of the emergency thresholds for registry functions set forth in Section 6 of Specification 10 is reached, ICANN may designate an emergency interim registry operator of the registry for the TLD (an “Emergency Operator”) in accordance with ICANN’s registry transition process (available at <xxxx://xxx.xxxxx.xxx/en/resources/registries/transition-­‐processes>) (as the same may be amended from time to time, the “Registry Transition Process”) until such time as Registry Operator has demonstrated to ICANN’s reasonable satisfaction that it can resume operation of the registry for the TLD without the reoccurrence of such failure. Following such demonstration, Registry Operator may transition back into operation of the registry for the TLD pursuant to the procedures set out in the Registry Transition Process, provided that Registry Operator pays all reasonable costs incurred (i) by ICANN as a result of the designation of the Emergency Operator and (ii) by the Emergency Operator in connection with the operation of the registry for the TLD, which costs shall be documented in reasonable detail in records that shall be made available to Registry Operator. In the event ICANN designates an Emergency Operator pursuant to this Section 2.13 and the Registry Transition Process, Registry Operator shall provide ICANN or any such Emergency Operator 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 Emergency Operator. 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 that an Emergency Operator is designated pursuant to this Section 2.13. In addition, in the event of such failure, ICANN shall retain and may enforce its rights under the Continued Operations Instrument.

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