V1.5 SP 20.0

From FPDS-NG

Revision as of 14:37, 30 January 2024 by WikiSysop (talk | contribs)

Schedule

DescriptionStart Date End Date
Beta DeploymentJanuary 08, 2024January 08, 2024
Government Acceptance Testing January 16, 2024January 19, 2024
Production Deployment January 27, 2024January 27, 2024

Document Changes

DocumentationChanges Required
XML SpecificationsNo
Web ServicesNo
Data DictionaryYes
NASA Specific Data DictionaryNo
Use Case SummaryYes
Validation RulesYes
ezSearchYes
Atom FeedsNo
Online HelpYes
User ManualNo

SPR Listing


SPR #Enhancement/ProblemSolutionImpact 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:
  • TYPE OF SET-ASIDE SOURCE
  • NUMBER OF OFFERS RECEIVED SOURCE
    		• No
    IAEREQ-7585/IAEMOD-21137 Update to FAB Business Types mapping to remove Date restriction for "Non-domestic (non-US) Entity" and disable SAM Business Types The FAADC application will be updated to system generate the value of "Non-domestic (non-US) Entity" to the "FABS Business Category" section and disable (lock) the SAM Business Types, regardless of the Assistance "Action Date", when the UEI is valid and "Foreign" is selected for "2 CFR Part 25 Exception". Yes
    IAEREQ-7526/IAEMOD-21928 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.

    The Contracting Office field must be empty for the Role "OTHER TRANSACTION" and has to be removed from the user profile for the user: "USER_XXXX"

    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.
    • The heading for column “DR” in the FAADC Assistance Extract shall be updated accordingly.
    • Any occurrence of the incorrect name in FPDS and FAADC documents shall be updated as well.
    		 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 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.

    • Per OMB policy, the Award Description for a modification should serve two functions:

    1. Describe what the modification itself is accomplishing. 2. Provide information about the award.

    		Yes
    IAEMOD-19698 "Legal Business Name" propagation issue on Save/Correct for 'Reason For Modification' on OT's The FPDS application will be updated for Other Transactions so that the ‘Legal Business Name’ (Entity with a name change) will be refreshed from SAM when the Reason for Modification is corrected to be a Novation Agreement.

    AND:

    The ‘Legal Business Name’ (Entity with a name change) will be reverted to its previous value when correcting an OT Novation Agreement and changing the Reason for Modification to a selection that does not update the Legal Business Name.

    		Yes
    IAEMOD-20385 Propagation issue for "IDV Number Of Offers" on Part 8 BPA that references an FSS modification. The FPDS application will be updated so the value of the 'IDV Number of Offers' data element on a Part 8 BPA (referencing an FSS) will continue to match the value on the referenced FSS modification after the FSS base (mod 0) contract has been corrected. Yes
    IAEMOD-21133 Correction issue on LBN value for Rerepresentation vendor modifications 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 Legal Business 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 NOT be refreshed from SAM when the record is Created/Approved.

    This issue is specific to UEI’s (Unique Entity Identifiers) that had changed “Legal Business Name” and on specific Awards type records only.

    		Yes
    IAEMOD-22670 Disable the National Interest Action data element on the FPDS Application


    		National Interest Action (NIA) data element will be decommissioned and will not be collected on new Contract Action Reports (CAR) on or after January 27, 2024.

    NIA data elements will continue to be available for correction on the existing CARs.

    		Yes
    Retrieved from "https://fpds.gov/wiki/index.php?title=V1.5_SP_20.0&oldid=5007"