PARTICIPATION OF SYSTEMS IN THE NIE IS DETERMINED THROUGH THE SEVEN-PHASE AGILE PROCESS. ENTRANCE CRITERIA ARE LED BY THE ACQUISITION COMMUNITY AND ARE BASED ON IDENTIFIED CAPABILITY GAPS ALIGNED TO NEAR-TERM REQUIREMENTS
AND OPPORTUNITIES.
ARCHITECTURE VALIDATION AND THREAD GENERATION At the heart of each NIE is a set of system threads generated using the TD archi- tecture. These threads are developed as part of a SoSI-led collaborative process that incorporates the NIE objectives - ties required by the U.S. Army Training and Doctrine Command Capability Managers for each platform and weapon system, and the stated capabilities of each piece of equipment provided by industry.
Thread development for each NIE begins immediately after the previous evaluation. The thread development process is iterative, drawing input from experience
gained in previous NIEs,
generic approved mission threads, and the placement of SUEs and SUTs
in
the TA. In addition, test threads must accomplish DA objectives for the NIE. NIE, serve as an overarching guide for the conduct of each evaluation.
SoSI’s Futures Directorate manages early solution evaluations across all stakehold- ers, conducts competition, and oversees - ment across the PEO community.
dismounts that feature SUEs or SUTs, or vehicles and dismounts that serve as gate- ways from one waveform to another. For example, the platoon leader and platoon sergeant vehicles operating in a lower- and mid-tier construct serve as a gateway Soldier Radio Waveform (SRW) net- work to the company and higher mid-tier Cross-Domain Solution hardware. (See Figure 2.)
- shooting and isolation of issues once the brigade begins equipment installation and integration at Fort Bliss, TX.
Once completed and validated in the CSIL, the vehicle system views are handed over for use during the NIE.
Upon receiving the required hardware and software, the CSIL replicates the key nodes in the TA and begins the risk reduc- tion process. Each proposed thread is run
ASC.ARMY.MIL 15
LAB REDUCES NETWORK AND INTEGRATION RISK The C4ISR [Command, Control, Com- munications, Computers, Intelligence, Surveillance, and Reconnaissance] Sys- tems Integration Laboratory (CSIL) at APG plays an integral role in net- work architecture validation and thread generation.
The lab uses actual hardware to test the interoperability of messages and provides support to reduce overall system risk, Lab Based Risk Reduction (LBRR) process ensures that priority of effort is placed on building out “key nodes” in the evaluation brigade’s architecture rather than the entire brigade structure.
TA by generating system views for each key node in the brigade. These system views display the equipment for each vehicle, connections between equipment, networks to be used in each vehicle, and the location of ATEC instrumentation.
The goal of each system view is to pro- vehicle, enabling the CSIL to test
the
vehicle architecture and make changes if needed before executing the thread in a live environment. Ideally, the CSIL will note the locations of cable connec- tions between devices once LBRR is capture points, and aid ATEC in instru- mentation checkout.
ACQUISITION
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 |
Page 201 |
Page 202 |
Page 203
