(Revised 19 May 2022)
Contracting officers will insert FAR clause 52.204-1, Approval of Contract, in solicitations and contracts when an agency official other than the contracting officer is the approval authority.
In addition to DFARS 204.201 requirements for bilateral contracts, contracting officers shall distribute a copy or reproduction of the contract form showing the contractor’s signature. The copy or reproduction shall be in the “portable document format” (.pdf) for distribution via electronic mail (email) or other electronic means.
Distribute a copy of contracts for utility services and communications to:
General Services Administration/Public Buildings Service
Office of Procurement, Public Utilities Service Division (PPU)
Room 7322, GSA Building
18th & F Streets NW
Washington DC 20405.
(d)(1) The National Industrial Security Program (NISP) Contract Classification System (NCCS) module Version 2.0 re-deployed effective 1 May 2022. Contracting officers shall follow the procedures at FAR 4.402(d)(1) to transmit DD Form 254s to the Defense Counterintelligence Security Agency (DCSA).
(1) In accordance with DFARS PGI 204.403(1), the contracting officer will include a DoD Form DD 254, DoD Contract Security Classification Specification in solicitations as appropriate and obtain the security manager’s signature (see Army Regulation 380-49, 4-4a, Department of the Army Industrial Security Program) as the certifying official on the form.
(2) See AFARS PGI 5104.403(2)-1.
(b)(4) Electronic commerce in contracting is satisfied if the reverse auction application posts the synopsis (or combined synopsis-solicitation) to SAM.gov.
The Assistant Secretary of the Army (Acquisition, Logistics and Technology) on a non-delegable basis, shall ensure that systems, technologies, procedures, and processes used by the agency to conduct electronic commerce follow the guidelines set forth in FAR 4.502 (b) and (c).
(a) The Senior Procurement Executive in coordination with the head of the contracting activity is responsible for developing and monitoring a process to ensure timely and accurate reporting of contractual actions to FPDS. See Appendix GG for further delegation.
(f) Contracting officers shall utilize the Virtual Contracting Enterprise (VCE) tools throughout the acquisition process to maximize visibility and management of contract specific information and documents. VCE shall not be used for classified documents or contracts.
(i) The Paperless Contract File (PCF) module shall be used to store, access, and route documents necessary to manage the acquisition process for review and approval. Contracting officers shall ensure that the PCF contains all appropriate contract documents. If the contract document is maintained within the Procurement Integrated Enterprise Environment (PIEE, https://wawf.eb.mil/) or the Federal Procurement Data System-Next Generation (FPDS-NG)), then that system is the official system of record; contracting officers should not duplicate the document and file it in the PCF.
Follow procedures at AFARS PGI 5104.802(f)(i)-1.
Follow procedures at AFARS PGI 5104.802(f)(i)-2.
(1) The Army Cabinet Index folder structure shall be used when filing documents in PCF to ensure standardization throughout Army contract files. See AFARS PGI 5104.802(f)(i)(1) for instructions to access the cabinet index structure.
(2) The Protest and Claims Tracking tool shall be used when the contracting officer receives knowledge of a preaward or postaward protest submitted to any venue.
(3) Milestone Tracking shall be used to forecast and document dates for initiation and completion of key documents and milestones. The VCE tool identifies the mandatory data fields based on specific criteria for the acquisition.
(4) Mission Partner/Requirement Owner Functionality shall be used by requirements owners to create cabinets and submit documents to contracting organizations. Contracting officers shall assist requirements owners as necessary to ensure utilization of the tool.
(ii) VCE Warrants Module shall be used to issue and track contracting officer and grant officer warrants; see 5101.603-3.
(iii) VCE shall be used for the Announcement of Awards and Small Business Coordination Record (DD Form 2579); see 5105.303 and 5119.201(d)(10)(B)(i) respectively.
(a)(24) Legal reviews in accordance with 5101.602-2-90(c) shall be done in writing and documented in the contract file.
(2) The head of contracting activity shall perform the duties as described in DFARS 204.804(2). See Appendix GG for further delegation.
(a)(12) When the contractor submits an adequate final indirect cost rate proposal in accordance with FAR 42.705-1(b)(1)(iii), the contracting officer must obtain a Defense Contract Audit Agency audit report or document the file with a memorandum that deems the proposal to be low-risk and not subject to further audit before closing out the contract file.
(a) The Assistant Secretary of the Army (Acquisition, Logistics and Technology) shall report the information set forth in FAR 4.903 to the IRS. See Appendix GG for further delegation.
(a) Definition. As used in this section, the following terms have the same meaning as given in the Implementation Guide for Internal Use Software located on the Procurement.Army.Mil Knowledge Management Portal at https://spcs3.kc.army.mil/asaalt/zp/doccenter/Documents/Policy Alert 19-79 Instructions for Accounting for IUS in Contract Documents.msg.
(1) internal use software
(b) Procedures. When procuring internal use software, Army contracting activities shall—
(1) Confirm that the requiring activity has established separately identifiable line items for all capitalized and expensed requirements in the purchase request;
(2) Ensure the line item structure aligns with the lines of accounting related to the capitalized and expensed classifications assigned by the requiring activity; and
(3) Include appropriate invoicing instructions and acceptance criteria in the solicitation and contract or order.
See AFARS PGI 5104.7304-1 for implementation guidance of Enhanced Security Protections for Contractor Information Systems.