The TTIG is the official source for reporting on teaching technology integrations with UB Learns. The TTIG is managed and maintained by the UB Office of Curriculum, Assessment, and Teaching Transformation's (CATT) Learning Environments and Teaching Technologies team.
>> TTIG URL:  https://www.buffalo.edu/catt/support/technology.html

Teaching technology requests initiate a software review, prior to integration with UB Learns, which includes a: CATT consultation; faculty new technology request, vendor registration, UB IT VAR; and Procurement review. Teaching technologies integrated with UB Learns will be regularly monitored for significant change and compliance with UB software review and procurement policies, and may be restricted or removed from UB Learns while a risk assessment or additional review is completed.

CATT maintains a document archive for all teaching technologies that have been integrated with UB Learns or gone through a review. The archive is managed on UBbox and the TTIG strategic partners have shared access to the archive. 

The preferred integration level is service-wide access. If an integration needs to be given limited access, the limitation should be based on an operational condition such as digital accessibility, information security, or procurement.

Integrations that require an access limitation should follow this schedule:

5.1) Service Impact: Any integration limitation is proceeded by a scope of the UB Learns service to confirm no course site is currently using the integration or that setting the limitation would produce a negative impact on course sites.  Setting a limitation when a course site has provisioned an integrated tool could interrupt access to the course site’s tool use, data, or interactions. In the case of a provisioning conflict or negative impact, the next highest limitation will be implemented and may include departments or units outside the scope of the limitation requested. 

5.2) Unit Level:  This level is the preferred level of integration limitation. This level is typical when multiple departments in a unit are identified as part of a limitation.

5.3) Department Level:  This level of limitation is appropriate when more restrictive limitations are warranted.  This level is typical when a single department or multiple departments across multiple units are identified as part of a limitation

5.4) Course-Level:  This level of limitation is not recommended. The preference for course-level limitation is to recommend a Pilot Integration (item 7) or to not integrate the technology and instead recommend an alternative technology.

6.1) Any limitation put in place for digital accessibility or information security will stay in place until the conditional issue is resolved. Once resolved, access will be reset to service-wide access.

6.2) Any limitation put in place for procurement will be based on the purchase contract/agreement and stay in force for the length of the contract/agreement. If a contract is not renewed, the teaching technology will be restricted or removed from UB Learns.

CATT may offer pilots of teaching technologies under the following guidelines:

7.1) Pilots are intended to allow faculty with specific needs to test-run a teaching technology in their course.

7.2) Pilots are limited to a set of faculty or courses, preferably a single faculty and course. Some pilots may be open to larger audiences if program or application review needs are justified.

7.3) Pilots will have a duration of one semester.

7.4) During the pilot, the faculty must agree to provide alternative access to content and instructional experiences for students and to work with University Accessibility Resources when appropriate. 

7.5) The faculty and vendor must work with CATT to request a new teaching technology, expand the use of an existing integration, complete vendor registration, and complete a software review.

7.6) Pilots will not be allowed for LTI that require the faculty or student to enter into a contract or use-level-agreement.

7.7) Pilot timing is contingent on available staff resources, the requirements of the pilot request, and the current scope of pilots in production.