Performance or Compliance Audits The Department may conduct or have conducted performance and/or compliance audits of the Contractor and subcontractors as determined by the Department. The Department may conduct an audit and review all the Contractor’s and subcontractors’ data and records that directly relate to the Contract. To the extent necessary to verify the Contractor’s fees and claims for payment under the Contract, the Contractor’s agreements or contracts with subcontractors, partners, or agents of the Contractor, pertaining to the Contract, may be inspected by the Department upon fifteen (15) calendar days’ notice, during normal working hours and in accordance with the Contractor’s facility access procedures where facility access is required. Release statements from its subcontractors, partners, or agents are not required for the Department or its designee to conduct compliance and performance audits on any of the Contractor’s contracts relating to this Contract. The Inspector General, in accordance with section 5.6, the State of Florida’s Chief Financial Officer, and the Office of the Auditor General shall also have authority to perform audits and inspections.
CEQA Compliance The District has complied with all assessment requirements imposed upon it by the California Environmental Quality Act (Public Resource Code Section 21000 et seq. (“CEQA”) in connection with the Project, and no further environmental review of the Project is necessary pursuant to CEQA before the construction of the Project may commence.
FERPA Compliance In connection with all FERPA Records that Contractor may create, receive or maintain on behalf of University pursuant to the Underlying Agreement, Contractor is designated as a University Official with a legitimate educational interest in and with respect to such FERPA Records, only to the extent to which Contractor (a) is required to create, receive or maintain FERPA Records to carry out the Underlying Agreement, and (b) understands and agrees to all of the following terms and conditions without reservation:
Law Compliance In providing the SOLID WASTE HANDLING SERVICES required by this AGREEMENT, CONTRACTOR shall observe and comply with all applicable federal and, state laws, regulations and codes regarding the provision of the SOLID WASTE HANDLING SERVICES described herein, as such may be amended from time to time, including where required by such laws, the funding and maintenance of sufficient closure and post-closure maintenance financial assurances for any landfill operated or utilized by CONTRACTOR for disposal of the SOLID WASTE. Any violation of this Paragraph shall constitute a major breach.
OSHA Compliance To the extent applicable to the services to be performed under this Agreement, Contractor represents and warrants, that all articles and services furnished under this Agreement meet or exceed the safety standards established and promulgated under the Federal Occupational Safety and Health Law (Public Law 91-596) and its regulations in effect or proposed as of the date of this Agreement.
Compliance Review During the Term, Xxxxxxxxx agrees to permit the GLO, HUD, and/or a designated representative of the GLO or HUD to access the Property for the purpose of performing Compliance-Monitoring Procedures. In accordance with GLO Compliance-Monitoring Procedures, the GLO or HUD will periodically monitor and audit Developer’s compliance with the requirements of this Agreement, the CDBG-DR Regulations, the CDBG Multifamily Rental Housing Guidelines, and any and all other Governmental Requirements during the Term. In conducting any compliance reviews, the GLO or HUD will rely primarily on information obtained from Developer’s records and reports, on-site monitoring, and audit reports. The GLO or HUD may also consider other relevant information gained from other sources, including litigation and citizen complaints. Attachment G GLO Contract No. 20-063-013-B934 5.04 Hazardous Materials: Indemnification
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”).
