V1.4 SP12.0
From FPDS-NG
Schedule
Description | Start Date | End Date |
---|---|---|
BETA Installation | Thursday 9/15/2011 | Friday 9/16/2011 |
Functional Qualification Testing | Monday 9/19/2011 | Thursday 9/22/2011 |
Re-test (if needed) | Tuesday 9/27/2011 | Tuesday 9/27/2011 |
Installation in Production | Friday 10/07/2011 | Friday 10/07/2011 |
Document Changes
Documentation | Changes Required |
---|---|
XML Specifications | No |
Web Services | No |
Data Dictionary | Maybe |
NASA Specific Data Dictionary | No |
Use Case Summary | Maybe |
Validation Rules | Yes |
Online Help | No |
Computer-Based Training | No |
Report Manual | No |
SPR Listing
SPR # | Problem | Solution | Impact to Users and Integrators |
---|---|---|---|
FPDSHD-72202, 83129, 86488 | The “Place of Manufacture” value, ‘Mfg Outside the U.S. - Qualifying Country (DoD Only)’ indicates the following:
1. Contracting Agency is DoD 2. Country of Product or Service Origin is one of the qualifying countries as mentioned above 3. PSC Codes allowed are 1000-9999, with an exception of 5510, 87**, 88**, 9410, 9430, 9440, 9610, 9620 or 9630 However, the following discrepancies have been noticed: 1. Currently, the “Buy American Act Place of Manufacture” report does not consider the following in the calculation of data for the column “Mfg Outside the U.S. - Qualifying Country (DoD Funds Only)”: a. the value of “Country of Product or Service Origin” b. DoD as the Contracting Agency Hence, for this column, “Country of Product or Service Origin’ could be any country and the contract could be civilian, as long as the value for “Place of Manufacture” is ‘L’ (Mfg Outside the U.S. - Qualifying Country (DoD Only)). 2. Additionally, FPDS-NG does not have validation rules to restrict selection of only those qualifying countries as “Country of Product or Service Origin” when “Place of Manufacture” is ‘Mfg Outside the U.S. - Qualifying Country (DoD Only)’. 3. Also, al though the value reads as ‘Mfg Outside the U.S. - Qualifying Country (DoD Only), there is no validation rule in FPDS-NG to restrict civilian users from selecting this value. 4. Finally, the validation rule 9H04 (Place of Manufacture can not be 'Mfg in U.S.', 'Mfg outside U.S. - Use outside the U.S.', 'Mfg outside U.S. - Resale', 'Mfg outside U.S. - Trade Agreements', 'Mfg outside U.S. - Commercial information technology', 'Mfg outside U.S - Public interest Determination', 'Mfg outside U.S. - Domestic non-availability', 'Mfg outside U.S. - Unreasonable cost' or 'Mfg outside U.S. - Qualifying country (DOD only)' when the 'PSC Code' is not '1000-9999', with an exception of the values: 5510, 87**, 88**, 9410, 9430, 9440, 9610, 9620 or 9630.) that ensures selection of only certain values for the PSC Code was implemented in mid 2008. So there are documents that have one of these values for “Place of Manufacture” and with an invalid PSC Code, bases signed prior to this rule or modifications against the bases that did not have this rule applied.
|
For the report fix:
The “Buy American Act Place of Manufacture” report shall be fixed such that the column, ‘Mfg Outside the U.S. - Qualifying Country (DoD Funds Only)’ shall consider only the following documents: Contracting Agency ID belongs to DoD AND "Place of Manufacture" = ‘L’ AND "PSC Code" between 1000 and 9999 (both values inclusive, but excluding 5510, 87**, 88**, 9410, 9430, 9440, 9610, 9620 or 9630) AND "Country of Product or Service Origin" is one of the following qualifying countries: o Australia o Austria o Belgium o Canada o Denmark o Egypt o Federal Republic of Germany o Finland o France o Greece o Israel o Italy o Luxembourg o Netherlands o Norway o Portugal o Spain o Sweden o Switzerland o Turkey o United Kingdom of Great Britain and Northern Ireland |
No |
FPDSPMOS-69 | Currently FPDS-NG determines “Reveal Date” as ‘Date Signed + 90 days’ for all the DoD documents so neither the civilian agencies nor the public users can access them.
As per the subject Change Request (CR), any DoD document that is funded by civilian agencies could be accessed by any user just like a civilian document could be accessed.
|
1. New DoD final documents that are funded by civilian agencies shall be accessed by the civilian agencies and the public users, as soon as the documents are reported to FPDS-NG.
Note: These documents will have a non-DoD Funding Agency and Funding Office. 2. Civilian agencies shall be able to award Orders (Delivery/Task Orders and BPA Calls) against the above documents that are IDVs. 3. The above documents shall be transferred to the civilian agencies, if need be. 4. Correction to the Funding Agency and the Funding Office as DoD values on the above documents shall qualify them to be categorized under the ‘Date Signed + 90 day’ condition. 5. “Reveal Date” condition shall continue to apply for the new DoD final documents that are funded by DoD. Such documents shall continue to be non-accessible by the civilian agencies and the public users, as soon as the documents are reported to FPDS-NG. Note: These documents will have a DoD Funding Agency and Funding Office. 6. New DoD draft documents, irrespective of who funded them, shall not be accessed by the civilian agencies and the public users. 7. Existing DoD final documents that are funded by civilian agencies shall be accessed by the civilian agencies and the public users. Note: These documents will have a non-DoD Funding Agency and Funding Office. Note: Existing Final Awards that currently have Reveal Date marked are 545. Existing Final IDVs that currently have Reveal Date marked are 14. 8. Civilian agencies shall be able to award Orders (Delivery/Task Orders and BPA Calls) against the above documents that are IDVs. 9. The above documents shall be transferred to the civilian agencies, if need be. 10. Correction to the Funding Agency and the Funding Office as DoD values on the above documents shall again qualify them to be categorized under the ‘Date Signed + 90 day’ condition. 11. “Reveal Date” condition shall continue to apply for the existing DoD final documents that are funded by DoD. Such documents shall continue to be non-accessible by the civilian agencies and the public users, as soon as the documents are reported to FPDS-NG. Note: These documents will have a DoD Funding Agency and Funding Office. 12. Existing DoD draft documents, irrespective of who funded them, shall not be accessed by the civilian agencies and the public users. 13. Standard Reports and Adhoc Reports, when executed by civilian agencies or the public users, shall retrieve the DoD (final) documents that are funded by civilian agencies. 14. BI Views, when executed by civilian agencies shall retrieve the DoD (final) documents that are funded by civilian agencies. 15. ezSearch, when searched by civilian agencies or the public users, shall retrieve the DoD (final) documents that are funded by civilian agencies. 16. ICD, when searched by civilian agencies or the public users shall retrieve the DoD (final) documents that are funded by civilian agencies. 17. Public Atom Feed shall retrieve the DoD (final) documents that are funded by civilian agencies. 18. Detail Atom Feed shall retrieve the DoD (final) documents that are funded by civilian agencies. 19. DoD Atom Feed shall continue to behave as is. |
No |
FPDSHD-60803 | It has been reported that the “Rerepresentation of Eligible Actions Report” is displaying the modification documents in the Award Detail on contrary to what the Appendix states. Appendix is correct as it matches with the finalized requirements for this report.
|
1. Rerepresentation Eligible Actions Report” shall count only the base contractual family eligible for Rerepresentation instead of sum of base or number of Mods in the Summary Report.
2. “Rerepresentation Eligible Actions Report” shall remove Modification Number from the drill down path and thus the report cannot be drilled down to Modification Number. 3. “Rerepresentation Eligible Actions Report” shall remove Modification Number column from the Award Detail. 4. The preview shall be updated to remove the “Modification Number” from the Award Detail. |
No |
FPDSHD-68472-73584-73963 | The “Buying Through Government Acquisition Vehicles Report” does not consider the “Contracting Office ID” when it is selected in the search criteria. Additionally, this report includes NASA Specific Awards.
|
The following changes have been suggested for the “Buying Through Government Acquisition Vehicles Report”:
1. It shall consider “Contracting Office ID” that is selected as one of the search criteria filters. 2. It shall exclude NASA Specific Awards (Grant for Research, Training Grant, Cooperative Agreement, Intragovernmental and Funded Space Act Agreement). |
No |
FPDSHD-77589 | Issue for the civilian agencies: It has been reported that the Agency Administrator for the agency, 1400 is not able to execute the “Contracting Office” report for the entire 1400 and is able to get data only for 1422.
|
YET TO BE FINALIZED | No |
FPDSHD-82179 | It has been reported that contracts like HSFLCH09J00142 (P00001) with current Action Obligation/Ultimate Contract Value as de-obligation, $12,652.00 is not included in the “Performance Based Acquisition” report, al though the cumulative dollars are $52,348 and the contract satisfies the PBSA inclusions.
Currently, “Performance Based Acquisition” report considers contracts only when the Action Obligation or Ultimate Contract Value on each of the contracts (in the family) is greater than $25,000. In other words, the contracts whose current Action Obligation or Ultimate Contract Value is greater than $25,000 are considered in the report.
|
1. “Performance Based Acquisition” report shall consider the cumulative “Action Obligation” or “Base and All Options Value” as greater than $25,000 on the contracts, as against the current “Action Obligation” or “Base and All Options Value” as greater than $25,000.
Note: Current exclusions continue to apply. 2. The Award Detail for “Performance Based Acquisition” report shall observe the following logic in determining the document (in the contractual family) to be displayed: 1. If the report is executed for the Date range that matches with the “Date Signed” on the base document, then base document shall be displayed. 2. If the report is executed for the Date range that matches with the “Date Signed’ on a particular modification document, then the respective modification shall be displayed. 3. If the report is executed for the Date range that matches with the “Date Signed” on more than one modification, then latest modification shall be displayed 4. If the report is executed for the Date range that matches with the “Date Signed” of the entire contractual family, then the latest modification shall be displayed. Latest Modification: Document with the latest “Date Signed” if the “Date Signed” is unique or document with the latest “Prepared Date” if two documents have the same “Date Signed”. Note: If the cumulative numbers qualify a contractual family to be eligible to be displayed in the “Performance Based Acquisition” report, it is redundant to display the whole family of base and the modifications. 3. Appendix changes shall be done accordingly. |
No |
FPDSHD-85385 | It has been reported that the following rule is firing on the V 1.3 BPA Calls when they are funded by civilian agencies and have propagated the “Consolidated Contract” as ‘Yes’ from the referenced IDV.
8P01- If "Funding Agency" is not DoD, then "Consolidated Contract" must be "No".
|
FPDS-NG shall not display the Validation Rule, 8P01 (If "Funding Agency" is not DoD, then "Consolidated Contract" must be "No") on V 1.3 and V 1.4 BPA Calls. | No |
FPDSHD-86105-86681-81258-84615 | For Extent Competed: When an existing V 1.0/1.1 Delivery/Task Order against a Multiple Award IDV is corrected using the V 1.4 service by sending the following tags, the Error code 4004 (“The value "CDO" for Data Element "Extent Competed" is invalid.) is displayed:
i. Extent Competed = A ii. Solicitation Procedures = MAFO iii. Type of Set Aside = NONE iv. Evaluated Preference = NONE v. Number of Offers = 2 For Local Area Set Aside: 1. When an existing V 1.2 document (signed on 07/30/2008) is corrected using the V 1.4 service, the validation rule, 10C20 (If "Other than Full and Open Competition" is 'Authorized by Statute' or 'SAP Non-Competition', then "Local Area Set Aside" must be 'No'.) displayed correctly. However when LASA is set to ‘No’ or ‘N’, the value is not saved. For Commercial Item Procedures (CIAP): 1. V 1.2 documents that have “Commercial Item Test Program”(CITP) = Yes (Y) when corrected using the V 1.4 service with the values of CIAP as A, B, C or D display the following error message: <ns1:errorCode>10J01V12</ns1:errorCode> <ns1:errorMessage>If the "Commercial Item Test Program" is "Yes" then "Commercial Item Acquisition Procedures must be "Yes".</ns1:errorMessage> 2. V 1.4 ‘Create’ with CIAP as ‘N’ or any invalid value displays a System Error.
|
YET TO BE FINALIZED | No |
FPDSHD-64205 | 1. BSDF is being returned in the XML in Data Archives for “Commercial Item Test Program” and “Local Area Set Aside” in Version 1.3 in Archives.
2. BSDF is returned for the data element “Commercial Item Test Program” through Version 1.4 ‘get’ Service. 3. BSDF is returned for the data element “Local Area Set Aside” through Atom Feeds.
|
1. FPDS-NG shall remove ‘BSDF’ values from Data Archives.
2. Remove ‘BSDF’ value from FPDS-NG for all the data elements. 3. Re-configure the following Validation Rule to be displayed on Version 1.2 contracts even if they were never touched through GUI services.
|
No |
FPDSPMOS-87 | 1. Some users are entering State Codes in the text box for PoP Country. There are State Codes in US which are same as the Country Code for another Country. The contracts end up having a foreign POP Country Code with a valid US Zip Code.
2. During the creation of the Reporting Views, the Congressional District and States are derived based on the Zip Codes. In the above scenario, the contract has a foreign PoP Country Code but with valid US Zip Codes, States and Congressional Districts.
|
The best solution would be to use 3 digit country codes instead of the current 2 digit codes. However, since changing the XML requires a version change and only 30% of the anomaly data is ‘Business Services Only’ the following solution is aimed to resolve the issue from GUI Services. The issue with the Reporting Issue is to be fixed.
Thus the solutions for the above issues are: 1. FPDS-NG shall accept only 3-digit country ISO codes from GUI Services and Web Portal but continue to accept 2-digit FIPS Code from Business Services. 2. The Reporting View creation shall be fixed to derive US Specific information (Congressional District, State Code etc) from the Zip-Code only when the Country Code is US. |
No |
FPDSHD-90310-74763 and FPDSPMOS-86 | FPDSHD-90310: The Appendix for the “Small Business Goaling Report” and the “Small Business Achievements by Awarding Organization Report” cites the following exclusion along with others:
Acquisitions by agencies on behalf of foreign governments or entities or international organizations: Awards in which the contract for foreign entity is yes are excluded from the report. FPDSHD-74763: Several Funding Office codes are displayed without the respective names in the “Small Business Goaling Report” and the “Small Business Achievements by Awarding Organization Report”. Some of them are: GE500, AJ200, CO200, PM070, SU400, DR860, CO150, BB210, GV100, GA100, MO550, HK300, BL400, TO400, MX115, MX530, JO100, TZ200, GY200, JA800, VE300, CA770, UV700, IZ100, KE500, AL600, PK330 and TS800. FPDSPMOS-86: DoD Tricare (Contracting) Office code H94002 has an end date of April 30, 2010; it exists as a funding office and is excluded in the “Small Business Goaling Report” and the “Small Business Achievements by Awarding Organization Report”. Contracting Office code HT9402 has a start date of May 1, 2010 and it should be excluded from these two reports.
|
1. The Appendix for the “Small Business Goaling Report” and the “Small Business Achievements by Awarding Organization Report” shall read as follows:
Acquisitions by agencies on behalf of foreign governments or entities or international organizations: Documents that are funded by foreign entities (“Funded by Foreign Entity” = ‘Yes’ OR “Foreign Funding” = ‘Foreign Funds – FMS’ or ‘Foreign Funds – non-FMS’) are excluded from the report. 2. “Small Business Goaling Report” and the “Small Business Achievements by Awarding Organization Report” shall display the names of the Funding Offices. 3. “Small Business Goaling Report” and the “Small Business Achievements by Awarding Organization Report” shall exclude documents that are awarded by HT9402 (TRICARE MGMT ACTIVITY AURORA WEST) |
No |
FPDSHD-87121 | As per the use case, V 1.0, V 1.1, V 1.2, Post CLOD V 1.3 and V 1.4 DOs and BPA Calls shall propagate the value of “Commercial Item Acquisition Procedures” from the referenced IDV. While V 1.0, V 1.1, V 1.2 and V 1.3 DOs and BPA Calls can no longer be created, any correction to the referenced IDV for the “Commercial Item Acquisition Procedures” has not been propagated to such DOs and BPA Calls.
|
1. FPDS-NG shall propagate the value of “Commercial Item Acquisition Procedures” to the V 1.0, V 1.1, V 1.2 and Post CLOD V 1.3 DOs and BPA Calls if their referenced IDV is corrected.
2. “Commercial Item Acquisition Procedures” shall continue to propagate from the referenced IDV on the V 1.4 DOs and BPA Calls. |
No |