Quick links
 
Office for Sponsored Research and Award Administration (OSRAA)
Other OSRAA Links

Back to Top

 

Cost Share

Back to Top

Templates and other useful information

NSF

NIH

OSU Library data management guide

Back to Top

Departments in the College of Science

GRA rates can vary by department. As of FY18, the rate is $2122/month typically among the departmetns. Please check with the CoS PIs for current rates for their students and postdocs.

Back to Top

Graduate Student OPE FY18

As per the CGE contract, OSU must now pay 88% of the premiums for health coverages during FY 18.   Effective 10-1-17 the OPE charge for Health Care contributions on Graduate Assistants (IGC account code 10994) is $420 per month.  Additionally the summer 1/9th coverage that most graduate assists take (I9C) is $140 per month.  In total, health related OPE rose from $489 to $560 per month as of Oct 1 2017, the start of their new plan year.

Back to Top

Postdoctoral Scholars (FY18)

For budgeting purposes on sponsored projects, please use the following guidelines:

  • OPE (fringe benefit costs) should be calculated at 14%.  10% covers social security, worker’s compensation, etc., and 4% covers the contributions to the retirement plan.  The retirement coverage (and deduction) begins after the first six month of their appointment.
  • For health insurance, coverage will be obtained through Student Health Services.  Depending on the coverage, the cost varies.  For a postdoctoral scholar and spouse/partner, an estimate of $500/month should be used. Note that this amount includes adding family, which is an optional expense the postdoc pays. According to PacificSource Plan Coordinator, the OSU contribution for health benefits for an individual is $385.83/month. 
  • The easy answer for FY18 is to use 24% to calculate OPE and insurance for postdoc scholars.

More information on pay rates and benefits can be found at: http://gradschool.oregonstate.edu/postdocs/stipends-and-benefits

Back to Top

Collaborators and Affiliations Template guidelines

  • Collaborators and co-Editors. A list of all persons in alphabetical order (including their current organizational affiliations) who are currently, or who have been collaborators or co-authors with the individual on a project, book, article, report, abstract or paper during the 48 months preceding the submission of the proposal. Also include those individuals who are currently or have been coeditors of journal, compendium, or conference proceedings during the 24 months preceding the submission of the proposal. If there are no collaborators or co-editors to report, this should be so indicated.
  • Graduate Advisors and Postdoctoral Sponsors. A list of the names in alphabetical order by last name of the individual’s own graduate advisor(s) and principal postdoctoral sponsor(s), and their current organizational affiliations, if known.
  • Ph.D. Advisor. A list of all persons with whom the individual has had an association as a Ph.D. advisor.
  • Note: Proposers using the Collaborators and Other Affiliations template for more than 10 senior project personnel will encounter proposal print preview issues. If there are more than 10 individuals designated as senior project personnel on the proposal, or if there are print preview issues when using the COA template, each completed template must be saved as a .txt file [select the Text (Tab Delimited) option] rather than as an .xlsx or .xls file. This format will still enable preservation of searchable text and avoid delays in processing and review of the proposal.

Back to Top

NSF Page formatting tips

This advice comes from Donn Forbes, a grant writer with a lot of experience with NSF proposals.

The NSF Proposal and Award Policies and Procedures Guide (PAPPG, the rule book) allows 10-point Arial type and requires at least 6 lines of text per vertical inch. If you draft a page in 10-point Arial and print it and measure the number of lines per inch with a ruler, you’ll find exactly six. So you would naturally expect that if you submit a proposal with 10-point Arial type, you’d be safe.

Not so.

Conversion to pdf often shrinks the type. Printers can also shrink the type. I know of cases in which reviewers or program managers printed the pdf files, measured the number of lines per inch with a ruler, found 5.9x lines per inch, and returned the proposal without review. 

If you’re going to submit an NSF proposal in Arial 10-point type, the best way to protect yourself from administrative disqualification is to select 1.15x line spacing instead of single spacing (Format > Paragraph  > Line Spacing > Multiple > 1.15). Then you’ll be safe.

back to top