V1.4 Fast Path



DescriptionStart Date End Date
BETA Installation Monday December 21, 2015Monday January 4, 2016
Government Acceptance Testing Tuesday January 5, 2016Thursday January 7, 2016
Installation in ProductionSaturday January 16, 2016Saturday January 16, 2016

Document Changes

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

SPR Listing

SPR #Enhancement/ProblemSolutionImpact to Users and Integrators
19284 Update the Trade Agreement Report (TAR) with the new thresholds for NAFTA and GPA. Every two years the United States Trade Representative has the authority to change the thresholds in the Trade Agreement Report (TAR) for the North American Free Trade Agreement (NAFTA) and Government Procurement Agreement (GPA) thresholds.

The thresholds for 2016 & 2017 for NAFTA are:

Goods: $25,000

Goods and Services: $77,533

Construction: $10,079,365

The thresholds for 2016 & 2017 for GPA are:

Goods and Services: $191,000

Construction: $7,358,000

15135 “Domestic or Foreign Entity” is currently a required field on all contract modifications. A software fix shall be performed so that the data element, “Domestic or Foreign Entity,” is no longer required on contract modifications. The value of “Domestic or Foreign Entity” shall propagate from the Base record to all subsequent modifications.

The two scenarios which are exceptions to this fix are listed below. The value for “Domestic or Foreign Entity” shall still be required on these modifications.

• Modifications where the “Reason for Modification” selected is ‘Novation Agreement.’

• New Base modifications following a ‘Transfer Action’ modification.

20089 FPDS is incorrectly checking the validity of Product or Service Codes (PSC) 1830 and 1850 on a modification. The validity of the PSC shall not be checked on modifications as the data is propagated from the base document. No
20221 Mandatory rule on the “Modification Number” is firing on the Change PIID Modification when it is the first modification after a Transfer between DoD agencies and from Civilian Agencies to DoD. After the transfer from a civilian agency to DoD, if DoD creates the Change PIID action with an invalid PIID, “Save Draft” fires the pertinent rule, but “Validate” fires the rule that the “Modification Number” is not present. However, the “Modification Number” is present in document

The rules will be modified to fire correctly when Validate is selected on records that have been transferred between Civilian Agency and DoD and transfers within DOD. This is not happening on a Change PIID that has not been transferred.