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

More documents

Recommendations

Info

For Official Use Only Testing in a Joint Environment Roadmap to analyze its own joint mission requirements and determine when the infrastructure will be mature enough to support the program. 2.6.2 A PHASED APPROACH TO THE ROADMAP Today's approach for testing in a joint environment is limited to ad hoc integration – that necessary for meeting the limited scale near-term joint requirements imposed on grandfathered programs, and by the Net-Ready KPP. Like the initial joint training demonstrations, testing in a joint environment can be conducted, but each event requires a unique ad hoc integration of live systems with virtual and constructive resources that is both costly and temporary. The ultimate destination, or goal, for testing in a joint environment is a persistent, robust, and adaptive interactive capability that is flexible enough to meet the emerging needs of the Department, yet rigid enough to provide a reliable, repeatable, baseline for comparison of future test results. A three-phase path is proposed to achieve a provisional capability, followed by a persistent capability, enroute to fully interactive capability. 2.6.2.1 PROVISIONAL CAPABILITY The provisional capability phase includes the initial steps of executing this roadmap and provides a foundation capable of supporting the pilot programs. A central program management office will be established to develop a detailed implementation plan, with oversight and advocacy continuing from DOT&E, in coordination with USD(AT&L), USD(P&R), JFCOM, the Services, the Joint Staff, and other Agencies and organizations, as appropriate. The implementation plan will be developed in the first year of the roadmap, clarifying the requisite details and processes to achieve the needed capability, as well as determining the final structure and organization of the central program management office. During this process, all the necessary changes to Department policies, regulations, test methods, and test processes will be identified and initiated. From an infrastructure stand-point, the focus will be on testing interactions among live systems (with some augmentation using constructive and virtual simulations). The focus on live system interactions will provide support to the warfighter more quickly, since the capability will give insight into how well current operational systems function together. We go to war with real weapon systems, not simulations of weapon systems. Furthermore, by focusing on live system interactions, it will be easier to align to live JNTC events being conducted in FY2005-FY2008. Through this phase, selection of connectivity sites, upgrades to the common middleware, definition of object models, enhancement to tools and utilities, and techniques in data archiving will focus primarily on supporting the pilot programs. In addition, only the joint mission scenarios for those pilot programs will need to be derived from the joint tasks. Date: FY2008. 32 For Official Use Only
For Official Use Only Testing in a Joint Environment Roadmap 2.6.2.2 PERSISTENT CAPABILITY The persistent capability phase will add a standing capability for scheduling support, so that ongoing events can be browsed and selected for potential opportunities to support test vignettes for programs based upon defined joint mission environments. Determining the impacts that new systems will have on the battlefield, and testing of interactions between a virtual prototype and live systems (with some additional augmentation using constructive simulations) will be the focus of this milestone. During this phase, all joint mission environments should be defined so that the joint mission infrastructure can support all acquisition programs. In addition, newer distributed software technologies, currently under development both within the Department’s science and technology (S&T) community and private industry, will be mature enough to be incorporated and leveraged in the common middleware in annual upgrades. Likewise, improved collaboration software solutions will be included in the standard software suite of support tools. Date: FY2012. 2.6.2.3 INTERACTIVE CAPABILITY The interactive capability phase will provide the standing capability for test engineers to seamlessly select between scheduled events or launch their own live, virtual, or hybrid event (using available virtual prototypes and constructive simulations). Aiding design trade-off decisions and testing of interactions between multiple virtual prototypes (with some additional augmentation using constructive simulations) will be the focus of this phase. The operational interactive capability will enable full T&E of capabilities-based systems against the joint performance attributes defined in the JCIDS capabilities documents (ICD, CDD and CPD), and the ability to do so for evolutionary and spiral developments. Date: FY2015. 33 For Official Use Only
Page 1 and 2: For Official Use Only Testing in a
Page 49: For Official Use Only Testing in a
Page 89 and 90: For Official Use Only Intentionally

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

Create successful ePaper yourself

Delete template?

Save as template?