Desktop Implementation Plan

Glendale Community College

URL: http://www.gc.maricopa.edu/apollo/desktop/GCC/index.html
Last update: Wednesday March 26 2003

Desktop Project Update -- August 19, 1997


[ Context ] [ Inventory ] [ Campus Planning ]
[ Timeline ] [ Goals ] [ Training and Support ] [ Reporting ]
[ Early Bird Special Workbook ] [ Early Bird Special Discussion ]

Context

Glendale Community College, even more than some of our other sister colleges, is facing many changes. In January, we welcomed our first new campus president in over 25 years; in April, we became an initial implementation site for the Learner-Centered System as well as one of two district test sites for Help Desk software. The campus is currently a roll-out site for the Tutor Management System and is presently engaged in a complete rewiring of both High Tech Centers to accommodate enhanced learning activities for students. Over the next six years, many other significant changes will occur that will have massive impact on the instructional program in particular and on all college processes in general (not just at GCC but elsewhere as well). Anticipation of all these activities, including the Desktop Project, have spurred college-wide strategic planning initiatives. But Glendale also has a clear technology vision and a strong history of meeting technology challenges.

Over the past several years, the Capital Request Committee, a sub-committee of the Campus Technology Committee, has constructed a dominoing and purchase plan to move the campus towards a measured funding program (as others have recommended) that provides generally for replacement of all campus lab machines over a five-year period. It is our intent to construct a parallel plan for employee machines, so that after the Desktop Project has been completed and the bond funds have been depleted, the college will have a schedule and budget for desktop replacements. Thus the overall goal of this plan is to negotiate between two conflicting goals: a massive infusion of desktop hardware over a short period of time in preparation for the introduction of many new systems and the development of a planned and budgeted five-year desktop hardware replacement cycle.

Inventory

Many of the planning decisions the college faces will be easier to make if we establish and maintain an accurate inventory of hardware.

a. Many of GCC's technical staff have been maintaining an inventory of the equipment in the offices they support, but until now, while those records are 95% accurate, they have been uncoordinated and idiosyncratic. In anticipation of the Desktop Project, we have identified a format and a series of fields for an initial coordinated inventory; we have also gathered some tools and written some instructions for DOS and for for Mac users that anyone can use to determine what kind of hardware is on his or her desktop (also useful for finding information about a personal machine.) After OGF processes become clear, we intend to transfer this data into a hardware database that intersects with the Fixed Assets portion of OGF, with Dial, and with other college records. Of primary importance is that the database be easy to maintain by multiple people and that it produce useful reports in a timely fashion.

A coordinator of the Desktop Project has been identified, and she has begun to collect and organize the inventory data. In addition, she is gathering a list of SIS users who will have immediate need for access to LCS when it becomes operational at GCC in April, 1997. We have recently added information to the inventory that identifies those individuals who have been waiting for as much as 18 months for hardware upgrades, and buildings that have inadequate networking. As we uncover other information needs, we will be able to add fields for them in the current spreadsheet; when college processes with respect to OGF, receiving, and installation become more stable, we will be better able to construct a useful and maintainable database that will help us make important decisions related to hardware purchases and installation. We believe these decisions should be grounded in good data, carefully considered by groups of people, and that the criteria should be public and open to question. Ultimately, our goal is a process for measured hardware replacement upon which people can rely for their personal growth, instructional development, and budget planning.

b. Currently, the network is functional in 80% of our campus buildings. Additional ethernet ports for new machines will be added to the current network as needed. Work continues on the Saratoga I portion of the Infrastructure Project.

c. Glendale does not intend to request any money for buy-back of current machines. Instead, we are proposing to extend the purchase of new machines over a three-year period, easing the college into a rational technology budgeting cycle. To this end, we have identified a category of "near-Apollo" desktop machines that we believe, with the addition of memory and storage, can provided specified users with the necessary functionality to accomplish the new tasks associated with their jobs for at least two years. GCC intends to defray replacement of these machines until they no longer serve their users.

Integration with other campus planning

A faculty committee spent much of Spring, 1996 outlining their expectations for technology at GCC. Spurred by that document and by new hiring in three of the four Information Services leadership positions, we have created a Staffing Plan to Support Emerging Initiatives. The plan has four main goals: to handle the projected changes while maintaining or exceeding current levels of service and reliability for instruction; to anticipate the new levels of support required by faculty and staff over the next few years and to devise creative means of providing it; to invest in our current staff by encouraging cross-training and continuous learning, rather than hiring new employees at high levels; and to work together to achieve these goals.

  1. GCC currently has a backlog of more than 200 requests for desktop computer upgrades or new purchases. In addition, no capital requests from offices for 1996-97 were filled, and some requests from 1995-96 are outstanding. Of course, the technology horizon has changed since many of these requests were made, and many new college programs have been developed or proposed, so it may be to these units' advantage that their requests have not yet been filled. However, there is a cost associated with having people spend time thinking about their needs and then not meeting their hardware requests. Because we have had a request process unsupported by adequate funding, many employees view technology requests as an exercise in futility. Moving to a measured replacement plan that people can count on should do much to restore faith in the request process.

    One of the first issues to be addressed by the GCC LCS Implementation Team will be establishing the order of Desktop Project computer installations, taking into account the following:

    1. the age and functionality of the current desktop hardware;
    2. the state of networking connections to the building (or unit) in which the machine is housed;
    3. the person (or unit's) role in other critical systems roll out (LCS, OGF, TMS);
    4. the person (or unit's) responsibility for supporting other users on campus;
    5. the person (or unit's) ability and willingness to install and support their own desktop machines (including the ability to transfer legacy data and reinstall non-standard applications);
    6. the person (or unit's) willingness to use standard software and to pilot application, file and print services.

  2. GCC has migrated to server-based printing over the past three years; all networked machines have access to network based print services, and work continues to make it more reliable for the users, although printing problems account for the most frequent calls to the Help Desk. Most users do not understand how their printing works, and they cannot perform simple troubleshooting procedures, even though instructions are available on-line.

    Some departments and units have experimented with applications and file serving on a limited basis, but many users do not know how to make effective use of these capabilities. One goal of the desktop project implementation plan is to move units toward standardizing on file and print services, including backups and user support, so as to minimize the need for continuing technical intervention. Obviously this will depend on the installation of a powerful enough network so that user productivity is not impacted. The goal is to have no more than 100 machines on a single server.

    As part of the current HTC rewiring project, GCC is installing four new servers to support HT 1 and 2 classrooms and pits. While these affect the instructional program, they will allow us an opportunity to test leveraging ethernet switching technology for students with an eye to doing the same for faculty and staff members elsewhere on campus. In addition, the main administrative server (Peabody) will be upgraded to Novell 4.1 in early fall. All of these efforts are directed towards increasing the reliability, efficiency and consistency of Glendale's network.

  3. GCC's Campus Technology Committee is the primary connection between the four Information Services units and the rest of the college. Anyone can attend its monthly meetings and participate in its subcommittees. This year, the committee will devote most of its time and energy to keeping the college informed about the new systems being developed and installed, and to make sure that the needs of the instructional program are being met.

Purchase and Installation Timeline