COUNTY’S QUALITY ASSURANCE PLAN The County or its agent will evaluate the Contractor’s performance under this Contract on not less than an annual basis. Such evaluation will include assessing the Contractor’s compliance with all Contract terms and conditions and performance standards. Contractor deficiencies which the County determines are severe or continuing and that may place performance of the Contract in jeopardy if not corrected will be reported to the Board of Supervisors. The report will include improvement/corrective action measures taken by the County and the Contractor. If improvement does not occur consistent with the corrective action measures, the County may terminate this Contract or impose other penalties as specified in this Contract.
Quality Assurance Plan The contractor shall develop and submit to NMFS a contractor Quality Assurance Plan, as referenced in Section F.5.3, which details how the contractor will ensure effectiveness and efficiency of collection efforts as well as the quality of data collected by its At-Sea Monitors. The contractor shall further establish, implement, and maintain a Quality Assurance Management program to ensure consistent quality of all work products and services performed under this contract.
Quality Assurance/Quality Control Contractor shall establish and maintain a quality assurance/quality control program which shall include procedures for continuous control of all construction and comprehensive inspection and testing of all items of Work, including any Work performed by Subcontractors, so as to ensure complete conformance to the Contract with respect to materials, workmanship, construction, finish, functional performance, and identification. The program established by Contractor shall comply with any quality assurance/quality control requirements incorporated in the Contract.
Quality Assurance The parties endorse the underlying principles of the Company’s Quality Management System, which seeks to ensure that its services are provided in a manner which best conforms to the requirements of the contract with its customer. This requires the Company to establish and maintain, implement, train and continuously improve its procedures and processes, and the employees to follow the procedures, document their compliance and participate in the improvement process. In particular, this will require employees to regularly and reliably fill out documentation and checklists to signify that work has been carried out in accordance with the customer’s specific requirements. Where necessary, training will be provided in these activities.
Quality Assurance Program An employee shall be entitled to leave of absence without loss of earnings from her or his regularly scheduled working hours for the purpose of writing examinations required by the College of Nurses of Ontario arising out of the Quality Assurance Program.
Product Specific Terms these terms apply to specific Products referenced in this section.
Product Specifications The Company agrees that all Products sold to Xxxx hereunder shall conform to the respective specifications set forth on Schedule A or to such other specifications as are from time to time agreed upon by the Parties.
Quality Assurance Requirements There are no special Quality Assurance requirements under this Agreement.
Agreement Deviation/Compliance Does the vendor agree with the language in the Vendor Agreement?
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.
