10/14/99

version 1.1

It is important as a technology committee that: (a) we make the best use of your time and energy, and (b) have an outcome this year which includes reasoned recommendations. Therefore, after consulting with several committee members, I have decided that rather than establish several subcommittees and provide each with a general charge, that we will be much more effective if we directly address a selected list of specific policy issues.

The policy questions given below have been chosen because they are concerned with campus-wide issues that we must visit if we are to have a "strategic" technology plan for the college. When we meet next week I will ask the committee for a list of other issues that we should consider.

We will build small working groups that will examine these issues. For each of the policy questions: it is expected that the subcommittee will:

1. Pick a chairperson and a recorder.
2. Examine the background issues, providing documentation and where appropriate find case studies.
3. Establish mechanisms that will help focus/solicit campus discussion on the issue
4. Examine practices at comparable institutions
5. Report back periodically to the whole Technology committee.
6. Develop specific recommendations back that includes action for this year, and for following year.

I will ask everyone to serve on one committee. However to assemble the committees, I would ask that each of you please pick two committees that you have interest in. I will initiate the first meeting of each subcommittee. From that time on, each subcommittee will have a life of its own.

I will also institute a policy that has worked very well in the Biology Department, which is about the same size as this committee. Subcommittee meeting times will be posted to our internal Listserver, and any member of the larger technology committee may attend any meeting they wish. (In Biology, by the way, visitors also have a vote on proposals).

I. Issues Relating to the Commonality and Guaranteed Availability of Software that is Used on Campus. The committee will be concerned with developing a proposal that considers what common software should be purchased/leased(?) for all students, faculty, administrators and personnel on campus. There are a variety of models for providing software from having individual copies of software packages to establishing an application software server for a variety of programs. Also changes in the Internet will certainly effect the way software is delivered and maintained. The committee needs to address financial issues, upgrade policies as well as training.

II. Formulation of Procedures for Computer Replacement/Purchase on Campus. The committee will be concerned with planning for campus-wide routine replacement of technology-related equipment. Replacement schemes should be formulated for individuals, facilities, as well as public labs. The plan that is developed will need to balance needs with the potential available funding. The committee may suggest ways to consolidate (pool) purchases from all subdivisions of the campus for best price, but not at the expense of delay.

III. Examine Network Structure and Establish a Plan to Develop our Basic Communications Infrastructure. The committee needs to determine how to make the basic campus network infrastructure ready for the next 2-3 years. This will require determining the common needs, examining currently available technology, and making educated guesses at the near-distant future. It will require meeting together with the relevant individuals from on and off campus. It should consider all communications issues, including those currently covered by the campus telecommunications system. This will be a strategic look, and will result in a rolling technology plan.

IV. Develop Standards that Define the Colleges’ External Web Presence/Intranet. Our "Web presence" has both internal (Intranet) and external components. Some portion is marketing to prospective students, other parts support the academic program at the college while others deal with extracurricular activities. The committee needs to determine what should be on the Geneseo Web site/Intranet, and by whom and how the site will be maintained. Our web presence varies quite a bit in quantity and quality by department, and currently if a department has not taken an active interest in this there may not be a site at all. Do we need to have some policy around what departments/college units need to have at a minimum?

Develop Recommendations about the Campus Role of Asynchronous Distance Learning (DL). There was at one time a protracted debate and the establishment of policies regarding synchronous distance learning on the Geneseo campus. In great part, technology passed this issue by as most of the DL currently taking place is in an asynchronous manner over the Internet. SUNY has a well established mechanism in place (SUNY Learning Network) for teaching courses DL courses and over 30 campus provide such offerings. We need to examine whether there is a role for such learning in regular academic-year classes and in the Summer/Intercession course that are taught by Geneseo faculty.

Determine Whether the College Should have a Program that Requires Students to have Laptop Computers. Which students? How will such a requirement be related to the academic program. How would it be paid for? How would it be phased into the college?

10/12/99

version 1.1

When I look at the list of issues that concern many of the members of our committee, I find some to be to require a fair amount of work, as in the general policy issues described above. On the other hand, some of the needs are obvious and could be accomplished in relatively short order either because individuals on our committee have the ability to carry out things or we could bring individual to meet with the committee that can lead to change.

As a campus we have made remarkable progress — without any strategic committee such as ours. In part this is because there are good people who have funds or can argue for funds to make things happen. In part, I have been concerned that we do nothing to undermine the advances we have already made. At the same time, there are times we can just move ahead because we have the desire and will to do so. The Nike motto — "Just Do It" can be applied to many of the needs we have. Therefore it would be useful if there were some way to move small items — without looking to a long term study. I call these a Small_Solutions.

Example Small_Solution: There is a desire to find a way to provide Secretarial staff with technology training. We have a set of on-line tutorials (CBT) that address cover many of the programs and concepts needed by such staff. Is there a way to encourage the use of this training? One startup session, the availability of Help Desk, establishing user-groups for the common software packages (Listserver, meet once a semester to hear an expert) etc.