eResearch

Overview This procedure outlines steps for ORSP to initiate award processing from a Proposal Approval Form (PAF) in eRPM. This activity is available on PAFs in the state of "Submitted to Sponsor", "Negotiation in Progress", "Post-Submission Project Team Requests Action", or "Awarded" (in certain cases when the same PAF is used to create a second Award).

Overview At the end of an awarded project, ORSP can initiate project closeout to move the state of the award from "Active" to "Project Closeout" and send an email to the U-M Investigators with the PI role, the Sponsor PI (if applicable), and the Primary Post-Award Contact. The email indicates that ORSP believes the award should be closed, and is starting the closeout process. Navigation Role: ORSP > Award workspace > Initiate Project Closeout activity

OverviewThis document covers the basics of creating a minimal UFA or PAF record in eRPM so that an Ironclad workflow can be created, linked, and worked while the project team completes the rest of the PAF or UFA entry.The process involves:Creating the UFA or PAF record from the Innovation Partnerships workspace in eRPMUFA - Entering Project Team personnel and any other desired data

OverviewThe Innovation Partnerships Compliance Manage Deliverables activity allows those with the Innovation Partnerships-Compliance role to complete or remove Innovation Partnership Compliance-type deliverables related to an Award.NavigationRole: Innovation Partnerships - ComplianceStep-by-Step ProcessWhen you log in to eResearch Proposal Management (eRPM), your Home workspace displays. Note the following:

OverviewThe Interested Party role in eResearch Proposal Management (eRPM) is for U-M personnel who have interest in sponsored projects but do not have direct responsibility for proposal processing.Contents:

OverviewThis job aid explains the Internal ORSP Request activity to assign tasks to or request help from another ORSP staff member on a project (e.g., review contract; fully executed agreement is ready to award, etc.) Upon running the activity:

OverviewIf a new PI or key investigator is added to the project in an Award Change Request (ACR), the Sign ACR activity will be available on the ACR workspace. New investigators will receive an email notification of ACRs Awaiting Investigator Signature, or they can access the record from the ACRs Not Yet Signed By An Investigator list on the ACRs inbox tab. All newly added investigators, regardless of role, are required to sign using the Sign ACR activity.

Overview After the Export Control Office (ECO) reviews a TCP Amendment, they will send an email notification to request signatures. This procedure contains instructions for IT Managers to approve a TCP Amendment. Navigation Role: PI & Project Team (IT Manager) Approve a TCP Amendment Depending on the type of change, anyone specified as an IT Manager in the Technology Control Plan will be required to approve a TCP Amendment. Approving in eResearch Proposal Management (eRPM):

Overview After the Export Control Office (ECO) reviews the Technology Control Plan (TCP), they will send an email notification to request signatures. This procedure contains instructions for Signing the TCP. See Technology Control Plans & Licenses for more information about TCPs. Important Information

Overview Beginning with eRPM Release 5.2, Awards will have the ability to be "linked" by relating award records. Type 1 Example: Awards that do not necessarily share the same Sponsor Award Reference Number but for U-M purposes they represent the same work. The classic NIH example for this type is a competing renewal. Years 1-5 will be the first award. Years 6-10 would be funded as a second, independent award. In this case the two awards would be created independently with unique Award ID numbers. Each award will have its own award amounts and allocations.