Information Technology Resource Allocation Policy
Approved: November 16, 2001
Last Reviewed: 09/20/2011
Last Modified: 09/20/2011
Responsible Office: Information Technology Services
Introduction
Santa Fe Community College acknowledges that Information Technology (IT) resources and services are essential for support of the College’s mission and goals. Therefore, it is the policy of the College to provide, to the extent that financial and human resources allow, appropriate allocation of IT resources for academic and administrative areas of the College.
Information Technology Resources
IT resources encompass all forms of technology used to create, store, exchange and use information in its various forms of voice, video and data, as well as the human resources and contracts required for the support of IT resources and services.
Examples of IT resources:
- Wiring and wireless infrastructure for voice, video and data
- Network electronics for voice, video and data
- Mainframe and server technology and operating systems
- Desktop computers, printers and scanners
- Telephone systems
- Interactive voice response systems
- Video conferencing systems
- Administrative application software and systems
- Academic application software and systems
- Desktop productivity application software
- Telecom lines for voice, video and data
- Maintenance and service contracts for IT resources
- Salary and benefits in direct support of IT resources and services
- Professional development of IT staff
Examples of what is NOT an IT resource:
- Personal Digital Assistants (PDA)
- Non-networked audio/visual equipment and services
- Stand-alone copiers
- Library database subscriptions
- End-user training
- Courseware development
- Computerized student testing systems
Allocation of IT Resources
To ensure equitable balance between all areas of the college, allocation of IT resources shall be a representative and participatory process linked to College planning and budgeting processes.
Link to college planning and budgeting processes
The allocation of IT resources shall result from college planning and budgeting processes. College planning considers IT issues and trends when formulating the College Strategic Plan which in turn drives IT Planning. The annual IT Plan is aligned with the College mission and goals, and contains prioritized initiatives with measurable outcomes, realistic budget estimates and required IT resources. Given the allocation of resources, service level agreements may be created or updated to reflect levels of IT services the College can provide.
Representative and participatory process
The allocation of IT resources shall be determined by the AVP for Information Technology Services with input from the Technology Advisory Committee (TAC) and approved by the Presidents Staff. TAC represents stakeholders from all College communities and is responsible for identifying the needs, expected outcomes, priorities, service levels, and resources for initiatives contained in the IT Plan. The AVP for Information Technology Services shall prepare the IT Plan and associated budget requests, SLAs and resource recommendations. The Resource Planning committee will approve the IT Plan and forward their recommendations to the President’s Staff for approval and appropriations.
Priorities For IT Resource Allocation
IT resources shall be allocated based on the priority of needs. Needs are determined through the College planning processes, and shall be transformed into programs or initiatives and classified as either “Must Do” or “Should Do”.
"Must Do" initiatives and programs are the top priorities. They are typically mission critical, required by code or law, essential to insure privacy, security and safety, or are driven by economic factors.
"Should Do" Initiatives and programs are prompted by the needs to stay competitive, improve efficiency, add value, create opportunities, improve services, and respond to the demand for more services. If not funded, these needs will eventually become “must do” initiatives.
Priorities are recommended by the Technology Advisory Committee.
History
11/16/2001 – Approved 09/20/2011 – Reviewed