THE BIG PICTURE
FIGURE 2 P&F Interface Defined by ICD
Adapted Sensor Sensor
IBCS A-Kit B-Kit IFCN Weapon Adapted Weapon
PLUG-AND-FIGHT INTERFACE A common configuration for interfacing with IBCS will be available at all echelons, including battalion, battery and platoon. The P&F ICD documents the sensor-weapon data interactions. (SOURCE: AIAMD PO)
A-Kit B-Kit EOC
(TIMs) with a variety of stakeholders to obtain input from subject-matter experts to the development and improvement of the ICD. Te TIMs provide opportuni- ties to improve understanding of the ICD and open the lines of communication among stakeholders. Participants include the Army’s Indirect Fire Protection Capa- bility (IFPC) Product Office as well as the managers of other land-based sensors, such as the Air Force’s Tree-Dimensional Expeditionary Long-Range Radar and the Marine Corps’ Ground/Air Task Oriented Radar, and programs under development by the Missile Defense Agency, such as the Terminal High Altitude Area Defense system (THAAD) and the Command and Control, Battle Management and Communications system.
components. Te government-controlled P&F B-Kit to A-Kit ICD is a fundamental element of the AIAMD program, defining the functional interface that allows con- nectivity and interoperability of disparate sensors and weapons on the IFCN under common command and control.
Te ICD defines who can get on the IFCN via
the A-Kit AIAMD program developed the
and B-Kit. Te first
version of the P&F ICD in July 2010 to support the A-Kit Preliminary Design Review. It is a system engineering docu- ment that the AIAMD PO’s System Integration Directorate maintains, using a well-defined configuration manage- ment process. Te ICD will continue to mature with additional releases during the AIAMD engineering and manufac- turing development phase.
Te IFCN, facilitated by the P&F Kit, fuses sensor data into a single integrated
114 Army AL&T Magazine April–June 2014
air picture. It provides data to support all potential fire solutions and the mis- sion command to synchronize AMD operations. Tis network functions over any physical medium that can carry Internet Protocol version 6 data, but track-load and fire-control quality require a high-bandwidth, low-latency system. In response, the AIAMD PO is using the Warfighter Information Network – Tactical (WIN-T) Increment 2 to build an organic communications capability for AMD units to provide line-of-sight transmission of IFCN data.
It is critical that all elements participat- ing on the IFCN be able to exchange data in a timely manner with defined message structures. Using an ICD, AIAMD’s P&F approach will enable the current critical elements as well as future Army technologies to define the interface for joint IAMD. Currently, the AIAMD PO is hosting technical interchange meetings
AIAMD plans to field IBCS to the air defense airspace management cells, ADA brigade headquarters, and Army air and missile defense command headquarters. A common configuration will be available at all echelons, including battalion, battery and platoon. IAMD specifications define the interface technologies that enable this broad integration effort, including the data distribution system and interface design language, and the P&F ICD documents the sensor-weapon data interactions. (See Figure 2.)
MANAGING THE ICD To manage the AIAMD ICD and the ASoS integration effort, the AIAMD PO created the Interface Control Working Group (ICWG) in November 2011 for effective systems engineering manage- ment of the AIAMD architecture. Te P&F Interface Control Working Group (ICWG-P) is responsible for the P&F interface, allowing the organizations involved to remain synchronized and to have correct, complete and accurate documentation as well as knowledge of
AIAMD System of Systems
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68 |
Page 69 |
Page 70 |
Page 71 |
Page 72 |
Page 73 |
Page 74 |
Page 75 |
Page 76 |
Page 77 |
Page 78 |
Page 79 |
Page 80 |
Page 81 |
Page 82 |
Page 83 |
Page 84 |
Page 85 |
Page 86 |
Page 87 |
Page 88 |
Page 89 |
Page 90 |
Page 91 |
Page 92 |
Page 93 |
Page 94 |
Page 95 |
Page 96 |
Page 97 |
Page 98 |
Page 99 |
Page 100 |
Page 101 |
Page 102 |
Page 103 |
Page 104 |
Page 105 |
Page 106 |
Page 107 |
Page 108 |
Page 109 |
Page 110 |
Page 111 |
Page 112 |
Page 113 |
Page 114 |
Page 115 |
Page 116 |
Page 117 |
Page 118 |
Page 119 |
Page 120 |
Page 121 |
Page 122 |
Page 123 |
Page 124 |
Page 125 |
Page 126 |
Page 127 |
Page 128 |
Page 129 |
Page 130 |
Page 131 |
Page 132 |
Page 133 |
Page 134 |
Page 135 |
Page 136 |
Page 137 |
Page 138 |
Page 139 |
Page 140 |
Page 141 |
Page 142 |
Page 143 |
Page 144 |
Page 145 |
Page 146 |
Page 147 |
Page 148 |
Page 149 |
Page 150 |
Page 151 |
Page 152 |
Page 153 |
Page 154 |
Page 155 |
Page 156 |
Page 157 |
Page 158 |
Page 159 |
Page 160 |
Page 161 |
Page 162 |
Page 163 |
Page 164 |
Page 165 |
Page 166 |
Page 167 |
Page 168 |
Page 169 |
Page 170 |
Page 171 |
Page 172 |
Page 173 |
Page 174 |
Page 175 |
Page 176 |
Page 177 |
Page 178 |
Page 179 |
Page 180 |
Page 181 |
Page 182 |
Page 183 |
Page 184 |
Page 185 |
Page 186 |
Page 187 |
Page 188 |
Page 189 |
Page 190 |
Page 191 |
Page 192 |
Page 193 |
Page 194 |
Page 195 |
Page 196 |
Page 197 |
Page 198 |
Page 199 |
Page 200
