Difference between revisions of "V1.4 SP 19.0"

From FPDS-NG

 
 
(29 intermediate revisions by the same user not shown)
Line 17: Line 17:
 
<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">No</td></tr>
−
<tr><td nowrap>Reporting</td><td align="center">Yes</td></tr>
+
<tr><td nowrap>Reporting</td><td align="center">No</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 26: Line 26:
 
<th width=18% align="center"><b>SPR #</b></th><th width=30% align="center"><b>Enhancement/Problem</b></th><th width=38% align="center"><b>Solution</b></th><th width=25% align="center"><b>Impact to Users and Integrators</b></th>
 
<th width=18% align="center"><b>SPR #</b></th><th width=30% align="center"><b>Enhancement/Problem</b></th><th width=38% 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-72999</td>
+
<td style="width:95px" valign="center">FPDSHD-113057</td>
−
<td> Civilian and DoD user's can successfully create modifications to contracts when the base belongs to another agency without a Transfer Action.
+
<td>Users cannot correct the New Base after a Transfer Action if there are existing mods after it.
  
−
</td>
+
<td>For the FPDS-NG action ‘correct’, FPDS-NG shall not restrict users from correcting a ‘New Base’ irrespective of the Award/IDV Status of any subsequent Modifications.
−
<td> In Progress
+
 
 +
This requirement shall apply to all Awards/IDVs.
  
 
</td>
 
</td>
 
<td align="center">No</td>
 
<td align="center">No</td>
−
</tr>
+
 
 
<tr>
 
<tr>
−
<td style="width:95px" valign="center">FPDSPMOS-132</td>
+
<td style="width:95px" valign="center">FPDSHD-113670</td>
−
<td>The “Buy American Act Place of Manufacture” report shall be updated to include Poland and Czech Republic as qualifying countries.
+
<td>When correcting base contracts, the “Contracting Officer’s Determination of Business Size” value on any Rerepresentation mods is getting overridden with that from the base.
  
−
<td>1. The column, “Mfg Outside the U.S. - Qualifying Country (DoD Funds Only)” of the “Buy American Act Place of Manufacture” report shall be updated to include ‘Poland’ and ‘Czech Republic’ in the list of qualifying countries.
+
<td>When the base contract is corrected, FPDS-NG shall not propagate “Contracting Officer's Business Size Selection” from the base to the ‘Rerepresentation’ or ‘Rerepresentation of non-Novated Merger/Acquisition’ modification.
−
The country code for ‘Poland’ is “POL” and the country code for Czech Republic is “CZE”.
 
  
−
2. Appendix of the report shall be updated as follows:
 
−
 
−
<i>Mfg Outside the U.S. - Qualifying Country (DoD Funds Only) - As a result of memoranda of understanding and other international agreements, DoD has determined it inconsistent with the public interest to apply the Buy American Act to the acquisition of qualifying country end products from the following qualifying countries (DFARS 225.872-1(a)):
 
−
 
−
Australia, Austria, Belgium, Canada, Czech Republic, Denmark, Egypt, Federal Republic of Germany, Germany, Finland, France, Greece, Israel, Italy, Luxembourg, Netherlands, Norway, Poland, Portugal, Spain, Sweden , Switzerland , Turkey , United Kingdom of Great Britain and Northern Ireland. "Country of Product or Service Origin" as one of these countries is counted.
 
−
 
−
Those actions that are awarded and funded by DoD, that have 'Mfg Outside the U.S. - Qualifying Country (DoD Only)' selected as the "Place of Manufacture" and whose PSC Code is between 1000 and 9999 (both values inclusive, but excluding 5510, 87**, 88**, 89**, 9410, 9430, 9440, 9610, 9620 or 9630) are counted in this column.</i>
 
−
 
 
</td>
 
</td>
 
<td align="center">No</td>
 
<td align="center">No</td>
  
 
<tr>
 
<tr>
−
<td style="width:95px" valign="center">FPDSPMOS-133</td>
 
−
<td>FPDS-NG updates to support Executive Compensation changes in USA Spending.
 
  
−
<td>This offers two resolutions, one for FPDS-NG and another for USA Spending.
+
<td style="width:95px" valign="center">FPDSIRB-173</td>
 +
<td>The values for the "National Interest Action" (NIA) and "Local Area Set Aside" (LASA) are defaulted as "Select One" on error records.
  
−
<b><u>FPDS-NG</u></b>
+
<td>1. FPDS-NG shall retain the user provided values for NIA and LASA on the base errored out documents.
  
−
<i><b>Software Change</b></i>:
+
2. FPDS-NG shall retain the user provided values for NIA and the propagated value of LASA on the modification errored out documents.
  
−
1.For vendors whose EC data is provided by SAM, FPDS-NG contracts will reflect vendor specific EC information with ‘base and all options’ value greater than or equal to $25,000 and date signed on or after July 8th, 2010.
+
3. The following documents shall be addressed:
 +
    Purchase Order
 +
    Delivery/Task Order
 +
    Definitive Contract
 +
    BPA Call
 +
    FSS
 +
    GWAC
 +
    BOA
 +
    BPA Call
 +
    IDC
  
−
2.For vendors whose EC data is provided by SAM, FPDS-NG shall update all existing contracts  with ‘base and all options’ value greater than or equal to $25,000 and date signed (base contract) on or after July 8th, 2010 with EC information. Note: This is a one-time process to update the existing contracts in FPDS-NG.  
+
4. The resolution applies the FPDS-NG actions - Create and Update.
 +
</td>
 +
<td align="center">No</td>
  
−
3.When the contract is tagged with EC data, all subsequent modifications will inherit the EC data from the base contract with some exceptions listed under modifications.
+
<tr>
  
−
4. Modifications:
+
<td style="width:95px" valign="center">FPDSHD-84802</td>
 +
<td>The user reported a conflict between the posted requirement state and the behavior of the Referenced IDV Modification Number on the Other Transaction documents.
  
−
a. <b>Novation modification</b>: if tagged with EC, EC data of the new vendor shall be reflected. Subsequent modifications shall reflect the new vendor EC data. The original base document will continue to reflect original vendor information.
+
<td>
  
−
b. <b>Re-representation modification</b>: EC data will continue to be inherited from the base on the modification.
+
<b>Web Portal</b>:
  
−
c. <b>Vendor DUNS change modification</b>: EC data will continue to be inherited from the base on the modification.
+
1. FPDS-NG shall auto-populate the Referenced IDV Modification Number as per the Date Signed on the Order.
  
−
d. <b>Vendor address change modification</b>: EC data will continue to be inherited from the base on the modification.
+
2. If the Date Signed is not provided on the Order, but an attempt is made to select the Referenced IDV, then FPDS-NG shall consider the System Date and auto-populate the respective Referenced IDV Modification Number.
  
−
<i><b>Tagging Existing Records</b></i>
+
<b>Business Services</b>:
  
−
A data management process will be run one-time to tag all applicable existing records in FPDS-NG with Executive Compensation data. This updated
+
1. FPDS-NG shall auto-populate the Referenced IDV Modification Number as per the Date Signed on the Order in the following cases:
−
data is available only for USASpending. This will not impact any of the Atom
 
−
feed users.
 
  
−
<b><u>USA Spending</u></b>
+
a.  The Referenced IDV Modification Number is provided as ‘0’.
 +
b.  The Referenced IDV Modification Number is provided as not ‘0’.
 +
c.  The Referenced IDV Modification Number tag is not sent.
 +
d.  The Referenced IDV Modification Number tag is sent, but the value is not provided.
  
−
<i><b>Prime Contracts - FPDS-NG</b></i>
+
2. If the Date Signed is not provided on the Order, but an attempt is made to select the Referenced IDV, then FPDS-NG shall consider the System Date and auto-populate the respective Referenced IDV Modification Number in the following cases:
  
−
Prime contract executive compensation data shall be displayed in the Complete Transaction Details view on USASpending.gov.
+
a.  The Referenced IDV Modification Number is provided as ‘0’.
 +
b.  The Referenced IDV Modification Number is provided as not ‘0’.
 +
c.  The Referenced IDV Modification Number tag is not sent.
 +
d.  The Referenced IDV Modification Number tag is sent, but the value is not provided.
  
−
<i><b>Prime Grants - DSVT</b></i>
+
All the above requirements shall apply to the ‘Create’ operation. They also apply to the ‘Update’ and ‘Correct’ operations when the “Date Signed’ is changed on the Order.
−
 
 
−
Prime grant executive compensation data shall be displayed in the Complete Transaction details view on USASpending.gov.
 
−
 
 
−
<i><b>Data Dissemination</b></i>
 
−
 
 
−
The reported executive compensation data for Prime Grants and Prime Contracts shall be available through the Data Feed, Export, Archives, and API features on USASpending.gov
 
  
 
</td>
 
</td>
Line 103: Line 104:
  
 
<tr>
 
<tr>
−
<td style="width:95px" valign="center">FPDSPMOS-134</td>
 
−
<td>Changes to the "Small Business Goaling Report", "Small Business Achievements by Awarding Organization Report" and "Small Business Dashboard".
 
−
 
−
<td>Following are the requirements:
 
−
 
−
1. The “Small Business Goaling Report” and the “Small Business Achievements by Awarding Organization Report” shall be changed for the following:
 
−
 
−
a. The “8(a) Procedures” Actions, Dollars and the Percentage columns shall be updated with the “Contracting Officer’s Determination of Business Size” as ‘Small Business’ condition.
 
−
 
−
b. For the Goaling condition - “Contracts performed outside of the United States shall be excluded”, the report logic shall be updated to include all the US territories.
 
  
−
2. The “Small Business Dashboard” shall be changed for the following:
+
<td style="width:95px" valign="center">FPDSHD-108437</td>
−
For the Goaling condition - “Contracts performed outside of the United States shall be excluded”, the logic shall be updated to include all the US territories.
+
<td>Modifications to the Other Transaction Order, Agreement and IDV are validating the PSC code although it propagates from the base.  
  
−
3. Appendix for the “Small Business Goaling Report” and the “Small Business Achievements by Awarding Organization Report” shall be updated accordingly.
+
<td>1. FPDS-NG shall not validate the PSC code on the modifications for the following documents:
  
−
4. Appendix for the published “Small Business Goaling Reports” for FY ’11, ’10 and ’09 shall be updated with the correct UNICOR DUNS listing, to match with the Standard “Small Business Goaling Report".
+
    Other Transaction IDV
 +
    Other Transaction Order
 +
    Other Transaction Agreement
  
 +
2. The resolution applies to the FPDS-NG actions - Create, Update and Correct.
 
</td>
 
</td>
 
<td align="center">No</td>
 
<td align="center">No</td>
Line 126: Line 120:
 
<tr>
 
<tr>
  
−
<td style="width:95px" valign="center">FPDSHD-82415</td>
+
<td style="width:95px" valign="center">FPDSHD-91657</td>
−
<td>The SAM Exception value cannot be removed when trying to process a "Vendor DUNS Change" modification.
+
<td>The Place of Performance Zip Code is retained when the Place of Performance Country Code is corrected from USA to a foreign country.
  
−
<td>The following resolution applies:
+
<td>
 +
<b>For all agencies</b>:
  
−
1. On the ‘Vendor DUNS Change’ mod for operations ‘Create’ and ‘Update’:
+
If the “Place of Performance Country Code” is changed from ‘USA’ to a foreign country, then the values for “Place of Performance Zip Code” and “Place of Performance Zip +4 Code” shall be cleared out for the following documents:
−
FPDS-NG shall allow the user to remove the SAM Exception that is propagated from the base, if the new DUNS is not a SAM exception DUNS. FPDS-NG shall not error the modification.
 
  
−
2. On the ‘Vendor DUNS Change’ mod for operations ‘Create’ and ‘Update’:
+
    Purchase Order
−
FPDS-NG shall allow the user to retain the SAM Exception that is propagated from the base, if the new DUNS is a SAM exception DUNS. FPDS-NG shall not error the modification.
+
    Delivery/Task Order
 +
    Definitive Contract
 +
    BPA Call
  
−
3. On the ‘Vendor DUNS Change’ mod for operations ‘Create’ and ‘Update’:
+
Note: US Territories are not foreign.
−
FPDS-NG shall allow the user to change the SAM Exception that is propagated from the base, if the new DUNS is a SAM exception DUNS. FPDS-NG shall not error the modification.  
 
  
−
4. Requirements 1 through 3 shall apply to the following V 1.4 documents:
+
<b>For DHS and DoD</b>:
  
−
    Purchase Order – both civilian and DoD
+
If the “Place of Performance Country Code” is changed from ‘USA’ to a foreign country, then the values for “Place of Performance Zip Code” and “Place of Performance Zip +4 Code” shall be cleared out for the following documents:
−
    Definitive Contract – both civilian and DoD
+
−
    FSS – only civilian
+
    Other Transaction IDV
−
    GWAC – only civilian
+
    Other Transaction Order
−
    BOA – both civilian and DoD
+
    Other Transaction Agreement
−
    Part 13 BPA – both civilian and DoD
 
−
    IDC – both civilian and DoD
 
−
 
 
−
5. Requirements 1 through 3 shall not apply to the following V 1.4 documents:
 
−
 
 
−
a. NASA Specific Awards – except for “Novation”, other vendor change mods do not apply
 
−
 
 
−
b. Other Transaction documents – SAM Exception does not apply
 
−
 
 
−
6. On the ‘Vendor DUNS Change’ mod for the operation ‘Correct’:
 
−
FPDS-NG shall allow the user to remove the SAM Exception that is propagated from the base, if the new DUNS is not a SAM exception DUNS. The vendor data of the new DUNS shall be propagated. FPDS-NG shall not error the modification.
 
−
 
 
−
7. On the ‘Vendor DUNS Change’ mod for the operation ‘Correct’:
 
−
FPDS-NG shall allow the user to remove the SAM Exception that is propagated from the base, if the new DUNS is not a SAM exception DUNS. The vendor data of the new DUNS shall be propagated.
 
−
 
 
−
8. On the ‘Vendor DUNS Change’ mod for the operation ‘Correct’:
 
−
FPDS-NG shall allow the user to retain the SAM Exception that is propagated from the base, if the new DUNS is a SAM exception DUNS. The vendor data of the new DUNS shall be propagated.
 
  
−
9. Requirements 7 through 9 shall apply to the following documents:
+
Note: US Territories are not foreign.
  
−
    Purchase Order – both civilian and DoD
+
<b>For NASA</b>:
−
    Definitive Contract – both civilian and DoD
 
−
    FSS – only civilian 
 
−
    GWAC – only civilian
 
−
    BOA – both civilian and DoD
 
−
    Part 13 BPA – both civilian and DoD
 
−
    IDC – both civilian and DoD
 
  
−
10. Requirements 7 through 9 shall not apply to the following documents:
+
If the “Place of Performance Country Code” is changed from ‘USA’ to a foreign country, then the values for “Place of Performance Zip Code” and “Place of Performance Zip +4 Code” shall be cleared out for the following documents:
  
−
a. NASA Specific Awards – except for “Novation”, other vendor change mods do not apply
+
    Intragovernmental
−
b. Other Transaction documents – SAM Exception does not apply
+
    Cooperative Agreement
 +
    Training Grant
 +
    Funded Space Act Agreement
 +
    Grant for Research
  
−
The current behavior with Novation, Rerepresentation, Rerepresentation of non-Novated Merger/Acquisition, and Vendor Address Change shall continue as is.
+
Note: US Territories are not foreign.
  
−
</td>
+
<b>For all agencies</b>:
−
<td align="center">No</td>
 
−
 
 
−
<tr>
 
  
−
<td style="width:95px" valign="center">FPDSHD-77600</td>
+
The above requirements shall apply to the 'Update' and 'Correct' FPDS-NG actions, and through Web Portal and Business Services. For Business Services, the Zip Code value must be cleared out for the following scenarios:
−
<td>The Contracting Office Report is only displaying the first line of the address.
 
  
−
<td>The Contracting Office Report shall display the complete address for the office.
+
    When the tag is not sent
 +
    When the tag is sent without the value
 +
    When the tag is sent with a value
  
 
</td>
 
</td>

Latest revision as of 12:50, 26 February 2013

Schedule

DescriptionStart Date End Date
BETA Installation Friday March 15, 2013Friday March 15, 2013
Functional Qualification Testing Monday March 18, 2013Friday March 22, 2013
Installation in ProductionFriday March 29, 2013Friday March 29, 2013

Document Changes

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

SPR Listing

SPR #Enhancement/ProblemSolutionImpact to Users and Integrators
FPDSHD-113057 Users cannot correct the New Base after a Transfer Action if there are existing mods after it. For the FPDS-NG action ‘correct’, FPDS-NG shall not restrict users from correcting a ‘New Base’ irrespective of the Award/IDV Status of any subsequent Modifications.

This requirement shall apply to all Awards/IDVs.

No
FPDSHD-113670 When correcting base contracts, the “Contracting Officer’s Determination of Business Size” value on any Rerepresentation mods is getting overridden with that from the base. When the base contract is corrected, FPDS-NG shall not propagate “Contracting Officer's Business Size Selection” from the base to the ‘Rerepresentation’ or ‘Rerepresentation of non-Novated Merger/Acquisition’ modification. No
FPDSIRB-173 The values for the "National Interest Action" (NIA) and "Local Area Set Aside" (LASA) are defaulted as "Select One" on error records. 1. FPDS-NG shall retain the user provided values for NIA and LASA on the base errored out documents.

2. FPDS-NG shall retain the user provided values for NIA and the propagated value of LASA on the modification errored out documents.

3. The following documents shall be addressed: 

   Purchase Order
   Delivery/Task Order
   Definitive Contract
   BPA Call
   FSS
   GWAC
   BOA
   BPA Call 
   IDC

4. The resolution applies the FPDS-NG actions - Create and Update.

No
FPDSHD-84802 The user reported a conflict between the posted requirement state and the behavior of the Referenced IDV Modification Number on the Other Transaction documents.

Web Portal:

1. FPDS-NG shall auto-populate the Referenced IDV Modification Number as per the Date Signed on the Order.

2. If the Date Signed is not provided on the Order, but an attempt is made to select the Referenced IDV, then FPDS-NG shall consider the System Date and auto-populate the respective Referenced IDV Modification Number.

Business Services:

1. FPDS-NG shall auto-populate the Referenced IDV Modification Number as per the Date Signed on the Order in the following cases:

a. The Referenced IDV Modification Number is provided as ‘0’. b. The Referenced IDV Modification Number is provided as not ‘0’. c. The Referenced IDV Modification Number tag is not sent. d. The Referenced IDV Modification Number tag is sent, but the value is not provided.

2. If the Date Signed is not provided on the Order, but an attempt is made to select the Referenced IDV, then FPDS-NG shall consider the System Date and auto-populate the respective Referenced IDV Modification Number in the following cases:

a. The Referenced IDV Modification Number is provided as ‘0’. b. The Referenced IDV Modification Number is provided as not ‘0’. c. The Referenced IDV Modification Number tag is not sent. d. The Referenced IDV Modification Number tag is sent, but the value is not provided.

All the above requirements shall apply to the ‘Create’ operation. They also apply to the ‘Update’ and ‘Correct’ operations when the “Date Signed’ is changed on the Order.

No
FPDSHD-108437 Modifications to the Other Transaction Order, Agreement and IDV are validating the PSC code although it propagates from the base. 1. FPDS-NG shall not validate the PSC code on the modifications for the following documents: 
   Other Transaction IDV
   Other Transaction Order
   Other Transaction Agreement

2. The resolution applies to the FPDS-NG actions - Create, Update and Correct.

No
FPDSHD-91657 The Place of Performance Zip Code is retained when the Place of Performance Country Code is corrected from USA to a foreign country.

For all agencies:

If the “Place of Performance Country Code” is changed from ‘USA’ to a foreign country, then the values for “Place of Performance Zip Code” and “Place of Performance Zip +4 Code” shall be cleared out for the following documents: 

   Purchase Order
   Delivery/Task Order 
   Definitive Contract 
   BPA Call

Note: US Territories are not foreign.

For DHS and DoD:

If the “Place of Performance Country Code” is changed from ‘USA’ to a foreign country, then the values for “Place of Performance Zip Code” and “Place of Performance Zip +4 Code” shall be cleared out for the following documents: 

   Other Transaction IDV
   Other Transaction Order 
   Other Transaction Agreement

Note: US Territories are not foreign.

For NASA:

If the “Place of Performance Country Code” is changed from ‘USA’ to a foreign country, then the values for “Place of Performance Zip Code” and “Place of Performance Zip +4 Code” shall be cleared out for the following documents: 

   Intragovernmental
   Cooperative Agreement
   Training Grant
   Funded Space Act Agreement 
   Grant for Research

Note: US Territories are not foreign.

For all agencies:

The above requirements shall apply to the 'Update' and 'Correct' FPDS-NG actions, and through Web Portal and Business Services. For Business Services, the Zip Code value must be cleared out for the following scenarios: 

   When the tag is not sent
   When the tag is sent without the value
   When the tag is sent with a value
No
Retrieved from "https://fpds.gov/wiki/index.php?title=V1.4_SP_19.0&oldid=4312"