Deployment Guide

Owned by Hannah Petty
Last updated: Dec 01, 2015Version comment
3 min read

In this section:

Overview

This document provides guidance to those preparing for an EchoSystem deployment within an institution. It discusses core system requirements and functionality, server configuration, classroom and faculty-based capture options, and other deployment considerations. It is designed as a high-level overview for institutions planning an initial deployment of the EchoSystem platform.

There are several major aspects to consider when planning an EchoSystem deployment, including:

  • Personnel to manage EchoSystem
  • Project management
  • System design and sizing requirements
  • Server infrastructure
  • Classroom equipment, audiovisual setup and classroom wiring
  • Software installation on classroom and faculty computers
  • Integration with existing systems and infrastructure
  • Planning for growth

Who Should Read This Guide?

EchoSystem is a network-dependent application with multiple components that run across a number of different computers and devices within an institution. Integrating EchoSystem into a new or existing infrastructure requires the participation and cooperation of several personnel sets within the institution. If you are responsible for installing and/or maintaining classroom technologies, managing server infrastructure or client services, or administering course management system(s), you should read this document to learn what an EchoSystem deployment requires within your institution. The list below provides some common personnel sets and related EchoSystem components. Responsibility for some components may be shared among the groups listed or perhaps other groups as well.

Instructional Technology
Personnel responsible for the instructional environment within the classroom.

Needs to consider

The EchoSystem features two classroom-capture component types. Each of these components requires network connectivity to communicate with the EchoSystem Server, receive schedules and transfer raw files for publication. The software-based option may also require operating system configuration:

  • EchoSystem capture appliances (EchoSystem Capture Appliance, EchoSystem SafeCapture HD, Echo360 PRO) - Dedicated all-in-one capture devices for audio, video, and external VGA capture. Provides schedule-based or faculty-driven capture, and is typically installed in an AV rack or podium.
  • Classroom Capture - Windows application for audio and local screen capture. Provides schedule-based or faculty-driven capture, and is typically installed on a podium or lectern PC.

Faculty based capture components:

  • Personal Capture - Windows or Mac application for audio, screen, and webcam video capture. Provides faculty-driven capture, and is typically installed on laptop or tablet computers.

Audio/Visual
Personnel responsible for the installation and maintenance of audiovisual equipment within the classroom.

Needs to consider

EchoSystem capture appliance deployment in the classroom requires that the appropriate audio, video, and VGA sources be properly routed and connected to the device inputs. External amplification may also be required to achieve the necessary audio levels for a successful capture.

Programmers may also use the Capture Appliance API to integrate capture appliance operation into the room control system (e.g., AMX or Crestron). For details see API Documentation.

Information Technology
The group that is responsible for managing and maintaining the server infrastructure and/or client services across an institution. This group might include systems administrators forweb, network, and streaming infrastructure, the help desk or support staff, CMS administrators, or iTunes U administrators.

Needs to consider

There are various networking, bandwidth, storage, and firewall considerations for EchoSystem Server and supporting servers, classroom or faculty-based capture components, and publishers (or CMS/LMS/VLE integrations).

Servers:

  1. EchoSystem Server (ESS) - Central web-based management component running on the Window or Linux operating systems.
  2. EchoSystem Media Processor(s) - Media processing components running on Windows or Linux.
  3. Web and Streaming Server(s) - Bundled as part of the ESS, but may be separated to accommodate system scale or pre-existing infrastructure.
  4. File Transfer Server - Bundled as part of the ESS, but may be separated to accommodate system scale or pre-existing infrastructure.
  5. Database Server - Bundled as part of the ESS, but recommended to be separated onto pre-existing infrastructure and/or to accommodate system scale.

Capture Components:

See Instructional Technology above.

Publishers (CMS/LMS/VLE):

  • LTI-Based Publishing for Blackboard, Canvas, Desire3Learn, Moodle, and Sakai Learning Management Systems.
  • Includes Blackboard Learning System Enterprise, Blackboard Learning System CE/Vista, Moodle, and Angel Learning Management Suite.
  • May also include custom integrations
  • The individuals or group responsible for these systems will need to assist with integration between the ESS and the CMS/LMS/VLE.
  • The ESS communicates with the CMS/LMS/VLE used by the student to view course materials.

iTunes U:

  • The ESS provides integration with iTunes U by automatically uploading content to the iTunes U repository or serving RSS feeds to iTunes U. The personnel responsible for maintenance of this system will need to assist with the integration of the ESS and iTunes U, primarily by providing authentication token(s).

Programmers:

  • EchoSystem includes APIs for integration with existing technologies such as scheduling systems, room control systems (e.g., AMX or Crestron), and publishers (see above). See API Documentation.