How to Submit a Project Request to the Office of Information Technology (OIT)

Tags projects

Description

Step by step instructions for how to submit an OIT Project Request.

Instructions

  1. Go to the UCO Service Desk Client Portal.
  2. Select Services.
  3. Select OIT Internal Services.
  4. Select OIT Project Request.
  5. Click the blue Request Project option on the right hand menu.
  6. Complete all required fields on the project request form.  Required fields are noted with a red asterisk.
    • Project Name;  Provide a unique name for the project request.
    • Project Category: Select the appropriate Project Category - defines approval workflow.
    • Problem Statement:  Provide a brief problem statement describing the specific "Problem" the project will be solving.
    • Project Description:  Provide a short description of the project.
    • Project Impact:  Describe the impact to the University if the project is not implemented.
    • Project Benefits:  Briefly describe how this project will benefit the university
    • Project Type:  Select all that apply - helps define the project scope.
    • Strategic Alignment:  Explain how the project is aligned with UCO and OIT strategies.
    • ITEC Division:  Select the applicable ITEC Division responsible for the project.
    • Affected Population:  Select the population affected by this project. Select all that apply.
    • Sponsor Name:  Search and locate the person that "owns" the project on behalf of the organization. The person that has overall responsibility for a project and can authorize work on the project to begin.
    • Acct/Dept Specify under which department in your organization this project falls
    • Current State of System or Process:  Select the state of the current system or process.
    • Describe Current State of System or Process:  Provide additional information about the selected state of the current system or process.
    • Project Scope:  A project scope statement defines the boundaries of a project, and as a minimum should include the objectives/goals of the project.
    • Out of Scope:  Provide details regarding any work that should be considered "Out of Scope". This information helps to set additional boundaries of the project work.
    • Project Deliverables:  List out the unique and verifiable products, results, services or capabilities to be produced to consider the project complete.
    • Regulatory Project:  Yes or No - Is this project required to maintain compliance with a regulation?
    • Regulatory Project Details:  Provide additional information about the regulatory requirements. If this is not a Regulatory Project, enter "None" or "N/A" in this field.
    • Priority:  Select the appropriate priority.
    • Is There an Approved Budget for the Project?  - Select "Yes". "No" or N/A  (NOTE:  If there is an implementation or recurring cost but no budget, STOP. Identify the budget details prior to completing the Project Request.
    • ORG #:  Enter the applicable ORG# for the department budget funding the project. If no cost required, enter "N/A"
    • Budget Amount:  Enter the budget $ amount that has been approved.
    • Project Budget Details:  Provide additional information on the budget for this project such as cost center detail, multiple budget allocations, etc..
    • Source of Budgeted Funds:  Select all that apply.
    • Implementation Cost:  Enter the known or estimated one time implementation cost required to deliver the project. If no implementation cost, enter "0".
    • Document the details around the one-time implementation cost for this project. If any costs are estimated costs, please note those items as "Estimated". If no implementation cost, enter "None".
    • Recurring Costs:  Enter total cost for recurring expenses that will repeat with a fixed due date the department will incur beyond implementation and indicate whether recurring costs are monthly, annual, or other.
    • Recurring Cost Details:  List relevant details related to the recurring costs for the project. Include the length of contract, frequency of recurrence, and the amount due at recurrence. If no recurring costs, enter "None".
    • Return on Investment:  Provide information about the return on the project investment such as increased revenues, lower costs, or efficiency / customer service improvements.
    • Estimated Project Duration (Days):  Estimate the number of business days the project will take to complete
    • Is There a Required Implement By Date?  Select Yes or No.
    • Desired Implementation Date:  Enter the date the project is targeted for completion. 
    • Importance of Desired Implementation Date:  Describe the effect of not completing the project by the desired implementation date. Note any project dependencies that are important to ensuring project delivery by the desired date
    • Technical Resource Roles Required:  Select all that apply
    • Other Technical Support Resource Details:  Describe other related technical support required for the project, include technical vendor details, contractor details etc.
    • Will Non-Technical / Functional Resources be Required for the Project?  Select Yes or No.
    • Non-Technical Resource Requirements:  Describe estimated non-technical resource requirements for the project.
  7. Upon completion of filling in the "required" request fields - click the blue "Save" button at the top of the form.
  8. On the next screen that appears, click the "Review and Submit" button.
  9. Add any required attachments to support the request by dragging / dropping the attachment(s) in the applicable location on the request form.
  10. Once the request is ready for approval, click the "Mark Complete and Submit" button.
  11. The request will then enter the applicable approval workflow based on the Project Category selected.
  12. Upon submission, the Project Request will be forwarded to the OIT PMO for review.  The requestor will receive email notifications as the request is processed.

Notes

Here are some additional tips for submitting a successful project request:

  • Be clear and concise in your completion of the request sections.
  • Provide a detailed justification for the project, including the benefits it will provide to the university.
  • Ensure budget information is provided if there are any applicable costs associated with the request.  
  • Requests with required cost and no budget information will be rejected to the requester until such information is provided.

 

Print Article

Attachments (0)

No attachments found.