9
OSP Updates MRAM May 2010 Office of Sponsored Programs May 13, 2010 Presented by: Casi Heintzman, Grant and Contract Administrator Carol Rhodes, Associate Director

OSP Updates MRAM May 2010

  • Upload
    malo

  • View
    37

  • Download
    0

Embed Size (px)

DESCRIPTION

OSP Updates MRAM May 2010. Office of Sponsored Programs May 13, 2010 Presented by: Casi Heintzman, Grant and Contract Administrator Carol Rhodes, Associate Director. Grants.gov Submissions. Grants.gov NIH submission process: - PowerPoint PPT Presentation

Citation preview

OSP UpdatesMRAM

May 2010

Office of Sponsored ProgramsMay 13, 2010Presented by:Casi Heintzman, Grant and Contract AdministratorCarol Rhodes, Associate Director

Grants.gov Submissions

• Grants.gov NIH submission process:o Proposal routed to OSP for review and submission per GIM

19 policyo Proposal must be submitted via Grants.gov by OSP,

without errors, by the Sponsor deadline

• Common error messages received by applicants from Grants.gov:

o PI Commons credential invalid or incorrecto PI Biosketch missing personal statemento Organization name of Key Personnel is missing on Key

Personnel page

2

NIH 2-day Correction Window

• NIH allows a “window” of time to correct errors after the Sponsor deadline.

• NIH sends error messages to OSP and the PI, based on the e-mail addresses in the proposal

• Effective May 8, 2010, NIH will only allow a 2-day window to correct errors after Sponsor deadline

• This is down from the 5 days NIH allowed applicants previously, due to grant.gov system issues.

• 2-day window starts at 5 pm on Sponsor due date, not at time of UW receipt of error notification!

3

Past Experiences with Grants.gov

4

• Grants.gov submissions can take time due to servers and the high traffic at peak deadline times such as June 5th

• Recent changes to the SF424 requirements mean a higher likelihood of errors

• System-generated error messages can lag from the time of submission to the time Grants.gov “reads” the error and sends an e-mail

• Some errors are atypical and require calls to the Grants.gov help desk and obtaining a “ticket number”

What does this mean for campus and OSP?

GIM 19: “Ready to Submit” proposal “IN OSP” no later than 5 days prior to Sponsor’s deadline

Ready to Submit for grants.gov submissions:

oAll fields and compliance section of GC-1 completeoSubcontract documents are attached to GC-1 oAll Sponsor required forms are complete, attached and match GC-1 dataoGrants.gov packet in final form (science, administrative, business, no placeholders or draft forms)oApplication is prepared per Sponsor requirements

June 5th dates to remember

June 5th is the deadline for new R01 applications to NIH

OSP needs Ready to Submit proposals by May 28th to review and decrease likelihood of errors upon submission

Any proposal due to Sponsor June 5th, received IN OSP after noon on June 3rd, will not be submitted without a GIM 19 waiver

Error Correction Process

7

If error message received and UW re-submits prior to Sponsor deadline:

oError message received

oOSP notifies department

oDepartment sends corrected application on GC-1

oOSP re-submits

Error Correction Process

If Error Message Received and UW re-submits after Sponsor deadline:

oError Message Received oOSP contacts departmentoDepartment must:

oPrepare cover letter outlining changes made to the proposaloInclude the previous grant tracking # reflecting submission prior to deadlineoInclude any “ticket” number if OSP contacted the G.g help desk due to an atypical error issueoRe-route changed/corrected application to OSP

oOSP re-submits

8

This process must occur within 2 days from Sponsor deadline, despite when Error message received!!!

Resources

Contact your:OSP AdministratorOSP Grant and Contract Coordinator

OSP Front Desk: (206) 543-4043

9

Online Resources:

OSP Website: http://www.washington.edu/research/main/osp

OSP GIM 19 text: http://www.washington.edu/research/osp/gim/gim19.html

NIH information on 2-day window: http://grants.nih.gov/grants/guide/notice-files/NOT-OD-10-088.html