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 APPENDIX E: INTEROPERABILITY STANDARDS OVERVIEW For U.S. Forces to counter current and future threats successfully, they must operate worldwide with speed, agility, and flexibility. Key to achieving this required level of responsiveness is providing the quality, shared situation awareness, and understanding necessary to make sound individual and collective judgments. This goal, in turn, requires interoperability, or the ability of systems, units, or forces to provide data, information, materiel, and services to and accept the same from other systems, units, or forces and to use the data, information, materiel, and services so exchanged to enable them to operate effectively together. Interoperability includes both the technical exchange of information and the end-toend operational effectiveness of that exchange of information as required for mission accomplishment. The Global Information Grid (GIG)—a seamless, common-user, information infrastructure—will be the foundation for information superiority by providing the enterprise-wide information services for the DoD command, control, communications, computers, intelligence, surveillance, and reconnaissance (C4ISR) systems. UA systems have the potential for being connected to the edge of the GIG, and for this reason networking capabilities must be implemented in UA systems. Integration of UA into the GIG will require that they adhere to open standards that facilitate their interoperability. Networking capabilities, although they may be considered as operationally integral to a particular UA system, actually are implemented through standards, protocols, and methods external to the data link itself (i.e., at layers three through seven of the open systems interconnect (OSI) networking model). This protocol provides the interworking between transport protocol class 0 (TP0) and TCP transport service necessary for OSI applications to operate over IP-based networks. The intent of the standards Section of the UA Roadmap will be to, discuss the preferred framework and methodology for establishment of interoperability within the UA domain where practical, specify those specific standards, which are the basis of UA interoperability, and which OSD expects to be implemented. Appendix E will also cover current and emerging standardization efforts. Development of the Roadmap has led to identification of roadblocks or impediments to implementation of the current philosophy of UA interoperability. Future actions will be recommended in order to address these impediments, allowing the continued evolution of interoperability among UA and improving the interoperability between UA and the broader warfighter community. Changes Supporting the DoD’s Transformation Objectives To support the DoD’s transformation objectives, several key information technology (IT) processes, programs, and related documents have been recently updated. The joint capabilities integration and development system (JCIDS) (CJCSI 3170.01D and CJCSM 3170.01A) restructured the requirements process used to assess existing and proposed capabilities with respect to future joint operational concepts (JOCs), joint functional concepts (JFCs), and mission area integrated architecture. The JCIDS was developed in coordination with the release of the new DoD 5000 (DoDI 5000.2) Defense acquisition system series to ensure integration of the capabilities development and acquisition processes through the use of integrated architectures, including the GIG integrated architecture. DoDD 4630.5 and DoDI 4630.8 establish the responsibilities of the CIO and other components for information interoperability. These directives reference the use of an integrated set of DoD enterprise architectures. Integrated architectures describe relationships between tasks and activities that generate effects on enemy forces and their supporting operations. The directives specify that integrated architectures must have three views: operational, systems, and technical, as defined in the architecture framework. In accordance with DoDI 5000.2 and DoDI 4630.8,—having a technical view derived from the standards and guidelines contained therein—is required at all program milestone decisions. CJCSI 6212.01C defines the net-ready key performance parameter (KPP) which is based on the use of the GIG integrated architecture. The net-ready APPENDIX E – INTEROPERABILITY STANDARDS Page E-1
UAS ROADMAP 2005 KPP will be used to assess net readiness, information assurance requirements, and both the technical exchange of information and the end-to-end operational effectiveness of that exchange. IT Standards Profile The Department of Defense Information Technology Standards Registry (DISR) replaces the Joint Technical Architecture (JT A). The DISR provides DoD systems with the basis for seamless interoperability. In DISRonline, the Joint Technical Architecture (JTA) document was parsed and populates an Oracle database that serves as the back-end repository for all of the web-based applications. It defines the DISR services and standards applicable to all DoD information technology (IT) systems. The DISR is mandated for the management, development, and acquisition of new or improved IT systems throughout DoD. Standards and guidelines in the DISR are stable, technically mature, and publicly available. The standards selected are essential for providing interoperability and net-centric services across the DoD enterprise and are consistent with the GIG architecture. These standards do not include vendor-unique standards. http://disronline.disa.mil. The command, control, communications, and computer systems directorate of the joint staff (J-6) interoperability and supportability tool supported by JCPAT-E enables component program managers (PM) to develop IT Standards Profiles IAW the DOD IT Standards Registry (DISRonline). The IT standards profile is required as a supporting JCIDS predecessor document for capability development document and CPDs. The standards profile generated by the DISRonline shall be submitted with its related CDDs, and CPDs to the KM/DS during the JCIDS process, and the ISP. The JCIDS predecessor requirement mandates the use of the J6 interoperability and supportability tool access, use of the JCPAT-E registration number for IT and NSS, and development of IT standards profile by component PMs. Supported by the J-6 interoperability and supportability tool, DISR online enables system developers to identify applicable DISR standards and provides users with an easy method to identify the applicable DOD standards needed and to build an IT system Standards Profile through analysis of the IT and NSS capability/system requirements. The J-6 interoperability and supportability tool may be accessed via the SIPRNET at http://jcpat.ncr.disa.smil.mil. Open Systems Interconnection/STANAG 4250 The NATO reference module for open systems interconnection is defined in STANAG 4250. This model is based on the ISO open systems interconnect model, using seven layers to define the elements of the interface protocol. The lowest level is the physical layer, defining the physical and electrical parameters of the actual connection. The highest layer defines the support for the applications that use the data being transported across the interface. The next part of the Standards appendix will describe standards for OSI. NETWORK STANDARDS The transport infrastructure is a foundation for net-centric transformation in DoD and the intelligence community (IC). To realize the vision of a global information grid, ASD/NII has called for a dependable, reliable, and ubiquitous network that eliminates stovepipes and responds to the dynamics of the operational scenario— bringing power to the edge. To construct the transport infrastructure DoD will: � Follow the Internet Model � Create the GIG from smaller component building blocks � Design with interoperability, evolvability, and simplicity in mind The Transport layer (OSI Layer 4) The OSI reference model transport layer (layer 4) defines the rules for information exchange and manages end-to-end delivery of information within and between networks, including making provision for error recovery and flow control. It also repackages long messages when necessary into smaller packets for transmission and, at the receiving end, rebuilds packets into the original message. Depending upon which APPENDIX E – INTEROPERABILITY STANDARDS Page E-2
- 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 136 and 137: UAS ROADMAP 2005 decryption and enc
- 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 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
- Page 186 and 187: UAS ROADMAP 2005 17% 14% 12% 19% 38
- Page 188 and 189: UAS ROADMAP 2005 that for a number
- Page 190 and 191: UAS ROADMAP 2005 RECOMMENDATIONS Ba
- Page 192 and 193: UAS ROADMAP 2005 APPENDIX I: HOMELA
- Page 194 and 195: UAS ROADMAP 2005 CUSTOMS AND BORDER
- Page 196 and 197: UAS ROADMAP 2005 APPENDIX J: UNMANN
- Page 198 and 199: UAS ROADMAP 2005 Joint Robotics Pro
- Page 200 and 201: UAS ROADMAP 2005 Anti-Personnel/Obs
UAS ROADMAP <strong>2005</strong><br />
KPP will be used to assess net readiness, information assurance requirements, and both the technical<br />
exchange <strong>of</strong> information and the end-to-end operational effectiveness <strong>of</strong> that exchange.<br />
IT Standards Pr<strong>of</strong>ile<br />
The Department <strong>of</strong> Defense Information Technology Standards Registry (DISR) replaces the Joint<br />
Technical Architecture (JT A). The DISR provides DoD systems with the basis for seamless<br />
interoperability. In DISRonline, the Joint Technical Architecture (JTA) document was parsed and<br />
populates an Oracle database that serves as the back-end repository for all <strong>of</strong> the web-based applications.<br />
It defines the DISR services and standards applicable to all DoD information technology (IT) systems.<br />
The DISR is mandated for the management, development, and acquisition <strong>of</strong> new or improved IT systems<br />
throughout DoD. Standards and guidelines in the DISR are stable, technically mature, and publicly<br />
available. The standards selected are essential for providing interoperability and net-centric services<br />
across the DoD enterprise and are consistent with the GIG architecture. These standards do not include<br />
vendor-unique standards. http://disronline.disa.mil.<br />
The command, control, communications, and computer systems directorate <strong>of</strong> the joint staff (J-6)<br />
interoperability and supportability tool supported by JCPAT-E enables component program managers<br />
(PM) to develop IT Standards Pr<strong>of</strong>iles IAW the DOD IT Standards Registry (DISRonline). The IT<br />
standards pr<strong>of</strong>ile is required as a supporting JCIDS predecessor document for capability development<br />
document and CPDs. The standards pr<strong>of</strong>ile generated by the DISRonline shall be submitted with its<br />
related CDDs, and CPDs to the KM/DS during the JCIDS process, and the ISP.<br />
The JCIDS predecessor requirement mandates the use <strong>of</strong> the J6 interoperability and supportability tool<br />
access, use <strong>of</strong> the JCPAT-E registration number for IT and NSS, and development <strong>of</strong> IT standards pr<strong>of</strong>ile<br />
by component PMs.<br />
Supported by the J-6 interoperability and supportability tool, DISR online enables system developers to<br />
identify applicable DISR standards and provides users with an easy method to identify the applicable<br />
DOD standards needed and to build an IT system Standards Pr<strong>of</strong>ile through analysis <strong>of</strong> the IT and NSS<br />
capability/system requirements. The J-6 interoperability and supportability tool may be accessed via the<br />
SIPRNET at http://jcpat.ncr.disa.smil.mil.<br />
Open <strong>Systems</strong> Interconnection/STANAG 4250<br />
The NATO reference module for open systems interconnection is defined in STANAG 4250. This model<br />
is based on the ISO open systems interconnect model, using seven layers to define the elements <strong>of</strong> the<br />
interface protocol. The lowest level is the physical layer, defining the physical and electrical parameters<br />
<strong>of</strong> the actual connection. The highest layer defines the support for the applications that use the data being<br />
transported across the interface. The next part <strong>of</strong> the Standards appendix will describe standards for OSI.<br />
NETWORK STANDARDS<br />
The transport infrastructure is a foundation for net-centric transformation in DoD and the intelligence<br />
community (IC). To realize the vision <strong>of</strong> a global information grid, ASD/NII has called for a dependable,<br />
reliable, and ubiquitous network that eliminates stovepipes and responds to the dynamics <strong>of</strong> the<br />
operational scenario— bringing power to the edge. To construct the transport infrastructure DoD will:<br />
� Follow the Internet Model<br />
� Create the GIG from smaller component building blocks<br />
� Design with interoperability, evolvability, and simplicity in mind<br />
The Transport layer (OSI Layer 4)<br />
The OSI reference model transport layer (layer 4) defines the rules for information exchange and manages<br />
end-to-end delivery <strong>of</strong> information within and between networks, including making provision for error<br />
recovery and flow control. It also repackages long messages when necessary into smaller packets for<br />
transmission and, at the receiving end, rebuilds packets into the original message. Depending upon which<br />
APPENDIX E – INTEROPERABILITY STANDARDS<br />
Page E-2