Difference between revisions of "V1.4 SP3.0"

From FPDS-NG

(→‎Document Changes)
(→‎SPR Listing)
Line 26: Line 26:
 
<th width=11% align="center"><b>SPR #</b></th><th width=35% align="center"><b>Problem</b></th><th width=40% align="center"><b>Solution</b></th><th width=10% align="center"><b>Impact to Users and Integrators</b></th>
 
<th width=11% align="center"><b>SPR #</b></th><th width=35% align="center"><b>Problem</b></th><th width=40% align="center"><b>Solution</b></th><th width=10% align="center"><b>Impact to Users and Integrators</b></th>
 
<tr>
 
<tr>
−
<td style="width:95px" valign="top">FPDSHD-54414</td>
+
<td style="width:95px" valign="top">FPDSHD-71390,
−
<td valign="top">Disabled users are able to submit data to FPDS-NG and create documents through Business Services.</td>  
+
FPDSHD-69612,
 +
FPDSHD-69190,
 +
FPDSHD-72585,
 +
FPDSHD-68838
 +
</td>
 +
<td valign="top">User reported an issue with the Novation Agreement functionality. A new Novation on the IDV updated all the Delivery Order Modifications against that IDV regardless of the date signed.
 +
The IDV is NAS598145 and the Novation mod is 26 with a date signed of 03/23/2010.
 +
</td>  
 
<td valign="top">
 
<td valign="top">
−
*FPDS-NG shall perform authentication and authorization for all the requests through Business Services.
+
*Upon ‘Approve’ or ‘Correct’ of an IDV Vendor Modification, FPDS-NG shall propagate the respective vendor information and the IDV Modification Number to its successive Modifications and Referencing Orders based on the “Date Signed” and “Reason for Modification” on the documents.
−
*The new rule '''“Unauthorized user. Your FPDS-NG Service Originator User ID is disabled.  Please contact your FPDS-NG system administrator.”''' shall be fire when the Service Originator ID has been disabled.
+
*Upon ‘Correct’ of a Delivery Order, FPDS-NG Shall fetch the respective vendor information from the latest Vendor Modification or the base of the referenced IDV based on the “Date Signed”.
−
*Authorization error '''“Operation failed due to Authorization Failure”''' shall fire when the Service Originator ID does not have the privileges required or does not exist.
+
</td>
−
*Authentication error '''“Operation failed due to Authentication Failure”''' shall fire when the User ID does not exist or is disabled.
 
−
*User Locked error '''“For security purposes, user account '<<ID>>' has been disabled and locked from use because of five (5) unsuccessful log-in attempts. Please contact your FPDS-NG System administrator to have the user account unlocked.”''' Shall fire if the User ID or Service Originator ID is locked.
 
−
*Inactivity error '''“For security purposes, user account '<<ID>>' has been disabled due to ninety (90) days of inactivity. Therefore, access to FPDS-NG is not available, until the user account is re-enabled. Please contact your agency's FPDS-NG system administrator to have the user account re-enabled.”''' shall fire when User ID or Service Originator ID is inactive due to 90 days of inactivity</td>
 
 
<td align="center">No</td>
 
<td align="center">No</td>
 
</tr>
 
</tr>

Revision as of 22:49, 6 May 2010

Schedule

DescriptionStart Date End Date
BETA Installation Monday May 24, 2010Monday May 24, 2010
Functional Qualification TestingTuesday May 25, 2010Thursday May 27, 2010
Installation in ProductionFriday June 04, 2010Friday June 04, 2010

Document Changes

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

SPR Listing

SPR #ProblemSolutionImpact to Users and Integrators
FPDSHD-71390,

FPDSHD-69612, FPDSHD-69190, FPDSHD-72585, FPDSHD-68838

User reported an issue with the Novation Agreement functionality. A new Novation on the IDV updated all the Delivery Order Modifications against that IDV regardless of the date signed.

The IDV is NAS598145 and the Novation mod is 26 with a date signed of 03/23/2010.

  • Upon ‘Approve’ or ‘Correct’ of an IDV Vendor Modification, FPDS-NG shall propagate the respective vendor information and the IDV Modification Number to its successive Modifications and Referencing Orders based on the “Date Signed” and “Reason for Modification” on the documents.
  • Upon ‘Correct’ of a Delivery Order, FPDS-NG Shall fetch the respective vendor information from the latest Vendor Modification or the base of the referenced IDV based on the “Date Signed”.
 No
FPDSHD-66211 During a Transfer Action, the users under receiving offices and agencies are getting emails even when they are end dated or they don’t have the privilege.
  • FPDS-NG shall send an email when a contract is transferred to the users of the receiving and transferring agency having “Agency System Administrator” privileges and users of the office under that agency having “Contracting Office Administrator” privileges.
  • For DoD Agencies, FPDS-NG shall send the email to users of the receiving and transferring department having “Department System Administrator” privileges if the respective agency does not have any users with “Agency System Administrator” privileges. FPDS-NG shall send the email to fpdssupport@gcefederal.com if there are no users with “Department System Administrator” privileges for the Department and no users with “Agency System Administrator Privileges” for the Agency. This applies to both receiving and transferring departments.
  • For Civilian Agencies, FPDS-NG shall send the email to users of receiving and transferring Department having “Agency System Administrator” privileges if the respective agency does not have any users with “Agency System Administrator” privileges. FPDS-NG shall send the email to fpdssupport@gcefederal.com if there are no users having “Agency System Administrator” privileges for the Agency or Department. This applies to both receiving and transferring departments.
  • FPDS-NG shall send the email only to Active Users having “Receive Email Notification” as checked.
 No
FPDSNG-163 New rules were identified between competition elements during V1.4 FQT testing which will ensure that FPDS-NG shall not allow the contracts to be approved or corrected with the following combinations.
  • “Extent Competed” as ‘Full and Open Competition after exclusion of sources’ and “Solicitation Procedures” as ‘Only One Source’.
  • “Fair Opportunity/Limited Sources” as ‘Only One Source’ and “Number Of Offers” as value other than ‘1’.
  • Invalid combinations of “Country of Product or Service Origin”, “Place of Manufacture” and “Place of Performance”.
 FPDS-NG shall display following rules to restrict users from entering the above mentioned invalid data combinations on base Awards or IDVs.
  • “If “Solicitation Procedures” is ‘Only One Source’, then “Extent Competed” must be ‘Not Competed’ or ‘Not available for Competition’.” ( Version 1.4 and Post-Clod only for lower Versions)
  • “If “Fair Opportunity/Limited Sources” is ‘Only One Source - Other’, then “Number of Offers” must be 1.” ( Version 1.4 and Post-Clod only for lower Versions)
  • “If “Country of Product or Service Origin” is ‘US’, then “Place of Manufacture” can only be ‘Performed or Manufactured in US, but services performed by a foreign concern or more than 50% foreign content’, ‘Not a manufactured end product’, or ‘Mfg in U.S.’.” ( Version 1.4 Only)
  • “If “Country of Product or Service Origin” is other than ‘US’, then “Place of Manufacture” can not be ‘Mfg in U.S.’.” ( Version 1.4 Only)
 No
Retrieved from "https://www.fpds.gov/wiki/index.php?title=V1.4_SP3.0&oldid=3384"