27.01.2015 Views

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 ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

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.3.2.3 CORE INFRASTRUCTURE CAPABILITY<br />

The objective core <strong>in</strong>frastructure will provide the capability essential to generate the jo<strong>in</strong>t<br />

mission environment that is needed for T&E <strong>in</strong> all jo<strong>in</strong>t mission areas. The core <strong>in</strong>frastructure<br />

capabilities <strong>in</strong>clude a persistent data transport capability, common middleware, basic object<br />

models, tools and utilities, a data archive capability, and a reuse repository. A major<br />

enhancement to the current JDEP, address<strong>in</strong>g these requirements, has been fully studied<br />

separately by USD(AT&L) and the Defense Information Systems Agency (DISA). All the<br />

elements of a program plan that support the roadmap's recommendations are available separately.<br />

Technical details are provided <strong>in</strong> Appendix B. This required core <strong>in</strong>frastructure is the most<br />

resource-<strong>in</strong>tensive element needed to achieve the vision of test<strong>in</strong>g <strong>in</strong> a jo<strong>in</strong>t environment.<br />

2.3.2.4 SYSTEM/THREAT/ENVIRONMENT REPRESENTATIONS<br />

Current validated and accredited models and simulations are crucial to be able to conduct<br />

realistic and adequate T&E. The USD(AT&L), with other Office of the Secretary of Defense<br />

(OSD) offices, the Services, and Defense Agencies, must cont<strong>in</strong>ue work associated with the<br />

proposed recommendations under the SPG task [E17e] for Reformed Acquisition Management.<br />

Those proposals called for better leverag<strong>in</strong>g of M&S for capability-based acquisition, and<br />

enabl<strong>in</strong>g <strong>in</strong>creased test capability for systems and systems-of-systems <strong>in</strong> a jo<strong>in</strong>t environment<br />

with greater use of M&S. The USD(AT&L)-led Acquisition M&S Work<strong>in</strong>g Group shall develop<br />

an Acquisition Model<strong>in</strong>g and Simulation Master Plan that will address the development or<br />

update, validation, and ma<strong>in</strong>tenance of models and simulations to ensure needed virtual and<br />

constructive threat and system representations, as well as standard, readily available simulation<br />

environments. The Group will make recommendations to the USD(AT&L) regard<strong>in</strong>g fund<strong>in</strong>g to<br />

support systems eng<strong>in</strong>eer<strong>in</strong>g and T&E M&S requirements. Further, the Department must assure<br />

appropriate Department or commercial standards are agreed upon to facilitate needed shar<strong>in</strong>g,<br />

reuse, and <strong>in</strong>teroperability of M&S <strong>in</strong> systems eng<strong>in</strong>eer<strong>in</strong>g and test activity. The USD(AT&L)<br />

shall add DOT&E to the membership of the DoD Executive Council for Model<strong>in</strong>g and<br />

Simulation (EXCIMS) and task that body to oversee the coord<strong>in</strong>ation and implementation of all<br />

M&S actions related to test<strong>in</strong>g <strong>in</strong> a jo<strong>in</strong>t environment.<br />

Program managers must be able to "plug" the warfight<strong>in</strong>g capabilities under test <strong>in</strong>to a<br />

representative jo<strong>in</strong>t mission <strong>in</strong>frastructure that provides sufficient <strong>in</strong>teraction with the cluster of<br />

needed systems and threat forces <strong>in</strong> appropriate scenarios to meet their test objectives. Although<br />

there are many ways to categorize the various systems <strong>in</strong>teract<strong>in</strong>g <strong>in</strong> the jo<strong>in</strong>t mission<br />

<strong>in</strong>frastructure, this roadmap organizes them <strong>in</strong>to three major categories: system representations;<br />

threat representations; and environment representations. Specifics are discussed <strong>in</strong> Appendix B.<br />

While new systems developed to JCIDS requirements may be compelled to design their<br />

models and <strong>in</strong>terfaces to be compatible with the jo<strong>in</strong>t mission environment, legacy systems and<br />

those already <strong>in</strong> development haven’t been subject to the same requirement. These systems are<br />

21<br />

For Official Use Only

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!