V1.4 SP1.0

From FPDS-NG

Schedule

DescriptionStart Date End Date
BETA Installation Monday March 29, 2010Monday March 29, 2010
Functional Qualification TestingTuesday March 30, 2010Thursday April 01, 2010
Installation in ProductionFriday April 09, 2010Friday April 09, 2010

Document Changes

DocumentationChanges Required
XML SpecificationsNo
Web ServicesNo
Data Dictionary Yes
NASA Specific Data DictionaryNo
Use Case SummaryNo
Validation RulesNo
Online HelpYes
Computer-Based TrainingNo
Report ManualNo

SPR Listing

SPR #ProblemSolutionImpact to Users and Integrators
FPDSNG-3613 GSA has requested an ATOM Feed to be provided which can be used by the CWS like eSRS to retrieve contractual data. A new ‘Public Feed’ will be provided which shall display all the data elements in FPDS-NG along with the data element description as listed in the ‘Public Feed Data Elements’ text files in the Appendix section. This ‘Public Feed’ shall not display the element ‘globalParentDUNSNumber’, ‘parentDUNSNumber’ and ‘domesticDUNSNumber’ from the ‘vendorDUNSInformation’ section of the feed. This Public feed is available to all from the ezSearch page. Detail feed is available only upon a request, approved by GSA and shall not be available for all users through ezSearch. The reveal date criteria shall be applicable for the ‘Public Feed’. No
FPDSNG-3614 GSA has requested a change to description of the “Fair Opportunity/Limited Sources” value ‘FOO’ from ‘Follow-on Delivery Order Following Competitive Initial Order’ to ‘Follow-on Action Following Competitive Initial Action’. FPDS-NG shall change the description of ‘Follow-on Delivery Order Following Competitive Initial Order’ to ‘Follow-on Action Following Competitive Initial Action’ and display the new value ‘Follow-on Action Following Competitive Initial Action’ in “Fair Opportunity/Limited Sources” drop down for all versions irrespective of the “Date Signed” value. FPDS-NG shall display the new value ‘Follow-on Action Following Competitive Initial Action’ for all the existing contracts in draft and final status which have the value ‘FOO’ for “Fair Opportunity/Limited Sources”. FPDS-NG shall change the column names in the ‘Exceptions to Fair Opportunity’ Workflow of Competition Based on Obligations Report and shall display the new value ‘Follow-on Action Following Competitive Initial Action’ in Adhoc Reports when “Fair Opportunity/Limited Sources” is chosen as an attribute in the report. The “Short Description” for code ‘FOO’ shall be changed to the new value ‘Follow-on Action Following Competitive Initial Action’ for data element “Fair Opportunity/Limited Sources” (10R) in the V1.2, V1.3 and V1.4 data dictionaries. The description for code ‘FOO’ shall be changed to the new value ‘Follow-on Action Following Competitive Initial Action’ for data element “Fair Opportunity/Limited Sources” in the help file. No
FPDSNG-3615 GSA has requested to prevent the user from entering “Extent Competed” as ‘Competitive Delivery Order’ or ‘Non Competitive Delivery Order’ on V1.2 or V1.3 DO referencing Single Award IDV with pre CLOD date signed.


GSA has requested to stop Civilian users from creating new base Delivery Orders referencing BPAs. DoD users can create new base Version 1.3 Delivery Orders referencing Version 1.3 or lower Civilian BPAs; all other combinations will be stopped.

FPDS-NG shall not allow the values ‘Competitive Delivery Order’ and ‘Non-Competitive Delivery Order’ for “Extent Competed” on DO referencing Single Award IDV with pre CLOD date signed for version 1.2 and 1.3. The new validation rule “If Award Type is a Delivery Order and the Referenced IDV is a Single Award IDV or BOA then "Extent Competed" cannot be selected as ‘Competitive Delivery Order’ or ‘Non-Competitive Delivery Order’.” will be displayed when a ‘isExistingAwardComplete’, ‘isComplete’, ‘Approve’ or ‘Correct’ request is submitted against V1.3 endpoint to validate, approve or correct a DO against Single Award IDV with “Date Signed” as prior to the CLOD and “Extent Competed” as ‘Competitive Delivery Order’ or ‘Non-Competitive Delivery Order’. The same rule is displayed when a user tries to correct an existing V1.2 DO against Single Award IDV or an V1.3 final DO against Single Award IDV with “Date Signed” as prior to the CLOD and “Extent Competed” as ‘Competitive Delivery Order’ or ‘Non-Competitive Delivery Order’ through the web portal.


The existing validation rule “Delivery Task Orders cannot reference a “BPA”.” will be displayed on New and Draft Delivery Orders to prevent creation of new base Delivery Orders referencing BPAs. Creation of new base Delivery Orders referencing BPAs will be allowed only for DoD agencies for Version 1.3 Delivery Orders referencing Civilian V 1.3 or lower BPAs.
No
FPDSHD-67332 GSA has requested to allow the user to provide end date for Funding Office and even though the Contracting Office is still active. FPDS-NG shall suppress the rules REFGOV1C03, REFGOV1C04, REFGOV1C15 and 12049 allow the user to end date the funding office keeping the contracting office active. No
FPDSIRB-162 GSA has requested to update the rule 8N02 to use “Base And Exercised Options Value” instead of “Base and All Options value” on version 1.3 or prior for BPA Calls since “Base and All Options value” is not applicable for BPA Calls. FPDS-NG shall allow the users to create BPA Calls which are bundled contracts by considering the “Base and Exercised Options” instead of “Base and All Options”. FPDS-NG shall display the new validation rule “When the “Base And Exercised Options Value” is less than or equal to $5,500,000, the "Bundled Contract" value must be “Not a Bundled Requirement” when the Base and Exercised Option value is less than $5,500,000 and “Bundled Contract” is selected as any value other than ‘Not a Bundled Requirement’. FPDS-NG also shall suppress existing rule 8N02 using “Base and All Options Value” for version 1.3 or prior (1.2, 1.1, 1.0) BPA Calls. No