Our vendor, Huron Consulting Group, is sunsetting their current research administration product, and it will no longer be supported as of October 2031. Their product supports U-M eResearch systems including eResearch Proposal Management (eRPM), eResearch Regulatory Management (eRRM), eRAM, and M-Inform.
All customers using Huron Consulting Group’s research administration product, including U-M's enterprise systems for eResearch Proposal Management (eRPM), eResearch Regulatory Management (eRRM), eRAM, and M-Inform, as well as peer institutions nationwide will need to migrate to new solutions.
During this planning phase, your day-to-day work in eResearch systems won't change. To prepare for this change over the next few years, a cross-disciplinary team is developing a strategy to migrate the university research administration systems to new solutions. During this time, the university community will have opportunities to provide critical input by collaborating with project working groups on business requirements, vendor analysis, and feedback.
The current eResearch systems will continue to be supported while the journey to 2031 is underway. Routine system functionality improvements and fixes continue to be made as planned. At some point prior to the new system migration, there will be a determination surrounding functionality enhancements and customizations, and any changes will need to be evaluated and prioritized. Eventually, there will be a freeze on changes to the current systems.
The migration will include transitioning to to-be-determined software solutions, reengineering business processes, building new training materials, reestablishing system integrations – within the eResearch product lines and to other enterprise U-M systems, like M-Pathways Human Resource Management System (HRMS) and Financials – and rebuilding reporting mechanisms.
Conducting a Request for Proposal (RFP), transitioning to, and implementing new solutions are not part of this planning phase. New projects will be kicked off once the recommendation to executive sponsors is approved and funding is secured.
A Request for Information (RFI) helps U-M staff gather important details about the research administration software market. However, we cannot make purchases based solely on an RFI. By gathering information through the RFI process, we will be better prepared to issue Request for Proposals (RFP), evaluate different suppliers, and make informed decisions. The RFI process enables U-M staff to ask questions and gain insights into the latest features and limitations of the software, as well as obtain preliminary pricing data to help us budget appropriately for the later RFP phase.
An RFI (Request for Information) is a general inquiry asking suppliers of research administration software for information. It cannot be used to make a purchase. The RFI process is usually shorter and involves collecting written responses from suppliers and possibly product demonstrations. In contrast, an RFP (Request for Proposal) is a competitive bidding process that allows U-M to enter into contract negotiations with the top supplier after evaluations are complete. The RFP process is typically more thorough, involving written responses, product demonstrations, and proofs of concept with the leading suppliers. This ensures that we can make the best final selection based on comprehensive evaluations.
If you have questions or suggestions about the project and planning process, please contact the project team at [email protected].
The university community will have opportunities to provide critical input through collaboration with project working groups to identify business requirements, explore market alternatives, and evaluate replacement solutions. The project team will reach out as the planning effort progresses for your insights, expertise, and recommendations.