The Vendor is required to provide research administration software platforms with which you have direct implementation experience, and indicate whether your approach is vendor-agnostic or focused on particular solutions.
- Web-based system
• Support for all major browsers (chrome, Firefox, edge, etc.) On desktops/laptops. Include notes on look & feel and university design principles used.
• Ability to support full functionality on laptop/desktop and multiple operating systems. (MS windows and mac OS)
• Ability to support mobile and/or adaptive tablet devices.
• Ability to generate and print u-m defined versions of screens/data.
• Efficient search and navigation of record listings by type. Include typical search/navigation times for large lists and work areas.
• Database search using approximate ("fuzzy logic") search algorithm for data elements and documents.
• Designed to store and manage large data sets (e.g., 100+ columns, up to a million rows).
• Able to query all data rapidly (results in seconds, via application and APIS/interfaces). (data return and rendering from database)
• Any system function/action should execute and return results in a few seconds. (application user facing functions/mechanics)
• Ability to leverage AI features (note current/future support and approach to rapid innovation).
• Ability to add data elements to existing compliance areas including custom data/fields with selectable data types and code values.
• Ability to configure screens/fields/forms for compliance areas. (including branching logic)
• Ability to define complex workflow based on states, data fields, and security roles
• Ability to conditionally show forms/screens and fields based on institution requirements.
• Ability to create and write our own data validations for errors and warnings.
• Ability to trigger system actions/tasks based of other actions/tasks or response to questions (e.g., a positive response to a question triggers an ancillary review; a proposal not getting funded alerts the corresponding protocol)
• Ability to add/update/maintain data on all screens/pages/views and activities.
• Ability for business users or administrators to manage code value lists (agency picklists) in real time.
• Ability for a system activity audit trail that is easily queried with before/after, date/time, and user data. This is for an individual protocol, proposal, award, etc.
• Ability for administrators to update data attributes or trigger activities (e.g., deadline updates, state changes).
• Ability for developers to perform custom development directly on your platform. If so, please describe to what extent. If not, what features can be modified by an external development team without a ticket/enhancement request?
• Ability to Include/construct URLs and hyperlinks (internal and external; parameterized for access).
• Ability to control attributes on department and external entity tables
• Ability to set integration control attributes (effective date, effective status)
• Ability to delegate user role and department management to specific user roles so department personnel can view/maintain data on access to department information (e.g. who can review, who can approve, who should approve a disclosure)
• Ability to store organization contact information attributes
• Ability to host high level sponsor data in a single table that includes data feeds plus additional research-related custom attributes.
• Ability to set a Department hierarchy in each research module for at least three levels and manage sets of people in each department (division, department, school).
• Ability to create an action items to flag an item for review or to take action. E.g., HR appointment is inactivated would trigger all associated submission, awards, protocols for review.
- Email Functionality
• Ability to set up and send system-generated emails for institution-identified business process needs.
• Ability to add email content
• Ability to control subject line content
• Ability to control sender/recipient/cc lines
• Ability to add attachments to an email.
• Ability to embed URLS into email notifications.
• Ability to embed action links that take you directly into the Research Suite.
• Ability for out-of-office indication visible to email sender.
• Ability to view recipients of email correspondence.
• Ability to email-into-record feature: attach incoming emails (body, sender, recipients, and attachments) to relevant records.
• Ability to allow/disallow specific users and/or /domains on the email-into-record feature.
• Ability to trigger system actions based on incoming email (e.g., subject-line-based triggers).
• Ability to send reminder email notifications masse (e.g., send reminders for upcoming protocol expirations, reminders to users who haven’t yet disclosed.
• Ability to view history of email communications and the last time a person was sent an email.
- Contract Period/Term: 5 years
- Questions/Inquires Deadline: February 20, 2026
