Release Notes
Federal Procurement Data System Version: 1.1
Software Service Pack Number: 8.0
Internal Build: 144
Installation Date: December 07, 2003, 10:00 p.m. EST
FINAL
Prepared by:
Global Computer Enterprises, Inc.
10780 Parkridge Boulevard, Suite 300
Reston, VA 20191
December 9, 2003
FPDS-NG Release Notes
Table of Contents
Section Page
1 Introduction 1
1.1 Overview 1
1.2 Documentation 1
1.3 Impact to Users 1
1.4 Impact to Integrators 1
1.5 FPDS-NG Updates and Notices 1
1.6 Help Desk. 1
1.7 Reports. 1
2 Change Descriptions 2
Software Problem Report ID 2
Description 2
Impact on Users 2
Impact on Integrators 2
3 Screen Shots 5
Table of Figures
Figure Page
Figure 1 Action Obligation Screen Shot Before 5
Figure 2 Action Obligation Screen Shot After 5
Figure 3 CCR Exception Screen Shot Before 6
Figure 4 CCR Exception Screen Shot After 6
ii
FPDS-NG Release Notes
1 Introduction
1.1 Overview
This document describes the enhancements and changes made to the FPDS-NG system. These changes are included in the software release described below. The Software Problem Report (SPR) tracking number is included for each change.
1.2 Documentation
Changes to documentation required by this service pack:
· XML Specifications – see version 1.1 notes
· Web Services – see WSDL notes
· Data Dictionary – added CCR exception and vendor data not in the dictionary
· Use Case Summary – added CCR exception data to the use cases
· Validation Rules – added rules for report generation to check for wildcard search and send warnings to the user
· Batch Format – added fields to support CCR exception and IDV obligation amount
1.3 Impact to Users
The impact to the user is addressed for each change made to the system.
1.4 Impact to Integrators
The impact to the integrators is addressed for each change made to the system.
1.5 FPDS-NG Updates and Notices
All updates and notices are posted to the FPDS-NG Web site at http://www.fpdsng.com/downloads.html. The most recent updates and anticipated changes are posted at http://www.fpds-ng.com/status.html.
1.6 Help Desk.
If you have questions about the FPDS-NG system, please call the FPDS-NG Help Desk at (703) 390-5360 or (866) 490-3737. You may FAX us at (703) 390-5365, or visit the FPDS-NG Web Site at https://www.fpds.gov.
1.7 Reports.
The following Reports are ready for your review:
· Performance Statistics for Contracting Office
· Individual Contract Award Accepted – Key Details
· Individual Contract Award High Dollars – Key Details
· Register Report
The Reports are described in an associated document called FPDS-NG Reports, which will be posted to the FPDS-NG Web site.
2 Change Descriptions
Software Problem Report ID / Description / Impact on Users / Impact on Integrators /SPR 821 / Previous releases did not display Action Obligation amounts as shown in Figure 1. Release 8 adds the data element for Action Obligations to IDVs as shown in Figure2. / Users will be able to enter Action Obligation amounts for IDVs. / Integrators will be able to enter Action Obligation amounts for IDVs.
SPR 880 / Enhanced the Correct functionality on the base document to apply changes to all associated Modifications. This applies only to changes of data that cannot be changed on a modification. / Improves accuracy of data. / Improves accuracy of data.
SPR 881 / Enhanced the Correct functionality to apply changes to all Awards referencing a Corrected IDV.
Some data elements on the referenced IDV are used to populate data on the associated award (i.e. Delivery/Task Order or BPA Call). This data is not editable on the award. When a user corrects one of these data elements on the referenced IDV, the data will be changed on all awards referencing that IDV. / Improves accuracy of data. / Improves accuracy of data.
SPR 1916 / Some of the amounts in production are incorrect. A few still show they were multiplied by 1000 twice / Improves accuracy of data. / Improves accuracy of data.
SPR 1931 / Added ability to create Modifications when no base document is present.
SF281 summary data will not be supported after FY 2004. Documents reported using the SF281 summary data do not have a base document in FPDS-NG. The original requirements stated that the base document must exist before a modification can be created. This change will automatically create the base and the modification for the user when no base is found in FPDS-NG. / Users are able to create and approve modifications without having to input the base document. / Integrating systems will be able to create and approve modifications without having to input the base contract first.
SPR 2001 / Improved Contracting Office Code lookup on Advanced Search screens by allowing the user to specify an Agency ID. / Improved search functionality. / None.
SPR 2004 / Fixed bug with CCR vendor view that was preventing the save of some vendors from CCR. / Users are able to save documents for any CCR vendor. / Integrating systems are able to save documents for any CCR vendor.
SPR 2015 / Added validations to report criteria to prevent searches using only wildcards. / Prevents searches that take along time and informs the user that more selection criteria is required. / None.
SPR 2017 / Extended PIID field for Referenced IDV lookup screen to display all characters of PIID. / Users can now see more of the referenced PIID. / None.
SPR 2028 / Completed changes to migrate documents that failed the initial migration because reference data was missing. The data migrated from the legacy system did not have these integrity constraints but FPDS-NG has instituted many integrity constraints.
GCE added the reference data for the records and migrated over 95 % of the failed records. / Users now will have access to documents that had not migrated successfully from the legacy system. / Integrating systems will now will have access to documents that had not migrated successfully from the legacy system.
SPR 2031 / Modified FPDS-NG to include CCR enhancements now allowed by the FAR. In previous releases, the CCR Exception data element was not included as shown in Figure 3. The new data element for CCR Exception is added as shown in Figure 4. Enhancements include:
· CCR Exception field on the award and IDV screen above the contractor section
· Opened up vendor section for user input when a CCR exception is selected
· Added validation rules for the CCR Exception
· Added Batch processing for CCR exception
· Added web services processing for CCR exception
· Added error processing for CCR exceptions.
Additional validation rules include:
· DUNS number cannot be in CCR
· DUNS number cannot be bogus such as 123456789, 111111111, etc. / Users are able to identify create and approve procurements for vendors that are not registered in CCR. / Integrating systems will be able to create and approve procurements for vendors not registered in CCR.
SPR 2033 / Added the ability to delete Errored Out documents from the screen. The delete functionality on the Award and IDV screen would not allow users to delete Errored Out records, only Draft records. The users had to:
Fix the record to make it a valid Draft
Save document as Draft
Delete the Draft document.
SP 8 adds the delete functionality for Errored Out records without having to save it as draft. / Users can now delete Errored Out Awards and IDVs without having to make them a valid Draft. / None.
SPR 2039 / Country and City are not showing up as required data elements (orange) nor errored (red) after validation, but they are required to Validate and Approve. These should also be mandatory for Awards. / Improves Graphic User Interface. / None.
SPR 2048 / Changed the XSD to allow for negative confirmation numbers. / None. / Corrects migration errors related to restricting negative numbers.
SPR 2050 / For batch users, award web services for Modifications were updated to add a Performance Based Service Contract tag. / Performance Based Service Contracts are not handled in the batches. / Corrects batch upload of Performance Based Service Contract Awards.
SPR 2054 / Implement changes for Reports / Improved Reporting functionality. / Improved Reporting functionality.
SPR 2059 / When beta users were selecting a CCR Exception, the screen read: "Competition Info Selection" instead of something more appropriate like "CCR Exception Selection". Also, the Doc Type and Doc SubType fields at the bottom are not necessary and just confuse the user as to their purpose. / Improved usability of the Graphic User Interface. / Improved usability of the Graphic User Interface.
SPR 2066 / When beta users were adding Modifications to Awards and IDVs using CCR Exceptions, the values could not be altered because they were filled from the base regardless of what the user entered on the screen. This was confusing for the users. The user interface was redesigned to eliminate this confusion. / Improved usability of the Graphic User Interface for CCR Exceptions. / Improved usability of the Graphic User Interface for CCR Exceptions.
3 Screen Shots
For SPR 821, refer to Figure 1 and Figure 2 below. Previous releases do not allow Action Obligation amounts on IDVs.
Figure 1 Action Obligation Screen Shot Before
Release 8 adds the data element for action obligations for IDVs
Figure 2 Action Obligation Screen Shot After
For SPR 2031, refer to Figure 3 and Figure 4 below. Previous releases do not allow CCR exceptions.
Figure 3 CCR Exception Screen Shot Before
Release 8 allows CCR exceptions.
Figure 4 CCR Exception Screen Shot After
2