Planning for implementation of the EchoSystem |
In this section: |
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:
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 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:
Faculty based capture components:
|
Audio/Visual 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 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:
Capture Components: See Instructional Technology above. Publishers (CMS/LMS/VLE):
iTunes U:
Programmers:
|