Difference between revisions of "Version 1.5 Detail"
From FPDS-NG
| Line 114: | Line 114: | ||
If the user selected the ‘Close Out’ button by mistake, the user will be prompted with a screen that will be shown where the user can confirm their decision to close out the open contract. If the user does not want to close the contact, the ‘No’ button will cancel the Close Out action. | If the user selected the ‘Close Out’ button by mistake, the user will be prompted with a screen that will be shown where the user can confirm their decision to close out the open contract. If the user does not want to close the contact, the ‘No’ button will cancel the Close Out action. | ||
| − | https:// | + | https://fpds.gov/downloads/images/v1.5_image_2.jpg |
| − | https:// | + | https://fpds.gov/downloads/images/v1.5_image_1.jpg |
</td> | </td> | ||
| Line 218: | Line 218: | ||
The values will be system generated and will have the following values for both data elements: | The values will be system generated and will have the following values for both data elements: | ||
| − | https:// | + | https://fpds.gov/downloads/images/v1.5_image_4.jpg |
</td> | </td> | ||
<tr> | <tr> | ||
Revision as of 21:33, 22 March 2017
Schedule
| Description | Start Date | End Date |
|---|---|---|
| BETA Installation | 04/01/2017 | 04/01/2017 |
| Government Acceptance Testing | 05/15/2017 | 05/26/2017 |
| Government Acceptance Retest | 08/14/2017 | 08/18/2017 |
| Installation in Production | 10/01/2017 | 10/01/2017 |
Document Changes
| Documentation | Changes Required |
|---|---|
| XML Specifications | Yes |
| Web Services | Yes |
| Data Dictionary | Yes |
| Use Case Summary | Yes |
| Validation Rules | Yes |
| Reporting | Yes |
| ezSearch | Yes |
| Atom Feeds | Yes |
| Online Help | Yes |
| User Manual | Yes |
Item Listing
| Item# | Enhancements | High Level Description | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
IAESAM-40 |
Add CAGE code as a new data element on the FPDS-NG contract screen. | The CAGE code will be added as a new data element to the FPDS-NG contract screen. The field will be available in the Contractor Information section, via GUI screens and Web Services. | ||||||||||
|
IAESAM-126 |
FAR Case 2014-005 “Consolidation of Contract Requirements” Phase 2 requires Consolidated Contract to be Required on to FSS and GWACs. Previously the use case was "Not Applicable."
Details on Phase l (SP 33), are available at the following URL https://www.fpds.gov/wiki/index.php/V1.4_SP_33.0 | The use case will be changed from "Not Applicable” to “Required” for both FSS and GWACs. The V1.5 Data Dictionary will be updated to reflect this change. |
||||||||||
|
IAESAM-335 |
Allow “Commercial Item Acquisition Procedures” to be entered on a Part 13 BPA Call. |
The use case for Part 13 BPA Calls for “Commercial Item Acquisition Procedures”, will be changed from ‘Not Applicable’ to ‘Required’. |
||||||||||
|
IAESAM-382 |
Update the names for the “Legislative Mandates” data element to comply with the FAR. |
|
||||||||||
|
IAESAM-394 |
A new web service shall be established to allow Contracting Officers to Close Contracts via Business Services with a new API. The new Close Out API will allow users to close out contracts through their interfacing systems. The function will also be available from the contract screen via the web portal and GUI services in V1.5.
Please reference the technical specifications at the url below for more information. https://www.fpds.gov/fpdsng_cms/index.php/en/worksite.html
| New data elements to be display are as follows: ‘Closed Status’, ‘Closed Date’, and ‘Closed By User’.
For exercising this option from the web portal the user will select the Close Out Button. Examples are shown below. If the user selected the ‘Close Out’ button by mistake, the user will be prompted with a screen that will be shown where the user can confirm their decision to close out the open contract. If the user does not want to close the contact, the ‘No’ button will cancel the Close Out action. |
||||||||||
|
IAESAM-414 |
Add 24 blank XML tags to each CAR format for inbound web services. | FPDS-NG shall add the following blank tags:
• 10 Generic String tags NOTE: Future use of the blank tags will be decided by the executive governance working group following the V1.5 implementation. |
||||||||||
|
IAESAM-415 |
In order to give more clarity to the Dollar Values contained it FPDS-NG, the data element “Total Estimated Order Value” was added. Also, the names for “Base and All Options Value” and “Maximum Order Limitation” were changed. | Established a new data element on IDC, FSS and GWACs to distinguish between “Estimated Value of Orders” and “Total Potential Value of Obligations” on the respective IDVs. Changed the name of the data element “Base and All Options Value” to “Base and All Options Value (Total Contract Value)”. Changed the name of data element “Maximum Order Limitation” to “Individual Order / Call Limit”.
|
||||||||||
|
IAESAM-460 |
Four socioeconomic vendor types will be added and displayed on the Business Category section of the FPDS-NG screen. These values and the association validation rules are already in FPDS-NG. The only enhancement is to add them to the screen display. | The screen will be changed to display the following four socioeconomic categories.
• Women-Owned Small Business |
||||||||||
|
IAESAM-462 |
A new Data Element will be added to the Contract Data Section of the FPDS-NG screens for the “Inherently Government Function”. The data for this element was previously collected in the “Description of Requirements” field. | The new data element “Inherently Government Function” will have the following values
• Closely Associated |
||||||||||
|
RTC-31035 |
A new data element labeled “Additional Reporting” will be added to the Legislative Mandates section on the FPDS-NG screens. | The Data Element labeled “Additional Reporting” will have the following list of values.
• Service Contract Inventory NOTE: Currently these are the only values in the list. Multiple Values cannot be selected for "Additional Reporting" when 'None of the above' is selected. |
||||||||||
|
RTC-27665 |
This enhancement is to assist the user community and the public, to be able to distinguish between what the value is on the IDV from the value on an Award for the data elements “Type of Set Aside Source”, and “IDV Number of Offers”. | The new Data Elements “IDV Type of Set Aside”, “Type of Set Aside Source”, “IDV Number of Offers”, “Number of Offers Source”, will be added to all Awards in order to provide clarity as to which values are propagated from the Referenced IDV and which values are selected on the Award.
The values will be system generated and will have the following values for both data elements: |
||||||||||
