Difference between revisions of "V1.5 SP 12.0"

From FPDS-NG

Line 4: Line 4:
 
<tr><th width=30% align="center"><b>Description</b></th><th width=34% align="center"><b>Start Date</b></th>
 
<tr><th width=30% align="center"><b>Description</b></th><th width=34% align="center"><b>Start Date</b></th>
 
<th width=34% align="center"><b>End Date</b></th></tr>
 
<th width=34% align="center"><b>End Date</b></th></tr>
<tr><td nowrap>BETA Implementation </td><td nowrap>January 10, 2022</td><td nowrap>January 10, 2022</td></tr>
+
<tr><td nowrap>Beta Deployment</td><td nowrap>March 11, 2022</td><td nowrap>March 11, 2022</td></tr>
<tr><td nowrap>Government Acceptance Testing </td><td nowrap>January 18, 2022</td><td nowrap>January 20, 2022</td></tr>
+
<tr><td nowrap>Government Acceptance Testing </td><td nowrap>March 21, 2022</td><td nowrap>March 25, 2022</td></tr>
<tr><td nowrap>Production Deployment </td><td nowrap>January 29, 2022</td><td nowrap>January 29, 2022</td></tr>
+
<tr><td nowrap>Production Deployment </td><td nowrap>April 2, 2022</td><td nowrap>April 2, 2022</td></tr>
 
</table>
 
</table>
  
Line 31: Line 31:
  
 
<td style="width:95px" valign="center">
 
<td style="width:95px" valign="center">
IAEENH-1034 / IAEDEV-58948
+
IAEDEV-60364 / IAEDEV-60365
 
</td>
 
</td>
  
<td>DoD has requested “CAGE Code” be added to the FPDS lookup screen.
+
<td>FPDS and FAADC Phase 3 UEI Enhancements
  
<td>This item will add the 'CAGE Code' as a searchable data element on the FPDS entity lookup screen.
+
<td>This is the third and final phase of the DUNS to UEI transition for both FPDS and FAADC systems. This will make the UEI element a mandatory field. All instances of the DUNS data element and associated values will be removed and the UEI (SAM) field will be renamed to ‘Unique Entity ID’ (short: ‘UEI’) from both systems, and the (GUI Screens, GUI Services, validation rules, documentation, etc.).
  
</td>
+
WSDLs will not be updated to remove DUNS-related tags, but the tags will be disabled from user entry/submission and users must begin using the UEI tag (FPDS: <genericString02>; FAADC: <UEI>) to submit a vendor for transactions.
 +
 
 +
Both FPDS and FAADC Atom Feeds will be updated so that DUNS values are not sent in DUNS-related tags. All DUNS-related tags will appear as null/empty in the Atom Feeds.</td>
  
<td align="center">No</td>
+
<td align="center">Yes</td>
  
 
<tr>
 
<tr>
  
 
<td style="width:95px" valign="center">
 
<td style="width:95px" valign="center">
IAEENH-995 / IAEDEV-57389
+
IAEDEV-64036 / IAEDEV-64037
 
</td>
 
</td>
  
<td>Change data element screen name for 'Fedbizopps' to a more descriptive term as Fedbizopps has been integrated within SAM.gov. Approved screen name change is ‘Contract Opportunities Notice'.
+
<td>Decommissioning of the D&B API for both FPDS and FAADC systems
 
    
 
    
<td>The data element screen name for 'Fedbizopps' will be changed to ‘Contract Opportunities Notice'.
+
<td>The Dun & Bradstreet API used to retrieve new SAM Exception entities (previously not found in FPDS/FAADC) will be decommissioned and a new SAM API will be used to retrieve all SAM Exception entity information using a UEI (SAM) value, instead of UEI (DUNS).
  
 
</td>
 
</td>
Line 59: Line 61:
  
 
<td style="width:95px" valign="center">
 
<td style="width:95px" valign="center">
IAEENH-988 / IAEDEV-57388
+
IAEDEV-59966
 
</td>
 
</td>
  
<td>When Funding Agency is outside of the Department Agency the “Interagency Contracting Authority” is not mandatory. 
+
<td>ezSearch ‘ICD’ tab Search Issues
 
    
 
    
<td>New Validation rules will fire whenever a Funding Agency Department is outside of the Contracting Awarding Department, requiring that the user needs to fill out “Interagency Contracting Authority” (ICA). Conversely if the user fills out the ICA, but the Department values match, another validation rule should be introduced to not require ICA data.
+
<td>UEI (SAM) values cannot be used to search in the ‘ICD’ tab of ezSearch. The system will be updated to ensure UEI values are indexed and searchable from the ezSearch ‘ICD’ tab.
  
 
</td>
 
</td>
  
<td align="center">No</td>
+
<td align="center">Yes</td>
  
 
<tr>
 
<tr>
  
 
<td style="width:95px" valign="center">
 
<td style="width:95px" valign="center">
IAEENH-985 / IAEDEV-57387
+
IAEDEV-62921
 
</td>
 
</td>
  
<td>Two validation rules for Solicitation Date fire for the DoD agency only.
+
<td>‘SAM Exception’ label update in FPDS/FAADC
 
    
 
    
<td>The verbiage for validation rule ‘DOD2H06’ shall be updated for clarity to the following:
+
<td>After completion of the DUNS to UEI transition, SAM Exception entities will be required to go to SAM to generate a UEI value, for record creation purposes in FPDS. The ‘SAM Exception’ label will be updated to ‘FAR 4.1102 Exception’ on all GUI screens, validation rules, and documentation. Web services and Atom Feed are not impacted.
 
 
<b>
 
“The Solicitation Date in this IDV cannot be later than the Solicitation Date of an Award referencing this IDV. Please provide a Solicitation Date equal to or earlier than the Solicitation Date of the finalized Awards referencing this IDV.
 
</b>
 
 
 
<br>
 
Validation rules ‘DOD2H05’ and ‘DOD2H06’ shall be extended to Civilian Agencies.
 
 
 
 
</td>
 
</td>
  
Line 94: Line 88:
  
 
<td style="width:95px" valign="center">
 
<td style="width:95px" valign="center">
IAEENH-981 / IAEDEV-57386
+
IAEDEV-59967
 
</td>
 
</td>
  
<td>The IDV Reference PIID is not always being entered on a Part 8 BPA.
+
<td>UEI loading issue on records referencing an IDV
 
    
 
    
<td>FPDS shall add an information message when new BPAs are opened, reminding users to include the referenced IDV PIID if this is a BPA against an FSS.
+
<td>There are two issues related to UEI (SAM) on IDVs/Awards with referenced IDVs:
 +
<ol>
 +
<li>When a record is created from a template (that contains a referenced IDV), the original UEI value remains on the new record after record creation.</li>
 +
<li>UEI does not appear on a record after selecting the referenced IDV through the ellipsis button.</li>
 +
</ol>
  
</td>
+
Both defects will be resolved so that UEI is displaying correctly in all scenarios.</td>
  
 
<td align="center">No</td>
 
<td align="center">No</td>
Line 108: Line 106:
  
 
<td style="width:95px" valign="center">
 
<td style="width:95px" valign="center">
IAEENH-892 / IAEDEV-57380
+
IAEDEV-62064
 
</td>
 
</td>
  
<td>The Government Furnished Property (GFP) data element value does not propagate to modification records.
+
<td>Other Transaction Awards and Other Transaction IDVs can be created with the same PIID
 
    
 
    
<td>The functionality of modifications for Government Furnished Property (GFP) will be changed so the value from the base award is pre-populated on modifications.  
+
<td>There is no validation rule which prevents Other Transaction Awards and Other Transaction IDVs from being created with the same PIID. A validation rule will be implemented to enforce the PIID to be unique between Other Transaction Awards and Other Transaction IDVs.
</td>
 
 
 
<td align="center">No</td>
 
 
 
<tr>
 
 
 
<td style="width:95px" valign="center">
 
IAEENH-887 / IAEDEV-57379
 
</td>
 
 
 
<td>Add the “DoD Acquisition Program” data element to Other Transactions.
 
 
 
<td>The 'DoD Acquisition Program' data element in DoD Contract Actions will be added to the OT module.
 
 
 
 
</td>
 
</td>
  
Line 135: Line 119:
  
 
<td style="width:95px" valign="center">
 
<td style="width:95px" valign="center">
IAEENH-886 / IAEDEV-57378
+
IAEENH-735 / IAEDEV-62635
 
</td>
 
</td>
  
<td>Add two new data elements to FAADC:
+
<td>FAR Case 2018-018 - Federal Acquisition Regulation: Revision of Definition of "Commercial Item"
<ul>
 
<li> Indirect Cost Federal Share Amount
 
<li> Funding Opportunity Goals Text
 
<ul>
 
  
<td>Add two new data elements to the FAADC module that will allow users to enter “Indirect Cost Federal Share Amount” data within FAADC assistance actions and the “Funding Opportunity Goals Text” that is assigned by the agency from the funding opportunity announcement. DoD only.
+
<td>Per FAR Case 2018-018, data elements (10H, 8H, and 10J) with 'Commercial Item' will be renamed to ‘Commercial Products and Services’.
 
 
</td>
 
 
 
<td align="center">Yes</td>
 
 
 
<tr>
 
 
 
<td style="width:95px" valign="center">
 
IAEREQ-4326 / IAEDEV-60353
 
</td>
 
 
 
<td>Update Assistance Description maximum length to 18k characters
 
 
 
<td>In compliance with the new data standard requirements (IDD 2.1 from DAIMS 2.1), the maximum length for the Assistance for the FAADC module will be '18,000' characters.
 
  
 
</td>
 
</td>
Line 167: Line 133:
  
 
<td style="width:95px" valign="center">
 
<td style="width:95px" valign="center">
IAEDEV-60444
+
IAEENH-1018 / IAEDEV-57560
</td>
 
 
 
<td>Update 'CFDA' data element name to 'Assistance Listing'
 
 
 
<td>The CFDA label name in all the Record Type forms in FAADC have to comply with the Grants Data Standardization (GRM FIBF update) naming convention.
 
The CFDA label will be renamed to ASSISTANCE LISTING and add the note (formerly known as CFDA).
 
 
 
 
</td>
 
</td>
  
<td align="center">No</td>
+
<td>Updated Category 1 IT PSCs
  
<tr>
+
<td>Category 1 IT Product Service codes have been updated and will be implemented in FPDS. FPDS PSC Codes Crosswalk will be updated with the new information.
  
<td style="width:95px" valign="center">
 
IAEDEV-58911
 
 
</td>
 
</td>
  
<td>The state, zip, and country are not propagating on a 'Correct' on a NON-SAM Exception DUNS to SAM Exception record.
+
<td align="center">Yes</td>
 
 
<td>The system will be modified to ensure that on a NON-SAM Exception DUNS to SAM Exception record, that the state, zip, and country propagates on a 'Correct'.
 
 
 
</td>
 
 
 
<td align="center">No</td>
 
  
 
<tr>
 
<tr>
  
 
<td style="width:95px" valign="center">
 
<td style="width:95px" valign="center">
IAEDEV-58912
+
IAEENH-1071 / IAEDEV-64340
 
</td>
 
</td>
  
<td>The DUNS and UEI value open on a Delivery Order (DO) and BPA Calls.
+
<td>IAEPOL DFARS Case 2022-D012, New Qualifying Country - Lithuania
  
<td>The functionality will be updated to ensure that DUNS and UEI values do not open on DOs and BPA Calls with a SAM Exception when selecting 'Correct'.
+
<td>Per DFARS case 2022-D012, Lithuania will be added to the list of qualifying countries associated with ‘Country of Product / Service Origin’ validation rule DoD9H03. The validation rule will be updated to the language below:
 +
<ul>
 +
<li>If the "Country of Product / Service Origin" is 'Australia', 'Austria', 'Belgium', 'Canada', 'Czech Republic', 'Denmark', 'Egypt', 'Estonia', 'Germany', 'Finland', 'France', 'Greece', 'Israel', 'Italy', 'Japan', 'Latvia', ‘Lithuania’, 'Luxembourg', 'Netherlands', 'Norway', 'Poland', 'Portugal', 'Slovenia', 'Spain', 'Sweden', 'Switzerland', 'Turkey', or 'United Kingdom of Great Britain and Northern Ireland' the "Place of Manufacture" can only be 'Mfg Outside U.S -Qualifying Country (DOD only)' or 'Not a Manufactured End Product'.</li>
 +
<ul>
 
</td>
 
</td>
  
<td align="center">No</td>
+
<td align="center">Yes</td>
 
 
<tr>
 
 
 
<td style="width:95px" valign="center">
 
IAEDEV-58903
 
</td>
 
 
 
<td>The SAM Exception value is not being retained on ‘Save Draft’.
 
 
 
<td>The system will ensure that when creating a Part 8 BPA with a SAM Exception, the value will be retained when selecting ‘Save Draft’.
 
 
 
</td>
 
 
 
<td align="center">No</td>
 
 
 
<tr>
 
 
 
<td style="width:95px" valign="center">
 
IAEDEV-59442
 
</td>
 
 
 
<td>The SAM-exception button is not enabled on the initial load of a GUI Service URL.
 
 
 
<td>The system will be updated to ensure that the SAM-exception data element button is enabled, upon initial load of a GUI screen.
 
 
 
</td>
 
 
 
<td align="center">No</td>
 
 
 
<tr>
 
 
 
<td style="width:95px" valign="center">
 
IAEDEV-59961
 
</td>
 
 
 
<td>FAADC Business Services ‘Create’ request cannot be processed when the Small Business Indicator value is ‘Small Business’ and the ‘vendorOrganizationFactors’ tag is not included in the request.
 
 
 
<td>The system will be updated so a FAADC ‘Create’ request can be processed when the Small Business Indicator value is ‘Small Business’ and the ‘vendorOrganizationFactors’ tag is not included in the request.
 
</td>
 
 
 
<td align="center">No</td>
 
  
 
<tr>
 
<tr>

Revision as of 21:51, 9 February 2022

Schedule

DescriptionStart Date End Date
Beta DeploymentMarch 11, 2022March 11, 2022
Government Acceptance Testing March 21, 2022March 25, 2022
Production Deployment April 2, 2022April 2, 2022

Document Changes

DocumentationChanges Required
XML SpecificationsNo
Web ServicesYes
Data DictionaryYes
NASA Specific Data DictionaryNo
Use Case SummaryYes
Validation RulesYes
ezSearchYes
Atom FeedsYes
Online HelpYes
User ManualYes

SPR Listing

SPR #Enhancement/ProblemSolutionImpact to Users and Integrators

IAEDEV-60364 / IAEDEV-60365

FPDS and FAADC Phase 3 UEI Enhancements This is the third and final phase of the DUNS to UEI transition for both FPDS and FAADC systems. This will make the UEI element a mandatory field. All instances of the DUNS data element and associated values will be removed and the UEI (SAM) field will be renamed to ‘Unique Entity ID’ (short: ‘UEI’) from both systems, and the (GUI Screens, GUI Services, validation rules, documentation, etc.).

WSDLs will not be updated to remove DUNS-related tags, but the tags will be disabled from user entry/submission and users must begin using the UEI tag (FPDS: <genericString02>; FAADC: <UEI>) to submit a vendor for transactions.

Both FPDS and FAADC Atom Feeds will be updated so that DUNS values are not sent in DUNS-related tags. All DUNS-related tags will appear as null/empty in the Atom Feeds.
Yes

IAEDEV-64036 / IAEDEV-64037

Decommissioning of the D&B API for both FPDS and FAADC systems The Dun & Bradstreet API used to retrieve new SAM Exception entities (previously not found in FPDS/FAADC) will be decommissioned and a new SAM API will be used to retrieve all SAM Exception entity information using a UEI (SAM) value, instead of UEI (DUNS). No

IAEDEV-59966

ezSearch ‘ICD’ tab Search Issues UEI (SAM) values cannot be used to search in the ‘ICD’ tab of ezSearch. The system will be updated to ensure UEI values are indexed and searchable from the ezSearch ‘ICD’ tab. Yes

IAEDEV-62921

‘SAM Exception’ label update in FPDS/FAADC After completion of the DUNS to UEI transition, SAM Exception entities will be required to go to SAM to generate a UEI value, for record creation purposes in FPDS. The ‘SAM Exception’ label will be updated to ‘FAR 4.1102 Exception’ on all GUI screens, validation rules, and documentation. Web services and Atom Feed are not impacted. No

IAEDEV-59967

UEI loading issue on records referencing an IDV There are two issues related to UEI (SAM) on IDVs/Awards with referenced IDVs:
  1. When a record is created from a template (that contains a referenced IDV), the original UEI value remains on the new record after record creation.
  2. UEI does not appear on a record after selecting the referenced IDV through the ellipsis button.
Both defects will be resolved so that UEI is displaying correctly in all scenarios.
No

IAEDEV-62064

Other Transaction Awards and Other Transaction IDVs can be created with the same PIID There is no validation rule which prevents Other Transaction Awards and Other Transaction IDVs from being created with the same PIID. A validation rule will be implemented to enforce the PIID to be unique between Other Transaction Awards and Other Transaction IDVs. Yes

IAEENH-735 / IAEDEV-62635

FAR Case 2018-018 - Federal Acquisition Regulation: Revision of Definition of "Commercial Item" Per FAR Case 2018-018, data elements (10H, 8H, and 10J) with 'Commercial Item' will be renamed to ‘Commercial Products and Services’. No

IAEENH-1018 / IAEDEV-57560

Updated Category 1 IT PSCs Category 1 IT Product Service codes have been updated and will be implemented in FPDS. FPDS PSC Codes Crosswalk will be updated with the new information. Yes

IAEENH-1071 / IAEDEV-64340

IAEPOL DFARS Case 2022-D012, New Qualifying Country - Lithuania Per DFARS case 2022-D012, Lithuania will be added to the list of qualifying countries associated with ‘Country of Product / Service Origin’ validation rule DoD9H03. The validation rule will be updated to the language below:
  • If the "Country of Product / Service Origin" is 'Australia', 'Austria', 'Belgium', 'Canada', 'Czech Republic', 'Denmark', 'Egypt', 'Estonia', 'Germany', 'Finland', 'France', 'Greece', 'Israel', 'Italy', 'Japan', 'Latvia', ‘Lithuania’, 'Luxembourg', 'Netherlands', 'Norway', 'Poland', 'Portugal', 'Slovenia', 'Spain', 'Sweden', 'Switzerland', 'Turkey', or 'United Kingdom of Great Britain and Northern Ireland' the "Place of Manufacture" can only be 'Mfg Outside U.S -Qualifying Country (DOD only)' or 'Not a Manufactured End Product'.
Yes