Long term agenda topics

Voting results from January 21, 2016 meeting

  • Campus/Enterprise Storage Strategy (ie. Internal “cloud”, shared services, tiered services) - 13
  • Out-of-faculty/unit collaboration: how do we support the selection and use of technology when it involves multiple faculties (eg. The Games Institute) or institutions (eg. TUG libraries, UW/WLU joint programmes)? -13
  • Change Management: publicizing of change that may effect other UW constituents - 13
  • Review of Faculty strategic plans - 12
  • Software development (in progress) - 10
  • How do we learn what others do for a specific IT activity? How do we efficiently communicate what we are doing? - 10
  • Operational Level Agreements (OLAs) - 10
  • Bring Your Own Device (BYOD) - students being encouraged or required to use their personal devices in classes/teaching spaces - 9
  • Asset Management update - 9
  • Digital Signage demo/update - 8
  • Public Documentation of CTSC conclusions - 6
  • Instructional Software - 5
  • Student lab support - 2

CTSC future agenda items – voting results from meeting on April 30th

(Number beside item is total number of votes for; number in bracket is total number of votes for having the item done as an update via email).

  • Software Development – 17 (in progress)
  • How do we learn what others do for a specific IT activity? How do we efficiently communicate what we are doing – 9
  • Student Lab Support – 9
  • Campus/Enterprise Storage Strategy (ie. Internal “cloud”, shared services, tiered services) – 9 (scheduled for the Fall)
  • Asset Management Project – 8 (2 for update)
  • Internet of things – 7
  • Public Documentation of CTSC conclusions - 7
  • Instructional Software – 4
  • Open Scholar update
  • Review of Faculty strategic plans
  • Operational Level Agreements
  • Out-of-faculty/unit collaboration: how do we support the selection and use of technology when it involves multiple faculties (eg. The Games Institute) or institutions (eg. TUG libraries, UW/WLU joint programmes)?
  • Digital Signage demo/update
  • Bring Your Own Device (BYOD) - students being encouraged or required to use their personal devices in classes/teaching spaces.

Upcoming items for discussion

  • Identity and Access Management (IDAM) - Jason will present on this after the RFP closes)
  • Software Licensing (Sandra Laughlin will attend February 4th meeting).
  • Electronic Classroom Support (In progress - Trevor Bain is working on).
  • Apple management (Manfred Grisebach will attend February 4th meeting.)

Agenda topic descriptions

  1. Electronic Classroom Support.  For centrally scheduled and managed classrooms: What technologies are in them? What technologies are coming? How is software distributed? How are upgrades decided? What is the rollover plan? For Faculty or department scheduled and managed classrooms: Same questions as for central, plus, who pays for what in these rooms? For both: What challenges arise? What accessibility issues arise? How are they being dealt with (or not)? June, not before Convocation, or later
  2. Instructional Software. What software is being used for online or blended (in-class and online) centrally? What support do you provide for instructional software in your Faculty/department areas? Do you need to know more about what is supported with LEARN (added-on tools)?
  3. Student Lab Support.  What are we doing with student labs?  How software is paid for, distributed, etc.? What is the future of student labs? 
  4. Software development.  The role of IT groups in the Faculty for software development and innovation.  How is it supported?  How are decisions made on what to do? Who supports it after it’s developed?  Etc. – First meeting in June
  5. Identity and Access management – break into phased updates
  6. Overall Security Strategy update – to be done as a consensus item and sent via email
  7. Lync update – to be done via email as a consensus item

Items added as of April 19th meeting

  • How do we learn what others do for a specific IT activity? How do we efficiently communicate what we are doing? - BInce
  • Asset Management project – gap analysis; how does the product score against the campus requirements.  – DKeenan
  • Update from each IST director - BCampbell
  • Review of UCIST’s 6 month agenda. - BCampbell
  • Public documentation of CTSC conclusions (where conclusions can be technical guidelines, recommendations, best practices etc.) - BInce
  • WCMS Feature Request list (Andrew McAlorum) - BHicks
  • Takeaways from OUCC and Canheit - BHicks
  • Project updates as needed. – Bhicks
  • Video asset management – video storage and delivery, and archive (late May, early June, by or on the 11th preferred, but also any time afterward) - AChappell

Items already discussed

  • FORE issues - discussed at February 19th meeting including follow up from Bruce.
  • Admin tools & data access – discussed at February 19th meeting – more to come on this topic
  • The role of the Account Reps in the Faculties – discussed at March 5th CTSC meeting.
  • Software support. As already mentioned in meeting. Also we should also have a roadmap of what we have and a calendar of what is expiring, etc. Also – look at site licencing – discussed at March 19th meeting with Sandra Laughlin
  • Pain points – discussed at April 2nd meeting
  • Authentication Directions – Sean Mason – discussed at April 19th meeting
  • WCMS Feature Request List – 9 (already discussed)