V1.5 SP 25.0
From FPDS-NG
Contents
Schedule
| Description | Start Date | End Date |
|---|---|---|
| Beta Deployment | May 19, 2025 | May 19, 2025 |
| Production Deployment | May 31, 2025 | May 31, 2025 |
Document Changes
| Documentation | Changes Required |
|---|---|
| XML Specifications | No |
| Web Services | No |
| Data Dictionary | Yes |
| NASA Specific Data Dictionary | No |
| Use Case Summary | No |
| Validation Rules | No |
| ezSearch | No |
| Atom Feeds | No |
| Online Help | No |
| User Manual | Yes |
Federal Procurement Data System (FPDS) Version 1.5 Service Pack Requirements (SPR) Listing
| SPR # | Enhancement/Problem | Solution | Impact on Users and Integrators |
|---|---|---|---|
| IAEMOD-40815 | On Other Transaction Awards and IDVs, on 'Novation Agreement' modifications, updated UEI information propagates incorrectly to existing ‘UEI Change’ and 'Novation Agreement' modifications | “Unique Entity ID” (UEI) changes made to a ‘Novation Agreement’ modification of an Other Transaction Award or Other Transaction IDV shall only be applied to appropriate sets of subsequent modifications.
When a contracting officer corrects the UEI on a ‘Novation Agreement’ modification of an Other Transaction Award or Other Transaction IDV, the updated UEI shall now propagate only to modifications that occur after (based on “Date Signed”) the corrected ‘Novation’ modification and up to, but not beyond, the next ‘Novation’ modification in the contract’s lifecycle. |
Yes |
| IAEMOD-42685 | On Other Transaction records created as 'Change PIID' modifications, the value of "Primary Consortia Member’s UEI for this Award" is removed | On Other Transaction Award and Other Transaction Indefinite Delivery Vehicle modifications created with 'Change PIID' as the “Reason for Modification,” the value of the "Primary Consortia Member’s UEI for this Award" data element shall be propagated from the base record and be retained. | Yes |
Federal Assistance Award Data Collection (FAADC) Version 1.2 Service Pack Requirements (SPR) Listing
| SPR # | Enhancement/Problem | Solution | Impact on Users and Integrators |
|---|---|---|---|
| IAEMOD-43884 | On Correct, the "Discretionary" data element incorrectly propagates to existing Amendments | Currently, when the user corrects a finalized V1.2 Grant or Cooperative Agreement, the value of the “Discretionary” data element propagates to existing Amendments, replacing the values selected when the Amendments were created. In combination with the values of “Funding Opportunity Number,” “Funding Opportunity Goals Text,” and “Competed Opportunity,” the propagated value may cause an Amendment to violate FAADC Validation Rules. When the user corrects a finalized V1.1 Grant or Cooperative Agreement, a ‘null’ value propagates to the “Discretionary” data element of existing V1.2 Amendments, removing the values selected when the Amendments were created. The FAADC application shall be updated so the value of the “Discretionary” data element does NOT propagate to existing V1.2 Amendments when a finalized V1.1 or V1.2 base document is corrected. | Yes |