Additional Background Screening Process and Standard Sample Clauses

Additional Background Screening Process and Standard. Level 2 If requested by DMS with respect to the security needs of a Customer, Contractor shall have an additional background screening performed for each Person providing service to the User, having access to the User’s data, or who may enter the User’s facilities. The additional background screening shall be a Level 2 Background Check, as defined in Florida Statutes, performed through FDLE.
AutoNDA by SimpleDocs

Related to Additional Background Screening Process and Standard

  • Background Screening VENDOR shall comply with all requirements of Sections 1012.32 and 1012.465, Florida Statutes, and all of its personnel who (1) are to be permitted access to school grounds when students are present, (2) will have direct contact with students, or (3) have access or control of school funds, will successfully complete the background screening required by the referenced statutes and meet the standards established by the statutes. This background screening will be conducted by SBBC in advance of VENDOR or its personnel providing any services under the conditions described in the previous sentence. VENDOR shall bear the cost of acquiring the background screening required by Section 1012.32, Florida Statutes, and any fee imposed by the Florida Department of Law Enforcement to maintain the fingerprints provided with respect to VENDOR and its personnel. The parties agree that the failure of VENDOR to perform any of the duties described in this section shall constitute a material breach of this Agreement entitling SBBC to terminate immediately with no further responsibilities or duties to perform under this Agreement. VENDOR agrees to indemnify and hold harmless SBBC, its officers and employees from any liability in the form of physical or mental injury, death or property damage resulting from VENDOR’s failure to comply with the requirements of this section or with Sections 1012.32 and 1012.465, Florida Statutes.

  • Background Screening and Security 14 These General Contract Conditions supersede and replace in their entirety all General Contract Conditions, Form PUR 1000, which is incorporated by reference in Rule 60A-1.002, Florida Administrative Code (F.A.C.)

  • BACKGROUND STATEMENT The Borrower has requested that the Lenders make available to the Borrower revolving credit facilities in the aggregate principal amount of $725,000,000. The Borrower will use the proceeds of these facilities as provided in Section 5.5. The Lenders are willing to make available to the Borrower the credit facilities described herein subject to and on the terms and conditions set forth in this Agreement.

  • Design Criteria and Standards All PROJECTS/SERVICES shall be performed in accordance with instructions, criteria and standards set forth by the DIRECTOR.

  • Changes to Specifications All Specifications and any changes thereto agreed to by the Parties from time to time shall be in writing, dated and signed by the Parties. No change in the Specifications shall be implemented by Cardinal Health, whether requested by Reliant or requested or required by any Regulatory Authority, until the Parties have agreed in writing to such change, the implementation date of such change, and any increase or decrease in costs, expenses or fees associated with such change. Cardinal Health shall respond promptly to any request made by Reliant for a change in the Specifications, and both Parties shall use commercially reasonable, good faith efforts to agree to the terms of such change in a timely manner. If after initial Product qualification, Reliant requests a change in the Specifications for its own benefit or to comply with the requirements of a Regulatory Authority, the Specifications shall be amended as soon as [***]: Certain information on this page has been omitted and filed separately with the Commission. Confidential treatment has been requested with respect to the omitted portions. possible after a request is made for any change in Specifications, and Cardinal Health shall notify Reliant of the costs associated with such change and shall provide such supporting documentation as Reliant may reasonably require. Reliant shall pay all costs associated with such Reliant-requested changes or changes required by a Regulatory Authority as may be agreed upon by the Parties. Changes, agreed to between the Parties, for the benefit of Cardinal Health, shall be at the expense of Cardinal Health. If there is a conflict between the terms of this Agreement and the terms of the Specifications, this Agreement shall control.

  • Introduction and Background 1.1 The purpose of this Schedule 2 (Contract Services and Contract Supplies) is to set out the characteristics of the Contract Services and/or Contract Supplies (as the case may be) and Funding that the Provider will be required to make available to all Contracting Authorities in relation to Lot 1 and/or Lot 2 (as the case may be) and to provide a description of what the Contract Services and/or Contract Supplies (as the case may be) and Funding will entail.

  • MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.

  • Project Background 6.1.1. Brief description of Contracting Agency’s project background and/or situation leading to this Project

  • Technical Specifications 1. A procuring entity shall not prepare, adopt or apply any technical specification or prescribe any conformity assessment procedure with the purpose or effect of creating an unnecessary obstacle to trade between the Parties.

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

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