I.T. Master Plan

Timetable and issues list

May 7, 2004

 

1)      First meeting in fall: establish initial goals, solidify timetable

2)      By end of October:  Meet with divisions, committees and/or departments (invite them) to get feedback on what others think needs to be addressed

1.      note to all academic and administrative depts.. asking if they’d like to meet with us individually

2.      plan multiple open sessions by academic and administrative divisions

3)      create a list of wants/needs and prioritize into initial plan

4)      meet with same as above or hold general colloquy's to air the plan for feedback

5)      create final plan

                                                   i.      Set of goals (i.e. Support academic excellence)

                                                 ii.      objectives that support the goal (i.e., foster faculty research in teaching and technology)

                                                iii.      action plan to achieve the objectives (i.e. hire a statistics expert, provide 24/7 support)

                                               iv.      assessment plan to measure whether we achieve the goals

 

At our May meeting, we established the following areas to address:

 

Administration

            Use of Banner

            Refresh Banner training/analyze use

            Other systems that interact with Banner

            Expect all employees to have basic technology skills? How to measure and administer?

 

Policy: Continue to only do system critical modifications to Banner?

 

Infrastructure

            Replacement cycle

            Determination of when to replace/upgrade

            Set minimum bandwidth averages

            Review limits set on students

                        Time of day limitations

                        Downloading limitations

                                    Speed

                                    Copyright

 

Policy: Should the College take a stronger stand on downloading of copyrighted materials rather than leave the onus on students to comply with these rules?

 

Student computing

 

Policy: Should there be a set of graduation requirements for students to achieve that demonstrate their proficiency with technology and information tools?

 

Policy: Should there be a consequence for a student violating network policies- broadcasting traffic, worms, etc?

 

 

Instructional and research computing

 

Computer support

            Web site responsibility

                        Home page

                        Second level pages

                        Content vs. design

            Space issues; Help Desk, Web team, Repair shop, Networking, Programming

 

 

Policy: Should we continue our current method of distributing responsibility for Web content?

 

Policies

This one might be absorbed into each of the other areas rather than standalone. The question here is should there be a review process for new policies?

 

Security

Security vs. convenience

Access to on-campus resources from off-campus

Spam blockers

Network authentication

 

Policy: Do we put in place “commercial” spam blockers that might increase false positives?

 

Policy: Should the campus have an anti-Spam policy for on-campus mail? With penalities?

 

 

E-commerce

 

 

 

Additional information requested:

 

Network diagram

Corporate benchmarking for administrative usage/lead innovators