Technology Project Proposals


Proposals in this context are defined as special requests that are not already represented in our support pages.

The CUIMC IT Project Management Office (PMO) uses ServiceNow to collect and review ideas for technology-related projects. Anyone may turn in a proposal using the Submit an Idea form linked under Submit a Service Request. "Idea" is the term used in ServiceNow to track proposals as they flow through the project management process.

 Is my request considered a proposal? Yes No
Do you have a business problem that you think IT can help solve? Proposal Please contact us
Are you exploring a new application that you want IT to help evaluate? Proposal Please contact us


A proposal can also be submitted for the following reasons:

What happens when you submit a proposal? 1. End user submits a proposal: Submit the ServiceNow Idea form linked under Submit a Service Request on this page. The form creates an IDEA ticket in with the relevant information regarding the proposal. 2. Proposal reviewed: The PMO confirms project goals, scope are documented. The idea is triaged and scoped, ticket is changed to DEMAND and queued for approval 3. PMO Advisory reviews the proposal: The PMO guides the proposal through the approval process. The proposal is approved, prioritized, resourced and placed in the pipeline.

What is the proposal process?

  1. Use the Submit Idea form linked under Submit a Service Request on this page to describe the business problem, need, or opportunity.
  2. The form logs the idea in ServiceNow and someone from the PMO will contact you to get additional information.
  3. The idea then is presented by the customer or Certified IT Group (CITG) lead and reviewed at a Technical Steering Group (TSG) meeting. This allows the larger IT and CITG community to discuss tools already being used that may meet the need, and other groups having a similar need to join in on supporting a future state solution.
  4. The architecture team then reviews a proposed solution to make sure it will work in our environment and not be blocked or incompatible with other services.
  5. Security then reviews the proposed solutions to ensure that no data will be at risk. A BAA may also be needed and so the effort will be referred accordingly.
  6. IT Finance then reviews the proposed solution to understand cost and licensing.
  7. IT Support then reviews to ensure there is knowledge and documentation for the Service Desk and Desktop Support, and that resources are available to support the solution.
  8. The application portfolio is then updated so the new service is clearly documented and other important considerations like disaster recovery planning and license tracking are considered.
  9. Finally, the service is made available as a supported offering.