Difference between revisions of "V1.4 SP 19.0"

From FPDS-NG
 
(26 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
 
  
−
</td>
+
This requirement shall apply to all Awards/IDVs.
−
<td align="center">No</td>
 
−
</tr>
 
−
<tr>
 
−
<td style="width:95px" valign="center">FPDSHD-113057</td>
 
−
<td>Users cannot correct the New Base after a Transfer Action if there are existing mods after it.
 
  
−
<td>In Progress
 
−
 
 
</td>
 
</td>
 
<td align="center">No</td>
 
<td align="center">No</td>
Line 46: Line 38:
 
<tr>
 
<tr>
 
<td style="width:95px" valign="center">FPDSHD-113670</td>
 
<td style="width:95px" valign="center">FPDSHD-113670</td>
−
<td>The user is reporting data accuracy issue when correcting base contracts that have re-rep mods.
+
<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>In progress
+
<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.
  
 
</td>
 
</td>
Line 54: Line 46:
  
 
<tr>
 
<tr>
−
<td style="width:95px" valign="center">FPDSPMOS-135</td>
 
−
<td>SOLR 4 setup and data export
 
  
−
<td>In Progress
+
<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.
 +
 
 +
<td>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.
 
</td>
 
</td>
 
<td align="center">No</td>
 
<td align="center">No</td>
Line 63: Line 71:
 
<tr>
 
<tr>
  
−
<td style="width:95px" valign="center">FPDSHD-82415</td>
+
<td style="width:95px" valign="center">FPDSHD-84802</td>
−
<td>The SAM Exception value cannot be removed when trying to process a "Vendor DUNS Change" modification.
+
<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.
  
−
<td>The following resolution applies:
+
<td>
  
−
1. On the ‘Vendor DUNS Change’ mod for operations ‘Create’ and ‘Update’:
+
<b>Web Portal</b>:
−
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’:
+
1. FPDS-NG shall auto-populate the Referenced IDV Modification Number as per the Date Signed on the 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.
 
  
−
3. On the ‘Vendor DUNS Change’ mod for operations ‘Create’ and ‘Update’:
+
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.
−
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>Business Services</b>:
  
−
    Purchase Order – both civilian and DoD
+
1. FPDS-NG shall auto-populate the Referenced IDV Modification Number as per the Date Signed on the Order in the following cases:
−
    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
 
  
−
5. Requirements 1 through 3 shall not apply to the following V 1.4 documents:
+
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.
  
−
a. NASA Specific Awards – except for “Novation”, other vendor change mods do not apply
+
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:
  
−
b. Other Transaction documents – SAM Exception does not apply
+
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.
  
−
6. On the ‘Vendor DUNS Change’ mod for the operation ‘Correct’:
+
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.
−
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’:
+
</td>
−
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.
+
<td align="center">No</td>
  
−
8. On the ‘Vendor DUNS Change’ mod for the operation ‘Correct’:
+
<tr>
−
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:
 
−
 
 
−
    Purchase Order – both civilian and DoD
 
−
    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:
+
<td style="width:95px" valign="center">FPDSHD-108437</td>
 +
<td>Modifications to the Other Transaction Order, Agreement and IDV are validating the PSC code although it propagates from the base.
  
−
a. NASA Specific Awards – except for “Novation”, other vendor change mods do not apply
+
<td>1. FPDS-NG shall not validate the PSC code on the modifications for the following documents:
−
b. Other Transaction documents – SAM Exception does not apply
 
  
−
The current behavior with Novation, Rerepresentation, Rerepresentation of non-Novated Merger/Acquisition, and Vendor Address Change shall continue as is.
+
    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 124: Line 120:
 
<tr>
 
<tr>
  
−
<td style="width:95px" valign="center">FPDSHD-77600</td>
+
<td style="width:95px" valign="center">FPDSHD-91657</td>
−
<td>The Contracting Office Report is only displaying the first line of the address.
+
<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>
 +
<b>For all agencies</b>:
 +
 
 +
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.
 +
 
 +
<b>For DHS and DoD</b>:
 +
 
 +
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.
 +
 
 +
<b>For NASA</b>:
 +
 
 +
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.
 +
 
 +
<b>For all agencies</b>:
 +
 
 +
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 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"