GETTING THE WORD OUT
Contract personnel and those hired as host nation workers benefit from iWatch training, including an easy-to-carry card such as this one with text on front (left) and back, and a phone number to call to report suspicious activity.
included in the requirements package, the - ments package cover sheet, indicating the before contract solicitation. During and after the solicitation and award of the may ask for assistance from the requiring activity’s ATO in evaluating source selec- tion criteria as a technical advisor.
The ATO may request assistance from using terrorist
screening databases to
conduct background checks on con- tract employees. These databases could include the National Crime Information Center, local law enforcement agency background checks, the National Law Enforcement Telecommunications Sys- tem, and the Defense Reporting System.
Incident-Based
In addition, during contract execution, the ATO may conduct a post-award risk evaluation based on the contract award and changes to threat levels. Moreover, - cer’s representative (COR) on execution of the quality assurance surveillance plan the contract. Any changes in the threat or friendly situation could trigger the
Anticipating potential changes during the planning sequences, before complet- ing the requirements package, can avert problems when those events occur. The ATO must be attuned to the possibility and include appropriate review in con- nection with any changes to the Force Protection Conditions. If necessary, the ATO should contact the KO or COR for any changes to AT-related procedures that could affect the supporting contractor.
MANAGING THE WORKLOAD The requirement to integrate AT and OPSEC into the contract support pro- cess is not new. It has been promulgated in Army AT policy since 2006. If the requirement seems to be a tremendous addition in workload, perhaps a closer examination of the problem will reveal possible solutions.
Many Army organizations, as requiring activities, execute hundreds or even thou- sands of contracts in a given year. With volume this high, it might seem excessive every requirements package. Most often, however, organizations can develop ways to reduce the load.
Many contracts are similar enough to embed necessary procedures in a unique
command policy covering all contracts with the same security measures. In other cases, the contracts are spread through the chain of command, and multiple ATOs can evaluate the risk at the appropriate level. Distributing the load can reduce time spent reviewing all requirements packages. In still other situations, when demand is truly high with many differ- ing requirements, commands can train
In January, the Army issued the
ALARACT 015-2012 message, Use of an Antiterrorism/Operations Security (AT/ OPSEC) in Contracting Cover Sheet for Integrating AT/OPSEC into the Contract Support Process, stating that “a signed AT cover sheet is required to be included in all contract support requirements pack- ages except for supply contracts under - ment purchase card purchases.”
In February, the Deputy Assistant Sec- retary of
the Army for Procurement
released a Policy Alert that indicated that the cover sheet would become mandatory on May 1. The date was subsequently - icy Alert (PARC Policy Alert #12-22,
ASC.ARMY.MIL 69
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