V1.5 SP 29.0
From FPDS-NG
Contents
Schedule
| Description | Start Date | End Date |
|---|---|---|
| Beta Deployment | September 12, 2025 | September 12, 2025 |
| Production Deployment | September 20, 2025 | September 20, 2025 |
Document Changes
| Documentation | Changes Required |
|---|---|
| XML Specifications | No |
| Web Services | No |
| Data Dictionary | No |
| NASA Specific Data Dictionary | No |
| Use Case Summary | No |
| Validation Rules | No |
| ezSearch | No |
| Atom Feeds | No |
| Online Help | Yes |
| User Manual | No |
Federal Procurement Data System (FPDS) Version 1.5 Service Pack Requirements (SPR) Listing
| SPR # | Enhancement/Problem | Solution | Impact on Users and Integrators |
|---|---|---|---|
| IAEMOD-49205 | Funding Agency/Office fields disabled on "Novation Agreement" and "UEI Change" modifications of Other Transaction IDVs | The FPDS application shall be corrected so the “Funding Agency ID” and “Funding Office ID” fields are open/editable for Other Transaction Indefinite Delivery Vehicle modifications when the "Reason for Modification" is one of the following:
Currently, the “Funding Agency ID” and “Funding Office ID” fields are open initially, but when the “Reason for Modification” selected is either of these, both fields incorrectly become locked/disabled. If the user corrects a finalized Other Transaction IDV modification with either of these “Reason for Modification” values, both fields remain locked. This behavior occurs on Other Transaction IDV modifications in New, Draft or Final status. |
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-48670 | “Unique Record Identifier” on FAADC Non-Aggregate records does not propagate to Amendments | Currently, the user may optionally enter a value in the "Unique Record Identifier" field on a Non-Aggregate or a Non-Aggregate Individual award. When a value is entered in the “URI” field on the Base, the value does not propagate to new Amendments, and the field is open/editable while the Amendment is in 'New' status. This allows the “URI” values to differ between the Base document and the Amendments, causing other propagation issues.
The FAADC application shall be corrected to propagate the “Unique Record Identifier” value (if any) from the Base record of a Non-Aggregate or Non-Aggregate Individual award to each new Amendment and to lock the "URI" field while the Amendment is in ‘New’ status. |
Yes |