Quality Assurance Report Sample Clauses

Quality Assurance Report. The monthly report shall include a detailed summary of the steps that are being employed to ensure quality construction and workmanship. Each report shall specifically address issues that were raised by the Department and/or its Program Manager during the prior month and outline the steps that are being taken to address such issues.
Sample 1Sample 2Sample 3See All (34)
AutoNDA by SimpleDocs
Quality Assurance Report. The contractor shall provide a Quality Assurance Report as specified in each individual TO.
Sample 1Sample 2Sample 3See All (5)
Quality Assurance Report. The Contractor shall submit a Quality Assurance Report that summarizes information collected from the Quality Assurance plan and describes how the information will be used to improve service delivery.
Sample 1Sample 2
Quality Assurance Report. The Contractor must submit annually on July 1, a Quality Assurance Report that summarizes the information collected per the Quality Assurance plan and describes how the information will be used to improve service delivery, including a timeline for such improvements. The first annual report is due on July 1, 2019.
Sample 1Sample 2
Quality Assurance Report. The monthly report and biweekly update shall include a detailed summary of the steps that are being employed in order to ensure quality construction and workmanship. Each report and update should specifically address issues that were raised by the Department and/or its Program Manager during the prior reporting period and outline the steps that are being taken to address such issues.
Sample 1
Quality Assurance Report. Vendor shall provide a monthly Quality Assurance Report to the Citizens’ Contract Manager which covers the calendar month. The Quality Assurance Report shall include the following information:
Sample 1
Quality Assurance Report. The program shall submit to EPA by July of each year a report providing basic statistics on the quality assurance program for January through December of the previous year, including:
Sample 1
AutoNDA by SimpleDocs
Quality Assurance Report. D1.2 (M26) Quality Assurance Report. D1.3 (M26) Web site for Toolkit Dissemination Milestones and expected result M0 M4 M8 M12 M16 M20 M23, Project Management Meetings (7) M18 Public demonstration of the project (toolkit and prototypes of demonstrators) M26 Final prototype and demonstrators B3. Workpackage description Workpackage number : 2 Start date or starting event: Month 0 Participant number: 1 2 3 4 5 6 7 Person-months per participant: 4 5 2 2 8,6 3 2 Objectives • To identify requirements on systems for affective autonomous agents • To specify architectural models for affective autonomous agents • To design a framework for affective autonomous agents development • To implement the framework. • To develop a toolkit and necessary APIs for affective autonomous multi-agent systems development • To define and formalise an end-to-end engineering methodology for the design and development • To validate the methodology and framework by building agent demonstrators, demonstrating different concepts concerning structuring, packaging and visualising agents. Enabling the vision of the project beyond the scope of just the implemented demonstrators and current technologies. • To disseminate information about achieved knowledge to standard bodies related to agent technologies. Description of work This workpackage serves as a focal point for co-ordinating and integrating the defined cognitive and affect components which are required to implement affective computing in real-time multi-agent applications. It is also in this workpackage that a framework for enriching interactions and applications with an affective dimension will be designed. This framework will provide some guidelines for enriching applications with affective interaction and methodologies for developing affective real-time multi-agent systems. Which will be subsequently used for the demonstrators developed in workpackage 6. Workpakage 3 will serve to provide the input sensory components required for affective real-time mulit-agent applications; workpackage 4 will provide the internal computational mechanisms for reasoning, learning and affective planning required for affective agent behaviour; whereas workpackage 5 will express the agent behaviour through different modalities. The results achieved in these workpackages will be integrated through the use of common APIs as a set of tools resulting in a toolkit for affective real-time multi-agent system development.
Sample 1
Quality Assurance Report. The Contractor shall be required to provide a written report detailing the findings of its quality assurance program, as outlined in Section II., F. This report shall be submitted on a semi-annual basis to the On-Site Contract Monitor with a copy to the Contract Manager (or designee).
Sample 1

Related to Quality Assurance Report

  • 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 Requirements There are no special Quality Assurance requirements under this Agreement.

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

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

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

  • Project Monitoring Reporting and Evaluation The Recipient shall furnish to the Association each Project Report not later than forty-five (45) days after the end of each calendar semester, covering the calendar semester.

  • Compliance Report The Subservicer agrees that it shall permit, not more than once per year, the Servicer, the Issuer, the Indenture Trustee or the Indenture Administrator, as the Indenture Trustee’s designee, to conduct or have conducted a procedural audit regarding the Subservicer’s compliance with the requirements of the Higher Education Act or the terms of this Agreement. Such audits shall be at the expense of the Servicer.

  • Drug-Free Workplace Certification As required by Executive Order No. 90-5 dated April 12, 1990, issued by the Governor of Indiana, the Contractor hereby covenants and agrees to make a good faith effort to provide and maintain a drug-free workplace. The Contractor will give written notice to the State within ten (10) days after receiving actual notice that the Contractor, or an employee of the Contractor in the State of Indiana, has been convicted of a criminal drug violation occurring in the workplace. False certification or violation of this certification may result in sanctions including, but not limited to, suspension of contract payments, termination of this Contract and/or debarment of contracting opportunities with the State for up to three (3) years. In addition to the provisions of the above paragraph, if the total amount set forth in this Contract is in excess of $25,000.00, the Contractor certifies and agrees that it will provide a drug-free workplace by:

  • Monthly MWBE Contractor Compliance Report A. In accordance with 5 NYCRR § 142.10, Contractor is required to report Monthly MWBE Contractor Compliance to OGS during the term of the Contract for the preceding month’s activity, documenting progress made towards achievement of the Contract MWBE goals. OGS requests that all Contractors use the New York State Contract System (“NYSCS”) to report subcontractor and supplier payments made by Contractor to MWBEs performing work under the Contract. The NYSCS may be accessed at xxxxx://xx.xxxxxxxxxxxxxx.xxx/. This is a New York State-based system that all State agencies and authorities will be implementing to ensure uniform contract compliance reporting throughout New York State.

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

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