FAR 4.606(a)(2) requires the GSA Center for Charge Card Management (CCCM) to provide the Government purchase card data, at a minimum annually, and GSA will incorporate that data into FPDS for reports. Currently the Government purchase card data is not being reported into FPDS. Instead, the data is posted on the GSA SmartPay® website at the below URL. Please contact This email address is being protected from spambots. You need JavaScript enabled to view it. with questions related to this FAR 4.606(a)(2) reporting requirement. The URL for the SmartPay reporting data is: https://smartpay.gsa.gov/about/statistics/

Begin using the Unique Entity ID (SAM) from SAM.gov on April 4, 2022

Change is coming. Starting Monday, April 4, 2022, the new Unique Entity ID from SAM.gov will be the official governmentwide identifier used for federal awards. 

On April 4, 2022, FPDS users will no longer use the DUNS Number to identify vendors. Instead, vendors will only be identified by the Unique Entity ID (SAM). To find an entity’s Unique Entity ID (SAM), see this FAQ at our supporting Federal Service Desk, fsd.gov. The DUNS Number will no longer be accepted in FPDS input.

The Unique Entity ID (SAM) is already visible and available for data entry in FPDS. Remember, prior to April 4, 2022, the authoritative unique entity identifier is the DUNS Number. On and after April 4, 2022, the authoritative unique entity identifier will be the Unique Entity ID (SAM). 

For Interfacing Systems ONLY:

• Because the Unique Entity ID (SAM) data element is not present in pre-V1.5 FPDS Schema/WSDLs, the Unique Entity ID (SAM) cannot be corrected using the older version WSDL/Schema in which the contract action was initially created.
• If an interfacing system corrects an older version using the V1.5 Schema/WSDL, then it can update the Unique Entity ID (SAM) on older versions.
• If an interfacing system uses the pre-V1.5 Schema/WSDL to correct the CAR, you must use the web portal to correct the Unique Entity ID (SAM) via the user interface. In this case, you can use the entity lookup next to the “Entity Name” field to search for and select the correct entity.

For Atom Feed Systems ONLY:

• The Entity Data Source tag (<entityDataSource>) shall be populated with values of either 'D&B' or 'E&Y' beginning April 4, 2022. This tag was implemented during UEI Phase 1, V1.5 Service Pack 9 to track source of entity name and address information, and is displayed in Atom Feeds only.
• All FPDS and FAADC records containing a UEI (DUNS) value and were finalized on or prior to the V1.5 FPDS Service Pack 13 Production deployment (4/2/2022) shall be internally appended with a value of 'D&B'.
• The 'Last Modified Date' of existing records shall not be updated as part of this update, and this update will not be pushed to downstream Atom Feed systems.
• Please refer to the FPDS FAQ and Atom Feed FAQ for more information regarding Entity Data Source tag location/applicable values, and removal of UEI (DUNS)-related tags from Atom Feed views.

A new FPDS Atom Feed version of 1.5.3 is to be implemented with FPDS V1.5 Service Pack 15 (10/29/2022) and will impact the following feeds.

• Public (Civilian) Atom Feed
• DoD Authenticated Atom Feed

The aforementioned FPDS Atom Feeds will be updated to include the following tag names that are relevant to the Consortia data elements and are applicable to Other Transaction (OT) records only.

<ns1:consortiaInformation>
     <ns1:consortiaFlag/>
     <ns1:primaryConsortiaMemberUEI/>
     <ns1:primaryConsortiaMemberName/>
     <ns1:primaryConsortiaMemberCageCode/>
     <ns1:primaryConsortiaLocation>
                <ns1:streetAddress1/>
                <ns1:streetAddress2/>
                <ns1:streetAddress3/>
                <ns1:city/>
                <ns1:state/>
                <ns1:ZIPCode/>
                <ns1:congressionalDistrictCode/>
                <ns1:countryCode/>
     </ns1:primaryConsortiaLocation>
<ns1:consortiaInformation>

*Note that <ns1:consortiaInformation> will be in the xpath directly under <ns1:contractDetail>

After 10/29/2022, there will be two versions (V1.5.2 and V1.5.3) of the FPDS Atom feeds that will be available for use.

As applicable entity information will only be displayed on FPDS V1.5.3 Atom Feeds and beyond, the following FPDS V1.5.2 Atom Feeds shall be decommissioned along with the FPDS V1.5 Service Pack 17 deployment schedule:

• Beta Decommission Date: 4/10/2023
  
  • V1.5.2 Public (Civilian) Atom Feed
  • V1.5.2 DoD Authenticated Atom Feed

• Prod Decommission Date: 4/29/2023
  
  • V1.5.2 Public (Civilian) Atom Feed
  • V1.5.2 DoD Authenticated Atom Feed

For additional information regarding FPDS V1.5 Service Pack 15, including the content and associated implementation dates, the Service Pack Release notes can be accessed on the FPDS status page:
https://www.fpds.gov/fpdsng_cms/index.php/en/status.html

The FPDS XML Archives have been decommissioned from FPDS with the production implementation of V1.5 Service Pack 9 on 6/12/2021.

Users of the XML archives are directed to transition to utilize FPDS Atom feeds to consume FPDS Contract Action Report data. As the archives will be decommissioned as part of V1.5 Service Pack 9, the current XML archives information will not be updated to include UEI information.

Specific guidance from the FPDS tier 2 help desk will be provided to users who are transitioning from the XML archives to the FPDS Atom feeds. For any assistance in the transition to Atom feeds, please create a ticket with the Federal Service Desk (FSD), and request that it be escalated to the FPDS tier 2 help desk. The FSD can be contacted as follows:

Website: www.fsd.gov
FSD Phone Contact: (866) 606-8220

 Additional helpful material for users of the FPDS Atom feeds include the Atom Feed FAQ, and the Atom Feed demo slides. The Atom feed FAQ includes answers to common Atom feed questions, which can be accessed at the following link:

 https://www.fpds.gov/wiki/index.php/ATOM_Feed_FAQ

The Atom feed demo slides contain details of the Atom feeds, including instructions on how to put together query URLs. The slide presentation can be accessed at the following link:

https://www.fpds.gov/downloads/Atom_feed/Atom_feed.ppt

For additional information on Service Pack 9, including the content of the release, and the associated deployment and Government Acceptance Testing dates, the Service Pack 9 release notes can be accessed at the following URL:

https://www.fpds.gov/wiki/index.php/V1.5_SP_9.0

As part of the implementation of V1.5 Service Pack 9, a new version of the FPDS Atom feed is being introduced (V1.5.2) to include Unique Entity Identifier (UEI) information. Along with the implementation of FPDS Atom Feed V1.5.2, to ensure that FPDS Atom feed users are all receiving the latest contract action report formatting, all FPDS Atom Feed versions prior to V1.5.2 shall be decommissioned, on a scheduled decommission timeline.

For both Public and DoD Atom Feeds:

1. The following FPDS Atom feeds were decommissioned along with the V1.5 Service Pack 9 Beta Deployment, on 5/14/2021:

V1.4
V1.4.1
V1.4.2
V1.4.3

2. The following FPDS Atom feed versions were decommissioned 3 months after V1.5 Service Pack 9 Production Deployment, on 9/11/2021:

V1.4.4
V1.4.5
V1.5.0

3. The following FPDS Atom feed versions were decommissioned 4 months after V1.5 Service Pack 9 Production Deployment, on 10/16/2021:

V1.5.1

After the decommissioning tasks listed above, the ONLY active version of the FPDS Atom feed will be FPDS V1.5.2.  For additional information regarding FPDS V1.5 Service Pack 9, including the content and associated implementation dates and Government Acceptance Testing dates, the Service Pack Release notes can be accessed at the following link:

https://www.fpds.gov/wiki/index.php/V1.5_SP_9.0

Multi-factor authentication (MFA) for FPDS is now mandatory for FPDS users as of Saturday, December 5, 2020.

In order to improve the security of the FPDS user log in process, FPDS now integrates with login.gov to enable multi-factor authentication.

• Multi-factor authentication (MFA) for FPDS is now mandatory for individual FPDS users as of Saturday, December 5, 2020. There are no changes for FPDS System account users.
• Multi-factor authentication (MFA) is a security enhancement that requires two forms of authentication when individual users log into FPDS and adds critical protection for your sign-on credentials.
• All individual users should create an account with login.gov with the same email address associated with your FPDS account.
• By creating a login.gov account with the same email address as the existing user FPDS account, after integration with login.gov, the process will enable the user to log into FPDS to perform normal business activities.

Please see below helpful Login.gov links to help with the registration process:

• Login.gov general help page

https://login.gov/help/

• How to create an account with Login.gov

https://login.gov/help/creating-an-account/how-to-create-an-account/

• An overview of the authentication method options that are available for users

https://login.gov/help/authentication-methods/which-authentication-method-should-i-use/

Attention: FPDS reports module is now retired.

Go to SAM.gov to access any Contract Data Reports.

On October 17, 2020, the FPDS reports module retired and the SAM.gov Data Bank is the only place to create and run both standard and ad hoc reports on federal contract data. Learn more about the transition.

Static reports like National Interest Action reports (including the bi-weekly COVID-19 report), the annual Small Business Goaling Reports, the annual Top 100 Contractor Reports, and other periodic reports of government-wide data, remain publicly available. Download them from https://sam.gov/reports/awards/static.

If you are searching for details on specific contracts, continue using FPDS ezSearch as FPDS remains the authoritative source for entering and viewing details about contract award data.

This article provides the prerequisites and instructions to create a helpdesk ticket to correct a Multiple or Single Award IDV value.

1. Multiple to Single Conversion
   
   
   1. Identify all agencies that have placed orders against the IDV
   2. Inform agency administrators of each agency that “Fair Opportunity/Limited Sources” will be updated to blank
   3. Obtain approval from each of the Order agency administrators for the change
   4. Submit a ticket to the www.FSD.gov Help Desk
   5. FPDS will perform a data management fix to convert the IDV from Multiple to Single. Once the fix is executed the following associated Order information will be provided
      • Summary counts by agency
      • Department Name (ID)
      • Contracting Agency Name (ID)
      • PIID details
        • Agency
        • PIID
        • Modification Number
        • Transaction Number
        • IDV PIID
        • IDV Agency
        • IDV Modification Number
      • Date Signed
      • Dollar Amounts
   6. Agency administrators should ensure that Competition information is accurate on any associated Delivery Orders.

1. Single to Multiple Conversion
   
   
   1. Identify all agencies that have placed orders against the IDV
   2. Inform agency administrators of each agency that the following data elements will be updated to blank on orders referencing the IDV and they are in charge of getting the data updated after the data fix.
      
      • Local Area Set-Aside
      • Number of offers received
      • Recovered Material Clauses
      • Statutory Exception to Fair Opportunity
   3. Obtain approval from each of the Order agency administrators for the change
   4. Submit a ticket to the www.FSD.gov Help Desk
   5. FPDS will perform a data management fix to convert the IDV from Single to Multiple. Once the fix is executed the following associated Order information will be provided
      • Summary counts by agency
      • Department Name (ID)
      • Contracting Agency Name (ID)
      • PIID details
        • Agency
        • PIID
        • Modification Number
        • Transaction Number
        • IDV PIID
        • IDV Agency
        • IDV Modification Number
      • Date Signed
      • Dollar Amounts
   6. Agency administrators should ensure that Competition information is accurate on any associated Delivery Orders.