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

From FPDS-NG

 
(30 intermediate revisions by the same user not shown)
Line 25: Line 25:
 
==SPR Listing==
 
==SPR Listing==
 
<TABLE id="box-table-a" border=2 style="width: 950px">
 
<TABLE id="box-table-a" border=2 style="width: 950px">
<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=25% align="center"><b>Impact to Users and Integrators</b></th>
 
<tr>
 
<tr>
<td style="width:95px" valign="top">FPDSHD-71390, FPDSHD-69612, FPDSHD-69190, FPDSHD-72585, FPDSHD-68838
+
<td style="width:95px" valign="top">FPDSNG-3629
 
</td>
 
</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.  
+
<td valign="top">CCR will be stopping the dissemination of SIC Code from v4.10.3 – Scheduled for July 28, 2010. FPDS-NG CCR Loading Process needs to be changed to accommodate the File Format changes.
The IDV is NAS598145 and the Novation mod is 26 with a date signed of 03/23/2010.
 
 
</td>  
 
</td>  
 
<td valign="top">
 
<td valign="top">
*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 CCR loading process shall be modified to read all the records from the CCR flat file without the “SIC Code” and “SIC Code Counter”.
*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”.
+
</td>
*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 align="center">No</td>
 +
</tr>
 +
<td style="width:95px" valign="top">FPDSNG-3630
 +
</td>
 +
<td valign="top">The TAS Codes that may be used for ARRA (American Recovery and Reinvestment Act) contracts are not limited to Recovery contracts. To give the users the ability to mark the contracts as ‘Recovery’, the data element “Initiative” shall be changed from text box to dropdown and made as ‘Optional’ for Version 1.4.</td>
 +
<td valign="top">
 +
*FPDS-NG shall have the data element “Initiative” as an Optional Dropdown with the value ‘American Recovery and Reinvestment Act’.
 +
*FPDS-NG shall accept only ‘ARRA’ through Business Services for the data element “Initiative”. Sending any other value shall display the following Validation Rule on ‘create’, ‘update’, ‘isComplete’ and ‘correct’.
 +
*For ARRA actions, FPDS-NG shall return ‘ARRA’ under the “initiative” tag for Business Services response
 +
“The value <<value>> for Data Element "Initiative" is invalid.”
 +
*The ‘isComplete’ and ‘correct’ operations shall display the rule but not error out the document.
 +
*FPDS-NG shall display the following Validation Rule if “Initiative” is marked as ‘ARRA’ and “Treasury Account Symbol” is empty or invalid:
 +
“If “Initiative” is selected then "Treasury Account Symbol" must have a valid value.”
 +
*The above Validation rule shall be displayed on ‘Validate’, ‘Approve’ and ‘Correct’ through GUI Services and ‘isComplete’, ‘isExistingAwardComplete’, ‘isExistingIDVComplete’, ‘approve’ and ‘correct’ operations through Business Services.
 +
*All the requirements shall apply to both Civilian and DoD agencies for Version 1.4 only.
 +
*The Help file, Version 1.4 Data Dictionary and Validation Rules document shall be updated.
 
</td>
 
</td>
 
<td align="center">No</td>
 
<td align="center">No</td>
 
</tr>
 
</tr>
 
 
<tr>
 
<tr>
<td style="width:95px" valign="top">FPDSNG-3624, FPDSNG-3625</td>
+
<td style="width:95px" valign="top">FPDSNG-3631, FPDSNG-3632
<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>
 +
<td valign="top">The TAS Codes may be used for ARRA (American Recovery and Reinvestment Act) contracts but are not limited to Recovery contracts. The “Initiative” data element is not present in Version 1.3 XML. Hence, for business services Version 1.3, the contract can be marked or unmarked as “ARRA” through the “Description of Requirement” element.
 +
</td>  
 
<td valign="top">
 
<td valign="top">
*FPDS-NG shall load FAST book TAS codes into FPDS-NG.
+
*FPDS-NG shall accept the value for the data element “Initiative” through “Description of Requirement” for Business Services in the following format:
*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.
+
ARRA::YES::ARRA
The above validation rule is applicable for the following services:
+
or
<TABLE border=0>
+
ARRA::NO::ARRA
<tr><td>Business Services</td>
+
*FPDS-NG shall have the “Initiative” data element as a dropdown on the screen with the value “American Recovery and Reinvestment Act”
<td>isComplete, isExistingAwardComplete, isExistingIDVComplete,approve and correct</td>
+
*FPDS-NG shall accept only ‘YES’ or ‘NO’ through Business Services. If any other value is sent  in the format ARRA:: <<value>>::::ARRA, FPDS-NG shall display the following error message:
<td> Version 1.3 & 1.4</td>
+
“Initiative should be of format ‘ARRA::YES::ARRA’ or ‘ARRA::NO::ARRA’ and should not contain special characters.”
</tr>
+
*FPDS-NG shall display the following Validation Rule on ‘Validate’, ‘Approve’ and ‘Correct’ operations through Web Portal and GUI Services if “Initiative” is marked as ‘ARRA’ and “Treasury Account Symbol” is empty or invalid.
<tr><td>Gui Services</td>
+
“If “Initiative” is selected then "Treasury Account Symbol" must have a valid value.”
<td>Correct and validate</td>
+
*Both the validation rules specified above shall apply to ‘isComplete’, ‘isExistingAwardComplete’, ‘isExistingIDVComplete’, ‘approve’ and ‘correct’ operations through Business Services.
<td>Version 1.3 & 1.4</td>
+
*If the contract has been touched once through GUI Services or Web portal. i.e. If ‘Save Draft’, ‘Approve’ or ‘Correct’ operation has been performed through GUI Services or Web Portal; FPDS-NG shall not accept ‘ARRA::YES::ARRA’ or ‘ARRA::NO::ARRA’ sent in “Description Of Requirement” as “Initiative” through Business Services and the system shall take the value from the screen through the dropdown.
</tr>  
+
*When a contract created through Business Services is opened through Web Portal/GUI Services, “Initiative” shall be populated as ‘American Recovery and Reinvestment Act’ if the “Description of Requirement” has ‘ARRA::YES::ARRA’.
 +
*FPDS-NG shall have a Data Management fix to add ‘ARRA::YES::ARRA’ in “Description of Requirements” for all Version 1.3 Awards and IDVs which have not been touched by GUI Services and Web portal and marked as recovery in the system
 +
*FPDS-NG shall have a Data Management fix to populate “Initiative” as ‘American Recovery and Reinvestment Act’ if “Description of Requirement” has ‘ARRA::YES::ARRA’ and the “Treasury Account Symbol” is a valid code.
 +
*FPDS-NG shall have a Data Management fix for all Version 1.3 Awards and IDVs which have not been touched by GUI Services or Web portal; to remove ‘American Recovery and Reinvestment Act’ from “Initiative” if “Description of Requirement” has ‘ARRA::NO::ARRA’.  
 +
*Validation Rules document shall be updated to include the new rule.
 +
*All the above requirements apply to all Awards and IDVs for both Civilian and DoD agencies for Version 1.3 only.
 +
</td>
 +
<td align="center">No</td>
 +
</tr>
 
<tr>
 
<tr>
<td>Web Portal</td>
+
<td style="width:95px" valign="top">FPDSIRB-169
<td>Correct ,validate and approve</td>
+
</td>
<td>Version 1.3 & 1.4</td>
+
<td valign="top">As of April 26th 2010, CCR has discontinued providing the following non-essential business types information of the Vendors.     
 +
<ol><li>
 +
Architecture and Engineering  (isArchitectureAndEngineering)
 +
</li><li>Construction Firm  (isConstructionFirm)
 +
</li><li>Research and Development (isResearchAndDevelopment)
 +
</li><li>Service Provider (isServiceProvider)
 +
</li><li>Other Business or Organization Type (isOtherbusinessOrOrganization)
 +
</li></ol>
 +
To maintain FPDS-NG data integrity, changes have been made to the system in SP-2.0 SPR FPDSNG-3623. Documentation, reports, ezSearch and ATOM feeds have to be updated.
 +
</td>  
 +
<td valign="top">
 +
*Standard Reports, Ad hoc Reports and their previews shall not display any columns for the CCR flags. The Award Detail on any Standard Report shall not display the CCR Socio Economic Indicator columns.
 +
*EzSearch shall not return any results when searched by the CCR Socio Economic Indicators. e.g. SOCIO_ECONOMIC_INDICATORS:“Architecture and Engineering”.
 +
*The ATOM Feed specifications shall be updated to remove the CCR Socio Economic fields.
 +
*The following ATOM feeds shall not return the CCR Socio Economic Flags.
 +
**Public Feeds
 +
**Detail Feeds
 +
**DOD Feeds
 +
</td>
 +
<td>Atom Feeds shall not disseminate the information for the flags mentioned above.</td>
 
</tr>
 
</tr>
</TABLE>  
+
<tr>
 +
<td style="width:95px" valign="top">FPDSNG-3633
 +
</td>
 +
<td valign="top">FPDS-NG does not have a procedure in place to load new or modified TAS codes from FAST book into reference table.
 +
</td>
 +
<td valign="top">
 +
*FPDS-NG shall have a monthly procedure in place to load new or modified TAS codes from FAST book into reference table.
 +
*All the TAS Codes in FAST Book shall be available for use in FPDS-NG.
 +
*The existing functionality shall remain unchanged
 
</td>
 
</td>
 
<td align="center">No</td>
 
<td align="center">No</td>
 
</tr>
 
</tr>
 +
</TABLE>

Latest revision as of 21:18, 23 July 2010

Schedule

DescriptionStart Date End Date
BETA Installation Monday June 25, 2010Monday June 25, 2010
Functional Qualification TestingTuesday June 28, 2010Thursday June 30, 2010
Installation in ProductionFriday July 09, 2010Friday July 09, 2010

Document Changes

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

SPR Listing

SPR #ProblemSolutionImpact to Users and Integrators
FPDSNG-3629 CCR will be stopping the dissemination of SIC Code from v4.10.3 – Scheduled for July 28, 2010. FPDS-NG CCR Loading Process needs to be changed to accommodate the File Format changes.

The CCR loading process shall be modified to read all the records from the CCR flat file without the “SIC Code” and “SIC Code Counter”.

No
FPDSNG-3630 The TAS Codes that may be used for ARRA (American Recovery and Reinvestment Act) contracts are not limited to Recovery contracts. To give the users the ability to mark the contracts as ‘Recovery’, the data element “Initiative” shall be changed from text box to dropdown and made as ‘Optional’ for Version 1.4.
  • FPDS-NG shall have the data element “Initiative” as an Optional Dropdown with the value ‘American Recovery and Reinvestment Act’.
  • FPDS-NG shall accept only ‘ARRA’ through Business Services for the data element “Initiative”. Sending any other value shall display the following Validation Rule on ‘create’, ‘update’, ‘isComplete’ and ‘correct’.
  • For ARRA actions, FPDS-NG shall return ‘ARRA’ under the “initiative” tag for Business Services response

“The value <<value>> for Data Element "Initiative" is invalid.”

  • The ‘isComplete’ and ‘correct’ operations shall display the rule but not error out the document.
  • FPDS-NG shall display the following Validation Rule if “Initiative” is marked as ‘ARRA’ and “Treasury Account Symbol” is empty or invalid:

“If “Initiative” is selected then "Treasury Account Symbol" must have a valid value.”

  • The above Validation rule shall be displayed on ‘Validate’, ‘Approve’ and ‘Correct’ through GUI Services and ‘isComplete’, ‘isExistingAwardComplete’, ‘isExistingIDVComplete’, ‘approve’ and ‘correct’ operations through Business Services.
  • All the requirements shall apply to both Civilian and DoD agencies for Version 1.4 only.
  • The Help file, Version 1.4 Data Dictionary and Validation Rules document shall be updated.
No
FPDSNG-3631, FPDSNG-3632 The TAS Codes may be used for ARRA (American Recovery and Reinvestment Act) contracts but are not limited to Recovery contracts. The “Initiative” data element is not present in Version 1.3 XML. Hence, for business services Version 1.3, the contract can be marked or unmarked as “ARRA” through the “Description of Requirement” element.
  • FPDS-NG shall accept the value for the data element “Initiative” through “Description of Requirement” for Business Services in the following format:

ARRA::YES::ARRA or ARRA::NO::ARRA

  • FPDS-NG shall have the “Initiative” data element as a dropdown on the screen with the value “American Recovery and Reinvestment Act”
  • FPDS-NG shall accept only ‘YES’ or ‘NO’ through Business Services. If any other value is sent in the format ARRA:: <<value>>::::ARRA, FPDS-NG shall display the following error message:

“Initiative should be of format ‘ARRA::YES::ARRA’ or ‘ARRA::NO::ARRA’ and should not contain special characters.”

  • FPDS-NG shall display the following Validation Rule on ‘Validate’, ‘Approve’ and ‘Correct’ operations through Web Portal and GUI Services if “Initiative” is marked as ‘ARRA’ and “Treasury Account Symbol” is empty or invalid.

“If “Initiative” is selected then "Treasury Account Symbol" must have a valid value.”

  • Both the validation rules specified above shall apply to ‘isComplete’, ‘isExistingAwardComplete’, ‘isExistingIDVComplete’, ‘approve’ and ‘correct’ operations through Business Services.
  • If the contract has been touched once through GUI Services or Web portal. i.e. If ‘Save Draft’, ‘Approve’ or ‘Correct’ operation has been performed through GUI Services or Web Portal; FPDS-NG shall not accept ‘ARRA::YES::ARRA’ or ‘ARRA::NO::ARRA’ sent in “Description Of Requirement” as “Initiative” through Business Services and the system shall take the value from the screen through the dropdown.
  • When a contract created through Business Services is opened through Web Portal/GUI Services, “Initiative” shall be populated as ‘American Recovery and Reinvestment Act’ if the “Description of Requirement” has ‘ARRA::YES::ARRA’.
  • FPDS-NG shall have a Data Management fix to add ‘ARRA::YES::ARRA’ in “Description of Requirements” for all Version 1.3 Awards and IDVs which have not been touched by GUI Services and Web portal and marked as recovery in the system
  • FPDS-NG shall have a Data Management fix to populate “Initiative” as ‘American Recovery and Reinvestment Act’ if “Description of Requirement” has ‘ARRA::YES::ARRA’ and the “Treasury Account Symbol” is a valid code.
  • FPDS-NG shall have a Data Management fix for all Version 1.3 Awards and IDVs which have not been touched by GUI Services or Web portal; to remove ‘American Recovery and Reinvestment Act’ from “Initiative” if “Description of Requirement” has ‘ARRA::NO::ARRA’.
  • Validation Rules document shall be updated to include the new rule.
  • All the above requirements apply to all Awards and IDVs for both Civilian and DoD agencies for Version 1.3 only.
No
FPDSIRB-169 As of April 26th 2010, CCR has discontinued providing the following non-essential business types information of the Vendors.
  1. Architecture and Engineering (isArchitectureAndEngineering)
  2. Construction Firm (isConstructionFirm)
  3. Research and Development (isResearchAndDevelopment)
  4. Service Provider (isServiceProvider)
  5. Other Business or Organization Type (isOtherbusinessOrOrganization)

To maintain FPDS-NG data integrity, changes have been made to the system in SP-2.0 SPR FPDSNG-3623. Documentation, reports, ezSearch and ATOM feeds have to be updated.

  • Standard Reports, Ad hoc Reports and their previews shall not display any columns for the CCR flags. The Award Detail on any Standard Report shall not display the CCR Socio Economic Indicator columns.
  • EzSearch shall not return any results when searched by the CCR Socio Economic Indicators. e.g. SOCIO_ECONOMIC_INDICATORS:“Architecture and Engineering”.
  • The ATOM Feed specifications shall be updated to remove the CCR Socio Economic fields.
  • The following ATOM feeds shall not return the CCR Socio Economic Flags.
    • Public Feeds
    • Detail Feeds
    • DOD Feeds
Atom Feeds shall not disseminate the information for the flags mentioned above.
FPDSNG-3633 FPDS-NG does not have a procedure in place to load new or modified TAS codes from FAST book into reference table.
  • FPDS-NG shall have a monthly procedure in place to load new or modified TAS codes from FAST book into reference table.
  • All the TAS Codes in FAST Book shall be available for use in FPDS-NG.
  • The existing functionality shall remain unchanged
No