Versions Compared

Old Version 4

changes.mady.by.user Piet Niederhausen

Saved on

compared with

New Version Current

changes.mady.by.user Piet Niederhausen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

Attendees

  • Piet Niederhausen, Georgetown University
  • Dan Brint , State University of New York - ITEC
  • Glenn E. Donaldson, The Ohio State University
  • Phil Robinson, Cornell University
  • Vinay I. Varughese, Cornell University - Weill Medical College
  • Scott Fullerton, University of Wisconsin - Madison
  • Paul Erickson, University of Nebraska--Lincoln
  • Emily Eisbruch, Internet2 (scribe)

Agenda

  1. Roll Call (please add your name and institutions to the Attendees above)
  2. Welcome Emily Eisbruch at Internet2
  3. Agenda Bash (any working group report outs?)
  4. Minutes from last call
  5. Face2Face Meeting
    1. Your input on the draft agenda (see next section below)
    2. Case studies we can include
  6. Report Out -- Common Solutions Group meeting (see last page of this doc)

Face2Face Planning

The Face2Face meeting will be on Tuesday, November 6, as a preconference seminar at the Educause national conference in Denver, Colorado. The following is the work of the ITANA Face2Face Planning Committee.

Feedback from the 2011 Face2Face meeting

  • More case studies
  • More Enterprise Architecture 101 for new architects
  • More opportunities to interact and meet others (eg, mixing up tables during the session)
  • More practical stuff to take home
Agenda build

Additions to/comments on the draft agenda during the call are highlighted in green.

A. Disruptive Change in Higher Education - Why does architecture matter?

  1. Fundamental changes that are coming to higher education
  2. CIO’s view on Enterprise Architecture and change management
  3. Break-out session on disruptive change
    1. What disruptive changes to you see or foresee at your institution?
    2. See Diana Oblinger’s free e-book at http://www.educause.edu/game-changers

Break

B. Enterprise Architecture 101 - How do architects get started?

  1. Architects at all levels are leaders
  2. Questions you should be asking as an EA
  3. Case studies as an example of how you get things done
  4. Scott: What is the domain/scope of the architects work, and who are the consumers?
    1. Is it for conversation among key stakeholders?
    2. Is the goal to create new capabilities?
    3. Examples of different ways for an architect to engage, and what gets produced
    4. Adapting these tools to specific contexts and consumer needs
  5. Lifecycle Analysis as a framework for EA
    1. Starting conversations that wouldn’t normally start
    2. Connecting people who normally wouldn’t connect
    3. Linking initiatives that people haven’t thought about the linkage
    4. Focusing on the customers
    5. Highlights governance issues
    6. Forces you to frame your argument in business terms
  6. Capability Mapping
    1. A way to bring out the capabilities for a business unit
    2. A way to think about People, Process and Technology in neutral terms
  7. Using SOA as a model
    1. You need to be able to communicate value in each of the tiers of the enterprise
    2. You need to justify even technical work in business terms
  8. Dan: Examples of documentation, tools you use to do your job
  9. Break Out / Workbook Activity:
    1. Think of a something that you tried to sell that didn’t go well and how you might have sold it differently. (influence and other dimensions)
    2. You have seen some higher level artifacts, how would you have used them

C. Report out from morning session

  1. How do you add value as an architect
  2. How do you manage cost / reduce risk
  3. Gartner’s idea that you drive Fiscal Efficiency and Business Execution
  4. Disruption drivers vs. university reality.

Lunch

D. Applied Architecture - How do we practice architecture?

  • Case studies (this a list in progress of potential case studies)
    • DEM IT Services Capability Mapping and IT Realignment as an example
    • Advising Architecture Review Board and their Core Diagram
    • SOA as a way of dealing with disruptive change
    • Storage - general purpose storage, regulated data and explosion of personal data
    • Data architecture in an ERP implementation (Workday HR/Benefits/Payroll)
    • Dan: Real world example of documentation/artifacts and how they were used; or things that didn’t work
    • Scott: How can we create thematic continuity through the day? Pull through items from earlier in the agenda -- examples of disruptive changes and how they were resolved in real life case studies
  • Exercise in personal landscape scanning and planning a response
    1. Given a change scenario, how will you lead through that change?
    2. Various scenarios including distance education, BYOD, outsourcing of various university operations, big research data, business process changes
    3. Scott: Enterprise data management; as a necessary step toward SOA; control of research data; integration of ERP data; data bus -- as a response to:
      1. Need to open university boundaries, across internal and external solutions
      2. Clarity about security and privacy
      3. Quicker time to market, responding quickly with data
      4. New data that is digital-native; how to maintain, curate, preserve it
      5. Need for business intelligence in response to various drivers
    4. Each table gets one of the disruptive scenarios and think about how you would approach the problem
    5. Context, drivers and next steps
    6. Fiscal Efficiency and Business Execution

Break

E. Current and Future ITANA Work - How can ITANA help?

  • Reference architecture development
    • What questions would a reference architecture answer for you?  What kinds of questions would you like it to answer
    • What is does a reference architecture for HE look like to you?
    • Glenn: Starting point for those with no architecture yet
    • Scott: Layered; have to keep focus in the discussion
      • Systems
      • Business processes
      • Common core business systems and boundaries
      • Integration, middleware
      • Data models
      • Strategic goals
    • Scott: Does Kuali have a starting point?
  • Enterprise Data Management and BI
  • SOA working group materials (other than included above)
  • Report on current working group activities

Report Out -- Common Solutions Group meeting

Overall meeting agenda (June 13-15 at the University of Iowa)

Highlights - Cloud

  • Most institutions present are executing on a portfolio of cloud solutions with multiple solutions from SaaS to Paas to IaaS
  • A few institutions are considering replicating critical infrastructure in the cloud, such as SSO, DNS, email routing -- mainly to ensure continuous service
  • No good general solutions for provisioning and de-provisioning user accounts and groups across cloud solutions; discussion of OAuth
  • Progress on operationalizing cloud services, for example using Boomering and JMeter to monitor user experience

Highlights - VDI

  • In all case studies, there was significant concern about cost and ROI
  • Most case studies lean toward application-specific virtualization rather than full or persistent desktop virtualization, to limit costs
  • For the same reason most case studies lean toward a few applications that need to be virtualized for security or because of special platform requirements
  • BYOD is both a challenge and a promise; users are increasingly just interested in applications, accessible on any device, and virtualization can help support new devices such as tablets