Difference between revisions of "V1.5 SP 9.0"

RTC-56803, RTC-56819, RTC-56811

UEI and UEI-hierarchy elements within Atom Feeds will not utilize generic XML tags, and will instead use UEI named XML tags. A new ‘Entity Data Source’ data element shall be created to track entity address and name information, and shall be displayed on Atom Feeds only. A new FPDS Atom Feed - V1.5.2, will be created (see RTC-56808 below for additional details).

All UEI and UEI-hierarchy data will be populated from SAM. A data management update will be performed to affix UEI data to all existing Contract Action Reports in FPDS.

The data element name will be “Unique Entity ID (SAM).” See screenshot below:

https://wwww.fpds.gov/downloads/UEI_SAM_onscreen.png

The vernacular will be updated on the FPDS GUI screens and documentation for any instances of “Vendor”, “Contractor”, “Company”, and “Recipient” to be referred to as 'Entity.’ Specific vernacular such as “Vendor Name” will be updated to “Legal Business Name” for consistency across IAE systems.

A UEI Crosswalk document containing all applicable UEI (and DUNS) information will be created and uploaded in two separate files. The first file will be uploaded as soon as FPDS receives the most up-to-date UEI information from SAM. The second file shall be uploaded after the SP9 Production Deployment date, to account for any FPDS Contract Action Reports created between these dates. Both files will be available for download to CCB members in a user-restricted JIRA IAEREQ ticket.

RTC-56808

This new version will integrate UEI changes, utilizing the existing ‘genericString02’* tag to display UEI, and new named XML tags to display UEI, UEI hierarchy, and associated UEI name information for an entity in order to match the DUNS/entity hierarchy information format on existing Atom Feeds. A new ‘Entity Data Source’ data element will be created to track the source of entity address and name information. The source will initially be Dun and Bradstreet, and in future UEI Phase implementations, will be Ernst and Young. All changes are as follows:

• A new ‘entityIdentifiers’ parent tag shall be created, storing both the existing ‘vendorDUNSInformation’ and future ‘vendorUEIInformation’ tags
• A new ‘vendorUEIInformation’ tag shall be created, storing the UEI and associated name data element tags
• The ‘cageCode’ data element tag shall become a child tag of the ‘entityIdentifiers’ tag
• A new ‘entityDataSource’ element shall be created, specifying the source of entity information
• The generic string tag, ‘genericString02,’ shall be used to populate UEI

Changes shall apply to the following FPDS Atom Feeds (containing DUNS information):

• Public Atom Feed
• Bio-Preferred Atom Feed
• DoD Authenticated Atom Feed
• eSRS Atom Feed

∗Note: In order to minimize impact to CWS users, the ‘genericString02’ tag will be used to capture the user-entered UEI value in Phase 2 UEI implementation, as generic strings have already been implemented and tested in FPDS V1.5. The ‘genericString02’ tag and associated value will still populate on Atom Feed output. The associated value shall be duplicated and displayed in the ‘UEI’ tag.

For more information about:
1. Tag names, please visit the Atom Feed FAQ: https://www.fpds.gov/wiki/index.php/ATOM_Feed_FAQ
2. Tag locations and sample schemas, please visit the FPDS Atom Feed V1.5.2 Specifications: https://www.fpds.gov/wiki/index.php/Atom_Feed_Specifications_V_1.5.2

RTC-58565

For both Public and DoD Atom Feeds:
1. The following FPDS Atom feeds will be decommissioned along with the V1.5 Service Pack 9 Beta Deployment on 5/14/2021:

• V1.4.0
• V1.4.1
• V1.4.2
• V1.4.3

2. The following FPDS Atom feed versions will be decommissioned 3 months after V1.5 Service Pack 9 Production Deployment, tentatively on 9/11/2021:

• V1.4.4
• V1.4.5
• V1.5.0

3. The following FPDS Atom feed versions will be decommissioned 4 months after V1.5 Service Pack 9 Production Deployment, tentatively on 10/16/2021:

• V1.5.1

After the decommissioning tasks listed above, the ONLY active version of the FPDS Atom feed will be FPDS V1.5.2.

RTC-58563

• Users of the XML Archives will be directed to utilize the FPDS Atom Feeds to retrieve FPDS Contract Action Report data.
• The FPDS XML Archives will not be updated to include UEI information.
• Specific guidance from the FPDS Tier 2 Help Desk will be provided to users who are transitioning from the XML archives to the FPDS Atom feeds.
• For users needing assistance in the transition to Atom feeds, FSD Tier 2 Help Desk will be utilized to escalate the issue to the FPDS Tier 2 Help Desk.

IAEENH-727, RTC-55772, RTC-56595, RTC-56596

Note: UEI and UEI-hierarchy elements within FAADC will not utilize generic XML tags, and will instead use named XML tags.

The Close Out function that was included in Version 1.5 for FPDS will also be added to FAADC. The new data elements to be displayed are as follows:

• “Closed Status”
• “Closed Date"
• “Closed By"

For exercising this option from the web portal, the user will select the “Close Out” Button, as displayed in the screenshot below.

https://www.fpds.gov/downloads/closeout_button.png

If the user selected the “Close Out” button by mistake, the user will be prompted with a screen where the user can confirm their decision to close out the open contract. If the user does not want to close the contract, the ‘No’ button will cancel the Close Out action.

https://www.fpds.gov/downloads/cancel_closeout.png

RTC-56816

A new version of the FAADC Atom Feeds - V1.1 will be created.

This new version will integrate UEI changes, new named XML tags to display UEI, UEI hierarchy, and associated UEI name information for an entity in order to match the DUNS/entity hierarchy information format on existing Atom Feeds. A new ‘Entity Data Source’ data element will be created to track the source of entity address and name information. The source will initially be Dun and Bradstreet, and in future UEI Phase implementations, will be Ernst and Young. All changes are as follows:

• A new ‘entityIdentifiers’ parent tag shall be created, storing both the existing ‘vendorDUNSInformation’ and future ‘vendorUEIInformation’ tags
• A new ‘vendorUEIInformation’ tag shall be created, storing the UEI and associated name data element tags
• The ‘cageCode’ data element tag shall become a child tag of the ‘entityIdentifiers’ tag
• A new ‘entityDataSource’ element shall be created, specifying the source of entity information

Changes shall apply to the following FAADC Atom Feeds (containing DUNS information):

• FAADC Authenticated Deleted Atom Feed

∗Note: FAADC will not use the 'genericString02' tag to capture the user-entered UEI value in Phase 2 UEI implementation, as generic strings were not previously implemented in the FAADC module. The primary UEI shall be displayed on FAADC Atom Feed V1.1 using the 'UEI' tag.

For more information about:
1. Tag names, please visit the Atom Feed FAQ: https://www.fpds.gov/wiki/index.php/ATOM_Feed_FAQ
2. Tag locations and sample schemas, please visit the FAADC Atom Feed V1.1 Specifications: https://www.fpds.gov/wiki/index.php/FAADC_Atom_Feed_Specifications_V_1.1

RTC-56597

RTC-57409

IAEENH-849, RTC-55778

See screenshot below:

https://www.fpds.gov/downloads/ApprovedDate_onscreen.png

Note: Currently, these values are saved in applicable FPDS database tables but are not displayed on the screens.