eRPM FAQs
As with any new system, the questions will come quickly. We will post as questions have impact for the UMHS users and answers cannot be found through online help.
When should I contact my UL (Unit Liaison)?
- As often as you like
- When things aren’t behaving quite like you expect and you want to talk through/ see if a system change is possible
- When you have observations that are not “user error” or you find out a problem is due to software UMHS provides
- When you are about to tear out your hair
Heather Offhaus
Director, Grant Review & Analysis
Unit Liaison, Health System eRPM
hmills@umich.edu
(734)763-4272
Any “understood” business process for the Health System?
- Use the Notes sections any time you do an activity so that no one has to recreate what you did to know…
- Be ready to answer questions from colleagues
- Be ready to be patient
- Be ready to help each other
What questions should I be asking participating units on a proposal I am putting together?
The same ones you asked in the paper world… In addition, we recommend:
- What DeptID number do I assign for effort, space, subaccounts, etc?
and- Does your unit have any business processes I should know about before trying to route?
What answers should I be providing other units – even if they don’t ask?
The same ones you asked in the paper world… In addition, we recommend:
- The exact DeptID number to assign for effort, subaccounts, etc
- The exact space reference to load the space
- Where you want the DeptID to be overridden and replaced (especially important for clinical / hospital space)
- Whether your department/school has a unique process they should know about before trying to route
Should I add other grant / research administrators so that they have access to the PAF?
Maybe… they can enter the system and enter the things they would have written into a paper PAF for you – and you can always remove their access later… Examples might be if you wanted them to personally add their Co-Investigators space to the PAF prior to routing.
What do I need to know about Dept IDs and why are they important?
Dept IDs have two purposes
- Identify where a resource is being committed
- Generate the routing path to the unit that can guarantee
Sometimes these are not the same answer…
Space: You want to be committed Hospital resources, but the approval is the CDA for the clinical department. In order to route space (either found in the system OR entered as a generic area) to the correct area, you have to override the DeptID populated by MAIS from the space system with the DeptID associated with the CDA.
Usually the needs of mapping the routing path outweigh the identification / location of the resources
If you are identified as a Reviewer in the routing path, once the proposal is routed for approval, what can you do?
- You can see it in your Upcoming or In Box
- You may receive notices telling you where it is
- You may review and approve it simultaneously with another unit
- You may review and approve it out of order
- You can see changes that were made after you approved it
Note the word “You”… All individuals named to a Unit see the same thing, but not all are a reviewer who can approve…
Do I need to know how the routing path is set up and where the proposal “travels” for approval?
No. The eRPM system does all the mapping and routing and you do not need to know. However, during the pilot phase, it was very common for people to need to learn the routing paths so that they understood why they were getting notifications at different times or why the proposal seemed to go one place first. If you do want to learn more about the routing process, we will post documents showing the assigned path and your UL will be happy to walk you through the order assignment. We have also developed a short power point to give an example of how the proposal routes.
Is eRPM a replacement for MSGrants?
We are currently planning that the answer will be Yes. However, MSGrant data is used for
![]() |
![]() |
And we will not close MSGrant Database until we are sure we can pull the same reliable data.


