CUSTOMER’S COMPLIANCE WITH PROGRAM STANDARDS Clause Samples

CUSTOMER’S COMPLIANCE WITH PROGRAM STANDARDS. 4.1. The Customer shall keep itself fully informed of the Program Standards including laws, ordinances, codes, rules and regulations, governmental general and development plans, setback limitations, rights of way, and all changes thereto, which in any manner affect the Customer’s construction, operation, maintenance, and repair of the Solar Facility and sale to the Agency of the Energy produced by the Solar Facility, all as provide for in the Agreements. 4.2. The Customer shall, at its sole expense, obtain all land use approvals, building permits, and other permits or licenses, including easements or other permanent interests in real property, which may be required in connection with the construction, operation, repair, and maintenance of the Solar Facility and shall give all notices, pay all fees, and take all other action which may be necessary to ensure that the Solar Facility is constructed operated, repaired, and maintained in accordance with the Program Standards and Applicable Law. 4.3. The Customer shall be responsible for payment of all applicable federal, state, and county taxes and fees which may become due and owing as a result of the construction and operation of the Facility or the sale of the Energy to the Agency, including but not limited to (a) income taxes,
View SourceView Similar (2)
CUSTOMER’S COMPLIANCE WITH PROGRAM STANDARDS. 4.1. The Customer shall keep itself fully informed of the Program Standards including laws, ordinances, codes, rules and regulations, governmental general and development plans, setback limitations, rights of way, and all changes thereto, which in any manner affect the Customer’s construction, operation, maintenance and repair of the Generation Facility and sale to the Company of the Energy produced by the Generation Facility, all as provide for in the Agreements. 4.2. The Customer shall, at its sole expense, obtain all land use approvals, building permits and other permits or licenses, including easements or other permanent interests in real property, which may be required in connection with the construction, operation, repair and maintenance of the Generation Facility and shall give all notices, pay all fees, and take all other action which may be necessary to ensure that the Generation Facility is constructed operated, repaired and maintained in accordance with the Program Standards and Applicable Law. 4.3. The Customer shall be responsible for payment of all applicable federal, state, and county taxes and fees which may become due and owing as a result of the construction and operation of the Facility or the sale of the Energy to the Company, including but not limited to (a) income taxes, (b) energy or sales taxes, (c) employment-related fees, assessments, and taxes, (d) property or privilege tax and (d) general excise taxes.
View Source

Related to CUSTOMER’S COMPLIANCE WITH PROGRAM STANDARDS

  • Compliance with Policies Each Individual Limited Partner hereby agrees that he shall comply with all policies and procedures adopted by any member of the Och-Ziff Group or which Limited Partners are required to observe by law, or by any recognized stock exchange, or other regulatory body or authority.

  • COMPLIANCE WITH POLICIES AND PROCEDURES During the period that Executive is employed with the Company hereunder, Executive shall adhere to the policies and standards of professionalism set forth in the Company’s Policies and Procedures as they may exist from time to time.

  • Compliance with Accessibility Standards All parties to this Agreement shall ensure that the plans for and the construction of all projects subject to this Agreement are in compliance with standards issued or approved by the Texas Department of Licensing and Regulation (TDLR) as meeting or consistent with minimum accessibility requirements of the Americans with Disabilities Act (P.L. 101-336) (ADA).

  • Compliance with Standards Although the standards for workmanship, material, and equipment have been selected in these specifications as a basis of reference, standards and specifications of the other bank member countries and recommendations of standards international organizations will be acceptable provided they are substantially equivalent to the designated standards and provided furthermore that the contractor submits for approval detailed specifications which he proposes to use. Reference to brand names or catalog numbers if any in these specifications have been made only for that equipment for which it has been determined that a degree of standardization is necessary to maintain certain essential features. And in certain cases such references have also been made for purposes of convenience to specify the requirements, in either case offers of alternative goods, which have similar characteristics and provide performance and quality at lease equal to those specified are acceptable. If the contractor offers materials, equipment, design calculations or tests, which conform to standards other than those specified, full details of the differences between the proposed standards and that specified in so far as they affect the design or purpose of the equipment, are to be supplied by the contractor if called upon to do so by the engineer, where required by the engineer for approval purposes, the contractor shall supply, without charge, duplicate copies of the proposed standards with English translations of the relevant portions. The contractor shall have available in his place of business (or in his supplier’s works) the relevant copies of standards or codes used for the use of the Engineer.

  • Standards Compliance Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF), including all successor standards, modifications or additions thereto relating to the DNS and name server operations including without limitation RFCs 1034, 1035, 1123, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 4343, and 5966. DNS labels may only include hyphens in the third and fourth position if they represent valid IDNs (as specified above) in their ASCII encoding (e.g., “xn--ndk061n”).