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

From FPDS-NG

 
 
(12 intermediate revisions by the same user not shown)
Line 38: Line 38:
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<td style="width:95px" valign="top">FPDSHD-58307, FPDSIRB-129</td>
+
<td style="width:95px" valign="top">FPDSHD-54136</td>
<td valign="top">The following table contains a list of expired generic DUNS numbers and users who are allowed to create contracts using the duns.
+
<td valign="top">The user reported the issue of not being able to correct the FSS ‘GS06F0006L’. The user was getting a ‘System Error’ on correcting the FSS.
<table>
 
<tr><th>DUNS Number</th><th>Vendor Name</th></tr>
 
<tr><td>167445977</td><td>GPC SMALL DISADVANTAGED BUSINESS (SDB)</td></tr>
 
<tr><td>167445993</td><td>GPC JAVITS-WAGNER-O-DAY (JWOD)</td></tr>
 
<tr><td>167446025</td><td>GPC SERVICE DISABLED VET OWNED SB (SDVOSB)</td></tr>
 
<tr><td>167446058</td><td>GPC HUBZONE SB</td></tr>
 
<tr><td>167446116</td><td>GPC Women-owned SB</td></tr>
 
<tr><td>167446173</td><td>GPC DOCUMENT AUTOMATION & PRODUCTION SERVICE (DAPS)</td></tr>
 
<tr><td>167446223</td><td>GPC SF 1556 TRAINING</td></tr>
 
</table>
 
 
</td>
 
</td>
<td>*FPDS-NG shall display the following Validation rule when the Date Signed on the contract is greater than the expired date for these generic DUNS.
+
<td>  
'''The selected vendor with “DUNS Number” <<dunsNumber>> has expired on <<dateSigned>>. Please select a valid vendor.'''.
+
*On ‘Correct’ of an IDV, FPDS-NG shall ensure that the IDV is corrected successfully and ‘System Error’ is not displayed.
*The above requirement shall apply for ‘Validate’, ‘Approve’ and ‘Correct’ operations through GUI Services and Web Portal. It shall apply on ‘Correct’ only if the “Date Signed” or DUNS Number is changed.  
+
*On ‘Correct’ of an IDV, FPDS-NG shall ensure that all ‘Not Required’ data elements on the referencing Awards and IDVs are updated with the values from the referenced IDV successfully.
*The above requirement shall apply to ‘isComplete’, ‘isExistingIDVComplete’, ‘isExistingAwardComplete’, ‘approve’ and ‘correct’ operations through Business Services. It shall apply on ‘Correct’ operation only if the “Date Signed” or DUNS Number is changed.  
+
*On ‘Correct’ of an IDV, FPDS-NG shall ensure that all ‘Not Required’ data elements on the modifications are updated with the values from the IDV successfully.
*The above requirements shall apply only on the following base documents and their vendor modifications for all versions:
+
*All above requirements shall apply on all Versions through Web Portal, GUI and Business Services.
'''Award:''' PO, DCA, OT Agreement, Cooperative Agreement, Grant For Research, Intragovernmental, Funded Space Act Agreement, Training Grant.
 
'''IDV:''' IDC, BOA, Stand-alone BPA, GWAC, FSS, OT IDV.
 
*The Version 1.4 and 1.3 Validation Rules document shall be updated to include the changes.  
 
 
</td>
 
</td>
 
<td align="center">No</td>
 
<td align="center">No</td>
 
</tr>
 
</tr>
<td style="width:95px" valign="top">FPDSHD-72449, FPDSHD-70707, FPDSHD-74439</td>
+
<tr>
<td valign="top">For “Date Signed” prior to 4th of August 2006, both of the following Validation Rules fire making it impossible to ‘Approve’ or ‘Correct’ a document.
+
<td style="width:95px" valign="top">FPDSHD-66884</td>
 +
<td valign="top">The user is not able to login successfully using the session expired screen when his/her password was reset by the Agency Administrator.
 +
</td>
 +
<td>
 +
*From the session expired screen, FPDS-NG shall redirect the user to the ‘Reset Password’ screen when the password of the user is reset by the administrator and the password entered by the user is correct.
 +
*On the session expired screen, FPDS-NG shall display the following inactivity or user locked message when the user tries to login based on the profile of the user.
  
10C20 – “If "Other than Full and Open Competition" is 'Authorized by Statute' or 'SAP Non-Competition', then "Local Area Set Aside" must be 'No'.”
+
'''“For security purposes, user account '<userID>' 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 FPDS-NG System administrator to have the user account re-enabled.”'''
  
10U02 – “The Local Area Set Aside must not be selected if the “Date Signed” is prior to "08/04/2006".”
+
'''“For security purposes, user account '<userID>' 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.”'''
 +
</td>
 +
<td align="center">No</td>
 +
</tr>
 +
<tr>
 +
<td style="width:95px" valign="top">FFPDSHD-60169</td>
 +
<td valign="top">
 +
The user is not able to successfully correct a migrated contract which is signed on or after 1st October 2003 as the data element “Description of Requirements” is closed for editing and the following mandatory message fires:
 +
'''“The Mandatory element: "descriptionOfContractRequirement" is missing for Contract Type: IDV and Contract Action Type: IDC.”'''
 
</td>
 
</td>
<td>
+
<td>  
*FPDS-NG shall suppress the following Validation Rule for contracts having “Date Signed” prior to ‘08/04/2006’ for all versions. The rule shall continue to fire for contracts having “Date Signed” greater than ‘08/04/2006’.
+
*FPDS-NG shall allow the users to edit the data element “Description of Requirement” through front end on DoD contracts prepared by “DOD_ MIGRATOR” or “MIGRATOR”.
  
‘10C20’ – “If "Other than Full and Open Competition" is 'Authorized by Statute' or 'SAP Non-Competition', then "Local Area Set Aside" must be 'No'.
+
*FPDS-NG shall accept the value for the data element “Description of Requirement” only if the “Date Signed” is equal to or later than 1st October 2003.
  
*FPDS-NG shall ensure that the following validation rules are displayed on Version 1.4 based on the “Date Signed” of the contract:
+
*The following warning message shall not be displayed for DoD contracts prepared by “DOD_ MIGRATOR” or “MIGRATOR” and the “Date Signed” is equal to or later than 1st October 2003.
 +
.
  
‘10U01’ – “The Local Area Set Aside” must be selected if the “Date Signed” is later than  "08/04/2006".”
+
'''5004 – “The description of contract requirement cannot be changed for DOD documents that were Migrated.”'''
  
‘10U02’ – “The Local Area Set Aside” must not be selected if the “Date Signed” is prior to "08/04/2006".
+
*All the above requirements are applicable on ‘Correct’ through Web Portal and Business Services.
  
*The above validation rules shall fire for ‘Validate’, ‘Approve’ and ‘Correct’ operations through GUI Services and Web Portal.
+
*All the above requirements are applicable on finalized bases and modifications of Awards and IDVs on all versions. 
*The above validation rules shall fire for‘isComplete’, ‘isExistingIDVComplete’, ‘isExistingAwardComplete’, ‘approve’ and ‘correct’ operations through Business Services.
+
</td>
*The Version 1.4 and 1.3 Validation Rules document shall be updated to include the changes.
+
<td align="center">No</td>
*FPDS-NG shall have a Data Management fix to remove all the values for “Local Area Set Aside” from contracts having “Date Signed” prior than ‘08/04/2006’.
+
</tr>
 +
<tr>
 +
<td style="width:95px" valign="top">FPDSNG-3639</td>
 +
<td valign="top">The labels for Place of Performance state, location and country code have to be moved to be placed above the text boxes.
 +
</td>
 +
<td>
 +
*FPDS-NG shall update and re-arrange the Principal Place of Performance labels for (State, Location, Country) to be placed above the text boxes on the Award and IDV Screens.
 +
*The above requirement shall apply to Awards on all Versions and 1.4 Other Transactions IDV.
 +
*The CBT Training material and the V 1.4/1.3 Users Manual shall be updated to update the screenshots with the updated position for the Principal Place of Performance labels.
 
</td>
 
</td>
<td valign="center">No</td>
+
<td align="center">No</td>
 +
</tr>
 
<tr>
 
<tr>
<td>FPDSHD-58504, FPDSHD-70122</td>
+
<td style="width:95px" valign="top">FPDSHD-77483
<td valign="top">The user reported an issue while creating a Modification to a document saying.
+
</td>
 +
<td valign="top">The user was not able to select the value “Order Dependent (IDV allows pricing arrangement to be determined separately for each order)” on the IDV for the data element “Type of Contract Pricing” due to the following rule.
  
“The value "64133 4676" for Data Element "Place of Performance (PoP) ZIP Code" is invalid.”
+
6A02 – “When "Commercial Item Acquisition Procedures" is other than 'Commercial Item Procedures not used' then "Type of Contract" must be "Firm Fixed Price" or "Fixed Price with Economic Price Adjustment" or "Time and Materials" or "Labor Hours".”
 
</td>
 
</td>
<td>
+
<td>  
*Through Business Services, FPDS-NG shall validate the “Place of Performance Zip Code” on ‘create’ and ‘update’ only when the Zip Code is sent in the request.
+
*FPDS-NG shall update the validation rule 6A04_LoV to accept three additional values for “Type of Contract” on IDVs when “Commercial Item Acquisition Procedures” are used.  The additional values are ‘Fixed Price Incentive’, ‘Fixed Price Award Fee’ and ‘Order Dependent (IDV allows pricing arrangement to be determined separately for each order)’. The updated rule with rule code 6A04_LoV for all Version 1.3 and 1.4 IDVs  shall read as:
*The following Validation Rule shall be displayed when the Zip Code sent is invalid or end dated and the document shall be saved in error status:
+
 
'''“The value <<zipCode>> for Data Element “Place of Performance ZIP Code” is invalid.'''
+
'''“When "Commercial Item Acquisition Procedures" is other than 'Commercial Item Procedures not used' then "Type of Contract" must be ‘Firm Fixed Price’ or ‘Fixed Price with Economic Price Adjustment’ or ‘Time and Materials’ or ‘Labor Hours’ or ‘Order Dependent (IDV allows pricing arrangement to be determined separately for each order)’ or ‘Fixed Price Incentive’ or ‘Fixed Price Award Fee’.”'''
*Through Business Services, FPDS-NG shall propagate the “Place of Performance Zip Code” from the latest modification document on ‘create’ of Modification when the Zip Code is not sent in the request. The propagated Zip Code shall not be validated on ‘create’ and the document shall be saved in ‘draft’ status successfully.
+
 
*FPDS-NG shall display and validate the “Place of Performance Zip Code” on ‘Save Draft’, ‘Validate’, ‘Approve’ and ‘Correct’ through Web Portal and GUI Services.
+
*For all Version 1.2 and lower IDVs as “Commercial Item Acquisition Procedures” is a checkbox, the rule with code 6A04 shall read as:
*FPDS-NG shall validate the “Place of Performance Zip Code” on ‘isComplete’, ‘isExistingAwardComplete’, ‘approve’ and ‘correct’ through Business Services.
+
 
*All the above requirements apply on Modifications and to Version 1.3 and 1.4.
+
'''When "Commercial Item Acquisition Procedures" is selected then "Type of Contract" must be ‘Fixed Price’ or ‘Fixed Price with Economic Price Adjustment’ or ‘Time and Materials’ or ‘Labor Hours’ or ‘Order Dependent (IDV allows pricing arrangement to be determined separately for each order) or ‘Fixed Price Incentive’ or ‘Fixed Price Award Fee’.'''
 +
 +
*FPDS-NG shall update the validation rule 6A02_LoV to add additional values for “Type of Contract” on Awards when “Commercial Item Acquisition Procedures” are used.  The additional values are ‘Fixed Price Incentive’ and ‘Fixed Price Award Fee’. The updated rule with rule code 6A02_LoV for all Version 1.3 and 1.4 Awards (PO, DCA, DO and BPA Call) shall read as:
 +
 
 +
'''When "Commercial Item Acquisition Procedures" is other than 'Commercial Item Procedures not used' then "Type of Contract" must be 'Firm Fixed Price' or 'Fixed Price with Economic Price Adjustment' or 'Time and Materials' or 'Labor Hours' or 'Fixed Price Incentive' or 'Fixed Price Award Fee'.'''
 +
 
 +
*For Version 1.2 and lower Awards (PO, DCA and DO) as “Commercial Item Acquisition Procedures” is a checkbox, the rule with code 6A02 shall read as:
 +
 
 +
'''When "Commercial Item Acquisition Procedures" is selected then "Type of Contract" must be 'Fixed Price' or 'Fixed Price with Economic Price Adjustment' or 'Time and Materials' or 'Labor Hours' or 'Fixed Price Incentive' or 'Fixed Price Award Fee'.'''
 +
 
 +
*The above rules shall apply on Base documents only for both Civilian and DoD agencies.
 +
 
 +
*The rules shall fire on ‘Validate’, ‘Approve’ and ‘Correct’ through GUI Services and Web Portal and ‘isComplete’, ‘isExistingAwardComplete’/‘isExistingIDVComplete’, ‘approve’ and ‘correct’ through Business Services.
 
</td>
 
</td>
 
<td align="center">No</td>
 
<td align="center">No</td>
 
</tr>
 
</tr>
</TABLE>
+
</table>

Latest revision as of 00:44, 2 April 2011

Schedule

DescriptionStart Date End Date
BETA Installation Monday Sep 20, 2010Monday Sep 20, 2010
Functional Qualification TestingTuesday Sep 21, 2010Thursday Sep 23, 2010
Installation in ProductionFriday Oct 15, 2010Friday Oct 15, 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-56611

In the Adhoc reports, the attribute selection list for the attribute: "who can use", the list shows the description, but the report returns the code.

FPDS-NG shall display codes for “Who Can Use” listed in the ‘Contract Marketing Data’ Section in the “Select Attributes” tab of Ad-hoc reports for all agencies.

No
FPDSHD-54136 The user reported the issue of not being able to correct the FSS ‘GS06F0006L’. The user was getting a ‘System Error’ on correcting the FSS.
  • On ‘Correct’ of an IDV, FPDS-NG shall ensure that the IDV is corrected successfully and ‘System Error’ is not displayed.
  • On ‘Correct’ of an IDV, FPDS-NG shall ensure that all ‘Not Required’ data elements on the referencing Awards and IDVs are updated with the values from the referenced IDV successfully.
  • On ‘Correct’ of an IDV, FPDS-NG shall ensure that all ‘Not Required’ data elements on the modifications are updated with the values from the IDV successfully.
  • All above requirements shall apply on all Versions through Web Portal, GUI and Business Services.
No
FPDSHD-66884 The user is not able to login successfully using the session expired screen when his/her password was reset by the Agency Administrator.
  • From the session expired screen, FPDS-NG shall redirect the user to the ‘Reset Password’ screen when the password of the user is reset by the administrator and the password entered by the user is correct.
  • On the session expired screen, FPDS-NG shall display the following inactivity or user locked message when the user tries to login based on the profile of the user.

“For security purposes, user account '<userID>' 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 FPDS-NG System administrator to have the user account re-enabled.”

“For security purposes, user account '<userID>' 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.”

No
FFPDSHD-60169

The user is not able to successfully correct a migrated contract which is signed on or after 1st October 2003 as the data element “Description of Requirements” is closed for editing and the following mandatory message fires: “The Mandatory element: "descriptionOfContractRequirement" is missing for Contract Type: IDV and Contract Action Type: IDC.”

  • FPDS-NG shall allow the users to edit the data element “Description of Requirement” through front end on DoD contracts prepared by “DOD_ MIGRATOR” or “MIGRATOR”.
  • FPDS-NG shall accept the value for the data element “Description of Requirement” only if the “Date Signed” is equal to or later than 1st October 2003.
  • The following warning message shall not be displayed for DoD contracts prepared by “DOD_ MIGRATOR” or “MIGRATOR” and the “Date Signed” is equal to or later than 1st October 2003.

.

5004 – “The description of contract requirement cannot be changed for DOD documents that were Migrated.”

  • All the above requirements are applicable on ‘Correct’ through Web Portal and Business Services.
  • All the above requirements are applicable on finalized bases and modifications of Awards and IDVs on all versions.
No
FPDSNG-3639 The labels for Place of Performance state, location and country code have to be moved to be placed above the text boxes.
  • FPDS-NG shall update and re-arrange the Principal Place of Performance labels for (State, Location, Country) to be placed above the text boxes on the Award and IDV Screens.
  • The above requirement shall apply to Awards on all Versions and 1.4 Other Transactions IDV.
  • The CBT Training material and the V 1.4/1.3 Users Manual shall be updated to update the screenshots with the updated position for the Principal Place of Performance labels.
No
FPDSHD-77483 The user was not able to select the value “Order Dependent (IDV allows pricing arrangement to be determined separately for each order)” on the IDV for the data element “Type of Contract Pricing” due to the following rule.

6A02 – “When "Commercial Item Acquisition Procedures" is other than 'Commercial Item Procedures not used' then "Type of Contract" must be "Firm Fixed Price" or "Fixed Price with Economic Price Adjustment" or "Time and Materials" or "Labor Hours".”

  • FPDS-NG shall update the validation rule 6A04_LoV to accept three additional values for “Type of Contract” on IDVs when “Commercial Item Acquisition Procedures” are used. The additional values are ‘Fixed Price Incentive’, ‘Fixed Price Award Fee’ and ‘Order Dependent (IDV allows pricing arrangement to be determined separately for each order)’. The updated rule with rule code 6A04_LoV for all Version 1.3 and 1.4 IDVs shall read as:

“When "Commercial Item Acquisition Procedures" is other than 'Commercial Item Procedures not used' then "Type of Contract" must be ‘Firm Fixed Price’ or ‘Fixed Price with Economic Price Adjustment’ or ‘Time and Materials’ or ‘Labor Hours’ or ‘Order Dependent (IDV allows pricing arrangement to be determined separately for each order)’ or ‘Fixed Price Incentive’ or ‘Fixed Price Award Fee’.”

  • For all Version 1.2 and lower IDVs as “Commercial Item Acquisition Procedures” is a checkbox, the rule with code 6A04 shall read as:

When "Commercial Item Acquisition Procedures" is selected then "Type of Contract" must be ‘Fixed Price’ or ‘Fixed Price with Economic Price Adjustment’ or ‘Time and Materials’ or ‘Labor Hours’ or ‘Order Dependent (IDV allows pricing arrangement to be determined separately for each order) or ‘Fixed Price Incentive’ or ‘Fixed Price Award Fee’.

  • FPDS-NG shall update the validation rule 6A02_LoV to add additional values for “Type of Contract” on Awards when “Commercial Item Acquisition Procedures” are used. The additional values are ‘Fixed Price Incentive’ and ‘Fixed Price Award Fee’. The updated rule with rule code 6A02_LoV for all Version 1.3 and 1.4 Awards (PO, DCA, DO and BPA Call) shall read as:

When "Commercial Item Acquisition Procedures" is other than 'Commercial Item Procedures not used' then "Type of Contract" must be 'Firm Fixed Price' or 'Fixed Price with Economic Price Adjustment' or 'Time and Materials' or 'Labor Hours' or 'Fixed Price Incentive' or 'Fixed Price Award Fee'.

  • For Version 1.2 and lower Awards (PO, DCA and DO) as “Commercial Item Acquisition Procedures” is a checkbox, the rule with code 6A02 shall read as:

When "Commercial Item Acquisition Procedures" is selected then "Type of Contract" must be 'Fixed Price' or 'Fixed Price with Economic Price Adjustment' or 'Time and Materials' or 'Labor Hours' or 'Fixed Price Incentive' or 'Fixed Price Award Fee'.

  • The above rules shall apply on Base documents only for both Civilian and DoD agencies.
  • The rules shall fire on ‘Validate’, ‘Approve’ and ‘Correct’ through GUI Services and Web Portal and ‘isComplete’, ‘isExistingAwardComplete’/‘isExistingIDVComplete’, ‘approve’ and ‘correct’ through Business Services.
No