Unmanned Aircraft Systems Roadmap 2005-2030 - Federation of ...
Unmanned Aircraft Systems Roadmap 2005-2030 - Federation of ... 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
UAS ROADMAP 2005 • Ensure systems are developed to operate in authorized spectrum anywhere in the world. End goal: All RF based systems use spectrum appropriate to their size, class and individual requirements. APPENDIX C - COMMUNICATIONS Page C-24
- Page 86 and 87: UAS ROADMAP 2005 range/endurance ai
- Page 88 and 89: UAS ROADMAP 2005 level below that a
- Page 90 and 91: UAS ROADMAP 2005 � Unmanned syste
- Page 92 and 93: UAS ROADMAP 2005 Appendices
- Page 94 and 95: UAS ROADMAP 2005 APPENDIX A: MISSIO
- Page 96 and 97: UAS ROADMAP 2005 be treated more li
- Page 98 and 99: UAS ROADMAP 2005 3. The integration
- Page 100 and 101: UAS ROADMAP 2005 of expendables. In
- Page 102 and 103: UAS ROADMAP 2005 Range Transporter
- Page 104 and 105: UAS ROADMAP 2005 APPENDIX B: SENSOR
- Page 106 and 107: UAS ROADMAP 2005 film can. Primary
- Page 108 and 109: UAS ROADMAP 2005 mature, and integr
- Page 110 and 111: UAS ROADMAP 2005 should be encourag
- Page 112 and 113: UAS ROADMAP 2005 Contractors have p
- Page 114 and 115: UAS ROADMAP 2005 APPENDIX C: COMMUN
- Page 116 and 117: UAS ROADMAP 2005 FIGURE C-1. GLOBAL
- Page 118 and 119: UAS ROADMAP 2005 GCS, Ops Cell MOB
- Page 120 and 121: UAS ROADMAP 2005 (TSAT), Net-Centri
- Page 122 and 123: UAS ROADMAP 2005 Architecture, GIG,
- Page 124 and 125: UAS ROADMAP 2005 Tier 1 Team Covera
- Page 126 and 127: UAS ROADMAP 2005 FIGURE C-7. BLACK
- Page 128 and 129: UAS ROADMAP 2005 � Aircraft Contr
- Page 130 and 131: UAS ROADMAP 2005 � Any new federa
- Page 132 and 133: UAS ROADMAP 2005 communications, pr
- Page 134 and 135: UAS ROADMAP 2005 CDL requirements e
- Page 138 and 139: UAS ROADMAP 2005 APPENDIX D: TECHNO
- Page 140 and 141: UAS ROADMAP 2005 specific fuel cons
- Page 142 and 143: UAS ROADMAP 2005 technology program
- Page 144 and 145: UAS ROADMAP 2005 the effect of smal
- Page 146 and 147: UAS ROADMAP 2005 Displays that show
- Page 148 and 149: UAS ROADMAP 2005 29 % ($747.3 M) in
- Page 150 and 151: UAS ROADMAP 2005 Laboratory Initiat
- Page 152 and 153: UAS ROADMAP 2005 APPENDIX E: INTERO
- Page 154 and 155: UAS ROADMAP 2005 layer 4 protocol i
- Page 156 and 157: UAS ROADMAP 2005 The family of stan
- Page 158 and 159: UAS ROADMAP 2005 Military Satellite
- Page 160 and 161: UAS ROADMAP 2005 DoD Discovery Meta
- Page 162 and 163: UAS ROADMAP 2005 STANAG 3809 (Digit
- Page 164 and 165: UAS ROADMAP 2005 � SDN.706, X.509
- Page 166 and 167: UAS ROADMAP 2005 Level 1: Indirect
- Page 168 and 169: UAS ROADMAP 2005 APPENDIX F: AIRSPA
- Page 170 and 171: UAS ROADMAP 2005 Class A or B Misha
- Page 172 and 173: UAS ROADMAP 2005 Hawk and Predator,
- Page 174 and 175: UAS ROADMAP 2005 knowledge skills r
- Page 176 and 177: UAS ROADMAP 2005 decision and the a
- Page 178 and 179: UAS ROADMAP 2005 OSD ROADMAP GOALS
- Page 180 and 181: UAS ROADMAP 2005 APPENDIX G: TASK,
- Page 182 and 183: UAS ROADMAP 2005 APPENDIX H: RELIAB
- Page 184 and 185: UAS ROADMAP 2005 throughout its ACT
UAS ROADMAP <strong>2005</strong><br />
• Ensure systems are developed to operate in authorized spectrum anywhere in the world.<br />
End goal: All RF based systems use spectrum appropriate to their size, class and individual requirements.<br />
APPENDIX C - COMMUNICATIONS<br />
Page C-24