V1.5 SP 5.0



DescriptionStart Date End Date
BETA Installation September 27, 2019September 27, 2019
Government Acceptance Testing October 8, 2019October 10, 2019
Installation in ProductionOctober 25, 2019October 25, 2019

Document Changes

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

SPR Listing

SPR #Enhancement/ProblemSolutionImpact to Users and Integrators

RTC 51862

'Number Of Offers Received' is being populated with a Zero (0) instead of showing a blank. When a Delivery Order or a BPA Call is made against a Single award IDC or BPA the Data Element 'Number Of Offers Received' is being populated with a '0' instead of correctly displaying a null value. A fix will be applied to display a blank in the 'Number of Offers' field.

A data management fix will be applied to ensure a null value is being displayed on the contract action screen as well as reports for records already in FPDS.


IAESAM-693, RTC 51757

Other Transactions Module - extend the Award/IDV PIID rules to Other Transactions (OTs) for DoD only. The following three PIID validation rules will be added to OTs for DOD only:
• The first character of the modification number must be 'A' or 'P'.
• The modification number must be 6 characters in length.
• If the transaction is an initial award of an 'Other Transaction Order', then the PIID must be 13 characters long.

RTC 51260

Assigned locked fields are not being retained when an Award or IDV is updated more than once. This issue is specific to the Data Ownership functionality of FPDS. The Data Ownership functionality of FPDS allows agencies to lock fields, making them read-only. These locked fields are not being retained when the Award or IDV is updated more than once. The status for the data elements will be maintained regardless how many times the data elements are updated. This applies to agencies that have designated certain fields to be locked. No

IAESAM-639, RTC 49385

Change 'Effective Date' to propagate to Modifications from the Base Award (Mod 0) The use case for the 'Effective Date' data element on V1.5 Award and IDV Modifications will be changed to 'Propagate.' The value of Effective Date will populate from the Base (Mod 0) and will no longer be required on modifications.

Values sent for 'Effective Date' on modifications by Contract writing systems or integrators will be ignored.

This change will apply only to V1.5 contracts with a Date Signed on or after October 25, 2019



Updates to the FAADC Delete ATOM Feed The following updates have been made to the FAADC Delete ATOM Feed:

- The removal of the unnecessary ‘deletedType’ flag within the FAADC delete feed
- Updating the root tag of the deleted feed entries to be more accurately labeled ‘<assistance>’
- Resolving an issue where the ‘last modified date’ does not match the FABS report sent date.