V1.5 SP 4.0

From FPDS-NG

Schedule

DescriptionStart Date End Date
BETA Installation June 14, 2019June 14, 2019
Government Acceptance Testing June 18, 2019June 20, 2019
Installation in ProductionJune 28, 2019June 28, 2019

Document Changes

DocumentationChanges Required
XML SpecificationsNo
Web ServicesNo
Data DictionaryYes
NASA Specific Data DictionaryNo
Use Case SummaryYes
Validation RulesYes
ReportingNo
ezSearchYes
Atom FeedsYes
Online HelpYes
User ManualYes

SPR Listing

SPR #Enhancement/ProblemSolutionImpact to Users and Integrators

IAESAM-588, RTC-47866

The "Treasury Account Symbol" (TAS) fields are no longer required and can be disabled. The following Treasury Account Symbol (TAS) data elements will be disabled for data entry on all V1.5 Award, IDV, OT, and NASA contract screens (Data Element number in parenthesis):
• Treasury Account Symbol Agency Identifier ('6SC')
• Main Account Code ('6SG')
• Sub Account Code ('6SH')
• Initiative ('6SI')

This change will be effective June 28, 2019 based on the Prepared Date of the Award/IDV. Any newly created contract action will display the TAS fields as grayed out and disabled from data entry.

Contract actions that have already reported Treasury Account Symbol may still be corrected.

No impact to Contract Writing Systems

Contract Writing Systems (CWS) which currently send TAS data elements will not be prevented from creating, validating, and approving contract actions if they continue to send TAS data elements.

No

IAESAM-589,RTC-47873

FPDS Version 1.5 introduced the "Inherently Governmental Functions" (IGF) data element which eliminated the need for inputting these values in the "Description of Requirement" field. However, users are still entering these values in "Description of Requirement." A new validation rule will display when a user enters any of the valid IGF values below in "Description of Requirement."
1. IGF::CL::IGF
2. IGF::CT::IGF
3. IGF::OT::IGF
4. IGF::CL,CT::IGF or IGF::CT,CL::IGF

6M19: "Description of Requirement" must not contain IGF XML Tags. Please use the Inherently Governmental Function field.

No

IAESAM-604 and 606 RTC-47664 and 47665

IAESAM-604: Implement the Uniform PIID Structure for DoD.

IAESAM-606: With the implementation of the Uniform PIID Structure, deprecate PIID rules that only apply to DoD.

IAESAM-604:

The Uniform PIID Structure implemented for Civilian Agencies will now apply to DoD:

• Positions 1 through 6 will continue to be required to match the Contracting Office ID (DoDAAC).
• Positions 7 through 8 will continue to be required to match the Fiscal Year of the Date Signed.
• Position 9 will continue to designate the type of instrument.
• Positions 10 through 13 will be assigned by the Agency.

The minimum PIID length is 13 characters and the maximum PIID length is 17 characters.

The new PIID validation rules for DoD will be effective June 28, 2019.

IAESAM-606: The following PIID validation rules that only apply to DoD will be deprecated: '1A2','DoD1A04:A','DoD1A04:I','DoD1A07:I','DoD1A09A,'DoD1A09I','DoD1A19','DoD1A21','DoD1A22','DoD1A23:A','DoD1A26','DoD1A33A','DoD1A33I','DoD1A36','DoD1A37','DoD1A40:A','DoD1A41:A','DoD1B7:A','DoD1B7:I','DoD1B8'

Yes

IAESAM-618, RTC-47896

The “Description of Requirement” data element is an open free text field with a maximum of 4,000 alpha-numeric characters. The size of this field invites copying and pasting of sizeable portions of a performance work statement or statement of work rather than thoughtfully including just a brief description of what is being procured (which is its purpose). To increase the quality of data in the "Description of Requirement” field, the following validation rule will be established:

6M20: The maximum length of “Description of Requirement” must be no more than 250 characters.

The new rule will apply to Base records created 6/28/2019 or later. The rule will also apply to Modifications against Base records that were created 6/28/2019 or later. The rule will not apply to Modifications of existing records whose Base was created prior to 6/28/2019.

Records existing prior to 6/28/2019 can be corrected and the Description of Requirement of those records may exceed 250 characters.

Yes

IAESAM-626, RTC-49381

There are four Procurement Committee for e-Government (PCE) changes approved for Product and Services Codes (PSC).

1) The current PSC, ‘D305,’: IT AND TELECOM - TELEPROCESSING, TIMESHARE, AND CLOUD COMPUTING, shall be end-dated on 05/19/2019.
2) A new PSC, ‘D305,’ will be added with the following description, effective 5/20/2019: “IT AND TELECOM – TELEPROCESSING, TIMESHARE, CLOUD COMPUTING AND HIGH PERFORMANCE COMPUTING”.
3) A new code ‘R616’ will be created with a start-date of 05/20/2019.

Code: R616
Description: SUPPORT – ADMINISTRATIVE: PHYSICAL RECORDS MANAGEMENT SERVICES.

4) A new code ‘R617’ will be created with a start-date of 05/20/2019.

Code: R617
Description: SUPPORT – ADMINISTRATIVE: ELECTRONIC RECORDS MANAGEMENT SERVICES
No

IAESAM-638, RTC-49384

The 2018 NDAA Section 886 requires that DoD collect the data in FPDS necessary to determine the length of time between initial issuance of a solicitation and the date an award was made. FPDS currently collects the solicitation number; but not the date the solicitation was issued. The “Solicitation Date” was applied for DoD only on June 28, 2018. This same requirement will now be applied to Civilian Agencies.


The existing DoD-only validation rule will now be applied to Civilian Agencies. “Solicitation Date” is an optional field that is only required when the following validation rules are met:

DOD2H02: The “Solicitation Date” is required when “Solicitation Procedures” is other than ‘Simplified Acquisition’ and “Base and All Options Value (Total Contract Value)” is greater than $250,000.

DOD2H03: The “Solicitation Date” is required when “Solicitation Procedures” on the Referenced IDV is other than ‘Simplified Acquisition’ and “Base and All Options Value (Total Contract Value)” is greater than $250,000.

The rules will be effective starting June 28, 2019 for Civilian agencies.

As part of this update, the use case for "Solicitation Date" will be changed from N/A to Optional for FSS and GWAC contracts.

No

IAESAM-648, RTC-49386

The data element “Contingency, Humanitarian, or Peacekeeping Operation” currently does not provide much context or instruction for the user and the name does not specifically tie the field to the part of the FAR it supports. The data element shall be renamed to “Emergency Acquisition” to tie it directly to FAR part 18. A validation rule will be added to prevent users from entering a value of ‘Not Applicable’ when the value of “National Interest Action” is other than ‘NONE.’

6H02: The "National Interest Action" must be ‘None’ when the "Emergency Acquisition" is ‘Not Applicable.'

A new value, 'Presidential issued emergency declaration, or a major disaster declaration,' will be added to "Emergency Acquisition."

No

IAESAM-660, 661, 662, 663 and 664 RTC-49528, 49529, 49530, 49531 and 49532

The tickets outlined in this entry have been grouped together because they all relate to changes to the 'Other Transaction' contract action forms

IAESAM-660, 661, 662 and 663:
The following new data elements are being updated or added to Other Transaction records (OT): “Fiscal Year,” “Type of Agreement,” “For Profit,” “NotforProfit,” Educational Categories, and “Solicitation Date.”

IAESAM-660: System generating this field based on the Date Signed will make this consistent with the FPDS.
IAESAM-661: Statutes have broadened for Other Transactions for Prototypes applicability to allow for prototype-to- production use.
IAESAM-662: OTs have the need for socioeconomic information when a Vendor DUNs has Profit,” “NotforProfit,” and/or Educational organization credit.
IAESAM-663: There is congressional interest on whether the PALT differs between contracts and other transactions. The solicitation date is being added in order to determine this.
IAESAM-664: The “Funding Agency ID” and “Funding Office ID” will be changed from ‘Optional’ to ‘Required’ for OT IDVs. This makes OTs consistent with FPDS.

IAESAM-660:
“Fiscal Year” will now be system-generated based on the date signed of the action.
Existing validation rules for “Fiscal Year” will no longer apply. A Data Management fix will be done to all OT actions to convert them to the appropriate “Fiscal Year” based on the Date Signed of the action.

IAESAM-661:
“Type of Agreement” will now have two values in the drop-down menu:
https://www.fpds.gov/downloads/images/toa_dropdown.png

IAESAM-662:
When a DUNS number is entered for a “For Profit,” “NotforProfit,” and/or Educational organization, the appropriate categories will be displayed on the contract screen.
Below is an example of a DUNs that is a “Non-Profit Organization” and an “Educational Institution.”
https://www.fpds.gov/downloads/images/not_for_profit_appears.png

IAESAM-663:
“Solicitation Date” will be added above “Fiscal Year.”
All “Solicitation Date” existing validation rules will now fire for OTs, except for the following.

DOD2H02: The “Solicitation Date” is required when “Solicitation Procedures” is other than ‘Simplified Acquisition’ and “Base and All Options Value (Total Contract Value)” is greater than $250,000.
DOD2H03: The “Solicitation Date” is required when “Solicitation Procedures” on the Referenced IDV is other than ‘Simplified Acquisition’ and “Base and All Options Value (Total Contract Value)” is greater than $250,000.

New Validation Rule to be added:

The “Solicitation Date” is required when the“Base and All Options Value (Total Contract Value)” is greater than $250,000 on a Base Modification (0).

IAESAM-664:
The “Funding Agency ID” and “Funding Office ID” will be changed from ‘Optional’ to ‘Required’ for OT IDVs.

Current Screen
https://www.fpds.gov/downloads/images/funding_office_optional.png

Future Screen
https://www.fpds.gov/downloads/images/funding_office_required.png

All applicable validation rules that fire for Funding Agency ID and Funding Office ID will apply.

No