V1.5 SP 20.0
From FPDS-NG
Schedule
| Description | Start Date | End Date |
|---|---|---|
| Beta Deployment | January 08, 2024 | January 08, 2024 |
| Government Acceptance Testing | January 16, 2024 | January 19, 2024 |
| Production Deployment | January 27, 2024 | January 27, 2024 |
Document Changes
| Documentation | Changes Required |
|---|---|
| XML Specifications | No |
| Web Services | No |
| Data Dictionary | Yes |
| NASA Specific Data Dictionary | No |
| Use Case Summary | Yes |
| Validation Rules | Yes |
| ezSearch | Yes |
| Atom Feeds | No |
| Online Help | Yes |
| User Manual | No |
SPR Listing
| SPR # | Enhancement/Problem | Solution | Impact to Users and Integrators |
|---|---|---|---|
| IAEREQ-9577/IAEMOD-18759 | Add two data elements to FPDS Data Dictionary | This is an update to the FPDS Data Dictionary V1.5 to add two system generated data elements that were not included:
| No |
| IAEREQ-7585/IAEMOD-21137 | Update to FAB Business Types mapping to remove Date restriction for "Non-domestic (non-US) Entity" | This is a correction to the FAADC application so that when "Foreign" is selected as the 2 CFR Part 25 Exception and the Foreign UEI is not registered in SAM, the system will auto-assign the value of "Non-domestic (non-US) Entity" to the FABS Business Category data element.
Also, regardless of the Action Date, when the UEI is foreign and not in SAM, the system will auto-assign the value of "Non-domestic (non-US) Entity” to the FABS Business Category after clicking “Save Draft.” |
Yes |
| IAEREQ-7526/IAEMOD-21928 | This is a Defect Fix: Suppress the message preventing FPDS Admins from assigning OT Role (only) to account with Contracting Office ID | The FPDS application will be updated so that when an Administrator populates the Contracting Office ID field in a user account and then attempts to assign the “Other Transaction” role (only) to the account, the message below shall be suppressed.
AND: When a user account that has the “Other Transaction” role (only) attempts to use Validate or Correct action on an “Other Transaction” record, a validation rule shall fire, if the Contracting Office ID on the OT record differs from the Contracting Office ID on that user account. |
Yes |
| IAEMOD-20055 | Update the name of FPDS data element 13LB (FAADC data element 11O) from "Community Developed Corporation Owned Firm" to "Community Development Corporation-Owned Concern" on FPDS and FAADC screens and in related documents | *The GUI Screen Name for FPDS data element 13LB / FAADC data element 11O shall be updated from Community Developed Corporation Owned Firm to Community Development Corporation-Owned Concern on all FPDS and FAADC screens.
|
Yes |
| IAEMOD-21762 | Incorrect validation rules being triggered when updating Grants offices | This is a defect fix to allow the “Grants Office Start Date” to precede the “Funding Office End Date”. | Yes |
| IAEMOD-20226 | Update the FAR/DFARS reference in detail for data element 10R in the FPDS Data Dictionary | This is a correction to the FPDS Data Dictionary. There are erroneous FAR references in the Values table for data element 10R, “Fair Opportunity/Limited Sources.” | Yes |
| IAEMOD-21993 | FPDS Documentation Updates: Update Definition in FAADC Data Dictionary for Data Element 1I | This is an update to the FAADC Data Dictionary that will provide a more detailed definition for FAADC data element “Assistance Description” (1I).
For all Federal financial assistance, agencies are required to establish detailed and accurate award descriptions at the time of award. Assistance descriptions are critical to ensuring accountability and transparency, as they are a primary means to inform the public of the purpose of the Federal funding that is distinct from the programmatic level information in the Assistance Listings. At a minimum, Assistance descriptions should provide specificity about the award purpose, activities to be performed, deliverables and expected outcomes, and intended beneficiary(ies) or recipient of the funds, as well as subrecipient activities if known or specified at the time of award.
|
Yes |
| IAEMOD-19698 | "Legal Business Name" propagation issues with specific “Reason for Modification” values for OT Order & OT IDV records | The FPDS application will be updated so ‘Legal Business Name’ (Entity with a name change) will display from SAM Vendor Modifications for these record types:
AND: The ‘Legal Business Name’ (Entity with a name change) will propagate from the Base (mod 0) or from one of the following Vendor Modifications based on ‘Date Signed’ on Save Draft/Correct:
|
Yes |
| IAEMOD-20385 | Propagation issues when "IDV Number Of Offers" is corrected Note: This issue is specific to UEI’s (Unique) Entity Identifiers) that had changed “Legal Business Name” on specific Awards type records only.on FSS | The FPDS application will be updated so the value of the 'IDV Number of Offers' data element on the Part 8 BPA (referencing an FSS modification) will continue to match. the value on the FSS base contract after the FSS base contract has been corrected. | Yes |
| IAEMOD-21133 | Correction issue with all-vendor modification values | The FPDS application will be updated so when existing Award Modifications are corrected and the ‘Reason for Modification’ is changed to Rerepresentation or Rerepresentation of Non-Novated Merger/Acquisition, then the "Legal Business Name" will pull the current value from SAM.
Note: This is to ensure the correction functionality matches the current behavior for newly created Rerepresentation modifications. |
Yes |
| IAEMOD-21220 | Vendor Name is incorrectly updated for Entity Address Change on Create/Approve | This is a defect fix so that ‘Legal Business Name’ for modifications with ‘Reason for Modification’ as ‘Entity Address Change’ will propagate the value from the base record on Create/Approve.
This issue is specific to UEI’s (Unique Entity Identifiers) that had changed “Legal Business Name” and on specific Awards type records only. | Yes |