Testing in a Joint Environment Roadmap - U.S. Army Operational ...
Testing in a Joint Environment Roadmap - U.S. Army Operational ...
Testing in a Joint Environment Roadmap - U.S. Army Operational ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
For Official Use Only<br />
<strong>Test<strong>in</strong>g</strong> <strong>in</strong> a Jo<strong>in</strong>t <strong>Environment</strong> <strong>Roadmap</strong><br />
2.7 IMPLEMENTATION PLANNING<br />
To ensure smooth execution and implementation of the provisions of this roadmap after its<br />
approval by the Deputy Secretary of Defense, an implementation plan shall be developed. The<br />
plan developed after roadmap approval will establish an <strong>in</strong>terim organizational oversight and<br />
work<strong>in</strong>g level structure, and ensure cont<strong>in</strong>uity and transition until permanent leadership and<br />
organization has been established. The plan will address the concept, management, resourc<strong>in</strong>g,<br />
development, coord<strong>in</strong>ation, approval, and implementation of the T&E capability for test<strong>in</strong>g <strong>in</strong> a<br />
jo<strong>in</strong>t environment <strong>in</strong> the level of detail needed. Appendix D presents a framework for<br />
implementation plann<strong>in</strong>g and the considerations to be addressed.<br />
2.8 RECOMMENDATIONS AND COLLATERAL REQUIREMENTS<br />
To be fully prepared for developmental and operational test<strong>in</strong>g <strong>in</strong> the jo<strong>in</strong>t environment <strong>in</strong><br />
time to support the Department’s Force Transformation <strong>in</strong>itiatives, I recommend the Deputy<br />
Secretary of Defense:<br />
1. Approve the proposed changes and considerations presented <strong>in</strong> this roadmap and direct its<br />
execution, depend<strong>in</strong>g on the identification of fund<strong>in</strong>g. Direct the implementation plann<strong>in</strong>g to be<br />
under the leadership of DOT&E <strong>in</strong> full partnership with the offices of USD(AT&L), USD(P&R),<br />
and ASD(NII), the Jo<strong>in</strong>t Staff, the Services, JFCOM, and others as required. As the major<br />
proponent for acquisition and DT&E, the office of USD(AT&L) will be a key partner <strong>in</strong><br />
implementation plann<strong>in</strong>g. Identification of a long-term sponsor and steps for transition to this<br />
sponsor will be addressed dur<strong>in</strong>g implementation plann<strong>in</strong>g. DOT&E will work closely with the<br />
designated long-term sponsor <strong>in</strong> its T&E oversight and advocacy role.<br />
2. Direct the development of a common, fully enhanced network <strong>in</strong>frastructure capability, and<br />
the phased establishment of the responsible field-level program management office. Direct<br />
DOT&E to work with the USD(AT&L), the Under Secretary of Defense (Comptroller)<br />
(USD(C)), the Director of Program Analysis and Evaluation (D,PA&E), effected Components,<br />
and the Jo<strong>in</strong>t Staff to identify available FY2005 funds for realignment/reprogramm<strong>in</strong>g to <strong>in</strong>itiate<br />
this development.<br />
3. Direct DOT&E to pursue FY2006-2011 fund<strong>in</strong>g for the cont<strong>in</strong>uation of the common, fully<br />
enhanced network <strong>in</strong>frastructure program, and other roadmap-associated costs, dur<strong>in</strong>g the<br />
Program Objective Memorandum (POM) 2006-2011 Program Review.<br />
4. Direct the Department update DoDD 5000.1, DoDI 5000.2, and other directives to<br />
<strong>in</strong>stitutionalize test<strong>in</strong>g <strong>in</strong> the jo<strong>in</strong>t environment as an enabler for Force Transformation.<br />
There are several important enabl<strong>in</strong>g actions that must be accomplished concurrently to<br />
ensure the Department establishes a robust capability to test systems and system-of-systems <strong>in</strong><br />
35<br />
For Official Use Only