UM IT RFP Process

UM IT's approach is to meet departments at the door, not at the checkout.

A guide for UM departments planning a technology purchase and for UM IT staff who support them.

The short version

  1. Before an RFP posts: contact UM IT and UM Procurement Services. This is the stage when UM IT can answer technical questions and help shape the requirements.
  2. After an RFP posts: every vendor question goes through the Procurement Officer who posted it. UM IT staff cannot answer these questions, even to be helpful.
  3. If a gap shows up after posting: talk to the Procurement Officer right away. Do not gather answers from UM IT on your own.

Why this process exists

RFPs follow strict rules so the bidding stays fair, open, and competitive. These are the reasons behind the rules.

  • Fairness. The rules prevent any committee member or vendor from gaining influence, or being unfairly discredited, during the bid.
  • Confidentiality and conflict of interest. Only RFP committee members have signed the required non-disclosure and conflict-of-interest form. UM Procurement has advised that people who have not signed, including UM IT staff, are not allowed by law to take part once the RFP is open.
  • Blackout period. From posting until a contract is awarded, discussing the bid is not allowed, including gathering more information from outside the committee. Committee discussion is limited to official evaluation meetings.
  • Details must come first. All technical specifications and scoring criteria must be complete before the RFP posts. A posted RFP cannot simply be fixed mid-stream.
  • A weak RFP costs more. Missing details can lead to poor proposals, vendors who decline to bid, vendor complaints and challenges, or a product that does not work at UM.

The process at a glance

Stage What is happening What to do
1. Planning (before the RFP posts) Requirements, technical specifications, and scoring criteria are written. UM IT input is welcome and expected.
  • Contact UM IT and UM Procurement as soon as a technology purchase is being considered.
  • Share the draft requirements for review before the RFP posts.
2. RFP open (posting until contract award) A blackout period applies. Only the Procurement Officer and the RFP committee may discuss the bid.
  • Send every vendor question to the Procurement Officer who posted the RFP.
  • Do not ask UM IT or anyone else outside the committee for help.
3. Contract awarded The blackout ends.
  • Bring UM IT in to plan implementation, such as sign-in setup, security and accessibility review, and integrations.

What UM IT will want to know before an RFP posts

These topics come up in most technology purchases. Raising them early prevents surprises and lets UM IT plan its time.

Topic Why it matters What UM IT needs from you
Sign-in (SSO) Setting up single sign-on takes time from UM IT's identity team, which already has other projects underway. Will people sign in with their UM accounts? Which groups: employees, students, or both?
Accessibility Software used at UM must be accessible, and an accessibility review takes time. The standard the vendor must meet (UM targets WCAG 2.1 Level AA) and the documentation the vendor must provide.
Data and security Any product that handles UM data needs a security review. What data the product will hold. Plan to require a SOC 2 report or a HECVAT (a standard higher-education security questionnaire) from the vendor.
Banner integration Connecting to Banner requires approval and a technical fit. Whether the request went through the UM Banner Advisory Committee (UBAC). Which Banner information is needed. Whether the vendor is an official Ellucian partner and supports Ellucian integration management.
Other connections Each connection adds work, and some systems may not be open to third parties. A list of every system the product must connect to, such as directories, APIs, email, and other platforms.
Consulting and services Technology work can be tucked into the scope of work of a consulting RFP, and it still needs review. Share consulting and services RFPs with UM IT too.
UM IT capacity UM IT's project list is always full. Prioritizing a new project, even a relatively small or quick one, requires approval from IT leadership (IT executives, managers, or team leads). UM IT will say early what is realistic, such as about [x] hours per week for the project, so expectations are set before posting.

Rules while an RFP is open

Do

  • Send every vendor question to the Procurement Officer who posted the RFP. That person is the single point of contact and brings in the right experts.
  • If a vendor contacts you directly, do not reply about the RFP. Forward the message to the Procurement Officer, who will decide how to handle it.

Do not

  • Ask UM IT, or anyone outside the committee, to help answer vendor questions or gather more information about the bid.
  • Share informal answers, even ones that seem harmless or easy to provide.
  • Discuss the bid with anyone outside the committee.

If a question about an open RFP reaches UM IT staff

First, check whether the RFP has posted. If it has not, UM IT can help; use Message B below. If it has posted, follow these steps.

  1. Pause. Do not answer, even in part, and do not send technical details.
  2. Bring in Procurement right away. Notify [UM IT Procurement contact] and the Procurement Officer on the RFP, if known.
  3. Redirect the requester. Use Message A below.
  4. Record it. Note the redirect in the TDX ticket.
  5. Flag unplanned purchases. If the request shows a purchase UM IT did not know about, forward it to UM IT Executive Leadership so UM IT can plan its time and reach departments earlier next time.

If a gap shows up after the RFP posts

Vendor questions can reveal details that were missed. The RFP cannot be fixed mid-stream, so talk with the Procurement Officer right away. UM Procurement has described two options, and the Procurement Officer may offer others:

  1. Answer as well as possible. The most technically knowledgeable committee member answers. The RFP may continue, but weak answers risk inadequate proposals or vendors who decline to bid.
  2. Withdraw and reissue. Tell vendors there is not enough information to answer properly, withdraw the RFP, work with the UM IT teams responsible for the technical pieces, rebuild the RFP with that detail, and thank the vendor for raising the issue.

In a past case, UM Procurement recommended the second option. It adds delay, but it avoids a failed bid, vendor complaints, and scoring proposals that may not work at UM.

Ready-to-use message templates

Message A: reply to a question about an open RFP

Subject: Your question about [RFP name]

Hello [name],

Thank you for reaching out. Because [RFP name] has posted, vendor questions must go through the Procurement Officer who posted it, [name and contact]. While an RFP is open, only the Procurement Officer and the RFP committee may discuss the bid. This keeps the process fair for every vendor and protects the university from conflict-of-interest problems. UM IT staff therefore cannot answer technical questions about this RFP, even informally.

Please send the vendor's question to [Procurement Officer]. They can bring in the right experts and explain your options. I have also let [UM IT Procurement contact] know.

After a contract is awarded, UM IT is ready to help with sign-in, security, accessibility, and integrations. For future purchases, please contact UM IT before the RFP posts at [contact or link].

Thank you,
[name]

Message B: early outreach before an RFP posts

Subject: Planning [project name]: a short meeting with UM IT

Hello [name],

UM IT would like to help [department] before the RFP for [project] posts. This is the only stage when UM IT can help shape the technical requirements. Please plan to provide to UM IT and UM Procurement Services the following information:

  • Sign-in (SSO) needs
  • The data the product will handle and the security documentation to require
  • Accessibility requirements
  • Connections to Banner or other systems
  • Timeline and UM IT capacity (currently about [x] hours per week for a project like this)

Please share the draft requirements by [date] so they can be reviewed before posting.

Contacts and links

Role Contact When to use
UM IT Executive Leadership UMITExecutiveLeadership@mso.umt.edu A purchase UM IT was not told about.
Director of Software and IT Procurement Robert Giblin, robert.giblin@mso.umt.edu Immediately, when a question about a technology RFP arrives.
Procurement Officer on the RFP [name and email from the RFP posting] The only contact for vendor questions while the RFP is open.
UBAC request BannerAdvisoryCommittee@umconnectumt.onmicrosoft.com Before the RFP is written, for any Banner integration.
UM IT ticket system UM Solutions Center To record requests and redirects.
Was this helpful?
0 reviews