LSA Research Administration Office

1. LSA Research Administration Office

2. Paper forms our Office Still signs • Material Transfers • Travel to Cuba • Research Faculty Hiring Packets • MICHR proposals • Anything research related that has a line for the Dean to sign

3. Electronic Systems/electronic signatures • eGIF • eRPM

4. What does the College Review TeamLook for in your Proposal? • For eRPM proposals is the PAF filled out in accordance with LSA Business Process • http://www.lsa.umich.edu/UMICH/lsa_research/home/Resources%20and%20Links/Research%20Administration%20Toolkit/LSA%20Research%20Admin%20Advisory%20Group/eResearch/eResearch_PAF_Questions%20(lsaraag).xls • All budget and budget justification documents are finalized and loaded in PAF • Ideally finished packages! Your faculty are looking for your guidance • For eGIF does it follow the templates at http://www.lsa.umich.edu/research/gateway/egif_examples • Special attention is given to resource commitments • eRPM--Space, Costsharing, faculty effort, subawards, subaccounts, PI eligibility, budget, and budget justification, indirect rate, DMP. Upload supporting emails • eGIF--Commitment documentation is critical!!! Upload supporting e-mails

5. “The Perfect Proposal” • All the final documents are uploaded into eRPM • A copy of the sponsor guidelines is attached with the indirect rate circled if not the normal rate. (If the indirect rate is 36.3952% and it’s in the sponsor guidelines—include the guidelines—don’t make us dig for it). • If thereare multiple PI’s on the project, an internal budget that breaks out each of their pieces of the budget and matches the subaccounts on the PAF. • Cost-sharing approved before the PAF is routed. Include the e-mail approvals—attach them to the PAF. • A clear budget justification that supports the budget and details what the supplies and materials are (A21). • Items in the proposal can be interpreted at award and implemented by anyone (i. e. appointments, cost-sharing commitments, equipment, etc) • The $ amounts match everywhere in the documents uploaded with the PAF. • There’s a final version of the research narrative to see how the science meshes with the budget.

6. Things we don’t look at • Not looking for formatting or that the sponsor forms are filled out correctly—that’s the PI/department’s responsibility to read and understand the Sponsor’s rules • We never go into the sponsor’s grant application systems to look at applications (we can’t even if we wanted to) • Not looking at specific budget $’s (If the amount budgeted for someone’s salary or tuition, etc is wrong we won’t catch that.) • Situations covered by departmental rules (i.e. course buyouts and space)

7. Steve’s resources • You – the department Research Administrators • LSA Business Process http://www.lsa.umich.edu/UMICH/lsa_research/home/Resources%20and%20Links/Research%20Administration%20Toolkit/LSA%20Research%20Admin%20Advisory%20Group/eResearch/eResearch_PAF_Questions%20(lsaraag).xls • eRPM References Materials (http://www.umich.edu/~eresinfo/erpm/training.html) • eRPM Help (4-4357) • DRDA (http://www.drda.umich.edu/) • eGIF examples (http://www.lsa.umich.edu/research/gateway/egif_examples) • LSA Research Website (http://www.lsa.umich.edu/research/) • MRS (https://www-a1.lsa.umich.edu/admindata/) • Sponsors websites • When all else fails Google

8. eRPM Review • Steve gets the e-mail from eRPM saying the PAF is ready for LSA’s review • Steve reviews PAF • If necessary returns PAF to department for any corrections or clarifications • Talks with Peggy about any issues that are unusual • Peggy determines if follow-up with the Associate Dean or other UM entity is necessary before she signs it. • Once its ready to sign Steve puts a note in eRPM and then forwards the eRPM message to cue Peggy to sign it • Peggy reviews for any additional questions and alerts PI Team if compliant with deadline • Once Peggy signs proposal it is off to DRDA for their review. • Steve checks his eRPM inbox at the start of the day and at the end of the day, as well as periodically throughout the day, to make sure no proposals get lost due to a failure in the e-mail notification.

9. eGIF Review • Peggy gets ane-mail from eGIF saying the application is ready for LSA’s review and sends to Steve for first review • If necessary Steve contacts the PI or Key AD for any corrections or clarifications • Talks with Peggy about any issues that are unusual • Once its ready to sign Steve forwards to Peggy for her review • After Peggy reviews it she forwards it to the appropriate Associate Dean for their funding decision and/or approval. • Proposal goes on to other funding sources for their decision (i. e. Rackham, OVPR, Humanities Institute) • Once Peggy has entered LSA funding decision, Steve finishes process by notifying the PI of the LSA award. The transfer form for obtaining the funds is part of this process. • The commitment is input into the Unit Defined Commitment Systems until the transfer is made.