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

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

Appendix D – Implementation Plann<strong>in</strong>g<br />

D.1 Introduction<br />

An implementation plan shall be developed upon approval of the test<strong>in</strong>g <strong>in</strong> a jo<strong>in</strong>t<br />

environment roadmap. The implementation plan will articulate the required organization;<br />

policies, processes, and procedures; and resources at the necessary level of detail to establish the<br />

T&E capabilities described <strong>in</strong> the roadmap. It will also describe the tasks required to achieve<br />

this capability with a detailed implementation schedule. This plan will establish an <strong>in</strong>terim<br />

organizational oversight and work<strong>in</strong>g level structure, and ensure cont<strong>in</strong>uity and transition until<br />

permanent leadership and organization have been established.<br />

D.2 Framework for Implementation<br />

DOT&E is designated the lead for fully develop<strong>in</strong>g the capability for test<strong>in</strong>g <strong>in</strong> a jo<strong>in</strong>t<br />

environment and shall, <strong>in</strong> full partnership with the offices of USD(AT&L), USD(P&R), and<br />

ASD(NII), the Jo<strong>in</strong>t Staff, the Services, JFCOM, and others as required, lead the development of<br />

the implementation plan, coord<strong>in</strong>at<strong>in</strong>g with PPBE pr<strong>in</strong>cipals and others as required. DOT&E<br />

shall establish an implementation plann<strong>in</strong>g team with<strong>in</strong> 60 days of approval of this roadmap, and<br />

the <strong>in</strong>itial implementation plan will be completed, coord<strong>in</strong>ated, and approved by DOT&E on or<br />

about June 30, 2005. Identification of a long-term sponsor and steps for transition to this sponsor<br />

will be addressed dur<strong>in</strong>g implementation plann<strong>in</strong>g.<br />

The implementation plan will describe the “who, what, when, where, how, and why” of the<br />

development and operation of the capability needed to enable test<strong>in</strong>g <strong>in</strong> a jo<strong>in</strong>t environment <strong>in</strong><br />

the necessary level of detail. At a m<strong>in</strong>imum, the implementation plan will address:<br />

Organization, <strong>in</strong>clud<strong>in</strong>g OSD sponsorship, Service/Agency responsibilities, ownership of<br />

technical <strong>in</strong>frastructure, and organizational concepts and <strong>in</strong>terrelationships.<br />

Fund<strong>in</strong>g for development, modernization, and susta<strong>in</strong>ment. Def<strong>in</strong>ition of PPBE<br />

responsibilities for OSD, Services, and Agencies. Develop <strong>in</strong>itial FY2005 budget changes,<br />

issues, BCP, PCPs, etc. Develop PPBE documentation required for FY2006. Establish an<br />

operat<strong>in</strong>g budget beg<strong>in</strong>n<strong>in</strong>g <strong>in</strong> FY2005 for implementation plann<strong>in</strong>g.<br />

Policy, directives, regulations <strong>in</strong>clud<strong>in</strong>g the identification and draft<strong>in</strong>g of specific changes<br />

required <strong>in</strong> DoD publications/issuances concern<strong>in</strong>g acquisition, jo<strong>in</strong>t capabilities, budget and<br />

f<strong>in</strong>ancial management, organization, and tra<strong>in</strong><strong>in</strong>g. Draft a specific directive govern<strong>in</strong>g the<br />

development, operation, fund<strong>in</strong>g, and mandated use of the <strong>in</strong>frastructure to provide the capability<br />

to support test<strong>in</strong>g <strong>in</strong> a jo<strong>in</strong>t environment.<br />

D-1<br />

For Official Use Only<br />

Appendix D

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

Saved successfully!

Ooh no, something went wrong!