Test Documentation. Test documentation shall include a complete description of any unique or unusual test procedures/methods, including environmental stresses, and all data required to duplicate electrical test set-ups, jigs, fixtures or tests stations. The contractor shall include a description of software verification and audit procedures to ensure the performance and functional requirements defined in the software technical baseline are achieved by the design and that the software design is accurately documented in the software technical baseline and updates. Documentation shall define all parameters and reference all associated drawings and/or specifications (by number and title) that specify the performance of the item to be tested. All alignment requirements shall be defined through the use Government-approved contractor test equipment, or standard equipment. When special test/inspection equipment is required, the contractor will create Special Inspection Equipment Drawings and Associated Lists as required by applicable Notices of Revision.
Test Documentation. The Contractor shall prepare an Agenda and Test Memoranda of the required tests and trials for the vessel in accordance with the requirements set forth herein. Two copies of the Agenda and Test Memoranda shall be submitted to the COR for review and approval 60 days prior to the scheduled testing (see Contract Section H, Clause H02).
Test Documentation. 8 4.0 MILESTONE DESCRIPTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 TABLE 4.0-1 TNPC MILESTONES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Test Documentation. 7.2.1 Test Requirements Specification and Detailed Test Plans The Contractor shall prepare and deliver Test Requirements Specifications and Detailed Test Plans at System, Subsystem and Equipment Level in accordance with the requirements of the CDRL. These documents shall reflect the requirements of the Overall Test Plan and shall provide an overview of each of the tests to be performed at the appropriate level to demonstrate that the specified requirements are met.
Test Documentation. QUALCOMM shall deliver to Buyer one full set of test data for one sample of a GSP-1700, SDVM and GCK-1700 Car Kit representative of the production run. The test data shall be collected in agreement with the test plan provided to Buyer as part of the Production Readiness Review described in Section 25.3. QUALCOMM will make available for review by Buyer at QUALCOMM's offices, test results and data for all other GSP-1700s, SDVMs and GCK-1700 Car Kits. This information is confidential information subject to Section 18 of the Supply Terms and Conditions."
Test Documentation. Test documentation will be developed by both the subsystem suppliers and Motorola to describe the applicable test processes. These documents will be made available to Iridium for review at least 30 days prior to testing. Copies of test reports will be provided to Iridium, Inc. within 30 days following testing. Test procedure documents will contain information which is used to verify or test functional capabilities of the Gateway Equipment. These procedures will contain information such as: test requirements specifications, system under test scenarios, test plans, stimulus/response, verification matrices, etc. Test acceptance documents will contain the test procedures which will be executed. A pass/fail criteria will be developed for the key performance specifications. Iridium, Inc. will be offered the opportunity to witness testing. Test report documents will contain the results of the test effort. TND test efforts will include supplier acceptance testing, lab testing, Beta Site pre-acceptance testing, or demonstration testing. The test reports will provide information as to the success and status of the system under test including an action plan to correct deficiencies or defects discovered during testing. ---------------------------------- * Information has been omitted and filed separately with the Commission pursuant to Rule 406 of the Securities Act of 1933.
Test Documentation. 3.32.1. Each test and inspection shall be documented as per applicable IEEE standard for each test.
Test Documentation a. AACS LA has prepared a document containing a description of tests that will be required pursuant to the Certification Testing requirements of the Adopter Agreement (“Test Scenario Document”) and a related list of equipment to be used to conduct such tests (“Test Equipment List”). Upon payment by Adopter of the fee indicated below, AACS LA will supply Adopter with one copy of the Test Scenario Document and one copy of the Test Equipment List solely for use as provided in this Addendum.
Test Documentation. The long-term usefulness of test data and results can only be assured by a full documentation and preservation of the information for later reference. This can serve later comparison or review of procedures in retrospective. Such documentation should include sketches and photographs of the test set-up, test protocols and observations, full (raw) data records, sensor IDs/ positions/ calibration information, test protocols, data evaluation, results and potential reports. Sensor calibration and traceability The use of sensors calibrated on a regular basis is the basic prerequisite for generating valid test data. Established calibration procedures should be documented and calibrations traceable to national or internal standards.
Test Documentation. As part of the system or software supplied, a document shall be provided that describes the test plan, test procedures that show how the security mechanisms were tested, and results of the security mechanisms' functional testing.
