IAM Steering Committee Minutes - January 2008

Monday, January 7, 2008
4:00 - 5:00 p.m. MCB, 6A

Present

A. Wissmiller & H. Schmidt, co-chairs; J. Showstack, C. Tianen, O. Bawa, J. Cox, A. Dobson, G. Barbachov; Terrie Coleman, ITS - guest

DRAFT – IAM Objectives and Principles

  • Objectives and guiding principles are useful as filters for prioritizing IAM projects.
  • “Reduce costs” cannot be documented, however reduced password management costs can be (i.e. reduced number of calls to help desks) and should be tracked.
  • The most important guiding principle for the Medical Center is security.
  • The principles do not necessarily reflect implementation order: pilot projects can come before a project that serves the entire campus, for example.
  • A “toolkit” for departmental use is vital and should be a priority.

Heidi will route a revised draft of the Objectives and Guiding Principles for review and comment.

Project Prioritization Process

Heidi and Terrie Coleman are meeting with known IAM stakeholders to check assumptions and discover any “hot” areas in projects. They will summarize their findings before our next meeting on February 5.

Members stressed the necessity for establishing deployment teams and drafting contract templates for project/systems owners that will state responsibilities, expectations, timeline, objectives, etc. Each contract will necessarily be customized to each project. It would be useful for templates to be in the technical toolkit. There was discussion about the need to distinguish infrastructure from applications when phasing IAM deployments.

Short-term Targets

Andrew provided an update on the production readiness of the TIM/TAM environment and described a few activities currently underway – a proposed wireless pilot at Mission Bay, discussions about Sentillion integration with the Medical Center and meetings with SOM/ISU about integration with their security framework.

Technical Briefing

A separate 90-minute technical briefing describing the Identity system, TIM/TAM data flow, and technical architecture will be scheduled in March. The briefing will include a case study of a specific deployment, e.g. GALEN or Active Directory. Members recommended such a briefing should be held before each major implementation.

Service Manager Position

Members recommended the proposed IAM service manager position be viewed within the context of the broader organizational picture; which unit will be the ultimate functional owner of IAM; operational needs; the ability of the incumbent to transition from an implementation to support/maintenance manager.

Recorder: J. Evind

Back to main page.