For Official Use Only <strong>Test<strong>in</strong>g</strong> <strong>in</strong> a Jo<strong>in</strong>t <strong>Environment</strong> <strong>Roadmap</strong> Intentionally Blank C-8 For Official Use Only Appendix C
For Official Use Only <strong>Test<strong>in</strong>g</strong> <strong>in</strong> a Jo<strong>in</strong>t <strong>Environment</strong> <strong>Roadmap</strong> Appendix D – Implementation Plann<strong>in</strong>g D.1 Introduction An implementation plan shall be developed upon approval of the test<strong>in</strong>g <strong>in</strong> a jo<strong>in</strong>t environment roadmap. The implementation plan will articulate the required organization; policies, processes, and procedures; and resources at the necessary level of detail to establish the T&E capabilities described <strong>in</strong> the roadmap. It will also describe the tasks required to achieve this capability with a detailed implementation schedule. This plan will establish an <strong>in</strong>terim organizational oversight and work<strong>in</strong>g level structure, and ensure cont<strong>in</strong>uity and transition until permanent leadership and organization have been established. D.2 Framework for Implementation 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 environment and shall, <strong>in</strong> full partnership with the offices of USD(AT&L), USD(P&R), and ASD(NII), the Jo<strong>in</strong>t Staff, the Services, JFCOM, and others as required, lead the development of 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 shall establish an implementation plann<strong>in</strong>g team with<strong>in</strong> 60 days of approval of this roadmap, and the <strong>in</strong>itial implementation plan will be completed, coord<strong>in</strong>ated, and approved by DOT&E on or about June 30, 2005. Identification of a long-term sponsor and steps for transition to this sponsor will be addressed dur<strong>in</strong>g implementation plann<strong>in</strong>g. The implementation plan will describe the “who, what, when, where, how, and why” of the 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> the necessary level of detail. At a m<strong>in</strong>imum, the implementation plan will address: Organization, <strong>in</strong>clud<strong>in</strong>g OSD sponsorship, Service/Agency responsibilities, ownership of technical <strong>in</strong>frastructure, and organizational concepts and <strong>in</strong>terrelationships. Fund<strong>in</strong>g for development, modernization, and susta<strong>in</strong>ment. Def<strong>in</strong>ition of PPBE responsibilities for OSD, Services, and Agencies. Develop <strong>in</strong>itial FY2005 budget changes, issues, BCP, PCPs, etc. Develop PPBE documentation required for FY2006. Establish an 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. Policy, directives, regulations <strong>in</strong>clud<strong>in</strong>g the identification and draft<strong>in</strong>g of specific changes required <strong>in</strong> DoD publications/issuances concern<strong>in</strong>g acquisition, jo<strong>in</strong>t capabilities, budget and 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 development, operation, fund<strong>in</strong>g, and mandated use of the <strong>in</strong>frastructure to provide the capability to support test<strong>in</strong>g <strong>in</strong> a jo<strong>in</strong>t environment. D-1 For Official Use Only Appendix D