A community resource for the acquisition workforce not a .gov website
part52.dev Federal Acquisition Clause Monitor
Deviated Text
This text comes from the Word attachment to class deviation 2026-O0043, not from acquisition.gov. The deviation memo directs contracting officers to use it in place of the codified PGI. The source attachment linked below is authoritative.

Text

(a)(1) Helpful documents. The Federal Procurement Data System (FPDS) website at https://www.fpds.gov provides useful documentation assist with FPDS data entry. The Data Dictionary and FPDS User’s Manual are provided to guide users on data requirements and to facilitate the accurate entry of data into the FPDS. These documents can be found at the top of the website homepage under the “Training” and “Worksite” tabs to include:

(i)  FPDS Data Element Dictionary. There is a Data Dictionary specific to contracts and Other Transactions. The Data Dictionary data dictionary outlines relevant information for each data field. The Data Dictionary identifies whether a data field is “Required,” “Optional,” “Propagates from the base action,” “Not Applicable,” or “System Generated,” for each type of data entry screen (Awards, Indefinite-Delivery Vehicles, Other Transactions, and Transactions/Modifications). It also identifies the source of data entry (e.g., Contracting Officer, (SAM), FPDS); the format of the field; and whether the field input is derived from entries in other fields. At the back of the Data Dictionary is a useful summary.

(ii)  FPDS Data Validations. This document identifies all the validation rules that are applied to data entry. Most of the rules apply Governmentwide. DoD specific validation rules are clearly identified with the prefix “DoD” throughout the document and in section “1.5.1 DoD Specific Validations”.

(iii)  FPDS Users Manual. This manual provides general guidance on how to navigate FPDS, familiarize users with FPDS data requirements and assist them with FPDS data entry. The nature of the fields in this document were determined based on Governmentwide requirements. To determine DoD-specific requirements, refer to the Instructions that mention “DoD” in the FPDS Data Element Dictionary. The FPDS User Manual is not a policy document; it is intended only for general guidance. Refer to PGI for specific FPDS reporting requirements.

(2)  Reporting technical or policy issues.

(i)  Technical issues. To report an FPDS technical issue—

(A)(1) Users of contract writing systems should contact the local contract writing system administrator to determine the appropriate procedures; and

(2) Web users should contact their local system administrator, who will then contact the FPDS Help Desk if further support is required; or

(B) If the issue is an obvious FPDS technical issue that needs to be documented and corrected by the system, the user should create and submit a trouble ticket with the Federal Service Desk (https://www.fsd.gov/), or submit a comment or request via the Live Chat at www.fsd.gov. When submitting a ticket to When e-mailing FSD, also send a copy to the applicable agency representative identified in paragraph (2)(iii) of this section.

(ii)  Policy issues. Report policy issues and submit or questions to the applicable agency representative identified in paragraph (2)(iii) of this section.

(iii) Agency representatives. Department and component FPDS representatives and their contact information can be found at https://dodprocurementtoolbox.com/site-pages/ebusiness-fpds-ng.

Sources: Deviation attachment (.docx) · Codified PGI 204.301-70