GROUND TRUTH
SPEEDING WEAPONS DEVELOPMENT LL_763: Possibly shorten the time it takes to validate requirements by
“piggybacking” onto unfulfilled, cur- rently validated requirements and proposing a technology insertion of your program to fulfill those unmet requirements.
Background Te Command Post of the Future (CPOF) is a virtual command post where participants can see a common picture of the battlefield and scheme of maneuver, and exchange information in real time from dispersed locations.
Te CPOF concept and technology were developed by the Defense Advanced Research Projects Agency, but needed
to be transitioned to a military service. Te Army was preparing for deploy- ment to Iraq at the time, and there was a critical operational need for the collabo- ration capability because of the growing threat from improvised explosive devices. Under the traditional DOD acquisition process, it generally takes two years to validate requirements. Te CPOF tran- sition team identified an approach that would substantially shorten the two-year timeline to meet the Army’s urgent need: piggybacking onto existing requirements.
Te transition team searched existing information technology (IT) require- ments within the U.S. Army Training and Doctrine Command database to find unfulfilled but validated require- ments that the CPOF system could satisfy. Te team found six or seven
suitable requirements, including one for collaboration in the Maneuver Control System (MCS), a network of computer workstations that form the command- and-control system for Army maneuver elements in battalion through corps eche- lons. In January 2006, the team was able to justify adding CPOF as a technology insertion into the MCS program because of the program’s unfulfilled collaboration requirement.
Recommendation Identify candidate requirements and programs by searching existing, unmet requirements and selecting a best fit. It may be better to select requirements associated with programs that may pass Milestone C before your program fully transitions, to simplify completion of paperwork, meetings and other acquisi- tion requirements.
LL_770: Consider fielding a capability without full-scale initial operational test and evaluation (IOT&E) and the Beyond Low-Rate Initial Production (LRIP) Report, instead satisfying the need for operational testing by using the “as soon as practicable” provision in the Joint Network Node law.
Background Te Joint Network Node – Network (JNN-N) is considered a successful rapid acquisition. Less
than a year after the
GETTING THE TOOLS TO THE TROOPS Sgt. Jon Findley, right, of the 311th Sustainment Command (Expeditionary) (311th ESC), tells Pfc. Arturo Gonzalez how to brief the enemy situation using the CPOF computer system during the 311th ESC Command Post Exercise – Functional at Camp Parks, California, in September 2015. When seeking an approach that would substantially shorten the timeline to get the CPOF fielded, the transition team piggybacked onto existing requirements. (Photo by Lt. Col. Gregg Moore, 311th ESC Public Affairs)
submission of an operational needs state- ment in 2004, the program delivered greatly enhanced beyond-line-of-sight communication capabilities to the war- fighter. Furthermore, JNN was fielded to almost the entire Army within five years.
Te rapid acquisition of JNN-N overcame a number of challenges, including the perceived avoidance or postponement of testing requirements by DOD’s Director
38
Army AL&T Magazine October-December 2016
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
