Testing in a Joint Environment Roadmap - U.S. Army Operational ...

More documents

Recommendations

Info

For Official Use Only Testing in a Joint Environment Roadmap RECOMMENDATIONS I recommend the Deputy Secretary of Defense: 1. Approve the proposed changes and considerations presented in this roadmap and direct its execution, depending on the identification of funding. Direct the implementation planning to be under the leadership of DOT&E in full partnership with the offices of USD(AT&L), USD(P&R), and ASD(NII), the Joint Staff, the Services, JFCOM, and others as required. As the major proponent for acquisition and DT&E, the office of USD(AT&L) will be a key partner in implementation planning. Identification of a long-term sponsor and steps for transition to this sponsor will be addressed during implementation planning. DOT&E will work closely with the designated long-term sponsor in its T&E oversight and advocacy role. 2. Direct the development of a common, fully enhanced network infrastructure capability, and the phased establishment of the responsible field-level program management office. Direct DOT&E to work with the USD(AT&L), the Under Secretary of Defense (Comptroller) (USD(C)), the Director of Program Analysis and Evaluation (D,PA&E), effected Components, and the Joint Staff to identify available FY2005 funds for realignment/reprogramming to initiate this development. 3. Direct DOT&E to pursue FY2006-2011 funding for the continuation of the common, fully enhanced network infrastructure program, and other roadmap-associated costs, during the Program Objective Memorandum (POM) 2006-2011 Program Review. 4. Direct the Department update DoDD 5000.1, DoDI 5000.2, and other directives to institutionalize testing in the joint environment as an enabler for Force Transformation. COLLATERAL REQUIREMENTS Because these actions are critical to execution of this Roadmap, I further recommend: 1. The Deputy Secretary of Defense direct establishment of a common task-based language derived from the UJTL, for concept development, functional analyses, JCIDS capabilities, acquisition, T&E, training and experimentation, and mandate its use in all JCIDS documents. 2. The Chairman update his Chairman Joint Chiefs of Staff Instruction (CJCSI) 3170.01D to ensure all JCIDS CDD and CPD documents define, or reference the source for, the explicit joint mission capability needed in task-based terms derived from the UJTL, and to provide for feedback of T&E results to the Functional Capability Boards (FCB) as appropriate. 3. The USD(AT&L)-led Acquisition M&S Working Group, with other Office of the Secretary of Defense (OSD) offices, the Services, and Defense Agencies, develop an Acquisition M&S Master Plan that addresses the development or update, validation, and maintenance of models x For Official Use Only
For Official Use Only Testing in a Joint Environment Roadmap and simulations to ensure needed virtual and constructive threat and system representations; standard, readily available simulation environments; and identify required funding to support systems engineering and T&E M&S requirements. 4. The ASD(NII), USD(AT&L), and DOT&E establish an Engineering and T&E Community of Interest (COI) to ensure system engineering, and DT&E and OT&E data are made visible, accessible, and understandable across the Services, Agencies, developers, and other parties. xi For Official Use Only
Page 1 and 2: For Official Use Only Testing in a
Page 15: For Official Use Only Testing in a
Page 67 and 68:
For Official Use Only Testing in a
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
For Official Use Only Intentionally
show all

Testing in a Joint Environment Roadmap - U.S. Army Operational ...

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

Delete template?

Save as template?