V1.5 SP 7.0

From FPDS-NG

Schedule

DescriptionStart Date End Date
BETA Installation June 1, 2020June 1, 2020
Government Acceptance Testing June 9, 2020June 11, 2020
Installation in ProductionJune 26, 2020June 26, 2020

Document Changes

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

SPR Listing

SPR #Enhancement/ProblemSolutionImpact to Users and Integrators

IAESAM-721

The Trade Agreement Report is updated every two years. The new thresholds are being added for Fiscal Years 2020 and 2021. The Trade Agreement Report will be updated with the NAFTA and GPA thresholds for Fiscal years 2020 and 2021. The new thresholds are shown below:

NAFTA
Goods: $25,000
Goods and Services: $83,099
Construction Services: $10,802,884

GPA
Goods and Services: $182,000
Construction Services: $7,008,000

No

IAESAM-726

Apply DAIMS V1.4 reporting changes to FAADC. This item will update the FAADC financial assistance reporting module to be compliant with Treasury issued DAIMS V1.4 reporting changes. Updates to FAADC will include updates to the FABS report to differentiate a new record type for aggregate assistance records, updates to the assistance principle place of performance data to incorporate 'City Wide' codes, and further updates to the FABS report to accurately account for the new 'City Wide' place of performance information. No

IAESAM-731

Apply NDAA 2017 Section 1811 to DoD Funded actions. This item will add a new value in the "Emergency Acquisition" data element to allow the selection for 'Humanitarian and Civic Assistance as Defined in 10 U.S.C. 401(e).' The NDAA 2017 section 1811 expanded the DoD exclusions from small business goals as it relates humanitarian and civic assistance provided in conjunction with military operations. As a result, the current use of the existing 'Emergency Acquisition' drop down list value for 'Humanitarian or Peacekeeping Operations' does not accurately account for the new exclusions.

The new value will provide the ability to further exclude contract actions from future Small Business Goaling Reports and Small Business Achievements Reports.

A validation rule will be introduced to only allow this drop down value to be selected when the Funding Agency is DoD.

Yes

IAESAM-752

Apply maximum character lengths to FPDS hierarchy names and addresses. This item will update the FPDS hierarchy office name and Address Line 1-2 data table to accept data that is longer than the existing maximum length. As a result of data act investigations, it was discovered that there are instances of office name information on existing contract actions that have been truncated in comparison to the name within the DoDAAD. In addition to updating the maximum length for the office within the FPDS database, data management updates will be implemented to ensure the correct, full name is correctly appended to any impacted records in the 'Contracting Office' name and 'Funding Office' name. Additionally, the maximum length for address line 1-2 for the hierarchy office details will be updated to incorporate the appropriate maximum length. No

IAESAM-767

Change the name of the “Effective Date” to “Period of Performance Start Date” This item will update the screen name for the current “Effective Date” data element to rename it to “Period of Performance Start Date”. The reasoning for this change is to make the data element name more understandable for users and interfacing systems. Currently, some systems are mapping this data element to an incorrect effective date field, when it should reflect the accurate period of performance start date for the contract action. The award detail in the Standard Reports will be updated to change “Effective Date” to “Period of Performance Start Date”. No

IAESAM-768

Change the functionality on OTs to allow the “Base and All Options Value (Total Contract)” to be “0". This item will suppress an OT validation rule for the data element 'Base and All Options Value (Total Contract') that prohibits an OT contract action from being finalized with a 'Base and All Options Value (Total Contract') ' of $0. Because there are OT's that exist that are funded completely from non-appropriated funds, there is a business case for allowing the OT contract action to have $0 for the 'Base and All Options Value' data element. Yes

IAESAM-787

The 2020 NDAA Conference Report Section 806 requires that FPDS be updated to collect Lowest Price Technically Acceptable (LPTA) information on award of new contracts and orders. A new data element "Source Selection Process" will be added to FPDS As a result of FAR changes Contracting personnel are required to identify Lowest Price Technically Acceptable awards. Although LPTAs are described in FAR 15.101-2 the option is available for use when you use any parts of the FAR, i.e., 6, 8, 12,13,15).

The new data element “Source Selection Process” will be Required on FSS, GWAC, IDC, PO, DCA, Orders Under FSS/GWAC/Multiple Award IDC, Part 8 BPAs, BPA Calls Under Multiple Award Part 8 BPAs, BPA Calls Under Part 13 BPAs, and Orders Under BOAs.

The value will propagate to orders under single award IDCs and Part 8 BPA Calls under single-award Part 8 BPAs, and to Modifications. The value will be Not Required on Part 13 BPAs and BOAs.

The three drop-down values for the new data element are as follows:

Lowest Price Technically Acceptable (LPTA):
Select this option if contract award used the LPTA source selection process. LPTA is defined in FAR subpart 15.101-2, but select this option if the process was used for competitive procurements conducted in accordance with other subparts (e.g., 8, 12, 13, 16).

Trade-off (TO):
Select this option if contract award used any type of best value tradeoff process using price/cost and non-price/cost factors to determine the successful offeror award. Trade-off is defined in FAR subpart 15.101-1, but select this option if the process was used for competitive procurements conducted in accordance with other subparts (e.g., 8, 12, 13, 16).

Other (O):
Select this option if contract award did not use LPTA or a Trade-off process, to determine the successful offeror (e.g., price-only, sole-source).

A screen shot of the new data element and values is shown below:

Source Selection Process

The two new validation rules are shown below:

"Source Selection Process" must be 'Other' when "Extent Competed" is 'Not Competed', 'Not Available for Competition' or 'Not Competed\Under SAP'.

"Source Selection Process" must be 'Other' when "Fair Opportunity Limited Sources" is 'Follow-on Action Following Competitive Initial Action', 'Minimum Guarantee', 'No Exception - Fair Opportunity given', 'Only One Source - Other ', 'Other Statutory Authority', 'Sole Source', or'Urgency'.

The new data element will be included in the Standard Reports Award Detail.

Yes

RTC-52984

FAADC: Update to no longer accept any R&D Dollar categories when R&D Indicator is ‘NO’. This item will update the FAADC financial assistance reporting module to not allow R&D dollars to be saved on a contract under any circumstances when the Data Element “Research and Development Fund Indicator” is ‘No R&D Funds’.

This will resolve a defect where R&D dollars were previously reported on an assistance award, and the user corrects the 'Research and Development Funds Indicator' to have a 'No’ value. In these instances, the system continues to retain the dollar amounts entered within the R&D funding data elements, when it should be removing the provided dollar amounts. The system will be updated to ensure that if the 'Research and Development Funds Indicator' has a 'No' value selected, any previously entered R&D dollar amounts will be removed.

Yes

RTC-53714

A 'Recipient Change' amendment cannot be finalized in FAADC without having to have a different DUNS number than the previous action. This item will update the FAADC financial assistance reporting module to suppress an existing 'DUNS Number' data element validation rule (FAADC:6E1). The current validation rule requires that the 'DUNS Number' data element cannot be equal to the DUNS number on a previous assistance award with the same FAIN number and the 'Action Type' for the assistance award is 'Recipient Change.' The validation rule will be removed from FAADC. Yes