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.4 CHANGES TO POLICY AND REGULATIONS<br />

2.4.1 NEW DEPARTMENT POLICY<br />

The FY2006-2011 SPG conta<strong>in</strong>s a clear statement of Department policy:<br />

"Develop<strong>in</strong>g and field<strong>in</strong>g jo<strong>in</strong>t force capabilities requires adequate, realistic T&E <strong>in</strong> a<br />

jo<strong>in</strong>t operational context. To do this, the Department will provide new test<strong>in</strong>g<br />

capabilities and <strong>in</strong>stitutionalize the evaluation of jo<strong>in</strong>t system effectiveness as part of new<br />

capabilities-based processes."<br />

A fundamental goal of this roadmap is to provide recommendations as to where and how to<br />

appropriately <strong>in</strong>corporate this Department policy appropriately <strong>in</strong> exist<strong>in</strong>g directives,<br />

<strong>in</strong>structions, and regulations to ensure that it is <strong>in</strong>stitutionalized.<br />

2.4.2 REVISIONS TO DIRECTIVES, INSTRUCTIONS, REGULATIONS<br />

Current Department policies do not preclude test<strong>in</strong>g <strong>in</strong> a jo<strong>in</strong>t environment. Most exist<strong>in</strong>g<br />

regulations neither encourage nor require such test<strong>in</strong>g. Noteworthy exceptions are the<br />

<strong>in</strong>teroperability test<strong>in</strong>g and certification requirements <strong>in</strong> DoDD 4630.5, DoDI 4630.8, and CJCSI<br />

6212.01C that address operational <strong>in</strong>teroperability requirements identified by JCIDS. Thirty<br />

departmental documents conta<strong>in</strong><strong>in</strong>g policy, procedures, and guidance were reviewed for change<br />

as summarized <strong>in</strong> Appendix C. Recommendations or suggested changes are identified there, but<br />

the details will be developed dur<strong>in</strong>g implementation plann<strong>in</strong>g and submitted to the cognizant<br />

offices for review and <strong>in</strong>corporation. There are four key focus areas where policy changes are<br />

necessary.<br />

2.4.2.1 DEFENSE ACQUISITION SYSTEM<br />

Fundamental acquisition system policy should declare that test<strong>in</strong>g <strong>in</strong> a jo<strong>in</strong>t environment is<br />

required <strong>in</strong> a cont<strong>in</strong>uum of evaluation throughout a system's or system-of-system’s lifecycle.<br />

Policies <strong>in</strong> DoDD 5000.1 and procedures conta<strong>in</strong>ed <strong>in</strong> DoDI 5000.2, and other applicable<br />

documents, should be enhanced to <strong>in</strong>clude statements that establish the guidance for PMs and<br />

<strong>Operational</strong> Test Agencies (OTA) to conduct test<strong>in</strong>g <strong>in</strong> a jo<strong>in</strong>t environment as an <strong>in</strong>tegral part of<br />

the acquisition process based on requirements/capabilities identified and approved through the<br />

JCIDS process. Other areas <strong>in</strong>clude:<br />

− Creation of the networked jo<strong>in</strong>t mission <strong>in</strong>frastructure and M&S resources, and<br />

<strong>in</strong>tegration of developmental systems with the <strong>in</strong>frastructure.<br />

− Development, upgrade, and ma<strong>in</strong>tenance of system-level constructive models and virtual<br />

simulations throughout the lifecycle of each system.<br />

25<br />

For Official Use Only

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

Saved successfully!

Ooh no, something went wrong!