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:
i) acts of God;
ii) typhoons, floods, lightning, cyclone, hurricane, drought, famine, epidemic, plague or other natural calamities;
iii) acts of war (whether declared or undeclared), invasion or civil unrest;
iv) any requirement, action or omission to act pursuant to any judgment or order of any court or judicial authority in India (provided such requirement, action or omission to act is not due to the breach by the SPG or of any Law or any of their respective obligations under this Agreement);
v) inability despite complying with all legal requirements to obtain, renew or maintain required licenses or Legal Approvals;
vi) earthquakes, explosions, accidents, landslides; fire;
vii) expropriation and/or compulsory acquisition of the Project in whole or in part by Government Instrumentality;
viii) chemical or radioactive contamination or ionizing radiation; or
ix) damage to or breakdown of transmission facilities of GETCO/ DISCOMs;
x) Exceptionally adverse weather condition which are in excess of the statistical measure of the last hundred (100) years.
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:
(a) accident, death or severe injury to any person;
(b) damaged or dislodged fixed equipment;
(c) flooding of Project Highway; and
(d) any other unusual occurrence.
Meteorological Data Reporting Requirement (Applicable to wind generation facilities only)
Unbundled Loop Modifications (Line Conditioning 2.5.1 Line Conditioning is defined as routine network modification that BellSouth regularly undertakes to provide xDSL services to its own customers. This may include the removal of any device, from a copper Loop or copper Subloop that may diminish the capability of the Loop or Subloop to deliver high-speed switched wireline telecommunications capability, including xDSL service. Such devices include, load coils, excessive bridged taps, low pass filters, and range extenders. Excessive bridged taps are bridged taps that serves no network design purpose and that are beyond the limits set according to industry standards and/or the BellSouth’s TR 73600 Unbundled Local Loop Technical Specification.
2.5.2 BellSouth will remove load coils only on copper Loops and Subloops that are less than eighteen thousand (18,000) feet in length.
2.5.3 For any copper loop being ordered by NewPhone which has over six thousand (6,000) feet of combined bridged tap will be modified, upon request from NewPhone, so that the loop will have a maximum of six thousand (6,000) feet of bridged tap. This modification will be performed at no additional charge to NewPhone. Loop conditioning orders that require the removal of bridged tap that serves no network design purpose on a copper Loop that will result in a combined total of bridged tap between two thousand five hundred (2,500) and six thousand (6,000) feet will be performed at the rates set forth in Exhibit A.
2.5.4 NewPhone may request removal of any unnecessary and non-excessive bridged tap (bridged tap between zero (0) and two thousand five hundred (2,500) feet which serves no network design purpose), at rates pursuant to BellSouth’s SC Process as mutually agreed to by the Parties.
2.5.5 Rates for ULM are as set forth in Exhibit A.
2.5.6 BellSouth will not modify a Loop in such a way that it no longer meets the technical parameters of the original Loop type (e.g., voice grade, ADSL, etc.) being ordered.
2.5.7 If NewPhone requests ULM on a reserved facility for a new Loop order, BellSouth may perform a pair change and provision a different Loop facility in lieu of the reserved facility with ULM if feasible. The Loop provisioned will meet or exceed specifications of the requested Loop facility as modified. NewPhone will not be charged for ULM if a different Loop is provisioned. For Loops that require a DLR or its equivalent, BellSouth will provide LMU detail of the Loop provisioned.
2.5.8 NewPhone shall request Loop make up information pursuant to this Attachment prior to submitting a service inquiry and/or a LSR for the Loop type that NewPhone desires BellSouth to condition.
2.5.9 When requesting ULM for a Loop that BellSouth has previously provisioned for NewPhone, NewPhone will submit a SI to BellSouth. If a spare Loop facility that meets the Loop modification specifications requested by NewPhone is available at the location for which the ULM was requested, NewPhone will have the option to change the Loop facility to the qualifying spare facility rather than to provide ULM. In the event that BellSouth changes the Loop facility in lieu of providing ULM, NewPhone will not be charged for ULM but will only be charged the service order charges for submitting an order.
Failure to Maintain Financial Viability The System Agency may terminate the Grant Agreement if the System Agency, in its sole discretion, determines that Grantee no longer maintains the financial viability required to complete the services and deliverables, or otherwise fully perform its responsibilities under the Grant Agreement.
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.
Additional Disruption Events Change in Law: Applicable; provided that Section 12.9(a)(ii) of the Equity Definitions is hereby amended by adding the words “(including, for the avoidance of doubt and without limitation, adoption or promulgation of new regulations authorized or mandated by existing statute)” after the word “regulation” in the second line thereof.
LIABILITY FOR FAILURE TO COMPLETE TRANSACTIONS If We do not
Failure to Fulfill Conditions In the event that either of the parties hereto determines that a condition to its respective obligations to consummate the transactions contemplated hereby cannot be fulfilled on or prior to the termination of this Agreement, it will promptly notify the other party.
