Expectations for GCC Technology Delivery

(Organized -- February 1, 1996)
(Prioritized -- February 15, 1996)
(Final revision -- February 20, 1996)

Presented to and Accepted by the Joint Planning, Procedures and Futures Committee

May 7, 1996

Network Expectations Update -- September 9, 1997

  1. Level of access (place and time)
    Use will expand; requires serving more students and in more ways

    1. Global access (college-wide)

        1a. Anytime the campus is open, the software is on the network
        1b. Ready at all hours of building/lab access
        1c. [Continue to be] Able to access software from multiple locations
        1d. Expanded hours of[summer] access

        2a. Basic access package for faculty/staff/students (e-mail, software, Internet, Netscape)
        2b. Interface to the library from anywhere

        3a. Student on-line records and advisement access
        3b. Communication between networks (student and faculty)

        4. Student/faculty storage from multiple locations

        5. Expanded hours of access

    2. Scheduled access and/or specialized use
      1. Area for student access to CD's
      2. Private or collaborative area for students on computers
      3. Ability to accommodate student hardware

    3. Off campus, round-the-clock
      1. Distance learning
      2. Off-campus access

  2. Planning (expansion and abandonment)

    1. Local development (district and campus opportunities and constraints)

      1. Monetary support for operations and support
      2a. Planned obsolescence
      2b. Continue to keep software on the network
      2c. Flexibility/portability with hardware

    2. Educational technology development (broad context)

      1a. Striking a balance between maintaining programs and innovating
      1b. Ahead of the pack but aware of what mainstream is doing
      2. Multimedia delivery
      3. Monetary and commitment to support for innovation
      3a. Latitude for innovation
      3b. State of art equipment

  3. Procedures

    1. Ongoing reliability of academic applications

      1. Consistent applications
      2. How to accommodate faculty customizations
      3. Student customizing

    2. Changes are planned and consensual

        Expecting that the work of others is being considered in problem solving
        [For instance, changes to software packages that others are using do not occur without consulting those others.]

    3. Maintenance

    4. Priorities

      1. Follow an established set of priorities

  4. Quality Control

    1. Analysis/Evaluation

      1. Bench marking--what are we doing well or intending to do well
      2. Good/effective communications between services and users - progress reports (GCC and District)
      3. Maximum reliability level
      4. Ready at all hours of building/lab access ?(intentional duplication)
      5. Maximum level of support

    2. Training

      1. Access to training resources (variety of training delivery)
      2. **** [Encourage] More self-reliance on the part of technology users
      3. Expectation that faculty/staff can run what they request
        (UNCLEAR INTENT:hardware? knowledgeablility? for themselves? for students?)
      4. More demanding software requires more training and knowledgeable support people

Page maintained by Karen Schwalm
URL: http://www.gc.maricopa.edu/apollo/desktop/GCC/expect.html
Last update: Tuesday November 17 1998