Small Entity Compliance Guide Sample Clauses

Small Entity Compliance Guide. AGENCIES: Department of Defense (DoD), General Services Administration (GSA), and National Aeronautics and Space Administration (NASA). ACTION: Small Entity Compliance Guide.
AutoNDA by SimpleDocs
Small Entity Compliance Guide. AGENCY: Department of Defense (DoD), General Services Administration (GSA), and National Aeronautics and Space Administration (NASA). ACTION: Small Entity Compliance Guide. Canadian or Israeli End Products: applicable excepted materials or Line item No. Country of origin [List as necessary] Alternate III (Feb 2021). * * *
Small Entity Compliance Guide. AGENCY: Department of Defense (DoD), General Services Administration (GSA), and National Aeronautics and Space Administration (NASA). ACTION: Small Entity Compliance Guide. Small Business Regulatory Enforcement Fairness Act of 1996. It consists of a summary of the rule appearing in Federal Acquisition Circular (FAC) 2020–02, which amends the Federal Acquisition Regulation (FAR). An asterisk (*) next to a rule indicates that a regulatory flexibility analysis has been prepared. Interested parties may obtain further information regarding this rule by referring to FAC 2020–02, which precedes this document. These documents are also available via the internet at xxxx://xxx.xxxxxxxxxxx.xxx. DATES: November 22, 2019. FOR FURTHER INFORMATION CONTACT: Xx.

Related to Small Entity Compliance Guide

  • Compliance Plan (1) This paragraph (h) applies to any portion of the contract that—

  • Public safety compliance The Hirer shall comply with all conditions and regulations made in respect of the premises by the Fire Authority, Local Authority, the Licensing Authority or otherwise, particularly in connection with any event which constitutes regulated entertainment, at which alcohol is sold or provided or which is attended by children.

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

  • Requirement to Utilize HUB Compliance Reporting System Pursuant to Texas Administrative Code, Title 34, Part 1, Sections 20.285(f) and 20.287(b), TFC administers monthly administration HSP-PAR compliance monitoring through its HUB Compliance Reporting System commonly known as B2G. PSP and PSP’s subcontractors/subconsultants shall submit required PAR information into the B2G system. Any delay in the timely submission of PAR information into the B2G system will be treated as an invoicing error subject to dispute under Texas Government Code Section 2251.042.

  • Compliance Reporting a. Provide reports to the Securities and Exchange Commission, the National Association of Securities Dealers and the States in which the Fund is registered.

  • COMPLIANCE AND CERTIFICATION 25.1 Each Party shall comply at its own expense with all Applicable Laws that relate to that Party’s obligations to the other Party under this Agreement. Nothing in this Agreement shall be construed as requiring or permitting either Party to contravene any mandatory requirement of Applicable Law.

  • ETHICS COMPLIANCE All Bidders/Contractors and their employees must comply with the requirements of Sections 73 and 74 of the Public Officers Law, other State codes, rules, regulations and executive orders establishing ethical standards for the conduct of business with New York State. In signing the Bid, Bidder certifies full compliance with those provisions for any present or future dealings, transactions, sales, contracts, services, offers, relationships, etc., involving New York State and/or its employees. Failure to comply with those provisions may result in disqualification from the Bidding process, termination of contract, and/or other civil or criminal proceedings as required by law.

  • Statutory Compliance ‌ The Union and the Employer agree to cooperate fully in matters pertaining to the prevention of accidents and occupational disease and in the promotion of the health and safety of all employees. There shall be full compliance with all applicable statutes and regulations pertaining to the working environment.

  • 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 Program The Company has established and administers a compliance program applicable to the Company, to assist the Company and the directors, officers and employees of the Company in complying with applicable regulatory guidelines (including, without limitation, those administered by the FDA, the EMA, and any other foreign, federal, state or local governmental or regulatory authority performing functions similar to those performed by the FDA or EMA); except where such noncompliance would not reasonably be expected to have a Material Adverse Effect.

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