E-Verify compliance under 143-133 Sample Clauses

E-Verify compliance under 143-133. 3. The contractor and its subcontractors shall comply with the requirements of Article 2 of Chapter 64 of the North Carolina General Statutes (NCGS). This E-Verify compliance under 143-133.3 section is intended to apply to only the contracts to which NCGS 143-133.3(a) applies and shall be construed in accordance with that statute. Any clause in this contract included under the authority of NCGS 160A-20.1(b) shall be of no effect; provided, however, to the extent (if any) required to comply with NCGS 143-129(j), a clause in this contract requiring the contractor and its subcontractors to comply with the requirements of Article 2 of Chapter 64 shall remain in effect if this contract is subject to NCGS 143-129. This E-Verify compliance under 143-133.3 section is valid only if House Xxxx 318, which was ratified on 29 September 2015, is signed into law by the Governor of North Carolina.
AutoNDA by SimpleDocs
E-Verify compliance under 143-133. 3. (a) If this contract is awarded pursuant to North Carolina General Statutes (NCGS) 143-129 – (i) the contractor represents and covenants that the contractor and its subcontractors comply with the requirements of Article 2 of Chapter 64 of the NCGS; (ii) the words "contractor," "contractor’s subcontractors," and "comply" as used in this subsection (a) shall have the meanings intended by NCGS 143-129(j); and (iii) the City is relying on this subsection (a) in entering into this contract. (b) If this contract is subject to NCGS 143-133.3, the contractor and its subcontractors shall comply with the requirements of Article 2 of Chapter 64 of the NCGS.
E-Verify compliance under 143-133. 3. The contractor and its subcontractors shall comply with the requirements of Article 2 of Chapter 64 of the North Carolina General Statutes (NCGS). This E-Verify compliance under 143-133.3 section is intended to apply to only the contracts to which

Related to E-Verify compliance under 143-133

  • E-Verify Compliance The contractor represents and covenants that the contractor and its subcontractors comply with the requirements of Article 2 of Chapter 64 of the North Carolina General Statutes (NCGS). In this E-Verify Compliance section, "contractor," "its subcontractors," and "comply" shall have the meanings intended by NCGS 160A-20.1(b). The City is relying on this section in entering into this contract. The parties agree to this section only to the extent authorized by law. If this section is held to be unenforceable or invalid in whole or in part, it shall be deemed amended to the extent necessary to make this contract comply with NCGS 160A-20.1(b).

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

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

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

  • PCI-DSS Compliance Merchant shall be in full compliance with rules, regulations, guidelines and procedures adopted by any Card Association or Payment Network relating to the privacy and security of Cardholder and Card transaction data, including without limitation the most up-to-date version of the Payment Card Industry Data Security Standard (PCI-DSS), as amended from time to time by the Payment Card Industry Security Standards Council. Detailed information pertaining to aforementioned requirements may be found at xxxxx://xxx.xxxxxxxxxxxxxxxxxxxx.xxx. Additional information regarding security requirements may be found on the Card Association’s respective web sites.

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

  • Privacy Compliance The Provider shall comply with all applicable federal, state, and local laws, rules, and regulations pertaining to Student Data privacy and security, all as may be amended from time to time.

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

  • Certification of Compliance The Owner may permit the use, prior to sampling and testing, of certain materials or assemblies when accompanied by manufacturer's certificates of compliance stating that such materials or assemblies fully comply with the requirements of the contract. The certificate shall be signed by the manufacturer. Each lot of such materials or assemblies delivered to the work must be accompanied by a certificate of compliance in which the lot is clearly identified. Materials or assemblies used on the basis of certificates of compliance may be sampled and tested at any time and if found not to be in conformity with contract requirements will be subject to rejection whether in place or not. The form and distribution of certificates of compliance shall be as approved by the Owner. When a material or assembly is specified by "brand name or equal" and the Contractor elects to furnish the specified "brand name", the Contractor shall be required to furnish the manufacturer's certificate of compliance for each lot of such material or assembly delivered to the work. Such certificate of compliance shall clearly identify each lot delivered and shall certify as to:

  • PCI Compliance A. The Acquiring Bank will provide The Merchant with appropriate training on PCI PED and/or DSS rules and regulations in respect of The Merchants obligations. Initial training will be provided and at appropriate intervals as and when relevant changes are made to such rules and regulations.

Time is Money Join Law Insider Premium to draft better contracts faster.