Unavailability Events and Service Failures Sample Clauses

Unavailability Events and Service Failures. (a) After the occurrence of each Unavailability Event, the Department will be entitled to claim an Unavailability Penalty, as applicable to the Unavailability Event in accordance with this Article 11 (Unavailability Events and Service Failures).
AutoNDA by SimpleDocs

Related to Unavailability Events and Service Failures

  • Unavailability of Services You understand and agree that the Services may at times be temporarily unavailable due to system maintenance or technical difficulties. In the event any of the services included in our Mobile Banking Services are unavailable, you acknowledge that you can deposit an original check at our branches or through ATM that accepts your deposit, or by mail.

  • Force Majeure Events a) Neither Party shall be responsible or liable for or deemed in breach hereof because of any delay or failure in the performance of its obligations hereunder (except for obligations to pay money due prior to occurrence of Force Majeure events under this Agreement) or failure to meet milestone dates due to any event or circumstance (a "Force Majeure Event") beyond the reasonable control of the Party experiencing such delay or failure, including the occurrence of any of the following:

  • Reports of unusual occurrence The Contractor shall, during the Maintenance Period, prior to the close of each day, send to the Authority and the Authority’s Engineer, by facsimile or e- mail, a report stating accidents and unusual occurrences on the Project Highway relating to the safety and security of the Users and Project Highway. A monthly summary of such reports shall also be sent within 3 (three) business days of the closing of month. For the purposes of this Clause 15.4, accidents and unusual occurrences on the Project Highway shall include:

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only) The wind generation facility shall, at a minimum, be required to provide the Transmission Provider with site-specific meteorological data including: • Temperature (degrees Fahrenheit) • Wind speed (meters/second) • Wind direction (degrees from True North) • Atmosphere pressure (hectopascals) • Forced outage data (wind turbine and MW unavailability)

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

  • Failure to Maintain Financial Viability The System Agency may terminate the Contract if, in its sole discretion, the System Agency has a good faith belief that Grantee no longer maintains the financial viability required to complete the services and Deliverables, or otherwise fully perform its responsibilities under the Contract.

  • Availability of Services CBT agrees not to discontinue or refuse to provide any service provided or required hereunder other than in accordance with the terms of this Agreement, or unless required by the Commission.

  • Reporting of Non-Force Majeure Events Each Party (the “Notifying Party”) shall notify the other Parties when the Notifying Party becomes aware of its inability to comply with the provisions of this Agreement for a reason other than a Force Majeure event. The Parties agree to cooperate with each other and provide necessary information regarding such inability to comply, including the date, duration, reason for the inability to comply, and corrective actions taken or planned to be taken with respect to such inability to comply. Notwithstanding the foregoing, notification, cooperation or information provided under this Article shall not entitle the Party receiving such notification to allege a cause for anticipatory breach of this Agreement.

  • 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”):

  • Initial Forecasts/Trunking Requirements Because Verizon’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom CSTC decides to market its services, Verizon will be largely dependent on CSTC to provide accurate trunk forecasts for both inbound (from Verizon) and outbound (to Verizon) traffic. Verizon will, as an initial matter, provide the same number of trunks to terminate Reciprocal Compensation Traffic to CSTC as CSTC provides to terminate Reciprocal Compensation Traffic to Verizon. At Verizon’s discretion, when CSTC expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, Verizon will provide the number of trunks CSTC suggests; provided, however, that in all cases Verizon’s provision of the forecasted number of trunks to CSTC is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and CSTC’s previous forecasts have proven to be reliable and accurate.

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