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 software fix:
1. FPDS-NG shall introduce a validation rule to state that when “Place of Manufacture” is ‘Mfg Outside the U.S. - Qualifying Country (DoD Only)’, then the value for “Country of Product or Service Origin” must be one of the following qualifying countries: • Australia • Belgium • Canada • Denmark • Egypt • Federal Republic of Germany • France • Greece • Israel • Italy • Luxembourg • Netherlands • Norway • Portugal • Spain • Sweden • Switzerland • Turkey • United Kingdom of Great Britain • Northern Ireland 2. FPDS-NG shall introduce a validation rule to state that only DoD can choose “Place of Manufacture” as ‘Mfg Outside the U.S. - Qualifying Country (DoD Only)’. The above requirements shall apply to ‘correct’ of V 1.2, V 1.3 and V 1.4 documents and for ‘isComplete’/’Validate’ on V 1.4 documents. 4. 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.) shall continue to display as is. For the data fix by the agencies: 5. Agencies shall correct their documents that have any of the following values of “Place of Manufacture”, but have PSC Codes that start with an alpha or one of the values - 5510, 87**, 88**, 9410, 9430, 9440, 9610, 9620 or 9630: • ‘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)' For the report fix: 6. Since it is not viable to make the civilian agencies pick another “Place of Manufacture” value on their contracts that currently have ‘Mfg Outside the U.S. - Qualifying Country (DoD Only)’, data fix is not being proposed. However, “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 • Country of Product or Service Origin is one of the following qualifying countries: o Australia o Belgium o Canada o Denmark o Egypt o Federal Republic of Germany 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 o Northern Ireland OR If agencies did not opt to fix the incorrect data, then 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 Belgium o Canada o Denmark o Egypt o Federal Republic of Germany 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 o 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-86397 | The validation rules introduced in SP 9.0 do not allow the Dates (“Date Signed”, “Effective Date” or “Current Completion Date”) on referencing orders to be prior to the “Date Signed” on referenced Vendor Mod IDV even if the dates are later than “Date Signed” on the base IDV.
A) The following validation rules are displayed on the Referencing Awards: 1. DOD2B01A - Version 1.3 and lower: o ““Effective Date” on the Delivery/Task Order, BPA Call or BPA cannot be earlier than the “Date Signed” on the Referenced IDV.” DOD2B01A - On Version 1.4 and later: o "Effective Date" on the Delivery/Task Order, BPA Call or Part 8 BPA cannot be earlier than the "Date Signed" on the Referenced IDV. 2. DOD2C02A - Version 1.3 and lower: o ““Current Completion Date” on the Delivery/Task Order, BPA Call or BPA cannot be earlier than the “Date Signed” on the Referenced IDV.” DOD2C02A - On Version 1.4 and later: o "Current Completion Date" on the Delivery/Task Order, BPA Call or Part 8 BPA cannot be earlier than the "Date Signed" on the Referenced IDV. B) The following validation rules are displayed on the Referenced Vendor Mod IDV on ‘Correct’: 1. DOD2A06: o “The “Date Signed” provided is later than the “Effective Date” of a final document referencing this IDV. Please provide a “Date Signed” earlier than the “Effective Date” of all referencing documents.” 2. DOD2A07: o “The “Date Signed” provided is later than the “Current Completion Date” of a final document referencing this IDV. Please provide a “Date Signed” earlier than the “Date Signed” of all referencing documents.”
|
YET TO BE FINALIZED | 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.
|
YET TO BE FINALIZED | 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.
|
YET TO BE FINALIZED | 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-80259, 87121 | Sub-Contracting Plan: As per the use case, V 1.0, V 1.1, V 1.2 and V 1.3 DOs and BPA Calls shall propagate the value of “Sub-Contracting Plan” 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 “Sub-Contracting Plan” has not been propagated to such DOs and BPA Calls.
Commercial Item Acquisition Procedures: 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.
|
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.
|
YET TO BE FINALIZED | 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".
|
YET TO BE FINALIZED | 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 |