Downloaded from https://www.everyspec.com MATDEV by electronic means into the ATIRS to enable all members of the T&E community access to the data and information in a timely manner. The data will also be provided to others per agreements reached by the T&E WIPT. 10–11. Developmental Test Readiness Statement The Developmental Test Readiness Statement is a written statement prepared by the chair of the DTR Review (DTRR) as part of the minutes. The statement documents that the materiel system is ready for the PQT or that the C4I/IT is ready for the SQT. 10–12.
Operational Test Readiness Statement Operational Test Readiness Statements, as specified in the OTP MS schedule, are provided by each of the following: combat developer, MATDEV, training developer/trainer, test unit commander, or functional proponent, before the start of OT. The OTRSs are presented during the OTRR to certify the readiness of the system for testing in each member’s area of responsibility. An OTRS may also be required for some FDT/E and will be specified in the OTP if required. 10–13. Test reports a. Developmental Test Report.
The developmental TR is a formal document of record that reports the data and information obtained from DT and describes the conditions that actually prevailed during test execution and data collection. It may be an abbreviated or formal report or a test (firing) record. The developmental TR includes an audit trail of deviations from the planned testing. A DT event may be conducted and reported by the contractor. In these cases, a contractor test plan must be coordinated with and briefed to the T&E WIPT. The contractor test event must be observed by Government T&E personnel to validate the data for inclusion in the system evaluation. b. Operational reporting. (1) Operational Test Report.
The operational TR provides the results of a test event conducted on a system or concept that includes findings-of-fact, based on the data collected. It consists of a detailed report of test conditions and test results to include, as appropriate, detailed displays of data from the tests, and testers’ observations. The operational TR is completed to the level of the aggregation of data and supporting analyses as contained in the approved EDP. (2) Operational Test Data Report. In addition to the TR, the operational Test Data Report (TDR) is provided for some systems selected by the T&E command.
The TDR provides a detailed test description, test limitations, test team observations, and a level 3 (authenticated) test database. 10–14. Live fire test and evaluation documentation a. A LFT&E Strategy will be developed for each program designated for LFT&E. The LFT&E Strategy is approved as an integral part of the TEMP via the TEMP approval process at DOT&E. b. In the case of OSD LFT&E oversight programs that do not require the TEMP to be provided to HQDA and DOD for approval, the LFT&E strategy is forwarded separately through TEMA for the Army T&E Executive submission to DOT&E for approval (see para 4–2 b (6)). c.
LFT&E EDP and DTP documents, as identified in the LFT&E plan matrix of the LFT&E strategy, satisfy the DOD requirement for a Detailed T&E Plan for LFT&E. They are prepared to provide the information required by the Defense Acquisition Guidebook. d. Pre-shot predictions will be identified in the LFT&E Plan Matrix in the TEMP. Prior to the test, pre-shot predictions of expected LFT outcomes will be prepared (by USASMDC for strategic missiles and by U.S. Army Research Laboratory, Survivability Lethality Assessment Directorate for all other systems). The Pre-shot Prediction Reports are submitted for information only through TEMA for the Army T&E Executive submission to DOT&E. e.
The LFT results are contained in the final test report(s). The evaluation findings and recommendations are contained in the SER. Final Test Reports are provided through TEMA for the Army T&E Executive submission to DOT&E. If the DTP has been approved by the DOT&E, the final test report for that LFT phase will be approved by the Army T&E Executive. For other LFT phases, the testing agency approves the report. The SER is approved by the Commander USATEC or designee and is submitted through the Army T&E Executive to the DOT&E. 10–15. System Evaluation Report a. System Evaluation Report.
The System Evaluation Report (SER) documents independent evaluation findings and recommendations of system operational effectiveness, suitability, and survivability. It addresses and answers the critical operational issues and additional evaluation focus areas in the SEP based on all available credible data and the evaluator’s analytic treatment of the data. An USATEC System Analysis Report (SAR) provides the detailed analyses that support a SER. A SAR accounts for all issues and measures contained in the System Evaluation Plan. b. System assessments. System assessments provide input to non-MS decisions (such as decision reviews, interim progress reviews, materiel release, or upon request).
The scope of issues to be addressed by the SA is flexible in that it may or may not cover all aspects of effectiveness, suitability, and survivability. The SA is not usually tied to a MS decision review, but is developed as required. A SAR is also prepared to support a SA when the analysis is too detailed or inappropriate for inclusion in the SA and addresses only those issues and measures contained in the SA. c. MANPRINT Assessment. The MANPRINT assessment report is the formal overall assessment of the analyses 34 AR 73–1 • 1 August 2006