NEXT MEETING: The next meeting of the ITC will be Friday, 8 December at 9 am in EPC 304C.

ACTION ITEMS: Note action items: i) charge to software subcommittee ii) call for names of other individuals who might be willing to serve on subcommittees

MINUTES
1) Logistics. We discussed the additional meeting now scheduled for Friday, 15 December at 9 in EPC 304C. This meeting will be dedicated to a thorough discussion of the issues raised so far. We also have tentatively added additional meetings for the 4th Friday in January and February. Again, this is needed to get a handle on the tasks ahead. We also discussed adding community involvement. We decided to extend an invitation to Dr. Terry Bishop, CIO for District 11, as our K-12 representative. We will ask Jerry to nominate an individual from industry.

2) Core principles. Jere mentioned the changes he made to the first draft. These were brought on by the discussion from the 20 October meeting. Specifically added 'Research Technologies' to the Critical Services and a blurb about 'Why IT?'. More discussion on this document will be possible at future meetings.

3) Urgent issues. In addition to drafting the Strategic Plan for IT, another role of the ITC will be to advise Jerry on urgent IT issues. One such issue is software purchases and licensing. With software companies shifting from a metered license approach to a per seat approach, the costs to the campus are skyrocketing. We need a process to help decide what packages should be supported in the open labs and classrooms. In the end, the issue of software is complex and warrants a subcommittee. In addition, if the software issue is significant enough to warrant a budgetary request, the campus budget process requires we submit such requests probably no later than 1 January. We took volunteers to form such a group: Jackie Crouch, Barney Yetter, Scott Switzer, and Jerry Wilson. **Charge: Develop a plan and recommendation for a basic package of applications. Consider per seat or site licenses. Determine costs and make recommendations concerning budget request. Ultimately develop strategy for supporting 'non-basic' packages.

4) Subcommittees. As item 3 indicates, there are many complex issues that the ITC cannot handle alone and must call on subcommittees. Besides software issues, another possible subcommittee might be a Policy subcommittee. Mark Malone suggested that we might use the Faculty Assembly committee: Academic Computing Policy Committee. This is a faculty committee. (Note: I attended the Faculty Assembly later on Friday and Richard Blade suggested that the ACPC consist of those faculty members who now participate in the ITC.) We will need to 'recruit' subcommittee members from outside the ITC ... **Charge: Please suggest names of individuals that might have an interest/stake in technology issues that we can ask to participate in subcommittees.

5) Issue library. We continue to work on the issue library. ITC members can submit issues via the web by visiting: http://www.uccs.edu/~jhaefner/itcouncil/input/input.htm Our meeting on the 15th will be dedicated to getting a better understanding of these issues. These issues will form the basis of a needs assessment.

6) IT Inventory, part II: Jerry Wilson outlined the policies and procedures of the IT Help Desk. Basic ideas: IT is implementing a workorder tracking system; priorities for help are: network, labs and classrooms, offices (in that order); working to establish robust appointment system - but communication needs improvement; IT does not perform hardware maintenance on computer equipment in faculty and staff offices.

7) Needs Assessment. We decided that a survey instrument will be needed regardless of whether or not we use focus groups. Jere and Sue B. will work on a very rough draft of this survey. Institutional Research might be of help as well.

8) Roundtable discussion. Jere discussed the Course Management System dialog. The results of the faculty focus group survey is available at http://www.uccs.edu/~jhaefner/itcouncil/input/CMS/cms.htm Events basically necessitated that we upgrade to WebCT 3.12; the Teaching and Learning Center will provide support for migrating from our current system to 3.12. Details to follow.