1 / 47

AECOM Office of Grant Support aecom.yu/ogs Belfer 913,917; x3642

AECOM Office of Grant Support http://www.aecom.yu.edu/ogs Belfer 913,917; x3642 hathaway@aecom.yu.edu janicki@aecom.yu.edu OGS Grants.gov Info http://www.aecom.yu.edu/ogs/Gg. Grants.gov Electronic Submission of Applications to Federal Grant-making Agencies April 5-6, 2006.

chanda-riley
Download Presentation

AECOM Office of Grant Support aecom.yu/ogs Belfer 913,917; x3642

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. AECOM Office of Grant Support http://www.aecom.yu.edu/ogs Belfer 913,917; x3642 hathaway@aecom.yu.edu janicki@aecom.yu.edu OGS Grants.gov Info http://www.aecom.yu.edu/ogs/Gg

  2. Grants.gov Electronic Submission of Applications to Federal Grant-making Agencies April 5-6, 2006

  3. WHAT is Grants.gov? WHY does Grants.gov exist? WHO is affected by Grants.gov? WHEN does Grants.gov happen? HOW does Grants.gov work?

  4. WHAT is Grants.gov?

  5. Grants.gov will be the portal for all grant applications to 26 federal agencies Proposals are submitted through Person-to-System or System-to-System modes Person-to-System (Forms-based; uses PureEdge software) NIH Grants.gov Application Format Transformation DOD PI Desktop NSF Database System-to-System (aka “S2S”)

  6. Grants.gov will be the portal for all grant applications to 26 federal agencies AECOM proposals will be prepared and submitted using PureEdge software AECOM PI Grants.gov Application Format Transformation NIH Person-to-System (Forms-based; uses PureEdge software)

  7. PHS 398

  8. SF 424

  9. New Terminology NIH/PHS 398Grants.gov/SF 424 New New Competing Continuation Renewal Revision or Amendment Resubmission Competing Supplement Revision PA and/or RFA FOA (Funding Opportunity Announcement) PI PD/PI (combined term) SO (Signing Official) AOR (Authorized Organizational Rep) Other Support Current & Pending Support Literature Cited Bibliography & Refs Cited Consortium Budget Subaward Budget

  10. WHY does Grants.gov exist?

  11. eRA History 1993: Al Gore releases National Performance Review plan “to reinvent government to work better and cost less”

  12. NIH eRA History 1994-1997: Early pilot testing of electronic proposal submissions to NIH, DOD, DOE by 10-20 major grantee institutions 1999: NIH eRA Commons established to provide grants administration support through the Internet

  13. NIH eRA History 2003-2004: NIH conducts pilots in which 100 PIs from 30 institutions submitted electronic applications through commercial service providers. Nov 2003: NIH Commons begins eSNAP pilot to accept non-competing progress reports electronically Jan 2005: NIH opens door for electronic submissions via service providers for select grants

  14. August 19, 2005 NOT-OD-05-067 • NIH announces plans to: • transition from the PHS398 application to the SF424 Research and Related (R&R) application • simultaneously transition to electronic submission via Grants.gov by the end of 2007

  15. WHO is affected by Grants.gov?

  16. Grantor Agencies Grantee Institutions Principal Investigators Department Administrators Grant Reviewers Software companies

  17. WHEN does Grants.gov happen?

  18. Redefining the concept of “deadlines”… Electronic applications are different. Errors detected by federal agencies after the initial submission will need to be corrected. The resubmitted corrected version of the proposal must be received by the agency PRIOR to the original published deadline for the grant program.

  19. Hypothetical Grants.gov Submission for 1 June 2007 NIH Deadline Mon 21 May: Internal forms approved Tues 22 May: PI completes full proposal Tues 22 May: Proposal transmitted to Grants.gov Weds 23 May: Errors detected by agency Thurs 24 May: Errors “corrected” by PI and staff Fri 25 May: Proposal resubmitted to Grants.gov Sat 26 May: Errors still detected by agency Tues 29 May: Errors corrected by PI and staff Weds 30 May: Server slowdown delays sending Thurs 31 May: Proposal resubmitted to Grants.gov Fri 1 June: Error-free submission confirmed

  20. HOW does Grants.gov work?

  21. The Grants.gov Process Find a grant program Download and complete an application Submit application via AOR Correct errors and resubmit (if necessary)

  22. The Essentials: Register as “PI” on NIH Commons Install the PureEdge viewer Install PDF generation software Download FOA narrative Download FOA application package Follow FOA instructions

  23. The Essentials (continued) Prepare application Consult Grants.gov application guide Submit internal forms early Request AOR submission early Monitor application progress Reject error-free application image (optional)

  24. Register as “PI” on NIH Commons AECOM faculty investigators who plan to serve as PIs may open an NIH eRA Commons account by completing an authorization form: http://www.aecom.yu.edu/ogs/NIHCommonsRegistration.htm Install the PureEdge viewer http://www.aecom.yu.edu/ogs/gg/Downloads.htm

  25. Another option for Mac users?? BOOT CAMP Intel-based Macs only

  26. Funding Opportunity Announcements FOAs include all NIH PAs and RFAs. Identify FOAs using… NIH Guide http://grants.nih.gov/grants/guide/index.html Grants.gov http://www.grants.gov/ Ex. RFA-RM-06-005 PAR-06-093

  27. Funding Opportunity Announcements PA-06-309 Grants.gov application download site Parent R21 (with AECOM info)

  28. Preparing an Application Only the specific application package associated with an FOA can be used to apply. Some fields of the application are pre-filled from the announcement. The forms must be filled out according to the accompanying application guide and any specific guidelines in the announcement.

  29. All mandatory Grants.gov fields are high-lighted and denoted with an asterisk.

  30. However, there are application fields not marked as mandatory on the federal-wide form but that are required by NIH. For example, the credential field of the R&R Senior/Key Person Profile component MUST contain the PI’s assigned eRA Commons User ID for NIH to process the application submission.

  31. Preparing Text Attachments NIH only accepts attachments in PDF format. Do not put special characters in file names. Disable all security features in the PDF document. Do not send PDF documents with editable fields.

  32. WARNING!! When savings changes to a PureEdge application file, check both name and location of new file. Saves following PDF attachment may be made to the PDF source folders. This can result in storage of proposal components in multiple files.

  33. Consult the Grants.gov application guide 180 very helpful pages

  34. Submit Internal Forms General procedures for internal approvals have not changed. Failure to submit GA6742 at least eight (8) working days prior to agency deadline may make successful electronic submission impossible.

  35. Submit Internal Forms • GA6742 must be accompanied by: • detailed budget, • modular budget narrative or budget justification, • SF424 cover (2 pages), • PHS 398 cover supplement* (2 pages), • PHS 398 Checklist* (2 pages), • any other relevant documentation. • *part of PureEdge SF424 package

  36. Note: PI signatures on grant applications are no longer necessary. However, NIH will soon require all institutions to maintain a written certification with unique PI signature and date in support of the submission of the specific application. AECOM’s internal grant approval form GA6742 will soon be updated to include a new assurance page requiring PI signature.

  37. Submit application via Authorized Organizational Representative (AOR) AORs submit grant applications on behalf of institutions seeking federal funding. Each academic department will have an administrator serving as an AOR. Departmental administrators must request AOR designation by completing the 3 step process outlined at http://www.grants.gov/Register

  38. Submit application via AOR Principal investigators will transfer completed application files to his/her department’s AOR for proposal submission. Plan to submit as early as possible. If a department does not have a designated AOR, the PI will transfer the application to Grant Accounting for submission.

  39. Submit application via AOR No proposal will be submitted to NIH via Grants.gov prior to final approval of internal form GA6742.

  40. Monitor Application Progress Once the application has been submitted, Grants.gov and eRA Commons will send a series of status Email notifications. Grants.gov sends notifications to the AOR only; eRA Commons sends notifications to the AOR/SO and the PI. Email can be unreliable – applicants should proactively check the status of their applications in eRA Commons after submission.

  41. Application Received by Grants.gov Tracking No. Time stamp

  42. PI and SO must log into NIH Commons to check proposal status. Error and warnings will be displayed. Errors must be corrected and a new application submitted. Warnings do not require corrections.

  43. Once all errors are corrected, a grant image is generated and made available for viewing by the PI and the Signing Official (SO). NIH is expected to announce the elimination of the current requirement for PI and SO verification/approval of the grant image. Instead, either PI or SO may reject the error-free proposal within 48 hours of its availability on NIH Commons. If a proposal is not rejected, it will continue forward to review.

More Related