Difference between revisions of "V1.4 SP 17.0"
From FPDS-NG
| Line 13: | Line 13: | ||
<tr><td nowrap>XML Specifications</td><td align="center">No</td></tr> | <tr><td nowrap>XML Specifications</td><td align="center">No</td></tr> | ||
<tr><td nowrap>Web Services</td><td align="center">No</td></tr> | <tr><td nowrap>Web Services</td><td align="center">No</td></tr> | ||
| − | <tr><td nowrap>Data Dictionary </td><td align="center"> | + | <tr><td nowrap>Data Dictionary </td><td align="center">Yes</td></tr> |
| − | <tr><td nowrap>NASA Specific Data Dictionary</td><td align="center"> | + | <tr><td nowrap>NASA Specific Data Dictionary</td><td align="center">Yes</td></tr> |
| − | <tr><td nowrap>Use Case Summary</td><td align="center"> | + | <tr><td nowrap>Use Case Summary</td><td align="center">Yes</td></tr> |
<tr><td nowrap>Validation Rules</td><td align="center">Yes</td></tr> | <tr><td nowrap>Validation Rules</td><td align="center">Yes</td></tr> | ||
<tr><td nowrap>Reporting</td><td align="center">Yes</td></tr> | <tr><td nowrap>Reporting</td><td align="center">Yes</td></tr> | ||
<tr><td nowrap>Online Help</td><td align="center">Yes</td></tr> | <tr><td nowrap>Online Help</td><td align="center">Yes</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> | ||
| − | <tr><td nowrap>User Manual</td><td align="center"> | + | <tr><td nowrap>User Manual</td><td align="center">Yes</td></tr> |
</table> | </table> | ||
==SPR Listing== | ==SPR Listing== | ||
| Line 163: | Line 163: | ||
<td align="center">No</td> | <td align="center">No</td> | ||
<tr> | <tr> | ||
| − | <td style="width:95px" valign="center"> | + | <td style="width:95px" valign="center">Upgrade FPDS-NG Reporting to IE 9</td> |
| − | <td> | + | <td>The FPDS-NG Standard and Ad hoc reporting are not compatible with IE 9. |
| − | <td> | + | <td>The FPDS-NG Standard and Ad hoc reporting shall be made compatible with IE 9. The current report functionality shall continue to work as is. |
</td> | </td> | ||
<td align="center">No</td> | <td align="center">No</td> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
<tr> | <tr> | ||
Revision as of 18:08, 18 December 2012
Schedule
| Description | Start Date | End Date |
|---|---|---|
| BETA Installation | Monday October 01, 2012 | Monday October 01, 2012 |
| Functional Qualification Testing | Tuesday October 02, 2012 | Thursday October 04, 2012 |
| Installation in Production | Friday October 12, 2012 | Friday October 12, 2012 |
Document Changes
| Documentation | Changes Required |
|---|---|
| XML Specifications | No |
| Web Services | No |
| Data Dictionary | Yes |
| NASA Specific Data Dictionary | Yes |
| Use Case Summary | Yes |
| Validation Rules | Yes |
| Reporting | Yes |
| Online Help | Yes |
| Computer-Based Training | No |
| User Manual | Yes |
SPR Listing
| SPR # | Enhancement/Problem | Solution | Impact to Users and Integrators |
|---|---|---|---|
| FPDSPMOS-115 | The Defense Automatic Addressing System Center (DAASC) Trading Partner Number (TPN) interface sends information collected by the Defense Logistics Agency (DLA) pertaining to Department of Defense Activity Address Codes (DoDAAC). This information is disseminated as needed to DoD component systems and individuals as well as other agencies such as GSA. This is a daily file that is sent automatically to SAM.
Currently, FPDS-NG has been processing and loading the FedReg data by accessing the ‘FedReg Daily Extract File’ daily from BPN. There is a proposition from GSA that FPDS-NG should not be using ‘FedReg Daily Extract File’ anymore, and that the daily ‘DoDAAC Core Data File’ be obtained from SAM and be used.
|
1. FPDS-NG shall get “DoDAAC Core Data File” from SAM.
2. FPDS-NG shall be able to access and process the file with the format, SAM_DAASC_TPN_MMDDYYYY.TXT 3. The data elements that shall be obtained from this extract are as follows. GCE’s interpretation of each of these elements is also provided: • DoDAAC (9 digit TPN code) (9) - DODXYYYYY (DOD is the static “Filler”, X is the Service code and YYYYY stands for the actual DoDAAC) • Agency Code (2) – The first two characters if the agency code is in the format XX00 or the last two characters if the agency code is in the format 97XX • Bureau Code (4) • Entity Name (35) – Funding Office Name • Entity TAC 1 Address Line 1 (35) – Physical/Mailing Address 1 • Entity TAC 1 Address Line 2 (35) – Physical/Mailing Address 2 • Entity TAC 1 Address City (35) – Physical/Mailing City • Entity TAC 1 Address Country (3) – Physical/Mailing Country • Entity TAC 1 Address State (2) – Physical/Mailing State • Entity TAC 1 Address Zip (5) – Physical/Mailing Zip Code • Entity TAC 1 Address Zip+4 (4) – Physical/Mailing Zip+4 Code • Expiration Date (19) • Type Update (A=Add, C=Change, D=Delete) |
No |
| FPDSHD-58292 | Existing Purchase Orders, Definitive Contracts and IDCs that are signed after 09/30/2003 have the “Subcontracting Plan” value as ‘Plan Required (Pre 2004)’.
The validation rule, 11B07 (The "Subcontracting Plan" value can not be "Plan Required (Pre 2004)" when "Signed Date" is after September 30'th 2003) and the referential validation rule, “The value "Plan Required (Pre 2004)" for Data Element "Subcontract Plan" is invalid” are found to be not consistently implemented. | 1. For civilian/DoD V 1.0/1.1/1.2/1.3 PO, DCA and IDC that are signed after 09/30/2003:
The validation rule, 11B07 (The "Subcontracting Plan" value can not be "Plan Required (Pre 2004)" when "Signed Date" is after September 30'th 2003) shall display on ‘isComplete’, ‘Approve’ and ‘Correct. 2. For civilian V 1.0/1.1 FSS, GWAC, BOA and BPA that are signed after 09/30/2003: The validation rule, 11B07 (The "Subcontracting Plan" value can not be "Plan Required (Pre 2004)" when "Signed Date" is after September 30'th 2003) shall display on ‘isComplete’, ‘Approve’ and ‘Correct. |
No |
| FPDSHD-60534 | On Standard reports like “Contractor Search” and on Advanced Search, the DUNS numbers that do not have any final documents reported to FPDS-NG are displaying a message that “The DUNS Number entered does not exist in CCR.” although they are registered in CCR and are active.
This is not an issue on the contractual screens because such DUNS numbers are retrieved, thus allowing users to make a selection. | For the DUNS numbers that do not have any final documents reported to FPDS-NG, irrespective of whether or not the vendors are registered in CCR, the following message shall be displayed:
“The DUNS Number entered currently does not have any associated FPDS-NG contract action reports. Therefore, no data will be displayed.”. |
No |
| FPDSHD-80113 | The “Contractor Search’ report is displaying the “500 Internal Server Error” when an attempt is made to select a “DBAN” (Doing Business As Name) value on the “Vendor Selection” screen from the filter, “Vendor Name”.
Adhoc reporting and Advanced Search do not have this issue. | 1. From the “Vendor Selection” screen of the “Contractor Search” report, the area that displays the DBAN values and also the “Show DBAN” button shall be removed.
Note 1: The output will display both DBAN and no DBAN data for the chosen filters. Note 2: The DBAN shall only be removed from the Vendor Lookup in the Reports Search Criteria Screen. 2. The existing functionality of “Vendor Name”, “DUNS Number”, “Doing Business As Name”, “Country Code”, “City”, “State” and “Zip Code” shall continue as is. |
No |
| FPDSHD-81973 | Currently Advanced Search does not allow the “Funding Agency/Office” search for IDVs.
IDVs did not have to report data for “Funding Agency” and “Funding Office” until V 1.4. When V 1.4 went live, Advanced Search was not enhanced to accept values for “Funding Agency” and “Funding Office”. | Advanced Search shall be enhanced to accept values for “Funding Agency” and “Funding Office” for IDVs, and display data accordingly. | No |
| FPDSNG-3647 | CAPTCHA is a type of challenge-response test used in computing as an attempt to ensure that the response is generated by a person. CAPTCHAs are used in attempts to prevent automated software from performing actions which degrade the quality of service of a given system, whether due to abuse or resource expenditure.
To introduce CAPTCHA in FPDS-NG wherever user log in credentials are involved. | 1. For new user registration:
FPDS-NG shall introduce the CAPTCHA at the end on the “User Identification” screen. After the user enters all the information including the CAPTCHA correctly, and clicks on “Save”, then the “Your Registration is successful” screen will be displayed. Incorrect CAPTCHA can be entered any number of times. If the user fails to recognize the CAPTCHA, then they shall have a provision to request for another CAPTCHA. The correct CAPTCHA along with the correct user information will ensure a successful registration. 2. For forgot password: FPDS-NG shall introduce the CAPTCHA at the end on the “FPDS-NG” screen. After the user enters the User ID and the CAPTCHA correctly, and clicks on “Submit”, then the message, “Temporary Password has been sent. Please check your email.” will be displayed. Incorrect CAPTCHA can be entered any number of times. If the user fails to recognize the CAPTCHA, then they shall have a provision to request for another CAPTCHA. The correct CAPTCHA along with the correct user ID will ensure a successful password reset. 3. For User log in: FPDS-NG shall introduce the CAPTCHA after two unsuccessful log-in attempts. After the user successfully recognizes the CAPTCHA, the FPDS-NG Home Page will be displayed. If the user fails to recognize the CAPTCHA, then they shall have a provision to request for another CAPTCHA. Case 1: If CAPTCHA is correct and Password is correct, then user log in will be successful Case 2: If CAPTCHA is correct and Password is incorrect for the 3rd time, then the message, Invalid username/password will display. If CAPTCHA is correct and Password is incorrect for the 4th time, then the user will be suggested to reset the password. If CAPTCHA is correct and Password is incorrect for the 5th time, then the account will be locked out. Case 3: If CAPTCHA is incorrect and Password is incorrect, then user needs to identify CAPTCHA again. Incorrect CAPTCHA can be entered any number of times Case 4: If CAPTCHA is incorrect and Password is incorrect, then user needs to identify CAPTCHA again. Incorrect CAPTCHA can be entered any number of times. Note: If the password is incorrect after user corrects the CAPTCHA, the, the behavior for Case 2 will apply. |
No |
| FPDSPMOS-121 | Upgrade to IPV6. | In-progress | No |
| Upgrade FPDS-NG Reporting to IE 9 | The FPDS-NG Standard and Ad hoc reporting are not compatible with IE 9. | The FPDS-NG Standard and Ad hoc reporting shall be made compatible with IE 9. The current report functionality shall continue to work as is. | No |