V1.4 SP12.0

From FPDS-NG


Schedule

DescriptionStart Date End Date
BETA Installation Thursday 9/15/2011 Friday 9/16/2011
Functional Qualification TestingMonday 9/19/2011 Thursday 9/22/2011
Re-test (if needed)Tuesday 9/27/2011 Tuesday 9/27/2011
Installation in ProductionFriday 10/07/2011 Friday 10/07/2011

Document Changes

DocumentationChanges Required
XML SpecificationsNo
Web ServicesNo
Data Dictionary Yes
NASA Specific Data DictionaryNo
Use Case SummaryNo
Validation RulesYes
Online HelpYes
Computer-Based TrainingYes
Report ManualNo
User ManualYes

SPR Listing

SPR #ProblemSolutionImpact to Users and Integrators
FPDSPMOS-75 Change Request: FPDS-NG should be able to accommodate the changes that have taken place in the “Product or Service Codes” as of 10/01/2011.

Product or Service Code change details are available in the below spreadsheet:

Click here for PSC Crosswalk

Note: These changes will be implemented in production on October 7, 2011.

Resolution for Phase I:

1. Software Fix:

- FPDS-NG shall incorporate all the PSC Code changes as of 10/01/2011, where 10/01/2011 corresponds to the Date Signed on the documents. Prior to 10/01/2011 (09/30/2011), the existing PSC data shall continue to apply; from 10/01/2011 and later, the new PSC changes shall apply.

- Prior to 10/01/2011 (09/30/2011), the existing Validation Rules shall continue to display. From 10/01/2011 and later, the modified Validation Rules (with the PSC changes) shall display.

- Prior to 10/01/2011 (09/30/2011), the existing PSC Descriptions shall continue to display. From 10/01/2011 and later, the modified PSC Descriptions shall display.

- When an invalid PSC Code is selected, the referential validation rule shall continue to display.

2. Data Fix: No data fix is required.

3. Documentation Changes: Data Validation Rules documents.

Resolution for Phase II:

4. Reports Fix: The Standard reports that have PSC exclusions shall continue with the existing logic prior to 10/01/2011 and shall have the new logic (with the PSC changes) from 10/01/2011 and later. The reports impacted are:

- Small Business Goaling

- Small Business Achievements by Awarding Organization

- Performance Based Service Acquisition

- Place of Manufacture

No
FPDSHD-72202, 83129, 86488 1. The “Place of Manufacture” value, ‘Mfg Outside the U.S. - Qualifying Country (DoD Only)’ indicates the following:

• Contracting Agency is DoD • Country of Product or Service Origin is one of the qualifying countries • PSC Codes allowed are 1000-9999, with an exception of 5510, 87**, 88**, 89**, 9410, 9430, 9440, 9610, 9620 or 9630

The “Buy American Act Place of Manufacture” report for the column, “Mfg Outside the U.S. - Qualifying Country (DoD Funds Only)” does not consider the following conditions:

a. The value of “Country of Product or Service Origin” as one of the qualifying countries b. DoD as the Contracting Agency and the Funding 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, the validation rules 9H03, 9H04 and 9H05 require revision as the PSC 89** should be included in the exclusion list (as confirmed by DoD on 08/25/2011).


1. FPDS-NG shall revise the validation rule 9H03 as:

'Place of Manufacture' can only 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 '1000-9999', except the values: 5510, 87**, 88**, 89**, 9410, 9430, 9440, 9610, 9620 or 9630.

2. FPDS-NG shall revise the validation rule 9H04 as: 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 5510, 87**, 88**, 89**, 9410, 9430, 9440, 9610, 9620, 9630 or any service.

3. FPDS-NG shall revise the validation rule 9H05 as: Place of Manufacture can only be 'Not a manufactured end product' when the 'PSC Code' is 5510, 87**, 88**, 89**, 9410, 9430, 9440, 9610, 9620, 9630 or any service.

4. Data fix shall be performed to update the "Place of Manufacture" value as 'Not a manufactured End Product' for the existing documents that have a PSC starting with 89** and that were signed on or later than 06/28/2008.

5. The “Buy American Act Place of Manufacture” report shall use the below calculation for the column, “Mfg Outside the U.S. - Qualifying Country (DoD Funds Only)”: • DoD awarded and funded documents WITH • “Place of Manufacture” as ‘Mfg Outside the U.S. - Qualifying Country (DoD Only)’ WHOSE • PSC Code is between 1000 and 9999 (both values inclusive, but excluding 5510, 87**, 88**, 89**, 9410, 9430, 9440, 9610, 9620 or 9630) AND WHOSE • “Country of Product or Service Origin” as one of the following qualifying countries: ‘Australia’, ‘Austria’, ‘Belgium’, ‘Canada’, ‘Denmark’, ‘Egypt’, ‘Federal Republic of Germany’, 'Germany', ‘Finland’, ‘France’, ‘Greece’, ‘Israel’, ‘Italy’, ‘Luxembourg’, ‘Netherlands’, ‘Norway’, ‘Portugal’, ‘Spain’, ‘Sweden’, ‘Switzerland’, ‘Turkey’ and ‘United Kingdom of Great Britain and Northern Ireland’.

6. Appendix for the “Buy American Act Place of Manufacture” report shall be updated to read the changed logic for the column, ‘Mfg Outside the U.S. - Qualifying Country (DoD Funds Only)’.

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 Issues with the Rerepresentation Eligible Actions Report:

1. IDVs are not included in the report because the current logic of considering “Ultimate Completion Date” is filtering out all the IDVs. 2. The “Ultimate Completion Date” condition is not being applied on the latest modification in the Award family. It is currently applied on any modification that is eligible as per the 5 year period and is active. 3. Awards with a null “Ultimate Completion Date” are excluded from the report. 4. Award Detail includes both base and the modification documents in contradiction to the requirements to display only the base.



1. “Rerepresentation Eligibility Actions Report” shall determine the eligibility as follows: Get the documents by going back to 5 years from the “To Date” and apply the following conditions: - IDV Type = FSS, GWAC, BOA, Part 13 BPA and IDC or Award Type = PO and DCA AND - Contracting Officer’s Determination of Business Size = Small Business AND - IDV is active as determined by the “Last Date to Order” on the latest IDV modification OR Award is active as determined by the “Ultimate Completion Date” on the latest Award modification The combination of “Date Signed”, “Prepared Date” and “Last Modified Date” is used to determine the activeness of an IDV/Award if more than one modification has the same “Date Signed”. - If the latest modification is a vendor modification and falls into the 5 year period or later, then the contractual family is excluded from the report

2. The column “Total Eligible Actions for Rerepresentation” shall display either the base (mod 0) or the latest vendor modification in the eligible contractual family.

3. “Rerepresentation Eligibility Actions Report” shall exclude actions with data anomalies - Either a null “Last Date to Order” on the latest IDV modification or a null “Ultimate Completion Date” on the latest Award modification.

4. The “Modification Number” drill down continues to exist.

5. Award Detail for this report shall display the base. Note: The modification number retrieved at the Summary level > Modification Number shall match with that in the Award Detail.

6. Appendix for this report shall spell out all the data anomalies found and how they are addressed in the report.

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.


For civilian agencies, the “Organization Code” shall not be defaulted for the “Contracting Office” Report on the Search Criteria Screen. The current behavior for DoD shall continue to operate as is. 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:

Business Services: 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

This issue does not happen when “Competitive Procedures” tag is used with ‘CDO’ as the value. Additionally, V 1.0/1.1 requests do not display this error. V 1.2, V 1.3 and V 1.4 display this error when the “Competitive Procedures” tag is not used with ‘CDO’ as the value.

Web Portal: When “Competitive Procedures/Reason Not Competed” is null/empty: Correct the DO/TO with a value of CDO to get the error 10B02 (Either a Competitive Procedure or a Other than Full and Open Competition must be selected) and when “Competitive Procedures/Reason Not Competed” is CDO: Correct the DO/TO with a value of NDO or any other value to get the error 10B14 (Either Other than Full and Open Competition or Competitive Procedures can be entered).

For Local Area Set Aside:

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):

The validation rule 10J01 does not consider the value 'Services pursuant to FAR 12.102(g)' and V 1.4 IDV ‘Create’ with CIAP as ‘N’ or any invalid value displays a System Error.


1. For "Extent Competed":

- Business Services: FPDS-NG shall not display the Error Code 4004 (“The value "CDO" for Data Element "Extent Competed" is invalid”) when a V 1.0/1.1 DO/TO is being corrected using a V 1.4 Service.

- Web Portal: FPDS-NG shall not display 10B02 (Either a Competitive Procedure or a Other than Full and Open Competition must be selected) when a V 1.0/1.1 DO/TO that has “Competitive Procedures/Reason Not Competed” as null is being corrected to a value of CDO.

- Web Portal: FPDS-NG shall not display 10B14 (Either Other than Full and Open Competition or Competitive Procedures can be entered) when a V 1.0/1.1 DO/TO that has “Competitive Procedures/Reason Not Competed” as CDO is being corrected to any other value.

- Web Portal: FPDS-NG shall continue to not display any error message and shall continue to save the value when a V 1.0/1.1 DO/TO that has “Competitive Procedures/Reason Not Competed” as null is being corrected to a value other than a CDO.

2. For Local Area Set Aside:

- Business Services: FPDS-NG shall save the value of “Local Area Set Aside” on the V 1.2 documents that are signed on or later than 08/04/2006 when they are corrected using a V 1.4 Service.

- Business Services: FPDS-NG shall continue to display 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'.) when the V 1.2 documents that are signed on or later than 08/04/2006 are corrected.

- Business Services: FPDS-NG shall display the mandatory rule 10U01 (The Local Area Set Aside must be selected if the Date Signed is later than "08/03/2006".) when the V 1.2 documents are signed on or later than 08/04/2006 and are corrected.

- Business Services: FPDS-NG shall display the Validation Rule 10U02 (The Local Area Set Aside must not be selected if the Date Signed is prior to "08/04/2006".) when the V 1.2 documents are signed prior to 08/04/2006 are corrected with a value for ‘Local Area Set Aside”.

- Business Services: V 1.2 ‘get’ shall continue to not return “Local Area Set Aside”.

- Business Services: V 1.3 and V 1.4 ‘get’ shall continue to return “Local Area Set Aside”.

3. For Commercial Item Acquisition Procedures:

V 1.4 Business Services (correct) for versions V 1.3 and later: When an invalid* value is provided for CIAP, FPDS-NG shall display a validation rule to indicate that the value is invalid. FPDS-NG shall not display the System Error.

  • Valid values are A – Commercial Item, B - Supplies or services pursuant to FAR 12.102(f) , C - Services pursuant to FAR 12.102(g), and D – Commercial Item Procedures Not Used.

For V 1.3 and V 1.4, the Validation Rule 10J01 (If the Commercial Item Test Program is Yes, then Commercial Item Acquisition Procedures must be either Commercial Item or Supplies or Services pursuant to FAR 12.102(f)) shall be modified to include ‘Services pursuant to FAR 12.102(g)’.

Modified 10J01: If the Commercial Item Test Program is Yes, then Commercial Item Acquisition Procedures must be Commercial Item, Supplies or Services pursuant to FAR 12.102(f) or Services pursuant to FAR 12.102(g).

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’ value from FPDS-NG for the data elements: CITP, LASA and National Interest Action.

CITP: 247,185 Awards and 19,448 IDVs will be touched NIA: 13,400 Awards and 164 IDVs will be touched LASA: 129,817 Awards and 144 IDVs will be touched

2. FPDS-NG shall display the following validation rule in Version 1.2 and above when “Date Signed” is greater than 3rd August 2006 and “Local Area Set Aside” is not provided even if the contracts were never touched through GUI services 10U01 - The Local Area Set Aside must be selected if the Date Signed is later than "08/03/2006".

3. FPDS-NG shall update the “Local Area Set Aside” in Version 1.2 when a value is sent for ‘Correct’ for a V 1.2 contract.

4. FPDS-NG shall make sure the BSDFs are not returned in ‘get’ service, Atom Feeds or Data Archives.

5. FPDS-NG shall ensure referential data validation is carried out for CITP, LASA and. National Interest Action in Version 1.3 and above.

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: Actions 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, and also Pre CLOD V 1.3 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
FPDSPMOS-85 Change Request: OMB’s Environmental Attributes – Bio-based, Energy-efficient and Environmentally-preferable

o No separate and distinct PSC codes to report environmental attributes o Modify the Data Element, “Use of Recovered Material” to “Recovered Materials/Sustainability” o To include environmental options in the “Recovered Materials/Sustainability” drop down menu: 1. FAR 52.223-4 Included 2. FAR 52.223-4 and 52.223-9 Included 3. No clauses Included and No Sustainability Included 4. Energy efficient 5. Bio-based 6. Environmentally preferable 7. FAR 52.223-4 & energy efficient 8. FAR 52.223-4 & bio-based 9. FAR 52.223-4 & environmentally preferable 10. FAR 52.223-4 & bio-based & energy efficient 11. FAR 52.223-4 & bio-based & environmentally preferable 12. FAR 52.223-4 & bio-based & energy efficient & environmentally preferable


- FPDS-NG shall rename the data element, “Use of Recovered Material” as “Recovered Materials/Sustainability” only on the FPDS-NG contractual screens on all the existing and new documents.

Note: XML tag shall not be changed.

- FPDS-NG shall introduce the following values for the data element, “Recovered Materials/Sustainability”: 1. Energy efficient - D 2. Bio-based - E 3. Environmentally preferable (http://www.whitehouse.gov/omb/procurement_index_green/) - F 4. FAR 52.223-4 & energy efficient - G 5. FAR 52.223-4 & bio-based - H 6. FAR 52.223-4 & environmentally preferable (http://www.whitehouse.gov/omb/procurement_index_green/) - I 7. FAR 52.223-4 & bio-based & energy efficient - J 8. FAR 52.223-4 & bio-based & environmentally preferable (http://www.whitehouse.gov/omb/procurement_index_green/) - K 9. FAR 52.223-4 & bio-based & energy efficient & environmentally preferable (http://www.whitehouse.gov/omb/procurement_index_green/) - L

The new values come into effect from 10/01/2011.

- FPDS-NG shall continue to display the existing values as:

1. FAR 52.223-4 Included - A 2. FAR 52.223-4 and 52.223-9 Included - B

- FPDS-NG shall display the existing value, ‘No clauses Included’ as ‘No Clauses Included and No Sustainability Included’ - C.

- The validation rule 8L03A/DOD8L01A shall be modified as If "EPA Designated Products" is 'Not Required' then "Recovered Materials/Sustainability" must be 'No Clauses Included and No Sustainability Included’, for documents signed prior to 10/01/2011 and as If "EPA Designated Products" is 'Not Required' then "Recovered Materials/Sustainability" must be 'No Clauses Included and No Sustainability Included’, 'Bio-based', 'Energy Efficient' or 'Environmentally Preferable' for documents signed on or later than 10/01/2011.

- The validation rule 8L03B/DOD8L01B shall continue to display as is - If "EPA Designated Products" is other than 'Not Required' then "Recovered Materials/Sustainability" must have any value.

Note: 8L03B/DOD8L01B is suppressed for V 1.4, but is active for lower versions.

- The above changes shall apply to all the versions – V 1.0, V 1.1, V 1.2, V 1.3, V 1.4 and above.

- The above changes shall apply to ‘Correct’ of V 1.0, V 1.1, V 1.2 and V 1.3 documents AND ‘isComplete’/’Validate’, ‘Correct’ and ‘Approve’ of V 1.4 documents.

- FPDS-NG shall update the following documentation: 1. Data Dictionaries 2. Data Validation Rules documents 3. User Manual 4. Help Files

- FPDS-NG shall display the newly added “Recovered Materials/Sustainability” values in the Atom Feeds, as they are chosen on the FPDS-NG documents.

- Existing data with the values chosen as ‘No Clauses Included’ shall be modified to ‘No Clauses Included and No Sustainability Included’.

- RCRA report shall display the numbers for the "Recovered Materials/Sustainability” values that include FAR clauses. Appendix shall be modified accordingly.

- FPDS-NG shall allow the newly added “Recovered Materials/Sustainability” values, as they are selected, to be searchable, filtered and displayed in the Ad hoc reporting.

No
FPDSPMOS-99 Agency Name Updates
Agency CodeExisting Contracting Agency NameNew Contracting Agency Name
7001OFFICE OF THE SECRETARY, DEPARTMENT OF HOMELAND SECURITYOFFICE OF PROCUREMENT OPERATIONS
7003BUREAU OF CITIZENSHIP AND IMMIGRATION SERVICESU.S. CITIZENSHIP AND IMMIGRATION SERVICES
7012BUREAU OF IMMIGRATION AND CUSTOMS ENFORCEMENTU.S. IMMIGRATION AND CUSTOMS ENFORCEMENT
7014BUREAU OF CUSTOMS AND BORDER PROTECTIONU.S. CUSTOMS AND BORDER PROTECTION
1435BUREAU OF OCEAN ENERGY MANAGEMENT, REGULATION AND ENFORCEMENTBUREAU OF OCEAN ENERGY MANAGEMENT
Yes