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 />
their jo<strong>in</strong>t mission environments. Because these actions are critical to the successful execution<br />
of this <strong>Roadmap</strong>, I further recommend:<br />
1. The Deputy Secretary of Defense direct establishment of a common task-based language<br />
derived from the UJTL, for concept development, functional analyses, JCIDS capabilities,<br />
acquisition, T&E, tra<strong>in</strong><strong>in</strong>g and experimentation, and mandate its use <strong>in</strong> all JCIDS documents.<br />
2. The Chairman update his Chairman Jo<strong>in</strong>t Chiefs of Staff Instruction (CJCSI) 3170.01D to<br />
ensure all JCIDS CDD and CPD documents def<strong>in</strong>e, or reference the source for, the explicit jo<strong>in</strong>t<br />
mission capability needed <strong>in</strong> task-based terms derived from the UJTL, and to provide for<br />
feedback of T&E results to the FCBs as appropriate.<br />
3. The USD(AT&L)-led Acquisition M&S Work<strong>in</strong>g Group, with other Office of the Secretary<br />
of Defense (OSD) offices, the Services, and Defense Agencies, develop an Acquisition M&S<br />
Master Plan that addresses the development or update, validation, and ma<strong>in</strong>tenance of models<br />
and simulations to ensure needed virtual and constructive threat and system representations;<br />
standard, readily available simulation environments; and identify required fund<strong>in</strong>g to support<br />
systems eng<strong>in</strong>eer<strong>in</strong>g and T&E M&S requirements.<br />
4. The ASD(NII), USD(AT&L), and DOT&E establish an Eng<strong>in</strong>eer<strong>in</strong>g and T&E Community<br />
of Interest (COI) to ensure system eng<strong>in</strong>eer<strong>in</strong>g, and DT&E and OT&E data are made visible,<br />
accessible, and understandable across the Services, Agencies, developers, and other parties.<br />
36<br />
For Official Use Only