Difference between revisions of "FAADC Version 1.2"

From FPDS-NG

Line 172: Line 172:
 
<td align="center">Yes</td>
 
<td align="center">Yes</td>
  
<tr>
 
 
<td style="width:95px" valign="top">IAEMOD-30131
 
 
<td valign="top">FAADC Issue with Action Type for Version 1.2
 
 
<td valign="top">The FAADC application shall be updated to prevent validation rule FAADC:2D3 from firing:
 
 
*<i>"Period of Performance End Date" cannot be earlier than the "Action Date" when users select REVISION as “ACTION TYPE”.</i>
 
 
A new validation rule shall be created:
 
*FAADC:2D6 - <i>When “Action Type” is “New Assistance Award”, “Continuation”, or “Entity Change”, the “Period of Performance End Date” cannot be earlier than the “Action Date”.</i>
 
 
This will permit users to report administrative changes after the Period of Performance of an agreement has ended.
 
 
</td>
 
 
<td align="center">Yes</td>
 
<ul>
 
<tr>
 
  
 
</table>
 
</table>

Revision as of 22:59, 20 June 2024

Schedule

DescriptionStart Date End Date
Beta DeploymentJuly 01, 2024July 01, 2024
Government Acceptance Testing July 08, 2024July 19, 2024
Production Deployment November 16, 2024November 16, 2024

Document Changes

DocumentationChanges Required
XML SpecificationsYes
Web ServicesYes
Data DictionaryYes
NASA Specific Data DictionaryNo
Use Case SummaryYes
Validation RulesYes
ezSearchYes
Atom FeedsYes
Online HelpYes
User ManualYes

*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_Webservice_Integration_Specifications_V1.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/ProblemSolutionImpact 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:

  1. Indirect Cost Federal Share Amount, which used ‘genericFloat01', will now have a new XML tag of 'indirectCostFederalShareAmount'.
  2. Funding Opportunity Goals Text, which used ‘genericString01’, will now have a new XML tag of 'fundingOpportunityGoalsText'.
  3. Service-Disabled Veteran-Owned Business Joint Venture, which used 'genericString02’, will now have a new XML tag of 'isServiceDisabledVetOwnedJointVenture'.
  4. SBA-Certified Women-Owned Small Business, which used ‘genericString03’, will now have a new XML tag of 'isSBACertifiedWomenOwnedSmallBusiness'.
  5. SBA-Certified Economically Disadvantaged Women-Owned Small Business, which used ‘genericString04', will now have a new XML tag of 'isSBACertifiedEconDisadvWomenOwnedSmallBusiness'.
  6. Small Business Joint Venture, which used ‘genericString05’, will now have a new XML tag of ‘isSmallBusinessJointVenture'.
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.

FAADC V1.2 Assitance user screen.png

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 (April 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:

  • 4A - Federal Action Obligation
  • 4C - Non-Federal Funding Amount
  • 4D - Face Value of Direct Loan or Loan Guarantee
  • 4E - Original Loan Subsidy Cost

The FAADC application shall be updated with these new data elements:

  • 7C - Predominant Assistance Listing
  • 4H - Assistance Listing’s Federal Action Obligation Amount
  • 4I - Assistance Listing’s Non-Federal Funding Amount
  • 4J - Assistance Listing's Face Value of Direct Loan or Loan Guarantee
  • 4K - Assistance Listing’s Original Loan Subsidy Cost

The FAADC application shall be updated with the following validation rules:

  • FAADC:7A3 - “An Assistance Listing number cannot be used more than once on a record.”
  • FAADC:7A4 - “Only a maximum number of 5 Assistance Listings can be added to a record. Please limit the Assistance Listings to 5.”
  • FAADC:7A5 - “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."
  • FAADC:7C1 - “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."
  • FAADC:7C2 - “One Assistance Listing must be marked as the ‘Predominant Assistance Listing’."
  • FAADC:7C3 - “Only one Assistance Listing can be the ‘Predominant Assistance Listing’."

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 - “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."
  • FAADC:4A5 - “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."
  • FAADC:4B2 - “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."
  • FAADC:4D1 - “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."
  • FAADC:4E1 - “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."
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:

  • FAADC:1K1 - "If "Assistance Type" is Grant or Cooperative Agreement, the "Discretionary" data element is required."
  • FAADC:1K2 - "If a value is provided for "Funding Opportunity Number," then either "Competed Opportunity" must be 'Competitive Procedures were used' or "Discretionary" must be 'Yes'."
  • FAADC:1K3 - "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'."
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:

  • FAADC:1E3 - "If a value is provided for “Funding Opportunity Number”, then “Funding Opportunity Goals Text” must also have a value."
  • FAADC:1E4 - "If a value is provided for “Funding Opportunity Goals Text”, then “Funding Opportunity Number” must also have a value."
  • FAADC:1E5 - "If "Competed Opportunity" is 'Competitive Procedures were used' and "Discretionary" is 'Yes,' then both “Funding Opportunity Number” and “Funding Opportunity Goals Text” are required."
  • FAADC:1E6 - "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'."
  • FAADC:1J5 - "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'."
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:
  • "Federal Interagency Committee on Education (FICE) Code" must be valid value.”

This affects Assistance Amendment record requests including Validate(isComplete)/Correct/Approve.

Yes