Table of Contents
Contracting officers are required to sign all contract actions (either via wet signature, signature as produced by CON-IT, or digital signature produced with a DoD Public Key Infrastructure certificate using a Common Access Card), ensure contractor signatures are obtained, and maintain signed contractual documents within the official contract file.
See AFMC PGI 5304.100-90.
See SMC PGI 5304.101.
See SMC PGI 5304.102.
See AFMC PGI 5304.190.
See SMC PGI 5304.201.
See SMC PGI 5304.270-2.
(a) AFI 16-1406, Air Force Industrial Security Program, provides guidance for implementing the Air Force’s National Industrial Security Program.
(b) AFH 16-1406, National Interest Determination Handbook. This instruction clarifies responsibilities and procedures for processing National Interest Determinations (NID).
(c) AFI 16-701, Management, Administration and Oversight of Special Access Programs, establishes responsibilities for the management, administration and oversight of Special Access Programs. This instruction provides additional guidance for processing AF Special Access Program NIDs.
See SMC PGI 5304.402.
(a) Upon receiving adequate written justification from the requesting program office or activity, the contracting officer reviews, validates, and processes the NID and associated written approvals, in accordance with AFH 16-1406, National Interest Determination Handbook.
(b) The contracting officer shall maintain a copy of the approved program, project, or contract specific NID package in the contract file.
See SMC PGI 5304.403.
The contracting officer must insert the clause at AFFARS 5352.204-9000, Notification of Government Security Activity and Visitor Group Security Agreements, in solicitations and contracts which require a DD Form 254 for performance on U.S. Government installations and overseas. The contracting officer may change the number of days specified in AFFARS 5352.204-9000(a). If less than thirty days is used, coordinate with the servicing information protection office.
Immediately subsequent to each contract action, the contracting officer must place approved Contract Action Report (CAR) in the official contract file. The approved CAR provides evidence that the contracting officer has reviewed and validated the accuracy of the data reflected in the CAR when a contract action is accomplished.
See AFMC PGI 5304.605-90.
See AFMC PGI 5304.606.
See SMC PGI 5304.606.
See SMC PGI 5304.802.
SCOs may use the Air Force contract file content index templates below, or their own specific contract file content checklist or index to maintain contract files:
See SMC PGI 5304.803.
See SMC PGI 5304.804.
(c) The contracting officer should refer to the Standard Operating Procedure (SOP) for Internal Use Software (IUS) Accountability found in AFMAN 17-1203 when an IUS is identified by the requiring activity.
See SMC PGI 5304.1601.
See AFMC PGI 5304.1602.
The contracting officer administering the contract must obtain a contractor DoDAAC (see AFMAN 23-230, Maintaining Air Force DoD Activity Address Codes (DoDAAC)) for contracts that furnish Government property or authorize requisition from a Government supply source. The contracting officer administering the contract must provide the DoDAAC to the program management office/requiring activity to facilitate the shipment of government furnished property. The Purpose Code Management module contained within Procurement Integrated Enterprise Environment (PIEE) must be used to:
(a) Obtain the existing DoDAAC or submit a new DoDAAC request for all contracts awarded;
(b) Initiate contractor DoDAAC account changes, including extensions of contract completion dates and contract terminations;
(c) Initiate contractor DoDAAC deletion when the contract is physically complete, unless the DoDAAC covers other active contracts; and,
(d) Validate contractor DoDAACs in accordance with AFMAN 23-230, paragraph 4.2.
See SMC PGI 5304.7105.