# Presentation: 854784

## User Group Presentation – Release 2.14April 23, 2007

## Overview – Release 2.14 Highlights

**GLOBAL CHANGES**
- NOTHING NEW
**INBOX Tab – Task Filters**
- Updates have been made to ensure that users are getting email notifications. (Ticket 12889)
**RFA Tab**
- New Choices for Type of RFA to accommodate the new BAA process (Ticket 12972)
- Applications Report has been updated to handle BAA applications.  The report is also updated dynamically when the application is associated with organization and authorized representatives in the database. (Ticket 13893)
**APPLICATION Tab**
- Program Officer now has option to forward Award File to FALD for applications attached to a BAA RFA (Ticket 13049)
**AWARD Tab**
- New Financial and Progress Report Sections on Grants File Header; new FFR functionality (Ticket 14374)

**Notes:**
Blue font indicates there is no screen shot in this presentation for that ticket.

Previously the Applications Report could not handle BAA applications because the Program Office is the same as the Line Office.

## BAA Process for Federal Program Officers – UNSOLICITED Proposals

**Step 1 **
**– ****Proposals coming via Grants.gov will be attached to the Competitive RFA for the Broad Agency Announcement published in the Federal Register: Opportunity Number NFA-NFA-2007-2000946, and will be routed to the inbox of the GMAC for the Line Office which owns the CFDA number in the proposal.  (See BAA Policy Directive from AGO.) Hardcopy proposals will be sent directly to the GMAC rep for that CFDA number.**

**Notes:**
Please also refer to the BAA guidance document from AGO for additional programmatic instructions.  These steps only outline the mechanics of how to use Grants Online to process BAA applications.

The BAA RFA has a separate Competition for each Line Office.  The workload routing for each Competition contains the name of the GMAC Representative for that Line Office.  

## BAA Process for Federal Program Officers – UNSOLICITED Proposals cont.

**Step 2**
**The GMAC representative will review the proposal and determine if it should be sent to a particular Program Office for funding.  (The actual Minimum Requirements check can be done either by the GMAC representative or by the assigned FPO for the proposal.)**
**Step 3**
**- Once a determination has been made regarding the Program Office to fund the proposal, that Program Office will create a RFA of type “Broad Agency Announcement”.**

**Notes:**
The GMAC rep will determine if the proposal meets mission goals and will check to see if the potential Program Office has funding. 

The former “Non-Competitive” RFA type in Grants Online has replaced by the various choices from the “Basis for Selection” question on the PO Checklist.  All RFA Types other than “Competitive” follow the old “Non-Competitive” workflow in Grants Online with one special difference in the Certify Award File step for BAA RFAs which will be seen in a later slide. 

The selection on this page will populate the headers on subsequent pages for this RFA.  However, on the next screen (RFA Details) you must again select the RFA type because the choices are broken down into subtypes.

## BAA Process for Federal Program Officers – UNSOLICITED Proposals cont.

**Notes:**
The selection of the RFA Type on this screen does not automatically translate to the PO Checklist.  The Federal Program Officer will still need to select the correct option when completing the PO Checklist.  For a BAA RFA, the PO Checklist Basis for Selection should be “Competitive”.

## BAA Process for Federal Program Officers – UNSOLICITED Proposals cont.

**Step 4**
**Once the new RFA has been created, the GMAC representative will submit a Help Desk request to move the application from the Competitive BAA RFA to the newly created RFA.  From that point the process follows the same workflow as the former “Non-Competitive” processing up to the “Certify/Revise Award File” task on the PO Checklist.  **
**	****NOTE:****  *****The new RFA will not be posted on Grants.gov but the task still needs to go to Steve Drescher in order to complete the workflow on the RFA.  A note should be placed in the workflow comments to let Steve know that it does not need to be posted at Grants.gov.  FPOs should not act on the “Notify Recipients” task.  To prevent an accidental notification, the Recipient Contact should not be entered on the RFA.***
**The Help Desk request to move a BAA application needs to include the following information:**
- Application ID or Grants.gov tracking number
- Funding Opportunity Number of New RFA
- Program Office on New RFA
- Name of New Federal Program Officer who will be handling the application

**Notes:**
Additional Notes on Step 4:
The Help Desk can actually move proposals to un-published RFAs.  However, an un-published RFA would not be available if a paper application needed to be entered.  It also would not be available if the Program Office wanted to copy it to a new RFA using “Create New from Existing”.

## BAA Process for Federal Program Officers – EXPECTED Proposals

**Step 1**
**The Program Office will create an RFA with type “Broad Agency Announcement.”  This RFA will be posted on the “Apply” section of Grants.gov in order for applicants to submit their proposals directly to the Program Office.  (This saves the GMAC representative from having to put in a Help Desk ticket to move the application.)**
**Step 2**
**The RFA Creator should use the Notify Recipients task to provide instructions to the recipient for submitting their proposal via Grants.gov.**

## Processing a BAA Proposal – Solicited or Expected

** ****As with any application processing, the Award Number must be entered during the “Conduct Negotiations” task as well as the Org Lookup and Authorized Representative Lookup.**
**There are no changes to the NEPA and Procurement Request tasks.**
**The PO Checklist should be completed as usual, except...**

## PO Checklist for BAA Application

**Basis of Selection on a BAA Application is “Competitive”**

**Notes:**
NOTE:  Unlike with the other RFA Types, Broad Agency Announcement is not one of the choices under Basis of Selection.

## PO Checklist/Award File – New BAA Workflow

**New Option: Forward to FALD**
**Attach Selection Package to Award File, mark “Internal Use Only”**
**Forward to FALD and wait for response *****before***** sending to Grants Specialist**

**Notes:**
The workflow on the applications for the BAA will include the option to forward the Award File to FALD under the Certify/Revise Award File task. The Program Officer is expected to put together a selection package for each application and forward that to FALD for review. The documents for the selection package should be attached to the Award File page to provide easy and consistent access for FALD users. The selection documents should all be marked as "Internal Use Only" when attached. When they have the task available to Forward to FALD, they will also have the task to forward to GMD. They should NOT just choose forward to GMD because it is available. When they forward to FALD, their task to Certify/Revise Award File will NOT go away. They need to wait until FALD responds with their comments before taking another action. This is up to the Program Officer, not up to the system. FALD choosing "FALD Comment" or "No Legal Objection" will have no effect on their ability to forward to GMD. If FALD has concerns, these should be addressed and the Award File should be returned to FALD if they indicate that they want to see it again. The point needs to be hammered home to the Program Officers that this workflow is maintaining maximum flexibility as requested by FALD. The Program Officers are expected to know what they are doing and when they should be forwarding items to FALD and GMD. The first thing that the Grants Specialist will be looking for is a positive review by FALD. If they see that FALD has not had the document, or that the Program Officer has failed to address concerns, it is quite likely that the Grants Specialist will reject the Award File. That will terminate workflow and the Program Officer will have to start over again. 

## PPR and FFR Updates

**New Grants File Screen**
**The Financial Report section includes the following report types:**
- SF-269
- SF-272
- SF-272A
- SF-270 (Request for Advance or Reimbursement)
**New Search Reports Screen**

## New Grants File Screen –Grants File Header

**New Financial Reports Information in the “Grant Information” box**

**Notes:**
The frequency for Financial Reports have been separated into frequencies for the SF-272 and SF-269.  The Comprehensive Frequency on the SF-269 indicates that only one SF-269 needs to be submitted at the end of the award.  It will be marked as FINAL.

## New Grants File Screen –Sub Sections

**Notes:**
Financial and Progress Reports are now in separate sections
The Financial Report section includes the following report types:
SF-269
SF-272
SF-272A
SF-270 (Request for Advance or Reimbursement)
The default sort order for Financial Reports and Progress Reports is Period Start, Period End
Final Reports are indicated in the name of the report 

## SF-269 Launch Page

**Notes:**
The recipient will have a dropdown box that will include two options:
Replace Report
View SF-269 Details

## SF-269 Top of Screen

## SF-269 Bottom of Screen

## SF-272 Launch Page

**Notes:**
The recipient has similar options as the SF-269 report.

## SF-272 Details – Top of Screen

## SF-272 Details – Bottom of Screen

## Multiple Award SF-272A Launch Page

## Multiple Award SF-272 Details

## Multiple Award SF-272 Details – cont.

## New Search Reports Screen

## New Search Report Results – Added Recipient Name

## Next Release...

**Report Reminder Notifications**

## Additional Resources

**GrantsOnline.QandA@noaa.gov**
**GrantsOnline.HelpDesk@noaa.gov**
- (301) 444-2112
- (877) 662-2478  (1-877-NOAAGRT)
**Grants Online PMO Website at **_**www.ofa.noaa.gov/~grantsonline**_ **to Access:**
- Grants Online Training/Support Resources
- Frequently Asked Questions
- What’s New page

**Notes:**
Coming in Next Release – Financial Reports - 269s and 272s in Grants Online!