UNDERSTANDING ARMY ACQUISITION
“Fundamentally the engineering process does not change,” warned Hunter of CSIS.
“Programs that are new-build, complex platforms still have significant engineer- ing challenges.”
Sustainability is another definite concern, Dillard said. “Sustainment is certainly the area that presents risk when doing things on the quick.” It is well-established that long-term sustainment can be the most costly piece of a system life cycle. “Logis- tic support must be designed in, and that takes a deliberate, iterative effort for suitability and supportability analy- sis alongside the development, early on and throughout ‘the invention process,’ ” he said.
“Going from prototypes to production- ready systems is a leap that I think is makeable, but the proof ’s in the pudding,” said Hunter. “… Before we get too excited
about our success, we have to deliver some systems to the warfighter.”
JCIDS PROCESS ON WAY OUT? It is by now a given that people really want to move away from the 5000 defense acquisition machinery and start moving much more quickly. “Tey want to get out from underneath the JCIDS [Joint Capabilities Integration and Develop- ment System] process,” Etherton said. Te attractiveness of OTAs and other Section 804 authorities, which to some extent were designed deliberately “to get you out from underneath the JCIDS process, to me, that calls the whole JCIDS process into question,” he said.
“Now we have enough information and enough experience [to conclude] that maybe we don’t need a JCIDS process at all, or we need something that is a differ- ent approach for what JCIDS tries to
Federal
Acquisition Regulation 2,304 pages
Defense Federal Acquisition Regulation Supplement (3 volumes) 1,492 pages
Other-transaction authority guidebook 53 pages
REGULATIONS SHRINKING
OTAs require much less from businesses and from the government, making them a more flexible instrument than contracts based on the FAR. (Image courtesy of the authors)
to free us up from lots of unnecessary statutes and regulations, but are no substitute for our doing what is inherently governmental: defining what we expect as deliverables from rigorous requirements analysis and systems
engineering.”
https://asc.ar my.mil 15
“OTAs serve
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
