Test and Evaluation a. The Contractor shall provide the Authority’s Representative (Project – see Box 2 of Schedule 3 Annex A to the Contract – DEFFORM 111) with all appropriate paperwork, to the requirements of the Authority’s Representative to support conduct of test and evaluation; including but not limited to:
Test and Evaluation. 5.14.1 The Contractor shall provide services to test, evaluate, and qualify parts and assemblies. The Contractor shall also evaluate parts and assemblies prior to delivery of ORDALT Kits and INCO Spares or concurrent with installation at sites or aboard ships to ensure that delivered items meet all requirements for installation as specified in Systems Requirement Document (SRD). Tests include: Functional Bench Testing, First Article Testing, Environmental Qualification Testing (EQT), Integration Testing, Software Compatibility Testing, and any necessary regression testing. The Contractor shall submit test reports in accordance with CDRLs: A017, A018, A019, and A020.
Test and Evaluation. The transfer selection component is tested by determining the transfer of a test lemma in a given sentence context, and comparing it with the one of a reference translation. In the best case, all translations proposed by the Lt-Xfr component are identical with the transfers selected in the reference translations. As the LinguaDict lexicon contains many near translations, which can hardly be distinguished on the basis of conceptual transfer, a special evaluation procedure was adopted, consisting of three ranks instead of a binary decision: Rank 1: the translation proposed by the system is identical to the one in the test reference sentence Rank 2: the proposed translation close / synonym to the one in the test reference sentence. This was decided to be the case if o the proposed translation belongs to the same WordNet synset as the reference o the proposed translation is orthographically similar to the reference (like: ‘electric’ vs. ‘electrical’, ‘agglutinating’ vs. ‚agglutinative‘, ‘dialogue’ (UK) vs. ‘dialog’ (US) etc. Rank 3: the two translations are (still) different. Evaluation would allow rank1 and rank2, and reject rank3 results. Based on the three ranks, a simple scoring system is used (rank1 = 1, rank2 = 2, rank3 = 3) to compute an overall score: The lower the score the closer the translation is to the reference.
Test and Evaluation. The Contractor shall provide the Authority with all appropriate paperwork, to the requirements and acceptance of the Dstl Demand Owner to support conduct of test and evaluation; including but not limited to:
Test and Evaluation. The contractor shall conduct and evaluate the results of performance and quality conformance tests on production units to demonstrate full compliance of all equipment and software with PS/01/8855/002.
Test and Evaluation. The Contractor shall develop a GIMDE 2K Test Plan (TP), which shall govern all test and evaluation activities. The Contractor shall verify by means of the TP that all requirements of GIMDE 2K defined within the scope of this SOW have been met or exceeded. The TP shall detail test procedures and test scenarios to be followed as part of the evaluation process for each software deliverable defined with the scope of this SOW. The TP shall also include a detailed schedule as to the timing of all test and evaluation activities defined in the TP consistent with the PMS. The TP shall encompass all factory acceptance-testing activities. Factory acceptance testing as defined within this SOW includes: unit testing of each software deliverable defined within the scope of this SOW; subsystem testing both with respect to the software deliverables defined with the scope of this SOW, the Management Data Library (MDL) Information Access Services (IAS) and the GPT. The Contractor shall document instances in which test procedures fail to provide proof that a GIMDE 2K requirement(s) has been met in the form of a Discrepancy Report (DR). The Contractor shall repeat both unit and subsystem level testing if changes are made to a software deliverable after unit level tests on that software deliverable has been completed. The Contractor shall conduct unit and subsystem level testing consistent with GIMDE 2K PMS. The Contractor shall not be responsible for testing at the unit level, COTS software deliverables that have not been modified as the result of this acquisition. The Contractor shall perform all test and evaluation activities identified in the TP at the Contractors facility. The Contractor's test environment shall support or simulate a complete site configuration. In addition the Contractor shall document instances in which individual test procedures result in the system not performing as anticipated, but not associated with a requirement in the form of a Discrepancy Report (DR). The Contractor shall conduct Test Readiness Reviews and incorporate them into the TP as negotiated with the Government. The Contractor shall ensure software deliverables, which have passed factory acceptance testing as defined by this SOW, are delivered to the Reston NIMA Production Facility (NPF) consistent with the PMS. (CDRL A-013, Test Plan) (CDRL A-014, Discrepancy Report)
Test and Evaluation. Template will support a commercially based test and evaluation program that verifies the proper execution of software delivered by Template. This test program will be a functionally based test program based on the SRD delivered by Template. There will be three primary test steps in each phase, a factory acceptance test (FAT), an integration, checkout and test (IC&T) and a SAT. Software will be considered accepted upon completion of the FAT or upon full operational deployment, whichever comes first. Discrepancies from acceptance test procedures uncovered during the IC&T and SAT will be corrected by Template at no additional cost to the Government. The primary components of the test program are as follows: - Test Procedures - Template will develop and deliver to NIMA a list of test procedures based upon the SRD to verify the proper operation of the software developed for the GIMDE 2K Workflow / Production Planning effort. These procedures will be used for internal testing by Template, FAT, IC&T and SAT. - Test Readiness Review - prior to any formal testing of Template delivered software, a Test Readiness Review will be held with NIMA for formal Government approval to move to acceptance testing. The purpose of this review is to verify that the Test Procedures to be used by the Government and the Test Procedures used by Template for in house check out are identical. The review will also assure that the NIMA test laboratory is as anticipated by Template and that no significant difference between the NIMA lab and the Template lab exist. The Test Readiness Review also provides the Government with an assurance that the software has been thoroughly tested by Template in house and that the acceptance test has a high probability of success. Within the first 60 days of the program, Template will designate a test manager to coordinate the overall test program. This staff member will be part of the Deployment Team and work closely with the Requirements Team, who will do the actual testing. Similarly, NIMA will provide a primary point of contact for testing issues to work with the Template testing lead to assure that all activities are coordinated before testing begins.
Test and Evaluation. The HFV Class of Therapeutics will be developed in full accordance with FDA regulations and guidelines established by CFR 21, the Pure Food and Drug Act. The FDA mandates test and evaluation processes that follow a series of phases that establish the effectiveness and safety of new drugs. The FDA issues extensive mandatory guidance and requires submission of substantive evidence for FDA review. Only after FDA approval can work proceed from one phase to the next. The FDA process is mandatory for licensure. The Government will utilize the Contractor’s validated information and FDA process documentation in evaluating progress and conformance with TPP Guidelines.
Test and Evaluation. The contractor shall conduct tests to verify flight readiness of the munition system. This testing shall include all checks to provide a high level of confidence that the munition system will function as designed during flight testing. This test includes electrical and mechanical functioning, subsystem operation, and system integrity. The contractor shall conduct these tests, to include setup troubleshooting, data recording, real-time data analysis, and test analysis and documentation, as delineated in task orders. Test and Evaluation support efforts shall include test range reservation, range support, delivery of the munition system and test equipment to the test site, installation and assembly at the test site, preflight checkout, conduct of the test, and acquisition of test data.
Test and Evaluation. If, after visual and functional inspections, an item is found to meet manufacturer's minimum performance specifications, the contractor will be allowed the firm fixed price for test and evaluation. The Failure Data Report shall be prepared, indicating the Coast Guard's reported failure, and included with the returned component, as well as with the invoice.
