V1.4 SP 28.0

From FPDS-NG

Schedule

DescriptionStart Date End Date
BETA Installation Tuesday June 9, 2015Tuesday June 9, 2015
Government Acceptance Testing Friday June 12, 2015Tuesday June 16, 2015
Installation in ProductionFriday June 26, 2015Friday June 26, 2015

Document Changes

DocumentationChanges Required
XML SpecificationsNo
Web ServicesNo
Data DictionaryYes
NASA Specific Data DictionaryNo
Use Case SummaryNo
Validation RulesYes
ReportingNo
ezSearchNo
Atom FeedsNo
Online HelpNo
Computer-Based TrainingNo
User ManualNo

SPR Listing

SPR #Enhancement/ProblemSolutionImpact to Users and Integrators
14680 The Buy American Act Place of Manufacture Report is incorrectly including records where the PSC (Product or Service Code) is a Service (begins with an Alpha character). The Buy American Act Place of Manufacture Report shall be updated to exclude records where the PSC is a Service (begins with an Alpha character).

No Preview or Appendix updates for this change are necessary.

Documentation changes:

The Appendix of the Buy American Act Place of Manufacture Report shall be updated to remove mention of “IDVs,” which were never included in the report because IDVs do not have a “Place of Manufacture.”

No
15469 “Type of Set Aside” is losing its value on V1.4 Delivery Orders when the referenced V1.4 BOA is corrected.

Note: “Type of Set Aside” is a required value on V1.4 Delivery Orders but not applicable on V1.4 BOAs. “Type of Set Aside” loses its value on the V1.4 Base DO regardless of the data element(s) corrected on the referenced V1.4 BOA.

A software fix shall be performed so that the user-provided value for “Type of Set Aside” is retained on V1.4 Delivery Orders, regardless if a correction is made to the referenced V1.4 BOA.

This fix will also apply to the new Base after a “Transfer Action” for the above scenario.

Yes
16456 The current D&B Disclaimer text must be updated. The current D&B disclaimer text shall be updated throughout FPDS-NG.

All Standard Reports that include the D&B Disclaimer in the Preview and Appendix will be updated to include the new text.

The new D&B Disclaimer text (https://www.fpds.gov/help/DnB.htm) is as follows:

Limitation on Permissible Use of Dun & Bradstreet, Inc. (D&B) Data:

This website contains data supplied by third party information suppliers, one of which is D&B. Each entity DUNS Number and its associated business information are referred to herein as “D&B Data.”

D&B hereby grants you, the user, a license for a limited, non-commercial use of D&B data within the limitations set forth herein. By using this website you agree that you shall not use D&B data without giving written attribution to the source of such data (i.e., D&B) and shall not access, use or disseminate D&B data in bulk, (i.e., in amounts sufficient for use as an original source or as a substitute for the product and/or service being licensed hereunder).

Under no circumstances are you authorized to use the D&B data for commercial, resale or marketing purposes (e.g., identifying, quantifying, segmenting and/or analyzing customers and prospective customers). Systematic access (electronic harvesting) or extraction of content from the website, including the use of "bots" or "spiders", is prohibited. Federal government entities are authorized to use the D&B data for purposes of acquisition as defined in FAR 2.101 and for the purpose of managing Federal awards, including sub-awardees, or reporting Federal award information.

GSA assumes no liability for the use of the D&B data once it is downloaded or accessed. The D&B data is provided "as is" without warranty of any kind. The D&B data is the intellectual property of D&B. In no event will D&B or any third party information supplier be liable in any way with regard to the use of the D&B DATA. For more information about the scope of permissible use of D&B data licensed hereunder, please contact D&B at datause_govt@dnb.com.

Yes
16706 The DoD-only format rules for “Solicitation ID” are not firing on a new Base after a “Transfer Action” modification. A software fix shall be performed so that the DoD-only format rules fire correctly for “Solicitation ID” on a new Base created after a “Transfer Action” modification, when an incorrect value is entered for “Solicitation ID.”

The existing DoD-only format rules for “Solicitation ID” are as follows:

• DOD1E01 - Solicitation ID must be 13 characters.
• DOD1E02 - Position 9 of the Solicitation ID (type of instrument code) must be B, N, Q, R, T, or U.
• DOD1E03 - The first 6 characters of the Solicitation ID must be a valid DODAAC for a Contracting Office.
• DOD1E04 - Positions 7 and 8 of the Solicitation ID must be the current FY or any prior FYs. (up to 50 years prior to the current FY).

Yes
16849 1) “FedBizOpps” is incorrectly propagating to V1.4 Base Delivery Orders from the referenced V1.4 BOA.

2) When a user updates “FedBizOpps” on a V1.4 Base Delivery Order, the value is not being retained.


1) A software fix shall be performed so that the value for “FedBizOpps” no longer propagates to V1.4 Base Delivery Orders from the referenced V1.4 BOA.

2) A software fix shall be performed to retain the user-entered value for “FedBizOpps” on V1.4 Base Delivery Orders. This fix shall also apply to the new Base after a “Transfer Action.”

Yes
16937 ATOM Feed users are unable to pull records that contain non-printable ASCII characters in the “Description of Requirement” field.

FPDS-NG accepts non-printable ASCII characters in the following open text fields: Ordering Procedure, Description of Requirement, and Other Interagency Contracting Statutory Authority.

FPDS-NG shall no longer accept non-printable ASCII characters in the following open text fields:

• Ordering Procedure
• Description of Requirement
• Other Interagency Contracting Statutory Authority

FPDS-NG shall display the new validation rule ‘5H02’ on all records which have one or more non-printable ASCII characters in “Ordering Procedure.” There shall be no Start Date for this rule, and it shall apply to all existing records.

5H02: “Ordering Procedure” must not contain Non-printable ASCII characters.

• This requirement shall apply only to Base documents.
• This requirement shall apply to the actions: ‘Validate/isComplete’, ‘Approve’, and ‘Correct.’
• This requirement shall apply to the following IDV document types:

1. GWAC
2. BOA
3. PART 8 BPA
4. PART 13 BPA
5. IDC

FPDS-NG shall display the new validation rule ‘6M18’ on all records which have one or more non-printable ASCII characters in “Description of Requirement.” There shall be no Start Date for this rule, and it shall apply to all existing records.

6M18: “Description of Requirement” must not contain Non-printable ASCII characters.

• This requirement shall apply to Base documents and Modifications.
• This requirement shall apply to the actions: ‘Validate/isComplete’, ‘Approve’, and ‘Correct.’
• This requirement shall apply to the following Award/IDV document types:

1. Delivery Order/Task Order
2. Purchase Order
3. Definitive Contract
4. BPA Call
5. FSS
6. GWAC
7. BOA
8. BPA
9. IDC
10. Intragovernmental
11. Cooperative Agreement
12. Grants For Research
13. Funded Space Act Agreement
14. Training Grant

FPDS-NG shall display the new validation rule ‘7F02’ on all records which have one or more non-printable ASCII characters in “Other Interagency Contracting Statutory Authority.” There shall be no Start Date for this rule, and it shall apply to all existing records.

7F02: “Other Interagency Contracting Statutory Authority” must not contain Non-printable ASCII characters.

• This requirement shall apply to Base documents and Modifications.
• This requirement shall apply to the actions: ‘Validate/isComplete’, ‘Approve’, and ‘Correct’
• This requirement shall apply to the following Award/IDV documents types:

1. Delivery Order/Task Order
2. Purchase Order
3. Definitive Contract
4. BPA Call
5. FSS
6. GWAC
7. BOA
8. BPA
9. IDC
10. Intragovernmental
11. Cooperative Agreement
12. Grants For Research
13. Funded Space Act Agreement
14. Training Grant

FPDS-NG shall display the new validation rule ‘OT6M18’ on all OT records which have one or more non-printable ASCII characters in “Description of Requirement.” There shall be no Start Date for this rule, and it shall apply to all existing records.

OT6M18: “Description of Requirement” must not contain Non-printable ASCII characters.

• This requirement shall apply to Base documents and Modifications.
• This requirement shall apply to the actions: ‘Validate/isComplete’, ‘Approve’, and ‘Correct.’
• This requirement shall apply to the following OT document types:

1. Other Transaction Order
2. Other Transaction Agreement
3. Other Transaction IDV

FPDS-NG will no longer accept the following non-printable ASCII characters in Ordering Procedure, Description of Requirement, and Other Interagency Contracting Statutory Authority:

http://www.fpds.gov/downloads/non_printable_ascii_characters.png

Documentation changes:

The Data Validation rules document shall be updated to add the new validation rules to each of the following sections:

• 5H- Ordering Procedure
• 6M- Description of Requirement
• 7F- Other Interagency Contracting Statutory Authority

Yes