Administrative Computing Committee Charter
The Administrative Computing Committee reports to
the President. It also serves to advise the University's Chief Information Officer
and the President's Cabinet. Its minutes are subject to the scrutiny and review of
the Andrews University Senate. This committee meets at the call of the chair at
least once per quarter.
Georgetown University has four Technology
Charters from two other colleges are listed here as samples:
The following is from http://www.ohlone.cc.ca.us/org/acc/.
- Provide recommendations to the President's Cabinet concerning strategic policies and
directions for administrative information systems.
- Provide recommendations to Information Systems department regarding operational
priorities and system enhancements.
- Recommend policies and priorities related to the selection, implementation, and
operation of administrative information systems.
- Develop the Technology Plan for administrative information systems.
- Provide communication and administrative information system status reporting to
constituent groups and existing councils and committees.
- Coordinate the work of specially appointed Task Groups as required.
- Recommend allocation of resources to specific projects.
- Identify short and long term goals for administrative information systems.
- Recommend standards for College hardware and software.
- Participate as needed in building and remodeling plans involving administrative
- Provide recommendations to appropriate college offices for training and staff
development for the use of administrative information and communication systems.
The following is from http://www.bucknell.edu/committees/ACC/.
Administrative Computing Committee Charge
The Administrative Computing Committee (ACC) is charged with making policy
recommendations concerning the administrative computing and networking support functions
of Computer and Communications Services (CCS) and Information Services & Resources
(ISR). ACC also provides advice as appropriate to CCS, ISR, and/or the President's Staff.
ACC is responsible through the Associate Vice President for Information Services and
Resources to the Vice President for Academic Affairs and the President's staff.
The Administrative Computing Committee shall consist of fourteen voting members, as
- Associate VP for Information Services & Resources, ex-officio
- Associate Director for Computing and Information Services, ex-officio
- Administrative Conversion Project Leader, ex-officio
- Representatives from seven major user groups (designated by each office):
- Dean of Students, Enrollment Planning, Finance, Personnel Services, Library, Registrar,
- Representative from academic affairs (designated by VP Academic Affairs)
- Representative from two other offices (designated by ACC)
- Faculty representative (designated by ACC)
- Student representative (designated by ACC)
- Other representatives may be included, without vote, as resources to the Committee
The chair will be elected biennially in September by the Committee from among the
The following are among the broad categories of responsibility appropriately within the
purview of ACC:
- Policy advice to President's Staff
- Strategic planning for information/technology in administrative and academic support
- Vendor relations, including participation in user groups
- Architecture of administrative systems
- Custodianship of administrative data
- elimination of duplication of effort and redundancy of data
- interfaces to external resources
- Guidance in allocation/prioritization of resources
- microcomputers; funding issues
- CCS staff time
- major projects
- training needs/initiatives for users
- training needs of CCS staff
- levels of service
- Forum for the exchange of information
- forum for concerns to CCS
- sounding board for CCS initiatives
- forum for sharing of information among users
- feedback channel between campus community and CCS
- Definition of standards
- levels of computing required to support administrative users
- useful life-cycle of equipment
- access to printing
- Explore other sources of funding
Monday, January 6, 2003 12:11 PM