V1.4 SP13.0

From FPDS-NG


Schedule

DescriptionStart Date End Date
BETA Installation Friday 12/01/2011 Friday 12/01/2011
Functional Qualification TestingMonday 12/05/2011 Friday 12/09/2011
Installation in ProductionThursday 12/15/2011 Thursday 12/15/2011

Document Changes

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

SPR Listing

SPR #ProblemSolutionImpact to Users and Integrators
FPDSPMOS-74Enhancement:

FPDS-NG actions that are awarded to vendors with Socio Economic flags as “Women Owned Small Business”, “Economically Disadvantaged Women Owned Small Business”, “Joint Venture Women Owned Small Business” or “Joint Venture Economically Disadvantaged Women Owned Small Business” and whose “Contracting Officer’s Determination of Business Size” is 'Small Business' shall be included in the Standard Reports.

FPDS-NG actions that are awarded to vendors with Socio Economic flags as “Women Owned Small Business”, “Economically Disadvantaged Women Owned Small Business”, “Joint Venture Women Owned Small Business” or “Joint Venture Economically Disadvantaged Women Owned Small Business” and whose “Contracting Officer’s Determination of Business Size” is 'Small Business' shall be included in the "Woman Owned Small Business" column of the "Socio Economic Workflow" for the following reports:

1. Total Action by PSC Report 2. Total Actions by NAICS Report

FPDS-NG actions that are awarded to vendors with Socio Economic flags as “Women Owned Small Business”, “Economically Disadvantaged Women Owned Small Business”, “Joint Venture Women Owned Small Business” or “Joint Venture Economically Disadvantaged Women Owned Small Business” and whose “Contracting Officer’s Determination of Business Size” is 'Small Business' shall be included in the "Woman Owned Small Business" column of the Summary report for the following Standard Reports: 1. Procurement History for Market Research Report 2. Geographical Report by Place of Performance Report 3. Geographical Report by Vendor Location Report 4. Funding Report 5. National Interest Action Report

Summary for the "Local Area Set Aside Report": FPDS-NG actions that are awarded to vendors with Socio Economic flags as “Women Owned Small Business”, “Economically Disadvantaged Women Owned Small Business”, “Joint Venture Women Owned Small Business” or “Joint Venture Economically Disadvantaged Women Owned Small Business” shall be included in the "Woman Owned Small Business" column.

Note: Actions shall be counted only once if multiple flags are marked. Appendices shall be updated accordingly.

NO
FPDSHD-88462Post CLOD Delivery/Task Orders (DO) and BPA Calls are not propagating the “Competition” values from the referenced IDV during ‘Correct’ (of the referenced IDV).1. FPDS-NG shall propagate the following from the referenced IDV to the post CLOD V 1.3 DoD SDO (DO against BOA, BPA and single award IDC) when the IDV is corrected:

A. Extent Competed B. Solicitation Procedures

2. FPDS-NG shall propagate the following from the referenced IDV to the post CLOD V 1.4 DoD SDO (DO single award IDC) when the IDV is corrected:

A. Solicitation Procedures

3. Existing data discrepancies shall be fixed with the value from the referenced IDV for the data elements “Extent Competed” and “Solicitation Procedures”.

4. On V 1.3 DoD MDO, FPDS-NG shall propagate the value of “Extent Competed” from the referenced IDV when the latter is corrected.

5. Existing data discrepancies shall be fixed with the value from the referenced IDV for “Extent Competed”.

NO
FPDSHD-89606Other Transactional data is only available for DoD and DHS. It has been observed that the Adhoc reporting for the Other Transactional data is not considering the “Date Signed” filter as provided by the users. Hence the data displayed is for all the fiscal years. Adhoc reporting shall consider the “Date Signed” filter and should display data for the selected filters for DoD and DHS users.NO
FPDSPMOS-79, FPDSIRB-178, FPDSPMOS-88GSA’s proposition:

To introduce new validation rules for the following scenarios: 1. FPDSPMOS-79: No contingency, “Ultimate Contract Value” is more than $3,000 and “Other than Full and Open Competition” = ‘Less than or equal to the Micro-Purchase Threshold’.

2. FPDSIRB-178: “Type of Set Aside” = ‘Service Disabled Veteran Owned Small Business Set-Aside’ or ‘SDVOSB Sole Source’ and vendor business type is not ‘Service Disabled Veteran Owned Business’.

3. FPDSPMOS-88: “Number of Offers” must be greater than ‘1’ for Multiple Award IDVs.

The new validation rules shall apply from V 1.4 and later:

1. FPDSPMOS-79: Validation Rule on the base documents: If the “Base and All Options Value” is greater than the Micro-Purchase threshold and if the “Contingency Humanitarian Peace Keeping Operation” is ‘Not Applicable’, then “Other than Full and Open Competition” cannot be ‘Less than or equal to the Micro-Purchase Threshold’. Micro-Purchase Threshold = $3000. This rule does not apply to modifications, although they can answer whether or not it is a contingency, because, the value provided on the base only holds significance.

2. FPDSIRB-178: If the “Type of Set Aside” is either ‘Service Disabled Veteran Owned Small Business Set-Aside’ or ‘SDVOSB Sole Source’, then vendor business type must be ‘Service Disabled Veteran Owned Business’. This rule does not apply to modifications.

3. FPDSPMOS-88: On the IDV: “Number of Offers” should be greater than 1 when the IDV is Multiple Award.

NO
FPDSHD-85551“Number of Actions” is accepting more than 9 digits through business services, but the value saved in the database is totally different.

Additionally, Data Dictionary cites that the maximum number of digits that “Number of Actions” can accept is 4; so the greatest value is ‘9999’.

1. “Number of Actions” shall accept a maximum of 9 digits through business services; the greatest value being ‘999999999’, thus ensuring consistency between web portal and business services.

2. If a value outside the range of 1 and 999999999 is sent, a validation rule shall display - “Number of Actions” must be between 1 and 999999999.

3. The value provided by the user, if it is within the range of 1 and 999999999 shall be saved in the FPDS-NG database and shall be retrieved as is.

4. Data Dictionaries for V 1.2, V 1.3, V 1.4, V 1.4.1 and V 1.4.2 shall be updated with the changes. Data Validation Rules documents for V 1.4 and V 1.3 shall be updated to reflect the new edit.

NO
FPDSHD-85560, 92148, FPDSHD-86397, FPDSHD-94585FPDSHD-85560, 92148: ‘Correction’ on an IDV Vendor modification is displaying the following Validation Rules when the document is not corrected for “Dates”:

DOD2A06: The "Date Signed" provided is later than the "Effective Date" of a finalized document referencing this IDV. Please provide a "Date Signed" earlier than the "Effective Date" of referencing documents.

DOD2A07: The "Date Signed" provided is later than the "Current Completion Date" of a finalized document referencing this IDV. Please provide a "Date Signed" earlier than the "Current Completion Date" of referencing documents.

FPDSHD-86397: ‘Create-isComplete’ Service on a BPA Call base is displaying the following Validation Rule when the “Effective Date” on the Call is earlier than the “Date Signed” of the referenced IDV latest modification. However, the “Effective Date” on the Call is later than the “Date Signed” of the referenced IDV base.

DOD2B01A: "Effective Date" on the Delivery/Task Order, BPA Call or Part 8 BPA cannot be earlier than the "Date Signed" on the Referenced IDV.

FPDSHD-94585: ‘Correct’ Service on a base DO that does not reference a Transferred IDV is displaying the following Validation Rule:

DOD2A02: "Date Signed" on the Delivery/Task Order, BPA Call and BPA cannot be earlier than the "Date Signed" of the Referenced IDV.

FPDSHD-85560, 92148: The following validation rules shall fire on the base IDV that has referencing Orders when they are corrected for 'Date' related data:

a. DOD2A05: The "Date Signed" provided is later than the "Date Signed" of a finalized document referencing this IDV. Please provide a "Date Signed" earlier than the "Date Signed" of finalized referencing documents.

b. DOD2A06: The "Date Signed" provided is later than the "Effective Date" of a finalized document referencing this IDV. Please provide a "Date Signed" earlier than the "Effective Date" of referencing documents.

c. DOD2A07: The "Date Signed" provided is later than the "Current Completion Date" of a finalized document referencing this IDV. Please provide a "Date Signed" earlier than the "Current Completion Date" of referencing documents.

However, these rules shall not fire when the IDV, that has referencing Orders, is not corrected for 'Date' related data. Additionally, these rules shall not fire on the IDV mod that has referencing Orders.

IDV = FSS, GWAC, BOA, BOA, IDC and OT IDV.

FPDSHD-86397: On the base Part 8 BPA Calls, the following Validation Rules shall display when the “Date Signed”, “Effective Date” and “Current Completion Date” are not in agreement with the “Date Signed” on the referenced base BPA:

a. DOD2A02A: "Date Signed" on the Delivery/Task Order, BPA Call and Part 8 BPA cannot be earlier than the "Date Signed" of the Referenced IDV.

b. DOD2B01A: "Effective Date" on the Delivery/Task Order, BPA Call or Part 8 BPA cannot be earlier than the "Date Signed" on the Referenced IDV.

c. DOD2C02A: "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.

This shall apply to ‘Create-isComplete’, ‘Update-isComplete’ and ‘Correct’ Services.

FPDSHD-94585: The following validation rules shall not fire on the base DOs, BPA Calls and Part 8 BPAs in validation to the dates on the Transferred referencing IDV, when the former is not referencing the latter. However, the following rules shall fire on the former by validating with the "Date Signed" on the right referenced IDV, when the 'Dates' on the former are changed:

a. DOD2A02A: "Date Signed" on the Delivery/Task Order, BPA Call and Part 8 BPA cannot be earlier than the "Date Signed" of the Referenced IDV.

b. DOD2A02: "Date Signed" on the Delivery/Task Order, BPA Call and BPA cannot be earlier than the "Date Signed" of the Referenced IDV.

c. DOD2B01A: "Effective Date" on the Delivery/Task Order, BPA Call or Part 8 BPA cannot be earlier than the "Date Signed" on the Referenced IDV.

d. DOD2C02A: "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.

NO
FPDSHD-73253, 86934FPDSHD-73253: The Transfer Action email notification does not indicate the Referenced IDV information; it just indicates the Order PIID. Since DoD creates Orders with the same PIID but referencing different IDVs, it is suggested that the Referenced IDV information be included for their benefit in the Transfer Action Email Notifications.


FPDSHD-86934: The Transfer Action Email Notifications are being sent to incorrect recipients. Also, some of the Transfer Actions are reflected in the inboxes of incorrect recipients. A few users who are not associated with either the Transferring Office or the Receiving Office have been receiving the Transfer Action notification emails and also the Transfer Actions in their inboxes. All these users have “Contracting Officer”, “Contracting Specialist” and/or “Reports User” roles.
FPDSHD-73253:

A. To the Transferring Agency when the transferred document is not standalone: FPDS-NG shall send the email notification as follows: The PIID <PIID> referencing the IDV <Agency Code-PIID> has been transferred to agency <Agency Code> and contracting office <Contracting Office ID> from your agency. Please contact your Agency/Department Administrator for details about this transfer.

For questions, please contact the FPDS-NG Support Desk at 703-390-5360 or fpdssupport@gcefederal.com.

B. To the Transferring Agency when the transferred document is standalone: FPDS-NG shall send the email notification as follows: The PIID <PIID> has been transferred to agency <Agency Code> and contracting office <Contracting Office ID> from your agency. Please contact your Agency/Department Administrator for details about this transfer.

For questions, please contact the FPDS-NG Support Desk at 703-390-5360 or fpdssupport@gcefederal.com.

C. To the Receiving Agency when the transferred document is not standalone: FPDS-NG shall send the email notification as follows: The PIID <PIID> referencing the IDV <Agency Code-PIID> has been transferred from agency <Agency ID> and contracting office <Contracting Office ID> to your agency. Please contact your Agency/Department Administrator for details about this transfer.

For questions, please contact the FPDS-NG Support Desk at 703-390-5360 or fpdssupport@gcefederal.com.

D. To the Receiving Agency when the transferred document is standalone: FPDS-NG shall send the email notification as follows: The PIID <PIID> has been transferred from agency <Agency ID> and contracting office <Contracting Office ID> to your agency. Please contact your Agency/Department Administrator for details about this transfer.

For questions, please contact the FPDS-NG Support Desk at 703-390-5360 or fpdssupport@gcefederal.com.

FPDSHD-86934:

A. For DoD: Transfer Action Email Notifications shall not be sent to the users when the Transfer Action did not happen from/to their Contracting Office or their Agency.

B. For DoD: Transfer Actions shall not be received in the inboxes (Transfer Award or Transfer IDV) of the users when the Transfer Action did not happen from/to their Contracting Office or their Agency.

C. Civilian behavior shall not change.

NO