V1.5 SP 26.0

From FPDS-NG

Schedule

DescriptionStart Date End Date
Beta DeploymentJune 20, 2025June 20, 2025
Government Acceptance TestingJune 24, 2025June 24, 2025
Production Deployment June 28, 2025June 28, 2025

Document Changes

DocumentationChanges Required
XML SpecificationsNo
Web ServicesNo
Data DictionaryYes
NASA Specific Data DictionaryNo
Use Case SummaryNo
Validation RulesYes
ezSearchNo
Atom FeedsYes
Online HelpNo
User ManualYes

Federal Procurement Data System (FPDS) Version 1.5 Service Pack Requirements (SPR) Listing

SPR #Enhancement/ProblemSolutionImpact on Users and Integrators
IAEENH-1288 / IAEMOD-44550 Changes for Data Element 6T, “Inherently Governmental Functions” The FPDS application shall be updated to assign the new name, “Nature of Services,” to FPDS data element 6T, replacing the former name (“Inherently Governmental Functions”) on the screen, in Validation Rule messages, and in FPDS documents.

New Validation Rules 6T09 and 6T10 shall be created for contracts with a “Date Signed” on or after 06/28/2025, without exception logic for “Product Service Code” ‘R497.’ The Validation Rule messages shall read:

  • 6T09: When PSC is a Product, the “Nature of Services” value must be blank.
  • 6T10: When PSC is a Service, a value for “Nature of Services” must be entered.


The current Validation Rules, 6T07 and 6T08, shall only apply to contracts with a “Date Signed” before 06/28/2025. The Validation Rule messages shall be updated to read:

  • 6T07: When PSC is a Product or PSC = R497, and the “Date Signed” is between 04/29/2023 and 06/27/2025, the “Nature of Services” value must be blank.
  • 6T08: When PSC is a Service (except when PSC = R497), and the “Date Signed” is between 04/29/2023 and 06/27/2025, a value for “Nature of Services” must be entered.
Yes
IAEMOD-39990 In FPDS Public and DoD Atom Feeds, values for the "Community Development Corporation" and "Community Development Corporation-Owned Concern" data elements are reversed The FPDS application shall be updated to ensure that the Public and DoD Atom Feeds display accurate values for the "Community Development Corporation" and "Community Development Corporation-Owned Concern" data elements. Currently, the values displayed in the XML Tags, isCommunityDevelopmentCorporation and isCommunityDevelopedCorporationOwnedFirm, in the Public and DoD Atom Feeds are reversed from the values stored on each contract in the FPDS database. Yes

Federal Assistance Award Data Collection (FAADC) Version 1.2 Service Pack Requirements (SPR) Listing

SPR #Enhancement/ProblemSolutionImpact on Users and Integrators
IAEMOD-44656 Decommissioning of FAADC 1.1 Atom Feeds Currently, users can access the FAADC V1.1 ASSISTANCE and ASSISTANCEDELETED Atom Feeds. These FAADC Atom Feeds have remained operational since November 16, 2024, when FAADC Version Change 1.2 was deployed to production. The V1.1 ASSISTANCE and ASSISTANCEDELETED Atom Feeds shall be deprecated, as data no longer displays in generic XML Tags previously assigned to six (6) FAADC data elements, which were replaced by dedicated XML Tags, and essential data displays in the new XML Tags added for FAADC V1.2. Yes
IAEMOD-43005 "Federal Action Obligation" field is editable on Aggregate Other Financial Assistance records Currently, the “Federal Action Obligation” data element is editable at the record level on Aggregate Other Financial Assistance records. Starting with FAADC V1.2, this data element should be locked/disabled at the record level, because it is auto-calculated as the sum of “Federal Action Obligation” values entered on the Assistance Listing(s) on the record. When the user enters a value at the record level, it temporarily overrides the auto-calculated sum, but when the user clicks ‘Save Draft,’ the auto-calculated sum replaces the user-entered value. The FAADC application shall be updated to disable the “Federal Action Obligation” field at the record level. Yes