|Forms & Deadlines|
|Change of Grantee|
|Other Federal Forms|
|Standard Due Dates|
|Progress Report Due Dates|
RPPR: Pilot and FDP Early Access
The materials on this page are for use by the 7 grantee institutions participating in the RPPR pilot beginning 4/20/2012, and Federal Demonstration Partnership (FDP) institutions which are provided with early access to the RPPR module beginning 6/15/2012.Activity codes for which an RPPR may be submitted are:
Early access to the RPPR module is provided as of 6/15/2012 to allow FDP institutions to begin training their investigators and research administration staff, and gain experience with the system before it is available to all NIH grantees and well in advance of an NIH requirement to use the RPPR. FDP institutions are not required to use the RPPR at this time, but are encouraged to take advantage of this opportunity in the FDP spirit of collaborating with Federal partners.
An RPPR training webinar will be provided for FDP institutions on June 18, 2012, from 1:30-3:00 EST, and archived on this webpage.
FDP institutions are encouraged to consider submission of RPPRs for July 2012 due dates since after that time most institutions will not have significant numbers of progress reports due until 10/1/2012 or later.Grantees may access a list of progress report that are due using the Status page in eRA Commons, selecting the Tab “List of Applications/Grants.” The far right column on the resulting table entitled Action will include an eSNAP link if a progress report is due. If the award is a Fellowship, the link will be RPPR. Eventually all “eSNAP” tabs and links will be replaced with “RPPR.”
The 7 pilot institutions are:
Pilot institutions may submit RPPRs up to two weeks late, and are encouraged to submit a variety of RPPR types (e.g., R01-like SNAPs, individual K SNAPs, etc.). Pilot institutions may also opt to submit an eSNAP, or, in the case of Fellowship awards, a paper PHS 416-9 progress report in lieu of an RPPR.
We would appreciate being alerted as soon as possible if you identify significant system functionality errors such as unable to submit, route, view, etc. We need these comments in a timely manner in order to incorporate any required code changes in the subsequent eRA release(s). There is no defined format for feedback but we would appreciate receiving emails so we can document issues.A Feedback “Go-to-Meeting” session is scheduled for Tuesday, June 26, 2012, from 1:30-3:30 (EST) for a general discussion with the pilot participants.
Back to the main Research Performance Progress Report (RPPR) page