Minutes - October 19 2007
ITAC
Meeting MinutesFriday, October 19 2007
1:30 - 3:00 pm
I. G. Greer - Room 224Persons Present
Ex Officio members: Tom Van Gilder (TSS), Jeff Williams (ITS - Chair)
Voting Members: Amy Cheney (Reich COE) James Hayes (University Advancement), Emory Maiden (Coll.of A&S), Toni Becvinovski (Registrar, Proxy for Don Rankins), Rene Salinas (Coll.of A&S), Scott Schneberger (Walker COB), James Wilkes (Coll.of A&S), Sandi Jones (HRS/Chancellor’s Office)
Visitors: Steve Breiner (LTS, Recorder), Jeff Church (LTS), Tom Culver (ITES), David Earp (ITES), David Hayler (ITES), Tom McDonnell (Hayes SOM), Tung Ong (Walker COB), Greg Simmons (LTS), Kevin Snook (TSS), John Spagnolo (Reich COE)
1) Welcome, Opening Comments
Jeff Williams welcomed the group and called the meeting to order at 1:35PM.
2) Update on the NC State Virtual Computing Lab (VCL) project
David Earp (TSS) reported on progress with the Virtual Computing Lab concept, developed at NC State for shared application license usage. VCL allows users to run software carrying an expensive license remotely, on a prescheduled basis, in effect sharing the expensive license among multiple users. The licensed software runs on a server that is “allocated” to the user by scheduling software with its output being displayed on the users computer via a Windows Terminal Services mechanism (on either Windows or McIntosh computers). The purchase of software licenses can thus be shared in order to maximize the usage of the software while reducing the number of licenses required to serve the needs of the users.
David Hayler noted that a 1000-blade server was being acquired by NC State for deployment at MCNC (Microelectronic Center of North Carolina) with the SPSS and ACR-GIS scheduled first for software deployment. Earp mentioned that various possible distribution plans were being considered for VCL, with the current, interim mechanism being resources pooled at MCNC with campuses proposing to kick in resources in exchange for VCL access. Other models being considered include campus-based deployments or multi-campus pooled deployments at MCNC or at regional campuses, with and without failover capabilities. Jeff Williams noted that the UNC system seems to view VCL as something of a “killer application” with a possibility of dramatically changing the way campuses license software, particularly the more expensive packages.
3) Update on Learning Management Systems
Steve Breiner (LTS) reported on the Fall Semester implementation of the Moodle (Modular Object-Oriented Distributed Learning Environment) learning management system (LMS) that will replace WebCT at Appalachian by the 29th of November, 2008, when the WebCT license will expire. He reported briefly on the eLearning Institute that was sponsored by Academic Affairs during spring and summer of 2007. In the eLearning Institute, some 20 faculty participated in intensive workshops, consulting sessions, and course development activities to build new (and redesign existing) courses using the new LMS.
He noted initial LTS’ expectations of 30 to 40 course sites in the new system, following its release in August. Favorable faculty impressions of the new system and word of mouth “advertising” by faculty who found the new system friendly and usable eventually pushed LTS to build an unexpected 154 “live” course sites for use during fall semester. The new system was successfully integrated with the Banner Student system so that courses specified in Banner as “Moodle Courses” are automatically built, their rolls populated, and their faculty assignments updated in “real time” as the designations are applied.
Breiner mentioned that LTS was working intensely on work flows and mechanisms to assist faculty in making the transition from WebCT to the new LMS and that he expected formal announcements of those during spring semester of 2008. Scott Schneberger (WCOB) asked whether LTS required faculty to have training in order to obtain “live” classes in the new LMS. Breiner replied that the system seemed to be sufficiently user-friendly and easy-to-use for technically savvy users to learn to use on their own, but that most faculty would likely benefit from at least a minimal formal introduction in workshops being developed and offered by LTS.
4) Discussion of a need for planned maintenance windows for IT infrastructure
Jeff Williams briefly discussed the recent unplanned service outages in email, AppalNET and Banner. He noted that, in most cases, the longest outages resulted from the need to move and/or copy data among the various systems involved. He mentioned that he had been asked by numerous users why the updates and data migrations that occurred over Fall Break had occurred at that time. He answered that because of registration requirements earlier and academic requirements during other parts of the semester, the least disruptive time in which to perform needed operations (replacement of aging servers, increases in storage space, applying patches, upgrading software) was during the fall break. ITS had considered holidays, breaks, inter-semester gaps and other times, but the variety of constituents had essentially vetoed every time except for that break during which the operations commenced - critical operations had been postponed from and earlier proposed summer timeframe. He noted that despite having issued some 17000 emails notifying users about the maintenance that would occur over the break, only 4 replies had expressed concern with the fall break operations. Williams suggested that that most of the outstanding mail issues, logging issues, and Banner self-service issues had been corrected, and that one outstanding security issue was expected to be resolved in an impending patch from Sungard Higher Education.
Acknowledging that more concerns had been expressed about the upgrade timeframe after the fact, Williams asked that the ITAC membership help develop regular, prescheduled maintenance windows during which maintenance and repair operations could be scheduled. Such windows would be advertised well in advance and published in the normal academic and institutional calendars, so that users would be aware of the times and dates during which systems might be taken offline for necessary maintenance. Williams proposed to develop and distribute a tentative maintenance schedule for consideration by ITAC and for public comment.
Scott Schneberger expressed some concern that the information regarding system downtime was, with the latest outages, not released sufficiently early for users to avoid impacting prescheduled assignment deadlines, test dates, and other time-sensitive activities. Tom Van Gilder (TSS) reported that the “Friday Technical Group” had been having extensive discussions about how to improve communications between ITS and the campus. Schneberger then emphasized that many faculty schedule activities based on tight semester schedules and that planned (non-emergency) service windows must be announced early enough to allow their accommodation without severe disruptions to class schedules. Amy Cheney then mentioned that the College of Education had many courses where 24×7 access to eLearning activities was required. Hayler responded that 100% uptime is the ideal for IT services, but users need to realize that the complexity and interconnectedness of the services we provide absolutely require occasional maintenance, and the downtime that sometimes requires. Williams said he would distribute to the group a proposed schedule of maintenance windows for further consideration.
5) Overview of campus technical support (including asutech, Friday Morning Group, etc.)
Tom Van Gilder reported on the campus efforts toward improving communications and technical support. He asked for suggestions from the group about mechanisms they might propose that would increase awareness of various technical information. He suggested, and was encouraged by several members, to add the ITAC membership to the ASUTech listserv that is used by campus IT consultants for rapid communications. Schneberger suggested a general principle for IT communications — “push problems and pull solutions,” i.e., when there is a problem, actively communicate it (”push”) to the campus, then provide resources that users can seek (”pull”) when they are trying to solve a particular problem.
Van Gilder also noted that TSS was being charged by the Provost’s office with implementing a campus-wide classroom technology development and support structure. There will be a structure and positions created to support a large-scale modernization and maintenance of classroom technologies throughout campus.
6) Update on Banner deployment
Toni Becvinovski (Registrar’s Office) reported that the campus was now fully engaged with Banner and that all of its modules.are now in full production. He stated that everyone involved in the Banner implementation was now feverishly engaged in identifying and developing all of the functionality, tools, and work flows that the campus had come to expect from the aging and highly customized SIS-Plus system. He surmised that as we become familiar with Banner, the fine-grained access controls in the new system would offer self-service capabilities and functionality that would never have been possible with SIS-Plus. With the new system, the “Dashboard” reporting tools will eventually replace most paper-based reports with searchable and sharable electronic reports. He mentioned that Dave Haney (Academic Affairs) was working closely with the registrar’s office to implement degree-audit capabilities and catalog maintenance tools. He noted that, in the registrar’s office, Spring term courses were being built, 500 new students were matriculating to Appalachian, and deployment of a new sports ticketing system was in progress.
Williams noted that the deployment of Banner had been a 5-year, complicated process, with hundreds of people involved. He mentioned that, from a technical standpoint, drop/add had gone reasonably well for a first run, but that some deans had not been as complimentary of the process… they, and any others, are being encouraged to bring those concerns to the registrar and to ITS for discussion and eventual resolution.
7) Other business
Rene Salinas (Arts & Sciences) asked about the status of wireless networking on campus. Tom Culver mentioned that Appalachian was undergoing a significant expansion in wireless access, funded largely from Education and Technology (E&T) fees and that the expansion would continue for the foreseeable future.
Adjournment
Williams adjourned the meeting at around 3:00 PM.
Permalink Comments off
