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
UNDERSTANDING ARMY ACQUISITION


and Instrumentation has 459 federal employees, of whom 29 are military, but, overall, has nearly 1,000 employees, including contractors. In addition, it has employees in 66 countries work- ing on foreign military sales. So, while the size of the acquisition workforce is about 40,000, it’s also two or three times that size.


WHY UNDERSTAND? Because acquisition is so complex, it’s fair to ask the question: Why bother? For those who work in acquisition, there are proba- bly three salient reasons. First, because we are spending taxpayer money, we have a duty to do so. Second, by understanding how the parts of acquisition fit together, we are more likely to be able to help all of the parts work together better—the parts of the system itself, but also the parts of the materiel systems. Complex- ity makes acquisition so easy to misunderstand that it’s easy to either make mistakes or fail to take reasonable risks. Finally, and somewhat circularly, understanding acquisition better helps us understand acquisition better.


THE NUTS AND BOLTS On paper, traditional acquisition appears to be linear. Or it can be made to look linear. It begins with a need and ends with the divesting of the thing that used to be needed. However, it is no more linear than a coastline, nor is it as simple as the graphic that follows would make it appear. It’s virtually impossible to render how it works in its entirety in two dimensions. Tat doesn’t mean it can’t be understood. Understanding acquisition isn’t about getting every last thing. And sometimes it means oversimplifying.


Te nuts and bolts of materiel acquisition in the Army are thus: Te field expresses a need for a capability. Tat need gets devel- oped into requirements by the appropriate cross-functional team within the U.S. Army Futures Command (AFC). AFC works to turn the concept into a technology demonstration and perhaps a prototype. Te U.S. Army Training and Doctrine Command (TRADOC) has a hand in all of this because it’s responsible for doctrine and training. Everything that’s acquired has to fit within the Army’s conceptual framework of doctrine, organiza- tion, training, materiel, leadership and education, personnel and facilities (DOTMLPF), and TRADOC owns DOTMLPF. (Tat TRADOC layer isn’t the only level that’s not in plain sight. More on that in a bit.)


Tat concept from AFC then gets handed off to a PEO within the Office of the Assistant Secretary of the Army for Acquisi- tion, Logistics and Technology (ASA(ALT)) for development and execution. Once the capability is built, tested and fielded, it’s handed off to the U.S. Army Materiel Command (AMC), more


or less, and AMC assumes responsibility for sustainment and logistics and, eventually, divestiture and perhaps demilitarization.


However, those exchanges are much more complex than any graphic can show, and differ from program to program. What appear to be dividing lines between the organizations’ responsi- bilities aren’t really dividing lines at all, because the organizations and their functions within the acquisition enterprise are so closely intertwined. (Bromides like “acquisition is a team sport” don’t just appear out of thin air.) And the system is sometimes circu- lar, too, as with older programs that are being upgraded and sustained indefinitely.


CONCLUSION As might be clear from the foregoing, the three major organiza- tions that make up the enterprise are AFC, ASA(ALT) and AMC. Other major commands that are involved in the process are the U.S. Army Test and Evaluation Command, the U.S. Army Corps of Engineers, U.S. Army Forces Command and many others. We didn’t put them in, for the sake of simplicity.


Acquisition has layers of complexity that are also not depicted. Looked at one way, the acquisition career fields that DAWIA mandates offer a window into those layers. Contracting, program management, engineering, business financial management, life cycle logistics, and test and evaluation are just a few of the layers, each with different imperatives and different work.


So big is Army acquisition that it begins to resemble an infinite coast in the coastline paradox. Tat paradox has it that the closer you try to measure a coastline, the longer it gets. A coastline is an obviously finite thing, but just how finite depends on how you look at it. Still, it’s not hard to find the beach.


Tat’s a lot like Army acquisition—the closer you try to look at it, the harder it gets to understand. But everyone knows where the beach is. And, if it were easy to understand, we wouldn’t need Defense Acquisition University.


STEVE STARK is senior editor of Army AL&T magazine. He holds an M.A. in creative writing from Hollins University and a B.A. in English from George Mason University. In addition to more than two decades of editing and writing about the military, science and technology, he is, as Stephen Stark, the best-selling ghostwriter of several consumer health-oriented books and an award-winning novelist.


https://asc.ar my.mil


25


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