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 ...
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 />
2.0 TESTING IN A JOINT ENVIRONMENT ROADMAP<br />
2.1 JOINT CAPABILITIES IDENTIFICATION AND ACQUISITION<br />
The long-term objective of Force Transformation is to match current capabilities more<br />
closely to the warfight<strong>in</strong>g needs of the Combatant Commanders (CoComs) and transform the<br />
requirements def<strong>in</strong>ition and acquisition bus<strong>in</strong>ess practices to capabilities-based processes that<br />
ensure future capabilities are designed, developed, tested, and fielded to fully support jo<strong>in</strong>t<br />
operat<strong>in</strong>g, functional, and <strong>in</strong>tegrat<strong>in</strong>g concepts. The CoComs are the ultimate customers of<br />
capabilities-based acquisition and test<strong>in</strong>g. Force Transformation requires both modernization of<br />
exist<strong>in</strong>g legacy military capabilities to more closely meet jo<strong>in</strong>t needs, and fill<strong>in</strong>g capability gaps<br />
us<strong>in</strong>g capabilities-based acquisition that is fully focused on provid<strong>in</strong>g the needed jo<strong>in</strong>t mission<br />
capability. As noted <strong>in</strong> the Jo<strong>in</strong>t Operations Concepts document: “The Jo<strong>in</strong>t Force must move<br />
beyond deconfliction to fully <strong>in</strong>tegrated elements with all functions and capabilities focused<br />
toward a unified purpose. This means that the capabilities provided by the Services, combatant<br />
commands and combat support agencies are ‘born jo<strong>in</strong>t’ and fully <strong>in</strong>tegrated. Thus the Jo<strong>in</strong>t<br />
Force Commander will have a set of <strong>in</strong>herently <strong>in</strong>teroperable and synergistic jo<strong>in</strong>t capabilities to<br />
employ. Legacy equipment and systems will be ‘made jo<strong>in</strong>t’ to the extent possible until such<br />
time as replacement by ‘born jo<strong>in</strong>t’ equipment is feasible.”<br />
Full implementation of the Jo<strong>in</strong>t Capabilities Integration and Development System (JCIDS)<br />
def<strong>in</strong>ed <strong>in</strong> CJCS Instruction (CJCSI) 3170.01D as the means to develop and communicate<br />
desired system capabilities to the acquisition and T&E communities will be the most significant<br />
change that will affect how T&E will be conducted <strong>in</strong> the future. For illustration purposes <strong>in</strong> this<br />
roadmap, Figure 1 shows JCIDS decisions that def<strong>in</strong>e a materiel solution as the <strong>in</strong>itiation of the<br />
capabilities-based acquisition process. The procedures established <strong>in</strong> the JCIDS support the<br />
Chairman of the Jo<strong>in</strong>t Chiefs of Staff (CJCS) and the Jo<strong>in</strong>t Requirements Oversight Council<br />
(JROC) <strong>in</strong> identify<strong>in</strong>g, assess<strong>in</strong>g, and prioritiz<strong>in</strong>g jo<strong>in</strong>t military capability needs. JCIDS is the<br />
source of the Initial Capabilities Document (ICD), CDD, and CPD, replac<strong>in</strong>g the older Mission<br />
Needs Statement (MNS) and <strong>Operational</strong> Requirements Document (ORD). Additionally, the<br />
JCIDS is a key element <strong>in</strong> the Chairman’s efforts to realize the <strong>in</strong>itiatives directed <strong>in</strong> the<br />
Secretary’s Transformation Plann<strong>in</strong>g Guidance (TPG). JCIDS will move materiel developers<br />
and testers away from the Service-centric system requirements of the past towards the necessary<br />
jo<strong>in</strong>t-centric capability development for future systems. JCIDS will drive both the requirement<br />
for jo<strong>in</strong>tness <strong>in</strong> acquisition systems, and the test and acquisition community’s need for a<br />
match<strong>in</strong>g systems eng<strong>in</strong>eer<strong>in</strong>g and test capability that will support JCIDS-based system and<br />
system-of-systems developments and T&E.<br />
5<br />
For Official Use Only