search.noResults

search.searching

dataCollection.invalidEmail
note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
FIGURE 1 AIAMD SoS Architecture | FY 2017 JLENS SuR JIIM


Sentinel Sensor C2


JLENS FCR Avenger JTAGS GIG FDL Link 16 EOC EOC THAAD Radar


AIAMD BN EOC


(FCQ Engagement Net) (FCQ Engagement Net) IFC-Net


THAAD Fire Control


Fire Control Qual Engage Net Joint Data Net (Link-16) FAAD Data Link (Legacy) IFPC Fire Control Cooperative Eng Cap


AAMDC – Army Air and Missile Defense Command ADAM – Air Defense and Airspace Management ASoS – AIAMD System-of-Systems EOC – Engagement Operations Center FAAD – Forward Area Air Defense FCQ – Fire Control Quality FCR – Fire Control Radar FDL – FAAD Data Link GIG – Global Information Grid


IBCS – IAMD Battle Command System IFC – Integrated Fire Control IFPC – Indirect Fire Protection Capability JIIM – Joint, Interagency, Intergovernmental, Multinational


JTAGS – Joint Tactical Ground Station P&F – Plug and Fight


PPLI – Precise Participant Location and Identification SuR – Surveillance Radar THAAD – Terminal High Altitude Area Defense


AIAMD Btr y EOC


EOC AIAMD Btry THAAD Launcher IFC-Net Patriot


ASoS Patriot Launcher


ASoS Improved Sentinel


Interface Unit


Radar


ASoS Patriot Radar


Interface Unit


Radar


SYSTEM-OF-SYSTEMS ARCHITECTURE The IFCN fuses sensor data into a single integrated air picture, supporting all potential fire solutions and the mission command to synchronize AMD operations. This is the system-of-systems (SoS) architec- ture that the AIAMD Project Office envisions by FY17. Each sensor and weapon platform will have a P&F interface module defined by the P&F ICD. (SOURCE: AIAMD 2009 Acquisition Strategy)


by a P&F ICD, that will supply distrib- uted battle management functionality to enable network-centric operations on the Integrated Fire Control Network (IFCN). (See Figure 1.)


Te P&F ICD defines the interface between the IAMD Battle Command System (IBCS) B-Kit and the Compo- nent Acquisition Program (CAP) A-Kit. Tis ICD enables the AIAMD PO to con- trol the design of the interfaces between


the IBCS and CAPs that are part of the AIAMD system-of-systems (ASoS) archi- tecture. In addition, the ICD will allow for the incorporation of future systems into the P&F architecture.


Te AIAMD PO has used a number of innovative techniques to manage the P&F ICD, including the creation of an interface control working group with representation from all key stakehold- ers. In addition, establishing a notice of


revision process through the working group, to allow developers to implement in-scope, no-cost changes


has proven to be a valuable way to reduce schedule risk.


BENEFITS OF P&F ICD By using an ICD to control interface design and to enable the exchange of data across the IFCN, the AIAMD PO will ensure that IBCS can incorporate additional air defense artillery (ADA)


ASC.ARMY.MIL 113


immediately,


SCIENCE & TECHNOLOGY


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