Joint Operations Group (JOG) and
Communications Planning Group (CPG) Meetings
 
May 5-6, 2003
UC Santa Barbara

Meeting Notes

Agenda

Logistics

Meeting Notes

Presentations

Campus Reports

JOG Home
 

     

    Notes from the May 5-6, 2003 JOG/CPG Meeting

    Creation of the UC Information Technology Leadership Council (ITLC)
    (formerly Joint Operations Group [JOG])

    1. A new charter for the Information Technology Leadership Council (ITLC) will be developed. A small group (K. Orgill, Kris Hafner, John Bruno, Rich Kogut, Jack McCredie, Jim Davis) volunteered to develop a draft charter for review by the ITLC.

    2. An ITLC Steering Committee will be formed, consisting of 5 members (UCOP and 4 campuses) selected by the ITLC membership. Steering Committee terms will rotate to ensure continuity during membership transitions. The Steering Committee will set agendas for subsequent ITLC meetings and workshops.

    3. ITLC members will share responsibility for hosting meetings on a rotating basis.

    4. Campuses and UCOP will designate up to two ITLC members. National laboratories and Medical Centers will each designate one ITLC member.

    5. ITLC meetings will occur 3 times /year, with a one and one half day agenda, including evening dinner (or some variation of the above.). UCOP will continue to provide staff support and meeting coordination logistics to ITLC members and hosting campuses.

    6. Several UCOP-initiated ITLC conference calls will be scheduled between meetings to provide a more regular forum for issue resolution and information exchange.

    7. A number of ITLC standing committees and special interest groups (e.g. CPG) will be formed, with a designated convener and appropriate UCOP, campus, lab and medical center membership. These groups will meet independently of the ITLC, but will provide leadership in specific on-going areas of IT-related interest to the University and to the ITLC. They will report regularly to ITLC on the status of issues and projects underway. Examples of potential standing committees or special interest groups include :

      • An email group to explore state of the art products, best practices, integrated solutions and emerging needs (e.g. secure e-mail)
      • An IT funding strategies group to share campus models, develop new models (e.g. technology fee) and approaches to gaining support for continued IT investment
      • A group to further exploit UC wide software licensing opportunities
      • A UC-wide disaster recovery group

    8. The ITLC will develop a mechanism for selecting and tracking priorities, initiatives and technology topics (see note below) to pursue. One or more individuals will serve as the focal point for tracking and reporting on activities and information about each topic.

    9. The ITLC will establish a set of ongoing relationships with relevant national and statewide organizations in the IT area (e.g. CENIC, Digital California Project, Common Solutions Group, Internet2, etc.) Liaisons should also be created with UC groups and constituencies such as the California Digital Library and UC library community, media directors, teaching and learning technology group, California Institutes for Science and Technology, etc. The ITLC liaison will follow the activities of each organization and report to the ITLC.

    Suggested Technology Topics to Track (see # 8 above)

    • Telephony (VOIP, etc.)
    • WiFi
    • Learning management / Distance learning tools
    • Enterprise Email/calendar
    • Mobility technologies, virtual collaboration, messaging
    • Web services
    • Digital archives
    • ERP systems in higher education (and UC legacy system migration strategies)
    • Authentication / Identity Management (middleware)
    • Directories
    • Portals/content management
    • Research support, Grid computing
    • Digital rights management
    • IT Security (firewalls, intrusion detection, spam, virus protection, etc.) and privacy
    • Advanced networking, peer to peer

    Proposed Next Steps

    • UC institutions designate ITLC representatives (July 1, 2003)
      • Listserv created to reflect new membership
      • Old "JOG" listserv retained to communicate with the broader IT community
      • UCOP Web site changed to reflect new name and structure
    • ITLC members submit (to Kris Hafner) nominations for first round of ITLC Steering Committee members (July 15, 2003)
    • Draft charter developed for review by ITLC group (July 15, 2003)
    • New charter finalized at September, 2003 ITLC meeting
    • ITLC creation communicated formally to UC constituencies (July 15, 2003)
    • Convener identified for the CPG group (July 1, 2003)