PV System Compliance Sample Clauses

PV System Compliance. Host Facility Owner agrees to take electrical service under Idaho Public Utilities Commission Xx. 00, Xxxxxx Xx. 000 Schedule 84 – Customer Energy Production Net Metering rate schedule, as updated from time to time. Additionally, Host Facility Owner shall comply with all utility requirements set forth in Schedule 68, as updated from time to time, including access to the PV System production meter and disconnect switch.
AutoNDA by SimpleDocs

Related to PV System Compliance

  • PCI Compliance A. The Acquiring Bank will provide The Merchant with appropriate training on PCI PED and/or DSS rules and regulations in respect of The Merchants obligations. Initial training will be provided and at appropriate intervals as and when relevant changes are made to such rules and regulations.

  • Program Compliance The School Board shall be responsible for monitoring the program to provide technical assistance and to ensure program compliance.

  • Privacy Compliance The Provider shall comply with all applicable federal, state, and local laws, rules, and regulations pertaining to Student Data privacy and security, all as may be amended from time to time.

  • Minimum System Requirements The following summarizes the minimum office system requirements for all Contractors and Architect/Engineer to possess in order to participate. It is the responsibility of all Contractors and Architect/Engineer to possess these minimum requirements at no additional cost to Princeton University.

  • Accounting System Requirement The Contractor shall maintain an adequate system of accounting and internal controls that meets Generally Accepted Accounting Principles or “GAAP.”

  • Switching System Hierarchy and Trunking Requirements For purposes of routing ECI traffic to Verizon, the subtending arrangements between Verizon Tandem Switches and Verizon End Office Switches shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to ECI, the subtending arrangements between ECI Tandem Switches and ECI End Office Switches shall be the same as the Tandem/End Office subtending arrangements that ECI maintains for the routing of its own or other carriers’ traffic.

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

  • Labor Compliance Program The City has its own Labor Compliance Program authorized in August 2011 by the DIR. The City will withhold contract payments when payroll records are delinquent or deemed inadequate by the City or other governmental entity, or it has been established after an investigation by the City or other governmental entity that underpayment(s) have occurred. For questions or assistance, please contact the City of San Diego’s Equal Opportunity Contracting Department at 000-000-0000.

  • HIPAA Compliance If this Contract involves services, activities or products subject to the Health Insurance Portability and Accountability Act of 1996 (HIPAA), the Contractor covenants that it will appropriately safeguard Protected Health Information (defined in 45 CFR 160.103), and agrees that it is subject to, and shall comply with, the provisions of 45 CFR 164 Subpart E regarding use and disclosure of Protected Health Information.

  • Standards Compliance DNS. 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”).

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