(1) OT&E shall be used to determine
the operational effectiveness and suitability of a system under realistic
operational conditions, including joint combat operations; determine if
thresholds in the approved CPD and critical operational issues have been
satisfied; assess impacts to combat operations; and provide additional
information on the systemís operational capabilities.
(2) The lead OTA shall brief the
DOT&E on concepts for an OT&E 120 days prior to start. They shall
submit the OT&E plan 60 days prior, and shall report major revisions as
(3) Typical users shall operate and
maintain the system or item under conditions simulating combat stress and
(4) The independent OTAs shall use
production or production-representative articles for the dedicated phase of
IOT&E that supports the full-rate production decision (or for ACAT IA or
other acquisition programs, the full-deployment decision).
(5) Hardware and software alterations
that materially change system performance, including system upgrades and
changes to correct deficiencies, shall undergo OT&E.
(6) OTAs shall conduct an independent,
dedicated phase of IOT&E before full-rate production to evaluate
operational effectiveness and suitability, as required by section 2399 of Reference (k).
(7) All weapon, information, and
Command, Control, Communications, Computers, Intelligence, Surveillance, and
Reconnaissance programs that depend on external information sources, or that
provide information to other DoD systems, shall be tested and evaluated for
(8) The DOT&E, following
consultation with the PM, shall determine the quantity of articles procured
for IOT&E for MDAPs; the cognizant OTA, following consultation with the
PM, shall make this decision for non-MDAPs (section 2399 of Reference (k)).
(9) The DOT&E shall assess the
adequacy of IOT&E and LFT&E and evaluate the operational
effectiveness, suitability, and survivability, as applicable, of systems
under DOT&E oversight. DOT&E-oversight programs beyond LRIP shall
require continued DOT&E test plan approval, monitoring, and FOT&E
(a) Complete IOT&E activity;
(b) Refine IOT&E estimates;
(c) Verify correction of
(d) Evaluate significant changes to
system design or employment; and
(e) Evaluate whether or not the
system continues to meet operational needs and retain operational
effectiveness in a substantially new environment, as
(1) The responsible test organization
shall release valid test data and factual information in as near-real-time
as possible to all DoD organizations and contractors with a need to know.
Data may be preliminary and shall be identified as such.
(2) To protect the integrity of the OTA
evaluation process, release of evaluation results may be withheld until the
final report, according to the established policies of each OTA. Nothing in
this policy shall be interpreted as limiting the statutory requirement for
immediate access to all OT&E results by DOT&E.
(3) The primary intent of this policy
is to give developing agencies visibility of factual data produced during
OT&E, while not allowing the developmental agency any influence over the
outcome of those evaluations.
c. Use of
Contractors in Support of OT&E
(1) Per section 2399 of Reference (k), persons employed by the
contractor for the system being developed may only participate in OT&E
of MDAPs to the extent they are planned to be involved in the operation,
maintenance, and other support of the system when deployed in combat.
(2) 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 Department of Defense)
may not be involved in any way in establishing criteria for data collection,
performance assessment, or evaluation activities for OT&E.
(3) The DOT&E may waive the
limitations in 5.c.(1) and 5.c.(2) of this enclosure if the DOT&E
determines, in writing, that sufficient steps have been taken to ensure the
impartiality of the contractor in providing the services. 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
Department of Defense.