PART 5304 -
[ Revised June 3, 2016 ]
SUBPART 5304.1 — CONTRACT EXECUTION
5304.101 Contracting Officer’s Signature
(INTERIM CHANGE: See Policy Memo 16-C-03)
Contracting Officers shall manually sign via wet signature all contract actions and ensure contractor signatures are obtained. A scanned signature page for all contract actions shall be uploaded into Electronic Data Access (EDA) and the Contracting Officer will validate that the wet signature page is attached within EDA.
SUBPART 5304.4 — SAFEGUARDING CLASSIFIED INFORMATION WITHIN INDUSTRY
(a) AFI 16-1406, Air Force Industrial Security Program, provides guidance for implementing the Air Force’s National Industrial Security Program. This instruction clarifies responsibilities and procedures for processing National Interest Determinations (NID).
(b) 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.
5304.403 Responsibilities of Contracting Officers
(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 Air Force instruction.
(b) The Contracting Officer shall maintain a copy of the approved program, project, or contract specific NID package in the contract file.
5304.404-90 Additional Contract Clauses
The contracting officer must insert the clause at 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 5352.204-9000(a). If less than thirty days is used, coordinate with the security police activity.
SUBPART 5304.6 — CONTRACT REPORTING
5304.604 (2) Responsibilities
Immediately subsequent to each contract action, the contracting officer must print and sign the Contract Action Report (CAR) and place it in the contract file. The signed 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.
SUBPART 5304.8 -- GOVERNMENT CONTRACT FILES
5304.803 Contents of Contract Files
MAJCOMs/DRUs/AFRCO and SMC 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:
Operational Services and Construction File Checklist
Research and Development File Checklist
Systems and Logistics File Checklist
SUBPART 5304.70 -- UNIFORM PROCUREMENT INSTRUMENT IDENTIFICATION NUMBERS
5304.7003-90 Maintaining DoD Activity Address Codes (DoDAAC)
The Contracting Officer must obtain a contractor DoDAAC (see AFI 24-230, Maintaining Air Force DoD Activity Address Codes) for contracts that furnish Government property or authorize requisition from a Government supply source. The Contracting Officer must provide the DoDAAC to the program management office/requiring activity to facilitate the shipment of government furnished property. The Contracting Officer must use the DoDAAC Web Management System 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 AFI 24-230, paragraph 4.2.