V1.4 SP 29.0
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
Deprecated: Non-static method MagicWord::get() should not be called statically, assuming $this from incompatible context in /opt/mediawiki-1.6.12/includes/Parser.php on line 2102
From FPDS-NG
Schedule
Description | Start Date | End Date |
---|---|---|
BETA Installation | Wednesday October 14, 2015 | Wednesday October 14, 2015 |
Government Acceptance Testing | Tuesday October 27, 2015 | Thursday October 29, 2015 |
Installation in Production | Saturday November 14, 2015 | Saturday November 14, 2015 |
Document Changes
Documentation | Changes Required |
---|---|
XML Specifications | No |
Web Services | No |
Data Dictionary | Yes |
NASA Specific Data Dictionary | No |
Use Case Summary | Yes |
Validation Rules | Yes |
Reporting | No |
ezSearch | No |
Atom Feeds | No |
Online Help | No |
User Manual | Yes |
SPR Listing
SPR # | Enhancement/Problem | Solution | Impact to Users and Integrators |
---|---|---|---|
14694 | 1) When a record is created with a Foreign (non-U.S.) Place of Performance Country and a Place of Performance Zip Code value, the user is unable to subsequently delete or update the value in the Zip Code field.
2) When a record is created with a Foreign (non-U.S.) Place of Performance Country and without a Place of Performance Zip Code, the user is unable to subsequently add a value in the Zip Code field. | 1) A software fix shall be performed for records with a Foreign (non-U.S.) Place of Performance Country and a value in the Place of Performance Zip Code field, so that when a user subsequently deletes or updates the value in the Zip Code field, the new value is retained.
2) A software fix shall be performed for records with a Foreign (non-U.S.) Place of Performance Country and a blank value in the Place of Performance Zip Code field, so that when a user subsequently adds a value to that field, the new value is retained. |
Yes |
14901 | The short description of the Reason for Modification, ‘Vendor DUNS Change,’ does not indicate to the user that it may also be used to update the vendor’s name from SAM. | The short description of the Reason for Modification, ‘Vendor DUNS Change’ shall be updated to the following: ‘Vendor DUNS or Name Change – Non-Novation’ Please note: 1) The DUNS number is not required to be changed when ‘Vendor DUNS or Name Change – Non-Novation’ is selected. 2) This change does not impact any of its existing functionality Documentation changes: The Data Validation Rules document shall be updated to reflect the new short description of ‘Vendor DUNS Change.’ All instances of ‘Vendor DUNS Change’ shall be replaced with ‘Vendor DUNS or Name Change – Non-Novation.’ The V1.4 Data Dictionary shall be updated to reflect the new short description for ‘Vendor DUNS or Name Change – Non-Novation.’ The V1.4 User Manual shall be updated to reflect the new short description for ‘Vendor DUNS or Name Change – Non-Novation.’ |
No |
15414 | The verbiage in the FPDS-NG Registration section will be updated for clarity. | The verbiage in the FPDS-NG Registration section (https://www.fpds.gov/fpdsng_cms/index.php/en/register.html) shall be updated to the following: GOVERNMENT ACCOUNTS If you are an acquisition official (contracting officer / contracting specialist / administrator) and require access, click here in order to submit data. PUBLIC ACCOUNTS If you are a member of the public, a member of the Congress, or a government official who does not require access to submit data, click here to establish an account that allows you to create reports and retrieve data. |
No |
15838 | Replace ISO with GENC as the source for Country data in FPDS-NG. As part of this update, the following additional items will also be fixed: 14895 - U.S. Territories with active country codes should be replaced with the country code ‘USA.’ 15190 – Two active country codes exist for Burma/Myanmar
| FPDS-NG shall replace ISO with the Geopolitical Entities, Names, and Codes Standard (GENC) as the source for Country data in FPDS-NG. GENC specifies an authoritative set of country codes and names for use by the Federal Government for information exchange, using ISO 3166 (Parts 1 and 2) names and code elements wherever possible, with modifications only where necessary to comply with U.S. law and U.S. Government recognition policy. The GENC Country data can be viewed here: https://nsgreg.nga.mil/genc/discovery The following spreadsheet shows a crosswalk of changes that will occur in FPDS-NG between the current display name and Alpha-3 Code used, and the GENC Standard: https://www.fpds.gov/downloads/FPDS_GENC_Country_Code_Crosswalk.xlsx 14895 – FPDS-NG shall end-date the active country codes associated with the following U.S. Territories as of 9/30/2015: • American Samoa (ASM) Beginning 10/1/2015, FPDS-NG users shall instead use ‘USA’ as the Country Code. For Principal Place of Performance, the user shall report the 9-zigit ZIP Code within the US Territory. 15190 – FPDS-NG shall remove the Start Date for Country Code ‘BUR’ (Burma) and set the End Date to ‘1/1/1989.’
|
Yes |
16116 | When the period of performance is extended on a modification, no validation rules currently exist on the following fields: Completion Date, Estimated Ultimate Completion Date, and Last Date to Order. | FPDS-NG shall have two new validation rules fire on Award modifications where the Reason for Modification value is ‘Exercise an Option’: The “Completion Date” shall be equal to or greater than the “Date Signed” value on a Modification Number greater than zero (0) when the “Reason for Modification” value is "Exercise an Option". The “Estimated Ultimate Completion Date” shall be equal to or greater than the “Date Signed” value on a Modification Number greater than zero (0) when the “Reason for Modification” value is "Exercise an Option". FPDS-NG shall have a new validation rule fire on IDV modifications where the Reason for Modification value is "Exercise an Option": The Last Date to Order Date shall be equal to or greater than the “Date Signed” value on a Modification Number greater than zero (0) when the Reason for Modification value is "Exercise an Option". Documentation changes: The Data Validation Rules document shall be updated to add the new validation rules. |
Yes |
16199 | When a user attempts to email a report from the Ad-Hoc Reports module that is larger than 10MB, a generic error message displays that does not indicate the reason for the error. | FPDS-NG shall update the generic error message and add text to inform the user why they are receiving the error:
Error sending email. Please contact Administrator. Email is not available for reports greater than 10MB; Please use the Export Function. |
No |
16778 | DoD PIID validation rules are not firing in the two use-cases listed below: 1) Two DoD PIID validation rules are not firing on the ‘Transfer Action,’ ‘Change PIID,’ and ‘New Base’ types of Reason for Modification actions. 2) A DoD PIID validation rule is not firing when the length of the Modification Number is greater than 10 characters. | FPDS-NG shall perform a software fix so that the two use-cases of DoD PIID validation rules fire as expected: 1) FPDS-NG shall fire the following validation rules on ‘Transfer Action,’ ‘Change PIID,’ and ‘New Base types of Reason for Modification actions: DOD1B07:A:If the transaction is a modification of a Purchase Order, Definitive Contract Action, Delivery/Task Order where position 9 is 'F', or BPA Call where position 9 is 'F', then the modification number cannot be more than 6 characters in length. NOTE: This rule applies to the 13 character PIID for Awards. DOD1B08: If the transaction is a modification of a Delivery/Task Order or BPA Call referencing an IDV awarded by DoD then the Mod number cannot be more than 6 characters in length. NOTE: This rule applies to the 4 character PIID for Awards. 2) FPDS-NG shall fire the following validation rule on all modification types based on the inputted length of the Modification Number: DOD1B07:I: If the transaction is a modification of an IDV, then the modification number cannot be more than 6 characters in length.
NOTE: This rule only applies to IDVs. NOTE: This rule only applies to IDVs. |
Yes |
16954 | The Small Business Goaling Report and Small Business Achievements by Awarding Organization Report are incorrectly excluding the U.S. Territories: United States Minor Outlying Islands (UMI) and United States Miscellaneous Pacific Islands (PUS). | Contracts performed in the U.S. Territories: United States Minor Outlying Islands (UMI) and United States Miscellaneous Pacific Islands (PUS) shall be included in the Small Business Goaling Report and Small Business Achievements by Awarding Organization Report. | No |
17481 | Pursuant to DIAR (Department of the Interior Acquisition Regulation) and the Buy Indian Act, the Type of Set Aside value of ‘Buy Indian’ should be end-dated as of 07/07/2013for the Department of the Interior. Additionally, two new Type of Set Aside values, ‘Indian Small Business Economic Enterprise (ISBEE)’ and ‘Indian Economic Enterprise (IEE)’ should be added with a start-date of 07/08/2013 for the Department of the Interior. | FPDS-NG shall end-date the Type of Set Aside value ‘Buy Indian’ as of 07/07/2013 for the Department of the Interior. FPDS-NG shall add two new Type of Set Aside values as of 07/08/2013 for the Department of the Interior: ‘Indian Small Business Economic Enterprise (ISBEE)’ and ‘Indian Economic Enterprise (IEE).’ These two new Type of Set Aside values are only valid with the following vendor Socio-Economic values: • 13Y American Indian Owned Business Additionally, ‘Indian Small Business Economic Enterprise (ISBEE)’ is only valid when the “Contracting Officer’s Determination of Business Size” is ‘Small Business.’ FPDS-NG shall update the Competition Report (Workflow – Competitive- EXCLUDES ORDERS SUBJECT TO FAIR OPPORTUNITY) and Competitive Procedures, but One Offer Report (Workflow – COMPETITIVE-EXCLUDES ORDERS SUBJECT TO FAIR OPPORTUNITY WITH ONE OFFER) to include the two new Type of Set Aside values. Documentation changes: The Data Validation Rules document shall be updated to add the new validation rules. The Appendix of the Competition Report and Competitive Procedures Report will be updated with the new Type of Set Aside values as referenced above. The V1.4 Data Dictionary shall be updated with the new Type of Set Aside values. The V1.4 User Manual shall be updated with the new Type of Set Aside values. |
Yes |