Local & Municipal Code Compliance Sample Clauses

Local & Municipal Code Compliance. The pool or spa / hot tub owner is responsible for compliance with any and all local and municipal codes involving but not limited to buildings, electrical, safety, plumbing and piping. Further, the pool or spa / hot tub owner is responsible for adherence to all applicable homeowner association rules and regulations.
Sample 1Sample 2Sample 3See All (10)
AutoNDA by SimpleDocs
Local & Municipal Code Compliance. The spa / hot tub owner is responsible for compliance with any and all local and municipal codes involving but not limited to buildings, electrical, safety, plumbing and piping. Further, the spa / hot tub owner is responsible for adherence to all applicable homeowner association rules and regulations. Safety And Safe Work Site: It is the responsibility of the spa / hot tub owner to provide a safe worksite for Xxxxxxxx Pools & Spas Service staff, free of hazards and dangers. Property and Equipment Access: It is the responsibility of the spa / hot tub owner to provide Xxxxxxxx Pools & Spas Service staff physical access to the worksite and all equipment associated with the pool or spa / hot tub. Failure to provide access to the pool or spa / hot tub may result in rescheduling and may be subject to additional trip or labor charges. Pets & Domestic Animals: The spa / hot tub owner is responsible for containing and restraining pets or domestic animals when Xxxxxxxx Pools & Spas staff are on site.
Sample 1Sample 2

Related to Local & Municipal Code Compliance

  • Federal Medicaid System Security Requirements Compliance Party shall provide a security plan, risk assessment, and security controls review document within three months of the start date of this Agreement (and update it annually thereafter) in order to support audit compliance with 45 CFR 95.621 subpart F, ADP System Security Requirements and Review Process.

  • LABOR CODE COMPLIANCE The Grantee agrees to be bound by all the provisions of the Labor Code regarding prevailing wages and shall monitor all contracts subject to reimbursement from this Agreement to assure that the prevailing wage provisions of the Labor Code are being met. Current Department of Industrial Relations (DIR) requirements may be found at: xxxx://xxx.xxx.xx.xxx/ xxx.xxx. For more information, please refer to DIR’s Public Works Manual at: xxxx://xxx.xxx.xx.xxx/ dlse/PWManualCombined.pdf. The Grantee affirms that it is aware of the provisions of section 3700 of the Labor Code, which requires every employer to be insured against liability for workers’ compensation or to undertake self-insurance, and the Grantee affirms that it will comply with such provisions before commencing the performance of the work under this Agreement and will make its contractors and subcontractors aware of this provision.

  • ENVIRONMENTAL PROTECTION STANDARDS CONTRACTOR shall be in compliance with the Clean Air Act (Title 42 USC Section 7401 et seq.), the Clean Water Act (Title 33 USC Section 1251 et seq.), Executive Order 11738 and Environmental Protection Agency, hereinafter referred to as “EPA,” regulations (Title 40 CFR), as any may now exist or be hereafter amended. Under these laws and regulations, CONTRACTOR assures that:

  • COMPLIANCE WITH NEW YORK STATE INFORMATION SECURITY BREACH AND NOTIFICATION ACT Contractor shall comply with the provisions of the New York State Information Security Breach and Notification Act (General Business Law Section 899-aa; State Technology Law Section 208).

  • County Review and Approval of Insurance Requirements The County reserves the right to review and adjust the Required Insurance provisions, conditioned upon County’s determination of changes in risk exposures.

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