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

For Official Use Only
Testing in a Joint Environment Roadmap
models, tools and utilities, a data archive capability, and a reuse repository. This required
infrastructure is also the most costly element needed to achieve the vision of testing in a joint
environment.
B.2.3.1 PERSISTENT DATA TRANSPORT CAPABILITY
The Persistent Data Transport Capability provides wide-area connectivity between
geographically-dispersed development laboratories, Department of Defense (DoD) industry
laboratories, test facilities, simulation centers, and ranges as well as any other site linked to the
joint mission infrastructure. The Persistent Data Transport Capability is not a new DoD network.
Instead, the capability will be created by using existing and emerging DoD networks, including
Secret Internet Protocol Router Network (SIPRNET), Defense Information System Network
Asynchronous Transfer Mode Services – Unclassified/Classified (DATMS-U/C), DISN Leading
Edge Services (DISN-LES), Defense Research and Engineering Network (DREN), and
ultimately, the Global Information Grid – Bandwidth Expansion (GIG-BE). Functioning like a
virtual private network (VPN) or collection of VPNs, the Persistent Data Transport Capability
will be an established “community of interest” on these existing DoD networks, allowing the
security accreditation processes to be streamlined. For sites that do not have connectivity on one
of the approved DoD networks, the existing networks will be appropriately extended to satisfy
the requirements for that site to be incorporated into the joint mission infrastructure. The
Persistent Data Transport Capability will build upon and interoperate with the data transport
solution for the JNTC, so that Joint Forces Command (JFCOM) training exercises can be
leveraged to generate the joint mission environment for testing.
B.2.3.2 COMMON MIDDLEWARE
The Common Middleware is the high-performance, real-time, low-latency communication
infrastructure used by applications and tools during execution for all communication between
systems. Providing a unified interface to all software applications, the Common Middleware
will have features for creating, managing, publishing, and deleting distributed objects (with state
information), publish/subscribe messaging, and data streams (e.g., tactical data links, video,
audio, raw telemetry, etc.). Furthermore, it will have services to support managing distributed
objects in the exercise, such as access control and data integrity to maintain consistency across
distributed systems. It will support many different strategies for communication, including typebased
subscription, interest-based subscription, multi-cast, "best effort," and reliable delivery,
each with various qualities of service associated with them. The Common Middleware will
support numerous communication media, such as conventional IP networks, wireless networks,
shared memory, and reflective memory, and will be optimized to work over the Persistent Data
Transport Capability. The Common Middleware will be based upon best commercial practices;
however, it will be designed to easily incorporate new and advancing data distribution
technologies with minimal impact to compliant applications. Since the Common Middleware is
B-5
For Official Use Only
Appendix B