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

More documents

Recommendations

Info

For Official Use Only Testing in a Joint Environment Roadmap − Mandates use of the joint mission infrastructure. − Embedded instrumentation whenever feasible to provide inherent T&E capability responsive to accelerated acquisition processes. − Update the Interim Defense Acquisition Guidebook to require identification of joint mission T&E requirements in the TEMP and, in cases where multi-Service participation is identified, provide for coordination with applicable Service OTA commanders as part of the TEMP review and approval process. − Use of properly trained and equipped guard and reserve forces to augment OT&E. 2.4.2.2 REQUIREMENTS/CAPABILITIES GENERATION Changes to the CJCS 3170 series are essential to ensure the CDD and CPD documents contain, or reference the source for, the explicit capability needed. There must be enough specificity in terms of tasks and measurable performance parameters for PMs to know what to build, and for testers to determine what/how to test. A common task-based language (derived from the UJTL) is needed that identifies missions and operational tasks including the specification of measures and conditions. 2.4.2.3 RESOURCES DoD 7000.14-R, the Department of Defense Financial Management Regulations, should be updated to ensure that funding and reimbursement policies for T&E infrastructure and operations facilitate testing in a joint environment. Specific areas that should be addressed include: − Policy assigning responsibility for funding development, operation, and maintenance of the infrastructure, including the cost of network connectivity to T&E sites. − Policy assigning financial responsibility to users of the infrastructure, providing for reimbursement to T&E ranges and facilities for direct costs (as applicable), including the cost of travel, logistical support, and execution of the test. − Policy assigning responsibility for the cost of integrating other necessary systems to create the requisite mission environment, and the costs incurred by participating live systems. 26 For Official Use Only
For Official Use Only Testing in a Joint Environment Roadmap 2.4.2.4 SYNTHESIS OF TRAINING AND TESTING DoDD 1322.18, CJCSI 3500.01B and 3500.02C, regarding joint training, are subject to modification to facilitate, or encourage, the conduct of testing in a joint environment during joint training exercises, and provide for coordination of joint training exercises with testing needs. Modifications to these publications should facilitate coordinated training and testing in a joint environment without compromising either objective. 2.4.3 STRATEGIC PLANNING The DTRMC was created to perform T&E budget certification and strategic planning for the T&E infrastructure through a ten year horizon. It will also manage the CTEIP and TE/ST programs for T&E modernization. The DTRMC strategic plan should be updated to include the new/enhanced T&E capabilities documented herein. 2.4.4 UNRESOLVED POLICY DECISIONS Department acquisition regulations must provide guidance for necessary correction of operational performance or interoperability issues for operationally interdependent systems, when incompatibilities between those systems are demonstrated through testing. Clear direction should identify the organization responsible for adjudicating differences and providing direction to the programs involved. Policy must be established to assign responsibility for funding the changes necessary to correct discrepancies in the legacy systems. Policy and funding for modeling legacy and grandfathered systems to support the joint environment for capabilities-based acquisitions must be addressed by the SPG’s Reformed Acquisition Management task of the Capabilities-Based Planning strategy. 2.5 ORGANIZATION AND RESOURCE CONSIDERATIONS 2.5.1 ORGANIZATION A program management office is needed as a field office to execute the development of the network infrastructure and coordinate its operations. The program office will fully develop, sustain, modernize, provide configuration control, and operate the desired enhanced network infrastructure. Specific details of its leadership, staffing, and location will be determined in a subsequent implementation plan; but broadly speaking the central program management office (Figure 8) will consist of a director and three divisions for program management, engineering, and operations. This office may or may not require a new organization. Several alternatives for location include use of existing DISA billets and assets, collocation with JFCOM's JNTC Joint Management Office (JMO) in Suffolk, VA, or at an existing Service facility such as the Army’s net-centric operation of its ranges established at White Sands Missile Range. 27 For Official Use Only
Page 1 and 2: For Official Use Only Testing in a
Page 43: 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?