Regulatory Event New Taxes If, after the Effective Date, a Regulatory Event occurs or New Taxes are imposed, and such event or taxes have a direct, material and adverse effect on the economic benefits to a Party of this ESA, the affected Party shall send written notice to the other Party, setting forth the Regulatory Event or New Taxes and reasonably demonstrating the effect of the same on the affected Party. Upon delivery of such notice, the Parties shall use reasonable efforts to negotiate an amendment to this ESA to mitigate such effect. Alternatively, if as a direct result of such a Regulatory Event or New Taxes, the Competitive Supplier incurs additional, material costs, the Competitive Supplier shall provide a written notice to the Town that documents: a) the effective date of the Regulatory Event or New Taxes; b) a detailed explanation and reasonable demonstration of the material costs incurred as a result of the Regulatory Event or New Taxes; c) the timing of the cost impact to be incurred by the Competitive Supplier; d) the proposed price increase per kWh to be passed on to Participating Consumers; and e) a proposed plan for coordinating with the Local Distributor for an increase in the price per kWh that is billed by the Local Distributor, designed to reimburse the Competitive Supplier for such cost impact. If the Town and the Competitive supplier cannot agree on the amendment to this ESA or reimbursement contemplated by this section, the matter may be subject to dispute resolution in accordance with section 12.2. In no event shall a price change become effective without providing Participating Consumers with a 30-day advance notice of the price change.
Expected Outcomes Each Faculty member as a result of the five- year TEC process will: • Gather and review feedback from student evaluations in a minimum of 3 different classes during the five-year cycle. • Gather data on courses and/or program to determine trends and opportunities to improve student success. • Gather and review feedback from cohort member classroom observations. Each member of the TEC will visit the classroom at least once within the 5 year cycle and provide written and oral feedback to the TEC member. • Complete a self-evaluation based upon student evaluations, data trends, peer feedback and learning insights to fulfill the professional development goals. This is done at the conclusion of the five-year cycle. • Meet with their division xxxx at the conclusion of the five-year cycle to review their completed self-evaluation based upon peer feedback, data, student evaluations, and professional development goals; and discuss the administrative evaluation which must include at least one classroom observation.
Force Majeure Event 16.1 If a Force Majeure Event gives rise to a failure or delay in either party performing any obligation under this Agreement (other than any obligation to make a payment), that obligation will be suspended for the duration of the Force Majeure Event.
REGULATORY EVENT If a Regulatory Event occurs, the Parties shall use their best efforts to reform this ESA to give effect to the original intent of the Parties. If a Regulatory Event affects Competitive Supplier and Competitive Supplier incurs excess costs as a result thereof, such amount shall be allocated to and collected from Participating Consumers on a per kWh basis through applicable monthly invoice(s).
Cyber incident damage assessment activities If DoD elects to conduct a damage assessment, the Contracting Officer will request that the Contractor provide all of the damage assessment information gathered in accordance with paragraph (e) of this clause.
Name Collision Occurrence Assessment 6.2.1 Registry Operator shall not activate any names in the DNS zone for the Registry TLD except in compliance with a Name Collision Occurrence Assessment provided by ICANN regarding the Registry TLD. Registry Operator will either (A) implement the mitigation measures described in its Name Collision Occurrence Assessment before activating any second-‐level domain name, or (B) block those second-‐level domain names for which the mitigation measures as described in the Name Collision Occurrence Assessment have not been implemented and proceed with activating names that are not listed in the Assessment.