Unmanned Aircraft Systems Roadmap 2005-2030 - Federation of ...

UAS ROADMAP 2005
decryption and encryption across the GIG. This would increase latency and add potential points of failure
to the path.
NSA oversees development of HAIPE devices and the HAIPE Interoperability Specification (HAIPIS).
The HAIPE device will be installed between a classified (red) processing node or network and the
unclassified (black) networks of the GIG. Ultimately, HAIPE devices will be integrated into all systems,
pushing the red boundary as close to the classified source as possible. UA sensors will be an important
source of such classified information (i.e. imagery, SIGINT, MASINT). Therefore, UA systems that
create classified information must integrate HAIPE devices as they become available.
NEXT STEPS
Aside from written guidance and existing programs meant to bring UA communications into the netcentric
vision, specific steps can be taken now, to eliminate obstructions to broad based information
sharing and facilitate UA systems integration into the GIG. Some of the actions have been noted earlier
in the text but are repeated here for emphasis and to provide a consolidated list. Failure to implement any
of these will significantly limit a UA system’s ability to share information across the GIG.
� Embrace DoD approved net-centric products. Focus resources on moving toward GIG compliance
rather than justifying waiver requests for legacy hardware and software.
� Develop Net-Ready Key Performance Parameters (NR-KPP).
� Perform GIG Capstone Requirements Document (GIG CRD) crosswalk as specified in the GIG CRD.
The following measures should be initiated as soon as possible to eliminate existing and programmed
obstructions to information flow across the GIG.
� Implement IP transport layer in all UA systems, including legacy data links, to the maximum extent
practical.
• Comply with the IPv6 mandate.
• Implement IP based network interfaces between sensors, control elements, and the GIG.
• Apply the Aircraft Systems Engineering Model to all new UA designs and modifications.
• Insure clear separation between key functional components: aircraft control, payload control,
weapons employment, and situational awareness reporting.
• Separate data, application, and transport layers of the onboard UA communications architecture.
� Develop and register legacy and developing system metadata descriptions using DISA’s DoD
Metadata Registry and Clearinghouse. This exposes data and data characteristics to all
interested/authorized users, both intended and unintended, and greatly simplifies development of
interfaces to disparate sources of data.
� Migrate from legacy radios to JTRS compliant clusters.
• Comply with the SCA, use or develop software-based waveforms for all RF and optical physical
interfaces.
• Coordinate all future radio procurements with the JTRS Joint Program Office.
• Procure JTRS compliant hardware when available.
• Procure SCA compliant software when available.
• Make maximum use of the capabilities provided by JTRS compliant hardware and SCA
compliant software.
� Follow Spectrum Use Policy.
• Transition to IP based wireless connections in the near term.
• Establish and meet firm transition dates from non-DoD approved spectrum to DoD spectrum
recommendations.
APPENDIX C - COMMUNICATIONS
Page C-23