
Ocotillo Retreat 99 Flagstaff, AZ May 18-19, 1999

welcome
location
agenda
discuss
photos
evaluation
next steps

This was one of the technology issues small groups brainstormed solutions/suggestions in the 'café' sessions. A summary report is from the discussions on day 2.

go to:
ocotillo central
|
Ocotillo.retreat.99
(café)
ISSUE: Technology Cost/Replacement
QUESTION: What are the ways colleges can classify technology use and prioritize for equipment upgrade / replacement / recycling? How can costs of software, upgrades, and human support be tied to capital purchases?
e.g. levels of users, locations of use (lab, office, mobile)
IDEAS:
- Continuously evaluation of need cyclical process of replacement
- Match level of user to level of equipment for perfect ratio
- Communication between ITS and Instruction
- Prioritize people and their need. Also prioritize functional needs e.g. classroom, library, office, labs. People: students, faculty, admin support
- TLTR be supported to make more of an impact on decisions re: software and memory, upgrades, re-allocations
- Survey students for feedback on their needs for technology increase communication access/avenue
- For every dollar of capitol allocate, say .25 cents towards operation/support/staff/software
- Tie it ratio of computer unites = related to # of support staff
- Ratio of # of 'technology using' classes to support staff
- Trickle down upgrades each 3-5 years. Use a cost benefit analysis to categorize based on need
- Clarification of technology use vs. prioritization of equipment upgrades are not necessarily tied together
- Centralized the prioritization for technology capital decisions e.g. Dean of IT responsible for all technology computer decisions.
- Tie Fees to capital requests
- Upgrade only when needed
- Classify - computers for student needs first - faculty who teach computers - faculty who use computers to enhance instruction
- Build an operational budget plan that ties technology allocation to support, training, and software
- Classify on core values - goals
- Holistic approach; look at requests as packages equipment, support, software, etc.
- Allocation by needs based on individuals capacities
- Faculty who are doing things for students
- Replacement cycle vs. cost long eye/how cost
- Student fees reflect cost of technology
- Restrictions on admin/faculty use by needs who determines
- Technology users group t" hat decides and assess technology needs throughout the group and allocate resources through this plan
- Program growth that includes certificate programs, facility growth, new classrooms and remodels
- Low technology must be assessed and replaced everyday!
- Holistic approach to planning that would related to capital requests to technology plan, support needs
- Mostly new computer hardware/software to courses that need state of art systems. Prioritizing labs/classrooms scheduling to software needs
- Costs such as security, training, support and maintenance may need to be calculated into true costs of obtaining "new" capital
- Move students to computers- not computers to students
- Don't always let district "standards" drive all decisions
- Faculty should be provided with hardware and software prior to expending on facilities and students (course development)
- Adequate compensation
- Capital bond for technology should include technology personnel and all hard resources (a separate pay category for technicians for which capital funds can be used)
- Create a master technology plan; prioritize user levels as high/medium/low
- Capital expenses tied to campus strategic plan
- Categorize by functional groups and rate user type by high/medium/low
- Revise budgeting process - make more flexible - systems approach to budgeting so as to consider personnel needs and software when purchasing capital
- Classify by use: lab, classroom, instructional; driven by curriculum applications
- Administratively by responsibility or task instructional priority, guideline driven
- Formula for support per desktop
- Capital expenditures should be tied to the strategic plan
- Automatic commitment of operational dollars per capital expenses
- Prioritize based on function, need for standards
- Prioritize based on academic program e.g. Microsoft certification
- Manage resources, target specific application computer installations e.g. Word and Netscape ... only
- Conduct "functional audit" of technology to determine priorities and support costs
- Purchase or lease options include: Training, set-up, configuration
- Classify by criticality of need
- The criticality of needs to capital
- Develop common annotated cost matrix
- Consider total cost of ownership for technology budgeting. Include life cycle technology budgeting and support
- Consider "buy low $ end and turn over faster" to ensure average quality of computing environment vs. buy high dollar and keep forever
- Strategize to developmental planning -- instructional technology plans
- Plan for growth in base of computers
- Consider facilities implications of increasing technology available (e.g. networking old buildings without conduit)
- Classify based on: learning, teaching, administrative, training, skill level of user, user friendliness and relevant for task
- Prioritize: needs of students, remain current with internal and external entities
- Bundle purchases "hardware and software". Develop ratios ex: for every 10 computers purchased hire one support person ex2: for every three people hired, hire one person for recruitment and selection
- Organize / recycle based on type of use. Distinguish between high end and low end users
- Bundle equipment with software and technical support
- Bundle individual purchases from different colleges to ?? better prizes or higher quality
- Assess the support cost associated with equipment and software purchases
- Trade equip and software with other college
- Set priorities that match the colleges priorities - tie measures to institutional measures
- Replacement - needs to be formula driven; 1/5 of total is not realistic since you may not have capital dollars to do this
- Technological happens so fast, we are planning for something we don't know what to plan for
- Tie increases and operational support to capital purchases
- Examine job placement system purchased than afterward ask who will run the system
- Evaluate user/usage requirement; Establish standard set of software tools and desktop platform; appropriate for learning outcome (job); Low cost PC, define standard cycle of upgrades (phased approach)
- Desktop shouldn't be capital; concurrent software (mentoring)
- Tie costs to headcount just like benefits; total cost formula based on capital expenditures to people, equip, software,
- Capital is wrong place to tie it - rewarding for spending more money
- Prioritize by rewarding the productive users; Leverage cost of capital expenditure through centralized purchasing
- Criteria for upgrades: competency-based, classroom instruction
- Electronic survey of usage
- Prioritize job skills vs. tools for teaching/learning
- If technology is used to learn job skills than this should be given highest priority
- Older versions of technology can be recycled to classes where technology is used for learning purposes i.e. word processors
- Be sensitive to impact of technology acquisition related to staffing, classrooms, space, supplies, infrastructure, etc.
|