ITANA Conference Call Minutes - May 26, 2011

---------------
Attending
Jim Phelps, University of Wisconsin-Madison (chair)
Chris Eagle, University of Michigan
Leo Fernig, University of British Columbia
Rick Francis, Gonzaga University
Paul Haller, Cardiff University
Paul Hobson, University of British Columbia
Rhys Smith, Cardiff University
Piet Niederhausen, Georgetown University
Steve Olshansky, Internet2
Julian Pietras, South Puget Sound Community College System

---------------
Face2Face Planning Update

See https://spaces.at.internet2.edu/display/itana/Face2Face+Meetings

• Registration is open for the F2G.
• You can register for just the ITANA F2F, or for the full conference.

---------------
Project Moonshot
(Rhys Smith)

See http://www.project-moonshot.org/

Project Moonshot is a JANET-led initiative, with the goal of enabling access management to a wide range of services and applications using a
single technology and infrastructure.

For more information on JANET, see: http://www.ja.net/

Discussion:

• This allows more than federated access, it can also be deployed as an enterprise-level service.
• Applications that use GSF should work, LINUX will work, and Windows will work. The problem is that GSF or XPI access need more development; this will be taking place over the next several months.
• Rhys or Paul would be willing to talk to other groups who are interested. Get in touch with either of them if you’d like to discuss.
• We may revisit Project Moonshot again in the fall.

---------------
Lifecycle Ontology
(Leo Fernig, Jim Phelps)

See: https://spaces.at.internet2.edu/display/itana/Lifecycle+Management+and+Analysis

The group would like to spend some time over the next few calls discussing ontology, and developing the concept.

“Lifecycle” as an architectural tool: there are several “lifecycles” that can be used to represent processes: student lifecycle, instructor
lifecycle, research lifecycle.

The document Leo shared can be found on the wiki: https://spaces.at.internet2.edu/download/attachments/25203676/LifecycleTool.pdf?version=1&modificationDate=1306431847431

Delta Airlines core diagram adapted (see slide 2): instead of “customer” experience, consider it a “learner” experience.

Discussion:

• On the core diagram, there are many tools/systems listed are those used at UBC. The primary purpose of the diagram is to help provide a backdrop for the discussion of the business analysis, and looking at the process from a customer point of view. In our case, the “customer” is a student.
• On the first diagram, employees are not included as part of the analysis.
• There may be more customer lifecycles to consider: learner, advisor, teacher. Some may be “sub”-lifecycles of other larger cycles: e.g. different employee types, different student types, etc.
• Is advising actor-based? product-based? or process-based? At UW-Madison, there is a type of tiered organization of advising.
• “Advising” may be one of the processes that supports “exploration.”
• Individuals may have multiple experiences: an aspect of IDM/multiple roles.
• Would like to continue this discussion, considering tools that can be used for developing the lifecycle represenations.

--------
Next Meeting: June 9, 2011
2:00 p.m. (ET) / 1:00 p.m. (CT) / noon (MT) / 11:00 a.m. (PT)