Difference between revisions of "FAADC Version 1.2"
From FPDS-NG
(Created page with "__NOEDITSECTION__ ==Schedule== <TABLE id="box-table-a" border=2> <tr><th width=30% align="center"><b>Description</b></th><th width=34% align="center"><b>Start Date</b></th> <...") |
|||
(6 intermediate revisions by the same user not shown) | |||
Line 25: | Line 25: | ||
<b>*Note: In addition to the release notes content below, more detailed information regarding the FAADC V1.2 Version Change can be found at the following link:</B> | <b>*Note: In addition to the release notes content below, more detailed information regarding the FAADC V1.2 Version Change can be found at the following link:</B> | ||
− | <font color="blue">https://www.fpds.gov/downloads/FAADC/ | + | <font color="blue">https://www.fpds.gov/downloads/FAADC/FAADC_XSD_Specification_Changes_for_Version_1.2.pdf</font> |
This link contains: | This link contains: | ||
Line 38: | Line 38: | ||
<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">IAEMOD-9905 | <td style="width:95px" valign="top">IAEMOD-9905 | ||
</td> | </td> | ||
− | |||
<td valign="top">Version 1.1 genericTag Data Elements created with new XML tags in Version 1.2 and resetting of genericTags | <td valign="top">Version 1.1 genericTag Data Elements created with new XML tags in Version 1.2 and resetting of genericTags | ||
+ | <td valign="top">The FAADC application shall be updated as part of the genericTag maintenance during a version change, data elements utilizing genericTags in Version 1.1 will be given their own XML tags for future use in Version 1.2. The genericTags will be reset to nullify existing logic so they can be used for future purposes. The following data elements utilized genericTags in Version 1.1 and will have new XML tags in Version 1.2: | ||
+ | <ol> | ||
+ | <li>Indirect Cost Federal Share Amount, which used <i>‘genericFloat01'</i>, will now have a new XML tag of <i>'indirectCostFederalShareAmount'</i>.</li> | ||
− | < | + | <li>Funding Opportunity Goals Text, which used <i>‘genericString01’</i>, will now have a new XML tag of <i>'fundingOpportunityGoalsText'</i>.</li> |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | <li>Service-Disabled Veteran-Owned Business Joint Venture, which used <i>'genericString02’</i>, will now have a new XML tag of <i>'isJointVentureServiceDisabledVetOwnedBusiness'</i>.</li> | |
− | + | <li>SBA-Certified Women-Owned Small Business, which used <i>‘genericString03’</i>, will now have a new XML tag of <i>'isSBACertifiedWomenOwnedSmallBusiness'</i>.</li> | |
− | + | <li>SBA-Certified Economically Disadvantaged Women-Owned Small Business, which used <i>‘genericString04'</i>, will now have a new XML tag of <i>'isSBACertifiedEconDisadvWomenOwnedSmallBusiness'</i>.</li> | |
+ | <li>Small Business Joint Venture, which used <i>‘genericString05’</i>, will now have a new XML tag of <i>‘isJointVentureSmallBusiness'</i>.</li> | ||
+ | </ol> | ||
</td> | </td> | ||
Line 76: | Line 72: | ||
Please <b>[[Media:FAADC V1.2 Assitance user screen.png|click here]]</b> to see the updated V1.2 Assistance user screen | Please <b>[[Media:FAADC V1.2 Assitance user screen.png|click here]]</b> to see the updated V1.2 Assistance user screen | ||
− | A new version of the ASSISTANCE and ASSISTANCEDELETED Atom Feeds will be created to reflect the multiple Assistance Listings. The 1.1 Atom Feeds will be decommissioned 6 months after ( | + | A new version of the ASSISTANCE and ASSISTANCEDELETED Atom Feeds will be created to reflect the multiple Assistance Listings. The 1.1 Atom Feeds will be decommissioned 6 months after (May 16, 2025) V1.2 Atom Feeds are implemented. |
− | A new Version 1.2 WSDL will be deployed. WSDL Version 1.1 will be retired and will only allow ‘Correct’ and | + | A new Version 1.2 WSDL will be deployed. WSDL Version 1.1 will be retired and will only allow ‘Correct’ and ‘Get’ actions to be performed. |
− | Data Elements 2K: ‘Correction Delete Indicator’ and 2M: ‘FABS Sent Date’ will be tracked at the Individual Assistance Level instead of at the previous record level. | + | Data Elements 2K: ‘Correction Delete Indicator’, 2L: 'Correction Delete Indicator Description' and 2M: ‘FABS Sent Date’ will be tracked at the Individual Assistance Level instead of at the previous record level. |
− | Data Element 7A will change XML tag | + | Data Element 7A will change XML tag name from <i>‘CFDANumber’</i> to <i>‘ALNumber’</i>. |
− | Data Element 7B will change XML tag | + | Data Element 7B will change XML tag name from <i>‘CFDAProgramTitle’</i> to <i>‘ALProgramTitle’</i>. |
− | The following data elements will now be | + | The following data elements will now be auto calculated and will no longer allow input from the user: |
*4A - Federal Action Obligation | *4A - Federal Action Obligation | ||
Line 95: | Line 91: | ||
The FAADC application shall be updated with these new data elements: | The FAADC application shall be updated with these new data elements: | ||
− | * | + | *4H - Assistance Listing’s Federal Action Obligation Amount |
− | |||
*4I - Assistance Listing’s Non-Federal Funding Amount | *4I - Assistance Listing’s Non-Federal Funding Amount | ||
− | *4J - Assistance | + | *4J - Assistance Listing's Face Value of Direct Loan or Loan Guarantee |
*4K - Assistance Listing’s Original Loan Subsidy Cost | *4K - Assistance Listing’s Original Loan Subsidy Cost | ||
+ | *7C - Predominant Assistance Listing | ||
− | The FAADC application shall be updated with the following | + | The FAADC application shall be updated with the following validation rules: |
− | *FAADC:7A3 - <i>“An Assistance Listing number cannot be used more than once on a | + | *FAADC:7A3 - <i>“An Assistance Listing number cannot be used more than once on a record.”</i> |
− | *FAADC:7A4 - <i>“Only a maximum number of 5 Assistance Listings can be added to a record. Please limit the Assistance Listings to 5.” | + | *FAADC:7A4 - <i>“Only a maximum number of 5 Assistance Listings can be added to a record. Please limit the Assistance Listings to 5.”</i> |
− | *FAADC:7A5 - <i>“Deleting this Assistance Listing will cause the R&D dollar values to not equal the Federal Action Obligation on an Amendment(s). Please change the dollar values on the Amendment(s) first, then you can delete this Assistance Listing.</i> | + | *FAADC:7A5 - <i>“Deleting this Assistance Listing will cause the R&D dollar values to not equal the Federal Action Obligation on an Amendment(s). Please change the dollar values on the Amendment(s) first, then you can delete this Assistance Listing."</i> |
− | *FAADC:7C1 - <i>“The Predominant Assistance Listing cannot be deleted from an award that has been sent to USASpending.gov. In order to remove this Assistance Listing from the award, the record will have to be deleted and recreated.</i> | + | *FAADC:7A6 - <i>"Assistance Listing number <value> is invalid."</i> |
− | *FAADC:7C2 - <i> | + | *FAADC:7A7 - <i>"Assistance Listing on the Amendment cannot be different than the Assistance Listing on the Base record."</i> |
− | *FAADC:7C3 - <i>“Only one Assistance Listing can be the ‘Predominant Assistance Listing’.</i> | + | *FAADC:7C1 - <i>“The Predominant Assistance Listing cannot be deleted from an award that has been sent to USASpending.gov. In order to remove this Assistance Listing from the award, the record will have to be deleted and recreated."</i> |
+ | *FAADC:7C2 - <i>“One Assistance Listing must be marked as the ‘Predominant Assistance Listing’."</i> | ||
+ | *FAADC:7C3 - <i>“Only one Assistance Listing can be the ‘Predominant Assistance Listing’."</i> | ||
The FAADC application shall be updated with the following validation rules which are now based on the auto calculated dollar amounts. The rule verbiage shall also be updated as follows: | The FAADC application shall be updated with the following validation rules which are now based on the auto calculated dollar amounts. The rule verbiage shall also be updated as follows: | ||
− | *FAADC:4A2 - <i>“When | + | *FAADC:4A2 - <i>“When "Action Type" is "NEW" or "CONTINUATION" on a Base award, the sum of all Assistance Listing "Federal Action Obligation" values must be greater than or equal to $0.00."</i> |
− | *FAADC:4A5 - <i>“The sum of all the Research and Development | + | *FAADC:4A5 - <i>“The sum of all the Research and Development dollar fields must equal the sum of all Assistance Listing "Federal Action Obligation" values on the record."</i> |
− | *FAADC:4B2 - <i>“When | + | *FAADC:4B2 - <i>“When "Action Type" is "NEW" or "CONTINUATION" on a Base award, the sum of all Assistance Listing "Non-Federal Funding Amount" values must be greater than or equal to $0.00."</i> |
− | *FAADC:4D1 - <i>“When "Action Type" = "NEW" or 'CONTINUATION" on a Base Award, the sum of all Assistance Listing “Face Value of Direct Loan or Loan Guarantee” values must be greater than or equal to $0.00.</i> | + | *FAADC:4D1 - <i>“When "Action Type" = "NEW" or 'CONTINUATION" on a Base Award, the sum of all Assistance Listing “Face Value of Direct Loan or Loan Guarantee” values must be greater than or equal to $0.00."</i> |
− | *FAADC:4E1 - <i>“When "Action Type" = "NEW" or 'CONTINUATION" on a Base Award, the sum of all Assistance Listing "Original Loan Subsidy Cost" values must be greater than or equal to $0.00.</i> | + | *FAADC:4E1 - <i>“When "Action Type" = "NEW" or 'CONTINUATION" on a Base Award, the sum of all Assistance Listing "Original Loan Subsidy Cost" values must be greater than or equal to $0.00."</i> |
− | + | *FAADC:4G5 - <i>"The sum of “Indirect Cost Federal Share Amount” for all actions with the same FAIN must be less than or equal to the sum of the “Total Federal Award Value” for all actions with the same FAIN."</i> | |
+ | *FAADC:4G6 - <i>"The sum of “Indirect Cost Federal Share Amount” for all actions with the same URI must be less than or equal to the sum of the “Total Federal Award Value” for all actions with the same URI."<i/> | ||
<td align="center">Yes</td> | <td align="center">Yes</td> | ||
<ul> | <ul> | ||
<tr> | <tr> | ||
− | <td style="width:95px" valign="top">IAEENH-1228/IAEMOD-27666 | + | <td style="width:95px" valign="top">IAEENH-1228/IAEMOD-27666</td> |
− | </td> | ||
<td valign="top">New "Discretionary" data element in FAADC required due to DATA Act requirements related to funding opportunity numbers | <td valign="top">New "Discretionary" data element in FAADC required due to DATA Act requirements related to funding opportunity numbers | ||
Line 129: | Line 127: | ||
<td valign="top">The FAADC application shall be updated to add a new data element named “Discretionary” which will have values “Yes” and “No” only. | <td valign="top">The FAADC application shall be updated to add a new data element named “Discretionary” which will have values “Yes” and “No” only. | ||
− | + | The FAADC application shall be updated with the following validation rules to require a selection be made for this data element on all Grants and Cooperative Agreements, and to ensure that when values are provided for “Funding Opportunity Number” and “Funding Opportunity Goals Text," the Grant or Cooperative Agreement is discretionary, competitive, or both: | |
+ | |||
+ | *FAADC:1K1 - <i>"If "Assistance Type" is Grant or Cooperative Agreement, the "Discretionary" data element is required."</i> | ||
+ | *FAADC:1K2 - <i>"If a value is provided for "Funding Opportunity Number," then either "Competed Opportunity" must be 'Competitive Procedures were used' or "Discretionary" must be 'Yes'."</i> | ||
+ | *FAADC:1K3 - <i>"If a value is provided for "Funding Opportunity Goals Text," then either "Competed Opportunity" must be 'Competitive Procedures were used' or "Discretionary" must be 'Yes'."</i> | ||
</td> | </td> | ||
+ | |||
<td align="center">Yes</td> | <td align="center">Yes</td> | ||
<ul> | <ul> | ||
<tr> | <tr> | ||
− | <td style="width:95px" valign="top">IAEENH-1229/IAEMOD-27667 | + | <td style="width:95px" valign="top">IAEENH-1229/IAEMOD-27667</td> |
− | </td> | ||
<td valign="top">FON Format new mandatory requirements for October 1st, 2023 per OMB memo M22-02 | <td valign="top">FON Format new mandatory requirements for October 1st, 2023 per OMB memo M22-02 | ||
<td valign="top">The FAADC application shall be updated to require acceptable values be provided for both “Funding Opportunity Number” and “Funding Opportunity Goals Text” on all discretionary, competitive Grants and Cooperative Agreements. Additionally, the “Funding Opportunity Number” data element shall be disabled on non-Grants and non-Cooperative Agreements (AssistanceType = 06, 07, 08, 09, 10, or 11). | <td valign="top">The FAADC application shall be updated to require acceptable values be provided for both “Funding Opportunity Number” and “Funding Opportunity Goals Text” on all discretionary, competitive Grants and Cooperative Agreements. Additionally, the “Funding Opportunity Number” data element shall be disabled on non-Grants and non-Cooperative Agreements (AssistanceType = 06, 07, 08, 09, 10, or 11). | ||
+ | |||
+ | The FAADC application shall be updated with the following validation rules to ensure values are provided for both “Funding Opportunity Number” and “Funding Opportunity Goals Text” or for neither data element, and to require acceptable values for both data elements on discretionary, competitive Grants and Cooperative Agreements: | ||
+ | |||
+ | *FAADC:1E3 - <i>"If a value is provided for “Funding Opportunity Number”, then “Funding Opportunity Goals Text” must also have a value."</i> | ||
+ | *FAADC:1E4 - <i>"If a value is provided for “Funding Opportunity Goals Text”, then “Funding Opportunity Number” must also have a value."</i> | ||
+ | *FAADC:1E5 - <i>"If "Competed Opportunity" is 'Competitive Procedures were used' and "Discretionary" is 'Yes,' then both “Funding Opportunity Number” and “Funding Opportunity Goals Text” are required."</i> | ||
+ | *FAADC:1E6 - <i>"If "Competed Opportunity" is 'Competitive Procedures were used' and "Discretionary" is 'Yes,' then “Funding Opportunity Number” cannot be 'NOTAPPLICABLE' or 'NA' or 'NONE' or 'BLANK' or '0'."</i> | ||
+ | *FAADC:1J5 - <i>"If "Competed Opportunity" is 'Competitive Procedures were used' and "Discretionary" is 'Yes,' then “Funding Opportunity Goals Text” cannot be 'NOTAPPLICABLE' or 'NOT APPLICABLE' or 'NA' or 'N/A' or 'NONE' or 'BLANK' or '0'."</i> | ||
+ | </td> | ||
<td align="center">Yes</td> | <td align="center">Yes</td> | ||
− | |||
− | |||
<ul> | <ul> | ||
<tr> | <tr> | ||
− | <td style="width:95px" valign="top">IAEMOD-25630 | + | <td style="width:95px" valign="top">IAEMOD-25630</td> |
<td valign="top">Validation rule for FICE incorrectly fires on Amendment | <td valign="top">Validation rule for FICE incorrectly fires on Amendment | ||
− | <td valign="top">The FAADC application shall be updated to prevent | + | <td valign="top">The FAADC application shall be updated to prevent this validation rule from firing incorrectly on Amendments: |
− | |||
− | |||
− | + | *<i>"Federal Interagency Committee on Education (FICE) Code" must be valid value.”</i> | |
</td> | </td> | ||
<td align="center">Yes</td> | <td align="center">Yes</td> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</table> | </table> |
Latest revision as of 17:34, 17 July 2024
Schedule
Description | Start Date | End Date |
---|---|---|
Beta Deployment | July 01, 2024 | July 01, 2024 |
Government Acceptance Testing | July 08, 2024 | July 19, 2024 |
Production Deployment | November 16, 2024 | November 16, 2024 |
Document Changes
Documentation | Changes Required |
---|---|
XML Specifications | Yes |
Web Services | Yes |
Data Dictionary | Yes |
NASA Specific Data Dictionary | No |
Use Case Summary | Yes |
Validation Rules | Yes |
ezSearch | Yes |
Atom Feeds | Yes |
Online Help | Yes |
User Manual | Yes |
*Note: In addition to the release notes content below, more detailed information regarding the FAADC V1.2 Version Change can be found at the following link: https://www.fpds.gov/downloads/FAADC/FAADC_XSD_Specification_Changes_for_Version_1.2.pdf
This link contains:
- Version change summary
- Changes to Web Services (WSDL Changes)
- WSDL Mapping for new elements
- XML Specification Changes
- and more
SPR Listing
SPR # | Enhancement/Problem | Solution | Impact to Users and Integrators |
---|---|---|---|
IAEMOD-9905 | Version 1.1 genericTag Data Elements created with new XML tags in Version 1.2 and resetting of genericTags | The FAADC application shall be updated as part of the genericTag maintenance during a version change, data elements utilizing genericTags in Version 1.1 will be given their own XML tags for future use in Version 1.2. The genericTags will be reset to nullify existing logic so they can be used for future purposes. The following data elements utilized genericTags in Version 1.1 and will have new XML tags in Version 1.2:
|
Yes |
IAEENH-885/IAEMOD-9907 | Enable FAADC to collect multiple CFDA Numbers/Descriptions | The FAADC application shall be updated to permit the collection of up to 5 Assistance Listings Numbers and Descriptions on a single award. The Assistance screen will be updated to include a new ‘Assistance Listings and Amounts’ section that will include all Assistance Listing information, their dollar amounts, as well as a ‘Predominant Assistance Listing’ checkbox, a ‘Remove Assistance Listing’ button, and an ‘Add Assistance Listing’ button.
Please click here to see the updated V1.2 Assistance user screen A new version of the ASSISTANCE and ASSISTANCEDELETED Atom Feeds will be created to reflect the multiple Assistance Listings. The 1.1 Atom Feeds will be decommissioned 6 months after (May 16, 2025) V1.2 Atom Feeds are implemented. A new Version 1.2 WSDL will be deployed. WSDL Version 1.1 will be retired and will only allow ‘Correct’ and ‘Get’ actions to be performed. Data Elements 2K: ‘Correction Delete Indicator’, 2L: 'Correction Delete Indicator Description' and 2M: ‘FABS Sent Date’ will be tracked at the Individual Assistance Level instead of at the previous record level. Data Element 7A will change XML tag name from ‘CFDANumber’ to ‘ALNumber’. Data Element 7B will change XML tag name from ‘CFDAProgramTitle’ to ‘ALProgramTitle’. The following data elements will now be auto calculated and will no longer allow input from the user:
The FAADC application shall be updated with these new data elements:
The FAADC application shall be updated with the following validation rules:
The FAADC application shall be updated with the following validation rules which are now based on the auto calculated dollar amounts. The rule verbiage shall also be updated as follows:
| Yes |
IAEENH-1228/IAEMOD-27666 | New "Discretionary" data element in FAADC required due to DATA Act requirements related to funding opportunity numbers | The FAADC application shall be updated to add a new data element named “Discretionary” which will have values “Yes” and “No” only.
The FAADC application shall be updated with the following validation rules to require a selection be made for this data element on all Grants and Cooperative Agreements, and to ensure that when values are provided for “Funding Opportunity Number” and “Funding Opportunity Goals Text," the Grant or Cooperative Agreement is discretionary, competitive, or both:
|
Yes |
IAEENH-1229/IAEMOD-27667 | FON Format new mandatory requirements for October 1st, 2023 per OMB memo M22-02 | The FAADC application shall be updated to require acceptable values be provided for both “Funding Opportunity Number” and “Funding Opportunity Goals Text” on all discretionary, competitive Grants and Cooperative Agreements. Additionally, the “Funding Opportunity Number” data element shall be disabled on non-Grants and non-Cooperative Agreements (AssistanceType = 06, 07, 08, 09, 10, or 11).
The FAADC application shall be updated with the following validation rules to ensure values are provided for both “Funding Opportunity Number” and “Funding Opportunity Goals Text” or for neither data element, and to require acceptable values for both data elements on discretionary, competitive Grants and Cooperative Agreements:
|
Yes |
IAEMOD-25630 | Validation rule for FICE incorrectly fires on Amendment | The FAADC application shall be updated to prevent this validation rule from firing incorrectly on Amendments:
|
Yes |