“War, like most other things, is a science to be acquired and perfected by diligence, by perseverance, by time, and by practice.”
—Alexander Hamilton, The Federalist Papers O Afghanistan’s Kandahar province
n March 19, 2011, a man contracted to provide secu- rity for Forward Operating Base (FOB) Frontenac in shot
and killed Army SPC Rudy A. Acosta and CPL Donald R. Mickler Jr., wound- ing four others.
has attacked U.S. forces from within. A contractor allegedly used illegal immi- buildings at an Army post in the United in July 2010.
It is time to review how we address the issue of security in the contracting pro- cess. How can we “perfect by diligence… and by practice” procedures to ensure that we prevent a terrorist attack?
The Army’s antiterrorism (AT) vision is to “successfully prevent terrorist attacks.” Initiated six years ago in the Army Anti- terrorism Strategic Plan, this vision drives gaps that demand improved protective measures.
Clearly, rigorous searching often reveals surprising results. As the incidents men- tioned above indicate, closer coordination between contracting elements and the requiring activity’s functions of AT and operations security (OPSEC) might have improved the odds of prevention. Subsequent assessments have supported
that Army organizations did not fully integrate AT and OPSEC into the con- tracting process.
AVENUES OF ATTACK The process presents an interesting challenge. Through contracts, Army - or product can make the organization vulnerable to terrorist attack.
There are at least two scenarios in which terrorists could use contracting as an avenue to attack Army missions. One is a contract, as occurred at FOB Fronte- nac. The other is an attack on contractors themselves, thus affecting Army missions.
What measures can mitigate these pos- sibilities? To be sure, greater protection from terrorist attack lies in a coordinated effort involving many functions, but pri- marily between the requiring activity and the contracting activity. It is the requir- ing activity’s responsibility to ensure that necessary AT and OPSEC measures are considered in developing a contract and the resulting requirements package. It is the contracting activity’s responsibility to integrate the selected AT and OPSEC measures into the solicitation and result- ing contract. Figure 1 on Page 68 sums up the process.
Necessary coordination starts at the very beginning of
the contracting process.
Initial planning determines the needed support for the requiring activity. It
also initiates routine staff planning to execute a risk assessment, review cur- rent and future threats, evaluate critical elements of the organization, determine organizational
vulnerabilities, and
review local and Army policies requiring security measures.
Potential Installation Access Control Vulnerability with Non-CAC Eligible Contractors (DTG: 212251 Mar 11), pro- vide direction and guidance for vetting personnel in certain circumstances. For some cases in which AT and OPSEC are not at issue, this initial review ends the planning allows the requiring activity what, if any, security measures might be a component of the prospective perfor- mance work statement (PWS).
DEVELOPING THE REQUIREMENT The next step is to develop the require- ment. Performing a risk analysis, the - cer review the draft PWS to determine whether security matters have been con- sidered and addressed adequately. This entries that should become a part of the requirements package. In some cases, the - ing security-related contract language or clauses for applicability. If these do not effectively provide for the requisite secu- rity, they can devise new language that
ASC.ARMY.MIL
67
CONTRACTING
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
