Department of Defense INSTRUCTION

DoDI 5000.02, January 7, 2015
(b) For integrated test results to count for operational testing, the lead OTA must
develop a plan for the integrated test to be approved by DOT&E before the start of testing that, at
a minimum, details the required test realism and conditions, operational test objectives,
operational test metrics and data collection requirements. Data collected outside an approved
OTP or major LFTP can be used for a DOT&E operational or live fire evaluation if the data is
approved by DOT&E. Depending on circumstances, DOT&E approval will not necessarily be
possible in the TEMP and may require some other documentation. Data approval will be based
on understanding of the realism of the test scenario(s) used and the pedigree (test conditions and
methodologies) of the data. The data in question will typically come from operational exercises,
certification events, and developmental test events conducted in operationally relevant
environments. Data approval should be coordinated with the LTO and DOT&E prior to the start
of testing. When advance coordination is not possible, the LTO will facilitate data re-use (in a
DOT&E assessment or evaluation) through independent documentation of the test data pedigree
(test conditions and methodologies).
(5) In OT&E, typical users or units will operate and maintain the system or item under
conditions simulating combat stress in accordance with 10 U.S.C. 139 (Reference (g) (h)) and
peacetime conditions, when applicable. The lead OTA, in consultation with the user and the
Program Manager, will identify realistic operational scenarios based on the CONOPS (per
paragraph 5d(1) in this enclosure) and mission threads derived from the Joint Mission Essential
Task List or DoD Component-specific Mission Essential Task List. See paragraph 7d of this
enclosure for risk-assessed OT&E of software acquisitions.
(6) In accordance with 10 U.S.C. 2399 (Reference (g) (h)), persons employed by the
contractor for the system being developed may only participate in OT&E of systems on under
OSD OT&E oversight to the extent they are planned to be involved in the operation,
maintenance, and other support of the system when deployed in combat.
(a) A contractor that has participated (or is participating) in the development,
production, or testing of a system for a DoD Component (or for another contractor of the DoD)
may not be involved in any way in establishing criteria for data collection, performance
assessment, or evaluation activities for OT&E.
(b) These limitations do not apply to a contractor that has participated in such
development, production, or testing, solely in test or test support on behalf of the DoD.
(7) IOT&E for all programs will use production or production-representative test articles
that, at a minimum, will incorporate the same parts and software items to be used in LRIP
articles. Production-representative systems meet the following criteria:
(a) The hardware and software must be as defined by the system-level critical design
review, functional configuration audit, and system verification review, including correction of
appropriate major deficiencies identified during prior testing.
Change 2, 02/02/2017 121
ENCLOSURE 5