Downloaded from https://www.everyspec.com from a complete, unified T&E program by efficiently using resources to shorten acquisition time. The process envisions the development of a single integrated test/simulation execution strategy, leading to a single system evalua- tion report. 5–1. Types of operational tests The OT is a field test of a system or item under realistic operational conditions with users who represent those expected to operate and maintain the system when it is fielded or deployed. All OTs will be categorized as listed in a through c . Tests should be selected from this listing with the objective of building an efficient and effective OT strategy to support a given program.
a. Pre-FRP-Common to materiel and C4I/IT systems. (1) Early User Test (EUT). (2) Limited User Test (LUT). (3) IOT. b. Post-FRP-Common to materiel and C4I/IT systems. (1) Follow-on Operational Test (FOT). (2) User Acceptance Test (UAT). c. As-required tests. (1) Customer Test (CT) is common to materiel and C4I/IT systems. (2) Supplemental Site Test (SST) is unique to C4I/IT systems. (3) Limited User Test. 5–2. Guidance applicable to all operational tests All operational tests related to the acquisition of systems under AR 70–1 will be documented in Part IV (or combined Parts III/IV) of the TEMP, approved in the TSARC process, and included in the FYTP. a.
Requirements for any added (out-of-cycle) testing must be generated by the T&E WIPT process, submitted as a change to the TEMP, and accepted by the TSARC unless a higher authority generates the requirements for added testing. Costs for unprogrammed testing must be borne by the activity that generates the requirement for conduct of the test. b. All tests that require the U.S. Army Forces Command (USAFORSCOM) and USATRADOC assets (such as user troops) must comply with USAFORSCOM and USATRADOC notification requirements.
Optimally, USAFORSCOM requires 2-year notification for units and a minimum of 120-day notification for individual soldiers, civilians, and other assets to comply with FM 25–100 training schedule. The USATRADOC requires a minimum of 110-day notification for soldiers, civilians, and other assets. In the area of personnel support, USAFORSCOM provides test players (unit and soldiers) and USATRADOC provides subject matter experts for its assigned programs. Subject matter experts are not data collectors. Other major Army commands (MACOMs) (USASMDC, USAMEDCOM, USAINSCOM, and others) provide personnel and other assets supporting OTs and have similar notification requirements.
All major Army commands referenced above will ensure that the impacted IMA garrison(s) are copy furnished as part of their respective notification process. c. The TSARC membership will resolve the details of test scheduling and out-of-cycle requirements. (See chap 9.) 5–3. Pre-full-rate production testing—common to materiel and C4I/IT systems Operational testing for systems normally occurs from program initiation (MS B) to the FRP decision review. Pre-FRP test requirements will be incorporated into the TEMP in support of MS B or C. The types of OT conducted prior to FRP are EUT, LUT, and IOT and are defined below. a. Early User Test.
The EUT, a generic term, encompasses all system tests employing representative user troops during concept and technology development or early in system development and demonstration. The EUT may test a materiel concept, support planning for training and logistics, identify interoperability problems, and/or identify future testing requirements. EUT provides data for the SER in support of MS B. FDT/E or Concept Experimentation Program (CEP) or both may comprise all or part of EUT. An EUT is conducted with RDTE funds. The EUTs use procedures that are described for IOT per paragraph c, below, and modified as necessary by maturity or availability of test systems and support packages.
The EUTs seek answers to known issues that must be addressed in the SER. b. Limited User Test. The LUT is any type of RDTE funded OT normally conducted during system acquisition other than the IOT. The LUT normally addresses a limited number of evaluation issues. The LUT will not be used to circumvent requirements for an IOT before the FRP decision review as prescribed by statute, DOD directives, and this regulation. A LUT will not be used to segment an IOT through a series of limited operational tests. If conducted during production and deployment, a LUT will not be used in lieu of a FOT.
(1) The LUT for materiel systems may be conducted to provide a data source for the system evaluation in support of the LRIP decision (MS C) and for reviews conducted before IOT. The LUT may be conducted to verify fixes to problems discovered in IOT that must be verified prior to the FRP decision review (that is, the fixes are of such importance that verification cannot be deferred to the FOT). 22 AR 73–1 • 1 August 2006