FIGURE 1
Acquisition Corps Field Integrator /
LEGEND
OPCON operational control JIEDDO Joint Improvised Explosive Device Defeat Organization
RDECOM U.S. Army Research, Development and Engineering Command
FOA Forward Operational Assessment
recommend that these areas of support be considered the acquisition lines of operation and that we develop a deployed doctrine focusing on these particular areas.
OPCON contract integration.
Purchase order. Funding visibility. Services delivery. CONTRAX database support.
Coordinated system fielding requirements.
PEO/PM field OPCON responsibilities.
Coordinated DOD AT&L OPCON responsibilities.
System sustainment and drawdown support.
JIEDDO fielding initiatives.
Rapid fielding initiatives. OPCON RDECOM initiatives.
OPCON Defense Advanced Research Projects Agency responsibilities.
As the author learned from his deployment to Iraq, a senior AAC officer with access to the CO- COM commander can integrate, synchronize and communicate acquisition capabilities in support of the commander’s intent and objectives. (SOURCE: MAJ Corey Hemingway)
FOA approval. Coordinate DOD AT&L approval authority to operate in theater of operations.
CONCLUSION Most Army operators understand the role of the AAC as that of materiel develop- ers. However, we are more than that. We are acquisition support coordinators on the modern battlefi eld of commercial ser- vices, wherein civilians in theater provide operations and sustainment support to meet our demand for high-tech equip- ment for the warfi ghter.
We have come to depend on these services to maintain our force protection capabili- ties and information dominance, which are critical on the battlefi eld. We pro- vide logistics support and fi eld emerging warfi ghting technologies in support of urgent requirements. Finally, we provide forward operational assessments to assess new capabilities delivered by the PM.
objectives. T is person would need the capability and authority to have opera- tional control of all forward-deployed acquisition personnel (with specifi c limi- tations), communicate with senior-level general offi cers
and Senior Executive BREAKING THE LANGUAGE BARRIER
Acquisition officers understand contracting language and can communicate the limitations of a contract in order to obtain the right capability for the mission. Here, French- speaking Josue Onguene Ayissi (center left) translates for MAJ Jean Nko’o (center right), head of security for the Cameroon Army Engineer Base, CWO Robert Sandberg (left), security specialist with the 300th Military Intelligence Brigade, and CPT Andrew Denno, anti-terrorism/force protection officer with the 231st Brigade Support Battalion, Feb. 13 in Douala, Cameroon. (U.S. Army photo by SSG Amy Wieser Willson)
Service personnel, and integrate the total deployed capabilities of the AAC.
Figure 1 shows how the proposed acqui- sition support coordination offi cer would provide
support to the COCOM. I
We are an important force multiplier to the COCOM that can infl uence a battle- fi eld just as any other Soldier executing the mission.
For more information, contact the author at
corey.hemingway@us.army.mil.
The views expressed in the article are those of the author and do not reflect the official pol- icy or position of DA or the U.S. government.
MAJ COREY HEMINGWAY is a DA systems coordinator for the ASA(ALT). He holds a B.S. in criminal justice from Albany State University and an M.S. in project management from the Florida Institute of Technology. A member of the AAC, Hemingway is Level III certified in program management and Level I certified in information technology.
ASC.ARMY.MIL 137
CONTRACTING PROGRAM
MANAGEMENT
SCIENCE & TECHNOLOGY TESTING
COMMENTARY
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
