Technology Solution Request
Technology Solution Request
Once your need is defined and scoped, the New Technology Solution Request supports the evaluation and procurement of technology solutions in alignment with the University’s architecture, security, risk, vendor, and compliance standards.
Features
It is advised to complete any applicable IRB, DUA, and/or ORIT consultation prior to submitting a request to ensure appropriate scoping, data considerations, and readiness. ORIT can assist you with the needed reviews as part of your research consultation.
You can find more information at the New Technology Solution Request Service Portal
Get Started
What's Included
- Technical scope and dependency review
- Identification of resource needs and project costs
- Initial security assessment
- Systems integration and architecture review
- Documentation and categorization for IT Governance review
- Assign IT Owner and Support Liaison
Planning & Timing
To support a smooth path to implementation, it is recommended to plan for ~3-6 weeks of lead time prior to study/project start, allowing adequate time for review, procurement, and coordination across teams.
The Approval Process
Select a step below to learn more about the process.
IT Governance
- Technology Request review and approval
- This includes:
- 3PA
- Technical Advisory
- Architecture Advisory
- IRB Approval
- InfoSec & Risk & Compliance
- Vendor Contracting /Procurement
Contact
If you have questions, please contact Research Support.
FAQs
- Improve visibility and transparency for project requests
- Improve portfolio project reporting & resourcing
- Improve engagement and collaboration
- Reduce tool redundancy
- Encourage operational excellence
- Streamline the project request and project approval process
The Technology Request process gives you expert help and visibility early in the process, to make sure you avoid issues such as:
- Buying software that is not suitable for integration into the university platform
- Hiring a developer to build a custom database that replicates a function about to be released in a University service
- Signing a contract for a new system without realizing that it requires high-risk sharing of sensitive data with a vendor, without suitable vendor protections in place in the contract.
- Investing in a large new system without considering the staffing required for setting up integrations or providing long-term administration and support.
No. As soon as you can articulate the business need, fill out the form and we will talk through available technologies, and next steps that would best fit your needs.
Technology requests will be reviewed by IT governance committees and senior leaders to determine the project timeline. There will be ongoing customer communications to alert you of the status.
Project intake (1 week)
During this time, we will:
- Document and categorize the Technology Request in the Enterprise portfolio
- Assign a Project Manager for an initial consultation
Initial consultation (1 week)
During this initial meeting, we will work with you to:
- Discuss the “Five Ws”: Who, What, When, Where, and Why
- Clarify details of the Technology Request
- Document known dependencies, timeline factors, and budget implications
- Identify stakeholders
Technical and business review (Duration is determined by the scope of the project)
During this time, we will:
- Assess technical scope and dependencies
- Assess technical feasibility
- Identify potential existing solutions
- Identify resource gaps/project costs
- Perform a portion of the security review
- Perform initial systems architecture review
- Business analysis
Intake completion (Duration is determined by the scope of the project)
During this time, we will:
- Contact you with the next steps and timeline
- Queue up the Technology Request for IT governance review