Difference between revisions of "V1.4 SP 18.0"

From FPDS-NG

 
Line 5: Line 5:
 
<th width=34% align="center"><b>End Date</b></th></tr>
 
<th width=34% align="center"><b>End Date</b></th></tr>
 
<tr><td nowrap>BETA Installation </td><td nowrap>Friday February 01, 2013</td><td nowrap>Friday February 01, 2013</td></tr>
 
<tr><td nowrap>BETA Installation </td><td nowrap>Friday February 01, 2013</td><td nowrap>Friday February 01, 2013</td></tr>
<tr><td nowrap>Functional Qualification Testing </td><td nowrap>Monday February 04, 2013</td><td nowrap>Monday February 11, 2013</td></tr>
+
<tr><td nowrap>Functional Qualification Testing </td><td nowrap>Monday February 04, 2013</td><td nowrap>Wednesday February 06, 2013</td></tr>
 
<tr><td nowrap>Installation in Production</td><td nowrap>Thursday February 14, 2013</td><td nowrap>Thursday February 14, 2013</td></tr>
 
<tr><td nowrap>Installation in Production</td><td nowrap>Thursday February 14, 2013</td><td nowrap>Thursday February 14, 2013</td></tr>
 
</table>
 
</table>

Latest revision as of 08:52, 29 January 2013

Schedule

DescriptionStart Date End Date
BETA Installation Friday February 01, 2013Friday February 01, 2013
Functional Qualification Testing Monday February 04, 2013Wednesday February 06, 2013
Installation in ProductionThursday February 14, 2013Thursday February 14, 2013

Document Changes

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

SPR Listing

SPR #Enhancement/ProblemSolutionImpact to Users and Integrators
FPDSPMOS-131 Base (modification number = 0) documents that are reported to FPDS-NG on or later than 02/15/2013 will not allow a value of “0.00” in the “Base and All Options Value”

1. For the following base (modification number = 0) documents that are reported to FPDS-NG on or later than 02/15/2013, FPDS-NG will not allow a value of “0.00” in the “Base and All Options Value”:

Awards

  1. Delivery/Task Order
  2. Purchase Order
  3. Definitive Contract
  4. BPA Call
  5. Other Transaction Order
  6. Other Transaction Agreement
  7. Intragovernmental
  8. Cooperative Agreement
  9. Grant for Research
  10. Training Grant
  11. Funded Space Act Agreement

IDVs

  1. FSS
  2. GWAC
  3. IDC
  4. Other Transaction IDV

2. V 1.4 Data Validation Rules document shall be updated to add the new validation rule.

No
FPDSPMOS-132 The “Buy American Act Place of Manufacture” report shall be updated to include Poland and Czech Republic as qualifying countries. 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.

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:

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.

No
FPDSPMOS-133 FPDS-NG updates to support Executive Compensation changes in USA Spending. This offers two resolutions, one for FPDS-NG and another for USA Spending.

FPDS-NG

Software Change:

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.

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.

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.

4. Modifications:

a. Novation modification: 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.

b. Re-representation modification: EC data will continue to be inherited from the base on the modification.

c. Vendor DUNS change modification: EC data will continue to be inherited from the base on the modification.

d. Vendor address change modification: EC data will continue to be inherited from the base on the modification.

Tagging Existing Records

A data management process will be run one-time to tag all applicable existing records in FPDS-NG with Executive Compensation data. This updated data is available only for USASpending. This will not impact any of the Atom feed users.

USA Spending

Prime Contracts - FPDS-NG

Prime contract executive compensation data shall be displayed in the Complete Transaction Details view on USASpending.gov.

Prime Grants - DSVT

Prime grant executive compensation data shall be displayed in the Complete Transaction details view on USASpending.gov.

Data Dissemination

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

No
FPDSPMOS-134 Changes to the "Small Business Goaling Report", "Small Business Achievements by Awarding Organization Report" and "Small Business Dashboard". 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: 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.

3. Appendix for the “Small Business Goaling Report” and the “Small Business Achievements by Awarding Organization Report” shall be updated accordingly.

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".

No
FPDSHD-82415 The SAM Exception value cannot be removed when trying to process a "Vendor DUNS Change" modification. The following resolution applies:

1. On the ‘Vendor DUNS Change’ mod for operations ‘Create’ and ‘Update’: 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’: 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’: 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:

    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

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:

    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:

a. NASA Specific Awards – except for “Novation”, other vendor change mods do not apply 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.

No
FPDSHD-77600 The Contracting Office Report is only displaying the first line of the address. The Contracting Office Report shall display the complete address for the office. No