Regulatory Requirements and Governing Law 43 14.1 Regulatory Requirements. 43 14.2 Governing Law 44 ARTICLE 15. NOTICES 44 15.1 General. 44 15.2 Xxxxxxxx and Payments. 44 15.3 Alternative Forms of Notice 44 15.4 Operations and Maintenance Notice 44 ARTICLE 16. FORCE MAJEURE 45 16.1 Force Majeure 45 ARTICLE 17. DEFAULT 45 17.1 Default. 45 ARTICLE 18. INDEMNITY, CONSEQUENTIAL DAMAGES AND INSURANCE 46 18.1 Indemnity. 46 18.2 No Consequential Damages. 47 18.3 Insurance 47 ARTICLE 19. ASSIGNMENT 49 19.1 Assignment. 49 ARTICLE 20. SEVERABILITY 49 20.1 Severability. 49 ARTICLE 21. COMPARABILITY 50 21.1 Comparability. 50 ARTICLE 22. CONFIDENTIALITY 50 22.1 Confidentiality. 50 ARTICLE 23. ENVIRONMENTAL RELEASES 53 23.1 Developer and Connecting Transmission Owner Notice 53 ARTICLE 24. INFORMATION REQUIREMENT 53 24.1 Information Acquisition. 53 24.2 Information Submission by Connecting Transmission Owner 54 24.3 Updated Information Submission by Developer 54 24.4 Information Supplementation 54 ARTICLE 25. INFORMATION ACCESS AND AUDIT RIGHTS 55 25.1 Information Access. 55 25.2 Reporting of Non-Force Majeure Events. 55 25.3 Audit Rights. 56 25.4 Audit Rights Periods. 56 25.5 Audit Results. 56 ARTICLE 26. SUBCONTRACTORS 56 26.1 General. 56 26.2 Responsibility of Principal. 57 26.3 No Limitation by Insurance 57 ARTICLE 27. DISPUTES 57 27.1 Submission 57 27.2 External Arbitration Procedures. 57 27.3 Arbitration Decisions. 58 27.4 Costs. 58 27.5 Termination 58 ARTICLE 28. REPRESENTATIONS, WARRANTIES AND COVENANTS 58 28.1 General. 58 ARTICLE 29. MISCELLANEOUS 59 29.1 Binding Effect. 59 29.2 Conflicts. 59 29.3 Rules of Interpretation 59 29.4 Compliance 60 29.5 Joint and Several Obligations. 60 29.6 Entire Agreement. 60 29.7 No Third Party Beneficiaries. 60 29.8 Waiver 60 29.9 Headings. 61 29.10 Multiple Counterparts. 61 29.11 Amendment. 61 29.12 Modification by the Parties. 61 29.13 Reservation of Rights. 61 29.14 No Partnership 62 29.15 Other Transmission Rights. 62 Appendices STANDARD LARGE GENERATOR INTERCONNECTION AGREEMENT THIS STANDARD LARGE GENERATOR INTERCONNECTION AGREEMENT (“Agreement”) is made and entered into this 17th day of April 2013, by and among Erie Boulevard Hydropower, LP (a limited partnership subsidiary of Brookfield Renewable Power), a company organized and existing under the laws of the State of New York (“Developer” with a Large Generating Facility), the New York Independent System Operator, Inc., a not-for-profit corporation organized and existing under the laws of the State of New York (“NYISO”), and Niagara Mohawk Power Corporation d/b/a National Grid, a corporation organized and existing under the laws of the State of New York (“Connecting Transmission Owner”). Developer, the NYISO, or Connecting Transmission Owner each may be referred to as a “Party” or collectively referred to as the “Parties.”
Entitlements and Purchasing Requirements You must purchase the appropriate number of Software Subscription(s), based on the number of Socket-pairs for all Managed Nodes being managed by the Red Hat CloudForms Software. A “Socket-pair” is up to two sockets each occupied by a CPU on a Managed Node. Red Hat CloudForms Software is configured to manage virtual machines on certain public clouds (a “Red Hat CloudForms Enabled Cloud”). You must purchase the appropriate number of Red Hat CloudForms for Public Cloud Software Subscriptions based on the number of Managed VMs instantiated on a Red Hat CloudForms Enabled Cloud. Please confirm that a specific public cloud is a Red Hat CloudForms Enabled Cloud prior to purchasing. A Red Hat Enterprise Linux Software Subscription is bundled with the Red Hat CloudForms Software Subscription and the fees for the Red Hat CloudForms Subscription are based on such bundled use. Any use of the Red Hat Enterprise Linux other than to run the Red Hat CloudForms Software is subject to Red Hat’s standard Software Subscription fees for such use.
Federal Requirements Pertaining to Grants and Subrecipient Agreements A. Requirement to Have a Single Audit: In the case that this Agreement is a Grant that is funded in whole or in part by federal funds, the Subrecipient will complete the Subrecipient Annual Report annually within 45 days after its fiscal year end, informing the State of Vermont whether or not a Single Audit is required for the prior fiscal year. If a Single Audit is required, the Subrecipient will submit a copy of the audit report to the granting Party within 9 months. If a single audit is not required, only the Subrecipient Annual Report isrequired. For fiscal years ending before December 25, 2015, a Single Audit is required if the subrecipient expends $500,000 or more in federal assistance during its fiscal year and must be conducted in accordance with OMB Circular A-133. For fiscal years ending on or after December 25, 2015, a Single Audit is required if the subrecipient expends $750,000 or more in federal assistance during its fiscal year and must be conducted in accordance with 2 CFR Chapter I, Chapter II, Part 200, Subpart F. The Subrecipient Annual Report is required to be submitted within 45 days, whether or not a Single Audit is required.
Accessibility of Web-Based Information and Applications For State Agency Authorized User Acquisitions: Any web-based information and applications development, or programming delivered pursuant to the contract or procurement, will comply with New York State Enterprise IT Policy NYS-P08-005, Accessibility of Web-Based Information and Applications as follows: Any web-based information and applications development, or programming delivered pursuant to the contract or procurement, will comply with New York State Enterprise IT Policy NYS-P08- 005, Accessibility of Web-Based Information and Applications as such policy may be amended, modified or superseded, which requires that state agency web-based information and applications are accessible to persons with disabilities. Web-based information and applications must conform to New York State Enterprise IT Policy NYS-P08-005 as determined by quality assurance testing. Such quality assurance testing will be conducted by the State Agency Authorized User and the results of such testing must be satisfactory to the Authorized User before web-based information and applications will be considered a qualified deliverable under the contract or procurement.
Compliance with Other Instruments The execution, delivery and performance by the Purchaser of this Agreement and the consummation by the Purchaser of the transactions contemplated by this Agreement will not result in any violation or default (i) of any provisions of its organizational documents, (ii) of any instrument, judgment, order, writ or decree to which it is a party or by which it is bound, (iii) under any note, indenture or mortgage to which it is a party or by which it is bound, (iv) under any lease, agreement, contract or purchase order to which it is a party or by which it is bound or (v) of any provision of federal or state statute, rule or regulation applicable to the Purchaser, in each case (other than clause (i)), which would have a material adverse effect on the Purchaser or its ability to consummate the transactions contemplated by this Agreement.
Exception Where Databases Contain Sufficient Information A Reporting Financial Institution is not required to perform the paper record search described in subparagraph D.2. of this section if the Reporting Financial Institution’s electronically searchable information includes the following:
Conditions and Exclusions Notwithstanding anything to the contrary set forth in this SLA, this SLA and Customer’s entitlement to the remedies set out in this SLA are subject to the following conditions and exclusions:
Compliance with Data Privacy and Security Laws and Standards Contractor shall comply with all applicable State and federal data privacy and data security laws, rules, and regulations.
Additional Licensing Requirements and or Use Rights a. Multiplexing. Multiplexing (sometimes referred to as “pooling”) is a manner of indirect hardware or software access (“indirect access”) that • pools connections, • reroutes information, • reduces the number of users that directly access or use the software, or • reduces the number of users the software directly manages. Any user accessing the ERP Solution through a multiplexed connection must be appropriately licensed with an Access License.
PRESERVATION OF CONTRACTING INFORMATION 2.27.1 The requirements of Subchapter J, Chapter 552, Texas Government Code, may apply to this Agreement and the Contractor agrees that this Agreement can be terminated if the Contractor knowingly or intentionally fails to comply with a requirement of that subchapter. If the requirements of Subchapter J, Chapter 552, Texas Government Code, apply to this Agreement, then for the duration of this Agreement (including the initial term, any renewal terms, and any extensions), Contractor shall preserve all Contracting Information, as defined by Section 552.003 of the Texas Government Code, related to this Agreement as provided by the records retention requirements applicable to the City pursuant to federal or state law or regulation, city ordinance or city policy, which record retention requirements include but are not limited to those set forth in Chapters 201 and 205 of the Texas Local Government Code and Texas Administrative Code Title 13, Chapter 7. Within five business days after receiving a request from the Director, Contractor shall provide any Contracting Information related to this Agreement that is in the custody or possession of Contractor. Upon the expiration or termination of this Agreement, Contractor shall, at the Director’s election, either (a) provide, at no cost to the City, all Contracting Information related to this Agreement that is in the custody or possession of Contractor, or (b) preserve the Contracting Information related to this Agreement as provided by the records retention requirements applicable to the City pursuant to federal or state law or regulation, city ordinance or City policy.
