Quality Control File Sample Clauses

Quality Control File a. A quality control file containing a record of all inspections conducted by Vendor and all corrective actions taken ("Quality Control File") shall be recorded, maintained, and updated and reported to the Board by Vendor throughout the Term and made available to the Board or Board Designee upon request. Vendor is fully responsible for the quality and operational data contents, integrity and for their safe retention.
AutoNDA by SimpleDocs

Related to Quality Control File

  • Personnel File (a) An employee, or the President of the Union (or the President's designate) with the written authority of the employee, shall be entitled to review an employee's personnel file, in the office in which the file is normally kept. The employee or the President, as the case may be, shall give the Employer adequate notice prior to having access to such files.

  • ODUF Physical File Characteristics 6.2.1 ODUF will be distributed to Image Access via Secure File Transfer Protocol (FTP). The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (one hundred seventy-five (175) byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one (1) dataset per workday per OCN. If BellSouth determines the Secure FTP Mailbox is nearing capacity levels, BellSouth may move the customer to CONNECT:Direct file delivery.

  • EODUF Packing Specifications 7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • Implementation Report Within 150 days after the Effective Date, Extendicare shall submit a written report to OIG summarizing the status of its implementation of the requirements of this CIA (Implementation Report). The Implementation Report shall, at a minimum, include:

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

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

  • Deliverables Upon satisfactory completion of the work authorization, the Engineer shall submit the deliverables as specified in the executed work authorization to the State for review and acceptance.

  • Physical File Characteristics 6.2.1 The Optional Daily Usage File will be distributed to <<customer_name>> via an agreed medium with CONNECT:Direct being the preferred transport method. The Daily Usage Feed will be a variable block format (2476) with an LRECL of 2472. The data on the Daily Usage Feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis (Monday through Friday except holidays). Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

  • Inspection Checklist (check one) ☐ In order to avoid disagreements about the condition of the Premises, at the time of accepting possession of the Premises, Tenant will complete the Inspection Checklist incorporated herein by reference and attached hereto as Exhibit B and record any damage or deficiencies that exist at the commencement of the Term. Landlord will be liable for the cost of any cleaning or repair to correct damages found at the time of the inspection. Tenant will be liable for the cost of any cleaning and/or repair to correct damages found at the end of the Term if not recorded on the inspection checklist, normal wear and tear excepted. ☐ The Tenant is NOT required to complete an inspection checklist.

  • Drug Testing Procedures a. The testing procedures and safeguards provided in this policy shall be adhered to by any laboratory personnel administering departmental drug tests.

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