NOTICE: FPDS Downtime Notification
The FPDS production application (https://www.fpds.gov) will be down for scheduled maintenance on Saturday, December 21st, 2024, from 8:00 AM to 3:00 PM (EST).
During the downtime, the FPDS web portal, web services, ezSearch tool, and search capabilities will be unavailable for regular use.
|
|
The National Interest Action data element on the FPDS application has been disabled as of January 27, 2024 |
|
The National Interest Action (NIA) data element has been decommissioned and will not be collected on new Contract Action Reports (CAR) on or after January, 27, 2024. The NIA data elements will continue to be available for correction of the existing CARs. |
GSA SmartPay Reports |
|
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/ |
New FPDS Atom Feed Version 1.5.3 |
|
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
|
Transition from Unique Entity (DUNS) to Unique Entity ID (SAM) |
|
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.
|
|
|