Page History
...
(0) Roll Call. Agenda Bash
1. Accept minutes of last call
2. Enterprise IT Capabilities - see Surveys of Key Enterprise IT Capabilities (Hebert)
3. Report out of Architecture Tool presentation (Mark P)
4. St. Louis University's Pillars and Value Chain Documents - see Value Chain and Pillars (Jim H)
5. Re-structuring of the wiki (Jim P)
6. CIO Survey on Enterprise Architecture (Jim P)
(99) Next steps, next call
**Action Items**
Wiki Markup
Wiki Markup
\[AI\] Jim Phelps will start to formulate an "Educause CIO" survey on the wiki.
Wiki Markup
\[AI\] Group: Consider the EA survey framework and begin defining the maturity levels. Start sharing information on the wiki in preparation for starting the nuts-and-bolts on the next call.unmigrated-wiki-markup
\[AI\] Jim Phelps will contact Richard Katz about ECAR's survey capabilities.
**Action Items from Last Call**Jim Phelps is waiting for the University of Wisconsin's RFP for content management systems to be made public, then will post a link on the ITANA wiki.Jim Hooper provided the details of his work on value chain mappings to applications and to St. Louis University's pillars of architecture. The information is on the ITANA wiki: https://spaces.at.internet2.edu/display/itana/Home*
\*
**EA Survey**
Hébert posted a draft of an Enterprise Identity Mapping (EIM) capability and maturity survey to the ITANA wiki:
https://spaces.at.internet2.edu/display/itana/2007/08/28/Enterprise+Information+Management+Capbility+Survey
...
- Define key areas of EA
- Determine levels of EA maturity at institutions
Wiki Markup
Another key question is whether the points in the draft survey represent the right measures of maturity. One measure, for example, asks whether faculty understand the value of information and see it as a differentiator. Is this a good measure? Just establishing what "maturity" means is important. In some areas, faculty involvement is deemed to be very important, but other areas are administrative in function.
Jim suggested that the survey could provide a summary of maturity around key technical areas. If done each year, the survey would also provide longitudinal data. One suggestion is for the working group to establish and clearly define the levels of maturity, then approach the Educause Center for Applied Research (ECAR) about conducting the survey. This may complement the "core competencies" survey that ECAR already conducts.
Wiki Markup
Wiki Markup
**Wiki Organization**
Jim Phelps reorganized the wiki and asked for feedback from the working group. Hébert suggested an area that gathers "working documents" for the group to edit, and another that would archive final versions, as well as information gathered from elsewhere. Also, a separate section for minutes and agendas would be helpful. Another idea is to organize by specific areas of discussion (SOA, technology infrastructure issues, business process analysis, etc.)
Wiki Markup
**Educause CIO Survey**
Jim had a discussion with a person at Educause about conducting a survey of CIOs concerning Enterprise Architecture. The survey would explore such areas as the different ways architecture is done, where EA reports and other facets of EA. Jim will begin posting potential survey questions on the wiki for group editing and feedback. The object is to have a survey out to the Educause CIO list and report out at the Educause meeting.
**Wisconsin RFP for a Content Management System**unmigrated-wiki-markup
Jim Phelps will place on the wiki the University of Wisconsin's RFP for a content management system. A discussion ensued about campuses that have successfully deployed a CMS that is encompasses most of the university, as opposed to having many units making their own decisions. \ [AI\] Jim will review the RFP to see if it includes any information on well-deployed systems.
**Next call: September 7, 2:00 pm (EDT)**
Overview
Content Tools