Proposal Review Process

THIS IS A DRAFT AND A WORK IN PROGRESS. ALL COMMENTS ARE APPRECIATED.

Unable to render {include} The included page could not be found.

After receiving the proposal, it is logged and categorized.

Request Type	Detail
Campus requests	These are for new systems or system enhancements which affect or are visible to the campus users.
Internal requests	These projects are usually not directly visible to the campus community and may include hardware, software, or system upgrades. These sometimes involve back-end work to campus systems, or requests to assess and introduce tools, utilities or technical solutions. Internal requests are typically submitted by OIT staff.
Mandated requests	These requests are usually mandated by the Federal or State Government, UC Office of the President, Auditors, or other regulatory agencies. They often contain compliance deadlines that the campus must meet.
Small requests	This category includes campus requests that are found to be less than 80 hours of work after a technical review has been completed (see below).

Proposals are routed to the responsible OIT manager for technical evaluation and time/budget estimate.
Estimated hours for development projects should include all phases of the development effort including requirements gathering, design, coding and testing, documentation, and implementation. Estimates for other projects such as vendor software should include time for installations, coordination, tracking, and implementation.

An initial budget for the project will be derived based on the project's estimated hours, any software licensing and hardware or equipment costs, training and possibly consulting costs. This is a ballpark estimate which may be revised once the project has been scheduled and the requirements are more completely understood.