Skip to main content

My MidWest tour (Wisconsin-Madison, Michigan and Miami)


I very much enjoyed my recent trip to visit the EA teams at three Universities in the American Midwest.  My hosts were generous with their time and gladly shared their knowledge and experience of establishing Enterprise Architecture practices.  I learnt a lot about EA techniques and even more about the soft skills required to establish an EA practice for a large and diverse institution with a limited budget.

The topics of our discussions reflected the different priorities that the three institutions have set for their EA teams.  The UM-W team focus on major initiatives rather than try to map the overall space.  They provide EA input to assess which aspects of the current state need most attention and then helping with the transition to the new processes.  This seems to reflect the steer I was given by a Gartner consultant, to show some immediate business outcomes.

The other two institutions are taking a more systematic approach in that they are attempting to define certain artefacts across all organisation units of their respective universities.  In the case of UMich, the EA team is helping organisational units across the university to define and clarify their (IT) strategies.  They have a common framework for presenting this information and this has proved especially useful for those units who are developing a strategy for the first time.  The resulting catalogue provides context for the prioritisation and implementation of projects.  

The team at Miami U is mapping the current state of five domains: business capabilities, applications, data entities, infrastructure, and security, in order to provide a context for decision making.  For example, their CIO wants to use this map of the “as-is” state to avoid (or at least discourage) the procurement of new systems that reproduce existing functionality.

Apart from showing me a variety of EA techniques, this diversity illustrated the importance of clear goals for the EA practice.  EA is an immensely flexible discipline, so we need to agree what we want to achieve, depending on the strategy of the institution.

For the University of Edinburgh, our goal is to emphasise the development of our data architecture.  To this end, I intend to produce conceptual data model, a business vocabulary, and high-level target architectures for both BI and operational data.  As data cannot exist in isolation, we will also look at the business processes that produce and consume data, and the applications that produce, store and consume data.

This runs alongside the development of EA processes themselves, of course.  A secondary goal of mine is to define a roadmap for achieving level 2 in the EA maturity model.

Comments

Popular posts from this blog

Changing Principles

In EA, architecture principles set a framework for making architectural decisions.  They help to establish a common understanding across different groups of stakeholders, and provide guidance for portfolios and projects.  Michael Durso of the LSE gave a good introduction to the idea in a webinar last week for the UCISA EA community.

Many organisations take the TOGAF architecture principles as a starting point.  These are based on the four architectural domains of TOGAF: business, information/data, applications, technology/infrastructure.  These principles tend to describe what should be done, e.g. re-use applications, buy in software rather than build it, keep data secure.  See for example the principles adopted at Plymouth University and the University of Birmingham.

Recently though, I encountered a different way of looking at principles.  The user experience design community tend to focus more on how we should do things.  E.g. we should start with user needs, use iterative developm…

Why the UCISA Capability Model is useful

What do Universities do?

This may seem a strange question to ask and the answer may seem obvious.  Universities educate students and undertake research.  And perhaps they work with industrial partners and create spin-off companies of their worn.  And they may work with local communities, and affiliation bodies for certain degress, and they definitely report on their activities to government bodies such as HEFCE.  They provide student services and support.  The longeryou think about it, the more things you can think of that a University does.

In business, the things that an organisation does are called "capabilities", which is a slightly strange term.  I think it is linked to the HR idea of a combination of the CAPacity and ABILITY to do a task.  Whatever the name, it is a useful concept.  A capability is more basic than a process: a University may change the way it educates students but as long as it remains a University it will educate them one way or another.

A capability …

A new EA Repository

One of my goals since starting this job two years ago has always been to create a repository for architecture documents.  The idea is to have a central store where people can find information about the University's applications, data sources, business processes, and other architectural information.  This store will make it easier for us to explain our plans, to show the current state of the University's information systems, and to explain what Enterprise Architecture is all about.

It's taken a long time to reach this goal, mainly because we're often had more pressing and immediate work to be done.  The creation of a repository is one of those tasks that is very important but never quite urgent.  So I'm now very happy to say that we are in the process of deploying a repository and modelling tool.


This is the culmination of a careful process to select the most appropriate tool for our needs.  We began by organising several workshops to gather requirements from a rang…