Power Factor Design Criteria (Reactive Power A wind generating plant shall maintain a power factor within the range of 0.95 leading to 0.95 lagging, measured at the Point of Interconnection as defined in this LGIA, if the ISO’s System Reliability Impact Study shows that such a requirement is necessary to ensure safety or reliability. The power factor range standards can be met using, for example without limitation, power electronics designed to supply this level of reactive capability (taking into account any limitations due to voltage level, real power output, etc.) or fixed and switched capacitors if agreed to by the Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected, or a combination of the two. The Developer shall not disable power factor equipment while the wind plant is in operation. Wind plants shall also be able to provide sufficient dynamic voltage support in lieu of the power system stabilizer and automatic voltage regulation at the generator excitation system if the System Reliability Impact Study shows this to be required for system safety or reliability.
Union Activity During Working Hours Solicitation of Union membership or collection or checking of dues will not be conducted during working time. The Company agrees not to discriminate in any way against any employee for Union activity, but such activity shall not be carried on during working time, except as specifically allowed by the provisions of this Agreement.
Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Xxxx has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Xxxx. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Xxxx (e.g. hairpinning):
1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises.
2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated.
3. If capacity exists, provide "side-door" porting through the switch.
4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch).
2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases.
2.6.3 If no alternate facility is available, and upon request from Xxxx, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Xxxx will then have the option of paying the one-time SC rates to place the Loop.
Compressed Work Week The Company and Union recognize the concept of the compressed work week. It is further understood that the compressed work week conditions will apply only to those departments that are on the compressed work week.
Weekend Differential Employees assigned to State institutions other than Maine State Prison shall be eligible for a weekend differential of fifty cents ($.50) per hour to the base for shifts beginning between 10:00 p.m. Friday and 9:59 p.m.
SPECIALIZED SERVICE REQUIREMENTS In the event that the Participating Entity requires service or specialized performance requirements not addressed in this Contract (such as e- commerce specifications, specialized delivery requirements, or other specifications and requirements), the Participating Entity and the Supplier may enter into a separate, standalone agreement, apart from this Contract. Sourcewell, including its agents and employees, will not be made a party to a claim for breach of such agreement.
Additional Statutory and Regulatory Obligations Vendor acknowledges that it has the following additional obligations under Section 2-d with respect to any Protected Data received from the District, and that any failure to fulfill one or more of these statutory or regulatory obligations will be deemed a breach of the Master Agreement and the terms of this Data Sharing and Confidentiality Agreement:
(a) To limit internal access to Protected Data to only those employees or subcontractors that are determined to have legitimate educational interests within the meaning of Section 2-d and the Family Educational Rights and Privacy Act (FERPA); i.e., they need access in order to assist Vendor in fulfilling one or more of its obligations to the District under the Master Agreement.
(b) To not use Protected Data for any purposes other than those explicitly authorized in this Data Sharing and Confidentiality Agreement and the Master Agreement to which this Exhibit is attached.
(c) To not disclose any Protected Data to any other party, except for authorized representatives of Vendor using the information to carry out Vendor’s obligations to the District and in compliance with state and federal law, regulations and the terms of the Master Agreement, unless:
(i) the parent or eligible student has provided prior written consent; or
(ii) the disclosure is required by statute or court order and notice of the disclosure is provided to the District no later than the time of disclosure, unless such notice is expressly prohibited by the statute or court order.
(d) To maintain reasonable administrative, technical, and physical safeguards to protect the security, confidentiality, and integrity of Protected Data in its custody.
(e) To use encryption technology to protect Protected Data in its custody while in motion or at rest, using a technology or methodology specified by the Secretary of the U.S. Department of Health and Human Services in guidance issued under Section 13402(H)(2) of Public Law 111-5.
(f) To adopt technologies, safeguards and practices that align with the NIST Cybersecurity Framework.
(g) To comply with the District’s policy on data security and privacy, Section 2-d and Part 121.
(h) To not sell Protected Data nor use or disclose it for any marketing or commercial purpose or facilitate its use or disclosure by any other party for any marketing or commercial purpose or permit another party to do so.
(i) To notify the District, in accordance with the provisions of Section 5 of this Data Sharing and Confidentiality Agreement, of any breach of security resulting in an unauthorized release of Protected Data by Vendor or its assignees or subcontractors in violation of applicable state or federal law, the District’s Bill of Rights for Data Security and Privacy, the District’s policies on data security and privacy, or other binding obligations relating to data privacy and security contained in the Master Agreement and this Exhibit.
(j) To cooperate with the District and law enforcement to protect the integrity of investigations into the breach or unauthorized release of Protected Data.
(k) To pay for or promptly reimburse the District for the full cost of notification, in the event the District is required under Section 2-d to notify affected parents, students, teachers or principals of a breach or unauthorized release of Protected Data attributed to Vendor or its subcontractors or assignees.
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.
Clean-Up Period (a) Notwithstanding anything to the contrary set forth herein or in any other Loan Document, during the Clean-Up Period, the occurrence of any breach of a representation, covenant or an Event of Default (other than an Event of Default set out in Section 9.1(a)) will be deemed not to be a breach of a representation or warranty or a breach of a covenant or an Event of Default, as the case may be, if it would have been (if it were not for this provision) a breach of representation or warranty or a breach of a covenant or an Event of Default only by reason of circumstances relating exclusively to, with respect to any Permitted Acquisition or other Permitted Clean-Up Investment (or the subsidiaries of such target), the target of such Permitted Acquisition or Permitted Clean-Up Investment, and provided that such breach or Event of Default:
(i) is capable of being remedied within the Clean-Up Period and the Loan Parties are taking appropriate steps to remedy such breach or Event of Default;
(ii) does not have and is not reasonably likely to have a Material Adverse Effect; and
(iii) was not procured by or approved by Holdings or the Borrowers.
(b) Notwithstanding Section 9.6(a), if the relevant circumstances are continuing on or after the expiry of the Clean-Up Period, there shall be a breach of representation or warranty, breach of covenant or Event of Default, as the case may be, notwithstanding the above (and without prejudice to the rights and remedies of the Agents and the Lenders).
(c) For the avoidance of doubt, if any breach of representation or warranty, breach of covenant or Event of Default shall be deemed to not exist due to Section 9.6(a) during the Clean-Up Period, then such breach of representation or warranty, breach of covenant or Event of Default shall be deemed not to exist for purposes of Section 5.2 for so long as (but in no event later than the end of the Clean-Up Period) such breach of representation or warranty, breach of covenant or Event of Default shall be deemed not to exist due to the provisions of Section 9.6(a).
In the Event of Forecasted Surpluses If the HSP is forecasting a surplus, the Funder may take one or more of the following actions: adjust the amount of Funding to be paid under Schedule A, require the repayment of excess Funding; adjust the amount of any future funding installments accordingly.
