Possible IT structures sent to me

Several people have asked that I describe the IT structures people sent to me after I asked for them in open meetings and before I developed version 0.5. You'll see that I learned (AKA stole) a lot from them.

Here they are:

• A model with three groups:
  
• Enterprise computing
• Networking
• Enterprise systems (Banner, PeopleSoft, WebCT, Pipeline, etc.)
• Security
• Data Center
• Audio-Visual
• Administrative computing
• Budgeting
• Purchasing
• Planning
• Licensing and Maintenance Management
• Inventory Control
• Support Services Computing
• Hardware/Software support
• Academics
• Administration and Advancement
• Business and Finance
• Facilities and Engineering
• Student Services
• Instructional/Curriculum Support
• Design and Development

• A centralized model
• VP for IT
• VP's staff
  
• Director, IT security
• IT administrative support
• Director, Help Desk
• Assistant VP, IT Development Services
• Assistant VP, Enterprise IT Systems
• Director, Network Systems
• Director, Business Systems
• Assistant VP, IT User Services
• Director, IT Student Services
• Director, IT Faculty/Staff Services
• Director, IT Computer Lab Services

• A model that addresses types of services rather than an IT structure per se:
  Three service segments
• Core Service
• Customer Service
• Customer Needs
• The service segments can be further divided into sections to represent specific services

• A model with five main categories:
• Classrooms and Labs
• AV Equipment
• Lecture Halls
• Management of Lab SA’s
• Card Access
• Student Support
• Faculty and Faculty Support Staff
• Software and hardware support
• Training
• Infrastructure
• Telecomm
• Software Development
• Enterprise Application Support
• Communications
• Graphics Services
• Library Systems
• Security
• Operations
• Server Support
• Networking
• Admin (non faculty support staff) Support
• Alumni House
• President’s Office
• IRP
• Business and Finance
• ETC…
• Administrative Application Support
• Management
• Planning
• Budgeting
• Coordination
• Assessment
• Asset Management
• Notes:
• Somewhere within all this would be user account management. Probably, though, like we have now in some cases, each group would access servers somewhere to manage their own group of user accounts.
• Whatever the case, you need to have that single point of contact for all things and an inbound call center with solid first level support and an online database for first level techs. You’d have different levels of escalations, prioritization of issues based upon importance, etc.

On a related note, here's a structure discussed last year by the ad hoc IT reorganization committee (whose work was suspended in light of all the management changes and acting appointments at that time).