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

From FPDS-NG
Line 42: Line 42:
 
<td style="width:95px" valign="top">FPDSHD-66211</td>
 
<td style="width:95px" valign="top">FPDSHD-66211</td>
 
<td valign="top">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.</td>
 
<td valign="top">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.</td>
−
<td valign="top">• FPDS-NG shall send an email when a contract is transferred to the users of the receiving agency having “Agency System Administrator” privileges and to the users of the receiving agency and office having “Contracting Office Administrator” privileges.  
+
<td valign="top">
−
• For DoD Agencies, FPDS-NG shall send the email to users of the receiving department having “Department System Administrator” if the receiving agency does not have any users with “Agency System Administrator” privileges and to fpdssupport@gcefederal.com if there are no users with “Department System Administrator” privileges and no users with “Agency System Administrator Privileges” for the receiving Department and Agency.
+
*FPDS-NG shall send an email when a contract is transferred to the users of the receiving agency having “Agency System Administrator” privileges and to the users of the receiving agency and office having “Contracting Office Administrator” privileges.  
−
• For Civilian Agencies, FPDS-NG shall send the email to users having “Agency System Administrator” privileges for the Department if the receiving agency does not have any users with “Agency System Administrator” privileges and to fpdssupport@gcefederal.com if there are no users having “Agency System Administrator” privileges for the receiving Agency or receiving Department.
+
*For DoD Agencies, FPDS-NG shall send the email to users of the receiving department having “Department System Administrator” if the receiving agency does not have any users with “Agency System Administrator” privileges and to fpdssupport@gcefederal.com if there are no users with “Department System Administrator” privileges and no users with “Agency System Administrator Privileges” for the receiving Department and Agency.
−
• FPDS-NG shall send the email only to Active Users having “Receive Email Notification” as checked.
+
*For Civilian Agencies, FPDS-NG shall send the email to users having “Agency System Administrator” privileges for the Department if the receiving agency does not have any users with “Agency System Administrator” privileges and to fpdssupport@gcefederal.com if there are no users having “Agency System Administrator” privileges for the receiving Agency or receiving Department.
 +
*FPDS-NG shall send the email only to Active Users having “Receive Email Notification” as checked.
 
</td>
 
</td>
 
<td align="center">No</td>
 
<td align="center">No</td>
Line 52: Line 53:
 
<td style="width:95px" valign="top">FPDSIRB-121</td>
 
<td style="width:95px" valign="top">FPDSIRB-121</td>
 
<td valign="top">The user reported the following rule is not firing correctly and FPDSNG is allowing more than 2 characters. </td>
 
<td valign="top">The user reported the following rule is not firing correctly and FPDSNG is allowing more than 2 characters. </td>
−
<td valign="top">FPDS-NG shall not allow creation of new DoD Modifications referencing DoD IDVs having length of “Modification Number” greater than 2 through the following rules:
+
<td valign="top">
 +
FPDS-NG shall not allow creation of new DoD Modifications referencing DoD IDVs having length of “Modification Number” greater than 2 through the following rules:
 +
<br/>
 
Version 1.4 – “If the transaction is a modification of a Delivery/Task Order or BPA Call referencing an IDV awarded by DoD then the Mod number cannot be more than 2 characters in length.”  
 
Version 1.4 – “If the transaction is a modification of a Delivery/Task Order or BPA Call referencing an IDV awarded by DoD then the Mod number cannot be more than 2 characters in length.”  
 +
<br/>
 
Version 1.3 - “If the transaction is a modification of a Delivery/Task Order referencing an IDV awarded by DoD then the Mod number cannot be more than 2 characters in length.”
 
Version 1.3 - “If the transaction is a modification of a Delivery/Task Order referencing an IDV awarded by DoD then the Mod number cannot be more than 2 characters in length.”
 
</td>
 
</td>

Revision as of 17:45, 16 April 2010

Schedule

DescriptionStart Date End Date
BETA Installation Monday April 26, 2010Monday April 26, 2010
Functional Qualification TestingTuesday April 27, 2010Thursday April 29, 2010
Installation in ProductionFriday May 07, 2010Friday May 07, 2010

Document Changes

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

SPR Listing

SPR #ProblemSolutionImpact to Users and Integrators
FPDSHD-54414 Disabled users are able to submit data to FPDS-NG and create documents through Business Services.
  • FPDS-NG shall perform authentication and authorization for all the requests through Business Services.
  • 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.
  • 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.
  • 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
 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 agency having “Agency System Administrator” privileges and to the users of the receiving agency and office having “Contracting Office Administrator” privileges.
  • For DoD Agencies, FPDS-NG shall send the email to users of the receiving department having “Department System Administrator” if the receiving agency does not have any users with “Agency System Administrator” privileges and to fpdssupport@gcefederal.com if there are no users with “Department System Administrator” privileges and no users with “Agency System Administrator Privileges” for the receiving Department and Agency.
  • For Civilian Agencies, FPDS-NG shall send the email to users having “Agency System Administrator” privileges for the Department if the receiving agency does not have any users with “Agency System Administrator” privileges and to fpdssupport@gcefederal.com if there are no users having “Agency System Administrator” privileges for the receiving Agency or receiving Department.
  • FPDS-NG shall send the email only to Active Users having “Receive Email Notification” as checked.
 No
FPDSIRB-121 The user reported the following rule is not firing correctly and FPDSNG is allowing more than 2 characters.

FPDS-NG shall not allow creation of new DoD Modifications referencing DoD IDVs having length of “Modification Number” greater than 2 through the following rules:
Version 1.4 – “If the transaction is a modification of a Delivery/Task Order or BPA Call referencing an IDV awarded by DoD then the Mod number cannot be more than 2 characters in length.”
Version 1.3 - “If the transaction is a modification of a Delivery/Task Order referencing an IDV awarded by DoD then the Mod number cannot be more than 2 characters in length.”

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.

1) “Extent Competed” as ‘Full and Open Competition after exclusion of sources’ and “Solicitation Procedures” as ‘Only One Source’. 2) “Fair Opportunity/Limited Sources” as ‘Only One Source’ and “Number Of Offers” as value other than ‘1’. 3) 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.

1) “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) 2) “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) 3) “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) 4) “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_SP2.0&oldid=3341"