Notice: Trying to access array offset on value of type null in /opt/mediawiki/includes/profiler/SectionProfiler.php on line 99

Notice: Trying to access array offset on value of type null in /opt/mediawiki/includes/profiler/SectionProfiler.php on line 99

Notice: Trying to access array offset on value of type null in /opt/mediawiki/includes/profiler/SectionProfiler.php on line 100

Notice: Trying to access array offset on value of type null in /opt/mediawiki/includes/profiler/SectionProfiler.php on line 100

Notice: Trying to access array offset on value of type null in /opt/mediawiki/includes/profiler/SectionProfiler.php on line 101

Notice: Trying to access array offset on value of type null in /opt/mediawiki/includes/profiler/SectionProfiler.php on line 101
Difference between revisions of "V1.5 SP 13.0"

Difference between revisions of "V1.5 SP 13.0"

From FPDS-NG

(Blanked the page)
(Tag: Blanking)
Line 1: Line 1:
__NOEDITSECTION__
 
==Schedule==
 
<TABLE  id="box-table-a" border=2>
 
<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>
 
<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>March 21, 2022</td><td nowrap>March 25, 2022</td></tr>
 
<tr><td nowrap>Production Deployment </td><td nowrap>April 2, 2022</td><td nowrap>April 2, 2022</td></tr>
 
</table>
 
  
==Document Changes==
 
<TABLE border=2 id="box-table-a">
 
<tr><th align="center"><b>Documentation</b></th><th align="center"><b>Changes Required</b></th></tr>
 
<tr><td nowrap>XML Specifications</td><td align="center">No</td></tr>
 
<tr><td nowrap>Web Services</td><td align="center">Yes</td></tr>
 
<tr><td nowrap>Data Dictionary</td><td align="center">Yes</td></tr>
 
<tr><td nowrap>NASA Specific Data Dictionary</td><td align="center">No</td></tr>
 
<tr><td nowrap>Use Case Summary</td><td align="center">Yes</td></tr>
 
<tr><td nowrap>Validation Rules</td><td align="center">Yes</td></tr>
 
<tr><td nowrap>ezSearch</td><td align="center">Yes</td></tr>
 
<tr><td nowrap>Atom Feeds</td><td align="center">Yes</td></tr>
 
<tr><td nowrap>Online Help</td><td align="center">Yes</td></tr>
 
<tr><td nowrap>User Manual</td><td align="center">Yes</td></tr>
 
 
</table>
 
==SPR Listing==
 
<TABLE id="box-table-a" border=2 style="width: 1080px">
 
<th width=18% align="center"><b>SPR #</b></th><th width=30% align="center"><b>Enhancement/Problem</b></th><th width=38% align="center"><b>Solution</b></th><th width=25% align="center"><b>Impact to Users and Integrators</b></th>
 
<tr>
 
 
 
<td style="width:95px" valign="center">
 
IAEDEV-60364 / IAEDEV-60365
 
</td>
 
 
<td>FPDS and FAADC Phase 3 UEI Enhancements
 
 
<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.).
 
 
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">Yes</td>
 
 
<tr>
 
 
<td style="width:95px" valign="center">
 
IAEDEV-64036 / IAEDEV-64037
 
</td>
 
 
<td>Decommissioning of the D&B API for both FPDS and FAADC systems
 
 
 
<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 align="center">No</td>
 
 
<tr>
 
 
<td style="width:95px" valign="center">
 
IAEDEV-59966
 
</td>
 
 
<td>ezSearch ‘ICD’ tab Search Issues
 
 
 
<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 align="center">Yes</td>
 
 
<tr>
 
 
<td style="width:95px" valign="center">
 
IAEDEV-62921
 
</td>
 
 
<td>‘SAM Exception’ label update in FPDS/FAADC
 
 
 
<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.
 
</td>
 
 
<td align="center">No</td>
 
 
<tr>
 
 
<td style="width:95px" valign="center">
 
IAEDEV-59967
 
</td>
 
 
<td>UEI loading issue on records referencing an IDV
 
 
 
<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>
 
 
Both defects will be resolved so that UEI is displaying correctly in all scenarios.</td>
 
 
<td align="center">No</td>
 
 
<tr>
 
 
<td style="width:95px" valign="center">
 
IAEDEV-62064
 
</td>
 
 
<td>Other Transaction Awards and Other Transaction IDVs can be created with the same PIID
 
 
 
<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">Yes</td>
 
 
<tr>
 
 
<td style="width:95px" valign="center">
 
IAEENH-1018 / IAEDEV-57560
 
</td>
 
 
<td>Updated Category 1 IT PSCs
 
 
<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>
 
 
<td align="center">Yes</td>
 
 
<tr>
 
 
<td style="width:95px" valign="center">
 
IAEENH-1071 / IAEDEV-64340
 
</td>
 
 
<td>IAEPOL DFARS Case 2022-D012, New Qualifying Country - Lithuania
 
 
<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 align="center">Yes</td>
 
 
<tr>
 

Revision as of 19:34, 2 March 2022