Quality Assurance Report Sample Clauses

Quality Assurance Report. The contractor shall provide a Quality Assurance Report as specified in each individual TO.

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.

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.

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.

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: a. A minimum of five (5) Interpretation Services call reviews, preferably representing more than one (1) of the languages referenced on Attachment A. b. Name of Interpreter being reviewed. c. Average speed of answer. d. Quality measurement of the Interpretation Services call. e. If available, one (1) audio and written Transcription Services review. f. Quality measurements of any Transcription Services reviews.

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

Quality Assurance Report. D1.2 (M26) Quality Assurance Report. D1.3 (M26) Web site for Toolkit Dissemination 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 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 • 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. 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.