NETWORK NECESSITY
Spc. Brandon McClure, left, and Sgt. Michael Remaly of the 2nd Infantry Brigade Combat Team, 3rd Infantry Division (2-3 IBCT) perform preventive maintenance checks and services in February on a Satellite Transportable Terminal (STT) at Fort Stewart, Georgia. The STT is a mobile satellite system that operates in con- junction with Joint Network Node - Network, which was fielded after operational test and evaluation but without initial operational test and evaluation or a Beyond LRIP Report. (U.S. Army photo by Spc. Nicholas Holmes, 2-3 IBCT Public Affairs)
of Operational Test and Evaluation. Te Army had allocated funds and bought equipment without completing testing. How- ever, since JNN was not a program of record, DOD officials disagreed over whether JNN would fall under DOD Instruction (DODI) 5000.02 processes. Because of the rapid acquisition practices in the JNN-N program, Congress included provisions, now known as the JNN Law, in the National Defense Authori- zation Act for Fiscal Year 2007 that require operational test and evaluation (OT&E) before fielding. However, this law does not prevent fielding without IOT&E and a Beyond LRIP Report. It requires only that a Beyond LRIP Report be provided “as soon as practicable.”
Te reduced testing would result in increased program risks of uncertain nature, which program managers would have to bal- ance against the risks posed by not delivering the capability in a timely manner. Operational demonstration of effectiveness is currently not credited toward official testing requirements, but it may provide an opportunity to satisfy the law’s official testing requirement while reducing testing efforts.
Recommendation To satisfy the valid need for operational testing without perform- ing full-scale OT&E, acquire equipment on a small scale at first and field equipment on a trial basis, enabling users to provide direct and rapid feedback to developers on equipment perfor- mance and other issues. Tis operational testing approach is also
more consistent with the use of commercial and government off- the-shelf equipment, the subsystems of which are already mature and largely understood, and the importance of user feedback in setting requirements for software and IT-heavy systems.
LL_138: Use other services’ contracts when feasible and when an accelerated schedule does not allow for long con- tract development times.
Background Team Coalition Command, Control, Communications, Com- puters, Intelligence, Surveillance and Reconnaissance (C5ISR) used numerous methods to procure equipment; however, accel- erated deployment timelines made it difficult for the team to execute contract actions in a timely matter. Ideally, an omni- bus contract would satisfy most needs, but development of such a contract requires time that is often unavailable for a quick reaction capability. Team C5ISR, which included personnel from the Program Executive Office for Command, Control and Communications – Tactical (PEO C3T) and the PEO for Intelligence, Electronic Warfare and Sensors, reached out to the Navy for several of its materiel procurements. Te Navy contracting office became a critical partner, executing materiel procurements on several omnibus contracts to meet the deploy- ment timelines.
ASC.ARMY.MIL
39
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
