Common Systems Group (CSG)

 

February 28, 2006

Meeting Summary

 

 

CSG Attendees: Paul Craft, Jim Davis, Jason Frand, Bill Jepson, Carol King, Michelle Lew, Kathleen O’Kane, Tom Phelan, Sean Pine, Nick Reddingius, Vincent Riggs (for Max Kopelevich), Terry Ryan, Mike Schilling, Marsha Smith, David Snow, Eric Splaver, Kent Wada, Esther Woo-Benjamin, Don Worth

 

Guests: Joel Bellon (PDP participant), Diane Blake (CTS)

 

Agenda

 

1)   Revised Incident Tracking Response Diagram and Process Document

 

The Incident Tracking Response process has been modified to include the role of the Applied Security Task Force (ASTF). The ASTF is available to provide assistance with problem analysis if called upon by a department IT representative.

 

A planned enhancement to the process that is currently being developed is a trouble ticketing system that is a campus-wide database of all incidents. The CSG recommended implementation of an online form for capturing the necessary information.

 

An unanswered question is how DMCA issues from the RIAA with home users coming in through the VPN are being handled.

 

The target rollout for this process is Spring quarter 2006.

 

Actions:

·        The CSG was asked to document their local departmental process using actual experiences, and note how well it maps to the Diagram. Diane Blake offered to meet individually with members that would like help with mapping.

·        At next CSG meeting, run through some examples.

·        At next CSG meeting, endorse the process.

·        Gather examples of a telecommuting policy, specifically around the risks (viruses, RIAA file sharing) and bring back to CSG (to address the issue of how we handle DMCA issues from the RIAA with home users coming in through a VPN).

 

2)   Update on Governance

 

The campus IT governance structure is being reviewed to clarify the committee roles around campus wide applications/functional systems and implementation strategies. Two drivers of this review are 1) the governance process has not been effective in disseminating information and gathering feedback; and 2) the need to look ahead to address future IT issues. Governance discussions have resulted in a potential change of the CSG membership because CAOs are not represented in the current governance structure and need to be included in a more direct way. The CSG was in agreement that CAOs should be included and several options were discussed and debated.

 

·        Option 1 proposed forming a separate representative CAO group that parallels the current CSG. The two groups would have coordinated agendas and notes and recommendations would be shared between them.

·        Option 2 proposed forming an integrated CSG and CAO group with membership drawn from CCC, Administrative IT Directors Group, Academic CAOs, and Administrative CAOs.

 

There was strong CSG support for Option 1 with the addition of periodic joint meetings. Other recommendations include:

 

·        Don’t remove any current CSG members (don’t break something that works)

·        Have joint CSG-CAO sessions, but don’t co-mingle the two groups

·        Form CAO group that meets quarterly with the CSG. Continue monthly CSG meetings.

·        Let CAOs join CITI

·        Let CITI members attend CSG

 

Actions:

 

·        Bring Governance back as first agenda item for next meeting.

 

 

3)   Repositioning IT

 

Marsha Smith reported on the status of current projects: Network, Email, Data Center, Security, and Funding. She also reported on next steps for the Next General Network Architecture and Service Design Team, UCLA eMail, Messaging, and Calendaring System, and Applied Security.

 

Actions:

 

·        The CSG was asked to identify the set of end user services that need to be in place (in a rapid way) in order for the UCLA eMail, Messaging, and Calendaring System service to work. Some that have already been identified are:

 

o       Password reset

o       New account creation

o       Account suspensions

o       Accessing mail boxes (2nd party)

o       File restores

o       Message recall (from accidentally hitting ‘send’)

o       Guest accounts

o       Access to CTS staff or tools

 

·        The CSG was asked to describe how these services are currently being handled by local unit frontline staff.

 

 

Meeting Schedule for Remainder of 2006:

 

Tuesday

March 28

2:00 – 4:00

2121 Murphy

Tuesday

April 25

2:00 – 4:00

2121 Murphy

Tuesday

May 23

2:00 – 4:00

2121 Murphy

Tuesday

June 27

2:00 – 4:00

2121 Murphy

Tuesday

July 25

2:00 – 4:00

2121 Murphy

Tuesday

August 22

2:00 – 4:00

2121 Murphy

Tuesday

September 26

2:00 – 4:00

2121 Murphy

Tuesday

October 24

2:00 – 4:00

2121 Murphy

Tuesday

November 28

2:00 – 4:00

2121 Murphy

Tuesday

December 19

2:00 – 4:00

2325 Murphy