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, the Office of the Auditor General also have authority to perform audits and inspections.
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.
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”).
Compliance Audits D.4.1 Compliance Audit(s). Without limiting the generality of section A.7.4 (Records Review), if requested by the Province from time to time, which request shall be at the Province’s sole discretion, the Recipient, at its own expense, will forthwith retain an independent third party auditor to conduct one or more compliance audits of the Recipient or any Project. The audit will be conducted in accordance with Canadian Generally Accepted Auditing Standards, as adopted by the Canadian Institute of Chartered Accountants, applicable as of the date on which a record is kept or required to be kept under such standards. In addition, the audit will assess the Recipient’s compliance with the terms of the Agreement and will address, with respect to each Project, without limitation, the following:
Contractual and Operational Compliance Audits (a) ICANN may from time to time (not to exceed twice per calendar year) conduct, or engage a third party to conduct, contractual compliance audits to assess compliance by Registry Operator with its representations and warranties contained in Article 1 of this Agreement and its covenants contained in Article 2 of this Agreement. Such audits shall be tailored to achieve the purpose of assessing compliance, and ICANN will (a) give reasonable advance notice of any such audit, which notice shall specify in reasonable detail the categories of documents, data and other information requested by ICANN, and
