How to Answer Questions Asked in the Tech Adoption Ticket

The Tech Adoption (TA) process reviews all requests in terms of how a new or changed application will fit into the college’s current technology landscape and ensure the technology’s security practices meet the college’s criteria.

When submitting a TA ticket, you’ll be asked several questions to help us process your request. All questions must be answered completely or your request could be delayed (in some cases, the delay may be significant). These questions, along with more details about the specific data we are looking for, are listed below.

  1. Who is your request for?
    Will the request you are making impact only you, a professor and a few students in a class, an entire department (for example, the Finance Office, Math Department, etc.), or everyone at the college (for example, something like Banner, Office365, etc.)?

  2. Who is the contact person for the request?
    List the person responsible for the item being requested. Things to consider: who will make sure software or hardware stays up to date, who should IT or others across campus contact should they have questions about the requested item, etc.

  3. Name/type of technology?
    What is the specific name of the technology and the name of the company that owns the technology? Often, companies own more than one specific product, so we’ll need to know the specific one you’re looking at. Are you considering replacing an existing piece of technology with this new one? What technology would be replaced?

  4. How will this technology be used?
    What does the technology do? How will it help the individual(s), department, or campus with its work?

  5. What is the ballpark cost and who will pay for it?
    It will be important for you to consider funding options for your request if it will not be part of your departmental budget. Currently, IT does not pay for individual(s)- or department-specific technology.

  6. What other college-owned technology have you looked at to fit the need?
    The college has many different types of technology serving many different needs across campus, and often the use of those technologies can be expanded to other people or departments. Please contact the Solutions Center at its@coloradocollege.edu or (719) 389-6449 to explore other options prior to submitting your request.

  7. Attachments
    Contracts, websites, correspondence with the vendor, etc., can and should be included here. Inclusion of this information up front can help move the TA request process faster.

  8. Vendor contact information so we can reach out (name, title, email address, phone number)
    The TA group will contact the vendor to ask a list of IT questions we need to have answered in order to complete the review.

  9. Have you obtained leadership approval? If so, from whom?
    It is important that leadership be made aware of your request and have approved it in advance so they can make funding and other decisions as needed prior to your request. This is especially true for departmental or campus-wide applications.

  10. Who has reviewed and approved the contract (if a contract has been received)?
    Please follow the college’s Procurement and Purchasing Policy when reviewing and approving contracts.

  11. What campus data does this application need? (Will it need to integrate with Banner, Slate, etc.)
    Please be specific about what data needs to come from other sources like Banner to use the application. If you’re not sure which existing source your new application will use, list out the information that the application needs (names, addresses, etc.).

  12. What is your ideal timeline for implementation, if approved? When do you hope this new application can be up and running?
    If an application needs ITS’s assistance to be fully implemented/integrated, the IT governance process will need to determine its priority within the existing projects. The IT governance group is made up of senior leadership members from across campus, so all projects can be viewed appropriately.
Report an issue - Last updated: 04/22/2024