Skip to main content

This is only a guide to assist with filling it out and may still be confusing about what to choose after reading. If you have questions about any of these fields after reviewing this, email us at AT@unt.edu with your questions.

Click here to go back to the Software Acquisition checklist.

  • Name of Department IT Manager

    • For all of AT-supported units it is "Academic Technologies"

  • Campus

    • For all of AT-supported units it is 'UNT'

  • Department

    • List of all departmental units. Select the one appropriate.

  • Type of Purchase

    • If a new acquisition (even if it's free), choose this.

    • Any renewals need a TAQ.

  • Name of the System, Application, and/or Service

    • Be as specific as possible. For example, "adobe" is not specific enough when referring to Adobe DC, put "Adobe Document Cloud".

  • Vendor(s) name(s)

    • Full names of company that is selling the software.

    • If another company is 'managing' the software in any way (online, licensing) they need to include them also.

  • System, Application, and/or Service Website URL

  • Cost of System, Application, and/or Service

    • If the software is part of a larger acquisition, but is required for that to work, list the total cost.

  • Will this System, Application, and/or Service integrate with existing software/systems?

    • If they want this in Canvas, in software center, used to work a piece of equipment, etc.

  • Is this resource student-facing?

    • Do students use this as part of being a student, not as part of their job if they also happen to be a student.

  • Describe the System, Application, and/or Service and the department's intended use of this System, Application, and/or Service

    • They should be as in-depth as possible with what they want to do with this software/service.

  • Select the Service Delivery of the System, Application, and/or Service?

    • Software-as-a-Service: This is where the software is licensed and hosted. Think Dropbox or similar.

    • Infrastructure-as-a-Service: Generally this is server hosting.

    • Platform-as-a-Service: Used to make new apps or develop things. Rollbase, Longjump, etc.

    • Hybrid: If it's multiples.

    • On Premises: software installed on a local machine, may be licensed via a license server on campus or on install of software with license key.

  • Is this System, Application, and/or Service a web or mobile application?

    • Yes if it is fully online or a mobile app. If the software interfaces with a server or can push information to the web, it is not a web application.

  • Will the system, application, and/or service store and/or process institutional information? (Any information created, collected, and/or maintained by the institution for the purpose of conducting business).

    • Research data generated, grades, class syllabi. If it's for UNT work, it's UNT's institutional info. If the software doesn't do anything, perhaps it hosts webcams, but doesn't store the video and has no credentials, then it would be a no.

  • Would the loss of this system, application, and/or service cause a severe or adverse effect on the institution's operations, assets, and/or individuals?

    • This is in relation to the University as a whole. For example, Canvas going down would be a yes. If a software used by a single class, a single researcher, or even a department fails but would not stop them from other work would not be causing a severe or adverse effect.

  • Please rate how loss of this system, application, and/or service would cause a severe or adverse effect on the institution's operations, assets, and or individuals.

  • This is based on how it affects the University as a whole, it is not how it would affect you or your group. For example, if the software/service being out of action would prevent you from doing work, that is a low-impact resource. If it would affect an entire department, college, or UNT as a whole, that would be Moderate or High.

    • Low Impact Information Resource. In accordance with 1 TAC 202.1, an Information resource whose loss of confidentiality, integrity, or availability could be expected to have a limited adverse effect on organizational operations, organizational assets, or individuals. Such an event could:

      • cause a degradation in mission capability to an extent and duration that the organization continues to perform its primary functions, but functions at noticeably reduced effectiveness.

      • result in minor damage to organizational assets.

      • result in minor financial loss, or

      • result in minor harm to individuals.

    • Moderate Impact Information Resource. . In accordance with 1 TAC 202.1, an Information Resource whose loss of confidentiality, integrity, or availability could be expected to have a serious adverse effect on organizational operations, organizational assets, or individuals. Such an event could:

      • cause a significant degradation in mission capability to an extent and duration that the organization can perform its primary functions, but the effectiveness of the functions is significantly reduced.

      • result in significant damage to organizational assets.

      • result in significant financial loss, or

      • result in significant harm to individuals that does not involve loss of life or serious life-threatening injuries.

    • High Impact Information Resource. In accordance with 1 TAC 202.1, an Information Resource whose loss of confidentiality, integrity, or availability could be expected to have a severe or catastrophic adverse effect on organizational operations, organizational assets, or individuals. Such an event could:

      • cause a severe degradation in or loss of mission capability to an extent and duration that the organization is not able to perform one or more of its primary functions.

      • result in major damage to organizational assets.

      • result in major financial loss, or

      • result in severe or catastrophic harm to individuals involving loss of life or serious life-threatening injuries.

  • Have you received and reviewed an Accessibility Conformance Report for the system, application, or service (VPAT® or equivalent report)?