Selecting the Right Desktop Conferencing System for Your Campus


Published on

As increasing number of colleges and universities are considering campus-wide adoption of interactive desktop conferencing programs to enhance student learning experiences, institutions can make use of an apples-to-apples comparison of available products in consideration of the software features, license costs, and hosting options that are most suitable for the individual campus environment. In this session, three institutions with various needs and setups (e.g., institutional size, IT infrastructure, online communication needs, and hosting options) will share their experiences in the selection of campus-wide solutions and the criteria they used for the selection process.

Published in: Education, Business
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Requirements considered for PfeifferWide range of audience: UG, Grad, Adult, Collaborative programs, Faculty, Public / minimum to medium tech proficiencyCollaborative programs, multiple sites, traveling/ working adultsMainly DL faculty, Low to medium tech proficiencyWebinar/ Symposium, Special events, Chapel Browser-based solution preferred.
  • Pfeiffer RequirementsMedium to high qualityConnection with telephonyRecording / archiving with screen shareAbility to toggle between all students / select viewMobile access
  • Pfeiffer Requirements:Named user basis to cost down, bigger or unlimited attendanceHosted service – maintenance free, no HW acquisition, no staff assignment, no bandwidth provisionAdaptive bandwidth
  • Pfeiffer RequirementsLess emphasis on auto-integration with LMSSystem support by the host svc providerVendor support for ongoing training/ knowledge base
  • Elluminate – Bb –licence hikeWeb 2.0 startups and M&AOpen source TCO
  • Selecting the Right Desktop Conferencing System for Your Campus

    1. 1. Southeast Regional ConferenceWednesday, May 29, 2013Selecting the Right DesktopConferencing System for YourCampusDavid GannonAssociate Director, Academic Computing & Media ServicesBryant UniversityRob MooreInstructional DesignerUNC-Chapel Hill School of GovernmentEnoch ParkDirector of Distance LearningPfeiffer University
    2. 2. AgendaUse CasesTarget AudienceFunctionalityLicenseIntegrationLessons Learned
    3. 3.  Why are we even looking at this in the first place?Use Cases
    4. 4. Use Cases – Bryant University Academic Distance learning – Graduate School Virtual office hours Guest speakers Administrative Teleconferencing Virtual meetings Recorded informational sessions Interviews
    5. 5. Use Cases – UNC Chapel HillMain campus (Blackboard Collaborate) Campus support Web conferencing solution for students,faculty and staffSchool of Government (Adobe Connect) Using the state web conferencing contract Webinars, e-learning modules hosting forcourse content/delivery
    6. 6. Use Cases – Pfeiffer University Accommodating current (and potential) end-user requirements Claiming the selection power back tocampus Lessons learned from LMS market
    7. 7. Questions?
    8. 8.  Who are we trying to serve?Target Audience
    9. 9. Target Audience – Bryant University Graduate school All faculty/staff/students Executive Development Center (EDC)
    10. 10. Target Audience – UNC Chapel HillMain campus Undergraduate and graduate students Faculty and staffSchool of Government Course delivery: Webinars and e-learningmodules– state and local governmentofficials Client consultation: Use campus solution(currently Blackboard Collaborate)
    11. 11. Target Audience – Pfeiffer University Student population Undergraduate / Graduate / Adult / Public On-Campus / Distance Learning Level of Technology Proficiency Faculty On-Campus / Distance Learning Level of Technology Proficiency Staff / Departments Outreach / General Public
    12. 12. Questions?
    13. 13.  What are the needs for the selecting solution?Functionality
    14. 14. Functionality – Bryant University Real time audio & video streaming Recording capability Use for both academic and administrativepurposes Screen & application sharing IP & telephone access Branding Integration with current systems Mobile access
    15. 15. Functionality – UNC Chapel HillMain campus Private rooms Ability to be supported by main campus Ability to be integrated into campus LMS so thatfaculty/staff can make own roomsSchool of Government Ability to customize layout Ability to record and archive meeting recordings High quality recordings (audio/images) Interactive experience
    16. 16. Functionality – Pfeiffer University Audio Video Extensions/ Connectivity Branding and layout Screen share / Application share Mobile Access
    17. 17. Questions?
    18. 18.  How much will this cost to support and maintain?License
    19. 19. License – Bryant University How is pricing calculated? Who can use and who is counted Additional costs for on-site/hosted Storage & bandwidth limitations
    20. 20. License – UNC Chapel Hill Main campus is covering cost forBlackboard Collaborate as a campusservice School of Government has 2 named usersrooms (500/375 concurrent users) Unlimited storage space for archivedwebinars, e-learning module content
    21. 21. License – Pfeiffer University Cost calculation Campus wide/ all user / concurrent user/named user Size of attendance Hosting options On premise / Hosted Maintenance Bandwidth requirement
    22. 22. Questions?
    23. 23.  How will this work with our existing infrastructure (e.g. single-sign-on, LMS)Integration
    24. 24. Integration – Bryant University LMS (Blackboard) Email & calendaring system (Exchange) Single sign on Mobile Other applications (Office)
    25. 25. Integration – UNC Chapel HillMain campus LMS (Sakai) Super Admins have ability to create roomsSchool of Government Instructional Support are the two namedusers and manage the room and publishingof e-learning modules
    26. 26. Integration – Pfeiffer University Connection to the existing system LMS Calendar / Appointment system Support structure Training Convenience vs. Functionality
    27. 27. Questions?
    28. 28.  What are potential trouble areas or sports to consider and be aware of?Lessons Learned
    29. 29. Lessons Learned – Bryant University Institutional Strategy “Advertising” and training are vital! Compatibility with other systems No phone access HD capability Mobile solutions – for all platforms?
    30. 30. Lessons Learned – UNC Chapel HillSchool of Government Demand ≠ Usage Faculty use their conference line more thanthe virtual meeting rooms Current actual use of virtual meeting roomsdoes not warrant separate contract outside ofcampus supported solution Using the state contract improved reliability,increased capacity, and lowered costs
    31. 31. Lessons Learned – Pfeiffer University Be aware of system lock-in Stability / longevity of vendor True cost of own
    32. 32. Questions?
    33. 33. Contact InformationDavid Gannon, Bryant UniversityAssociate Director, Academic Computing & Media Servicesdgannon@bryant.edu Moore, UNC-Chapel Hill School of GovernmentInstructional Designerrobmoore@unc.edu Park, Pfeiffer UniversityDirector of Distance LearningDL@fsmail.pfeiffer.edu