Downloaded from https://www.everyspec.com (2) The LUT for C4I/IT may be conducted to provide a data source for system assessments in support of acceptance of hardware and commercial off-the-shelf software for operational testbeds and interim blocks of software functionality prior to the IOT. Additional LUTs may be conducted to verify fixes to problems discovered in IOT or to support acceptance of blocks of functionality subsequent to the IOT but prior to acceptance of the objective system. c. Initial Operational Test.
Per the Defense Acquisition Guidebook, programs will be structured to determine the operational effectiveness, suitability, and survivability of a system operated by typical users under realistic conditions (such as combat and representative threat). Section 2399, title 10, U.S. Code, requires initial operational test and evaluation (IOT&E) before a major defense acquisition program proceeds beyond LRIP. Before an IOT for a major defense acquisition program can commence, the DOT&E approves the operational test plan for the program. (1) For C4I/IT, the IOT uses a production database and is executed on target hardware.
The C4I/IT IOT should include the conversion, training, and software verification and validation processes to ensure that the system meets the collective user and proponent needs, can be operated by users, and is ready for deployment. (2) System evaluation based on data sources other than IOT may be appropriate when coordinated with the T&E WIPT. 5–4. Post-full-rate production testing—common to materiel and C4I/IT systems Operational testing in post-FRP supports development and fielding subsequent to the IOT, and supports PDSS. Post- FRP testing requirements will be incorporated into the TEMP in support of the FRP decision review. a. Follow-on Operational Test.
(1) Production and deployment testing for materiel systems normally consists of a Follow-on Operational Test (FOT). An FOT is an OT that may be necessary during or after production to refine the estimates made during IOT, provide data to evaluate changes, and verify that deficiencies in materiel, training, or concepts have been corrected. The FOT may also provide data to ensure that the system continues to meet operational needs and that it retains its effectiveness in a new environment or against a new threat. (2) For software intensive systems, if OT is required to support PDSS, then the operational tester will conduct a FOT.
Post-FRP test requirements will be incorporated into the TEMP in support of the FRP decision review. When the strategy is to develop and field additional blocks of functionality subsequent to the IOT, OT will be conducted on intermediate blocks and an FOT will be conducted prior to the acceptance of the objective system. b. User Acceptance Test. If OT is required to support PDSS, then the operational tester will conduct a FOT. Otherwise the functional proponent will conduct an UAT. The combat developer will conduct an UAT for systems that are required to support PDSS. For systems that have both a functional proponent and a combat developer, the functional proponent will conduct the UAT.
The UAT is limited in scope relative to an FOT. The UAT’s primary purpose is to verify the functionality of the changes to the C4I/IT in the user environment. 5–5. As-required testing—common to materiel and C4I/IT systems All as-required testing requirements that pertain to a specific system acquisition will be incorporated into the TEMP. a. Customer Test. A CT is conducted for a requesting agency. The requesting agency coordinates support require- ments and provides funds and guidance for the test. A CT is not directly responsive to a MS decision. If coordination is required to obtain USAFORSCOM or USATRADOC support for the test, the TSARC process is used.
A CT will not be used to circumvent requirements for an IOT. b. Supplemental Site Test. A SST may be necessary for C4I/IT that execute in multiple hardware and operating system environments if there are differences between user locations that could affect performance or suitability. The SST supplements the IOT and UAT. 5–6. Use of system contractors and developers in operational test and evaluation 10 USC 2399, as implemented by the Defense Acquisition Guidebook, prohibits system contractors from participating in the initial operational test and evaluation (IOT&E) for ACAT I and II programs.
This policy applies to the IOT&E of all programs as described in a through c below and is meant to prevent system contractor manipulation or influence during the IOT&E or activities that provide input for consideration in the system evaluation. a. During IOT&E or associated activities, system contractor personnel will not— (1) Participate, except to the extent that they are involved in the operation, maintenance, and other support of the system when it is deployed in combat. (2) Establish criteria for data collection, performance assessment, or evaluation activities for OT data.
(3) Participate in collecting, reducing, processing, authenticating, scoring, assessing, analyzing, or evaluating OT data. (4) Attend or be directly involved as members or observers in data authentication group sessions or RAM scoring and assessment conferences that address data supporting evaluation and assessment of their systems. b. Discussions with system contractor and developer personnel may be necessary to ensure full technical understand- ing of test incidents observed during IOT&E or activities. All such discussions will be held separately from any scoring 23 AR 73–1 • 1 August 2006