V1.5 SP 9.0

From FPDS-NG

Revision as of 23:46, 27 April 2021 by WikiSysop (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Schedule

DescriptionStart Date End Date
BETA Implementation May 14, 2021May 14, 2021
Government Acceptance Testing May 24, 2021May 28, 2021
Production Deployment June 5, 2021June 5, 2021

Document Changes

DocumentationChanges Required
XML SpecificationsYes
Web ServicesYes
Data DictionaryYes
NASA Specific Data DictionaryNo
Use Case SummaryNo
Validation RulesYes
ReportingNo
ezSearchYes
Atom FeedsYes
Online HelpYes
User ManualYes

SPR Listing

SPR #Enhancement/ProblemSolutionImpact to Users and Integrators

RTC-56803, RTC-56819, RTC-56811

The Unique Entity Identifier (UEI) will be added to the FPDS screens. The UEI will be added to the FPDS screens directly under the DUNS number data element. An existing generic XML tag (genericString02) will be used to display this new data element within web services. Contract Writing Systems (CWS) that interface with FPDS will not need to re-certify.

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://beta.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.

Yes

RTC-56808

FPDS Atom Feed V1.5.2 Implementation A new version of the FPDS Atom Feeds - V1.5.2 will be created.

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://beta.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://beta.fpds.gov/wiki/index.php/Atom_Feed_Specifications_V_1.5.2

Yes

RTC-58565

FPDS Atom Feed Decommission As part of the implementation of FPDS Atom Feed V1.5.2, all FPDS Atom Feed versions prior to V1.5.2 shall be decommissioned after Service Pack 9 release, on a scheduled decommission timeline.

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.

Yes

RTC-58563

FPDS XML Archives Decommission The XML Archives will be decommissioned.
  • 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.
Yes

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

The Unique Entity Identifier (UEI) and Close Out Function will be added to the FAADC screens. All of the changes outlined in RTC-56803 will also be added to FAADC screens. A new version of FAADC will be created to implement generic tags. There is only one CWS system that interfaces with FAADC, which will have to be re-certified by FPDS Change Management team to ensure that the new data elements can be sent through business services. A new FAADC Atom Feed - V1.1, will be created (see RTC-56816 below for additional details).

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://beta.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://beta.fpds.gov/downloads/cancel_closeout.png

Yes

RTC-56816

FAADC Atom Feed V1.1 Implementation

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://beta.fpds.gov/wiki/index.php/ATOM_Feed_FAQ
2. Tag locations and sample schemas, please visit the FAADC Atom Feed V1.1 Specifications: https://beta.fpds.gov/wiki/index.php/FAADC_Atom_Feed_Specifications_V_1.1

Yes

RTC-56597

Add 24 blank XML tags to each FAADC Assistance Award inbound web services. FAADC shall add the following blank tags:
  • 18 Generic String tags
  • 2 Generic Boolean tags
  • 2 Generic Float tags
  • 2 Generic Integer tags

  • Note: Future use of the blank tags will be decided by the executive governance working group. The CWS will have to be certified to ensure that the new generic tags can be sent.
    Yes

    RTC-57409

    Add 24 blank XML tags to eSRS web services output and eSRS ATOM Feed. Currently, FPDS web services and ATOM Feed utilize and display generic tags. eSRS web services/ATOM Feed does not display generic tags. FPDS shall add the following blank tags to eSRS output:
  • 10 Generic String tags
  • 10 Generic Boolean tags
  • 2 Generic Float tags
  • 2 Generic Integer tags

  • Note: Future use of the blank tags will be decided by the executive governance working group.
    No

    IAEENH-849, RTC-55778

    Display “Approved Date” at the top of FPDS CAR screens. The “Approved Date” and “Approved By” will be displayed on the FPDS Screens in the Transaction Information Section.

    See screenshot below:

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

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

    No

    RTC-52536

    In FAADC, a user can select a Record Type on a Modification that is different from the Record Type of the base document. A new validation rule will be added that will fire when the user creates a modification and selects a Record Type that is different form the Record Type on the base document. No

    RTC-28122

    Agency ID and Administrators fields values are not displayed on System User Account profile from the web portal. This defect will be fixed so the Agency ID and Administrators fields’ values are displayed on any System User Account profile screen. No

    RTC-52664

    FAADC Amendments are being validated as Base records for the isComplete web service. The isComplete web service method will be fixed so that only validation rules applicable to the amendment document fire on the output. No

    RTC-58401

    Validation Rule OT2B02 “Period of Performance Start Date cannot be earlier than the Date Signed on the base document” is incorrectly firing on ‘Approve’ for an OT modification to an IDV. Change the code that is causing the Validation rule OT2B02 to fire incorrectly on ‘Approve’ for a Modification to an OT IDV. The rule is correctly firing on OT Awards. It is also firing correctly on ‘Validate’. No

    RTC-58490

    Authenticated Atom Feed System Account privileges will be separated between FAADC and DoD Atom feeds. Enhancement to separate DoD and FAADC System Account privileges. This will enable for Authenticated DoD Atom Feed users to have access to either DoD Atom Feed/FAADC Atom Feed or access to both feeds, dependent on privileges enabled for the user.

    Any user with existing Authenticated Atom Feed access can continue accessing DoD feeds but will need to update their privileges to gain access to FAADC Atom Feeds.

    No