UA Software Request Process

 
Purchasing Software Overview
The Software Request Process
Frequently Asked Questions
Give Feedback
Helpful Resources
Software Procurement Change Log

 

Purchasing Software: Overview

 
UA has implemented a system-wide software review process in response to increased regulatory obligations relating to software and third party vendor risk management.  
 
To see an overview of the full process, please read the Step-By Step Guide (Document). To access this, you need to be logged into your UA google account.

 

Do you have questions about this process? Please visit our FAQ or contact us at ua-oit-risk@alaska.edu
 

 


The Process For Requesting Software

  Submit A Request
Submit your request through the Software Request Form. Make sure your request is as thorough and detailed as possible. Once the request is submitted, it will be reviewed by the applicable review groups.

  Wait & Watch TDX
Once your request is submitted, wait for it to be reviewed by the appropriate groups. Keep an eye on your ticket - if review groups need more information, the requestor will be reached out to.

  Use Your Software
Once your software request is reviewed, if it is approved, you can go on to procure and use your new software for the intended use case. It should only be used for the approved use case and nothing else. 

 

Frequently Asked Questions

The university is obligated to review software to ensure its quality, security, and effectiveness in meeting the educational needs of students, staff,  and faculty. This review process is crucial to protect the integrity of academic work, safeguard personal and institutional data, and promote an efficient and productive learning environment. Furthermore, it ensures that the software aligns with the university’s mission and values, complies with legal and ethical standards, and provides equitable access and usability for all users. 

At this time we are not evaluating device drivers or device firmware.   

 

Currently all software requests must be reviewed. However, we are working to eliminate this requirement in an upcoming version. 

 

No, only those individuals named in the request will have access.

 

We are not currently monitoring the version of the software. Automatic updates are preferred because this is how the software developer improves their product and it's security. However, if you are aware of significant changes to its terms and conditions or its privacy policy, please notify your help desk.

 

Once your request is approved, you will purchase the approved software. Then, you will need to contact the helpdesk to get your software installed. When you contact the helpdesk, please have your ticket number from the software request ready.


For the purposes of this review process, we are concerned with the following types of software:

 

Application Software:  Application software is typically installed on your device. Examples of application software could be products such as AutoCAD, and Adobe Photoshop.


Software as a Service (SaaS):  Software as a service (SaaS) allows users to connect to and use cloud-based apps over the Internet, typically in a “pay as you go” model. Examples include Asana, Slack, and Salesforce.

 

In general, anything that is on the restricted purchase list in the ProCard Manual does need to be reviewed. Some exceptions have other Procurement Waiver requirements that are not addressed through this process such as copyright evaluations. Please contact Procurement if you need assistance. 

However, these Defined Exclusions exist:

  • Stock photo services

  • Web hosting and design services (requires separate review​)
    • UAA has specific guidelines for web pages; please visit their site for more information

  • Subscriptions to newspapers, journals, and streaming services

  • Memberships in professional organizations

  • Network Hardware (Starlink, communication equipment, cellular services)

  • Online training (to receive instruction/training, products where no data other than a login is provided to the vendor)

  • Computing hardware (and the installed OS, firmware, drivers, etc)

  • Data files, records, or database access

 

Current review groups that review every product:

  •  Accessibility Review
  • Contract/EULA/T&C Review 
  • IT Risk & Compliance Review

Current review groups that review only those products identified as containing sensitive data: 

  • Data Export Control Review
  • Intellectual Property Review 
  • IRB/Human Subject Review
  • Foreign Company/Tax
  • PCI-DSS Point of Sale Review

Follow the steps outlined in this KB Article.

If you're adding licenses to the same request, or 'true-upping' a product then an additional review is not necessary. The key to this is ensuring that the business use case, the department, or the contract language for the software has not changed from the original request. If it has changed significantly, a new request form will need to be submitted.

Yes, freeware and open source software need to be reviewed just the same as purchased software.

 


We Want To Hear From You!

 

Have you used the new software procurement process? Please fill out our feedback form!

 

If you still have questions, please email us at ua-oit-risk@alaska.edu 

 


 

 

Helpful Resources for Software Procurement                                                

 
Software procurement is regulated by both OIT ISA and UA Procurement.

Procurement resources that impact software procurement:

Procurement Website
ProCard Program

Regulatory resources and policies that impact software procurement are:
Board of Regents Chapter VI - Procurement and Supply Management
UA Accounting and Administrative Manual Section 400: Information Technology

Useful KB Articles for software procurement:
View your Tickets in the Service Portal
Software Request

Best Practices related to software procurement are as follows:
    • Clearly describe the business use case. Why are you needing THIS particular software vs any other?
    • Clearly describe the type of information you'll be giving the software such as names, birthdays, grades, research data etc.
    • Ensure the contract administrator understands the role they're accepting. 

Change Log

 

Since its inception in December 2022, this process has gone through several revisions based on your feedback. 
 
Version 3 of the UA Software Request Process was released on July 22, 2024, and is the current version.
 

 

Version 3 Changes: 

 

  • A new notification has been sent to everyone in the ticket letting them know that the review has moved from the department review stage to the formal Risk & Compliance review.
  • The export control form has been replaced by a series of questions. This removes the need for a separate form.
  • PCI Compliance reviews have been streamlined.
  • An exception list has been created and can be found in the FAQ's.
  • Ticket Creator will get push notifications now.
  • Dept approver is OPTIONAL but if you put a person in there -then the field becomes REQUIRED - repercussions are if they don't answer or deny its a automatic ticket cancellation - the approver gets 3 total notifications before the ticket is automatically cancelled.
  • Reminder notifications added
  • Reviewer groups will be reminded daily to fulfill their duties
  • Requestor will be reminded every 2 days for 2 days so 3 notifications total
  • CA gets a separate notification with a pdf of their signed CA acknowledgement
  • Notification step included between dept approver and before the SLA application - notifying them that it's progressed to the Service Desk review.
  • SLA Clarification - 10 business days for all reviews- recognizes UA holidays and weekends, SLA starts AFTER the dept has responded. Depts have 5 days to respond. 
  • Reviewers are notified every 2 days for unreviewed software
  • Dept approver, creator, requestor and contacts are notified the software is denied.

 

See previous version Change Logs here:
  • Improve responsiveness of "Department Review" stage
  • Update Software Exception Choice Notification
  • Improve logic for copying "Comments" and translating HTML <br> tags to paragraphs.
  • procard field changes
  • Increase visibility of approval comments
  • Fix bug when canceling tickets due to no response from department
  • SLA Applied to Ticket
  • Software Renewal Terms
  • MAU Service Desktop Routing
  • changed auto cancellation times
  • changed workflow timing
  • Form issued ro procurement
  • Message for out of office set
  • User Survey attached to ticket
  • added notification to IT service desk to validate the dept instead of cancelling the ticket