E-911 Regulatory Requirements – U Sample Clauses

E-911 Regulatory Requirements – U. S. A provider of “interconnected VoIP service,” as defined by the Federal Communications Commission (FCC), is required by the FCC to route emergency 911 calls in conjunction with such VoIP service where such 911 calling is available.
AutoNDA by SimpleDocs

Related to E-911 Regulatory Requirements – U

  • Regulatory Requirements Each Party’s obligations under this Agreement shall be subject to its receipt of any required approval or certificate from one or more Governmental Authorities in the form and substance satisfactory to the applying Party, or the Party making any required filings with, or providing notice to, such Governmental Authorities, and the expiration of any time period associated therewith. Each Party shall in good faith seek and use its Reasonable Efforts to obtain such other approvals. Nothing in this Agreement shall require Developer to take any action that could result in its inability to obtain, or its loss of, status or exemption under the Federal Power Act or the Public Utility Holding Company Act of 2005 or the Public Utility Regulatory Policies Act of 1978, as amended.

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

  • Program Requirements A. The parties shall comply with the Disadvantaged Business Enterprise Program requirements established in 49 CFR Part 26.

  • General Program Requirements Subrecipient shall adhere, but not be limited to, the following requirements for all programs:

  • E-Verify Requirements To the extent applicable under ARIZ. REV. STAT. § 41- 4401, the Contractor and its subcontractors warrant compliance with all federal immigration laws and regulations that relate to their employees and their compliance with the E-verify requirements under ARIZ. REV. STAT. § 23-214(A). Contractor’s or its subcontractor’s failure to comply with such warranty shall be deemed a material breach of this Agreement and may result in the termination of this Agreement by the City.

  • Export Requirements The Program, Documentation and all related technical information or materials are subject to export controls and U.S. Government export regulations. You will comply strictly with all legal requirements established under these controls and will not, in connection with its limited evaluation rights hereunder, export, re-export, divert, transfer or disclose, directly or indirectly the Program, Documentation and any related technical information or materials without the prior approval of the U.S.

  • Safety Requirements 17.1.1 The Concessionaire shall comply with the provisions of this Agreement, Applicable Laws and Applicable Permits and conform to Good Industry Practice for securing the safety of the Users. In particular, the Concessionaire shall develop, implement and administer a surveillance and safety programme for providing a safe environment on or about the Project, and shall comply with the safety requirements.

  • Child Abuse Reporting Requirements A. Grantees shall comply with child abuse and neglect reporting requirements in Texas Family Code Chapter 261. This section is in addition to and does not supersede any other legal obligation of the Grantee to report child abuse.

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