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

From FPDS-NG

(→‎SPR Listing)
 
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
__NOEDITSECTION__
 
==Schedule==
 
==Schedule==
 
<TABLE  id="box-table-a" border=2>
 
<TABLE  id="box-table-a" border=2>
Line 16: Line 17:
 
<tr><td nowrap>NASA Specific Data Dictionary</td><td align="center">No</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">No</td></tr>
 
<tr><td nowrap>Use Case Summary</td><td align="center">No</td></tr>
−
<tr><td nowrap>Validation Rules</td><td align="center">No</td></tr>
+
<tr><td nowrap>Validation Rules</td><td align="center">Yes</td></tr>
 
<tr><td nowrap>Online Help</td><td align="center">No</td></tr>
 
<tr><td nowrap>Online Help</td><td align="center">No</td></tr>
 
<tr><td nowrap>Computer-Based Training</td><td align="center">No</td></tr>
 
<tr><td nowrap>Computer-Based Training</td><td align="center">No</td></tr>
Line 34: Line 35:
 
*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 ‘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”.
 
*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”.
 +
*Upon ‘Approve’ or ‘Correct’ of an Award or IDV Vendor Modification, FPDS-NG shall propagate the respective vendor information and “Contracting Officers Business Size Selection” to its successive Modifications based on the “Date Signed” and “Reason for Modification” on the documents.
 
</td>
 
</td>
 
<td align="center">No</td>
 
<td align="center">No</td>
Line 39: Line 41:
  
 
<tr>
 
<tr>
−
<td style="width:95px" valign="top">FPDSHD-66211</td>
+
<td style="width:95px" valign="top">FPDSNG-3624, FPDSNG-3625</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">FAST book data has to be loaded into FPDS-NG and the TAS codes will be validated against the FAST book.</td>
 
<td valign="top">
 
<td valign="top">
−
*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.  
+
*FPDS-NG shall load FAST book TAS codes into FPDS-NG.
−
*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.  
+
*FPDS-NG shall validate the TAS codes against the FAST book and display an error message "The “Treasury Account Symbol” code is not valid. Please enter a valid “Treasury Account Symbol” code or contact your Agency Administrator.” if the code submitted does not exist in FAST book.
−
*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.  
+
The above validation rule is applicable for the following services:
−
*FPDS-NG shall send the email only to Active Users having “Receive Email Notification” as checked.
+
<TABLE border=0>
−
</td>
+
<tr><td>Business Services</td>
−
<td align="center">No</td>
+
<td>isComplete, isExistingAwardComplete, isExistingIDVComplete,approve and correct</td>
 +
<td> Version 1.3 & 1.4</td>
 +
</tr>
 +
<tr><td>Gui Services</td>
 +
<td>Correct and validate</td>
 +
<td>Version 1.3 & 1.4</td>
 +
</tr>
 +
<tr>
 +
<td>Web Portal</td>
 +
<td>Correct ,validate and approve</td>
 +
<td>Version 1.3 & 1.4</td>
 
</tr>
 
</tr>
−
<tr>
+
</TABLE>  
−
<td style="width:95px" valign="top">FPDSNG-163</td>
 
−
<td valign="top">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”.
 
−
</td>
 
−
<td valign="top">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)
 
 
</td>
 
</td>
 
<td align="center">No</td>
 
<td align="center">No</td>
 
</tr>
 
</tr>

Latest revision as of 21:57, 2 June 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 RulesYes
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”.
  • Upon ‘Approve’ or ‘Correct’ of an Award or IDV Vendor Modification, FPDS-NG shall propagate the respective vendor information and “Contracting Officers Business Size Selection” to its successive Modifications based on the “Date Signed” and “Reason for Modification” on the documents.
 No
FPDSNG-3624, FPDSNG-3625 FAST book data has to be loaded into FPDS-NG and the TAS codes will be validated against the FAST book.
  • FPDS-NG shall load FAST book TAS codes into FPDS-NG.
  • FPDS-NG shall validate the TAS codes against the FAST book and display an error message "The “Treasury Account Symbol” code is not valid. Please enter a valid “Treasury Account Symbol” code or contact your Agency Administrator.” if the code submitted does not exist in FAST book.

The above validation rule is applicable for the following services:

Business Services isComplete, isExistingAwardComplete, isExistingIDVComplete,approve and correct Version 1.3 & 1.4
Gui Services Correct and validate Version 1.3 & 1.4
Web Portal Correct ,validate and approve Version 1.3 & 1.4
No
Retrieved from "https://www.fpds.gov/wiki/index.php?title=V1.4_SP3.0&oldid=3406"