CONTRACT COMPLIANCE REQUIREMENT The HUB requirement on this Contract is 0%. The student engagement requirement of this Contract is 0 hours. The Career Education requirement for this Contract is 0 hours. Failure to achieve these requirements may result in the application of some or all of the sanctions set forth in Administrative Policy 3.10, which is hereby incorporated by reference.
Non-compliance with the Clauses and termination (a) The data importer shall promptly inform the data exporter if it is unable to comply with these Clauses, for whatever reason.
Compliance with Audit and Reporting Requirements; Maintenance of Records A. The Grantee shall submit to an audit of funds paid through this Grant Agreement and shall make all books, accounting records and other documents available at all reasonable times during the term of this Grant Agreement and for a period of three (3) years after final payment for inspection by the State or its authorized designee. Copies shall be furnished to the State at no cost
Compliance Requirements K. If using volunteers as provided for in this Contract during FY19, which encompasses the Contract term of July 1, 2019 to June 30, 2020, then the Grantee must either:
Proof of Compliance with Disability Benefits Coverage Requirements In order to provide proof of compliance with the requirements of the Workers’ Compensation Law pertaining to disability benefits, a contractor shall:
Compliance with Xxxxx-Xxxxx and Related Act requirements All rulings and interpretations of the Xxxxx-Xxxxx and Related Acts contained in 29 CFR parts 1, 3, and 5 are herein incorporated by reference in this contract.
Proof of Compliance with Workers’ Compensation Coverage Requirements An XXXXX form is NOT acceptable proof of workers’ compensation coverage. In order to provide proof of compliance with the requirements of the Workers’ Compensation Law pertaining to workers’ compensation coverage, a contractor shall:
Policy Compliance Violations The Requester and Approved Users acknowledge that the NIH may terminate the DAR, including this Agreement and immediately revoke or suspend access to all controlled-access datasets subject to the NIH GDS Policy at any time if the Requester is found to be no longer in agreement with the principles outlined in the NIH GDS Policy, the terms described in this Agreement, or the Genomic Data User Code of Conduct. The Requester and PI agree to notify the NIH of any violations of the NIH GDS Policy, this Agreement, or the Genomic Data User Code of Conduct data within 24 hours of when the incident is identified. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. The Requester and PI agree to notify the appropriate DAC(s) of any unauthorized data sharing, breaches of data security, or inadvertent data releases that may compromise data confidentiality within 24 hours of when the incident is identified. As permitted by law, notifications should include any known information regarding the incident and a general description of the activities or process in place to define and remediate the situation fully. Within 3 business days of the DAC notification(s), the Requester agrees to submit to the DAC(s) a detailed written report including the date and nature of the event, actions taken or to be taken to remediate the issue(s), and plans or processes developed to prevent further problems, including specific information on timelines anticipated for action. The Requester agrees to provide documentation verifying that the remediation plans have been implemented. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. All notifications and written reports of data management incidents should be sent to the DAC(s) indicated in the Addendum to this Agreement. NIH, or another entity designated by NIH may, as permitted by law, also investigate any data security incident or policy violation. Approved Users and their associates agree to support such investigations and provide information, within the limits of applicable local, state, tribal, and federal laws and regulations. In addition, Requester and Approved Users agree to work with the NIH to assure that plans and procedures that are developed to address identified problems are mutually acceptable and consistent with applicable law.
COMPLIANCE WITH LICENSING REQUIREMENTS CONTRACTOR shall comply with all necessary licensing requirements and shall obtain appropriate licenses and display the same in a location that is reasonably conspicuous, as well as file copies of same with the County Executive Office.
Notification of Non-Compliance If Seller is unable to comply with the obligations stated in this Section, Seller shall promptly notify Apple, and Apple may take any one or more of the following actions: (i) suspend the transfer of Confidential Data to Seller; (ii) require Seller to cease processing Confidential Data; (iii) demand the secure return or destruction of Confidential Data; and/or (iv) immediately terminate this Agreement.
