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:
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.
Maintenance Requirements The Contractor shall ensure and procure that at all times during the Maintenance Period, the Project Highway conforms to the maintenance requirements set forth in Schedule-E (the “Maintenance Requirements”).
CLEARANCE REQUIREMENTS CONTRACTOR shall comply with the requirements of California Education Code section 44237, 35021.1, 35021.2, and 56366.1 including, but not limited to: obtaining clearance from both the California Department of Justice (hereinafter referred to as “CDOJ”) and clearance from the Federal Bureau of Investigation (hereinafter referred to as "FBI") for CONTRACTOR’s employees and volunteers, unless CONTRACTOR determines that the volunteers will have no direct contact with students. CONTRACTOR hereby agrees that CONTRACTOR’s employees and volunteers, unless CONTRACTOR determines that the volunteers will have no direct contact with students shall not come in contact with students until CDOJ and FBI clearance are ascertained. CONTRACTOR shall certify in writing to LEA that none of its employees, and volunteers, unless CONTRACTOR determines that the volunteers will have no direct contact with students, or contractors who may come into contact with students have been convicted of a violent or serious felony as those terms are defined in California Education Code section 44237(h), unless despite the employee’s conviction of a violent or serious felony, he or she has met the criteria to be eligible for employment pursuant to California Education Code section 44237 (i) or (j). Contractor shall certify to LEA that they have successful background checks and enrolled in subsequent arrest notification service for all employees who may come into contact with students. Notwithstanding the restrictions on sharing and destroying criminal background check information, CONTRACTOR, upon demand, shall make available to the LEA evidence of a successful criminal background check clearance and enrollment in subsequent arrest notice service, as provided, for each owner, operator, and employee of the NPS/A. CONTRACTOR is required to retain the evidence on-site, as specified, for all staff, including those licensed or credentialed by another state agency. Background clearances and proof of subsequent arrest notification service as required by California Penal Code section 11105.2 for all staff shall be provided upon request.
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”).
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.
Quality Assurance Requirements There are no special Quality Assurance requirements under this Agreement.
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.
Space Requirements The Construction Administrator will conduct a review of the adequacy of space allotments for maintenance of mechanical, telephone, and fire protection equipment.
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:
