CSU, Chico – Administrative Technology Council Meeting Notes
Meeting Date: March 11, 2009
Meeting Location: MLIB 338
ATTENDING TEAM MEMBERS AND GUESTS
✔
Post, Bill
✔
Mox, Andrea
✔
Ringel, Jerry
✔
Quinto, Ray
✔
Weddington, Phyllis
✔
Banks, Brooke
✔
Post, Linda
✔
Rosenow, Tom
✔
Hafer, Robyn
✔
Kissinger, Beth
DISCUSSION ITEMS
1.
Council draft charge: Bill discussed the reason he convened the council – to create a formal for discussion
about common application requirements, standard methodologies and tool sets, and allocation of resources.
The council is designed to provide cross divisional strategic and tactical planning to leverage campus
technical resources re infrastructure, common tools/standards, and non-duplication of effort.
2
Council structure: Reports to the CIO and up to the Chico Information Systems Committee (CISC). Jerry
and Phyllis will co-chair. Representation from AA/SA, B&F, UA, USRV, EAPP, ESYS, ISEC, ETPS.
Representation provides a technical – functional interface. Others areas may be added later. Initial meeting
outcomes will be discussed with CISC for approval to continue council activities.
3.
Council discussion: Effective use of technical resources to address the needs of functional staff. Group
discussion identified the following topics for future attention:
 Business Continuity/Disaster Planning – where does this responsibility reside
 Sharing of initiatives
 PCI – do not rebuild the wheel
 Carrying the council’s message to units
 Education and Planning opportunities
 Security
 Clear project definition and how projects meet the needs of the university – create a culture of
project description and documentation
 Cross training and back up
 Common framework for discussion
 Project visibility – common tools for planning and documentation
 Definition of project (beginning & end); phases, examples
 Create common culture for talking with/among staff
 IRES project submittal process, approval process, documentation (one sheets)
 Introduction of projects to wider audience
 Technology service cost models
 Numerous ticketing systems – consolidate on one
4.
Meeting schedule: Will meet every two weeks initially, likely less frequently in the future. Sub-groups will
meet to focus on specific topics.
5.
Handouts: Technology Development Council Draft Charge; Chico Information System Committee
discussion – Creation of an Administrative Technology Council.
TO DO LIST SUMMARY
#
1.
2.
3.
4.
Task
Schedule next meeting
Top 3 projects in your area
Identify project you want to know about
List of current technology
FUTURE MEETINGS
Date: March 26, 2009
Responsible Party
Phyllis
All
All
All
Time: 3:00 – 4:00
FUTURE AGENDA ITEMS
SA server consolidation – SQL server
Centralized vs decentralized – which makes sense
SMS – Footprints demo (Jerry/Andrea)
Priorities
Vendor issues
Central IT tasks/services
Regular meeting time
Due Date
ASAP
Status
Done
Place: MLIB 338