FACILITY COMPLIANCE REQUIREMENTS Sample Clauses

FACILITY COMPLIANCE REQUIREMENTS. A.8.1 Prior to receiving access to any Multnomah County Sheriff’s Office facility, all individuals shall submit a criminal history records check to determine access eligibility. Access eligibility is determined by the individual’s ability to obtain unescorted access within non-jail Sheriff’s Office facilities, and is verified through the submission of the applicant’s fingerprints to the Federal Bureau of Investigation. Any felony conviction would disqualify an applicant from obtaining unescorted access. There is no charge for this process. Once approved, the Multnomah County Sheriff’s Office will provide written access and security procedures to each individual. Each individual must read and sign statements verifying they have read and understand the information provided. Access will not be granted until the signed statements have been received. This process is performed when fingerprinted, and takes approximately 20-30 minutes. Individuals may request copies of the access and security procedures, or signed statements, at any time. Failure to follow access and/or security procedures may result in the termination of this Contract. A.8.2 If one of the facilities where Contractor performs Work is a health clinic accredited by the Joint Commission on Accreditation of Healthcare Organizations (JCAHO), then Contractor must comply with the JCAHO Safety Measures for Contractors attached as the Exhibit titled JCAHO Interim Life Safety Measures when providing services to those facilities.
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to FACILITY COMPLIANCE REQUIREMENTS

  • Compliance Requirements A. Nondiscrimination. The Contractor agrees to comply, and to require its subcontractor(s) to comply, with the nondiscrimination provisions of MCL 37.2209. The Contractor further agrees to comply with the provisions of Section 9:158 of Chapter 112 of the Xxx Arbor City Code and to assure that applicants are employed and that employees are treated during employment in a manner which provides equal employment opportunity.

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

  • Listing and Maintenance Requirements Compliance The Company has not in the two years preceding the date hereof received written notice from any stock exchange, market or trading facility on which the Common Stock is or has been listed or quoted to the effect that the Company is not in compliance with the listing, maintenance or other requirements of such exchange, market, trading or quotation facility. The Company has no reason to believe that it does not now or will not in the future meet any such requirements.

  • Standards Compliance 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 with Applicable Requirements In carrying out its obligations under this Agreement, the Sub-Adviser shall at all times comply with: (a) all applicable provisions of the 1940 Act, and any rules and regulations adopted thereunder; (b) the provisions of the registration statement of the Trust, as it may be amended or supplemented from time to time, under the Securities Act and the 1940 Act; (c) the provisions of the Declaration of Trust of the Trust, as it may be amended or supplemented from time to time; (d) the provisions of any By-laws of the Trust, if adopted and as it may be amended from time to time, or resolutions of the Board as may be adopted from time to time; (e) the provisions of the Internal Revenue Code of 1986, as amended, applicable to the Trust or the Funds; (f) any other applicable provisions of state or federal law; and In addition, any code of ethics adopted by the Sub-Adviser must comply with Rule 17j-1 under the 1940 Act, as it may be amended from time to time, and any broadly accepted industry practices, if requested by the Trust or the Adviser.

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

  • AML Compliance The Dealer Manager represents to the Company that it has established and implemented anti-money laundering compliance programs in accordance with applicable law, including applicable FINRA Conduct Rules, Exchange Act Regulations and the USA PATRIOT Act, specifically including, but not limited to, Section 352 of the International Money Laundering Abatement and Anti-Terrorist Financing Act of 2001 (the “Money Laundering Abatement Act,” and together with the USA PATRIOT Act, the “AML Rules”) reasonably expected to detect and cause the reporting of suspicious transactions in connection with the offering and sale of the Offered Shares. The Dealer Manager further represents that it is currently in compliance with all AML Rules, specifically including, but not limited to, the Customer Identification Program requirements under Section 326 of the Money Laundering Abatement Act, and the Dealer Manager hereby covenants to remain in compliance with such requirements and shall, upon request by the Company, provide a certification to the Company that, as of the date of such certification (a) its AML Program is consistent with the AML Rules and (b) it is currently in compliance with all AML Rules, specifically including, but not limited to, the Customer Identification Program requirements under Section 326 of the Money Laundering Abatement Act.

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

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!