Conference Call Notes

Agenda for next call

1. Roll Call (by timezone - East to West)
2. Scribe Call Out

3. Architecture Tool Case Studies

4. Itana Org Updates (if any)

   1. Working Group Updates
      
      1. Wiki Refresh Working Group
      2. New2EA Working Group
      3. API Working Group
      4. Business Architecture Working Group
      5. Information Architecture WG
      6. EDUCAUSE Connect WG
   2. Steering Committee Update

Full program on the 2021-2022 Itana Program page. All calls (including working groups) are listed on the Events page.

Architecture Tool Case Studies

Itana Overview

J.J. Du Chateau: Architecture Tools is a recurring topic: should we get one? are they valuable? which tool does my institution need?  These are really more than diagramming and documenting tools... they are truly modelling tools with the promise of providing ways of creating and managing real insights.  What is the relationship between the cost of these tools and the value they provide?  They are so complex!  Some of them start with top-level constructs such as "Vision", "Strategic Goals", and "Business Objectives", but do we have common understanding of what those things actually are, and do we have them at our institutions?  Is the learning curve steep?  How can we get value from the resources and investment we must make in establishing these tools and upkeeping the repositories we create with them?

NYU Case Study

Henry Pruitt.  Overall goals as depicted below (includes the ability to answer application-architecture questions like "where are all the places we are running Java?" and "where are there opportunities to align the use of similar business solutions across the institution?" such as when we find there are fifteen separate instances of Salesforce).

...and sample questions (these are really valuable) to be addresses include:

The journey included the initial capture in a spreadsheet of hundreds of applications (including mappings expressed with pivot tables to key things such as business capability), and part of what needed to be addressed by introducing the ability to find architecture diagrams and architecture documentation.  One useful outcome of the TOGAF training was that architects were able to start speaking the same language.  Using some of the ServiceNow functionality (around CMDB and the application portfolio), noting that there was a requirement to change some of the labels and functionality (jeff = in the ServiceNow Common Services Data Model?).

Technology planning happening in spreadsheets is disconnected from the architecture context (e.g., Identity & Access Management spanning significant application services such as the future plans for LDAP and the future plans of the university-wide Person Registry).  The promise of the EA tool is to help bring this work together and achieve better outcomes for the institution.  Also looking for the ability to run basic reports across the architecture (linking applications to business outcomes and strategic objectives and organizational structure), etc.

Some alternatives to traditional/mainstream EA tools were also considered by the NYU team, acknowledging the overlap between the domains of "EA Tools", "IT Portfolio Analysis", and "IT Service Management" (jeff = and also like Strategy Execution Management):

Key considerations for selecting an EA tool include scenario-based planning and:

NYU has an pre-CAUDIT version of their own "front office" business capability model = note the pace-layer color-coding here:

...and the same approach for the "back office" business capablities:

...and the ability to create summary views such as this applications tree map:

...and NYU is also using Tableau to create reports (in dashboards that were influenced and shaped by engagements with Gartner) that show costs and TIME assessments and resources and health, all able to be sliced and diced by various dimensions of interest).