Downloaded from https://www.everyspec.com c. An EDP may be developed by USATEC for a specific event or combination of events as appropriate. It provides a detailed overview of the test concept and design with factors, conditions, and treatments that govern the event requirements. Some examples are: independent variables, method of control, and constraints. The EDP will include any limitations that restrict the ability to obtain the required data. The content and degree of detail contained in the EDP must be sufficient to ensure the event is adequately planned, designed, prudently resourced, and will produce the required information. d.
Each EDP is jointly approved within the T&E activity or command conducting the event and the system evaluator. For those programs on the OSD T&E Oversight List, for OT and for LF, the EDP will be transmitted through TEMA for the Army T&E Executive submission to DOT&E for approval. 10–5. Test and evaluation briefings to the Office of the Secretary of Defense For a system on the OSD T&E Oversight List, briefings relevant to T&E during the process leading to the Defense Acquisition Board review or C4I/IT OIPT will be conducted in accordance with the Defense Acquisition Guidebook. 10–6.
Test and evaluation briefings to the Department of the Army For any system that must be sent to HQDA for review, as a minimum, draft T&E reports, authenticated by the responsible agency, are required before Army Systems Acquisition Review Council (ASARC) reviews. If necessary, the PEO or MATDEV chairs a T&E review 30 days before the decision review. The purpose is to review the adequacy of past tests, test results and evaluations, planning for future testing (including critical issues and requirements), and modifications of the test strategy to accommodate the evolving acquisition strategy.
Inconsistencies and problems not resolved in this forum will be brought to the attention of the Army T&E Executive. The Army T&E Executive may request a separate T&E review. 10–7. Detailed Test Plan A formal DTP is not a DA requirement except for congressionally mandated, or otherwise directed, LFT&E (see para 10–14). However, detailed test planning is required by the test organization that performs the testing and is usually documented in the DTP. 10–8. Outline Test Plan An OTP will be prepared for all tests that require Army or other service personnel or other resources (for example, training ranges, OT instrumentation, flying hours, standard ammunition, training devices, or other items).
a. An OTP is a formal resource planning and tasking document that is prepared for TSARC review (see chap 9). All programs must have an Army approved TEMP before they can compete in the TSARC process for resources and commitments to provide such resources. All new and revised OTPs will be coordinated with the system’s MATDEV before being submitted to the TSARC. b. An OTP identifies and schedules the required resources and provides administrative information necessary to support each test. c. The OTPs are prepared by the T&E organization (for example, USATEC, USAMEDCOM) and submitted to the TSARC. 10–9.
Five-Year Test Program The Five-Year Test Program (FYTP) is a compendium of OTPs approved by HQDA DCS, G–3 for the Chief of Staff, Army (see chap 9). USATEC publishes and disseminates the FYTP. It includes all OTPs for tests scheduled for the next 5 years. The OTPs contained in the FYTP must be continuously updated in TSARC working group sessions as data becomes available. The OTPs for DTs that require user troops must be included in the FYTP. When the FYTP is approved, the OTPs for the first 2 years (current and budget) become Army-level taskers. The remaining 3 years of the FYTP are for out-year planning purposes. The FYTP is updated twice per year in conjunction with the GO TSARC. 10–10.
Test Incident and Corrective Action Report a. The MATDEVs, combat developers, evaluators, and other organizations participating in the acquisition process must be informed of system performance during tests in a timely manner so that corrective actions may be initiated and a system evaluation conducted. b. A TIR describes the minimum essential data for test incidents as they occur, their respective corrective actions and status, and other test information. The TIR form and data stream formats will be used for reporting these data for all pre-FRP tests and for tests in production and deployment supporting a materiel release decision.
The TIRs are required for all tests in the TEMP and are entered electronically into ATIRS (ATIRS@atc.army.mil). c. Critical and major TIRs require the production of corrective action data. All other TIRs will be reviewed for possible corrective action. A CAR team (CART) will review all corrective action data to verify that all proposed corrective actions are appropriate and effective. The MATDEV, combat developer (or functional proponent), and system evaluator comprise the members on the CART. The testers serve as advisors. d. Test incident corrective action data, with the exception of classified data, will be entered promptly by the 33 AR 73–1 • 1 August 2006