Limited Liability in Emergency Conditions Except as otherwise provided in the Tariff or the Operating Agreement, no Interconnection Party shall be liable to any other Interconnection Party for any action that it takes in responding to an Emergency Condition, so long as such action is made in good faith, is consistent with Good Utility Practice and is not contrary to the directives of the Transmission Provider or of the Interconnected Transmission Owner with respect to such Emergency Condition. Notwithstanding the above, Interconnection Customer shall be liable in the event that it fails to comply with any instructions of Transmission Provider or the Interconnected Transmission Owner related to an Emergency Condition.
POLICY CONDITIONS In addition to the policy terms which are contained in other sections of this policy, the following conditions also apply.
GEOGRAPHIC AREA AND SECTOR SPECIFIC ALLOWANCES, CONDITIONS AND EXCEPTIONS The following allowances and conditions shall apply where relevant: Where the company does work which falls under the following headings, the company agrees to pay and observe the relevant respective conditions and/or exceptions set out below in each case.
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.
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 Sub-loop that may diminish the capability of the Loop or Sub-loop to deliver high-speed switched wireline telecommunications capability, including xDSL service. Such devices include, but are not limited to, 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 XxxxXxxxx XX 00000.
Interconnection Customer Compensation for Actions During Emergency Condition The CAISO shall compensate the Interconnection Customer in accordance with the CAISO Tariff for its provision of real and reactive power and other Emergency Condition services that the Interconnection Customer provides to support the CAISO Controlled Grid during an Emergency Condition in accordance with Article 11.6.
Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.
BASIC CONDITIONS The State shall have no obligation to disburse money for the Project under this Grant Agreement until the Grantee has satisfied the following conditions:
CONDITIONS APPLICABLE PENDING TRANSFER As has already been referred to in this agreement, the common property will be owned and controlled by a body corporate for and on behalf of all owners including the purchaser. As the body corporate will only be established once the first transfer of a unit in the development has occurred, the Seller shall from the completion date and until the date of the establishment of the body corporate bear the rights and obligations of the body corporate. In this regard, during the period from the completion date until date of transfer, the following conditions shall apply:
Completion of Concrete Pours and Emergency Work 24.14.1 Except as provided in this sub-clause an employee shall not work or be required to work in the rain.