Should I participate?
- Even if your project doesn't initially seem to meet the 200-45 criteria, broadly consider whether the system might be of interest or others or how it might expand over time.
- To ensure that your tactical and strategic decisions can benefit from campus feedback, it is generally better to err on the side of increased engagement and early participation.
Submission Requirements
As described in policy, proposed administrative computing systems that meet one or more of the following criteria must participate in the 200-45 review process:
- Systems that cross organizational boundaries.
- Systems critical to meeting the University's business needs, regulatory obligations, or the enterprise-wide delivery of educational content. this includes high-risk systems that could result in a failure by the University to perform essential functions, a significant loss of funds, or significant liability or legal exposure.
- Systems for which funding is sought from the Provost & Executive Vice Chancellor for development, implementation, modification, or maintenance.
- Systems for which total implementation costs (purchase, programming, consulting, integration, and first-year maintenance) equal or exceed $150,000.
Applicable administrative systems can originate from both academic and administrative departments at all levels within the University.
Types of Submissions
The following materials briefly describe the two types of 200-45 submissions. For details regarding the recommended submission formats, see Section C of the 200-45 Procedures.
Project Description (required)
A project description provides a structured overview of a project’s functional goals, technical approaches, timeline/budget, and risks/mitigations. It is typically limited to 5-10 pages in length, although sponsors often elect to provide additional supporting details via one or more appendices.
The following are typical components of a project plan:
- Business Need
- Stakeholder Value
- Business Impact
- Infrastructure Integration
- Accessibility
- Administrative Integration
- Scalability
- Timeline / Budget
- Risks / Mitigations
Conceptual Proposal (optional)
Prior to submitting a full project description, sponsors are encouraged to submit conceptual proposals that reflect early thinking about a potential project. These optional reviews allow a sponsor to receive early, structured feedback before all major project elements are defined, thereby informing development of the full project description. As such, a project concept briefly describes the basic elements of a proposed project, typically in 1-2 pages.
It is not expected that all aspects of the proposed project will be described at this stage, as the purpose of the conceptual review is to provide feedback before major project decisions have been made. Nonetheless, to the extent that specific ideas or assumptions about the project already exist, including them can generate valuable feedback.
The following are typical components of a project concept:
- Business Need
- Value and Impact
- Opportunities and Constraints
- Initial Ideas and Assumptions
Contact Information
To submit your project or ask questions about the 200-45 review process, please contact Jeff Barrett in the office of the Vice Provost, IET.