V1.5 SP 9.0
From FPDS-NG
Schedule
| Description | Start Date | End Date |
|---|---|---|
| BETA Implementation | TBD | TBD |
| Government Acceptance Testing | TBD | TBD |
| Production Deployment | TBD | TBD |
| FPDS V1.5 Service Pack 9 implementation schedule is currently to-be-determined. Once implementation dates are finalized, the release notes will be updated to provide additional information. |
|---|
Document Changes
| Documentation | Changes Required |
|---|---|
| XML Specifications | Yes |
| Web Services | Yes |
| Data Dictionary | Yes |
| NASA Specific Data Dictionary | No |
| Use Case Summary | No |
| Validation Rules | Yes |
| Reporting | No |
| ezSearch | Yes |
| Atom Feeds | Yes |
| Online Help | Yes |
| User Manual | Yes |
SPR Listing
| SPR # | Enhancement/Problem | Solution | Impact to Users and Integrators |
|---|---|---|---|
|
RTC-56803, RTC-56819, RTC-56811 |
The Unique Entity Identifier (UEI) will be added to the FPDS screens. | FPDS UEI implementation updates are forthcoming. | No |
|
IAEENH-727, 55772 RTC-56595, 56596 |
The Unique Entity Identifier (UEI) and Close Out Function will be added to the FAADC screens. | FPDS UEI implementation updates are forthcoming.
Additionally, 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,” and “Closed By.” For exercising this option from the web portal, the user will select the “Close Out” Button. Examples are shown 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 that will be shown 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. |
Yes |
|
RTC-56597 |
Add 24 blank XML tags to each FAADC Assistance Award inbound web services. | FPDS shall add the following blank tags:
|
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. However, eSRS web services/ATOM Feed does not display generic tags. FPDS shall add the following blank tags to eSRS output:
|
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 |
|
IAEREQ-3348, RTC-56706 |
“Contracting Officer’s Business Size Selection” is not being saved on a Novation Agreement. | This item will resolve a defect for ‘Novation Agreement’ modifications, where the DUNS is unchanged from the base Contract Action Report, and the user selects a different value for the data element “Contracting Officer's Business Size Selection.” The new selected value is not retained when saving the modification. This defect is only present on Awards and is not present on IDV Contract Action Reports. | No |
|
RTC-56838 |
Other Transaction Awards are omitting the “Congressional District Place of Performance” field when using the Print function. | This item will resolve a defect where the selected value for data element “Congressional District Place of Performance” is not displaying when printing Other Transaction Awards. | No |
|
RTC-56501 |
Part 13 BPA is not retaining the correct DUNS number for a Novation Agreement when the Date Signed is changed on a non-vendor modification. | This item will resolve a defect where the DUNS number on a 'Novation Agreement' modification reverts back to the original/base DUNS number. This occurs only when a non-vendor modification is corrected with a Date Signed between the Novation Agreement document and the base document. | No |
|
RTC-57378 |
IDV Modification records signed after a ‘Novation Agreement’ modification do not retain the correct “Subcontract Plan” value. | This item will resolve a defect where the value for “Subcontract Plan” does not propagate to subsequent modifications that are signed after a ‘Novation Agreement’ modification. This occurs only when the ‘Novation Agreement’ modification is corrected, the DUNS number is unchanged, and the user updates the value for “Subcontract Plan.” A data management update will be performed to correct existing records affected by this defect. | No |
|
RTC-56499 |
“Simplified Procedures for Certain Commercial Items” is grayed out on a Delivery Order (DO) against a Basic Order Agreement (BOA). | This item will resolve a defect where the required data element “Simplified Procedures for Certain Commercial Items” is closed on a DO against BOA. |
No |
|
RTC-48831 |
“Subcontract Plan” retention on a Part 13 BPA Call. | This item will resolve a defect where the data element “Subcontract Plan” value is not being retained on a Part 13 BPA Call. |
No |
|
RTC-46829 |
“Additional Reporting” is unavailable for selection when “SAM Exception” is selected. | This item will resolve a defect where the data element “Additional Reporting” is being closed when a user selects a value for the data element “SAM Exception.” |
No |
|
IAESAM-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 |
